SM-G960FD Flash Stock Firmware gets stuck on recovery.img - Samsung Galaxy S9 Questions & Answers

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?

Related

Unlocking Bootloader

I just Rooted my Z1 Compact by this method http://forum.xda-developers.com/showthread.php?t=2642081 and now I have 4.3 firmware UK. Now I have some questions:
1. When I check on phone if unlocking bootloader is possible, it says no. I haven't read that article about unlocking fully, but is there still any way to unlock it? Because, once Stable official CM comes out, I could install it.
2. When I check for software update, it says already latest, and doesn't provide KitKat(Don't forget I'm on UK rooted 4.3). Why? Also do I loose root if I update by official software?
3. As I said, once CM, stable comes out I will install it. But until then, I'm gonna stay on official firmware + root. What is simplest way to update to latest firmwares but still having root(or if really required, first updating, then rooting that latest firmware)?
I tried to be as straight as possible with my questions, and it would really mean a lot to me, any useful answers because I don't have much time for reading all those posts. Note that before this phone I had already Samsung galaxy mini with many roms, but for this phone it's much more complicated, so that's why I'm asking this all. Thanks.
Smoller said:
I just Rooted my Z1 Compact by this method http://forum.xda-developers.com/showthread.php?t=2642081 and now I have 4.3 firmware UK. Now I have some questions:
1. When I check on phone if unlocking bootloader is possible, it says no. I haven't read that article about unlocking fully, but is there still any way to unlock it? Because, once Stable official CM comes out, I could install it.
2. When I check for software update, it says already latest, and doesn't provide KitKat(Don't forget I'm on UK rooted 4.3). Why? Also do I loose root if I update by official software?
3. As I said, once CM, stable comes out I will install it. But until then, I'm gonna stay on official firmware + root. What is simplest way to update to latest firmwares but still having root(or if really required, first updating, then rooting that latest firmware)?
I tried to be as straight as possible with my questions, and it would really mean a lot to me, any useful answers because I don't have much time for reading all those posts. Note that before this phone I had already Samsung galaxy mini with many roms, but for this phone it's much more complicated, so that's why I'm asking this all. Thanks.
Click to expand...
Click to collapse
1. If you got your Phone from a provider then you're probably out of luck.
2. Should have used this instead if you want KK - http://forum.xda-developers.com/showthread.php?t=2688933
3. Read the forums with each new release, unless you unlock the BL you'll have to wait for a method like above.
XperienceD said:
1. If you got your Phone from a provider then you're probably out of luck.
2. Should have used this instead if you want KK - http://forum.xda-developers.com/showthread.php?t=2688933
3. Read the forums with each new release, unless you unlock the BL you'll have to wait for a method like above.
Click to expand...
Click to collapse
Well, yeah it's from T-mobile, so there is no way to unlock bootloader? Thanks for link, but is there any way to update just using phone? I have problems with PC, whenever PC detects flash drive inserted(my phone in flash mode) it freezes at the end of installation, so I have to flash on another PC, which is frustrating as I can do that like every 2 weeks(I have only 1 PC)
Smoller said:
Well, yeah it's from T-mobile, so there is no way to unlock bootloader?
Click to expand...
Click to collapse
Unfortunately, no. I had my Z for about year living in hope but Sony have locked it down too much for the devs to crack, so I'll never get another Phone from a carrier again.
Smoller said:
Thanks for link, but is there any way to update just using phone?
Click to expand...
Click to collapse
Modding the Phone breaks the OTA update service which is why, once you decide to start modding you're better off just flashing an .ftf to update.
Smoller said:
Well, yeah it's from T-mobile, so there is no way to unlock bootloader? Thanks for link, but is there any way to update just using phone? I have problems with PC, whenever PC detects flash drive inserted(my phone in flash mode) it freezes at the end of installation, so I have to flash on another PC, which is frustrating as I can do that like every 2 weeks(I have only 1 PC)
Click to expand...
Click to collapse
Z1 compact from tmobile? or z1s? or you have a z1 compact on tmobiles network? If it says bootloader unlocked allowed: no, you cant unlock it and will not be able to install cm. Where did you get the phone from?
Correct me if I'm wrong but.... Xperia Z1 Compact is still not available in US much more on carriers like T-Mobile.
If I guess correctly, 'bootloader unlocked allowed: No' should be stored in the TA partition. Maybe it's not so hard to find, if you compare two TA backups (one disallowed and one allowed). Is there any research done already about that?
@Smoller do you have a backup of your TA partition (DRM keys)?
@zxz0O0
It's impossible by just comparing. I'm not sure if you still remember my reply on your bootloader unlocking thread but I posted there a comparison between 2 the same TA backup just between 2 reboots and the result was that they are very2 different from each other.
zxz0O0 said:
If I guess correctly, 'bootloader unlocked allowed: No' should be stored in the TA partition. Maybe it's not so hard to find, if you compare two TA backups (one disallowed and one allowed). Is there any research done already about that?
@Smoller do you have a backup of your TA partition (DRM keys)?
Click to expand...
Click to collapse
Riyal said:
@zxz0O0
It's impossible by just comparing. I'm not sure if you still remember my reply on your bootloader unlocking thread but I posted there a comparison between 2 the same TA backup just between 2 reboots and the result was that they are very2 different from each other.
Click to expand...
Click to collapse
What? You made a TA backup on your phone and after 2 reboots it was completetly different? No I've never seen a post like that, that sounds really weird.
I would really be interested to see this myself.
Yes it says exactly bootloader unlock allowed: No. And I'm from Croatia so most likely it is also available in other Europe countries, especially UK...From T-Mobile...really weird it's not still on US Tmobile because this phone is made in January. And I can make a DRM backup if needed, if there might be any way to unlock bootloader. Also, just to be sure, if I input unlock SIM code for other carriers, it has still everything same except possibility to put SIM cards and use other carriers, right?
Sent from my D5503 using xda app-developers app
zxz0O0 said:
What? You made a TA backup on your phone and after 2 reboots it was completetly different? No I've never seen a post like that, that sounds really weird.
I would really be interested to see this myself.
Click to expand...
Click to collapse
@zxz0O0
You did forget it... Anyways here it is... 2 working TA backups made from the same version of Backup TA. What I only did between the 2 backups was
1. Make the 1st backup
2. Reboot the phone
3. Make the 2nd backup
And here are the results.
Please do note that I tried both TA backups and both of them are perfectly fine when restored on my phone. Also I made a 3rd TA backup and it's also very different from the last 2 backups which is shown in the screenshot.
{
"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"
}
Riyal said:
@zxz0O0
You did forget it... Anyways here it is... 2 working TA backups made from the same version of Backup TA. What I only did between the 2 backups was
1. Make the 1st backup
2. Reboot the phone
3. Make the 2nd backup
And here are the results.
Please do note that I tried both TA backups and both of them are perfectly fine when restored on my phone. Also I made a 3rd TA backup and it's also very different from the last 2 backups which is shown in the screenshot.
Click to expand...
Click to collapse
Isn't it only the log that changed? And the padding at the end? If not then I guess the partition is randomly encrypted and the key is stored inside the partition.
zxz0O0 said:
Isn't it only the log that changed? And the padding at the end? If not then I guess the partition is randomly encrypted and the key is stored inside the partition.
Click to expand...
Click to collapse
Nope! The log there is only like 4 lines. While the difference between both files are hundreds or even thousands of lines You could see the grey and yellow markings on the left. That should graphically show you what & how big the difference are between the 2 files.

AOSP on Sprint $$$

$20 to the dev who gets AOSP to work on Sprint's latest 1.80.651.30, WITHOUT using foreign firmware.
We're about a year into this device, and apparently we have no developers on the Sprint side working on this.
Not sure if that price is worth it to anyone, but I'm a man of my word.
mcwups1 said:
$20 to the dev who gets AOSP to work on Sprint's latest 1.80.651.30, WITHOUT using foreign firmware.
We're about a year into this device, and apparently we have no developers on the Sprint side working on this.
Not sure if that price is worth it to anyone, but I'm a man of my word.
Click to expand...
Click to collapse
You contacted me multiple times about editing the Verizon guide for Sprint.. I took my free time to respond.. and now you post this.. A bit of a slap in the face, no? :silly:
I would contact the Devs working on AOSP personally, however with N already here (and coming soon to the rest of the carriers), I personally don't see anyone taking their time on MM (just an opinion).
I do hope you get it working. :good:
andybones said:
You contacted me multiple times about editing the Verizon guide for Sprint.. I took my free time to respond.. and now you post this.. A bit of a slap in the face, no? :silly:
I would contact the Devs working on AOSP personally, however with N already here (and coming soon to the rest of the carriers), I personally don't see anyone taking their time on MM (just an opinion).
I do hope you get it working. :good:
Click to expand...
Click to collapse
No, you never got back with my question!
I have your zip, but haven't flashed it, because I'm not sure if it needs "modified" for Sprint.
Plus, I am looking for it to work with Sprint firmware first.
mcwups1 said:
No, you never got back with my question!
I have your zip, but haven't flashed it, because I'm not sure if it needs "modified" for Sprint.
Plus, I am looking for it to work with Sprint firmware first.
Click to expand...
Click to collapse
"No, you never got back with my question!"
I responded last night, and I quoted you so you'd get a notification to see it.
http://forum.xda-developers.com/showpost.php?p=70256059&postcount=15
The whole point of this method is to get back to stock Verizon/Sprint.
If you do my method you will be back on 100% Sprint (Since you are flashing the Sprint RUU AFTER the modified firmware) AND AOSP ROMs working. I don't know why, but it works. It's been confirmed on a number of Verizon users AND Sprint.
"Plus, I am looking for it to work with Sprint firmware first"
Then why did you contact me multiple times? I am not going to apologize for taking longer than you'd like to respond.. I wrote the guide for Verizon, so excuse me for not wanting to brick your device with rushed info..
Like I said, I hope you get it working.. I did respond in the thread, and as I said if you need help editing the android.info.txt, let me know. :good:
I didn't get it. Responded to the linked thread /post.
Thank you.
I understood your instructions for the firmware and RUU, but didn't think your zip would work with my Sprint device. Thank you so much for the deeper explanation.
Will report back here....
mcwups1 said:
I didn't get it. Responded to the linked thread /post.
Thank you.
I understood your instructions for the firmware and RUU, but didn't think your zip would work with my Sprint device. Thank you so much for the deeper explanation.
Will report back here....
Click to expand...
Click to collapse
You are very welcome my friend!
AOSP/CM ROMs are a great way to change up the device so I understand the want to use them, hence how this method was found.
andybones said:
You are very welcome my friend!
AOSP/CM ROMs are a great way to change up the device so I understand the want to use them, hence how this method was found.
Click to expand...
Click to collapse
@andybones
Just to make sure (on both threads, sorry), my CID is 11111111.
I don't use the Sprint CID, I change the android text to the Super CID number, right?
Okay.
Everything done and I didn't brick.
New problem.
I only have 3G, even after the RUU.
Something tells me I shouldn't have GSM options?
{
"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"
}
mcwups1 said:
Okay.
Everything done and I didn't brick.
New problem.
I only have 3G, even after the RUU.
Something tells me I shouldn't have GSM options?
Click to expand...
Click to collapse
In bootloader run these cmds
fastboot erase modemst1
fastboot erase modemst2
Okay. It appears I have LTE, but now I can't make calls.
Edit: Now, since I woke up this morning, I have no data. I can boot up, but I cannot make calls or message anyone.
Says my device is not activated, and I need to call customer service.
Or, you are not authorized to call this account (calling my wife), if you would like more services, contact customer service.
Showing all zeros for a phone number.
000-000-0000
@andybones
Check your Gmail.
mcwups1 said:
@andybones
Check your Gmail.
Click to expand...
Click to collapse
Thank you kindly my friend! Very much appreciated.
andybones said:
Thank you kindly my friend! Very much appreciated.
Click to expand...
Click to collapse
I can flash CM, but I can't use it.
I cannot make calls or message anyone.
If I restore my Sense backup, then I have no data. I have to erase modems again, just to get messaging back and to get my Sprint ID to return and give me my phone number again.
This has been a major headache, and I don't think this will actually work fully on my device.
Curious to know if you know why I had to input a PIN after flashing that modified firmware zip after reboot?
mcwups1 said:
I can flash CM, but I can't use it.
I cannot make calls or message anyone.
If I restore my Sense backup, then I have no data. I have to erase modems again, just to get messaging back and to get my Sprint ID to return and give me my phone number again.
This has been a major headache, and I don't think this will actually work fully on my device.
Curious to know if you know why I had to input a PIN after flashing that modified firmware zip after reboot?
Click to expand...
Click to collapse
Can't say about Sprint usage and AOSP ROMs or sprint anything really so can't comment on that.
After flashing the firmware it wiped my system so it had no ROM to boot to, so I had to hold volume buttons and power to get into bootloader and then ran the VZW RUU.
I have been using multirom personally since this method as well.
I still wish someone would find a way to get AOSP working on Sprint firmware.
After wiping modems, updating PRL and Profile, I have a working phone again on Sense.
I'm not sure what flashing that zip did, but I'm thinking it changes the internal partitions of firmware, and that Sprint either blocks partitions or doesn't have them, and the zip modded them, or added them.
But WTF do I know?
mcwups1 said:
I still wish someone would find a way to get AOSP working on Sprint firmware.
After wiping modems, updating PRL and Profile, I have a working phone again on Sense.
I'm not sure what flashing that zip did, but I'm thinking it changes the internal partitions of firmware, and that Sprint either blocks partitions or doesn't have them, and the zip modded them, or added them.
But WTF do I know?
Click to expand...
Click to collapse
As I. It seems once/if theres a fix for Sprint, it should also hopefully be the same for Verizon.
Your input is as good as the rest of us.
I've gotten CM/Lineage to work on my Sprint HTC 10. I did have to flash an international firmware zip to get it to get past the boot logo but now it's fine. Note though that I did delete the modems, radio, cache and recovery out of the firmware package before I flashed it. This is likely why you have issues with data now if you didn't do so.
That said, data is still iffy at times on AOSP without toggling some settings after rebooting so it might be worth it for some people to wait until that's fixed before proceeding.
ssmercurys said:
I've gotten CM/Lineage to work on my Sprint HTC 10. I did have to flash an international firmware zip to get it to get past the boot logo but now it's fine. Note though that I did delete the modems, radio, cache and recovery out of the firmware package before I flashed it. This is likely why you have issues with data now if you didn't do so.
That said, data is still iffy at times on AOSP without toggling some settings after rebooting so it might be worth it for some people to wait until that's fixed before proceeding.
Click to expand...
Click to collapse
You should do a write up on the Sprint forums for others.
Their are builds that are out now for sprint that doesn't require a custom firmware
trev23sks said:
Their are builds that are out now for sprint that doesn't require a custom firmware
Click to expand...
Click to collapse
How?

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:

unroot and remove twrp samsung galaxy tab s4

hi guys..
something i need help here.
how to unroot and lock [email protected] twrp
since i bought this tab s4...its already root by old user.
any one can help me this out..
thanks alot.
safuan samad said:
hi guys..
something i need help here.
how to unroot and lock [email protected] twrp
since i bought this tab s4...its already root by old user.
any one can help me this out..
thanks alot.
Click to expand...
Click to collapse
Just use smartswitch! hit update if the update is not there! Then download firmware and flash via odin Job done!!
Then download firmware and flash via odin Job done!!
what firmware would you download .... I am having trouble getting any to install.
Do I have to root it before I can install it.
{
"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"
}
marvinc said:
Then download firmware and flash via odin Job done!!
what firmware would you download .... I am having trouble getting any to install.
Do I have to root it before I can install it.
Click to expand...
Click to collapse
Nope, root is not needed.
Things to check: Do you have the most recent Odin? Did you download firmware for the correct Tab S4 model? Are you installing an older firmware over a newer version already on the tablet? Did you enter the right parts in the right slots in Odin?
I lean toward the thorough/careful side, so I recommend you start over from the beginning, making sure you have all the right stuff. In order to download the right firmware, you need three pieces of information up-front.
(1) Your Tab S4 Model Number
I have the WIFI edition, which has the model number SM-T830.
Go to: Settings -> About Tablet
It shows "Model number" just below the tablet name and [EDIT] button.
(2) Your Firmware Version - "Build Number"
Go to: Settings -> About Tablet -> Software information
Scroll to "Build number"
Installing a firmware with a matching version, or newer (last 4 letters, alphabetical order: ARK4 is newer than ARJ4).
Mine shows "M1AJQ.T830XXU2ARK4", which is the latest version (as of post date) for the SM-T830.
(3) Your "Carrier" or "Service provider"
Same screen as step #2
Settings -> About Tablet -> Software information
Scroll down to "Service provider / SW ver."
The last line in this section is a 3 letter code identifying your carrier.
Mine shows "XAR//", so it's XAR.
Now, go to sammobile.com to download your firmware. You can enter your model number (from step #1) in the search field.
As I mentioned before, my model is the SM-T830.
When you get to the page for your Tab S4 model, scroll down a tad bit and look at the section "LATEST FIRMWARES" and click on the "Select country" list. The list shows a country and the 3-letter code from step #3. My XAR appears in the list as "Cellular south (XAR)"... for some reason that's how Samsung lists the WIFI model for the USA.
After selecting, you will now see a list of firmware releases with dates. You can either just click the most-recent, or check against your firmware from Step #2. Compare the PDA field to your firmware version. My firmware appears in the list as: "2018-12-09 8.1.0 T830XXU2ARK4 T830OXM2ARK4", so I clicked that one (or something more recent if I want the newest). Clicking takes you to the download screen.
You can download via the "WAIT & DOWNLOAD" button, which takes about 2 or 3 hours (they meant it when they said "wait").
Please note on the right side of the page, you will see "INSTRUCTIONS (5 FILES)" which detail how to flash. The first line in the instructions tells you the most recent Odin version (v3.13.1) and provides a link to download it. The rest of the instructions tell you exactly what to do in order to flash. I followed them, though I left the CP slot blank since my model's firmware did not include the CP image.
-Pie
@EatingPie
if you look at the previous post that is exactly what I did .... and nothing would load ... no error message .... just FAIL
someone suggested using USB 2.0 ... I would think the computer would do that automatically
I do not have a working system to look at some of the things you suggested ... I have a factory binary
I think I have an expensive paperweight
I think I will wait a month or so and see if anyone can come up with an answer
How to go from Factory Binary to a working system
marvinc said:
@EatingPie
if you look at the previous post that is exactly what I did .... and nothing would load ... no error message .... just FAIL
someone suggested using USB 2.0 ... I would think the computer would do that automatically
I do not have a working system to look at some of the things you suggested ... I have a factory binary
I think I have an expensive paperweight
I think I will wait a month or so and see if anyone can come up with an answer
How to go from Factory Binary to a working system
Click to expand...
Click to collapse
Your flashing firmware this is not intended for your device, plain and simple.
You will also have a message on the device screen that will tell you the reason as well as the authorisation fail in Odin.
If you want to attempt to flash firmware not intended for your device, you need to be oem unlocked and rmm unlocked.
If you read the first response it says to use SMARTSWITCH. there is no reference to ODIN. if you install SMARTSWITCH on your computer it can restore the factory image. You need to provide the serial number from the device. (Usually printed on rear off device)
N1NJATH3ORY said:
Just use smartswitch! hit update if the update is not there! Then download firmware and flash via odin Job done!!
Click to expand...
Click to collapse
ashyx said:
Your flashing firmware this is not intended for your device, plain and simple.
You will also have a message on the device screen that will tell you the reason as well as the authorisation fail in Odin.
If you want to attempt to flash firmware not intended for your device, you need to be oem unlocked and rmm unlocked.
Click to expand...
Click to collapse
I downloaded a later firmware and it installed ... a second time and it is now working
the first time I installed userdata and it went into a continuous boot
Thanks to everyone that chimed in to help
Marvin
I can post the latest US Firmware I used if you tell me where to post it, and it will save others a great deal of time downloading.
XAR-T830XXU2ARK4_T830OXM2ARK4-20181203.zip
thanks for all the help
Marvin
1eStar said:
If you read the first response it says to use SMARTSWITCH. there is no reference to ODIN. if you install SMARTSWITCH on your computer it can restore the factory image. You need to provide the serial number from the device. (Usually printed on rear off device)
Click to expand...
Click to collapse
Are you reading a different thread or something?
It's mentions odin in post #2, #3 and #4.
ashyx said:
Are you reading a different thread or something?
It's mentions odin in post #2, #3 and #4.
Click to expand...
Click to collapse
I must stop taking drugs. You still don't need ODIN to complete the job.
1eStar said:
I must stop taking drugs. You still don't need ODIN to complete the job.
Click to expand...
Click to collapse
You don't, but Smartswitch can be a pia for some.
Odin is preferred by most.
1eStar said:
If you read the first response it says to use SMARTSWITCH. there is no reference to ODIN. if you install SMARTSWITCH on your computer it can restore the factory image. You need to provide the serial number from the device. (Usually printed on rear off device)
Click to expand...
Click to collapse
can confirm. i'm trading in my s4 for s7+ and even though I had just gone through the tedious process of rooting and twrp'ing the s7+ with odin (so fresh in my mind), it was still such a pain in the ass to try to figure out how to restore my s4 using odin. I fired up smartswitch for PC and it did it in about 30 minutes, one click.
coming from pixel phones, the way samsung rooting works in just crazy complicated to me.

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​

Categories

Resources