Database Info

Google is trying to update my phone

I just got a message saying there is an update available. I told it not to do it. I do not want RC30 because it gets rid of root.
However, the other side of me is tempted to see if telnetd and all the other goodies are still there.

I'm also very tempted to install it to see if it removes root access. I hope someone who doesn't care about root access tests this out and reports back soon, because my curiosity is about to get the better of me.
It won't stop prompting me and I don't think I have the heart to keep saying no.

Look on your phone, and see if there is a file named "update.install" in the /cache folder. Or maybe in the /cache/recovery folder. If so, would you mind grabbing it off your phone and posting it somewhere?

Woobins said:
I'm also very tempted to install it to see if it removes root access. I hope someone who doesn't care about root access tests this out and reports back soon, because my curiosity is about to get the better of me.
It won't stop prompting me and I don't think I have the heart to keep saying no.
Click to expand...
Click to collapse
If you ever do say yes can you tell us what your software version is?

JesusFreke said:
Look on your phone, and see if there is a file named "update.install" in the /cache folder. Or maybe in the /cache/recovery folder. If so, would you mind grabbing it off your phone and posting it somewhere?
Click to expand...
Click to collapse
neoobs said:
If you ever do say yes can you tell us what your software version is?
Click to expand...
Click to collapse
The only file of interest in the /cache directory is named, signed-RC30-from-RC29-fat.1582cace.zip. From this I'm assuming it's going to update my phone to RC30. I've made the file available here in case anyone is curious.

Ah, ok. It looks like that's the same file I just posted a link to then. Thanks

boo
neoobs said:
If you ever do say yes can you tell us what your software version is?
Click to expand...
Click to collapse
It did it.
just as I get home to catch up on the "jailbreak" and start doing it I get an
error while connecting to server, "connection refused"
error while receiving from server null
So I figured I'd check (I neglect my phone when I'm at work, and no, I don't recall accepting the update)
lo and behold:
Build description: kila-user 1.0 TC4-RC30 116143
ota-rel-keys, release-keys​Build ID: TC4-RC30
Build Date: Fri Oct 31 19:00:53 PDT 2008
Build type: user
Phone type: dream
Product brand: tmobile
Build user: android-build
Build host: undroid11.corp.google.com
Linux kernel version: 2.6.25-01843-gfea26b0
[email protected] #6​Mon Oct 6 14:13:36 PDT 2008​Baseband version: 62.33.20.08H_1.22.12.29
RIL Impl version: HTC-RIL 1.0 (Aug 19 2008,21:32:33)
Default keyboard device: trout-keypad-v3

That just proves that RC30 is specificaly out to close the telnet jailbreak method.
No need to apply it to patch/update other parts of the OS since it doesn't have anything else.
MMTest97 said:
error while connecting to server, "connection refused" error while receiving from server null
Click to expand...
Click to collapse
After starting telentd via pTerminal?

quedijo said:
That just proves that RC30 is specificaly out to close the telnet jailbreak method.
No need to apply it to patch/update other parts of the OS since it doesn't have anything else.
After starting telentd via pTerminal?
Click to expand...
Click to collapse
It has more than just that fix. It patches quite a few other packages on the phone... for what purpose? I don't know.

quedijo said:
That just proves that RC30 is specificaly out to close the telnet jailbreak method.
No need to apply it to patch/update other parts of the OS since it doesn't have anything else.
After starting telentd via pTerminal?
Click to expand...
Click to collapse
yes
tried pterminal and terminal emulator
netstat shows the ip
but telnet from pc fails to connect failed on port 23 and the port shown on netstat
I also tried the steps koush put up but still fail
granted I'm no linux/unix pro and I just installed cygwin a couple days after the connect bot app came out; so I may be doing something wrong

Does google check in the new change into the source tree before they push a update?

In addition to jailbreak fix there is a battery fix as well and a few others according to androidcommunity.com.

Well I finally got tired of clicking no and decided to go ahead and perform the update. After it finished, the phone rebooted and instead of booting up, the phone simply displays a '!' icon with a triangle around it and hangs. I'm not taking this as a good sign. I tried removing the battery but that didn't help.
I really hope the update didn't just brick my phone.

Woobins said:
Well I finally got tired of clicking no and decided to go ahead and perform the update. After it finished, the phone rebooted and instead of booting up, the phone simply displays a '!' icon with a triangle around it and hangs. I'm not taking this as a good sign. I tried removing the battery but that didn't help.
I really hope the update didn't just brick my phone.
Click to expand...
Click to collapse
When you're at the screen with the ! and triangle, Try pressing home+back (maybe several times). It should reboot, and hopefully boot back up normally.

JesusFreke said:
When you're at the screen with the ! and triangle, Try pressing home+back (maybe several times). It should reboot, and hopefully boot back up normally.
Click to expand...
Click to collapse
No dice. The phone reboots but still hangs at the error screen. The only thing I can think that might have caused it is that, while playing around, I set a root password and forgot to clear it before the update rebooted the phone. Who knows. I guess I'll call tmobile and see what can be done.
edit: I should mention that pressing alt-w to wipe the phone does not work either. It still returns to the error screen. I'm talking to tmobile tech support now and the original tech said that 'they were informed that a small number of users might experience this problem with the update'. I'm on hold waiting to talk to an android tech now. My advice to everyone who's played around with adding any extra files to /etc to hold off on upgrading for now. I'll report back with the results of my call with the android tech.

Now they're saying they would like to exchange the phone. Problem is the g1 isn't in their replacement program yet.
Aaaand they're out of stock so it's going to be at least 2 weeks.
I wish I'd have just kept hitting no.

Disturbing news, especially as I'm wanting to install a modified rc30. What exactly did you change?

I was playing around with trying to get dropbear to work and in the process I created some files in /etc (passwd, shadow, groups, etc). As well as creating a new regular user, I also added a password to the root account and carelessly forgot to remove it before applying the update. I'm only guessing here but I wouldn't be surprised if the new root password is what did it. The system does not have one by default and I wonder if that caused it to hang, waiting for a password to be entered while booting.
On a brighter note, I persisted and was able to get them to send me out a new phone immediatly. This has the added benefit of possibly fixing the loose-screen/creaking problem that I, like many others, am experiencing with the phone.
I'm wondering if I should try manually applying the update from the SD card while I wait for the new phone to see if that solves the problem. I probably should have tried that before calling. I'm hesitant to do that now, however, since if it does fix it, I'm not sure how tmobile would react to me returning a perfectly working phone.

Woobins said:
No dice. The phone reboots but still hangs at the error screen. The only thing I can think that might have caused it is that, while playing around, I set a root password and forgot to clear it before the update rebooted the phone. Who knows.
Click to expand...
Click to collapse
I don't get it. The update should restore whole /system folder, isn't it? /etc is actually a symlink to /system/etc, so, it should be restored too and passwd file successively removed.
Otherwise, I don't see any problem to keep the root access! Since /system is mounted without nosiud (any changes in RC30?), just keep a copy of shell with chmod 4777 somewhere there... where it wouldn't be removed by update, as it keeps passwd, and that's it.
Please, tell me where am I wrong, cause I definitely should be wrong somewhere.
PS: BTW, what was the progress with dropbear? I actually tried to make it work too, creating passwd etc, but no success...

Dimath said:
I don't get it. The update should restore whole /system folder, isn't it? /etc is actually a symlink to /system/etc, so, it should be restored too and passwd file successively removed.
Otherwise, I don't see any problem to keep the root access! Since /system is mounted without nosiud (any changes in RC30?), just keep a copy of shell with chmod 4777 somewhere there... where it wouldn't be removed by update, as it keeps passwd, and that's it.
Please, tell me where am I wrong, cause I definitely should be wrong somewhere.
PS: BTW, what was the progress with dropbear? I actually tried to make it work too, creating passwd etc, but no success...
Click to expand...
Click to collapse
Unlike the RC29 update, the RC30 update doesn't actually do a complete wipe and restore of the /system folder. It patches a number of files (which will fail if any of them have been modified), and does a recursive chmod on the entire /system directory to clear any suid bits.

New phone (RC29) - no console exploit (telnetd)

Okay, I had ordered another phone from ebay. The guy had just received it and it was new and unused. It has RC28 on it.
fingerprint= kila-user 1.0 TC4-RC28 114235 ota-rel-keys,release-keys
When I launch /system/bin/telnetd from terminal console I am not getting root. I do not see a process running when I run ps afterwards. Also, I tried typing reboot from the contact, and it is not recycling the phone.
Any chance they have updated the init.rc to close the console bug on an older RC for phones just shipping out from tmobile this past week?
I plan to update to the stock RC29 which I manually updated to on my other phone. I'd really like root before I update to the new RC30 modded, so I can back up my files before overwriting them. [Though, last time I upgraded Google did OTAs right away.]
** Anybody want me to explore the phone for any differences to the standard RC28 to see if the cause for the exploit not working?
-oldsk00lz

Just go ahead and install the official RC29 and you should be able to get root access

Are you sure it's not working? IIRC if you don't connect to telnetd fairly fast, it stops running for some reason. I know that I've had to run it a couple times before I could connect.
As for the root console bug, I've also heard that it closes after some time of the phone being on. Did you try it after a fresh reboot?
Updating to RC28 or RC29, the ones that we mirrored, should activate the console bug again, if they are fixing it.

Yeh, it was not working (telnetd/console exploit) on the RC28 I had. I tried hitting enter to clear any previous commands, tried rebooting, tried back to back calls with telnet right afterwards, telneting locally and from several boxes. Was weird.... Much different than another G1 I had. That's why I was surprised.
Only thing I could think of (besides a tweaked RC28) was that my router could have been acting up.
Anyhow, I moved forward with updating to RC29, getting root, updating to modded RC30, and all is good. Just wanted to throw this out there in case any other recent buyers encountered a similar issue.
SIDENOTE: JesusFreak lived up to his name. I was slightly "freaked" out after the recent upgrade. I went to the System settings and looked to be the standard RC30 fingerprint!!! versus the modded xda one. Thought I may have installed the stock update. :O But, everything else is as expected, root, root, and more root. I must have missed a message if he reverted back to the standard fingerprint.
-oldsk00lz

oldsk00lz said:
SIDENOTE: JesusFreak lived up to his name. I was slightly "freaked" out after the recent upgrade. I went to the System settings and looked to be the standard RC30 fingerprint!!! versus the modded xda one. Thought I may have installed the stock update. :O But, everything else is as expected, root, root, and more root. I must have missed a message if he reverted back to the standard fingerprint.
-oldsk00lz
Click to expand...
Click to collapse
Indeed, I thought the same thing, but it is much, much, much better this way. If JesusFreke left the fingerprint to be the same as the old one, Google would be able to target OTA updates specifically for rooted G1s. This way, if they release an update signed with the test keys, they'd have to have millions of non rooted G1s freak out because they couldn't update.

Gary13579 said:
Indeed, I thought the same thing, but it is much, much, much better this way. If JesusFreke left the fingerprint to be the same as the old one, Google would be able to target OTA updates specifically for rooted G1s. This way, if they release an update signed with the test keys, they'd have to have millions of non rooted G1s freak out because they couldn't update.
Click to expand...
Click to collapse
Not quite...
First, I don't think Google cares for those of us having root with RC30 moded recovery and keys. They really only care about patching the "average consumers" phone. They have to do it globaly (I mean in the distribution sense) not to get in trouble, or a BIG bug wich is what was patched.
Second, they only have to do the following if they want to put "us" back to stock (if we don't check the update of course AND don't pay attention and apply the update [BIG IF]):
Script the rewrite of recovery.img from their package (before rebooting in the background) to our phones and apply the update.... ... ... that's it.
This will get a bit of the "unaware" people who have root with RC30. But for the more savey of us, no.

quedijo said:
Script the rewrite of recovery.img from their package (before rebooting in the background) to our phones and apply the update.... ... ... that's it.
This will get a bit of the "unaware" people who have root with RC30. But for the more savey of us, no.
Click to expand...
Click to collapse
And what good would secretly rewriting recovery.img do? Once JF replaces the recovery.img with the modified one, it doesn't matter how many times they write it to flash, it's still modified.
They don't need to use the update package to take away your root. With modified RC30, any dalvik program that knows and wants to can write directly into /system. If they wanted to get draconian about it, they could push code down from Market to reflash whatever they want in /system.

You said "With modified RC30, any dalvik program that knows and wants to can write directly into /system".
Aren't these apps sandboxed? If they do have access to /system, I assume they would only have access if they ran su, assuming you didn't rename it, and was able to remount system as read/write.
Or am I missing something like a different exploit? root on 'my' phone is great for me, but not good for others.
-oldsk00lz

oldsk00lz said:
You said "With modified RC30, any dalvik program that knows and wants to can write directly into /system".
Aren't these apps sandboxed? If they do have access to /system, I assume they would only have access if they ran su, assuming you didn't rename it, and was able to remount system as read/write.
Or am I missing something like a different exploit? root on 'my' phone is great for me, but not good for others.
-oldsk00lz
Click to expand...
Click to collapse
Yeah, by invoking su. Deleting or renaming it is probably the safest bet for now. I doubt any Android devs are actively looking for phones to brick but better safe than sorry.

a new workaround for our very insecure rooted RC30
I just read a post here about a better fix for the issue.
This very smart cat, added a password routine to SU and judging by my read of the post it seems to be well implemented, you do have to type some commands and you could pooch your g1 but it seems better than runnin just about as wide open as goog had us...
Without a decent browser getting the link is a pita, if somebody can't find it ill link it when I'm at the desktop
Bhang
*EDIT*
I found the link its just a pain in the arse while typing a message, to all the helpful folks who will want to tell me how to do it, I know how I just think it could be easier
http://forum.xda-developers.com/showthread.php?t=448775

RC33? Firmware 1.1?

http://forums.t-mobile.com/tmbl/board/message?board.id=87&thread.id=30842
He took a screen shot of it here: http://m.flickr.com/#/photos/soreco/3249188324/
No word on what the changes are yet.

LOL, i dont wanna believe it then finally find out it's just a sick joke but the screenshot looks real though

wpbcubsfan said:
http://forums.t-mobile.com/tmbl/board/message?board.id=87&thread.id=30842
He took a screen shot of it here: http://m.flickr.com/#/photos/soreco/3249188324/
No word on what the changes are yet.
Click to expand...
Click to collapse
Somebody wake up JesusFreake!! Where's Koush?
Is it possible to pull an OTA and then take it off the device with ADB without installing it?

hmmm.
I'm gonna have to go with it being a hoax... I believe that Google even confirmed that the new cupcake branch upate would be called RC31.

Looks legit to me. Seems to be a tmobile version of adp 1.1.

dwang said:
Looks legit to me. Seems to be a tmobile version of adp 1.1.
Click to expand...
Click to collapse
I agree with the legitimate part. The kernel, baseband, and build ID numbers all look rationally composed/upgraydded. As long as they don't "fix" the SPL or lock out test keys, I'm ok with a little bump for now.

I'm still waiting to see if this is real or not but I did notice something on the google android issues site that made me think we were getting close. Usually the last thing you test before release are upgrade scenarios.
[imported from Google's internal bug database]
STEPS TO REPRODUCE:
1. Dream device was running a pre-cupcake userdebug. within the last week
or so I had previously downloaded a set of files from browser, a couple
market apps, etc
2. Flashed cupcake userdebug, without wiping data
EXPECTED RESULTS:
On device boot-up, none of the previous notifications would be displayed
OBSERVED RESULTS:
The home screen displayed 13 or so "download complete" notifications that
were previously dismissed.
I then selected 'Clear Notifications'
Result -> Notifications cleared, then approximately 5 seconds later
reappeared, then immediately disappeared again.
Click to expand...
Click to collapse
http://code.google.com/p/android/is...ID Type Version Security Status Owner Summary
Also I'm not sure if the flashing they are referring to is the way you would test an OTA update.
This might be a false alarm.... but I hope not

The guy in the original thread said there's google voice searching.

Just got an email about:
To ensure a great experiance with the T-mobile G1 with Google, customers with these devices will receive an Over the Air (OTA) update to their devices between February 5 and February 15. The OTA will include new system enhancements such as the ability to save pictures or files by long-pressing an item, check for system updates, and use the Google Voice Search feature. The OTA will also fix a number of known issues. New G1 activations will receive the OTA up to three days after service has been activated.

Just IM'ed the lord of the Dream.... we'll see what he says?

And still no cupcake.

coolbho3000 said:
And still no cupcake.
Click to expand...
Click to collapse
Wehhh wehhh...
Go play on the market where people care what you have to say.

rynosaur said:
Somebody wake up JesusFreake!! Where's Koush?
Is it possible to pull an OTA and then take it off the device with ADB without installing it?
Click to expand...
Click to collapse
Yes. It will be saved in /cache. All I need is the name of the zip file, and I can download it directly from google.
Everyone with RC30 check your logcat log for any sign of a zip file
something like
logcat -d V | grep zip

I got the same email that speoples20 got.
RC33 is an official update from T-Mobile to start being pushed out to the general public feb 5th to feb 15th and then for all new activations within 3 days.
speoples20 did you notice that The Forecast was dated February 2, 2008? Looks like T-Mobile came up with a time warp while making the OTA.

Just to clarify....
EVERYONE ON RC30 (JF OR NOT)
The reason for this is once JF has the file name, he will be able to download it.
NOT THE SD CARD CACHE!!!
Open Terminal Emulator
SU--Enter
Type in CD /cache
Type in LS
Now if that comes up empty, type THIS in and tell us if you see a log entry containing the file name:
logcat -d V | grep zip (enter)

The alarm has been rung!

http://code.google.com/android/migrating/m5-0.9/changes/android.content.Intent.html
can FOTA_UPDATE_ACTION or any of the other FOTA_* functions help out?

Also, you could try to force an update. Download and install anycut (if you haven't already ), and then make a shortcut to the "Device Info" activity. Open it up, go down to the bottom and click "check for update". If it starts downloading the file, I think it should say the name of the file on that same screen. If not, open up a terminal emulator and look in /cache, or try the logcat command:
logcat -d V | grep zip

CHECKIN_SUCCESS but no pending upgrades or downloads
I'm guessing that will be the case until Feb 5th or later for everyone else too.

ok word has spread fast about this issue at he AC and some people are asking from over here are asking JF users to still look for the zip file in the cache. but here is my question, will it even help? I ask because I am not sure about this:
All of us that have root are not supposed to be updated automatically. Now does that mean that the ota is downloaded by the phone and just never auto installed or does it mean that the file can never be downloaded ota?

New to G1

Good afternoon to the G1 community. I just purchased my G1 yesterday through Tmobile and I have a couple question.
I just came from using a wing so I am pretty savy with wmo rom flashing and whatnot, but android is completely new to me. Now, of course i want to get the most out of my device. I must say, out of the box it is by far the best device that I have used. Even so, i know that there is some stuff that i am missing.
I have done some reading here in the forum, and i do know how to search, but im not clear on a couple things. For starters, I have been reading about Rooting my device. Now to be totally honest with you, i've read through the Rooting Thread but only walked away with I would love to have autorotate for my screen! I mean, truely what are the benefits to rooting the phone? Will i loose access to the "market" or loose any other functionality of the phone as it is now? Future updates?
In a perfect world i'd love to have the auto rotate feature.... the ability to change the way the program list slides up to maybe sliding panel, and an onscreen keyboard (such as chompsms) when i select a line to type in (whether im in the browser or anyother program.)
I Love the phone as it is.. so all in all, what functionality would i gain, and what would i loose? besides warranty of course
I apologize, i realized i may have put this in the wrong section!

1. Rooting you phone allows you to basically use it to the best of its capabilities. For example, you can change themes, boot image, auto rotate, multitouch, etc. You won't lose the market or any other functions after you root the phone. (To my knowledge, I see paid apps and such just fine on my phone.) You will continue to see future OTA updates, but if you download them, you will lose root access for your phone.
2. The "Cupcake" OTA release is planned for April (As has been discussed on the forums, may be true, may be false. TMobile is claiming its false, but Google controls the updates) If we ever recieve this update, then we will be able to get things such as an onscreen keyboard.
3. I'm not sure about changing the order of the way the apps are presented on the slide-up menu, but there are apps like ahome or dxtop that have alternate home styles, such as the "Iphone" style horizontal scrolling or multiple menu tabs.

Thanks, I do appreciate your prompt response!

if you want the best out of your phone root it.. but thats completely up to you.. when you root you'll be able to get the latest builds from JF anyway soo you'll never be out on whats new.. if anything you'll be a couple steps ahead of regular g1 users at all times

Just to verify.... The market is still available for apps after rooting.. Now I will loose root if I download from the market or just the "OTA" updates for the phone?
Also, i was going through the instructions for the process and got to the point where you upgrade to the latest build. So, i assume RC33 is US Tmo vs RC8 being for UK. What is ADP1.1? So is my choice between ADP1.1 and RC33?

you shouldn't even recieve an OTA update notification if you follow directions, so you don't have to worry about that, and many apps on the market are actually FOR root users and only root users so you will not lose market obviously. the greatest thing about getting root is that you can basically make your phone do anything you want(so long as you are comfortable with linux commands and aren't afraid to temporarily "brick" you phone) but even if you kust want autorotate you will need to root the phone and you will need to grab a JF update. there is an app that someone has written, almost completely idiot proof rooting, and i am trying to help it to be COMPLETELY idiot proof, if you want to try it out search app that roots your phone and it should pop up

Ok, so I have decided to go ahead and play with this and see what there is to offer.
I have successfully downgraded to the rc29 firmware and verified it in my phone. Now I have also done these instructions to get root;
Rooting your RC29 or lower phone:
On RC29 phones and lower, anything you type into your keyboard is also being run in a hidden console with root permissions. More information regarding that at the bottom of this post. But, to get root access, do the following:
Instructions:
Download recovery.img and copy it to your SD card (see the previous instructions on how to copy from your computer to your Phone's SD card).
Download the Hard SPL and copy the zip file to the SD card.
All files must be on the root of your SD card.
Restart your phone. Wait for your phone to start up fully and show the home screen.
After your phone starts up, hit the enter key twice, type "telnetd" and press enter. (Yes, it will start up a contact search, don't worry. Just type it.)
Download an Android "Telnet" application from the Market and connect to localhost.
If you connect successfully, you will have a root prompt "#".
Type the following into Telnet (these commands will give you root access easier in the future):
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
cd sdcard
flash_image recovery recovery.img
cat recovery.img > /system/recovery.img
Now of course i dont know if it was successfull cause it doesnt tell you. Now here is my problem. I am trying to upgrade the rc33 now but with NO LUCK! Now the instructions say to download the file, rename to update.zip and go into recover mode and run update. However it keeps giving me the error "Can't open /sdcard/update.zip (bad). I have downloaded two copies and this happens with both and the radio version.
What am i doing wrong? I have tried to rename the file on both the phone and the computer, with the extension .zip and without it but with no luck. I have the file directly on the root of the sd card. Do I need any other files on the sd card? or just the zip file?
I have read and read, but I have not found a clear explanations.

I'm not on a G1 (I'm on a Google dev phone that came rooted out of the box), and thus haven't gone through that process myself, but I seem to remember reading something about having to go through RC30/JFv1.3x and THEN to RC33/JFv1.4x. Not RC29 -> RC33/JFv1.4x directly.
I could very well be wrong though.

Ok, well I did get it to install.. still working on it...
Definitely wierd. I'll update when i finish!
I successfully went from rc29 to rc33 v 1.41 but realized that the newest is 1.42 so thats loading now.
Its odd, it seems that my problem was when i was in recovery mode, I would alt L to bring up the menu and alt s to update from sdcard. It didnt work for nearly 10 times.. then all the sudden instead up alt L to bring up the menu, i just did alt S and it booted. I didnt realize that linux was that sensitive! Other than that, i'm about to play with the new firmware.
So there is no way to get an onscreen keyboard like chompsms? I kinda found that hard to believe.

while it is SUGGESTED that you go from 29 to 30 to 33(what ever happened to 31 and 32?) it is not necessary, i am gonna assume you are on windows and you may be naming it update.zip.zip because extensions are hidden. try it after just naming it update, and also make sure that you unmount the phone correctly after you put the file on there, a lot of times it is still writing data when you yank it out, and that will cause the (bad) error. hope this helps. if you get a file not found error after naming it update then just put the .zip extension back on the file and make sure you unmount properly

tubaking182 said:
i am gonna assume you are on windows and you may be naming it update.zip.zip because extensions are hidden.
Click to expand...
Click to collapse
This, and maybe you've downloaded the 'build environment' package.
At my first attempt I got the 'bad' message, too. I didn't know which one to pick up so my first try has been 'ADP1 build environment'. Later with 'ADP1' (not the build environment one) no problem. Now I'm going with the UK because I wanted the UI in german and because some market apps didn't download with ADP.

[Q] Supreme Sense Question

Aloha-
I recently purchased the Evo Shift 4g and i have perm rooted and have been able to flash to the supreme sense rom and back to the stock rom successfully. Mahalo for all the information that i was able to gather here to help a newbie like myself!
I had my shift programmed so that it will work with a local carrier here in Hawaii, MobiPCS. I am currently trying out the supreme sense rom now and so far so good. I have a few questions and hopefully, i didn't miss a post that has my answers.
1. I am using one of the cool lockscreens (Weather). How, if possible can i change the actual text, specifically "Sprint" that appears above the clock?
2. I can no longer gain access to EPST. ##3282# no longer works. Is there another code? I already have my MSL#. I am guessing that my first question must get the "Sprint" from data in the phone?
3. Voice Mail notification is the only thing that does not work. It did not function with the stock rom either. The only way i can get a notification is to run an app VoiceMail Notifier. Do i have any another options? I am assuming the sprint voice mail has no bearing on my voice mail service from Mobi. I don't understand if the flag to notify the phone is being changed to inform of a voice mail, why the phone natively does not send a notification. (Yes, the voice mail notifications is All turned on).
Not too sure if its okay to post multiple question in a single post, if not, i apologize!
Mahalo (thank you) for taking the time to help me!

Well, I can steer you in the right direction for question #1. Check out this post by one_love_420. I can't help you on #2 and #3 though. Sorry.

for number 3 would google voice help in anyway to help get notified when you get a voicemail?

To solve your EPST problem download this APK HERE
then it should work
BTW:Credit to Strapped365 for the link (which COULD be found in his second post on the Supreme Sense thread. .)
and if i knew who originally posted the EPST.apk a LONG time ago id five them credit here

stslivealoha said:
Aloha-
I recently purchased the Evo Shift 4g and i have perm rooted and have been able to flash to the supreme sense rom and back to the stock rom successfully. Mahalo for all the information that i was able to gather here to help a newbie like myself!
I had my shift programmed so that it will work with a local carrier here in Hawaii, MobiPCS. I am currently trying out the supreme sense rom now and so far so good. I have a few questions and hopefully, i didn't miss a post that has my answers.
1. I am using one of the cool lockscreens (Weather). How, if possible can i change the actual text, specifically "Sprint" that appears above the clock?
2. I can no longer gain access to EPST. ##3282# no longer works. Is there another code? I already have my MSL#. I am guessing that my first question must get the "Sprint" from data in the phone?
3. Voice Mail notification is the only thing that does not work. It did not function with the stock rom either. The only way i can get a notification is to run an app VoiceMail Notifier. Do i have any another options? I am assuming the sprint voice mail has no bearing on my voice mail service from Mobi. I don't understand if the flag to notify the phone is being changed to inform of a voice mail, why the phone natively does not send a notification. (Yes, the voice mail notifications is All turned on).
Not too sure if its okay to post multiple question in a single post, if not, i apologize!
Mahalo (thank you) for taking the time to help me!
Click to expand...
Click to collapse
Well bubbaearl steered you in the right direction for the first answer. Later on in that same thread there is a flashable posted up.
!!! MAKE SURE BEFORE YOU FLASH ANY MODS TO WIPE CACHE AND DALVIK BEFORE YOU FLASH !!!
HERE is the exact post.
As for the ESPT issue THIS should take care of it.
Your Voice mail should be working regardless of carrier. I would contact your current carrier, and ask them to help resolve the issue. They shuld be able to resolve the issue with you on the phone.

Mahalo to prboy1969, notsointeresting, bubbaearl, & youngcorruptionV2.0 for your help!
I'll ..attemp (lol) to do as suggested by the links provided to deal with question1 and 2.
As for the voicemail issue, the actual voicemail does work fine. its just the notification (visual, sound or vibrate) to let me know that there is a voicemail to be retrieved does not work (both the stock and supreme sense rom) As i mentioned, i am currently using Voicemail Notifier to resolve the issue, but i thought the actual phone would be able to notify me without a 3rd party app.
Unfortunately, google voice does not provide a number here out in the Pacific Ocean! but thanks for the idea...
I'll report back if i'm successful regarding the other stuff.
Again, mahalo for taking the time to help!!!

Did you follow THIS guide before flashing your Rom.

prboy1969-
Yes, i did exactly (3x's) what the guide mentioned except for the skipping of the setup...I couldn't figure out how to get out of the setup so i just cancelled/skipped to the end (hope that was okay).
I also flashed back to my stock rom (to get the magic smoke live wallpaper apk, and to back up with Titanium Backup some apps that i missed the first time), then i followed the instructions again. Both times, the voicemail notification did not work. I had a difficult time installing the Magicsmoke live wallpaper but with some help, i was able to get it going. btw, supreme sense rom so far is pretty cool.

Got the "Sprint" removed and replaced with my text! Thanks for the info and the link. very cool...
As fpr #2, the epst, the update(thank you for the zip) did not address the issue. although i guess i don't really need it since i thought i had to change the info here to resolve my issue #1. Just for my info though, why does it not work anymore? wouldn't you folks want to be able to change settings from there? btw, i did wipe the davlik and cache before installing from sd/zip. (installed from boot recovery)
As this is my FIRST android phone (always had a windows phone) As i am getting more familiar with this rom, installing the apps, etc. any other suggestions?
i did partition my sd 8GB with a 1gb ext3 as i flashed with a2sd. However, i didn't see the app in the drawer, and i wasn't sure if that's right? than i noticed any app shortcut (not sure what you call it, one of the home screens) that i installed on the SD, after reboot, the shortcut had a generic icon, rather than the app icon. (just noticed this). when i move the app back to the phone, then after reboot the icon appear fine!
I know i read many posts stating to follow the guide before flashing, and i did!!
Again, mahalo for your help!

stslivealoha said:
Got the "Sprint" removed and replaced with my text! Thanks for the info and the link. very cool...
As fpr #2, the epst, the update(thank you for the zip) did not address the issue. although i guess i don't really need it since i thought i had to change the info here to resolve my issue #1. Just for my info though, why does it not work anymore? wouldn't you folks want to be able to change settings from there? btw, i did wipe the davlik and cache before installing from sd/zip. (installed from boot recovery)
As this is my FIRST android phone (always had a windows phone) As i am getting more familiar with this rom, installing the apps, etc. any other suggestions?
i did partition my sd 8GB with a 1gb ext3 as i flashed with a2sd. However, i didn't see the app in the drawer, and i wasn't sure if that's right? than i noticed any app shortcut (not sure what you call it, one of the home screens) that i installed on the SD, after reboot, the shortcut had a generic icon, rather than the app icon. (just noticed this). when i move the app back to the phone, then after reboot the icon appear fine!
I know i read many posts stating to follow the guide before flashing, and i did!!
Again, mahalo for your help!
Click to expand...
Click to collapse
To fix EPST you're going to have to run RUU. Sorry to be the bearer of bad news.
Also I highly recommend using FAT32 for partitioning an sdcard or just letting Clockwork Recovery do its thing.

stslivealoha said:
Got the "Sprint" removed and replaced with my text! Thanks for the info and the link. very cool...
As fpr #2, the epst, the update(thank you for the zip) did not address the issue. although i guess i don't really need it since i thought i had to change the info here to resolve my issue #1. Just for my info though, why does it not work anymore? wouldn't you folks want to be able to change settings from there? btw, i did wipe the davlik and cache before installing from sd/zip. (installed from boot recovery)
As this is my FIRST android phone (always had a windows phone) As i am getting more familiar with this rom, installing the apps, etc. any other suggestions?
i did partition my sd 8GB with a 1gb ext3 as i flashed with a2sd. However, i didn't see the app in the drawer, and i wasn't sure if that's right? than i noticed any app shortcut (not sure what you call it, one of the home screens) that i installed on the SD, after reboot, the shortcut had a generic icon, rather than the app icon. (just noticed this). when i move the app back to the phone, then after reboot the icon appear fine!
I know i read many posts stating to follow the guide before flashing, and i did!!
Again, mahalo for your help!
Click to expand...
Click to collapse
You can also try THIS for the ESPT. For whatever reason sometimes you have to try a few different ESPT apk's. Also one other thing to consider is, since you flashed to a different carrier ESPT may not be available. Not sure who MobiPCS is asssociated with. But either way, no you don't have to RUU to get ESPT working again . Unless of course you want to start the whole process over.
When you use A2SD you do not have to move the app manually to the SD Card. I take it that's what you did before moving them back to the phone? A2SD takes care of that automatically. Although it appears the app is on the phone it is not. Also you can post up on the Supreme Sense thread with all your questions. We'd be glad to have you post up .

prboy1969 said:
You can also try THIS for the ESPT. For whatever reason sometimes you have to try a few different ESPT apk's. Also one other thing to consider is, since you flashed to a different carrier ESPT may not be available. Not sure who MobiPCS is asssociated with. But either way, no you don't have to RUU to get ESPT working again . Unless of course you want to start the whole process over.
When you use A2SD you do not have to move the app manually to the SD Card. I take it that's what you did before moving them back to the phone? A2SD takes care of that automatically. Although it appears the app is on the phone it is not. Also you can post up on the Supreme Sense thread with all your questions. We'd be glad to have you post up .
Click to expand...
Click to collapse
I've had someone had EPST corrupted and the only way to get it back was RUU. Nandroid first of course, run RUU then restore Supreme and it works fine.

Yes, i did format the remaining partition fat32, also set to primary.
As to the ruu, i hope not! However thing to note is after flashing to my the carrier i use MobiPCS, I had already perm rooted my shift and getting into the epst to change things that needed to be changed was done (I purchased the phone used off ebay). So, i'm pretty sure flashing to my new carrier had no impact on being able to use epst. However, upon flashing to supreme, no access.
I will try the other link (thanks prb1969) and see if that resolves the issue. Jus curious but for all the others that have flashed to supreme rom, they also have the same issue regarding EPST? Just to make sure the access code is ##3282#, then call...right?
The a2sd..i am a bit confused. (Supreme rom with a2sd flashed) if i understand the reply, a2sd moves the apps to the sd (i assume the ext3 partition) yet it still appears to be on phone? is that correct? Also, a2sd will not in the app drawer at all? (i couldn't find it)
So, i guess what i did, screwed things up? I installed a2sd, it then reported many apps on the phone, of which i did start to move to SD. (thats when i noticed my shortcut (app) icon issue.
Again, mahalo for your help Vicodan and prb1969. I originally wanted to post my questions...pleas for assistance on the supreme sense thread, but since i am a newbie...I couldn't. From what i understand, not until i reach a certain level?
I'd be happy, well, sort of (realizing i would have go through the setup process again) to start over (revert back to stock rom or reflash the supreme rom) if you all recommend that....
Anyways, i'll try that new link for the EPST. will report back..
Mahalo

thanks for the new link for EPST prb1969, however no change..i did wipe davlik and the cache before updating. No errors encountered during the update.
in the dialer, i input ##3282 but when i add the last #, the numbers disappear.
I'll wait to hear back but i thought i might try to restore back to stock rom and see if ##3282# still works (it did the last time but before i flashed supreme)

If you have a Nand of the stock Rom, Nand back and check to see if ESPT works. As for the posts I believe you need at least 10, before you can post on other threads.
VICODAN said:
I've had someone had EPST corrupted and the only way to get it back was RUU. Nandroid first of course, run RUU then restore Supreme and it works fine.
Click to expand...
Click to collapse
Hey VICODAN just for the record if you RUU back to stock. You can't just restore a Rom afterward . RUU equals no Root .

nand back to stock rom. Yes, EPST worked. copied epst.apk to sd. flashed back to supreme a2sd rom (clean).
will apply lockscreen banner update along with the magic smoke wallpaper..
Can i copy the epst.apk that i got from the stock rom and paste into the /system/app folder?
or do i need to something else first?
and btw, after flashing back to supreme a2sd rom, epst does not work

Don't know if this is the same EPST.apk you've used, this works fine on my phone running SSV8 A2SD with dodge kernel ext4. Hope it works on yours...
http://db.tt/nZpE2E2S
Sent from my "CRACKED" Speedy Evo engine... via Tapatalk!

Ok I'm back lol ha-ha with a fresh build station, man i don't know why you can't use epst, because all of us SS users can use it fine I'm not to sure about the metro users or not, and this has me stumped because SS is basically just a modded out stock ROM so i dunno but we will all try to do what we can to get you up and running as you see here
Shifted to the extreme, cause I rawk Supreme

Mahalo for the update file rhodiggah. I'll report back to see if it works.
also, can i use the epst.apk file from the stock rom, rename the existing one in the SS Rom, and paste into the /system/app folder?
do i also need the odex file?
btw i was able to get the magic smoke live wallpaper to work by copying the apk file from the stock rom, copying it into the ss rom and correcting the persmissions, and it worked. I didn't copy over the odex file. while it works, i read about what the odex file does, and now i'm wondering if i need this file also. the wallpaper seems to work fine.
Also, an update on a2sd, yes, it does move installed files to the SD card ext3 partition! lol. and i didn't install a newer version. (Since i started over again flashing SS) which begs to ask, what happens when there is an update to a2sd? I"m guessing there is a way to do it?
Again, can't say it enough about how helpful you everyone has been in helping a newbie out!!!
Mahalo...

prboy1969 said:
If you have a Nand of the stock Rom, Nand back and check to see if ESPT works. As for the posts I believe you need at least 10, before you can post on other threads.
Hey VICODAN just for the record if you RUU back to stock. You can't just restore a Rom afterward . RUU equals no Root .
Click to expand...
Click to collapse
RUU 2.2, reroot, reflash cwm, restore supreme sense. done.