The update center on my phone shows a system update available to 14.4.A.0.108. In the dialog it says "Computer required". I'm assuming that this means I need to connect using USB and run Sony PC Companion. Is that the case? Any information about this update will be appreciated.
I have the same message in update center saying "Computer required". But I am already on 14.4.A.0.108 build. What is going on?
Sent from my D5503 using Tapatalk
I got the same message
---------- Post added at 05:12 AM ---------- Previous post was at 05:12 AM ----------
Will I lose root if I update?
I got it too but I am already on 14.4.A.0.108
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my D5503 using XDA Free mobile app
Hmmm I wonder what it is
:good:
same here
I updated my phone through PC Companion and now all notification for updated version are now gone. Although no data/files are lost, I still lost my root so I need to re-root again. I'll observe what did change but the about screen is still the same except there are no more update notification
Update:
There's a bug before in the camera wherein after taking a picture and exiting, the screen cannot be swiped and I can only access the home button leading to either "Whats New" or Google search" and after that menu (app drawer) is now accessible. But now there's no bug like that on my end... let's see what else is changed
Anyone else updated already? Any changes seen?
I have kitslim Evo 9 and i have this notification too. Need Computer. Today i will update but backup first. In changelog there is a info that camera is updated and has new funkcion.
Hi everyone,
i'm sure this is a noob question, just like me, haha, but i was wondering, can this update applied with custom recovery? because i've been told that OTA updates cant work with devices with custom recoveries and if you do so, the update will stuck in the custom recovery, (either TWRP or CMW) ...
If that so, i also want to ask how revert back to stock recovery? any help about this would gladly appreciated
sorry about my bad english D:
salman_911 said:
Hi everyone,
i'm sure this is a noob question, just like me, haha, but i was wondering, can this update applied with custom recovery? because i've been told that OTA updates cant work with devices with custom recoveries and if you do so, the update will stuck in the custom recovery, (either TWRP or CMW) ...
If that so, i also want to ask how revert back to stock recovery? any help about this would gladly appreciated
sorry about my bad english D:
Click to expand...
Click to collapse
I had recovery and locked bootloader and update did norma,only lost root
salman_911 said:
because i've been told that OTA updates cant work with devices with custom recoveries ...
Click to expand...
Click to collapse
Is this correct? I'm currently on 757 and wanted to upgrade to 108. But both OTA and PC Companion updates failed. Is it because of my custom recovery (Philz Touch) and/or unlocked bootloader?
Unlocked bootloader
aigaming said:
I had recovery and locked bootloader and update did norma,only lost root
Click to expand...
Click to collapse
whoa, really? i guess it's safe to update then, thanks for the information :highfive:
matt.s said:
Is this correct? I'm currently on 757 and wanted to upgrade to 108. But both OTA and PC Companion updates failed. Is it because of my custom recovery (Philz Touch) and/or unlocked bootloader?
Click to expand...
Click to collapse
i think it's because unlocked bootloader, because i've read somewhere that one you unlock your bootloader, you can't get any official updates form sony because it have something to do with DRM keys, i don't know what it is exactly, haha, noob's speaking here...
maybe some senior members here can give a correct answer...
aigaming said:
I had recovery and locked bootloader and update did norma,only lost root
Click to expand...
Click to collapse
Please let us know if you are able to re-root successfully.
dave
The only thing changed is software revision.. before it was R4C and now it is R5C
Old108
New 108
Sent from my D5503 using XDA Free mobile app
Customization Version...
coolkoushik07 said:
The only thing changed is software revision.. before it was R4C and now it is R5C
Click to expand...
Click to collapse
Same thing here on my Z1... Customization version changed from 1276-7099_R4C to 1276-7099_R5C.
What does this means? No other noticeable change on firmware at all.
Rooted,locked bootloader, stock launcher modified with Xposed Framework (4x7 grid, other mods). What happens when I update to the new .108? No one yet has said whether they had any problem rooting the new .108.
dave
mine still is same at R6C since the first time i flashed .108
its probably some revision changes for some regions.
example my stock uk notbranded is still at R4C compared to the t-mobile specific i use now that is R6C
Related
Good morning everyone.
As you can see from my post count, I am fresh meat on the XDA forums, and more in general to fiddling with Android.
I rooted my phone while ago, doing great so far (but no custom ROM yet, waiting for CM 7/9).
Today I opened up Kies and found thet there's a firmware upgrade avaiable.
It reads like 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"
}
Now, my situation is like this:
. I am rooted
. I have uninstalled several system apps (mainly Samsung Bloatware)
Being the total noob I am, am I safe to to the upgrade from Kies? (apart the known fact I learnt that Kies is Satan's stepchild)
Thanks in advance for any reply!
Update from Kies is a risk. Many ppl was posting that they have some errors. I prefer to update by Samsung Ota, just need wifi connection and thats all. I made the update with rooted phone and after update phone was still rooted.
Hunteros said:
Update from Kies is a risk. Many ppl was posting that they have some errors. I prefer to update by Samsung Ota, just need wifi connection and thats all. I made the update with rooted phone and after update phone was still rooted.
Click to expand...
Click to collapse
I saw another thread similar to mine being opened, in which it says that this update is just the 2.3.6 one.
But I'm already on 2.3.6
My main concern about updating was about the fact that I'm rooted and uninstalled some default apps, and if that would interfere with the update
This update should bring your Version build to "GINGERBREAD.XXLA2"
It is now available in Italy both through Kies and OTA (I updated yesterday evening via OTA).
I think this upgrade can unroot your phone. But you can always root it again.
The "Root via Recovery" method should work on this release too.
banelicious said:
I saw another thread similar to mine being opened, in which it says that this update is just the 2.3.6 one.
But I'm already on 2.3.6
My main concern about updating was about the fact that I'm rooted and uninstalled some default apps, and if that would interfere with the update
Click to expand...
Click to collapse
If you think there's risk...use odin.it's more reliable than kies..that's only what I know..
Try clockworkmod recovery by arco68;
http://forum.xda-developers.com/showthread.php?t=1446593
It can do a lot of thing..u can do a nandroid backup if anything **** happen..just recover it..
Sent from another space
jahlee said:
If you think there's risk...use odin.it's more reliable than kies..that's only what I know..
Try clockworkmod recovery by arco68;
http://forum.xda-developers.com/showthread.php?t=1446593
It can do a lot of thing..u can do a nandroid backup if anything **** happen..just recover it..
Sent from another space
Click to expand...
Click to collapse
Yeah I'm investigating about ClockworkMod (I hate mindlessly use things without prior knowledge of how they work)
By the way I have succesfully upgraded with Kies (OTA Update kept failing instead).
Now I'm waiting for an update of ZergRush root, cause this last firmware update screwed it.
Thanks anyone for the tips
banelicious said:
Now I'm waiting for an update of ZergRush root, cause this last firmware update screwed it.
Click to expand...
Click to collapse
Not sure if that will happen soon, but I would recommend you to read, as mentioned above, about the rooting via Recovery:
It is also possible via ClockWorkMod.
About the CWM, via ODIN it is very easy to flash and you have the possibility to reflash the stock recovery in a couple of seconds, too. This may be needed if you update next time via OTA.
greets
THE-E
Hi Guys!
I'm sorry if this question has been asked a gazillion times, but I want to know what I'm getting into first as I am new to rooting.
I have a Sony Xperia Ion (LT28i) with Jelly Bean on it (4.1.2). I was simply wondering if the process outlined in this thread would work:
[Tutorial][ION] Flashing Firmware and Rooting
http://forum.xda-developers.com/showthread.php?t=1812168
Once again, sorry for a repeat but I'm not exactly sure about what my firmware is etc.
Thanks!
WGuitar said:
Hi Guys!
I'm sorry if this question has been asked a gazillion times, but I want to know what I'm getting into first as I am new to rooting.
I have a Sony Xperia Ion (LT28i) with Jelly Bean on it (4.1.2). I was simply wondering if the process outlined in this thread would work:
[Tutorial][ION] Flashing Firmware and Rooting
http://forum.xda-developers.com/showthread.php?t=1812168
Once again, sorry for a repeat but I'm not exactly sure about what my firmware is etc.
Thanks!
Click to expand...
Click to collapse
yes that will work..go to settings>about phone> and you will find all the info abt ur software versions...u are basically looking for build number here..
Build Number is:
6.2.B.0.211
Therefore since it appears to be the most recent firmware, I can simply skip to the rooting portion of the guide correct?
Thanks, I've been hoping to get my phone rooted to get rid of all the bloatware.
You guys are awesome!
I have attempted to root the device to no avail. Does the firmware have to be flashed over? Or can I use the firmware currently on it. If it has to be flashed over, my phone does not appear to have drivers in the flash tool. Can I flash without installing a driver?
WGuitar said:
I have attempted to root the device to no avail. Does the firmware have to be flashed over? Or can I use the firmware currently on it. If it has to be flashed over, my phone does not appear to have drivers in the flash tool. Can I flash without installing a driver?
Click to expand...
Click to collapse
u have an unlocked bootloader or locked???
I believe it is locked as I have not done anything to the phone besides upgrading to JB from ICS. I used the Sony PC Companion to do so as well.
Edit: Bootloader is locked and apparently cannot be unlocked. (According to System info)
WGuitar said:
I believe it is locked as I have not done anything to the phone besides upgrading to JB from ICS. I used the Sony PC Companion to do so as well.
Edit: Bootloader is locked and apparently cannot be unlocked. (According to System info)
Click to expand...
Click to collapse
It doesnt matter...can you tell me the steps that you did briefly and where you faced the problem?
Sent from my Micromax A110 using xda app-developers app
It tells me to use the display system check but it just gets stuck hanging at a white screen on my phone and the program does not continue from there. If you could tell me the version of the root program and which option to use, I might be able to do it, but I've tried a few different versions of it with different options. Not exactly sure what I can do.
Edit: Do I have to flash my firmware before trying to root? It doesn't say anywhere that I have to, however could that be what's not allowing me to root?
WGuitar said:
It tells me to use the display system check but it just gets stuck hanging at a white screen on my phone and the program does not continue from there. If you could tell me the version of the root program and which option to use, I might be able to do it, but I've tried a few different versions of it with different options. Not exactly sure what I can do.
Edit: Do I have to flash my firmware before trying to root? It doesn't say anywhere that I have to, however could that be what's not allowing me to root?
Click to expand...
Click to collapse
This method doesnt work with your .211 fw. Try this http://forum.xda-developers.com/showthread.php?t=1886460&highlight=root+211+ion
I've tried that thread's root method. All I keep getting is a screen that it pauses at basically indefinitely, and none of the other root options work.
{
"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"
}
So I got a notification today for a new firmware update to 183.46.15. WIthout thinking I hit install, even though Im unlocked and rooted. Now the phone kept rebooting into TWRP. Any idea when we should have a flashable firmware for this? Just had to factory reset.
firesice18 said:
So I got a notification today for a new firmware update to 183.46.15. WIthout thinking I hit install, even though Im unlocked and rooted. Now the phone kept rebooting into TWRP. Any idea when we should have a flashable firmware for this? Just had to factory reset.
Click to expand...
Click to collapse
In order to install system updates you need to be on full stock firmware and recovery. Also, If you receive that update again, please capture the zip and post it.
I got it too today...
..but haven't applied it yet, of course. Where should I look for the zip? I'll post it right up.
Tony
tonyyikes said:
..but haven't applied it yet, of course. Where should I look for the zip? I'll post it right up.
Tony
Click to expand...
Click to collapse
I believe it will be in /cashe. You'll need to use a root explorer to grab it.
But, if i accept this update, can i install my custom recovery using adb/fastboot method or i have to keep away from this?
RAZR M BOOTLOADER UNLOCKED & ROOTED
183.46.10
Broloff said:
But, if i accept this update, can i install my custom recovery using adb/fastboot method or i have to keep away from this?
RAZR M BOOTLOADER UNLOCKED & ROOTED
183.46.10
Click to expand...
Click to collapse
Go for it. It's just a minor update. Re-flash recovery then superuser.
I seem to have gotten a different update .zip. I haven't tried to install it yet.
https://www.dropbox.com/s/6ty1fqsvg87qfm9/Blur_Version.183.46.10.XT907.Verizon.en.US.zip?dl=0
This is what was in cache.
Strife89 said:
I seem to have gotten a different update .zip. I haven't tried to install it yet.
https://www.dropbox.com/s/6ty1fqsvg87qfm9/Blur_Version.183.46.10.XT907.Verizon.en.US.zip?dl=0
Click to expand...
Click to collapse
Updates are named after the version from which you are updating from. I'll need the build.prop sent to me if you guys would like me to apply the tether patch.
To update: Flash stock recovery, undo any system modifications. Update, reflash recovery. Reroot. Will not relock BL
http://www.verizonwireless.com/dam/support/pdf/system_update/razrm-09-09-14.pdf
Security and messaging improvements apparently.
{
"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"
}
What is the name of the update application (currently on 4.4.2) that I can freeze so the reminder stops showing up?
Sent from my XT907 using Tapatalk
toddbecker said:
What is the name of the update application (currently on 4.4.2) that I can freeze so the reminder stops showing up?
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
I believe it's
Code:
/ system / priv-app / 3c_ota.apk
ATTACK said:
I believe it's
Code:
/ system / priv-app / 3c_ota.apk
Click to expand...
Click to collapse
To elaborate (and make it easier to find in TiBu), that's com.motorola.ccc.ota, or "MotorolaOTA 1.0".
I'm freezing, too, as it'd be easier to RSD back to stock than to manually put it back together if I wanted to update (in other words, I'm lazy).
I am curious, though, on what exactly the update changes/fixes. D'oh, I missed coronado's post.
Strife89 said:
To elaborate (and make it easier to find in TiBu), that's com.motorola.ccc.ota, or "MotorolaOTA 1.0".
I'm freezing, too, as it'd be easier to RSD back to stock than to manually put it back together if I wanted to update. I am curious, though, on what exactly the update changes/fixes.
Click to expand...
Click to collapse
Well... [HERE'S] Verizon's "changelog". Motorola hasn't updated there's yet. > http://goo.gl/6YzYPu
Since it's only 10MB, not much has changed. FakeID, Futex Bug and the Trust Zone exploit have been closed, also Messaging fixes. I'm curious though, has anybody had Messaging problems? I haven't.
ATTACK said:
Well... [HERE'S] Verizon's "changelog". Motorola hasn't updated there's yet. > http://goo.gl/6YzYPu
Since it's only 10MB, not much has changed. FakeID and the Trust Zone exploits have been closed, also Messaging fixes. I'm curious though, has anybody had Messaging problems? I haven't.
Click to expand...
Click to collapse
I never noticed any Messaging issues either. I've been using 8sms since July, though.
Same here
That's the one I have as well.
firesice18 said:
This is what was in cache.
Click to expand...
Click to collapse
ATTACK said:
FakeID, Futex Bug and the Trust Zone exploit have been closed
Click to expand...
Click to collapse
...which means locked BL users should not take this update?
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]
AndyYan said:
...which means locked BL users should not take this update?
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]
Click to expand...
Click to collapse
Correct. Or unlock before taking the update.
ATTACK said:
Messaging fixes. I'm curious though, has anybody had Messaging problems? I haven't.
Click to expand...
Click to collapse
I have messaging issues here and there... Wife sends a message phone tells me I have a message yet I can't read it and the notification won't go away till I get and read another message... I really just thought it was from all the stuff I've done.. I really need a clean flash... Or I just never get the message notification or message at all no biggie tho
We cannot teach people anything; we can only help them discover it within themselves.
Tried to update to Lolipop build using the OTA.
Getting this error.
{
"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"
}
Wrong recovery. Can't use EU recovery for India version.
Use this one : http://forum.xda-developers.com/showpost.php?p=58631821&postcount=4338
ckpv5 said:
Wrong recovery. Can't use EU recovery for India version.
Use this one : http://forum.xda-developers.com/showpost.php?p=58631821&postcount=4338
Click to expand...
Click to collapse
Am still getting the same error.
atuladhikari said:
Am still getting the same error.
Click to expand...
Click to collapse
How can it be SAME error ? Post a screenshot.
The earlier screenshot shows clearly that it needs htc_asia_india but your device has htc_europe
If the recovery is properly installed, when there are more errors, they should be different errors.
For example, an expected contents error.
It's not on about the recovery, its saying the ROM on the phone has the EU build.prop fingerprint as opposed to the one it needs
EddyOS said:
It's not on about the recovery, its saying the ROM on the phone has the EU build.prop fingerprint as opposed to the one it needs
Click to expand...
Click to collapse
I see.. the system is smarter now. You have htc_europe ROM installed on a htc_asia_india device, do the OTA checking, the system will download htc_asia_india instead of htc_europe
Not necessarily. If the OTA was downloaded from HTC via the phone then the ROM is probably correct and the OP may have just changed the build.prop for some reason. We won't know unless they say so.
EddyOS said:
Not necessarily. If the OTA was downloaded from HTC via the phone then the ROM is probably correct and the OP may have just changed the build.prop for some reason. We won't know unless they say so.
Click to expand...
Click to collapse
So what do i need to do?
Have downloaded the OTA 4 times already and having the same error.
ckpv5 said:
I see.. the system is smarter now. You have htc_europe ROM installed on a htc_asia_india device, do the OTA checking, the system will download htc_asia_india instead of htc_europe
Click to expand...
Click to collapse
It can't be. mine was updated from the previous OTA. I just have rooted it. No custom ROM's installed ever.
atuladhikari said:
It can't be. mine was updated from the previous OTA. I just have rooted it. No custom ROM's installed ever.
Click to expand...
Click to collapse
Restore my 3.35.720.1 stock nandroid from the backups thread, and then flash this recovery, and then download the ota
atuladhikari said:
It can't be. mine was updated from the previous OTA. I just have rooted it. No custom ROM's installed ever.
Click to expand...
Click to collapse
I know it can't be ... that post is not for you.
I asked for another screenshot after you flashed the 3.35.720.1 that I gave you the link before. It should not be a htc_europe problem anymore but maybe other errors.
You did fastboot flash recovery 3.35.720.1_recovery.img after you downloaded the recovery image, right ?
atuladhikari said:
It can't be. mine was updated from the previous OTA. I just have rooted it. No custom ROM's installed ever.
Click to expand...
Click to collapse
You're using the stock recovery from Lollipop, hence it saying LRX22C release-keys at the top. If this is the wrong recovery you'll get an error. It HAS to be the recovery that came with your build
EddyOS said:
You're using the stock recovery from Lollipop, hence it saying LRX22C release-keys at the top. If this is the wrong recovery you'll get an error. It HAS to be the recovery that came with your build
Click to expand...
Click to collapse
where can i can get recovery for my build?
so the way my noob brain has understood.
i need to first need to flash unsuperuser.zip
the flash 3.35.720.1_recovery.img and redownload the OTA?
or flash unsuperuser.zip
and then flash 4.16.401.10_firmware.zip?
BUMP
Help someone!!!
I still have no Lollipop love!!!
atuladhikari said:
Help someone!!!
I still have no Lollipop love!!!
Click to expand...
Click to collapse
Flash the RUU from the stock backups thread
Hi Everyone,
I'm trying to re-lock my bootloader but the OEM Unlock toggle is stuck to the left position whilst displaying the message "Bootloader is already unlocked".
If I try to switch the toggle to the right position, the device will factory reset and then when it powers back up, the toggle is in the left position again.
Is this a result of knox being tripped?
In DL mode it displays both FRP and OEM lock as OFF.
Thanks for the help!
{
"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"
}
Just ignore it, it causes no problems and others have had the same problem since unlocking theirs
*Detection* said:
Just ignore it, it causes no problems and others have had the same problem since unlocking theirs
Click to expand...
Click to collapse
Yeah I know that it's not technically an issue but I want to sell the phone and would like to lock the bootloader before doing so.
Is there no way to re-lock it?
If not... would it stop the phone from passing safetynet/google pay checks?
Thanks
EDIT: I've just tested and google pay won't work on it in this state.
You tripped KNOX, many things won't work on it again anyway
*Detection* said:
You tripped KNOX, many things won't work on it again anyway
Click to expand...
Click to collapse
I'm quite aware of that. What i'm specifically trying to ascertaine is whether or not the bootloader is re-lockable.
If need be I'll just install magisk on stock and put the info in the eBay listing.
Thanks for the assistance anways!
As I said, other members have already posted about the same problem, I have not seen a solution yet, although you could read through a few of those threads and see if they were updated
Any news on this? I want to relock too! With it unlocked and stock os. I can't use Google pay or citrix workspace etc!
Hi, is there new news about this problem? the same happens to me. I have the bootloader unlocked with the button to the left, so I can't block it in a rom stock. This causes Google Play to say that the device is not certified and some applications are not installed. Can anybody help me?
MadSilence said:
Any news on this? I want to relock too! With it unlocked and stock os. I can't use Google pay or citrix workspace etc!
Click to expand...
Click to collapse
why in gods green earth would you actually WANT Citrix? Kidding, i use it 40 hours a week and its abysmal, as if you didnt already know that.
naztam said:
Hi, is there new news about this problem? the same happens to me. I have the bootloader unlocked with the button to the left, so I can't block it in a rom stock. This causes Google Play to say that the device is not certified and some applications are not installed. Can anybody help me?
Click to expand...
Click to collapse
So, the bootloader is unlocked, have you guys tried flashing the Odin files with a newer revision of the bootloader?
Thanks for your answer! I have tried to update it, to make a downgrade, to wait 7 days ... and nothing, everything remains the same. The bootloader is binary 6, and the only move I have been able to do with odin is update and donwgrade in the July and August updates. Maybe if Samsung updates the bootloader to binary 7, it will be solved, it is honestly the only thing left for me to try.
naztam said:
Thanks for your answer! I have tried to update it, to make a downgrade, to wait 7 days ... and nothing, everything remains the same. The bootloader is binary 6, and the only move I have been able to do with odin is update and donwgrade in the July and August updates. Maybe if Samsung updates the bootloader to binary 7, it will be solved, it is honestly the only thing left for me to try.
Click to expand...
Click to collapse
what firmware version are you on currently? if your bootloader is revision 5, flash a rev 6 and see what happens
I am in the last firmware
I have the rev6, I can only flash the firmware of July and August
naztam said:
I am in the last firmware
I have the rev6, I can only flash the firmware of July and August
Click to expand...
Click to collapse
[email protected] then. maybe a ver 7 will release soon?