return to kitkat problem - Galaxy Note 4 Q&A, Help & Troubleshooting

did anyone try to comeback (910C)lolipop (new poland stock rom COJ5) to kitkat (4.4.4) via odin
in Turkish forum some guy tried to comeback ,but he did not success it.I told him what I know about this.
he also used 4 parts rom and pit files ,one part rom and pit files,firstly try to kitkat bootloader via odin etc.etc but he said no,no,no
some guys are saying,now samsung has prevent to return kitkat from COJ5 ,is that true or not
we need alternatives way

hi,still no any idea
guys,I thing samsung putted a bootloader lock to return to kitkat even 5.0.1.
I tried to both of them ,but result no succesed it. that is way ,whom want to return to comeback to kitkat and 5.0.1 bootloader ,they will meet this lock. maybe you want to use miui rom like me .what will I do

I bought a new Note 4 N910G Indian version with LP 5.01. Loaded a custom Rom, Dr.Ketan ROM 5.0.1 after rooting. Got Xposed working but still didnt like it. I then downgraded to Stock Kitkat 4.4.4 from Sammobile site with ODIN. Rooted after loading TWRP again. (Root got disabled on downgrading so had to reroot SuperSu). Loaded Xposed. Everything working smoothly. Only one issue is Lockscreen Widgets which even Xposed is not able to bypass when the phone has PIN or Pattern lock but very happy now. Quite similar to my JB Note 3 N9005 which is what I wanted.

pelase help, any idea, suggestion,etc.
what should I do ,what can I do

i tried 5.0.1 but then came back to ANK3 4.4.4 Kitkat via ODIn with no problem. Nothing still beat the Xposed on Kitkat. One thing I am looking forward to is more options of 4.4.4 kernel. I can only see 1 kernel for kitkat which is KT kernel. Hopefully some more kernel for Note 4 Kitkat OS will be available.

theleftykid said:
i tried 5.0.1 but then came back to ANK3 4.4.4 Kitkat via ODIn with no problem. Nothing still beat the Xposed on Kitkat. One thing I am looking forward to is more options of 4.4.4 kernel. I can only see 1 kernel for kitkat which is KT kernel. Hopefully some more kernel for Note 4 Kitkat OS will be available.
Click to expand...
Click to collapse
do you mean try to change the kernel(kitkat)to return kitkat

mudur1998 said:
pelase help, any idea, suggestion,etc.
what should I do ,what can I do
Click to expand...
Click to collapse
Did you do all the steps properly?
I started off by doing a complete Reset and Format in TWRP. Wiped everything including External SD card.
So maybe you should do that first. But backup any important data on some external storage not connected to the phone. Most important : Make sure you are using the correct stock Kitkat ROM version for your model from Sammobile site.
Follow the instructions on Sammobile's firmware download page, and you should be back to stock Kitkat 4.4.4 soon.

niceguy1430 said:
Did you do all the steps properly?
I started off by doing a complete Reset and Format in TWRP. Wiped everything including External SD card.
So maybe you should do that first. But backup any important data on some external storage not connected to the phone. Most important : Make sure you are using the correct stock Kitkat ROM version for your model from Sammobile site.
Follow the instructions on Sammobile's firmware download page, and you should be back to stock Kitkat 4.4.4 soon.
Click to expand...
Click to collapse
that is good idea I will try it,firstly format evrything in twrp and after that try to flash rom with odin .I know my rom is correct rom.
I will report it

sorry ,no result,one part rom,four part roms,with pit and without pit .
before start I wiped everything in twrp

now, I believe that samsung putted a lock to prevent return also 5.1.1 my own rom

mudur1998 said:
now, I believe that samsung putted a lock to prevent return also 5.1.1 my own rom
Click to expand...
Click to collapse
any logs on odin?

kerbiii said:
any logs on odin?
Click to expand...
Click to collapse
knox warranty void 1
ap survey 2
sw rev.check fail device 2 binary 1
ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> _(N910CXXU1COI4_4files_5.1.1_TUR_Factory_Firmware)(like that I do not rememeber but it is my own firmware) HOME.tar .md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin engine v(ID:3.1005)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> sboot.bin
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I also tried kitkat but have no more odin logs

Dont know why you are fiddling with PIT. Not required to touch it at all. As far as I know 5.1.1 to KK is quite possible, just as mine I successfully downgraded from 5.0.1 to KK.
Once you wipe everything and format SD card as well, and start with a clean slate, it should work through ODIN. Try with another version of ODIN maybe? Dont touch PIT section at all.

niceguy1430 said:
Dont know why you are fiddling with PIT. Not required to touch it at all. As far as I know 5.1.1 to KK is quite possible, just as mine I successfully downgraded from 5.0.1 to KK.
Once you wipe everything and format SD card as well, and start with a clean slate, it should work through ODIN. Try with another version of ODIN maybe? Dont touch PIT section at all.
Click to expand...
Click to collapse
I mean 5.1.1 but COJ5 (poland new firmware),I also tried with pit and without pit,I could not to downgrade 4.4.4 or 5.0.1 and also my own rom 5.1.1 COI4

Same problem
I am having the same problem, please advise the solution
please text on Whatsapp +966553270134

mudur1998 said:
I mean 5.1.1 but COJ5 (poland new firmware),I also tried with pit and without pit,I could not to downgrade 4.4.4 or 5.0.1 and also my own rom 5.1.1 COI4
Click to expand...
Click to collapse
have you tried flashing CWM recovery and wiping everything and using clean install? that way it will remove your 5.1.1 FW

kerbiii said:
have you tried flashing CWM recovery and wiping everything and using clean install? that way it will remove your 5.1.1 FW
Click to expand...
Click to collapse
yes you can flash twrp,no problem. I tried also I wiped everything and clean install with odin.no,no,no
never comeback to even COI4

mudur1998 said:
yes you can flash twrp,no problem. I tried also I wiped everything and clean install with odin.no,no,no
never comeback to even COI4
Click to expand...
Click to collapse
try to search for custom ROM with the same bootloader that you are using right now, your official bootloader will not let you flash any older bootloader thats why you cant flash anything under 5.1.1.,
i suggest try flashing the latest wanam
http://forum.xda-developers.com/note-4/development/rom-wanamlite-clean-odex-xposed-t2923266
if you successfully flash the wanam then try to flash the stock kitkat again

kerbiii said:
try to search for custom ROM with the same bootloader that you are using right now, your official bootloader will not let you flash any older bootloader thats why you cant flash anything under 5.1.1.,
i suggest try flashing the latest wanam
http://forum.xda-developers.com/note-4/development/rom-wanamlite-clean-odex-xposed-t2923266
if you successfully flash the wanam then try to flash the stock kitkat again
Click to expand...
Click to collapse
yes, without miui I am using these types of custom roms DN5,sixperience,e robot,rulinglite,sweet rom,etc.but I like only miui rom ,that is way I want to try come back bootloader 4.4.4 or 5.0.1.
It is (wanam lite rom)based COJ5,what would be change.but I have tried it. I have already installed wanamlite rom, and wanam kernel etc.no ,no, no

mudur1998 said:
yes, without miui I am using these types of custom roms DN5,sixperience,e robot,rulinglite,sweet rom,etc.but I like only miui rom ,that is way I want to try come back bootloader 4.4.4 or 5.0.1.
It is (wanam lite rom)based COJ5,what would be change.but I have tried it. I have already installed wanamlite rom, and wanam kernel etc.no ,no, no
Click to expand...
Click to collapse
what im trying to say is, try to flash 5.1.1. custom rom first and from there downgrade to kitkat. have you done trying that?

Related

[Q] help with xnote

hey guys i was wondering if anyone could help me with installing the latest build of xnote 10.0 for my n9005
i am currently using the xnote 7.0 rom which is 4.3
my baseband is n900AUCUBMJ5
kernel is 3.4.0-1625098 [email protected]#1
and my version of xnote is XXUDML2
i currently have safestrap installed as my recovery
i am rooted as well
the xnote note instructions read as the following
"
[SIZE="1"[SIZE="3"]]ONLY IF COMING FROM ANDROID 4.3
FIRST DO THIS, SKIP IF ALREADY DONE CLICK H E R E
So you need a 4.4.2 official firmware already installed, a working KITKAT recovery and ROOT to backup EFS (use chainfire root for KITKAT)
1- Untick reactivation lock in security settings
2- do a EFS backup from your KitKat firmware
3- check the MD5 of your downloaded X-Note zip
4- reboot recovery
5- wipe data (don't do other wipes)
6- install zip and choose the rom in your sd
7- follow aroma, wait for first boot, done.[/SIZE][/SIZE]"
so my question is do i need to follow those instructions in order to flash from the old xnote 7 to xnote 10 and if so where do i find the download link for the 4.4.2 official poland firmware. (will the langauge be in polish) and will it completely wipe my device in any part of this process and do i need to install a different or newer recovery
thanks for all the help in advance
-ben
Omg
Is there a question?
kenny1991 said:
Omg
Is there a question?
Click to expand...
Click to collapse
Yes > >>
so my question is do i need to follow those instructions in order to flash from the old xnote 7 to xnote 10 and if so where do i find the download link for the 4.4.2 official poland firmware. (will the langauge be in polish) and will it completely wipe my device in any part of this process and do i need to install a different or newer recovery
thanks for all the help in advance
-ben
Click to expand...
Click to collapse
theres a couple of threads in the general section of this forum to download 4.4.2 - The language won't be Polish as you get to choose on setup wizard.
It won't wipe your device using Odin to flash it - although it's advisable you do wipe.
Lastest CWM by Chenglu - PhilZ Adavanced CWM - TWRP are all Kitkat compatible now. -- remember you don't need to root to install a custom recovery.
radicalisto said:
Yes > >>
theres a couple of threads in the general section of this forum to download 4.4.2 - The language won't be Polish as you get to choose on setup wizard.
It won't wipe your device using Odin to flash it - although it's advisable you do wipe.
Lastest CWM by Chenglu - PhilZ Adavanced CWM - TWRP are all Kitkat compatible now. -- remember you don't need to root to install a custom recovery.
Click to expand...
Click to collapse
thank you for the help is safestrap 3.71 using twrp v 2.6.3.1 an acceptable recovery to use to flash 4.4.2 and then xnote afterwards?
armadilloben said:
thank you for the help is safestrap 3.71 using twrp v 2.6.3.1 an acceptable recovery to use to flash 4.4.2 and then xnote afterwards?
Click to expand...
Click to collapse
Not 100% sure with using safestrap, you'd have to check the safestrap thread for advice.
flustered
radicalisto said:
Not 100% sure with using safestrap, you'd have to check the safestrap thread for advice.
Click to expand...
Click to collapse
okay in all honesty im becoming frustrated with this whole process could someone possibly reply with clear instructions with exactly what i need to do in order to update xnote 7.0 to xnote 10.0 im getting a tad bit confused as to exactly what i need to do :crying:
armadilloben said:
okay in all honesty im becoming frustrated with this whole process could someone possibly reply with clear instructions with exactly what i need to do in order to update xnote 7.0 to xnote 10.0 im getting a tad bit confused as to exactly what i need to do :crying:
Click to expand...
Click to collapse
Using safestrap automatically throws a spanner in the works due to the way it's handled flashing etc, there won't be a simple way with this but there are ways.
gchat
if anyone would be willing to google hangout chat me or skype me and possibly walk me through this process it would be hugely appreciated all of my usernames are armadilloben
radicalisto said:
Using safestrap automatically throws a spanner in the works due to the way it's handled flashing etc, there won't be a simple way with this but there are ways.
Click to expand...
Click to collapse
well in that case do you know of a way for me to reflash to a different recovery?
im sort of becoming overwhelmed with this process.
i understand how to flash roms pretty well and have been following the xda community for about two years now ive learned and read enough posts to not be a complete idiot anymore. this process however has kinda screwed with my head and im nervous to attempt to update to 10.0 without clearer instructions
ok ii attempted to do it
alrighty so i built up the courage and attempted to flash the poland 4.42 stock rom via odin i checked auto reboot and f. reset time loaded the firemware into AP
i put my phone into download mode plugged it in the my machine tried to start the proceess with odin and i got the following fail error
heres the log:
"<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENB3_N9005OXXENB1_N9005XXUENB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin v.3 engine (ID:4)..
<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> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)"
in download mode my phone says the following
"odin mode
product name sm-900a
current binary: samsung official
system status: official
know kernel lock: 0x0
knox warranty void: 0x0
qualcomm securtboot: enable (csb)
rp swrev: s2, t2 , a2 , a2, p2
wirte protection: enable
secure check fail: sbl1
what exactly did i do wrong?
my baseband is n900AUCUBMJ5
Click to expand...
Click to collapse
Which Note do you have? region/model I mean, defo an N9005? -- on first look at that I assume an ATT N900A - possibly wrong tho -
radicalisto said:
Which Note do you have? region/model I mean, defo an N9005? -- on first look at that I assume an ATT N900A - possibly wrong tho -
Click to expand...
Click to collapse
its an att sm n900a so US and ATT
Ah OK thought so, due to the bootloader being locked you can't write to the device hence the error. I wouldn't advise trying to write N9005 ROMs for now. I'm gonna guess however that due to the BL lock and since no 4.4.2 is out yet for the ATT version you won't be able to upgrade because of the requirement for the new 4.4.2 BL to boot up xnote 10.
Your really better off asking on the safestrap thread though as most people in this part won't know due to us having the international model.
radicalisto said:
Ah OK thought so, due to the bootloader being locked you can't write to the device hence the error. I wouldn't advise trying to write N9005 ROMs for now. I'm gonna guess however that due to the BL lock and since no 4.4.2 is out yet for the ATT version you won't be able to upgrade because of the requirement for the new 4.4.2 BL to boot up xnote 10.
Your really better off asking on the safestrap thread though as most people in this part won't know due to us having the international model.
Click to expand...
Click to collapse
so your saying that even though i installed the xnote 7.0 that 10.0 wont work because i need the bootloader unlocked. and how the hell did i install 7.0 if it was locked in the first place?
armadilloben said:
so your saying that even though i installed the xnote 7.0 that 10.0 wont work because i need the bootloader unlocked. and how the hell did i install 7.0 if it was locked in the first place?
Click to expand...
Click to collapse
7 used 4.3's Bootloader IIRC, 8 onwards uses the new KK bootloader. ATT has the JB bootloader, but doesn't yet have access to the new 4.4.2 bootloader.
radicalisto said:
7 used 4.3's Bootloader IIRC, 8 onwards uses the new KK bootloader. ATT has the JB bootloader, but doesn't yet have access to the new 4.4.2 bootloader.
Click to expand...
Click to collapse
ahhhh okay that makes sense to me. so basically am i SOL until i can get an official att 4.42 stock rom?
armadilloben said:
ahhhh okay that makes sense to me. so basically am i SOL until i can get an official att 4.42 stock rom?
Click to expand...
Click to collapse
I think so
radicalisto said:
I think so
Click to expand...
Click to collapse
crap that makes me very frustrated do you know if i can move to cyanogenmod 11 with my locked bl?
if not i really appreciate the help brother, its nice to know there really are people will to help all the time here
In regards to CM - I honestly have no idea if it's compatible with the ATT model - but from having a quick glance around the ATT Note 3 forum I can't see that it is. And checking the new unified build tree it shows it's only compatible with "hltespr(Sprint), hltetmo(T-Mobile), hltevzw(Verizon), htlexx(N9005) - However, that's not to say that there is no definite method. One may come via Safestrap or possibly already and I have just missed it.
No problem with helping, just sorry couldn't help you get xnote 10
radicalisto said:
In regards to CM - I honestly have no idea if it's compatible with the ATT model - but from having a quick glance around the ATT Note 3 forum I can't see that it is. And checking the new unified build tree it shows it's only compatible with "hltespr(Sprint), hltetmo(T-Mobile), hltevzw(Verizon), htlexx(N9005) - However, that's not to say that there is no definite method. One may come via Safestrap or possibly already and I have just missed it.
No problem with helping, just sorry couldn't help you get xnote 10
Click to expand...
Click to collapse
its alright not your fault and alrighty i mean ive searched around for cm for att and didnt find it either.
in all reality i just wanted 10.0 to get 4.42 because i assumed that my battery drain would be better on it. i love 7.0 its a great rom i just wish there was a real fix for my audio out wakelock issues that suck my battery dry. i have a 10,000ma zero lemon battery on my phone and it still only lasts me about a day. like its at about 20 percent when i charge it before bed every night

[Q] downgrade 4.4.2 to 4.2.2 successful

i have make downgrade to my phone i9500 form 4.4.2 to 4.2.2
with this firmware XFE-I9500XXUBMH1-20130927115211.zip
and phone work fine but after i back to download mode it's show custom
how i can fix that
thank you
Just flash another 4.2.2 firmware
RubbaBand said:
Just flash another 4.2.2 firmware
Click to expand...
Click to collapse
can you share link for best firmware have good speed and stable
EgyMan said:
can you share link for best firmware have good speed and stable
Click to expand...
Click to collapse
here is the link
and how did you downgraded to 4.2.2?
RubbaBand said:
here is the link
and how did you downgraded to 4.2.2?
Click to expand...
Click to collapse
this rom you share is stable ? and save battery
i just make wipe cash and format then i use odin and flash this > XFE-I9500XXUBMH1-20130927115211.zip
that all
i think this firmware XFE-I9500XXUBMH1 have original bootloader or some like that, make you do the downgraded easy
The link that I gave you contains the stock & original 4.2.2 that came with the device for the first time
So its the most stable
Please give me the link to the 4.2.2 firmware that you used for downgrade.
And after you downgraded you dont have wifi or imei problems??
RubbaBand said:
The link that I gave you contains the stock & original 4.2.2 that came with the device for the first time
So its the most stable
Please give me the link to the 4.2.2 firmware that you used for downgrade.
And after you downgraded you dont have wifi or imei problems??
Click to expand...
Click to collapse
this is link >> http://d-h.st/4bG
wifi and all things working so fine and bettery is good
,
but there is problem on phone when i use apk Multi room and phone auto lost os cygenmode and 4.3 and i flash new firmware 4.4.2
and after i goto recovery mode and i make wipa data / facorty reset and done
but when i press on wipa cash partition phone get auto restart
and after i make downgrade it's still
Ok tnx man
and the solution for your problem is to use custom recovery to wipe data & cache
Then flash stock 4.2.2
Downgrade the latest Samsung devices is the MOST STUPID THING you can do in your life. Maybe 2 or 3 persons dont agree with me but the rest for sure yes. If ODIN let u downgrade becomes the problems with wifi, data, random reboots, warranty void, battery drains... And you downgrade coz ur phone was bad with the new android version? Come on! :laugh:
Joku1981 said:
Downgrade the latest Samsung devices is the MOST STUPID THING you can do in your life. Maybe 2 or 3 persons dont agree with me but the rest for sure yes. If ODIN let u downgrade becomes the problems with wifi, data, random reboots, warranty void, battery drains... And you downgrade coz ur phone was bad with the new android version? Come on! :laugh:
Click to expand...
Click to collapse
after i make Downgrade phone is have good speed and working fine and battery is good
before i Downgrade phone is very slow and freeze for more time <<< u can say 4.4.2 it's very bad software because i have use it and phone it's killed after i use , but now phone is very good
if Samsung will fix that problem on 4.2.3 i will update it , but if still i never update it
i wanna use my phone without problem that all i need
RubbaBand said:
Ok tnx man
and the solution for your problem is to use custom recovery to wipe data & cache
Then flash stock 4.2.2
Click to expand...
Click to collapse
can you gived me link for custom recovery to flash it and how flash it
and if after i use custom recovery and make wipe data & cache
and flash stock rom phone will work fine and every think will good ?
thank you
EgyMan said:
can you gived me link for custom recovery to flash it and how flash it
and if after i use custom recovery and make wipe data & cache
and flash stock rom phone will work fine and every think will good ?
thank you
Click to expand...
Click to collapse
the link for Custom recovery
and how to flash custom recovery? just flash it like you want to flash firmware via odin, its the same thing
then boot into recovery wipe data & cache & dalvik cache
then you can flash stock, everything should be ok
After i Downgrade knox bootloader will be removed
No it will stay !
RubbaBand said:
the link for Custom recovery
and how to flash custom recovery? just flash it like you want to flash firmware via odin, its the same thing
then boot into recovery wipe data & cache & dalvik cache
then you can flash stock, everything should be ok
Click to expand...
Click to collapse
there option wipe for flash new rom i can use it or it's wrong
Choices Wipa Option
Clean To install a new Rom
No just try wipe
If the problem remains
First backup your EFS
Then wipe for new rom install
And flash stock
RubbaBand said:
No just try wipe
If the problem remains
First backup your EFS
Then wipe for new rom install
And flash stock
Click to expand...
Click to collapse
phone is show massage abort
SW REV Invalid Magic Strings
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9500XXUBMG9_I9500OJVBMG9_I9500XXUBMG9_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> sboot.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
why this massage ? and firmware not want flash
i use odin 3.7 and 3.9
Check if USB Debugging enabled
RubbaBand said:
Check if USB Debugging enabled
Click to expand...
Click to collapse
i make it enabled and i's still not able ?
it's show this massage
SW REV Invalid Magic Strings
i make usb enable and disable and i change usb
before that i install CMW you gived me easy and working and i flash my phone on this pc for meany time i remove kieas and install it
After i flash 4.2.2 knox will be trigged or it will be removed

Can't flash stock ROM through ODIN for my Note 3 N9005

Hi. I'm having some trouble when I tried to flash my Note 3 with CM13 but it seems like can't associate with gapps because it will crash. My note 3 is currently on CM13 but without any gapps. I decided to flash it back to original stock rom but ODIN fail.
it says:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1100)..
<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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
In the download mode, it says:
SECURE CHECK FAIL : aboot
I don't know what to right now. Help me. TQ
Download another copy .
JJEgan said:
Download another copy .
Click to expand...
Click to collapse
Another copy of STOCK ROM?
Yes and odin
Sent from my GT-N8013 using XDA-Developers mobile app
Odin is failing when trying to flash the bootloader (aboot.mbn) so either the rom isn't for the phone or the bootloader is too old.
audit13 said:
Odin is failing when trying to flash the bootloader (aboot.mbn) so either the rom isn't for the phone or the bootloader is too old.
Click to expand...
Click to collapse
Already try another copy of Stock ROM. But it keeps failing. So how to solve the out of dated bootloader?
Arobase40 said:
This happened to me after using CM ROMs on my old GN1 : hard to recover to stock...
This also happened with my GN3 with stock dutch firmware. Don't know the reasons... ^^
Try to flash a N9005XXUGN1 or N9005XXUEND3 kk firmwares (not dutch) to downgrade first to KK, then you could try upgrading to any other Lollipop firmwares...
Seems to me it's impossible to change or upgrading from Lollipop to another Lollipop. I always had to downgrade first to KK before upgrading to Lollipop so if you used CM13 it should be a bigger problem...
PS : BTW watch at your CM13 settings if a OEM unlock option is activated or de-activated...
Click to expand...
Click to collapse
Will try to download the KK ROM since the file is too big. But then where to find the OEM unlock option?
Isn't the oem unlock option available on the nexus 5x and 6p?
Try take out your battery 1st, then use 3 button combination to go to download mode.
Also try another usb cable as well..
I have never seen the oem unlock option on a cm rom. Doesn't the oem unlock relate to the bootloader? The n9005 has never had a locked bootloader.
With a locked bootloader, cwm, twrp, and ROMs not based on a Samsung kernel could never be flashed to the phone.
The inability to cross flash firmware is due to security checks built into the bootloader to ensure that the ROMs being flashed via Odin is made for the particular phone and not because it is locked. Think of it more as a safety feature.
In some of the Samsung phones, older firmware can't be flashed as the bootloader on the phone cannot be downgraded.
Arobase40 said:
This happened to me after using CM ROMs on my old GN1 : hard to recover to stock...
This also happened with my GN3 with stock dutch firmware. Don't know the reasons... ^^
Try to flash a N9005XXUGN1 or N9005XXUEND3 kk firmwares (not dutch) to downgrade first to KK, then you could try upgrading to any other Lollipop firmwares...
Seems to me it's impossible to change or upgrading from Lollipop to another Lollipop. I always had to downgrade first to KK before upgrading to Lollipop so if you used CM13 it should be a bigger problem...
PS : BTW watch at your CM13 settings if a OEM unlock option is activated or de-activated...
Click to expand...
Click to collapse
Finally managed to restore to its original stock rom after downloading Sprint Lollipop version. I dont know why it must be a Sprint. Anybody know how to unlock the carrier ? I live in Malaysia tho
aruruuuu said:
Finally managed to restore to its original stock rom after downloading Sprint Lollipop version. I dont know why it must be a Sprint. Anybody know how to unlock the carrier ? I live in Malaysia tho
Click to expand...
Click to collapse
Try the Sprint forum .
What is the exact model # of the phone shown in download mode? Was the phone new or used when you got it?
Arobase40 said:
Did you buy your GN3 to Sprint ? lol
Click to expand...
Click to collapse
It is an import version. It is unlocked when I first buy it. And now it relocked after I flash back to Stock ROM

Newbie Help ! Flash i337 ATT To stock then to Android 7

Ok ive never messed with android before, and have spent hours n hours etc reading and trying things... and have failed ;(
Tried to play with TWRP or whatever etc... that didnt work
Ive got a S4 ATT i337 that is on 4.2.2 it has some custom FW on it and its UNLOCKED.
I was using this a while back on TMOBILE so it IS unlocked (from AT&T)...
Ive tried to boot into recovery to SET IT BACK to STOCK (1st) then (so I could put it on 7.1)
I get a ATTENTION message that appears and says: System software not authorized by AT&T has been found on your phone. Please turn off and goto the nearest at&t store... (not happing haha)
I Have found the original FW for my ATT I337...
If anyone can help me in simple english of HOW to etc It would be a big xmas present to me !!!
Thanks in advance
Is the bootloader locked? If yes, you cannot run custom roms based on anything other than a stock Samsung rom.
Could you tell me how I can check to see if the bootloader is locked ? and I will
I read something somewhere about the baseband it ends in MF3
and Kernal version 3.4.0-812098
I dont know WHICH or WHAT ROM is loaded onto it but it IS version 4.2.2 android
audit13 said:
Is the bootloader locked? If yes, you cannot run custom roms based on anything other than a stock Samsung rom.
Click to expand...
Click to collapse
Transam98 said:
Could you tell me how I can check to see if the bootloader is locked ? and I will
I read something somewhere about the baseband it ends in MF3
and Kernal version 3.4.0-812098
I dont know WHICH or WHAT ROM is loaded onto it but it IS version 4.2.2 android
Click to expand...
Click to collapse
Download terminal emulator app from play store. Open it and type "getprop ro.bootloader" without the " "
It will give you some letters and numbers. If the last 3 are anything but MDL or MDB then your bootloader is locked and you have to use safe strap and can only boot Samsung ROMs.
Stoney: Thanks for the reply... So I got the terminal an it replied I337UCUAMF3...
Can you tell me the next step ?
(Ill google and get SAFE STRAP)....
what file would I use with safestrap ? Can I still put Android 7.1 on this ?
Thanks in advance !!
StoneyJSG said:
Download terminal emulator app from play store. Open it and type "getprop ro.bootloader" without the " "
It will give you some letters and numbers. If the last 3 are anything but MDL or MDB then your bootloader is locked and you have to use safe strap and can only boot Samsung ROMs.
Click to expand...
Click to collapse
If the bootloader is locked, and it looks to me like it is, you wont' be able to install Nougat or MM ROMs.
understandable ! Thanks for the info !!
So I have android 4.2.2 on it now (remember at&t i337 S4)....
is there a newer ROM like android 5 or 6 I can put onto it ? (stock ?)
I DID get safestrap and installed that
audit13 said:
If the bootloader is locked, and it looks to me like it is, you wont' be able to install Nougat or MM ROMs.
Click to expand...
Click to collapse
Don't think there is any custom MM but there may be a custom LP but a custom LP may require an updated bootloader and modem.
I would consult the ROM threads located here: http://forum.xda-developers.com/galaxy-s4-att/development/rom-resurrectionremix-5-7-4-t3476519
well I screwed up LOL ;(
I did a backup of my ROM with safestrap (its on the SD Card) and tried to write the file and now phone is stuck on attention yellow symbol ;(
I CAN boot into the DOWNLOADING but odin just sits there ;(
I guess phone now = garbage ;(
audit13 said:
Don't think there is any custom MM but there may be a custom LP but a custom LP may require an updated bootloader and modem.
I would consult the ROM threads located here: http://forum.xda-developers.com/galaxy-s4-att/development/rom-resurrectionremix-5-7-4-t3476519
Click to expand...
Click to collapse
does the phone appear as a com port in Odin? You're using the original Samsung USB cable?
the phone DOES appear in odin
Im using a motorla cable but does still fully work....
I also can get the phone into DL mode (pwr down,home,power)
and it WILL take a Download....
when it boots up it does says SAMSUNG and CUSTOM and a UNLOCKED Padlock...
But I guess I cant find the correct files ;( as it always goes to the attention from att detected blah blah blah software....
Id just be happy to get this to the newest ATT Stock FW and then unlock it I believe it is called 4.4.2 and im on 4.2
or IF it exists would be nice to get to at least 5.0 to use android auto
audit13 said:
does the phone appear as a com port in Odin? You're using the original Samsung USB cable?
Click to expand...
Click to collapse
Did you try flashing a stock rom from sammobile.com?
Ive downloaded : I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5
(from sammobile)... 2.49Gb
but rememeber my bootloader says (ends in MF3) and the only TWO on sammobile are MDL and MDB..
but of course the file name has MDB in it..... I337UCUAMDB_I337ATTAMDB_I337UCUAMDB_HOME.tar.md5
I loaded it in Odin3 (run as admin) and clicked AP and loaded it there, and it fails:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Id really love to get this going If you or someone can help/make suggestions for me to try as im pulling my hair out ;(
audit13 said:
Did you try flashing a stock rom from sammobile.com?
Click to expand...
Click to collapse
Bootloader is definitely locked based on Odin log.
This may help to restore the phone and upgrade the rom: http://forum.xda-developers.com/gal...-to-update-to-i337oc3-5-0-1-keeproot-t3075814
is there anything I can do ? It DID have a custom rom on it (well when it starts booting it says CUSTOM and has a padlock unlocked) and it was also unlocked (not stuck to at&t)... but now im just stuck with that attention logo ;(
audit13 said:
Bootloader is definitely locked based on Odin log.
This may help to restore the phone and upgrade the rom: http://forum.xda-developers.com/gal...-to-update-to-i337oc3-5-0-1-keeproot-t3075814
Click to expand...
Click to collapse
I'm not sure how the phone had a custom rom and a locked bootloader and now has a locked bootloader.
Which rom was on the phone running?
I believe it was somewhat a stock firmware, nothing looked "fancy" compared to a regular at&t firmware but it was DEF unlocked as I used to have a tmobile sim in it ....
but it still boots up with SAMSUNG and a unlocked padlock and then the samsung ring animation, then the AT&T logo, now it just boots u the samsung unlock "custom" and then to the yellow exclamation point about non at&t software.
audit13 said:
I'm not sure how the phone had a custom rom and a locked bootloader and now has a locked bootloader.
Which rom was on the phone running?
Click to expand...
Click to collapse
Were you able to try the methods outlined in the referenced thread to revive and update the phone?
I tried them but none of them work
audit13 said:
Were you able to try the methods outlined in the referenced thread to revive and update the phone?
Click to expand...
Click to collapse

Samsung S4 SGH I337(Don't know the PDA it's running on) hangs on AT&T logo.

Dear All,
I have been reading many threads for a week before I decided to post a new thread here.
I am running in a big problem here with my S4 SGH-I337 which I have. I have never updated it with any version and it's hanging on it's ATT logo. I have tried all the factory and data reset options which I have come across on this forum, but the phone didn't come back to life.
Then I tried to flash it with Odin using I337UCUAMDB tar file(Since the phone is not working I couldn't find the PDA its running on), but it's failing saying FAIL! (Auth). Since I am doing it first time and I don't know much about flashing things, I am stuck out here. After doing some research I found that I should flash it with the PDA version matching to my phone but since my phone is not booting up I am not sure how can i find the PDA version for my phone. Even I have tried reaching to SAMSUNG's authorized center but they replied, as you are in INDIA and your phone was purchased when you were in USA, so we don't have that software to repair it. Please help me as I don't know what to do this phone now. Your help would be greatly appreciated.
Have you tried to ODIN the MDL firmware instead of the MDB firmware? It might be on MDL if you never updated it. When you get it working my advice is DO NOT take any OTA firmware updates until you know what bootloader you're on. If it is MDL then NEVER update it because the MDL bootloader had a flaw in it that can be exploited by using Loki doki to allow you to boot custom ROM and recovery.
StoneyJSG said:
Have you tried to ODIN the MDL firmware instead of the MDB firmware? It might be on MDL if you never updated it. When you get it working my advice is DO NOT take any OTA firmware updates until you know what bootloader you're on. If it is MDL then NEVER update it because the MDL bootloader had a flaw in it that can be exploited by using Loki doki to allow you to boot custom ROM and recovery.
Click to expand...
Click to collapse
Thank You! so much StoneyJSG, Actually I have come across one post that says never update it on if you have MDB/MDL firmware, so I got scared and didn't try anything. As your advice let me try using MDL firmware, hopefully that should work if you are advising it. Just to confirm it once if I get successful then I would be able to update it with custom ROM as you mentioned.
mahendra_bhawsar said:
Thank You! so much StoneyJSG, Actually I have come across one post that says never update it on if you have MDB/MDL firmware, so I got scared and didn't try anything. As your advice let me try using MDL firmware, hopefully that should work if you are advising it. Just to confirm it once if I get successful then I would be able to update it with custom ROM as you mentioned.
Click to expand...
Click to collapse
Yeah try the MDL firmware in ODIN. Only the MDB and MDL firmware can use a custom ROM with loki doki. Don't flash any other firmware or else you won't be able to use loki doki and will be forced to use safe strap recovery instead of TWRP which can only boot custom Samsung ROM.
StoneyJSG said:
Yeah try the MDL firmware in ODIN. Only the MDB and MDL firmware can use a custom ROM with loki doki. Don't flash any other firmware or else you won't be able to use loki doki and will be forced to use safe strap recovery instead of TWRP which can only boot custom Samsung ROM.
Click to expand...
Click to collapse
@StoneyJSG, Really appreciate your quick responses and the value of this forum. I had been gone in a complete frustration from past one week but now I am having hope to get the phone working. Trying to download I337UCUAMDL and flash it through ODIN ? Thank You! so much once again.
Does the phone say anything about Knox in the download screen where you see the model #?
The phone is definitely the sgh-i337 on the download screen?
mahendra_bhawsar said:
@StoneyJSG, Really appreciate your quick responses and the value of this forum. I had been gone in a complete frustration from past one week but now I am having hope to get the phone working. Trying to download I337UCUAMDL and flash it through ODIN ? Thank You! so much once again.
Click to expand...
Click to collapse
I downloaded I337UCUAMDL firmware from http://stockroms.net/file/GalaxyS4/SGH-I337/I337UCUAMDL_I337ATTAMDL_ATT.zip but when I flesh it using ODIN it says FAIL(!Auth). Here is the ODIN Log: <ID:0/004> Added!!
<ID:0/004> Removed!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<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> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Please help me what should I do in this case.
audit13 said:
Does the phone say anything about Knox in the download screen where you see the model #?
The phone is definitely the sgh-i337 on the download screen?
Click to expand...
Click to collapse
Nope, It does not say anything about Knox in the download screen. I see model number(SGH-I337) on the hardware underneath the battery.
Thank You!
The aboot.mbn file is not flashing because the bootloader in the phone is newer than the bootloader in the rom, the bootloader is not meant for the phone, or you need to use a different usb cable or usb port.
audit13 said:
The aboot.mbn file is not flashing because the bootloader in the phone is newer than the bootloader in the rom, the bootloader is not meant for the phone, or you need to use a different usb cable or usb port.
Click to expand...
Click to collapse
I think I have purchased this cell phone back in Sept 2013, that time I believe AT&T had the following versions:
Build Date: 27.04.2013 -> Region: ATT (AT&T) PDA: I337UCUAMDL Changelist: 453947 Android: 4.2.2
Build Date: 09.04.2013 -> Region: ATT (AT&T) PDA: I337UCUAMDB Changelist: 440216 Android: 4.2.2
I tried both of them using both the ports of my laptop with different USB Cables(Original cable from Sony, Samsung and Moto G), but every time I got the same Odin Fail (!Auth) error. I am not sure whats the wrong here or what should I do to resolve this error and get the phone working.
Thank You!
What version of android was on the phone when you bought it?
Do you see anything about warranty bit in download mode?
audit13 said:
What version of android was on the phone when you bought it?
Do you see anything about warranty bit in download mode?
Click to expand...
Click to collapse
I think it was Android 4.2.2, this is what the download mode says:
ODIN MODE
PRODUCT NAME: SGH-I337
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Official
KNOX KERNAL LOCK: 0*0
KNOX WARRANTY VOID: 0*0
CSB-CONFIG-LSB: 0*30
WRITE PROTECTION: Enable
eMMC BURST MODE enabled
Thank You!
The fact that you see "Knox" on the screen indicates this:
1) the phone has a locked bootloader;
2) you cannot flash any stock rom that is older than 4.3. If you try, Odin will not flash the aboot.mbn file which is an old bootloader; and
3) the phone must have been running at least a 4.3 or newer rom.
audit13 said:
The fact that you see "Knox" on the screen indicates this:
1) the phone has a locked bootloader;
2) you cannot flash any stock rom that is older than 4.3. If you try, Odin will not flash the aboot.mbn file which is an old bootloader; and
3) the phone must have been running at least a 4.3 or newer rom.
Click to expand...
Click to collapse
Ohh I understand this now. But knox says 0*0 bit still it means it has a locked bootloader ? I think may be it was running on 4.3 before it crashed, may be I had got some update on 4.2.2 and that made it got updated on 4.3 which I didn't re-collect. What should I do now, which ROM you would suggest me to flash it with. Really appreciate your help.
Thank You!
If the was never updated to 4.3 or newer, you would not see the word "Knox" in download mode.
This may help: https://forum.xda-developers.com/showthread.php?t=2616221
audit13 said:
If the was never updated to 4.3 or newer, you would not see the word "Knox" in download mode.
This may help: https://forum.xda-developers.com/showthread.php?t=2616221
Click to expand...
Click to collapse
It has lots of ROMS and instructions to follow, I am a novice user in this so got confused what to do and what not. Even I don't know my current baseband version so unable to choose firmware or method to flash it in order to get it working. Any help from your side on this front ?
Thank You!
You could try this: https://forum.xda-developers.com/galaxy-s4-att/development/rom-100-stock-i337oc3-5-0-mdl-t3098197
audit13 said:
You could try this: https://forum.xda-developers.com/galaxy-s4-att/development/rom-100-stock-i337oc3-5-0-mdl-t3098197
Click to expand...
Click to collapse
My phone is in hanging state on boot loop won't be able to perform the steps mentioned on that link like : 1. Place the ROM onto your device (use either internal or ext-sdcard). etc... Any other suggestion please ?
You could downloading this file and flashing it with Odin: https://androidfilehost.com/?fid=23501681358540571
I found the link by googling around. I can't try the file because I don't the i337, I only have the i337m.
audit13 said:
You could downloading this file and flashing it with Odin: https://androidfilehost.com/?fid=23501681358540571
I found the link by googling around. I can't try the file because I don't the i337, I only have the i337m.
Click to expand...
Click to collapse
Great! Thanks I am trying to download it, it will take time since my network is a bit slow, will let you know if that works, hopefully it should.

Categories

Resources