HELP needed (can't flash stock rom) - Galaxy Note5 Q&A, Help & Troubleshooting

Galaxy Note 5 SM-N920G I need some help here. After a long time using custom roms, recently I've tried to flash a stock rom to my device (it was an Indian nougat rom from sammobile) and I got an error on Odin when flashing system. After that I lost my recovery (TWRP) an my Note 5 went only in download mode. Then a I flashed TWRP again and installed a custom rom again. Now I'm trying to flash any stock rom and I am getting random errors like "device 1 binary 0". I've tried many different roms and 0 luck. Someone could help me here? I never have this problem before and I just don't know more what to do.

diegowebber said:
Galaxy Note 5 SM-N920G I need some help here. After a long time using custom roms, recently I've tried to flash a stock rom to my device (it was an Indian nougat rom from sammobile) and I got an error on Odin when flashing system. After that I lost my recovery (TWRP) an my Note 5 went only in download mode. Then a I flashed TWRP again and installed a custom rom again. Now I'm trying to flash any stock rom and I am getting random errors like "device 1 binary 0". I've tried many different roms and 0 luck. Someone could help me here? I never have this problem before and I just don't know more what to do.
Click to expand...
Click to collapse
Peace..
I'm having the same exact problem--I found firmware that only flashed to radio--then abruptly stopped--wiping my system, so i'm stuck in download mode, phone will not power off. Instead of flashing Nougat ROM, i opted to flash "stock" MM firmware (6.01) and let phone update to Nougat on its on---then re-root it. As of now I have a paper-weight and it appears there's no support for 920G

Have you all tried Smart Switch?

CodeNameRedNeck said:
Have you all tried Smart Switch?
Click to expand...
Click to collapse
Yes... Smart Switch gave me an error in 2 ways of restoration.

ZEDEK said:
Peace..
I'm having the same exact problem--I found firmware that only flashed to radio--then abruptly stopped--wiping my system, so i'm stuck in download mode, phone will not power off. Instead of flashing Nougat ROM, i opted to flash "stock" MM firmware (6.01) and let phone update to Nougat on its on---then re-root it. As of now I have a paper-weight and it appears there's no support for 920G
Click to expand...
Click to collapse
Paper-weight? That's bad... Can't you flash a custom recovery on Odin and install a custom rom? I still can do that.

diegowebber said:
Galaxy Note 5 SM-N920G I need some help here. After a long time using custom roms, recently I've tried to flash a stock rom to my device (it was an Indian nougat rom from sammobile) and I got an error on Odin when flashing system. After that I lost my recovery (TWRP) an my Note 5 went only in download mode. Then a I flashed TWRP again and installed a custom rom again. Now I'm trying to flash any stock rom and I am getting random errors like "device 1 binary 0". I've tried many different roms and 0 luck. Someone could help me here? I never have this problem before and I just don't know more what to do.
Click to expand...
Click to collapse
It's because you flashed Nougat and that's Android 7.0 and it now thinks you're trying to "downgrade", which is pretty much blocked by trying to use "stock" roms.. The only thing you could probably do is find the stock rom you're interested in flashing but make sure it can be flashed via TWRP.. I don't think you can use Odin now to flash backwards "downgrade" to another stock rom after flashing Nougat 7.0..

MrMike2182 said:
It's because you flashed Nougat and that's Android 7.0 and it now thinks you're trying to "downgrade", which is pretty much blocked by trying to use "stock" roms.. The only thing you could probably do is find the stock rom you're interested in flashing but make sure it can be flashed via TWRP.. I don't think you can use Odin now to flash backwards "downgrade" to another stock rom after flashing Nougat 7.0..
Click to expand...
Click to collapse
Interesting... So maybe I can wait for a nougat ZTO ROM an then try to flash? Anyway, thanks for the help

MrMike2182 said:
It's because you flashed Nougat and that's Android 7.0 and ..
Click to expand...
Click to collapse
Good catch, I hadn't even thought of that.

CodeNameRedNeck said:
Good catch, I hadn't even thought of that.
Click to expand...
Click to collapse
Well I figured out you can downgrade from Nougat to Marshmallow but that's only to a specific firmware version. Depending upon what bootloader has been flashed (meaning if you flashed Nougat bootloader you can only go back to Marshmallow with the same bootloader level).. But this is only working (surprisingly) on the locked bootloaders of Verizon and AT&T.. The other S6 Edge Plus I have with an unlocked bootloader and tripped knox that I recently acquired will not accept nothing stock which is unusual, but I'm still working on that one.

Related

Rooted with motochopper and cannot do firmware update

I've tried uninstalling superuser and all it has. I've tried like 5 times now the install for the new firmware update won't install i keep getting a android with the red exclamation sign and its front door open, then it boots in to android and says update failed. Help please!
Do I have to factory restore first or somthing? i really dont wanna have to cause i just got this phone from at&t as a referb for my old one that had battery issues and its not fun setting everything up over again lol
\
Hi buddy.
First of all, I don't entirely understand what are you trying to do. What to you mean with "firmware update"? Do you want to flash a new ROM?
mauchito said:
Hi buddy.
First of all, I don't entirely understand what are you trying to do. What to you mean with "firmware update"? Do you want to flash a new ROM?
Click to expand...
Click to collapse
At&t just pushed an ota firmware update that won't install stock ROM is on here only rooted
djshadowxm81 said:
At&t just pushed an ota firmware update that won't install stock ROM is on here only rooted
Click to expand...
Click to collapse
Got it. Check this thread: http://forum.xda-developers.com/showthread.php?t=2751263
You may find all the information you need there. Even if you can't, don't worry, is just a minor update, it is not Kitkat.
I've already been through that thread and haven't really found my solution to my issue. Any ideas?
djshadowxm81 said:
I've already been through that thread and haven't really found my solution to my issue. Any ideas?
Click to expand...
Click to collapse
Sadly no, my friend. Any reason in particular about why you want this specific update?
Let's hope somebody else in this forum can help you.
Are you running a stock recovery? Have you tried using Myth Tools to flash back to stock?
Its running stock rom from factory everything is factory right now
I kept getting the dead Android as well. We're you running a KK ROM on your phone before restoring to stock? I was running Validus and tried to use Myth Tools to flash a stock ATT 4.1.1 ROM which also failed to take the update. I then installed a 4.1.2 Bell stock ROM (my phone came from Bell) via Myth, let the phone boot, and then flashed a stock ATT ROM via Myth and it took the update.
audit13 said:
I kept getting the dead Android as well. We're you running a KK ROM on your phone before restoring to stock? I was running Validus and tried to use Myth Tools to flash a stock ATT 4.1.1 ROM which also failed to take the update. I then installed a 4.1.2 Bell stock ROM (my phone came from Bell) via Myth, let the phone boot, and then flashed a stock ATT ROM via Myth and it took the update.
Click to expand...
Click to collapse
I am on 4.1.1 from the factory. This is a referb phone from the factory like not even a week old yet. Boot loader isn't even unlocked. Its all stock and I'm getting dead android.
If you're getting the dead Android, it makes me believe that something may be wrong with the stock recovery. Some people were able to get the update to install using the latest Philz Touch recovery rather than stock recovery.
This might help from Skeevy: http://forum.xda-developers.com/showpost.php?p=52745043&postcount=7

[Q] Can't Get Custom ROM to Flash on AT&T OA1 S5

I have a Samsung Galaxy S5 AT&T OA1 (G900A) and I cannot get the phone to take a custom rom flash. First I downgrade to NCE using ODIN 3.09, check install from unknown sources, then I install towelroot and successfully root the phone. Install SuperSU and update the binary, reboot, install Busybox. Shut down and go back into download mode and use ODIN to flash the OA1 kernel. I then install either flashfire or SafeStrap and then instruct them to wipe the phone other than internal memory and flash the rom zip. I have tried several roms and everytime I get back to the same thing... the default recovery screen with a dead android.
Any suggestions or ideas what I am doing wrong?
mnemonicj said:
I have a Samsung Galaxy S5 AT&T OA1 (G900A) and I cannot get the phone to take a custom rom flash. First I downgrade to NCE using ODIN 3.09, check install from unknown sources, then I install towelroot and successfully root the phone. Install SuperSU and update the binary, reboot, install Busybox. Shut down and go back into download mode and use ODIN to flash the OA1 kernel. I then install either flashfire or SafeStrap and then instruct them to wipe the phone other than internal memory and flash the rom zip. I have tried several roms and everytime I get back to the same thing... the default recovery screen with a dead android.
Any suggestions or ideas what I am doing wrong?
Click to expand...
Click to collapse
After downgrading to nce and rooting there is no need to update the kernel back to OA1 as all the kitkat roms are based off the nce build. Our you can root then upgrade to lollipop using this method
http://forum.xda-developers.com/showthread.php?t=3076803 as the devs for the s5 roms have moved to 5.0.
dirtydodge said:
After downgrading to nce and rooting there is no need to update the kernel back to OA1 as all the kitkat roms are based off the nce build. Our you can root then upgrade to lollipop using this method
http://forum.xda-developers.com/showthread.php?t=3076803 as the devs for the s5 roms have moved to 5.0.
Click to expand...
Click to collapse
I have tried to do the flash several times without going back to the OA1 kernel too, but I thought that may have been the issue. I figured out quickly it wasn't.
One thing I may have been missing is that I am trying to flash lollipop roms. Is that my problem? Do I need to be flashing a KitKat rom unless I flash the rom to linked to in your post? How do I get a lollipop rom flashed if that's the issue?
mnemonicj said:
I have tried to do the flash several times without going back to the OA1 kernel too, but I thought that may have been the issue. I figured out quickly it wasn't.
One thing I may have been missing is that I am trying to flash lollipop roms. Is that my problem? Do I need to be flashing a KitKat rom unless I flash the rom to linked to in your post? How do I get a lollipop rom flashed if that's the issue?
Click to expand...
Click to collapse
You can't flash lollipop roms unless your already on lollipop. You'll have to stick with kitkat roms unless you upgrade using the method in the link that i posted. Once you upgrade to lollipop using that method you'll be able to flash lollipop roms.
dirtydodge said:
You can't flash lollipop roms unless your already on lollipop. You'll have to stick with kitkat roms unless you upgrade using the method in the link that i posted. Once you upgrade to lollipop using that method you'll be able to flash lollipop roms.
Click to expand...
Click to collapse
Got it. Tried it out and finally was able to get a Lollipop custom rom to flash.
Thanks for your help!
mnemonicj said:
Got it. Tried it out and finally was able to get a Lollipop custom rom to flash.
Thanks for your help!
Click to expand...
Click to collapse
Good deal. Which one did you go with. I've ran alliance, twi5ted, and TMS 2.0. I personally like TMS best. Seems like it runs smother for me.
dirtydodge said:
Good deal. Which one did you go with. I've ran alliance, twi5ted, and TMS 2.0. I personally like TMS best. Seems like it runs smother for me.
Click to expand...
Click to collapse
I went with TMS 2.0, but I was hoping to get a Cyanogenmod based rom installed. I have tried several times to install the Fusion rom using FlashFire, but each time I get an unmount failed notice and have to go back to NCE.
What do you like about TMS?
mnemonicj said:
I went with TMS 2.0, but I was hoping to get a Cyanogenmod based rom installed. I have tried several times to install the Fusion rom using FlashFire, but each time I get an unmount failed notice and have to go back to NCE.
What do you like about TMS?
Click to expand...
Click to collapse
First off you can't flash cyanogenmod cause of the locked bootloader. We have to stick with TW base roms. I like the stability about TMS2.0 plus the fact that the dev is still working on it. Most all the other devs have went to other phones. TalkingMonkeys is a great dev and is constantly working on mods and features.

Odin flash auto-reverts after rebooting

Hi guys, i have an s4 active i9295 with a bootloop, so i decided to flash stock rom via odin as i always did with samsung phones with this problem but every time i flash a rom (i tried different ones) the phone restarts as normal but when the samsung logo appears then it says on the top left with blue letters revocery booting, then it does something with a progress bar and an android logo above and restarts. When it boots again its back at the bootloop, im an absolute noob in this but what i understand is happening is that the phone is reverting the flash i did with odin and i want to know what am i doing wrong, is this supposed to happen? Any help will be much appreciated
Hello,
Welcome to XDA.
To better assist you, your thread will be moved to your device Q&A forum linked below.
http://forum.xda-developers.com/galaxy-s4-active/help
The experts there may be able to help. Good luck.
I need help, its quite an expensive phone to just give up and throw it away
nexware said:
Hi guys, i have an s4 active i9295 with a bootloop, so i decided to flash stock rom via odin as i always did with samsung phones with this problem but every time i flash a rom (i tried different ones) the phone restarts as normal but when the samsung logo appears then it says on the top left with blue letters revocery booting, then it does something with a progress bar and an android logo above and restarts. When it boots again its back at the bootloop, im an absolute noob in this but what i understand is happening is that the phone is reverting the flash i did with odin and i want to know what am i doing wrong, is this supposed to happen? Any help will be much appreciated
Click to expand...
Click to collapse
C'mon guys you may know what is going on with my s4, no matter what i do it bootloops, tried everithing
pit + firmware on odin, still bootloops, wipe data/cache after and before flashing, still bootloops, i researched a lot and tried almost everithing with the same result, please help me, i'll personally bake a cake to the first nice guy to help me get out of the bootloop
nexware said:
C'mon guys you may know what is going on with my s4, no matter what i do it bootloops, tried everithing
pit + firmware on odin, still bootloops, wipe data/cache after and before flashing, still bootloops, i researched a lot and tried almost everithing with the same result, please help me, i'll personally bake a cake to the first nice guy to help me get out of the bootloop
Click to expand...
Click to collapse
I'll try to help you, what did you install or modify that caused the bootloop in the first place? Was your device rooted? Did you have custom recovery? What recovery? Did you have a custom ROM? What ROM?
Droidriven said:
I'll try to help you, what did you install or modify that caused the bootloop in the first place? Was your device rooted? Did you have custom recovery? What recovery? Did you have a custom ROM? What ROM?
Click to expand...
Click to collapse
I received the phone as it is with the bootloop, don't know much of its state before but i was told that it was a bad flashing procedure the cause of the problem. It had stock recoverys from the different roms i flashed in odin: I9295XXUDOB4
I9295XXUCNE5
I9295VJUDOF1
There was one time i managed to make it boot flashing CWM and installing cyanogenmod 12.1 but on restart it kept bootlooping again and i was unable to get it to boot again even repeating exactly the same steps i did before.
I want to make an absolute clean firmware flash with the original rom that this phone came in my country (VJUBMK4) but from what i understand once im on newer versions (im not sure if 4.3 or 5.0) i cant downgrade.
I really don't know what is it causing the bootloop, how can i get the pone to factory firmware? Am i doing something wrong?
nexware said:
I received the phone as it is with the bootloop, don't know much of its state before but i was told that it was a bad flashing procedure the cause of the problem. It had stock recoverys from the different roms i flashed in odin: I9295XXUDOB4
I9295XXUCNE5
I9295VJUDOF1
There was one time i managed to make it boot flashing CWM and installing cyanogenmod 12.1 but on restart it kept bootlooping again and i was unable to get it to boot again even repeating exactly the same steps i did before.
I want to make an absolute clean firmware flash with the original rom that this phone came in my country (VJUBMK4) but from what i understand once im on newer versions (im not sure if 4.3 or 5.0) i cant downgrade.
I really don't know what is it causing the bootloop, how can i get the pone to factory firmware? Am i doing something wrong?
Click to expand...
Click to collapse
Ah, it sounds like you have one of the devices with locked bootloaders then if you can't downgrade, if that is the case you can't use CWM, TWRP, CM or AOSP custom ROMs, those devices have to use Safestrap and modified Stock ROMs. Or you may can unlock the bootloader. I'm not sure that is your problem but you can check it out.
You can flash the newest stock firmware and just be done with it, you may not be able to root and flash custom but the device will at least work.
Sent from my SCH-I535 using Tapatalk
Droidriven said:
Ah, it sounds like you have one of the devices with locked bootloaders then if you can't downgrade, if that is the case you can't use CWM, TWRP, CM or AOSP custom ROMs, those devices have to use Safestrap and modified Stock ROMs. Or you may can unlock the bootloader. I'm not sure that is your problem but you can check it out.
You can flash the newest stock firmware and just be done with it, you may not be able to root and flash custom but the device will at least work.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
How can i be sure that the device has a locked bootloader? If that's the case, what can i do to make it to just work as stock? I need a special kind of stock firmware?
nexware said:
How can i be sure that the device has a locked bootloader? If that's the case, what can i do to make it to just work as stock? I need a special kind of stock firmware?
Click to expand...
Click to collapse
Boot into download mode by holding the volume down + power button and see what is the device name listed there
nexware said:
How can i be sure that the device has a locked bootloader? If that's the case, what can i do to make it to just work as stock? I need a special kind of stock firmware?
Click to expand...
Click to collapse
Take the cover off and pull the battery, the label under the battery should have the model number for the phone.
If the model is GT-i9295, then you have an unlocked bootloader and should be able to flash any firmware.
If the model is SGH-i537, then you have a locked bootloader and can only flash firmware meant for that phone.
Once we know which phone you have we can help you.
JASONRR said:
Boot into download mode by holding the volume down + power button and see what is the device name listed there
Click to expand...
Click to collapse
It says this:
PRODUCT NAME: GT-I9295
CURRENT BINARY: Custom
SYSTEM STATUS: Official
CSB-CONFIG-LSB: 0x30
SECURE DOWNLOAD : ENABLE
WRITE PROTECTION: ENABLE
eMMC BURST MODE enabled
Devo7v said:
Take the cover off and pull the battery, the label under the battery should have the model number for the phone.
If the model is GT-i9295, then you have an unlocked bootloader and should be able to flash any firmware.
If the model is SGH-i537, then you have a locked bootloader and can only flash firmware meant for that phone.
Once we know which phone you have we can help you.
Click to expand...
Click to collapse
Its GT-i9295
Can you flash VJUCNI1 or VJUDOF1?

Possible to downgrade from Oreo to Nougat?

I have the leaked ver of Oreo installed, but I have an app that's incompatible with the new OS, so I've been trying to downgrade for several weeks now, with no success.
I've seen answers online that completely contradict each other- use Smart Switch backup (tried that, didn't roll back the OS), tried several versions of Odin and firmware, always get 'FAILED AUTH'.
Also seen some posts that say you can't downgrade, others that say yes you can.
Is it possible? How can I find out which bootloader I have?
I heard with Oreo they did the same as Apple do. They stop downgrading the OS, but I'm not sure about it.
I hope other members can help you.
I'm having the same issue, I have a Verizon tmb tmb vzw software version, I flashed the carrier switch CDC thing xxa I entered the codes what ever, but i don't k ow i kind of got stuck and flashed bra8 and it came up with tmobile after flashing that was my intention, and then I flashed oreo, I'm trying to roll back to update to the latest crb8 oreo but anything I try in Odin fails at initialization... or It just wont work, and the phone doesnt have a progress bar as I press start, it's like stuck, I'm losing my mind here, I even tried flashing tmobile and Verizon firmware on odin, I tried kies and switch to restore yo nougat bra8 with no go, even tried flashing the carrier switch thing, NOTHING IS WORKING different USB ports rebooting PC, reinstalled drivers, took aim out when odin, nothing.
Some one help us
Fixed
And just like that, as soon as I post this, I get it to work. After spending all night trying different versions of Prince Odin and different firmwares, I just switched to normal Odin and it worked immediately, so back to 7.1.1
can you please tell how and what you used to down grade note 8 back to 7.1.1....thanks
PAULG1919 said:
can you please tell how and what you used to down grade note 8 back to 7.1.1....thanks
Click to expand...
Click to collapse
Have you tried Odin and the firmware for your device?
as long as the version you want to downgrade to is same version bootloader would it not be fine?
ie.. v3 to v3 is fine but not v3 to v2
I haven't been rooting or flashing with the Note 8 yet but that's the understanding I have from other threads
briwil said:
And just like that, as soon as I post this, I get it to work. After spending all night trying different versions of Prince Odin and different firmwares, I just switched to normal Odin and it worked immediately, so back to 7.1.1
Click to expand...
Click to collapse
can you please share your files and steps?:good:
pls share your steps for downgrading
briwil said:
And just like that, as soon as I post this, I get it to work. After spending all night trying different versions of Prince Odin and different firmwares, I just switched to normal Odin and it worked immediately, so back to 7.1.1
Click to expand...
Click to collapse
i already tried few procedures with no luck. what do you mean in prince ODIN and normal ODIN ? i am using the latest 3.13.1, shd we use something else ?
btw, i have oreo ...U2 and the SAM nougat rom is ...U1, i cant find any nougat with U2.
appreciate any help here...
tks
I think they changed something in oreo , where you cant downgrade now. Odin. Maybe latest update annoying i know.....no work around yet
The thing is like this: you can always flash roms with EQUAL O HIGHER bootloader version, just that, and NEVER to a lower bootloader version, and this is not new
briwil said:
I have the leaked ver of Oreo installed, but I have an app that's incompatible with the new OS, so I've been trying to downgrade for several weeks now, with no success.
I've seen answers online that completely contradict each other- use Smart Switch backup (tried that, didn't roll back the OS), tried several versions of Odin and firmware, always get 'FAILED AUTH'.
Also seen some posts that say you can't downgrade, others that say yes you can.
Is it possible? How can I find out which bootloader I have?
Click to expand...
Click to collapse
Don't you want to try flashing only AP and CSC_OXM (not HOME)? I read on 4pda that it's possible, but you can have some errors while using your device.
Flash the oldest oreo with bootloader you have, then flash the latest nougat without BL and CP. Only AP and CSC OXM. Backup your data before doing it.

Only Official Released Binaries... Samsung Galaxy Note 8

Hey guys,
I've done my custom rom well and it all was working fine, and I restared right after it started and then my phone has stopped at Samsung Galaxy Note 8, and in Red Text up it says:
Only Official Released Binaries are allowed to be flashed.
Is there any solution with my situation?
Your help would be appreciated guys
Ziezo said:
Hey guys,
I've done my custom rom well and it all was working fine, and I restared right after it started and then my phone has stopped at Samsung Galaxy Note 8, and in Red Text up it says:
Only Official Released Binaries are allowed to be flashed.
Is there any solution with my situation?
Your help would be appreciated guys
Click to expand...
Click to collapse
The only way to fix that is by flashing stock filmware with Odin. Just make sure to download the same filmware or newer than what is on the phone as you can't flash older filmware and you would just get an error. You can use "Frija" for PC to download the filmware at a decent speed, just Google "Frija XDA"
Did you flash a rom and this happened? Or did you just flash TWRP and reboot?
The ' Only Official Released Binaries are allowed to be flashed ' error is due to bootloader not being fully unlocked.
As @stonedpsycho has said flash firmware to fix.
Is it related to RMM ? https://forum.xda-developers.com/t/...ll-twrp-on-exynos-samsung-after-2018.3747535/
stonedpsycho said:
The only way to fix that is by flashing stock filmware with Odin. Just make sure to download the same filmware or newer than what is on the phone as you can't flash older filmware and you would just get an error. You can use "Frija" for PC to download the filmware at a decent speed, just Google "Frija XDA"
Did you flash a rom and this happened? Or did you just flash TWRP and reboot?
Click to expand...
Click to collapse
I'll try the "Frija XDA" and see what I can get, because I got tired of keep downloading STOCK ROM at low speed and then stopped!!
and I got this message after flashing the ROM, I flashed it the first time and it was very good, but I wanted to remove some unwanted apps, then I flashed it again, OK! This time it works fine too and when it started and before making any setups (Google account, WIFI, etc) I restarted my phone to flash some additional Add-On's but I got this message and I'm stock here untill now.
Ziezo said:
I'll try the "Frija XDA" and see what I can get, because I got tired of keep downloading STOCK ROM at low speed and then stopped!!
and I got this message after flashing the ROM, I flashed it the first time and it was very good, but I wanted to remove some unwanted apps, then I flashed it again, OK! This time it works fine too and when it started and before making any setups (Google account, WIFI, etc) I restarted my phone to flash some additional Add-On's but I got this message and I'm stock here untill now.
Click to expand...
Click to collapse
Very strange that this happened after flashing a rom as the RMM state should be patched (This should only be an issue when wanting to root stock filmware and not flash a rom). Post the link to the Lightrom you are using and I will have a look on the thread as maybe you missed something or there may be others who encountered the same problem with someone offering a solution.
stonedpsycho said:
Very strange that this happened after flashing a rom as the RMM state should be patched (This should only be an issue when wanting to root stock filmware and not flash a rom). Post the link to the Lightrom you are using and I will have a look on the thread as maybe you missed something or there may be others who encountered the same problem with someone offering a solution.
Click to expand...
Click to collapse
This is the LightRom I used, always I'm following the instructions and my work always goes the right, except this time, I may did something wrong.
And by the way, I have formatted Data before doing the 1st flash and the 2nd flash.
stonedpsycho said:
The only way to fix that is by flashing stock filmware with Odin. Just make sure to download the same filmware or newer than what is on the phone as you can't flash older filmware and you would just get an error. You can use "Frija" for PC to download the filmware at a decent speed, just Google "Frija XDA"
Did you flash a rom and this happened? Or did you just flash TWRP and reboot?
Click to expand...
Click to collapse
Flashed the Stock rom and it worked, thank you guys @LR7875 @spawnlives @stonedpsycho
The RMM and/or KG state has been around since oero. Flashing stock firmware will reactive this state. To modify your phone this state has to change.
So you will need
Oem unlocked in developers menu
In download mode
RMM - normal or dissapeared
KG - checking
Then you start to flash non samsung signed firmware. ie: twrp,root,custom roms etc.
Read the post quoted above for rmm state bypass
KG state there is no zip to bypass so it has to be in checking mode and will generally stay that way until flashing stock firmware again.

Categories

Resources