Develop Bugs

[Q] Ace II i8160, startup error always with all new roms

Hello and happy new year ,
Οver three months I try to flash my mobile and always writes me the same error "unfortunately, samsung setupwizard has stopped" . Τhe device always hangs at the point where I choose system language on screen. To be able to work on my device should I have make it "flash" with version of android 2.3.6. Ι have tried to do "flash" with roms too, "pac-rom android 4.2.2" and "10.2 cyanogenmod", and always my device hangs at the point of the loading logo. I've done "flash" with these roms , as stated above, in my friend's phones ,same as mine, and has been correctly installed. The devices are not stuck like mine and working properly. Why my device is not working properly as the other? I am disappointed . I would like to help me :crying:

Try to wipe data/factory reset in CWM after you install new ROM. But you have to know that you lost all of your data.

As far as I understand, you are on GB 2.3.6 ? :confusing:
If this is the case, flash Jelly Bean 4.1.2 then you could flash Customs ROMS based on 4.x

Aarek said:
Try to wipe data/factory reset in CWM after you install new ROM. But you have to know that you lost all of your data.
Click to expand...
Click to collapse
I've done it several times what you're saying. The error message is always the same when the device become "flash" with the version 4.1.2. A friend who is technical in Mobile phones, IPHONE, HTC told me, that should be reprogram the motherboard or replace. If this is the only way, then we are talking about 100 euro cost. He said that, because the device does not show the serial number and the baseband has this "ΧΧΧΧ". I do not know if anyone here on the site also has solved a similar problem without changing the motherboard

You must flash 3-part firmware (PIT + CODE/PDA + CSC) when switching between 2.x and 4.x!
(Google MB4.zip for the to 4.x conversion)

Ryccardo said:
You must flash 3-part firmware (PIT + CODE/PDA + CSC) when switching between 2.x and 4.x!
(Google MB4.zip for the to 4.x conversion)
Click to expand...
Click to collapse
Please I would like you to give me much information about what you say, a more complete guide

embodio said:
Please I would like you to give me much information about what you say, a more complete guide
Click to expand...
Click to collapse
Install Odin and USB drivers, extract mb4.zip (http://d-h.st/6QB) until you get .pit, CODE and CSC files.
Open Odin, load the 3 files (CODE goes into PDA), reboot your phone in download mode (hold volume-, home and power until you get a yellow triangle then press volume+ then connect cable to PC), click start in Odin and let it work, after it boots to "Samsung Galaxy, choose your language" reboot into recovery, open the CWM zip, wipe data/cache then flash the rom you want

Ryccardo said:
Install Odin and USB drivers, extract mb4.zip (http://d-h.st/6QB) until you get .pit, CODE and CSC files.
Open Odin, load the 3 files (CODE goes into PDA), reboot your phone in download mode (hold volume-, home and power until you get a yellow triangle then press volume+ then connect cable to PC), click start in Odin and let it work, after it boots to "Samsung Galaxy, choose your language" reboot into recovery, open the CWM zip, wipe data/cache then flash the rom you want
Click to expand...
Click to collapse
I knew pretty much everything that you say. Unfortunately, my friend, every time a file is missing me. This file is the modem file for this mobile, where fixes the baseband.This file I have not ever found in no one zip file. Can you find it for me, I should be grateful to you .

Is it a P? a L? a Chinese/HK model?
(Unluckily I don't know those variants well, you'll have to extract various firmwares until you see one with modem.bin.md5 and ipl.bin.md5 then flash those 2 files...)

Ryccardo said:
Is it a P? a L? a Chinese/HK model?
(Unluckily I don't know those variants well, you'll have to extract various firmwares until you see one with modem.bin.md5 and ipl.bin.md5 then flash those 2 files...)
Click to expand...
Click to collapse
The device writes from behind model: GT-i8160. I have done that you say , I have unzip the modem.bin file and when i had try to "flash" it , the odin program has stopped with an error.

embodio said:
The device writes from behind model: GT-i8160. I have done that you say , I have unzip the modem.bin file and when i had try to "flash" it , the odin program has stopped with an error.
Click to expand...
Click to collapse
flash the whole firmware...

teddytsen said:
flash the whole firmware...
Click to expand...
Click to collapse
The firmware means "rom" or is it something else?

The .md5 file you get when you download and extract stock firmware..
Sent from my GT-I8160 using Tapatalk

embodio said:
The device writes from behind model: GT-i8160. I have done that you say , I have unzip the modem.bin file and when i had try to "flash" it , the odin program has stopped with an error.
Click to expand...
Click to collapse
You can't flash single images with Odin (well, maybe if you wrap them back in a .tar) or just use Heimdall

Anyway , I have sent my device to the Samsung service and they will replace my phone's board. Thanks everyone for your advice.

Pardon Me.. But I'm a newbie... Custom ROM suggestions required...

Hi ,
I am new here.. not new to rooting ....
I used to use my Samsung galaxy grand i9082 but switched to nexus 5 last year...
Since then my grand has been sitting in my cupboard drawer. I also found this phone very slow performance so switched...
But now i am thinking of flashing a custon Rom to increase its performance and remove all the bloatware...
so i need suggestions of a stable custom ROM with good performance and all features working like dual sim ...etc..
Can you guys help me .... ?
Lollipop or Kitkat or Marshmellow expected with fast perfomance and no lagging ( I guess Marshmellow will lag too much so i can go with KK or Lollipop...)
Please suggest me ...

CM12.1

I cant even flash my recovery...( i dont know why.... its so easy for nexus 5 )
First of all i cant find any download link for CWM recovery for i9082...( .tar file which can be flashed using odin.. ihave the zip file with name CWM_6.0.5.0_Non_Touch_xenon92.zip )
As of now i have downloaded TWRP recovery i9082_TWRP_skullface.tar which is flashed successfully using odin3 v3.07.
but when i restart the device after booting into android it again shows android recovery ...
I also tried the unchecking the auto reboot in odin and removing battery after flashing and trying to boot into recovery but again no result ..everytime the samsung logo comes and again phone restarts and same goes again and again till i boot into the android.
Can anyone give me the CWM recovery...thanks in advance....
Also i have download 2 super user SU files with diffrent version.... UPDATE-SuperSU-v1.25_2.zip and UPDATE-SuperSU-v2.46.zip ...can anyone confirm if the latter one ( new version ) will work.....

anirudh.88 said:
I cant even flash my recovery...( i dont know why.... its so easy for nexus 5 )
First of all i cant find any download link for CWM recovery for i9082...( .tar file which can be flashed using odin.. ihave the zip file with name CWM_6.0.5.0_Non_Touch_xenon92.zip )
As of now i have downloaded TWRP recovery i9082_TWRP_skullface.tar which is flashed successfully using odin3 v3.07.
but when i restart the device after booting into android it again shows android recovery ...
I also tried the unchecking the auto reboot in odin and removing battery after flashing and trying to boot into recovery but again no result ..everytime the samsung logo comes and again phone restarts and same goes again and again till i boot into the android.
Can anyone give me the CWM recovery...thanks in advance....
Also i have download 2 super user SU files with diffrent version.... UPDATE-SuperSU-v1.25_2.zip and UPDATE-SuperSU-v2.46.zip ...can anyone confirm if the latter one ( new version ) will work.....
Click to expand...
Click to collapse
Nevermind i got it ....
if anyone else needs help ...
I used below mentioned files
1) UPDATE-SuperSU-v2.46.zip for rooting....
2) twrp-2.8.6.0-i9082.tar downloaded from twrp website latest version....
Steps:...
1) Flashedtwrp from odin..
2) after RES OK !! success message in odin .... removed battery ...
3) put battery back....
4) pressed vol UP + home + power ...and voila!!!
5) booted into TWRP recovery....
6) flashed UPDATE-SuperSU-v2.46.zip from external-sd .....
Now if anyone can anyone please provide good custom ROM suggestions...

anirudh.88 said:
Nevermind i got it ....
if anyone else needs help ...
I used below mentioned files
1) UPDATE-SuperSU-v2.46.zip for rooting....
2) twrp-2.8.6.0-i9082.tar downloaded from twrp website latest version....
Steps:...
1) Flashedtwrp from odin..
2) after RES OK !! success message in odin .... removed battery ...
3) put battery back....
4) pressed vol UP + home + power ...and voila!!!
5) booted into TWRP recovery....
6) flashed UPDATE-SuperSU-v2.46.zip from external-sd .....
Now if anyone can anyone please provide good custom ROM suggestions...
Click to expand...
Click to collapse
kitkat- cosmic CM
lollipop - latest cm12.1

anirudh.88 said:
Nevermind i got it ....
if anyone else needs help ...
I used below mentioned files
1) UPDATE-SuperSU-v2.46.zip for rooting....
2) twrp-2.8.6.0-i9082.tar downloaded from twrp website latest version....
Steps:...
1) Flashedtwrp from odin..
2) after RES OK !! success message in odin .... removed battery ...
3) put battery back....
4) pressed vol UP + home + power ...and voila!!!
5) booted into TWRP recovery....
6) flashed UPDATE-SuperSU-v2.46.zip from external-sd .....
Now if anyone can anyone please provide good custom ROM suggestions...
Click to expand...
Click to collapse
Try this rom: http://forum.xda-developers.com/showthread.php?t=3073108
That is a CM 12.1 port to grand duos by pawitp. It is pretty stable and functional. Though I experienced frequent freezing with the latest build 20151115, I got it fixed by installing frost kernel ( here: http://forum.xda-developers.com/showthread.php?t=2927449).
After installing frost kernel, adjust your cpu governor to lulzactive, and your i/o scheduler to sioplus (the most recommended setting for Grand duos with CM 12.1).
Though the consequences of using custom kernel with that rom is that you can no longer uses delta upgrade features of that rom, you have to download full update build and flash it as if you're to flash new rom (though without wiping cache partition and dalvik cache).
Good luck with your quest to find perfect rom for your grand duos!

Install CM12.1 (Based on Lollipop 5.1.1) by pawitp. It is stable and very fast. I'm using it currently

[G928I]MM Bootloader from G928G

I tested it, G928G MM Bootloader works on G928I.
I tested it with this [ROM][SM-G928 F/I/C/L/K/S][6]Ditto S7 ROM [v6] from Electron Team[PC8] Thanks to GigilinE
Take a look at Attachment!
TAR File(sboot.bin, cm.bin) flash via Odin. (For install a ROM you need Recovery and Kernel for MM)

Hey mate,
Wanting to use AUDAX Rom using this... did you need to flash the 928G modem files as well or just the bootloader?
Thanks

itstongy said:
Hey mate,
Wanting to use AUDAX Rom using this... did you need to flash the 928G modem files as well or just the bootloader?
Thanks
Click to expand...
Click to collapse
Hey, i flashed the modem, hidden, bootloader and cm from this rom G928GUBU2BPD2_G928GUUB2BPD2_G928GUBU2BPD2.
It works great.

So have you uploaded just the bootloader here? Do you have the modem files?

Im in New Zealand with a G928I DVU2AOK2, Would this work?
If it would work how does one install it? ( I know how to use odin just need the ROM link and what to do with your bootloader files)
Thanks

finesir said:
Im in New Zealand with a G928I DVU2AOK2, Would this work?
If it would work how does one install it? ( I know how to use odin just need the ROM link and what to do with your bootloader files)
Thanks
Click to expand...
Click to collapse
I flashed mine to Marshmallow earlier today using Audax Rom,
This is the process I followed:
1- Put Rom in your device
2- Enable Developers options in your phone
Go to Settings / About Device / Software Info and tap on Build Number 10 times to enable Developers Options.
Then Go to Settings / Developers Options and Make enable "USB Debugging" and "OEM Unlock".
3- Make a backup of you internal SDcard and your data.
4- Power off your device
5- Reboot into Download Mode
(Press and Hold Volume Down + Home + Power button)
6- Open Odin 3.10.7
7- Put BOOTLOADER in BL
8- Put TWRP RECOVERY in AP (I had to specifically use this TWRP as the current one wasn't working for me https://www.androidfilehost.com/?w=files&flid=52574)
9- Connect device to PC and it added in Odin
10- Go in options tab and uncheck autoreboot (check only F. Reset Time).
11- Click on Start to Flash the files
12- Once it's completed and you see "PASS" in a green box, disconnect device and long press Volume Down + Power
13- Once screen turns off, immediately press Volume Up + Power + Home to reboot to recovery manually.
14- Once in Recovery, install Audax Rom and in Aroma installer select WIPE DATA.
15- When device reboot seems like a Bootloop but is normal. Than start Samsung bootanimation. Complete reboot ends after 7/8 minutes.

i´ve flashed this firmware complete G928GUBU2BPD2_G928GUUB2BPD2_G928GUBU2BPD2 and it works for me on my G928I! Only problem is LTE with O2 for me.
i think the best is install firmware. And then install recovery and kernel for other roms.

[a520f] Bricked after flashing boot partition with heimdall no Downloadmode/Recovery

Hey guys,
i wanted to get lineage for my galaxy a5 and managed to install twrp and successfully and also flashed lineage 14.1 with for microg. It booted fine but no sim was detectet. On first boot wlan worked, when rebooted: no more wlan.... additionally it could not be turned off, because it automatically turned itself on again. Download mode and recovery worked fine. I read, that this problem occurs, when the phone ran with oreo before (what has been the case) and a possible solution would be to flash the nougat bootloader and modem. So i looked for mentioned files and found them in this forum (https://forum.xda-developers.com/sa...to/ref-modems-bootloaders-collection-t3799551). The instructions say one has to use odin to flash bootloader and modem, but i prefer linux so i use heimdall. But the files in the post above come in *.tar.md5 Format and heimdall did not want to accept that (at least the way i understood it). So i thought it would be intelligent to simply unpack the *.tar.md5 files. I received 3 files with *.bin ending, and i thought nice thats just what i need.
So next in Heimdall:
- i selected BOOT for partition name (instead of Bootloader)
- selected the first of the 3 files called sboot.bin
- no reboot
- put phone in Download mode
- connected phone
- click start in Heimdall
- flashing process
- wait a few moments
- disconnect phone
- restart phone manually
-> now when i try to power on or put phone into recovery mode/ download mode: all i get is black screen with red tiny writing in the top saying: "could not do normal boot. Invalid KERNEL LENGTH!"
i cannot acces Download mode or recovery or boot the phone
after many hours of research and no real progress i ask for your help.
is there still hope for my phone ? If Yes, what would be a possible solution?
grateful for your response

wolkengold said:
Hey guys,
i wanted to get lineage for my galaxy a5 and managed to install twrp and successfully and also flashed lineage 14.1 with for microg. It booted fine but no sim was detectet. On first boot wlan worked, when rebooted: no more wlan.... additionally it could not be turned off, because it automatically turned itself on again. Download mode and recovery worked fine. I read, that this problem occurs, when the phone ran with oreo before (what has been the case) and a possible solution would be to flash the nougat bootloader and modem. So i looked for mentioned files and found them in this forum (https://forum.xda-developers.com/sa.../ref-modems-bootloaders-collection-t3799551). The instructions say one has to use odin to flash bootloader and modem, but i prefer linux so i use heimdall. But the files in the post above come in *.tar.md5 Format and heimdall did not want to accept that (at least the way i understood it). So i thought it would be intelligent to simply unpack the *.tar.md5 files. I received 3 files with *.bin ending, and i thought nice thats just what i need.
So next in Heimdall:
- i selected BOOT for partition name (instead of Bootloader)
- selected the first of the 3 files called sboot.bin
- no reboot
- put phone in Download mode
- connected phone
- click start in Heimdall
- flashing process
- wait a few moments
- disconnect phone
- restart phone manually
-> now when i try to power on or put phone into recovery mode/ download mode: all i get is black screen with red tiny writing in the top saying: "could not do normal boot. Invalid KERNEL LENGTH!"
after many hours of research and no real progress i ask for your help.
is there still hope for my phone ? If Yes, what would be a possible solution?
grateful for your response
Click to expand...
Click to collapse
Can you boot to download mode? If you can, flash latest oreo.

iloveoreos said:
Can you boot to download mode? If you can, flash latest oreo.
Click to expand...
Click to collapse
no i cant... at least not with button combinations...

wolkengold said:
no i cant... at least not with button combinations...
Click to expand...
Click to collapse
Your phone is probably screwed then. If you dualboot your PC and installed smart switch, you MIGHT be able to fix it.
But jtagging it is probably cheaper than buying Windows.

iloveoreos said:
Your phone is probably screwed then. If you dualboot your PC and installed smart switch, you MIGHT be able to fix it.
But jtagging it is probably cheaper than buying Windows.
Click to expand...
Click to collapse
thanks, i will try if smart switch will help me.

wolkengold said:
thanks, i will try if smart switch will help me.
Click to expand...
Click to collapse
There is a small chance.

iloveoreos said:
There is a small chance.
Click to expand...
Click to collapse
mh... i did make a little progress but i have no clue how it really happened... i ran windows on a VM installed Smart Switch connected the phone and somehow after a few trys it bootet into TWRP without button combination. So did format data, and wiped cache and System partition, reinstalled lineageos 14.1 (microg) + su addon and it booted. I then successfully started download mode to flash bootloader and modem as described above, this time with a windows pc (no VM) and odin. I did exactly as described in the post (https://forum.xda-developers.com/sa...to/ref-modems-bootloaders-collection-t3799551), but operation failed. Now i can still boot into the os but not into twrp or Download mode. USB debugging is turned
Here is how i tried to acces TWRP and Download mode:
Phone off: Button Combinations home+vol down+power -> boots into os
adb command: adb reboot-bootloader (device is recognized and authorized)
edit:
okay i did manage to enter download mode with the right timing of button combination.... (had to press them really hard...) still dont understand why adb wasnt able to boot into recovery...

wolkengold said:
mh... i did make a little progress but i have no clue how it really happened... i ran windows on a VM installed Smart Switch connected the phone and somehow after a few trys it bootet into TWRP without button combination. So did format data, and wiped cache and System partition, reinstalled lineageos 14.1 (microg) + su addon and it booted. I then successfully started download mode to flash bootloader and modem as described above, this time with a windows pc (no VM) and odin. I did exactly as described in the post (https://forum.xda-developers.com/sa.../ref-modems-bootloaders-collection-t3799551), but operation failed. Now i can still boot into the os but not into twrp or Download mode. USB debugging is turned
Here is how i tried to acces TWRP and Download mode:
Phone off: Button Combinations home+vol down+power -> boots into os
adb command: adb reboot-bootloader (device is recognized and authorized)
edit:
okay i did manage to enter download mode with the right timing of button combination.... (had to press them really hard...) still dont understand why adb wasnt able to boot into recovery...
Click to expand...
Click to collapse
Cool! Now what happens when you reboot to download mode from twrp?

SnowFuhrer said:
Cool! Now what happens when you reboot to download mode from twrp?
Click to expand...
Click to collapse
after i was able do enter download mode i wanted to flash stock rom again to start anew. Problem is that i somehow cant. I used odin to flash stock rom and also tried with heimdall to flash every single partition. i get problems with several....
I try to summarize my situation:
- I can access Download Mode with button combination and via twrp
- I was able to flash twrp and can use it
- I can not flash stock rom with odin oder heimdall
flashing system.img with odin or heimdall gives me an error. on the phone it says:
KERNEL REV. CHECK FAIL. DEVICE:5, BINARY: 1
Flashing Bootloader also gives me an error, phone says:
SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 8, BINARY:4
anybody an idea what i could do?

wolkengold said:
after i was able do enter download mode i wanted to flash stock rom again to start anew. Problem is that i somehow cant. I used odin to flash stock rom and also tried with heimdall to flash every single partition. i get problems with several....
I try to summarize my situation:
- I can access Download Mode with button combination and via twrp
- I was able to flash twrp and can use it
- I can not flash stock rom with odin oder heimdall
flashing system.img with odin or heimdall gives me an error. on the phone it says:
KERNEL REV. CHECK FAIL. DEVICE:5, BINARY: 1
Flashing Bootloader also gives me an error, phone says:
SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 8, BINARY:4
anybody an idea what i could do?
Click to expand...
Click to collapse
You need to flash oreo on it because the bootloader prevents an older version bootloader from being flashed.

SnowFuhrer said:
You need to flash oreo on it because the bootloader prevents an older version bootloader from being flashed.
Click to expand...
Click to collapse
Sorry for misunderstanding.
- I downloaded newest oreo stock Rom and can not flash. I get the above discribed errors

wolkengold said:
Sorry for misunderstanding.
- I downloaded newest oreo stock Rom and can not flash. I get the above discribed errors
Click to expand...
Click to collapse
Flash stock firmware using Odin?

wolkengold said:
Sorry for misunderstanding.
- I downloaded newest oreo stock Rom and can not flash. I get the above discribed errors
Click to expand...
Click to collapse
Interesting, the error that you got means you were flashing too old of bootloader. Was it the newest version of oreo you could get?
Try flashing the whole tar.md5 firmware without extracting.

SnowFuhrer said:
Interesting, the error that you got means you were flashing too old of bootloader. Was it the newest version of oreo you could get?
Try flashing the whole tar.md5 firmware without extracting.
Click to expand...
Click to collapse
sorry for the late response. You were right, i accidentally downloaded an older oreo release and thats why i could not flash it. I now downloaded the newest stock rom from updato.com and it worked perfect.
Thanks for your support

wolkengold said:
after i was able do enter download mode i wanted to flash stock rom again to start anew. Problem is that i somehow cant. I used odin to flash stock rom and also tried with heimdall to flash every single partition. i get problems with several....
I try to summarize my situation:
- I can access Download Mode with button combination and via twrp
- I was able to flash twrp and can use it
- I can not flash stock rom with odin oder heimdall
flashing system.img with odin or heimdall gives me an error. on the phone it says:
KERNEL REV. CHECK FAIL. DEVICE:5, BINARY: 1
Flashing Bootloader also gives me an error, phone says:
SW REV. CHECK FAIL (BOOTLOADER) DEVICE: 8, BINARY:4
anybody an idea what i could do?
Click to expand...
Click to collapse
Hello friend, the solution to your problem is very simple, you are trying to flash rom stock Binary 1 and your phone is with binary 5 what you should do is download a rom bin 5 and then flash again Greetings and comment if it worked

jack364030 said:
Hello friend, the solution to your problem is very simple, you are trying to flash rom stock Binary 1 and your phone is with binary 5 what you should do is download a rom bin 5 and then flash again Greetings and comment if it worked
Click to expand...
Click to collapse
You are correct but...He sorted this 4 months ago.

Samsung S9 UNABLE TO BOOT UP after flashing SuperSU

Dear all,
I (newbie who trying to root for the first time) have tried to root my Samsung S9 with SuperSu via Odin. My device is now stuck at the S9 loading screen which will not boot up anymore.
Source of learning:
https://www.youtube.com/watch?v=g3IppGISkP0
Here's what I have done:
Stage 0 - Download all needed files
1. Odin 3.13.1
2. no-verify-opt-encrypt-6.0-star
3. RMM-state-ByPass_Mesa.zip
4. Samsung-anti-removal.2.4.zip
5. SupserSu-v.2.82.201705271822.zip
Stage 1 (Setup environment)
1. Enable Developer mode - OEM unlock enabled & USB Debugging enabled
2. Turn off my device, enter download mode (volume down button + bixby button + power button)
3. Connect my S9 device to my laptop
4. Launch Odin 3.13.1 on my laptop (S9 device recognized!) - Select AP, choose TWRP 3.3.1.1, press on start. (Device turn off itself)
5. As soon as device begins to boot, I enter recovery mode (volume up button + bixby button + power button)
Stage 2 Managed to entered TWRP
1. Swipe to Allow Modification
2. Tap on Wipe > Format Data > type in YES
3. Back to Menu
4. Tap on Install, (no-verify-opt-encrypt-6.0-star) - success
5. Reboot - Recovery
6. Tap on Install - (RMM-state-ByPass_Mesa.zip) - success
6. Hit back button
7. Tap on (SupserSu-v.2.82.201705271822.zip) - success
8 . Hit back button
9. Tap on (Samsung-anti-removal.2.4.zip) - success
10. Reboot system
11. Device begins reboot (Device stuck at Samsung S9 Screen)
Any advice what should I do now? Am I making any mistakes?
Please help. Appreciate!

CounteReborn said:
Dear all,
I (newbie who trying to root for the first time) have tried to root my Samsung S9 with SuperSu via Odin. My device is now stuck at the S9 loading screen which will not boot up anymore.
Source of learning:
https://www.youtube.com/watch?v=g3IppGISkP0
Here's what I have done:
Stage 0 - Download all needed files
1. Odin 3.13.1
2. no-verify-opt-encrypt-6.0-star
3. RMM-state-ByPass_Mesa.zip
4. Samsung-anti-removal.2.4.zip
5. SupserSu-v.2.82.201705271822.zip
Stage 1 (Setup environment)
1. Enable Developer mode - OEM unlock enabled & USB Debugging enabled
2. Turn off my device, enter download mode (volume down button + bixby button + power button)
3. Connect my S9 device to my laptop
4. Launch Odin 3.13.1 on my laptop (S9 device recognized!) - Select AP, choose TWRP 3.3.1.1, press on start. (Device turn off itself)
5. As soon as device begins to boot, I enter recovery mode (volume up button + bixby button + power button)
Stage 2 Managed to entered TWRP
1. Swipe to Allow Modification
2. Tap on Wipe > Format Data > type in YES
3. Back to Menu
4. Tap on Install, (no-verify-opt-encrypt-6.0-star) - success
5. Reboot - Recovery
6. Tap on Install - (RMM-state-ByPass_Mesa.zip) - success
6. Hit back button
7. Tap on (SupserSu-v.2.82.201705271822.zip) - success
8 . Hit back button
9. Tap on (Samsung-anti-removal.2.4.zip) - success
10. Reboot system
11. Device begins reboot (Device stuck at Samsung S9 Screen)
Any advice what should I do now? Am I making any mistakes?
Please help. Appreciate!
Click to expand...
Click to collapse
I believe you need magisk.

Instead of using SuperSU try using Magisk, it's more simple has has more features compared to SuperSU.
Also I think the reason why you stuck at the bootscreen is that after you format your phone, that means your phone got no rom/ system. Maybe you can try installing the ROM from the custom one which you can find in the cross device section in Here (Exynos Only).
And each of them has the instruction on how to install Magisk to root your phone
Edit: The video you refered to I believe is for the android 9 version, if your phone is on android 10 then it's outdated for your phone

TheMadScientist said:
I believe you need magisk.
Click to expand...
Click to collapse
I actually tried with Magisk.. but it stays the same. Basically I replace stage 2, step 7 with Magisk instead of Supersu.
Flashing only Magisk does not mean I have any system in place correct?
B1nz said:
Instead of using SuperSU try using Magisk, it's more simple has has more features compared to SuperSU.
Also I think the reason why you stuck at the bootscreen is that after you format your phone, that means your phone got no rom/ system. Maybe you can try installing the ROM from the custom one which you can find in the cross device section in Here (Exynos Only).
And each of them has the instruction on how to install Magisk to root your phone
Edit: The video you refered to I believe is for the android 9 version, if your phone is on android 10 then it's outdated for your phone
Click to expand...
Click to collapse
My device was on Android 9 actually.. so I have the exact same version as the video shown. Today I have flashed back my device with Stock ROM on Android 10. Im not sure with the steps Im doing it is right, when should I actually flash a custom rom? Please correct me if im wrong, my stage 1 should be all correct. Stage 2, before step 10 rebooting system, I should actually flash Custom ROM? Because after formatting my device and installing Magisk on Stage 2 step 7, my device still got no rom right?

After flashing back my device with Stock ROM on Android 10, I tried to root my device again with the steps give in video (still failed, device stuck at Samsung Logo again).
Flashing back again with Stock ROM. Tried to enter download mode to start TWRP via Odin.
Then I was given a message "Only official release binaries are allowed to be flashed (RECOVERY)" in Download Mode
Now what? Does that mean I can't go flash anymore? :crying:

CounteReborn said:
My device was on Android 9 actually.. so I have the exact same version as the video shown. Today I have flashed back my device with Stock ROM on Android 10. Im not sure with the steps Im doing it is right, when should I actually flash a custom rom? Please correct me if im wrong, my stage 1 should be all correct. Stage 2, before step 10 rebooting system, I should actually flash Custom ROM? Because after formatting my device and installing Magisk on Stage 2 step 7, my device still got no rom right?
Click to expand...
Click to collapse
Yes, the steps that I did on my own by coming from stock ROM:
1. Flash TWRP from odin, disable the automatic reboot
2. If success, then manually reboot to TWRP
3. Then I formated my phone
4. Follow the custom ROM installation steps
5. Done!
note:
- Steps 1 & 2 is basically the same as what you've done.
- If you still want to running the stock ROM, you have to flash the modified one or you'll stuck on the boot screen.
My suggestion is using the Alexis ROM, which is more updated (already on oneUI 2.1), more light, has alot of features (which you can choose in the aroma installer), and built in Magisk. so you don't have to install magisk manually
---------- Post added at 12:55 PM ---------- Previous post was at 12:51 PM ----------
CounteReborn said:
After flashing back my device with Stock ROM on Android 10, I tried to root my device again with the steps give in video (still failed, device stuck at Samsung Logo again).
Flashing back again with Stock ROM. Tried to enter download mode to start TWRP via Odin.
Then I was given a message "Only official release binaries are allowed to be flashed (RECOVERY)" in Download Mode
Now what? Does that mean I can't go flash anymore? :crying:
Click to expand...
Click to collapse
is it written "Prenormal"?
there's this stage called prenormal where you failed to modified your phone for the firstime, basically you have to wait like 7 days until you can modify your phone again.
and if still failing, it will back to the prenormal stage.
so far that's what i know, correct me if i'm wrong
if not then you can try to flash TWRP to see if it works
Also the thing i realize is that to be able to flash TWRP in Odin you have to finished doing the first time setup on the ROM, idk why but that's what i'm facing back then

Are you on Android 10? If yes, i followed this video.
https://m.youtube.com/watch?feature=youtu.be&v=HSqam9CYNGU
---------- Post added at 09:19 AM ---------- Previous post was at 09:13 AM ----------
CounteReborn said:
After flashing back my device with Stock ROM on Android 10, I tried to root my device again with the steps give in video (still failed, device stuck at Samsung Logo again).
Flashing back again with Stock ROM. Tried to enter download mode to start TWRP via Odin.
Then I was given a message "Only official release binaries are allowed to be flashed (RECOVERY)" in Download Mode
Now what? Does that mean I can't go flash anymore? :crying:
Click to expand...
Click to collapse
Because you flashed the stock firmware, you might forgot to enable oem bootloader unlock?

B1nz said:
Yes, the steps that I did on my own by coming from stock ROM:
1. Flash TWRP from odin, disable the automatic reboot
2. If success, then manually reboot to TWRP
3. Then I formated my phone
4. Follow the custom ROM installation steps
5. Done!
note:
- Steps 1 & 2 is basically the same as what you've done.
- If you still want to running the stock ROM, you have to flash the modified one or you'll stuck on the boot screen.
My suggestion is using the Alexis ROM, which is more updated (already on oneUI 2.1), more light, has alot of features (which you can choose in the aroma installer), and built in Magisk. so you don't have to install magisk manually
---------- Post added at 12:55 PM ---------- Previous post was at 12:51 PM ----------
is it written "Prenormal"?
there's this stage called prenormal where you failed to modified your phone for the firstime, basically you have to wait like 7 days until you can modify your phone again.
and if still failing, it will back to the prenormal stage.
so far that's what i know, correct me if i'm wrong
if not then you can try to flash TWRP to see if it works
Also the thing i realize is that to be able to flash TWRP in Odin you have to finished doing the first time setup on the ROM, idk why but that's what i'm facing back then
Click to expand...
Click to collapse
Not sure what actually happened, but the message is now gone after restart.
Anyway, Do you know this website (https://desktop.firmware.mobi/) instead, can I just use the ROM here to flash my device?
Not sure if I could just do the same, downlaod the recovery and boot img, then flash via Odin?
mkl.xda said:
Are you on Android 10? If yes, i followed this video.
https://m.youtube.com/watch?feature=youtu.be&v=HSqam9CYNGU
---------- Post added at 09:19 AM ---------- Previous post was at 09:13 AM ----------
Because you flashed the stock firmware, you might forgot to enable oem bootloader unlock?
Click to expand...
Click to collapse
Not sure what I did again, but the message "Only official release binaries are allowed to be flashed (RECOVERY)" is now removed. I just recall I did a restart I think. I tried your video, it didn't work. I end up in the same screen which I now think this is expected case? Because once we completely wipe the phone, the device has no more ROM. So in the video, we only flash back Magisk and Disable Verify.
Do you know this website (https://desktop.firmware.mobi/) instead, can I just use the ROM here to flash my device?
Not sure if I could just do the same, downlaod the recovery and boot img, then flash via Odin?

CounteReborn said:
Not sure what actually happened, but the message is now gone after restart.
Anyway, Do you know this website (https://desktop.firmware.mobi/) instead, can I just use the ROM here to flash my device?
Not sure if I could just do the same, downlaod the recovery and boot img, then flash via Odin?
Click to expand...
Click to collapse
Never knew that before tho, but if you want to download the official one I would recomend you downlaod from the SamMobile, which I highly recommend and is already trusted by alot of users here, just choose the right model number and country and you're done!, or if you want a faster download then I recommend you to use either Frija or SamFirm which is the same, and both are tools to download firmware from SamMobile.
It will download a zip of firmware, you just have to extract it and flash it by using Odin, also for the CSC file choose the HOME_CSC don't choose the normal CSC,
if you able to get into the normal rom, then you can do the instruction that i give before
hope it works