Do not take APH1 update!

FoxyDrew

Senior Member
Aug 18, 2014
955
293
63
East Taunton
After taking the APH1 update on my phone, I can no longer downgrade to PG5, and I also can't flash the PG9 U firmware. I don't know what Samsung/Verizon did, but it's ridiculous.

I'm now stuck on the APH1 firmware and can't get on the U firmware at all.

I haven't tried rooting, but there is no Odin firmware for APH1 yet, so I'm not going to try until there is, so that if I mess up my phone I can fix it.
 
Last edited:
  • Like
Reactions: TheAugust

Milly7

Senior Member
Oct 21, 2010
1,221
378
0
What is the full firmware version number? If they updated the bootloader that would explain why you can't downgrade.
 
G

GuestK00143

Guest
After taking the APH1 update on my phone, I can no longer downgrade to PG5, and I also can't flash the PG9 U firmware. I don't know what Samsung/Verizon did, but it's ridiculous.

I'm now stuck on the APH1 firmware and can't get on the U firmware at all.

I haven't tried rooting, but there is no Odin firmware for APH1 yet, so I'm not going to try until there is, so that if I mess up my phone I can fix it.
What Odin version have you tried?
 

ShadowyStorm

Senior Member
Sep 29, 2013
119
19
0
Looking at the full firmware name it looks like it's on bootloader v4. None of that will probably work.

---------- Post added at 01:59 PM ---------- Previous post was at 01:57 PM ----------

G930VVRS4APH1 is the firmware he referring to.
 

Ph0nysk1nk

Senior Member
Jul 28, 2016
96
18
0
After taking the APH1 update on my phone, I can no longer downgrade to PG5, and I also can't flash the PG9 U firmware. I don't know what Samsung/Verizon did, but it's ridiculous.

I'm now stuck on the APH1 firmware and can't get on the U firmware at all.

I haven't tried rooting, but there is no Odin firmware for APH1 yet, so I'm not going to try until there is, so that if I mess up my phone I can fix it.
Don't bother trying to root... even though I'm not a Verizon customer, it looks like you house have been dicked out of root as you can't go back to previous firmwares and another site I visit says it's been fixed. Sorry guys on Verizon :crying:

---------- Post added at 01:06 AM ---------- Previous post was at 01:04 AM ----------

Don't bother trying to root... even though I'm not a Verizon customer, it looks like you house have been dicked out of root as you can't go back to previous firmwares and another site I visit says it's been fixed. Sorry guys on Verizon :crying:
Meant to say guys... not house. On another note, this means Aat will probably be getting bootloader v4 soon then too... :/
 

Ph0nysk1nk

Senior Member
Jul 28, 2016
96
18
0
Don't bother trying to root... even though I'm not a Verizon customer, it looks like you guys have been dicked out of root as you can't go back to previous firmwares and another site I visit says it's been fixed. Sorry guys on Verizon. This also means a att will be getting it too...
 

Milly7

Senior Member
Oct 21, 2010
1,221
378
0
Well for individuals who did update here is a link to the firmware in case it is needed. https://drive.google.com/open?id=0BybvkLkW8XrDdlRSUGI5Y1VSM3c md5 43E1295CAA08F8E16E873F945728B7D5 @Misterxtc can mirror in the firmware thread if he chooses. But, DO NOT FLASH OR YOU CANNOT DOWNGRADE! The only reason I flashed it was to convert my unlocked T-Mobile Device to Verizon as it was stuck on bootloader 3.
 
Last edited:
  • Like
Reactions: 335Deezl

Casetheace

Senior Member
Aug 3, 2014
79
40
0
Why would the updated bootloader stop the root? Ru sure? Tmobile had there bootloader updated after the root exploit and was still able to root. It's a developmental kernal, can't see anything on update that would affect the exploit.

---------- Post added at 03:08 AM ---------- Previous post was at 03:05 AM ----------

Well for individuals who did update here is a link to the firmware in case it is neede. https://drive.google.com/open?id=0BybvkLkW8XrDdlRSUGI5Y1VSM3c md5 43E1295CAA08F8E16E873F945728B7D5 @Misterxtc can mirror in the firmware thread if he chooses. But, DO NOT FLASH OR YOU CANNOT DOWNGRADE! The only reason I flashed it was to convert my unlocked T-Mobile Device to Verizon as it was stuck on bootloader 3.
If the U firmware gets a upgrade and it's a matching bootloader version as any US carriers bootloader, I would bet it would be able to flash again.
 

Ph0nysk1nk

Senior Member
Jul 28, 2016
96
18
0
Why would the updated bootloader stop the root? Ru sure? Tmobile had there bootloader updated after the root exploit and was still able to root. It's a developmental kernal, can't see anything on update that would affect the exploit.
It's not the bootloader that "patches" the root method... it was the security update in PH1 that broke root. The bootloader being V4, prevents you guys from going back to rootable firmware. You now need a new root method which PROBABLY won't happen :(
 

FoxyDrew

Senior Member
Aug 18, 2014
955
293
63
East Taunton
Why would the updated bootloader stop the root? Ru sure? Tmobile had there bootloader updated after the root exploit and was still able to root. It's a developmental kernal, can't see anything on update that would affect the exploit.
It's not the bootloader that "patches" the root method... it was the security update in PH1 that broke root. The bootloader being V4, prevents you guys from going back to rootable firmware. You now need a new root method which PROBABLY won't happen :(


Good thing root sucked anyways
 
G

GuestK00143

Guest
Why would the updated bootloader stop the root? Ru sure? Tmobile had there bootloader updated after the root exploit and was still able to root. It's a developmental kernal, can't see anything on update that would affect the exploit.
It's not the bootloader that "patches" the root method... it was the security update in PH1 that broke root. The bootloader being V4, prevents you guys from going back to rootable firmware. You now need a new root method which PROBABLY won't happen :(

PH1 roots just fine.
Good thing root sucked anyways
And it still does on PH1 lol.
 
Last edited: