Database Users

0[Q] [Help] (4.2.2 MDL i337 AT&T) Unknown IMEI Number + softbrick (SOLVED)

Hi,
I'm still a newb to the s4, so thanks for taking the time to look at my thread!
I got an S4 i337 from eBay. The phone booted up with the little custom and unlock graphic on the boot screen. The IMEI was reading all 0000... I tried to use QPST to see if restoring the .QCN from my other S4 i337 (also on 4.2.2 MDL) would help the IMEI issue. QPST gave me a "no phone" error when I tried to backup/restore on the new i337. I tried to root / reinstall recovery using CASUAL. It successfully rooted and installed TWRP but didn't help my QPST situation.
I had read that an incorrect or mis-flashed modem could be causing my problems so tried installing the MDL modem through ODIN 3.07. I tried to flash the modem.bin from through "phone" and got...
"<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)"
After that point I couldn't do anything with the phone so I unplugged the USB and did a battery pull to reboot. Since then I haven't been able to boot up the phone, nor boot into Recovery. It just sits on the samsung logo, or in the case of recovery goes to a black screen and then reboots to the samsung logo. I can still boot into download-mode.
I imagine the solution is simple to one of you pros, but I've been having trouble searching for it and clearly haven't done such a good job so far... any help is much appreciated!
Thanks XDA!

Are you sure your phone is on mdl firmware? If you are I would try to flash the mdl factory firmware with odin, not just the modem but the tar file.
Sent from my Nexus 5

jd1639 said:
Are you sure your phone is on mdl firmware? If you are I would try to flash the mdl factory firmware with odin, not just the modem but the tar file.
Click to expand...
Click to collapse
You're right I don't know what the previous owner did. I'll try that, thanks for the advice!

jd1639 said:
Are you sure your phone is on mdl firmware? If you are I would try to flash the mdl factory firmware with odin, not just the modem but the tar file.
Click to expand...
Click to collapse
Okay well I downloaded the firmware from Sammobile and followed their instructions...
http://www.sammobile.com/firmwares/3/?download=14623
This time Odin finished it's job...
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337UCUAMDL_I337ATTAMDL_I337UCUAMDL_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> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> modem.bin
<ID:0/003> NON-HLOS.bin
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
The phone is still unable to get past the startup screen
This one...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And if I try to boot it into recovery I get the "recovery booting..." but it then shuts off and (fails at) start up again...
Is it possible my recovery is damaged? If so is there a way to install it through Odin? Am I still able to somehow use ADB?
Thanks

Odin does flash the recovery. Keep trying to get into recovery. When you do do a factory reset. That'll get you past the boot loop. The boot loop is common, but you need to do the factory reset.
If you can't get in to recovery try flashing with odin again
Sent from my Nexus 5

jd1639 said:
Odin does flash the recovery. Keep trying to get into recovery. When you do do a factory reset. That'll get you past the boot loop. The boot loop is common, but you need to do the factory reset.
If you can't get in to recovery try flashing with odin again
Click to expand...
Click to collapse
Hey you're right, I didn't think I'd eventually get into recovery. I just kept holding down the "vol up" button, and after it failed to boot into recovery the first time it successfully did it the second time!
Ran factory reset, reboot phone... successful boot!
Now both my Baseband and IMEI are listed as unknown...
So I rooted this time using Motochopper (worked well for me on my other S4)
Ran RegionLock Away (as a crapshoot... someone reported it bringing back their lost imei...)... didn't help
Installed phoneutil.apk and ran QPST again. It still reports no phone connected on the the COM#s it was connected to.
So far softbrick has been fixed (Thank you SO much!), but now does anyone have any ideas regarding my IMEI number?

This might sound crazy, but I'd Odin again. It should bring your baseband and imei back unless something is really messed up.
Sent from my SAMSUNG-SGH-I727

jd1639 said:
This might sound crazy, but I'd Odin again. It should bring your baseband and imei back unless something is really messed up.
Click to expand...
Click to collapse
Reinstalled the same MDL firmware through ODIN, booted fine on first try but no fix to IMEI or Baseband. used CASUAL to install TWRP, and used TWRP to install the "modem_CWM_I337UCUAMDL.zip", followed by the "Modem_CWM_I337UCUAMDL_Unlock.zip". Neither seemed to help anything. Going to run the firmware install through Odin again, but I don't expect results.
(Edit: yea, no results)

I found this thread on the Galaxy S3 boards talking about efsv1 and efsv2 (came out July 2013) and efsv1 basebands can't read efsv2... is this at all relevant to the Galaxy S4?

Ziida said:
I found this thread on the Galaxy S3 boards talking about efsv1 and efsv2 (came out July 2013) and efsv1 basebands can't read efsv2... is this at all relevant to the Galaxy S4?
Click to expand...
Click to collapse
@rootSU do you know the answer to this? He's lost his imei and odining the stock firmware has not brought it back. I'm out of ideas. Thanx rootSU
Sent from my Nexus 5

Check this thread
http://forum.xda-developers.com/showthread.php?t=2370699

jd1639 said:
@rootSU do you know the answer to this? He's lost his imei and odining the stock firmware has not brought it back. I'm out of ideas. Thanx rootSU
Sent from my Nexus 5
Click to expand...
Click to collapse
I'll be honest, I do not know. I would assume that since Samsung released EFSv2, all subsequent devices were already EFSv2. Of course., these are just the names I have penned. They, in reality could have been EFSv46 and EFSv47. It could also be that each device undergoes these revisions of EFS, to fix bugs or improve service, but this is mere conjecture.
In short, I cannot answer as I have no direct experience of the device in question. Sorry.

jmjoyas said:
Check this thread
http://forum.xda-developers.com/showthread.php?t=2370699
Click to expand...
Click to collapse
Well... That thread worked in getting my imei from "null / null" to "0 / 00". It also made my phone recognized in QPST again! so I was able to install the AWS qcn file and that gave my phone a legitimately recognized IMEI number!
I need to thank everyone for all their help in this thread, the linked thread, and the AWS thread. Looks like I've got an IMEI number again!

[Q] Soft brick - Fail flashing Stock ROM at hidden.img Odin

Guys good morning.
I have rooted and successfully flashed custom recovery and custom firmwares on my Note 3 (9005 Qualcomm LTE), however the last flash (stock ROM 4.4.2 N9005XXUENB4) attempt with Odin (v 3) failed at the end of the flash process ( hidden.img.ext4 -> FAIL! (Size)):
Code:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENB4_N9005DBTENB1_N9005XXUENB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> sbl1.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> aboot.mbn
<ID:0/007> rpm.mbn
<ID:0/007> tz.mbn
<ID:0/007> sdi.mbn
<ID:0/007> NON-HLOS.bin
<ID:0/007> boot.img
<ID:0/007> recovery.img
<ID:0/007> system.img.ext4
<ID:0/007> modem.bin
<ID:0/007> cache.img.ext4
<ID:0/007> hidden.img.ext4
<ID:0/007> FAIL! (Size)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Now the phone won't boot anymore, it is stuck at the following screen (click to enlarge):
I cannot boot in recovery mode. What can I try?

RixNox said:
Guys good morning.
I have rooted and successfully flashed custom recovery and custom firmwares on my Note 3 (9005 Qualcomm LTE), however the last flash (stock ROM 4.4.2 N9005XXUENB4) attempt with Odin (v 3) failed at the end of the flash process ( hidden.img.ext4 -> FAIL! (Size)):
Code:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N9005XXUENB4_N9005DBTENB1_N9005XXUENB1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> sbl1.mbn
<ID:0/007> NAND Write Start!!
<ID:0/007> aboot.mbn
<ID:0/007> rpm.mbn
<ID:0/007> tz.mbn
<ID:0/007> sdi.mbn
<ID:0/007> NON-HLOS.bin
<ID:0/007> boot.img
<ID:0/007> recovery.img
<ID:0/007> system.img.ext4
<ID:0/007> modem.bin
<ID:0/007> cache.img.ext4
<ID:0/007> hidden.img.ext4
<ID:0/007> FAIL! (Size)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Now the phone won't boot anymore, it is stuck at the following screen (click to enlarge):
I cannot boot in recovery mode. What can I try?
Click to expand...
Click to collapse
You need to flash with this PIT file:
http://forum.xda-developers.com/showpost.php?p=50614669&postcount=77
Click PIT, select that file and tick Re-Partition in addition to the other stuff.

Wrathlon said:
You need to flash with this PIT file:
http://forum.xda-developers.com/showpost.php?p=50614669&postcount=77
Click PIT, select that file and tick Re-Partition in addition to the other stuff.
Click to expand...
Click to collapse
You mean I need to flash again the whole stock ROM + PIT & repartition using the suggested file?

RixNox said:
You mean I need to flash again the whole stock ROM + PIT & repartition using the suggested file?
Click to expand...
Click to collapse
Correct

Flashed successfully, however the Samsung logo kept glowing endlessly at startup, so I have removed the battery, booted in recovery mode and wiped cache and factory reset and YESSSSSSSSSSSS!!!!!!!!!!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You rule mate!!! Thanks a lot!!!!!!!!!!!

Thankfully Samsung have a secondary bootloader. The picture you displayed is secondary bootloader, if the flash fails there then you are looking at a brick, not a soft brick but a true paperweight...
You can also forget Kies, since the MJ3 bootloader Kies doesn't recognise the Note 3....

ultramag69 said:
Thankfully Samsung havce 2 bootloader modes, the picture you displayed is secondary bootloader, if the flash fails there then you are looking at a brick, not a soft brick but a true paperweight...
Click to expand...
Click to collapse
I recall once upon a time it was very easy to brick Samsung phones over Odin. Did things change lately? Are later firmwares/phones more foolproof than before as much as HTC are?

RixNox said:
I recall once upon a time it was very easy to brick Samsung phones over Odin. Did things change lately? Are later firmwares/phones more foolproof than before as much as HTC are?
Click to expand...
Click to collapse
Since the Samsung Galaxy S I can safely say it has a secondary bootloader, maybe before but I started on the Samsung galaxy tab7(1st edition) which was an enlarged Galaxy S. If you used Heimdall you'd see it has a file called SBL - secondary bootloader.
It gives you 2 chances to stuff up completely though if you do flash the wrong firmware - for different device - then you overwrite the secondary bootloader and essentially brick your device...

ultramag69 said:
Since the Samsung Galaxy S I can safely say it has a secondary bootloader, maybe before but I started on the Samsung galaxy tab7(1st edition) which was an enlarged Galaxy S. If you used Heimdall you'd see it has a file called SBL - secondary bootloader.
It gives you 2 chances to stuff up completely though if you do flash the wrong firmware - for different device - then you overwrite the secondary bootloader and essentially brick your device...
Click to expand...
Click to collapse
So what conditions can occur to brick the phone?
- damaged/wrong firmware?
- power failure while flashing?
- Or?

RixNox said:
So what conditions can occur to brick the phone?
- damaged/wrong firmware?
- power failure while flashing?
- Or?
Click to expand...
Click to collapse
All the above but if you have the pictured screen on the device you have a final chance to flash correctly... This really is the FINAL chance though, Screw up that flash and you've got a brick that won't turn on or charge...
I have a friends Gtab 7" to prove it. Short of replacing the MB there is no way to get it up and running....

ultramag69 said:
All the above but if you have the pictured screen on the device you have a final chance to flash correctly... This really is the FINAL chance though, Screw up that flash and you've got a brick that won't turn on or charge...
I have a friends Gtab 7" to prove it. Short of replacing the MB there is no way to get it up and running....
Click to expand...
Click to collapse
Very risky.... I wonder how they manage at Samsung OTA/Kies updates... are they any safer? Maybe it's a bad habit to download firmwares from other sites?

It's a standard risk when you flash a rom... This is why the MD5 checks are there, even from the best source you can get a corrupted file...
Also why the devs put the disclaimer that you are flashing your rom and they take no responsibility if it fails...

ultramag69 said:
It's a standard risk when you flash a rom... This is why the MD5 checks are there, even from the best source you can get a corrupted file...
Also why the devs put the disclaimer that you are flashing your rom and they take no responsibility if it fails...
Click to expand...
Click to collapse
The good thing is that an OTA or Kies flashing failure will be covered bi warranty, if any.
Any chance to get the bit 0x1 to 0x0 once "spoiled"? Flashing an original stock rom will not reset to 0...

Still Stuck
RixNox said:
Flashed successfully, however the Samsung logo kept glowing endlessly at startup, so I have removed the battery, booted in recovery mode and wiped cache and factory reset and YESSSSSSSSSSSS!!!!!!!!!!!
You rule mate!!! Thanks a lot!!!!!!!!!!!
Click to expand...
Click to collapse
Many thanks to Wrathlon as I was stuck in the same place! Now I'm stuck at the Samsung logo. I cannot boot into recovery mode to wipe cache and factory reset. Any suggestions?

RixNox said:
The good thing is that an OTA or Kies flashing failure will be covered bi warranty, if any.
Any chance to get the bit 0x1 to 0x0 once "spoiled"? Flashing an original stock rom will not reset to 0...
Click to expand...
Click to collapse
Nope... The bounty is over $3000 USD...

jebanec said:
Many thanks to Wrathlon as I was stuck in the same place! Now I'm stuck at the Samsung logo. I cannot boot into recovery mode to wipe cache and factory reset. Any suggestions?
Click to expand...
Click to collapse
As I wrote I got through removing the battery, booting in recovery mode, performed a wipe data (format) & wipe cache (2 steps in total)

RixNox said:
As I wrote I got through removing the battery, booting in recovery mode, performed a wipe data (format) & wipe cache (2 steps in total)
Click to expand...
Click to collapse
Please excuse my ignorance, but how are you actually booting into recovery? I'm on stock ROM and haven't rooted.

jebanec said:
Please excuse my ignorance, but how are you actually booting into recovery? I'm on stock ROM and haven't rooted.
Click to expand...
Click to collapse
Once you've turned off the phone, keep pressed at the same time (with following sequence)
1) Volume up
2) home
3) power
Keep the buttons pressed at the same time until the phone shows "booting recovery"
This should bring into recovery mode. navigate menus using volume up/down and use power button to confirm/enter. Perform both wipe data factory reset & wipe cache. Once done select reboot

RixNox said:
Once you've turned off the phone, keep pressed at the same time (with following sequence)
1) Volume up
2) home
3) power
Keep the buttons pressed at the same time until the phone shows "booting recovery"
This should bring into recovery mode. navigate menus using volume up/down and use power button to confirm/enter. Perform both wipe data factory reset & wipe cache. Once done select reboot
Click to expand...
Click to collapse
Many thanks. I tried this earlier but for some reason I couldn't get into recovery. I'll try again later to see if I can get it to work.

jebanec said:
Many thanks. I tried this earlier but for some reason I couldn't get into recovery. I'll try again later to see if I can get it to work.
Click to expand...
Click to collapse

Help special case to flash stock rom in s7 edge 935a

Hello every one, i am here to ask help for a special case, if is there someone with the knowlege in XDA to help mein this, i got a friend who has his s7 edge from at&t one day not working anymore it got stuck in boot loop, he never try to root or nothing he is a normal simple phone user. so now i am trying to help him but i dont know which firmware the phone had, i cant put developer options , the usb debugging nothing etc, i try to start in recovery mode but it get stuck in blue letters that say recover booting and never boot into recovery, the only thing the phone do now is get into download mode, and the pc recognize it and odin too, i have read every single thread i think to flash every single stock rom available and none has work i try diferent pc´s, cables, usb port, odin version etc. the most common error i got all times by odin was this one
ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<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> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
i am noob in this things i barely know a little readding all the threads i have put so much effort on this without success ,
can someone guide me please i will apreciate it

Darkboss10 said:
Hello every one, i am here to ask help for a special case, if is there someone with the knowlege in XDA to help mein this, i got a friend who has his s7 edge from at&t one day not working anymore it got stuck in boot loop, he never try to root or nothing he is a normal simple phone user. so now i am trying to help him but i dont know which firmware the phone had, i cant put developer options , the usb debugging nothing etc, i try to start in recovery mode but it get stuck in blue letters that say recover booting and never boot into recovery, the only thing the phone do now is get into download mode, and the pc recognize it and odin too, i have read every single thread i think to flash every single stock rom available and none has work i try diferent pc´s, cables, usb port, odin version etc. the most common error i got all times by odin was this one
ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<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> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
i am noob in this things i barely know a little readding all the threads i have put so much effort on this without success ,
can someone guide me please i will apreciate it
Click to expand...
Click to collapse
Remove PIT file and try again.
From Edge of Galaxy Seven

Darkboss10 said:
Hello every one, i am here to ask help for a special case, if is there someone with the knowlege in XDA to help mein this, i got a friend who has his s7 edge from at&t one day not working anymore it got stuck in boot loop, he never try to root or nothing he is a normal simple phone user. so now i am trying to help him but i dont know which firmware the phone had, i cant put developer options , the usb debugging nothing etc, i try to start in recovery mode but it get stuck in blue letters that say recover booting and never boot into recovery, the only thing the phone do now is get into download mode, and the pc recognize it and odin too, i have read every single thread i think to flash every single stock rom available and none has work i try diferent pc´s, cables, usb port, odin version etc. the most common error i got all times by odin was this one
ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<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> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
i am noob in this things i barely know a little readding all the threads i have put so much effort on this without success ,
can someone guide me please i will apreciate it
Click to expand...
Click to collapse
Not knowing WHAT you are flashing, makes it a little harder to determine what is going wrong.
Go HERE and flash this in Download Mode. This is the latest Stock 935A ROM, This will wipe Everything on the device, and it'll be like it came brand new

norbarb said:
Remove PIT file and try again.
From Edge of Galaxy Seven
Click to expand...
Click to collapse
which is the pit file, sorry for dumb question

Darkboss10 said:
which is the pit file, sorry for dumb question
Click to expand...
Click to collapse
If I remember correctly you need to uncheck PIT in odin and this should help. BTW. What are you trying to flash?
From Edge of Galaxy Seven

I have try the stock rom version 935a...pf2 . And any other stock rom i have found for the 935a seeing which will work .

Darkboss10 said:
I have try the stock rom version 935a...pf2 . And any other stock rom i have found for the 935a seeing which will work .
Click to expand...
Click to collapse
If you are currently on a ROM that has v4 boot loader's, part of your problem may be that you are trying to flash a rom with v2, v3 bootloaders
Sent from my SM-G935T using XDA-Developers Legacy app

so i do better go with the v4 bootloader and i will check if the pit file is uncheck, what should i put on the re-partition case of odin active or inactive?
by the way thanks for your help

kangi26 said:
If you are currently on a ROM that has v4 boot loader's, part of your problem may be that you are trying to flash a rom with v2, v3 bootloaders
Sent from my SM-G935T using XDA-Developers Legacy app
Click to expand...
Click to collapse
hey i did exactly as you told me , and for first time i guess i have an advance, i still get an error but at least a new error , check it out maybe you know what it is
<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> emmc_appsboot.mbn
<ID:0/005> lksecapp.mbn
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
any idea what can be?
i try to flash the G935a...PI2 rom bot without the CSC which i guess is the pit file right?

When you try to get the device into Recovery, it will appear like it isn't doing it or looks like an "No Command" error and it can take a couple of min to actually get into Recovery.
I would boot into Recovery again, let it sit for a few min. My bet is that it will eventually get into Recovery. Once it does, do a Factory reset, and then reboot into Download Mode, open Odin connect the device to your PC and install all 4 of the items from the Stock ROM thread, don't mess with any of the settings in Odin, just populate the slots with the BL, AP, CP and CSC

kangi26 said:
When you try to get the device into Recovery, it will appear like it isn't doing it or looks like an "No Command" error and it can take a couple of min to actually get into Recovery.
I would boot into Recovery again, let it sit for a few min. My bet is that it will eventually get into Recovery. Once it does, do a Factory reset, and then reboot into Download Mode, open Odin connect the device to your PC and install all 4 of the items from the Stock ROM thread, don't mess with any of the settings in Odin, just populate the slots with the BL, AP, CP and CSC
Click to expand...
Click to collapse
This is what i get . But it doesnt enter recovery at the end. It just shut off ....

Darkboss10 said:
This is what i get . But it doesnt enter recovery at the end. It just shut off ....
Click to expand...
Click to collapse
Looks like the device is just rebooting
Sent from my SM-G935T using XDA-Developers Legacy app

kangi26 said:
Looks like the device is just rebooting
Sent from my SM-G935T using XDA-Developers Legacy app
Click to expand...
Click to collapse
if you watch the top corner blue letters it says recovery booting....

Darkboss10 said:
if you watch the top corner blue letters it says recovery booting....
Click to expand...
Click to collapse
I'm at a loss man, I'm sorry. I haven't seen that before, I dont get the "Samsung" part when I enter Recovery

Darkboss10 said:
if you watch the top corner blue letters it says recovery booting....
Click to expand...
Click to collapse
Can you post screen from download mode?
From Edge of Galaxy Seven

norbarb said:
Can you post screen from download mode?
From Edge of Galaxy Seven
Click to expand...
Click to collapse
There you go . By the way i should mention the phone only turns on download mode when plugged.

Darkboss10 said:
There you go . By the way i should mention the phone only turns on download mode when plugged.
Click to expand...
Click to collapse
OK you got bootloader v2. Try to flash some older version of MM in download mode using odin
Like from here: http://forum.xda-developers.com/showthread.php?p=67601581
From Edge of Galaxy Seven

You need to start by using the latest Odin, 3.12.3 for installing the original ROM. If you try to unlock, you need to go get the PrinceComsy version. PrinceComsy won't work for in-bricking a device, and if you have any of the stock versions of the ROM, you need the 3.12.3 version.

norbarb said:
OK you got bootloader v2. Try to flash some older version of MM in download mode using odin
Like from here: http://forum.xda-developers.com/showthread.php?p=67601581
From Edge of Galaxy Seven
Click to expand...
Click to collapse
I try that . Now i got this error but only on the phone screen and odin is stuck at initialization .. any idea what could be

i download the venom stock rom and the odin file he suggest but that odin is v 3.11.2 , so that was the one that trows me the odin protocol error, i try the same rom but with the v 3.12.3 odin , and it start working but it says fail at the on the recovery image, do that has to do something with my problem that the phone can boot into recovery mode?
here are the logs
<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> boot.img
<ID:0/005> recovery.img
<ID:0/005> FAIL! (Erase)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1

[GUIDE]: How to flash CRB7 using Odin - S8+

UPDATE (27TH FEB 2018): We now have Odin v3.13.1 which is compatible with the new .lz4 compressed files referred to below in the tutorial. All the steps below are only required now if you are using a version of Odin older than 3.13.1. It is recommended that you use this new version to save yourself the hassle.
Odin v3.13.1 - XDA Link
S8+ G955F / G955FD (F ROMs work on the FD variants, there are no FD specific ROMs):
Mirror Link 1 (Google Drive) - Thanks @cretu01
Mirror Link 2 (Android File Host) - Thanks @panchuckles
Mirror Link 3 (OneDrive) - Thanks @Brotuck
-------------------------------------------------------------------------------------------------------------------------------
Let me start of by saying, Samsung changed some things around with Oreo. I downloaded 'XXU1CRAP' using SamFirm today, tried with both TUR and DBT CSCs, to make sure it wasn't a bad download or anything, but Odin just wouldn't accept the file. It froze on the first step, sboot.bin.lz4.
I had never seen the .lz4 extension before, so I asked a couple of helpful lads in the Samsung Oreo Telegram group who were very helpful throughout this process.
For those of you who want to join:
http://t.me/sammyoreoclub
Samsung is using a new compression method for the Oreo ROMs, so all files within BL, AP, CP and CSC have the .lz4 extension which Odin has trouble reading, and so the flash will never go past the first step.
Note: THIS DOESN'T TRIP KNOX.
Pre-requisites:
-SamFirm to get the CRAP ROM - https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647
-Windows PC
-This modded version of 7Zip which can open .lz4 files. Link - Github
-The ability to read the instructions below.
-Prince Comsy's modified Odin - Google Drive Link
-A Galaxy S8/S8+ (G950F / G950FD / G955F / G955FD) - I tested this on my own G955FD and it worked just fine.
-The XXU1CRB7 Oreo ROM for your device
-A decent amount of storage space on your PC
-Preferably some experience with flashing using Odin
DISCLAIMER: I AM NOT RESPONSIBLE FOR BRICKED DEVICES, FOLLOW TUTORIAL AT YOUR OWN RISK.
INTERNAL STORAGE WILL BE COMPLETELY WIPED CLEAN (IF YOU USE CSC_OXM), MAKE SURE YOU BACKUP BEFORE FLASHING.
IF YOUR INTERNAL STORAGE SHOWS AS '16 GB' AFTER FLASHING, DO A FACTORY RESET AND IT'LL RETURN TO NORMAL.
Steps below:
1. Extract the zip file for the 3.7 GB firmware file you just downloaded. Should contain 5 files, AP, BL, CP, CSC_OXM and HOME_CSC_OXM.
In the tutorial below, I will be using CSC_OXM, however that does wipe internal storage.
If you are coming from ZRA5 or just don't want to wipe your data, use HOME_CSC_OXM instead.
2. All the files will have ".tar.md5" extensions. Remove the .md5 part so they can be opened in either WinRAR or 7Zip.
AP will contain a folder called 'meta-data', userdata.img.lz4, system.img.lz4, recovery.img, boot.img.lz4
Extract all these files from AP into a new folder. Right click on each one, select the '7Zip Standard' menu and hit 'Extract Here'.
This will extract all the files within, without .lz4 extensions. So you'll have userdata, system, recovery and boot as plain IMG files.
Note: Repeat this for CP, BL and CSC_OXM.
3. Grab the original file names for the files you extracted earlier, copy paste them into notepad.
They should be in this format, make sure .md5 isn't added at the end of any filenames. Do keep in mind that the filenames for the S8 (G950F) will obviously be slightly different.
Code:
AP_G955FXXU1CRAP_CL12993656_QB16754780_REV00_user_low_ship_meta.tar
BL_G955FXXU1CRAP_CL12993656_QB16754780_REV00_user_low_ship.tar
CP_G955FXXU1CRAP_CP8821296_CL12993656_QB16754780_REV00_user_low_ship.tar
CSC_OXM_G955FOXM1CRAP_CL12993656_QB16754780_REV00_user_low_ship.tar
4. Select all the files you extracted for AP (including the meta-data folder), right click, scroll down to the '7Zip Standard' menu again and this time hit 'Add to Archive'. Copy-paste the filename for whichever file you're creating an archive for, AP, BL, CP or CSC, make sure archive format is set to .tar and leave everything else default and hit 'OK' at the bottom of the window.
Note: This too will be have to be done for CP, CSC and BL as well.
5. Once this is done, you should have 4 .tar files ready to be flashed. Open up Prince Comsy's Odin, add each file to it's respective field in Odin.
6. Connect your device in Download Mode, press Start, and wait for the flash to be completed and for Odin to show 'PASS' at the top of the window.
Your device will reboot automatically.
ALTERNATIVELY, you can watch this very crappy screen recording I made for a better idea on how to do it.
YouTube link: https://youtu.be/eyIh3_p8WBQ
Credits go to:
@FatalONEM8 and @me2151 for helping out.
Tino Reichardt (mcmilk) for the modified 7Zip
Prince Comsy for the modified Odin.
Samsung for making flashing more and more difficult every year.
----------------------------
For Linux/Ubuntu, @kernel.killer has created a script to unpack the .lz4 compressed firmwares without having to do all of the above manually.
See this post - Link

Very useful, thank you. I still hesitated to flash, but now I'm going to start.
Thanks again.

Awesome guide thanks, I'll try and report back

that what I did but boot file cant be opened by 7-zip

What a brilliant title.
How to flash CRAP
L O V E I T!!!!
Thanks for putting this tut together folks!

thanks download links ?

When i tried to update with the 4 file, Odin read them without any problem, but when i press start, phone just reboot. Maybe it is just because i was trying to flash the same version of firmware (CRAP over CRAP)? Maybe i'll have the error reported if just started to flash... but my question is: is it possible to overwrite the firmware with the same version using Odin?

renton82 said:
When i tried to update with the 4 file, Odin read them without any problem, but when i press start, phone just reboot. Maybe it is just because i was trying to flash the same version of firmware (CRAP over CRAP)? Maybe i'll have the error reported if just started to flash... but my question is: is it possible to overwrite the firmware with the same version using Odin?
Click to expand...
Click to collapse
Yeah that did happen with me.
If you use HOME_CSC and flash CRAP over CRAP, nothing happens.
You can overwrite if you use CSC_OXM.
Sent from my ONEPLUS A5000

Will this method trip knox? (void warranty)

cretu01 said:
will this method trip knox? (void warranty)
Click to expand...
Click to collapse
no it will not.

hasanben35 said:
thanks download links ?
Click to expand...
Click to collapse
you read just title !!!

hello guys, does this tutorial only works for devices with ZRA5 firmware or can I do it with the AQL5?

Blasembauer said:
hello guys, does this tutorial only works for devices with ZRA5 firmware or can I do it with the AQL5?
Click to expand...
Click to collapse
...:crying: is like all many roms ( for XXXX firmware )!!

Worked like a charm , Much appreciated
<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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> cm.bin
<ID:0/004> param.bin
<ID:0/004> sboot.bin
<ID:0/004> up_param.bin
<ID:0/004> boot.img
<ID:0/004> recovery.img
<ID:0/004> system.img
<ID:0/004> userdata.img
<ID:0/004> modem.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> modem_debug.bin
<ID:0/004> Transmission Complete..
<ID:0/004> Now Writing.. Please wait about 2 minutes
<ID:0/004> Receive Response from boot-loader
<ID:0/004> cache.img
<ID:0/004> omr.img
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

OkaY THANKS samfrim turkey rom crap downloadded normal flash not work ? use method

Is not anyone who can do a new archive with the Modded rom?

Mine is stuck at file analysis, what should I do?

Done everything.
I got this on odin:
<ID:0/005> Added!!
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
And nothing happens.

nelfurdui85 said:
Done everything.
I got this on odin:
<ID:0/005> Added!!
<ID:0/005> Removed!!
<ID:0/005> Added!!
<ID:0/005> Odin engine v(ID:3.1203)..
<ID:0/005> File analysis..
And nothing happens.
Click to expand...
Click to collapse
Mine too.

I can not install an original ROM, and I can not do a hard reset [SM-G530T1]

I went to do a root on my Samsung Grand Prime and it occurred some error and corrupted the system (I think). The phone turns on and is locked on the initiation screen. I have tried to install several different ROM, from various sites, including the original manufacturer. Anyway, nothing helped, always gives error for Odin (including I used different versions of Odin too). I also can't access the recovery mode so I can do a hard reset.
Would it have any way to make the hard reset of the phone through the PC? I've tried everything and so far I've got nothing.
Model = SM-G530T1 (METRO PCS)

marcolp said:
I went to do a root on my Samsung Grand Prime and it occurred some error and corrupted the system (I think). The phone turns on and is locked on the initiation screen. I have tried to install several different ROM, from various sites, including the original manufacturer. Anyway, nothing helped, always gives error for Odin (including I used different versions of Odin too). I also can't access the recovery mode so I can do a hard reset.
Would it have any way to make the hard reset of the phone through the PC? I've tried everything and so far I've got nothing.
Model = SM-G530T1 (METRO PCS)
Click to expand...
Click to collapse
What instructions did you followed? Does the rom no longer boots or gets to Android or download mode? Maybe you forgot to enable OEM Unlock option available at Developer Options.

Hey, look
First, from the recovery, wipe the system, the data and everything (cash,davlik)
Then, go to the samsung firmware site, and search your phone model number, then download the firmware
Finally, install the ROM to your phone via Odin
And everything should be fine

tasnim_tamim said:
What instructions did you followed? Does the rom no longer boots or gets to Android or download mode? Maybe you forgot to enable OEM Unlock option available at Developer Options.
Click to expand...
Click to collapse
I followed all the steps correctly. I downloaded the original ROM, Odin. I activated the debug mode and left marked the Unlock OEM option in developer mode. I enter the download mode by mobile (the recovery mode is not working), I open the Odin, select the file PIT and the PDA file, start the process, and then a few seconds later says it failed, and on the phone pops up the error "SW REV CHECK FAIL : [aboot] Fused 2 > Binary 1 ". I can't get rid of that mistake. I have tried more than 5 different ROM and all end up giving that same error on the phone. I just wanted to know some way to get into recovery mode and do a hard reset. But it's not working through the buttons on the phone, just to enter the download mode.
<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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<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)

marcolp said:
I followed all the steps correctly. I downloaded the original ROM, Odin. I activated the debug mode and left marked the Unlock OEM option in developer mode. I enter the download mode by mobile (the recovery mode is not working), I open the Odin, select the file PIT and the PDA file, start the process, and then a few seconds later says it failed, and on the phone pops up the error "SW REV CHECK FAIL : [aboot] Fused 2 > Binary 1 ". I can't get rid of that mistake. I have tried more than 5 different ROM and all end up giving that same error on the phone. I just wanted to know some way to get into recovery mode and do a hard reset. But it's not working through the buttons on the phone, just to enter the download mode.
<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> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<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)
Click to expand...
Click to collapse
Tell me your phone baseband.
Also can you boot to Android? According to logs it seems that Odin was not able to write anything on your device. So it should be bootable to Android.
Which firmware did you tried to download and install? Tell me the CSC of it. If possible link to the firmware site.

tasnim_tamim said:
Tell me your phone baseband.
Also can you boot to Android? According to logs it seems that Odin was not able to write anything on your device. So it should be bootable to Android.
Which firmware did you tried to download and install? Tell me the CSC of it. If possible link to the firmware site.
Click to expand...
Click to collapse
Where can I look at the baseband of the phone? As I said, I tried with several firmwares, and none had succeeded. I will leave the links of all that I have tried to use. I'm trying to download the firmware from Sammobile, but the downloads for free will only be back tomorrow, on Monday.
SW: G530T1UVU1AOH9
PDA: G530T1UVU1AOH9
http://www.galaxyrom.com/2015/08/up...e-sm-g530t1-g530t1uvu1aoh9-android-5-1-1.html
http://live.samsung-updates.com/details/82656/Samsung_SM-G530T1/SM-G530T1/TMB/G530T1UVU1AOH9.html
https://forum.xda-developers.com/grand-prime/development/stock-fw-metropcs-sm-g530t1-t3340513
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Let me know if you get back to stock 5.1.1 because nothing works. Im forced to use june version of lineage 14.1

got back to stock 5.1.1
https://forum.xda-developers.com/gr...ch-samsung-t3755208/post75696587#post75696587