920T Security Error after flashin Stock Firmware with Odin - T-Mobile Samsung Galaxy S6

Hi everyone
Here's the situation
A few days ago i sent my pone to repair because i messed up with the IMEI and need it to be restored, the guy flashed it bak to stock and left the root in my phone, i unrooted manually and when i restarted my phone it said "Custom Binary blocker by FRP".
Then i flashed back the stock firmware with odin, and then i get this error "Security Error This phone has been flashed with unofficial firmware" and it does not leave me to unlock it via Device Unlock.
I have tried to Factory reset via recovery after i flashed the stock firmware
At this point i don't know what to do, so if you help me it i'll be very appreciated!

Have you resolved this issue?
If not, there's like hood you have messed up efs
Your imei and s/n probably not correct now.
You will need to repair your imei.
Using Z3x.
I used to have same issue, but got it resolved.

Related

[Q] Z1 cannot register network after update

hi.. I was on omni rom before i updated. I had a problem with omni rom, I had an error, process stopped working. i tried reinstalling omni rom, wiping everything but still problem persisted. I tired also slimkat rom but still same problem so I decided to flash stock rom. I flashed the .757 update and after flashing I cannot register a network. Z1 can search my network but when i try to register it takes forever. i tried also downgrading to the first rom out of the box which is .290 but I am having baseband unknown problem. i tried to flash other stock rom but still same problem. I also tried to flash iHackers 4.1, followed the steps but still i cannot register a network. Baseband and IMEI are both available. Is there any way to fix my z1
I also tried fixing via SUS, still same problem, can look for network but cannot register. Basing on the box SI my rom is CUS HK which is the same stock ROM that I used but still had the problem. please help...
bjo12 said:
hi.. I was on omni rom before i updated. I had a problem with omni rom, I had an error, process stopped working. i tried reinstalling omni rom, wiping everything but still problem persisted. I tired also slimkat rom but still same problem so I decided to flash stock rom. I flashed the .757 update and after flashing I cannot register a network. Z1 can search my network but when i try to register it takes forever. i tried also downgrading to the first rom out of the box which is .290 but I am having baseband unknown problem. i tried to flash other stock rom but still same problem. I also tried to flash iHackers 4.1, followed the steps but still i cannot register a network. Baseband and IMEI are both available. Is there any way to fix my z1
I also tried fixing via SUS, still same problem, can look for network but cannot register. Basing on the box SI my rom is CUS HK which is the same stock ROM that I used but still had the problem. please help...
Click to expand...
Click to collapse
Sounds like you've lost your IMEI number.
Dial *#06# and see if it shows up all zeros, I bet it does.
I'm looking to downgrade mine from Kitkat back to 4.3 and I've gathered that if you go further back, and you did, you could lose your IMEI.
I don't know how to fix this myself, but I'm still looking and learning.
Have a look at this thread and see if it helps --> http://forum.xda-developers.com/showthread.php?t=2628185
Second post down gives NUT's .ftf to use to downgrade without losing IMEI, but I don't know if it will restore yours. Might be worth a try. Have a read, and hope it points you in the right direction.
---------- Post added at 05:41 PM ---------- Previous post was at 04:44 PM ----------
Try flashing a completely stock .757 ftf including kernel, that should restore your IMEI, and flash everything.
Hope you sort it
Not .757, but .534. You'll get your imei back and try going back to .757 from there. I can't tell you how to fix that from nothing as I downgraded to .534 and restored a backup of .757. Try some other .534 ftfs if yours doesn't work. There's one version of the ftf that messes up your imei.
Don't get too scared mate, it happened for me too!
Wysłane z mojego C6903 przy użyciu Tapatalka
I dont think flashing NU'T's .534 alone will restore IMEI, but I could be wrong, I'm no expert.
Flashing a firmware before .290 seems result in loss of IMEI, so looks like the best way to go is to go back to the ROM you were using originally that had IMEI showing.
@op - If you reinstall OMNI rom does your IMEI come back??
If the OP is wanting to get onto KitKat .757, and was on OMNI rom previously, I'd probably flash the stock .290, or .136 ftf completely.
That firmware should in theory work, and restore IMEI, then I'd look at updating to .757.
If I'm wrong, sorry, and someone please correct.
Many thanks.
Thanks for the replies.
Actually I already did some research and flashed every ROM available even NUT's. I downgraded to .534 had bootloop. flashing .757 restores my IMEI and baseband but sadly doesn't fix the signal registration problem that I have. I have both IMEI and baseband. My IMEI is same as I have with the box so I really do not know why I cannot register a network. I have flashed back to .290 as it was FW when i unboxed it but it removes my baseband even if I choose to exclude baseband when flashing through flashtool. Anyway, I have again .757 and relocked bootloader because I sent it for warranty. Now my problem is can they know if I flashed custom ROM coz we all know it voids warranty.. hehe..
When I reinstall OMNI I cannot get it to boot properly because I always have Process is not responding error and then reboots continuously
Ah, right.
What's the status of the TA partition? Was it backed up, and restored when you relocked the bootloader?
As far as I've read, restoring TA and relocking should be okay for warranty purposes. The only thing I've wondered about is you usually have to unlock via the Sony website, so they must know you requested the unlock key.
If the bootloader is locked with a restored TA partition, they cannot prove that you actually used it tho, so should be fine.
If you didn't backup, then restore the TA, then they may know.
As for the signal issue, had you tried another sim card to see if that worked?
MickieH said:
Ah, right.
What's the status of the TA partition? Was it backed up, and restored when you relocked the bootloader?
As far as I've read, restoring TA and relocking should be okay for warranty purposes. The only thing I've wondered about is you usually have to unlock via the Sony website, so they must know you requested the unlock key.
If the bootloader is locked with a restored TA partition, they cannot prove that you actually used it tho, so should be fine.
If you didn't backup, then restore the TA, then they may know.
As for the signal issue, had you tried another sim card to see if that worked?
Click to expand...
Click to collapse
TA partition was not backed up because of my excitement to flash custom ROM!! Hahaha so It's really my mistake for not doing so... :cyclops:
Anyway I tried sending it for warranty purpose and now after waiting for weeks already I was updated with the status. I was told that the main board was replaced and now my phone is being prep to be shipped and returned hopefully I will receive it tomorrow. Now my question is if the board was replaced does it mean that it will have a new set of DRM keys and others? If not will flashing again a Custom Rom bring the same problem? hehe.. Because I am thinking of flashing custom ROM again once I have it.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
So I have my Z1 back, actually not my actual Z1 but a brand new replacement. =)
Time to back up everything now! =)
bjo12 said:
TA partition was not backed up because of my excitement to flash custom ROM!! Hahaha so It's really my mistake for not doing so... :cyclops:
Anyway I tried sending it for warranty purpose and now after waiting for weeks already I was updated with the status. I was told that the main board was replaced and now my phone is being prep to be shipped and returned hopefully I will receive it tomorrow. Now my question is if the board was replaced does it mean that it will have a new set of DRM keys and others? If not will flashing again a Custom Rom bring the same problem? hehe.. Because I am thinking of flashing custom ROM again once I have it.
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
So I have my Z1 back, actually not my actual Z1 but a brand new replacement. =)
Time to back up everything now! =)
Click to expand...
Click to collapse
Lol, yes, and the TA partition
Nice one getting a new handset :good:

sprint htc one keeps rebooting even after ruu

i have a sprint htc one and it is being quite a pain in the a**. i had gotten it flashed to cricket a few months ago but like a month ago i flashed a sense based rom and it showed up with htc.htcdialer not responding. so i flashed a aosp rom back and it was fine except every once and a while it would reboot and i would have no baseband or anything until i flashed the radio through CWM and it worked. so today i decided to try and restore it to stock using a RUU but after it booted it worked for a min then it rebooted and when it came back on it showed a black screen with the status bar but i could pull the notification drawer down and access the settings but it keeps rebooting
and on top of that i cant flash a custom recovery it comes up with
FAILED (remote: not allowed)
im at a loss idk what to do ive been up night and day trying to fix this someone please help :crying::crying::crying::crying::crying::crying::crying:
WICK3DREAP3R said:
i have a sprint htc one and it is being quite a pain in the a**. i had gotten it flashed to cricket a few months ago but like a month ago i flashed a sense based rom and it showed up with htc.htcdialer not responding. so i flashed a aosp rom back and it was fine except every once and a while it would reboot and i would have no baseband or anything until i flashed the radio through CWM and it worked. so today i decided to try and restore it to stock using a RUU but after it booted it worked for a min then it rebooted and when it came back on it showed a black screen with the status bar but i could pull the notification drawer down and access the settings but it keeps rebooting
and on top of that i cant flash a custom recovery it comes up with
FAILED (remote: not allowed)
im at a loss idk what to do ive been up night and day trying to fix this someone please help :crying::crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
Did you try to flash the latest RUU 5.03.651.3? If not, then download it from this site and follow the instructions in the OP. The MD5 for this RUU is 9ae375b6022e823fa4f90226115b0c54. Double check the MD5 to ensure you didn't have a corrupt download. If you are still S-ON, then you will have to re-lock your bootloader prior to running this RUU.
so i restored my phone to stock using the ruu you gave me but when it boots up it shows the lock screen then when i unlock it it shows a white screen with a green htc logo and i can just see the status bar if i pull down from the top
and its still rebooting every few min and it shows htc.htcdialer not responding
and i cant flash a custom recovery
WICK3DREAP3R said:
so i restored my phone to stock using the ruu you gave me but when it boots up it shows the lock screen then when i unlock it it shows a white screen with a green htc logo and i can just see the status bar if i pull down from the top
and its still rebooting every few min and it shows htc.htcdialer not responding
Click to expand...
Click to collapse
The RUU should have put everything back to stock. Did the RUU complete properly without any failures? You can try and run the RUU again paying close attentions to the steps and double check the MD5. If that doesn't work, then download the firmware from the same site and flash it. This will give you the correct radio, hboot and stock recovery. Are you able to get to Settings and check About to see if your imei and baseband are present? If not, it may be a hardware issue which would require returning the phone to Sprint or HTC.
majmoz said:
The RUU should have put everything back to stock. Did the RUU complete properly without any failures? You can try and run the RUU again paying close attentions to the steps and double check the MD5. If that doesn't work, then download the firmware from the same site and flash it. This will give you the correct radio, hboot and stock recovery. Are you able to get to Settings and check About to see if your imei and baseband are present? If not, it may be a hardware issue which would require returning the phone to Sprint or HTC.
Click to expand...
Click to collapse
so i unlocked the bootloader and flashed a custom recovery and i flashed a custom rom its the bad boyz sprint one rom
http://forum.xda-developers.com/showthread.php?t=2635051
but it still just unlocks to the white htc screen with com.htc.htcdialer is not responding
and i dont know if i can return it to sprint since its flashed to cricket
WICK3DREAP3R said:
so i unlocked the bootloader and flashed a custom recovery and i flashed a custom rom its the bad boyz sprint one rom
http://forum.xda-developers.com/showthread.php?t=2635051
but it still just unlocks to the white htc screen with com.htc.htcdialer is not responding
and i dont know if i can return it to sprint since its flashed to cricket
Click to expand...
Click to collapse
1. Did you run the RUU again?
2. Did you flash the firmware?
3. Are the baseband & imei in your Settings?
4. Do you mean you have an unlocked SIM to Cricket?
One of the fixes for htcdialer is to do a factory reset in bootloader, another was to reinstall the radio. If you were to flash the stock firmware, it would have accomplished both of these objectives. Prior to flashing it, copy what you can off of your phone and save to your computer. Note: For most GSM phones (yours is a CDMA) when you flash the firmware it fails on this command fastboot flash zip firmware.zip you just have to re-enter the command a second time. If it works the first time thru then great.
majmoz said:
1. Did you run the RUU again?
2. Did you flash the firmware?
3. Are the baseband & imei in your Settings?
4. Do you mean you have an unlocked SIM to Cricket?
One of the fixes for htcdialer is to do a factory reset in bootloader, another was to reinstall the radio. If you were to flash the stock firmware, it would have accomplished both of these objectives. Prior to flashing it, copy what you can off of your phone and save to your computer. Note: For most GSM phones (yours is a CDMA) when you flash the firmware it fails on this command fastboot flash zip firmware.zip you just have to re-enter the command a second time. If it works the first time thru then great.
Click to expand...
Click to collapse
yes i ran the RUU more than once
by what firmware do you mean?
no my baseband and imei are UNKNOWN in settings but when i do fastboot getvar all it shows them
and no i took it to a phone store and they flashed it to cricket since they said that the sprint gsm radios wouldnt work with cricket
i havent tried the factory reset in my bootloader yet because i flashed CM11 M9 SNAPSHOT so it would work because no matter what sense-based rom i flash it comes up with the htcdialer and i have tried to flash every sprint radio i could through CWM but when i restart it it shows an unknown baseband

[Q] can imei be easily overwritten?

hi guys, i am in lost here, i've been downgrading roms into 4.1.2 and i am facing no imei issue and unknown baseband issue, so i am reverting back to my stock rom. when i restarted my phone, i cannot get the nfc update status, and it has always restarting. and when i check my imei for unlocking my bootloader, i get the wrong imei according to my phone boxes. my question is, can imei be easily overwritten by using flashtool? if that's the case, can it causing my phone to refuses to startup?
As far as I know, it's impossible to downgrade fully. You may have noticed that later updates have a Nfc Firmware popup, I'm not sure how to downgrade nfc firmware or if it's backwards compatible.
What do you mean by "so I'm reverting to stock ROM"? Isn't that what you're doing, flashing an official Ftf?
Sent via Tapatalk on my Xperia Z

[Q] softbricked after OF2 OTA update

Got a stock G900A that had gotten the OTA update to OF2, then I bricked it trying to flash what I thought was a stock ROM but wasn't. Seems to be soft-bricked now (stuck on AT&T logo at boot) Tried wipe/reset options also.
I tried flashing that 5.0 ROM from the http://forum.xda-developers.com/att...-s5-lollipop-stock-rom-g900aucu3boc4-t3137519 thread but it said SW REV CHECK FAIL: [aboot] Fused 4 > Binary 3 which I assume means that the image included the OC4 bootloader which the phone is loath to downgrade.
Any suggestions on how to get a stock image with the OF4 update installed? Or can I flash everything but the bootloader?
I just picked up an S5 last night and Im so glad I didnt try that,lol. But on a real note, Id like to have some suggestions for rooting after taking the of2 update. Im about ready to ditch it and keep running my S3.
thanatos2k, since you started this thread, would you mind keeping your findings posted here please.
thanatos2k said:
Got a stock G900A that had gotten the OTA update to OF2, then I bricked it trying to flash what I thought was a stock ROM but wasn't. Seems to be soft-bricked now (stuck on AT&T logo at boot) Tried wipe/reset options also.
I tried flashing that 5.0 ROM from the http://forum.xda-developers.com/att...-s5-lollipop-stock-rom-g900aucu3boc4-t3137519 thread but it said SW REV CHECK FAIL: [aboot] Fused 4 > Binary 3 which I assume means that the image included the OC4 bootloader which the phone is loath to downgrade.
Any suggestions on how to get a stock image with the OF4 update installed? Or can I flash everything but the bootloader?
Click to expand...
Click to collapse
You guys that don't know what you are doing should stop flashing your phones, this is getting old. Anyway, flash this in Odin's PDA/AP slot to recover:
G900A_OF2_Stock_Kernel.tar.md5

cant flash stock RUU/rom

Hi guys, I have a serious and weird problem.I can't get my HTC One back to stock, I updated my phone to Android 5.0.2 but had camera issues so I decided to downgrade it back to 4.3 using rom.zip-fastboot method which worked, but I found out that I can't recharge/ check my account balance because all I see is Chinese, I can't do anything reasonable on my mtn sim.I tried flashing it back to 6.23.651.10 which I've done several times successfully but got error 155, I tried different things to make it work, I even tried unlocking the bootloader flashing a stock recovery and relocking the boot loader but got the same error. I successfully flashed viper one using twrp but it didn't solve the problem, I'm in need of serious help here guys, please

Categories

Resources