Root Still running 2.2.1...Can/should I update?

[bigdanmeys13]

I am still running Froyo on my Commando. Rooted, de-bloated (deleted, not frozen), V-6 Supercharged, and I installed GNM's recovery. I love my phone the way it is as of now, but I do like the GB status bar better. My only complaint is that GPS seems somewhat slow. Has anyone noticed a significant improvement in that department with the GB updates? And am I even able to update having deleted instead of frozen bloat?

 

[rjglenn]

You probably will not be able to take the update even if you restore all the apps. Nobody else has been able to, so it's pretty safe to make the above statement. You can call in and exercise your warranty if you want. Others, including myself have been successful in doing so. Do not mention anything about superuser, superoneclick, titanium, etc. Good answers to probing questions are "I don't know", "not that I know of", and "what does that mean?". In other words, play dumb and just say it won't update for some reason.

 

[Rafael]

I wish I were still running 2.2.1. It is faster and less glitchy.

You might look for a replacement status bar app if you are not happy with the original. I prefer the one you have......the new one uses smaller font size....harder to read at-a-glance.

I have not had GPS problems and notice no difference in it between 2.2.1 and 2.3.3.

 

[Spike G]

Rafael, have you tried changing your system fonts? I use font changer (root) and i made my font a much more bold one so it was easier to read the clock even thoguh i'm running 2.2.1

 

[Rafael]

I had not thought of that. May try it.
The sluggishness of 2.3.3 is the most bothersome change.

 

[paxchristos]

@BigDanMeys -- Could you do me an enormous favor? Since you are rooted and on 2.2.1, this should be pretty easy.

If you could open up terminal emulator (if you have it, if you don't there are free ones out there) and type in
1) su
2) cat /proc/mtd
look at the list, one of them should say /boot.
3) cat /dev/mtd/mtd# [# represents the number that /boot has in the list]

If you could find a way to email that to me (nielson.peter@gmail.com) , it would be outstanding (don't worry, all it contains is the boot sector for android, no personal data)

Thank you,
Peter

 

[Spike G]

@paxchristos i typed those commands in and it sent me into a scrolling loop of nonsense. boot was mtd1 in the list

 

[paxchristos]

Sorry about that it should be done via adb, not terminal emulator. (my bad) Commands are still the same.

 

[Spike G]

my adb has never actually worked for commands, idk how i got it to root but i'm reinstalling sdk right now, if that fails i'll boot to linux and do it there



EDIT AGAIN: i'm ******ed, the screen was locked so i didnt notice shell requesting superuser. DOH

 

[Spike G]

ok so same results in ADB ad terminal emulator... ill try something else real quick

 

[Spike G]

just tried to manually pull the files by

 adb -s [my serial number] pull /dev /C:/users/spike/desktop

and it failed

apparently superuser and su are completly different and adb cant run as root with

adb root

becuase that root is built into the boot file and is different from the su privileges in adb shell

 

[paxchristos]

just tried to manually pull the files by

 adb -s [my serial number] pull /dev /C:/users/spike/desktop

and it failed

apparently superuser and su are completly different and adb cant run as root with

adb root

becuase that root is built into the boot file and is different from the su privileges in adb shell

Duh, my bad... can you try pushing this file (zergRush, it's an adb exploit)
http://db.tt/KQQ5NCVl

to run it you'll need to do this

 adb shell
mkdir /data/local/tmp
exit
adb push "C:\path\to\zergRush" /data/local/tmp
adb shell
chmod 755 /data/local/tmp/zergRush
/data/local/tmp/zergRush
adb remount
adb shell 
cat /dev/mtd/mtd1 > /mnt/sdcard/boot.img
exit

Then you can either copy it from your sd card the old fashioned way, or you can do adb pull /mnt/sdcard/boot.img "C:\where\ever\you\want\it"

 

[Spike G]

i'm getting an error on the last step copying the mtd1 to the sdcard "/mnt/sdcard/boot.img: is a readonly file system"

 

[Spike G]

I used the same method i tried as before with an adb pull after the exploit, here you go

2.2.1 mtd1 Boot file

 

[paxchristos]

I used the same method i tried as before with an adb pull after the exploit, here you go

2.2.1 mtd1 Boot file

Thank you Good Sir,

When i get around to doing the kernels for this phone, i now have a ramdisk for 2.2.1, so i can support that too

 

[Spike G]

thanks man, i appreciate it, anything else you need, let me know so i'm not SOL when someone releases new stuff and only supports 2.3.3

p.s. are you changing the ro.secure to equal 0 in that

 

[paxchristos]

thanks man, i appreciate it, anything else you need, let me know so i'm not SOL when someone releases new stuff and only supports 2.3.3

p.s. are you changing the ro.secure to equal 0 in that

Yes, amongst other things.

I'm (hopefully) going to find someone on the Evo Shift 4g forums on XDA (same chipset/similar-ish radio) and see if i can't get some help from them in setting up custom kernels/open it up for custom roms... My only problem with 2.2 is that most roms are setup for 2.3.3+ so that's gonna be the base (and baseband is gonna be an issue until i can figure out how to pull that...)

 

[Spike G]

well baseband was the only thing that kept me from updating to 2.3.3, i've had it installed and working but no service due to the 2.2.1 baseband. i wouldnt mind 2.3.3 if thats what i have to do first to get roms/kernels