Database Users

[Q] Need help installing Custom ROM on SPH-L720 MK2 Baseband

I used to have Verizon Gs3 and played a lot with Custom Roms.
Recently changed to Sprint Gs4.
I am on L720VPUEMK2 baseband.(Most recent Stock 4.3)
I did root my device by flashing CF-Auto-Root and Phil Touch Wiz 5.18.2 ( ODIN mode)
Here comes the challenge:
When I try to flash any custom rom using Recovery mode I am getting stuck at Boot screen with error.
Funny thing is If i use Cyanogen Mod Installer directly from My Laptop to flash 10.2 version.
I am guessing it has some thing to do with Samsung Knox Boot Loader.
Can some one help me with getting around this to flash custom Rom?

its been my experience with philz recovery once you factory reset you have to go into power menu and reboot into recovery again and then flash rom

loumoli said:
its been my experience with philz recovery once you factory reset you have to go into power menu and reboot into recovery again and then flash rom
Click to expand...
Click to collapse
So you are saying that Once I flash the Rom
1. Go back to Recovery and Do a factory Reset
2. Re-Flash the Desired Rom.
I tried this too.
Its not just Philz Recovery. I user CWM Recovery as well and having similar issues.

[email protected] said:
I used to have Verizon Gs3 and played a lot with Custom Roms.
Recently changed to Sprint Gs4.
I am on L720VPUEMK2 baseband.(Most recent Stock 4.3)
I did root my device by flashing CF-Auto-Root and Phil Touch Wiz 5.18.2 ( ODIN mode)
Here comes the challenge:
When I try to flash any custom rom using Recovery mode I am getting stuck at Boot screen with error.
Funny thing is If i use Cyanogen Mod Installer directly from My Laptop to flash 10.2 version.
I am guessing it has some thing to do with Samsung Knox Boot Loader.
Can some one help me with getting around this to flash custom Rom?
Click to expand...
Click to collapse
Use PC Odin to flash Philz latest recovery.
But in Odin don't check the "Auto Reboot". When Odin is finished unplug the phone and hard power it off or batter pull.
Edited for clarity - Meant AutoReboot

leaderbuilder said:
Use PC Odin to flash Philz latest recovery.
But in Odin don't check the f.reset. When Odin is finished unplug the phone and hard power it off or batter pull.
Click to expand...
Click to collapse
i will give this a try today after work.
Will let you know

[email protected] said:
i will give this a try today after work.
Will let you know
Click to expand...
Click to collapse
Meant - "Auto Reboot". Didn't have enough coffee yet.

leaderbuilder said:
Meant - "Auto Reboot". Didn't have enough coffee yet.
Click to expand...
Click to collapse
So when i did install custom Rom I am stuck on Samsung Galaxy s4 Screen
With Error
KERNeL IS NOT SEANDROID ENFORCING ( RED color)
Set Warranty Bit : Kernel (Yellow Color)
Its about 10 Minutes now and I will leave it that way for 1 more hour.
Update: its been 30 mins and am still stuck in that screen.

I'm curious as to what ends up happening with this. I was reading how to flash a custom rom, by using Clockworkmod Recovery.
It looks like the CWM is flashed in via ODIN after the root as a .tar.md5, then you factory reset/wipe data, then wipe cache, then wipe davilk cache, then install from .zip extSDcard. It seemed simple enough, and I have the same model as you, but it appears there are hang ups that you are having which I'll wait until I try it.
I also have stock ROM and MK2 GS4 with Sprint.

[email protected] said:
So when i did install custom Rom I am stuck on Samsung Galaxy s4 Screen
With Error
KERNeL IS NOT SEANDROID ENFORCING ( RED color)
Set Warranty Bit : Kernel (Yellow Color)
Its about 10 Minutes now and I will leave it that way for 1 more hour.
Update: its been 30 mins and am still stuck in that screen.
Click to expand...
Click to collapse
Reflash a ROM
Sent from my SPH-L720 using Tapatalk

daniel4653 said:
Reflash a ROM
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
Did So. And no changes.
Stuck in The same screen.

[email protected] said:
Did So. And no changes.
Stuck in The same screen.
Click to expand...
Click to collapse
Forgot you have to wipe data. And fdont flash any kernel or anything like that.
Sent from my SPH-L720 using Tapatalk

[email protected] said:
I used to have Verizon Gs3 and played a lot with Custom Roms.
Recently changed to Sprint Gs4.
I am on L720VPUEMK2 baseband.(Most recent Stock 4.3)
I did root my device by flashing CF-Auto-Root and Phil Touch Wiz 5.18.2 ( ODIN mode)
Here comes the challenge:
When I try to flash any custom rom using Recovery mode I am getting stuck at Boot screen with error.
Funny thing is If i use Cyanogen Mod Installer directly from My Laptop to flash 10.2 version.
I am guessing it has some thing to do with Samsung Knox Boot Loader.
Can some one help me with getting around this to flash custom Rom?
Click to expand...
Click to collapse
make sure to wipe delvic and cache and what is the error, it sounds like a bad download possibly

deneid310 said:
make sure to wipe delvic and cache and what is the error, it sounds like a bad download possibly
Click to expand...
Click to collapse
No you get that error when you trip Knox. Well at least it did for me.
Sent from my SPH-L720 using Tapatalk

daniel4653 said:
No you get that error when you trip Knox. Well at least it did for me.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
How did you Pass that?

[email protected] said:
How did you Pass that?
Click to expand...
Click to collapse
By rooting with saferoot in Verizon forum or kingo app
Sent from my SPH-L720 using Tapatalk

daniel4653 said:
By rooting with saferoot in Verizon forum or kingo app
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
If you root with safe root you are correct, you won't trip the knox warranty flag. But you can't install a custom rom without flashing a custom recovery which is what actually trips the knox flag not root. So safe root is only good if you are going to run stock rooted and not install a custom rom.

[email protected] said:
How did you Pass that?
Click to expand...
Click to collapse
My sprint s4 with Philz does the same exact thing, gets stuck at the same screen. Sometimes it takes a few then boots up , other times I have to manually reboot it.
I've tried many things myself and still this problem confines.
I've asked in other threads about this but no one had an idea of way.
The phone was on MK2, rooted with CF Auto, and has latest Philz.
I'll be checking in here to see if we can fix this... If it's even fixable. I think it has to do with Knox /new security.. But I'm no programmer so maybe a pro can chime in.
Sent from my SCH-I545 using XDA Premium 4 mobile app

Hoping for some experts to help us.. May be a video on how to root of MK2 version And flash custom Rom will help us..
Sent from Sprint GS4

SOLVED recovery is not seandroid enforcing set warrenty bit : recovery --> loop

after I had succesfully rooted my phone, I wanted to install a custom rom.
I am sure I did something wrong ofcource otherwise I wouldn't be here.
#1 Battery in
#2 power on
#3 vibrate
#4 screen on RECOVERY BOOTING
Recovery is NOT SEANDROID ENFORCING
Set Warrenty Bit : recovery
Samsung
GALAXY Note3
SM-N9005
#5 screen off--> reboot -->goto #3
how to brake in the loop so I can use odin ( or whatever ) to install (at least) a normal boot again?

Which custom recovery did you flashed Twrp or Cwm?
Sent from my SM-N900W8 using xda app-developers ap

fwberg said:
after I had succesfully rooted my phone, I wanted to install a custom rom.
I am sure I did something wrong ofcource otherwise I wouldn't be here.
#1 Battery in
#2 power on
#3 vibrate
#4 screen on RECOVERY BOOTING
Recovery is NOT SEANDROID ENFORCING
Set Warrenty Bit : recovery
Samsung
GALAXY Note3
SM-N9005
#5 screen off--> reboot -->goto #3
how to brake in the loop so I can use odin ( or whatever ) to install (at least) a normal boot again?
Click to expand...
Click to collapse
You installed a 4.3 recovery on a 4.4 phone.
Most likely you downloaded the TWRP on the main page and did not download the latest 4.4 compatible one.
Please flash this in Download Mode: http://techerrata.com/bigbiff/hlte-recovery.img.tar
To get into Download Mode, remove the battery, wait a few minutes then put it back, Hold the Download Mode Combination then it would boot directly into Download Mode.

hey nicho, thank you very much
so that was the trick. REMOVE THE BATTERY --> PRESS THE DOWNLOAD KEYS AND HOLD THEM --> THEN ENTER THE BATTERY BACK.
it costed me the whole day yesterday searching for a solution.
at least now I can continue to install a new rom
Thanks man

TWRP
during twrp it told me, there was a newer one. 2.x.x.9
so stupid me, if I had sticked to the plan, nothing would happend.
I used twrp b4 some days ago, for my samsung note 10.1 (2014) without trubbles,
I guess, I overread something
but I'm happy it is all fixed now.
thx for show ur interest
greetz, fred

thank you
nicholaschum said:
You installed a 4.3 recovery on a 4.4 phone.
Most likely you downloaded the TWRP on the main page and did not download the latest 4.4 compatible one.
Please flash this in Download Mode: techerrata.com/bigbiff/hlte-recovery.img.tar
To get into Download Mode, remove the battery, wait a few minutes then put it back, Hold the Download Mode Combination then it would boot directly into Download Mode.
Click to expand...
Click to collapse
this solved my recovery problem, i clicked thank you!!!

nicholaschum said:
You installed a 4.3 recovery on a 4.4 phone.
Most likely you downloaded the TWRP on the main page and did not download the latest 4.4 compatible one.
Please flash this in Download Mode: http://techerrata.com/bigbiff/hlte-recovery.img.tar
To get into Download Mode, remove the battery, wait a few minutes then put it back, Hold the Download Mode Combination then it would boot directly into Download Mode.
Click to expand...
Click to collapse
You just saved my phone i readed so much almost one week 12hours without stop before i try custom recovery,rom and so on.
But well since i decided that im ready to, and first thing i tried to do was custom recovery wich leaded to this problam Now im afraid to enter revovery mode xD

Idiots
You're really the dumbest person I've ever seen in my life. See if this is solution to some kind of problem your beast

Worked for me
Thank you.
remove the battery then press download buttons keep them pressed and put the battery back. choose volume down to continue....

Solution To Loop SM-N900P
I am new to XDA and have only been with android for 6 months but i figure this will help new comers to this issue. Power+Volume Down+Home at the same time to enter download mode. Flash CWM via ODIN. This should work to fix the loop. I found out the hard way but it only took me an hour. I am not sure if this will work if you have not already rooted your phone but it should (since this is the major step in rooting). I believe i deleted my CWM file (accidentally) when i was trying to clear space for my recovery with ROM Manager. Be sure to download the Samsung drivers if you had not already done so during the rooting process.
Hope this helps.

Gives me same error message
But after that it boots into recovery.
Should I proceed installing custom rom or is there anything else to be taken care of

Thanks!
Thank you very much,you save me a lot of trouble.

hey_joe said:
Which custom recovery did you flashed Twrp or Cwm?
Sent from my SM-N900W8 using xda app-developers ap
Click to expand...
Click to collapse
hey joe im getting the same problem but im using the note 3 SM-N900W8 and I flash the CWM straight from the app and not using odin. My phone is already rooted using towelroot

billygun118 said:
hey joe im getting the same problem but im using the note 3 SM-N900W8 and I flash the CWM straight from the app and not using odin. My phone is already rooted using towelroot
Click to expand...
Click to collapse
Which android os do you have on your phone and which cwm version did you flashed?

hey_joe said:
Which android os do you have on your phone and which cwm version did you flashed?
Click to expand...
Click to collapse
im using version 4.4.2 jellybean. The rom manager is v5. 5.3.7/ current recovery 6.0.4.6

billygun118 said:
im using version 4.4.2 jellybean. The rom manager is v5. 5.3.7/ current recovery 6.0.4.6
Click to expand...
Click to collapse
Based on my experience, using rom manager to flash recovery always results in a problem. I suggest you use odin to flash this in download mode.
Btw, 4.4.2 is Kitkat

hey_joe said:
Based on my experience, using rom manager to flash recovery always results in a problem. I suggest you use odin to flash this in download mode.
Btw, 4.4.2 is Kitkat
Click to expand...
Click to collapse
should I root my phone first using cf-root. Then flash the cwm recovery. What happens if I get stuck in a bootloop after flashing the recovery

billygun118 said:
should I root my phone first using cf-root. Then flash the cwm recovery. What happens if I get stuck in a bootloop after flashing the recovery
Click to expand...
Click to collapse
The way I did this is, first install the cwm recovery then flash cf-root after. You can always use odin to flash back the original firmware.

hey_joe said:
The way I did this is, first install the cwm recovery then flash cf-root after. You can always use odin to flash back the original firmware.
Click to expand...
Click to collapse
so there is nothing else I have to do before flashing the recovery?
what boxes should be checkmarked in odin

billygun118 said:
so there is nothing else I have to do before flashing the recovery?
what boxes should be checkmarked in odin
Click to expand...
Click to collapse
Just make sure reactivation lock is off.
When you first start odin, F.Reset Time and Auto Reboot are ticked off so let them be and make sure only those are checked and nothing else.
You probably know this but just to make sure, load the recovery on the AP slot before hitting start.

Rogers I337M S4 won't boot after ODIN flashing

My girlfriend has been having S4 issues in the past such as random restarts and application issues probably related to a ROM issue. Her phone IS rooted. While I was at work, she went to my floormate for advice and he, who also has an I337M S4, suggested she reflash a ROM. Things went well according to him (i.e. no ODIN issues) and I trust him since he has been messing with these things for a while; however, now her phone will not boot past the Samsung logo. It won't reliably go past the simple "Samsung Galaxy S4" white-and-black splash screen and when it does it fails to progress to actually being on. I CAN reliably get the phone into download mode and CAN flash ROMs using ODIN; however, I have no idea how to fix this issue. :/ I have access to any necessary S4 files (such as the PIT file) from my floormate.
Since I can't get anything more useful than download mode, here's the information from that:
Product: SGH-I337M
Binary: Samsung Official
Status: Custom
Knox Lock: 0x0
Knox Warranty Void: 0x1
USB-Config-LSD: 0x30
Write Protection: Enable
MMC Burst Mode: Enable
I apologise if any of that isn't quite right as she has a crack in the top left of her phone that makes it very hard to read.
Thanks in advance,
Jacob

wethestill said:
My girlfriend has been having S4 issues in the past such as random restarts and application issues probably related to a ROM issue. Her phone IS rooted. While I was at work, she went to my floormate for advice and he, who also has an I337M S4, suggested she reflash a ROM. Things went well according to him (i.e. no ODIN issues) and I trust him since he has been messing with these things for a while; however, now her phone will not boot past the Samsung logo. It won't reliably go past the simple "Samsung Galaxy S4" white-and-black splash screen and when it does it fails to progress to actually being on. I CAN reliably get the phone into download mode and CAN flash ROMs using ODIN; however, I have no idea how to fix this issue. :/ I have access to any necessary S4 files (such as the PIT file) from my floormate.
Since I can't get anything more useful than download mode, here's the information from that:
Product: SGH-I337M
Binary: Samsung Official
Status: Custom
Knox Lock: 0x0
Knox Warranty Void: 0x1
USB-Config-LSD: 0x30
Write Protection: Enable
MMC Burst Mode: Enable
I apologise if any of that isn't quite right as she has a crack in the top left of her phone that makes it very hard to read.
Thanks in advance,
Jacob
Click to expand...
Click to collapse
Just boot into recovery and do a factory reset
Sent from my SAMSUNG-SGH-I727

jd1639 said:
Just boot into recovery and do a factory reset
Sent from my SAMSUNG-SGH-I727
Click to expand...
Click to collapse
I can't reliably get into recovery; however, I have done a factory reset on one of the times I was able to do so. This didn't fix the issue.

wethestill said:
I can't reliably get into recovery; however, I have done a factory reset on one of the times I was able to do so. This didn't fix the issue.
Click to expand...
Click to collapse
Custom roms are typically flashed through a custom recovery.. trwp, cwm, phils..... stock roms are flashed through odin.... 2 ways you can go here... flash custom recovery ( tripping knox btw) or download a stock rom from sam mobile.... making sure you get the right one of course.... and flash it through odin... sounds like currently you have a bad flash.......

Gage_Hero said:
Custom roms are typically flashed through a custom recovery.. trwp, cwm, phils..... stock roms are flashed through odin.... 2 ways you can go here... flash custom recovery ( tripping knox btw) or download a stock rom from sam mobile.... making sure you get the right one of course.... and flash it through odin... sounds like currently you have a bad flash.......
Click to expand...
Click to collapse
Sorry, I should have specified. What "Passed" on Odin is a stock ROM or at least it should be. I'm just trying to get the phone to a bootable state and am unconcerned with the end resulting ROM. Do you have a link to a recommended ROM that won't take an entire day to download?

wethestill said:
Sorry, I should have specified. What "Passed" on Odin is a stock ROM or at least it should be. I'm just trying to get the phone to a bootable state and am unconcerned with the end resulting ROM. Do you have a link to a recommended ROM that won't take an entire day to download?
Click to expand...
Click to collapse
If your coming from 4.3 there are a number of good roms... unfortunately they are all around 1.2 to 1.4 GB so if you have a slow connection it will take a while... I run Danvh's 4.4 http://forum.xda-developers.com/showthread.php?t=2537495 , there is also this one that people seem to like but I haven't tried it.... http://forum.xda-developers.com/showthread.php?t=2375180 you will need a custom recovery.... both of these suggest twrp.... I flashed with 2.6... 2.7 is out now and I don't know how it reacts but you will need a custom revovery to flash the zip file....

I guess the issue is you have to restore to stock via odin but you don't know what version bootloader you have? Guess you'll have to use samsung tool which will probably install knox?
Can you install custom recovery via odin?

Try with the new 4.4 files
sent from my mobile device

Knox is already tripped. I'd go into recovery, do a factory restore again and then plug it into the computer and do a restore with Kies.
Sent from my SGH-I337M using Tapatalk

Custom Recovery not possible - new protection from Samsung?

Hi!
I have tried to install a custom recovery image on different ways on my new Galaxy S5 (SM-G900F, Andoird 5.0, G900FXXU1BOD3, DBT) for root, de-bloat, etc with no success. Is there some new protection from Samsung to avoid the use of a custom recovery image?
I have tried the following procedures:
1.
-data/factory reset, wipe cache
-flash different custom recoveries with odin openrecovery-twrp-2.8.5.0-gt-klte.tar / philz_touch_6.26.2-klte.tar.md5 / twrp-2.8.6.0-klte.tar (no auto reboot in odin)
-remove battery after flash
-boot into recovery
Result:
Screen shows: RECOVERY BOOTING...., Set Warranty Bit: recovery -> then comes a black screen (also after 15 minutes), no reaction on pushing keys, custom recovery mode is not working
2.
-data/factory reset, wipe cache
-flash Android 4 stock rom DBT-G900FXXU1ANE2 (for towelroot)
Result:
Screen keeps black all the time, buttons and phone are working
So, I switched back to Android 5 in blind flight
3.
-data/factory reset, wipe cache
-flash Android 4 stock rom DBT-G900FXXU1ANG2
-flash Kernel KERNEL_G900FXXU1ANE2.tar.md5 (for towelroot)
Result:
Phone is not booting
So, I switched back to Android 5
What did I miss (no problems with galaxy S1-S4)? Is there some new protection from Samsung to avoid custom recoveries?

All you have to do is ensure no F-Time reset is ticked, and force the phone into recovery mode. That drove me crazy in my G900F, cause I were accustomed to my S2 and S3. LOL
Enviado desde mi SM-G900F mediante Tapatalk

worf_1977 said:
All you have to do is ensure no F-Time reset is ticked, and force the phone into recovery mode. That drove me crazy in my G900F, cause I were accustomed to my S2 and S3. LOL
Click to expand...
Click to collapse
Thank you for your hint. I have always checked the odin option "F. Reset Time". But the custom recovery is not working (black screen after forcing recovery, removing batterie/long power button holding is necessary to use the phone again). If I am the only one who has this problem, maybe the device has a hardware failure?
The stock recovery always works fine.

b8213 said:
Thank you for your hint. I have always checked the odin option "F. Reset Time". But the custom recovery is not working (black screen after forcing recovery, removing batterie/long power button holding is necessary to use the phone again). If I am the only one who has this problem, maybe the device has a hardware failure?
The stock recovery always works fine.
Click to expand...
Click to collapse
Maybe you're flashing incorrect recovery image?

If rooted, use this to install TWRP (Install Busybox first)
https://play.google.com/store/apps/details?id=com.jmz.soft.twrpmanager&hl=en_GB

Keeping an eye on this thread to see where it goes, as I have heard *rumours* of 'beefed up' security on Samsung's LP firmwares......
Sent from my rooted, debloated stocKK kn0x0 SM-G900F

TheATHEiST said:
Maybe you're flashing incorrect recovery image?
Click to expand...
Click to collapse
I have used the following sources:
openrecovery-twrp-2.8.5.0-gt-klte.tar: techerrata.com/browse/twrp2/klte
philz_touch_6.26.2-klte.tar.md5: downloadandroidrom.com/file/GalaxyS5/CWM/Qualcomm/philz_touch_6.26.2-klte.tar.md5
twrp-2.8.6.0-klte.tar: dl.twrp.me/klte/
I assume that at least one of the sources should be correct. But no one is working.

*Detection* said:
If rooted, use this to install TWRP (Install Busybox first)
Click to expand...
Click to collapse
Good idea, but how to root, if there seems to be no way to...
towelroot:
Android 4, G900FXXU1ANE2, stock image is not running
Android 4, G900FXXU1ANG2, device is not supported in towelroot
Android 5, G900FXXU1BOD3, device is not supported in towelroot
chainfire via custom recovery:
not possible, force recovery lead to black screen
Is there another way to root one of the stock images Android 4 G900FXXU1ANG2 or Android 5 G900FXXU1BOD3?

b8213 said:
Good idea, but how to root, if there seems to be no way to...
towelroot:
Android 4, G900FXXU1ANE2, stock image is not running
Android 4, G900FXXU1ANG2, device is not supported in towelroot
Android 5, G900FXXU1BOD3, device is not supported in towelroot
chainfire via custom recovery:
not possible, force recovery lead to black screen
Is there another way to root one of the stock images Android 4 G900FXXU1ANG2 or Android 5 G900FXXU1BOD3?
Click to expand...
Click to collapse
CF Auto Root & ODIN

You're not alone! Im trying to root/flash custom recovery on my S5 (also G900FXXU1BOD3) since Friday, same approach as you. Tried everything I could find, nothing works.
Keeping an eye on this thread.

*Detection* said:
CF Auto Root & ODIN
Click to expand...
Click to collapse
Thanks.
I have also tried this: flashing of chainfires auto root via odin, then straight ahaed to recovery mode -> black screen (no execution of chainfires script, device is not rooted)

Running ODIN as Admin?
Got phone in Download Mode?
Samsung Drivers installed?
Using a native PC?

*Detection* said:
Running ODIN as Admin?
Click to expand...
Click to collapse
Yes, have tried Odin 3.07 and 3.10.6 run as administrator
*Detection* said:
Got phone in Download Mode?
Click to expand...
Click to collapse
yes, download mode is always possible
*Detection* said:
Samsung Drivers installed?
Click to expand...
Click to collapse
yes, the last one v. 1.5.51.0
*Detection* said:
Using a native PC?
Click to expand...
Click to collapse
yes, its a notebook with native win 7 SP1 64 bit (no vm)

Do you have another machine you can try flashing it from?
Different USB cable?

*Detection* said:
Do you have another machine you can try flashing it from?
Click to expand...
Click to collapse
I have already tried adb sideload from an ubuntu pc - same result (black screen). At the moment, I have no other Windows machine to try flashing from.
*Detection* said:
Different USB cable?
Click to expand...
Click to collapse
Yes, I have tried the original white one and an old black one - same result (black screen)
Flashing the stock rom from Android 4.4 ANG2 <-> Android 5 BOD1 via odin works fine. Also flashing only stock recovery.img (via odin, packed as tar) works fine. Before I am going to try to flash a custom recovery, I made sure that stock recovery is flashed an working.

I'm just leaving this here in case someone solves it. Running G900FXXU1BOD3 and need root.

Try to flash back to ANG(X), boot, then flash ANE2 kernel and use toweloroot. And ignore the FC's you should be getting, and reflash ANG2 kernel.
That should do it. If not, well, I'm in the dark (you can't use Samsung's service claiming that you are not able to root the phone LOL)
Enviado desde mi SM-G900F mediante Tapatalk

Bought a Galaxy S5 yesterday and tried to flash from 5.0 to 4.4.2. It´s Mission Impossible.
When i flash anything older than ANG2 the phone boots but Display stays completly black.
tried to flash from G900FXXU1BOD3 to G900FXXU1ANE2 -----> Black Display
tried to flash from G900FXXU1BOD3 to G900FXXU1ANG2 -----> works, but towelroot does not support G900FXXU1ANG2
tried to flash from G900FXXU1BOD3 to G900FXXU1ANG2 and flash the G900FXXU1ANE2 Kernel -----> Black Display

This ties in with what I've heard rumours of......that something in a 5.0 firmware is not erased/overwritten during a rollback to 4.4 and causes 'problems'......
I wonder if flashing a pit would sort it out? If I understand how a pit file works, I *think* it formats the partitions and re writes them......that being the case, it should erase every trace of any pre existing OS allowing you to flash onto a completely blank device......somebody please CMIIW......
Sent from my rooted, debloated stocKK kn0x0 SM-G900F

Yep, that's my understanding of PIT files too
But I have flashed back from the latest LP to KK without any problems
And CF Auto Root still works like it did with any firmwares
If Samsung had changed something, everyone would be having the same problems surely

bricked s5 g901f "could not do normal boot"

hello everyone, after rooting and flashing lots of phones, i have probably managed to brick one
since i am using linux, i tried heimdall wich detected but couldnt flash , not even read pit
i tried to root it, with kingroot, failed
then i tried kingoroot desktop app, it seemed to work then after flashing philzcwm using rashr, it went into download mode
at some time i may have flashed a recovery img onto BL, wich i NOW know is the bootloader
i knew that i shouldnt mess with the bootloader, but didnt think BL was bootloader
now using odin 3.10.6 in win xp it doesent seem to do nothing
it automatically goes into download mode with first line saying
"could not do normal boot"
i am now downloading an original firmware 4.4.6 from sam mobile
can anyone help me or is it bricked?

Lost count of how many things you did wrong there
Get a Native Windows 7+ PC running, boot the phone into download mode, flash stock ROM with ODIN 3.10.7
If it fixes it - spend a long time reading threads here on XDA before trying anything else

i dont think i flashed the bootloader, i remembered, odin was crashing before i ever hit start cause i was selecting the md5 and it didnt have the tar
now after flashing twrp 2.8 it boots fine, but if i try to boot in recovery, it goes to download mode "cant do normal boot"
flashed cf autoroot it also goes to download mode
i remember on galaxy s3 if you didnt restart straight to recovery just after flashing it would overwrite with stock recovery
but now if i try to restart to recovery after flashing it doesent do anything, i have to unplug it and take out the battery
edit
if i press vol[-] home power it goes to normal download mode
if i press vol[+] home power it supposed to go to recovery but goes to download mode with "could not do normal boot" message
if i press power alone it boots normally
in download mode it says
product name: sm-g901f
current binary:custom
system status:custom
reactivation lock: off
knox warranty void 0x1(4)
qualcomm secureboot: enable (csb)
RP SWREV: S1 T1 R1 A1 P1
secure download : enable
UDC start
i dont mind learning but android is pretty ugly with all the lack of documentation and standards
i learned a lot of stuff reading this forum, and will always respect people who know more than me
i just dont understand what the hell just happened, didnt encountered this before

Yea.. So follow my instructions

i am following your instructions precisely , will spend the day installing crap win7 wich i am running away from, to use with 3.10.7
in the meantime can you explain to me what happened?
i read somewhere something about odin bad usb on xp, would that pe hardware, driver, odin or usb protocol error

fixed, was flashing klte recovery, damn dozen versions of every phone
only clean rom i found was cm12 and dokdo7, both 5.1 based
waiting for network unlock, and case and im good to go
would have loved more after-market roms omni,aokp,pac, maybe 4.4
5.1 has the crap pie (position independent executable) so i cant play with perl 5.20, im stuck with 5.7
if anyone knows where to find more clean roms for g901f / kccat6xx i would be greatful
a more recent version of perl to work on 5.1 would also be nice

did you ever get this fixed?
having the same trouble with my Note4...just happened out of nowhere.

broad_st_bully said:
did you ever get this fixed?
having the same trouble with my Note4...just happened out of nowhere.
Click to expand...
Click to collapse
His last post says he fixed it...

*Detection* said:
His last post says he fixed it...
Click to expand...
Click to collapse
this phone is making me think I'm crazy...after pure hell all day yesterday and last night I wake up (after accepting the fact the phone was R.I.P.) and it turns right on and lets me set up after a factory reset.
This happened yesterday too though so I'm not gonna get all happy yet...

broad_st_bully said:
this phone is making me think I'm crazy...after pure hell all day yesterday and last night I wake up (after accepting the fact the phone was R.I.P.) and it turns right on and lets me set up after a factory reset.
This happened yesterday too though so I'm not gonna get all happy yet...
Click to expand...
Click to collapse
S5 or NOTE 4?

Could not do normal boot odin mode
I just rooted my phone so i can install a rom on my sm-n900s but i didnt realise that it was for an sm-n900.I flashed it on my phone with flashify and now all i can do is go to my custom recovery TWRP to wipe everything but still to no avail.I really do not know what to do.PLS HELP :crying::crying::crying::crying::crying:

zpimp said:
fixed, was flashing klte recovery, damn dozen versions of every phone
only clean rom i found was cm12 and dokdo7, both 5.1 based
waiting for network unlock, and case and im good to go
would have loved more after-market roms omni,aokp,pac, maybe 4.4
5.1 has the crap pie (position independent executable) so i cant play with perl 5.20, im stuck with 5.7
if anyone knows where to find more clean roms for g901f / kccat6xx i would be greatful
a more recent version of perl to work on 5.1 would also be nice
Click to expand...
Click to collapse
How did you fix it ??? if i flash a custom rom i get the same issue and my device is the same as yours. I flashed back stock rom, samsungs own recovery works well but as soon as i flash a custom recovery (twrp-3.0.0-0-klte-klte.img.tar or philz_touch_6.57.8-klte.tar.md5) i get your issue. How can i fix this and install a custom recovery ? When i install CF-Auto-Root-kccat6-kccat6xx-smg901f.tar.md5 the recovery is back but even when i flash within the os (terminal) the recovery is broken "again"
FIXED!!!! Installed CWM-based Recovery v6.0.5.1

MichelN said:
How did you fix it ??? if i flash a custom rom i get the same issue and my device is the same as yours. I flashed back stock rom, samsungs own recovery works well but as soon as i flash a custom recovery (twrp-3.0.0-0-klte-klte.img.tar or philz_touch_6.57.8-klte.tar.md5) i get your issue. How can i fix this and install a custom recovery ? When i install CF-Auto-Root-kccat6-kccat6xx-smg901f.tar.md5 the recovery is back but even when i flash within the os (terminal) the recovery is broken "again"
FIXED!!!! Installed CWM-based Recovery v6.0.5.1
Click to expand...
Click to collapse
Download stock rom and flash by odin.They are plenty of websites online.Just search for ur phone model followed by stock rom and u will find the exact rom for u to download and flash via odin.

The problem was the recovery, same as the user on page 1. See my last notes in prev. post