So there seems to be a bit of confusion surrounding the DI01 ota update that's coming out to Fascinate users. Hopefully I can shed some light on the situation and prevent some people from spending lots of quality time with Odin.
The update is not a "full" update. The update package will simply patch your system as part of the upgrade, instead of deleting/replacing files. So, if you've made changes to any the files that it is looking for, the signature check will fail, and your update will FAIL.
So, you basically have 2 options. Either restore back to complete stock using the Odin files here, or find another way to update that will compensate for your modifications. If you're not running a stock configuration, then DON'T take the update!
Personally, I was only interested in getting rid of the update nag and updating my radio, instead of taking the full update. So, I stripped down the DI01 update and repackaged so that it will only flash the modem.bin and replace build.prop to make it look like you're running the newer software. Please find the zip attached to this post. Just put it on your sdcard and apply. This file will work if you're rooted/de-bloated/lag-fixed/whatever. If you've made any mods to build.prop then you'll need to re-do them.
NOTE: if you want to flash the attached zip you will need to either use the CMWrecovery.tar from here or flash it using clockwork recovery.
EDIT: replaced attachment with one that copies over a complete build.prop instead of patching the existing one.
What is considered messing with the build.prop? I've changes my dpi, will that make this update fail?
edit : yep it fails the verification on build.prop I'm going to try changing it back to 240 and see if it passes
Rooting after the SCH-I500.DI01 Update
adb shell
cd /data/local/tmp
./rage*.bin
wait....
when it brings you back to your original shell in windows then follow these commands
adb shell (you should see # this time instead of $ this is exactly what we want)
cd /system/xbin (or /system/bin if your files are there)
chmod 4755 su
chmod 4755 busybox
exit
Here is a before and after of the permissions:
Code:
# ls -l su
-rwxr-xr-x root shell 26264 2010-09-11 23:09 su
# ls -l busybox
-rwxr-xr-x root shell 1867568 2010-09-11 23:11 busybox
#
# chmod 4755 su
# ls -l su
-rwsr-xr-x root shell 26264 2010-09-11 23:09 su
# chmod 4755 busybox
-rwsr-xr-x root shell 1867568 2010-09-11 23:11 busybox
Exactly what I want but it fails on update.
Whole file signature failure.
Changed my build.prop back to stock and it still fails the hash check. Anyone know how to correct it back to stock ?
added a note to the op
so we just flash it through clockwork??
jt1134 said:
added a note to the op
Click to expand...
Click to collapse
Bingo, worked, thanks! You da man.
bubbleywine said:
so we just flash it through clockwork??
Click to expand...
Click to collapse
That's what I did and it worked.
i did this even though im not to sure on what the fixes are lol
So out of these things
Instant notification of Visual Voice Mail in the messaging bar.
Improved sync between phone and e-mail accounts.
Prompt notification when switching to airplane mode.
Faster switching from 3G to 1x RTT.
Search phone while on a call.
Improved Exchange password alerts.
No Service audio alert removed.
what does this zip not update?
justaguy17 said:
That's what I did and it worked.
Click to expand...
Click to collapse
How did you flash it using clock work recovery?
ckochinsky125 said:
How did you flash it using clock work recovery?
Click to expand...
Click to collapse
open rom manager go to install rom from sd card scroll to the bottom select the zipu want to install then a box will come up to clear data or back up u dont have to click either of those u can back up if u want but the back up will be with out the update
ckochinsky125 said:
How did you flash it using clock work recovery?
Click to expand...
Click to collapse
In CWRecovery there's an 'apply zip from sdcard' option.
dialect129 said:
So out of these things
Instant notification of Visual Voice Mail in the messaging bar.
Improved sync between phone and e-mail accounts.
Prompt notification when switching to airplane mode.
Faster switching from 3G to 1x RTT.
Search phone while on a call.
Improved Exchange password alerts.
No Service audio alert removed.
what does this zip not update?
Click to expand...
Click to collapse
We don't know.. We hope it's 3G to 1x and no service audio alert.. I would be very grateful if someone who applied it could test the no service audio alert though.
I can't get my signal to drop at my house. VZW signal is too strong, even inside my microwave.. (where I get 3 bars, apparently)
namebrandon said:
We don't know.. We hope it's 3G to 1x and no service audio alert.. I would be very grateful if someone who applied it could test the no service audio alert though.
I can't get my signal to drop at my house. VZW signal is too strong, even inside my microwave.. (where I get 3 bars, apparently)
Click to expand...
Click to collapse
Does switching to airplane mode produce the same sound?
justaguy17 said:
Does switching to airplane mode produce the same sound?
Click to expand...
Click to collapse
No.. you can't control when the sound happens, you have to lose signal.
namebrandon said:
No.. you can't control when the sound happens, you have to lose signal.
Click to expand...
Click to collapse
No, actually turning it to airplane mode and turning it off does produce the lost signal sound.
bomber889 said:
No, actually turning it to airplane mode and turning it off does produce the lost signal sound.
Click to expand...
Click to collapse
when i turn airplane mode on it gives me a nextel bleep kind of sound
I understand guys, the fix doesn't hide the sound, it's supposed to stop the sound from playing when you lose signal. You can't do anything on the phone to generate the lost service / signal notification, you need to physically lose signal.
Related
This is just a simple build.prop mod to fix the fingerprint back to the working ERE27 one used in CM. Everything in Settings still shows FroYo, but the Market sees you as ERE27 & thus gives you your protected apps back
To install run this from the directory you unzip the file to:
ADB Method:
Code:
adb remount
adb shell rm /system/build.prop
adb push froyo.prop /system/build.prop
adb shell reboot
Then, once it reboots, go into the dialer, and type
Code:
*#*#CHECKIN#*#*
which is
Code:
*#*#2432546#*#*
for those of you who are too lazy to read the letters
A message should pop up into the status bar after a few seconds depending on your connection speed saying checkin succeeded.
Now you're good to go, open Market and download away
EDIT: Since I know some of you will wonder what this does, it just changes the ro.build.fingerprint & ro.build.description settings back to ERE27. This alone would normally be enough, but you're depending on luck to when you next check in. Dialing that code in the Dialer will force a checkin.
EDIT 2: Thanks to Shafty023 here is a method for the shell:
LINUX SHELL METHOD
Copy froyo.zip to /sdcard, then open a Terminal shell on your phone
Code:
su
mount -o remount,rw /system
cd /system
mv build.prop new.build.prop
unzip /sdcard/froyo.zip
mv froyo.prop build.prop
rm /sdcard/froyo.zip
reboot
Upon booting back up, open Dialer and type in the following code
Code:
*#*#2432546#*#*
Once you see a notification in the notification bar that says checkin succeeded you can now open Market and are done.
Nice! Trying it now.
EDIT: Working great so far. Thanks!
athereal said:
Nice! Trying it now.
EDIT: Working great so far. Thanks!
Click to expand...
Click to collapse
testing it in a few minutes too.... [UPDATE: works like a charm!]
Nice job Geniusdog254! really nice
thanks!
Thanks, works great!
Grrr... adb has been broken for me for months. Any way to fix this without adb?
Part Four said:
Grrr... adb has been broken for me for months. Any way to fix this without adb?
Click to expand...
Click to collapse
Use one of the root file explorers to unzip the file, delete the old build.prop, put the new one in, and then type the command in the dialer
Works like a charm, thanks!
Worked great, THANK YOU!!!!!
I'm getting checkin failed. should I have renamed froyo.prop to build.prop?
edit: I'm able to see protected apps though.
So what happens when apps start getting udated to take advantage of JIT? If you have ERE27 signature do you get the JIT'less version of the apps? I know Replica Island is coming with a JIT version. I'm afraid to mess with anything right now, rather be patient and give it a few days.
dudebro said:
I'm getting checkin failed. should I have renamed froyo.prop to build.prop?
edit: I'm able to see protected apps though.
Click to expand...
Click to collapse
If you inserted this line correctly, it renames and places the file in its directory as build.prop
adb push froyo.prop /system/build.prop
Mikey1022 said:
If you inserted this line correctly, it renames and places the file in its directory as build.prop
adb push froyo.prop /system/build.prop
Click to expand...
Click to collapse
yeah, I was wondering if it worked because I was getting checkin failed.
bluehaze said:
So what happens when apps start getting udated to take advantage of JIT? If you have ERE27 signature do you get the JIT'less version of the apps? I know Replica Island is coming with a JIT version. I'm afraid to mess with anything right now, rather be patient and give it a few days.
Click to expand...
Click to collapse
Apps don't have to be updated to take advantage of JIT at all. They can be optimized but they can be optimized without JIT too. There are no different versions. JIT just converts the Java/Dalvik code into native code at app launch, instead of running it through the slower virtual machine. Its like C++ vs Java on a desktop, the native code (C++) is much faster when executed.
The only thing this will lead to is when apps start showing up in the Market as 2.2+ only, but by that point Google will have updated the market to recognize the new footprint.
Can someone give an example of a "Protected" app? If its worth anything, im assuming its paid apps. If so, i can see them without a modded build.prop.
serialtoon said:
Can someone give an example of a "Protected" app? If its worth anything, im assuming its paid apps. If so, i can see them without a modded build.prop.
Click to expand...
Click to collapse
I think Twidroid Pro is protected.
What I'm wondering is, if somebody swaps out the build prop but hasn't installed flash yet, would this block them from doing so?
serialtoon said:
Can someone give an example of a "Protected" app? If its worth anything, im assuming its paid apps. If so, i can see them without a modded build.prop.
Click to expand...
Click to collapse
Pure calender widget (agenda) is a protected app taht doesnt show up in the 2.2 market
Edit: Works perfect! Thanks.
If you are having problems with the checkin, make sure your on 3g and not WiFi.
Mi|enko said:
I think Twidroid Pro is protected.
What I'm wondering is, if somebody swaps out the build prop but hasn't installed flash yet, would this block them from doing so?
Click to expand...
Click to collapse
Nope, Flash still shows up in the Market top apps for me, but I already have it installed. Technically it probably should show up only on the 2.2 Market, but Google may not be able to filter that yet since they haven't enabled the 2.2 fingerprint yet. Just theories here, don't take anything I say too seriously
Also, a perfect example of protected apps is all the Gameloft apps. Search the Market for Gameloft. They won't show up on 2.2 without this, I tried multiple times
Geniusdog254 said:
Nope, Flash still shows up in the Market top apps for me, but I already have it installed. Technically it probably should show up only on the 2.2 Market, but Google may not be able to filter that yet since they haven't enabled the 2.2 fingerprint yet. Just theories here, don't take anything I say too seriously
Also, a perfect example of protected apps is all the Gameloft apps. Search the Market for Gameloft. They won't show up on 2.2 without this, I tried multiple times
Click to expand...
Click to collapse
Yea, im not getting any of the GameLoft games.
serialtoon said:
Yea, im not getting any of the GameLoft games.
Click to expand...
Click to collapse
Even after this?
Do not use the lagfix anymore voodoo will be incorporated into our new kernels very soon. Thanks
Kept the attachments so you can remove if needed!
I keep getting permission errors when I try this. I found another way to update busybox but the script doesn't work
With the current limited root I have, I could not write to /system/bin. I just woke up and I didn't feel like figuring that out, so I copied stuff to the sdcard, then I used cat to write the file to /system/bin as shown above (steps below). I would suggest before starting, download Quadrant Standard from the Market, run the full benchmark and see where your device is on the list. Mine was below the Galaxy S before starting.
This is what I did (on Mac) to get busybox in place:
Code:
./adb shell
su
mkdir /sdcard/lag_fix/
exit
exit
./adb push ~/Downloads/busybox /sdcard/lag_fix/
./adb shell
su
cat /sdcard/lag_fix/busybox > /system/bin/busybox
cd /system/bin/
chmod 755 busybox
ls -l (check the permissions)
exit
exit
Now busybox is in it's right place with the right permissions.
Now, I have to manually execute the steps in the lagfixme.bat file, because I'm not on a PC and I don't feel like re-writing the script, because I just woke up.
Before pushing the files, I edited lines 35 and 36 in the createlagfix.txt file to fit my sdcard folder path. I like to keep my SD card organized, so I put all the files from the zip into the /sdcard/lag_fix folder I created above. Here is what my line 35 and 36 look like before I push createlagfix.txt to the SD card:
busybox cp /sdcard/lag_fix/playlogos1 /system/bin/playlogos1
busybox cp /sdcard/lag_fix/userinit.sh /system/bin/userinit.sh
Now, I know the folder paths below looks ugly, but that's because I just pushed the files directly from my Downloads folder. Hopefully you guys can see what I did here. If not, let me know and I'll edit the post to read better. These are basically the lines in the batch file written out manually for Mac users:
Code:
./adb kill-server
./adb push ~/Downloads/RyanZAEXT2LagFix\ ALPHA\ 1/createlagfix.txt /sdcard/lag_fix/createlagfix.sh
./adb push ~/Downloads/RyanZAEXT2LagFix\ ALPHA\ 1/playlogos1 /sdcard/playlogos1
./adb push ~/Downloads/RyanZAEXT2LagFix\ ALPHA\ 1/userinit.sh /sdcard/userinit.sh
./adb shell su -c "/system/bin/sh /sdcard/lag_fix/createlagfix.sh"
Once the process is complete, run Quadrant Standard again and you'll see your device as the fastest one in the list.
Many thanks to Dirrk!!
Worked just fine for me.
Thanks for this and your root instructions!
Guys, is the phone actually laggy, or are you just assuming it's laggy because of complaints with the other models? I mean, you've only had them a day or two, right? Took me longer to notice lag than that on my i9000.
I'm tempted to grab a Fascinate, but all the issues I've had with the i9000 and it's a tough call.
I've seen it lag sometimes under high load, but I thought that was normal.
I've tested it with GroceryIQ, to compare against the last 30 seconds or so of this video ( http://www.youtube.com/watch?v=10ox35vMS78 ) and the Fascinate is nowhere near as bad at lagging. That video was 8/21/2010, so they may have updated their application by now, not sure.
Edit - Anyway, it works just fine. Nice work Dirrk! 2,191 !
Yep, worked like a charm! My Quadrant score jumped to 2125 after the fix. Phone is much snappier too. Thanks Dirrk!
i've been trying this but i keep getting permission denied.
can someone take me step by step on how to do this?
So, after running this, I am now getting a notification that internal storage is nearly full. Any ideas?
spotmark said:
So, after running this, I am now getting a notification that internal storage is nearly full. Any ideas?
Click to expand...
Click to collapse
If you have root, you can now remove many of the bloatware apps that you do not use (this fix uses 1gb of your internal storage - performance is expensive)
m2cool2go said:
If you have root, you can now remove many of the bloatware apps that you do not use (this fix uses 1gb of your internal storage - performance is expensive)
Click to expand...
Click to collapse
Whoa, careful there. That's a quick way to brick your phone. Try removing Verizon Backup Assistant and you're bricked.
C:\sdk\tools>adb shell
$ su
su
# cat /sdcard/busybox > /system/xbin/busybox
cat /sdcard/busybox > /system/xbin/busybox
cannot create /system/xbin/busybox: read-only file system
Any ideas why I'm getting this error? It looks like I'm screwing up something very simple...
namebrandon said:
Whoa, careful there. That's a quick way to brick your phone. Try removing Verizon Backup Assistant and you're bricked.
Click to expand...
Click to collapse
Really? I removed Backup Assistant and I'm not bricked. Am I missing something?
Removing VZW backup assistant will absolutely not brick your phone. Its one of the first things to go on all my android phones since the eris.
undo lagfix
Hello. I want to undo this for now, due to running out of space for apps. I assumed running unlagfixme would do the trick, but it hasn't given me back the 1 gb it used. Am I doing it wrong, or is it stuck like this now? Thanks for your help!
is there a list of apps someone can recommend to remove that's just bloat? thanks....and ive ran this quadrant score, im averaging 871 three times testing now with minimal apps (used task killer...) - and ive got 177mb left on my phone hehe...
Nevermind, figured it out
xirnibor said:
is there a list of apps someone can recommend to remove that's just bloat? thanks....and ive ran this quadrant score, im averaging 871 three times testing now with minimal apps (used task killer...) - and ive got 177mb left on my phone hehe...
Click to expand...
Click to collapse
You screwed up if your only getting 871 thats stock. Open up a shell on your phone and type mount and place the results in here
Whitepaint said:
Removing VZW backup assistant will absolutely not brick your phone. Its one of the first things to go on all my android phones since the eris.
Click to expand...
Click to collapse
Thanks for the info, and my bad on the post!
I heard that removing this on the Droid X was bricking phones.
If people want to share what they've been successful in removing/renaming, that would be helpful.
namebrandon said:
Thanks for the info, and my bad on the post!
I heard that removing this on the Droid X was bricking phones.
If people want to share what they've been successful in removing/renaming, that would be helpful.
Click to expand...
Click to collapse
I am waiting on rom manager so I can make a back up before I continue removing stuff
I'm posting this here for visibility for Fascinate users and ROM developers. In the following thread you can find all the information, as well as how to download and apply the patch files:
http://forum.xda-developers.com/showthread.php?t=977154
I'm sure it will be incorporated into the major ROM's soon. However, if you install apps from unverified sources, or regularly try out new apps from the market, you shouldn't wait.
Patching via CWM:
imnuts said:
Here are two zips if people want them and don't feel like going to another thread/page/topic/whatever.
DroidDreamMalwarePatch_pre-edify.zip
DroidDreamMalwarePatch_edify.zip
Click to expand...
Click to collapse
Patching via ADB or terminal emulator:
Alternatively, probably the quickest way (and if you copy and paste, the most fool-proof) if you are rooted and know how to use ADB, is to open up a command prompt or a terminal emulator on the phone to access the adb shell. If on a PC, type:
Code:
adb shell su
Then type the following lines, omitting the $ and # (if you are on a terminal emulator, start here):
Code:
$ su
# mount -o rw,remount /dev/block/stl9 /system
# touch /system/bin/profile
# chmod 444 /system/bin/profile
You are now protected from the current iteration of DroidDream Malware. Consider installing a security program like LookOut to protect against future vulnerabilities.
Original Post:
Rodderik said:
[Patch][Rom]Malware Exploit for all pre-Gingerbread phones
Who is affected? All phones pre-gingerbread
Who should act? Users and developers using pre-gingerbread roms
How do I fix? Flash attached .zip at the bottom of this post or use one of the alternate methods down there
What if I think I was infected? Completely wipe your device, format sdard, go back to stock and re-apply rom, then flash the attached .zip (before installing any apps)
Why should I care? read below...
http://www.androidpolice.com/2011/0...your-phone-steal-your-data-and-open-backdoor/
Link to publishers apps here. I just randomly stumbled into one of the apps, recognized it and noticed that the publisher wasn’t who it was supposed to be.
Super Guitar Solo for example is originally Guitar Solo Lite. I downloaded two of the apps and extracted the APK’s, they both contain what seems to be the "rageagainstthecage" root exploit – binary contains string "CVE-2010-EASY Android local root exploit (C) 2010 by 743C". Don’t know what the apps actually do, but can’t be good.
I appreciate being able to publish an update to an app and the update going live instantly, but this is a bit scary. Some sort of moderation, or at least quicker reaction to malware complaints would be nice.
EDIT: After some dexing and jaxing, the apps seem to be at least posting the IMEI and IMSI codes to http://184.105.245.17:8080/GMServer/GMServlet, which seems to be located in Fremont, CA.
I asked our resident hacker to take a look at the code himself, and he’s verified it does indeed root the user’s device via rageagainstthecage or exploid. But that’s just the tip of the iceberg: it does more than just yank IMEI and IMSI. There’s another APK hidden inside the code, and it steals nearly everything it can: product ID, model, partner (provider?), language, country, and userID. But that’s all child’s play; the true pièce de résistance is that it has the ability to download more code. In other words, there’s no way to know what the app does after it’s installed, and the possibilities are nearly endless.
Click to expand...
Click to collapse
The offending apps from publisher Myournet:
* Falling Down
* Super Guitar Solo
* Super History Eraser
* Photo Editor
* Super Ringtone Maker
* Super Sex Positions
* Hot Sexy Videos
* Chess
* ????_Falldown
* Hilton Sex Sound
* Screaming Sexy Japanese Girls
* Falling Ball Dodge
* Scientific Calculator
* Dice Roller
* ????
* Advanced Currency Converter
* App Uninstaller
* ????_PewPew
* Funny Paint
* Spider Man
* ???
Click to expand...
Click to collapse
http://www.androidpolice.com/2011/0...-android-nightmare-and-weve-got-more-details/
Now, on to some more details of the virus. We should point out that this vulnerability was patched with Gingerbread, meaning any device running Android 2.3+ should be fine. In other words, if you’re looking to play the blame game (which I’m not, but having read all the comments on the original post, many people are), then there’s plenty to go around. The hole was fixed by Google, but it’s relatively useless since many phones aren’t yet running a version of Android that is protected. It’s noteworthy that some manufacturers released updates that patched the exploit for devices without updating to Gingerbread; unfortunately, it appears that minority is quite a small one.
Perhaps most important is the question of what infected users can do about their situation; unfortunately, the answer is not much of anything. Because the virus opens up a backdoor and can bring in new code at any time, the only way to really rid an infected device of any damage is to completely wipe the device – not exactly the optimal solution, but it looks like the only one available, at least for now.
Finally, Justin notes that ROM developers working with pre-Gingerbread versions of Android can prevent the virus from backdooring in code by putting a dummy file at /system/bin/profile.
Click to expand...
Click to collapse
As you can see androidpolice.com reports on this backdoor and roots and steals personal information. The apps are removed from the market but that doesn't mean they got them all. Attached is a flashable fix as suggested by androidpolice.com
So users can flash this .zip or simply create a blank file called profile and place it in /system/bin/ (developers are encouraged to include this file in future releases. A blank file is not going to affect performance at all)
Alternate methods:
Using 'adb shell' or terminal emulator (should work on any ROOTED phone) as suggest by xaueious here
Code:
$ su
su
# remount rw
Remounting /system (/dev/stl9) in read/write mode
# touch /system/bin/profile
# chmod 644 /system/bin/profile
#
Alternate 2:
Download blank profile file from here (or create one and name it profile)
Use a program like Root Explorer to copy it to /system/bin/
Then longpress on it and check the permissions should be read/write for user, read for group, and read for others.
Alternate 3:
cyansmoker has put together an apk for the patch here https://market.android.com/details?id=com.voilaweb.mobile.droiddreamkiller
Thanks for pointing this out photoframd and androidpolice.com for investigating and reporting!
UPDATE: I renamed the .zip file and reuploaded it (350 hits wow). Also in the edify scripted version I added 644 permissions to the file (but if you already flashed it then it should have defaulted to that). I also added a pre-edify version of the patch thanks to xaueious for people using a recovery that does not yet understand edify.
Click to expand...
Click to collapse
Thanks
Sent from my Rocking dj05, themed superdark w/o swype mod, voodoo 5, with custom boot and shutdown.. With premium xda app.
I would also recommend installing the free Lookout Mobile Security app. I find it to be very non-intrusive on my phone, no negligible battery drain or performance issues. Just scans any app you install, looking for bad stuff. Also does weekly full system scans, contact backup, and provides phone lock/alarm/location tracking features in case you lose it. Premium version has even more bells and whistles.
Posted from my EB01 SuperClean Fascinate with Voodoo
This has been stuck for the time being as it seems to be affected a BOATLOAD of users. Thanks for the linkage!
Here are two zips if people want them and don't feel like going to another thread/page/topic/whatever.
adb shell busybox touch /system/bin/profile
is all you need. Most fascinate kernels (of recent) have a bug, and /system is mounted as r/w.
So everyone should flash this no matter what rom you are using? Should we flash the new cwr also?
sorry delete
jcase said:
adb shell busybox touch /system/bin/profile
is all you need. Most fascinate kernels (of recent) have a bug, and /system is mounted as r/w.
Click to expand...
Click to collapse
adb shell chmod 644 /system/bin/profile
also?
NOsquid said:
adb shell chmod 644 /system/bin/profile
also?
Click to expand...
Click to collapse
This would probably be a good thing. Basically locks the file from being written to, right? Should I add it to the first post?
lasportsfan said:
So everyone should flash this no matter what rom you are using? Should we flash the new cwr also?
Click to expand...
Click to collapse
Yes.
All this is is a quick fix that will create a blank file. The current iteration of the malware checks to see if it already exists. This file fools it into thinking it already exists, so it moves on.
As you might guess, the author needs to only update his code to bypass this, in order for this to be an issue again.
And now that this is out, someone else will probably try it. Someone who is a little more thorough.
Moral of the story?
Be careful.
Consider running something like LookOut.
Backup your important data regularly.
As far as CWM goes, is there some kind of connection to the malware thing? Or just in general?
(If just in general, it's better to ask elsewhere as to not derail the thread).
Otherwise, I don't believe the newest (orange) clockwork recovery from ROM manager is fully compatible yet. Last I heard, it still had some bad binaries and 1 bad mounting point. Stick with the Red from JT's thread (which is the same bundled into SuperClean). Other than a couple superficial bugs that don't hurt anything, it works wonderfully and has more features than the orange CWM currently has.
GizmoDroid said:
This would probably be a good thing. Basically locks the file from being written to, right? Should I add it to the first post?
Click to expand...
Click to collapse
I dunno, it was in Rodderik's post but jcase didn't mention it. He's smarter than me, that's why I asked...
444 or 000 would be safer as that would prevent the file from being overwritten at all. 444 for read-only, 000 for no access.
If I never downloaded any of the apps in the list and have lookout on my phone is this neccesary to download or should i not be worried?
italysfinest327 said:
If I never downloaded any of the apps in the list and have lookout on my phone is this neccesary to download or should i not be worried?
Click to expand...
Click to collapse
Who should act? Users and developers using pre-gingerbread roms
Click to expand...
Click to collapse
I'd say that means you should be worried. Those apps listed are just the ones that were found on the market with them from one publisher. Just how virus's can get put into any application on a PC, the same can be done on phones.
Remember folks, our phones are just as exploitable as any other computer, so be careful!
good thing the patch came out!
imnuts said:
444 or 000 would be safer as that would prevent the file from being overwritten at all. 444 for read-only, 000 for no access.
Click to expand...
Click to collapse
Not sure whether Android interprets permissions differently from desktop Linux, but even if a file is 000 the owner can delete it on Debian. And root definitely can. If the file needs to be there for the root exploit to work, then this prevents it, but if they can run the root exploit and get root while this file is there then changing permissions on it will do nothing.
iofthestorm said:
Not sure whether Android interprets permissions differently from desktop Linux, but even if a file is 000 the owner can delete it on Debian. And root definitely can. If the file needs to be there for the root exploit to work, then this prevents it, but if they can run the root exploit and get root while this file is there then changing permissions on it will do nothing.
Click to expand...
Click to collapse
This is just another reason why I see this as a quick fix for what will need to have a much better one in the future.
If anyone hears of a more robust solution (besides using LookOut), let us know!
I navigated through Root Explorer to system/bin/profile and found a file there that reports
"01 Aug 08 06:00:00 rwxr-xr-x 0 bytes".
The 2008 date has me worried, although the 0 bytes means it is empty. Does anybody know if this is put there by FrankenClean 2.8 as a fix for this issue, or am I the only one on SuperClean seeing this (which would be bad!)
SupraLance said:
I navigated through Root Explorer to system/bin/profile and found a file there that reports
"01 Aug 08 06:00:00 rwxr-xr-x 0 bytes".
The 2008 date has me worried, although the 0 bytes means it is empty. Does anybody know if this is put there by FrankenClean 2.8 as a fix for this issue, or am I the only one on SuperClean seeing this (which would be bad!)
Click to expand...
Click to collapse
It is included in SC2.8. The 0 bytes is the best indicator that you are clean, since this patch is merely an empty file.
If you were infected, that file would actually have code in it.
For CWM 2.5.x.x DJ05, which one do you flash? or both?
DroidDreamMalwarePatch_pre-edify.zip
DroidDreamMalwarePatch_edify.zip
Thanks and sorry for the trouble, just wanted to be sure.
21.03.2014 RELEASE #4 UPDATE
Here is first ever CM for LG D605 (Optimus L9 II).
This is unofficial ROM and might have some serious faults, if this breaks your phone or they fire you from your job because alarm didn't start it will be your own fault since you have installed it. You have been warned!
The installation procedure was tested with unbranded phone (OPEN_EU variant). This might not work with branded ROM (but it would be good if someone check it).
Sources can be found at:
https://github.com/Varcain/android_kernel_lge_d605
https://github.com/Varcain/android_device_lge_d605
Things that don't work and won't be included in this ROM by default (possible enable by porting stock apps):
- FM radio
- IR port
Things that I already know that don't work at all or are bugged:
- NFC (no support at all yet)
- Manual service network selection (only auto supported right now)
- SIM card contact/SMS reading
For best battery life keep bluetooth off if you are not using it. It will keep constant wakelock if left on right now
NEWEST RELEASE #4
- Added USB tethering
- Added Bluetooth tethering
- Working move to sd-card function (but MTP on internal memory is disabled, external SD card is now mandatory)
- Vibration patterns tuning
- Correct WLAN and Bluetooth MAC addresses should be used now
CHANGES FROM RELEASE #3
- Fixed first call with no voice bug
- Fixed incoming call volumes
CHANGES FROM RELEASE #2
- Fixed voice call volume
- Fixed mute microphone option during calls
NEWEST ROM RELEASE #4:
d605_cm10_v4.zip - 164.61 MB
GAPPS:
http://goo.im/gapps/gapps-jb-20121011-signed.zip
Old releases:
release #3:
http://d-h.st/Zr4
How to install:
1. Flash CWM (from here: http://forum.xda-developers.com/showthread.php?p=50407619)
2. Download the ROM and gapps to sdcard
3. Boot to recovery
4. Wipe all userdata
5. Install CyanogenMod first then gapps
6. Reboot.
Now wait for CM to boot... (first boot will take longer as always).
For reporting bugs/problems:
- Send me logcat output (it would be good to have "logcat -b radio" output too if this is related to sim card/radio)
- Send me dmesg output
If you experience reboot (kernel panic most likely) then send me contents of /proc/last_kmsg (you have to copy this right after reboot, you can do it from terminal application if you don't have access to PC with adb at that time).
Reserve for info.
Thanks Varcain!
Beginning installation right now.
----------------------------------------EDIT---------------------------------------------
Help: http://forum.xda-developers.com/showpost.php?p=50007962&postcount=318
WORKS!
great =) i already love it
one small problem: I've got no gapps!
from the adb shell inside /data/local/tmp I executed the cp -r command to install the gapps, which I unzipped to /storage/external_SD/Download
the shell did something, because it wrote: SD/Download/system/* mntpoint/
then I synced and rebooted to recovery which is my astonishing beautiful CM10 now =)
But: no gapps...
wanted to import my contacts from my googlemail
TaZRAge said:
WORKS!
great =) i already love it
one small problem: I've got no gapps!
from the adb shell inside /data/local/tmp I executed the cp -r command to install the gapps, which I unzipped to /storage/external_SD/Download
the shell did something, because it wrote: SD/Download/system/* mntpoint/
then I synced and rebooted to recovery which is my astonishing beautiful CM10 now =)
But: no gapps...
wanted to import my contacts from my googlemail
Click to expand...
Click to collapse
Check /system directory on the phone if files from gapps are really here, if they are try repeating steps (from stock ROM):
How to install:
Unzip contents, boot your phone to stock ROM, connect via USB with USB debugging mode on, install adb (if you don't have it yet), then adb push all unzipped files to /data/local/tmp (for example adb push ./system.tar /data/local/tmp). After that enter adb shell, issue "su" command and:
# cd /data/local/tmp
# chmod 777 clear_partitions.sh
# chmod 777 loki_flash
# chmod 777 system_update.sh
# mkdir mntpoint
# ./clear_partitions.sh
# ./loki_flash recovery rom.lok
# ./system_update.sh
After that locate your unzipped gapps and do the following (I assume gapps are unzipped directly in /storage/external_SD/Download
# cp -r /storage/external_SD/Download/system/* mntpoint/
# sync
# reboot recovery
Click to expand...
Click to collapse
I think this happened to me few times as well and I had to repeat installation process and then gapps were fine. I will investigate this issue because this is really strange. Alternatively you can do this (from running CM rom):
# su
# mount -o remount rw /system
# cp -r /storage/sdcard1/Download/system/ /
# sync
# reboot
I found that when doing installation steps without installing gapps at first and then installing them on a running system never fails (but I think this is technically worse solution to do so I still have to check this out).
Also there is some wakelock problem I have just noticed so the phone won't go into deep sleep as it should. Until I fix that beware of some battery drainage.
Varcain said:
Check /system directory on the phone if files from gapps are really here, if they are try repeating steps (from stock ROM):
I think this happened to me few times as well and I had to repeat installation process and then gapps were fine. I will investigate this issue because this is really strange. Alternatively you can do this (from running CM rom):
# su
# mount -o remount rw /system
# cp -r /storage/external_SD/Download/system/ /
# sync
# reboot
I found that when doing installation steps without installing gapps at first and then installing them on a running system never fails (but I think this is technically worse solution to do so I still have to check this out).
Also there is some wakelock problem I have just noticed so the phone won't go into deep sleep as it should. Until I fix that beware of some battery drainage.
Click to expand...
Click to collapse
Okay.
Will try that.
Also: I cannot connect via USB debug, my computer always sais: no driver found.
The original LG driver seems not to work with the Custom ROM.
The workaround to install the gapps from external SD, from shell in CM10, doesn't work either, directory not found. seems it does not mount the SD card correctly.
booting to stock ROM now and working hard
TaZRAge said:
Okay.
Will try that.
Also: I cannot connect via USB debug, my computer always sais: no driver found.
The original LG driver seems not to work with the Custom ROM.
The workaround to install the gapps from external SD, from shell in CM10, doesn't work either, directory not found. seems it does not mount the SD card correctly.
booting to stock ROM now and working hard
Click to expand...
Click to collapse
I made a typo, try /storage/sdcard1 instead of /storage/external_SD.
Well... It did something...
i can manualy get to the .apk files of the gapps. at least it mounted the sdcard1 correctly.
But when i do:
# cp -r /storage/sdcard1/Download/system/ /
the shell gets "occupied" for a minute or two and when i get # again i do sync and reboot recovery
After the reboot i still can't find the gapps...
And since i cannot get on CM10 via ADB Shell on my computer i cannot push the files where i need them...
gona reinstall everything i think
TaZRAge said:
Well... It did something...
i can manualy get to the .apk files of the gapps. at least it mounted the sdcard1 correctly.
But when i do:
# cp -r /storage/sdcard1/Download/system/ /
the shell gets "occupied" for a minute or two and when i get # again i do sync and reboot recovery
After the reboot i still can't find the gapps...
And since i cannot get on CM10 via ADB Shell on my computer i cannot push the files where i need them...
gona reinstall everything i think
Click to expand...
Click to collapse
I run on a linux machine so ADB works for me, don't know about windows drivers. I will check it later.
Varcain said:
I run on a linux machine so ADB works for me, don't know about windows drivers. I will check it later.
Click to expand...
Click to collapse
reinstalled everything
maybe I gona set up a dualboot on my PC too =)
made 2 screenshots from my adb shell with wel.... rare behaviour
but now it worked!
i have Gapps
Not rare behavior at all! You forgot Download directory in first screenshot and in second one it looks fine to me.
Varcain said:
Not rare behavior at all! You forgot Download directory in first screenshot and in second it looks fine to me.
Click to expand...
Click to collapse
*headpalm* no wonder it did not work
Well whatever.... that is one fine port =)
I am only missing my apps i installed via the amazon appmarket =D
And since its not really a ROM for daily use i will not install everything i have in my stock ROM
---------- Post added at 07:44 PM ---------- Previous post was at 07:14 PM ----------
Varcain said:
Just use the ROM like you normally would, compare with stock and if you find some anomalies report it in my ROM's thread, I will add them to bug list and hopefully fix in next release.
you can save logs to sd card and then load them from PC connection (I turned off MTP setting by default so it wont be detected as MTP device for file transfers, you need to turn it on in settings>storage>press menu> select MTP).
To do this from console app in phone:
logcat -d > /storage/sdcard1/logcat.txt
logcat -d -b radio > /storage/sdcard1/logcatradio.txt
dmesg > /storage/sdcard1/dmesg.txt
cat /proc/last_kmsg > /storage/sdcard1/lastkmsg.txt
Click to expand...
Click to collapse
This should be in here too!
And by the way, after activating MTP in the ROM i can use adb shell at my computer again!
Regarding camera crashes:
It was very annoying to me too and I found out some things about it (sadly I can't 100% fix it, at least not in CM 10 because a lot of camera stuff is closed source and CM camera app might not be very compatible).
Anyways what I know about the problem:
It happens when you try to make picture with rear camera and the image you are trying to make is dark.
Current solution:
Switch ISO from Auto to Auto (HJR) in camera options (these three little squares). Pictures will be darker in this mode so you will have to use flash. You can switch back from Auto (HJR) to Auto for bright scenery. You can increase exposure by 1 or 2 to balance this. In Auto (HJR) you shouldn't experience any crashes even with dark scenery.
Found something that irritates me:
On stock i had up to 7 homescreens, that could be reduced to a maximum that i need.
On the CM i have 5 and I can't find a option to reduce them.
Taping the homebutton twice does not work, "pinching" the screen neither.
Am i so "stockROMdamaged" that i cannot even find a way to reduce home screens???
TaZRAge said:
Found something that irritates me:
On stock i had up to 7 homescreens, that could be reduced to a maximum that i need.
On the CM i have 5 and I can't find a option to reduce them.
Taping the homebutton twice does not work, "pinching" the screen neither.
Am i so "stockROMdamaged" that i cannot even find a way to reduce home screens???
Click to expand...
Click to collapse
Settings>Launcher>Homescreen>Homescreens
TaZRAge said:
*headpalm*
Click to expand...
Click to collapse
Thanks again
---------- Post added at 10:39 PM ---------- Previous post was at 10:33 PM ----------
Varcain said:
Regarding camera crashes:
It was very annoying to me too and I found out some things about it (sadly I can't 100% fix it, at least not in CM 10 because a lot of camera stuff is closed source and CM camera app might not be very compatible).
Anyways what I know about the problem:
It happens when you try to make picture with rear camera and the image you are trying to make is dark.
Current solution:
Switch ISO from Auto to Auto (HJR) in camera options (these three little squares). Pictures will be darker in this mode so you will have to use flash. You can switch back from Auto (HJR) to Auto for bright scenery. You can increase exposure by 1 or 2 to balance this. In Auto (HJR) you shouldn't experience any crashes even with dark scenery.
Click to expand...
Click to collapse
Works this way!
---------- Post added at 11:01 PM ---------- Previous post was at 10:39 PM ----------
I connected my BT stereoheadset to listen to some music that doesn't sound like coming out a can....
Music via BT is no fun with this right now
I'm sitting next to my phone and the music comes interruptedly and sometimes with crackling sounds.
Gets even worse when i begin to experiment with the equalizer.
Next song comes flawless.... Ah display got disabled.
Screen back working and interruptions are back.
Controlls work perfect as i am used to (volume up + down + start/stop + next song + previous song do what they are supposed to do).
BT Speed to slow?
Disabled GPS now its better again.
Does this happen with stock ROM and/or other headset? I tested bluetooth audio profile and there were no problems for me. Maybe you were in radio-noisy environment.
Varcain said:
Does this happen with stock ROM and/or other headset? I tested bluetooth audio profile and there were no problems for me. Maybe you were in radio-noisy environment.
Click to expand...
Click to collapse
I tested it with stock many times before. Without problems like these.
And its sure I am in a radio-noisy environment. Around here are 4 wifi nets and the one i am in has 3 repeaters.
I had BT disabled on my computer during the test.
I will test it with a cable headset today, I don't have another BT headset.
Yet i had no other problems, bugs or errors!
Just install it!
First impression is VERY GOOD!
I think is faster than stock rom.
Minor problems with installation.
GApps works ok.
Known problem with camera.
Play some games, all run ok and FAST.
I think battery goes faster.
Install some themes, minor problems.
Basic Bluetooth ok.
That's all for now. I will play more later.
Thanks a lot Varcain! :victory:
I will upload new build in a moment and update the OP with it. There is major bug in first alpha release which causes constant wakelock (so the phone never goes into deep sleep). I managed to debug and fix it, please install new version.
This thread has been deleted.
This thread has been deleted.
This thread has been deleted.
***** really really really reserved*****
Working w/ Root on a Mac (OSX Yosemite)
CONFIRMED: This works using AT&T (SM-R750A), OSX (Yosemite), VirtualBox and Windows XP. See this link for the driver setup I used on my Mac.
http://www.onebadkid.com/?p=6930
I also find that after factory reset, I still have root! Great job!
---
Also, I haven't been able to get the scripts to work in the virtual machine so I've just been "pushing" the files manually. I did open up the scripts to get the destinations for the various files, so thank you OP. Also, you have to have the Tizen Wearables SDK installed and then use SDB commands in the terminal.
Remember, when using SDB on a Mac, it's: ./sdb [command] (you have to use the "dot-slash")
./sdb devices (to show whether or not your device is connected)
./sdb root on
./sdb shell (puts you into the device's shell so you can navigate the device in a Darwin/Linux terminal)
./sdb push [/full path of the file you want to upload to the device] [/full path of the desination]
I usually open up three Darwin/Linux Terminals on my Mac. One to use to navigate my watch in shell, the other to run the ./sdb command (just like in Windows, you have to run SDB on the mac from within it's home location: "/Users/[you]/tizen-wearable-sdk/tools"), and a third to drop files into so I can quickly see their full file path/location.
"PWD" = print working directory so you can use that in the Darwin/Linux Terminal so you don't get lost.
I'm using Windows 8.1 (don't know if it matters) but after updating to this driver my PC no longer recognized my Gear S. Had to roll back to previous driver.
Ohhhhh!!!
ohh SO installing these and getting it ready for the rest
Edit: got rootfs.img odin'd in so now i wait lmao
Wondering
Good write up so far. I had already gotten root from the previous thread with horrible direcions. LoL After I got my replacement gear s (ALWAYS CHECK YOUR SIM COVER), I rooted it using the bad direction method again (luckily I already know how to do these things), but your directions are very clear cut and noob friendly. You're doing a huge favor to new comers who come looking to root their gear. Hopefully they don't brick them before they find this.
cipherswitch said:
Got any request for certain alarms, notification sounds or ringtones? Shoot me a PM and I will get through them as fast as I can and repost here.
No themes as of yet, but I will definitely be working on custom clock faces apart from everything else
Click to expand...
Click to collapse
Reset my gear to factory to try out your method.
Odin'd over the root img and all went well after a few reboots (dont' turn off destination, installing new configuration, final reboot).
Watch reboots, open a command prompt and type "sdb root on" (Switched to'root' account mode)
sdb shell whoami
root
sdb shell setup-folder.sh
-1: /bin/setup-folder.sh: Permission Denied
I went and checked your .bat file and it uses the same command. The device says I have root but it's read only file system. I have been trying every trick I know the past half hour; any thoughts?
Megaflop666 said:
Reset my gear to factory to try out your method.
Odin'd over the root img and all went well after a few reboots (dont' turn off destination, installing new configuration, final reboot).
Watch reboots, open a command prompt and type "sdb root on" (Switched to'root' account mode)
sdb shell whoami
root
sdb shell setup-folder.sh
-1: /bin/setup-folder.sh: Permission Denied
I went and checked your .bat file and it uses the same command. The device says I have root but it's read only file system. I have been trying every trick I know the past half hour; any thoughts?
Click to expand...
Click to collapse
Do this
sdb root on
sdb shell
chmod +x /bin/setup-folder.sh
./bin/setup-folder.sh
Megaflop666 said:
Reset my gear to factory to try out your method.
Odin'd over the root img and all went well after a few reboots (dont' turn off destination, installing new configuration, final reboot).
Watch reboots, open a command prompt and type "sdb root on" (Switched to'root' account mode)
sdb shell whoami
root
sdb shell setup-folder.sh
-1: /bin/setup-folder.sh: Permission Denied
I went and checked your .bat file and it uses the same command. The device says I have root but it's read only file system. I have been trying every trick I know the past half hour; any thoughts?
Click to expand...
Click to collapse
Color me embarrassed. It seems in the final uploads, I nabbed the rootfs file that wasn't done yet. Uploading the new file now,sorry for the delay.
I reset, flashed the wrong one to confirm the issue then flashed the correct rootfs and confirmed it working. That was the issue, Im waiting for the new one to upload to mediafire now.
and yeah, I couldnt type this morning, totally freaking out.
cipherswitch said:
Color me embarrassed. It seems in the final uploads, I nabbed the rootfs file that wasn't done yet. Uploading the new file now,sorry for the delay.
I reset, flashed the wrong one to confirm the issue then flashed the correct rootfs and confirmed it working. That was the issue, Im waiting for the new one to upload to mediafire now.
and yeah, I couldnt type this morning, totally freaking out.
Click to expand...
Click to collapse
Its all good, I decided to tear into some things and bricked the damn thing, so I am sitting here waiting (forever) for the original firmware to download so I can factory restore it. I was not even able to get into recovery, just download mode. LoL
Oh well, if flashing the original firmware doesn't fix it, i'll take it up to Tmo at 10am and get a new one.
new rootfs uploaded as of 12/17/14 8:42 am est, I also updated the link in the writeup.
::::::Just a quick dirty write-up of how to load sounds with your newly rooted Samsung Gear S::::::
Since most folks are rooting their Gear S for the ability of adding Ringtones (which can be done via a pay app) and adding Notifications, Wallpapers, Watch Faces, you get it......
Once you have followed the awesome rooting guide contained here and you want to load some stuff:
Path for Ringtones:
/opt/share/settings/Ringtones/
Path for Notifications:
/opt/share/settings/Alerts/
Path for Wallpapers:
/opt/share/settings/Wallpapers/
Path for Alarm Sounds:
/opt/share/settings/Alarms/
I have placed both mp3 and off files and they both work fine. Sometimes when setting your applicable Alert/Notification/Ringtone and the file is a mp3, the sound will not play, no worries, it will when the Alert/Notification/Ringtone is invoked.
To load files (Choose appropriate folder listed above)
sdb root on
sdb shell ls /opt/share/settings/Alerts/ (Shows directory listing for /opt/share/settings/Alerts/ on the Gear 2)
sdb push NAMEOFFILE /opt/share/settings/NOTIFICATION_TYPE_FOLDER (ie /Alerts or /Ringtones)
Megaflop666 said:
Its all good, I decided to tear into some things and bricked the damn thing, so I am sitting here waiting (forever) for the original firmware to download so I can factory restore it. I was not even able to get into recovery, just download mode. LoL
Oh well, if flashing the original firmware doesn't fix it, i'll take it up to Tmo at 10am and get a new one.
Click to expand...
Click to collapse
It is SO hard to brick this device so you will be fine! If you get into the firmware failed to install screen you're still good to go. Like I said, I got to bootloops and thought it was dead but stock fixed everything.
No worries you're fine!
You'll be fine!
You will be fine. I've been able to restore from this screen using stock.
Um actually..... its easier. Connect your gear, drop your content into the right folders (eg; ringtones, alerts and such) and run the update script. done and done.
ipstack said:
::::::Just a quick dirty write-up of how to load sounds with your newly rooted Samsung Gear S::::::
Since most folks are rooting their Gear S for the ability of adding Ringtones (which can be done via a pay app) and adding Notifications, Wallpapers, Watch Faces, you get it......
Once you have followed the awesome rooting guide contained here and you want to load some stuff:
Path for Ringtones:
/opt/share/settings/Ringtones/
Path for Notifications:
/opt/share/settings/Alerts/
Path for Wallpapers:
/opt/share/settings/Wallpapers/
Path for Alarm Sounds:
/opt/share/settings/Alarms/
I have placed both mp3 and off files and they both work fine. Sometimes when setting your applicable Alert/Notification/Ringtone and the file is a mp3, the sound will not play, no worries, it will when the Alert/Notification/Ringtone is invoked.
To load files (Choose appropriate folder listed above)
sdb root on
sdb shell ls /opt/share/settings/Alerts/ (Shows directory listing for /opt/share/settings/Alerts/ on the Gear 2)
sdb push NAMEOFFILE /opt/share/settings/NOTIFICATION_TYPE_FOLDER (ie /Alerts or /Ringtones)
Click to expand...
Click to collapse
sbrownla said:
It is SO hard to brick this device so you will be fine! If you get into the firmware failed to install screen you're still good to go. Like I said, I got to bootloops and thought it was dead but stock fixed everything.
No worries you're fine!
Click to expand...
Click to collapse
I wasn't worried to begin with. It's dead, stock firmware flash didn't even fix it. New one will be here tomorrow afternoon. It'll be my third one since I first bought it done my kids drowned the first one. Lmao
Megaflop666 said:
I wasn't worried to begin with. It's dead, stock firmware flash didn't even fix it. New one will be here tomorrow afternoon. It'll be my third one since I first bought it done my kids drowned the first one. Lmao
Click to expand...
Click to collapse
Hm ... what was it doing when you tried to flash?!
I was working on changing some permissions, rebooted it and it never came back, don't even have recovery. From what tmo said, this has happened to other people on this watch