Database Info

[INFO][32B] [PORT/FIX] for [ROM] JACxHEROSkiv2.1- JAC/CC 2.83.x posted in Dream Forum

This is for those who have a Sapphire 32B who had issues running Compcache in the 2.0/1 JACxHEROSki.
The problem is that the Magic convert script included copies a 32A .img file to the boot flash. I removed the lines that do this and things seem to work fine. This must be done after flashing the new image, but before running the script.
Here are the steps to be done immediately after booting to new image, but BEFORE running MAGIC script:
1. Download the modified MAGIC script attached to this message and rename it to remove the .TXT extension (should be just "MAGIC")
2. Use ADB Push to push the modified MAGIC script to /sdcard
3. Use ADB Shell and enter the following:
su
mount -o remount,rw /dev/block/mtdblock3 /system
cp /sdcard/magic /system/bin
cd /
rwsystem
magic
4. Choose MyTouch.
5. Edit user.conf for desired settings.
6. Use reboot command to reboot phone.
I would also like to qualify this by saying this worked for me, and this is my first share of this sort with this forum. So, please use this at your own risk.
Good luck.

Hello,
is there a chance for a 32A version of your latest rom?
regards
endebe

Thanks, ill try later

Yeah man ! Thx for the trick Works fine !

I'm still wondering what s best... compcache with backing swap, or linux swap alone ?
What's your opinion ?

on my 32b the g-sensor doenst work.. ist there a fix?!

psxx said:
on my 32b the g-sensor doenst work.. ist there a fix?!
Click to expand...
Click to collapse
You're right, doesn't work anymore on my 32B too

just run the shell script
su
rwsystem
magic
-then press M for mytouch
wifi and gsensor both work after

Very nice.
I'm just waiting for someone to package the JACxHeroSki 2.1 kernel so I can apply it directly over my MCR 2.2e from Paul @ MoDaCo! Right now, I'm using Cyanogen's 4.1.8 kernel, which isn't bad...but I hear that the JAC one is far superior.

dills84 said:
just run the shell script
su
rwsystem
magic
-then press M for mytouch
wifi and gsensor both work after
Click to expand...
Click to collapse
i already did this... but gsensort wont work after... i tried... no autorote... no apps with gsenor are working

compcache is working naow with this script, but no wifi and gsensor, without this scrips works g sensors and wifi

well this script is relativ simple... the first just remounts the fs to rw and the "2nd" part just replayces 3 libs..
i checked twice... but gsensor doenst work with my phone... i had tha same issue on 1.7r2... later i used the port from setenza01 which had a working g-sensor.
so please if someone know how to fix the G-sensor let me know!

jacko6969 said:
This is for those who have a Sapphire 32B who had issues running Compcache in the 2.0/1 JACxHEROSki.
The problem is that the Magic convert script included copies a 32A .img file to the boot flash. I removed the lines that do this and things seem to work fine. This must be done after flashing the new image, but before running the script.
Here are the steps to be done immediately after booting to new image, but BEFORE running MAGIC script:
1. Download the modified MAGIC script attached to this message and rename it to remove the .TXT extension (should be just "MAGIC")
2. Use ADB Push to push the modified MAGIC script to /sdcard
3. Use ADB Shell and enter the following:
su
mount -o remount,rw /dev/block/mtdblock3 /system
cp /sdcard/magic /system/bin
cd /
rwsystem
magic
4. Choose MyTouch.
5. Edit user.conf for desired settings.
6. Use reboot command to reboot phone.
I would also like to qualify this by saying this worked for me, and this is my first share of this sort with this forum. So, please use this at your own risk.
Good luck.
Click to expand...
Click to collapse
To be honest, you don't have to use this script at all, the script is already in there you just need to run this command.
rwsystem
magic
m
reboot

Hi... By stripping the sapphire.img from the script, you're only solving part of the problem (the compcache part).
Actually sapphire.img is important for you to be able to turn on g-sensors.
Here's the solution I posted on the T-Mobile Android forums. ( http://forums.t-mobile.com/tmbl/board/message?board.id=AndroidDev&thread.id=13826 )
It replaces the some of the files with the ones found in ZeroXd's Hero.
-----
Download the following file, that I put together: http://www.megaupload.com/?d=Q759VAG2
This file fixes the compcache problem found in JACxHeroSki v.2.0 and v.2.1. I don't know if this will work for any later versions of the ROM because they didn't exist when I tried it all.
I take no credit for any of this. I just put everything together and zipped it up. All the included files and the knowledge it took to put all this together came from the wonderful people at the Dream forums on xda-developers.com. --eatabagel
Thanks especially to the following awesome devs:
For the ROMs -
JustAnotherCrowd
CCyrowski
For the 32B files (from ZeroXd 5.2r4) -
Twistedumbrella
For the instructions -
Setenza01
============
Instructions
============
Run all of this after flashing JACxHeroSki 2.0 or 2.1, but before running the "magic" command. I assume that your install went well (that means you did everything you needed to do: wipe, clean out ext2/3, etc.). At the stage you run the following commands, you should have a working install of JACxHeroSki 2.0 or 2.1 that hasn't yet been 'fixed' for 32B. That means no WiFi yet.
1. Copy file onto /sdcard
2. Either from a terminal emulator (i.e., Better Terminal Emulator) or from adb shell, type the following:
cd /sdcard
unzip sapphire32bfix.zip
su
rwsystem
cp /sdcard/sapphire32bfix/sapphire/* /system/bin/sapphire
cp /sdcard/sapphire32bfix/sensors.sapphire.so /system/lib/hw
cd /
magic
3. Type 'm' for magic
4. Reboot. Compcache and Wifi should all run perfectly now. No more home screen loads!!!!

I was going to suggest the same solution but you beat me to it.
I dont know if I like the comp cache with vm... it seems slower...
I really like the ZeroXd 5.2rX it seems to be the most responsive...

zambezy said:
I was going to suggest the same solution but you beat me to it.
I dont know if I like the comp cache with vm... it seems slower...
I really like the ZeroXd 5.2rX it seems to be the most responsive...
Click to expand...
Click to collapse
Yea, I agree, having Compcache is definately slower, I don't know about the VM part though.
They did a comparison btwn Linux-Swap and Compcache and Linux-Swap is the winner for speed and I think so too. As for VM I don't think it does anything, I might turn it off to see what happens.

Sweetness! Did the fix and it worked. I finally have landscape and wifi works! Haven't tested bluetooth yet. But other than the messed up screen wake my phone runs flawlessly. I'd have to say that JACxHeroSki 2.1 is the best Hero rom out right now.

solved! thank your for there these files

eatabagel said:
Hi... By stripping the sapphire.img from the script, you're only solving part of the problem (the compcache part).
Actually sapphire.img is important for you to be able to turn on g-sensors.
Here's the solution I posted on the T-Mobile Android forums. ( http://forums.t-mobile.com/tmbl/board/message?board.id=AndroidDev&thread.id=13826 )
It replaces the some of the files with the ones found in ZeroXd's Hero.
-----
Download the following file, that I put together: http://www.megaupload.com/?d=Q759VAG2
This file fixes the compcache problem found in JACxHeroSki v.2.0 and v.2.1. I don't know if this will work for any later versions of the ROM because they didn't exist when I tried it all.
I take no credit for any of this. I just put everything together and zipped it up. All the included files and the knowledge it took to put all this together came from the wonderful people at the Dream forums on xda-developers.com. --eatabagel
Thanks especially to the following awesome devs:
For the ROMs -
JustAnotherCrowd
CCyrowski
For the 32B files (from ZeroXd 5.2r4) -
Twistedumbrella
For the instructions -
Setenza01
============
Instructions
============
Run all of this after flashing JACxHeroSki 2.0 or 2.1, but before running the "magic" command. I assume that your install went well (that means you did everything you needed to do: wipe, clean out ext2/3, etc.). At the stage you run the following commands, you should have a working install of JACxHeroSki 2.0 or 2.1 that hasn't yet been 'fixed' for 32B. That means no WiFi yet.
1. Copy file onto /sdcard
2. Either from a terminal emulator (i.e., Better Terminal Emulator) or from adb shell, type the following:
cd /sdcard
unzip sapphire32bfix.zip
su
rwsystem
cp /sdcard/sapphire32bfix/sapphire/* /system/bin/sapphire
cp /sdcard/sapphire32bfix/sensors.sapphire.so /system/lib/hw
cd /
magic
3. Type 'm' for magic
4. Reboot. Compcache and Wifi should all run perfectly now. No more home screen loads!!!!
Click to expand...
Click to collapse
Thanks you, its really works fine

Hi guys, could someone please host the fix file on mediafire or filehosting as i can't download it from megaupload nor rapidshare . Would be really nice
Thx in advance

[SCRIPT] Android-Linux Tools v0.2 for Linux [[Suggestions Needed]]

Okay. If this is not where the MODs want this post, please move it.
[UPDATE] - Jump over to Post #12 for some of my recent ideas and changes for this application.
I have been using mods for the G1 and the myTouch 3G for a little while now. I have used Backup for Root, and I use Nandroid. I created just a little simple script to backup your device to your linux-based machine and restore from there too. The concept behind this is having your backup on your computer, not your sd-card. Please, feel free to contribute. (If this is not your cup of tea, please do not leave a comment). I am limited on time, and wanted to contribute a little to the community. All this script is a compilation of adb commands. Anyone could compile these commands, I just wanted it organized and in one place.
README
After using all of the backup tools for root, I have ran into random FCs and bugs. This script uses Android SDK's adb tool and was designed to be simple. This script goes through and backs up your applications, bookmarks, sms, alarm clocks, settings, launcher settings and dictionary. There are plans for this script to be interactive in the future. As for now, it is a very basic script that will backup your device then restore your device.
Notes. As for now this script requires sudo. On every other linux pc tested, sudo was required (maybe because user did not install adb correctly?). This will change in future versions.
= Details =
REQUIREMENTS
1. Android SDK Toolkit 1.5 or higher
2. Bash v4.0.33
3. Root access to your device
4. Root access to your pc
HOWTO
Backing-Up
1. Plug your device in
2. Open command-line (On PC)
3. Run ./abrtool -b
4. Done.
Restoring
1. Reboot from flash of rom (Enter credentials and let phone setup first)
2. Open command-line (on PC)
3. Run ./abrtool -r
4. Restart device
5. Done
Changelog
Version 0.1.5
- Merged into Android-Linux-Tools (alt)
- Changed zenity commands (shows restore progress)
- Option to restart device after restore
- Can install abrtool via command-line (./abrtool --install)
Version 0.1.4
- Added Icons
- Runs Fix Permissions after restoration of applications
Version 0.1.3
- Fixed Restore (Again) - Sets $BACKUPDIR as $PATH
Version 0.1.2
- Restore applications now uses adb install instead of push
Version 0.1.1
- Fixed Restore arugement (-r restores now)
Version 0.1
- Created initial script
- Creates backups for Apps, Sms, Bookmarks, Alarms, Settings, User Dictionary, and Launcher
- Restores device
Download
Project Page for Android-Linux-Tools (ALT) http://code.google.com/p/android-linux-tools
Project Page for abrtool http://code.google.com/p/abrtool
Download abrtool ConvertVideoToAndroid
Download InstallOnAndroid Nautilus Script
InstallOnAndroid
Disclaimer
I am not responsible for anything. Anything at all. I'm just not. Blame someone else if something goes horribly wrong.

[Reserved]
[Reserved for future post]

Nice script but bart.sh can accomplish a full backup of your Android environment for restoration at a later date. While it does it to the SD card initially, these "barts" can easily be copied to any computer. I can, however, see a use for this as it serves a slightly different purpose. Thanks.

I wasn't sure what response I would get to this post. I have had to flash, partition, format, wipe.. enough times that I just wanted to plugin into my computer, backup, wipe-flash then restore. Thanks!

nice. I don't use linux myself, but i see the point of having the backup else where (not an SD card attached to the phone itself).
will this, in theory be made to work on windows? Cause that will be awesome.

@str4vag It would be really simple to just use a .bat file for Windows. I don't have any plans on making a windows script anytime soon. Sorry. Same commands especially though.

This is exactly what I've been looking for, now I just need to mod it to sync apps/bookmarks/etc automatically whenever I plug in my phone, and to only sync the new items to keep it speedy, great work dev!

@ggolemg I can play around with some "real" features soon. I plan on having it archive your backups and allow you to select which backup (default is most recent) you would like to use. I am sure I can play around with your idea too. Thanks.

subscribing to the thread, idea is very interesting. i've been looking for a foolproof way to backup and restore bookmarks, sms messages, and different alarms, without all the issues of backup for root users. gonna check out the script tonight.

Update coming by the end of the week.
- Will only backup apps not already backed up.
- Possibly apply the Python interface I have developed.
- More goodies.

How about switchrom?

Android-Linux-Tools
Okay, so this week has been crazy for me. (Mind you I am a restaurant manager first and a developer (primary web) second). I think I am going to gear this project in a different direction. First off, I have created GTK2 Dialogs and a settings panel for this application. I would like to gear towards general linux tools on the pc side. So over the next two weeks you can expect,
- Graphical Interface for abrtool (Android-Backup-Restore)
- Configuration for each application.
- Nautilus Scripts for all applications.
- Right-Click to Encode Video (With GTK2 Dialog progress)
- Right-Click to Install APK (With GTK2 Dialog progress)
- Right-Click to Sign APK (With GTK2 Dialog progress)
- Right-Click to Copy Files to SD Card
- abrtool will backup to Ubuntu One Cloud (Simple adb pull ~/Ubuntu\ One/? or maybe play with the API?)
Ideas and Possibilities
- User.conf editor
- Select with applications to backup
- Switchrom features?
Any other thoughts or suggestions are welcome. I want to start simple, keep working on the abrtool and then make my way out to some other useful tools for us linux (Ubuntu) users. Let me know what you think and what would be helpful.

i had to make a bynch of edits so this dosent run as root, id recomend everyone do the same, only run root when you must. Also changed ,.adb to adb so i dont have to run it in my android sdk dir

@ahronzombi Can you post those changes?

I am a firm believer of only running root when needed, Like I mentioned before I don't really have a huge amount of time, and when I tested this on a friends notebook adb required root to atleast kill-server then you could perform shell/push/pull.

AFAIK, adb server only requires root if ou haven't set the proper udev rules for the device.

Exactly. If we want this script to run universally we cannot rely on all users to have added the udev rules. If they don't they have to run sudo. Maybe a quick check for the udev file then sudo if not?

boulderjams said:
Exactly. If we want this script to run universally we cannot rely on all users to have added the udev rules. If they don't they have to run sudo. Maybe a quick check for the udev file then sudo if not?
Click to expand...
Click to collapse
no i think it would be wise to have people understand there udev permissions rather than run root so its universal. that kind of thinking leads to very big security problems. with root in the script most of the simplest linux users could exploit anyone

I fully understand that. Do you mind posting your changes to the script?

this is the secure version of the script that dosent run as root
keep in mind i set my own adb and home directorys so you'll have to change those
Code:
#! /bin/bash
# abrtool version 0.1
# Last Updated Wednesday, November 18, 2009
# Android Backup Data and Restore Data Script
#TODO
# 1- See if config file exists
# 2- If not, create config file (for now, select directory to backup to)
# 3- See if arguments are specified
# 4- If not, return an error via dialog
# 5- If argument -b exists, run backup
# 6- If argument -r exsists, run restore
export PATH=${PATH}:/home/ahron/android/android-sdk-linux/tools:/home/ahron/android/abr
BACKUPDIR=/home/ahron/android/backups
USER=${username-`whoami`}
backupscript() {
export PATH=$PATH:$BACKUPDIR
adb kill-server
adb pull /system/sd/app $BACKUPDIR/apps
adb pull /system/app $BACKUPDIR/apps/device
echo "---------- Backed Applications"
adb pull /data/data/com.android.providers.telephony/databases/mmssms.db $BACKUPDIR/msgs/mmssms.db
echo "---------- Backed Text Messages"
adb pull /data/data/com.android.browser/databases/browser.db $BACKUPDIR/bookmarks/browser.db
echo "---------- Backed Bookmarks"
adb pull /data/data/com.android.alarmclock/databases/alarms.db $BACKUPDIR/other/alarms.db
adb pull /data/data/com.google.android.providers.settings/databases/googlesettings.db $BACKUPDIR/other/googlesettings.db
adb pull /data/data/com.android.launcher/databases/launcher.db $BACKUPDIR/other/launcher.db
adb pull /data/data/com.android.providers.userdictionary/databases/user_dict.db $BACKUPDIR/other/user_dict.db
echo "---------- Backed Other Settings"
chown -R $USER $BACKUPDIR
zenity --info --text "Successfully Backed-up to $BACKUPDIR"
}
restorescript() {
export PATH=$PATH:$BACKUPDIR
adb kill-server
#sudo adb push $BACKUPDIR/apps /system/sd/app
echo "----------- Installing Applications"
cd $BACKUPDIR/apps
for searchfile in ./*.apk
do
echo "------------ Processing $searchfile"
sudo adb install "$searchfile"
done
echo "---------- Restored Applications"
adb shell su
adb shell fix_permissions
echo "---------- Fixed Application Permissions"
adb push $BACKUPDIR/msgs/mmssms.db /data/data/com.android.providers.telephony/databases/mmssms.db
echo "---------- Restored Messages"
adb push $BACKUPDIR/bookmarks/browser.db /data/data/com.android.browser/databases/browser.db
echo "---------- Restored Bookmarks"
echo "---------- (Please, make sure to restart your browser)"
adb push $BACKUPDIR/other/alarms.db /data/data/com.android.alarmclock/databases/alarms.db
adb push $BACKUPDIR/other/googlesettings.db /data/data/com.google.android.providers.settings/databases/googlesettings.db
adb push $BACKUPDIR/other/launcher.db adb pull /data/data/com.android.launcher/databases/launcher.db
adb push $BACKUPDIR/other/user_dict.db /data/data/com.android.providers.userdictionary/databases/user_dict.db
echo "---------- Restored Other Settings"
zenity --info --text "Successfully Restored Android device from $BACKUPDIR"
}
if [ "$#" -eq 0 ]
then
echo "Usage $0"
echo " -b Backup"
echo " -r Restore"
exit $E_OPTERR
fi
set -- `getopt "br:" "[email protected]"`
while [ ! -z "$1" ]
do
case "$1" in
-b) backupscript;;
-r) restorescript;;
esac
shift
done

Alternative method: Removing bloatware

Requirements:
- ClockworkMod Recovery on your device
- Know how to reboot into recovery
- Have Android SDK (adb) installed - and familiar with the concept of what it does, and know how to access it via command line - if not look around, it's everywhere on how to do this.
Disclaimer:
- What you do is your fault
Optional:
- Ability to discern what, and what not to remove
Synopsis:
This is a good technique if you're receiving 'read only' errors while trying to remove apps - namely located in /system/app
[size=+3]Method:[/size]
- Reboot into recovery - it's been said in other threads it's best to DISCONNECT USB, power down, boot into recovery and THEN replug the USB connector.
- Using the clockwork menu - navigate down to 'partitions menu' using your volume down button - then hit the power button
- From the partitions menu, select 'mount /system' and hit the power button
- From your Android SDK tools directory - check 'adb devices' - this should indicate your phone is connected and in 'recovery' mode.
e.g.:
Code:
$ adb devices
List of devices attached
HT06BR007742 recovery
- Type 'adb shell' - this will put you into a command line for your phone
- From the command shell: 'cd /system/app'
- To get a list of what you can remove, type 'ls'
- To remove an .apk - type 'rm FileName.apk'
- When you're done, it's suggested you use the clockwork menu to reboot the phone ('back to the main clockwork menu, and 'reboot device')
Further example / note:
Once logged in via 'adb shell' and the system dir is mounted via clockwork:
Code:
/system/app # ls |grep "ATT"
ATT_Maps.apk
ATT_Navigator.apk
/system/app # rm ATT_Navigator.apk
Also, a side note, you can see all available commands for this shell by typing:
Code:
ls /sbin
The list is quite comprehensive.

I hope this helps someone

thanks thinice !

Added to the sticky roll-up.

I'm not 100% on this but I was able to uninstall whatever I wanted through Titanium Backup, including the ATT bloatware once I was rooted.

I am not sure about the Titanium Backup method. I restored to stock rom with root and used Titanium backup to remove some apps. They showed as removed, however when I reboot the phone the apps are back and not removed. I could not get Titanium backup to remove the apps with root alone.

removing AT&T Radio
I have searched the forum and have not yet found the answer to this question...I have removed all of the AT&T apps that I want to remove, except, which apk is AT&T radio?

You talking about fm radio on a sense rom?
Sent from my HTC Liberty using XDA App

Ah, no I'm using my HTC Aria with the stock image. I've rooted it though, and I'm just getting rid of the included AT&T apps I do not want. This one shows up as "AT&T Radio". Just trying to figure out which apk to remove in order to remove this app.

what apps are SAFE to remove without effecting HTC Sense or Aria? we need to make a list of files/apps safe to remove. i heard one user saying removing HTC stocks caused error issues when it tried to sync.

Hello also any luck with change the radio to activate for 1700 mhz UMTS ?

wdlamb said:
Ah, no I'm using my HTC Aria with the stock image. I've rooted it though, and I'm just getting rid of the included AT&T apps I do not want. This one shows up as "AT&T Radio". Just trying to figure out which apk to remove in order to remove this app.
Click to expand...
Click to collapse
AndroidMusic.apk

Thanks, that was exactly what I was looking for.

I've worked on this a few hrs now. I got Clockwork Recovery to work. Figured out HTC Sync was reverting the phone to stock recovery somehow. Removed that though...
Have rerun Unrevoked, and I can get into clockwork. I'm not interested in changing to different ROM now, just removing ATT crap.
When I try sideloading instructions/alternate method for removing ATT stuff, I get an error in cmd:
C:\android\tools>adb remount
remount failed: Operation not permitted
adb devices returns:
List of devices attached:
<myserial#> device
Any ideas? Have I not completed the root access procedure? I thought it was part of the Unrevoked process.

ahren37 said:
I've worked on this a few hrs now. I got Clockwork Recovery to work. Figured out HTC Sync was reverting the phone to stock recovery somehow. Removed that though...
Have rerun Unrevoked, and I can get into clockwork. I'm not interested in changing to different ROM now, just removing ATT crap.
When I try sideloading instructions/alternate method for removing ATT stuff, I get an error in cmd:
C:\android\tools>adb remount
remount failed: Operation not permitted
adb devices returns:
List of devices attached:
<myserial#> device
Any ideas? Have I not completed the root access procedure? I thought it was part of the Unrevoked process.
Click to expand...
Click to collapse
Yes, I think I was getting the same problem so I did a sequence of steps in some weird sequence to actually change it. It went something like this:
1. Make sure your PATH variable is set to Tools folder of Android SDK
2. Boot your phone into Clockwork and connect to PC
3. On your phone go to Partitions Menu and mount /system, then mount USB storage
3. Go to command prompt on your PC change your drive to phone/SD card drive (whatever that is, F:\ in my case)
4. adb remount
5. unmount /system
6. mount /data, mount USB storage
7. adb pull /data/data/com.android.providers.settings/databases/settings.db C:\settings.db
where C:\ is the main PC drive
8. change to C:\
9. echo update secure set value = 1 where name = 'install_non_market_apps';|sqlite3 settings.db
10. change to F:\
11. adb push C:\settings.db /data/data/com.android.providers.settings/databases/settings.db
12. Unmount everything, reboot and sideloading should work

sorting and backup
To see which files take the most space, use du with sort:
Code:
du * | sort -n
If concerned about deleting an important app, try moving it to the sd card instead. First mount the sdcard with the recovery menu, then:
Code:
mkdir -p /sdcard/backup/system/app
mv /system/app/something.apk /sdcard/backup/system/app
Thanks for the guide!

Great I'll try this tonight. Thanks
Sent from my HTC Aria using XDA App

I'm getting errors when attempting to remove the ATT_Navigator and ATT_Maps.
/system/app # rm ATT_Navigator.apk
rm ATT_Navigator.apk
rm: can't remove 'ATT_Navigator.apk': Directory not empty
Same error for both. Any suggestions?
I'm running Liberated 2.1 and ClockworkMod 2.5.0.1.

asiancuta said:
what apps are SAFE to remove without effecting HTC Sense or Aria? we need to make a list of files/apps safe to remove. i heard one user saying removing HTC stocks caused error issues when it tried to sync.
Click to expand...
Click to collapse
Yeah, I think it'll be nice to have a master list so future people won't have to mess with backups.
some I'm curious about is Mobi TV, Mobile banking, Mobile Video, Peep, and mostly if it'll be okay to remove the htc twitter widget.

the only program i ran into any issues with removing was the defalut mms app. i decided to see what would happen if i got rid of that app and replaced it with handcent or chompsms. those programs could still send messages, but i couldn't receive any.
the easiest way to compile a list like that is browse the forums for any preexisting knowledge, then just start testing things for yourself. make a nandroid backup of your rom as it sits, start removing programs, boot normally and see what happens! if theres no errors after you've removed the desired apk, make a new backup, reboot into recovery and keep going at it.

Porting cyanogenmod

I am attempting to port Cyanogenmod to the Garminfone. I have root, know how to have it load a recovery.img at boot, and know how to flash partitions on it (it comes with a flash_image program that can flash an image to a given partition, which is how it flashes the recovery.img
I am very familiar with the layout of the partitions, os, and with not too much effort could get the current OS running in the emulator,as they left all of the emulator initial scripts on the device and did a great job commenting everything.
The one thing I am not sure about is flashing the bootloader in a way that will not trash the device. I know it is a msm7227 cpu and can provide dumps of anything anyone may need to help.
Any assistance would be appreciated. Thanks!

Hi Merwin, Have you had any success porting CM to garminfone/nuvifone A50?

No luck yet... still trying to figure out how to do it without bricking it. Not getting much in the way of assistance on how to port the recovery image to my phone properly, so I can recover while testing.
I know how to unpack it and a couple ways of getting it flashed back that are yet untested but should work.
Its pretty standard hardware (msm7227), and aside from the Atheros wifi and potentially the gps in it (crazy accurate, down to 6.6 feet and works without a sim, so I think there must be something different) the sensor drivers all report being standard android drivers.
I make my living doing software development, database development, and lots of middleware to get different systems to play nicely,but have nearly no hardware or driver development experience and very little work with asm, so decompiling and inspection is out, but can figure out most anything when pointed in the right direction. I just need someone experienced to work with me on it.
Anyone interested?
Sent from my Garminfone using XDA App

Wouldn't it just be easier to figure out how to compile a rooted recovery and to set up mayb keymaps to be able to boot from.. With a recovery thats able to flash if we were to have to flash the bootloader change spl/radio or anything we would be able to go about making a update.zip for the recovery and flash it that way???

I can already rebuild the existing recovery img as well as the bootloader. The existing recovery can flash an update.zip if the keymapping to select menu entries was there.
There is no hardware method to boot into recovery aside from the failsafe, which triggers if the main boot image fails to load a certain number of times.
So, you are safe unless you **** up both the main bootloader and the recovery... which is why I flash any test boot image to the recovery partition first, test it, then flash back my rooted recovery, test it, and flash the main boot image.
It takes longer, but works. What would be nice would be to compile the boot image using the first stage loader as well as the second stage loader. That would let you have your minimal loader that responds to the recovery keychord and then boots to the second stage loader that has all the features. Not sure how to accomplish it.
I did check the kernel config and every nonstandard component is loaded as a module and the kernel is 2.6.29 so there is no reason why we shouldn't be able to configure and compile a working Froyo at the very least.
I just need to work my way through the build process. The fun part will be seeing if the Garmin software would run on Cyanogen or if it checks more than just the model and serial.

I'm watching your progress with anticipation. I have no programming or development experience, but if I can help with testing or anything let me know.
Sent from my Garmin-Asus A50 using XDA App

Also watching this thread! Would love to be able to flash a kernel that allows overclocking and hopefully 2.2

Was this ever completed?

Re: Cyanogen for Garminfone
There is a solution. I just made it last weekend. This post will follow with video demos.
---
Start with a factory wipe.. not using garmins KB method: (We want a clean FS mounted)
Unmount and remove SD Card from phone.
Connect a usb cable and enable USB mass storage mode.
Create a desktop folder and move all contents of Garminfone drive to new folder.
Download 7-zip and restore.zip from garmin-asus support site.
Open restore.zip, browse restore and drag drop .system to root of Garminfone storage.
While USB mass storage mode is enabled hit menu > settings > privacy > master reset. Yes, yes.
Wait for the phone to reboot twice.
Pop cover, install SD card.
Menu > Settings > Storage
SD Card detected use as default? No.
Scroll down, unmount, format.
Scroll up, Default storage > SD Card
Home
Slide > USB > File Transfer
Launch Garmin Web Updater .. install select guide icons, voices, etc.
Optionally update garmin lifetime maps now here.
Install z4root and root phone
Open Superuser and check for updates, reboot if updates apply.
Install GO Launcher and replace ‘Breeze’ launcher
You should reboot now. (Apps > Terminal Emulator > #su > #reboot )
Install a startup manager (I used Android Assistant)
Cut the following apps from User/System startup: Flashlight,CardioTrainer,My Tracks, Pandora, Garmin Voice Studio, IM, Messaging, My Account, Offers Provider..
Install Dolphin Browser Mini
Install Google Voice (Port your number!!)
Install SSHDroid
Reboot phone when all is complete (Apps> Terminal Emulator > #su > #reboot )
From here forward it is much easier from a desktop ssh terminal such as putty, but this is entirely up to you. It may also be done in the Terminal Emulator app on the phone without using SSHDroid.
If you use Visual Voicemail still.. (its a mem hog!) omit the line with vvm-signed.apk
Either use T.E. and start with #su (root) and do the following commands or ssh as root/admin:
We’re going to remount the system partition so we can move some stuff around and trim the fat.
mount -o remount,rw,noatime,nodiratime,data=ordered -t ext3 /dev/block/mmcnand
blk0p3 /system
We’re going to hide some of the standard bundled apps since the phones permissions are all over the place we’re going to rename the files instead of doing a chmod -x:
cd /system/carrier/persist-app/
mv amazonmp3.apk amazonmp3.apk.no
mv HotSpotApp.apk HotSpotApp.apk.no
mv Myspace.apk Myspace.apk.no
mv Twitter.apk Twitter.apk.no
mv vvm-signed.apk vvm-signed.apk.no
Let’s make the phone boot the way Garmin-Asus intended:
mv /system/carrier/images/startup/bootanimation.zip /system/carrier/images/startup/bootanimation.zip.no
reboot !
The phone should now have around 70Mb RAM free!! Around 32Mb with Google maps/navigation running. This *will not* break your lifetime maps!
I highly reccomend making a point in time snapshot of some sort (Titanium Backup)
---------- Post added at 12:50 PM ---------- Previous post was at 12:37 PM ----------
There is a solution. I just made it last weekend. This post will follow with video demos.
---
Start with a factory wipe.. not using garmins KB method: (We want a clean FS mounted)
Unmount and remove SD Card from phone.
Connect a usb cable and enable USB mass storage mode.
Create a desktop folder and move all contents of Garminfone drive to new folder.
Download 7-zip and restore.zip from garmin-asus support site.
Open restore.zip, browse restore and drag drop .system to root of Garminfone storage.
While USB mass storage mode is enabled hit menu > settings > privacy > master reset. Yes, yes.
Wait for the phone to reboot twice.
Pop cover, install SD card.
Menu > Settings > Storage
SD Card detected use as default? No.
Scroll down, unmount, format.
Scroll up, Default storage > SD Card
Home
Slide > USB > File Transfer
Launch Garmin Web Updater .. install select guide icons, voices, etc.
Optionally update garmin lifetime maps now here.
Install z4root and root phone
Open Superuser and check for updates, reboot if updates apply.
Install GO Launcher and replace ‘Breeze’ launcher
You should reboot now. (Apps > Terminal Emulator > #su > #reboot )
Install a startup manager (I used Android Assistant)
Cut the following apps from User/System startup: Flashlight,CardioTrainer,My Tracks, Pandora, Garmin Voice Studio, IM, Messaging, My Account, Offers Provider..
Install Dolphin Browser Mini
Install Google Voice (Port your number!!)
Install SSHDroid
Reboot phone when all is complete (Apps> Terminal Emulator > #su > #reboot )
From here forward it is much easier from a desktop ssh terminal such as putty, but this is entirely up to you. It may also be done in the Terminal Emulator app on the phone without using SSHDroid.
If you use Visual Voicemail still.. (its a mem hog!) omit the line with vvm-signed.apk
Either use T.E. and start with #su (root) and do the following commands or ssh as root/admin:
We’re going to remount the system partition so we can move some stuff around and trim the fat.
mount -o remount,rw,noatime,nodiratime,data=ordered -t ext3 /dev/block/mmcnand
blk0p3 /system
We’re going to hide some of the standard bundled apps since the phones permissions are all over the place we’re going to rename the files instead of doing a chmod -x:
cd /system/carrier/persist-app/
mv amazonmp3.apk amazonmp3.apk.no
mv HotSpotApp.apk HotSpotApp.apk.no
mv Myspace.apk Myspace.apk.no
mv Twitter.apk Twitter.apk.no
mv vvm-signed.apk vvm-signed.apk.no
Let’s make the phone boot the way Garmin-Asus intended:
mv /system/carrier/images/startup/bootanimation.zip /system/carrier/images/startup/bootanimation.zip.no
reboot !
The phone should now have around 70Mb RAM free!! Around 32Mb with Google maps/navigation running. This *will not* break your lifetime maps!
I highly reccomend making a point in time snapshot of some sort (Titanium Backup)
---------- Post added at 01:01 PM ---------- Previous post was at 12:50 PM ----------
Since I can't link, I'm too new. You'll have to search youtube for Garminfone 2.1 root demo under user mjlar94. There are three videos, enjoy. You are now back on the grid using actively supported and updated applications.
I was unable to locate and disable the WhereTo app, this would take some discovery to find out if the GPS functionality is nested in the Garmin apk's. You should switch to google Nav/Places

Hi
Any help where can I fine the procedure on how to port Cyanogenmod 10 on a ICS phone? Can I do this on a stock rom of an ICS phone or do I need to wait for a JB Rom?

Hello all,
It's fantastic this works, but as you see i'm a noob. And these guidelines above are simply too difficult to follow...
I looked for the vid's but none of them show the whole deal...
Can you bee so kind to go thrue this step by step?
That would help me very much to get cyanogen on my Garminfone...
I'm waiting already very very long to do so...!!
So MLARIV, thank you in advance!
Grtz From Belgium
Dreezyne

[ROOT][FILESYSTEM]Full 500MB SuperSU rooted Root.fs for BlueStacks

Current rooted version: 0.8.3.3026
!!!UPDATE 07DEC13!!! -> With SuperSU v1.80!
Here are the rewritable rooted filesystem-files for BlueStacks. Easy if you want to install BlueStacks for development reasons and don't want to go through the trouble of rooting it yourself.
I'll try to keep it updated as they make their updates, but since they don't really announce them, forgive me if I skip some. :silly:
It's also allowed to point me out there's a new version, I'll probably get to it faster that way.
Anyway,
Usage:
Install BlueStacks
Quit Bluestacks completely.
- (By clicking on their tray icon and selecting Quit, or by running the HD-Quit.exe)
Go to your BlueStacks-ProgramData directory
- (In Windows Vista and up it's: x:\ProgramData\BlueStacks)
- (In Windows XP it'll be: x:\Documents and Settings\All Users\Application Data\BlueStacks)
Unpack and replace Root.fs and initrd.img with the 2 files in this 7zip
Restart BlueStacks
If "Installer" asks root access, give it root access... ;p
Done!
Code:
[URL="http://cur.lv/5atkp"][COLOR="DeepSkyBlue"][U]Download both files 7zip'd from 'ADrive' here[/U][/COLOR][/URL] (269.3MB)
Mirrors:
[URL="http://cur.lv/5atb6"][COLOR="SeaGreen"][U]Download both files 7zip'd from 'FileDropper' here[/U][/COLOR][/URL] (269.3MB)
[URL="http://cur.lv/5blid"][COLOR="DarkBlue"][U]Download both files 7zip'd from 'Dev-Host' here[/U][/COLOR][/URL] (269.3MB)
[URL="http://cur.lv/5blth"][COLOR="DarkOrchid"][U]Download both files 7zip'd from 'MediaFire' here[/U][/COLOR][/URL] (269.3MB)
[URL="http://cur.lv/5bpjr"][COLOR="Red"][U]Download both files 7zip'd from 'Android File Host' here[/U][/COLOR][/URL] (269.3MB)
---
[URL="http://bit.ly/1bP5VjD"]MD5 Checksum[/URL]: 0f199f0f353e701a7b9c535098b243b3
Please excuse me trying to get something out of the trouble, though. ;p
----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- -----
Then, for the noobs that just can't get it working and the limitless downloaders who just don't look at filesize, next, I give you the full 'Android' directory! 7zipped while not running, these files are a certainty that all should work, because they come with /system and /data together and are meant to replace your own. All your own apps and settings (not your backupz to SD) will have gone after doing the following, so it's only recommended when you're planning to start anew anyway or when you just can't get the root into it for some reason... Or maybe you planned ahaed and backed everything up anyway... ;p These files are certain to give you not only SuperSU-root access, but also a Play Store ready to use and as a bonus a full Debian Linux (Jessie) installed underneath it. (This is why it's so much bigger. ;p)
A little info on the linux:
Debian's root password is set to "bluestacks", and it's also the password for the "BlueStacks" user. You can change these without any problems. You can also just enter Debian Linux by opening the installed Terminal. I already preset it to do this. I also used the none standard Terminal app so you can use the normal one for your own purpouses without constantly fiddling and swapping with it's settings. ;p
So, just kill BlueStacks completely and swap the contents of this 7z with the contents of your ProgData-BlueStacks-Android dir (except for the missing sdcard.sparsefs, of course).
It should be located here:
- For XP: x:\documents and settings\all users\application data\BlueStacks\Android
- For Vista, 7, 8,...: x:\programdata\BlueStacks\Android
(x marks the drive your windows is installed on. )
And restart BlueStacks.
Code:
[URL="http://cur.lv/5d4xj"][COLOR="DeepSkyBlue"][U]Download the BlueStacks Androdebian Project from 'ADrive' here[/U][/COLOR][/URL] (622.3MB)
[URL="http://cur.lv/5dbr7"][COLOR="SeaGreen"][U]Download the BlueStacks Androdebian Project from 'FileDropper' here[/U][/COLOR][/URL] (622.3MB)
[URL="http://cur.lv/5dct9"][COLOR="DarkBlue"][U]Download Part 1 of the BlueStacks Androdebian Project from 'Dev-Host' here[/U][/COLOR][/URL] (311.5MB)
[URL="http://cur.lv/5dcyx"][COLOR="DarkBlue"][U]Download Part 2 of the BlueStacks Androdebian Project from 'Dev-Host' here[/U][/COLOR][/URL] (310.8MB)
[URL="ttp://cur.lv/5d51y"][COLOR="DarkOrchid"][U]Download the BlueStacks Androdebian Project from 'MediaFire' here[/U][/COLOR][/URL] (622.3MB)
[URL="http://cur.lv/5dciu"][COLOR="Red"][U]Download the BlueStacks Androdebian Project from 'Android File Host' here[/U][/COLOR][/URL] (622.3MB)
---
[URL="http://bit.ly/JbVniG"]MD5 Checksum (Full File)[/URL]: 5763bf8f96d4f4990494d4bab1b2fd0b
[URL="http://bit.ly/18mVKlB"]MD5 Checksum (Part 1)[/URL]: 32ee4dc23717c2c5878dfdf125231fe1
[URL="http://bit.ly/Jg3v1H"]MD5 Checksum (Part 2)[/URL]: 7a989a027454786ab45fe4eb6d3917b7
----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- ----- -----
And btw, if you want to try it yourself, I always write down my steps taken, so here they are:
Rooting BlueStacks as I did it:
For this you will need the following programs:
BlueStacks (of course)
IOBit Uninstaller
7zip
Notepad++
Portable Ubuntu
I used Windows XP x86, but I added the info for higher windows versions and x64 windows versions as well)
x marks the drive your windows is installed on.
Winkey-R (Run) "%programfiles%\BlueStacks\HD-Quit.exe" (or "%Programfiles(x86)%\BlueStacks\HD-Quit.exe" for x64);
Kill HD-LogRotatorService.exe in Task Manager;
I used IOBit Uninstaller because I hate waiting on the Windows internal one and it does a lot more stuff we need done.
(If you want it and haven't already, get IOBit Uninstaller here!);
Uninstall BlueStacks with IOBit Uninstaller;
Choose to scan for remaining stuff and delete all of the findings;
Uninstall BlueStacks Notification Center
When it asks to keep all data and userfiles, say no;
Delete x:\Documents and Settings\All Users\Application Data\BlueStacksSetup (or x:\ProgramData\BlueStacksSetup in Vista or higher)
('BlueStacks' dir has been removed by clicking 'yes' in uninstall, if not, remove it as well);
If you can't delete hyperviser.log, you'll have to reboot first, then delete the BlueStacks folder before you'll be able to continue.
Re-install BlueStacks
(If you haven't already, get BlueStacks here!);
Download "busybox-i686" from this site and rename it to "busybox";
Download SuperSU in flash zip format from this site.
Inside this zip is more then just SuperSU. Unzip these files to "c:\pubuntu":
(out of zipped directory "/common"
- "Superuser.apk";
- "install-recovery.sh";
- "99SuperSUDaemon";
(out of zipped directory "/x86"
- "su";
Open Superuser.apk with 7zip, extract the files "/assets/chattr.x86.png" and "/assets/supersu.x86.png to any temporary directory, rename the files to "chattr.arm.png" and "supersu.arm.png", re-insert them (by dragging them back to the still open 7zip) and replace the other 2 png-files.
(If you haven't already, get 7zip here!);
Close 7zip and save;
Open x:\Documents and Settings\All Users\Application Data\BlueStacks (or x:\ProgramData\BlueStacks in Vista or higher);
Open "initrd.img" with 7zip;
Unpack "initrd" to any temporary dir;
Open "initrd" with Notepad++
(If you haven't already, get Notepad++ here!);
Search for " ro " (including the spaces, not the quotationmarks)
There should be two results, change the first to " rw "
- Hint: It's not the one which starts with "Option: ro (read-only",
It's the one that resembles 'try_mount ro $1 /mnt && [ -e /mnt/$SRC/ramdisk.img ]'. ;P;
Save "initrd" and close Notepad++;
Drag it back into the 7zip application where "initrd.img" is still open and overwrite existing "initrd";
Close 7zip;
Then you'll need Portable Ubuntu
(If you haven't already, get Portable Ubuntu here!);
NOTE: Portable Ubuntu does not work on x64 Windows, so if you're not running an x86 Windows, you'll need to use a Linux box or vm (with shared folders) here instead.
- If you have Windows installed on any other drive than C, do the following, if it's installed in C, skip this:
- Open Ubuntu Portable folder;
- Go to the "config" subfolder;
- Edit the file "portable_ubuntu.conf";
- Under the line: "shared_folder0=c:\" add "shared_folder1=x:\" (where x is still the drive your windows is on);
- Save "portable_ubuntu.conf" and exit Notepad++;
Open Portable Ubuntu;
Open the terminal window once it's fully loaded;
Do the following in the exact order:
Code:
sudo su
(pubuntu's password is '123456')
mkdir /n
mkdir /n/rootfs
mkdir /n/sfs
mkdir /n/img
[B]- If windows was on C:[/B]
e2fsck -f -y "/media/cofs2/Documents and Settings/All Users/Application Data/BlueStacks/Android/Root.fs"
resize2fs -f "/media/cofs2/Documents and Settings/All Users/Application Data/BlueStacks/Android/Root.fs" 500M
mount -o loop "/media/cofs2/Documents and Settings/All Users/Application Data/BlueStacks/Android/Root.fs" /n/rootfs
[COLOR="Gray"](or for Vista and up:
e2fsck -f -y "/media/cofs2/ProgramData/BlueStacks/Android/Root.fs"
resize2fs -f "/media/cofs2/ProgramData/BlueStacks/Android/Root.fs" 500M
mount -o loop "/media/cofs2/ProgramData/BlueStacks/Android/Root.fs" /n/rootfs
)[/COLOR]
[B]- If not:[/B]
[I]e2fsck -f -y "/media/cofs3/Documents and Settings/All Users/Application Data/BlueStacks/Android/Root.fs"
resize2fs -f "/media/cofs3/Documents and Settings/All Users/Application Data/BlueStacks/Android/Root.fs" 500M
mount -o loop "/media/cofs3/Documents and Settings/All Users/Application Data/BlueStacks/Android/Root.fs" /n/rootfs
[COLOR="Gray"](or for Vista and up:
e2fsck -f -y "/media/cofs3/ProgramData/BlueStacks/Android/Root.fs"
resize2fs -f "/media/cofs3/ProgramData/BlueStacks/Android/Root.fs" 500M
mount -o loop "/media/cofs3/ProgramData/BlueStacks/Android/Root.fs" /n/rootfs
)[/COLOR][/I]
mount -o loop /n/rootfs/android/system.sfs /n/sfs
cp /n/sfs/system.img /n/rootfs/android
e2fsck -f -y /n/rootfs/android/system.img
resize2fs -f /n/rootfs/android/system.img 480M
umount /n/sfs
rm /n/rootfs/android/system.sfs
rmdir /n/sfs
mount -o loop /n/rootfs/android/system.img /n/img
mkdir /n/img/bin/.ext
mkdir /n/img/etc/init.d
cp "/media/cofs2/pubuntu/su" /n/img/xbin/daemonsu
cp "/media/cofs2/pubuntu/su" /n/img/xbin/su
cp "/media/cofs2/pubuntu/su" /n/img/bin/.ext/.su
cp "/media/cofs2/pubuntu/Superuser.apk" /n/img/app/SuperSU.apk
cp "/media/cofs2/pubuntu/install-recovery.sh" /n/img/etc/install-recovery.sh
cp "/media/cofs2/pubuntu/99SuperSUDaemon" /n/img/etc/init.d/99SuperSUDaemon
cp "/media/cofs2/pubuntu/busybox" /n/img/xbin
echo 1 > /n/img/etc/.installed_su_daemon
chown 0:2000 /n/img/bin/.ext
chown 0:2000 /n/img/bin/.ext/.su
chown 0:2000 /n/img/xbin/su
chown 0:2000 /n/img/xbin/daemonsu
chmod 777 /n/img/bin/.ext
chmod 6755 /n/img/bin/.ext/.su
chmod 6755 /n/img/xbin/su
chmod 6755 /n/img/xbin/daemonsu
chmod 755 /n/img/etc/install-recovery.sh
chmod 755 /n/img/etc/init.d/99SuperSUDaemon
chmod 644 /n/img/etc/.installed_su_daemon
chmod 644 /n/img/app/SuperSU.apk
umount /n/img
rmdir /n/img
chown 0:2000 /n/rootfs/android/system.img
chmod 0644 /n/rootfs/android/system.img
umount /n/rootfs
rmdir /n/rootfs
rmdir /n
exit
exit
Shutdown Portable Ubuntu;
Boot BlueStacks;
Install custom launcher like ADW, Go or Apex (Superuser app does not show up in BlueStacks' Launcher);
Install Root Explorer;
Move custom launcher from "/data/app" to "/system/app";
Reboot BlueStacks;
You can now safely remove apps like "Launcher2.apk" and "new_Home.apk" and other original launcher related stuff.
Enjoy and grtz,
~ Nephatiu

Can you explain the steps to root my version manually instead of downloading a 500mb file, if not possible then can you please provide a mirror since Adrive gives Public File Busy error all the time to me?
Thanks
Edit:
Never mind, ignore it. Got it now. Although it's better if you could provide mirrors for others as Adrive is giving problems. I had to download using a premium downloader.

nicesoni_ash said:
Can you explain the steps to root my version manually instead of downloading a 500mb file, if not possible then can you please provide a mirror since Adrive gives Public File Busy error all the time to me?
Thanks
Edit:
Never mind, ignore it. Got it now. Although it's better if you could provide mirrors for others as Adrive is giving problems. I had to download using a premium downloader.
Click to expand...
Click to collapse
Still want instructions, then?
Cause I wrote down the steps I took, so I could easily paste them here (and adapt them a little for others to read, of course. ).
Grtz,
~ Nephatiu

Sure go ahead if you already wrote them down. It will be useful since it's a separate thread then your other post where you put these download links. The only thing messing up my plans right now is to download that portable linux for 1+gb file so for now I have downloaded your files and they work great, I will make them manually next time when there will be a new bluestack update.
Thanks

Rewritable initrd.img (1.3MB)
Rooted Root.fs (500MB)
Click to expand...
Click to collapse
Don't work this url...

nicesoni_ash said:
Sure go ahead if you already wrote them down. It will be useful since it's a separate thread then your other post where you put these download links. The only thing messing up my plans right now is to download that portable linux for 1+gb file so for now I have downloaded your files and they work great, I will make them manually next time when there will be a new bluestack update.
Click to expand...
Click to collapse
Okay, I'll add it in the original post,... ;p
Grtz,
~ Nephatiu

New Version
Version 0.8.2.3018 is out.
I accepted the update & Root Checker Pro says I still have root.

SuperSU updated
SuperSU just updated a few hours ago. Problems to update the apk. Could someone please update Root.fs and initrd.img with the new superSU apk.
Thank you

0.8.2.3018 updates and root is still there except the root apk is gone as the Root.fs has been replaced.

Almighty2 said:
0.8.2.3018 updates and root is still there except the root apk is gone as the Root.fs has been replaced.
Click to expand...
Click to collapse
I'll be adding my new Root.fs here later today. Just got back from a few days trip, and first of all I need some sleep, but when I wake, I'll get right to it.
Grtz,
~ Nephatiu

Nephatiu said:
I'll be adding my new Root.fs here later today. Just got back from a few days trip, and first of all I need some sleep, but when I wake, I'll get right to it.
Grtz,
~ Nephatiu
Click to expand...
Click to collapse
If possible could the root files be compressed before theyre uploaded by any chance in .7z? it would half the download size from 500MB to around 256MB, im sure the many with sucky internet speeds would appreciate it >.<
Hope you enjoyed le trip ~

Chakkas said:
If possible could the root files be compressed before theyre uploaded by any chance in .7z? it would half the download size from 500MB to around 256MB, im sure the many with sucky internet speeds would appreciate it >.<
Hope you enjoyed le trip ~
Click to expand...
Click to collapse
Good idea. I don't know why I didn't do that in the first place...
Ah, well, I'll 7zip them and up them again,...
Grtz,
~ Nephatiu

Great!!, you update with the last version of bluestacks, but supersu.apk is still version 1.69. Could you please update with SuperSU version 1.75. This is the last one.
Thanks!!

huisterduin said:
Great!!, you update with the last version of bluestacks, but supersu.apk is still version 1.69. Could you please update with SuperSU version 1.75. This is the last one.
Click to expand...
Click to collapse
Why? What's so new about it? This one works and was already unpacked to me. (Lazyness ftw. ;p) Also, it's still the last one available on Google Play Store, since it doesn't want to update, so I'm guessing that it's probably not that much of an update. (Haven't checked though. )
And I don't see why you wouldn't be able to upgrade it yourself... Just install the new SuperSU (replace other in system/app or install in data and don't touch system/app, your choice.
I'll see what I can do next release.
Grtz,
~ Nephatiu

1.75 has actually been available on Google Play Store since November 20, 2013 and these are the changes:
What's New
- Fixed OTA survival 4.3 --> 4.4
- Fixed unresponsive tabs on 2.x devices
- Fixed white flicker when using dark theme
- Fixed issue with language resetting on some firmwares
- Fixed upgrading from CWM SU to SuperSU on 4.3+ without reboot
- Added mgyun root (vroot) uninstall procedure
- Added xxhdpi and xxxhdpi icons (if available)
- Stop touching .has_su_daemon
- Several dozen security hardening commits (mini-audit by Kevin Cernekee)
- Fixed issues with sd-ext based ROMs
- Updated language files
Except from reading the thread, 1.75 still has problems with some devices as some people have lost root trying to upgrade according to the xda thread so better wait for a stable version before replacing it. 1.69 is fine as long as swiping works across the tabs and the request for su prompt comes up as that was what people were complaining about in 1.69.
I'll test to see if 1.75 works by upgrading once I finish downloading since installing rhe apk is the easy part, it's updating the su binary that is always the problem with SuperSU.

Almighty2 said:
1.75 has actually been available on Google Play Store since November 20, 2013 and these are the changes:
Click to expand...
Click to collapse
Ok, strange, I checked yesterday on BlueStacks, right before posting my answer (to make sure). I opened Play Store on it, looked up SuperSU (had to go through the whole 1-click setup again, even ) and it said: Open and Uninstall... No update.
I'll admit I did wanted it not to be, so I had a proper excuse next to me being lazy, but I swear to you, I checked and there wasn't. Not on my BlueStacks, anyway. Haven't checked my phone, since there was no version numbering to be found in their "What's New", so I had no way to check it there without first installing it.
Almighty2 said:
- Fixed OTA survival 4.3 --> 4.4
- Fixed unresponsive tabs on 2.x devices
- Fixed white flicker when using dark theme
- Fixed issue with language resetting on some firmwares
- Fixed upgrading from CWM SU to SuperSU on 4.3+ without reboot
- Added mgyun root (vroot) uninstall procedure
- Added xxhdpi and xxxhdpi icons (if available)
- Stop touching .has_su_daemon
- Several dozen security hardening commits (mini-audit by Kevin Cernekee)
- Fixed issues with sd-ext based ROMs
- Updated language files
Click to expand...
Click to collapse
This was indeed what it said when I checked for the update on BlueStacks,... But it did not give me the Update button, just the Open button, so I expected it to have been the 1.69 release adding those stuff... (I don't really follow SuperSU, so for as far I knew, it could have been and would've easily be explained by the '.su' file and the 'otasurvival' zip in 1.69... ;p)
Almighty2 said:
Except from reading the thread, 1.75 still has problems with some devices as some people have lost root trying to upgrade according to the xda thread so better wait for a stable version before replacing it. 1.69 is fine as long as swiping works across the tabs and the request for su prompt comes up as that was what people were complaining about in 1.69.
Click to expand...
Click to collapse
Apart from the fact it didn't even want to update in my Market,...
Almighty2 said:
I'll test to see if 1.75 works by upgrading once I finish downloading since installing rhe apk is the easy part, it's updating the su binary that is always the problem with SuperSU.
Click to expand...
Click to collapse
You think SuperSU won't be able to update, when it's already the main superuser app? I understand the problems when changing with apps from other users you have no control over, but not over one's own stuff...
Why is this SuperSU app so wanted anyway? It seems to have more bugs than any other... And 99% of the time you're just going to push "Allow" anyway...
Grtz,
~ Nephatiu

The version numbering is always under the description in Google Play Store. I downloaded the Root.fs and initrd.img and just tried to update to SuperSU 1.75 and just as I had suspected, installation of the su binary failed. CWM's Superuser installs but the su binary on that one seems to be dead as it doesn't prompt and one can't even su in terminal mode with all versions released after the CWM Superuser you included in the earlier BS Root.fs.
As for SuperSU, here is the comparison and I think both CWM and SuperSU are good, it's just the original Superuser that sucks...
Superuser, the original by chainsdd, is open source, and has been used the longest. The problem is that it has been outdated and it required work to get it on 4.2
SuperSU is a closed source app from chainfire, a well known developer. Its got a ton of options and its well made. This one was made because of the issues in the original superuser app. Lots of people personally use this one.
Superuser by koush was designed to make a working superuser app, that was open source. It comes built into the settings menu of AOKP and Cyanogenmod.

Almighty2 said:
The version numbering is always under the description in Google Play Store. I downloaded the Root.fs and initrd.img and just tried to update to SuperSU 1.75 and just as I had suspected, installation of the su binary failed. CWM's Superuser installs but the su binary on that one seems to be dead as it doesn't prompt and one can't even su in terminal mode with all versions released after the CWM Superuser you included in the earlier BS Root.fs.
Click to expand...
Click to collapse
Always wondered where that info was... It somehow feels like it should have a more obvious place. And although this seems to be the official place for it, indeed, it's often mentioned in What's New too,... Anyway, I know now, and I can clearly see version 1.75, but then I wonder why I didn't get the Update button in BlueStacks? Because that's the main thing I took as evidence.
Almighty2 said:
As for SuperSU, here is the comparison and I think both CWM and SuperSU are good, it's just the original Superuser that sucks...
Superuser, the original by chainsdd, is open source, and has been used the longest. The problem is that it has been outdated and it required work to get it on 4.2
SuperSU is a closed source app from chainfire, a well known developer. Its got a ton of options and its well made. This one was made because of the issues in the original superuser app. Lots of people personally use this one.
Click to expand...
Click to collapse
Yeah, I was along with everybody else to change and change it every ROM again,... But then CM began to build in theirs (as did AOKP), and it didn't actually bother me, had the same functionality (notification per app settings and such...) and has a much nice clear popup, imho, where as SuperSU has that small white one which still looks Gingerbreadlike. ;p So, again, in my eyes as I did before, I moved on. Some people tend to get stuck with their first change, they never change again, that's why I ask why SuperSU would be better, if it's such a mess even updating it... ;p As I remember CWM's su updated just fine, even on BlueStacks... Dunno if it could handle SuperSu, though, but if it didn't I'd expect it to be more SuperSU's fault than CMWsu's. ;p
Almighty2 said:
Superuser by koush was designed to make a working superuser app, that was open source. It comes built into the settings menu of AOKP and Cyanogenmod.
Click to expand...
Click to collapse
And a good job they did, imho. ;p
Grtz,
~ Nephatiu

My problem is SuperSU is nice but the SU binary isen't istalled. I keep getting no root privilages error. am i doing something wrong?
For me in a sence its not really rooted it just has a superuser app installed which isen't rooted.

CptKlink said:
My problem is SuperSU is nice but the SU binary isen't istalled. I keep getting no root privilages error. am i doing something wrong?
For me in a sence its not really rooted it just has a superuser app installed which isen't rooted.
Click to expand...
Click to collapse
And you are using my Root.fs ánd my initrd.img? Because they work fine here, though, and from recent reply's I think I can confirm more people having it working. :/ Try uninstalling BlueStacks completely, removing everything (like in the beginning of my tutorial for rooting BS in the OP), rebooting, and reinstalling BS with a clean slate. All su binaries and the sudaemon should be pre-installed on it. :/ I forgot to make a symlink to /system/bin this time, but apparently it wasn't needed and the /system/xbin/su should do. This can be done later (with root of course) by going to /system/bin with the android terminal and typing:
Code:
su
ln -s ../xbin/su
Oh, right, and do check if SuperSU doesn't get updated automatically by your Play Store or anything. It should stay v1.69, because it fails at updating it's own su binaries for some reason...
Can anyone else confirm the last release has working root, though, just to be sure? Because they could always have changed something to make rooting harder, disabling the 'just replace Root.fs' possibility with some build in checker. I highly doubt that's the case, though.
Anyway, keep me updated. ;p
Grtz,
~ Nephatiu