[Q] Need help installing Custom ROM on SPH-L720 MK2 Baseband - Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot

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

Related

[Q] S4 Bell 1337m wont boot after flash.

Hello all, so i've run into a little problem and after a few hours i cant figure out what i did wrong so i reach out for help
i rooted my device successfully with odin and instlal CWM.
booted into recover, wiped data/cache/system/data as the walk through told me
then install a cx rom from here
http://forum.xda-developers.com/show....php?t=2391142
now when i turn my device on it gose stright into downloading mode with "could not do normal boot" in the top right
can any1 tell me waht i did wrong or missed?
oh i can sitll get into recovery
thanks in advanced
BurnAll said:
Hello all, so i've run into a little problem and after a few hours i cant figure out what i did wrong so i reach out for help
i rooted my device successfully with odin and instlal CWM.
booted into recover, wiped data/cache/system/data as the walk through told me
then install a cx rom from here
http://forum.xda-developers.com/show....php?t=2391142
now when i turn my device on it gose stright into downloading mode with "could not do normal boot" in the top right
can any1 tell me waht i did wrong or missed?
oh i can sitll get into recovery
thanks in advanced
Click to expand...
Click to collapse
Did you check the MD5 before flashing? Are you absolutely sure the ROM your flashing is compatible with your device? Were you on the latest MF3 firmware before you started flashing?
agent929 said:
Did you check the MD5 before flashing? Are you absolutely sure the ROM your flashing is compatible with your device? Were you on the latest MF3 firmware before you started flashing?
Click to expand...
Click to collapse
no i did not check the firmware. i missed that very first line.. sigh, but i got my phone when s4's 1st came out dose that help?
and thats another thing thats confusing me, what rom/kernals are compatiable with this phone i've read a bunch of forums but alot of them appear to leave a list out of it.
the one i'm trying to do has my device listed
http://forum.xda-developers.com/showthread.php?t=2391142
BurnAll said:
no i did not check the firmware. i missed that very first line.. sigh, but i got my phone when s4's 1st came out dose that help?
and thats another thing thats confusing me, what rom/kernals are compatiable with this phone i've read a bunch of forums but alot of them appear to leave a list out of it.
the one i'm trying to do has my device listed
http://forum.xda-developers.com/showthread.php?t=2391142
Click to expand...
Click to collapse
heck at this point i'd be happy just to get it back to normal as its late and i need to sleep and work tomorrow
BurnAll said:
no i did not check the firmware. i missed that very first line.. sigh, but i got my phone when s4's 1st came out dose that help?
and thats another thing thats confusing me, what rom/kernals are compatiable with this phone i've read a bunch of forums but alot of them appear to leave a list out of it.
the one i'm trying to do has my device listed
http://forum.xda-developers.com/showthread.php?t=2391142
Click to expand...
Click to collapse
Anything that says i337 will work on your phone, given that the developer has it bug free (the US ATT Samsung Galaxy S4)
agent929 said:
Anything that says i337 will work on your phone, given that the developer has it bug free (the US ATT Samsung Galaxy S4)
Click to expand...
Click to collapse
okay so this should work i also put on kernal
http://forum.xda-developers.com/show...php?p=41675354
4.2.2 TW version.
but still saying could no do normal boot, while on downloading screen
BurnAll said:
okay so this should work i also put on kernal
http://forum.xda-developers.com/show...php?p=41675354
4.2.2 TW version.
but still saying could no do normal boot, while on downloading screen
Click to expand...
Click to collapse
It says page not found...get the dots out of your link
Did you use your carriers Kernel?
Hey I just noticed that your subject for this post says i337m. Can you confirm if you have a i337 or an i337m please? Thank you.
agent929 said:
Hey I just noticed that your subject for this post says i337m. Can you confirm if you have a i337 or an i337m please? Thank you.
Click to expand...
Click to collapse
i have the m
BurnAll said:
i have the m
Click to expand...
Click to collapse
it appears you have flashed an ATT rom for the i337 and not a Rom for the i337m -- you now have several options to restore your phone
1. flash the Loki'd fix to allow the kernel and rom you flashed to boot your phone or
2. flash a cutom kernel that does work with your phone such a Ktoonz kernel (read the install instructions, for your i337m you need the TMO version of his kernel) or
3 download the stock firmware package for your phone, I'd recommend MG1 either from a link on xda or from samMobile or Samsung updates and install using Odin -- this will completely reset you phone and then you can worry about root and custom recovery after
If you do decide to install fresh factory stock MG1 I can recommend using CF-root to root the i337m and then installing Philz Recovery rather than regular CWM as it installs more easily and plays nicer on the i337m in my experience.
Remember each phone is different but do not attempt to install ATT designed roms on your i337m unless you have the loki patch also on your SD card ready to flash also.
There are many great roms available that do fir the i337m and are specifically set up for our phone.
But first, let's get you out of the download loop. EIther of the 3 options above will do. Personally, I would recommend the Odin install of the stock MG1 firmware and start over with a factory reset and a clean phone.
agent929 said:
It says page not found...get the dots out of your link
Click to expand...
Click to collapse
sorry here it is.
another fella on bell said this one worked for him
http://forum.xda-developers.com/showthread.php?p=41675354
lgsshedden said:
it appears you have flashed an ATT rom for the i337 and not a Rom for the i337m -- you now have several options to restore your phone
1. flash the Loki'd fix to allow the kernel and rom you flashed to boot your phone or
2. flash a cutom kernel that does work with your phone such a Ktoonz kernel (read the install instructions, for your i337m you need the TMO version of his kernel) or
3 download the stock firmware package for your phone, I'd recommend MG1 either from a link on xda or from samMobile or Samsung updates and install using Odin -- this will completely reset you phone and then you can worry about root and custom recovery after
If you do decide to install fresh factory stock MG1 I can recommend using CF-root to root the i337m and then installing Philz Recovery rather than regular CWM as it installs more easily and plays nicer on the i337m in my experience.
Remember each phone is different but do not attempt to install ATT designed roms on your i337m unless you have the loki patch also on your SD card ready to flash also.
There are many great roms available that do fir the i337m and are specifically set up for our phone.
But first, let's get you out of the download loop. EIther of the 3 options above will do. Personally, I would recommend the Odin install of the stock MG1 firmware and start over with a factory reset and a clean phone.
Click to expand...
Click to collapse
okay thanks i'll try to restore it using odin with the MG1 and then give the philz a shot. i'll update u once i've done so.
CF root:
http://forum.xda-developers.com/showthread.php?t=2293800
Philz recovery
http://forum.xda-developers.com/showthread.php?t=2201860
Goldeneye Rom:
http://forum.xda-developers.com/showthread.php?t=2313469
stock rooted MG1 rom
http://forum.xda-developers.com/showthread.php?t=2375180
stock firmware download links:
http://forum.xda-developers.com/showthread.php?t=2269304
lgsshedden said:
CF root:
http://forum.xda-developers.com/showthread.php?t=2293800
Philz recovery
http://forum.xda-developers.com/showthread.php?t=2201860
Goldeneye Rom:
http://forum.xda-developers.com/showthread.php?t=2313469
stock rooted MG1 rom
http://forum.xda-developers.com/showthread.php?t=2375180
stock firmware download links:
http://forum.xda-developers.com/showthread.php?t=2269304
Click to expand...
Click to collapse
okay got it back to stock, now quick question for the philz do i flash the .tar with odin? or do something else with the .zip?
Its not the ROM that's incomparable its the kernal your using. Find one for a i337m then flash it immediately after you flash your ROM and see if it works.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
---------- Post added at 09:58 PM ---------- Previous post was at 09:58 PM ----------
Zip gets flashed in your recovery.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
agent929 said:
Its not the ROM that's incomparable its the kernal your using. Find one for a i337m then flash it immediately after you flash your ROM and see if it works.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
---------- Post added at 09:58 PM ---------- Previous post was at 09:58 PM ----------
Zip gets flashed in your recovery.
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Click to expand...
Click to collapse
so just to go over the steps to make sure i dont mess this up,
so i flashed to the origonal versoin with odin
that worked
then i rooted it using CF root
now i got 2 files from philz and i'm not 100% sure what to do with them, i got a .tar what i assume i flash with odin and a .zip i'm not to sure what i do with they are both named philz_touch_5.15.0-jfltecan.tar.md5 and philz_touch_5.15.0-jfltecri.zip
then once i get into recovery i know how to flash roms, its just this whole kernal thing thats got me confused.
BurnAll said:
so just to go over the steps to make sure i dont mess this up,
so i flashed to the origonal versoin with odin
that worked
then i rooted it using CF root
now i got 2 files from philz and i'm not 100% sure what to do with them, i got a .tar what i assume i flash with odin and a .zip i'm not to sure what i do with they are both named philz_touch_5.15.0-jfltecan.tar.md5 and philz_touch_5.15.0-jfltecri.zip
then once i get into recovery i know how to flash roms, its just this whole kernal thing thats got me confused.
Click to expand...
Click to collapse
how the heck do i install this philz i boot into recovery and install the zip but i get like 4 red errors when i do it and i still dont have philz
BurnAll said:
how the heck do i install this philz i boot into recovery and install the zip but i get like 4 red errors when i do it and i still dont have philz
Click to expand...
Click to collapse
READ THIS FIRST:
MAKE SURE YOU DO NOT HAVE THE MF3 FIRMWARE ON YOUR S4. THAT IS THE MOST IMPORTANT THING TO DO RIGHT NOW. IF YOU DO, DO NOT ATTEMPT TO INSTALL A CUSTOM RECOVERY.
You don't have a custom recovery already that's why. Did casual not install TWRP for you? If not try installing Goo Manager from the app market and try installing TWRP that way. MAKE SURE THAT WHEN YOU INSTALL IT, IT SAYS YOUR MODEL NUMBER EXACTLY! I CAN NOT STRESS THIS ENOUGH! When you have TWRP installed, then flash philz with TWRP and you'll have that custom recovery instead.
BurnAll said:
how the heck do i install this philz i boot into recovery and install the zip but i get like 4 red errors when i do it and i still dont have philz
Click to expand...
Click to collapse
do not use the zip you quoted it is not for your phone
use odin flash the tar philz_touch_5.15.0-jfltecan.tar.md5
now you have stock updated MG1 firmware with the latest baseband
root by CF root
Philz Recovery
Now follow the next steps:
1. set up your google account play store etc.
2.next, go into the recovery and do a full nandroid backup -- this gives you a stable base you can restore when needed
3. go flash a custom rom, I highly recommend the latest version of Goldeneye -- updated, well maintained, great developer, clear install instructions
4. try itt then again, use recovery to make a 2nd nandroid, this one of your custom rom install -- try different kernels, every phone is different and someone's favorite kernel just may not like your phone -- doesn't make it a bad kernel just makes it the wrong one for your phone, flash a different one
5. theme if you want -- this is where your recoveries become important as themes are notorious for not always sitting well and all is ok if you have a backup you can return to
6. NEVER flash a baseband from another variant -- stick with your MG1 from your carrier until your carrier updates stock firmware

[RESOLVED]Recovery help

RESOLVED:
- Flashed a stock firmwire image from Sammobile using Odin. (AMDL)
- Did a factory reset in the stock recovery TWICE to get it to finally boot.
- Rooted with motochopper
- Installed TWRP
- Back to Task650.
Okay, so I'm a bit stuck. I was running the newest Task650 rom and KT's 9/17 kernel.
I updated to the 10/20 kernel as soon as it was released and it bugged my phone. Blew up everything, glitched my DPI and colors. It was unusable, however the weirdest part is that my custom recovery was removed so I can't seem to flash the old kernel to get my device back to normal.
I tried using odin but it just keeps failing, so I really am unsure what to do now. If I could get the previous kernel back onto it, it would be fine.
Any help? I can't seem to find a .tar.md5 file for TWRP or clockworkmod to flash a new recovery in Odin. I tried Philz .tar.md5 files but it fails as well.
Click to expand...
Click to collapse
As long as your not MF3
try goo manager for TWRP
or
Try ROM manager just to flash CWM
Note: do not use ROM manager for nothing else if you didn't already know.
Sent from my GT-I9505G using xda premium
jball said:
As long as your not MF3
try goo manager for TWRP
or
Try ROM manager just to flash CWM
Note: do not use ROM manager for nothing else if you didn't already know.
Sent from my GT-I9505G using xda premium
Click to expand...
Click to collapse
I cannot use the Google Playstore.. my entire screen is over scaled and impossible to navigate.
So no use of DPI settings.can you use ADB or terminal emulator
Sent from my SAMSUNG-SGH-I337 using xda premium
when you say you tried odin, are you saying you tried flashing the stock rom (MDL), tried flashing a custom recovery tar, or both? what error is it giving?
unfortunately i think kt accidentally uploaded a 4.2.2 kernel and thats what you downloaded. check out his thread and see what anyone else in your situation may have done already to remedy this. good luck
Can you reroot by flashing an autorooter through download mode? Doing so might enable you to flash kernels again.
Is factory reset an option?
xBeerdroiDx said:
when you say you tried odin, are you saying you tried flashing the stock rom (MDL), tried flashing a custom recovery tar, or both? what error is it giving?
unfortunately i think kt accidentally uploaded a 4.2.2 kernel and thats what you downloaded. check out his thread and see what anyone else in your situation may have done already to remedy this. good luck
Click to expand...
Click to collapse
I managed to get the latest stock firmwire (AMDL 4.2.2) off of Sammobile. I did successfully flash the stock .tar.md5 image through Odin, using the PDA slot. Phone seemed to restart and boot right up, but now gets stuck at the AT&T logo. It makes the boot sound and than BAM; frozen.
Now I am truly stuck. Seems flashing the stock image didn't work.. unless I did it wrong through Odin but I doubt it. These are the steps I took,
- Start Odin
- Connect phone in downloaded mode
- Click PDA (select the I337UCUAMDL_I337ATTAMDL_ATT.tar.md5 file)
- Wait for it to confirm the firm, than hit start.
- After waiting about 5 minutes it's successful.
Am I doing ANYTHING wrong?
Te3k said:
Can you reroot by flashing an autorooter through download mode? Doing so might enable you to flash kernels again.
Is factory reset an option?
Click to expand...
Click to collapse
Do a factory reset in the stock recovery after you flash with Odin. It'll get you past the boot loop.
jd1639 said:
Do a factory reset in the stock recovery after you flash with Odin. It'll get you past the boot loop.
Click to expand...
Click to collapse
Did a Factory reset in the stock recovery, wiped all data etc. Still gets stuck at the AT&T logo.
EDIT: Did it twice and it worked!
Br4nd3n said:
Did a Factory reset in the stock recovery, wiped all data etc. Still gets stuck at the AT&T logo.
EDIT: Did it twice and it worked!
Click to expand...
Click to collapse
How long have you given the boot? The first boot can take a long time. 5 minutes or more isn't unheard of.
jd1639 said:
How long have you given the boot? The first boot can take a long time. 5 minutes or more isn't unheard of.
Click to expand...
Click to collapse
Gave it about 2 hours the first time.. knew it was stuck. However I did the factory reset twice in a row, and it finally booted. Just did a quick root through Motochopper, installed TWRP and now I'm back and running on Task650 :good:
Good deal
Sent from my GT-I9505 using xda premium
Br4nd3n said:
Gave it about 2 hours the first time.. knew it was stuck. However I did the factory reset twice in a row, and it finally booted. Just did a quick root through Motochopper, installed TWRP and now I'm back and running on Task650 :good:
Click to expand...
Click to collapse
:good:

Philz Touch problem! Please help!

I updated my GS4 to rooted (without knox) 4.3 and now i want to flash Sacs Custom rom but i can't i've tried every recovery I could find none work for me even Philz, everyone is saying use that one and I did but when I flash it through odin nothing happens when I try to boot it to recovery the phone simply skips through and reboots( yes it does try to get into recover, the blue text) but if i keep trying it, it'll boot to stock recovery after 2-3 tries (assuming that's a fail safe?) I don't know what i'm doing wrong can anyone help?
Yes i have the drivers (Odin can do anything but get a recovery to stick)
bounddyy said:
I updated my GS4 to rooted (without knox) 4.3 and now i want to flash Sacs Custom rom but i can't i've tried every recovery I could find none work for me even Philz, everyone is saying use that one and I did but when I flash it through odin nothing happens when I try to boot it to recovery the phone simply skips through and reboots( yes it does try to get into recover, the blue text) but if i keep trying it, it'll boot to stock recovery after 2-3 tries (assuming that's a fail safe?) I don't know what i'm doing wrong can anyone help?
Yes i have the drivers (Odin can do anything but get a recovery to stick)
Click to expand...
Click to collapse
Run Odin 'as administrator' and make sure you're flashing the right .tar - philz_touch_5.18.2-jfltespr.tar.md5
leaderbuilder said:
Run Odin 'as administrator' and make sure you're flashing the right .tar - philz_touch_5.18.2-jfltespr.tar.md5
Click to expand...
Click to collapse
Yes i did those and is it possible to downgrade to mf9 and directly flash sacs custom v4 4.3?
bounddyy said:
Yes i did those and is it possible to downgrade to mf9 and directly flash sacs custom v4 4.3?
Click to expand...
Click to collapse
If you can get into recovery now (philz). You can certainly flash Sac's 4.3. If you want the mf9 modem that is in the dev section too. Check out Unknownforce's post
But I suspect you've taken the mja "firmware" and tripped that Knox counter, and if that's the case I dint believe you can Odin back to mf9.
Sent from my SPH-L720 using XDA Premium 4 mobile app
Well my rom was pre rooted and wasn't supposed to have Knox I'll try it and see but is it okay to flash to 4.3 v4 from mf9?
Sent from my SPH-L720 using xda app-developers app
bounddyy said:
Well my rom was pre rooted and wasn't supposed to have Knox I'll try it and see but is it okay to flash to 4.3 v4 from mf9?
Sent from my SPH-L720 using xda app-developers app
Click to expand...
Click to collapse
well that didn't workout so i figured out that i shouldnt let my phone reboot after flashing Philz recovery and instead directly force into recovery and it worked but now i need to just flash it thourgh there lol

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.

[Q] boot failure, logo stuck.

Hey guys, i will go direct into topic
i have note 2 n7100
1- i made a factory reset from settings menu on phone then the mobile didn't load again (stuck into logo)
2- tried all recovery ROM with all methods and no luck.
3- Downloaded and installed official ROM from SAMMOBILE and the mobile loaded and worked.
4- Installed a custom ROM.
5- Made a wipe to go back for the official ROM again and starting from here everything went bad..
my mobile didn't accept any ROMS, recovery or anything.
just rebooted and stuck on Samsung logo
i tried many things for 3 days but no luck.
Please HELP.
-----
-----
EDIT:
i know that wiping from recovery mode might solve the problem ,, but i don't have access to recovery mode. i have access to download mode. and sure i tried MANY times to flash recovery roms with ODIN and no luck.
Which rom u r using nd which method ... Cwm 6.04. ???
Sent from my GT-N7100 using Tapatalk
sufiyankatra said:
Which rom u r using nd which method ... Cwm 6.04. ???
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
rom of what ?
CWM is a recovery and i said that all of recovery roms were failed.
probably you have enabled knox, just flash official firmware again
Enviado do meu GT-N7100 através de Tapatalk
monteiro-ribas said:
probably you have enabled knox, just flash official firmware again
Enviado do meu GT-N7100 através de Tapatalk
Click to expand...
Click to collapse
I did, the same one which worked before..
but it turned to the same result.
stuck with Samsung logo
siimoz said:
I did, the same one which worked before..
but it turned to the same result.
stuck with Samsung logo
Click to expand...
Click to collapse
Have you tried booting into recovery and performing a full data wipe from there? Including (internal) SDCard?
EmptyArea said:
Have you tried booting into recovery and performing a full data wipe from there? Including (internal) SDCard?
Click to expand...
Click to collapse
There's no recovery enabled
i tried to flash (philz , twrp2 and cmw 2 ) none of them is booting.
So we know what bootloader you have, what does it say (in the top left) when you're in download mode?
#Also, you should ask for this thread to be moved to Q&A
EmptyArea said:
So we know what bootloader you have, what does it say (in the top left) when you're in download mode?
#Also, you should ask for this thread to be moved to Q&A
Click to expand...
Click to collapse
here it is:
ODIN MODE
Product name: GT-N7100
CUSTOM BINARY DOWNLOAD: YES (12 COUNTS)
CURRENT BINARY: CUSTOM
SYSTEM STATUS: CUSTOM
KNOX WARRANTY VOID: 1
RP SWREV: A2
So you're on a 4.3+ bootloader, I haven't looked into that much - I'm assuming you can downgrade and have a custom recovery, but I'm not sure on the procedure. (Although i imagine Knox Warranty is irreversible - not like that matters because you would simply say: "I've got know idea what that [KNOX] is" and "My phone must have come like that."
It would not be the first time someone has opened a phone to find the software in a peculiar state!)
Either way you should be able to install and 4.3 stock rom and get stock recovery back.
Perhaps it's your odin and OS setup. Try flashing a few different versions of recovery, on different PCs*, with different cables and different versions of odin. If that doesnt work try the same with different stock ROMs. It's what I'd try whilst seeking more expert advice.
*if on Win7 try running odin 'as Windows XP'
Also see here:
http://techbeasts.com/2014/01/17/how-to-deknox-samsung-galaxy-s3-s4-note-2-note-3/
EmptyArea said:
So you're on a 4.3+ bootloader, I haven't looked into that much - I'm assuming you can downgrade and have a custom recovery, but I'm not sure on the procedure. (Although i imagine Knox Warranty is irreversible - not like that matters because you would simply say: "I've got know idea what that [KNOX] is" and "My phone must have come like that."
It would not be the first time someone has opened a phone to find the software in a peculiar state!)
Either way you should be able to install and 4.3 stock rom and get stock recovery back.
Perhaps it's your odin and OS setup. Try flashing a few different versions of recovery, on different PCs*, with different cables and different versions of odin. If that doesnt work try the same with different stock ROMs. It's what I'd try whilst seeking more expert advice.
*if on Win7 try running odin 'as Windows XP'
Also see here:
http://techbeasts.com/2014/01/17/how-to-deknox-samsung-galaxy-s3-s4-note-2-note-3/
Click to expand...
Click to collapse
Thank you for your help, i am downloading a different stock ROM now.
but can you please tell me more about that downgrading thing?
I'm not too sure I'm afraid.
My objective, if I were you, get a custom recovery working and install Wamrick's NC3 - stock kernel will work for you as your bootloader is 4.3 and I don't think you can downgrade that due to Knox.
EmptyArea said:
I'm not too sure I'm afraid.
My objective, if I were you, get a custom recovery working and install Wamrick's NC3 - stock kernel will work for you as your bootloader is 4.3 and I don't think you can downgrade that due to Knox.
Click to expand...
Click to collapse
still.. i don't know how to make the Custom recovery work! as you see in the boot loader i tried to flash 12 times and nothing happened.
And you've tried flashing a full stock 4.3 rom from Sammobile right? Running odin as win XP (if on 7)

Categories

Resources