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:
Related
My phone is rooted, and has TWRP custom recovery installed.
The phone automatically downloaded the OTA, and tried to install it. With TWRP, the update failed and my phone is working fine now.
I don't need the rooting anymore (was for teetering, but with new data plan it's now included). So I'm okay with losing the root and all.
Using SuperSU I deselected the rooting, and after reboot RootCheck tells me my phone is not rooted. I still have TWRP installed.
Now, I'm stock MF1/ 4.1.2. How do I install the 4.3 update and remove the TWRP recovery? I found in another thread the 4.3 Tar file. Do I simply use Odin on my PC and flash it on my phone? What about TWRP?
airtrons said:
My phone is rooted, and has TWRP custom recovery installed.
The phone automatically downloaded the OTA, and tried to install it. With TWRP, the update failed and my phone is working fine now.
I don't need the rooting anymore (was for teetering, but with new data plan it's now included). So I'm okay with losing the root and all.
Using SuperSU I deselected the rooting, and after reboot RootCheck tells me my phone is not rooted. I still have TWRP installed.
Now, I'm stock MF1/ 4.1.2. How do I install the 4.3 update and remove the TWRP recovery? I found in another thread the 4.3 Tar file. Do I simply use Odin on my PC and flash it on my phone? What about TWRP?
Click to expand...
Click to collapse
Are you sure you want the 4.3, this latest rom will lock your bootloader permanently, meaning you will NOT able to install CWM,TWRP, custom rom/kernel or downgrade the OS to the early version. The only thing you can do once updated is root. If you still decided to upgrade, just Odin the full rom MF1 here http://www.androidfilehost.com/?fid=23134718111254196 then after bootup your OS should auto update to the latest (OTA).
airtrons said:
My phone is rooted, and has TWRP custom recovery installed.
The phone automatically downloaded the OTA, and tried to install it. With TWRP, the update failed and my phone is working fine now.
I don't need the rooting anymore (was for teetering, but with new data plan it's now included). So I'm okay with losing the root and all.
Using SuperSU I deselected the rooting, and after reboot RootCheck tells me my phone is not rooted. I still have TWRP installed.
Now, I'm stock MF1/ 4.1.2. How do I install the 4.3 update and remove the TWRP recovery? I found in another thread the 4.3 Tar file. Do I simply use Odin on my PC and flash it on my phone? What about TWRP?
Click to expand...
Click to collapse
I had the same question myself, and have been proverbially "running around in circles" today (instead of working). Anybody have success flashing said Odin file and then upgrading via the OTA?
Ha! I came from a mytouch3g years ago, flashing incessantly. I got this phone so i could stop. Then rooted to take the ads away, and got a bit more than I bargained for... now I just want back on OTA stock.
Thanks for any suggestions.
Cheers
Kevvy1066 said:
I had the same question myself, and have been proverbially "running around in circles" today (instead of working). Anybody have success flashing said Odin file and then upgrading via the OTA?
Ha! I came from a mytouch3g years ago, flashing incessantly. I got this phone so i could stop. Then rooted to take the ads away, and got a bit more than I bargained for... now I just want back on OTA stock.
Thanks for any suggestions.
Cheers
Click to expand...
Click to collapse
if you download this full firmware http://www.androidfilehost.com/?fid=23134718111254196 unzip the file then use Odin to flash, this will bring you back to pure stock rom with stock recovery (no more twrp/cwm). After this you will be prompt for OTA and just take the upgrade. Once done you should be on the latest factory 4.3 with locked bootloader.
I ended up downloading the 4.3 files from another post here, and flashing it with Odin. Worked fine.
Of course, without a root, can't recover my apps from Titanium but oh well.
airtrons said:
I ended up downloading the 4.3 files from another post here, and flashing it with Odin. Worked fine.
Of course, without a root, can't recover my apps from Titanium but oh well.
Click to expand...
Click to collapse
Why don't you just root with saferoot found here?http://forum.xda-developers.com/showthread.php?t=2565758
I wish I would have found this thread before starting my own... woops. Anyway I would like to install 4.3 and I too rooted with twrp. I don't care anymore if I am rooted or not. I stopped flashing roms and such a while back and will be upgrading this next year to the s5 most likely.
Is there a way to install 4.3 w/out removing root? If not, since I never used odin, and used twrp what steps do/should I take to get back to where I can install 4.3?
Thank you.
Sithlyone said:
I wish I would have found this thread before starting my own... woops. Anyway I would like to install 4.3 and I too rooted with twrp. I don't care anymore if I am rooted or not. I stopped flashing roms and such a while back and will be upgrading this next year to the s5 most likely.
Is there a way to install 4.3 w/out removing root? If not, since I never used odin, and used twrp what steps do/should I take to get back to where I can install 4.3?
Thank you.
Click to expand...
Click to collapse
Since your life is too busy and you don't want to mess with your phone anymore, your best bet is go back to stock 4.3 which is very good by the way, very stable, smooth and bug free. After so many complaints from my wife I rolled it back to stock 4.3 and she's so happy now.
1. Flash stock MF1 here http://www.androidfilehost.com/?fid=23134718111254196 , just unzip the flash with Odin
2. Your phone should take the 4.3 OTA update and you're home free.
Hi,
I wanted to install a custom rom but seems like it was unsuccesful.. D: Now i'm stuck at the "Samsung Galaxy S6" logo. I can enter the recovery mode though. Is there a way to fix it?
There's also a message in red which says "recovery is not seandroid enforcing".
Thanks in advance!
*Solved: Flashed the wrong version of twrp. That caused the issue. Flashed the 5.1.1 stock rom problem solved
AxelBlade said:
Hi,
I wanted to install a custom rom but seems like it was unsuccesful.. D: Now i'm stuck at the "Samsung Galaxy S6" logo. I can enter the recovery mode though. Is there a way to fix it?
There's also a message in red which says "recovery is not seandroid enforcing".
Thanks in advance!
Click to expand...
Click to collapse
Here are two separate techniques. First try a factory data reset from recovery. If that fails use odin to restore the stock firmware
Snowby123 said:
Here are two separate techniques. First try a factory data reset from recovery. If that fails use odin to restore the stock firmware
Click to expand...
Click to collapse
Oh wait, just re-readed what i typed. Seems like it rolled back. The problem started after installing the recovery. 1st i rooted it with odin which worked after testing if i had root. Afterwards i installed twrp with odin aswell, rebooted and everything was still working. Then i went to flashify and chose "boot to recovery" which led me to my actual problem.
During the instalation of twrp i din't have any issue, it just said "Pass". So no recovery mode for me
Can i just download the stock rom 5.0 from the forums? I had android 5.1. If not, is there any place to download the stock 5.1 rom? (Sammobile is way too slow)
Also, when i said "i can enter recovery mod though" i meant, download mode.
AxelBlade said:
Oh wait, just re-readed what i typed. Seems like it rolled back. The problem started after installing the recovery. 1st i rooted it with odin which worked after testing if i had root. Afterwards i installed twrp with odin aswell, rebooted and everything was still working. Then i went to flashify and chose "boot to recovery" which led me to my actual problem.
During the instalation of twrp i din't have any issue, it just said "Pass". So no recovery mode for me
Can i just download the stock rom 5.0 from the forums? I had android 5.1. If not, is there any place to download the stock 5.1 rom? (Sammobile is way too slow)
Also, when i said "i can enter recovery mod though" i meant, download mode.
Click to expand...
Click to collapse
Download mode is totally different from recovery mode. As long as you can boot into download mode you should install stock 5.0.2 through odin. It will unbrick and unroot
Snowby123 said:
Download mode is totally different from recovery mode. As long as you can boot into download mode you should install stock 5.0.2 through odin. It will unbrick and unroot
Click to expand...
Click to collapse
Thank you, downloading right now the stock rom. Also, any clue of what could've failed during the process of the twrp instalation? I installed this version :/
https://twrp.me/devices/samsunggalaxys6.html
Just asking to avoid the same issue in the future.
AxelBlade said:
Thank you, downloading right now the stock rom. Also, any clue of what could've failed during the process of the twrp instalation? I installed this version :/
https://twrp.me/devices/samsunggalaxys6.html
Just asking to avoid the same issue in the future.
Click to expand...
Click to collapse
I have no experience with TWRP. All I know about TWRP is it makes flashing zip files easier
AxelBlade said:
Oh wait, just re-readed what i typed. Seems like it rolled back. The problem started after installing the recovery. 1st i rooted it with odin which worked after testing if i had root. Afterwards i installed twrp with odin aswell, rebooted and everything was still working. Then i went to flashify and chose "boot to recovery" which led me to my actual problem.
During the instalation of twrp i din't have any issue, it just said "Pass". So no recovery mode for me
Can i just download the stock rom 5.0 from the forums? I had android 5.1. If not, is there any place to download the stock 5.1 rom? (Sammobile is way too slow)
Also, when i said "i can enter recovery mod though" i meant, download mode.
Click to expand...
Click to collapse
You can't go back to 5.0.2 if you took the 5.1.1 update because of the new bootloader also the reason you are stuck on the splash screen was because you started with 5.1.1 and probably used an older version of TWRP use 2.8.7.1 not 2.8.7.0 or anything lower because 2.8.7.1 is the only one that works for 5.1.1 on this new bootloader.
Odin back to 5.1.1 not 5.0.2 and I understand SamMobile is very slow so use this thread it has most firmwares mirrored http://forum.xda-developers.com/galaxy-s6/general/stock-firmware-official-stock-firmware-t3086387
ethanscooter said:
You can't go back to 5.0.2 if you took the 5.1.1 update because of the new bootloader also the reason you are stuck on the splash screen was because you started with 5.1.1 and probably used an older version of TWRP use 2.8.7.1 not 2.8.7.0 or anything lower because 2.8.7.1 is the only one that works for 5.1.1 on this new bootloader.
Odin back to 5.1.1 not 5.0.2 and I understand SamMobile is very slow so use this thread it has most firmwares mirrored http://forum.xda-developers.com/galaxy-s6/general/stock-firmware-official-stock-firmware-t3086387
Click to expand...
Click to collapse
Just in case i downloaded both. So i just have to reflash 5.1.1 and use TWRP 2.8.7.1 right? Welp, just noticed by checking my downloads that i downloaded the 2.8.6.0, now everything makes sense. Going to go back to stock and do all the procedure once again. I'll keep in touch!
AxelBlade said:
Just in case i downloaded both. So i just have to reflash 5.1.1 and use TWRP 2.8.7.1 right? Welp, just noticed by checking my downloads that i downloaded the 2.8.6.0, now everything makes sense. Going to go back to stock and do all the procedure once again. I'll keep in touch!
Click to expand...
Click to collapse
OK, correct flash 2.8.7.1 and flash to 5.1.1 but if you go back to 5.0.2 then you will brick your phone also tip when flashing custom roms use unikernel or some kind of custom kernel because sometimes it won't boot also you will have this same problem if you flash a rom based on 5.0.2
ethanscooter said:
OK, correct flash 2.8.7.1 and flash to 5.1.1 but if you go back to 5.0.2 then you will brick your phone also tip when flashing custom roms use unikernel or some kind of custom kernel because sometimes it won't boot also you will have this same problem if you flash a rom based on 5.0.2
Click to expand...
Click to collapse
Yay! Phone booting perfectly after flashing the 5.1.1 stock rom. Rooted, installed twrp and a custom rom aswell
Thanks for your help guys
Hi to All!: I'm new to this forum and you may consider me a newbie, willing to learn from you and share my experiences in the near future. Just recently I managed to root my Samsung Galaxy S5 SM-G900V running Lollipop latest release (OK3) following this tutorial (thanks a lot to jrkruse for that!!). Now I'm trying to install a Custom Recovery, I tried Safestrap (Safestrap-KLTEVZW-NCG-3.75-B03.apk), ClockworkMod (philz_touch_6.41.6-klte.tar) and TWRP (twrp-2.8.7.0-klte, tar & img versions) and this is what happened:
----Safestrap App installed successfully but failed to install Recovery.
----ClockworkMod (Philz Touch variant) failed to flash with Odin.
----TWRP succeeded to install via ADB shell, replaced Stock Recovery but gave this error:
''RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING''
I ended flashing Stock OK3 to have at least Stock Recovery again!, it's known OE1, OG5 and OK3 updates prevent downgrading, I want to downgrade to 4.4.4 to solve some wi-fi issues I've been having since Lollipop updates.
Some help about this subject will be very appreciated!!
Thanks a lot in advance to all members of this awesome forum!!
cd2xtac said:
Hi to All!: I'm new to this forum and you may consider me a newbie, willing to learn from you and share my experiences in the near future. Just recently I managed to root my Samsung Galaxy S5 SM-G900V running Lollipop latest release (OK3) following this tutorial (thanks a lot to jrkruse for that!!). Now I'm trying to install a Custom Recovery, I tried Safestrap (Safestrap-KLTEVZW-NCG-3.75-B03.apk), ClockworkMod (philz_touch_6.41.6-klte.tar) and TWRP (twrp-2.8.7.0-klte, tar & img versions) and this is what happened:
----Safestrap App installed successfully but failed to install Recovery.
----ClockworkMod (Philz Touch variant) failed to flash with Odin.
----TWRP succeeded to install via ADB shell, replaced Stock Recovery but gave this error:
''RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING''
I ended flashing Stock OK3 to have at least Stock Recovery again!, it's known OE1, OG5 and OK3 updates prevent downgrading, I want to downgrade to 4.4.4 to solve some wi-fi issues I've been having since Lollipop updates.
Some help about this subject will be very appreciated!!
Thanks a lot in advance to all members of this awesome forum!!
Click to expand...
Click to collapse
On OK3 the bootloader is locked. You cannot downgrade to 4.4.2 or 4.4.4 or any other previous version. You also cannot install custom recoveries like ClockworkMod or TWRP. You are relegated to Safestrap or FlashFire as discussed in jrkruse's threads.
You can ONLY use SafeStrap. TWRP and Clockworkmod cannot load because we have a locked bootloader.
You must flash a kitkat kernel to boot into safestrap, which I gather you didn't do. Then when you're done in Safestrap, flash a safestrap-flashable lollipop kernel BEFORE EXITING SAFESTRAP to boot back into your ROM.
@ landshark68
@painiac
Thank both for your replies!, let's see if I misunderstood something: flashing NI2 Stock Kernel with Odin will give the possibility to boot into Safestrap and flash zip of Stock NI2 ROM (4.4.4) or will I remain tied to OK3 even if I flash the KitKat Kernel?
cd2xtac said:
@ landshark68
@painiac
Thank both for your replies!, let's see if I misunderstood something: flashing NI2 Stock Kernel with Odin will give the possibility to boot into Safestrap and flash zip of Stock NI2 ROM (4.4.4) or will I remain tied to OK3 even if I flash the KitKat Kernel?
Click to expand...
Click to collapse
You will remain tied to OK3
@cd2xtac
I'm just curious about the whole flashing a custom recovery part you were talking about..
It let you flash one?
Normally I'd just shrug a thread like this off but when you said you tried to boot into recovery and saw
Code:
RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING
that means it actually let you flash a custom recovery.
So my real questions here are, in download mode, does it say Knox 0x1?
And/or after you tried to boot into twrp, did it say "set warranty bit: recovery"?
This part makes me curious because on a locked bootloader, we shouldn't be able to flash a custom recovery.
Or maybe we can and just can't boot into it.
I haven't looked into this much because I've always just accepted that a locked bootloader means we need to use SS or FF and can't flash custom ROMs like CM.
Although I am curious what makes Samsung phones different than my old Droid Bionic. It has a locked bootloader and can only use Safestrap but it can still flash CM13 in a non-stock ROM slot. Why can'take we?
Perhaps I should call someone like @jrkruse in to see if he can clarify or if he knows why.
Dudash said:
@cd2xtac
I'm just curious about the whole flashing a custom recovery part you were talking about..
It let you flash one?
Normally I'd just shrug a thread like this off but when you said you tried to boot into recovery and saw
Code:
RECOVERY BOOTING...
RECOVERY IS NOT SEANDROID ENFORCING
that means it actually let you flash a custom recovery.
So my real questions here are, in download mode, does it say Knox 0x1?
And/or after you tried to boot into twrp, did it say "set warranty bit: recovery"?
This part makes me curious because on a locked bootloader, we shouldn't be able to flash a custom recovery.
Or maybe we can and just can't boot into it.
I haven't looked into this much because I've always just accepted that a locked bootloader means we need to use SS or FF and can't flash custom ROMs like CM.
Although I am curious what makes Samsung phones different than my old Droid Bionic. It has a locked bootloader and can only use Safestrap but it can still flash CM13 in a non-stock ROM slot. Why can'take we?
Perhaps I should call someone like @jrkruse in to see if he can clarify or if he knows why.
Click to expand...
Click to collapse
Because on other phones they had ways to trick the phone into letting a custom kernel be flashed. These ways dont work on S5. Also Rom slots dont work on our phone either unless you go back to kitkat, but you were still booting off of main kernel,so still no go
jrkruse said:
Because on other phones they had ways to trick the phone into letting a custom kernel be flashed. These ways dont work on S5. Also Rom slots dont work on our phone either unless you go back to kitkat, but you were still booting off of main kernel,so still no go
Click to expand...
Click to collapse
Thanks for clarifying
Hello,
I rooted my s5 way back when it first came out but I haven't upgraded the firmware at all. From what I remember I had trouble installing a custom recovery so the phone is only rooted. I would like to bring it up to the most current version of android. What's the easiest way to do that? I'm on baseband version G900PVPUIAND2.
Thanks in advance.
Edit: I found this https://forum.xda-developers.com/showthread.php?t=2742994 which had a link to the stock factory image but sammobile doesn't seem to be hosting it anymore. Is there another reliable place that I can get it? Or would just doing a factory reset of my phone make it so I can start taking OTA's again?
The latest stock firmware for G900V is Marshmallow QC1. You can download it here and use ODIN to flash it:
https://www.androidfilehost.com/?fid=457095661767155677
If you want to root it you can use CF-Autoroot in ODIN. This will trip Knox if not already tripped (but probably doesn't matter on an older phone like this).
https://download.chainfire.eu/408/CF-Root/CF-Auto-Root/CF-Auto-Root-kltespr-kltespr-smg900p.zip
If you want to install TWRP you can use ODIN again:
https://twrp.me/devices/samsunggalaxys5qualcomm.html
Good luck.
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?