Develop Bugs

[Q] How to use Odin to upgrade from SGW 2.3.5 to 2.3.6 ?

Hello
I tried the search but did not find any tutorial on how to upgrade Samsung Galaxy W I8150 from Stock 2.3.5 to 2.3.6 with Odin
Can anyone list a link or the steps for downloading Odin and using it for upgrading to 2.3.6.
This will be my first time using Odin.
im on Windows XP Sp3

Ibn Saeed said:
Hello
I tried the search but did not find any tutorial on how to upgrade Samsung Galaxy W I8150 from Stock 2.3.5 to 2.3.6 with Odin
Can anyone list a link or the steps for downloading Odin and using it for upgrading to 2.3.6.
This will be my first time using Odin.
im on Windows XP Sp3
Click to expand...
Click to collapse
To update from 2.3.5 to 2.3.6 ODIN is not needed. You can simply update via Samsung Kies or OverTheAir(OTA). To do it over the air you will need to register at Samsung via phone. If you have trobles I can guide you trough this.
Incase you still want to Update via ODIN I will send you an instruction.
greets
THE-E

THE-E said:
To update from 2.3.5 to 2.3.6 ODIN is not needed. You can simply update via Samsung Kies or OverTheAir(OTA). To do it over the air you will need to register at Samsung via phone. If you have trobles I can guide you trough this.
Incase you still want to Update via ODIN I will send you an instruction.
greets
THE-E
Click to expand...
Click to collapse
Which is the best method ? Can you guide me through it please?
In the meantime, Kies is getting updated.
So if i use Kies, i should wait till i get the phone to 2.3.6 and then Root it ?
Should i root the phone before the update via Kies or after the update?

Ibn Saeed said:
Which is the best method ? Can you guide me through it please?
In the meantime, Kies is getting updated.
Click to expand...
Click to collapse
I would say updateing OverTheAir is maybe safer, because Kies messed up a couple of phones. I have updated mine a couple of times via Kies without an issue.
I will tell you both options, choose yourself:
OTA(OverTheAir):
1. step backup everything what is important to you. Nothing should be deleted, but you never know.
2. Make sure your phone has min 80% battery(safety reasons, not required) or be connected to the power socket.
3. You will have to have WiFi on your SGW enabled and connected with internet access.
4. Go to Settings->About Phone->Software update. Here they will ask you to register, do that and login.
5. Rest should be done automatically by your phone, download, updating etc..
If you don't want to register you should use Samsung Kies. It may be even easier but a couple of issues have been reported.
Samsung Kies:
1. step backup everything what is important to you. Nothing should be deleted, but you never know.
2. Make sure your phone has min 80% battery(safety reasons, not required) or be connected to the power socket.
3. Install Samsung Kies.
4. Make sure USB-Debugging is disabled(Settings->Applications->Development->USB-Debugging)
5. Connect your SGW with your PC and let all the drivers install.
6.Open Kies and wait until Kies recognizes your phone, than Kies should show, if you click on your device, that there is a new firmware available for your phone. Hit update and wait for 30-50 minutes(maybe even longer).
greets
THE-E
---------- Post added at 04:18 PM ---------- Previous post was at 04:16 PM ----------
Ibn Saeed said:
So if i use Kies, i should wait till i get the phone to 2.3.6 and then Root it ?
Should i root the phone before the update via Kies or after the update?
Click to expand...
Click to collapse
First do the update, because the root access will be vanished after updating.
So:
1.Update to latest firmware.
2.Root via recovery.
3. If you like, add CWM.
greets
THE-E

THE-E said:
I would say updateing OverTheAir is maybe safer, because Kies messed up a couple of phones. I have updated mine a couple of times via Kies without an issue.
I will tell you both options, choose yourself:
OTA(OverTheAir):
1. step backup everything what is important to you. Nothing should be deleted, but you never know.
2. Make sure your phone has min 80% battery(safety reasons, not required) or be connected to the power socket.
3. You will have to have WiFi on your SGW enabled and connected with internet access.
4. Go to Settings->About Phone->Software update. Here they will ask you to register, do that and login.
5. Rest should be done automatically by your phone, download, updating etc..
If you don't want to register you should use Samsung Kies. It may be even easier but a couple of issues have been reported.
Samsung Kies:
1. step backup everything what is important to you. Nothing should be deleted, but you never know.
2. Make sure your phone has min 80% battery(safety reasons, not required) or be connected to the power socket.
3. Install Samsung Kies.
4. Make sure USB-Debugging is disabled(Settings->Applications->Development->USB-Debugging)
5. Connect your SGW with your PC and let all the drivers install.
6.Open Kies and wait until Kies recognizes your phone, than Kies should show, if you click on your device, that there is a new firmware available for your phone. Hit update and wait for 30-50 minutes(maybe even longer).
greets
THE-E
---------- Post added at 04:18 PM ---------- Previous post was at 04:16 PM ----------
First do the update, because the root access will be vanished after updating.
So:
1.Update to latest firmware.
2.Root via recovery.
3. If you like, add CWM.
greets
THE-E
Click to expand...
Click to collapse
Thank you alot !!!!!!!!!!!!
I think since people have reported issues with Kies, thats why i asked to update via odin in the first place, after reading a post in another thread.
Ill just follow the steps you outlined for the "OTA" update. Right now the battery is at 49%, ill charge it full and then do the OTA update.
I will report back here.
Once again thanks for taking the time to right everything down.

Ibn Saeed said:
After the Update, would i be able to root the phone ?
Click to expand...
Click to collapse
Yes, the latest firmware (LA2) is rootable, but only with the method via recovery.
Make sure you check the Software update-status after the update. Maybe it will have to update once more.
greets
THE-E

THE-E said:
Yes, the latest firmware (LA2) is rootable, but only with the method via recovery.
Make sure you check the Software update-status after the update. Maybe it will have to update once more.
greets
THE-E
Click to expand...
Click to collapse
Alright, The-E. I have my phone updated.
This is the message i see after 2 updates.
"Phone Updated to version I8150JPLA4/I8150OJPLA1/I8150XXKL3"
The phone definitely feels a lot snappier and the icons have changed a bit as well. Theres a bit more detail in the colors.

THE-E said:
Yes, the latest firmware (LA2) is rootable, but only with the method via recovery.
Make sure you check the Software update-status after the update. Maybe it will have to update once more.
greets
THE-E
Click to expand...
Click to collapse
It seems that i have LA4 fireware, is that correct ?
Is it rootable ? Should i proceed with your recovery rooting method ?

Ibn Saeed said:
It seems that i have LA4 fireware, is that correct ?
Is it rootable ? Should i proceed with your recovery rooting method ?
Click to expand...
Click to collapse
Yes I just noticed this too. In Germany LA2 is still the latest firmware.
I think you are one of the first with this firmware. I think the way how to root should'nt have changed. All you can do is try and see or wait till somebody tries and reports.
good luck
THE-E

THE-E said:
Yes I just noticed this too. In Germany LA2 is still the latest firmware.
I think you are one of the first with this firmware. I think the way how to root should'nt have changed. All you can do is try and see or wait till somebody tries and reports.
good luck
THE-E
Click to expand...
Click to collapse
Alright, so if it does not work, will it brick my phone ? Are there chances of it happening ?
Do you want me to do any tests before rooting ?
i have noticed that the contrast is quite high in this update, HOw can i take a screenshot and post it here.

Ibn Saeed said:
Alright, so if it does not work, will it brick my phone ? Are there chances of it happening ?
Do you want me to do any tests before rooting ?
i have noticed that the contrast is quite high in this update, HOw can i take a screenshot and post it here.
Click to expand...
Click to collapse
As far as I know, bricking should not happen, because actually it is just transfering data
and setting permissions. But new firmware ne rules ;-)
If it does not boot or anything, you should be able to go to download mode and reflash the firmware.
This is how far I can tell, sorry, but for the rest you are by your own.
If you try do a backup of anything you need.
If you want to make a screenshot: while pressing Home-button, press the Power-Button.
BTW: There is no phone bricking reported for the SGW til now. There was always a solution.
greets
THE-E

Here are the screenshots:
{
"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"
}

THE-E said:
As far as I know, bricking should not happen, because actually it is just transfering data
and setting permissions. But new firmware ne rules ;-)
If it does not boot or anything, you should be able to go to download mode and reflash the firmware.
Click to expand...
Click to collapse
How would i reflash the firmware? do i have to download it from somewhere ?
By the way, which ROM is stable with good battery life for SGW ?

Ibn Saeed said:
How would i reflash the firmware? Where will i get the
firmware, do i have to download it from somewhere ?
Click to expand...
Click to collapse
Some are here in the forum. I have some too, german, european, asian, italian.
I will provide a detailed instruction if necessary(I have to search it, posted it somewhere).
greets
THE-E

THE-E said:
Some are here in the forum. I have some too, german, european, asian, italian.
I will provide a detailed instruction if necessary(I have to search it, posted it somewhere).
greets
THE-E
Click to expand...
Click to collapse
How do i know which firmware is mine in my phone right now? How to find it ?

Ibn Saeed said:
How do i know which firmware is mine in my phone right now? How to find it ?
Click to expand...
Click to collapse
You will have to search a I8150JP...... firmware. You have right now I8150JPLA4.
You can also get a older one and then update.
good luck, got to leave
EDIT: I have checked sammobile.com, they don't have a I8150JP...... firmware. So in case something goes wrong you will have to flash first a other firmware from a other region and wait till you get a new firmware with I8150JP... .
THE-E

THE-E said:
You will have to search a I8150JP...... firmware. You have right now I8150JPLA4.
You can also get a older one and then update.
good luck, got to leave
EDIT: I have checked sammobile.com, they don't have a I8150JP...... firmware. So in case something goes wrong you will have to flash first a other firmware from a other region and wait till you get a new firmware with I8150JP... .
THE-E
Click to expand...
Click to collapse
The E, really thanks for all of your help.
I think ill wait

Hi guys,
My phone uses build VJKJ4, 2.3.5 and I'd like to update to 2.3.6. What firmwares I can use? What should I look for? Any chances that my phone may not work due to different region standards?
Funny thing is that Kies says my phone can't be updated through it. WTF?!

can you help me please?!?!?
THE-E said:
I would say updateing OverTheAir is maybe safer, because Kies messed up a couple of phones. I have updated mine a couple of times via Kies without an issue.
I will tell you both options, choose yourself:
OTA(OverTheAir):
1. step backup everything what is important to you. Nothing should be deleted, but you never know.
2. Make sure your phone has min 80% battery(safety reasons, not required) or be connected to the power socket.
3. You will have to have WiFi on your SGW enabled and connected with internet access.
4. Go to Settings->About Phone->Software update. Here they will ask you to register, do that and login.
5. Rest should be done automatically by your phone, download, updating etc..
If you don't want to register you should use Samsung Kies. It may be even easier but a couple of issues have been reported.
Samsung Kies:
1. step backup everything what is important to you. Nothing should be deleted, but you never know.
2. Make sure your phone has min 80% battery(safety reasons, not required) or be connected to the power socket.
3. Install Samsung Kies.
4. Make sure USB-Debugging is disabled(Settings->Applications->Development->USB-Debugging)
5. Connect your SGW with your PC and let all the drivers install.
6.Open Kies and wait until Kies recognizes your phone, than Kies should show, if you click on your device, that there is a new firmware available for your phone. Hit update and wait for 30-50 minutes(maybe even longer).
greets
THE-E
---------- Post added at 04:18 PM ---------- Previous post was at 04:16 PM ----------
First do the update, because the root access will be vanished after updating.
So:
1.Update to latest firmware.
2.Root via recovery.
3. If you like, add CWM.
greets
THE-E
Click to expand...
Click to collapse
Hello MR THE-E
I install my rom I8150JPKJ3_OJPKJ4 (2.3.5) from
http://forum.xda-developers.com/showthread.php?t=1458964
And after that I cannot upgrade the device
I tried about->software update->update result = No update avalable
Then I tried kies but kies show not error and current firmware version: I8150JPKJ3/I8150OJPKJ4/I8150XXKJ1/I8150JPKJ3
The device was rooted after reading this thread I unroot the device and try but the same result
can you help me please?!?!?
what is SGW?????

SGW is our phone: Samsung Galaxy W(W for Wonder) aka Ancora.
The reason I believe, that you can not upgrade to 2.3.6 is that your region have no update yet.
You might want to wait a bit longer if you want original firmware.
Sent from my GT-I8150 using XDA App

New carrier unlocked GSM M8

This is the first carrier unlocked phone I've purchased. It's brand new and I bought it because I'm an M8 fanboy and my first M8 is dying. I'm on AT&T. I just got the phone and installed my SIM and setup my google accounts and all that stuff. I want to update Android but when I go to setting/about/software updates all it says is "checking". It's been checking for over an hour. Did I do something wrong? Is there a way to get the latest OTA Android for an AT&T M8?
My plan is to get to MM then unlock the bootloader and flash TWRP so I can start flashing custom ROM's. I never did anything to my original M8 but have done rooting etc on my old HTC Vivid and both my ASUS tablets.
Thanks in advance for your help.

Post fastboot getvar all result (remove serial & imei no.)
If it is a EU variant, then you can install RUU to update it to Marshmallow.

ckpv5 said:
Post fastboot getvar all result (remove serial & imei no.)
If it is a EU variant, then you can install RUU to update it to Marshmallow.
Click to expand...
Click to collapse
First, thanks for your reply ckpv5.
Second, not sure I'm following you. I can connect via ADB and it show this when I use the devices command:
device product:htc_europe model:HTC_One_M8 device:htc_m8
Is that the correct ADB command or am I just doing it wrong. Could you please provide more information. I'd really appreciate it. This is my first carrier unlocked phone so I'm a noob at this.

theandies said:
First, thanks for your reply ckpv5.
Second, not sure I'm following you. I can connect via ADB and it show this when I use the devices command:
device product:htc_europe model:HTC_One_M8 device:htc_m8
Is that the correct ADB command or am I just doing it wrong. Could you please provide more information. I'd really appreciate it. This is my first carrier unlocked phone so I'm a noob at this.
Click to expand...
Click to collapse
adb reboot bootloader
fastboot getvar all

Thanks for everyone's replies so far.
Here is what I get when doing the adb commands suggested.
{
"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 help me continue with getting this phone updated to at least MM.
:good:

theandies said:
Thanks for everyone's replies so far.
Here is what I get when doing the adb commands suggested.
Now help me continue with getting this phone updated to at least MM.
:good:
Click to expand...
Click to collapse
Download this RUU.zip
Rename it by deleting everything in name of the .zip except for 0P6BIMG (and .zip of course)
Place the renamed .zip onto your extSD card and put it into your phone. (the card must be formatted to FAT32 for this, and if it is 32gb or less, it probably already is)
Boot to bootloader and follow the prompts (vol up to confirm the flash ~ power button to reboot after it's flashed)
And that's it, super easy.
Make sure to delete the renamed .zip after the flash, or every time you boot to bootloader it'll try to update again
Good luck!

Awesome. Trying it now.
Can you school me on the information that I posted? I'm used to messing with WiFi only tablets and this is my first time messing this deep into a phone. I don't want to brick my brand new M8 so I'm going real slow.
Here is some more info if needed. I see it says s-off, is that correct? Also, once I update can I then proceed to flash TWRP and custom ROM's?

Thanks. Updated to Android 6!!! Now beware I'll have a lot more questions.

theandies said:
Thanks. Updated to Android 6!!! Now beware I'll have a lot more questions.
Click to expand...
Click to collapse
Cool! glad I could help.
A little info: since you are S-Off you shouldn't need to unlock the bootloader before you flash TWRP and ROMs, S-Off is all you'll need.

So it IS s-off! Cool. Any way you could tell me how you knew what RUU to use? Just trying to learn.

theandies said:
So it IS s-off! Cool. Any way you could tell me how you knew what RUU to use? Just trying to learn.
Click to expand...
Click to collapse
Your version-main in your getvar/ OS in your bootloader is your current firmware version. To find what you need for updating, the third series of numbers is what is important to match. In your case that was 401 which = WWE/Interanational
But that won't matter with your M8, only if you get a newer HTC device. The RUU I linked you to is not only the latest, but also the last firmware/ROM update for the M8. It won't be updated anymore and hasn't been for almost a year. In general, manufacturers and carriers will only update a device for two years.

xunholyx said:
Your version-main in your getvar/ OS in your bootloader is your current firmware version. To find what you need for updating, the third series of numbers is what is important to match. In your case that was 401 which = WWE/Interanational
But that won't matter with your M8, only if you get a newer HTC device. The RUU I linked you to is not only the latest, but also the last firmware/ROM update for the M8. It won't be updated anymore and hasn't been for almost a year. In general, manufacturers and carriers will only update a device for two years.
Click to expand...
Click to collapse
Understood. I have one more problem. My mobile data is not working. I checked all the APN settings and all of them are grayed out. Any ideas on what to do? I'll post a screenshot in a while. Just got to work.
I also tried *#*#4636#*#* but I really don't want to do anything with that yet as I really don't know what to do there and don't want to make things worse.
Texting and phone calls are working just fine.
Well snooping around the internet at work tonight I was able to figure out that I need to set my APN setting. More snooping and I found an APN setting that works......kind of. It will not go 4G LTE only HSPA. Here is a screen shot and the APN settings that get me HSPA.
I will try and duplicate the APN settings from my old phone in the mean time does anyone have a known good 4G (or 4G LTE) AT&T APN that will work with this phone? Hopefully I've posted enough information for the experts to help me get back up to speed.

Either of those APNs should work fine. Literally, the grayed out one (nextgenphone) is the one I'm on now, and it works flawlessly for me (3G, LTE, MMS, etc.). The one you entered (ATT Phone) I believe is actually the new/current one being used as default on most newer ATT phones, and should work fine as well. Your problem isn't APN, I think it's the RUU you used.
I would suggest using the AT&T RUU 6.20.502.5 from here (see RUU section): https://forum.xda-developers.com/showthread.php?t=2751432
Note the red text below the RUU. If you get Error 155 installing the RUU, you'll need to fastboot flash the firmware, before the RUU will install properly (peculiarity of US Marshmallow RUUs).
Reason you need the AT&T RUU, is that by flashing the Euro RUU, you installed the Euro radio, which is only intended to support LTE bands 3, 7, 8, 20. AT&T uses LTE bands 2, 4, 5, and 17. Therefore, you are missing support for every LTE band used by AT&T (the band or bands used by AT&T in you local area being the most important), and explains why everything works but LTE.

Great information redpoint73. I'll flash the other RUU this weekend.
Please bear with me, when you say flash via. fastboot you mean using ADB and pushing it though USB from my computer? Forgive me but as I said this is my first phone I've messed with this deep. My experience has been on ASUS tablets and most of the custom stuff done on them is usually flashed via SD card (or internal storage) 99% of the time. I can do it with the help of XDA I just don't want to render my new M8 inoperable.

theandies said:
when you say flash via. fastboot you mean using ADB and pushing it though USB from my computer?
Click to expand...
Click to collapse
If you read the red colored note regarding Error 155, under the RUUs in my Index thread (which I linked) you will see another link there, to a separate post/thread that will tell you exactly how to flash the firmware (if needed). Follow those instructions, and you will be good.
Flash via fastboot uses your computer and USB. But keep in mind that adb and fastboot are similar, but not exactly the same.

I see the RUU you suggested is an .exe file. Just connect via ADB and run that file? Also I downloaded the firmware you suggested as well. To avoid any issues should I flash that first before the RUU?
Thanks

theandies said:
I see the RUU you suggested is an .exe file. Just connect via ADB and run that file? Also I downloaded the firmware you suggested as well. To avoid any issues should I flash that first before the RUU?
Thanks
Click to expand...
Click to collapse
Just hook up your phone and double click on the download. The .exe will install a lot like software for your PC
If it fails to install booting to bootloader first before starting the RUU.exe sometimes helps.
On HTC's US website, there are both manual update instructions and a download for the RUU
I'm not sure if you'll need to flash the firmware first since you are already on Android 6, but it couldn't hurt to do so, and you might actually need to.

Awesome, this place is full of great people willing to help. I just wish I could reciprocate more.

theandies said:
Also I downloaded the firmware you suggested as well. To avoid any issues should I flash that first before the RUU?
Click to expand...
Click to collapse
It wouldn't hurt to flash firmware first. Only reason I would suggest folks to run the RUU first (and see if it works) is because not everyone is comfortable using fastboot commands to flash the firmware (and therefore may avoid having to learn how to do that). But if you are comfortable with the process to flash the firmware (it's not hard), then go ahead and do so before running the RUU.
Like xunholyx, I'm not sure if you need to flash the firmware first, or not. If you were coming from Lollipop, you definitely would need to. I have a feeling that you will indeed need to flash the US firmware before the RUU will install. Even though you are on Marshmallow firmware, it's the Euro one, so I think (but not sure) the RUU will still fail until you flash the US MM firmware.

EDIT - Forget it I found it........duh.
Thanks redpoint73. I'm going to flash the firmware first because of what you said (Euro phone vs. US).
I can't seem to find your post on how to do that again in the sea of posts. I thought I bookmarked it but it's not there. Can you be so kind as to link it up.
:good:

SM-G960FD Flash Stock Firmware gets stuck on recovery.img

Hello all, So I have been flashing for years but I am a complete nOOb. Ive just spent 4 hours looking around the internet and XDA for a solution to this issue... Any thoughts or help would be greatly appreciate it!
First off when I received this phone I waited the 7 days for Samsung's new security feature (I came from a S5 so this was a shock). Flashed TWRP with no issues. Proceeded over a few weeks to flash Lineage, Resurrection remix, and then tried to flash Light ROM for the s9. Had some issues with that so I flashed back to Stock Firmware no issue and have been using the past month. Now that I am not busy again I wanted to get twrp back on my phone but OEM unlock was not available. Thought that was weird seeing as the up time was well over the 168 hour marker so I decided to factory reset just to see if that would reset it. I waited the 7 days again and still wasnt there. So I wanted to Flash Stock rom again but now whenever I do it this pops up on the download screen:
sw rev. check fail (bootloader) device 2, binary 1
and Odin is stuck on the recovery.img protion.
Please let me know if you an help or if more info is needed!

Check you're not trying to downgrade the bootloader as shown here
G960FXXU2BRGA << Version 2
Check which version it says in Download mode (B:1 or B:2)
Either match it or flash a higher version

*Detection* said:
Check you're not trying to downgrade the bootloader as shown here
G960FXXU2BRGA << Version 2
Check which version it says in Download mode (B:1 or B:2)
Either match it or flash a higher version
Click to expand...
Click to collapse
{
"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"
}
Picture is of my download screen and ,
Great call! Just dug into it some more and thats the issue. Since the PAK CSC isnt on U2 yet im going to flash one from another country. I know you can but ive never heard of the downsides of flashing another countries firmware... is there one? Also have you heard of the issue with the oem unlock not appearing after 7 days?
Edit: Also what is the proper way to give you credit for answering the question as well as pointing out a good answer for people in the future who are confused? Just the thanks button?
Update: I tried again with a swiss one with Version 2 but it still failed. Ill download a few and try them as well just to be sure.

drowsy_fish said:
Picture is of my download screen and ,
Great call! Just dug into it some more and thats the issue. Since the PAK CSC isnt on U2 yet im going to flash one from another country. I know you can but ive never heard of the downsides of flashing another countries firmware... is there one? Also have you heard of the issue with the oem unlock not appearing after 7 days?
Edit: Also what is the proper way to give you credit for answering the question as well as pointing out a good answer for people in the future who are confused? Just the thanks button?
Update: I tried again with a swiss one with Version 2 but it still failed. Ill download a few and try them as well just to be sure.
Click to expand...
Click to collapse
Yea just hit the thanks button if someone helped (I don't see your image)
Only real downsides I've heard of are things like VoLTE and WiFi calling not being active on certain CSCs
Check the "Repartition" option in ODIN 3.13.1 settings too, possible the custom ROM messed them up
OEM unlock does seem to be hit and miss for some people, some get it immediately (I did), some wait 7 days, others wait 7 days and nothing, not seen a solution other than just keep waiting yet

*Detection* said:
Yea just hit the thanks button if someone helped (I don't see your image)
Only real downsides I've heard of are things like VoLTE and WiFi calling not being active on certain CSCs
Check the "Repartition" option in ODIN 3.13.1 settings too, possible the custom ROM messed them up
OEM unlock does seem to be hit and miss for some people, some get it immediately (I did), some wait 7 days, others wait 7 days and nothing, not seen a solution other than just keep waiting yet
Click to expand...
Click to collapse
Eh im not to worried about VoLTE or WifiCalling so thats good but I was under the impression you needed a PIT file to re-partition your phone without bricking it? (No clue whata PIT file is , just remember reading that about 5 years ago)
Hmm thats annoying.... the idea for this security is nice but it is sure a hassle for people who want custom binaries.

drowsy_fish said:
Eh im not to worried about VoLTE or WifiCalling so thats good but I was under the impression you needed a PIT file to re-partition your phone without bricking it? (No clue whata PIT file is , just remember reading that about 5 years ago)
Hmm thats annoying.... the idea for this security is nice but it is sure a hassle for people who want custom binaries.
Click to expand...
Click to collapse
PIT file is now included in the CSC part of the firmware (Partition Information Table)
Yea Samsung have really gone to town on locking down devices lately, I haven't even bothered rooting a phone since my S5, had an S7 and now S9 since then, just left them stock

*Detection* said:
PIT file is now included in the CSC part of the firmware (Partition Information Table)
Yea Samsung have really gone to town on locking down devices lately, I haven't even bothered rooting a phone since my S5, had an S7 and now S9 since then, just left them stock
Click to expand...
Click to collapse
God, I loved the S5... solid phone. Had it up to just 3 months ago when I got the s9.
I had just tried to flash the firmware I just used and failed with. But I clicked to fast and forgot to check the box for it to re-partition with. Weirdly enough it flashed with no issue... I have no clue what happened but it must have just been those 1s and 0s being finicky. Thanks for the info about the bootloader ect though.... you have been a huge help brother

drowsy_fish said:
God, I loved the S5... solid phone. Had it up to just 3 months ago when I got the s9.
I had just tried to flash the firmware I just used and failed with. But I clicked to fast and forgot to check the box for it to re-partition with. Weirdly enough it flashed with no issue... I have no clue what happened but it must have just been those 1s and 0s being finicky. Thanks for the info about the bootloader ect though.... you have been a huge help brother
Click to expand...
Click to collapse
Nice one, just a glitch in the matrix no probs :good:

*Detection* said:
Check you're not trying to downgrade the bootloader as shown here
G960FXXU2BRGA << Version 2
Click to expand...
Click to collapse
I am also stuck at recovery.img in Odin, while downgrading to a 6 months older stock firmware. The long story short - I want the older firmware because I have a TWRP backup done while this older stock rom was installed on my phone. When upgraded to the new stock firmware, I lost root and restored the TWRP backup (incl. boot) but in the end it the phone doesn't start up. So I want to install the older stock rom in order to be able to restore the TWRP backup. Any ideas how to do that? My only wish is to have a phone that boots and to which I can restore the TWRP backup (where all my apps and settings are).
Update: managed to flash the new firmare, I obviously cannot flash the older firmware because of the older bootloader. So, any ideas how to restore the TWRP backup (made when the old firmware was installed) while the new firmware is currently installed?

How To Guide Root Galaxy A22 SM-A225F Android 11

{
"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"
}
How to Root:
1. Unlock Bootloader
Boot to Downloadmode
On first screen press and hold volume up button until unlock screen appears
2.Flash my Magisk-prepatched boot.img with Odin
In Odin first untick the autoreboot
press on AP, select my customboot.tar and press Start
Dont Reboot !!!! You need to Factory Format or it will bootloop so turn device off and reboot to recovery and make factory reset
3.Reboot
Attention !!! I made my own Kernel for this customboot.tar The device Starts with Selinux Permissive so only use it if you know what you do here
Viper4Android is working with my Kernel
to make your own patched boot.img download stockboot.tar extract it with 7zip and patch the extracted .img on your Phone ....than pack the patched img as .tar and flash it with odin

hi, can you or someone explain more carefully?
how to unlock bootloader? how to flash that magisk prepated boot.img? what is odin and where do I get it?
do I need my own kernel for this customboot.tar? Also, what is customboot.tar and where do I download it?
Please, we need something much more clear.

virividiann1434 said:
hi, can you or someone explain more carefully?
how to unlock bootloader? how to flash that magisk prepated boot.img? what is odin and where do I get it?
do I need my own kernel for this customboot.tar? Also, what is customboot.tar and where do I download it?
Please, we need something much more clear.
Click to expand...
Click to collapse
take a look under Attachments there you can download stock and custom.tar

Hi there! I have couple ( 4 pcs) of Samsung Galaxy A22(SM-A225F) 4G 64gb devices. I successfully flashed and root two of them, but the other two no. Both phones where i succeeded with flash and root have spec: AP: A225FXXU1AUG1, CP:A225FXXU1AUF5, CSC:A225F0LE1AUG1. The other two I bricked are with AP:A225FXXU2AUH1, CP:A225FXXU2AUH1, CSC: A225F0XM2AUH4. The problem is that the two bricked phones worked but missing IMEI and baseband connection also when i check wit *#1234# the CP is missing. How can I restore my phones to work?

dimitrov94 said:
Hi there! I have couple ( 4 pcs) of Samsung Galaxy A22(SM-A225F) 4G 64gb devices. I successfully flashed and root two of them, but the other two no. Both phones where i succeeded with flash and root have spec: AP: A225FXXU1AUG1, CP:A225FXXU1AUF5, CSC:A225F0LE1AUG1. The other two I bricked are with AP:A225FXXU2AUH1, CP:A225FXXU2AUH1, CSC: A225F0XM2AUH4. The problem is that the two bricked phones worked but missing IMEI and baseband connection also when i check wit *#1234# the CP is missing. How can I restore my phones to work?
Click to expand...
Click to collapse
Try to flash stock from this website. If the IMEI is still gone, re-partition and maybe even select NAND Erase. That's how I restored IMEI on my device.

Successful Root!!!!

Hi i have a few questions:
- Why do you uploaded stockboot.tar? Is that the original boot.img in case we want to go back to the original unrooted?
- Can this root method be model dependent? Mine is SM-A225MZKEARO , not the global version, and it has NFC; can it loose functionality by applying your image?
- Does this root method bypasses SafetyNet?
Thanks in advance, great work.

BlueTower said:
Try to flash stock from this website. If the IMEI is still gone, re-partition and maybe even select NAND Erase. That's how I restored IMEI on my device.
Click to expand...
Click to collapse
I have this same problem but on an A32.
I would try re-partitioning and maybe NAND erase as you say, but:
- do I need the PIT file later?
- doesn't that finish erasing the nvram, efs or whatever contains the IMEI information and finish killing the phone capabilities?
Tanks!

Fixed it on the a32, working so far
[fixed] rooted a325m suddenly no imei, no sim
I rooted my a325m by patching the stock AP file with magisk, had to use FRP hijacker by hagard to be able to flash the patched file. I root uninstalled several apps for debloating. The phone worked fine for like a couple of weeks, and now...
forum.xda-developers.com

Hello all, I bought a phone on installment payment but i wasn't able to continue the payment. But unfortunately, there is an APP on the PHONE that automatically LOCK the phone one the PAYMENT has DUE. My question is: Is there a way I can remove the APP from my phone ENTIRELY without it (the phone) been lock again?
The device name is SAMSUNG A22 4G
The company is M-KOPA

Adekunlex said:
Hello all, I bought a phone on installment payment but i wasn't able to continue the payment. But unfortunately, there is an APP on the PHONE that automatically LOCK the phone one the PAYMENT has DUE. My question is: Is there a way I can remove the APP from my phone ENTIRELY without it (the phone) been lock again?
The device name is SAMSUNG A22 4G
The company is M-KOPA
Click to expand...
Click to collapse
Phone is locked. Since u do not have root access to the phone, it is a paper weight. But, after paying it off they would have unlocked it or at least told u the steps to unlock it. Always buy phones out right and unlocked, otherwise u buy a paper weight in the end.

I think you should not buy used phones because the price of the phones is not too expensive and now telcos have a policy of buying new phones without losing money but with the condition that they sign a long-term contract with them. This ensures the security of your information.
getting over it​

Question Downgrade to Android 12

I'm having issues trying to downgrade to Andriod 12 from andriod 13 beta 3.
1. I've opted out of Beta
2. Software update notification received
3. Click on download and install
4. After a couple of mins get error message couldn't update 'Installation problem'
The screen remains on the update screen.
What am i doing wrong please help?
Device state: locked
edit:actually now I'm stuck in Fastboot Mode
Phone keeps rebooting back to Fastboot mode

With a locked bootloader, your only option to get fixed is to try sideloading an OTA - usually, the OTA has to be either the same as what you were most recently running or newer. Click the yellow How To Guide quick filter at the top of the list of threads for one of the root guides. Even though you're not rooting, one or two of them should tell how to sideload an OTA - just ignore things that reference root.
This is why the instructions for the Beta program say you should have an unlocked bootloader, as without an unlocked bootloader your choices to fix the situation are much more limited.

roirraW edor ehT said:
With a locked bootloader, your only option to get fixed is to try sideloading an OTA - usually, the OTA has to be either the same as what you were most recently running or newer. Click the yellow How To Guide quick filter at the top of the list of threads for one of the root guides. Even though you're not rooting, one or two of them should tell how to sideload an OTA - just ignore things that reference root.
This is why the instructions for the Beta program say you should have an unlocked bootloader, as without an unlocked bootloader your choices to fix the situation are much more limited.
Click to expand...
Click to collapse
thanks for that, any advice on how to ota pls?
Can't find any instructions sorry.

riz157 said:
thanks for that, any advice on how to ota pls?
Click to expand...
Click to collapse
You're welcome. Since I never do the OTA process, I always flash the full firmware zip (which you can't do with a locked bootloader), I can't advise any further than what I said about using the quick filter for the How To Guides. At least one or two of these threads should help you, although they may concentrate on doing so with rooting, as long as you ignore the root parts to the OTA method, you can still follow the instructions. You'll get better help to any questions in one of the threads that give OTA sideload instructions:
{
"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"
}

roirraW edor ehT said:
Yo
You're welcome. Since I never do the OTA process, I always flash the full firmware zip (which you can't do with a locked bootloader), I can't advise any further than what I said about using the quick filter for the How To Guides. At least one or two of these threads should help you, although they may concentrate on doing so with rooting, as long as you ignore the root parts to the OTA method, you can still follow the instructions. You'll get better help to any questions in one of the threads that give OTA sideload instructions:
View attachment 5642011
Click to expand...
Click to collapse
much appreciated yes want to avoid root or unlocking the bootloader, why does google have it to make it so difficult to downgrade. Maybe take a leaf out of apple's book

To sideload you need USB debugging enabled. Reboot the device to recovery, either by powering off the device and holding power and volume up, let go of power when the phone vibrates, on the the android with an exclamation mark, tap on volume up I think it is. Or by typing in terminal
Code:
fastboot reboot recovery
since it's stuck in fastboot. In recovery tap on 'apply update from adb'
Then download the ota package from here.
Grab the platform tools (Google for it) and unzip it to c:\platform-tools if you're running windows. Open a terminal in the platform tools folder and type
Code:
adb sideload /path_to_ota.zip
Let it do its thing and you should be up and running. I wouldn't try to downgrade from the a13 beta, but you can try. Good luck!

riz157 said:
thanks for that, any advice on how to ota pls?
Can't find any instructions sorry.
Click to expand...
Click to collapse
Just a few things. You don't need USB debugging enabled for OTA updates (you can't boot into Android to enable it anyway).
Just be aware that with OTA's, you can't downgrade - only reinstall the same version or upgrade, so you need to make sure you're on Android 13 to reinstall ota version 13 (recovery mode will tell you your version).
Here's a video to help with the ota update.

riz157 said:
I'm having issues trying to downgrade to Andriod 12 from andriod 13 beta 3.
1. I've opted out of Beta
2. Software update notification received
3. Click on download and install
4. After a couple of mins get error message couldn't update 'Installation problem'
The screen remains on the update screen.
What am i doing wrong please help?
Device state: locked
edit:actually now I'm stuck in Fastboot Mode
Phone keeps rebooting back to Fastboot mode
Click to expand...
Click to collapse
Any luck with your device?

Alekos said:
Any luck with your device?
Click to expand...
Click to collapse
No luck finally contacted Google who will have this sorted.

riz157 said:
No luck finally contacted Google who will have this sorted.
Click to expand...
Click to collapse
What happened with the OTA updates? Did it complete? Getting the windows driver and fastboot/adb (platform-tools) to all work can be tricky..

what about the https:// flash.android .com/build/8151327?target=raven-user&signed=true Website?

jlede18 said:
what about the https:// flash.android .com/build/8151327?target=raven-user&signed=true Website?
Click to expand...
Click to collapse
Flash.android uses fastboot, which requires the bootloader to be unlocked. User can't unlock it since Android won't boot..

I don't think I'll be flashing beta version again lol, too much hassle to downgrade.
In the end decided to send in to Google to repair.
I think they will give me a replacement instead of repairing it.
Did anyone notice any major bugs with android 13, can't say I did?

Alekos said:
What happened with the OTA updates? Did it complete? Getting the windows driver and fastboot/adb (platform-tools) to all work can be tricky..
Click to expand...
Click to collapse
Decided against that, off to Google to fix

Alekos said:
Flash.android uses fastboot, which requires the bootloader to be unlocked. User can't unlock it since Android won't boot..
Click to expand...
Click to collapse
Copy that. Would of probably just been easier to reflash the beta back save everything, unlock the bootloader and then flash android 12

jlede18 said:
Copy that. Would of probably just been easier to reflash the beta back save everything, unlock the bootloader and then flash android 12
Click to expand...
Click to collapse
Yup, very easy to flash ota, but op didn't feel comfortable doing it unfortunately.

Might seem dumb but I used the web browser tool and flashed back to stock via that from 13 B3 it unlocks bootloader and flashes and re locks bootloader , back on stable 12 working fine then opted out of 13 beta

The way I did it was downloading the entire firmware from google and then changing the config to remove- w so your data doesn't get wiped. Then running the .su or .bat depending on your is. It worked for me. Cheers