Hello to all Devs and fans at XDA who see my first post. For years I have watched the community and benefited from the knowledge they shared on the smartphones frontier. But today, I humbly ask for a hand from whoever might be be able to provide me with what I need.Here is situation:
1- I do hate Sony firmwares of Android 4.3 and the new 4.4 firmware because I want to stay LB and I do need to root and mount SYSTEM partition
which are difficult on such firmwares and I simply don't like deodexed flashable roms dear devs here provide.In my opinion Android 4.2.2 FW 14.1.G.2.257 seems to be the best one for me...but how to get this one rooted and stay odexed on LB? here are the steps I took :
2- I was on 4.3 and when i went to 14.1.G.534 my phone lost IMEI and GSM SIGNAL and couldn't OTA to 14.1.G.2.257(much to my surprise the phone downloaded the OTA update but the installation failed, so I flashed 14.1.G.2.257 and then went all the way back to the first firmware of z1 which is rootable: 14.1.G.534
3- I rooted this firmware with Kingo root , updated superSU Pro to the latest version enabled survival mode in its settings and installed recovery but now the OTA updater on the phone detects Android 4.3 FW 14.2.A.0.290 and I have no clue how to make it OTA to 14.1.G.2.257 NOT 14.2.A.0.290. As of now, I am stopped here and wondering if a small flashable zip with my desired OTA update could be provided to solve my problem or any other idea how to have my phone in the desired state...
Your help is highly appreciated :crying:
I'm not sure but I believe that not all firmware versions allows for OTA update from 534 to 257. You might have flashed a 534 firmware that only allows for OTA from 534 to 290. Have you tried the firmware from this thread?
If you are already on the firmware in the above thread, it may be the case that the OTA to 257 is just no longer available. You'll have to flash a de-odexed and pre-rooted 257 firmware (e.g. here).
Thank you for your reply. I am indeed on the firmware you mentioned. If you noticed I had said if Iflashed directly from 290 to 534 I would lose IMEI but my phone detected 257 for OTA update but when it restarted to install, it failed and i was back with no change. If I downgrad from 290 to 257 and then to 534 I will have IMEI and signal back but this time 290 is detected for OTA.Yeah i read the post related to my firmware but I don't need a deoexed rom and I don't know how to redoex it if using that would be my last choice.
hfaz63 said:
Thank you for your reply. I am indeed on the firmware you mentioned. If you noticed I had said if Iflashed directly from 290 to 534 I would lose IMEI but my phone detected 257 for OTA update but when it restarted to install, it failed and i was back with no change. If I downgrad from 290 to 257 and then to 534 I will have IMEI and signal back but this time 290 is detected for OTA.Yeah i read the post related to my firmware but I don't need a deoexed rom and I don't know how to redoex it if using that would be my last choice.
Click to expand...
Click to collapse
On NUT thread you'll find firmware 534.
You can flash that one from 4.3 or even 4.4 and you'll preserve IMEI.
Without IMEI you can't update firmware through OTA so, probably, that was the problem.
Now you should be able to update firmware through OTA.
If that fails or OTA offers latest firmware you don't want to use you can try to find flashable firmware 290 but I doubt we have that...
Sent from my C6903 using Tapatalk
OK i think I know what is going on but could I have a rooted UN-DEODEXED 14.1.G.2.257 on my z1??The method you proposed for upgrading to 257 and keeping root now want's to install 290 on my phone....I wish to install 257 NOT 290
I searched but couldn't find any rooted un-deodexed 257 firmware, and that's why I didn't point you to one in my previous post. I think most of us upgraded via OTA to 257 and kept root, hence there wasn't a need for a developer to create a rooted un-deodexed 257 firmware.
Related
The update is 74 MB in size.
My original firmware was .181 HK. Rooted via Gingerbreak. OTA updated to .145. Now .368.
Rogers locked/branded Arc.
As of 8.20.11 OTA is available in the following countries:
HK generic
UK generic
Germany generic
hellocng said:
The update is 74 MB in size.
My original firmware was .181 HK. Rooted via Gingerbreak. OTA updated to .145. Now .368.
Rogers locked/branded Arc.
Click to expand...
Click to collapse
Great news! Just in time as I was about to unlock the bootloader!
So the OTA is for HK firmware?
EDIT: Given up! Tried and couldn't get updated . Now I've unlocked the bootloader .
...and root remained after the update?
-Sent from my Arc (LT15a)
I'm not sure if the CDA code changes after an OTA but I dont think the firmware region matters.
Yes, root remained. Also, through both OTA, I did not remove any bloatware or mod any system files.
So what should we do to have that update now? I have tried to edit build.prob file to
- Hong Kong Generic 1247-1052. but no luck. It says you have the latest firmware
How much time and effort do you want to invest and get .368 OTA? I reflashed my Arc four days ago because I had a notification on my modded .145 that an update was available. I knew I couldnt get the OTA if I did not have a clean install of the .145 so the logical thing for me to do was flash a new .181, Gingerbreak it and update. I chose the .181 HK firmware. Until today I only had the .145 offered. I did nothing to alter the stock firmware so that I could update when the OTA was offered again.
So the steps are:
Flash .181 HK firmware
Gingerbreak
OTA .145
OTA .368
Then you can mod it and tweak it as you please. I cannot guarantee you anything if you even install Busybox. Do the bare minimum you need to obtain root and then update.
so with HK firmwares having OTA now, I'm pretty much optimistic they'll come for the global generic too...
i've a rooted .145 via OTA coming from .181 gbreak (based on the namaste guide) and as far as this post's date, no OTA yet...
*still a mystery why the generic one is being prioritized last... TT.TT
Based on my experience, this update is unlike .145 and any changes you make to the stock firmware, including removing bloatware may hinder the success of the update. The update will download but it will stop at the third stage/circle during the update and fail. Others can chime in on their OTA experience when the update is more available.
I am a good boy.
Here is HK.181 http://www.mediafire.com/?k4m8nsgm8a2k1z9
enjoy
In Indonesia still no update when i checked with wifi
it works for me
datagubben said:
I am a good boy.
Here is HK.181 http://www.mediafire.com/?k4m8nsgm8a2k1z9
enjoy
Click to expand...
Click to collapse
Great, updated the Index with all new information!
That truth, updating it is accessible on ОТА?
muzontnt said:
That truth, updating it is accessible on ОТА?
Click to expand...
Click to collapse
Yep, flash the firmware I linked in the Index thread, just follow the steps in red
Ambroos said:
Yep, flash the firmware I linked in the Index thread, just follow the steps in red
Click to expand...
Click to collapse
Downloading in super slow mo, can't wait 6 hours lol
Guess I've got a project for after work tomorrow now.
Sent from my LT15i using XDA App
After the OTA update 4.0.A.2.368 Hong Kong, it's possible to change the country of firmware retaining root?
cesar7 said:
After the OTA update 4.0.A.2.368 Hong Kong, it's possible to change the country of firmware retaining root?
Click to expand...
Click to collapse
Nope. Changing region is only possible by doing either a full wipe or an update with SEUS/PC Companion. OTA is not possible after changing the region.
Just flashed back to 2.3.2 HK firmware and was able to OTA directly to .368, the update was just under 90MB. Root maintained!
im in the UK and ive just rooted 2.3.2 world generic, if i OTA to .368 with world generic software will i still have root?
Do I need to flash back to 2.3.2 to get the ota update? Or will it eventually be possible from my current 2.3.3?
Hi guys just to let you know that the 7105 (TGY) owners have a new FW update N7105ZHDMB1 N7105ZZHDMB1; I suspect it is the 4.1.2 version... OTA is queuing users, KIES has the update, and of course @ http://samsung-updates.com/device/?id=GT-N7105 and http://www.sammobile.com/firmwares/ to download the files it is a full GB update.Cheers
Well I updated using KIES and lost root, neitherSU survival mode nor OTA Rootkeeper are able to restore it.
Anyone can suggest a way to recover root? Cheers
Re rooted with the same method I used to root on the first time...I guess that is pretty ease lol... I should have read the OTA statement that it only restores after OTA not KIES!! Cheers
Hi All,
I have used CF-Auto-Root when I first got my phone about 3 months ago and rooted successfully and it changed my device status from Official to custom and therefore I was never able to check for OTA or install them.
I have also tried CF's Triangle Away at that time but it never set the status back to Official until last night when I installed the latest TA version 3.05 and this had worked it's magic and my phone status is now back to Official and I found an available OTA and downloaded it but I have not installed it yet. Why? Because I am almost sure I will lose root after installing the OTA update and I am not sure if I am able to re-root it again as I have heard and read that Samsung is trying to lock things down to make it harder for us to play around with our phones.
I My current build number is JDQ39.I9505XXUAMDE so if I am not mistaken, that means I am on firmware XXUAMDE.
The phone does not tell me any info after it completed the OTA download about this upfate apart "Stability Improvement"
My questions are:
1. How can I tell if this new firmware is not going to lock things down?
2. Would I be able to easily re-root after completing the firmware update?
I just plugged in my phone to my computer and Samsung Kies is telling me this:
Current firmware version : PDA:MDE / PHONE:MD8 / CSC:MD8 (VAU)
Latest firmware version : PDA:MG4 / PHONE:MG1 / CSC:MG1 (VAU)
and asking me if I want to upgrade.
Can someone help me answer my questions and clear this for me?
Sorry for all these questions but I am just a little worried this update will be a bad move and I don't want to regret it.
Thanking you in advance for putting up with me and my apologies if some of these questions are repeated or dumb.
AFAIK, MG4/MG1 is not sooo new, and it's still not afected by the 'knox' bootloader thing.
I upgraded to MGA (AMN) some 3 weeks ago, using KIES, temporarylly lost root, but flashet CF Auto Root again, and .... voila! good to go again.
.... oh yes, I had to install supersu again from play store (somehow it was rooted, but the application was not there).
Hope that can help you!
Bak
Thanks Bak for the info.
I was doing some more googling and I came across these 2 pages:
http://www.ibtimes.co.uk/articles/4...ial-android422-xxuamde-jellybean-firmware.htm
http://www.ibtimes.co.uk/articles/4...roid422-xxuamdn-jellybean-official-update.htm
There is something wrong here as my phone is I9505 and it came with the amde unlike what is suggesting that official firmware for I9505 is amdn.
I got my phone from Voda Australia hence the VAU.
If I am reading this correctly:
Current firmware version : PDA:MDE / PHONE:MD8 / CSC:MD8 (VAU)
Latest firmware version : PDA:MG4 / PHONE:MG1 / CSC:MG1 (VAU)
Then after the OTA update then I should be on XXUAMG4 ? I really don't get this whole PDA / PHONE / CSC variables.
I am just tempted to install it and thinking if anything goes wrong or not to my liking then I can use the link I provided above to flash my phone with the official xxaumdn and this does not have the "knox" bootloader thing?
good decision mate! dont flash to the latest MH8 firmware cuz it locks out your fone.
sadly i've flashed mine without reading around. little did in know, MH8 includes knox with locked my phone.
right now i'm having root problems. tried using CF 1.60 the latest one.. which they said can bypass the knoxx thing. we'll i'm still having problems getting root access.. IDK why.
just wait and see. a dev might come up with some work around this KNOX bootloader thing
Saturn007 said:
Thanks Bak for the info.
I was doing some more googling and I came across these 2 pages:
http://www.ibtimes.co.uk/articles/4...ial-android422-xxuamde-jellybean-firmware.htm
http://www.ibtimes.co.uk/articles/4...roid422-xxuamdn-jellybean-official-update.htm
There is something wrong here as my phone is I9505 and it came with the amde unlike what is suggesting that official firmware for I9505 is amdn.
I got my phone from Voda Australia hence the VAU.
If I am reading this correctly:
Current firmware version : PDA:MDE / PHONE:MD8 / CSC:MD8 (VAU)
Latest firmware version : PDA:MG4 / PHONE:MG1 / CSC:MG1 (VAU)
Then after the OTA update then I should be on XXUAMG4 ? I really don't get this whole PDA / PHONE / CSC variables.
I am just tempted to install it and thinking if anything goes wrong or not to my liking then I can use the link I provided above to flash my phone with the official xxaumdn and this does not have the "knox" bootloader thing?
Click to expand...
Click to collapse
Just checked with www.samfirmware.com
If you select the 'check your firmware', you'll see that the last version for i9505 and Australia VAU (vodaphone) is PDA:MG4 / PHONE:MG1 / CSC:MG1
So your carrier (vodaphone) hasn't released the MHx version yet (versions MHx hsve the knox thing)
PDA / PHONE / CSC are different pieces of the software/firmware, and may have different releases (you can even play with different ones, for instance, a diferent PHONE to be able to sim unlock, etc....)
If I was you, I'd let KIES do the update (it's the safest, together with the OTA), and re-root it.
Good luck
Bak
Thanks Bak. I upgraded over the weekend and re-rooted it and all is back to normal now.
I even got Triangleaway to reset counter and back to official status.
Thanks for all your info.
so after cf autoroot...I unrooted clicking on the full unroot in SUPERSU...as my one's the N900 model from Saudi Arabia...I jst received an update of MJ7 through kies....when I checked for ota it jst stucked on Connecting to servers..surprisingly I got the update notification frm Ota first..I didnt update yet but i dnt knw the size of the update and so slow over kies..someone check Ota and tell me of its possible...How to fast kies update...and what may be the size? pls inform....anybody following the method can always root back by flashing supersu within 1min..u can easily GET FIRMWARE UPDATE EASILY AFTER ROOTING...please answer my questions too.thanks
Well, new update for Tablet Z2. According to this:http://www.xperiablog.net/2014/12/0...a-3-12-and-z2-tablet-23-0-1-a-4-44-in-taiwan/
yet another firmware update for tablet Z2 is rolling out right now. Newest buildnumber is 23.0.1.A.4.44. Previous was 23.0.1.A.4.30.
Seems that so far Taiwan region and also branded HK, SA, AE, KW are updated. Haven´t seeing any chance log.
Is this going to pose a threat to our root?
I am guessing towel root will not work because of the exploits being patched up in 4.4.4
Very good question....
Got my notification to update via PC a little while ago. Will see if I can trap it first
Suppose I will test the waters. Almost for sure root will be gone.
Most likely towelroot or any other roottool's based on that will not work. However flashing vulnerable kernel from 314 firmware, rooting it and flashing new firmware kernel back might work.
I'll check my tablet when I get home, I've gotten the notification for my z2 phone now.
Unable to update
Unable to install it,
updating via PC Companion, downloading update, but when tablet reboots i get the message from Companion that there is no update available.
I'm probably not the only one with that problem..
http://blogs.sonymobile.com/2014/11/04/our-latest-sony-software-upgrade-brings-ps4-remote-play-hi-res-audio-new-smart-social-camera-apps-more-for-xperia-z2-and-xperia-z2-tablet/#comments
I got the same thing happening to my tablet :/
Downloads, starts to update then just turns of the tablet and it fails.
Same here... update fails.
Envoyé de mon SGP511 en utilisant Tapatalk
I used this guide to intercept the download from PC Companion and create an FTF file.
I have no clue if it's a valid file, but here's the link (I have an SGP511):
<link removed>
Well that's nice. PC Companion says there's a new version, but it just downloads the old one
So I download firmware that Sony PC Companion offers as new .167 firmware and found out it is old .314 firmware . Have to wait.
MrMagic said:
I used this guide to intercept the download from PC Companion and create an FTF file.
I have no clue if it's a valid file, but here's the link (I have an SGP511):
https://mega.co.nz/#!nohxDQyD!u05pwh2yP_y8kWwhlS8pQAQbyeuiujlVyvTWUjJnFuM
Click to expand...
Click to collapse
And you are up and running with 4.4.4 and no issues?
SweDunda said:
And you are up and running with 4.4.4 and no issues?
Click to expand...
Click to collapse
I just edited my post and removed the link, since PC Companion says there's a new version available but it just downloads the old one
Update is working now. Installing... FALS ALARM !
EDIT: FFS ! It only reinstalled the old 4.4.2 !
There's some problems with Sony Server, wait for few hours...
Update is working now. Just finished the upgrade.
Can't root
Updated (Firmware 23.0.1.A.0.167).
Can't root via easyroottool V12.3 or towelroot v3.
I read rooting works if you flash the old .314 kernel first, then root, then flash back the .167 kernel. Didn't try it myself yet though.
Uploading a FTF for SGP511 now! Stay tuned!
Update is working right now. Everything's working fine!