Develop Bugs

MJ5 bootloader flash problems

Hi guys!
I hope that I chose the right forum to ask my question: I installed this rom onto my Note 2 LTE N7105, but now I don't have wifi (as the text in the rom description says). Before I flashed the rom, I had installed Devils Rom (deodexed and deknoxed 4.3 stock) with the devils kernel (based on MK5). I thought that the bootloader will be kept, because I already installed a wifi hotfix for that bootloader.
Now I have the new 4.4 rom installed, it works fine - except for wifi. If I got this right (if not, correct me) - flashing the MJ5 bootloader will solve the problem and I won't have KNOX triggered (now I have a "MA5" bootloader). So I tried to flash the MJ5 bootloader with ODIN 3.09 but it keeps failing. The drivers are installed, I can access the download menu. My pc recognizes the phone as COM5, but when I load the bootloader and click on flash, almost instantly a red FAIL appears in the first block. The output says "writing NAND..." and then "FAILED".
Now I am a bit confused - does the MJ5 bootloader work with the Note 2 LTE or only the non- LTE version? Are there any other ways to get wifi to work? If there's now way around, I am willing to trigger my knox.
Thanks in advance, I hope you can help a very confused user

Im having the same problems. odin is giving no love on updating the bootloader

Kenny_ken said:
Hi guys!
I hope that I chose the right forum to ask my question: I installed this rom onto my Note 2 LTE N7105, but now I don't have wifi (as the text in the rom description says). Before I flashed the rom, I had installed Devils Rom (deodexed and deknoxed 4.3 stock) with the devils kernel (based on MK5). I thought that the bootloader will be kept, because I already installed a wifi hotfix for that bootloader.
Now I have the new 4.4 rom installed, it works fine - except for wifi. If I got this right (if not, correct me) - flashing the MJ5 bootloader will solve the problem and I won't have KNOX triggered (now I have a "MA5" bootloader). So I tried to flash the MJ5 bootloader with ODIN 3.09 but it keeps failing. The drivers are installed, I can access the download menu. My pc recognizes the phone as COM5, but when I load the bootloader and click on flash, almost instantly a red FAIL appears in the first block. The output says "writing NAND..." and then "FAILED".
Now I am a bit confused - does the MJ5 bootloader work with the Note 2 LTE or only the non- LTE version? Are there any other ways to get wifi to work? If there's now way around, I am willing to trigger my knox.
Thanks in advance, I hope you can help a very confused user
Click to expand...
Click to collapse
Did you try to flash the kernel as stated in the installation instructions of the rom that your trying to install?

I have the agni kernel as it is the only way to get the wifi to work without the bootloader, which im trying to get too. For the life of me i cannot figure out why odin doesnt want to flash the bootloader. mj5 or nd3 makes no difference. according to info app my boot loader version is N7105ZHALJ4. Do I need to step up 'slower'?
I want to go to any of those recent bootloaders so wifi will work normally. It seems slow on the agni kernel but at least it works.

TeamFox said:
I have the agni kernel as it is the only way to get the wifi to work without the bootloader, which im trying to get too. For the life of me i cannot figure out why odin doesnt want to flash the bootloader. mj5 or nd3 makes no difference. according to info app my boot loader version is N7105ZHALJ4. Do I need to step up 'slower'?
I want to go to any of those recent bootloaders so wifi will work normally. It seems slow on the agni kernel but at least it works.
Click to expand...
Click to collapse
AFAIK you can't install Agni Kernel using Odin. Instead use your Custom Recovery to install that kernel, under "Install Zip from Storage" option of your custom recovery. HTH.

asin_punk said:
AFAIK you can't install Agni Kernel using Odin. Instead use your Custom Recovery to install that kernel, under "Install Zip from Storage" option of your custom recovery. HTH.
Click to expand...
Click to collapse
To clear things up i have already got agni kernel installed via recovery. I just cant update my bootloader via odin.

problem flashing mj5 bootloader and agni kernel too
i am on phoenix rom v18.8
cannot figure out if i am on mj5 bootloader
how to check my bootloader version?
secondly, i m trying to flash mj5 via odin but it says FAILED
Trying to flash agni kernel via odin and mobile odin,, it says success but when i check in my phone, nothing is done...
where am i going wrong?
pls help

anandsaurabh said:
i am on phoenix rom v18.8
cannot figure out if i am on mj5 bootloader
how to check my bootloader version?
secondly, i m trying to flash mj5 via odin but it says FAILED
Trying to flash agni kernel via odin and mobile odin,, it says success but when i check in my phone, nothing is done...
where am i going wrong?
pls help
Click to expand...
Click to collapse
Agni kernel is only flashable via recovery not with odin.. Its a zip file.. U can flash it using CWM or Philz Or twrp recoveries
Sent from my GT-N7100 using XDA Premium 4 mobile app

U r right hazin ... That file can be flashed only via recovery... But I m not able to flash it.. It goes into aroma installer, does its work and says done but does not show on settings... I e saved log file too of that process...

So no answer on this question yet?? I'm also trying to flash the MJ5 bootloader using Odin, no luck though.
Can anyone explain why it keeps failing?

did you fix the problem ?
apuntigam said:
So no answer on this question yet?? I'm also trying to flash the MJ5 bootloader using Odin, no luck though.
Can anyone explain why it keeps failing?
Click to expand...
Click to collapse
having the same thing now...

Davids said:
having the same thing now...
Click to expand...
Click to collapse
No, I never managed to fix it. I think I found out in the end that there never was an MJ5 bootloader for the GT-N7105 (the international LTE version). There was only an MJ5 bootloader for the non-LTE version, the GT-N7100. And of course, that phone's bootloader will never work on the N7105.
So we're out of luck it appears

so the phone is dead ?
apuntigam said:
No, I never managed to fix it. I think I found out in the end that there never was an MJ5 bootloader for the GT-N7105 (the international LTE version). There was only an MJ5 bootloader for the non-LTE version, the GT-N7100. And of course, that phone's bootloader will never work on the N7105.
So we're out of luck it appears
Click to expand...
Click to collapse
noting to do to bring back wifi&BT ?

Davids said:
noting to do to bring back wifi&BT ?
Click to expand...
Click to collapse
All of the new KitKat ROMs have fixes built in for that. Some of the Lollipop ROMs also fix this, so you don't really need that bootloader.

apuntigam said:
All of the new KitKat ROMs have fixes built in for that. Some of the Lollipop ROMs also fix this, so you don't really need that bootloader.
Click to expand...
Click to collapse
can you give me a link pls for somthing that works ?
i am Desperate a week with no wifi BT
THX

Davids said:
can you give me a link pls for somthing that works ?
i am Desperate a week with no wifi BT
THX
Click to expand...
Click to collapse
I'm on NamelessROM 5.0.2 at the moment, works fine for me. I'd probably recommend that one, battery life is also great. It's in the N7105 development forum. :good:
I was also on CM11 official, worked like a charm. There are a number of 4.4.4 ROMs in the N7105 development forum that were quite mature and worked well.

apuntigam said:
I'm on NamelessROM 5.0.2 at the moment, works fine for me. I'd probably recommend that one, battery life is also great. It's in the N7105 development forum. :good:
I was also on CM11 official, worked like a charm. There are a number of 4.4.4 ROMs in the N7105 development forum that were quite mature and worked well.
Click to expand...
Click to collapse
i have the 7100..
somthing for that device..

Davids said:
i have the 7100..
somthing for that device..
Click to expand...
Click to collapse
Ok, then it's a completely different discussion... not sure why the bootloader would be failing in that case, since it was built for that device. You could try a different Odin? (Assuming of course that your are NOT trying to DOWNGRADE the bootloader... it's well known that you can't downgrade the bootloarder to MJ5 from something more recent).
Otherwise, I'm sure there are equally useful ROMs for the N7100 in the Note 2 Original Development forum.
But, since your device is probably pretty old and almost certainly out of warranty by now, I would seriously consider flashing the latest official Samsung ROM to get the latest bootloader and then flash whatever you want on top of that. Voiding the warranty is irrelevant if you're already out of warranty. But, I have heard that even with the latest bootloader some people still have trouble with wifi and BT. In that case all I can suggest is playing around with different ROMs until you find something that works for you. As I'm not a N7100 user I can't really offer more advice than that, sorry man.

Guys where I can find a REAL WORKING link to download mj5 or higher bootloader??
I tried a lot & most of them are obselete

Maybe downnload the latest stock ROM from sammobile.com and extract the bootloader?
https://www.sammobile.com/firmwares/database/GT-N7105/

Stuck in boot screen

I unlocked my bootloader, installed custom recovery and rooted my phone so that I can install custom ROMS.
However, when I install a custom rom phone does not boot. It will get stuck on the HTC logo screen. I tried Android Revolution, InsertCoin and SkyDragon roms with same result.
I also tried to flash boot.img via fastboot with no joy.
I have S-ON (I tried to turn S-off but that attempt failed as well)
Can somebody please help me before I bust this phone up?

sti-06 said:
I unlocked my bootloader, installed custom recovery and rooted my phone so that I can install custom ROMS.
However, when I install a custom rom phone does not boot. It will get stuck on the HTC logo screen. I tried Android Revolution, InsertCoin and SkyDragon roms with same result.
I also tried to flash boot.img via fastboot with no joy.
I have S-ON (I tried to turn S-off but that attempt failed as well)
Can somebody please help me before I bust this phone up?
Click to expand...
Click to collapse
I know this definitely happens with Android Revolution, but if you leave it alone for long enough, it will boot. I am running SkyDragon now, and it seems to work just fine. Even though I am S-Off'd, it should still work for you since you have an unlocked bootloader. Can you post a screenshot of your phone in bootloader mode?

It might be because of your firmware. Do you happen to be on Verizon?

MrKhozam said:
I know this definitely happens with Android Revolution, but if you leave it alone for long enough, it will boot. I am running SkyDragon now, and it seems to work just fine. Even though I am S-Off'd, it should still work for you since you have an unlocked bootloader. Can you post a screenshot of your phone in bootloader mode?
Click to expand...
Click to collapse
You are right. I just found out that I was not waiting long enough for it to boot. However, everytime I restart the phone it takes almost 10 minutes for phone to boot but I shut it down and start, it would start.
Now, I dont cannot get root on SkyDragon. SuperSU says "The SU binary needs to be updated. Continue?" I would hit continue and hit "normal". I get "Installation Failed! Please reboot and try again" error message....Ugh this has been very frustrating...

sti-06 said:
You are right. I just found out that I was not waiting long enough for it to boot. However, everytime I restart the phone it takes almost 10 minutes for phone to boot but I shut it down and start, it would start.
Now, I dont cannot get root on SkyDragon. SuperSU says "The SU binary needs to be updated. Continue?" I would hit continue and hit "normal". I get "Installation Failed! Please reboot and try again" error message....Ugh this has been very frustrating...
Click to expand...
Click to collapse
I had the EXACT same thing happen. How I resolved the SuperSU problem: flash the SuperSU 1.94 zip in recovery. How I solved the slow as hell boot problem: go to Settings > Power and disable Fast Boot. Good luck!

babtron said:
It might be because of your firmware. Do you happen to be on Verizon?
Click to expand...
Click to collapse
I am on ATT

MrKhozam said:
I had the EXACT same thing happen. How I resolved the SuperSU problem: flash the SuperSU 1.94 zip in recovery. How I solved the slow as hell boot problem: go to Settings > Power and disable Fast Boot. Good luck!
Click to expand...
Click to collapse
Excellent! Flashing the SuperSU has resolved the root issue. Thank you!!
But the slow boot is still there even though I unchecked fast boot.

Check your firmware version.

babtron said:
Check your firmware version.
Click to expand...
Click to collapse
+1

babtron said:
Check your firmware version.
Click to expand...
Click to collapse
MrKhozam said:
+1
Click to expand...
Click to collapse
If the firmware version = build number then it is 2.22.1540.4

sti-06 said:
If the firmware version = build number then it is 2.22.1540.4
Click to expand...
Click to collapse
I had the same problem.. what fixed it for me was getting on my stock ROM and doing HTC's OTA update to 4.4.3. This updates your firmware and make it compatible with newer firmware ROMs (such as Android Revolution) To do the OTa if you don't know how I recommend restoring a stock nandroid , flash the stock recovery and you should be ggod to go.

ILIVE4HEAD said:
I had the same problem.. what fixed it for me was getting on my stock ROM and doing HTC's OTA update to 4.4.3. This updates your firmware and make it compatible with newer firmware ROMs (such as Android Revolution) To do the OTa if you don't know how I recommend restoring a stock nandroid , flash the stock recovery and you should be ggod to go.
Click to expand...
Click to collapse
I checked to see if there is an OTA update before I flashed a custom ROM and there was none. Can I just flash a stock rom with an updated firmware? If so where can I find the latest firmware?

Newbie here, I think I soft bricked my phone

Hey, I don't really understand what I did but I'll try to explain. So I downloaded kingroot rooted my phone, but I wanted to switch from kingroot to supersu I followed a guide, but what I didn't realise was that the guide had a warning saying that the version of supersu.me they linked to wasn't working with phones with latest Android version (I have 5.0). So I used supersu.me it said it worked, opened supersu it told me it needed to update the binaries I said okay, and chose normal mode. Then it said failed need to reboot it rebooted my phone.
Now at first it got stuck in a bootloop I entered recovery mode and factory reset it. Now it turns but nothing on touchscreen only Wi-Fi no signal and time on top and home button below
I have an lg h735
Please help

Flash stock or reflash custom ROM

pinn___________ said:
Flash stock or reflash custom ROM
Click to expand...
Click to collapse
Okay i'm a bit new to this, i did this all through my phone, how can i flash stock ?

Shepperton said:
Okay i'm a bit new to this, i did this all through my phone, how can i flash stock ?
Click to expand...
Click to collapse
Download the stock rom, reboot to recovery and flash or flash through Odin.

Help needed ! stuck in Bootloop

Hey guys. Today I tried rooting for the first time using this guide
In the third step of the article "3.Flashing TWRP and Rooting via TWRP" I pressed cancel when it asks for an encryption password(I hadn't put one yet). I also flashed the english TWRP( Recovery file) and not the one provided in the article . Now the phone just wont boot. Whenever I try to boot it, it gives me the error message:
"Your device has been unlocked and cannot be trusted.
ID: N/A"
And TWRP comes up everytime .
When i try booting from factory it shows:
"Your device has been unlocked and cannot be trusted.
ID: bad key"
and TWRP comes up.
The phone is still recognized in adb.I still haven't flashed SuperSU if that helps.
Should i Flash stock recovery and try again ?
Please send help, guys.

porthumor said:
Hey guys. Today I tried boot for the first time using this guide
In the third step of the article "3.Flashing TWRP and Rooting via TWRP" I pressed cancel when it asks for a password. I also flashed the english TWRP( Recovery file) and not the one provided in the article . Now the phone just wont boot. Whenever I try to boot it, it gives me the error message:
"Your device has been unlocked and cannot be trusted.
ID: N/A"
And TWRP comes up everytime .
When i try booting from factory it shows:
"Your device has been unlocked and cannot be trusted.
ID: bad key"
and TWRP comes up.
The phone is still recognized in adb.I still haven't flashed SuperSU if that helps.
Should i Flash stock recovery and try again ?
Please send help, guys.
Click to expand...
Click to collapse
I have similar problem like yours. The solution to boot your drvice. If your in twrp go to advance - reboot - bootloader. And in bootloader menu click start. And your phone now is booted
This is a alternative solution. But it wont damage your device. Trust me

Kap_Tutan said:
I have similar problem like yours. The solution to boot your drvice. If your in twrp go to advance - reboot - bootloader. And in bootloader menu click start. And your phone now is booted
This is a alternative solution. But it wont damage your device. Trust me
Click to expand...
Click to collapse
Tried this . It displays :
"Your device has been unlocked and cannot be trusted.
ID: bad key"
Reboots to show :
"Your device has been unlocked and cannot be trusted.
ID: N/A"
and goes into TWRP .

I think you need to flash new logo bin from here
https://forum.xda-developers.com/moto-z-play/themes/logo-bin-t3538153

mijing said:
I think you need to flash new logo bin from here
https://forum.xda-developers.com/moto-z-play/themes/logo-bin-t3538153
Click to expand...
Click to collapse
How will flashing a new logo help me get out of boot loop ? AFAIK it only replaces the warning.

porthumor said:
How will flashing a new logo help me get out of boot loop ? AFAIK it only replaces the warning.
Click to expand...
Click to collapse
I am not sure but
Yes
If showing "Your device has been unlocked and cannot be trusted"
I fix my device flashing new logo bin .

mijing said:
I am not sure but
Yes
If showing "Your device has been unlocked and cannot be trusted"
I fix my device flashing new logo bin .
Click to expand...
Click to collapse
Well thank you for the tip but that's not the problem here.The problem is that my phone never boots into OS ,it is stuck in recovery.Any Indication as to why would be a huge help !

porthumor said:
Well thank you for the tip but that's not the problem here.The problem is that my phone never boots into OS ,it is stuck in recovery.Any Indication as to why would be a huge help !
Click to expand...
Click to collapse
Are you sure OS is even there?

flashallthetime said:
Are you sure OS is even there?
Click to expand...
Click to collapse
I don't think I messed with the OS . I just unlocked the bootloader and flashed TWRP without flashing SuperSU.(done it for the first time for my Moto Z play). Used Wipe to clear davlik,cache and that's it.haven't done anything in the recovery since then.
The only thing i remember messing up was to not input the encryption key when it prompt me for it by clicking cancel.
I've read in some forums that it doesn't boot if it doesn't have SuperSU flashed,but I'm not sure if it's safe since i don't exactly know what might or might now permanently brick my phone.
Also some forums had something to do with patching the kernels (don't know if that's what you call it) but i don't know if it's a safe thing to do since it might also permanently brick my phone.
Running Nougat April Security Patch.

porthumor said:
I don't think I messed with the OS . I just unlocked the bootloader and flashed TWRP without flashing SuperSU.(done it for the first time for my Moto Z play). Used Wipe to clear davlik,cache and that's it.haven't done anything in the recovery since then.
The only thing i remember messing up was to not input the encryption key when it prompt me for it by clicking cancel.
I've read in some forums that it doesn't boot if it doesn't have SuperSU flashed,but I'm not sure if it's safe since i don't exactly know what might or might now permanently brick my phone.
Also some forums had something to do with patching the kernels (don't know if that's what you call it) but i don't know if it's a safe thing to do since it might also permanently brick my phone.
Running Nougat April Security Patch.
Click to expand...
Click to collapse
You used the Chinese TWRP originally? Now you have alberto97 TWRP? Is this correct?
I would flash a custom ROM, why I'm saying that is it's far safer flashing a zip ROM than trying to flash the stock firmware.
Again I will remind people the flashing bootloaders on moto devices will inevitably cause hard bricks if you downgrade and the accept an ota.
---------- Post added at 06:47 PM ---------- Previous post was at 06:39 PM ----------
The only solution and this applies only if you want to remain on the stock ROM.
Download the retail firmware and only manually flash the boot.img, the 10 sparsechunks and the OEM.img.
Do not use rsdlite!!
This should boot your phone.

flashallthetime said:
You used the Chinese TWRP originally? Now you have alberto97 TWRP? Is this correct?
Click to expand...
Click to collapse
Yes,exactly.
flashallthetime said:
I would flash a custom ROM, why I'm saying that is it's far safer flashing a zip ROM than trying to flash the stock firmware.
Click to expand...
Click to collapse
Which Custom ROM do you think is the safest possible alternative?
flashallthetime said:
Again I will remind people the flashing bootloaders on moto devices will inevitably cause hard bricks if you downgrade and the accept an ota.
Click to expand...
Click to collapse
Can you explain this a bit better ? I would like to understand what i'm getting into !
flashallthetime said:
The only solution and this applies only if you want to remain on the stock ROM.
Download the retail firmware and only manually flash the boot.img, the 10 sparsechunks and the OEM.img.
Do not use rsdlite!!
This should boot your phone.
Click to expand...
Click to collapse
Could you,if possible, link to me to the respective article ? Do I need to Get the firmware for Nougat or does it depend on security patch as well?
Gotcha,No rsdlite !

porthumor said:
Yes,exactly.
Which Custom ROM do you think is the safest possible alternative?
Can you explain this a bit better ? I would like to understand what i'm getting into !
Could you,if possible, link to me to the respective article ? Do I need to Get the firmware for Nougat or does it depend on security patch as well?
Gotcha,No rsdlite !
Click to expand...
Click to collapse
I would install the aosp ROM as it is bare bones android.
As for bootloaders, when you receive an ota it flashes a new bootloader.
What some folks have done is because they feel like a new ota isn't working to their liking, they have downgraded their firmare, either by flashing the firmware package that can be downloaded. They flash the entire package including bootloader, what this does is set up a perfect hard brick scenerio for moto devices.
They accept an ota or for reasons that are beyond uderstanding, sideload the package and bam as soon as they restart there device it bricks their device due to the mismatched bootloaders.
You are unlocked and the easiest way to prevent hard bricks is to for go flashing firmware.
I'm running validus 7.1.2 on the original bootloader that was installed on MM.
---------- Post added at 07:19 PM ---------- Previous post was at 07:17 PM ----------
I'm attempting to build a stock flashable TWRP stock 7.1.1 ROM.
You may also flash any flashable TWRP stock 7 rom, either bye me or dedracks

flashallthetime said:
I would install the aosp ROM as it is bare bones android.
As for bootloaders, when you receive an ota it flashes a new bootloader.
What some folks have done is because they feel like a new ota isn't working to their liking, they have downgraded their firmare, either by flashing the firmware package that can be downloaded. They flash the entire package including bootloader, what this does is set up a perfect hard brick scenerio for moto devices.
They accept an ota or for reasons that are beyond uderstanding, sideload the package and bam as soon as they restart there device it bricks their device due to the mismatched bootloaders.
You are unlocked and the easiest way to prevent hard bricks is to for go flashing firmware.
I'm running validus 7.1.2 on the original bootloader that was installed on MM.
---------- Post added at 07:19 PM ---------- Previous post was at 07:17 PM ----------
I'm attempting to build a stock flashable TWRP stock 7.1.1 ROM.
You may also flash any flashable TWRP stock 7 rom, either bye me or dedracks
Click to expand...
Click to collapse
Is it fine if i go ahead with this and see if it works ?
I will try to flash a custom ROM if it doesn't.

porthumor said:
Is it fine if i go ahead with this and see if it works ?
I will try to flash a custom ROM if it doesn't.
Click to expand...
Click to collapse
That's fine and it's my ROM lol.
You may want to format your data but first try to flash the ROM and see if it boots.
That Chinese TWRP is a nasty thing

porthumor said:
How will flashing a new logo help me get out of boot loop ? AFAIK it only replaces the warning.
Click to expand...
Click to collapse
Bro are you sure you followed my instruction? In twrp menu click on reboot>bootloader
Then it will boot the device in bootloader mode. And in the bootloader menu click on "start" using the power button. Then it will boot your phone. Everytime you reboot your phone do the same step. If you want to get rid of that thing you need to flash official rom via rsd lite

Kap_Tutan said:
Bro are you sure you followed my instruction? In twrp menu click on reboot>bootloader
Then it will boot the device in bootloader mode. And in the bootloader menu click on "start" using the power button. Then it will boot your phone. Everytime you reboot your phone do the same step. If you want to get rid of that thing you need to flash official rom via rsd lite
Click to expand...
Click to collapse
Rsdlite sucks, never flash any firmware with resdlite unless you know which lines need to be removed from the text file that tells rsdlite what to flash.
manually flashing firmware is IMO much safer and all you need to flash is the boot.img all the spareschunks and oem.img

Kap_Tutan said:
Bro are you sure you followed my instruction? In twrp menu click on reboot>bootloader
Then it will boot the device in bootloader mode. And in the bootloader menu click on "start" using the power button. Then it will boot your phone. Everytime you reboot your phone do the same step. If you want to get rid of that thing you need to flash official rom via rsd lite
Click to expand...
Click to collapse
I did what you had asked me to ,unfortunately it doesn't work. I would be happy just being able to boot using the above method.
Thanks for the suggestion tho !
flashallthetime said:
That's fine and it's my ROM lol.
You may want to format your data but first try to flash the ROM and see if it boots.
That Chinese TWRP is a nasty thing
Click to expand...
Click to collapse
I'll try to get this done by tomorrow and see if it helps !

porthumor said:
I did what you had asked me to ,unfortunately it doesn't work. I would be happy just being able to boot using the above method.
Thanks for the suggestion tho !
I'll try to get this done by tomorrow and see if it helps !
Click to expand...
Click to collapse
Hopefully it does

flashallthetime said:
Rsdlite sucks, never flash any firmware with resdlite unless you know which lines need to be removed from the text file that tells rsdlite what to flash.
manually flashing firmware is IMO much safer and all you need to flash is the boot.img all the spareschunks and oem.img
Click to expand...
Click to collapse
When flashing the boot the sparsechunk and the oem then can i able to receive a OTA in my device? Or do i need to flash the recovery.img also?
Anyways thanks bro i learned again something from you

Kap_Tutan said:
When flashing the boot the sparsechunk and the oem then can i able to receive a OTA in my device? Or do i need to flash the recovery.img also?
Anyways thanks bro i learned again something from you
Click to expand...
Click to collapse
You also need to flash the recovery image as well

Pie root, twrp fail, odin fail and Emergency Recovery Function

Hi, community
I tried to root my SM G-9600 but it all went wrong. First i went on twrp, it worked, but wiped my entire data. Then i tried make a factory reset o installation with odin and the latest firmware for my device, but it failed and showed this message labeled in red color: "sw rev check fail device 4 binary 3 error". then i found in this and other forums that it was because i used not the latest firmware. I downloaded the latest one, tried once to flash it via ODIN, and it failed again. Then when it restarted this message was shown : " An error has occurred while updating the devide software. Use the Emergency recovery function in the Smart Switch PC software. I donwloaded the smart switch, installed it, plugged my devide, but it shown that my device was "Unsupported". IDK what to do by now, so i need help from anyone on this forum. PLS
Greeting from Peru.

i had the same problem
(before processing to the next step try to redownload the firmware, i think i was using an old firmware and this is why i got this error)
i am assuming that you can not boot on twrp recovery
that's not a problem , you need to install twrp via odin and boot directly to it....
format the data and connect to your laptop (if it does recognize the phone but there is no storage dont worry, just reboot again to recovery (there is an option on reboot tab))
since you already tripped the knox just flash a custom rom, boot and set it up, and then try to flash stock image via odin as normal.
and sorry for my bad english.

Cant install a custom rom
Thanks. I made posible the TWRP installation, root, but i cannot install any custom rom i have. Can you suggest any one that will be suitable for my device (SM G-9600) ?, thats Samsung Galaxy S9 g9600 (Snapdragon SoC)

dimitrispas22 said:
i had the same problem
(before processing to the next step try to redownload the firmware, i think i was using an old firmware and this is why i got this error)
i am assuming that you can not boot on twrp recovery
that's not a problem , you need to install twrp via odin and boot directly to it....
format the data and connect to your laptop (if it does recognize the phone but there is no storage dont worry, just reboot again to recovery (there is an option on reboot tab))
since you already tripped the knox just flash a custom rom, boot and set it up, and then try to flash stock image via odin as normal.
and sorry for my bad english.
Click to expand...
Click to collapse
Thanks. I made posible the TWRP installation, root, but i cannot install any custom rom i have. Can you suggest any one that will be suitable for my device (SM G-9600) ?, thats Samsung Galaxy S9 g9600 (Snapdragon SoC)

Stevie1997 said:
Thanks. I made posible the TWRP installation, root, but i cannot install any custom rom i have. Can you suggest any one that will be suitable for my device (SM G-9600) ?, thats Samsung Galaxy S9 g9600 (Snapdragon SoC)
Click to expand...
Click to collapse
do you want to install a custom rom or revert back to stock?

For custom ROM I suggest Soldiers ROM here's the link to the thread. https://forum.xda-developers.com/ga...g96xf-fd-n-stock-rom-soldier9312-1-0-t3771346 . You can more information about it on the thread. Been using the moment I rooted my phone.

Xspidera said:
For custom ROM I suggest Soldiers ROM here's the link to the thread. https://forum.xda-developers.com/ga...g96xf-fd-n-stock-rom-soldier9312-1-0-t3771346 . You can more information about it on the thread. Been using the moment I rooted my phone.
Click to expand...
Click to collapse
i think he is out of lack it looks like he doesn't know exactly his model snapdragon samsung devices are different from our g960f exynos version and it may brick his device
i think hes only option is to flash the stock firmware and yea just that....