Guest thisweb Posted May 26, 2010 Report Posted May 26, 2010 Woo, got reboot whilst on power. Doh! Thats a shame. I haven't noticed any reboots, but it could have done overnight. Difficult to tell. I'll test it tonight and leave some apps running. On another point I do have problems charging my phone at the moment. Sometimes its stops charging beofre the battery is full. Its plugged in but does nothing, no charge simbol. Its strange and random. anyone else had this issue (only seems with 2.1 roms) but could be a hardware fault with my phone/charger.
Guest robot1000 Posted May 26, 2010 Report Posted May 26, 2010 Quick Question: Would this stop me from upgrading to a newer official software in the future?
Guest goce.nakov Posted May 26, 2010 Report Posted May 26, 2010 Quick Question: Would this stop me from upgrading to a newer official software in the future? From the newer no...but you cant go back to older ones ex...December T-mobile update
Guest robot1000 Posted May 26, 2010 Report Posted May 26, 2010 Quick Question: Would this stop me from upgrading to a newer official software in the future? Do all the custom ROMS still work and could I use this update.app in the same way as the December 09 (ie. restoring if something goes wrong)?
Guest goce.nakov Posted May 26, 2010 Report Posted May 26, 2010 Do all the custom ROMS still work and could I use this update.app in the same way as the December 09 (ie. restoring if something goes wrong)? All the custom ROM's are working...and yes you can use it the same way as the December update
Guest McSpoon Posted May 26, 2010 Report Posted May 26, 2010 Quick Question: Would this stop me from upgrading to a newer official software in the future? There is a possibility of that. But we don't know for sure!! For example, when T-Mobile UK produce their next update they must list which previous firmware versions can be updated. In order for the updata.app file to install, your firmware version must be in that list otherwise it will be rejected. We can pretty much assume they will list the following firmware versions:- U8220V100R001GBRC85B116SP01 (T-Mobile UK, November 2009 firmware) U8220V100R001GBRC85B118SP01 (T-Mobile UK, December 2009 firmware) etc. But they have no reason to list U8220V100R001C125B249SP01 which is a different carrier, it's 3 Sweden, Hutchinson 3G firmware. By installing that updata.app file you are installing the 3 Sweden Android 1.5 firmware and you might not be able to install any T-Mobile updata.app files anymore. You WILL still be able to install Android ROMs in update.zip format but perhaps not the T-Mobile updata.app firmware updates.
Guest Gurdjieff Posted May 26, 2010 Report Posted May 26, 2010 From the newer no...but you cant go back to older ones ex...December T-mobile update It seems i find the answer for my question So no any way back?
Guest -Yaya- Posted May 26, 2010 Report Posted May 26, 2010 I guess your theory is wrong! If that would be the case why did 3 Sweden, (Hutchinson 3G firmware) like you said, include the T-Mobile 2009 December Update into their list of versions which can be updated?!
Guest McSpoon Posted May 26, 2010 Report Posted May 26, 2010 If that would be the case why did 3 Sweden, (Hutchinson 3G firmware) like you said, include the T-Mobile 2009 December Update into their list of versions which can be updated?! I don't know why, but they did. You can use this Perl script to extract the contents of the updata.app file. One of the files extracted is called 'upgradable_versions.txt'. That list in the 3 Sweden Hutchinson updata.app contains the following:- U8220V100R001C00B010SP2 U8220V100R001C85B101 U8220V100R001C85B102 U8220V100R001C85B103 U8220V100R001C85B103SP01 U8220V100R001C85B103SP02 U8220V100R001C85B104 U8220V100R001C85B105 U8220V100R001C85B105SP01 U8220V100R001C85B105SP02 U8220V100R001C85B106 U8220V100R001C85B106SP01 U8220V100R001C85B107 U8220V100R001C85B107SP01 U8220V100R001C85B108 U8220V100R001C85B108SP01 U8220V100R001C85B108SP01_de U8220V100R001C85B109 U8220V100R001DEUC85B109 U8220V100R001C85B109SP01 U8220V100R001C85B110 U8220V100R001C85B110SP01 U8220V100R001C85B111 U8220V100R001C85B111SP01 U8220V100R001C85B111SP02 U8220V100R001C85B111SP03 U8220V100R001C85B112 U8220V100R001C85B112SP01 U8220V100R001C85B113 U8220V100R001C85B115 U8220V100R001C85B115SP01 U8220V100R001C85B115SP02 U8220V100R001C85B115SP03 U8220V100R001C85B116 U8220V100R001C85B116SP01 U8220V100R001C85B116SP02 U8220V100R001C85B116SP03 U8220V100R001C85B116SP04 U8220V100R001C85B117 U8220V100R001C85B117SP01 U8220V100R001C85B117SP02 U8220V100R001C85B117SP03 U8220V100R001C85B117SP04 U8220V100R001C85B118 U8220V100R001C85B118SP01 U8220V100R001C85B118SP02 U8220V100R001C85B118SP03 U8220V100R001C85B118SP04 U8220V100R001C01B221 U8220V100R001C01B222 U8220V100R001C01B223 U8220V100R001C01B224 U8220V100R001C01B225 U8220V100R001C01B226 U8220V100R001C01B227 U8220V100R001C01B228 U8220V100R001C01B229 U8220V100R001C01B230 U8220V100R001C01B231 U8220V100R001C01B232 U8220V100R001C01B233 U8220V100R001C01B234 U8220V100R001C01B235 U8220V100R001C01B236 U8220V100R001C01B237 U8220V100R001C01B238 U8220V100R001C01B239 U8220V100R001C01B240 U8220V100R001C01B241 U8220V100R001C01B242 U8220V100R001C01B243 U8220V100R001C01B244 U8220V100R001C01B245 U8220V100R001C01B246 U8220V100R001C01B247 U8220V100R001C01B248 U8220V100R001C01B249 U8220V100R001C01B250 U8220V100R001C01B251 U8220V100R001C01B252 U8220V100R001C01B253 U8220V100R001C01B254 U8220V100R001C01B255 U8220V100R001C01B256 U8220V100R001C01B257 U8220V100R001C01B258 U8220V100R001C01B259 U8220V100R001C01B260 U8220V100R001C01B261 U8220V100R001C01B262 U8220V100R001C01B263 U8220V100R001C01B264 U8220V100R001C01B265 U8220V100R001C01B266 U8220V100R001C01B267 U8220V100R001C01B268 U8220V100R001C01B269 U8220V100R001C01B270 The versions starting with U8220V100R001C85B*** are all T-Mobile (C85) Why have they been included? I don't know. And I've no idea which carrier the C01 versions are (U8220V100R001C01B***), perhaps that just means generic. For some reason, that Hutchinson 3G firmware had listed T-Mobile versions as being acceptable for upgrading. But will future T-Mobile updates list U8220V100R001C01B255 ?? BTW, I've just discovered that updata.app file actually has a firmware ID of U8220V100R001C01B255 which perhaps isn't so bad as it's generic and not Hutchinson 3G. I had initially assumed it was U8220V100R001C125B249SP01 because of the filename. But I'm still concerned that T-Mobile might not list it as being upgradeable.
Guest Lord_Shaithis Posted May 26, 2010 Report Posted May 26, 2010 (edited) About to finally jump to 2.1 and failed at the first hurdle.... I have applied the first ROM (the 1.5) and it has worked, going back to vanilla (was 1.8 before) but volume up + red key and switch on either: Boots normally (sd card removed) Says update failed (sd card inserted - even after formatting the sd card) Booting normally with s card inserted is fine....I am very confused! Any ideas? EDIT: Nvm......just had an epiphany!! Its volume down not volume up :rolleyes: EDIT2: Also got the touch screen not functioning but just carried on and it was ok again once 2.1 was loaded. Edited May 26, 2010 by Lord_Shaithis
Guest le_lutin Posted May 27, 2010 Report Posted May 27, 2010 I still have the lines in my photos when taken with the camera. This is after applying the vibration fix and going to (Starkos') 2.1.
Guest le_lutin Posted May 27, 2010 Report Posted May 27, 2010 I still have the lines in my photos when taken with the camera. This is after applying the vibration fix and going to (Starkos') 2.1. In addition to the above, 2.1 still has the gallery* bug where it doesn't support screen rotation (screen goes all screwy). *Note this is NOT the default gallery that comes with the phone, it's the 2.1 Nexus version.
Guest igor_anta Posted May 27, 2010 Report Posted May 27, 2010 In addition to the above, 2.1 still has the gallery* bug where it doesn't support screen rotation (screen goes all screwy). *Note this is NOT the default gallery that comes with the phone, it's the 2.1 Nexus version. There is a newer version of the gallery, it's not a problem with our phone. I thought so as well but then I found the newer version and it's good. I posted it on the Systematic cleanup of errors thread you can download it. Cheers!
Guest le_lutin Posted May 27, 2010 Report Posted May 27, 2010 There is a newer version of the gallery, it's not a problem with our phone. I thought so as well but then I found the newer version and it's good. I posted it on the Systematic cleanup of errors thread you can download it. Cheers! Thanks igor, I had that version of the gallery before I applied the vibration fix. As you said yourself, when the phone rotates it just restarts the gallery application (at the root of all the folders), which isn't really very useful for me.
Guest kohaku Posted May 28, 2010 Report Posted May 28, 2010 In addition to the above, 2.1 still has the gallery* bug where it doesn't support screen rotation (screen goes all screwy). *Note this is NOT the default gallery that comes with the phone, it's the 2.1 Nexus version. I found that the rotation detection is over sensitive, it keep rotating even I am holding the phone in portait position running android market/any other apps But I rarely use landscape anyways and disabled the rotation. The spirit level when using GPS status seems fine though
Guest titchu Posted May 28, 2010 Report Posted May 28, 2010 (edited) I finally got my phone vibrate on 2.1 . thx all! :D however , camera FC when switching to video mode ? any ideas on this? :rolleyes: Edited May 28, 2010 by titchu
Guest ozren Posted May 28, 2010 Report Posted May 28, 2010 Is it possible to have a custom rom on a phone after applying this! I mean with working a2sd? I tried to flash both roms on my phone but in both cases first touchscreen did not work, when I fixed that with superboot and different boot.img I noticed that I can not install any app from the market or the sd due to insuficient memory. I tried fixing ext partition but that did not help. Is there a way to do this and am I doing something wrong? Pleasee anyone?
Guest goce.nakov Posted May 28, 2010 Report Posted May 28, 2010 Is it possible to have a custom rom on a phone after applying this! I mean with working a2sd? I tried to flash both roms on my phone but in both cases first touchscreen did not work, when I fixed that with superboot and different boot.img I noticed that I can not install any app from the market or the sd due to insuficient memory. I tried fixing ext partition but that did not help. Is there a way to do this and am I doing something wrong? Pleasee anyone? If you are using 1.7 Modaco vanilla you need to upgrade your SD partition to ext3 or ext4.........
Guest ozren Posted May 28, 2010 Report Posted May 28, 2010 If you are using 1.7 Modaco vanilla you need to upgrade your SD partition to ext3 or ext4......... Tried even that but did not help!
Guest goce.nakov Posted May 28, 2010 Report Posted May 28, 2010 Tried even that but did not help! Try to format your SD under PC...then re partition it again thru boot/recovery.....
Guest ozren Posted May 28, 2010 Report Posted May 28, 2010 Try to format your SD under PC...then re partition it again thru boot/recovery..... Многу ти благодарам!!! Now it works, uhhh got very angry on myself for the moment, I thought I am destined to live with constant reboots! Pozdrav!
Guest goce.nakov Posted May 28, 2010 Report Posted May 28, 2010 Многу ти благодарам!!! Now it works, uhhh got very angry on myself for the moment, I thought I am destined to live with constant reboots! Pozdrav! Glad that it helped :rolleyes:
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now