Dear friends, i invite all of us to discuss this sore subject in a separate toric., and here's what so far I managed to find out.
My flashed Chinese device XQ-BC72 (flashed to Russian f/w) stopped getting OTA updates. Without thinking twice i flashed back device`s native Chinese f/w and after that OTA update was immediately recieved by my device (i flashed Chinese .31 f/w).
So how I managed to figure out, OTA update service is not breakes forever, it`s restored after flashing f/w with device`s native region.
Let's think together now how to fix it.
I'm wondering, if this could be because of Newflasher doesn`t flash persist.sin in new versions, and the traces of the firmware of its native region remain in the device ? I know that persist delete some verification keys and certificates, but, maybe, OTA service will remain ofter FULL f/w flashing with persist.sin file ?
What do you think ?
And one more the most important question !
DOES ANYONE FINALLY GOT THE OTA UPDATE ON ANY REFLASHED DEVICE ???
I MEAN REFLASHED FROM YOUR NATIVE F/W TO ANY ANOTHER ONE !
IS THERE AT LEAST ONE SUCH CASE ????
Same here, flashed SEA firmware with no OTA received now.
It's interesting that somebody reports that software version in software info (Dial #*#*7378423*#*#) shows GLOBAL-C2 after flashing, though mine is still SEA-C2 which matches my firmware version. Not sure if this related to the issue.
i7killpii said:
Same here, flashed SEA firmware with no OTA received now.
It's interesting that somebody reports that software version in software info (Dial #*#*7378423*#*#) shows GLOBAL-C2 after flashing, though mine is still SEA-C2 which matches my firmware version. Not sure if this related to the issue.
Click to expand...
Click to collapse
Global C2 - Hong Kong. There are two ways for you to see Global C2 in software info is to flash HK f/w or to buy the device from HK.
Didn't have this device but would like to ask you guys, If the OTA is dead then is the "check update" option in Xperia Companian still work or not?
Persist.sin shouldn't have anything to do with it. I always delete them before flashing with older models using both Flashtool and Newflasher and it never breaks OTA.
Wonder if this issue could be related to a bootloader bug in this device that many people here encountered a bootloop when finished flashing and had to mess with active partition slot to get fixed? I remembered that the a/b partition slot is related to system update and OTA too.
Nimda01 said:
Didn't have this device but would like to ask you guys, If the OTA is dead then is the "check update" option in Xperia Companian still work or not?
Persist.sin shouldn't have anything to do with it. I always delete them before flashing with older models using both Flashtool and Newflasher and it never breaks OTA.
Wonder if this issue could be related to a bootloader bug in this device that many people here encountered a bootloop when finished flashing and had to mess with active partition slot to get fixed? I remembered that the a/b partition slot is related to system update and OTA too.
Click to expand...
Click to collapse
I think you are right, if the new flasher only flash to slot a (so that we need to set a to be active) then OTA update is not available since the update will be to slot b which is a different version of software. We can verify this by using the new flasher twice once for slot a (set a active) and once for slot b (set b active). Just a guess, it might destroy your phone!
I bought my Xperia 1 iii from Hong Kong (XQ-BC72), and used newflasher to flash the software of the US version of the device thinking that it may solve the issue of not having 5G working and VOLET in my country, Saudi Arabia.
Unfortunately nothing changed, so I decided to re-flash the original software of the device HK (61.0.A.11.92).
Now, I get the OTA software update as you can see in the attachments, but it stops immediately after beginning of the installation process.
I hope this is beneficial information and let's all work to try to find a solution for this issue.
{
"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"
}
Mansour Nejer said:
I bought my Xperia 1 iii from Hong Kong (XQ-BC72), and used newflasher to flash the software of the US version of the device thinking that it may solve the issue of not having 5G working and VOLET in my country, Saudi Arabia.
Unfortunately nothing changed, so I decided to re-flash the original software of the device HK (61.0.A.11.92).
Now, I get the OTA software update as you can see in the attachments, but it stops immediately after beginning of the installation process.
I hope this is beneficial information and let's all work to try to find a solution for this issue.
View attachment 5421925
View attachment 5421923
View attachment 5421921
View attachment 5421919
Click to expand...
Click to collapse
Hmmm...
Well, when i found out that OTA system stop working on non-native f/w, i re-flashed my device to it native China f/w, and after that it recieved OTA update immediately after i started flashed device and set it up, and update installed with no problem then.
Now my device is still on that f/w ....92, and it`s not recieved new update yet (...14.3) , when the phone will get this update, i`ll try to install it as usual, and i`ll report how did everything go, hope it will work well.
You know what, try to restore your device with Xperia Companion, i did so. Maybe OTA not working well because of changed slot (you changed it before flashing, right ?), and when you recover your device with Companion, maybe it will set all by default as it is necessary for everything to work correctly
[email protected] said:
I think you are right, if the new flasher only flash to slot a (so that we need to set a to be active) then OTA update is not available since the update will be to slot b which is a different version of software. We can verify this by using the new flasher twice once for slot a (set a active) and once for slot b (set b active). Just a guess, it might destroy your phone!
Click to expand...
Click to collapse
Already tested that flashing without changing to slot A will brick the phone. When my device was flashed Russian version of f/w, which is NOT native for my device, i tried to change the slot from A to B, and i did it, but after that all still the same, device didn`t get OTA updates.
So i had to reflash China rom again, and restored after that device with XC.
DennisDD78 said:
Hmmm...
Well, when i found out that OTA system stop working on non-native f/w, i re-flashed my device to it native China f/w, and after that it recieved OTA update immediately after i started flashed device and set it up, and update installed with no problem then.
Now my device is still on that f/w ....92, and it`s not recieved new update yet (...14.3) , when the phone will get this update, i`ll try to install it as usual, and i`ll report how did everything go, hope it will work well.
You know what, try to restore your device with Xperia Companion, i did so. Maybe OTA not working well because of changed slot (you changed it before flashing, right ?), and when you recover your device with Companion, maybe it will set all by default as it is necessary for everything to work correctly
Click to expand...
Click to collapse
Thank you for the advice... I will try to restore via Companion and report back to you if this solve my problem..
Mansour Nejer said:
Thank you for the advice... I will try to restore via Companion and report back to you if this solve my problem..
Click to expand...
Click to collapse
Good luck !
But you`ll not be able to check OTA untill next month, when next OTA update will roll out, right ?
DennisDD78 said:
Good luck !
But you`ll not be able to check OTA untill next month, when next OTA update will roll out, right ?
Click to expand...
Click to collapse
Thank you my friend.. Xperia Companion repair solved my problem and the new update installed on my phone now, but I guess you are right... I need to wait until the next update to see if OTA works...
Mansour Nejer said:
Thank you my friend.. Xperia Companion repair solved my problem and the new update installed on my phone now, but I guess you are right... I need to wait until the next update to see if OTA works...
Click to expand...
Click to collapse
Please feed me back on this next month if it`s not difficult for you and if you won`t forget
Today, I still can't update the software via OTA, I'm using China BC-72, however switched to SEA. i fixed it by Sony companion but my device was reset to chinese firmware
DennisDD78 said:
Already tested that flashing without changing to slot A will brick the phone. When my device was flashed Russian version of f/w, which is NOT native for my device, i tried to change the slot from A to B, and i did it, but after that all still the same, device didn`t get OTA updates.
So i had to reflash China rom again, and restored after that device with XC.
Click to expand...
Click to collapse
Did you actually flash to both slot A and B since I try the fastboot command to change slot I was not successful. The change slot command failed due to locked bootloader.
Friends, does anyboby knows exactly what`s happening with OTA sytem when device reflashed on non-native f/w ? What exactly breaks down in the device firmware ???
We tried an experiment, flashed Chinese device BC72 with Russian f/w on both slots, A, and then B, when active A, system boots, but no OTA recieved after that. When we set active B, then logo + bootloop. I repeat, f/w was flashed on both slots! When we returned slot A as active, device boots great, but still NO OTA.
HOW WE CAN FIX IT ?!
So far no success getting OTA after flashing different firmware. But i just update using new flasher so that i can enjoy the new patch and so far working for me. My data and settings are still intact so i think as of now this is the best solution. Mine originally china convert to SEA firmware..
spine6 said:
So far no success getting OTA after flashing different firmware. But i just update using new flasher so that i can enjoy the new patch and so far working for me. My data and settings are still intact so i think as of now this is the best solution. Mine originally china convert to SEA firmware..
Click to expand...
Click to collapse
me too exactly same as you cn flash over with SEA. do you update by just flash new flasher on top. Use flash all? or i need to delete something in order to not wipe data?
tanipat said:
me too exactly same as you cn flash over with SEA. do you update by just flash new flasher on top. Use flash all? or i need to delete something in order to not wipe data?
Click to expand...
Click to collapse
You need to delete 4 files so that it will be ome like OTA update, files are safe
spine6 said:
You need to delete 4 files so that it will be ome like OTA update, files are safe
Click to expand...
Click to collapse
is there a guide on XDA available to change region flash and keep files intact?
I would like to get SEA on my HK BC72.
Related
Hello, sorry for my long absence. Now I'm updating this thread as I do not have the time to create the firmwares. So the objective of the thread is:
To give simple instructions on how to create your own firmware. I am going to assume that you already know how to:
1. Read and follow instructions.
2. Change extensions of files.
3. Extract files.
4. Use the flashtool.
5. Create a .tft file.
If you answer no to any of this questions, please investigate a little or do not attemp to do this.
Now, the instructions:
1. Go to this website http://www.omnius-server.com/ and register.
2. Now that you have registered and logged in, go to this link http://www.omnius-server.com/downloads?id=58117. You should get 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"
}
3. Now search for the firmware you are looking for in any of the folders. I'm going to choose the folder R1FA016, and the file X10a_CLARO_GT_NAM1_1234_4844.rar. But it is going to work with any.
4. Now download it and create a new folder on the firmware folder of the flashtool and put it on there. Extract it and you should get two .rar files (if not, just change the extension to .rar). Extract them both on the same folder. You should get a lot of .sin files and a .xml file.
5. Now you have to rename some files with a name like this:
5.1. This one: "system_S1-SW-LIVE-AC12-0001-S1-PARTITION-WITH-SPARE.sin" to "system.sin"
5.2. And this one: "userdata_S1-SW-LIVE-AC12-0001-S1-PARTITION-WITH-SPARE.sin" to "userdata.sin"
Now you have a list of files like this: (the files that you have to change the name can vary depending on the firmware but the part you have to delete is going to be te same (_S1-SW-LIVE-AC12-0001-S1-PARTITION-WITH-SPARE), for example, so be sure to take a look to the picture if you are not so sure how a name should be)
6. Now create the .tft bundle and flash it.
7. Enjoy the phone with the firmware you created.
If this was helpful for you click on the THANKS button.
P.S.
I'm not responsible for any damage you do to your phone.
If you are going to take the time to create all the firmwares, give me the appropiate credit .
Sorry for my english if there is any mistake, I speak spanish.
If you have any sugestion you can PM me and I will be happy to help.
HTML:
Thank you for this!! I didn't have the Claro Guatemala firmware and I needed it for warranty purposes...
Sent from my AOSP on Xperia (GT)
Is it possible to have the Vodafone branded ROM for The Netherlands?
I've made a backup before I did the Nordic 2.1 update, but for some reason I can't use it with the above...
I'm getting an "Unable to open channel, GetLastError=0" message after pressing option 1 and connecting the X10 in flash mode...
I'm using Windows 7 Ultimate 32-bit with JRE and JDK 6u23 installed...
DaDude1973 said:
Is it possible to have the Vodafone branded ROM for The Netherlands?
I've made a backup before I did the Nordic 2.1 update, but for some reason I can't use it with the above...
I'm getting an "Unable to open channel, GetLastError=0" message after pressing option 1 and connecting the X10 in flash mode...
I'm using Windows 7 Ultimate 32-bit with JRE and JDK 6u23 installed...
Click to expand...
Click to collapse
If you get this error you have added WRONG device ID. Maybe you have not only ONE in registry. Try finding another one! If that doesn't work, please install SEUS one time, via SEUS put your phone in Flash Mode and the unplug it; that way SEUS will install the drivers and you'll have your DEVICEID, then go to the notepad called "DEVICEID" and put it in there. Try Reflashing again.
Let me know if this help you.
jimbo77 said:
If you get this error you have added WRONG device ID. Maybe you have not only ONE in registry. Try finding another one! If that doesn't work, please install SEUS one time, via SEUS put your phone in Flash Mode and the unplug it; that way SEUS will install the drivers and you'll have your DEVICEID, then go to the notepad called "DEVICEID" and put it in there. Try Reflashing again.
Let me know if this help you.
Click to expand...
Click to collapse
Thanks, but I've tried to find another DeviceID and can find only one, even if I use another USB port on my laptop...
I'm now installing SEUS, maybe that's the solution...
It's installing JRE also, so maybe the JRE version I've installed wasn't the good one?
Will let you know, thanks!
I'm now uploading the vodafone NL firmware. Just wait for it.
Yes! Seems to be working now, I see a lot of INFO: write commands on my screen!
Thanks for your help, hope to get the Vodafone branded 1.6 rom back again so I can upgrade to the Vodafone 2.1 branded rom, thanks!
oalf170892 said:
I'm now uploading the vodafone NL firmware. Just wait for it.
Click to expand...
Click to collapse
Thanks for the quick response!
DaDude1973 said:
Yes! Seems to be working now, I see a lot of INFO: write commands on my screen!
Thanks for your help, hope to get the Vodafone branded 1.6 rom back again so I can upgrade to the Vodafone 2.1 branded rom, thanks!
Click to expand...
Click to collapse
You're welcome pal..!! Let us know if that helped you and probably you can help us with a small donation
Have a great Day!
jimbo77 said:
You're welcome pal..!! Let us know if that helped you and probably you can help us with a small donation
Have a great Day!
Click to expand...
Click to collapse
Donation will certainly be done if everything works!
Have a great day too!
Thanks again...
Firmware you wanted is uploaded
There you go... now just download and follow the steps.
DaDude1973 said:
Donation will certainly be done if everything works!
Have a great day too!
Thanks again...
Click to expand...
Click to collapse
Yes! This really worked for me, I was back on the Vodafone branded 1.6 ROM and I'm now updating to the Vodafone branded 2.1 ROM as we speak!
You guys rock!
Donation will be made soon, I first have to update my own paypal account...
I also will tweet this page to my Twitter and Facebook, so you will get more traffic I hope!
Thanks again!
oalf170892 said:
for cases in wich you flashed a firmware on your x10 that isn't from your country or operator, and now your operator has released the 2.1 update (still not my case), and you want to run your operators firmware in case of any incident with your phone.
Click to expand...
Click to collapse
If you have 2.1 already and your network has also released it, you can use - [TUTORIAL] -Simple way to switch from one 2.1 version to another - to save having to flash twice.
XperiaX10iUser said:
If you have 2.1 already and your network has also released it, you can use - [TUTORIAL] -Simple way to switch from one 2.1 version to another - to save having to flash twice.
Click to expand...
Click to collapse
Yes, that is working, but you have to root your phone to acomplish that, and if your phone is rooted, you have lost all waranty both Sony Ericsson and your Operator. And over that, all the custom of your Operator is not going to be on your phone.
Thats why flashing 2 times isn't that hard to gain waranty back.
DaDude1973 said:
Yes! This really worked for me, I was back on the Vodafone branded 1.6 ROM and I'm now updating to the Vodafone branded 2.1 ROM as we speak!
You guys rock!
Donation will be made soon, I first have to update my own paypal account...
I also will tweet this page to my Twitter and Facebook, so you will get more traffic I hope!
Thanks again!
Click to expand...
Click to collapse
Is nice to hear that you have now your 2.1 android vodafone costume version.
And remember if this is working for you Recomend and Donate.
Enjoy your x10!!!
oalf170892 said:
Yes, that is working, but you have to root your phone to acomplish that, and if your phone is rooted, you have lost all waranty both Sony Ericsson and your Operator. And over that, all the custom of your Operator is not going to be on your phone.
Thats why flashing 2 times isn't that hard to gain waranty back.
Click to expand...
Click to collapse
Perhaps you've missed the point, that method allows you to flash a branded rom back to the phone via SEUS, so once you flashed, you've lost root and got a branded rom back on the phone.
Firmware Movistar 016 España
I uploading the link for flash firmware donut Movistar Spain.
http://www.megaupload.com/?d=3O33P3H7
question Device ID
just a quick question the devices id number is the same number as when you in cmd adb device listing??? thanx
vinny.1967 said:
just a quick question the devices id number is the same number as when you in cmd adb device listing??? thanx
Click to expand...
Click to collapse
Look, for the Device ID you should have something like this "5&34B1332A&0&5". I can't answer your question because i have never use adb.
But, to get your Device ID, before coping the firmware files to firmware_1, open it and run the x10flash and conect your x10 in flash mode, and a new file named DeviceID.txt ahould have been created. Open it and you should have your Device ID.
Hope to be Helpful
vinny.1967 said:
just a quick question the devices id number is the same number as when you in cmd adb device listing??? thanx
Click to expand...
Click to collapse
This is hoe you can get your DeviceID on Windows...
1: press start (or windows icon) and in the run box type "regedit" without the ""
2: click edit>find, and type in "Vid_0fce&Pid_adde". You should find "DeviceInstance". Copy the last section of that, it should look something like "5&2888d0ff&0&1" 2.1: If that fails to see anything, make sure "Match whole string" is un-ticked, and click "find next", if that fails, try "USB\VID_0FCE&PID_ADDE" Note: It changes with every diffrent USB port you use....
I hope this helps to clarify..
Sent from my X10i
I went to software update and there is a 197mb update on my phone then i started to download and it downloaded just fine but after rebooting it is failed always at 12% and meesage comes up " update through kies or contact samsung"... on kies there is no update.
My phone is not rooted.S II I9100 from KSA.
anyone?
This is what exactly going on
http://www.youtube.com/watch?v=gHkU_57zmlM&feature=player_embedded
Assuming you're running stock & have never messed with (rooted/run non stock firmware) the phone, try a factory reset/wipe in the first instance (boot into recovery), then try the update again.
You could flash a stock ICS rom manually with Odin, but be aware if you bork it in the process (very unlikely/small risk, but still a risk nonetheless), you'll likely not get it fixed under warranty. Get the PC version of Checkfus if you want to go down this route (search for it on here/Google), this will enable you to download the update manually, then flash it following the instructions here.
Ton need at least 40% to install an update.
MistahBungle said:
Assuming you're running stock & have never messed with (rooted/run non stock firmware) the phone, try a factory reset/wipe in the first instance (boot into recovery), then try the update again.
Click to expand...
Click to collapse
actually i have rooted my phone before 2 months but now it is not rooted... i just want to install official ICS using kies or through OTA ...don't want to root again.
Then take your pick. Do the reset & try it again (make sure you've got at least 40% battery; I think that's what JT meant), or do it manually with Odin. Or try the first option, then the 2nd one.
Up to you.
Also, if you can't find the firmware you need with Checkfus, search Samfirmware or here
Edit after your edit - In that case definitely the first option. If it doesn't work & you don't want to do it manually, take it to a Samsung service centre & ask them to put the latest firmware on it for you.
MistahBungle said:
Then take your pick. Do the reset & try it again (make sure you've got at least 40% battery; I think that's what JT meant), or do it manually with Odin. Or try the first option, then the 2nd one.
Up to you.
Also, if you can't find the firmware you need with Checkfus, search Samfirmware or here
Edit after your edit - In that case definitely the first option. If it doesn't work & you don't want to do it manually, take it to a Samsung service centre & ask them to put the latest firmware on it for you.
Click to expand...
Click to collapse
Ok, after reseting there is no update available on my phone when i try to update using phone.
OK. Have you ever flashed any other stock firmware on the phone ? I have two theories about this 'upgrade' - one; if you've flashed stock firmware for other regions on your phone, there's may be some issue with the CSC (even if you're currently running correct firmware for your region) preventing you from getting OTA updates successfully. Also, the update you saw may have been not for your region, because your CSC is messed up , it may have tried to pull an update for the region whose firmware you had on the phone previously. And when you did a reset it might have somehow fixed the issue with the CSC, and there is no update for your region. Conjecture, but hard to know exactly without knowing the history of the phone & exactly what you've done it.
Two; the size of the update sounds a bit strange. I would have thought it would be bigger than 197MB. Even zipped, I have a carrier branded ICS firmware and it's huge (>700MB). That you were able to download it, yet there was nothing on Kies is really strange.
Go into settings/about phone & tell me all the details you have in there. Also tell me everything you've done with the phone since you got it so far as rooting/flashing other firmware goes (details of kernels, roms, etc). And we'll see if we can shed a bit more light on things.
And one other thing, in your last post you say there's no update on the phone, have you checked Kies again. If not, have a look.
MistahBungle said:
it may have tried to pull an update for the region whose firmware you had on the phone previously. And when you did a reset it might have somehow fixed the issue with the CSC, and there is no update for your region. Conjecture
Click to expand...
Click to collapse
This might be true
Go into settings/about phone & tell me all the details you have in there
Click to expand...
Click to collapse
.
I bought S2 from Saudi Arabia.
baseband version: I9100XXKI4
Kernal Version: 2.6.35.7-I9100JPKJ2-CL655700 [email protected] #2
GBuild Number: GINGERBREAD.JPKJ2
]Also tell me everything you've done with the phone since you got it so far as rooting/flashing other firmware goes (details of kernels, roms, etc). And we'll see if we can shed a bit more light on things.
Click to expand...
Click to collapse
I have used this guide for rooting http://androidforums.com/galaxy-s2-...t/482994-rooting-galaxy-s2-dummies-guide.html
but after trying 5 or 6 custom ROMS i just unroot my phone.
And one other thing, in your last post you say there's no update on the phone, have you checked Kies again. If not, have a look.
Click to expand...
Click to collapse
no update on kies either.
I have also used this method toinstall official stock firmware http://www.technetinfo.in/mobile/mobile-software/stock-gingerbread.html
let me quote my own message while i was having problem with CSC.
k i did factory reset and wipe all data now it doesn't show "that device doest not support software upgrading via KIES" but firmware info is totally different now, it is suppose to be (KSA) not (XSG).
Click to expand...
Click to collapse
one thing more i would like to mention here is that before rooting....KIES showing
PDA:KJ2 / PHONE:KI4: / CSC KJ1 (KSA)
now it's showing
PDA:KJ2 / PHONE:KI4: / CSC KJ1 (XSG)
Click to expand...
Click to collapse
FIXED BY CHANGING CSC CODE
OK. Given all that, then it's obviously a CSC issue. Which means either it showed an update was available for the wrong region, and now that CSC issue has been resolved. Or there is an update for your region but your CSC is messed up so it can't get the update.
I've had a look at Checkfus, and the stock rom you're currently running is the latest for Saudi Arabia (GT-I9100LKAKSA -I9100JPKJ2/I9100OJPKJ1/I9100XXKI4/I9100JPKJ2) which was released on 25/10/2011.
So I'd say that update you saw was for another region, and the factory reset you did fixed whatever issue there was. There are no updates for your region, put it that way.
Edit - Unless it's some kind of minor carrier specific update ? That could explain the relatively small size of the one you saw. I guess you could find this out by contacting your carrier.
Thanks a lot MistahBungle, i really appreciate your help.
Now i have changed my CSC code from (KSA) to (JED) and now i'm getting official update from kies. Just curious about changing CSC, is there any negative effect on my phone in future by just changing CSC code?
Given you're getting OTA updates OK, probably not. Normally if you change your CSC to a different region, you often have problems getting OTA firmware updates. If it's working for you, it's obviously fine.
MistahBungle said:
Given you're getting OTA updates OK, probably not. Normally if you change your CSC to a different region, you often have problems getting OTA firmware updates. If it's working for you, it's obviously fine.
Click to expand...
Click to collapse
not sure about OTA but on KIES it is showing my firmware info correctly, i mean i can get updates through KIES without any issues.
suppose if i want to change my CSC back to original one (KSA) then what will happen?
As long as you can get it via Kies you're set. And even if you couldn't, it's simple to download the firmware with Checkfus & flash it via Odin. That's what I'd do if I were on rooted stock, for example (but I probably wouldn't be in any event).
I don't know. Try it & find out. Yes, I'm serious. I hate stock firmware, it's rubbish, and haven't run it since the first week I got my phone. So I honestly don't know.
Hello all,
I was trying to update touch firmware using *#2663#.
TSP FW Update and Touch key FW update was successful.
But failed 1. S-PEN FW Update(UMS) and 2. S-PEN FW Update(Kernel).
Now I my S-PEN is not working, also is not detected by the phone.
For solving the issue I flashed stock ROM, wiped all data and cache.
Also tried to update FW again from older stock ROM same way but nothing worked at all.
Please help me. How can I downgrade Touch, TSP and S-PEN FW?
{
"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"
}
Hmm there is a new one.
My first note randomly stopped detecting s-pens the second day I had it.
I thought it was the pen, but no other pen in the store would work either, so they swapped me phones.
If you are on bones stock, I would try an emergency update in kies.
If that doesn't work, Since you were Trying something official, and not some custom pen firmware, this might be covered under your warranty.
studacris said:
Hmm there is a new one.
My first note randomly stopped detecting s-pens the second day I had it.
I thought it was the pen, but no other pen in the store would work either, so they swapped me phones.
If you are on bones stock, I would try an emergency update in kies.
If that doesn't work, Since you were Trying something official, and not some custom pen firmware, this might be covered under your warranty.
Click to expand...
Click to collapse
Thanks for your help.
I tried many ways but could not 'emergency update' via kies.
My s-pen FW in IC: 0xFF. But I checked in my friend's phone where it is not same value.
s-pen FW can be updated from: /sdcard/firmware/wacom_firm.bin (found in: kernel\drivers\input\touchscreen\wacom_i2c.c).
but where can i get the file?
Any help from any one?
kamrul045 said:
Thanks for your help.
I tried many ways but could not 'emergency update' via kies.
My s-pen FW in IC: 0xFF. But I checked in my friend's phone where it is not same value.
s-pen FW can be updated from: /sdcard/firmware/wacom_firm.bin (found in: kernel\drivers\input\touchscreen\wacom_i2c.c).
but where can i get the file?
Any help from any one?
Click to expand...
Click to collapse
Kies will see the device only if the recovery is stock...and the flash counter is "0"...
You can flash the 3e stock recovery .zip to the device, followed by the flash counter reset .zip..then reboot..and then kies will see the device to perform the emergency restore.
Beyond factory firmware and recovery, if the device fails to perform using s-pen, then you may have partition corruption.
The flashes would be reversed.
If you flashed 3e first you can't flash the reset zip in stock recovery.....
Reset then stock recovery.
studacris said:
The flashes would be reversed.
If you flashed 3e first you can't flash the reset zip in stock recovery.....
Reset then stock recovery.
Click to expand...
Click to collapse
Problem still exist. No luck.
If you have formatted and installed the official build and the problem persists... could simply be your s-pen is broken or..like my first one, have a hardware defect that won't detect the pen.
I see no issue with warranty exchange of it's the latter... running official software only points to a few things. Only 1 of which would be your fault.... water damage.
Would reflashing the rom via odin work...maybe downgrade downgrade to gingerbread then upgrade bk to ics???
sent from my n7005 well actually i717 its jus the rom im on
My s-pen is no working. Galaxy Note SHV-E160S.
Hello.
My S-pen is not working.
I was trying to update touch firmware using *#2663#.
Please help me. How can I repair my S-PEN FW?
Did you make any operating system backup before you started experimenting?
Restore that, or back up your important crap and do a factory reset.
rangercaptain said:
Did you make any operating system backup before you started experimenting?
Restore that, or back up your important crap and do a factory reset.
Click to expand...
Click to collapse
factory reset will not work this is something related to wrong or bad partition. i also tried several methods but 0xff remains the same. i think jtag will be the only way to get re partition.
I have the same problem... Help
kamrul045 said:
Hello all,
I was trying to update touch firmware using *#2663#.
TSP FW Update and Touch key FW update was successful.
But failed 1. S-PEN FW Update(UMS) and 2. S-PEN FW Update(Kernel).
Now I my S-PEN is not working, also is not detected by the phone.
For solving the issue I flashed stock ROM, wiped all data and cache.
Also tried to update FW again from older stock ROM same way but nothing worked at all.
Please help me. How can I downgrade Touch, TSP and S-PEN FW?
View attachment 1603119
Click to expand...
Click to collapse
I have the same problem with my Korean Shv-e160s.
Did You repair yours? Please help me...
I have the updates
S-pen IC 0xFF
Kernel image 0x20A
Thanks.
Did anybody able to fix this problem? I'm having the same issue with my E160L.
I hope anyone can help us.
kamrul045 said:
Hello all,
I was trying to update touch firmware using *#2663#.
TSP FW Update and Touch key FW update was successful.
But failed 1. S-PEN FW Update(UMS) and 2. S-PEN FW Update(Kernel).
Now I my S-PEN is not working, also is not detected by the phone.
For solving the issue I flashed stock ROM, wiped all data and cache.
Also tried to update FW again from older stock ROM same way but nothing worked at all.
Please help me. How can I downgrade Touch, TSP and S-PEN FW?
View attachment 1603119
Click to expand...
Click to collapse
spen not working
same issue with n7100 wot to do I m facing issue during update wacom kernel binary failed
spen not working
my note 2 spen not working even I have checked with my frnds note 2 spen not working my spen working fine with frnds note 2 ...
I check and tried with code *#2663# and my phone shows
FW Version of WACOM IC : 0000
FW Version in kernel image : 0268
my frnds note 2 which is also on 4.3 default everything shows
FW Version of WACOM IC : 0268
FW Version in kernel image : 0268
I m on default rom 4.3 everything is default hope so it will b not hardware issue.....
I tried to update both Wacom fw update successfully but Wacom fw update (kernel Binary) gives error failed to update after 1 min....
please suggest some one said it corrupt kernel spen partition error???
when I in or out spen menu open but spen not working......
same problem
I have the same problem in my shv-e160l. I try to flash a stock rom, hard resets and the problem continues. Someone has solve it?
Stylus not working
I have the same problem. can anyone help please!
S-Pen FW Update fail
Did any body get the solution about the S-Pen Driver?
My Note1 version is SHV-E160L
I did the same foolish thing ( typed code #*2663#, and pressed all the buttons one by one to activate the touch buttons which were disabled after custom rom,
touch buttons became active but the last two options failed to update and S-Pen which was functional before this process became inactive
and now the situation is
FW Version of S-Pen IC: 0xFF
FW Version in Kernel Image: 0x370
I am stuck at this point,
I got my phone to JTag while trying to activate the spen, trying different kernels,
and after resuming the phone by JTag I am still in the same situation,
In repair shop they replaced the touch Screen to verify that if it is a hardware issue but the pen did not respond to other screen either,
I have checked the stylus on other note, it is fully functional, it also worked on note2,
Can anybody solve this problem?
Thanks in advance
Wow........... This hasn't been solved yet?? Same boat here. This is stupid.
I'm gonna mess with my friends Note and see if I can find the file and if I do, I will post it since no else has.
Waiting for your file......
Sloogle_Flugelmann said:
Wow........... This hasn't been solved yet?? Same boat here. This is stupid.
I'm gonna mess with my friends Note and see if I can find the file and if I do, I will post it since no else has.
Click to expand...
Click to collapse
I am waiting for you to upload the file dear..... this problem is still unsolved in my Note.... i will be veryyyyyyyyyyyyy thankful to you. so will be others! :crying:
I have the LTE version on Boost, its already on 5.1 but there is obviously an update for it, I get the prompt to download update but when I go to install it, the install fails. The notification gets annoying b/c it seems to come up while i'm trying to use the phone. How can I force the update? Or disable the notification for the update entirely....I like the phone as it is right now
is it fully stock ?
once you tinker with it you may lose ability to get OTA updates i think right.
and that update could be a "Stagefright" update.
update failure is due to modified recovery/system
Dvdxploitr said:
I have the LTE version on Boost, its already on 5.1 but there is obviously an update for it, I get the prompt to download update but when I go to install it, the install fails. The notification gets annoying b/c it seems to come up while i'm trying to use the phone. How can I force the update? Or disable the notification for the update entirely....I like the phone as it is right now
Click to expand...
Click to collapse
now to verify if ur system is modified then do one thing, reboot into ur bootloader and there will be displayed some text in yellow that device connected via USB or something like that above this text is : system status: official/modified(depending upon ur device ). And my guess here is that ur system status is modified and hence u might not recieve updates. Don't worry bro! it doesnt matter, anyways we wont recieve updates for android v6.0. As for 5.1 use any custom rom like CM12.1 or PACMAN.
I bought the phone off eBay and its already rooted, so obviously it has been modified, i clicked on "Disable" on the moto udpate thing and it seems to not be bothering me with the updates. I think its crazy that it downloads the updates and then tells me to install it, but it won't actually install....i'll just leave it as it is for right now. The phone is only used for PerkTV apps, so its not even used for service
i searched this sub-forum for update failed and pretty much every single topic showed up LOL
it seems i too am getting this update prompt too.
i tried letting it update and it always fails then eventually i get into a loop.
my phone keeps restarting to recovery automatically.
but it stopped when i re-flashed my Squid kernel.
But i do want to install the update though.. the update details said it was a stagefright fix.
i figured out what was going on by reading the logs.
the update for me downloads and tries to install.. it asks you to restart to apply the update.
when it restarts it fails with an error mentioning "Keys" and the versions found / needed.
i am thinking i *might be able to adb side load the update with TWRP but i have not used that before yet.
i also think forcing the update may be a bad idea.. i don't want to brick it LOL
so i don't know..
edit:
I guess it's common for these to fail.
something set test Keys on my phone prob SuperSU
It got detected and then the update failed.
i found some side loading info and possible TWRP flashable version info for another phone.
But they say flash to a stock firmware and i have done that a lot lately and can't be bothered right now.
So it seems if i want the OTA update installed it's gonna be some work/waiting.
Going to keep an eye out for a TWRP ready flashable.zip though
I have the same issue as xpmule, when phone restarts to install the update it boots into recovery (TWRP) so the update fails. I restored a backup and now I am waiting for an update that I can flash using TWRP, stagefright is serious business.
I have an euro XT1524, rooted, Stock 5.1 US ROM flashed and squid kernel r10f.
I have a Canadian XT1527, rooted, Stock 5.1 US ROM flashed and squid kernel r10f.
And i still have not had much time to research more but i think the problem lies
with the singing keys..
i can see WHY it failed when you open the TWRP log (middle button)
my log said it failed to execute the update script because of bad keys..
It mentions i have test/keys and it expects to see Retail/Keys
When i looked on the web i see that could be because of SuperSU (being signed with TestKeys)
Or i thought maybe even Squids Kernel i am running.
If anyone seen a topic on this or what ever then let us know
i will prob keep poking around and see what i can do.
Problem is i am being VERY cautious i don't want to brick my phone.
Official OTAs tend not to flash on rooted or modified devices. Specifically with custom recoveries. The zips script verifies partitions and if something doesn't match it'll fail. Usually to get the ota you'll have to go back to completely stock unrooted firmware with the stock recovery.
After growing tired of seeing the update popup each time the phone decided to switch networks I did this:
Full TWRP Backup (just in case)
Flashed XT1527_SURNIA_RETUS_5.1_LPI23.29-18.9_cid9_subsidy-DEFAULT_CFC.xml.zip from here
I flashed back TWRP (well, just replaced the recovery.img from the stock rom, did the same with the logo)
Restored data backup
Reinstalled squid's kernel
Reinstalled SuperSU
Had some minor quirks, like losing the swiftkey language (just enter the config and download again, didn't lose predictions) and having to open apps that needed root and reapply SuperSU permissions, but all of those sound normal. Everything seems to be working correctly, there's no annoying popup nor Stagefright vulnerability.
{
"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"
}
ya i was thinking of doing similar pretty quick..
was waiting to hear back from people if that included stage fright fixes.
people are slow to reply here lol
thanks for the info.. i was not sure what parts of the back up i was going to restore.
also i use Swift Keyboard to.. i just wish the Lollipop UI had the Holo Theme or some dark theme.
but ya me too that prompt was getting a bit irritating lol
I have a virgin mobile xt1526 running 5.0.2 rooted but i need to update to 5.1, if i flash the ret_us update will it correctly identify my phone as VM? Boost users, did android correctly identify your phone as boost when you flashed the ret_us 5.1 update?
Sent from my XT1526 using Tapatalk
Sands207 said:
I have a virgin mobile xt1526 running 5.0.2 rooted but i need to update to 5.1, if i flash the ret_us update will it correctly identify my phone as VM? Boost users, did android correctly identify your phone as boost when you flashed the ret_us 5.1 update?
Sent from my XT1526 using Tapatalk
Click to expand...
Click to collapse
The update is for people on 5.1 already.
There is a different update for the 5.0.2 versions.
The retail update will look for the right version to update or it will fail.
And it is VERY picky at what it expects to see too !
Your going to need the newest full firmware package (easiest way)
that is a whole new can of worms to open LOL
@direi
i did the same thing now..
i seem to be up running ok and not vulnerable using the same Stage Fright Test tool as you.
Although i had to let it fire up once after flashing then turn it off so i could get the partition restored.
Reinstalled squid kernel with twrp and problem solved. Then froze motorolaOTA. Working fine so far.
{
"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"
}
My s8+ had UAE firmware on it, settings showed FD version but all other apps like HW info and antutu, Samsung members said F only.
Moving forward I tried to flash a custom official noble rom, and I clicked install twrp too. Fast forward after installation my phone only is stuck in downloading screen, and holding down volume down and power button keeps taking me back to download mode, and it won’t even boot or do anything else. It’s just stuck. I tried to flash official firmware from Odin, i wasn’t sure what my csc was so I flashed and tried every single rom of UAE and I could not flash a single one. It keeps failing. My sister has exams, and I’m being held responsible, I’m poor and my mom can’t buy her a new phone let alone fix this from a shop. I beg any kind soul to please help me out of this.
shafin123 said:
View attachment 5894253My s8+ had UAE firmware on it, settings showed FD version but all other apps like HW info and antutu, Samsung members said F only.
Moving forward I tried to flash a custom official noble rom, and I clicked install twrp too. Fast forward after installation my phone only is stuck in downloading screen, and holding down volume down and power button keeps taking me back to download mode, and it won’t even boot or do anything else. It’s just stuck. I tried to flash official firmware from Odin, i wasn’t sure what my csc was so I flashed and tried every single rom of UAE and I could not flash a single one. It keeps failing. My sister has exams, and I’m being held responsible, I’m poor and my mom can’t buy her a new phone let alone fix this from a shop. I beg any kind soul to please help me out of this.
Click to expand...
Click to collapse
Alright, lets fix this. Looking at what firmware is available for your phone. Can you please give me your CSC? Dial *#1234#" to figure out what you're current CSC code is.
shafin123 said:
View attachment 5894253My s8+ had UAE firmware on it, settings showed FD version but all other apps like HW info and antutu, Samsung members said F only.
Moving forward I tried to flash a custom official noble rom, and I clicked install twrp too. Fast forward after installation my phone only is stuck in downloading screen, and holding down volume down and power button keeps taking me back to download mode, and it won’t even boot or do anything else. It’s just stuck. I tried to flash official firmware from Odin, i wasn’t sure what my csc was so I flashed and tried every single rom of UAE and I could not flash a single one. It keeps failing. My sister has exams, and I’m being held responsible, I’m poor and my mom can’t buy her a new phone let alone fix this from a shop. I beg any kind soul to please help me out of this.
Click to expand...
Click to collapse
Wait...you can't dial. Well, what country are you in?
ethical_haquer said:
Alright, lets fix this. Looking at what firmware is available for your phone. Can you please give me your CSC? Dial *#1234#" to figure out what you're current CSC code is.
Click to expand...
Click to collapse
Sir, the phone does not do anything but go in download mode, this is a screen shot I kept before starting the flashing process
ethical_haquer said:
Wait...you can't dial. Well, what country are you in?
Click to expand...
Click to collapse
I am in Bangladesh, this is a second hand phone and I’m not sure but I sense that this used to be a single sim phone and the previous owner put a dual SIM card tray and installed firmware for FD model, and somehow both sims did use to work just fine.
I’ll tell you where everything went wrong and what was the state of the device so that you can make a better judgement of where I ****ed up.
1. I used adb fast boot from cmd to reboot the phone into fastboot.
2. I installed linageos 19.1 android 12 version and the phone was working perfectly. The custom rom was installed.
3. Then I wanted to tweak the phone to increase battery life, stop over heating and screen flicker so I did some research and downloaded hadesRom v12.0 Pie S8/S8+/Note8 and stored it in my phone memory and flashed it in the similar way as linage OS. I also went ahead and tried to install a2n kernel. When trying to install, I received a message saying that I’m trying to install a wrong kernel where my g955 is “N” and not “F” which indicates that it’s a Korean variant but this contradicts everything I’ve done before, anyway that didn’t create a problem but I did this without even rebooting after the hades rom. Ever since then, I’ve been booted back to download mode and I’ve tried flashing official firmwares but nothing helped. It failed every time I’ve been up all night since yesterday and my mother is on the verge of kicking me out, I’m pulling my own hair to find out what is actually wrong but I can’t find anything.
All details of what has been done to the device***
ll tell you where everything went wrong and what was the state of the device so that you can make a better judgement of where I fvkd up.
1. I used adb fast boot from cmd to reboot the phone into fastboot.
2. I installed linageos 19.1 android 12 version and the phone was working perfectly. The custom rom was installed.
3. Then I wanted to tweak the phone to increase battery life, stop over heating and screen flicker so I did some research and downloaded hadesRom v12.0 Pie S8/S8+/Note8 and stored it in my phone memory and flashed it in the similar way as linage OS. I also went ahead and tried to install a2n kernel. When trying to install, I received a message saying that I’m trying to install a wrong kernel where my g955 is “N” and not “F” which indicates that it’s a Korean variant but this contradicts everything I’ve done before, anyway that didn’t create a problem but I did this without even rebooting after the hades rom. Ever since then, I’ve been booted back to download mode and I’ve tried flashing official firmwares but nothing helped. It failed every time I’ve been up all night since yesterday and my mother is on the verge of kicking me out, I’m pulling my own hair to find out what is actually wrong but I can’t find anything
shafin123 said:
it keeps failing.
Click to expand...
Click to collapse
How?
Also, what version of Android did you have with stock? - Right now it looks like I can only download A9 for your device.
ethical_haquer said:
How?
Click to expand...
Click to collapse
Secure check fail: (pit)
And then if I reboot the phone into download mode, and reset and start the process from scratch again, it fails and the error this time is write operation failed
ethical_haquer said:
Also, what version of Android did you have with stock?
Click to expand...
Click to collapse
Android 9 on stock, then installed linageOS with android 12 then flashed hades ported android 9 and that’s where it went wrong
I
shafin123 said:
Secure check fail: (pit)
And then if I reboot the phone into download mode, and start Odin, fails and the error is write operation failed
Click to expand...
Click to collapse
I’ve even tried multiple csc in both Odin 1.3 and the latest one. I haven’t left any stone unturned from my knowledge. All adb drivers and Samsung drivers are installed as well
shafin123 said:
Android 9 on stock, then installed linageOS with android 12 then flashed hades ported android 9 and that’s where it went wrong
Click to expand...
Click to collapse
So do you want to go back to stock A9 or LOS19, both are an option.
shafin123 said:
I’ve even tried multiple csc in both Odin 1.3 and the latest one. I haven’t left any stone unturned from my knowledge. All adb drivers and Samsung drivers are installed as well
Click to expand...
Click to collapse
Is this with F, or FD as the end of the model firmware?
It sounds like the PIT error happens when the firmware isn't the right version.
Also, do you want the BNG (Bangladesh) firmware or something else?
ethical_haquer said:
So do you want to go back to stock A9 or LOS19, both are an option.
Is this with F, or FD as the end of the model firmware?
It sounds like the PIT error happens when the firmware isn't the right version.
Also, do you want the BNG (Bangladesh) firmware or something else?
Click to expand...
Click to collapse
BNG firmware is fine, I don’t know if I should flash F or FD, as I’ve tried both and both have failed. I’d rather go back to A9 and then work my way around. And I have all the firmwares downloaded. I think I’ve messed up my boot loader somehow.
ethical_haquer said:
So do you want to go back to stock A9 or LOS19, both are an option.
Is this with F, or FD as the end of the model firmware?
It sounds like the PIT error happens when the firmware isn't the right version.
Also, do you want the BNG (Bangladesh) firmware or something else?
Click to expand...
Click to collapse
Beggars can’t be choosers, I just want the phone to work again, and somehow get out of the download mode
shafin123 said:
Beggars can’t be choosers, I just want the phone to work again, and somehow get out of the download mode
Click to expand...
Click to collapse
So, what exactly happens when you flash the firmware, a PID error?
Secure check fail: (pit)
And alternatively
Write operation failed, this is after I get pit fail and try again
shafin123 said:
Secure check fail: (pit)
And alternatively
Write operation failed, this is after I get pit fail and try again
Click to expand...
Click to collapse
Look at this tutorial. I've followed it before. Just make sure that you're flashing it properly with Odin, as you need to make sure you wipe the device:
As you can see, flashing the CSC file will wipe, whereas the HOME_CSC will not.
ethical_haquer said:
Look at this tutorial. I've followed it before. Just make sure that you're flashing it properly with Odin, as you need to make sure you wipe the device:
As you can see, flashing the CSC file will wipe, whereas the HOME_CSC will not.
Click to expand...
Click to collapse
Yes I’m aware and only using the CSC file not home.
shafin123 said:
Yes I’m aware and only using the CSC file not home.
Click to expand...
Click to collapse
Try looking at these solutions. Let me know if it still doesn't work.