Any ODIN flashable Rom Request - Galaxy Note Pro 12.2 Q&A, Help & Troubleshooting

hi all, I've managed to brick my SM-P900.
Could someone point me to where I can get an Odin flashable rom please, with all the individual bits such as PDA / Phone / CSC.
I can't flash normal roms, it's not working with just the md5. Ideally stock, but happy with any rom as I can flash something else with TWRP.
I can't use any of the normal samsung sites as they're paid, and I'm broke =(
I would really appreciate it if you could help me fix this.
Many thanks

Google
SM-P900 - Samsung Firmware | Samsung Updated
---------- Post added at 03:14 AM ---------- Previous post was at 03:09 AM ----------
https://forum.xda-developers.com/galaxy-note-pro-12/general/firmware-firmware-t3038178

Where you able to solve your problem?

bmwdroid said:
Where you able to solve your problem?
Click to expand...
Click to collapse
x2 for me also

sp000n said:
x2 for me also
Click to expand...
Click to collapse
Sorry, don't understand.
Problems or just interested as well?

Nope, not solved, tried for ages, but ODIN doesn't flash it, just gets stuck on initialising.... I'm completely out of ideas!

Zophixan said:
Nope, not solved, tried for ages, but ODIN doesn't flash it, just gets stuck on initialising.... I'm completely out of ideas!
Click to expand...
Click to collapse
Did you get the multiple part ROM using samfirm_reborn tool?

bmwdroid said:
Did you get the multiple part ROM using samfirm_reborn tool?
Click to expand...
Click to collapse
Just tried downloading it and I get .tar.md5 file, not sure how i did it but from a previous attempt at fixing it, I have the same thing but in seperate files, with boot, cache, hidden, recovery s boot and system. Do i need to put them into odin? where do they go? I get stuck on initialising, tried pulling out cable and putting it back in, then it says it can't find a pit partition... tried flashing a pit file but still stuck on initiailising so pit doesn't flash.

@Zophixan the files you see, are in the opened archive.
Where did you get the file from?
You should have downloaded and decrypted 3 (P900) or 4-5(P905) separate files all ending md5 when using samfirm.
When there is only one you obviously have NOT the multiple part stock ROM.
Which Odin using?

bmwdroid said:
@Zophixan the files you see, are in the opened archive.
Where did you get the file from?
You should have downloaded and decrypted 3 (P900) or 4-5(P905) separate files all ending md5 when using samfirm.
When there is only one you obviously have NOT the multiple part stock ROM.
Which Odin using?
Click to expand...
Click to collapse
I've tried odin 3.07 and 1.85. I downloaded samfirm_reborn and upon use it downloaded just one file "SM-P900_1_20170222195126_gly008r5gf.zip" and inside it is the tar md5. Where can I get the separate items?
Even if I am not using the seperated one, shouldn't odin flash? It's always stuck on intiailising, I don't know if this matters but it says knox warranty 0500 on the download screen, and custom kernal / binary.
I remember having a similiar problem years ago on the same tablet but no idea how I fixed it, vaguely remember downloading seperate files to flash in each of the odin sections.
thanks.
EDIT, found the binary option nature option, will download now and try flashing each bit and report back...

bmwdroid said:
@Zophixan the files you see, are in the opened archive.
Where did you get the file from?
You should have downloaded and decrypted 3 (P900) or 4-5(P905) separate files all ending md5 when using samfirm.
When there is only one you obviously have NOT the multiple part stock ROM.
Which Odin using?
Click to expand...
Click to collapse
Still stuck on initializing, tried samsung drivers, even tried heimdall (and installed it's drivers), is there anything else I can try?
It says AP SWREV A1 and know warranty voide 0500, and current binary / system status as custom on the tablet.

Try a newer Odin.
I recommend at least 3.09.
What it says in DL mode is just information and no failure afaik.

bmwdroid said:
Try a newer Odin.
I recommend at least 3.09.
What it says in DL mode is just information and no failure afaik.
Click to expand...
Click to collapse
I tried both 3.10 and 3.09 but still stuck on initialisation... (do i need to do anything with CP or UMS field?),
does the current binary/ system status as custom ,or AP SWREV A1, or knox warranty mean anything?
Do you have any other suggestions, I can't think of anything else! =(

Knox was triggered when flashing other than stock.
Forget about it.
Other is shown on mine as well.
CP stays empty at WiFi models.
UMS I've never did anything with.
Try to use other cables and USB ports.

Related

[Q] AT&T SGH-I727 Odin Crashes at "Getting PIT for mapping..."

Hello
I have an issue trying to use KIES, ODIN, or Heimdall Suite trying to flash just about anything to an AT&T Galaxy S II Skyrocket - SGH-I727. This phone was my brother's and according to him he installed CW Recovery (do not currently have the version) successfully but when he tried to flash a new ROM the phone rebooted with the "Firmware upgrade encountered an issue..." screen. He is adamant that anytime he used ODIN he did not leave the option for PIT checked.
These are the steps I have tried to flash back to stock
1. Use KIES as recommended by the error on the screen. Installed the Samsung Galaxy S II Skyrocket drivers, phone is detected by windows device manager and I attempt to do an emergency recovery. The process gets all the way to the point of trying to flash the new firmware but hangs there. I let it run for over 48 hours and did not move a single percent.
2. Use ODIN to flash a Stock Recovery TAR. ODIN, of any version number but specifically 1.85, will crash with an 0xc0000005 error at "Getting PIT for mapping..." consistently. I have tried this across three different physical Windows 8 and 7 machines, Windows XP mode on one of them, and a myriad of different micro USB cables.
3. Use Heimdall Suite, versions 1.3.1 and 1.3.2, on both Windows platform and Ubuntu running in a virtual machine. The device is detected on both platforms. On windows the software will hang if I try to read the PIT. On Ubuntu it will "read" the PIT but the file produced is 0 bytes. If I try to flash the TAR file using Heimdall then when the phone reboots it hangs at the Samsung logo and I can put it into download mode without getting the "Firmware upgrade encountered an issue..." message. However, neither ODIN or Heimdall will do a successful flash.
From most of my searches and reading of posts it seems that if I can get into Download Mode then the phone is not hard bricked. It appears though there is some form of corruption in the PIT if that is possible, like a quasi-brick.
As a last ditch effort I wanted to take fate in my hands and do flash the PIT but I have not been able to find a PIT file for the SGH-I727.
Does anyone know if there is a PIT file for the SGH-I727 or have any other suggestions for how to get the phone back to stock? Or, does it look like even though I can hit download mode JTAG will be the only real solution?
Have you tried one of the Odin one clicks, it can be found here... http://www.androidaddicted.com/firm...lc4-ics-4-0-3-leaked-firmware-update-576.html
Sent from my SGH-I727 using Tapatalk 2
worias said:
Hello
I have an issue trying to use KIES, ODIN, or Heimdall Suite trying to flash just about anything to an AT&T Galaxy S II Skyrocket - SGH-I727. This phone was my brother's and according to him he installed CW Recovery (do not currently have the version) successfully but when he tried to flash a new ROM the phone rebooted with the "Firmware upgrade encountered an issue..." screen. He is adamant that anytime he used ODIN he did not leave the option for PIT checked.
These are the steps I have tried to flash back to stock
1. Use KIES as recommended by the error on the screen. Installed the Samsung Galaxy S II Skyrocket drivers, phone is detected by windows device manager and I attempt to do an emergency recovery. The process gets all the way to the point of trying to flash the new firmware but hangs there. I let it run for over 48 hours and did not move a single percent.
2. Use ODIN to flash a Stock Recovery TAR. ODIN, of any version number but specifically 1.85, will crash with an 0xc0000005 error at "Getting PIT for mapping..." consistently. I have tried this across three different physical Windows 8 and 7 machines, Windows XP mode on one of them, and a myriad of different micro USB cables.
3. Use Heimdall Suite, versions 1.3.1 and 1.3.2, on both Windows platform and Ubuntu running in a virtual machine. The device is detected on both platforms. On windows the software will hang if I try to read the PIT. On Ubuntu it will "read" the PIT but the file produced is 0 bytes. If I try to flash the TAR file using Heimdall then when the phone reboots it hangs at the Samsung logo and I can put it into download mode without getting the "Firmware upgrade encountered an issue..." message. However, neither ODIN or Heimdall will do a successful flash.
From most of my searches and reading of posts it seems that if I can get into Download Mode then the phone is not hard bricked. It appears though there is some form of corruption in the PIT if that is possible, like a quasi-brick.
As a last ditch effort I wanted to take fate in my hands and do flash the PIT but I have not been able to find a PIT file for the SGH-I727.
Does anyone know if there is a PIT file for the SGH-I727 or have any other suggestions for how to get the phone back to stock? Or, does it look like even though I can hit download mode JTAG will be the only real solution?
Click to expand...
Click to collapse
There is no pit for the skyrocket.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
xcrazydx said:
There is no pit for the skyrocket.
Click to expand...
Click to collapse
Sure there is, just pull it from mmcblk0p11 on a good skyrocket using adb and then dd command. Then write it to mmcblk0p11 on the bad phone in recovery using adb and dd command, or flash it in ODIN.
That's exactly what ODIN is doing when it says 'Getting PIT for mapping...', it pulling it from the phone.
An SGH-I727 pit dump is attached.
cschmitt said:
Sure there is, just pull it from mmcblk0p11 on a good skyrocket using adb and then dd command. Then write it to mmcblk0p11 on the bad phone in recovery using adb and dd command, or flash it in ODIN.
That's exactly what ODIN is doing when it says 'Getting PIT for mapping...', it pulling it from the phone.
An SGH-I727 pit dump is attached.
Click to expand...
Click to collapse
cschmitt, this is exactly what I needed! I was able to flash the PIT file in ODIN without crashing. I then flashed the stock firmware using ODIN and the phone is now booting perfectly. All is well.
Great news! Glad you're back up and running.
worias said:
cschmitt, this is exactly what I needed! I was able to flash the PIT file in ODIN without crashing. I then flashed the stock firmware using ODIN and the phone is now booting perfectly. All is well.
Click to expand...
Click to collapse
Did you have another phone to extract it from? Or was that file cschmitt attached what you odined?
Sent from my SAMSUNG-SGH-I727 using xda premium
cschmitt said:
Sure there is, just pull it from mmcblk0p11 on a good skyrocket using adb and then dd command. Then write it to mmcblk0p11 on the bad phone in recovery using adb and dd command, or flash it in ODIN.
That's exactly what ODIN is doing when it says 'Getting PIT for mapping...', it pulling it from the phone.
An SGH-I727 pit dump is attached.
Click to expand...
Click to collapse
i dont/never used adb, can u post the commands(step by step) so i can put it in the 1 stop sticky
worias said:
cschmitt, this is exactly what I needed! I was able to flash the PIT file in ODIN without crashing. I then flashed the stock firmware using ODIN and the phone is now booting perfectly. All is well.
Click to expand...
Click to collapse
to confirm, u didnt use adb to flash the pit file, you used odin to flash the pit file and used the pit option in odin, then you picked pda option for the stock firmware, more details u give the better so i can add it to the sticky
cschmitt said:
Sure there is, just pull it from mmcblk0p11 on a good skyrocket using adb and then dd command. Then write it to mmcblk0p11 on the bad phone in recovery using adb and dd command, or flash it in ODIN.
That's exactly what ODIN is doing when it says 'Getting PIT for mapping...', it pulling it from the phone.
An SGH-I727 pit dump is attached.
Click to expand...
Click to collapse
Cool, thanks!
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
@vincom, yes flashing the pit in Odin along with a stock rom in PDA is the safest method.
Yes please vinvom put it in your stickies, it'll help a lot of us.
Sent from my SGH-I727 using xda app-developers app
cschmitt said:
@vincom, yes flashing the pit in Odin along with a stock rom in PDA is the safest method.
Click to expand...
Click to collapse
so, to confirm, use the pit option, no reboot, then immediately flash stock files, or do then simultaneously
can u also give the adb commands for the pit, can adb also be used for the stock firmwares, which i dont think we can
cschmitt said:
@vincom, yes flashing the pit in Odin along with a stock rom in PDA is the safest method.
Click to expand...
Click to collapse
Was that file you posted the actual pit used in ODIN? It's the same for all our skyrockets/Rogers I727rs ?
Sent from my SAMSUNG-SGH-I727 using xda premium
stoopendis said:
Was that file you posted the actual pit used in ODIN? It's the same for all our skyrockets/Rogers I727rs ?
Click to expand...
Click to collapse
Yes, celox.pit (extracted from the zip) is the actual pit to flash in ODIN. It's from an SGH-I727 and should be the same for Rogers version. Not 100% sure if it's the same for TMO flavor.
vincom said:
so, to confirm, use the pit option, no reboot, then immediately flash stock files, or do then simultaneously
can u also give the adb commands for the pit, can adb also be used for the stock firmwares, which i dont think we can
Click to expand...
Click to collapse
k in going to use this thread to link from the sticky and also add it in the odin troubleshootibg section in restoring to stock
********************************************
when trying to flash stock firmwares and/or recoveries and it hangs at "Getting PIT for mapping" or getting pit errors in odin, download celox.zip and "unzip" the file, select the extracted "celox.pit" file in the pit option for odin, with all other options unchecked hit the start button in odin, once flashed you can then flash the stock firmware and/or recovery in odins pda section.
thanks cschmitt
Extract celox.pit from the zip and flash the pit file, do not attempt to flash the zip file directly.
cschmitt said:
Extract celox.pit from the zip and flash the pit file, do not attempt to flash the zip file directly.
Click to expand...
Click to collapse
k, i reedited the post
stoopendis said:
Did you have another phone to extract it from? Or was that file cschmitt attached what you odined?
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
I used the attachment from cschmitt, extracted the PIT file from the zip and then used ODIN to flash it. I was then able to flash a Skyrocket Stock ODIN tar to restore to GB and boot the phone. I have since been able to get it rooted, CWTouch on it, and have CM10 running on it well.
Thanks again everyone.
I did copy TWRP2.2.0 and stock firmware zip in SD card and hold volume up+down + power button to get recovery mode but I only see pictures of phone & monitor with yellow
triangle at center.( including : Firmware upgrade encountered an issue . please select recovery mode in Kies & try again.)
---------- Post added at 06:31 AM ---------- Previous post was at 06:23 AM ----------
I upgraded my samsung s2 version 2.3.6 to 4.0.4 through the Kies. Then I tried to install TWRP 2.2.0 and Odin 1.85. I saw COM 14 ; COM 17 when I hit start button .It said
FAILED. Now it showed a yellow triangle in the middle of phone & monitor pictures. ( including : Firmware upgrade encountered an issue . please select recovery mode in Kies & try again). I saw COM 3 but it said it couldn't open the serial (COM )port . All thread completed (success 0/ failed 1) .
I just tried other laptop to use Odin & stock 4.0.4 to flash back Stock rom.and got getting mapping pit....I still can go to Download mode but I can't flash anything.
Please help . Thank you very much.
If I understand, you're trying to flash 4.0.4 with odin. And it's a md5 file, right? Keep trying it. Sometimes it takes more than one try.
And check the check sum of the stock rom file you downloaded it could be a bad download
God promised men that he'd put beautiful women in all corners of the world. Then he laughed and laughed and made the world round

[Q] P6810 Problem! - Won't go to Recovery - Bootloop

Hi, I'm having and issue with my Galaxy Tab 7.7 (P6810) and don't know what is the problem, so I'm looking for assistance here. (Thanks in advance).
Let me describe my issue(s):
1. A friend went to flash the Tab and apparently used the wrong firmware, in Odin mode shows GT-P7560.
2. I already tried flashing different firmwares but when I use ICS the Tab goes into a bootloop. I can go to download (odin) mode, but can't go to recovery mode (volume up + power).
3. I flashed it with a stock firmware (P6810DTKL5_P6810XSAKL2_XSA) and got it to boot, but is asking for a password it never had.
So I'm thinking there's an issue with the partition or bootloader. Already tried a "p6810-16g.pit" file with no luck
Tried flashing different CWM versions and nothing works. So at this point I'm stuck on this issue.
What can I do to bring back my device to a functional state? Any advice would be appreciated! THANKS A LOT!! :good::laugh:
I'm attaching the images describing the issues.
edwing29 said:
Hi, I'm having and issue with my Galaxy Tab 7.7 (P6810) and don't know what is the problem, so I'm looking for assistance here. (Thanks in advance).
Let me describe my issue(s):
1. A friend went to flash the Tab and apparently used the wrong firmware, in Odin mode shows GT-P7560.
2. I already tried flashing different firmwares but when I use ICS the Tab goes into a bootloop. I can go to download (odin) mode, but can't go to recovery mode (volume up + power).
3. I flashed it with a stock firmware (P6810DTKL5_P6810XSAKL2_XSA) and got it to boot, but is asking for a password it never had.
So I'm thinking there's an issue with the partition or bootloader. Already tried a "p6810-16g.pit" file with no luck
Tried flashing different CWM versions and nothing works. So at this point I'm stuck on this issue.
What can I do to bring back my device to a functional state? Any advice would be appreciated! THANKS A LOT!! :good::laugh:
I'm attaching the images describing the issues.
Click to expand...
Click to collapse
You don't need a bootloader, it was already "flashed" when he flashed the stock official firmware - bootloader would have been included in that and PIT
If done correctly, the PIT should work, if not - unfortunately, most likely back for repair............ bummer
Without actually checking the above is HC, have you tried the official HoneyComb firmware ? Just don't factory reset in HC recovery
P6810 ICS LPP Bootloader
Here you go............
I have packaged my P6810 ICS LPP bootloader files into an ODIN flashable .tar.mD5 format.
Flashing Instructions :
Extract the Sbl.bin.zip and boot.bin.zips so that you have Sbl.bin.tar.md5 & boot.bin.tar.md5
Ensure you have the latest Samsung USB drivers installed
Disable KIES
Disable KIES process in Task Manager
Run ODIN
Ensure ONLY "auto reboot" and "reset time" are checked
Device in Download mode
Connect device to PC USB port
ODIN - Flash Sbl.bin.tar.md5 in either "bootloader" -or- "PDA" option (choose one only)
Then repeat above same method to flash boot.bin.tar.md5
** After that, try reflash the COMPLETE official stock ICS LPP package with ODIN
Best of luck
UITA
.
UpInTheAir said:
Here you go............
I have packaged my P6810 ICS LPP bootloader files into an ODIN flashable .tar.mD5 format.
Flashing Instructions :
Extract the Sbl.bin.zip and boot.bin.zips so that you have Sbl.bin.tar.md5 & boot.bin.tar.md5
Ensure you have the latest Samsung USB drivers installed
Disable KIES
Disable KIES process in Task Manager
Run ODIN
Ensure "auto reboot" and "reset time" are checked
Device in Download mode
Connect device to PC USB port
ODIN - Flash Sbl.bin.tar.md5 in either "bootloader" -or- "PDA" option (choose one only)
Then repeat above same method to flash boot.bin.tar.md5
** After that, try reflash the COMPLETE official stock ICS LPP package with ODIN
Best of luck
UITA
.
Click to expand...
Click to collapse
Hi, thanks for your assistance... here's what I just did:
1. I downloaded the bin files you attached and both are appearing as invalid md5 in ODIN, apparently the hash is invalid.
2. I renamed them from .tar.md5 to just .tar and flashed my device with both files as you described.
3. Rebooted twice, went to Download mode again.
4. Flashed with P6810XXLPP_P6810XSALJ2 (stock firmware).
5. Got bootloop again.
6. Re-flashed the "Sbl.bin" & "boot.bin" again, and still got bootloop.
7. Download mode still shows "P7560" as the installed firmware.
Any other advice?
Thanks again! :good:
edwing29 said:
Hi, thanks for your assistance...
I downloaded the bin files you attached and both are appearing as invalid md5 in ODIN, apparently the has is invalid.
Can you check them and re-upload if there's no problem?
Thanks again! :good:
Click to expand...
Click to collapse
I'll have a play around on my device first, and see if I can get them to work. Those were untested.
Sent from my GT-I9500 using xda premium
UpInTheAir said:
I'll have a play around on my device first, and see if I can get them to work. Those were untested.
Sent from my GT-I9500 using xda premium
Click to expand...
Click to collapse
Hi, I just edited the previous reply.
Check it out, Thanks.
edwing29 said:
Hi, thanks for your assistance... here's what I just did:
1. I downloaded the bin files you attached and both are appearing as invalid md5 in ODIN, apparently the hash is invalid.
2. I renamed them from .tar.md5 to just .tar and flashed my device with both files as you described.
3. Rebooted twice, went to Download mode again.
4. Flashed with P6810XXLPP_P6810XSALJ2 (stock firmware).
5. Got bootloop again.
6. Re-flashed the "Sbl.bin" & "boot.bin" again, and still got bootloop.
7. Download mode still shows "P7560" as the installed firmware.
Any other advice?
Thanks again! :good:
Click to expand...
Click to collapse
Very strange, particularly if the flash was successful.....................
Try flashing both the files at once. boot.bin in "bootloader" and SBl.bin in "PDA".
Maybe something else we haven't thought of..
If I think of anything else, will let you know, but try the stock HC firmware too, just in case.
UpInTheAir said:
Very strange, particularly if the flash was successful.....................
Try flashing both the files at once. boot.bin in "bootloader" and SBl.bin in "PDA".
Maybe something else we haven't thought of..
If I think of anything else, will let you know, but try the stock HC firmware too, just in case.
Click to expand...
Click to collapse
Tried the steps above and still the same.
I had to flash back to the stock HC firmware because the ICS led into an infinite loop, at least HC let me turn off the device.
I'll wait for any other suggestions, thanks!
Sent from my GT-I9100 using xda app-developers app
All I can suggest is to send it away for repair.
JTag (riff box) by a 3rd party or Samsung.
If it's NOT a hardware issue, JTag should be much cheaper, and if successful, faster.
http://www.jtagbox.com/riff-jtag-bo...s-unbrick-bricked-phone-riff-box-owners-list/
Sent from my GT-I9500 using xda premium

[Q] S6 Demo Unit no rom installed

hey
i have a s6 demo unit G920x
i want to install custom recovery twrp but when i do (twrp-2.8.7.1-zeroflte.img.tar) via odin the phone doesnt go any futher than the samsung boot screen (even when i hold the volume up, power and home button)
i managed to go back to the original recover with CF auto root (CF-Auto-Root-zeroflte-zerofltedv-smg920i.tar.md5), but when i boot the recovery up, i cant wipe the phone because it is a demo unit (mdm does not allow factory reset)
on the end of the recovery there are also two yellow lines saying '''dm-verity verification failed...'' and ''Need to check DRK first...)
So, anyone know how to get the custom recovery working so i can install a new rom through the recovery, or does anyone has the official fimware for the demo unit
ps. my recovery is LRX22G.G920IDVU1AOC6 and downloadmode G920XXXU1A0BI_LLK (not sure about this one, i red this from the recovery log)
allright, found the way to unbrick
even when the recovery is not working;
1. Go to sammobile and download the fimware you think it is the right one (for example, the one matching your recovery)
2. Extract the fimware file
3. You will now have somthing like this G920IDVU1AOC6_G920ICOD1AOC6_G920IDVU1AOC6_HOME.tar.md5
4. rename it to anything shorter (ie ldu925x.tar)
5 download cygwin and install it
6 Move the tar file (ldu925x.tar) to C:\cygwin\home\''username''
7 Open cygwin
and delete all the ''.bin'' files by typing the following commands
tar --delete --file=ldu925x.tar modem.bin
tar --delete --file=ldu925x.tar cm.bin
tar --delete --file=ldu925x.tar sboot.bin
8 Once the last command is done just close cygwin. if you want you can check if cygwin really deleted te bin files, by opening the .tar file with winrar
9 Make sure the samsung drivers are installed on your computer
10 Download the latest odin and unzip it
11 Open odin and connect your S6
12 Click on AP and choose modified .tar file from step 7 and press start
... your s6 should boot a few times, and then start up like new, if not, try another fimware from your country from sammobile
Flash stock 5.1.1 ROM via odin.
roydok said:
Flash stock 5.1.1 ROM via odin.
Click to expand...
Click to collapse
Can I do that on my SM-G920X? will it brick my device?
which model?
no it wont if you do it right. I did this on my own SM-G920X
i would recommend you to go into the recovery mode if you didnt flash a custom one, and see what model customrecovery is on your s6, mine was LRX22G.G920IDVU1AOC6, so i downloaded the matching fimware from sammobile (the one with country unkown)
good luck
afehst said:
no it wont if you do it right. I did this on my own SM-G920X
i would recommend you to go into the recovery mode if you didnt flash a custom one, and see what model customrecovery is on your s6, mine was LRX22G.G920IDVU1AOC6, so i downloaded the matching fimware from sammobile (the one with country unkown)
good luck
Click to expand...
Click to collapse
I didn't exactly understand.
Listen: Your story is identical to mine. I bought mine from someone who got it stuck on S6 live demo trying to root it. I flashed exactly the same firmware you mentioned (But different country) without removing the modem or anything (I now have a weird mostly 0 IMEI with baseband) . Can I take a 5.1.1 SM-G920I (same model) and flash it? Thts all. Thanks!
roydok said:
Flash stock 5.1.1 ROM via odin.
Click to expand...
Click to collapse
there is no stock available for the demo unit
AndroidState said:
I didn't exactly understand.
Listen: Your story is identical to mine. I bought mine from someone who got it stuck on S6 live demo trying to root it. I flashed exactly the same firmware you mentioned (But different country) without removing the modem or anything (I now have a weird mostly 0 IMEI with baseband) . Can I take a 5.1.1 SM-G920I (same model) and flash it? Thts all. Thanks!
Click to expand...
Click to collapse
i think it should work if you use the fimware for 5.1.1 with the same operator and same country you used for the 5.0.2 version
if it does not, and odin gives you a failure, you could always just flash back the 5.0.2 version.
i'm currently downloading the 5.1.1 fimware for my s6, and I will install it later on today, i will let you know whetever it worked or not
afehst said:
i think it should work if you use the fimware for 5.1.1 with the same operator and same country you used for the 5.0.2 version
if it does not, and odin gives you a failure, you could always just flash back the 5.0.2 version.
i'm currently downloading the 5.1.1 fimware for my s6, and I will install it later on today, i will let you know whetever it worked or not
Click to expand...
Click to collapse
Thank you Waiting...
allright, i flashed the only rom on sammobile with country unkown on 5.1.1,
it flashes but it does not go any further than the samsung boot screen, neither goes into recovery, so i flashed back the other old rom.
i looked on the internet and i think my s6 5.0.2 provider didnt recieve the 5.1.1 update, maybe you have more luck on trying it, if anything goes wrong, you can always flash back to the old rom.
anyway good luck
afehst said:
no it wont if you do it right. I did this on my own SM-G920X
i would recommend you to go into the recovery mode if you didnt flash a custom one, and see what model customrecovery is on your s6, mine was LRX22G.G920IDVU1AOC6, so i downloaded the matching fimware from sammobile (the one with country unkown)
good luck
Click to expand...
Click to collapse
Please help. When I press volume up, home and power and go into the Android system recovery menu it shows LRX22G.G920XXXU1A0D7_LLK. Which firmware should I download from Sam Mobile? If you could provide the link that would be very much appreciated!
make sure youre wiping cache and data after installing a rom
lite426 said:
Please help. When I press volume up, home and power and go into the Android system recovery menu it shows LRX22G.G920XXXU1A0D7_LLK. Which firmware should I download from Sam Mobile? If you could provide the link that would be very much appreciated!
Click to expand...
Click to collapse
you seem to have the original recovery, there isnt a original s6 rom for your recovery
i bought mine without the original recovery and i couldnt get into the recovery, so i fistly flashed the CF-Auto-Root-zeroflte-zerofltedv-smg920i.tar.md5 to get a working recovery, but now i cant get twrp to work.
if you really want to get your s6 without the demo software, i would suggest you to firstly try this http://www.naldotech.com/how-to-disable-exit-galaxy-s6-demo-live-unit-retail-mode/
if for whatever reason, that doesnt solve your problem (ie your s6 is not booting or it doesnt work) i recommend to flash the twrp-2.8.7.1-zeroflte.img.tar or the twrp-2.8.7.0-zerofltespr.img.tar (if you live in a country with sprint) first . If you manage to get into the custom recovery you could just flash the fimware in this link http://forum.xda-developers.com/gal...-xtrestolite-pure-edition-1-0-beta-1-t3082467
if both of these suggestions are not working for you, you could just do what i did. First flash CF-Auto-Root-zeroflte-zerofltedv-smg920i.tar.md5, than download this file G920IDVU1AOC6_G920ICOD1AOC6_COD.zip from this link (http://dl.sammobile.com/M1FbQyA3Ij1...eRUFfXkI./G920IDVU1AOC6_G920ICOD1AOC6_COD.zip) and follow the tutorial i wrote
Thank you very muchi will try it. , do you have the link for "CF-Auto-Root-zeroflte-zerofltedv-smg920i.tar.md5" please?
How many storage is there after you flashed the new rom? My concern is if the partition is re-written.
afehst said:
allright, found the way to unbrick
even when the recovery is not working;
1. Go to sammobile and download the fimware you think it is the right one (for example, the one matching your recovery)
2. Extract the fimware file
3. You will now have somthing like this G920IDVU1AOC6_G920ICOD1AOC6_G920IDVU1AOC6_HOME.tar.md5
4. rename it to anything shorter (ie ldu925x.tar)
5 download cygwin and install it
6 Move the tar file (ldu925x.tar) to C:\cygwin\home\''username''
7 Open cygwin
and delete all the ''.bin'' files by typing the following commands
tar --delete --file=ldu925x.tar modem.bin
tar --delete --file=ldu925x.tar cm.bin
tar --delete --file=ldu925x.tar sboot.bin
8 Once the last command is done just close cygwin. if you want you can check if cygwin really deleted te bin files, by opening the .tar file with winrar
9 Make sure the samsung drivers are installed on your computer
10 Download the latest odin and unzip it
11 Open odin and connect your S6
12 Click on AP and choose modified .tar file from step 7 and press start
... your s6 should boot a few times, and then start up like new, if not, try another fimware from your country from sammobile
Click to expand...
Click to collapse
lite426 said:
Thank you very muchi will try it. , do you have the link for "CF-Auto-Root-zeroflte-zerofltedv-smg920i.tar.md5" please?
Click to expand...
Click to collapse
http://download.chainfire.eu/736/CF-Root/CF-Auto-Root/CF-Auto-Root-zeroflte-zerofltedv-smg920i.zip
shadowcliffs said:
How many storage is there after you flashed the new rom? My concern is if the partition is re-written.
Click to expand...
Click to collapse
20gb
afehst said:
http://download.chainfire.eu/736/CF-Root/CF-Auto-Root/CF-Auto-Root-zeroflte-zerofltedv-smg920i.zip
20gb
Click to expand...
Click to collapse
So the demo stuff has been get rid of? I heard that on the original demo unit there is only 8 GB left.
shadowcliffs said:
So the demo stuff has been get rid of? I heard that on the original demo unit there is only 8 GB left.
Click to expand...
Click to collapse
No, the demo stuff is not completly gone, at least not the whole partition. Because still 11.41gb is used for the system. But yes. There is more available space to acces for the user;
aznabil said:
ty man for your help
i dont know why my phone is 32g but i have 23.4go for systéme and just 8 go for me
and after flash this rom why the nam of my phone is g925i like s6 edge???
and ty another time man
Click to expand...
Click to collapse
Hey I followed your instructions and flashed it worked but when I turn it on the touchscreen doesn't work and when it booted up it still says Samsung galaxy s6 demo unit and all my apps are still there. and btw I cant boot into recover only download mode.
---------- Post added at 04:41 PM ---------- Previous post was at 04:32 PM ----------
Hey I followed your instructions and flashed it worked but when I turn it on the touchscreen doesn't work and when it booted up it still says Samsung galaxy s6 demo unit and all my apps are still there. and btw I cant boot into recover only download mode. I flashed that one.
PDA G9200ZHU1AOCI
CSC G9200ZZH1AOCI
Also is there a way to factory reset like delete all my files from odin
Do I need to disable Samsung Demo Mode in order to odin flash anything? It seems usb debugging mode is disabled by the Samsung retail mode (actually the entire developer options is greyed out).

Help! Galaxy amp prime (SM-J320AZ) stuck in bootloop

So my galaxy amp prime(Cricket, SM-J320AZ) is stuck in a bootloop, and I have tried to research why, yet every reason seams plausible. So ill start at the beginning...
I used odin with a boot.tar in the ap slot so that kingroot could root my phone. it was successful at rooting my device but refused to switch with supersu me( I now know I needed kingroot 4.5) anyways kingroot deployed as a system app which in turn compromised my safetynet status. I couldn't use a number of apps and services, so I decided to flash the stock rom for my device (found here on xda) it was a little over 1gb and I followed directions. yet when odin successfully flashed it, the device rebooted and now is stuck in a bootloop. it loads the Samsung logo twice then reverts to the android recovery. I tried to wipe cache partition and reboot to no avail. I then tried to wide data/factory reset and reboot, but its still stuck in bootloop.
I originally made a backup with Samsung smart switch, but now it says the device is unsupported.
Is there anything I can do? ive read soft bricks and bootloops can be fixed, but I'm not finding much on my device. any help is greatly appreciated,
sorry if this is in the wrong area, I'm still new to xda
Rororoolz said:
So my galaxy amp prime(Cricket, SM-J320AZ) is stuck in a bootloop, and I have tried to research why, yet every reason seams plausible. So ill start at the beginning...
I used odin with a boot.tar in the ap slot so that kingroot could root my phone. it was successful at rooting my device but refused to switch with supersu me( I now know I needed kingroot 4.5) anyways kingroot deployed as a system app which in turn compromised my safetynet status. I couldn't use a number of apps and services, so I decided to flash the stock rom for my device (found here on xda) it was a little over 1gb and I followed directions. yet when odin successfully flashed it, the device rebooted and now is stuck in a bootloop. it loads the Samsung logo twice then reverts to the android recovery. I tried to wipe cache partition and reboot to no avail. I then tried to wide data/factory reset and reboot, but its still stuck in bootloop.
I originally made a backup with Samsung smart switch, but now it says the device is unsupported.
Is there anything I can do? ive read soft bricks and bootloops can be fixed, but I'm not finding much on my device. any help is greatly appreciated,
sorry if this is in the wrong area, I'm still new to xda
Click to expand...
Click to collapse
Point to the firmware you downloaded and also which version of odin you used.
ashyx said:
Point to the firmware you downloaded and also which version of odin you used.
Click to expand...
Click to collapse
I extracted this
AP_J320AUCS2AQA1_CL7663112_QB12351033_REV00_user_low_ship.tar
i believe is the firmware, and I'm using odin 3.11.1
I also asked in page 17 of the original thread
I'm just running out of options here lol
you actually posted right above me in that thread!
Rororoolz said:
I extracted this
AP_J320AUCS2AQA1_CL7663112_QB12351033_REV00_user_low_ship.tar
i believe is the firmware, and I'm using odin 3.11.1
I also asked in page 17 of the original thread
I'm just running out of options here lol
Click to expand...
Click to collapse
I suggest you flash the entire firmware not just AP.
ashyx said:
I suggest you flash the entire firmware not just AP.
Click to expand...
Click to collapse
Do u happen to know where i can find the rest?
Would i have to re partition it? Because im trying to research and learn, but i was under the impression that AP was the only spot to put firmware
I believe your proper firmware would be J320AZTUU1APC4
http://www.mediafire.com/file/skiapd1xqj3s7se/J320AZTUU1APC4_J320AZAIO1APC4_5.1.1_USA_4Files.zip
seaf0ur said:
I believe your proper firmware would be J320AZTUU1APC4
http://www.mediafire.com/file/skiapd1xqj3s7se/J320AZTUU1APC4_J320AZAIO1APC4_5.1.1_USA_4Files.zip
Click to expand...
Click to collapse
The files say md5 error, binary failed
I think im missing something here
You tried to flash only AP but for J320A, here you have full firmware for J320AZ: https://drive.google.com/file/d/0B5vkBxwCY_cCSkh0UHNZMmxmcVk/view
johnny.goldy said:
You tried to flash only AP but for J320A, here you have full firmware for J320AZ: https://drive.google.com/file/d/0B5vkBxwCY_cCSkh0UHNZMmxmcVk/view
Click to expand...
Click to collapse
Most these files worked, i checked auto reboot, re partition, and r reset. I set the pit file and all 4 others in correct spot. Yet it failed a few times. I unchecked the bl file and it succeeded. When i reboot it shows logo twice then shows android saying installing sys update.... then error... then goes back to recovery.
Essentially i flashed everything except the bl file. And when i try to flash it by itself it says
Initialization
Erase...
Set PIT file
DO NOT TURN OFF TARGET
get pit for mapping
Firmware update starting
Single download
Sboot.bin
NAND write start!
Fail!
Complete(write) operation fail
............
Im guessing the problem is with my BL file
When i go to boot phone it shows an android and says installing system update then says error very quickly and goes to recovery.
I feel like thats progress but why would only BL file be failing? The green bar in odin goes halfway then fails (with only bl file checked)
Rororoolz said:
Most these files worked, i checked auto reboot, re partition, and r reset. I set the pit file and all 4 others in correct spot. Yet it failed a few times. I unchecked the bl file and it succeeded. When i reboot it shows logo twice then shows android saying installing sys update.... then error... then goes back to recovery.
Essentially i flashed everything except the bl file. And when i try to flash it by itself it says
Initialization
Erase...
Set PIT file
DO NOT TURN OFF TARGET
get pit for mapping
Firmware update starting
Single download
Sboot.bin
NAND write start!
Fail!
Complete(write) operation fail
............
Im guessing the problem is with my BL file
When i go to boot phone it shows an android and says installing system update then says error very quickly and goes to recovery.
I feel like thats progress but why would only BL file be failing? The green bar in odin goes halfway then fails (with only bl file checked)
Click to expand...
Click to collapse
It WILL fail at the bootloader as it's not intended for your device. Just flash the correct firmware as advised.
ashyx said:
It WILL fail at the bootloader as it's not intended for your device. Just flash the correct firmware as advised.
Click to expand...
Click to collapse
Thats what i mean, i extracted all 5 files as advised(a few comments ago) it had
BL
AP
CP
CSC
PIT
I placed them in corresponding odin slot (even pit, with re partition) yet it fails at the BL slot)
I flash it all except bl its still in bootloop
Also Says dm-verity verification failed
Mind you, that i am flashing the right firmware now. I realize my original mistake by flashing the 320a. But these are the stock 320AZ files i am now speaking of...
Rororoolz said:
Thats what i mean, i extracted all 5 files as advised(a few comments ago) it had
BL
AP
CP
CSC
PIT
I placed them in corresponding odin slot (even pit, with re partition) yet it fails at the BL slot)
I flash it all except bl its still in bootloop
Also Says dm-verity verification failed
Mind you, that i am flashing the right firmware now. I realize my original mistake by flashing the 320a. But these are the stock 320AZ files i am now speaking of...
Click to expand...
Click to collapse
This probably means you had a newer firmware revision on your device.
ashyx said:
This probably means you had a newer firmware revision on your device.
Click to expand...
Click to collapse
So do i have any options left? Or should i just chuck it into the cornfield
Rororoolz said:
So do i have any options left? Or should i just chuck it into the cornfield
Click to expand...
Click to collapse
Of course you probably just need the revision 3 firmware. It's posted at the link below.
https://forum.xda-developers.com/galaxy-j3-2016/development/odin-j320a-j320az-links-t3631914
J320AZTUS3AQG1
Try this one: https://www.androidfilehost.com/?fid=817550096634792721
johnny.goldy said:
Try this one: https://www.androidfilehost.com/?fid=817550096634792721
Click to expand...
Click to collapse
IT WORKED! Omg IT wOrked!
ashyx said:
Of course you probably just need the revision 3 firmware. It's posted at the link below.
https://forum.xda-developers.com/galaxy-j3-2016/development/odin-j320a-j320az-links-t3631914
J320AZTUS3AQG1
Click to expand...
Click to collapse
It wasnt the firmware you said, but thank you so much for the help!
Rororoolz said:
It wasnt the firmware you said, but thank you so much for the help!
Click to expand...
Click to collapse
Doesn't matter it was still revision 3 firmware.
The one linked is the latest revision 3 firmware.

No OS Found \ SW Check Fail [aboot]: fused 3/Binary 2 Error

If I'm not allowed to post this please remove.
Although I could really use some help.
My device is a Galaxy J3 Emerge J327p (2017)
I was following a guide to flash a CFW via TWRP.
I thought I had made a NAND backup but somehow it is nno where to be found. I did a wipe of the phone before flashing an Unofficial LineageOS.
After the formatting device rebooted. Loaded up into recovery automatically. However my TWRP was gone and it was stock. Reflashed TWRP and tried to flash the new OS. Failed to flash, incomparable version of Lineage I take it. Maybe not built for my build. However there was still no OS.
I proceeded to download the stock J3 Emerge firmware.
It was in 4 parts which was really new to me. My GS5 only needed a AP Tar file to restore stock OS.
I put all files in Odin in proper places, and flash.
Odin fails, and Download mode gives SW Check Fail error.
SW Check Fail [aboot] : fused 3 / Binary 2.
I read a lot of forums and watched a lot of videos before writing all this and asking for help.
I cannot restore to stock, I cannot find another CFW to replace stock.
Any help is appreciated.
Rawbert.Watkins said:
If I'm not allowed to post this please remove.
Although I could really use some help.
My device is a Galaxy J3 Emerge J327p (2017)
I was following a guide to flash a CFW via TWRP.
I thought I had made a NAND backup but somehow it is nno where to be found. I did a wipe of the phone before flashing an Unofficial LineageOS.
After the formatting device rebooted. Loaded up into recovery automatically. However my TWRP was gone and it was stock. Reflashed TWRP and tried to flash the new OS. Failed to flash, incomparable version of Lineage I take it. Maybe not built for my build. However there was still no OS.
I proceeded to download the stock J3 Emerge firmware.
It was in 4 parts which was really new to me. My GS5 only needed a AP Tar file to restore stock OS.
I put all files in Odin in proper places, and flash.
Odin fails, and Download mode gives SW Check Fail error.
SW Check Fail [aboot] : fused 3 / Binary 2.
I read a lot of forums and watched a lot of videos before writing all this and asking for help.
I cannot restore to stock, I cannot find another CFW to replace stock.
Any help is appreciated.
Click to expand...
Click to collapse
CFW?
You need a revision 3 firmware.
Rawbert.Watkins said:
If I'm not allowed to post this please remove.
Although I could really use some help.
My device is a Galaxy J3 Emerge J327p (2017)
I was following a guide to flash a CFW via TWRP.
I thought I had made a NAND backup but somehow it is nno where to be found. I did a wipe of the phone before flashing an Unofficial LineageOS.
After the formatting device rebooted. Loaded up into recovery automatically. However my TWRP was gone and it was stock. Reflashed TWRP and tried to flash the new OS. Failed to flash, incomparable version of Lineage I take it. Maybe not built for my build. However there was still no OS.
I proceeded to download the stock J3 Emerge firmware.
It was in 4 parts which was really new to me. My GS5 only needed a AP Tar file to restore stock OS.
I put all files in Odin in proper places, and flash.
Odin fails, and Download mode gives SW Check Fail error.
SW Check Fail [aboot] : fused 3 / Binary 2.
I read a lot of forums and watched a lot of videos before writing all this and asking for help.
I cannot restore to stock, I cannot find another CFW to replace stock.
Any help is appreciated.
Click to expand...
Click to collapse
Did you do your NANDROID backup to the phone? If so, wiping it would of course wipe out your backup. If you chose a complete wipe, it would even wipe the sd card.
Doh!
I'm not laughing, I did this not long ago myself, and I've rooted dozens of devices.
I'll search for a solution to this, no promises.
ashyx said:
CFW?
You need a revision 3 firmware.
Click to expand...
Click to collapse
CFW=Custom FirmWare
Sent from my Samsung Galaxy Trend Plus using XDA Labs
I'm getting the same error. I was fortunate enough to have another device available and pulled a backup from that device. But I need to use Odin to flash a different modem to get WiFi working again. It currently won't turn on and stays greyed out. It's been a couple weeks since this topic was posted. Any luck getting Odin to work?
Sent from my SM-G950U using Tapatalk
equitube said:
Did you do your NANDROID backup to the phone? If so, wiping it would of course wipe out your backup. If you chose a complete wipe, it would even wipe the sd card.
Doh!
I'm not laughing, I did this not long ago myself, and I've rooted dozens of devices.
I'll search for a solution to this, no promises.
Click to expand...
Click to collapse
Any word by chance?
Sent from my SM-G950U using Tapatalk
lancemulvihill85 said:
Any word by chance?
Click to expand...
Click to collapse
You need a matching NON-HLOS.bin flashed to the APNHLOS partition. You can flash this with TWRP.
However if you'd have paid attention to my previous post all you need to do is flash the correct firmware with odin.
ashyx said:
You need a matching NON-HLOS.bin flashed to the APNHLOS partition. You can flash this with TWRP.
However if you'd have paid attention to my previous post all you need to do is flash the correct firmware with odin.
Click to expand...
Click to collapse
I can't figure out how to flash to that partition with twrp. Just zipping the .bin to .tar and flash just doesn't fly. I apologize for my ignorance in the matter. However I was paying attention, and read the few previous posts. My situation is a little different. The last 3 letters of the current firmware end in QL3. And I can't seem to find that build ANYWHERE. When using the sammobile app to figure out what it's currently running, the CSC partition is empty. I have no CSC. When googling how to flash a CSC with twrp, I run into dead ends about using Odin (which will not work for my build). I'll post screenshots in a lil bit if anyone would help. I'm at a loss right now
Sent from my SM-G950U using Tapatalk
---------- Post added at 05:49 PM ---------- Previous post was at 05:47 PM ----------
Basically, I have a working build, but WiFi is broken. It won't turn on. That's all I need. And I've been googling for about 2 weeks trying to figure this out
Sent from my SM-G950U using Tapatalk
lancemulvihill85 said:
I can't figure out how to flash to that partition with twrp. Just zipping the .bin to .tar and flash just doesn't fly. I apologize for my ignorance in the matter. However I was paying attention, and read the few previous posts. My situation is a little different. The last 3 letters of the current firmware end in QL3. And I can't seem to find that build ANYWHERE. When using the sammobile app to figure out what it's currently running, the CSC partition is empty. I have no CSC. When googling how to flash a CSC with twrp, I run into dead ends about using Odin (which will not work for my build). I'll post screenshots in a lil bit if anyone would help. I'm at a loss right now
Sent from my SM-G950U using Tapatalk
---------- Post added at 05:49 PM ---------- Previous post was at 05:47 PM ----------
Basically, I have a working build, but WiFi is broken. It won't turn on. That's all I need. And I've been googling for about 2 weeks trying to figure this out
Click to expand...
Click to collapse
You don't need to flash the same build, you just need the right revision and version of Odin.
What is the error on the device when flashing the firmware?

Categories

Resources