Develop Bugs

[Q] updating to 4.3 -> error -> note 2 bricked..help plz

Hi to all,
I tried to update the note 2 to the 4.3 version (india one). The rom flashing wasn't finished (it taken a lot of time, more than 1 hour and the laptop battery discharged).
Now when i switch on the note 2, it shows me the error: " firmware upgrade encountered"
I think it loaded the new bootloader, in fact if i boot my note in recovery mode it shows me "knox warranty void: 1".
I tried to flash the cwm recovery and now i'm able to boot it in recovery mode but i'm not able to mount the sd card (it mounts only as usb storage, not in the other mode).
I tried to flash the note 2 with:
- the factory rom: N7100XXDMB2_N7100OXADMA5_N7100XXDLK7_FACTORY_XEF.TAR
- using PIT: PIT_N7100_16GB_20121102.pit
but odin shows me this error:
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> modem.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> sboot.bin
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and on my note 2 there is an error: "unsupported version"
what can i do?
thanks

19malag83 said:
Hi to all,
I tried to update the note 2 to the 4.3 version (india one). The rom flashing wasn't finished (it taken a lot of time, more than 1 hour and the laptop battery discharged).
Now when i switch on the note 2, it shows me the error: " firmware upgrade encountered"
I think it loaded the new bootloader, in fact if i boot my note in recovery mode it shows me "knox warranty void: 1".
I tried to flash the cwm recovery and now i'm able to boot it in recovery mode but i'm not able to mount the sd card (it mounts only as usb storage, not in the other mode).
I tried to flash the note 2 with:
- the factory rom: N7100XXDMB2_N7100OXADMA5_N7100XXDLK7_FACTORY_XEF.TAR
- using PIT: PIT_N7100_16GB_20121102.pit
but odin shows me this error:
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> modem.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> sboot.bin
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and on my note 2 there is an error: "unsupported version"
what can i do?
thanks
Click to expand...
Click to collapse
Can you try formating SD card from recovery, i understand you are not able to mount but worth a try... i could format my ext sd card when i could not mount it

ameyamg said:
Can you try formating SD card from recovery, i understand you are not able to mount but worth a try... i could format my ext sd card when i could not mount it
Click to expand...
Click to collapse
Yes i' able to format it. Just do it. But after that, i'm not able to mount it.
I made a search, and i read that it could be a cwm recovery problem. I have to try with another recovery

Hey you wanted to upgrade right? So why don't you just flash that stock 4.3 mk4/mk3 rom with the new bootloader..? Because you already have the new bootloader, you can't do anything about it now...until dr ketan finds a way to downgrade
Sent from my GT-N7100 using XDA Premium 4 mobile app

manan999583 said:
Hey you wanted to upgrade right? So why don't you just flash that stock 4.3 mk4/mk3 rom with the new bootloader..? Because you already have the new bootloader, you can't do anything about it now...until dr ketan finds a way to downgrade
Sent from my GT-N7100 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes, it is what i'd like to do. But i'm not able. If i try to do it, odin shows me this error:
imageshack.us/photo/my-images/200/4nxc.png (add http before, sorry but i'm not able to insert a pic or a link because i have less then 10 posts )

UPDATE: using windows XP i wasn't able to flash the 4.3 rom. I try with Windows 7 and it works

Bricked my phone and need help

So, I've recently wanted to use a custom ROM for my phone, and I have done this before, but there's a bunch of changes I guess. I thought that "unified s3" meant that the ATT variants and others (including my i747m) would be compatible, so I tried to flash "Liquid Smooth v3.0" ROM but it didn't work with TWRP. So I got CWM and restored my phone (also my restore file by accident) so my phone was totally wiped, but I could flash the ROM. The problem occurs here, the phone WILL NOT boot, it is stuck at the "Samsung Galaxy S III" splash and won't go past it. I cannot delete the cache or anything without the phone restarting itself. I tried to flash a modem with Odin but get an error also.
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> modem.bin
<ID:0/003> NAND Write Start!!
<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!
<OSM> All threads completed. (succeed 0 / failed 1)
I've been searching the forums for a way to fix my i747m but I cannot find anything. Any solutions or is my phone dead. Also I can get into both recovery and download screen. I cannot flash a stock ROM because another error pops up. And when I go into download mode and flash, the "QUALCOMM SECUREBOOT: ENABLE" turns into "SECURE CHECK FAIL : aboot"

Tonamon said:
So, I've recently wanted to use a custom ROM for my phone, and I have done this before, but there's a bunch of changes I guess. I thought that "unified s3" meant that the ATT variants and others (including my i747m) would be compatible, so I tried to flash "Liquid Smooth v3.0" ROM but it didn't work with TWRP. So I got CWM and restored my phone (also my restore file by accident) so my phone was totally wiped, but I could flash the ROM. The problem occurs here, the phone WILL NOT boot, it is stuck at the "Samsung Galaxy S III" splash and won't go past it. I cannot delete the cache or anything without the phone restarting itself. I tried to flash a modem with Odin but get an error also.
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> modem.bin
<ID:0/003> NAND Write Start!!
<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!
<OSM> All threads completed. (succeed 0 / failed 1)
I've been searching the forums for a way to fix my i747m but I cannot find anything. Any solutions or is my phone dead. Also I can get into both recovery and download screen. I cannot flash a stock ROM because another error pops up. And when I go into download mode and flash, the "QUALCOMM SECUREBOOT: ENABLE" turns into "SECURE CHECK FAIL : aboot"
Click to expand...
Click to collapse
Since you can get into both download and recovery modes, there is plenty of hope and your phone is far from dead. Odin probably failed because you were trying to flash incompatible firmware or one that involved a bootloader downgrade attempt. You may be able to recover by re-flashing the correct firmware from (custom) recovery. You need to provide more information including what stock were you on before going custom and what stock you are now trying to revert to. When flashing stock firmware, however, you need to be sure you are working with the right ones. In spite of the near similarity in the names, firmware for the i747U... (AT&T) is different from the Canadian versions (i747M...) and you should be careful to pick only the ones specific to your phone model. You probably were on a 4.3 bootloader so your safest bet now may be to search for and download the i747M 4.3 stock rom, bootloader/modem and kernel zips and reflash these via recovery. If you are on TWRP, you may also do an advance wipe to remove all existing firmware before flashing new ones.

* N910AUCS2EQF1 * Full 4-File Odin 6.0.1 Firmware *

Hello!
Here is the full N910AUCS2EQF1 Odin manual update to 6.0.1 for everyone to enjoy. You can flash from any current version you have now it doesn't matter whether you are on 4.4.4, 5.1.1 or 6.0.1.
https://www.androidfilehost.com/?fid=745425885120746376
If for whatever reason you want to downgrade or don't like this build, you can safely downgrade to any of the below versions without any issues. After you flash a lower android version using Odin, phone might get stuck on AT&T logo. If that happens, all you need to do is boot into recovery and do a factory wipe/reset and phone will boot right up after that. Make sure you backup your data when upgrading or downgrading firmware so you don't loose any information..
N910AUCS2EQE1 (6.0.1) - https://www.androidfilehost.com/?fid=745425885120742009
N910AUCS2EPK4 (6.0.1) - https://www.androidfilehost.com/?fid=673368273298964563
N910AUCU2EPH5 (6.0.1) - https://www.androidfilehost.com/?fid=24651430732238073
N910AUCU2DOI2 (5.1.1) - https://www.androidfilehost.com/?fid=24438995911970946

Thanks. Will give it a try later.

Great job!
Does the Odin update wipe the phone?

Thanks for sharing this. I'm a few updates behind, so I presume this will be faster than installing multiple OTAs to get up to date.
Can someone recommend a safe download location for Odin? Some of the sites that come up in Google look a little shady. Thanks.

erm, which files go where? i get an error no matter where i put any file.

hello guys, anybody know how to backup full data if the phone dont have root ??

Flashing the firmware from Odin keeps failing.
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
It's happened this way 3 times thus far. I'm assuming it's an issue with the BL? I don't know...Could be very wrong. But it keeps failing.

help
Phone gets stuck at the logo even after full wipe

D3ATHSTALK3R said:
Phone gets stuck at the logo even after full wipe
Click to expand...
Click to collapse
for how long?

toutanje said:
Hello!
Here is the full N910AUCS2EQF1 Odin manual update to 6.0.1 for everyone to enjoy. You can flash from any current version you have now it doesn't matter whether you are on 4.4.4, 5.1.1 or 6.0.1.
If for whatever reason you want to downgrade or don't like this build, you can safely downgrade to any of the below versions without any issues. After you flash a lower android version using Odin, phone might get stuck on AT&T logo. If that happens, all you need to do is boot into recovery and do a factory wipe/reset and phone will boot right up after that. Make sure you backup your data when upgrading or downgrading firmware so you don't loose any information..
Click to expand...
Click to collapse
Tried this repeatedly now. fails every time. cant get past system. tried different cables, different usb ports. fails every time. every 3rd boot gets me an mmc_read_failed. I am on QF1 already, and was trying to correct a corrupted over the air install. anyone able to help?
<ID:0/007> Added!!
<ID:0/007> Odin engine v(ID:3.1203)..
<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> boot.img
<ID:0/007> recovery.img
<ID:0/007> system.img.ext4
<ID:0/007> FAIL! (Write)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse

Hello all, anyone successfully used this to upgrade their phone... from the above, it looks like not the case... thanks!

ridgemagnet said:
Hello all, anyone successfully used this to upgrade their phone... from the above, it looks like not the case... thanks!
Click to expand...
Click to collapse
Yea, it worked perfectly fine for me.

Thx, where is N910AUCS2EQG1?

Gxzn said:
Yea, it worked perfectly fine for me.
Click to expand...
Click to collapse
which file did you use?

Thanks. I use this to updgrade an old phone that still had the Marshmallow beta on it.

Can someone repost the download link for N910AUCS2EQF1 I tried downloading it I've been getting really slow speeds and it stops during the download

no matter what mine just fails every time. Is there anything we can do?

F3AR420 said:
no matter what mine just fails every time. Is there anything we can do?
Click to expand...
Click to collapse
Are you still having trouble with this?

Did anyone successfully rooted sm-n910a with 6.0.1 ? if so, how?

Worked for me.
Loaded AP files first then the other 3 files after all at once.
Upgraded to 6.01 from 5.01 . I was surprised at how easy the process was as I have no knowledge on this subject.

[HadesRom][A520F] No Sim Recognition

Hello,
I rooted my Samsung A520F with this HadesRom / Guide Klick
Everything worked fine but the only thing is, that my sim card is not recognised. I think the problem is the wrong bootloader.
Here are some Information:
Pic1
Pic2
From the Hadesrom I have the software of a A530F now.
Or is there another problem ?
Thanks in advance for you help!
StrohhutKevin

Did you update modem and bootloader to Oreo?
You need to do this if you came from N firmware or above

Baseminge said:
Did you update modem and bootloader to Oreo?
You need to do this if you came from N firmware or above
Click to expand...
Click to collapse
Thanks for the quick answer.
Ok. I think the problem is the bootloader.
I flashed the BL and CP from here for the A520F.
Flashing the CP was no problem, but when I want to flash the BL I get an Error in Odin:
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 5 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> param.bin
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and in the Download Window on the phone it says:
SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 8, BINARY: 4
I googled for that error message but I don't find the right solution. Maybe I understand it wrong.
Edit.: I found out that I already have the newest BL. The problem is that this version is further secured by Samsung. Here is a Guide how to get over this but I have no desire to do that so I flashed everything back to normal.
Thanks anyway @Baseminge
StrohhutKevin

StrohhutKevin said:
Thanks anyway @Baseminge[/B]
StrohhutKevin
Click to expand...
Click to collapse
Not at all man

StrohhutKevin said:
Thanks for the quick answer.
Ok. I think the problem is the bootloader.
I flashed the BL and CP from here for the A520F.
Flashing the CP was no problem, but when I want to flash the BL I get an Error in Odin:
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 5 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> param.bin
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and in the Download Window on the phone it says:
SW REV. CHECK FAIL(BOOTLOADER) DEVICE: 8, BINARY: 4
I googled for that error message but I don't find the right solution. Maybe I understand it wrong.
Edit.: I found out that I already have the newest BL. The problem is that this version is further secured by Samsung. Here is a Guide how to get over this but I have no desire to do that so I flashed everything back to normal.
Thanks anyway @Baseminge
StrohhutKevin
Click to expand...
Click to collapse
Hello brother how did you flashed everything back to normal ?
Can you please share the links for getting back to normal
I am also stuck on custom ROM without sim cards
I have tried everything but couldn't get back to stock ROM

H
kaustubh99 said:
Hello brother how did you flashed everything back to normal ?
Can you please share the links for getting back to normal
I am also stuck on custom ROM without sim cards
I have tried everything but couldn't get back to stock ROM
Click to expand...
Click to collapse
I found the original stock on this page
"This forum does not allow me to post an outside link because I'm a new. Maybe you can Google for updato com"
Problem is that the phone is still "rooted". But that didn't bother me in any way. Everything is just fine like before.
Hope this helps. I'm not at home so if you stuck in some point write again.
StohhutKevin

StrohhutKevin said:
H
I found the original stock on this page
"This forum does not allow me to post an outside link because I'm a new. Maybe you can Google for updato com"
Problem is that the phone is still "rooted". But that didn't bother me in any way. Everything is just fine like before.
Hope this helps. I'm not at home so if you stuck in some point write again.
StohhutKevin
Click to expand...
Click to collapse
Thanks bro I am back to normal
Only few Samsung features won't work but that's fine

SM-J600G bootloop after June 29.6.2020 security update

Hello, I was just wondering if anyone can help me fix this problem, anyways, I bought the phone it was on Android 9 Pie, I got the notification for software update, the phone was working fine, the owner said to me that there was a motherboard issue which I neglect and I'm fully sure that it's a software problem with the latest update, anyways, I downloaded and installed the update and when it finished It started going in nonstop bootloop, I tried flashing the device with the latest firmware, the Carier ID is: INS(INDIA), however when I try to flash the phone the Odin shows me this:
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 5716 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> param.bin
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Phone also says SW REV CHECK FAIL (Bootloader) Device 7, Binary: 6 after failed ODIN flashing
I know the error is saying to me that I'm trying to DOWN-grade the phone but it's the latest official firmware for the phone, i tried also flashing it with on BL and AP in Odin and Z3x tools, however when I try to flash it in Z3X tool and when I insert only AP and BL the loading on the phone goes to the middle, and sometimes Z3X tool shows that the flashing is done but it's still in a Bootloop.
Honestly I'm desperate for the help, any kind of help will be appreciated, if someone knows how to help and needs fruther information, feel free to ask.
Thanks in advance!
Also I cannot enter to Recovery Mode the phone either goes to Download Mode or constant bootloop

Well, i think the phone has the wrong CSC or something else.
I was seeing the SW REV CHECK FAIL part and it seems like that the phone's binary is U7, but firmware is U6, meaning that the phone has a different CSC.
If it's possible, flash another firmware with a different CSC, but with U7.
And tell if it works.

Do you have any link to U7 firmware I tried flashing with like 10 combinations, none of them worked, I was searching for U7 firmware but i couldn't find it, I haven't slept for 3 days trying to fix it, or if you can tell me how can I recognize the file combination has the U7 firmware, I think there's a some trick in reading the symobols in combination files but I don't know, thanks for replying!