I managed not only brick one, but two SM-N9005, trying to do the Root de la Vega (yes, I used the right files).
After entering download mode, Odin failed after a short time (blue status bar was 2mm long).
Now the phone only says: Firmware upgrade encountered an issues. Please select recovery mode in Kies & try again.
But:
- Kies recovery fails
- I can't go into recovery mode, only download mode.
- Can't install stock ROM with Odin, fails as well.
- Can't CF-Auto-Root, Odin fails.
Note: Reactivation lock is OFF.
Any ideas?
k3000 said:
I managed not only brick one, but two SM-N9005, trying to do the Root de la Vega (yes, I used the right files).
After entering download mode, Odin failed after a short time (blue status bar was 2mm long).
Now the phone only says: Firmware upgrade encountered an issues. Please select recovery mode in Kies & try again.
But:
- Kies recovery fails
- I can't go into recovery mode, only download mode.
- Can't install stock ROM with Odin, fails as well.
- Can't CF-Auto-Root, Odin fails.
Note: Reactivation lock is OFF.
Any ideas?
Click to expand...
Click to collapse
try a different odin
jaythenut said:
try a different odin
Click to expand...
Click to collapse
Tried that, did not help. Thanks for the input. Used v1.85 mainly, though.
k3000 said:
Tried that, did not help. Thanks for the input. Used v1.85 mainly, though.
Click to expand...
Click to collapse
Try 3. what ever the number is i think it's better
jaythenut said:
Try 3. what ever the number is i think it's better
Click to expand...
Click to collapse
Odin3v185
That's the one I used.
k3000 said:
Odin3v185
That's the one I used.
Click to expand...
Click to collapse
No not that one v 3.07
jaythenut said:
No not that one v 3.07
Click to expand...
Click to collapse
Just tried it again with ODIN v3.07 and got the same error message in ODIN
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
This is getting really frustrating...
I tried different ODINs running on XP, Win 7 and Win 8.
I ran ODIN as Admin or Standard user and I used different USB ports and cables.
Nothing seems to help.
For example, trying to flash stock ROM gives me this error in ODIN:
<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> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
What's the error on the phone?
Example:
ODIN MODE
PRODUCTION NAME: SM-N9005
CURRENT BINARY: Samsung
SYSTEM STATUS: Official
REACTIVIATION LOCK: OFF
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
QUALCOM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1 T1 R1 A2 P1
WRITE PROTECTION: ENABLE.....
toker_X1 said:
What's the error on the phone?
Example:
ODIN MODE
PRODUCTION NAME: SM-N9005
CURRENT BINARY: Samsung
SYSTEM STATUS: Official
REACTIVIATION LOCK: OFF
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
QUALCOM SECUREBOOT: ENABLE (CSB)
RP SWREV: S1 T1 R1 A2 P1
WRITE PROTECTION: ENABLE.....
Click to expand...
Click to collapse
There is no error message on the display... that's exactly the text I see as well.
The only things that happens on the display the moment ODIN displays "FAIL", the blue progress bar freezes... I'd day it doesn't get further than 1-2%.
Normally there should be a red line with the error code/message.
All I can suggest is you try flashing stock rom using the several files (Kernel, PDA, CSC) method if you already havent done so already.
toker_X1 said:
Normally there should be a red line with the error code/message.
All I can suggest is you try flashing stock rom using the several files (Kernel, PDA, CSC) method if you already havent done so already.
Click to expand...
Click to collapse
Would you kindly be able to provide a link to the procedure you are referring to?
I have attached a picture of my bricked screen... I either see this one or the download screen.
k3000 said:
Would you kindly be able to provide a link to the procedure you are referring to?
I have attached a picture of my bricked screen... I either see this one or the download screen.
Click to expand...
Click to collapse
Why didn't you use ODIN 3.09 like guide here on XDA says?
Have you tried with that version?
k3000 said:
Would you kindly be able to provide a link to the procedure you are referring to?
I have attached a picture of my bricked screen... I either see this one or the download screen.
Click to expand...
Click to collapse
Thats not 'Download Mode', thats phone firmware recovery mode.
Can you get to 'Download Mode'? - ie. Green Andriod Robot screen? (Pull out the battery, Vol Down, Home and Power)
When I soft brinked my phone, I eventually got it working by doing this..
1) Boot into 'Download Mode'
2) Using Odin 3.09 flash Stock Kernel (my kernel file was 'KERNEL-BTU-N9005XXUBMJ3-1381515654.tar'), this enabled boot to 'Recovery Mode' where is was not working before.
3) Using Odin 3.09 flash CSC (my CSC file was 'N9005OXABMJ3_CSC.tar.md5')
4) Boot into 'Recovery Mode' and wipe all (System, Data, Cache etc..)
5) Using Odin 3.09 flash Stock Firmware (my file was 'N9005XXUBMJ3_N9005OXABMJ1_N9005XXUBMJ2_HOME.tar.md5') - this will fail.
6) Using Kies 3 Beta - Perform a 'Emergency Firmware Recovery', recovery code is required - this got be back to normal
Hope this helps.
toker_X1 said:
Thats not 'Download Mode', thats phone firmware recovery mode.
Can you get to 'Download Mode'? - ie. Green Andriod Robot screen? (Pull out the battery, Vol Down, Home and Power)
When I soft brinked my phone, I eventually got it working by doing this..
1) Boot into 'Download Mode'
2) Using Odin 3.09 flash Stock Kernel (my kernel file was 'KERNEL-BTU-N9005XXUBMJ3-1381515654.tar'), this enabled boot to 'Recovery Mode' where is was not working before.
3) Using Odin 3.09 flash CSC (my CSC file was 'N9005OXABMJ3_CSC.tar.md5')
4) Boot into 'Recovery Mode' and wipe all (System, Data, Cache etc..)
5) Using Odin 3.09 flash Stock Firmware (my file was 'N9005XXUBMJ3_N9005OXABMJ1_N9005XXUBMJ2_HOME.tar.md5') - this will fail.
6) Using Kies 3 Beta - Perform a 'Emergency Firmware Recovery', recovery code is required - this got be back to normal
Hope this helps.
Click to expand...
Click to collapse
Just tried... I get stuck at 2) again trying to flash the Kernel.
k3000 said:
Just tried... I get stuck at 2) again trying to flash the Kernel.
Click to expand...
Click to collapse
try stock firmware from www.samfirmwares.com with odin v3.09
k3000 said:
Just tried... I get stuck at 2) again trying to flash the Kernel.
Click to expand...
Click to collapse
Uhm, probably a dumb question, but did you use the CSC file as well? Didn't see that in the SS.
nabilsweet007 said:
try stock firmware from www.samfirmwares.com with odin v3.09
Click to expand...
Click to collapse
Unfortunately, no progress. Fails at the very same stage all where all my other efforts have failed, too.
Note: I am using the standard USB 3.0 cable which came with the Note 3. I have tried about 5 different USB 2.0 I have at home. Windows would not recognize a USB device being connected, but the Note 3 itself starts to charge the battery.
What was the csc of the phone before you tried the first flash?
Sent from my SM-N9005
SUCCESS!!
I went to the basement and dug out an old Win XP laptop, approx. 2002 vintage, which has not been used since probably 2005.
Plugged in my Note 3 with the USB 3.0 cable (of course at USB 1.0 speeds), re-ran Root de la Vega from scratch and voilĂ , it worked!
LESSON LEARNED: Do not use VMWARE FUSION/MAC to root. IT WILL BRICK YOUR PHONE.
Related
Ive been desperately trying to return to stock to unroot my phone for 2 days to no avail.
Holding the power button takes me to the Samsung bootloop.
I used Odin 1.85 to flash a HOME.tar.md5 file getting this message:
<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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
In download mode it says the following:
ODIN MODE
Product Name:GT-i19505
Current binary: Custom
System status: Custom
Knox Kernel lock: 0x0
Knox warranty void: 0x1
CSB-CONFIG-LSB: 0x30 (have no idea what this is)
Write protection: Enable
eMMC Burst mode: enabled
START [224, 1440]
Any ideas?
poninaine said:
Ive been desperately trying to return to stock to unroot my phone for 2 days to no avail.
Holding the power button takes me to the Samsung bootloop.
I used Odin 1.85 to flash a HOME.tar.md5 file getting this message:
<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> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
In download mode it says the following:
ODIN MODE
Product Name:GT-i19505
Current binary: Custom
System status: Custom
Knox Kernel lock: 0x0
Knox warranty void: 0x1
CSB-CONFIG-LSB: 0x30 (have no idea what this is)
Write protection: Enable
eMMC Burst mode: enabled
START [224, 1440]
Any ideas?
Click to expand...
Click to collapse
are you putting it in download mode
http://galaxys4root.com/galaxy-s4-tutorials/how-to-unroot-galaxy-s4-and-remove-root-completely/
jaythenut said:
are you putting it in download mode
http://galaxys4root.com/galaxy-s4-tutorials/how-to-unroot-galaxy-s4-and-remove-root-completely/
Click to expand...
Click to collapse
Yes, I specifically wrote down what it said on the top left side in download mode,too.
poninaine said:
Yes, I specifically wrote down what it said on the top left side in download mode,too.
Click to expand...
Click to collapse
Did you:
Use the cable that came with your device.
Use the usb ports in the back of your computer. Don't use a hub.
Try on a different computer.
Get firmware from sammobile.com
These are all things that you should check. Also, I've had Odin fail a number of times and the for whatever reason decide to work. It can be finicky.
jd1639 said:
Did you:
Use the cable that came with your device.
Use the usb ports in the back of your computer. Don't use a hub.
Try on a different computer.
Get firmware from sammobile.com
These are all things that you should check. Also, I've had Odin fail a number of times and the for whatever reason decide to work. It can be finicky.
Click to expand...
Click to collapse
I also found certain versions of Odin didn't work with some ROMS. When I tried using a 3.1x version of Odin to root my I9505G, it didn't setup properly, but using the 3.07 version did.
jd1639 said:
Did you:
Use the cable that came with your device.
Use the usb ports in the back of your computer. Don't use a hub.
Try on a different computer.
Get firmware from sammobile.com
These are all things that you should check. Also, I've had Odin fail a number of times and the for whatever reason decide to work. It can be finicky.
Click to expand...
Click to collapse
Yes I have tried all of those things. I also downloaded all the Odin versions and tried them. Unfortunately all of them failed. Is there any idea of what the failure in the original post means?
poninaine said:
Yes I have tried all of those things. I also downloaded all the Odin versions and tried them. Unfortunately all of them failed. Is there any idea of what the failure in the original post means?
Click to expand...
Click to collapse
In the last fail the box on the bottom left side said "Leave CS" what does this mean?
poninaine said:
Yes I have tried all of those things. I also downloaded all the Odin versions and tried them. Unfortunately all of them failed. Is there any idea of what the failure in the original post means?
Click to expand...
Click to collapse
Do you know what firmware you were on? And what country and carrier are you.
jd1639 said:
Do you know what firmware you were on? And what country and carrier are you.
Click to expand...
Click to collapse
You mean now or before the root? And my country is Estonia which has no stock .tar file anywhere on the internet. I read somewhere that you can just use a random countrys one and change the csc later so I decided to do that.
poninaine said:
You mean now or before the root? And my country is Estonia which has no stock .tar file anywhere on the internet. I read somewhere that you can just use a random countrys one and change the csc later so I decided to do that.
Click to expand...
Click to collapse
Yes, before root.
I even tried re-partition. Still failed instantly.
jd1639 said:
Yes, before root.
Click to expand...
Click to collapse
Before root I was on the stock Android 4.2.2. The first time I flashed anything it was the new leaked 4.3 which worked just fine.
Then I flashed CM 10.1 and it worked but the problems started when I wanted to get back to stock.
poninaine said:
I even tried re-partition. Still failed instantly.
Click to expand...
Click to collapse
I'm pretty sure it's the firmware version you're flashing that's the problem. If you know what it was before you rooted I'd look for the same version.
I have a similar problem
Hello there,
I have a similar problem but in odin it is a success but then i get stuck at boot.
To flash the file as a success, remove your device then flash again. By looking at your info, it says you have samsung knox which is a bummer (i'm in the same boat), you'll have to flash the same stock firmware as you did last time
Let me know how you get on mate
LimitedStreak said:
Hello there,
I have a similar problem but in odin it is a success but then i get stuck at boot.
To flash the file as a success, remove your device then flash again. By looking at your info, it says you have samsung knox which is a bummer (i'm in the same boat), you'll have to flash the same stock firmware as you did last time
Let me know how you get on mate
Click to expand...
Click to collapse
If Odin is successful but you get stuck at boot, do a factory reset in the stock recovery and it'll get you past the boot loop.
Would that delete my internal sd card folders etc?
---------- Post added at 10:12 PM ---------- Previous post was at 10:04 PM ----------
jd1639 said:
If Odin is successful but you get stuck at boot, do a factory reset in the stock recovery and it'll get you past the boot loop.
Click to expand...
Click to collapse
Would that delete my internal sd cards folders, prictures etc?
What if I flash another recovery then try wiping?
LimitedStreak said:
Hello there,
I have a similar problem but in odin it is a success but then i get stuck at boot.
To flash the file as a success, remove your device then flash again. By looking at your info, it says you have samsung knox which is a bummer (i'm in the same boat), you'll have to flash the same stock firmware as you did last time
Let me know how you get on mate
Click to expand...
Click to collapse
What do you mean I have Samsung Knox? I dont know how to find the same stock firmware as I dont know what I exactly need. As in if I need the exact same as it was when I bought it then I probably wont have no luck because my countrys csc firmware is nowhere for download.
I just realised - Im probably a huge idiot - I just checked the store site from where I bought my phone and it says the OS version is 4.2 not 4.2.2. Im going to try that but does every site only has 4.2.2!
My phone fall down on the ground from my pocket and after that its like dead cannot enter bootloader recovery except when i conect it to pc.
when i connect it to pc and i try to enter recovery i get message "recovery is not seandroid enforcing i9505" and phone is restarting. only thing i can do is entering download mode and thats all how can i fix this thank you.
ivanmadzarov said:
My phone fall down on the ground from my pocket and after that its like dead cannot enter bootloader recovery except when i conect it to pc.
when i connect it to pc and i try to enter recovery i get message "recovery is not seandroid enforcing i9505" and phone is restarting. only thing i can do is entering download mode and thats all how can i fix this thank you.
Click to expand...
Click to collapse
- Shutdown ur phone
- Press button Volume up + Home + Power. When see the white title "Samsung Galaxy GT-i9505" drop the Power button
- It will go to CUSTOM Recovery
Joku1981 said:
- Shutdown ur phone
- Press button Volume up + Home + Power. When see the white title "Samsung Galaxy GT-i9505" drop the Power button
- It will go to CUSTOM Recovery
Click to expand...
Click to collapse
i tried this already but its not wokring when i connect it to pc its starting but i get message recovery is not seandroid enforcing i9505 and device its turning off. i can enter in download mode same but volume down button but i dont know how can that help me what can i do to fix it please someone... thanks
ivanmadzarov said:
i tried this already but its not wokring when i connect it to pc its starting but i get message recovery is not seandroid enforcing i9505 and device its turning off. i can enter in download mode same but volume down button but i dont know how can that help me what can i do to fix it please someone... thanks
Click to expand...
Click to collapse
if you can enter download mode, flash stock files via odin see if that allows your phone to boot normally
andy1weir said:
if you can enter download mode, flash stock files via odin see if that allows your phone to boot normally
Click to expand...
Click to collapse
ok i noticed something now when i enter in download mod it says downloading on screen and in the korner i see this
odin mode
product mode: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 how can i use odin is this how i connect it to odin i have the program but how can i use it
ivanmadzarov said:
ok i noticed something now when i enter in download mod it says downloading on screen and in the korner i see this
odin mode
product mode: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 how can i use odin is this how i connect it to odin i have the program but how can i use it
Click to expand...
Click to collapse
you need to find the stock files for you device and flash via odin, theres plenty guides of how to use odin, once you have the files its pretty easy, what software was it running originally? 4.2.2? or 4.3?
andy1weir said:
you need to find the stock files for you device and flash via odin, theres plenty guides of how to use odin, once you have the files its pretty easy, what software was it running originally? 4.2.2? or 4.3?
Click to expand...
Click to collapse
originaly was running 4.2.2 i am trying to find for dubai or uae is it problem if i donwload a firmware from different region then this
i downloaded this firmware http://forum.xda-developers.com/showthread.php?t=2409867 and i extracted it and i put it in the pda in odin trying when i press start i see FAIL
<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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
what i did wrong
ivanmadzarov said:
i downloaded this firmware http://forum.xda-developers.com/showthread.php?t=2409867 and i extracted it and i put it in the pda in odin trying when i press start i see FAIL
<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> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
what i did wrong
Click to expand...
Click to collapse
hey there mate , your having a problem flashing that file because its a 4.2.2 rom and you already have a newbootloader which mean Not possible to downgrade when you have Knox Warranty Void. and you can check this threadto know more about KNOX, so Download and Flash a 4.3 base in your country and you should be fine.Have a nice day.
Edit: You can download a Official rom from here base from your country.
Repulsa said:
hey there mate , your having a problem flashing that file because its a 4.2.2 rom and you already have a newbootloader which mean Not possible to downgrade when you have Knox Warranty Void. and you can check this threadto know more about KNOX, so Download and Flash a 4.3 base in your country and you should be fine.Have a nice day.
Edit: You can download a Official rom from here base from your country.
Click to expand...
Click to collapse
i did same like you explained to me guys but its still not working same error
on the phone i can see this
start[224,1448]
sw rev, check fail: found :3, binary :1
Can anyone help me wake up my phone or atleast if someone have idea what the problem can or cannot be fixed
Hello guys... I was given a phone that I can keep and use if I fix it, but this phone is stuck on the open padlock/custom logo just stays there (if I try to go to recovery it says AT&T found unauthorized software). I fixed that by flashing stock NC1 Recovery but that only eliminated the unauthorized software message. I have read every thread and tried everything... Even flashed NC1 Modem and Kernel also since I found them... Only thing I have yet to try is flash a full I337UCUFNC1 via Odin but cant find it (At least not free). It seems this phone will only take NC1 stuff. Any help on getting the full I337UCUFNC1 Rom for Odin will be appreciated. I have the zip version but that does not work form DL mode...
More info:
Galaxy S4 i337
Binary: Official
System Status: Custom
Knox void: 0x1
CSB-Config-LSB: 0x30
Write protection: Enabled
eMMC Burst Mode: Enabled
You can Odin flash NB1. That will work even on NC1.
More info http://forum.xda-developers.com/showthread.php?t=2616221
Phone disconnects and reconnects by itself at about 98% of the process. Tried on 2 diff pc's. Going crazy... LOL.
Apexseal said:
Phone disconnects and reconnects by itself at about 98% of the process. Tried on 2 diff pc's. Going crazy... LOL.
Click to expand...
Click to collapse
Try a different cable and try different usb ports. Odin can be finicky
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Try a different cable and try different usb ports. Odin can be finicky
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Two brand new original cables, brand new usb/charging connector (Tried connector in another i337 and works fine), all usb ports tried on both pc's. It starts flashing then after a while I hear the usb disconnect and reconnect sound and Fail. I can flash nc1 modem, kernel and recovery all day without problems that gets me out of the Kies screen but no recovery either It gets stuck at the "Custom" logo with the "Recovery booting" on top left. if I flash a custom recovery i get the AT&T unauthorized software message. I'm writing this thread because I read and read and read and can't find a solution. Tried Odin 1.85, 3.07 and 3.09 all with same results. I was thinking maybe if I flash a full NC1 rom for Odin I can get it to work since all NC1 stuff flashes ok.
Apexseal said:
Two brand new original cables, brand new usb/charging connector (Tried connector in another i337 and works fine), all usb ports tried on both pc's. It starts flashing then after a while I hear the usb disconnect and reconnect sound and Fail. I can flash nc1 modem, kernel and recovery all day without problems that gets me out of the Kies screen but no recovery either It gets stuck at the "Custom" logo with the "Recovery booting" on top left. if I flash a custom recovery i get the AT&T unauthorized software message. I'm writing this thread because I read and read and read and can't find a solution. Tried Odin 1.85, 3.07 and 3.09 all with same results. I was thinking maybe if I flash a full NC1 rom for Odin I can get it to work since all NC1 stuff flashes ok.
Click to expand...
Click to collapse
There is no nc1 tar file. Nb1 should work. Try downloading it again
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
There is no nc1 tar file. Nb1 should work. Try downloading it again
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Downloaded from 3 diff places...
The only way I can get the progress bar to reach at least 98% is if I discharge the phone by briefly connecting the battery backwards (1-2 seconds). I have tried the NB1 file from different places all with the same result. Is there any way to convert the NC1 flash for TWRP recovery to .tar?
Apexseal said:
The only way I can get the progress bar to reach at least 98% is if I discharge the phone by briefly connecting the battery backwards (1-2 seconds). I have tried the NB1 file from different places all with the same result. Is there any way to convert the NC1 flash for TWRP recovery to .tar?
Click to expand...
Click to collapse
I think you have a hardware issue, bad emmc. You're doing everything right
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
I think you have a hardware issue, bad emmc. You're doing everything right
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Frustrating... Is there an unbrick sd card image for i337??? I'm willing to try anything now... I just dont care anymore... LOL
<OSM> Leave CS..
<ID:0/046> Odin v.3 engine (ID:46)..
<ID:0/046> File analysis..
<ID:0/046> SetupConnection..
<ID:0/046> Initialzation..
<ID:0/046> Set PIT file..
<ID:0/046> DO NOT TURN OFF TARGET!!
<ID:0/046> Get PIT for mapping..
<ID:0/046> Firmware update start..
<ID:0/046> SingleDownload.
<ID:0/046> sbl1.mbn
<ID:0/046> NAND Write Start!!
<ID:0/046> sbl2.mbn
<ID:0/046> sbl3.mbn
<ID:0/046> rpm.mbn
<ID:0/046> aboot.mbn
<ID:0/046> tz.mbn
<ID:0/046> boot.img
<ID:0/046> recovery.img
<ID:0/046> persdata.img.ext4
<ID:0/046> system.img.ext4
<ID:0/046> __XmitData_Write
<ID:0/046> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/046> Removed!!
<ID:0/046> Added!!
Ok... I was able to do a full flash "Pass" in Odin... BUT still stuck on Custom Logo. I Used JFLTE_USA_ATT_16G.pit and AP_I337UCUEMK2_1921628_REV06_user_low_ship_MULTI_C ERT.tar.md5. Recovery also not working.
179
Seems I can flash MK2 all day long but nothing... Stuck at Custom logo and no recovery... If emmc is bad would it do a full flash at all? Did 2 full flashes with MK2 but everything else that I try to flash fails...
MK2 still does not make it boot but... Any ideas why I can flash MK2 ROM and not NB1 ROM???
I extracted system.img.ext4 from NB1 rom then converted to .tar using cygwin, all the bars loaded in odin but right at the point where it is supposed to reboot it failed. Should I try flashing with z3x?
Hi,
I wouldn't normally post unless I really need help and I do, I've been at this for days, I'm stressing out because I really need my phone for work and I can't fix it myself...
My phone is stuck in a loop where every time I turn it off/on it goes straight into download mode.
It's doing this because I foolishly (without knowing what I was doing) used a .pit file I downloaded off of the internet.
I installed Clockworkmod 11 on my i9507 with the jfltexx i9505 rom.
It worked flawlessly except the 3G would drop out every time I locked the screen. Only 2G would work.
To try and fix it I downloaded a I9505DVUAMD8_MODEM.tar because I'm on Australia's 3G Telstra network through ALDI (medion) mobile.
The problem I had was that when I tried to flash the new modem, Odin would say that it failed.
So without knowing what I was doing, I used CSB_signed_Fusion3_TDD_0906_V2.pit
Now my phone is stuck in a loop where it goes straight into download mode.
Can someone please tell me how to fix this, I'm stressing out because all of my work is on this phone.
Please help, I'd really appreciate it.
Just flash a stock rom for the I9507 and you will be fine.
Lennyz1988 said:
Just flash a stock rom for the I9507 and you will be fine.
Click to expand...
Click to collapse
This is a really noob question but would you be able to save me a heap of time and link me to one please? My head is going to explode soon...
Edit:
I found this, which has the stock optus rom but it's an extremely slow (10 hour) 1.7gb download. I don't think this is right...
http://www.mrcrab.net/viewstockrom/30638-gt-i9507.html
alex8337 said:
This is a really noob question but would you be able to save me a heap of time and link me to one please? My head is going to explode soon...
Edit:
I found this, which has the stock optus rom but it's an extremely slow (10 hour) 1.7gb download. I don't think this is right...
http://www.mrcrab.net/viewstockrom/30638-gt-i9507.html
Click to expand...
Click to collapse
http://samsung-updates.com/details/41041/Galaxy_S4_TD-LTE/GT-I9507/OPS/I9507XXUFOA1.html
Neither mirror in that link works.
The download starts but doesn't actually download anything... It just sits at 0% with '10 hours left'.
Edit: Now it's jumped up to 22 hours left...
alex8337 said:
Neither mirror in that link works.
The download starts but doesn't actually download anything... It just sits at 0% with '10 hours left'.
Edit: Now it's jumped up to 22 hours left...
Click to expand...
Click to collapse
You can also try to reflash the recovery and then reflash the custom rom you were on. That should also work.
Lennyz1988 said:
You can also try to reflash the recovery and then reflash the custom rom you were on. That should also work.
Click to expand...
Click to collapse
Noob again... Sorry. How do I do that? Reflash the recovery I mean.
I really appreciate your help. At least I don't feel like I'm about to burst into tears anymore.
Edit: I've got recovery-clockwork-touch-6.0.4.7-jfltexx.img on my desktop, I just don't know how to use it with Odin.
alex8337 said:
Noob again... Sorry. How do I do that? Reflash the recovery I mean.
I really appreciate your help. At least I don't feel like I'm about to burst into tears anymore.
Edit: I've got recovery-clockwork-touch-6.0.4.7-jfltexx.img on my desktop, I just don't know how to use it with Odin.
Click to expand...
Click to collapse
Put it in AP/PDA (depends on the Odin version). Uncheck auto-reboot and flash it in download mode.
Lennyz1988 said:
You can also try to reflash the recovery and then reflash the custom rom you were on. That should also work.
Click to expand...
Click to collapse
I don't understand what you mean by 'reflash recovery'?
I downloaded clockworkmod touch 6.0.4.7 but its a .img file and I don't know how to use it with Odin.
So I continued with what you told me to do the first time.
Lennyz1988 said:
Put it in AP/PDA (depends on the Odin version). Uncheck auto-reboot and flash it in download mode.
Click to expand...
Click to collapse
I9507XXUFOA1_I9507OPSFOA1_I9507XXUFOA1_HOME.tar.md5 with Odin 3.09, AP.
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9507XXUFOA1_I9507OPSFOA1_I9507XXUFOA1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<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> sbl2.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> sbl3.mbn
<ID:0/005> rpm.mbn
<ID:0/005> aboot.mbn
<ID:0/005> tz.mbn
<ID:0/005> boot.img
<ID:0/005> recovery.img
<ID:0/005> system.img.ext4
<ID:0/005> FAIL! (Ext4)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I reset the phone a good 10min after and now it still boots into Odin mode but this is on the screen instead.
Odin mode
Product name: GT0i9507
Current binary: Samsung official
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]
ODIN : Invalid ext4 image
FIRMWARE UPGRADE ENCOUNTERED AN ISSSUE. PLEASE SELECT RECOVERY MODE IN KIES & TRY AGAIN.
You must flash the zip file,dont unpack the zip file,put the zip file in PA or PDA
ludoke said:
You must flash the zip file,dont unpack the zip file,put the zip file in PA or PDA
Click to expand...
Click to collapse
The zip file on its own doesn't show up when I click open in Odin though?
When I click AP/PDA and the Open box pops up, it doesn't show the zip file.
file name must be PDA File (*.tar, *.md5, *.smd, *.gz, *.tgz)
What am I supposed to do...
alex8337 said:
The zip file on its own doesn't show up when I click open in Odin though?
When I click AP/PDA and the Open box pops up, it doesn't show the zip file.
file name must be PDA File (*.tar, *.md5, *.smd, *.gz, *.tgz)
What am I supposed to do...
Click to expand...
Click to collapse
Open Odin ,connect your phone to pc via usb ,developers options enabled in ...settings ...about phone ..tap 6 or 7 times on build and enable usb ...foutopsporing in Dutch...also enable unknown sources .gO IN download mode ..search for how to do it. When phone is recognized in Odin
(If in the section ID COM is blue or yellow with a number it ,youre ready to go...
Tap on AP and it will ask for a file ...navigate on your pc to the location where you have stored the file,at first choose the Chainfire root file(,leave all the settings in Odin as the are) .it will appear in the AP section and hit Start ,wait until PASS appears in Odin...Disconnect phone from pc ,shut down Odin , Start the phone again in Download mode connect to pc and follow the same steps as with root,NOW UNCHECK automatic reboot in Odin,hit start and wait for Pass.
This should do the trick
---------- Post added at 01:10 PM ---------- Previous post was at 12:56 PM ----------
For root you need .tar file so unzip the zip file only once and flash that .tar file . For TWRP use the zip file,it contents the recovery.img NO need to unzip!!!
Sorry if i put you on the wrong leg.
I kept getting the same fail message in Odin.
I've fixed it now. I used Samsung Kies > Tools > Firmware upgrade and installation. It's taken the phone back to the stock Australian Optus rom. Not the original optus rom with baseband XXUAMH2 but a newer one running 4.2.2 with baseband XXUFOA1. Unfortunately I've lost all data on it but thankfully the phone still works. I was stressing out of my mind.
Thanks to everyone for helping, I appreciate your input
Hello,
i got a device to repair. I am not so familiar with samsung devices so i would apreciate some advice/help.
I dont know how to flash correctly the n9005 firmware.
I cant go to recovery and when try to boot there is shown on the screen "kernel is not seandroid enforcing, set warranty bit : kernel" and the device is rebooting to this text over and over.
It Is N9005 (is written under the battery).
But when i go to download mode it is listed this:
Code:
Odin Mode
product name: SM-N900P
Current Binary: Samsung Official
System Status: Official
Knox Kernel Lock: 0x0
Knox Warranty Void: 0x1
Qulcomm Secureboot: Enable (CSB)
RP SWREV: S1, T1, R1, A3, P1
Write Protection: Enable
I assume the owner accidentally flashed an n900P firmware to his n9005 device.
I tried many ODIN bversions (3.10.7,3.10.6,3.07,1.85) and stock 5.0, 4.4.2, 4.3 firmwares, various n9005 PIT files
when flashing a stock 4.4.2 firmware (only AP file from sammobile)
Code:
<ID:0/016> Get PIT for mapping..
<ID:0/016> Firmware update start..
<ID:0/016> SingleDownload.
<ID:0/016> sbl1.mbn
<ID:0/016> NAND Write Start!!
<ID:0/016> FAIL! (Auth)
when flashing a stock 5.0 firmware (only AP file from sammobile)
Code:
<ID:0/015> Firmware update start..
<ID:0/015> SingleDownload.
<ID:0/015> aboot.mbn
<ID:0/015> NAND Write Start!!
<ID:0/015> FAIL! (Auth)
when flashing a 4.4.? csc file for n9005
Code:
<ID:0/015> Odin engine v(ID:3.1100)..
<ID:0/015> File analysis..
<ID:0/015> SetupConnection..
<ID:0/015> Initialzation..
<ID:0/015> Set PIT file..
<ID:0/015> DO NOT TURN OFF TARGET!!
<ID:0/015> FAIL!
<ID:0/015>
<ID:0/015> Re-Partition operation failed]
closest i got with this:
in ODIN 3.07 when flashing kitkat csc file i got
Code:
<ID:0/015> Firmware update start..
<ID:0/015> cache.img.ext4
<ID:0/015> NAND Write Start!!
<ID:0/015> hidden.img.ext4
<ID:0/015> FAIL
and on the device was shown:
Code:
secure check fail : PIT
Set warranty bit : cache
Unsupport dev_type
nobody?
I make a step further.
Now i can flash system (AP) or i can flash twrp recovery or root trough ODIN, but i cant flash the whole stock, because it will fail everytime on sbl1.img, aboot or hidden.image.ext4
So now i can boot the system, but with N900P modem, kernel and othe rpartitions, so wifi dont work ect.
Now it would be superb to have a zip file with stock modem,sbl,aboot,non-hlos to flash it trough TWRP.
please any advice?
Sorry for my English!!
Download your region firmware from sammobile and pit file for your device n9005 note 3 open europ from xda.
Open odin select pit then the rom on itch specific place flash everything...
Let me know if you've got a positive result.
Sent from my SM-N910F using XDA-Developers mobile app
tried this dozen times. It gives me error when Odin tries to write the sbl1 or aboot or modem partition (as i wrote in OP). It gives error because the pit file doesn't match.
Is it possible the phone's motherboard was swapped for a 900p?
don't know... maybe. so you suggest to imstall stock N900P firmware?
https://mega.nz/#!kQtGnCYZ!7jko1XT7fPc9mIGHE8JLZhOvaeGH6qQbaW7Y6RYBQjU
This is a pit file for n9005 Europe
I advice you to reflash the rom of your original specific model with the pit file with wipe partition checked
Let me know wen u did
Sent from my SM-N910F using XDA-Developers mobile app
I will try. I avoided to wipe partitions while users say here on xda that it is a one way ride. ?
Samsung seems to have pretty good security measures in place to prevent flashing incorrect ROMs via Odin.
The failure to flash the 9005 aboot file tells me the bootloader on the rom and the bootloader in the phone do not match.
so how it can be, that i have an n9005 device with n900p Firmware and all partitions?
Does the imei in the phone match the imei on the printed label under the battery?
And why not your device would be a N900P ? Remove battery and see...
Maybe your USB is bad (it happened to me : 4 cables, 3 not working, 1 working hopefully)
Or maybe your downloaded ROM can't been flashed (weird, but it happened also to me), so flash the same model, but other revision (exemple OD3 doesn't work, try with OJ3, in my case)
Good luck !
use kies to install firmware. from kies select tools then "Emergency firmware recovey".
Munawar Mehmood said:
use kies to install firmware. from kies select tools then "Emergency firmware recovey".
Click to expand...
Click to collapse
the kies dont see my device.
cedric3 said:
And why not your device would be a N900P ? Remove battery and see...
Maybe your USB is bad (it happened to me : 4 cables, 3 not working, 1 working hopefully)
Or maybe your downloaded ROM can't been flashed (weird, but it happened also to me), so flash the same model, but other revision (exemple OD3 doesn't work, try with OJ3, in my case)
Good luck !
Click to expand...
Click to collapse
as i wrote under thebbattery is written n9005. usb is good use it to flash other phones. tried to flash about 4 stock roms.
DallasCZ said:
as I wrote, under the battery is written N9005. USB is good : I use it to flash other phones. I tried to flash about 4 stock roms.
Click to expand...
Click to collapse
Install Kies ot SmartSwitch (Kies' replacement)
Go to Emergency
Enter N9005 in device model
Enter the S/N number (written under the battery)
Connect your phone (don't worry if it is not recognized)
Go !
It will download the right update and install it : be patient, don't disconnect the phone or internet...
Good luck
jemis1983 said:
https://mega.nz/#!9BtkxK4A!Gy7muVwEtYBQFtxktDfCFK3VfcMZanfOMdOP9Elrm1U
This is a pit file for n9005 Europe
I advice you to reflash the rom of your original specific model with the pit file with wipe partition checked
Let me know wen u did
Sent from my SM-N910F using XDA-Developers mobile app
Click to expand...
Click to collapse
this is only a bat file to store the pit from the device.There is no pit file inside.
cedric3 said:
Install Kies ot SmartSwitch (Kies' replacement)
Go to Emergency
Enter N9005 in device model
Enter the S/N number (written under the battery)
Connect your phone (don't worry if it is not recognized)
Go !
It will download the right update and install it : be patient, don't disconnect the phone or internet...
Good luck
Click to expand...
Click to collapse
smart switch sys that my device dont support iniciation (after i added the sn number and mobile number.
DallasCZ said:
smart switch sys that my device dont support iniciation (after i added the sn number and mobile number.
Click to expand...
Click to collapse
Ok, and have you found the PIT file for your device ?
cedric3 said:
Ok, and have you found the PIT file for your device ?
Click to expand...
Click to collapse
I have the pit file for N9005 i flashed it using ODIN ..it was all ok
When i try to flash the AP image of stock (that cotains all parts BL,AP,CSC, CP) the flash ends by starting with flashing BL partitions sbl1.img)
When try to flash BL (bootloader) there is error in flashing sbl1.img.
the same goe with CSC and CP images (always show some error in flashing aboot.img and other partitions and ODIN stops.
I can flash AP (the AP that is only the system,recovery,boot) it goes well, the device starts but has some errors (because of missing parts in CSC and CP?.). wifi dont work i see full signal but there is no simcard inserted
Now i can boot the device the imei that is shown in the android systme is other than the imei on the back (under the battery).
I think someone tried to flash a N900P firmware over the N9005.
Now i cant flash the rest of the partitions.