Dear friends, it's the first time that I write a thread seeking your help.
I purchased my note 4 N910H 5.1.1 few weeks ago and I discovered that battery drains in a horrible fast way even if it is turned off (6 to 7 hours max). I read that many people had the same problem and that after a downgrade to kitkat this issue was solved. So I decided to do so.
I tried all methods I found on forums; all files I found on sammobile. No success.
I only could install 2 files..
1- N910HXXU2COJ4_N910HOLB2COJ2_N910HXXU1COJ2_HOME.tar is a 5.1.1 with CSC from Cambodia (CAM). I don't think it is the good one coz after installing it I could not do an update with kies (shows an unknown error).
2- N910HXXU2COJ4_N910HOJV2COJ1_N910HXXU1COJ2_HOME.tar is also a 5.1.1 with CSC from Iraq (MID). With it, kies accepted to update firmware without problems, so I think it's the good one.
I also found a 4 files ROM N910HXXU1ANJ4_OLB1ANJ4 it is a kitkat ROM but can not be flashed (Odin shows nand writing error). I tries to flash this rom without loading Bootloader file.. it worked but phone was stuck on a bootloop and could start again only after flashing 5.1.1 ROM.
I think that bootloader is locked or secured somehow and refuses all roms.
What is the solution? is there an other kitkat ROM with same actual bootloader maybe? is there a way to change bootloader version?
dzeus11 said:
Dear friends, it's the first time that I write a thread seeking your help.
I purchased my note 4 N910H 5.1.1 few weeks ago and I discovered that battery drains in a horrible fast way even if it is turned off (6 to 7 hours max). I read that many people had the same problem and that after a downgrade to kitkat this issue was solved. So I decided to do so.
I tried all methods I found on forums; all files I found on sammobile. No success.
I only could install 2 files..
1- N910HXXU2COJ4_N910HOLB2COJ2_N910HXXU1COJ2_HOME.tar is a 5.1.1 with CSC from Cambodia (CAM). I don't think it is the good one coz after installing it I could not do an update with kies (shows an unknown error).
2- N910HXXU2COJ4_N910HOJV2COJ1_N910HXXU1COJ2_HOME.tar is also a 5.1.1 with CSC from Iraq (MID). With it, kies accepted to update firmware without problems, so I think it's the good one.
I also found a 4 files ROM N910HXXU1ANJ4_OLB1ANJ4 it is a kitkat ROM but can not be flashed (Odin shows nand writing error). I tries to flash this rom without loading Bootloader file.. it worked but phone was stuck on a bootloop and could start again only after flashing 5.1.1 ROM.
I think that bootloader is locked or secured somehow and refuses all roms.
What is the solution? is there an other kitkat ROM with same actual bootloader maybe? is there a way to change bootloader version?
Click to expand...
Click to collapse
hey, maybe a twrp backup as you can read in:
https://forum.xda-developers.com/no...-stock-rom-t3255649/post63975652#post63975652
if you find it let me know
Related
Two days ago i bought Samsung Galaxy Note 2 N7100 (international). It had android 4.1.2 but i saw there is available update. After update to official android 4.3 my phone lost signal and started showing me "Not registered on network". 1 day passed since i am searching how to fix this thing. Tried custom rom (4.4.2) and still the same. I went back to official 4.3 for UK O2 , successfully rooted it, passed knox, installed busybox, installed ARIZA Patch. Still the same. Tried to flash MJ5 bootloader via ODIN but it shows me FAIL. And after every FAIL my phone is bricked so i am flashing all over again official ROM. I have NO backups of my EFS (in my search i saw that i need some EFS to repair this thing). I got no issue with WI-FI but only with network. If i revert back to stock android 4.1.2 will i be able to call somebody? If the answer is "YES", would somebody tell me how? I saw in some threads that with new 4.3 ROM note 2 got knox locked bootloader which is impossible to be downgraded. Please, give me guide step by step what to do to repair my phone by myself. Thank you in advance.
I would suggest you to take an efs backup on 4.1. Then flash 4.3 and if you aren't getting network try restoring your efs backup. That might solve your problem.
Hi everybody!
I have a big problem with my S4 mini Duos i9192, so I´ll try to explain everything as better as I can:
The phone is NEW, i bought it a week ago in Chile and I bring it to Argentina. It was working fine (both sim cards, wi fi, camera, etc..) until it started to reboot like crazy.
I discovered that it could be solved with a simple factory wipe, but I did it without any success. After that I found somewhere that sometimes this could be solved with an update of the firmware. I dont know what my factory firmware was (Yes, I´m a newbie), but I downloaded I9192XXUCNG2 from SamMobile and flashed it with Odin3 following all the steps. It wasn´t any update available in KIES, so I decided to try that russian Kit Kat version.
It didn´t solve my problem, so I flashed it several times, like 10 times.. and until now I still stuck like before. Then I tryed to flash other Jelly Bean versions (I9192UBUBND1, I9192UBUBNA2, I9192UBUBND2, I9192UBUBMK5), but I wasn't allowed to proceed so I am now stuck in Kit Kat and dont know how to do a downgrade to solve my problem someway.
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
Dont know what to do.. could it be a hardware problem? The moments when the phone is working without rebooting everything looks fine.
Help please! & Thanks for reading! :good:
Yenien said:
Hi everybody!
I have a big problem with my S4 mini Duos i9192, so I´ll try to explain everything as better as I can:
The phone is NEW, i bought it a week ago in Chile and I bring it to Argentina. It was working fine (both sim cards, wi fi, camera, etc..) until it started to reboot like crazy.
I discovered that it could be solved with a simple factory wipe, but I did it without any success. After that I found somewhere that sometimes this could be solved with an update of the firmware. I dont know what my factory firmware was (Yes, I´m a newbie), but I downloaded I9192XXUCNG2 from SamMobile and flashed it with Odin3 following all the steps. It wasn´t any update available in KIES, so I decided to try that russian Kit Kat version.
It didn´t solve my problem, so I flashed it several times, like 10 times.. and until now I still stuck like before. Then I tryed to flash other Jelly Bean versions (I9192UBUBND1, I9192UBUBNA2, I9192UBUBND2, I9192UBUBMK5), but I wasn't allowed to proceed so I am now stuck in Kit Kat and dont know how to do a downgrade to solve my problem someway.
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
Dont know what to do.. could it be a hardware problem? The moments when the phone is working without rebooting everything looks fine.
Help please! & Thanks for reading! :good:
Click to expand...
Click to collapse
you are now stock into kitkat you cant go back ... try to flash kitkat through odin several times is the only solution
..and next time please read before proceding any upgrade :fingers-crossed:
rrgrrg said:
you are now stock into kitkat you cant go back ... try to flash kitkat through odin several times is the only solution
..and next time please read before proceding any upgrade :fingers-crossed:
Click to expand...
Click to collapse
OK, thanks for the advice.
I´m worried because the problem emerged in JB and in KK it keeps bothering...
Now I dont know if the guys of the service will reject my phone alluding that I modified the firmware :crying:
Any other comments will be welcomed.
Regards.
Yenien said:
Hi everybody!
I have a big problem with my S4 mini Duos i9192, so I´ll try to explain everything as better as I can:
The phone is NEW, i bought it a week ago in Chile and I bring it to Argentina. It was working fine (both sim cards, wi fi, camera, etc..) until it started to reboot like crazy.
I discovered that it could be solved with a simple factory wipe, but I did it without any success. After that I found somewhere that sometimes this could be solved with an update of the firmware. I dont know what my factory firmware was (Yes, I´m a newbie), but I downloaded I9192XXUCNG2 from SamMobile and flashed it with Odin3 following all the steps. It wasn´t any update available in KIES, so I decided to try that russian Kit Kat version.
It didn´t solve my problem, so I flashed it several times, like 10 times.. and until now I still stuck like before. Then I tryed to flash other Jelly Bean versions (I9192UBUBND1, I9192UBUBNA2, I9192UBUBND2, I9192UBUBMK5), but I wasn't allowed to proceed so I am now stuck in Kit Kat and dont know how to do a downgrade to solve my problem someway.
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x0
Dont know what to do.. could it be a hardware problem? The moments when the phone is working without rebooting everything looks fine.
Help please! & Thanks for reading! :good:
Click to expand...
Click to collapse
If I were in your shoes I'd try:
1. root the phone
2. install CWM recovery
3. install CyanogenMod 11, KitKat 4.4.4
All this is available for I9192. You can find proper procedures on XDA.
FearFac said:
If I were in your shoes I'd try:
1. root the phone
2. install CWM recovery
3. install CyanogenMod 11, KitKat 4.4.4
All this is available for I9192. You can find proper procedures on XDA.
Click to expand...
Click to collapse
Thanks..
I'll try that if I have no luck with Samsung Technical Support
did anything help you to solve it ? I'm from ARG as you are and I brought my I9192 from Panama and I have exactly the same problem even with CM12 (lollipop).
Cheers
Hello,
I'm a noob but usually try to fix this kind of issues on my own, looking at the boards, following tutorials, learning, but this time I think I'm not able to find a solution on my own so I'm asking for advice here.
Some time ago I installed cyanogenmod 10.1 on my Note 2 LTE and was happy with it for some month, than last week I tried to upgrade to cm12.1 It worked but there where some issues and bugs, mainly I wasn't able to swap internal/external sd cards.
So I decided to go back to latest available stock rom 4.4.2 from sammobile.
Here is where the problem starts. The stock 4.4.2 resulter in a bootloop, tried cache/dalvik/factory reset, flash again, whipe again.. nothing.
The phone is not able to get past the white label "Samsung Note 2 gt-n7105" screen. It goes black than the white label again and again.
It doesn't even get to the Samsung animated logo.
Ok bottloop, no problem, try to flash again something else.
I tried different Custom roms, different kernels, different flashing methods. I can flash anything with no problem but every time a get a bootloop.
During the various attempts knox fired, but I don't care. I don't know if this could be the cause.
Actually the only firmware that works is the original oldest STOCK 4.1.2, every other stock firmware past that or any custom rom is bootlooping the same way. To fix I only can reinstall stock 4.1.2 with odin.
I really need any advice or hint.
At the moment my goal is to get at least to stock 4.3 but I cant.........
Thanks!
When you first bought your phone, did it come with Knox?
ErnestChia said:
When you first bought your phone, did it come with Knox?
Click to expand...
Click to collapse
nope it doesn't existed before, but now I can see it when I boot in download mode "knox warranty void:1"
Try to get the latest firmware available via kies ,that worked for me
http://forum.xda-developers.com/showthread.php?t=2088809/[URL]
From what you've described, I think the Stock ROM 4.4.2 from Sammobile contained a bootloader update. So when you flashed this ROM, it updated your bootloader from the non-Knox version to the Knox version.
I am very unfamiliar with the technical details of Knox, but I think the new Knox bootloader is causing your bootloop problem.
However, I don't know why 4.1.2 works when everything else doesn't work!
Can you check the Stock ROM 4.4.2, and see whether it really contains a bootloader update?
mysuperdonghae said:
Try to get the latest firmware available via kies ,that worked for me
http://forum.xda-developers.com/sho...can flash cm10, 11 and 12 with no issue too..
Click to expand...
Click to collapse
misthero said:
I think so, there is a boot.im, anyway I also discovered that I can flash cm10, 11 and 12 with no issue too..
Click to expand...
Click to collapse
Since a boot.img is present, it means that it would flash your boot partition. So now we know for sure that when you attempted to flash the Stock ROM 4.4.2, your bootloader was changed to the Knox version.
So the lesson here is: before you flash anything via ODIN, always check to see if there is a bootloader update. Usually you don't want to be changing the bootloader on your phone.
***
So now there are 2 possible ways to reach your goal:
1) Keep your new bootloader and see whether you can get Stock 4.3 or Stock 4.4.2 running on your phone
2) Try to restore your old bootloader
As I said earlier, I'm not familiar with the technical details of Knox, so I'm not sure how to get Stock 4.3 or Stock 4.4.2 running on your phone when your Knox indicator is already 0x1. You need someone else to help you.
And you can only restore your old bootloader if you happen to have made a copy of your boot partition before you flashed the Stock ROM 4.4.2. Even if you did have a copy of your original boot partition, I'm not confident with helping you to restore your old bootloader. You need someone else to help you in this case too.
Conclusion: I don't think I can help you to solve your problem I'm sorry. Hopefully someone else who is more of a pro than me will come along to help you out.
Good luck!
Hello everyone,
A little while ago I purchased a note 5 and I kept getting a knox unauthorized access warning...so I downloaded the knox status app and noticed that the firmware and baseband were different (see attached photo) I've even attempted an OTA update and also through smart switch (OTA failed and the later shows as up to date) what do I do
There's a way to flash back to PB2 using ODIN. You'll have to find the 4 files you need, plus ODIN to flash them. Do you know how to use Odin?
I haven't been on here in quite a while so I don't remember exactly which thread they're in. I may have them saved on my computer but I'll have to look. I don't mind sharing them if I still have them.
Mr_Edwards said:
Hello everyone,
A little while ago I purchased a note 5 and I kept getting a knox unauthorized access warning...so I downloaded the knox status app and noticed that the firmware and baseband were different (see attached photo) I've even attempted an OTA update and also through smart switch (OTA failed and the later shows as up to date) what do I do
Click to expand...
Click to collapse
Just flash the BP3 bootloader one since it says 2 right now.. This will solve the problem just download the BP3 firmware and extract the boot.img and flash it through odin.
I do see that he has an eng kernel though and I think maybe @TechNyne66 would be interested in looking at that.
I'm still running OGG bootloader as far as I know. Just flash marshmallow from odin. Forget about OTA, it sucks and causes problems.
I was trying to root my samsung galaxy a5 2017 with TWRP and I accidentally deleted system data. Then, I tried rebooting the phone and it got stuck in a bootloop. To fix this problem I tried flashing stock 8.0 firmware from sammobile via odin and I got this error:
Sw rev. Check fail. Device: 6, binary 5. I think that this means I have to flash the latest stock firmware but there isn't a newer one.
After that, I tried to use my phone by flashing a custom rom (Lineage 15.1) and I discovered that I have no imei,no baseband and no ip adress. I have installed many custom roms but the issue is still there. I am trying to get my phone to work with stock firmware and fix the IMEI issue but odin wont let me flash because of that error. I would appreciate if anyone could help. Thanks.
Flash a firmware version that contains S6 or U6 in the middle, it won't work with U5/S5! Not the Samsung phone S5 or S6, but rather, the firmware version.
For cellular, change the modem firmware, or backup and wipe /data/. /data/data/?.
Unless the efs was wiped (probably not if the baseband version isn't there, load a backup then, only if the efs was wiped don't restore it otherwise, and it must not be a backup created with an older twrp, view the recovery log in the backup folder)
julianmunozvaras said:
I was trying to root my samsung galaxy a5 2017 with TWRP and I accidentally deleted system data. Then, I tried rebooting the phone and it got stuck in a bootloop. To fix this problem I tried flashing stock 8.0 firmware from sammobile via odin and I got this error:
Sw rev. Check fail. Device: 6, binary 5. I think that this means I have to flash the latest stock firmware but there isn't a newer one.
After that, I tried to use my phone by flashing a custom rom (Lineage 15.1) and I discovered that I have no imei,no baseband and no ip adress. I have installed many custom roms but the issue is still there. I am trying to get my phone to work with stock firmware and fix the IMEI issue but odin wont let me flash because of that error. I would appreciate if anyone could help. Thanks.
Click to expand...
Click to collapse
You aren't flashing the current version of software.
Sent from my Samsung SM-A520W using XDA Labs
iloveoreos said:
You aren't flashing the current version of software.
Sent from my Samsung SM-A520W using XDA Labs
Click to expand...
Click to collapse
I tried installing the latest version available and I had the same error.
julianmunozvaras said:
I tried installing the latest version available and I had the same error.
Click to expand...
Click to collapse
Well, I don't know what else could be wrong.
Sent from my Samsung SM-A520W using XDA Labs
julianmunozvaras said:
I tried installing the latest version available and I had the same error.
Click to expand...
Click to collapse
Listen to me, it happened to me 2 days ago, and I came to the conclusion that I was not flash the latest firmware. You need to flash the same firmware with the same bootloader or more recent, the error you receive is because you are flashing an older version of bootloader. Do one thing, type the code *#1234# on the phone keypad
mark the code that gives you on 'AP and look it on Sammobile at https://www.sammobile.com/firmwares/galaxy-a5/SM-A520F/ITV/ select your language and look for the firmware with your own code . You will see that odin flash it.
Samsung A520F Custom Binary Error
Hello please I have been trying to reload my Samsung A520F firmware for a couple of weeks
It all started with the phone trying to update (over WIFI) and somewhere along the line files must have gotten corrupted
This led to the phone constantly restart and shutting down applications
I decided to just download the firmware and use Odin to reload. This, unfortunately, didn't go so well as now the phone isn't starting up anymore but can still get to download mode.
PDA firmware is A520FXXUACSE6
Region is EUR
Network is OPEN
every time I use this firmware I get the error
" Custom binary (BOOT) Blocked by FRP Lock
Please note currently at the moment phone refuses to boot up I read about removing OEM lock and don't know if this is the problem.
Please could you help out
koolblowkid said:
Hello please I have been trying to reload my Samsung A520F firmware for a couple of weeks
It all started with the phone trying to update (over WIFI) and somewhere along the line files must have gotten corrupted
This led to the phone constantly restart and shutting down applications
I decided to just download the firmware and use Odin to reload. This, unfortunately, didn't go so well as now the phone isn't starting up anymore but can still get to download mode.
PDA firmware is A520FXXUACSE6
Region is EUR
Network is OPEN
every time I use this firmware I get the error
" Custom binary (BOOT) Blocked by FRP Lock
Please note currently at the moment phone refuses to boot up I read about removing OEM lock and don't know if this is the problem.
Please could you help out
Click to expand...
Click to collapse
Obviously you are frp locked. But I didn't think that blocked from flashing official.