Anyone heard anything about this one? Supposedly it started popping out yesterday to some of the people and when I manually checked, popped out to me too. Brings back G-sensor calibration tool.
Any more info? Download link?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Got the same!But after downloading,it asked me to install the update and rebooted
into Recovery menu!
Then,at recovery menu,I got "No Siganture (235 files)" and "Verfication failed"
error!
Installing update,maybe not possible at Custom ROMs!
My download from server attached:
never seen that b4...
Ganii said:
...I got "No Siganture (235 files)" and "Verfication failed"
error!
Installing update,maybe not possible at Custom ROMs!
:
Click to expand...
Click to collapse
yes, you won't be able to install this on custom rom
Hm,maybe anybody can make it possible?
Ganii said:
Hm,maybe anybody can make it possible?
Click to expand...
Click to collapse
Yeah, it should be possible.
Htc release ota updates as delta upgrades, containing only differences between files. Custom ROMs don't use the identical same files, so we need to patch the old ones with these new files.
And our custom recovery images don't accept htc ota keys, since you could get locked out of rooting if this happened.
I can try and look later on at this...
Ok,so it seems problems with the "patch files" too,not possible
via recovery menu,right?
Hope you can do it!
Hmm it seems that this update only add's a gsensor config, I dont know if they fixed the problem with streams and T-Mobile Netherlands (I guess not).
Seems to be a lot of changes (a lot of files to patch) just to add G-sensor config. Probably a bugfix release too...
Eddie1506 said:
Seems to be a lot of changes (a lot of files to patch) just to add G-sensor config. Probably a bugfix release too...
Click to expand...
Click to collapse
Hmm well because I have a different bootloader and a stock T-Mobile rom it just don't show up. It's gonna take a while before I get my hands on this one
so is there a full list of what this update has done?
i have a custom rom and managed to install this with no problems.
i have seen a similar update on the desire and it seems to fix the message notifications (messages will display 1, even though all messages are read.)
Hi All,
Loking at the files contained within this update, can anyone confirm if this will have an effect on the Bluetooth capabilities of the phone. There are a few threads out there with people like myself who had their bluetooth functionality reduced with their car kits. The pairing would work, but the connection failed. The connection worked fine in 1.5, and is working again in custom 2.2 roms (I'm running Fusion),
Cheers
DoNcAs
pulser_g2 said:
Yeah, it should be possible.
Htc release ota updates as delta upgrades, containing only differences between files. Custom ROMs don't use the identical same files, so we need to patch the old ones with these new files.
And our custom recovery images don't accept htc ota keys, since you could get locked out of rooting if this happened.
I can try and look later on at this...
Click to expand...
Click to collapse
any progress?
hmm, update.zip contains boot.img and recovery.img, as well as many updates for framework, many apps, system etc...
so it can contain any new protection method to disable root possibility and/or changing roms to custom.
anybody with genuine 2.1 installed this? anything happened?
I just checked the boot.img from the original update to Android 2.1 and from this one, and they're exactly the same, bit by bit, so there isn't any changes in the kernel.
appied update and then rooted all worked fine
i have installed this update after i got my repaired hero back from htc yesterday. i did root my phone after this update and it seems to be fine.
the only thing i cant do is downgrade to 1.5 using a goldcard. it say something about im using the incorrect id.
But i dont know if that was the update that did that or htc did it when they had my phone
sleepymonk said:
i have installed this update after i got my repaired hero back from htc yesterday. i did root my phone after this update and it seems to be fine.
the only thing i cant do is downgrade to 1.5 using a goldcard. it say something about im using the incorrect id.
But i dont know if that was the update that did that or htc did it when they had my phone
Click to expand...
Click to collapse
Sounds normal. What rooting method did you use? (Shamelessly trying to find out if my port of the Droid eris one still works after this update)
If you root and flash custom recovery, you can flash another hboot, thus allowing a 1.5 RUU to work with gold card.
But that is a risky process, and there's no need in my opinion to use it.
@pulser_g2
You are working on an update.zip,so we can flash with
custom rom`s?
Or not possible?
Ganii said:
@pulser_g2
You are working on an update.zip,so we can flash with
custom rom`s?
Or not possible?
Click to expand...
Click to collapse
What do you mean? I'll probably post the raw files from this update, and then anyone who wants them can push them into a ROM.
Looking at the zip right now and it's definatly a bunch of updates for the system!
Related
Can a mod please delete this thread fully. I am pulling the project and going to stock rom until i learn alot more about this crap.
sorry for any inconvenience this may cause.
Please root it as soon as possible
Radio version is not correct.
Radio version included in this OTA is 63.18.55.06PU_6.35.15.11.
Rooting now...
Eddie1506 said:
Radio version is not correct.
Radio version included in this OTA is 63.18.55.06PU_6.35.15.11.
Click to expand...
Click to collapse
Well that's wierd, I can post screenshots the radio that came from the update on my system about... Where did you get the info from?
andrewb84uk said:
Well that's wierd, I can post screenshots the radio that came from the update on my system about... Where did you get the info from?
Click to expand...
Click to collapse
Opened radio.img with a hex editor
Eddie1506 said:
Opened radio.img with a hex editor
Click to expand...
Click to collapse
It's not the version it says once flashed
andrewb84uk said:
It's not the version it says once flashed
Click to expand...
Click to collapse
Did you actually witness radio flashing while flashing OTA? Try rebooting one more time to see. If there's no mention of .11 version in system/about, it didn't flash correctly.
P.S. can you make nandroid dump of your newly flashed device? (Just the system.img ofc)
Just FYI:
DO NOT FLASH THIS OR IT WILL WIPE YOUR ROOT & YOU WILL NEVER BE ABLE TO GET IT BACK!
Unless for some crazy reason you don't want root...
Eddie1506 said:
Did you actually witness radio flashing while flashing OTA? Try rebooting one more time to see. If there's no mention of .11 version in system/about, it didn't flash correctly.
P.S. can you make nandroid dump of your newly flashed device? (Just the system.img ofc)
Click to expand...
Click to collapse
I sat and watched it flash the radio img I made an update.zip signed for it. Going to flash it again give me a moment.
Is the WWE multilingual? I don't remember how it was with 1.5.
andrewb84uk said:
I sat and watched it flash the radio img I made an update.zip signed for it. Going to flash it again give me a moment.
Click to expand...
Click to collapse
Ah, so you didn't flash the whole OTA, just radio.img.
Maybe you put a wrong radio.img in the zip by mistake
I would flash the radio myself, but there's no need for me as I have an even newer version (.14 from Asia release three days ago)
Eddie1506 said:
Ah, so you didn't flash the whole OTA, just radio.img.
Maybe you put a wrong radio.img in the zip by mistake
I would flash the radio myself, but there's no need for me as I have an even newer version (.14 from Asia release three days ago)
Click to expand...
Click to collapse
I have just sat and done the radio again.... about > version
63.18.55.06PH_6.35.15.11
I packed the wrong radio haha!
andrewb84uk said:
I have just sat and done the radio again.... about > version
63.18.55.06PH_6.35.15.11
I packed the wrong radio haha!
Click to expand...
Click to collapse
Hahaha
andrewb84uk said:
I have just sat and done the radio again.... about > version
63.18.55.06PH_6.35.15.11
Click to expand...
Click to collapse
Wondering if I should bother. I am on: 63.18.55.06PU_6.35.15.14
Anyone know how the radio numbering scheme works?
Just to clarify - I'm not that fussed about root at the moment but I guess I might want to have it at some stage. If I take this update I won't be able to roll back to a stock rom or do some sort of hard reset in order to be able to start from fresh in order to get root?
Stringy said:
Just to clarify - I'm not that fussed about root at the moment but I guess I might want to have it at some stage. If I take this update I won't be able to roll back to a stock rom or do some sort of hard reset in order to be able to start from fresh in order to get root?
Click to expand...
Click to collapse
It will overwrite your recovery image, and does have have root, or the exploit used in the past to get root.
So, unless you like the possibility of never being able to load a custom ROM, DON'T INSTALL THIS... Wait for a repack.
Does this need http://liveimage.htc.com/OTA_Hero_HTC_WWE_2.73.405.93-2.73.405.5_release7sd65upagwzkrpms.zip first?
Note, I'm not planning on flashing it.
EDIT: Ok it seems this is more complicated than I initially thought. I was going to try my first attempt at rooting a stock ROM today but this appears to just be a patch of some sort?
Hacre said:
Does this need http://liveimage.htc.com/OTA_Hero_HTC_WWE_2.73.405.93-2.73.405.5_release7sd65upagwzkrpms.zip first?
Note, I'm not planning on flashing it.
EDIT: Ok it seems this is more complicated than I initially thought. I was going to try my first attempt at rooting a stock ROM today but this appears to just be a patch of some sort?
Click to expand...
Click to collapse
There could be a possible chance that you do because I just tryed to flash with that file and it came up
Code:
E:Failure at line 2:
assert file_contains("System:build.prop", "ro.build.fingerprint=htc_wwe/htc_hero/hero/hero:1.5/CUPCAKE/154788:user/release-keys") == "true" || file_contains("SYSTEM.build.prop", "ro_build.fingerprint=htc_wwe/htc_hero/hero/hero:2.1-upd
Installation aborted.
and so when i check line 2 of update-script
Code:
assert file_contains("SYSTEM:build.prop", "ro.build.fingerprint=htc_wwe/htc_hero/hero/hero:1.5/CUPCAKE/154788:user/release-keys") == "true" || file_contains("SYSTEM:build.prop", "ro.build.fingerprint=htc_wwe/htc_hero/hero/hero:2.1-update1/ERE27/3.32.405.1_191507:user/release-keys") == "true"
please have a look at this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is what most french people get after the update.(for the radio)
it shows PU instead of PH.
PS : sorry for the small size.
Nope Sorry.
Janek566 said:
Nope Sorry.
Click to expand...
Click to collapse
ok
then is it possible to unlock for free without root?
I just got a new SGSII and I don't want to have a big yellow exclamation mark my current one has
Then buy a £2 MicroUSB "jig" from eBay - that will clear it.
what do you mean "unlock without root?"
also there is a solution to exclamation mark if you flash custom kernels.
viper98 said:
ok
then is it possible to unlock for free without root?
I just got a new SGSII and I don't want to have a big yellow exclamation mark my current one has
Click to expand...
Click to collapse
No you need root.
Flash CF root, then flash back your stock kernel, you will still have root but without the yellow warning triangle.
veyka said:
No you need root.
Flash CF root, then flash back your stock kernel, you will still have root but without the yellow warning triangle.
Click to expand...
Click to collapse
how to I backup my stock kernel?
No need to, just make a note of what kernel you're using, then download it from http://forum.xda-developers.com/showthread.php?t=1075278
1. It is not possible to root without flashing kernal
But you can update firmware to newest one via ODIN
2. You can unlock without rooting... Its called paying for the unlock code
Free is only through rooting
3. And why have you got another one if you already have a SGS2 ??????
Is that you are hooked on to rooting and bricking
tfn said:
1. It is not possible to root without flashing kernal
But you can update firmware to newest one via ODIN
2. You can unlock without rooting... Its called paying for the unlock code
Free is only through rooting
3. And why have you got another one if you already have a SGS2 ??????
Is that you are hooked on to rooting and bricking
Click to expand...
Click to collapse
The screen was driving me crazy
the blue tint on it was so bad at off angle viewing
this one is much MUCH better
check out the difference
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I consider myself to be a bit of a videophile so having this was just eating away at my soul
You do know that updates fixed a bunch of colour temp issues right?
seshmaru said:
You do know that updates fixed a bunch of colour temp issues right?
Click to expand...
Click to collapse
this isn't a color temp issue
it's the coating on the screen
ok so I flashed XKWDD_insecure through Odin
that went fine
but now when I'm trying to root with super 1 click it keeps locking up at step #5
anyone know what's going wrong?
Just flash CF-Root kernel and you're done.
Sent from my GT-I9100 using XDA App
If you gotten a new SGS2, should that not have come with the latest firmware version of that phone, in such a case, would rooting with CF-root not be better?
MS. said:
Just flash CF-Root kernel and you're done.
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=14283383&postcount=3
how do I know which file to get?
viper98 said:
http://forum.xda-developers.com/showpost.php?p=14283383&postcount=3
how do I know which file to get?
Click to expand...
Click to collapse
go to applications > settings > phone information
and note down the kernel version. (look at the KE, KF1/2/3 etc)
and compare that to the ones in that topic. Pick the one that is like it, or almost like it.
Here is the full Thread http://forum.xda-developers.com/showthread.php?t=1103399
Syrellaris said:
go to applications > settings > phone information
and note down the kernel version.
and compare that to the ones in that topic. Pick the one that is like it, or almost like it.
Click to expand...
Click to collapse
but since I've already changed the kernel thru odin wont that information already be skewed?
Well if you didn't note down your stock kernel and flashed a completely different one into it, then you have a problem. Im still very much new to android systems and XDA. (i registed today, but I lurked and read and researched for several days)
But, I think you can just grab one of the latest ones but I think some more experienced users here can give you a better answer on that matter.
Syrellaris said:
Well if you didn't note down your stock kernel and flashed a completely different one into it, then you have a problem. Im still very much new to android systems and XDA. (i registed today, but I lurked and read and researched for several days)
But, I think you can just grab one of the latest ones but I think some more experienced users here can give you a better answer on that matter.
Click to expand...
Click to collapse
heh I think I got it working
thanks for the help guys
I just downloaded the first file on the list
flashed it and it gave me superuser access
then I got Galaxy_S Unlock and it successfully unlocked my phone
As the title states.. here is the 4.4.3 OTA zip for the GPE
http://www.androidfilehost.com/?fid=23501681358541868
link re uploaded
Thanks! Grabbing now <333
edit: Worked like a charm through stock recovery! Thanks again!
graffixnyc said:
link re uploaded
Click to expand...
Click to collapse
did you see a radio in there ?
no radio in the firmware zip
HolyAngel said:
no radio in the firmware zip
Click to expand...
Click to collapse
They must not have updated it..
Anyone else having WiFi problems? (OTA'd, so if necessary I will take this to Q&A.) Thanks.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from space.
TheriaultAJ said:
Anyone else having WiFi problems? (OTA'd, so if necessary I will take this to Q&A.) Thanks.
Sent from space.
Click to expand...
Click to collapse
Yes, My Wi-Fi won't turn on. Sucky
Any update in camera quality that puts 4.4.3 gpe on par with sense?
Sent from my HTC One_M8 using XDA Premium 4 mobile app
No.
Sent from space.
TheriaultAJ said:
No.
Sent from space.
Click to expand...
Click to collapse
There are many bugs in this build, i would not update. Camera doesn't work, won't mount an sd card, and the Wi-Fi will not turn on!
I am seeing wifi issue also will try the GPE radio if no good i will reflash to 4.4.2 stock
will it be safe to install on a at&t m8 converted to gpe ?
That's how I installed it. GPE conversion, received OTA this afternoon, installed, broke all of the things.
I was hoping to move away from .zips and manual installations after converting, and only use pushed OTAs.
Still looking for resolution. I doubt the devs didn't regression test, etc.
Sent from space.
Mine is an unlocked HTC One with the RUU GPE conversion. I'm having the same problems, even after reflashing the RUU and reapplying the OTA.
TheriaultAJ said:
That's how I installed it. GPE conversion, received OTA this afternoon, installed, broke all of the things.
I was hoping to move away from .zips and manual installations after converting, and only use pushed OTAs.
Still looking for resolution. I doubt the devs didn't regression test, etc.
Sent from space.
Click to expand...
Click to collapse
hummm i haven't received any ota but i think i'm going to try it anyways or i won't sleep tonight lol.
Please post results if you use OTA method.
Sent from space.
I figured out the problem. I flashed the new RUU that graffix posted with 4.4.3. The Kernal in the OTA is not updating like it should, it stays on the kernal that was made in March. The new Kernal has a date of Thursday May 22nd. So for whatever reason, the OTA is not flashing the new Kernal, which is why all those things were broken. If you use the RUU update, it will flash the new kernal, and everything works as it should.
You'll know right off the bat at first boot. With the OTA, the boot animation hangs and it hangs on the home screen. With the RUU flash, everything is buttery smooth
Psosmith82 said:
I figured out the problem. I flashed the new RUU that graffix posted with 4.4.3. The Kernal in the OTA is not updating like it should, it stays on the kernal that was made in March. The new Kernal has a date of Thursday May 22nd. So for whatever reason, the OTA is not flashing the new Kernal, which is why all those things were broken. If you use the RUU update, it will flash the new kernal, and everything works as it should.
You'll know right off the bat at first boot. With the OTA, the boot animation hangs and it hangs on the home screen. With the RUU flash, everything is buttery smooth
Click to expand...
Click to collapse
so what you are saying is do not take the ota and download the one from graffix and flash it in recovery ?
Is there a 4.4.3 ruu?
Sent from my HTC One_M8 using XDA Premium 4 mobile app
hello
First off, I have modded with cyanogenmod quite some time ago.
I have kept that up date (cause of their nice update program), but I have never updated the carrier roaming lists (PRL?). My coverage seems to be crappy and I think it just may have to do with my newbishness.
I am running Cyanogenmod 11-20141112-SNAPSHOT-M12-jflte
Sprint PRL = 55018
is there a retard guide for me to easily update.... any suggestions or links would be great. I have spent over an hour searching google, but I am obviously using the wrong keywords and I am getting frustrated. I keep stumbling across other models / mods and I am fearful of breaking something....
Thanks for your time
qu1nn
You'll need to flash a touchwiz based ROM to do a PRL update.
qu1nn said:
hello
First off, I have modded with cyanogenmod quite some time ago.
I have kept that up date (cause of their nice update program), but I have never updated the carrier roaming lists (PRL?). My coverage seems to be crappy and I think it just may have to do with my newbishness.
I am running Cyanogenmod 11-20141112-SNAPSHOT-M12-jflte
Sprint PRL = 55018
is there a retard guide for me to easily update.... any suggestions or links would be great. I have spent over an hour searching google, but I am obviously using the wrong keywords and I am getting frustrated. I keep stumbling across other models / mods and I am fearful of breaking something....
Thanks for your time
qu1nn
Click to expand...
Click to collapse
Make a nandroid backup.
Wipe everything.
Flash TouchWiz ROM.
Go to Settings/System Updates.
Update PRL and Profile.
Restore nandroid.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
bilgerryan said:
Make a nandroid backup.
Wipe everything.
Flash TouchWiz ROM.
Go to Settings/System Updates.
Update PRL and Profile.
Restore nandroid.
Click to expand...
Click to collapse
thanks for the detail.
I dont mean to be a turd, but there seems to be a whole lot of TouchWiz variants. Is there a specific one to use?
thanks, and best regards
qu1nn said:
thanks for the detail.
I dont mean to be a turd, but there seems to be a whole lot of TouchWiz variants. Is there a specific one to use?
thanks, and best regards
Click to expand...
Click to collapse
Any TouchWiz should be fine, but go with stock if you want to make sure
mattzeller said:
Any TouchWiz should be fine, but go with stock if you want to make sure
Click to expand...
Click to collapse
another dumb question, will I loose root if I flashTouchWiz (which is the original S4 Rom)..?
qu1nn said:
another dumb question, will I loose root if I flashTouchWiz (which is the original S4 Rom)..?
Click to expand...
Click to collapse
Yes, unless you use stock rooted. But that doesn't matter since all you are doing is flashing stock ROM, updating PRL and then restoring cyanogenmod
mattzeller said:
Yes, unless you use stock rooted. But that doesn't matter since all you are doing is flashing stock ROM, updating PRL and then restoring cyanogenmod
Click to expand...
Click to collapse
sorry for being a pain, but as I dont do this often...
if I flash the zip here http://forum.xda-developers.com/showthread.php?t=2257503
this will put me back to TouchWIz original (plus root)
then I will follow the rest of the steps
(sorry for being dense, I was incorrectly thinking that I would loose the ability to use clockworkmod recovery / restore functions once I flashed the touchwiz rom and I would have to root before I could restore cyanogen, but that is firmware not ROM..... )
Its late and I have been up forever...
Thanks
I need some help.
Using Clockworkmod recovery V 6.0.4.7.
Tried using http://galaxys4root.com/galaxy-s4-rooted-stock-roms/ >>>> "Download Galaxy S4 rooted Stock ROM Sprint SPH-L720 Latest MF9 "
checked the filesize and the md5 sum, all good.
WHen I tried to use CWM to install zip from SDcard1 it gave me an error (missing 4 of 5) and aborted the installation.
I tried to search somewhere else to find a .zip that would bring the Sprint SPH-L720 back to stock, however they all seem to not have .zip for CWM recovery however make use of ODIN (which i cannot use as I dont have a windows computer, I use linux)
I want to go back to stock to update the prl before going to cyanogenmod 12.1
any suggestions ?
thanks
qu1nn
Rough night here.
somehow I lost clockworkmod recovery and ended up being still rooted with stock mf9 recovery, but I still had cyanogenmod 11 working; I recovered by installing clockworkmod application; > model > flash clockworkmod recovery > shutdown.
In the midst of that fiasco I say this page http://forum.xda-developers.com/showthread.php?t=2296167
which implies that keeping the PRL as up to date is not so required.....
so I bailed after several different attempts to install a ROM that would allow me to do a prl update.
I flashed the latest cyanogenmod nightly 12.1 and I am off and running.
qu1nn
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
download
or
paffo said:
If you are already on 5.1.1 its enough to overwrite libs from rom .264
http://forum.xda-developers.com/showpost.php?p=64216224&postcount=160
Click to expand...
Click to collapse
Only Italy is available. Is there English option for this firmware?
palmpre3 said:
Only Italy is available. Is there English option for this firmware?
Click to expand...
Click to collapse
yes all firmwares have the english language you wont find any difference.
jefffisher said:
yes all firmwares have the english language you wont find any difference.
Click to expand...
Click to collapse
Thanks for the info.
I have been using US customized firmware without any issue with Hangouts dialer. But after I flashed to Nordic's latest, it stop working with error msg 'phone calling not available temp something...'. So I wonder some countries' firmware might have impact on that...
Update now available here in Austria.
Do u guys think I can simply OTA Update my rooted 256 fw? The Update is only 19.8 mb in size.
Dixxhead said:
Update now available here in Austria.
Do u guys think I can simply OTA Update my rooted 256 fw? The Update is only 19.8 mb in size.
Click to expand...
Click to collapse
You can but will lose root. :good:
chris5s said:
You can but will lose root. :good:
Click to expand...
Click to collapse
Thanks for the Feedback! Figures I lost it anyways (and the Recovery with it) even though I made and flashed a pre-rooted firmware from recovery as always. Whatever happened there. Gonna have to roll back to KK tonight, get Recovery up and running and then finally retry flashing the a newly created pre-rooted FW from my FTF file.
Really quite annoyed at this right now. Could have just OTA`d and the result would have been the same. Hopefully no big Security holes for some time. Not big on wasting several hours, just to get my phone running the way I want it to run.
Dixxhead said:
Thanks for the Feedback! Figures I lost it anyways (and the Recovery with it) even though I made and flashed a pre-rooted firmware from recovery as always. Whatever happened there. Gonna have to roll back to KK tonight, get Recovery up and running and then finally retry flashing the a newly created pre-rooted FW from my FTF file.
Really quite annoyed at this right now. Could have just OTA`d and the result would have been the same. Hopefully no big Security holes for some time. Not big on wasting several hours, just to get my phone running the way I want it to run.
Click to expand...
Click to collapse
did you use CWM or TWRP to flash?
jefffisher said:
did you use CWM or TWRP to flash?
Click to expand...
Click to collapse
I think I used CWM, now that u mention it. Philztouch thing. So better to use TWRP?
Dixxhead said:
I think I used CWM, now that u mention it. Philztouch thing. So better to use TWRP?
Click to expand...
Click to collapse
yeah try using TWRP next time i had no issues and the only difference i could think of is the method used to flash.
jefffisher said:
yeah try using TWRP next time i had no issues and the only difference i could think of is the method used to flash.
Click to expand...
Click to collapse
TWRP did the trick. Rocking a dual recovery, rooted fresh install of .264 now.
What if i update via PCC? Will i loose root?
AMDFenics said:
What if i update via PCC? Will i loose root?
Click to expand...
Click to collapse
yes
So the flash must be with twrp only right ?
If you are already on 5.1.1 its enough to overwrite libs from rom .264
http://forum.xda-developers.com/showpost.php?p=64216224&postcount=160
paffo said:
If you are already on 5.1.1 its enough to overwrite libs from rom .264
http://forum.xda-developers.com/showpost.php?p=64216224&postcount=160
Click to expand...
Click to collapse
Thnx, added it.
.264 error power off
after upgraded to .264, my phone was down, cannot power on. any one faced this problem
So I ran the OTA and after it installed, all the apps that I had moved to the SD card were no longer on my homescreens, and I cannot even search for them in the Google Now launcher app. They are still in the app drawer but I have to manually scroll down and find them. I can't just type in their name?? Anyone else have this issue? I am totally stock, no root or anything.
I had something similar. With all apps on the sd card initially being unavailable. After maybe 5 minutes the phone rebooted itself and now all apps appear to have been restored to where they were prior to the update and are once more able to be used
vdefender said:
So I ran the OTA and after it installed, all the apps that I had moved to the SD card were no longer on my homescreens, and I cannot even search for them in the Google Now launcher app. They are still in the app drawer but I have to manually scroll down and find them. I can't just type in their name?? Anyone else have this issue? I am totally stock, no root or anything.
Click to expand...
Click to collapse
Since the update, i have the same problem ... In conclusion my micro sd card is dead ... Impossible to format and i can't delete files ...