Related
I want to revert to stock from Cloudyflex 1.4 but i dont know my firmware version, my phone is the d802 32gb ,i bought it from amazon,and in the box it says SEA,but no software information ,just the imei and the serial number,how can i discover what file to download???
settings, about phone, software information portion will see.
ocankurt said:
settings, about phone, software information portion will see.
Click to expand...
Click to collapse
But i am using a custom rom
ousionc way
I think it was version d80...10e.
This post/thread is to summarize where to find full SBF files, leaks, etc for the Moto X (2013 or First Generation).
REMEMBER... Always flash the same ROM/SBF or Newer to your phone. NEVER attempt to downgrade your rom!!! for more info, see DOWNGRADING
Motorola posts their complete STOCK "Recovery Images" (aka SBF files) for the GSM and Verizon Developer Edition X at -> https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
If you have the Retail and/or Moto Maker XT1053 (aka Unlocked ships with T-Mobile SIM, or Unlocked Ships with Net10 SIM), you can also use the GSM Developer Edition (XT1053) roms from Moto's site.
If you have the Retail and/or Moto Maker Verizon X (XT1060), you can also use the Verizon Developer Edition (XT1060) roms from Moto's site.
There might be a delay in Moto making an SBF available.
For other models of X, I know of 3 sites for "leaks" which contain the SBF files for nearly every model of X (2013). You may need to check EACH site to find the particular rom you are looking for. NOTE: None of the following sites are owned, operated, or sponsored by Motorola. They may be down or offline at any time, without warning.
http://sbf.droid-developers.org/ <- DEAD when checking on 8/22/15
http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=100&page=1 <- seems to have the most 4.4.4 roms
http://motofirmware.com/files/category/9-ghost/ <- DEAD when checking on 8/22/15 once there, look under the GHOST folder. (as of 11/9/2014, its format and access has changed)
http://motofirmware.center/files/ <- Select Moto X 1St Generation from the list along the right side of the page
Are there any others?
@dagoban has linked a few other in Post #17 of this thread..
dagoban said:
..Really good and fast overview page with most/all files, when you look for something, go here 1st:
https://cloud.mail.ru/public/64a43f0fcc1e/Moto_X or here:
https://cloud.mail.ru/public/a083d0bb5e97/Motorola
Big Thx to OP: http://4pda.ru/forum/index.php?showtopic=514209&st=8360
Click to expand...
Click to collapse
See Post #17 for more direct links.
As 5.1 SBF files become available, they are being collected and curated in this thread -> [OFFICIAL] Collection Full Firmwares (FXZ/SBF) Lollipop 5.1
FAQ:
1. How do I know which file to download?
- If you are NOT running a 3rd Party or Custom ROM... take a look on your phone, under App Drawer -> Settings... Make note of what is listed under System Version, Android Version, and build number. Then visit one (or all) of the sites until you find the SBF that matches. The file name will usually contain parts or all of that info listed under settings, and possibly the carrier name, or acronym for the carrier name (Verizon might be VZW, Rogers Canada might be RCI, etc).
Normally I would suggest BEFORE you flash away from Stock, on the phone you first go App Drawer -> Settings -> About Phone... Make note of what is listed under System Version, Android Version, and build number. Then visit one (or all) of the sites until that host the leaked SBF files until you find the SBF that matches and down load the file to your PC for use later.. The file name will usually contain parts or all of that info listed under settings, and possibly the carrier name, or acronym for the carrier name (Verizon might be VZW, Rogers Canada might be RCI, etc).
So for example: If your phone model is XT1058 and under about phone it reports...
android version is 4.4.4
system version is 212.44.26. ghost_row.RCI.en.ca
build nunber is KXA21.12-L1.26
That tells me you have a Rogers Canada (RCI) XT1058 with 4.4.4 ROM on it. When you look at the file factory site for your SBF, you want to look for a file that contains some/all of that info, like... XT1058_RCI-CA_4.4.4_KXA21.12-L1.26_59_cid14_CFC_1FF.xml.zip
(notice the parts of the "about phone" info and file name which are highlighted in Bold to help illustrate the example)
IF you are already running a CUSTOM or 3Rd party rom, like CM, system version and build number will not match STOCK Moto SBF files
2. Where do all these SBF files come from?
As mentioned earlier, Moto does make the Dev Edition "recovery images" (in SBF format) available on their web site. For all others, the only way for us to get firmware files, is for a copy to be LEAKED to us.. The "Leaked" firmwares are files that are basically "stolen" by a Motorola or wireless carrier employee, who then posts the file on the internet for us... So we can't always count on this ever happening, nor can we have any expectations that a particular firmware will actually get leaked, or when it will be leaked.
There is some talk about using Motorla Device Manager (MDM) app to upgrade your phone, and how during the update process, the app downloads the full FXZ (another term for SBF) to your PC, so it could be copied/saved to another folder for use later. I have not done this with MDM.
EDIT: As of 12/12/14, Only the filefactory.com link is working. The others appear to be down. I don't know the owners of the sites, so I can't say if they will return or not.
EDIT2: As of 1/2/15, motofirmware.com seems to be back up, but sbf.droid-developers.org appears to be gone.
Great info! ??
SBF is my first choice, but when I needed the 4.4.4 retail firmware not found it in SBF, I had to turn to Google and found it.
FTP of Moto Firmware is empty, but the File Factory folder has many versions! Very cool.
if my firmware is currently 4.2.2, can I download the 4.4.2 or 4.4.4 firmware and it would fix a soft brick with 4.2.2? or must i find the 4.2.2 firmware in order to fix the issues?
x000x said:
if my firmware is currently 4.2.2, can I download the 4.4.2 or 4.4.4 firmware and it would fix a soft brick with 4.2.2? or must i find the 4.2.2 firmware in order to fix the issues?
Click to expand...
Click to collapse
I'm not sure what problem you encountered is.. If it is truely "soft bricked" first start by booting the phone to APFastboot/Booloader screen and use fastboot or mFastboot on the PC to erase the phone's cache then try to reboot.
If that doesn't work, generally to recover from any issues, if you can boot into APFasboot/Booloader, check the version on the second line, then download and flash the appropriate ROM version, you can recovery from most soft brick scenarios.
30.70 = original 4.2.2
30.71 = 4.2.2 OTA with camera update
30.B2 = 4.4
30.B4 = 4.4.2
30.B7 = 4.4.4
Once on 4.4.2, 4.4.3 or 4.4.4, NEVER flash an older version ROM!!!
On occasion, you need to use mfastboot, and do a few extra commands (See Option 5 at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html )
If you have any questions, please search and see if any threads with your phone's symptoms already exist then post in that thread. If a thread doesn't already exist, start a new one, and post any details of what phone you have (model, carrier), what the symptom is, and what was done leading up to the symptom appearing. The more details you can supply the better.
edit: problem resolved. see my findings: http://forum.xda-developers.com/showpost.php?p=57122184&postcount=635
Thanks Kidjoe
x000x said:
well issue was I was rooted with twrp and silly me I tried to do the ota update. so now it won't get past the warning about unlocked bootloader. I read after the fact that you needed to revert back to stock before taking ota. mine is 30.71, but the other issue is I cannot find that firmware anywhere. my only option in regards to firmware is to use 4.4.2 that I found. I've posted the question here http://forum.xda-developers.com/showthread.php?t=2542219&page=123
Click to expand...
Click to collapse
BUT if you tried to take the OTA while TWRP was on your phone, just boot into fastboot mode on the phone, and do a mfastboot erase cache will get you out of the bootloop. Then you can flash stock recovery on there, take the ota.
Or you can just flash the 4.4.2 or 4.4.4 for your phone, when completed, flash TWRP on there, reboot hte phone to bootloader, enter Recovery/TWRP and root.
Yes, You can flash a higher/newer version without problems. You just can't flash older once 4.4.2 or higher has been flashed to your phone. (the only time its safe to flash older was when you had 4.4 on your phone, and you were Following the SlapMyMoto process to downgrade to 4.2.2. W/Camera Update as part of the process).
Thank you for this!
KidJoe said:
I'm not sure what problem you encountered is.. If it is truely "soft bricked" first start by booting the phone to APFastboot/Booloader screen and use fastboot or mFastboot on the PC to erase the phone's cache then try to reboot.
If that doesn't work, generally to recover from any issues, if you can boot into APFasboot/Booloader, check the version on the second line, then download and flash the appropriate ROM version, you can recovery from most soft brick scenarios.
30.70 = original 4.2.2
30.71 = 4.2.2 OTA with camera update
30.B2 = 4.4
30.B4 = 4.4.2
30.B7 = 4.4.4
Once on 4.4.2, 4.4.3 or 4.4.4, NEVER flash an older version ROM!!!
On occasion, you need to use mfastboot, and do a few extra commands (See Option 5 at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html )
If you have any questions, please search and see if any threads with your phone's symptoms already exist then post in that thread. If a thread doesn't already exist, start a new one, and post any details of what phone you have (model, carrier), what the symptom is, and what was done leading up to the symptom appearing. The more details you can supply the better.
Click to expand...
Click to collapse
Getting a Moto X VZW dev ed in a few days, and while it may never apply to me, I had his same question.
I understand what you said, but it doesn't really address the issue of if it is OK to use these images to flash to a later version...
I am aware of the risks of flashing to older firmwares, but are their risks to flashing NEWER updates? I have seen people go as far as to recommend flashing the current version first to recover, then updating... But is this necessary?
scryan said:
Getting a Moto X VZW dev ed in a few days, and while it may never apply to me, I had his same question.
I understand what you said, but it doesn't really address the issue of if it is OK to use these images to flash to a later version...
I am aware of the risks of flashing to older firmwares, but are their risks to flashing NEWER updates? I have seen people go as far as to recommend flashing the current version first to recover, then updating... But is this necessary?
Click to expand...
Click to collapse
U can always flash newer images without a problem. It's flashing older images (downgrading) that's a problem.
scryan said:
I am aware of the risks of flashing to older firmwares, but are their risks to flashing NEWER updates? I have seen people go as far as to recommend flashing the current version first to recover, then updating... But is this necessary?
Click to expand...
Click to collapse
The OTA updates are incremental, so you need to be on a certain level to take them. (to take 4.4.4 you need to be on 4.4.2, to take 4.4.2 you need to be on 4.4, etc)
Full SBF/FXZ files are complete roms. They are not incremental like the OTA Updates are. When flashing a FULL SBF/FXZ you can just flash it, so long as its the same version OR newer than what is on your phone, with no need to "step up." In other words, if you have 4.4 on your phone, you can flash directly to 4.4.4 using the full 4.4.4 SBF, without having to flash 4.4.2 on there first.
The risks to keep in mind would be, just like any update...
If you have a locked bootloader, the vulnerabilities exploited to root and disable write protection might be patched in the newer roms, that means you might not be able to root, or the processes may change for the newer rom. However, with an unlocked bootloader, there is no issue rooting and disabling write protection (lollipop is yet to be confirmed).
In either case, since you can't safely downgrade, if you find bugs, other issues (battery life, reception, etc), or there is something you don't like about the rom, you're stuck, since you can't safely downgrade.
THANK YOU SO MUCH every damn site I went to posted a link to a long dead server LIFE SAVER YOU ARE....
Method to go STOCK.
Hey,I'm currently on CM12/5.0.2 Official ROM for ghost[Bootloader unlocked & I had rooted my device for upgrading to CM12 obviously but now Root Checker says that my device is not rooted].My model number is XT1052(Asia Retail/India).I've found a link(but sadly can't post) for the stock ROM on FileFactory but I don't know the further steps to return back to stock.Before upgrading to CM12/5.0.2 I was on 4.4.4 and since Official 5.0.2 is just right around the corner I'd like to go stock(4.4.4). I'd be highly obliged.I've even downloaded a recovery file as posted by @flasherruts in his thread
"Stock Recovery 4.4.4 XT1052". Will your guide for Returning to stock work for me as well?Sorry but I'm new to this community.
Build Number: KXA21.12-L1.26
System Version:212.44.26.ghost_row.AsiaRetail.en.03
Model Number:XT 1052
Thanks in Advance!
the_fiasco said:
Hey,I'm currently on CM12/5.0.2 Official ROM for ghost[Bootloader unlocked & I had rooted my device for upgrading to CM12 obviously but now Root Checker says that my device is not rooted].My model number is XT1052(Asia Retail/India).I've found a link(but sadly can't post) for the stock ROM on FileFactory but I don't know the further steps to return back to stock.Before upgrading to CM12/5.0.2 I was on 4.4.4 and since Official 5.0.2 is just right around the corner I'd like to go stock(4.4.4). I'd be highly obliged.I've even downloaded a recovery file as posted by @flasherruts in his thread
"Stock Recovery 4.4.4 XT1052". Will your guide for Returning to stock work for me as well?Sorry but I'm new to this community.
Build Number: KXA21.12-L1.26
System Version:212.44.26.ghost_row.AsiaRetail.en.03
Model Number:XT 1052
Thanks in Advance!
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
I suggest you use this : perfect compatible stock firmware for xt1052 asia retail first gen moto x. : http://www.filefactory.com/file/3qr..._4.4.4_KXA21.12-L1.26_18_cid7_CFC_1FF.xml.zip pl. check it with someone else just in case if I'm wrong. pm me if you have any problems
Hey, thanks for replying!
Yeah, I found this stock recovery a while ago and downloaded it and now back to stock 4.4.4. Thanks a lot!
Sent from my Moto X using XDA Free mobile app
@KidJoe since filefactory is really slow, I searched for some alternatives and found some good ones, maybe you could add it to your 1st post?
Really good and fast overview page with most/all files, when you look for something, go here 1st:
https://cloud.mail.ru/public/64a43f0fcc1e/Moto_X or here:
https://cloud.mail.ru/public/a083d0bb5e97/Motorola
Big Thx to OP: http://4pda.ru/forum/index.php?showtopic=514209&st=8360
Some other alternatives:
XT1053 4.4.2; 4.4.3; 4.4.4 (downloading from mega server (fast!)), thx to OP (http://www.grupoandroid.com/topic/110743-aporte-firmware-t-mobile-retail-442/):
TMO_RETAIL_XT1053_4.4.2-KXA20.16-1.25_MR3_CFC.xml.zip: https://mega.co.nz/#!7RJygbQI!Sbx-bGRV8NbRsqLKS-d33nM_SEgY81czr8rye2ROYb0
TMO_RETAIL_XT1053_4.4.3-KXA21.12-L1.21_MR4_CFC.xml.zip: https://mega.co.nz/#!HQ4l2JIT!LD1gf8m2GxBou3NDFD8lzuxSi2OCn37X7Vhbe-hjNqc
TMO_RETAIL_XT1053_4.4.4_213.44.1.ghost_row.Retail.en.US_MR4_CFC.tgz: https://mega.co.nz/#!zIJhlSCS!o9B7xvRSJ9gTCdTYjXdmVActEmdWRBvhIVjs8JUHI8Q
XT1052_RETAIL-EU_4.4.4_KXA21.12-L1.26_54_cid7_CFC_1FF.xml.zip: https://yadi.sk/d/M2H9LMFJbYiag
from mega (fast!):http://www.mega.co.nz/#!jZgjECZT!sG0-9Vqngms551gwv9PfejY1mw_5QCL8Pg48KTVx4m0
XT1052_RETAIL-GB_4.4.4_KXA21.12-L1.26_56_cid7_CFC_1FF.xml.zip: https://yadi.sk/d/KLmLR43SbYiaX
XT1052_RETAIL-DE_4.4.4_KXA21.12-L1.26_54_cid7_CFC_1FF.xml.zip: https://yadi.sk/d/hDEHw2O-bYiae
For Brazilians user's
http://www.motoforum.com.br/topic/4...oto-g-2014-moto-e-moto-maxx-nexus-6-moto-360/
Does anyone know of a link that contains the Rogers 4.4.4 file? I need it to update to 5.1.
I have tried the filefactory link but after the countdown, the file is unavailable. I haven't seen any other links for it.
Thanks
I have the same problem. I've looked everywhere and cannot find the rogers 4.4.4 file.
If anyone has it download, could you please share with us.
Alternatively, would i be able to Flash XT1058_VIVO-BR_4.4.4_KXA21.12-L1.26_59_cid12_CFC_1FF.xml.zip since the build versions are the same?
I only need the 4.4.4 in order to install the Lolipop update.
Thanks
Hello!
I've been searching all around about this problem, but I've not found nothing useful. I hope you can help me.
I downgraded my phone flashing a Custom Rom. Unfortunately I did not backup EFS folder before doing that, because only after I got the problem, I saw that it should have been backed up. Now my phone has a fake IMEI (after I managed to fix it. At the beginning was null/null) and I have no carrier service. It says "Not registered on network" every time I try to make a call. Now I upgraded again to the latest firmware, but still fake IMEI and not registered on network. My question is: is there any possibility to restore my original IMEI? If not, can I get registered on network with a fake IMEI? My phone details are:
Samsung Galaxy S4
Model number: GT-I9500
Baseband Version: I9500ZCUCMH1
Kernel Version: 3.4.5-3943544 [email protected] #1
Build number: LRX22C.I9500XXUHOA7
I hope in your help!
Best regards,
mfo12002
IMEI is no longer stored in the EFS folder but in hidden partitions on the device. Restore your Android 4.2.2 stock ROM and see if your IMEI is restored using that, as your baseband didn't change from Android 4.2.2 though the rest of the firmware did.
I think also my baseband changed when I downgraded it for the first time. Baseband was unknown. Then after I upgraded again, it became the one I posted here. I've also searched in samsung-updates site for stock roms but the problem is I cannot find my region stock rom. Is there any problem if I download a stock rom of a different region?
Best regards,
mfo12002
Please post the following information:
1. Model Number
2. Android Version, found by going to Settings > More > About device.
3. Firmware Version (AP, CP, CSC), found by dialing *#1234# in the dialer or by installing Phone Info from the Play Store and running it.
4. Service Provider
5. Country
6. Is the phone rooted? (Yes/No)
7. Is a custom ROM installed? (Yes/No, and the name of the ROM)
Downloading a ROM from a different region is not a good idea unless the phone is carrier unlocked, so by providing all this information in one post, even if you've already given some of it, will make it easier for me to help.
1. Model Number: GT-I9500
2. Android Version: 5.0.1
3. Firmware Version: AP=I9500XXUHOA7 ; CP=I9500ZCUCMH1 ; CSC=I9500SERHOA7
4. Service Provider: VODAFONE
5. Country: Albania
6. Is the phone rooted: Yes
7. Is a custom ROM installed: I think yes, but I don't know where to find the name.
Try this ROM instead. It's a later version of the one you're currently using. It's unbranded, so you should have no issues with carrier-added bloatware.
It still have the same problem. Not registered on network whenever I try to make a call and the notification "No service. Selected network not available" in the up-left corner.
Unless someone else on the forum has an idea I haven't thought of, have Samsung look at it. The IMEI in your S4 appears to be irretrievably gone.
Strephon Alkhalikoi said:
Unless someone else on the forum has an idea I haven't thought of, have Samsung look at it. The IMEI in your S4 appears to be irretrievably gone.
Click to expand...
Click to collapse
Ok! I will wait a little bit more if someone else has also an idea of what to do and then, if the problem still persist, I will give it to Samsung.
Thank you anyway for your time!
download lastet rom then flash it or use kies emergeny recovery
@shahram Ali: See post #6 in this thread. I directed him to the latest ROM. He flashed it and had no luck.
Does anyone else have an idea on this problem, please?
see this Post I hope it Work
http://forum.xda-developers.com/gal...-downgrade-t3168137/post62097381#post62097381
---------- Post added at 03:03 PM ---------- Previous post was at 03:01 PM ----------
SO...
I went through and followed the instructions word for word of the gentleman in this link:
http://forum.xda-developers.com/p8lite/general/mega-thread-root-unbricking-updating-t3400994
My current Phone info is:
Model- hi6210sft
Build Number ALE-L21C432B551
EMUI-4.0
Android Version-6.0
Now my problem is that in order to make any progress in installing 6.0, I had to install an earlier build as it states in the link above. Now the link I selected for the earlier build number was for single-sim yet for whatever reason my phone is now telling me that I have two sim slots. Which is cool, I don't mind that. My phone has 1 Sim slot an 1 SD slot so thankfully this build didn't mess with my SD slot. Now it was said that downgrading would be followed with an OTA update, however I was not actually able to access an OTA update and the Balong glitch came up with the next upgrade I think. Everything I have done so far has been manual and I am worried that something may be wrong with that. Even now when I check for OTA's it states that no updates are available and yet higher build numbers are available. On top of all this, my region is New Zealand and the region of the current build I'm using is for Europe I believe. Will that be causing any problems? Lack of OTA support? Glitches in general (I have had a few of those with this build of MM, multiple messenger and/or contacts app icons appearing on home screen, themes glitching out and doubling up in the theme store under my downloaded themes menu and the one annoying me most is my camera now no longer taking full screen pictures rather now the image i see in the camera is a box instead of full screen).
Anyway, any tips on what I should do and where I should go for further info, please let me know in the comments. Any assistance is appreciated immensely. I am very new to this whole phone thing but not completely ignorant.
I have also attached some screenshots to show the sort of glitches I mentioned.
Few questions:
1) Are you still on b551?
2) Did you change your oeminfo file (one that changes your region)?
If you're still on b551 and have balongbug issue then head over to b170 (or b052) and apply the vendor update..
If you haven't changed your oeminfo file then you need to change it
https://yadi.sk/d/3eMg8bG0p8pU8 download this file and change it
change where? here's the location : /dev/block/platform/hi_mci.0/by-name
yeah you need to be rooted to change it...
1) Are you still on b551? Yes
2) Did you change your oeminfo file (one that changes your region)? No. Didn't think you could but given you have to be rooted I now know why lol
If you're still on b551 and have balongbug issue then head over to b170 and apply the vendor update.
-The version I upgraded from to get b551 I think had the balong bug. I don't have it anymore thankfully. Spent the past three days reading these forums about all this stuff, sounds like the balong really stuffs people up.
If you haven't changed your oeminfo file then you need to change it.
-If I don't have Balong bug do I still need to change oeminfo file? Or is that so I can get OTA? We don't get a whole lot of OTA stuff in NZ to my knowledge...
On that subject, if the firmware is European then I wouldn't get OTA at all would I? Or is that why changing the oeminfo file is important?
Thanks for responding btw. If I had any thanks thumbs, you earned it
Horacio55555 said:
1) .
If you haven't changed your oeminfo file then you need to change it.
-If I don't have Balong bug do I still need to change oeminfo file? Or is that so I can get OTA? We don't get a whole lot of OTA stuff in NZ to my knowledge...
On that subject, if the firmware is European then I wouldn't get OTA at all would I? Or is that why changing the oeminfo file is important?
Thanks for responding btw. If I had any thanks thumbs, you earned it
Click to expand...
Click to collapse
Oeminfo file changes your region and hence you'll get the OTA's for that region..
Doea your build number show balong or hisoft?
Sent from my ALE-L21 using XDA-Developers mobile app
---------- Post added at 16:06 ---------- Previous post was at 16:05 ----------
amageek said:
Oeminfo file changes your region and hence you'll get the OTA's for that region..
Doea your model number show balong or hisoft?
Sent from my ALE-L21 using XDA-Developers mobile app
Click to expand...
Click to collapse
Sent from my ALE-L21 using XDA-Developers mobile app
So as you probably saw on the other thread, my model number showed hisoft but build came through fine. Something to do with changed made in MM for sure...
I have gone through and started from scratch everything I did and will see how that turns out! I will also seriously look into rooting my device, hopefully i dont brick it after all this work. But i mean... I am in nz and we dont have MM available for p8 lite and from what i hear we wont even get it here. big bummer
Horacio55555 said:
So as you probably saw on the other thread, my model number showed hisoft but build came through fine. Something to do with changed made in MM for sure...
I have gone through and started from scratch everything I did and will see how that turns out! I will also seriously look into rooting my device, hopefully i dont brick it after all this work. But i mean... I am in nz and we dont have MM available for p8 lite and from what i hear we wont even get it here. big bummer
Click to expand...
Click to collapse
I am out of Europe too.. I am from Nepal, Asia.. We dont have MM here too (except in China)...
So don't worry you can do it
Sent from my ALE-L21 using XDA-Developers mobile app
UPDATE!!!
So I attempted last night to downgrade using this guys instructions. http://forum.xda-developers.com/p8lite/general/guide-debranding-converting-single-sim-t3305977
Apparently I botched it up somehow and lost my IMEI file. So I went back to this guys thread.
http://forum.xda-developers.com/p8lite/general/mega-thread-root-unbricking-updating-t3400994
Starting from B133 I worked my way up to B565 Single Sim European Nordic MM firmware using this site. This fixed my lost IMEI file thankfully.
http://www.carbontesla.com/2016/06/...te-b565-marshmallow-update-single-sim-europe/
Still have the Balong bug. As I said last night, I attempted to use a vendor update, which I obtained from the Mega thread linked above (second link), to rectify this but it failed.
For some reason, all these updates I have done also got rid of the ugly Spark Mobile startup screen as well which is nice lol.
If I can get the Balong bug sorted then I will try root. Until then, as always, help is wholly appreciated.
I bought Samsung Galaxy S4 in 2013 back when it was a flagship device, it came installed with Android Jellybean, almost 4 years have passed and it is still stuck at Jellybean. Since then, it didn't got a single update.
I'm not sure what is the latest update for S4 because the updates pushed by Samsung never reach my phone and that is because of baseband version. Other S4's have got quite a few updates till now. In fact, I updated my friend's S4 to Lollipop and my own S4 is stuck at Jellybean.
I visited Samsung website and found that they release updates only for some baseband versions of S4 and that list didn't contain the baseband version of my S4 so it is forever stuck at 4.2.2. Samsung Customer Care says go to service center, they will update your phone manually. I said why should I when I got a flagship phone, it should get updates OTA.
Because my S4 didn't get any update, the same thing must have happened with many other ones and will probably happen with S8 due to launch in 2017. Many of those S8s will never receive any single update.
So is it possible that baseband version can be changed and I switch to the one that gets update? There is always an option to flash a custom ROM but if I get an official update to Lollipop, I will be happy.
Before the Samsung update reaches your phone it has to pass through the carrier's hands first, where they add their crappy bloat.
In other words, if there's no update, then it's probably your carrier's fault.
You could update manually with Odin.
Pwnycorn said:
Before the Samsung update reaches your phone it has to pass through the carrier's hands first, where they add their crappy bloat.
In other words, if there's no update, then it's probably your carrier's fault.
You could update manually with Odin.
Click to expand...
Click to collapse
I am from India so no system of carrier here.
Umm, you guys in India have cellular networks. Those are the aforementioned carriers. They may not add any bloat, but they do have to test the updates first before releasing them to the devices. This is to ensure the update doesn't cause unwanted problems on the network. However, we're heading into 2017, and after all this time you should have received an update to Android 5.0.1. So let's verify that you have a model intended for India. Please enter download mode and read off the model number at the top left corner of the screen.
Changing the baseband will not automatically get you a ROM update. If you want an updated ROM for your phone, I suggest updating to the latest bootloader and modem, flash TWRP, and then flash a custom ROM.
Strephon Alkhalikoi said:
Umm, you guys in India have cellular networks. Those are the aforementioned carriers. They may not add any bloat, but they do have to test the updates first before releasing them to the devices. This is to ensure the update doesn't cause unwanted problems on the network. However, we're heading into 2017, and after all this time you should have received an update to Android 5.0.1. So let's verify that you have a model intended for India. Please enter download mode and read off the model number at the top left corner of the screen.
Click to expand...
Click to collapse
Here is the correct firmware version of my device: sammobile.com/firmwares/download/14242/I9500XXUAMDK_I9500ODDAMDK_INU
Sam Mobile is not displaying Android version, if you look at sammobile.com/firmwares/database/GT-I9500/INU, my device PDA and CSC versions are second from last. But if you look at other S4s in the same list, most of them got Android 5.0.1 so can't I just download any one of them and flash it using Odin?
You're looking on the wrong page. Individual ROM pages do not display the Android version, but the full list does, where that information is applicable. In your case, the ROM you linked to doesn't have a version number, but also happens to be the ROM originally on the device, based upon the PDA and CSC. Check here. Not only does it tell you the version, but tells you the date it was posted. The one you want will be at the top of the list, as it's the latest available for your device.
Strephon Alkhalikoi said:
You're looking on the wrong page. Individual ROM pages do not display the Android version, but the full list does. Check here. Not only does it tell you the version, but tells you the date it was posted. The one you want will be at the top of the list, as it's the latest available for your device.
Click to expand...
Click to collapse
I also posted the same link as yours, just scroll to the very bottom, there are 2 entries that doesn't display the Android version and one of them is mine - second from last. The PDA and CSC matches my device.
PDA - I9500XXUAMDK
CSC - I9500ODDAMDK
Well, you might want to reread my post, as I edited it while you were typing.
Anyway, in post 6, this is the link you provided: sammobile.com/firmwares/download/14242/I9500XXUAMDK_I9500ODDAMDK_INU
This is mine: sammobile.com/firmwares/database/GT-I9500/INU/
Big difference.
The link you provided takes you directly to that particular ROM. The link I provided takes you to every ROM available for that device using the CSC of INU. Based upon your opening post, you're looking to update to the latest ROM. However, you are getting hung up because the ROM you currently have on your device doesn't have a date. It doesn't matter how old your ROM is! The latest version for your device will always be at the top of the database page, i.e. the link I provided in post 7. Thus, as of this moment, the ROM you want is here. Download it, flash it via Odin, and you're done.
Strephon Alkhalikoi said:
Well, you might want to reread my post, as I edited it while you were typing.
Anyway, in post 6, this is the link you provided: sammobile.com/firmwares/download/14242/I9500XXUAMDK_I9500ODDAMDK_INU
This is mine: sammobile.com/firmwares/database/GT-I9500/INU/
Big difference.
The link you provided takes you directly to that particular ROM. The link I provided takes you to every ROM available for that device using the CSC of INU. Based upon your opening post, you're looking to update to the latest ROM. However, you are getting hung up because the ROM you currently have on your device doesn't have a date. It doesn't matter how old your ROM is! The latest version for your device will always be at the top of the page. Thus, as of this moment, the ROM you want is here. Download it, flash it via Odin, and you're done.
Click to expand...
Click to collapse
Thanks! By the way, I did post 2 links, it's just that because I don't have a total of 10 posts, I can't post link so the second link(in plain text) isn't easily spotable but it is there and it is same as yours. Check after "Sam Mobile is not displaying Android version"
Obvious link was not obvious. You're right.
Strephon Alkhalikoi said:
Obvious link was not obvious. You're right.
Click to expand...
Click to collapse
I've downloaded firmware from the link you provided, flashed it via ODIN and now my S4 is successfully running 5.0.1, thanks a lot! Need one more help from you - I didn't perform factory reset, I directly flashed the firmware and now only 2 things have changed on my phone - root status and android version. Root is now gone and that's what I wanted, Android version has also changed but all my files, data and apps are same; no single app got deleted, all are exactly same as before so do I need to perform a factory reset and wipe cache?
If you haven't encountered any bugs or app crashes, I don't think a factory reset is needed.