DO NOT FLASH BOOTLOADERS EVEN ON YOUR PRECIOUS BOOTLOADER UNLOCKED S5 VERIZON YOU WILL HARD BRICK
this post is only for unlocked bootloaders i hard bricked my device 5 min ago because i flashed protected partitions on my s5 that was bootloader locked at the time
dont deviate in the slightest or you will likely hardbrick
there is an issue where you may have no data connection for me everything worked some people have reported this issue if you experience this issue go to post 8 in this thread
this will show you how to be on g900f firmware on g900v that is rooted and bootloader unlocked with pb1 unlocked bootloader installed
have device bootloader unlocked and rooted ON PB1 rooted firmware with bootloader unlock on pb1 bootloader
have busybox installed
have flashfire installed
have supersu installed
download flashfire and busybox apk put them onto your external sd card
download this firmware from sammobile.com G900FOXA1BOI3_BTU g900f firmware
put on external sd card
flash in flashfire
with these options checked
click flash firmware package: choose system
everroot: check inject supersu
reboot: check normal check preserve recovery
then flash
wait for reboot
you will still have root and bootloader unlock and twrp working
how to do it on locked bootloader PB1 ROOTED
evil_power said:
how to do it on locked bootloader PB1 ROOTED
Click to expand...
Click to collapse
I don't know if you will keep root or not will see what happens on a locked bootloader i will try to put up a guide by tonight, probably tomorrow night i'm a college student and i got homework to do
i will flash pb1 and root tonight and then try to flash in flashfire on a locked bootloader will tell you the results as soon as i know them
got secure check fail when i injected supersu so just tried ok3 root and i will see its a nope reflash pb1 and will try not wiping boot in
and i got it to boot with no root and i cant get it to transfer root so no there will be no root and recovery stock doesn't work bl unlocked people i will post a guide tommorow
I REPEAT DO NOT FLASH BOOTLOADERS OR PROTECTED PARTITIONS ON A BOOTLOADER LOCKED S5 YOU WILL HARD BRICK LIKE I JUST DID 5 MIN AGO
dont deviate in the slightest or you will hardbrick
everything worked for me but some people have issues with the data connection and call and text
this will show you how to be on g900f firmware on g900v that is rooted on pb1 firmware with bootloader locked
have device rooted
have busybox installed
have flashfire installed
have supersu installed
download this firmware from sammobile.com G900FOXA1BOI3_BTU g900f firmware
put on external sd card
flash in flashfire G900FOXA1BOI3_BTU g900f firmware in flashfire choose flash firmware option let it check md5
then with these options checked
click flash firmware package: choose system
everroot: disabled
reboot: check normal check preserve recovery
then flash
wait for reboot
you will not have root or bootloader unlock or a custom recovery
resserved
does your imei number change after doing this ?
i succesfully updated to G900F but run up to problem like sim card reading and someting not reading
and when i put *#06# nothing show up
evil_power said:
i succesfully updated to G900F but run up to problem like sim card reading and something not reading
and when i put *#06# nothing show up
Click to expand...
Click to collapse
i will update the op with a warning about possible no data/cell connection
i would have that issue sometimes when i flashed have and sometimes not will try to look into it I thought by not doing a wipe the data connection would stay because it did for me, but in the meantime the way to get back to g900v firmware is to flash the whole firmware in odin if you are bootloader locked this way you can root again if you only flash the system img in odin ok3 root method won't work.
if you are bootloader unlocked the way to get back to g900v firmware is to flash the system img tar for pb1 in odin it can be extracted from pb1 firmware tar with 7 zip file manager on your pc and then choose option add to archive and choose tar then flash system img tar in odin
evil_power said:
does your imei number change after doing this ?
Click to expand...
Click to collapse
i actually didn't even think about imei did it change for you?
Imeis will not change from this
Ok thanks I'm glad
Sent from my SM-G900V using Tapatalk
help me please
I booted g900v to g900f ... but privat mode not working and wifi workin but not saving password after restart phone and turn on not saved password
:good::good::good::good::good::good::good::good::good::good::good::good:
I don't own the g900v anymore so I can no longer help you sorry
Related
I used rom manager to install cwm. It said it was successful, but now i get the "Verizon has detected unauthorized software" when i try to boot into recovery. Can i safely install stock recovery. If so, what is the safest method?
ahiredgeek said:
I used rom manager to install cwm. It said it was successful, but now i get the "Verizon has detected unauthorized software" when i try to boot into recovery. Can i safely install stock recovery. If so, what is the safest method?
Click to expand...
Click to collapse
I think this is caused by bootloader, locked by 4.3 update. I do not know the answer to your question, however I have an additional one to whoever knows the answer: is there any custom recovery at all, which is known to properly work on 4.3+?
galets said:
I think this is caused by bootloader, locked by 4.3 update. I do not know the answer to your question, however I have an additional one to whoever knows the answer: is there any custom recovery at all, which is known to properly work on 4.3+?
Click to expand...
Click to collapse
If your on the locked bootloader 4.3 ML1 the only custom recovery option you have is safestrap, no cwm, twrp or philz
From my CM11 S3
but i actually used rom manager to flash the custom recovery and it said ti was a success. but when i try to enter recovery i get the Verizon error. i need to know if i can use safestrap or any other method to flash the native recovery back, so i can use the stock recovery.
or am i getting the Verizon error because i rooted my phone?
ahiredgeek said:
but i actually used rom manager to flash the custom recovery and it said ti was a success. but when i try to enter recovery i get the Verizon error. i need to know if i can use safestrap or any other method to flash the native recovery back, so i can use the stock recovery.
or am i getting the Verizon error because i rooted my phone?
Click to expand...
Click to collapse
If you have Odin installed on a Windows computer, flash the VRUDNE1 tar in the PDA slot. This should restore your phone to stock, VRUDNE1 4.4.2 stock firmware. You also will lose the data on the phone itself so choose your download wisely.
Download Odin from this post. Run Odin on your Windows PC, select PDA, then find the VRUDNE1 4.4.2 tar that you should have downloaded. Odin only flashes .tar or .tar.md5, it will not flash any files with anything else.
Tested on my Canadian i337M S4 (4.4.2 MVLUFNI2 firmware). Knox was not tripped.
This may work on other S4.
Summary of the Steps:
- Downgrade to special Kernel from W0lfdroid
- Root with TowelRoot
- Flash back 4.4.2 Kernel
- Downgrade to 4.2.2 Modem
- Unlock with RegionLock Away v1.3
- Flash back 4.4.2 Modem
Detailed Steps:
-=FILES REQUIRERD=-
Download these ROMs from SamMobile:
4.2.2 rom for your phone
- Use 7zip to extract MODEM.BIN from it
4.4.2 rom for your phone
- Use 7zip to extract MODEM.BIN from it
- Also use 7zip to extract BOOT.IMG (this is the Kernel), and archive it as a tar file.
-=ROOT=-
Follow this method:
http://www.w0lfdroid.com/2014/09/To...4-S5-and-Note3-Android-4.4.2-NF-or-Later.html
Important: for flashing back the Kernel, the 4.4.2 file from that site may not work properly (causes wifi to behave weird). You need to use the boot.img tar you made earlier.
-=UNLOCK=-
1. Put S4 into download mode by holding Volume Down and Home Button on startup, then press Volume Up
2. Attach Phone using USB cable
3. Start Odin
4. under the Files [Download] section 3rd button (Phone) point to the 4.2.2 modem.bin
5. click on start
6. --- After phone reboots, check it installed correctly by verifying the baseband version is the same as the one you just flashed
7. Once successful run RegionLockAway
8. Next you must install proper modem back using Odin
9. Start Odin
10. under the Files [Download] section 3rd button (Phone) point to the 4.4.2 modem.bin
11. click on start
12. --- After phone reboots, check it installed correctly by verifying the baseband is the same as the one you just flashed
Using Heimdall on Linux to flash stock ROM and getting everything back to original tripped KNOX for me.
Everything was done properly and ROM worked perfect. Oh well.
Tip: (lol)
When flashing stock firmware back to device stick to Windows stock ROM flashing methods. (Odin)
Wish I would of found this info a few weeks ago. niCCe!
ngold thanks
I have a phone from a guy at work it is a Rogers phone KNOX is already tripped the phone is rooted and on 4.4.2 MVLUFNI2 firmware can I still use your unlock method?
And if so which 4.2.2 firmware did you use on Sammobile I don't see any Canadian firmware listed for 4.2.2.
Do you have a link to the RegionLockAway is it just the 1.3 version I'm finding for the Note 3?
stdly said:
ngold thanks
I have a phone from a guy at work it is a Rogers phone KNOX is already tripped the phone is rooted and on 4.4.2 MVLUFNI2 firmware can I still use your unlock method?
And if so which 4.2.2 firmware did you use on Sammobile I don't see any Canadian firmware listed for 4.2.2.
Do you have a link to the RegionLockAway is it just the 1.3 version I'm finding for the Note 3?
Click to expand...
Click to collapse
Yeah you can use this method if KNOX is already tripped. (or you can just use CF-Autoroot as it saves some hassle)
To unlock, the firmware I used was VLUAMDJ . On Sammobile, you'll see it if you filter by Canada (Rogers).
For Regionlock Away 1.3, yes you can use the one posted in the Note 3 forum - http://forum.xda-developers.com/showthread.php?t=2470551
ngold said:
Yeah you can use this method if KNOX is already tripped. (or you can just use CF-Autoroot as it saves some hassle)
Click to expand...
Click to collapse
Thanks ngold,
Will CF-Autoroot unlock the phone it is already rooted?
stdly said:
Thanks ngold,
Will CF-Autoroot unlock the phone it is already rooted?
Click to expand...
Click to collapse
No CF-Autoroot only roots the phone. It trips the Knox, but it's easier. So if you already tripped Knox, that's the best method to root.
ngold said:
No CF-Autoroot only roots the phone. It trips the Knox, but it's easier. So if you already tripped Knox, that's the best method to root.
Click to expand...
Click to collapse
Thanks dude it worked I was worried because I didn't have a working sim card in it but no problems.
I can't flash the modem, bootloader locked?
download what roms? links?
If the phone has a 4.3 or newer bootloader, the phone can't be rooted without tripping knox as far as I know.
Hi,
I was planning to flash TWRP on my S6 on 5.1.1 and I see that the OEM unlock option in the developer options is missing. I can vouch that this was there when I was updating to 5.1.1 and even when I installed a custom kernel. Just wondering what my options are. Is it safe to flash or do I have to flash the firmware again to restore the functionality.
Just bought the galaxy s6 edge. I wanna root it but there is no "oem unlock" option in developer mode. Does this mean that the bootloader is already unlock or it just cant be unlocked?
Any solution to this?
SUperman00 said:
Just bought the galaxy s6 edge. I wanna root it but there is no "oem unlock" option in developer mode. Does this mean that the bootloader is already unlock or it just cant be unlocked?
Click to expand...
Click to collapse
Did u figured out any solution to this? I want to root my S6 Edge SM-G925I 5.1.1.. not able to! When I try flashing TWRP or custom kernel through Odin then it always stuck at some Mapping error.
HELP ME ? How can I?
I have this question as well on my 920i
I have an g920F s6. There is in developer options no oem unlock option in my stockrom 5.1.1
To root your phone use unibase v8 kernel flash this file via odin 3.10.6. Its for all models of the s6 except sprint and verizon.
When the phones reboots your rooted. You can flash twrp recovery via flashify
See this video
https://youtu.be/G5HDG6caoog
astraopcuser said:
I have an g920F s6. There is in developer options no oem unlock option in my stockrom 5.1.1
To root your phone use unibase v8 kernel flash this file via odin 3.10.6. Its for all models of the s6 except sprint and verizon.
When the phones reboots your rooted. You can flash twrp recovery via flashify
See this video
https://youtu.be/G5HDG6caoog
Click to expand...
Click to collapse
I used Odin 3 to install TWRP and it went without a hitch. Guess not having this is not a big issue at all.
Samsung G920F on nougat 7.0 QEG also dosn't have oem unlock button in developers option but i used odin 3.12 and flash correct recovery file it worked (means Bootloader is still unlocked on Android 7.0 for G920F) and do not forget to flash root also.
Pcsx2006 said:
Samsung G920F on nougat 7.0 QEG also dosn't have oem unlock button in developers option but i used odin 3.12 and flash correct recovery file it worked (means Bootloader is still unlocked on Android 7.0 for G920F) and do not forget to flash root also.
Click to expand...
Click to collapse
G920f variants come with unlocked bootloaders by default
I got the Galaxy S6 yesterday and coming from Nexus 5, I wanted to remove the existing bloatware by flashing the XtrestoLite Deodexed ROM. This one here: http://forum.xda-developers.com/galaxy-s6/samsung-galaxy-s-6--s-6-edge-unified-development/rom-xtrestolite-deodexed-mod-edition-1-3-t3119968
I'm haven't had much experience in rooting and it's my first time flashing a custom ROM. The phone was running on Android 5.1.1.
Apparently I failed. I started with CF-Root but I wasn't sure if it was done correctly. This was followed by TWRP 2.8.7.1 . Then I tried booting up the phone and the boot logo just loops. I tried to wipe the cache as well as the Delvik-cache through TWRP but it's still the same. Then I tried to flash the stock ROM that I found online but I got the error "Nand Write Start" followed by "Fail". I seem to have tried everything and now I just want to get the phone to work again. It shouldn't be so hard.
Someone help me please :crying:
Have you tried to flash the stock rom via Smart Switch software? There's an option in the top of the window where it says "More" called Emergency Recovery. When my S6 bricked nothing but that did the trick, you should give it a try.
Gallitho said:
Have you tried to flash the stock rom via Smart Switch software? There's an option in the top of the window where it says "More" called Emergency Recovery. When my S6 bricked nothing but that did the trick, you should give it a try.
Click to expand...
Click to collapse
How did you do it? I've installed the Smart Switch software but the device doesn't appear under the list in emergency software recovery, so I can't proceed.
Edit: I managed to do it through initialization. I'll update when it's done.
Edit 2: It worked! Thanks so much!
ztmj96 said:
How did you do it? I've installed the Smart Switch software but the device doesn't appear under the list in emergency software recovery, so I can't proceed.
Click to expand...
Click to collapse
Your PC is recognizing your phone? If not maybe you shall update your drivers first. My S6 is the same model number as yours and it does appears in the Emergency Recovery list.
Another solution could be trying to flash using another version of Odin; I saw a similar problem on another forum and it was solved using Odin 3.10 to reflash the stock firmware.
Also remember that you can't downgrade your firmware once that you are on 5.1.1, no 5.02 or so allowed.
ztmj96 said:
How did you do it? I've installed the Smart Switch software but the device doesn't appear under the list in emergency software recovery, so I can't proceed.
Click to expand...
Click to collapse
By the sounds of it you're able to boot into twrp? If so then simply boot into twrp, connect to your computer and copy a flashable rom to your phone and install it using twrp instead of odin
1qazwsx4 said:
By the sounds of it you're able to boot into twrp? If so then simply boot into twrp, connect to your computer and copy a flashable rom to your phone and install it using twrp instead of odin
Click to expand...
Click to collapse
How could I transfer the flashable ROM to the phone when I can't have it boot up to connect to my computer?
Gallitho said:
Your PC is recognizing your phone? If not maybe you shall update your drivers first. My S6 is the same model number as yours and it does appears in the Emergency Recovery list.
Another solution could be trying to flash using another version of Odin; I saw a similar problem on another forum and it was solved using Odin 3.10 to reflash the stock firmware.
Also remember that you can't downgrade your firmware once that you are on 5.1.1, no 5.02 or so allowed.
Click to expand...
Click to collapse
Since you're using the same model as mine, what are you running on your S6 right now? Are you able to root and flash a custom ROM like XtrestroLite onto Android 5.1.1?
Can you guys help me check if this post has the correct steps or is it missing anything like bootloader and root?
reddit.com/r/GalaxyS6/comments/39wwf6/should_i_install_xtrestolite_rom/cs7b7yq
ztmj96 said:
Since you're using the same model as mine, what are you running on your S6 right now? Are you able to root and flash a custom ROM like XtrestroLite onto Android 5.1.1?
Click to expand...
Click to collapse
Actually yeah. Earlier tonight I flashed XtreStoLite over stock 5.1.1, but I must confess it wasn't as easy as I thought, mainly because I didn't followed the steps in the right way and I ended up having to root my phone through installing UniKernel, which is pre-rooted and that did the trick for me, because I got stuck in the Samsung logo right after I tried to flash with CF-AutoRoot, needless to say I obviously couldn't root with that method and had to reflash stock 5.1.1 firmware to unbrick my phone, install UniKernel, and after that I was able to enter my phone config, uncheck the reactivation block under Find My Mobile settings (which was the reason for me to get stuck at the S-logo) and then flash through Odin XtreStoLite deodexed and Xposed FW too, so I can tell you for sure that SM-G920I can run XSL like a charm.
Gallitho said:
Actually yeah. Earlier tonight I flashed XtreStoLite over stock 5.1.1, but I must confess it wasn't as easy as I thought, mainly because I didn't followed the steps in the right way and I ended up having to root my phone through installing UniKernel, which is pre-rooted and that did the trick for me, because I got stuck in the Samsung logo right after I tried to flash with CF-AutoRoot, needless to say I obviously couldn't root with that method and had to reflash stock 5.1.1 firmware to unbrick my phone, install UniKernel, and after that I was able to enter my phone config, uncheck the reactivation block under Find My Mobile settings (which was the reason for me to get stuck at the S-logo) and then flash through Odin XtreStoLite deodexed and Xposed FW too, so I can tell you for sure that SM-G920I can run XSL like a charm.
Click to expand...
Click to collapse
1. So what is the correct order?
2. Did you have to manually unlock bootloader?
3. And is it a must to install uniKernel in order to root the device?
I have no idea how to proceed now.
This requires a lot more effort than I thought :fingers-crossed:
1. The correct order apparently WAS to flash 5.1.1 bootloader and modem over 5.0.2, then root, then TWRP, then flash XtreStoLite, or at least that was what I understood from Edgar's guide (as you can tell, I hurried myself too much and was to excited to flash XLS, so I didn't read properly).
Since I (and I think you did too) installed stock 5.1.1 first, there was no way to autoroot nor ping-pong root the device, that was the reason I got stuck in the Samsung logo screen after trying to autoroot, so I had to reflash stock 5.1.1 to regain access to the device settings/Find My Mobile as I explained before, after that I flashed UniKernel and that did the trick, no other steps were required to achieve root access beyond this point.
2. I didn't had to, but your carrier may have locked yours. My device is a SM-G920I (as yours) from Telcel carrier, so I can tell for sure.
3. There are several others way to root devices running over 5.0.2, but according to my personal research there aren't much options on 5.1.1 other than flash a pre-rooted kernel, but UniKernel isn't the only pre-rooted kernel, so you can choose whichever you like the most.
If I were you the first thing I'd try, as I said earlier, would be to switch to another Odin version or another firmware (as long as it is 5.1.1) and if that don't do the trick, then I'd update drivers and try via Smart Switch again.
Gallitho said:
1. The correct order apparently WAS to flash 5.1.1 bootloader and modem over 5.0.2, then root, then TWRP, then flash XtreStoLite, or at least that was what I understood from Edgar's guide (as you can tell, I hurried myself too much and was to excited to flash XLS, so I didn't read properly).
Since I (and I think you did too) installed stock 5.1.1 first, there was no way to autoroot nor ping-pong root the device, that was the reason I got stuck in the Samsung logo screen after trying to autoroot, so I had to reflash stock 5.1.1 to regain access to the device settings/Find My Mobile as I explained before, after that I flashed UniKernel and that did the trick, no other steps were required to achieve root access beyond this point.
2. I didn't had to, but your carrier may have locked yours. My device is a SM-G920I (as yours) from Telcel carrier, so I can tell for sure.
3. There are several others way to root devices running over 5.0.2, but according to my personal research there aren't much options on 5.1.1 other than flash a pre-rooted kernel, but UniKernel isn't the only pre-rooted kernel, so you can choose whichever you like the most.
If I were you the first thing I'd try, as I said earlier, would be to switch to another Odin version or another firmware (as long as it is 5.1.1) and if that don't do the trick, then I'd update drivers and try via Smart Switch again.
Click to expand...
Click to collapse
What did you use to root? May I ask for the link? I just tried flashing CF AutoRoot and now I think it's bricked again. (RECOVERY IS NOT SEANDROID ENFORCING) I'm thinking it might be due to incompatibility because I got it from here (https://autoroot.chainfire.eu/#odin) and the Android version states 5.0.2.
ztmj96 said:
What did you use to root? May I ask for the link? I just tried flashing CF AutoRoot and now I think it's bricked again. (RECOVERY IS NOT SEANDROID ENFORCING) I'm thinking it might be due to incompatibility because I got it from here (https://autoroot.chainfire.eu/#odin) and the Android version states 5.0.2.
Click to expand...
Click to collapse
Yep, that was the exact moment where mine got stuck too, as I stated before at that time I had to reflash stock firmware. The trouble is caused by CF-Autoroot, it won't work at all when you're on 5.1.1 (at least with SM-G920I) and if you try to root using this method, you'll get stuck with the message "RECOVERY IS NOT SEANDROID ENFORCING". You'll have to reflash to stock too, I'm affraid...
Flash UniKernel via Odin once you're on 5.1.1 stock again and see the magic happen. Once you have root access, gained by this kernel, you can install TWRP and flash XtreStoLite or any other rom you may want. Here is the direct link to the post: http://forum.xda-developers.com/galaxy-s6/samsung-galaxy-s-6--s-6-edge-unified-development/kernel-stockmod-kernel-t3100395
Hope you get lucky.
Gallitho said:
Yep, that was the exact moment where mine got stuck too, as I stated before at that time I had to reflash stock firmware. The trouble is caused by CF-Autoroot, it won't work at all when you're on 5.1.1 (at least with SM-G920I) and if you try to root using this method, you'll get stuck with the message "RECOVERY IS NOT SEANDROID ENFORCING". You'll have to reflash to stock too, I'm affraid...
Flash UniKernel via Odin once you're on 5.1.1 stock again and see the magic happen. Once you have root access, gained by this kernel, you can install TWRP and flash XtreStoLite or any other rom you may want. Here is the direct link to the post: http://forum.xda-developers.com/galaxy-s6/samsung-galaxy-s-6--s-6-edge-unified-development/kernel-stockmod-kernel-t3100395
Hope you get lucky.
Click to expand...
Click to collapse
I just did that before you suggested it and it worked! I was so elated! I love you bro (no homo). Our situations are identical. Now I have XtrestroLite running on the S6! Thank you so much!
Simply put:
1. Update bootloader and modem
2. Install TWRP without root via Odin
3. Install UniKernel via TWRP
4. Install ROMs!
ztmj96 said:
I just did that before you suggested it and it worked! I was so elated! I love you bro (no homo). Our situations are identical. Now I have XtrestroLite running on the S6! Thank you so much!
Simply put:
1. Update bootloader and modem
2. Install TWRP without root via Odin
3. Install UniKernel via TWRP
4. Install ROMs!
Click to expand...
Click to collapse
Glad to read that, dude!
Yep, our situations are identical and also happened at the same time haha.
Now's time to enjoy! :good:
Hey.
Just installed TWRP from the guide on XDA (will post link later). Odin worked, everything was OK. Until I installed a ROM.
I have tried 4 different ROMs withone outcome - phone wont get past first boot screen - the one witn Samsung S-+ Powered by Android. No matter the minutes I wait, it just stays there. No Samsung logo as normal boot is displayed.
I can freely get to recovery or bootloader. But there is a problem - I dont know the precise string full model number after G955F*. Therefore I dont know what stock image or bootloader to choose.
My questions:
1. How to get back to working phone?
2. How to check the full model number in this situation?
TWRP works perfectly. Odin works. Just System wont boot...
Thanks in advance!
Tom
Did you flash magisk before the first boot ?
Did you forget to OEM Unlock ?
Did you flash the right firmware for your device ?
If you forgot to OEM Unlock your royally screwed, follow the steps again to the letter and try CF-Autoroot or magisk after first boot.
Tried both Magisk and SuperSu, both no luck. I did update the phone via OTA, did not flash anything besides TWRP via Odin. Both Magisk and SuperSu were part of AROMA for the ROM.
I have G955F European version. Can I flash any ROM from Any country that matches the model name (via Odin) or do I need specific version that corresponds with my previous stock ROM verson (string after G955F*).
I did unlock OEM on stock ROM before TWRP flash. Downloader mode shows Unlocked True.
MecenasPL said:
Tried both Magisk and SuperSu, both no luck. I did update the phone via OTA, did not flash anything besides TWRP via Odin. Both Magisk and SuperSu were part of AROMA for the ROM.
I have G955F European version. Can I flash any ROM from Any country that matches the model name (via Odin) or do I need specific version that corresponds with my previous stock ROM verson (string after G955F*).
I did unlock OEM on stock ROM before TWRP flash. Downloader mode shows Unlocked True.
Click to expand...
Click to collapse
That's exactly what i did for mine, odd try flashing the bat stock ROM, also fash the Notorious kernel.
You CSC in aroma should be set to multi ( it's the default selection ) keep everything stock when you flash the ROM and see if it boots before falshing anything else, there is a newer TWRP now ending 3.1.1-1.
Strange thing is, whenever I turn on my phone it boots straight to Recovery - like there's no system partition.
I will download and try BatStock. Should I upgrade bootloader & modem through Odin?
I'm also thinking about flashing stock ROM through Odin. Maybe this will work?
Also, it's strange - I don't see any other files than TWRP folder when I connect the phone to PC.
Installed BatStock Rom, same thing happens - stuck on SAMSUNG Galaxy S8+ Powered by Android and nothing happens.
BatStock ROM in Aroma has option to flash bootloader and modem. Should I use it?