Hi guys,
I rooted my GS4 (SGH-I337 running 4.4.4) but wanted to update it but was receiving an error that said "install interrupted". I then used flashify to flash back to stock firmware that i downloaded from SamMobile. However, after I rebooted the phone, it became stuck on the ATT logo screen. I have tried to use Odin but I get a fail message. Here are the logs:
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<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> 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)
Here is what the phone says on Odin Mode:
Product name: SGH-I337
Current Binary: Samsung Official
System Status: Custom
KNOX Kernel Lock: 0x0
KNOX Warranty VOID: 0x0
CSB-CONFIG-LSB: 0x30
Write Protection: Enable
emMMC Burst MODE enabled
START [224,1440]
SW REV. CHECK FAIL : FUSED : 5 Binary : 1
I have tried Odin v3.10.6, 3.09, 1.85, 3.07, and 3.04 with the same result. I read in some forums that using a pit file would help, but I receive a fail message using it saying, "Re-partition operation failed".
I have also tried wiping cache partition and factory reset through recovery mode with no success.
Any help would be appreciated, thanks in advance!
-Daniel
bump
Odin stops at aboot.mbn because the rom you are flashing has a bootloader that is older than the bootloader on the phone.
audit13 said:
Odin stops at aboot.mbn because the rom you are flashing has a bootloader that is older than the bootloader on the phone.
Click to expand...
Click to collapse
How can I find the appropriate rom?
Can you boot into stock recovery? I think the second line will give you the recovery version which will give you an idea as to the bootloader version.
audit13 said:
Can you boot into stock recovery? I think the second line will give you the recovery version which will give you an idea as to the bootloader version.
Click to expand...
Click to collapse
Thanks, I will try that.
audit13 said:
Can you boot into stock recovery? I think the second line will give you the recovery version which will give you an idea as to the bootloader version.
Click to expand...
Click to collapse
Ok so i booted into recovery mode, this is what it says:
Android system recovery<3e>
KTU84P.I3377UCUFNJ5
This may help: http://forum.xda-developers.com/showthread.php?t=2616221
It worked!! Thanks so much man, you're awesome.
Thanks for letting us know it worked
Related
Hello,
-sorry for my english I dont speak well but...
phone: I9505
I was testing cyanogemod 10.1.3 for a while but then I decided get back to stock rom, did full wipe and put this ROM I9505XXUBMF8 into Odin and start flashing but he said this:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUBMF8_I9505OXABMF8_I9505XXUBMF8_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> SingleDownload.
<ID:0/003> sbl2.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
-then I couldnt go to system, recovery just to download mode so I flashed TWRP.
(I tried another stock rom, odin, PC but always same problem.)
-then i tried get back CM 10.1.3 via TWRP and it flashed and work without problem.
-then I tried flash omega rom via TWRP and it flashed without problem but booting is very slow and during the logo Samsung it takes about 10mins to boot into system and device is very hot.
-Everything about Kies and antivirus is off.
-Using just original USB cable.
-what says download mode:
ODIN MODE
PRODUCT NAME: gt-i9505
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
KNOX KERNEL LOCK: 0X0
KNOX WARRANTY VOID: 0X1
CSB-CONFIG-LSB: 0X30
WRITE PROTECTION: ENABLED
START [224, 1440]
SW REV, CHECK FAIL : FUSED : 2 , BINARY : 1
Any ideas how to resolve this?
Thank you
you have a secured bootloader, you can not flash old firmwares, flash MH8
use search button, there is a lot of threads talking about this issue
samersh72 said:
you have a secured bootloader, you can not flash old firmwares, flash MH8
use search button, there is a lot of threads talking about this issue
Click to expand...
Click to collapse
Thank you so much, I was looking for something all day but i didnt sure what Im really looking for
ODIN MODE
Product Name GT-I9505
CURRENT BINARY:
SYSTEM STATUS:
KNOX KERNEL LOCK: 0XFFFFFFFFFC
KNOW WARRANTY VOID: 0XFFFFFFFFC
CSB_CONFIG_LSB: 0X30
Write protection: Enabled
eMMC Burst: Enabled
Set Warranty bit: cACHED
Set Warranty bit: Hidden!
Firmware update encountered an issues, Please select recover mode in kies and try again.
Above is what my phone is currently showing me, Odin seems to flash philz/twrp however I can't boot into recovery.
I can still get into download mode tho
So I thought sod my root and everything, I just really need a phone and alarm clock so I downloaded the latest firmware for this phone (I9505XXUEMJ7) and attempted to flash as PDA in odin and got the follwoing response:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUEMJ7_I9505BTUEMJ8 _I9505XXUEMJ7_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Added!!
<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> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> sbl2.mbn
<ID:0/004> sbl3.mbn
<ID:0/004> rpm.mbn
<ID:0/004> aboot.mbn
<ID:0/004> tz.mbn
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have also tried the original firmware that came with the phone (XXUMBGA 4.2 UK Not locked) and many others, Still getting nothing, Just seems odin won't let me flash anything.
When philz or clockwork did run a few days ago, I could not install any zip files, It just kept giving me an error saying it can't mount /cahce or /system and the file is bad, despite me checking the MD5's and re downloading server times!
Can anyone make any suggestions? Or do I just have a new paper weight?
Thanks guys!
Nevermind, Got it back to factory setting using KIES
I highly recommend it but remember it will KNOX the device
Peace
philipkroberts said:
Nevermind, Got it back to factory setting using KIES
I highly recommend it but remember it will KNOX the device
Peace
Click to expand...
Click to collapse
What does Knox mean? I am having the same issues where odin just hangs on boot.img, my last resort will be using kies.
Can I not flash any roms after I restore using kies??
gunner05 said:
What does Knox mean? I am having the same issues where odin just hangs on boot.img, my last resort will be using kies.
Can I not flash any roms after I restore using kies??
Click to expand...
Click to collapse
If you use KIES to upgrade your phone you will get the latest firmware which contains the knox bootloader: http://forum.xda-developers.com/showthread.php?t=2447832
In that thread it says what knox is and what it means for us. But yeah, you can still flash ROMs, but you will trigger the knox warranty void flag (info is in the thread).
Can you tell me what you have done to fix it with Kies, please?
I tried to root my i9505 today and it stopped after 3 seconds when I used Odin to flash CF-Auto-Root.
And now since 7 hours I can't fix it. Kies won't recognize my smartphone and Odin always response with "Fail!".
I'm really desperate that I bricked my phone. :crying:
TStorm16 said:
Can you tell me what you have done to fix it with Kies, please?
I tried to root my i9505 today and it stopped after 3 seconds when I used Odin to flash CF-Auto-Root.
And now since 7 hours I can't fix it. Kies won't recognize my smartphone and Odin always response with "Fail!".
I'm really desperate that I bricked my phone. :crying:
Click to expand...
Click to collapse
That's almost impossible with CF-root or you yourself messed up real bad.
Try a different usb port, different cable, make sure Kies is not running, reinstall drivers.
Lennyz1988 said:
That's almost impossible with CF-root or you yourself messed up real bad.
Try a different usb port, different cable, make sure Kies is not running, reinstall drivers.
Click to expand...
Click to collapse
OMG!
I just fixed it. I flashed this PIT-File "CSB_signed_Fusion3_EUR_0325_V2.pit" and after that my smartphone rebooted normally.
Then when I was back I turned "USB-Debugging" on and went back to recovery mode and tried it again.
And now it works.:good:
Ok this is what my phone says when I try to unbrick it using any/all versons of Odin:
Odin mode
PRODUCT NAME: SM-N9005
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
REACTIVATION LOCK: OFF
KNOX KERNEL LOCK: 0X0
KNOX WARRANTY VOID: 0X1
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S2, T2, R2, A2, P2
WRITE PROTECTION: ENABLE
ODIN : INVALID EXT4 IMAGE
These are a list of files I've tried using to unbrick it with the same result shown above in failure:
N9005XXUDMJ7_N9005SFRDMJ4_N9005XXUDMJ7_HOME.tar
N9005XXUDMJ7-PRE-ROOTED-KNOX-FREE-ODEX-BL-FREE.tar.md5
I have used a total of 5 different regions firmwares to try to unbrick device to no avail.
Oden says this when trying to unbrick:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUDMJ7_N9005SFRDMJ4_N9005XXUDMJ7_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> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> aboot.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any help would be appreciated.
Noxious123 said:
Ok this is what my phone says when I try to unbrick it using any/all versons of Odin:
Odin mode
PRODUCT NAME: SM-N9005
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
REACTIVATION LOCK: OFF
KNOX KERNEL LOCK: 0X0
KNOX WARRANTY VOID: 0X1
QUALCOMM SECUREBOOT: ENABLE (CSB)
AP SWREV: S2, T2, R2, A2, P2
WRITE PROTECTION: ENABLE
ODIN : INVALID EXT4 IMAGE
These are a list of files I've tried using to unbrick it with the same result shown above in failure:
N9005XXUDMJ7_N9005SFRDMJ4_N9005XXUDMJ7_HOME.tar
N9005XXUDMJ7-PRE-ROOTED-KNOX-FREE-ODEX-BL-FREE.tar.md5
I have used a total of 5 different regions firmwares to try to unbrick device to no avail.
Oden says this when trying to unbrick:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUDMJ7_N9005SFRDMJ4_N9005XXUDMJ7_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> sbl1.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> aboot.mbn
<ID:0/004> rpm.mbn
<ID:0/004> tz.mbn
<ID:0/004> sdi.mbn
<ID:0/004> NON-HLOS.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img.ext4
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any help would be appreciated.
Click to expand...
Click to collapse
flash this rom it fixes all most anything got me out of trouble http://forum.xda-developers.com/showthread.php?t=2461929
jaythenut said:
flash this rom it fixes all most anything got me out of trouble http://forum.xda-developers.com/showthread.php?t=2461929
Click to expand...
Click to collapse
Hahah jay, always the same answer and they all love it
I ppl would search the forum a lil bit, u wouldnt hav to copy and paste it all day
hit 'thanks' if i helped you
SM-N9005 DBT-DMJ7 0x0
XDA Developers 4 premium app
Tried this
I think I tried this before but and it didn't work but I'll give it another go. So which files do I use can you give me the exact links please?
Like I said doesn't work
jaythenut said:
flash this rom it fixes all most anything got me out of trouble http://forum.xda-developers.com/showthread.php?t=2461929
Click to expand...
Click to collapse
I tried this link: http://www.hotfile.com/dl/255972464/4ceccee/N9005XXUDMJ7_N9005OXXDMJ4_TPH.zip.html
but it doesn't work I was fairly sure I'd tried this before. So unless its a specific link that you can give me I don't know what else to try.
Flash via recovery
Since you are 0x1 flash a recovery from here
http://forum.xda-developers.com/showthread.php?t=2454079
And then grab a clean rom from here
http://forum.xda-developers.com/showthread.php?t=2461929
for your device and flash it through recovery
ceidvi the
vit0r94 said:
Since you are 0x1 flash a recovery from here
http://forum.xda-developers.com/showthread.php?t=2454079
And then grab a clean rom from here
http://forum.xda-developers.com/showthread.php?t=2461929
for your device and flash it through recovery
Click to expand...
Click to collapse
I flashed the recovery and tried to install one of the zip flashes from here "SM-N9005 Official Stock ROM's for Odin (KNOX 0x1):" every time I try a different one it says:
e: signature verification failed:
crying:
still lindnni
Noxious123 said:
I flashed the recovery and tried to install one of the zip flashes from here "SM-N9005 Official Stock ROM's for Odin (KNOX 0x1):" every time I try a different one it says:
e: signature verification failed:
crying:
Click to expand...
Click to collapse
I've tried three different firmwares none work. I'm beginning to think this is impossible to fix unless you hand-feed me the direct links to the files that you believe will work I don't see this ever being resolved.
I don't have 9005 but should Write protection be enabled?
My suggestion
Uninstall KIES, try one of them Taiwan (http://terafile.co/5f6709f06654) or HongKong (http://terafile.co/80799e847756) firmwares as a last ditch option.
As i said, 'Last Ditch'. I mean if you have nothing else to try...
vit0r94 said:
Since you are 0x1 flash a recovery from here
http://forum.xda-developers.com/showthread.php?t=2454079
And then grab a clean rom from here
http://forum.xda-developers.com/showthread.php?t=2461929
for your device and flash it through recovery
Click to expand...
Click to collapse
These two links worked thank you for putting me on the right track but next time could you give me direct links and/or some explaination:
http://d-h.st/users/xiaolu/?fld_id=28640
http://www.androidfilehost.com/?fid=23203820527945403
Thanks again,
Nox.
Noxious123 said:
These two links worked thank you for putting me on the right track but next time could you give me direct links and/or some explaination:
http://d-h.st/users/xiaolu/?fld_id=28640
http://www.androidfilehost.com/?fid=23203820527945403
Thanks again,
Nox.
Click to expand...
Click to collapse
Actually it installed but when I restart the phone is stuck on the Samsung Boot Loader?
Noxious123 said:
These two links worked thank you for putting me on the right track but next time could you give me direct links and/or some explaination:
http://d-h.st/users/xiaolu/?fld_id=28640
http://www.androidfilehost.com/?fid=23203820527945403
Thanks again,
Nox.
Click to expand...
Click to collapse
FFS I think I might just chuck the phone at the wall I've seen tons of youtube videos where people do it and it works in one go and I've read thousands of forums that say this is tried tested and works but they don't ****ING work!!!
This is a link to the video of my phone with it not working:
http://www.youtube.com/watch?v=4-9doZTXbDM
stanley08 said:
I don't have 9005 but should Write protection be enabled?
My suggestion
Uninstall KIES, try one of them Taiwan (http://terafile.co/5f6709f06654) or HongKong (http://terafile.co/80799e847756) firmwares as a last ditch option.
As i said, 'Last Ditch'. I mean if you have nothing else to try...
Click to expand...
Click to collapse
This worked. Thank you very much.
Noxious123 said:
This worked. Thank you very much.
Click to expand...
Click to collapse
You are welcome mate, I'm really glad I could be of help mate.
stanley08 said:
You are welcome mate, I'm really glad I could be of help mate.
Click to expand...
Click to collapse
Just in the nick of time too I was going to chuck it all the wall if this didn't work.
Noxious123 said:
Just in the nick of time too I was going to chuck it all the wall if this didn't work.
Click to expand...
Click to collapse
Haha! Dat happens! And yh, dats why I said 'Last Gasp' attempt. I was almost certain it would work tho.
And btw, learn to hit the 'THANKS' button whenever you get a reply, any reply! It shows appreciation. Cheers!
Unroot problems
stanley08 said:
Haha! Dat happens! And yh, dats why I said 'Last Gasp' attempt. I was almost certain it would work tho.
And btw, learn to hit the 'THANKS' button whenever you get a reply, any reply! It shows appreciation. Cheers!
Click to expand...
Click to collapse
Hey I want to update to KitKat 4.4.2 but it wont let me update using the rom provided by Sammobile.com. When I tried to unroot with the Taiwan firmware it says the binary is locked or something like that any suggestions?
<ID:0/004> system.img.ext4
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
This means you gave probably 16GB instead of 32GB
Hello everyone,
sorry for my english I'm french, I had a concern during an update of a custom rom, and since I no longer access the recovery (recovery bootloop) and when I want to put a stock rom j 'have this error message:
SW REV CHECK FAIL : [aboot] Fused 3 > Binary 2
warhacke said:
Hello everyone,
sorry for my english I'm french, I had a concern during an update of a custom rom, and since I no longer access the recovery (recovery bootloop) and when I want to put a stock rom j 'have this error message:
SW REV CHECK FAIL : [aboot] Fused 3 > Binary 2
Click to expand...
Click to collapse
ODIN SAY :
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUDMK2_N9005OXXDMK3_N9005XXUDMJ7_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> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> aboot.mbn
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
My Phone SAY
ODIN MODE
Product-Name : SM-9005
Current Binary : Custom
System Status: Custom
Reactivation Lock: OFF
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY: 0x1
QUALCOMM SECURBOOT: Enable (CSB)
RP SWREV: S2, T2, A3, P2
WRITE PROTECTION: ENABLE
UDC START
Error on aboot.mbn, the bootloader. This arrive when we want flash a oldest bootloader then that we have already installed.
If You flash now a Costumer Recovery the Rom installed start and work. This arrived to me also.
See whit Shell Terminal Emulator, type getprop ro.bootloader and You see what is installed. You can't downgrade from it.
ValenteL said:
Error on aboot.mbn, the bootloader. This arrive when we want flash a oldest bootloader then that we have already installed.
If You flash now a Costumer Recovery the Rom installed start and work. This arrived to me also.
See whit Shell Terminal Emulator, type getprop ro.bootloader and You see what is installed. You can't downgrade from it.
Click to expand...
Click to collapse
Thx,
The Shell terminal Emulator, have you link for download ? it's for windows ?
warhacke said:
Thx,
The Shell terminal Emulator, have you link for download ? it's for windows ?
Click to expand...
Click to collapse
Is for Android, on Play Store. To see this on Note 3 (if it work).
Thanks
ValenteL said:
Error on aboot.mbn, the bootloader. This arrive when we want flash a oldest bootloader then that we have already installed.
If You flash now a Costumer Recovery the Rom installed start and work. This arrived to me also.
See whit Shell Terminal Emulator, type getprop ro.bootloader and You see what is installed. You can't downgrade from it.
Click to expand...
Click to collapse
Thanks for your support.
the shell emulator has to be run on the phone? because i can't even start my phone anymore because i tried to flash a custom recovery
jt_04 said:
the shell emulator has to be run on the phone? because i can't even start my phone anymore because i tried to flash a custom recovery
Click to expand...
Click to collapse
Seems it is. Make sure you flash correct recovery for your phone/android version.
Sent from my SM-G925F
Can you still boot into download mode? If you can, flash TWRP using Odin 3.07.
So my phone got stolen and when i got it back i couldn't get in to it. So i tried to flash stock firmware with odin and here is the error i got in odin and the error the phone had. I would be greatful for any advice.
<ID:0/013> Added!!
<ID:0/013> Odin engine v(ID:3.1203)..
<ID:0/013> File analysis..
<ID:0/013> skip file list for home binary
<ID:0/013> persist.img.ext4
<ID:0/013> userdata.img.ext4
<ID:0/013> Home Binary Download
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Get PIT for mapping..
<ID:0/013> Firmware update start..
<ID:0/013> SingleDownload.
<ID:0/013> emmc_appsboot.mbn
<ID:0/013> lksecapp.mbn
<ID:0/013> FAIL! (Auth)
<ID:0/013>
<ID:0/013> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Here is what phone said
SYSTEM STATUS: Custom
FRP LOCKN
WARRANTY VOID:0X0
sw rev check fail (aboot) fused 3 binary 2
The flash appears to be failing because of the FRP (factory reset protection) lock. The phone is an n9005?
frp lock
audit13 said:
The flash appears to be failing because of the FRP (factory reset protection) lock. The phone is an n9005?
Click to expand...
Click to collapse
No the phone is a SM-G935 t-mobile
Since the phone is not an n9005, not many people in this forum will b able to help because the n9005 doesn't have the frp option.
http://forum.xda-developers.com/tmobile-s7-edge
Hey guys,
I had succesfully rooted my device. a few weeks ago. because i wanted cyanogenmod rom on it i tried to flash CWM recovery menu.
now my device gives the following message:
firmware upgrade encountered an issue. please select recovery mode in kies and try again.
Now i tried to reflash the stock rom with odin.
i downloaded the stock rom for my area (i guess)
i also downloaded a europe .pit file (someone said that on a tutorial how to remove soft brick)
Tried flashing
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUFNA1_I9505OXAFNA1_I9505XXUFNA1_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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
I have an dutch galaxy s4. i have the provider T-mobile but the phone is not provider specified.
how can i fix this problem?
after trying with odin my downloading mode show's the following.
Odin mode
product name: GT-I9505
current binary: Custom
system status: Custom
knox kernel lock: 0x0
knox warranty void: 0x1
csb-config-lsb: 0x30
write protection: enable
emmc burst mode: enabled
start (224, 1440)
sw. rev. check fail : fused : 4 , binary : 3
what can i do to get my phone to start up normally, now i keep getting the firmware fault message.
Thanks in advance.
Edit: i cant open recovery mode. but i can open download mode.
VeryStealth said:
Hey guys,
I had succesfully rooted my device. a few weeks ago. because i wanted cyanogenmod rom on it i tried to flash CWM recovery menu.
now my device gives the following message:
firmware upgrade encountered an issue. please select recovery mode in kies and try again.
Now i tried to reflash the stock rom with odin.
i downloaded the stock rom for my area (i guess)
i also downloaded a europe .pit file (someone said that on a tutorial how to remove soft brick)
Tried flashing
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUFNA1_I9505OXAFNA1_I9505XXUFNA1_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> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
I have an dutch galaxy s4. i have the provider T-mobile but the phone is not provider specified.
how can i fix this problem?
after trying with odin my downloading mode show's the following.
Odin mode
product name: GT-I9505
current binary: Custom
system status: Custom
knox kernel lock: 0x0
knox warranty void: 0x1
csb-config-lsb: 0x30
write protection: enable
emmc burst mode: enabled
start (224, 1440)
sw. rev. check fail : fused : 4 , binary : 3
what can i do to get my phone to start up normally, now i keep getting the firmware fault message.
Thanks in advance.
Edit: i cant open recovery mode. but i can open download mode.
Click to expand...
Click to collapse
Try flashing a custom recovery through odin if u succeed u may have access to recovery nd if it doesnt work try flashing firmware without using pit file nd unchecking repartition option
Sent from my GT-I9500 using Tapatalk
---------- Post added at 10:56 PM ---------- Previous post was at 10:55 PM ----------
Which version is this which u r trying to flash via odin 4.3 or 4.4 2
Sent from my GT-I9500 using Tapatalk
aayushkhajuria2842 said:
Try flashing a custom recovery through odin if u succeed u may have access to recovery nd if it doesnt work try flashing firmware without using pit file nd unchecking repartition option
Sent from my GT-I9500 using Tapatalk
---------- Post added at 10:56 PM ---------- Previous post was at 10:55 PM ----------
Which version is this which u r trying to flash via odin 4.3 or 4.4 2
Sent from my GT-I9500 using Tapatalk
Click to expand...
Click to collapse
I thought it were a test version of 4.4.2 kitkat
though i now downloaded a netherlands version from this tread no idea wich version.
http://forum.xda-developers.com/showthread.php?t=2265477
and then the second one. also downloaded the .pit here. im gonna try it now.. youll hear in a few minutes
VeryStealth said:
I thought it were a test version of 4.4.2 kitkat
though i now downloaded a netherlands version from this tread no idea wich version.
http://forum.xda-developers.com/showthread.php?t=2265477
and then the second one. also downloaded the .pit here. im gonna try it now.. youll hear in a few minutes
Click to expand...
Click to collapse
I just want u 2 confirm it is 4.4.2 as u were trying to install cyanogenmod
Sent from my GT-I9500 using Tapatalk
aayushkhajuria2842 said:
I just want u 2 confirm it is 4.4.2 as u were trying to install cyanogenmod
Sent from my GT-I9500 using Tapatalk
Click to expand...
Click to collapse
leaked official version of 4.4.2
Why did i overlook that cyanogenmod recovery isnt compatible with 4.4.2 yet?
VeryStealth said:
leaked official version of 4.4.2
Why did i overlook that cyanogenmod recovery isnt compatible with 4.4.2 yet?
Click to expand...
Click to collapse
U can flash It if it is 4.4.2 ....nd I dont get your last line ???
Sent from my GT-I9500 using Tapatalk
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUEMKF_I9505PHNEMK5_I9505XXUEMKF_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/003> Added!!
<ID:0/003> Removed!!
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
following happend with the downloaded version of stock rom.
now trying with .pit file
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl1.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> aboot.mbn
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1
so i guess its not the pitt file?
is anything damaged? or do i have a faulty rom combo?
so your saying basicly that i should just try to reflash cyanogenmod? do you have a link to the version i can use. just to make sure i use the right one and don't screw it up more..
thanks for your help already btw.
I downloaded the newest CM i can find? CM 11-20140327? also i have the newest gapps i can find.. though its 20130813.
but how do i flash the recovery menu?
NVM i gave you a lot of false information< i had the firmware fault while installing clockworkmod recovery menu< not cyanogen< both with C im sorry.. i needed a recovery menu to install cyanogen. thats why i had problems.. i tried flashing to get the recovery menu and that failed. that gave the issues.. not cyanogen
Need to go puppy training with my dog< back in an hour or so
VeryStealth said:
so your saying basicly that i should just try to reflash cyanogenmod? do you have a link to the version i can use. just to make sure i use the right one and don't screw it up more..
thanks for your help already btw.
I downloaded the newest CM i can find? CM 11-20140327? also i have the newest gapps i can find.. though its 20130813.
but how do i flash the recovery menu?
NVM i gave you a lot of false information< i had the firmware fault while installing clockworkmod recovery menu< not cyanogen< both with C im sorry.. i needed a recovery menu to install cyanogen. thats why i had problems.. i tried flashing to get the recovery menu and that failed. that gave the issues.. not cyanogen
Need to go puppy training with my dog< back in an hour or so
Click to expand...
Click to collapse
Problem solved.. downloaded a new stock rom.. and used a 2.0 usb. I only have 3.0 stock an i could flash without problems on 3.0.. 2.0 were a first time hit.
Thanks again
VeryStealth said:
Problem solved.. downloaded a new stock rom.. and used a 2.0 usb. I only have 3.0 stock an i could flash without problems on 3.0.. 2.0 were a first time hit.
Thanks again
Click to expand...
Click to collapse
Glad u sovlved ur prblm bt from nxt tym read before flashing any custom rom u may hav flashed some wrong one
Sent from my GT-I9500 using Tapatalk