Database Users

Best method to root on 4.2.2?

My phone was rooted and I did a factory reset to send it to have the screen repaired. I lost root and I get the message "com.android.phone not responding" all the time if I restart the phone but it works fine. Someone told me to use Odin to wipe the phone and get rid of that message. After I do that, what tool should I use to root on 4.2.2?

Need MORE info. What was the Original firmware/ what firmware do you have right now? You said 4.2.2 but which one? MDB? MDL? or MF3?
MDB and MDL you can do a lot note with and use motochopper + Loki bootloader bypass. MF3 patched the exploit and can only use safestrap recovery.
Read some of the threads once you find which firmware you have and/or on right now. If your stock, then beware it will AUTO UPDATE you without your consent. So find out what you have and need to do quickly.

RockRatt said:
Need MORE info. What was the Original firmware/ what firmware do you have right now? You said 4.2.2 but which one? MDB? MDL? or MF3?
MDB and MDL you can do a lot note with and use motochopper + Loki bootloader bypass. MF3 patched the exploit and can only use safestrap recovery.
Read some of the threads once you find which firmware you have and/or on right now. If your stock, then beware it will AUTO UPDATE you without your consent. So find out what you have and need to do quickly.
Click to expand...
Click to collapse
Thanks.
{
"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"
}
Looks like it's MDL?. So I guess motochopper then. Mine cannot auto update fortunately. It fails every time. I've had it like that for a while but now I really want to root it again. I think it's because of that error I get on start-up that the update fails.

SRCP said:
Thanks.
Looks like it's MDL?. So I guess motochopper then. Mine cannot auto update fortunately. It fails every time. I've had it like that for a while but now I really want to root it again. I think it's because of that error I get on start-up that the update fails.
Click to expand...
Click to collapse
I had a similar situation, and the AT&T updates would fail at ~28%, even though I never approved the updates (my guess is that after I've said no more than 3 time, they did it anyways?). At that point I was stuck, and to make things worse, the WiFi was working only in my house, but no data over the ATT network, just voice. Even reflashing with ODIN didn't resolved the problem.
Had to bite the bullet and get the phone replaced by the warranty. I hope this doesn't happen to anyone else,

SRCP said:
Thanks.
Looks like it's MDL?. So I guess motochopper then. Mine cannot auto update fortunately. It fails every time. I've had it like that for a while but now I really want to root it again. I think it's because of that error I get on start-up that the update fails.
Click to expand...
Click to collapse
Since it is MDL firmware just use Motochopper + Loki and you will have a custom recovery (TWRP or CWM YOUR CHOICE). Then flash ANY custom ROM on your phone. You can have the best of BOTH worlds. You can flash a updated firmware ROM like ShoStock for the Touchwiz based Roms or a AOSP based ROMs. NO need to update firmware from ATT. In fact you lose what you can do with your phone if you do.
If you REALLY want to update to ATT newest firmware you can download the STOCK MDL firmware from samfirmware. Flash it which will make your phone PURE STOCK firmware and recovery. Then you will be able to update from ATT. The reason it fails is because you are rooted and probably custom recovery already?

Thanks. Well, I had it rooted but it seems like I lost root when I did something, I don't remember but I think it's when I factory reset it to send it to be repaired. It still says custom when I turn restart it but I am not rooted. I'm not very knowledgeable at this, I just follow guides step by step. I used an old method to root, it was an automated tool, can't remember the name. Anyway, in my current custom, non-rooted state, sgould I do something first before using motochopper?

SRCP said:
Thanks. Well, I had it rooted but it seems like I lost root when I did something, I don't remember but I think it's when I factory reset it to send it to be repaired. It still says custom when I turn restart it but I am not rooted. I'm not very knowledgeable at this, I just follow guides step by step. I used an old method to root, it was an automated tool, can't remember the name. Anyway, in my current custom, non-rooted state, sgould I do something first before using motochopper?
Click to expand...
Click to collapse
If you got it repaired does it have the same firmware version on it? Got to menu, settings, more, about device and look for the last three characters of your baseband. What are they?
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
If you got it repaired does it have the same firmware version on it? Got to menu, settings, more, about device and look for the last three characters of your baseband. What are they?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah, that pic is recent. I got it repaired months ago.

firmware upgrade encountered an issue! Please help

I know I know there's been quiet a few threads about people screwing up and I'm one of them with a little different problem.
So I really appreciate your help
I have a second I9505 running great on XXUEND1 (almost instant GPS lock) and tried very hard to find this modem to flash on my second I9505 but couldn't find it.
So I thought "lets download the stock which will change the modem, and then restore nandroid" Yes I have a TWRP nandroid I made just before this screw up
So I downloaded this stock from sammobile http://www.sammobile.com/firmwares/download/28734/I9505XXUEND1_I9505TELENC1_TEL
I was on:
GPE 4.4.4
Modem: I9505XXUGNK4
Baseband: I9505XXUGNK4
Loaded the stock firmware in PDA/AP and flashed. FAIL!
Now I can get into download more only (no twrp)
I've attached the screen of Odin 3.09
{
"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 on earth can I flash XXUEND1 and then restore my nandroid???
Cheers guys!

Any help guys? I'm getting nervous here...

The cable should be the stock one and should not be on a hub. Try a different port on the computer, and do not panic. The fact you can get into download mode still means all hope isn't lost.
EDIT: You posted this question twice, with the second location being a development thread, where it really doesn't belong. You received a response there as well: http://forum.xda-developers.com/showpost.php?p=59386461&postcount=18244 . In the future don't cross post, no matter how desparate you are.

Strephon Alkhalikoi said:
The cable should be the stock one and should not be on a hub. Try a different port on the computer, and do not panic. The fact you can get into download mode still means all hope isn't lost.
EDIT: You posted this question twice, with the second location being a development thread, where it really doesn't belong. You received a response there as well: http://forum.xda-developers.com/showpost.php?p=59386461&postcount=18244 . In the future don't cross post, no matter how desparate you are.
Click to expand...
Click to collapse
Thank you, it's directly connected to a port that I've flashed with many times.
I even tried other ports but still same thing.
Did I do wrong by trying to flash the 4.3 from 4.4.4? Or is that asking for trouble?
What else can I do?

sirs2k said:
Thank you, it's directly connected to a port that I've flashed with many times.
I even tried other ports but still same thing.
Did I do wrong by trying to flash the 4.3 from 4.4.4? Or is that asking for trouble?
What else can I do?
Click to expand...
Click to collapse
not sure but it might be partitions (.pit file) - for example one was too short and write failed due to no space left
try flashing the one you were using before (or at least 4.4.2).

Strephon Alkhalikoi said:
The cable should be the stock one and should not be on a hub. Try a different port on the computer, and do not panic. The fact you can get into download mode still means all hope isn't lost.
EDIT: You posted this question twice, with the second location being a development thread, where it really doesn't belong. You received a response there as well: http://forum.xda-developers.com/showpost.php?p=59386461&postcount=18244 . In the future don't cross post, no matter how desparate you are.
Click to expand...
Click to collapse
Yes I'm sorry about that. I was really starting to freak out.
Anyhow, I've managed to flash a 4.4.2 with modem and baseband XXUGNH6. I've also flash the latest twrp. But I would still very much love to complete what I wanted to do in the first place. Which is flashing XXUEND1.
I couldn't find it anywhere as a flashable and I couldn't downgrade to 4.3 which is where it is.
Could you guys please help me get this done?
Cheers

not sure if you have .pit file included in package downloaded form sammobile (the one for 4.3) but if so - add .pit and tick re-partition, while flashing 4.3 as you tried before.
re-partition, if it will include data partition will erease all your data - backup your movies, photos, etc before proceeding.
Sent from my TF300T using XDA Free mobile app

th3cr0w said:
not sure if you have .pit file included in package downloaded form sammobile (the one for 4.3) but if so - add .pit and tick re-partition, while flashing 4.3 as you tried before.
re-partition, if it will include data partition will erease all your data - backup your movies, photos, etc before proceeding.
Sent from my TF300T using XDA Free mobile app
Click to expand...
Click to collapse
Thanks mate,
Just managed to get it back to normal bu flashing 4.2.2, then downgraded to 4.3 XXUEND1.
Now the build is showing as XXUEND1. However the bootloader and baseband stayed at XXUGNH6!
IS it possible to flash XXUEND1 modem/baseband on this now?
I've tried compiling the modem flashable but aren't savvy enough! So here are the files if it's possible to flash
Modem: https://mega.co.nz/#!HRNHQZob!WLfbPp...ZHF7pAd5HmC00U
NON-HLOS: https://mega.co.nz/#!iVFjWCZI!jcUyjN...WP8kfnQZbIxDi0
Really appreciate your help!

sirs2k said:
Thanks mate,
Just managed to get it back to normal bu flashing 4.2.2, then downgraded to 4.3 XXUEND1.
Now the build is showing as XXUEND1. However the bootloader and baseband stayed at XXUGNH6!
IS it possible to flash XXUEND1 modem/baseband on this now?
I've tried compiling the modem flashable but aren't savvy enough! So here are the files if it's possible to flash
Modem: https://mega.co.nz/#!HRNHQZob!WLfbPp...ZHF7pAd5HmC00U
NON-HLOS: https://mega.co.nz/#!iVFjWCZI!jcUyjN...WP8kfnQZbIxDi0
Really appreciate your help!
Click to expand...
Click to collapse
Those links ask for password - not sure what would that be
You can always extract modem and non-hlos form your XXUEND1 package downloaded from sammobile and flash them separately via Odin as in here:
http://forum.xda-developers.com/gal...o-flash-modems-baseband-t3028314/post58785261

[Q] HELP! No wifi no camera no Sound on Samsung S4 GT-I9505 after flashing stock

hi there . i am new here and a noob .. i flashed my galaxy s4 gt-i9505 with stock ROM "I9505XXUBMEA" with odin after rebooting i have no sound ,when i launch the camera the device turn off ,WiFi wont turn on.
Please is there any repair for this. I don't care about any warranty or anything. I just want the device fully working with sound and wifi and camera on stock ROM. Please is there any solution to this problem, cant find the solution anywhere it does not matter jelly been or kitkat just working stock rom .thanks in advance.
version:
AP:I9505XXUBMEA
CP:I9505XXUBMEA
CSC:I9505XXOXXBMF1
Adroid Version: 4.2.2
Baseband: I9505XXUFNB9
Kernel Version: 3.4.0-768421
[email protected] #1

Why did you flash 4.2.2? My guess is your were on at least a 4.3 rom. Flash one of the latest roms. Atleast a 4.4.2 rom.

Lennyz1988 said:
Why did you flash 4.2.2? My guess is your were on at least a 4.3 rom. Flash one of the latest roms. Atleast a 4.4.2 rom.
Click to expand...
Click to collapse
I tried Lollipop it didn't work i was stuck in bootloop so i roled back to original one 4.2.2 . i also had the boot message "kernel is not seandroid enforcing set warranty bit kernel" .can u please suggest me what to do .

neoom said:
I tried Lollipop it didn't work i was stuck in bootloop so i roled back to original one 4.2.2 . i also had the boot message "kernel is not seandroid enforcing set warranty bit kernel" .can u please suggest me what to do .
Click to expand...
Click to collapse
Just flash the latest Lollipop again and it should be fixed.
What do you mean Lollipop didn't work? It works, so what steps did you take?

Lennyz1988 said:
Just flash the latest Lollipop again and it should be fixed.
What do you mean Lollipop didn't work? It works, so what steps did you take?
Click to expand...
Click to collapse
i just flashed it with latest Lollipop rom , but didn't start just bootloop , idid factory reset, wipe cache didn't work stuck in bootloop.

neoom said:
i just flashed it with latest Lollipop rom , but didn't start just bootloop , idid factory reset, wipe cache didn't work stuck in bootloop.
Click to expand...
Click to collapse
It should work. What version did you try to flash?

maybe you must more wait? Lollipop long boot after first clean install

Lennyz1988 said:
It should work. What version did you try to flash?
Click to expand...
Click to collapse
this one : I9505XXUHOB7_I9505OXXHOB4_I9505XXUHOB7_HOME.tar

neoom said:
this one : I9505XXUHOB7_I9505OXXHOB4_I9505XXUHOB7_HOME.tar
Click to expand...
Click to collapse
1. Perform a factory rest now
2. Try flashing that firmware again. Redownload it just to be sure.
https://mega.co.nz/#!R9YCjT5T!npRgHavTtiLTDOA3VNgwModN2zsz-q34rWIt5q3Cv1I
Wait at least 20 minutes for it to boot.

Lennyz1988 said:
1. Perform a factory rest now
2. Try flashing that firmware again. Redownload it just to be sure.
Wait at least 20 minutes for it to boot.
Click to expand...
Click to collapse
thks i will try it . i have a bad connection so it will take some time .i will feed back after .

KoNd2i0 said:
maybe you must more wait? Lollipop long boot after first clean install
Click to expand...
Click to collapse
i had a bootloop not a long boot .it just keep rebooting

Lennyz1988 said:
1. Perform a factory rest now
2. Try flashing that firmware again. Redownload it just to be sure.
Wait at least 20 minutes for it to boot.
Click to expand...
Click to collapse
ok just finished flashing . the same problem persist i bypassed the boot but still can't turn on wifi also no sound no camera .what to do ?

Hi, I have same problem as neoom. After flash to LP phone doesn't make any sound at all and the camera is off. I've tried flashing with firmware from Lenny1988 twice but it didn't change anything. I've tried flashing new modem and bootloader - still no sound. Anyone could help?

Use kies tool to upgrade your phone. Go to tools, firmware upgrade and initialization, enter the model number (ex : GT-I9505 with capital letters), then the s/n that you will find on the back sticker behind battery and kies will find and restore the correct csc, will repartition your phone, will wipe all the partitions and will flash the most appropriate firmware for your phone depending on the correct region. Your wifi and camera may not work because toy have a mismatching cp and ap so let the Samsung kies do the job for you remember not to connect the phone while inputting the model number and sn but only when it tells you to connect it in Odin mode.

Kies says GT-I9505 does not support initialization.

neoom said:
ok just finished flashing . the same problem persist i bypassed the boot but still can't turn on wifi also no sound no camera .what to do ?
Click to expand...
Click to collapse
The flashing was succesfull right? Odin gave no errors?
Then flash the firmware again only in this case with a pit and re-partition.
Get the pit from here:
http://forum.xda-developers.com/showthread.php?t=2265477

Maybe you are using the wrong version of Kies? Use Kies3. Because as you can see in this image, i can start initialization.(i cannot enter S/N because i have the gt-i9506) but pay attention to the capital letters! Write it down as the sticker behind the battery sais!
{
"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"
}

Lennyz1988 said:
The flashing was succesfull right? Odin gave no errors?
Then flash the firmware again only in this case with a pit and re-partition.
Get the pit from here:
[/QUOTE]
,i tried this methode now...art. tried wipe data .and cache same issue .
Click to expand...
Click to collapse

nikosdd said:
Maybe you are using the wrong version of Kies? Use Kies3. Because as you can see in this image, i can start initialization.(i cannot enter S/N because i have the gt-i9506) but pay attention to the capital letters! Write it down as the sticker behind the battery sais!
Click to expand...
Click to collapse
Let me be clear - of course i used Kies3, I'm getting the messege of not supported model after entering proper serial number (checked in Settings menu in phone and on the back sticker).

Hmm that's really weird. Then try to start this procedure while phone is connected to kies. I've done this on a i9505 to friend of mine so I know that there is a way to filly restore phone. Otherwise download the official rom from sammobile depending on your country and flash it via Odin.

[Q] Flashing 4.4.2, or Custom ROM?

Hey Y'all,
So I've been trying to root my 5.0.1 S4, but could not do it for the life of me. I figured since the CF Auto Root file was made for 4.4.2, I would try flashing back to that with Odin. After getting the correct build for my device, I've been trying to get it to flash, but it got to system, and then stalled forever. I let it run overnight, and it hadn't progressed, so I tried restarting. Now, it fails in a matter of seconds, but I keep seeing progress on the phone's blue bar.
[Q] AM I wasting my time trying to flash an old build? If so, should I just use a custom rom so I get my root? And if so, which one should I use (I'm new to this phone mod stuff.)
Thanks in advance!

F13Bubba said:
Hey Y'all,
So I've been trying to root my 5.0.1 S4, but could not do it for the life of me. I figured since the CF Auto Root file was made for 4.4.2, I would try flashing back to that with Odin. After getting the correct build for my device, I've been trying to get it to flash, but it got to system, and then stalled forever. I let it run overnight, and it hadn't progressed, so I tried restarting. Now, it fails in a matter of seconds, but I keep seeing progress on the phone's blue bar.
[Q] AM I wasting my time trying to flash an old build? If so, should I just use a custom rom so I get my root? And if so, which one should I use (I'm new to this phone mod stuff.)
Thanks in advance!
Click to expand...
Click to collapse
Yes, stop before you brick your device. CF Auto Root works for Lollipop. Or Odin TWRP and flash SuperSU zip. Or just flash a rooted ROM. Read the OPs and decide which one sounds like the best fit for you.
{
"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"
}

bilgerryan said:
Yes, stop before you brick your device. CF Auto Root works for Lollipop. Or Odin TWRP and flash SuperSU zip. Or just flash a rooted ROM. Read the OPs and decide which one sounds like the best fit for you.
Click to expand...
Click to collapse
KK, thanks. I could not get CF to root my device, trying 3 different versions of Odin. I'll go the custom rom route, methinks.

F13Bubba said:
KK, thanks. I could not get CF to root my device, trying 3 different versions of Odin. I'll go the custom rom route, methinks.
Click to expand...
Click to collapse
Uncheck Auto Reboot and F Reset (everything) when using Odin. And wait a minute after it says PASS before unplugging. Also try different ports and cables.

I can only find .img files for TWRP, I haven't yet been able to find any .tar files. Any tips on where to get a recovery file to use with Odin?
Yeah, definitely cannot restart my phone at the point, it's referring me to Kies to recover. Kies won't connect, either 3.0 or 2.6. So At this point I guess I'm hoping flashing a custom ROM will work...otherwise, is my phone bricked?

F13Bubba said:
I can only find .img files for TWRP, I haven't yet been able to find any .tar files. Any tips on where to get a recovery file to use with Odin?
Yeah, definitely cannot restart my phone at the point, it's referring me to Kies to recover. Kies won't connect, either 3.0 or 2.6. So At this point I guess I'm hoping flashing a custom ROM will work...otherwise, is my phone bricked?
Click to expand...
Click to collapse
TWRP can flash images now.
Flash this build of TWRP first. (It's a .tar for Odin)
https://dl.twrp.me/jfltespr/twrp-2.8.4.0-jfltespr.tar
Copy this build to your device somewhere. (You might as well go ahead and copy a ROM you want to install on your device also.)
https://dl.twrp.me/jfltespr/twrp-2.8.7.0-jfltespr.img
Boot into TWRP and go to install. Select images button at the bottom right and select the build you copied to your device. You will now be running the current version of TWRP.

WOOOOOO!
After a ton of troubleshooting and grief, I finally got 5.0.1 back on, and working. I also discovered that my front usb port was not working correctly. I guess I'll try to root it now!
Aaaaaand, it seems to have worked flawlessly. Thanks for all the help guys!

New Firmware QA1 released 1/26/2017...Security update

January 1 Security update. Everything else seems to have stayed the same.
{
"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"
}

Another update! Cool.

These security updates are coming very frequently. I would be careful updating if you value an unlocked bootloader. I wouldn't bet that Samsung wouldn't pull a fast one and lock it down even at this stage of the N4's life span. So be careful just incase.

Could anyone installed this update, confirms that the bootloader still unlocked, plz?
Sent from my SM-N910P using Tapatalk

tx_dbs_tx said:
These security updates are coming very frequently. I would be careful updating if you value an unlocked bootloader. I wouldn't bet that Samsung wouldn't pull a fast one and lock it down even at this stage of the N4's life span. So be careful just incase.
Click to expand...
Click to collapse
I agree. I never update until i have an Odin file!

aaron74 said:
I agree. I never update until i have an Odin file!
Click to expand...
Click to collapse
When you get the full tar file which files you remove from the tar before flashing to make sure that your bootloader still the old unlocked one?

anees02 said:
When you get the full tar file which files you remove from the tar before flashing to make sure that your bootloader still the old unlocked one?
Click to expand...
Click to collapse
I dont remove anything. But just use the name to verify the bootloader is same version. I cant verify this but I read somewhere that as long as the version number doesnt change, then its backwards flashable. Heres an example of what I mean.
Heres current firmware on sammobile N910PVPS4DPK1
and following so on like these N910PVPS4DPJ1, N910PVPU4DPH4, etc.
After the PVP is the bootloader version # as "S4" and "U4". Now what I read is as long as that # is same, that determines what firmware you can use.
So if you go back to firmware that we cant go back to like N910PVPU3BOF5. You can see its a 3. This is why we can only go back to N910PVPU4COG5
So in other words, as long as that stays a "4" , we should be able to downgrade to any firmware that is a "4".
As I already stated, I dont know this first hand, but have read it somewhere here!!
Hope this was helpful!!

aaron74 said:
I dont remove anything. But just use the name to verify the bootloader is same version. I cant verify this but I read somewhere that as long as the version number doesnt change, then its backwards flashable. Heres an example of what I mean.
Heres current firmware on sammobile N910PVPS4DPK1
and following so on like these N910PVPS4DPJ1, N910PVPU4DPH4, etc.
After the PVP is the bootloader version # as "S4" and "U4". Now what I read is as long as that # is same, that determines what firmware you can use.
So if you go back to firmware that we cant go back to like N910PVPU3BOF5. You can see its a 3. This is why we can only go back to N910PVPU4COG5
So in other words, as long as that stays a "4" , we should be able to downgrade to any firmware that is a "4".
As I already stated, I dont know this first hand, but have read it somewhere here!!
Hope this was helpful!!
Click to expand...
Click to collapse
Thank you very much.
I knew something new today because of you... Thanks again.
When I see to the latest OTA QA1 there are two things T4 and S4 what does that mean?
Maybe different CSC versions?

anees02 said:
Thank you very much.
I knew something new today because of you... Thanks again.
When I see to the latest OTA QA1 there are two things T4 and S4 what does that mean?
Maybe different CSC versions?
Click to expand...
Click to collapse
On all firmwares. The middle listing is the csc version, and its always got a different numbering than the others.
There's 3 version numbers here. 1st is the PDA (which is the actual rom firmware) 2nd is CSC (which is region) 3rd is the PHONE (which is the modem)
So this one is still #4 so it should be alright to still downgrade.
Now the last 3 digits just rep the date. Q=2017 A=January 1= 1st revision.
https://forum.xda-developers.com/showthread.php?t=1356325

wow. learning new things. thank guys.
just a little too late, after taking the update myself.
Has anyone been able to twrp/root? or odin backwards is the only way right now?

linhnd2000 said:
wow. learning new things. thank guys.
just a little too late, after taking the update myself.
Has anyone been able to twrp/root? or odin backwards is the only way right now?
Click to expand...
Click to collapse
You can Odin back as far as OG5 which is Android Lollipop 5.1
You can Odin TWRP on any of those updates. But Odin the desired update first if that's your goal.
What gets overlooked with TWRP flash is that you should boot directly into recovery after flashing. If you boot system first, immediately after TWRP flash, stock recovery gets restored.
That pattern and timing is tricky so it's recommended to uncheck auto reboot in Odin options when flashing TWRP. Once you get the success, 0 failed in Odin status, pull the USB cable and battery and wait at least 30 seconds (some suggest waiting at least a minute while discharging power circuit by holding power button down *Don't go Beastmode on that power button*). Reinstall battery and pattern boot into recovery (Vol+, Power and Home simultaneously until phone vibrates).
If you're rooting stock with stock kernel, you need systemless superuser. Flash SuperSU zip by Chainfire in recovery.
If flashing a custom ROM, you only need TWRP. No pre-root required for that.
Sent from my SM-N920P using Tapatalk

samep said:
You can Odin back as far as OG5 which is Android Lollipop 5.1
You can Odin TWRP on any of those updates. But Odin the desired update first if that's your goal.
What gets overlooked with TWRP flash is that you should boot directly into recovery after flashing. If you boot system first, immediately after TWRP flash, stock recovery gets restored.
That pattern and timing is tricky so it's recommended to uncheck auto reboot in Odin options when flashing TWRP. Once you get the success, 0 failed in Odin status, pull the USB cable and battery and wait at least 30 seconds (some suggest waiting at least a minute while discharging power circuit by holding power button down *Don't go Beastmode on that power button*). Reinstall battery and pattern boot into recovery (Vol+, Power and Home simultaneously until phone vibrates).
If you're rooting stock with stock kernel, you need systemless superuser. Flash SuperSU zip by Chainfire in recovery.
If flashing a custom ROM, you only need TWRP. No pre-root required for that.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
works perfectly. thanks. I went back to PK1 so I can use the debloated rom.