First of all I just want to say I am very new to the world of rooting and custom roms. I recently got bored of the original layout of my S4 and decided to root my phone and find a custom Rom. I rooted my phone and through Twrp I flashed android Kitkat 4.4.2 from AOKP. It seems that I either messed something up or the particular rom I downloaded doesn't work right. More than likely the first one. It ran okay for a minute or two then it started freezing and rebooting itself. I thought I would just go back to stock and restore from the backup I created but when I tried it said failed. I did some research and found a stock rom through Odin and tried to just revert back that way. That failed too and now my phone is stuck at the Galaxy S4 screen and at the top left it says kernel is not seandroid enforcing. Set warranty bit: kernal.
Any help would be greatly appreciated, I miss my phone! Lol. I apologize if any of my terminology is off also!
Sounds like the odin file you got was 4.2 and I'm guessing you were already stock 4.3. Find a mk2 4.3 Odin file and give that a shot.
Here's a link to a thread where you can get the files I mentioned.
http://forum.xda-developers.com/showthread.php?t=2509605
Sent from my SCH-R970 using Tapatalk
Okay I'll give that a shot. As a side note when I tried to restore my back up TWRP displayed a messaged saying that it appeared that my phone wasn't rooted. Slide to install now. Dunno if that makes a difference or not. I know for sure it was rooted unless the root check I did was wrong.. Lol
I myself use cwm so I'm not that familiar with twrp but I'm pretty sure the link I gave You is for stock unrooted so you'll have to reroot
Sent from my SCH-R970 using Tapatalk
Sacs 4.3 v5 ultra issues
I was running Sac's Custom ROM 4.3 v 4.4 and tried to update to the most recent version 5.5 Ultra. I download the ROM copied to SD Card. Using Philz recovery (devs preference) to wipe cache/davlic/factory reset etc...reboot into recovery...installed ROM. The phone will not get past boot screen. I can't post on the devs page because i am too new to the forum. Can you help me out here?
I plugged to phone into the charger when it was off last night and noticed that at first it had the stock S4 battey life indicator but after a second it changed to the android 4.4.2 one. Is there any way im stuck between 2 roms or anything like that?
I got it! Downloaded the stock firmware and flashed it through Odin! I'll re root it but I probably won't try a custom rom again for a while.. haha.
I've tried that same rom as you akop and it had an error with PhilZ.
I know with sacs it can be a little tricky with the multiple wipes and rebooting to recovery for more wipes but aosp custom ROMs Dont have near the steps. Just wipe data/cache/dalvic and format system then flash ROM and gapps and your good to go!
Sent from my SCH-R970 using Tapatalk
Won't boot past the galaxy s4 screen
I am very new to the world of rooting. I recently tried to root my t-mobile S4 m919 running 4.4.2. I rooted my phone with http://forum.xda-developers.com/galaxy-s4-tmobile?nocache=1&z=9919900225941092#root I did everything exactly as on the video but when I rebooted after going through clockwork mod and flashing ROOT_M919UVUAMDL.zip It reboots to the galaxy s4 screen and at the top left it says kernel is not seandroid enforcing. Set warranty bit: kernel. It just stays on that screen. anyone help please. I would either like to get my phone working again or finish the root.
---------- Post added at 10:14 PM ---------- Previous post was at 09:52 PM ----------
When I try to try to boot into recovery it also stays on the galaxy s4 screen saying recovery booting... in the left corner stuck
Related
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
Hey,
So I recently acquired a S4 i337m Fido (running 4.3, I1337MVLUEMK6). I tried to root and put TWRP via Odin, didn't end up working (not sure what I did wrong), but managed to root via auto-root and flashed TWRP via Goo Manager.
I have tried twice to put a custom room on, HyperDrive and Paranoid android. I created a nandbackup, then full wiped, and flashed the roms then Gapps and rebooted. Both times, they got stuck on the boot animation (just showing the Samsung Galaxy S4 Logo), with the top left corner saying something about my recovery (when flashed HyperDrive), and something about my kernel when I tried to flash PA. Also, I couldn't get to TWRP on my first 2 tries when flashing HyperDrive (to restore), but got it on my first try with PA.
Any ideas why I am having trouble flashing custom roms?
So what it says on the boot screen logo at top left is:
1. RECOVERY BOOTING (in blue),
2. RECOVERY IS NOT SEANDROID ENFORCING (red)
3. Set Warranty Bit: recovery (yellow)
Cheers, and thanks
Sent from my SGH-I337M using Tapatalk
Miyamato said:
Hey,
So I recently acquired a S4 i337m Fido (running 4.3, I1337MVLUEMK6). I tried to root and put TWRP via Odin, didn't end up working (not sure what I did wrong), but managed to root via auto-root and flashed TWRP via Goo Manager.
I have tried twice to put a custom room on, HyperDrive and Paranoid android. I created a nandbackup, then full wiped, and flashed the roms then Gapps and rebooted. Both times, they got stuck on the boot animation (just showing the Samsung Galaxy S4 Logo), with the top left corner saying something about my recovery (when flashed HyperDrive), and something about my kernel when I tried to flash PA. Also, I couldn't get to TWRP on my first 2 tries when flashing HyperDrive (to restore), but got it on my first try with PA.
Any ideas why I am having trouble flashing custom roms?
So what it says on the boot screen logo at top left is:
1. RECOVERY BOOTING (in blue),
2. RECOVERY IS NOT SEANDROID ENFORCING (red)
3. Set Warranty Bit: recovery (yellow)
Cheers, and thanks
Sent from my SGH-I337M using Tapatalk
Click to expand...
Click to collapse
You need to read a lot more. You can only use safestrap right now. Odin back to MF3 and install safestrap after rooting. Only touchwiz roms using stock kernel will work for you.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Hey, Thanks for answering. So I have to re flags firmware, and re root, with safestrap correct? After that only tw bases roms with stock kernels will work, or as of right now (current situation) only tw and stock kernels will work?
Sent from my SGH-I337M using Tapatalk
Miyamato said:
Hey, Thanks for answering. So I have to re flags firmware, and re root, with safestrap correct? After that only tw bases roms with stock kernels will work, or as of right now (current situation) only tw and stock kernels will work?
Sent from my SGH-I337M using Tapatalk
Click to expand...
Click to collapse
It appears the first one you flashed Hyperdrive is for ATT at model number is i337 your model is i337m not the same thing.... If it was my phone I would wait for azuziel to reply in the other thread or pm him directly.... you can't use i337 firmware on your phone.... you had and hope still have an unlocked bootloader... this means you don't need safety strap.... talk to azuziel before you get too flash happy.... could save you lots of headaches.....
Your issue is in my Galaxy Tab Pro 10.1 (SM-T525) li (kely. I do is just keep it in low battery state. (Even if you press the power button it wont boot. Dont Charge it!)
And connect it on computer. You will see the only logo of you samsung brand. That is second to the last step. The last step is go it on download mode. By pressing Volume Down+Home Button+Power Button. And click volume up. Now download odin and install the compatible version of TWRP for your phone. And now wait. You will see in odin a Reset *Blue* on top corner of the app that is a good sign. Now if you see a Pass *Green* on the top corner of the app. Your ready to go! It will boot in Normal State!
This Might Helpful!
Hello, I am MrGovernor.
I have recently purchased a Galaxy Note 3 N9005 and decided to root it earlier today. The device is running on 4.3 because my carrier decide to delay their releases (O2).
About 2 hours ago I then decided to put a custom recovery on it before installing Omega ROM...
Now, me being a newb, I was following about 3 different tutorials at once; I managed to get to the final stage of using ODIN to flash CWM onto the phone (n9005-cwm-recovery-6.0.4.7-kk). Now, I did this and when my phone rebooted it got the initial loading screen and this message appeared:
RECOVERY BOOTING....
Click to expand...
Click to collapse
Set Warranty Bit : recovery
Click to expand...
Click to collapse
This happens when I go into Recovery Mode and when I boot normally. I can still go into download mode.
I am a newb, have I bricked my new phone or is there any way to salvage it?
Thanks a load!
MrGovernor.
MrGovernor said:
Hello, I am MrGovernor.
I have recently purchased a Galaxy Note 3 N9005 and decided to root it earlier today. The device is running on 4.3 because my carrier decide to delay their releases (O2).
About 2 hours ago I then decided to put a custom recovery on it before installing Omega ROM...
Now, me being a newb, I was following about 3 different tutorials at once; I managed to get to the final stage of using ODIN to flash CWM onto the phone (n9005-cwm-recovery-6.0.4.7-kk). Now, I did this and when my phone rebooted it got the initial loading screen and this message appeared:
This happens when I go into Recovery Mode and when I boot normally. I can still go into download mode.
I am a newb, have I bricked my new phone or is there any way to salvage it?
Thanks a load!
MrGovernor.
Click to expand...
Click to collapse
no its fine all n3 rooted will have that when and if you go back to stock it will go
jaythenut said:
no its fine all n3 rooted will have that when and if you go back to stock it will go
Click to expand...
Click to collapse
Thanks a load!
MrGovernor said:
Hello, I am MrGovernor.
I have recently purchased a Galaxy Note 3 N9005 and decided to root it earlier today. The device is running on 4.3 because my carrier decide to delay their releases (O2).
About 2 hours ago I then decided to put a custom recovery on it before installing Omega ROM...
Now, me being a newb, I was following about 3 different tutorials at once; I managed to get to the final stage of using ODIN to flash CWM onto the phone (n9005-cwm-recovery-6.0.4.7-kk). Now, I did this and when my phone rebooted it got the initial loading screen and this message appeared:
This happens when I go into Recovery Mode and when I boot normally. I can still go into download mode.
I am a newb, have I bricked my new phone or is there any way to salvage it?
Thanks a load!
MrGovernor.
Click to expand...
Click to collapse
it's normal
hhai2pth said:
it's normal
Click to expand...
Click to collapse
Now... Another issue...
I installed PhilZ Touch Recovery and that has worked fine...
However, I went full retard and 'Wiped System for a New ROM' before I made a backup...
I then tried to flash FoxHound ROM, I managed to get through the install process flawlessly, BUT, when the device rebooted it stays on the boot screen...
What can be done to fix this? As I failed to make a backup of my original 4.3 firmware...
Thanks Again!
MrGovernor said:
Now... Another issue...
I installed PhilZ Touch Recovery and that has worked fine...
However, I went full and 'Wiped System for a New ROM' before I made a backup...
I then tried to flash FoxHound ROM, I managed to get through the install process flawlessly, BUT, when the device rebooted it stays on the boot screen...
What can be done to fix this? As I failed to make a backup of my original 4.3 firmware...
Thanks Again!
Click to expand...
Click to collapse
Did u use correct ROM for 4.3? Did u tried flash stock rom again?
hhai2pth said:
Did u use correct ROM for 4.3? Did u tried flash stock rom again?
Click to expand...
Click to collapse
I can't find the 4.3 firmare... Only the 4.4.2 firmare...
I just realized I may have to flash with O2's stock firmare as it is an O2 device...
MrGovernor said:
Hello, I am MrGovernor.
I have recently purchased a Galaxy Note 3 N9005 and decided to root it earlier today. The device is running on 4.3 because my carrier decide to delay their releases (O2).
About 2 hours ago I then decided to put a custom recovery on it before installing Omega ROM...
Now, me being a newb, I was following about 3 different tutorials at once; I managed to get to the final stage of using ODIN to flash CWM onto the phone (n9005-cwm-recovery-6.0.4.7-kk). Now, I did this and when my phone rebooted it got the initial loading screen and this message appeared:
This happens when I go into Recovery Mode and when I boot normally. I can still go into download mode.
I am a newb, have I bricked my new phone or is there any way to salvage it?
Thanks a load!
MrGovernor.
Click to expand...
Click to collapse
oh man...
You are running 4.3, but you flash cwm for KK (4.4.2) ?
You should flash cwm for 4.3 instead.
Try to find the stock firmware, and reflash it.
Cheers!
---------- Post added at 05:29 PM ---------- Previous post was at 05:26 PM ----------
MrGovernor said:
Now... Another issue...
I installed PhilZ Touch Recovery and that has worked fine...
However, I went full retard and 'Wiped System for a New ROM' before I made a backup...
I then tried to flash FoxHound ROM, I managed to get through the install process flawlessly, BUT, when the device rebooted it stays on the boot screen...
What can be done to fix this? As I failed to make a backup of my original 4.3 firmware...
Thanks Again!
Click to expand...
Click to collapse
if you have installed the ROM flawlessly and stuck at the boot screen, try go into recovery again and make a full wipe (but not the wipe for new rom). Then reboot.
But the custom ROM you are flashing is 4.3 also right ?
Because very simple, if you were on stock 4.3, and you flash custom ROM 4.4.2 without update your bootloader first to 4.4.2, the custom ROM won't run.
---------- Post added at 05:31 PM ---------- Previous post was at 05:29 PM ----------
MrGovernor said:
I can't find the 4.3 firmare... Only the 4.4.2 firmare...
I just realized I may have to flash with O2's stock firmare as it is an O2 device...
Click to expand...
Click to collapse
if your device N9005, you may use any other firmware so long as for N9005.
You can try to flash 4.4.2, but you have to tick "update bootloader" at ODIN. Please note, once you are on 4.4.2, you are not able to go back to 4.3, due to different bootloader.
antique_sonic said:
oh man...
You are running 4.3, but you flash cwm for KK (4.4.2) ?
You should flash cwm for 4.3 instead.
Try to find the stock firmware, and reflash it.
Cheers!
---------- Post added at 05:29 PM ---------- Previous post was at 05:26 PM ----------
if you have installed the ROM flawlessly and stuck at the boot screen, try go into recovery again and make a full wipe (but not the wipe for new rom). Then reboot.
But the custom ROM you are flashing is 4.3 also right ?
Because very simple, if you were on stock 4.3, and you flash custom ROM 4.4.2 without update your bootloader first to 4.4.2, the custom ROM won't run.
---------- Post added at 05:31 PM ---------- Previous post was at 05:29 PM ----------
if your device N9005, you may use any other firmware so long as for N9005.
You can try to flash 4.4.2, but you have to tick "update bootloader" at ODIN. Please note, once you are on 4.4.2, you are not able to go back to 4.3, due to different bootloader.
Click to expand...
Click to collapse
That's cleared a load up! I'll install the 4.3 firmware and get back to you (Samsung's Firmware Download Servers are incredibly slow <,<)
yeah. good luck
Thanks for all the help!
I used ODIN to flash this file:
N9005XXUENB4_N9005O2UENB1_N9005XXUENB1_HOME.tar.md5
From SamMobile's Firmware.
It's all working now, and it on the 4.4.2 KitKat Built.
Does this mean the bootload has updated and I can install the 4.4 Omega ROM?
This time I will make a restore point on PhilZ Custom Recovery!
MrGovernor said:
Thanks for all the help!
I used ODIN to flash this file:
N9005XXUENB4_N9005O2UENB1_N9005XXUENB1_HOME.tar.md5
From SamMobile's Firmware.
It's all working now, and it on the 4.4.2 KitKat Built.
Does this mean the bootload has updated and I can install the 4.4 Omega ROM?
This time I will make a restore point on PhilZ Custom Recovery!
Click to expand...
Click to collapse
when you flash it, u did tick the update bootloader right ?
If yes, means you are now on the 4.4.2 bootloader, and you can install the 4.4 custom ROM (but please read the respective thread on how to flash that custom ROM of your choice)
And when you want to flash Philz CWM, do choose the one for 4.4.2. Try to use the latest one.
Good luck!
antique_sonic said:
when you flash it, u did tick the update bootloader right ?
If yes, means you are now on the 4.4.2 bootloader, and you can install the 4.4 custom ROM (but please read the respective thread on how to flash that custom ROM of your choice)
And when you want to flash Philz CWM, do choose the one for 4.4.2. Try to use the latest one.
Good luck!
Click to expand...
Click to collapse
Thanks!
But... On last problem...
I've downloaded and used ODIN to install PhillZ Recovery ("philz_touch_6.08.9-hltexx.tar.md5").
It passes in ODIN, and boots straight to android.
However, when I try to boot into recovery mode, I get the normal 3 lines of text, but after a few seconds it reboots back to android...
What do?
P.S: I tried holding down all 3 buttons through the whole process (that just reboots), holding down only the Home and Volume + buttons once the text appears (still reboots)... I've also tried to Re-Flash the same version twice.
I just want to make a backup for this ROM in-case I f*ck up with other ROMs. Sorry for being such a scrub!
------NOTE----------
Installed Latest Version of PhillZ, all works A-OK!
MrGovernor said:
Thanks!
But... On last problem...
I've downloaded and used ODIN to install PhillZ Recovery ("philz_touch_6.08.9-hltexx.tar.md5").
It passes in ODIN, and boots straight to android.
However, when I try to boot into recovery mode, I get the normal 3 lines of text, but after a few seconds it reboots back to android...
What do?
P.S: I tried holding down all 3 buttons through the whole process (that just reboots), holding down only the Home and Volume + buttons once the text appears (still reboots)... I've also tried to Re-Flash the same version twice.
I just want to make a backup for this ROM in-case I f*ck up with other ROMs. Sorry for being such a scrub!
------NOTE----------
Installed Latest Version of PhillZ, all works A-OK!
Click to expand...
Click to collapse
Sorry was bit busy.
But if you do read my last post... I did mentioned you have to use the latest one better
Cheers, mate!
btw :
why do you like to use KK recovery on 4.3, and when you are on KK, you use 4.3 recovery ?
Set warranty bit is different than set warranty kernel
jerryspring said:
Set warranty bit is different than set warranty kernel
Click to expand...
Click to collapse
And what exactly is the point of posting this in a 4.5 years old thread ?
Dejan Sathanas said:
And what exactly is the point of posting this in a 4.5 years old thread ?
Click to expand...
Click to collapse
Cuz I asked a question and no one answered me. What would be causing the bootloop on my phone? With stock and custom ROMs, it is bootlooping in and out of recovery and saying set warranty bit recovery ...
But no user has to answer you .
Post and if somebody sees it and has the answer they will .
But on the Q&A board as very few read it now and a day is not long enough.
JJEgan said:
But no user has to answer you .
Post and if somebody sees it and has the answer they will .
But on the Q&A board as very few read it now and a day is not long enough.
Click to expand...
Click to collapse
The o.p is different than my question! So, instead of making a duplicate thread with basically same issue, I posted in here.
I updated my rooted note 3 to Kitkat, via this guide
http://forum.xda-developers.com/show....php?t=2740466
It was up and running, but having issues through out the day today. I read through the guide this evening and saw that it recommended wiping the delvic, I had not done that in the previous install so I went ahead, uninstalled the KK, wiped the delvic and re-installed. Now it wont boot at all. It just sits at the Samsung splash screen. It will not boot into stock or normal recovery. Knox is already tripped so im not worried about that. Can anyone help me fix this? All my data is backed up. I have tried reflashing via Odin with both KK and MJ roms. It will accept a MJ rom with appropriate PIT file, but will go to Samsung screen and show "starting recovery", then bootloop to the same. KK will not accept any flash, it will take the PIT file tough.
Help Please!
Did u try flashing a recovery alone?
Sent from my Galaxy Note 3 using Tapatalk
EDIT: Sorted it, flashed TWRP in odin and it worked this time.
I have rooted my i9505 (5.0.1 stock Baseband i9505XXUHOD5) using CF-auto and Odin but I cant install a custom recovery. When I try in odin it says pass but then gets stuck in a loop at reboot. When i go to recovery its still stock and the only way out of the loop is to factory reset abd then try again. It looks like a Vodaphone Germany rom thats been unlocked installed. Any ideas please? I want a custom rom to get rid of the Samsung crap in the background.
Thread can be closed
As you have solved it,like this you open this thread for nothing
And also, CWM and Philz are outdated and out of support(only for this device), always use TWRP[emoji6]
Sent from my GT-I9505 using Tapatalk