System Software not authorized by AT&T - AT&T Samsung Galaxy S6

Hi All This is my first post here .
yesterday i had a problem installing Xposed framework it said that it need a custom rom to be istalled
so i downloaded the TWRP app chosed my recovery version and run it, it was flashed succesfully but when i tried to boot to it i got this message in blue screen "System Software not authorized by AT&T ... "
I was able to boot the system normally so i tried to recovere the original stock recovery i downloaded an app called Flashify downloaded a stock recovery ( im not sure that it was the original ) and flash it , after rebooting i was shocked by the blue screen on the recovery and also on the system so i can't boot to the system now !
I tried to flash another TWRP using odin 3.10.6 and 3.12.3 but in the two cases it fails with this error :
Code:
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Im totally lost now i have a lot of personal data inside ( 6gb of pics + 200 mb of call records + phone numbers )
I bought the phone from a third party , and we dont have any AT&T agency here
Information about the phone :
- I think that the phone was rooted because the root checker said that but when i install the su it said that i need a binary update and every time i do that it reboot without updating , when i tried from the recovery it said,signature failed or something like that .
- I had android 5.1 i think it was a custom rom because when the s6 logo appear I see under Custom with an open lock
When i go to the download mode they write
ODIN MODE //it was there even before i flash it
PRODUCT NAME : SM-G920V
CURRENT BINARY : CUSTOM // it was OFFICIAL before flashing
SYSTEM STATUS : CUSTOM
REACTIVATION LOCK : OFF
SECURE DOWNLOAD : ENABLED
RP SWREV : B:4 K:3 S:3
on the back of the phone the product name is : SM-G920F
on the previous rom it was : SM-G920F
Please any solution to back up my DATA then flash a new rom updated with a custom recovery Or even recover the original stock recovery only ( i was not using an AT&T sim card )

Related

[Q] how can I repair wrong installed KERNEL on GT-I9220 - Help please!

Hi Folks,
please bare with me I am a total new comer in this forum and new on Android because of my new Phone:
Samsung Galaxy Note GT-I9220 Chinese Version (but no fake it has Android 4.0.4 and was bought from amazon)
I accidentially installed the franco.Kernel .... don't aks me why.... and since then I am in big troubles :crying:
I can not get a USB Connection to my Win7x64 PC anymore (MTP driver installation fails.... anything I tried did not work)
Eventhough Odin does see my phone but after clicking START if shows me FAILED (Odin 1.85 nor 1.87 works) ... and the phone does seems to do anything (not turn black ... as decsribe in the following threat: http://forum.xda-developers.com/showthread.php?t=1660012 )
So how do I get back to a "normal" Kernel and which file can I use?
Thanks a lot for looking into this.
Le_Tifou:
cowboy:
PS:
All this issues only have come up, because I actually only tried to get full access to all GOOGLE PLAY STORE apps, but google always (90% of all apps) tells me this is incompatible with your phone ... and under [+] sometime says it can not be delivered to your country China or so...
Are you putting the phone in download mode when you connect to odin? If yes then paste the odin logs.
here the ODIN log for 1.87 but same for 1.85
nokiamodeln91 said:
Are you putting the phone in download mode when you connect to odin? If yes then paste the odin logs.
Click to expand...
Click to collapse
Thanks for having a look into this.
So Windows recognizes the following drivers if it is in Download mode
SAMSUNG Mobile USB CDC Composite Device
SAMSUNG Mobile USB Modem
And ODIN 1.87 recognizes the device under ID:COM yellow 0:[com3]
<ID:0/003> Added!!
after START PIT and Bootloader
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The Phone does not do anything. :crying:
I assume that the wrong KERNEL is causing this missbehaviour!?
what to do now? Any idea?
Thx 1000times
So how do I first get a new fitting Kernel?
Le_Tifou said:
Hi Folks,
please bare with me I am a total new comer in this forum and new on Android because of my new Phone:
Samsung Galaxy Note GT-I9220 Chinese Version (but no fake it has Android 4.0.4 and was bought from amazon)
I accidentially installed the franco.Kernel .... don't aks me why.... and since then I am in big troubles :crying:
I can not get a USB Connection to my Win7x64 PC anymore (MTP driver installation fails.... anything I tried did not work)
Eventhough Odin does see my phone but after clicking START if shows me FAILED (Odin 1.85 nor 1.87 works) ... and the phone does seems to do anything (not turn black ... as decsribe in the following threat: http://forum.xda-developers.com/showthread.php?t=1660012 )
So how do I get back to a "normal" Kernel and which file can I use?
Thanks a lot for looking into this.
Le_Tifou:
cowboy:
PS:
All this issues only have come up, because I actually only tried to get full access to all GOOGLE PLAY STORE apps, but google always (90% of all apps) tells me this is incompatible with your phone ... and under [+] sometime says it can not be delivered to your country China or so...
Click to expand...
Click to collapse
You would better restock your note.
You will need a rom with four files: .pit , .pda, modem and csc
The rom MUST be made for your phone and you may find it in samfirmware.com.
If your phone can't enter dowload mode, you'll need a USB JIG.
Hope this can help.
After reading the Odin resulst, try to flash only PDA as your error is comming from the PIT file.
Uncheck "repartition"
First get a kernel for your phone in tar.md5, and flash it by selecting it in the PDA tab. Don't use PIT for now.
---------- Post added at 03:12 PM ---------- Previous post was at 03:10 PM ----------
Phone has to be in download mode to use odin
Is that the right file: 165512339/c6b85b4/I9220ZCLPL_I9220OZHLPL_CHN.zip ??
nokiamodeln91 said:
First get a kernel for your phone in tar.md5, and flash it by selecting it in the PDA tab. Don't use PIT for now.
---------- Post added at 03:12 PM ---------- Previous post was at 03:10 PM ----------
Phone has to be in download mode to use odin
Click to expand...
Click to collapse
Thanks for your adive.
How do I get the right kernel files I have no glue for what I should search for....
Ok I found recently this threat which seams to point to the origínal chinese android versions:
droidevelopers dot com/f479/11859-samsung-galaxy-note-i9220-china-firmware-list.html
which points to the following
CHINA I9220 Ice Cream Sandwich 4.0.4 Firmwares
Download PDA Version Release Date CSC version Country / Carrier
Link I9220ZCLPL 4.0.4 2012 July I9220OZHLPL China
from hotfile DOT com/dl/165512339/c6b85b4/I9220ZCLPL_I9220OZHLPL_CHN.zip =606MB
Is that the right stuff? I am just downloading it.
Thx
Even if you get a whole rom, it's good. Flash with odin without the pit
Le_Tifou said:
Thanks for your adive.
How do I get the right kernel files I have no glue for what I should search for....
Ok I found recently this threat which seams to point to the origínal chinese android versions:
droidevelopers dot com/f479/11859-samsung-galaxy-note-i9220-china-firmware-list.html
which points to the following
CHINA I9220 Ice Cream Sandwich 4.0.4 Firmwares
Download PDA Version Release Date CSC version Country / Carrier
Link I9220ZCLPL 4.0.4 2012 July I9220OZHLPL China
from hotfile DOT com/dl/165512339/c6b85b4/I9220ZCLPL_I9220OZHLPL_CHN.zip =606MB
Is that the right stuff? I am just downloading it.
Thx
Click to expand...
Click to collapse
Yes, should be fine, it's made for GT-I9220. Just flash PDA.:good:
Thanks KERNEL has been changed back to original
lionelia said:
Yes, should be fine, it's made for GT-I9220. Just flash PDA.:good:
Click to expand...
Click to collapse
Thanks both of you!!!
Odin 1.87 worked so far. And immediately Windows recognized the phone as GT-I9220 again.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9220ZCLPL_I9220ZCLPI_I9220OZHLPL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> Sbl.bin
<ID:0/003> param.lfs
<ID:0/003> factoryfs.img
<ID:0/003> zImage
<ID:0/003> hidden.img
<ID:0/003> cache.img
<ID:0/003> modem.bin
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
I got after disconneting and taking out battery and restart -
got into mode VOL-up + power-on + center key
and made a factory reset as well as deleted cache
Modell: GT-I9220
Android version: 4.0.4
Baseband: I9220ZCLPI
KERNEL: 3.0.15 - ...
Build: IMM76D.ZCLPL
When I unpacked the ZIP file there was an additioal file ss_DL.dll what shall I do with it?
now it works thanks to you!
Great!
Nothing to do with the the dll file. Congrats for a working phone.
Rooting failure
nokiamodeln91 said:
Nothing to do with the the dll file. Congrats for a working phone.
Click to expand...
Click to collapse
Please help,
I was trying to root my Samsung galaxy note gt-i9220, I followed the video instructions from rootgalaxynote.com, I used the CWM.Zip, CWM-supers-v0.87.zip and after I installed the franco kernel-r5.zip
PROBLEM: after installing the franco kernel when I restarted the system my note comes on and shows Galaxy Note GT-I9220 and after that I have a black screen.
What can I do to get back the original state, it seems I can not handle rooting it. However it can get to the download mode when I place the volume up+power+home burton.
NB: I did not use a computer while doing this neither did I backup any thing

Bricked :(

I can't boot my phone, it says Custom binary blocked by FRP
I can't flash twrp, and whenever I try to flash a stock md5, odin fails
What do I do?
Update- I tried to flash a stock rom from http://forum.xda-developers.com/not...ware-firmware-kernel-modem-recovery-t2902574/
Results were
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl1.mbn
<ID:0/004> rpm.mbn
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Firs of all. How did you brick your phone?
Sent from my SM-N910T using Tapatalk
Did you by chance turned on the Samsung Activation Lock?.This happened to me the first time i tried to install custom rom, i thought the phone had bricked but I was able to get into recovery mode and restart the OS. Try booting into recovery mode and choose restart system If not you will need to flash a stock rom but it needs to be the same version you had.
nano303 said:
Firs of all. How did you brick your phone?
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
I booted it into recovery and got the Custom Binary Blocked message when I try to boot
glm0025 said:
Did you by chance turned on the Samsung Activation Lock?.This happened to me the first time i tried to install custom rom, i thought the phone had bricked but I was able to get into recovery mode and restart the OS. Try booting into recovery mode and choose restart system If not you will need to flash a stock rom but it needs to be the same version you had.
Click to expand...
Click to collapse
I would, but I can't boot into recovery mode
Fixed it! I flashed about a dozen different files on Odin, finally got a 5.1.1 tar.md5, that's working
aaronfrickinaustin said:
Fixed it! I flashed about a dozen different files on Odin, finally got a 5.1.1 tar.md5, that's working
Click to expand...
Click to collapse
Which one worked?? Please tell me! Stuck in the same situation
This error is due to the Samsung Activation Lock being on before flashing a custom rom, be sure to turn this off in the future before installing another rom. If by chance you forget and get the error just try flashing back the stock version of the rom you currently have and it should come up.

Emergency

i have installed twrp and inside twrp installed the supersu now when i reboot device it is stuck at the samsung galaxy s5 screen HELP!
dexter_17 said:
i have installed twrp and inside twrp installed the supersu now when i reboot device it is stuck at the samsung galaxy s5 screen HELP!
Click to expand...
Click to collapse
Take the battery for 30sec out and reboot again
i have tried that still no luck? have i soft bricked my device i can still boot into twrp
please help
Try to Reflash boot loader in Odin
Otherwise go into download mode and reflash your rom using Odin.
Then twrp
Then SuperSU (not the one in twrp)
how do i reflash bootloader,
all i did was:
boot device into download mode and use odin to install twrp
once inside twrp i clicked supersu install
now the phone remains at SAMSUNG S5 logo
device information:
SSN = g900fgsmh
SM-G900F
6.0.1
anyone? please
hello?
Download a Boot loader: https://www.androidfilehost.com/?w=files&flid=18030
Open Odin select AP and browse for the Bootloader and click install/flash.
i cannot find my one SSN = g900fgsmh any advice>?
dexter_17 said:
i cannot find my one SSN = g900fgsmh any advice>?
Click to expand...
Click to collapse
Download for G900f it should work
SSN = g900fgsmh i cannot find my device in the list
just tried but it still is stuck at samsung galaxy s5
<ID:0/004> Odin engine v(ID:3.1203)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> rpm.mbn
<ID:0/004> sbl1.mbn
<ID:0/004> tz.mbn
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/004> Removed!!
this all happened after install twrp can i recover for this nightmare
dexter_17 said:
this all happened after install twrp can i recover for this nightmare
Click to expand...
Click to collapse
Which TWRP version and SuperSU version do you have tried to installed?
And on which firmware you were before?
Twrp version is twrp-3.0.2-2-klte.img (1).tar
supersu version is BETA-SuperSU-v2.44
im not sure what firmware version but android version i had before but i had 6.0.1
dexter_17 said:
Twrp version is twrp-3.0.2-2-klte.img (1).tar
supersu version is BETA-SuperSU-v2.44
im not sure what firmware version but android version i had before but i had 6.0.1
Click to expand...
Click to collapse
Your SuperSU is very old.
Install this TWRP version again : https://dl.twrp.me/klte/twrp-3.0.2-2-klte.img.html
And latest SuperSU : http://download.chainfire.eu/1003/SuperSU/SR1-SuperSU-v2.78-SR1-20160915123031.zip
are you here please
it must of started the bootloop after installing twrp, i have tried all the other versions also but still doesnt work.....

Galaxy s6 System Software not authorized by AT&T

Hi All This is my first post here .
yesterday i had a problem installing Xposed framework it said that it need a custom rom to be istalled
so i downloaded the TWRP app chosed my recovery version and run it, it was flashed succesfully but when i tried to boot to it i got this message in blue screen "System Software not authorized by AT&T ... "
I was able to boot the system normally so i tried to recovere the original stock recovery i downloaded an app called Flashify downloaded a stock recovery ( im not sure that it was the original ) and flash it , after rebooting i was shocked by the blue screen on the recovery and also on the system so i can't boot to the system now !
I tried to flash another TWRP using odin 3.10.6 , 3.11 and 3.12.3 but in the two cases it fails with this error :
Code:
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Im totally lost now i have a lot of personal data inside ( 6gb of pics + 200 mb of call records + phone numbers )
I bought the phone from a third party , and we dont have any AT&T agency here
Information about the phone :
- I think that the phone was rooted because the root checker said that but when i install the su it said that i need a binary update and every time i do that it reboot without updating , when i tried from the recovery it said,signature failed or something like that .
- I had android 5.1 i think it was a custom rom because when the s6 logo appear I see under Custom with an open lock
When i go to the download mode they write
ODIN MODE //it was there even before i flash it
PRODUCT NAME : SM-G920V
CURRENT BINARY : CUSTOM // it was OFFICIAL before flashing
SYSTEM STATUS : CUSTOM
REACTIVATION LOCK : OFF
SECURE DOWNLOAD : ENABLED
RP SWREV : B:4 K:3 S:3
on the back of the phone the product name is : SM-G920F
on the previous rom it was : SM-G920F
Please any solution to back up my DATA then flash a new rom updated with a custom recovery Or even recover the original stock recovery only ( i was not using an AT&T sim card )
(whitch version i should use to flash 920F or V or A ? )

SM-N910T3 still stuck in Download - Odin: firmware & twrp FAIL

My phone will keep itself stuck in reboot.
I can 3 button it to get to the downloading screen or the blue options screen.
In the downloading screen, I am able to connect Odin. I tried ADP to firmware and twrp...both failed (multiple times).
On start, it shows blue script reboot...then dead android with red exclamation triangle...then to the blue script menu. From this, I have tried:
- reboot (arrives back at same screen)
- reboot to bootloader
- apply update from SD card...says can not mount card (I tried loading disk image onto SD card to reflash that way)
- wipe data/factory reset...tries and quickly fails - something or other found, stays stuck
- clear cache...seems to do that and then leave me at the same screen
- mount system - asks me to do something that I do not at all understand
I tried downloading Kies3...it says it can not help me because I do not have a code from the old computer...?
I also tried downloading dr.phone.
Nothing seems to help.
I found out about Odin, firmware, twrp, windowsdiskimager, etc. ALL FROM THIS SITE... So, I am trying my best to understand all of this terminology and the processes.
However, after spending all day trying to solve this, I am feeling totally stumped...
Please help : )
Screen presently reads:
Android Recovery
MMB29M.N910T3UVU3EQC1
samsung/trltetmofrp/trltetmo
6.0.1/MMB29M/N910T3UVU3EQC1
user/release-keys
Use volume up/down and power
Reboot system now
reboot to bootloader
apply update from ADB
Apply update from SD card
Wipe data/factory reset
Wipe cache partition
Mount /system
View recovery logs
Power off
_____
Supported API: 3
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : TMB
Successfully applied multi-CSC.
-------------------------------------------------------------
After trying Odin (3.09) and twrp (twrp-3.0.2-0-trltetmo.img.tar), this is the screen:
ODIN MODE (HIGH SPEED)
PRODUCT NAME: SM-N910T3
CURRENT BINARY: Custom
SYSTEM STATUS: Custom
FAP LOCK: ON
KNOX WARRANTY VOID: 0x1 (4)
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S1, T1, A1, P1
SECURE DOWNLOAD: ENABLE
UDC START
Custom Binary(recovery) Blocked by FAP Lock
...android image
downloading...
Do not turn off target!!
------------------------------------------------------------
ODIN LOG:
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have fixed mine with same symptoms.
After two years of intensive use my n910t stuck at boot logo .
I heated the emmc with hot air and voila the phone booted normally just i broked my front cam
I downgraded to official lollipop version to get more battery life and much cooler cpu in my opinion !

Categories

Resources