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
Related
Hi folks,
I have installed the Steel web browser and like it much more that the one supplied by HTC with the phone... is it possible to uninstall it and just leave Steel?
The above is just an example, my HTC hero has lots of stuff I don't really plan to use, ever. Is there a way to get rid of them FOR GOOD?
Thanks in advance!
frandavid100 said:
Hi folks,
I have installed the Steel web browser and like it much more that the one supplied by HTC with the phone... is it possible to uninstall it and just leave Steel?
The above is just an example, my HTC hero has lots of stuff I don't really plan to use, ever. Is there a way to get rid of them FOR GOOD?
Thanks in advance!
Click to expand...
Click to collapse
I'm so with you on this one...I've added Twidroid and turned off Peep but would love to completely delete it in order to avoid any conflicts. Also the default messaging program is a bit of a dog when compared to Handcent SMS.
There used to be a way on the WinMo 6 phones to change the registry values to allow deletion of TouchFlo UI programs but I've not been able to find anything online yet. Maybe it's too early in the phone's life for anyone to have cracked this.
At the moment, the only thing I can do is to make sure that notifications from default programs that I have replaced with better ones are turned off so that they only come from the new software.
I realise this doesn't help you (or me) very much but I'd pay good money to have an add/remove program that works on the default apps (ASTRO, Appmanager and OI File Manager do not seem to be able to access the default programs for uninstallation).
Does anyone with modding experience (obviously I don't ;D) have any suggestions on how to achieve this?
DBR
i have installed QuickUninstall app and it offers all the built in apps as well as the added ones....didn't try to delete any though, they don't bother me that much to toy with it just yet
Kewl...thnx for the heads up. QuickUninstall is downloaded. I'll try to get rid of Peep and the inbuilt message program and if something goes wrong I'll be back here begging for more help
DBR
I've had some success with Root Explorer - I've successfully removed the stocks app and the stocks widget.
Big pointer before you start on removing default or stock Rom apps is to MAKE A NANDROID BACKUP!! You can do this by booting the temporary Recovery image from the rooting thread here
http://forum.xda-developers.com/showthread.php?t=543571
That way, if you do mess up, you can restore the Nandroid Backup.
Just ask Auntie Dayzee (BTW I wish I was this sensible with other stuff in my life!! LOL)
I need to partition my hard drive and install Windows in order to use Nandroid and root the phone (you need to root it in order to use root explorer right?).
As soon as I find a way for the installer to find my hard drive I'll poke you for advice, thanks dayzee
Does anyone know what's the name of the web'n'walk app? Can't find it in the app folder.
It's not an app afaik, it's just a shortcut.
all it does is open the default browser to the t-mob web and walk homepage.
Oh.. do you also happen to know where I can remove it?
Nevermind, found it in the app folder as "urlshortcut.apk"
frandavid100 said:
I need to partition my hard drive and install Windows in order to use Nandroid and root the phone
Click to expand...
Click to collapse
As far as i understand, ADB works in Mac and Linux as well, you just need to prefix the commands with ./
or have i missed something?? there's no point installing windows if you don;t have to....
how did you do it?
Dayzee said:
I've had some success with Root Explorer - I've successfully removed the stocks app and the stocks widget.
Big pointer before you start on removing default or stock Rom apps is to MAKE A NANDROID BACKUP!! You can do this by booting the temporary Recovery image from the rooting thread here
http://forum.xda-developers.com/showthread.php?t=543571
That way, if you do mess up, you can restore the Nandroid Backup.
Just ask Auntie Dayzee (BTW I wish I was this sensible with other stuff in my life!! LOL)
Click to expand...
Click to collapse
Hi Dayzee,
noob here. i just rooted my htc hero and i have root explorer running.
can you explain how you removed those apps?
I want to ditch peep, footprints and possibly pc synchronization (if this is safe).
I am a little lost in this file directory structure...
...or could you point me to a really great link on this topic?
thanks so much,
sprinkles
had success using Paul's method on Modaco...all credit to him in my case.
http://android.modaco.com/content/htc-hero-hero-modaco-com/291521/if-you-want-to-remove-htc-sync/
Used a file explorer (astro in my case) to view the folder /system/app so that i could see what needed to be removed, but am now happily without Peep, Learn More, Stocks,HTC Sync, Mail etc.
adb remount
adb shell rm /system/app/xxxxxx
replace xxxxxx with the app you want to remove
HTC Sync - PCSCII*
HTC Stocks and Widget - *Stock*
Peep - *Twit*
Learn More - Learn*
Footprints - *Foot*
Mail - HtcMail*
there's plenty of others in there as well if you have a look. Just be sure to be careful what you delete, and remember that the app names are case sensitive.
The rooted 2.73 rom from Modaco works fine with this command, and i expect the Modaco custom roms will as well.
I used a similar method to get rid of some HTC app which kept bugging me since I upgraded to the new ROM (Peep, Stock, etc), works perfectly and no problem so far.
It's pretty straightforward, even for a newb like me, but if anyone is interested in the steps I followed :
0- Before doing anything that can mess up your phone, it's recommended to do a nandroid backup.
I'll explain how to backup each removed app individually, but we're never cautious enough !
1- Load the recovery image and mount the system:
Code:
fastboot boot cm-hero-recovery.img
adb shell mount /system
2- Get the list of app installed, spot the files you want to delete
Code:
adb shell ls /system/app/
3.a - First alternative : Backup on SDcard and delete
Mount sdcard.
Create a folder saveHtcApp.
Move (copy + delete in one go ! ) files from system/app to saveHtcApp
Code:
adb shell mount /sdcard
adb shell mkdir /sdcard/saveHtcApp
adb mv /system/app/Stock.apk /sdcard/saveHtcApp
adb mv /system/app/Stock.odex /sdcard/saveHtcApp
adb mv /system/app/com.htc.StockWidget.apk /sdcard/saveHtcApp
adb mv /system/app/com.htc.StockWidget.odex /sdcard/saveHtcApp
Then check that all worked right by doing some ls (Yeah, I'm found of double-checking)
Code:
adb shell ls /sdcard/saveHtcApp
adb shell ls /system/app/
3.b - Second Alternative : (don't do it after 3.a !) Backup on Computer and delete.
(on Windows, I assume Linux's folks won't need explanations to do the same on linux.)
Create a folder saveHtcApp : in the following example, in the working directory.
(Of course, you can make it anywhere, but it make the path smaller to work on working directory... and move the save folder afterwards)
Then pull (copy) the files from the phone to the computer.
Just to make sure, a little dir to see that all files were actually copied on the computer.
Code:
mkdir saveHtcApp
adb pull /system/app/Stock.apk ./saveHtcApp
adb pull /system/app/Stock.odex ./saveHtcApp
adb pull /system/app/com.htc.StockWidget.apk ./saveHtcApp
adb pull /system/app/com.htc.StockWidget.odex ./saveHtcApp
dir
Then, delete them :
Code:
adb shell rm /system/app/Stock.odex
adb shell rm /system/app/Stock.apk
adb shell rm /system/app/com.htc.StockWidget.odex
adb shell rm /system/app/com.htc.StockWidget.apk
4 - Reboot the device !
Hope that could help someone.
Tested on Brown French Hero, 2.73.405.5 ROM offi.
Brill stuff - I'm rubbish at the coding stuff - where does this back the apps up to? and what does the dot do? and if its pulling to the PC, does the slash have to go the other way?
Dayzee
Good question, I should have explain that a little
I'll update my previous post.
For the slash-thing... I'm always switching from windows to linux to windows, so I'm always confused between which slash use.
When I have issue with /, I try with \.
BTW, in the present case, I run all those lines on Windows 7 without any issue.
Edit : post step-by-step edited. Is it clearer ?
If anyone see anything to change or explain, just say so.
removing htc hero sucka apps
Tweedeldee said:
Good question, I should have explain that a little
I'll update my previous post.
Click to expand...
Click to collapse
great and thanks. while you were sleeping, i went in and did some removals; just the apk files. what about the .odex files?
I took these apps out at the knees
-peep
-footprints
-tutorial
any other suggestions?
thanks.
Hey, I wasn't sleeping ! Just finding a way to save on sdcard instead of pc and re-redacting the post ! >.<
I didn't knew what was an odex file either, so I googled it :
http://groups.google.com/group/android-framework/browse_thread/thread/70ee61a240edc84a?pli=1
They are created for a final system image. They are not required --
if they don't exist, the system will create them in /data during
boot.
Click to expand...
Click to collapse
I backuped them too, just in case...
For the suggestion, the list to remove is pretty simple : anything you don't use at all.
As long as you keep the backups, there shouldn't be any problem to put them back if there is any issue.
Of course, any app used by other apps must stay on the phone.
I removed :
Stock
Peep
Footprints
Tutorial
HTC Sync
rhedgehog says he removed HtcMail too.
removing htc hero sucka apps
Tweedeldee said:
Hey, I wasn't sleeping ! Just finding a way to save on sdcard instead of pc and re-redacting the post ! >.<
I didn't knew what was an odex file either, so I googled it :
http://groups.google.com/group/android-framework/browse_thread/thread/70ee61a240edc84a?pli=1
I backuped them too, just in case...
For the suggestion, the list to remove is pretty simple : anything you don't use at all.
As long as you keep the backups, there shouldn't be any problem to put them back if there is any issue.
Of course, any app used by other apps must stay on the phone.
I removed :
Stock
Peep
Footprints
Tutorial
HTC Sync
rhedgehog says he removed HtcMail too.
Click to expand...
Click to collapse
thanks dog.
technically, if you wipe the device and start over all these apps are reinstalled from the get go.
this list is great. i am going to do some more cleaning and move onto the next task of partitioning my storage.
dayzee did a wonderful job for that newb root posting...i wish there was locked how to list that was easy enough for anyone to:
-1- root the htc hero (completed)
-2- remove and replace htc's crapware apps (maybe this thread is part 2)
-3- partition storage (not seeing an easy way yet but downloaded apps2sd)
-4- recommended replacement apps and next steps
i'd be glad to help put this together, make it easy to read, make it pretty, etc.
-sprinkles
Not a bad idea, you're on your way !
I want a pretty, clean, post with colors, pics, screencasts, videos, nice fonts...
Good luck with that !
sprinkles said:
thanks dog.
technically, if you wipe the device and start over all these apps are reinstalled from the get go.
this list is great. i am going to do some more cleaning and move onto the next task of partitioning my storage.
dayzee did a wonderful job for that newb root posting...i wish there was locked how to list that was easy enough for anyone to:
-1- root the htc hero (completed)
-2- remove and replace htc's crapware apps (maybe this thread is part 2)
-3- partition storage (not seeing an easy way yet but downloaded apps2sd)
-4- recommended replacement apps and next steps
i'd be glad to help put this together, make it easy to read, make it pretty, etc.
-sprinkles
Click to expand...
Click to collapse
I agree - I've added Tweedeldee's method to the Hero Wiki which is here
http://wiki.xda-developers.com/index.php?pagename=HTC_Hero
and has some other guides - Sprinkles, there is also a Dayzee Walkthrough for installing MoDaCo Roms, including some tips on Aps2SD partitioning methods.
Hugs - Dayzee xxx
All you need to do is extract this and run the "runme.bat"
Code:
echo off
cls
echo *********************************
echo * Please plug the USB into Nook *
echo *********************************
pause
adb kill-server
adb devices
echo *******************
echo * Blocking Update *
echo *******************
adb shell mount -o remount,rw /dev/block/mmcblk0p5 /system
adb push block-1.1.sh /system/media
adb shell sh /system/media/block-1.1.sh
ping -n 5 127.0.0.1 >NUL
echo Success
adb reboot
adb kill-server
echo *****************************
echo * You nook is rebooting *
echo * Disconnect the USB cable! *
echo * Wait until rebooted... *
echo * *
echo * BN 1.1 Update Blocked *
echo * *
echo *****************************
pause
exit
Download
Can you release an "Undo" script as well that undoes what this does?
I was under the impression that the otacert rename was a dud and the build.prop was very questionable???
found this and replied to the discussion on the subject.
IMO, Until the OTA is squashed we are going to have a repetitive debockle of blowing up everyones rooted work and would think addressing this would be of significant value:
-cut-n-paste-
I was wondering what you folks thought of this 'prevent' 1.1 hack??
http://forum.xda-developers.com/showthread.php?t=930477
seems reasonable to me, adding:
127.0.0.1 csqaint.barnesandnoble.com
(looks to be the primary check for updates?)
and
127.0.0.1 bncs.barnesandnoble.com
(just for good measure but might have unwanted consequences?)
to /etc/hosts file
I would personally like to be able to put an end to this 'forced' OTA update behind us and be able to sideload any updates from bn manually at our convienence in the future.
how bout u??????
In reviewing the script it appears to apply the build.prop spoof update?
I thought this was questionalble in overall effectiveness?? and even if it worked would have to be reapplied after every update from bn???
I noticed an interesting reply from ixampl as follows:
What I did when the first scare of an update arose was:
a) Checked in /data/data/com.bn.nook.devicemanager/databases/ for an sql file
b) Pulled the sql file.
c) Dump its contents with sqlite3.
d) In it there's an entry for OTAs... with value "auto"
e) Changed that value to "manual"
f) Pushed the modified database file to the device.
I never got any OTA updates. Still on first OS version.
This is exactly what I'm lookin for, a permenant block unless of course the database update got reversed back to auto?????
is this normal? i go into settings/device info/about your nook color. it still shows 1.0.1? where do i have to go to verify this is blocked?
C:\NC - Auto Config Script 1.0.1>adb push block-1.1.sh /system/media
32 KB/s (506 bytes in 0.015s)
C:\NC - Auto Config Script 1.0.1>adb shell sh /system/media/block-1.1.sh
cp: not found
sed: not found
sed: not found
sed: not found
sed: not found
john10101 said:
is this normal? i go into settings/device info/about your nook color. it still shows 1.0.1? where do i have to go to verify this is blocked?
C:\NC - Auto Config Script 1.0.1>adb push block-1.1.sh /system/media
32 KB/s (506 bytes in 0.015s)
C:\NC - Auto Config Script 1.0.1>adb shell sh /system/media/block-1.1.sh
cp: not found
sed: not found
sed: not found
sed: not found
sed: not found
Click to expand...
Click to collapse
You dont have busybox installed on the NC?
bonzer2u said:
In reviewing the script it appears to apply the build.prop spoof update?
I thought this was questionalble in overall effectiveness?? and even if it worked would have to be reapplied after every update from bn???
I noticed an interesting reply from ixampl as follows:
What I did when the first scare of an update arose was:
a) Checked in /data/data/com.bn.nook.devicemanager/databases/ for an sql file
b) Pulled the sql file.
c) Dump its contents with sqlite3.
d) In it there's an entry for OTAs... with value "auto"
e) Changed that value to "manual"
f) Pushed the modified database file to the device.
I never got any OTA updates. Still on first OS version.
This is exactly what I'm lookin for, a permenant block unless of course the database update got reversed back to auto?????
Click to expand...
Click to collapse
Can you elaborate a little further on what commands you used so I might be able to add it into a script.
i dont think so... what installs busybox?
No offense, but this isn't a worry any more anyway. We already have a CWM flashable update.zip that updates you to 1.1, but does not harm your root or installed aps. Why are people bothering with all this "blocking" nonsense?
From this thread:
http://forum.xda-developers.com/showthread.php?t=874871
Attached is a working sqlite3 binary. Copy it to /system/bin and you will be able to edit sqlite databases on the nook itself.
--------------------------------------------------------------------------------
Attached Files sqlite3.7z (11.9 KB, 56 views)
-----------------------------------------------------------------------------
And I found a sqlite3 sample that will need to be edited like somthing as follows:
In your terminal,
$ adb pull /data/data/com.bn.nook.devicemanager/databases/settings.db settings.db
$ sqlite3 settings.db
sqlite> update secure set value='manual' where name='an entry for OTAs???-Dont know the parameter here'
;
sqlite> .q
$ adb push /data/data/com.bn.nook.devicemanager/databases/settings.db settings.db
$ adb reboot
Hope this helps, I dont know the input name for placeholder.
xboxexpert said:
You dont have busybox installed on the NC?
Click to expand...
Click to collapse
Ok i installed busy box off the market, and ran the script!!! success. when i rebooted it told me that 1.1.0 has been installed. and it now shows 1.1.0 in the about.
i suggest noting busy box in the original post.
Divine_Madcat said:
No offense, but this isn't a worry any more anyway. We already have a CWM flashable update.zip that updates you to 1.1, but does not harm your root or installed aps. Why are people bothering with all this "blocking" nonsense?
Click to expand...
Click to collapse
not everyone wants to upgrade to 1.1, or has cwm installed.
john10101 said:
Ok i installed busy box off the market, and ran the script!!! success. when i rebooted it told me that 1.1.0 has been installed. and it now shows 1.1.0 in the about.
i suggest noting busy box in the original post.
Click to expand...
Click to collapse
It says 1.1 is installed but its really not. (Spoofed it)
john10101 said:
not everyone wants to upgrade to 1.1, or has cwm installed.
Click to expand...
Click to collapse
Uh... why? What is there about 1.1 not to want? And if you are ok with doing all of this to block an update, there is no reason not to have CWM (which is quite stable). Sorry, but this really is all just wasted effort..
Divine_Madcat said:
Uh... why? What is there about 1.1 not to want? And if you are ok with doing all of this to block an update, there is no reason not to have CWM (which is quite stable). Sorry, but this really is all just wasted effort..
Click to expand...
Click to collapse
Took me 2 seconds to throw together...took longer to upload then anything. Its just for people who want it. If you dont want it I dont want you to have it :/
xboxexpert said:
Took me 2 seconds to throw together...took longer to upload then anything. Its just for people who want it. If you dont want it I dont want you to have it :/
Click to expand...
Click to collapse
Don't get me wrong, im not knocking your work, just people's reasoning for wanting it done in the first place. I understand before the update.zip was developed, since it would break root and mess up your apps. But now, there is no reason not to take the update; thus the continued demand for this is puzzling.
If you really want the OTA update to stop, take a look at the updater-script inside the sideload_update.zip file from B&N. The first two lines read:
Code:
assert(getprop("ro.product.device") == "zoom2" ||
getprop("ro.build.product") == "zoom2");
I think those are set in the build.prop file. Change either ro.build.product or ro.product.device to something other than zoom2 (say zoom2a), and the rest of the script won't continue. This is what people are seeing when the file gets downloaded OTA and then disappears without being applied. If for some reason you must avoid it, make that change and you will stop the update cold. Not sure what the side effects of making the change are, but there would be an easy way to revert by undoing the edits, if you need to.
Wasn't this already available from another forum member?
http://forum.xda-developers.com/showthread.php?t=930382
Seems a lot easier to just copy and replace build.prop with a filemanager.
Divine_Madcat said:
Uh... why? What is there about 1.1 not to want? And if you are ok with doing all of this to block an update, there is no reason not to have CWM (which is quite stable). Sorry, but this really is all just wasted effort..
Click to expand...
Click to collapse
Yah go ahead and read thru the cwm thread and try to convince anyone in this forum that it is 100% stable. Not to suggest that anyones efforts are not welcome and appreciated but if you asked the actual devs involved I would bet they would not suggest so as well.
I for one have rooted twice (1.0 and 1.0.1) with autoroot and am 100% stable, never had a crash or the pleasure to have to restore/rebuild, not interested in the stock browser or anything else bn has to offer, quite happy and perhaps lucky with the way its workin now. I also dont appreciate being strong armed an update without a confirmation, hell even microbuddies doesnt have that kinda gawl.
I guess it will take one of the next of many 'future forced' updates from bn that bothches all the work that you have put into your NC and for whatever reason your recovery doesnt work and you are forced to rebuild from scratch before you realize that if you had a permenant block in place, you could have the time for outstanding efforts of the local devs to stabilize an upgrade path before you pulled the trigger?
The database hack appears to be best way to permanently kill OTA, no need for future updated spoof build.prop scripts (before you get hit) and no worries about being updated and possibly blown up while your sleepin and bn pushes an update out before you get the news.
or maybe its just me..........
Exactly! If you are not diligently checking the forum everyday, you wouldn't know BN is pushing out 1.1 update and you wouldn't know there is a pre-nootered 1.1 version available. BN will update you OTA before you know any better and screw up your rooted setup. Hence the need for a permanent update block.
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.
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
I bought device from a friend and all he could tell me is that it's rooted and that OTA updates are disabled. It's 8.9 HDX, current version 14.3.2.4_user_324002120 and has Play Market and custom launcher. What are my steps to install a custom rom?
Aftermath__ said:
I bought device from a friend and all he could tell me is that it's rooted and that OTA updates are disabled. It's 8.9 HDX, current version 14.3.2.4_user_324002120 and has Play Market and custom launcher. What are my steps to install a custom rom?
Click to expand...
Click to collapse
You will need to do some homework. Instructions (at least starting points) are posted throughout this forum. Ditch the play market (especially Google play services and associated framework), custom launcher and any other non-stock mods before diving in. While most are benign others can cause problems and potentially lead to a brick. If you have no experience installing custom roms plan on considerable research as you have much to learn. If experienced be aware that Kindles are unlike most other Android devices: easy to brick and nearly impossible to recover - especially the newer HDX models. If you are eying your trusty fastboot cable or other bag of tricks be aware most will not work on an HDX.
Davey126 said:
You will need to do some homework. Instructions (at least starting points) are posted throughout this forum. Ditch the play market (especially Google play services and associated framework), custom launcher and any other non-stock mods before diving in. While most are benign others can cause problems and potentially lead to a brick. If you have no experience installing custom roms plan on considerable research as you have much to learn. If experienced be aware that Kindles are unlike most other Android devices: easy to brick and nearly impossible to recover - especially the newer HDX models. If you are eying your trusty fastboot cable or other bag of tricks be aware most will not work on an HDX.
Click to expand...
Click to collapse
Thanks, also he said something about changing device name in build.prop Is it important?
Aftermath__ said:
Thanks, also he said something about changing device name in build.prop Is it important?
Click to expand...
Click to collapse
Don't mess with build.prop (get it wrong, create a brick). For experienced users. Keep reading ...
Davey126 said:
Don't mess with build.prop (get it wrong, create a brick). For experienced users. Keep reading ...
Click to expand...
Click to collapse
Yeah, I kinda bricked it already. was following instructions and decided to reboot device, now i have black screen after "kindle fire" logo. Is this it or i have some option?
Aftermath__ said:
Yeah, I kinda bricked it already. was following instructions and decided to reboot device, now i have black screen after "kindle fire" logo. Is this it or i have some option?
Click to expand...
Click to collapse
You're done. Recovery is almost impossible.
Davey126 said:
You're done. Recovery is almost impossible.
Click to expand...
Click to collapse
Not necessarily...
@Aftermath__: Can you gain adb access?
EncryptedCurse said:
Not necessarily...
@Aftermath__: Can you gain adb access?
Click to expand...
Click to collapse
Yes. After the reboot i mentioned device was shown in device manager as "Android" and I installed Kindle driver and now it's visible in "adb devices".
Aftermath__ said:
Yes. After the reboot i mentioned device was shown in device manager as "Android" and I installed Kindle driver and now it's visible in "adb devices".
Click to expand...
Click to collapse
Great! Assuming it's just a permissions issue, just enter adb shell and try running the following commands:
Code:
su
chmod 0644 /system/build.prop
EncryptedCurse said:
Great! Assuming it's just a permissions issue, just enter adb shell and try running the following commands:
Code:
su
chmod 0644 /system/build.prop
Click to expand...
Click to collapse
I've got
Code:
[email protected]:/ $ su
su
1|[email protected]:/ $ chmod 0644 /system/build.prop
chmod 0644 /system/build.prop
Unable to chmod /system/build.prop: Read-only file system
Aftermath__ said:
I've got
Code:
[email protected]:/ $ su
su
1|[email protected]:/ $ chmod 0644 /system/build.prop
chmod 0644 /system/build.prop
Unable to chmod /system/build.prop: Read-only file system
Click to expand...
Click to collapse
Oh, right. I forgot.
Code:
su
mount -o remount,rw /system
chmod 0644 /system/build.prop
mount -o remount,ro /system
Lett me know if that works.
EncryptedCurse said:
Oh, right. I forgot.
Code:
su
mount -o remount,rw /system
chmod 0644 /system/build.prop
mount -o remount,ro /system
Lett me know if that works.
Click to expand...
Click to collapse
Code:
[email protected]:/ $ su
su
1|[email protected]:/ $ mount -o remount,rw /system
mount -o remount,rw /system
mount: Operation not permitted
255|[email protected]:/ $
I guess I lost root access after reboot.
Aftermath__ said:
Code:
[email protected]:/ $ su
su
1|[email protected]:/ $ mount -o remount,rw /system
mount -o remount,rw /system
mount: Operation not permitted
255|[email protected]:/ $
I guess I lost root access after reboot.
Click to expand...
Click to collapse
draxie has an approach to that situation with ghettoroot.
http://forum.xda-developers.com/showpost.php?p=57659692&postcount=2
EncryptedCurse said:
draxie has an approach to that situation with ghettoroot.
http://forum.xda-developers.com/showpost.php?p=57659692&postcount=2
Click to expand...
Click to collapse
It worked. Thank you so much for your help.
Aftermath__ said:
It worked. Thank you so much for your help.
Click to expand...
Click to collapse
Glad you are able to fix the problem. Props to EncryptedCurse for picking up the ball and pointing you in the right direction. Thanks also to draxie for posting a solution. Not many devices live through a soft brick. Well done.
I have issue with both manual upgrading and downgrading my .3.2.4 . After reboot grey logo is showed and it seems like it's frozen. I've waited 10 minutes and turned it off and on and it's back to the state before update. Any advice will be appreciated.
Aftermath__ said:
I have issue with both manual upgrading and downgrading my .3.2.4 . After reboot grey logo is showed and it seems like it's frozen. I've waited 10 minutes and turned it off and on and it's back to the state before update. Any advice will be appreciated.
Click to expand...
Click to collapse
Let's focus on upgrading to 3.2.5 as I believe it is the safer path (for the record, tweaking build.prop for a direct downgrade from 3.2.4 is also fine if you know what you're doing and can recover from a mistake). So you put the 3.2.5 bin obtained from here in the root ("internal storage") directory and then follow the instructions in the same post. When the device reboots to only get the grey Kindle Fire Logo. Is that correct?
Suggestions:
- be sure to reenable OTA updates if previously disabled. Keep wifi off, delete all wifi profiles and stay away from open hotspots
- make sure you have a 'clean' copy of build.prop. The contents are machine specific so I can't point you to a link. If unsure check with the previous owner to see if he modified it. Need to be real careful with this file. If the contents or permissions get messed your device can become non-responsive (a kinder way of saying 'soft brick').
- if still no luck try enabling wifi and disabling airplane mode. Some folks claim this is a necessary step (has not been my experience)
- a somewhat riskier step is performing a factory reset just prior to upgrading. Again, some posters have stated this allowed the update to proceed. However, there is a small risk of harming your device with this technique of the recovery partition is damaged and/or build.prop is messed.
From Amazon: To start the software update:
-Swipe down from the top of the screen to open Quick Settings, and then tap Settings.
-Tap Device, and then tap System Updates.
-Tap Update. Your Kindle Fire will restart during the software update. After the restart, the message "Installing system update" will appear on the screen.
I realize the above seems simplistic; you've probably done everything right. Just covering the basics before moving on.
Davey126 said:
Let's focus on upgrading to 3.2.5 as I believe it is the safer path (for the record, tweaking build.prop for a direct downgrade from 3.2.4 is also fine if you know what you're doing and can recover from a mistake). So you put the 3.2.5 bin obtained from here in the root ("internal storage") directory and then follow the instructions in the same post. When the device reboots to only get the grey Kindle Fire Logo. Is that correct?
Suggestions:
- be sure to reenable OTA updates if previously disabled. Keep wifi off, delete all wifi profiles and stay away from open hotspots
- make sure you have a 'clean' copy of build.prop. The contents are machine specific so I can't point you to a link. If unsure check with the previous owner to see if he modified it. Need to be real careful with this file. If the contents or permissions get messed your device can become non-responsive (a kinder way of saying 'soft brick').
- if still no luck try enabling wifi and disabling airplane mode. Some folks claim this is a necessary step (has not been my experience)
- a somewhat riskier step is performing a factory reset just prior to upgrading. Again, some posters have stated this allowed the update to proceed. However, there is a small risk of harming your device with this technique of the recovery partition is damaged and/or build.prop is messed.
From Amazon: To start the software update:
-Swipe down from the top of the screen to open Quick Settings, and then tap Settings.
-Tap Device, and then tap System Updates.
-Tap Update. Your Kindle Fire will restart during the software update. After the restart, the message "Installing system update" will appear on the screen.
I realize the above seems simplistic; you've probably done everything right. Just covering the basics before moving on.
Click to expand...
Click to collapse
All of the above was done, except factory reset. I started with upgrading to 3.2.5 as I followed the steps in your post. Link in this part
- download 3.2.5 here; print upgrade instructions
Click to expand...
Click to collapse
wasn't about 3.2.5 and I guess I shouldn't follow the instructions in it, but I did. I downloaded bin file from here and started update and after the reboot got stuck with grey logo. I restarted device and tried to downgrade, but got the same result. Wi-Fi is on and all of the networks are protected.
I believe build.prop is untouched and there were 5 backups in internal storage, although I think he messed with some system apps, because, and that is one of the reasons I'm doing this now, there is no working keyboard and I can't access "Keyboard Language" and "Keyboard Settings". Should I try factory reset?
Aftermath__ said:
All of the above was done, except factory reset. I started with upgrading to 3.2.5 as I followed the steps in your post. Link in this part
wasn't about 3.2.5 and I guess I shouldn't follow the instructions in it, but I did. I downloaded bin file from here and started update and after the reboot got stuck with grey logo. I restarted device and tried to downgrade, but got the same result. Wi-Fi is on and all of the networks are protected.
I believe build.prop is untouched and there were 5 backups in internal storage, although I think he messed with some system apps, because, and that is one of the reasons I'm doing this now, there is no working keyboard and I can't access "Keyboard Language" and "Keyboard Settings". Should I try factory reset?
Click to expand...
Click to collapse
Sorry about the mispointed link. I usually test those as occasionally a previous cut gets 'stuck' in the clipboard. Given where you have been and the other symptoms I would consider a factory reset. Be aware this is some risk. Not great but there. In most cases undesirable outcomes are limited to doing nothing to help/hurt the problem or device. On rare occasions you are left with a brick.
When the device comes back try the upgrade process again.
(out for a few hours; will check back later)
Davey126 said:
Sorry about the mispointed link. I usually test those as occasionally a previous cut gets 'stuck' in the clipboard. Given where you have been and the other symptoms I would consider a factory reset. Be aware this is some risk. Not great but there. In most cases undesirable outcomes are limited to doing nothing to help/hurt the problem or device. On rare occasions you are left with a brick.
When the device comes back try the upgrade process again.
(out for a few hours; will check back later)
Click to expand...
Click to collapse
I tried and i can't do factory reset because of the same issue as with the upgrade/downgrade. I guess the reason is that I flashed this recovery and I really shouldn't.