i have been using 4.4 (CM,OMNI,Vanir,etc..) for a long time, now i want to go back to 4.3.1 (tried CrDorid,CM,Beanstalk) and all the 4.3 Roms i get boot loop... why is this happening?
sorry for my bad english... and thx!
jesan9 said:
i have been using 4.4 (CM,OMNI,Vanir,etc..) for a long time, now i want to go back to 4.3.1 (tried CrDorid,CM,Beanstalk) and all the 4.3 Roms i get boot loop... why is this happening?
sorry for my bad english... and thx!
Click to expand...
Click to collapse
strange because bootloop is related to corrupted rom or you are not wiping (3wipe) before installin new rom or old, i already test the kitkat Slimkat and to return to the 4.3.1 dirty unicorn the most cutomizable one and very good stability also, am using the classic CWM not the TWRP full touch version
so try to flash a CWM again then another rom
rami2013 said:
strange because bootloop is related to corrupted rom or you are not wiping (3wipe) before installin new rom or old, i already test the kitkat Slimkat and to return to the 4.3.1 dirty unicorn the most cutomizable one and very good stability also, am using the classic CWM not the TWRP full touch version
so try to flash a CWM again then another rom
Click to expand...
Click to collapse
i did that, tried TWRP (format system,cache anda data) and then CWM and nothing happened... but anyways, i can live with 4.4...
i cant even boot on 4.2.2... i want to go back and i cant, im stuck in 4.4.2 ._. plz help
You guys will probably have to Odin back to stock and then flash from there. Seems like something got corrupted with your upgrade into 4.4 I've personally gone all the way back down to 4.1.1 from 4.4 and had no issues. This was just to test a ROM but still.
Sent from my Galaxy Nexus using xda app-developers app
Or just use fastboot. Why isnt there love for fastboot?
Sent from my Galaxy Nexus using XDA Premium HD app
mkuehl06 said:
You guys will probably have to Odin back to stock and then flash from there. Seems like something got corrupted with your upgrade into 4.4 I've personally gone all the way back down to 4.1.1 from 4.4 and had no issues. This was just to test a ROM but still.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
i used NexusRootToolkit like 3 times and the stock 4.3 jwr66y is the only 4.3 that is booting... i cant understand why is this happening... im about to download a 4.2.2 rom to see if it boots... sorry for my english again
Related
First I will start off by thanking everyone for taking the time out to respond to my question. With that being said, I have the gt-n5110 firmware 4.1.2. I have seen the 4.2.2 leaked rom and roms from other developers that are running the 4.2.2. Is it possible to flash these roms, even though I have 4.1.2? Or do I have to stick to the 4.1.2 roms only? Thanks again.
Sent from my GT-N5110 using Tapatalk 2
There are two ways you can upgrade your note to 4.2.2. Head over to the note 8 development forum. There are custom roms that require you to root and flash a custom recovery before you can flash the upgrade. The other is the leaked rom that can be flashed via odin. Be sure to read and follow directions. The information is all there.
Sent from my GT-N5110 using Tapatalk 2
cavsoldier19d said:
There are two ways you can upgrade your note to 4.2.2. Head over to the note 8 development forum. There are custom roms that require you to root and flash a custom recovery before you can flash the upgrade. The other is the leaked rom that can be flashed via odin. Be sure to read and follow directions. The information is all there.
Sent from my GT-N5110 using Tapatalk 2
Click to expand...
Click to collapse
So I'M currently on CiV's 4.1.2 ROM all I have to do to be on CIV's 4.2.2 ROM is flash it Via CWM Recovery?
Yes. Because there is a big difference in android versions...you will want to do a full wipe, then flash. So be sure to backup whatever u need before doing so.
Sent from my GT-N5110 using Tapatalk 2
Its always good to see others with the same questions as me.
Sent from my GT-N5110 using Tapatalk 2
cavsoldier19d said:
Yes. Because there is a big difference in android versions...you will want to do a full wipe, then flash. So be sure to backup whatever u need before doing so.
Sent from my GT-N5110 using Tapatalk 2
Click to expand...
Click to collapse
Thanx again. Not to be a bother but would I be able to flash it via Mobile 0din? (just checking my options and for future reference)
you should be able to, but why would you want to?
Its a simple wipe and flash in CWM, so just do it that way, or, if you use TWRP, then do it with that...
wase4711 said:
you should be able to, but why would you want to?
Its a simple wipe and flash in CWM, so just do it that way, or, if you use TWRP, then do it with that...
Click to expand...
Click to collapse
Ok thanks, makes sense... no need for me to complicate things
Help
Hey everybody. I´m new here. Could someone please help me? I have a note 8.0 gt-n5110 and I flashed the leaked 4.2.2 firmware, but since I had some problems (sometimes it doesn´t respond) I decided to go back to 4.1.2. I already downloaded the firmware and flashed it, but now I´m on a bootloop, It will never pass the samsung logo. What should I do? I already flashed the 4.1.2 firmware 2 times and nothing...
grivera96 said:
Hey everybody. I´m new here. Could someone please help me? I have a note 8.0 gt-n5110 and I flashed the leaked 4.2.2 firmware, but since I had some problems (sometimes it doesn´t respond) I decided to go back to 4.1.2. I already downloaded the firmware and flashed it, but now I´m on a bootloop, It will never pass the samsung logo. What should I do? I already flashed the 4.1.2 firmware 2 times and nothing...
Click to expand...
Click to collapse
Can you get into your recovery? If so do a system restore, that should wipe everything and you could start again fresh.
Sent from my GT-N5110 using Tapatalk 2
Thank you
mann75 said:
Can you get into your recovery? If so do a system restore, that should wipe everything and you could start ack fresh.
Sent from my GT-N5110 using Tapatalk 2
Click to expand...
Click to collapse
Thank you so much, it worked :good: I got back to the old reliable 4.1.2. I think I will just upgrade to 4.2 when an official update is avalaible (no more beta). I don´t know if it was just me, but with the beta of 4.2.2 I had lots of problems such as the screen (didn´t respond sometimes), the s-pen was a little uncalibrated and when I wanted to set an image as wallpaper it looked blurred.
grivera96 said:
Thank you so much, it worked :good: I got back to the old reliable 4.1.2. I think I will just upgrade to 4.2 when an official update is avalaible (no more beta). I don´t know if it was just me, but with the beta of 4.2.2 I had lots of problems such as the screen (didn´t respond sometimes), the s-pen was a little uncalibrated and when I wanted to set an image as wallpaper it looked blurred.
Click to expand...
Click to collapse
Glad it worked out for you. Its a wonderful thing when you can use the recovery application.
Sent from my GT-N5110 using Tapatalk 2
grivera96 said:
Thank you so much, it worked :good: I got back to the old reliable 4.1.2. I think I will just upgrade to 4.2 when an official update is avalaible (no more beta). I don´t know if it was just me, but with the beta of 4.2.2 I had lots of problems such as the screen (didn´t respond sometimes), the s-pen was a little uncalibrated and when I wanted to set an image as wallpaper it looked blurred.
Click to expand...
Click to collapse
thats why they call it beta
My note 8 running 4.1.2 taste like running 4.2.2
The UI is a bit differences with S4 UI
Sent from my GT-N5100 using Tapatalk 2
cavsoldier19d said:
Yes. Because there is a big difference in android versions...you will want to do a full wipe, then flash. So be sure to backup whatever u need before doing so.
Sent from my GT-N5110 using Tapatalk 2
Click to expand...
Click to collapse
I have the same question regarding a 4.1.2 --> 4.2.2 rom flash... After I do a NANDROID backup, full wipe and flash the ROM from CWM/TWRP can I recover the cache from the NANDROID backup to bring back all my screen setups or do I have to build my setup from scratch?
Many thanks!! I know its a noob question but I've searched for a while and figured I might as well just post the question.
stilldmoney said:
I have the same question regarding a 4.1.2 --> 4.2.2 rom flash... After I do a NANDROID backup, full wipe and flash the ROM from CWM/TWRP can I recover the cache from the NANDROID backup to bring back all my screen setups or do I have to build my setup from scratch?
Many thanks!! I know its a noob question but I've searched for a while and figured I might as well just post the question.
Click to expand...
Click to collapse
Never a good idea to do this. More times than not, you will run into problems thereby creating even more work for yourself. Just do it the right way and start fresh after a base update.
Sent from my GT-N5110 using Tapatalk 2
I recently bought, and finally rooted my sprint sph-l710. I have flashed two roms, hyperdrive, and moar roms. My problem is that i cant flash anything else, only those two roms. Is there a fix?
bigchuq said:
I recently bought, and finally rooted my sprint sph-l710. I have flashed two roms, hyperdrive, and moar roms. My problem is that i cant flash anything else, only those two roms. Is there a fix?
Click to expand...
Click to collapse
What do you mean you can't flash anything else? When you flash, are you wiping everything clean each time before flashing ROMs or are you dirty flashing?
tkepk181 said:
What do you mean you can't flash anything else? When you flash, are you wiping everything clean each time before flashing ROMs or are you dirty flashing?
Click to expand...
Click to collapse
yes, i'm wiping everything, whenever i try to install any other rom i have some type of error. i'm new to this so please excuse my noobness. i've tried to flash a stable cm10, among others with no luck.
Do you have the md4 boot loader?
Sent from my SPH-L710 using xda app-developers app
The new S3 have been modded by Sprint /Samsung and require a modded recovery in order to mount storage. The other issue is that you can not flash an aosp style rom. You should be able to flash any TW rom but it won't allow aosp roms to flash. None of the developers have a new S3 so until someone gets one ir someone volunteers one this won't be solved.
Remember search is your best friend, Have a great day!
IDontKnowMang said:
Do you have the md4 boot loader?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
I believe so, but i'm not sure is that @ the end of the build number? If so, yes
bigchuq said:
I believe so, but i'm not sure is that @ the end of the build number? If so, yes
Click to expand...
Click to collapse
If your getting a status 7 error that is the bootloader error flash this in recovery it will update all your firmware and bootloader. http://db.tt/Qt6NcH0a
After flashing this make sure you reboot the phone then try going back into recovery and flashing the rom you want.
Remember search is your best friend, Have a great day!
Is this still a legit fix even after the 4.3 upgrade?
I just tried this and now my phone wont even power on.
Not sure what happen but whenever i try to flash a 4.3 rom i get the rom directory location with "(bad)" at the end. im trying to use the pac man rom but no luck i was on it last week but after i tried Ditto 3 it was a no go could some1 help i have mostly all I317 firmwares but any help would be nice.
ken2kold said:
Not sure what happen but whenever i try to flash a 4.3 rom i get the rom directory location with "(bad)" at the end. im trying to use the pac man rom but no luck i was on it last week but after i tried Ditto 3 it was a no go could some1 help i have mostly all I317 firmwares but any help would be nice.
Click to expand...
Click to collapse
What recovery you on?
Sent from my SAMSUNG-SGH-I317 using XDA Premium 4 mobile app
i have tried them all twrp, phil cwm, and regular cwm
ken2kold said:
i have tried them all twrp, phil cwm, and regular cwm
Click to expand...
Click to collapse
Have you tried using Odin to return to fully stock? Then re root it flash Rom of choice, too if problem still persist...
Before doing above did you try a internal storage wipe b4 your install? To get rid of all old days from previous Rom!!
SENT FROM MY SAMMY i317 USING TAPATALK
need a 4.3 Bootloader
ken2kold said:
i have tried them all twrp, phil cwm, and regular cwm
Click to expand...
Click to collapse
I had the issue then I scoured the net to find the download
Bajanman said:
Have you tried using Odin to return to fully stock? Then re root it flash Rom of choice, too if problem still persist...
Before doing above did you try a internal storage wipe b4 your install? To get rid of all old days from previous Rom!!
SENT FROM MY SAMMY i317 USING TAPATALK
Click to expand...
Click to collapse
I will try that sounds like it would work
Sent from my Nexus 7 using Tapatalk
Hi Guys This is not new to me, but what I missing,I have a galaxy s3 from at&t, I flashed to many roms before,but now I try to go to 4.4 and I can't I get error 7 and msd 5 no found android with a red triangle in the chest ,even the, I when back to stock 4.11 rooted and install recovery. What I done till now : the friendly guide for the error 7, toggle the the restriction in the recovery options still the same problem, even the OTA update from At& can't be installed. Is driving me nuts any Help ? thanks.:good:
Are you running the latest recovery? 4.4 ROMs require the latest TWRP or CWM.
audit13 said:
Are you running the latest recovery? 4.4 ROMs require the latest TWRP or CWM.
Click to expand...
Click to collapse
Sorry to take to long to get back ,You where right, I believed that I had the last ,now is working fine thanks a lot I did flash to 4.4 ,
now no WiFi, I'm working on it
chi3sol said:
Sorry to take to long to get back ,You where right, I believed that I had the last ,now is working fine thanks a lot I did flash to 4.4 ,
now no WiFi, I'm working on it
Click to expand...
Click to collapse
Could it be the modem that you're running? Did Wifi work on previous ROMs?
I got it working, but start geting froze and buch of isues, did flash it again and then after flash the google app the screen turn black and the phone won't boot , I did went back to stock everything is fine
Is any way to check if some aystem file is mising
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
What ROM are you trying to flash?
I fix it thanks
Sent from my GT-P3110 using xda app-developers app
audit13 Thanks a lot
Hi XDA! I have a Samsung Galaxy Note 3 N900T T-Mobile. I've had custom roms such as CM11 Nightly in the past. Well after trying to do a fresh install a while back of another custom rom, my phone at first had no OS because I wiped it like a doofus. So I flashed it back to stock, 4.3 at the time. And then starting a couple weeks ago I flashed CWM using CWM Manager app. That's when the same issue that's recurring over and over, began. My phone works great as long as I never reboot into recovery. If I reboot into recovery it gets stuck in a bootloop. However I noticed tonight after trying to reboot into recovery using goo manager, I noticed the last line when it first boots, then bootloops, says Set warranty bit-recovery. If I remember correctly shouldn't it say kernel?? I know this is my fault because I'm not as knowledgable as all of you (I'm still learning on my own). SO my question is this. I want to fix this once and for all because I can't ever flash a custom rom like Darthstalker (that's the one I'd like to flash)...after several failed attempts of flashing CM for example, to no avail. What can I do to fix this once and for all and be able to flash a kernel, and Darthstalker? I can get into download mode, needless to say. ANd all the other times it's bootlooped I flashed KitKat 4.4.2 and everything works fine until i try to reboot into recovery. I am at my witts end because this i I really want a custom rom instead of flashing only the md5. Would anyone please be willing to give me a tutorial of some kind? I know it's a lot to ask but I can't find another reliable source that can explain how to do all of this. You're the only site I trust and if anyone is willing to give mea tutorial via email , PM, etc. I'd be eternally grateful beyond belief. Thank you in advance for any advice or info
I posted a few days ago about my bootlooping in the recovery. I finally fixed it by these 3 steps.
1) Odin flashed Stock 4.4.2 complete as this sets the correct boot loader.
2) I downloaded Twrp 2.7.0 the one that list KitKat (Must say this) 4.4 version.
http://goo.im/devs/OpenRecovery/hltetmo/openrecovery-twrp-2.7.0.0-hltetmo-4.4.img.tar
3) Right from Odin when flashing this you set it not to reboot, Once finished you then unplug the usb cable and pull the battery. Let is sit for about 10 sec. Then with the upVlm,Home and Power it will boot to the recovery. It first will post what you said but wait about 10 sec more twrp will come up.
4) Now you should be able to flash any rom you want. I am using axmans N3 for now works great. I will be trying CM 11 later.
5) make a backup once in Twrp
Hope this helps.
helterkelter said:
Hi XDA! I have a Samsung Galaxy Note 3 N900T T-Mobile. I've had custom roms such as CM11 Nightly in the past. Well after trying to do a fresh install a while back of another custom rom, my phone at first had no OS because I wiped it like a doofus. So I flashed it back to stock, 4.3 at the time. And then starting a couple weeks ago I flashed CWM using CWM Manager app. That's when the same issue that's recurring over and over, began. My phone works great as long as I never reboot into recovery. If I reboot into recovery it gets stuck in a bootloop. However I noticed tonight after trying to reboot into recovery using goo manager, I noticed the last line when it first boots, then bootloops, says Set warranty bit-recovery. If I remember correctly shouldn't it say kernel?? I know this is my fault because I'm not as knowledgable as all of you (I'm still learning on my own). SO my question is this. I want to fix this once and for all because I can't ever flash a custom rom like Darthstalker (that's the one I'd like to flash)...after several failed attempts of flashing CM for example, to no avail. What can I do to fix this once and for all and be able to flash a kernel, and Darthstalker? I can get into download mode, needless to say. ANd all the other times it's bootlooped I flashed KitKat 4.4.2 and everything works fine until i try to reboot into recovery. I am at my witts end because this i I really want a custom rom instead of flashing only the md5. Would anyone please be willing to give me a tutorial of some kind? I know it's a lot to ask but I can't find another reliable source that can explain how to do all of this. You're the only site I trust and if anyone is willing to give mea tutorial via email , PM, etc. I'd be eternally grateful beyond belief. Thank you in advance for any advice or info
Click to expand...
Click to collapse
I'm honestly confused on what you are asking. What bootloader are you on . Jellybean or Kit Kat. That is the big part of the question. If you are on Kit Kat you can no longer run Darthstalker as it's a 4.3 rom. Just curious because you say that you flashed 4.4.2 rom and everything works. Also, the bootloop would either be your kernel or your recovery. I would suggest Philz or Twrp 2.7 as they are both updated and will work on either bootloader.
Once you have flashed a bootloader and custom recovery NEVER USE ODIN AGAIN UNLESS YOU HAVE BRICKED YOUR PHONE.
dragonstalker said:
I'm honestly confused on what you are asking. What bootloader are you on . Jellybean or Kit Kat. That is the big part of the question. If you are on Kit Kat you can no longer run Darthstalker as it's a 4.3 rom. Just curious because you say that you flashed 4.4.2 rom and everything works. Also, the bootloop would either be your kernel or your recovery. I would suggest Philz or Twrp 2.7 as they are both updated and will work on either bootloader.
Once you have flashed a bootloader and custom recovery NEVER USE ODIN AGAIN UNLESS YOU HAVE BRICKED YOUR PHONE.
Click to expand...
Click to collapse
I'm on 4.4.2.I figured it is my kernel. After sending this message last night I had my phone in download mode but didn't do anything to it. I decided to turn it off and then on again and it booted. So if this is a kernel issue where would I find one and how would I do this? Oh and when the bootloop occurred last night I was trying to boot into recovery via too manager. If I put Twrp on my phone when I have CWM will they interfere? I apologize for the likely stupid questions but I'm just wanting to get it done properly. One last thing is PacMan ROM compatible?
helterkelter said:
I'm on 4.4.2.I figured it is my kernel. After sending this message last night I had my phone in download mode but didn't do anything to it. I decided to turn it off and then on again and it booted. So if this is a kernel issue where would I find one and how would I do this? Oh and when the bootloop occurred last night I was trying to boot into recovery via too manager. If I put Twrp on my phone when I have CWM will they interfere? I apologize for the likely stupid questions but I'm just wanting to get it done properly. One last thing is PacMan ROM compatible?
Click to expand...
Click to collapse
The kernels you can use are listed in the general thread. A user posted a very good listing of what's what. TWRP 2.7 or Philz Touch are the 2 recoveries i would recommend using. Whichever one you decide will overwrite the other. you can never have 2 recoveries.
OK I'm sorry but I'm a little confused. One solution mentioned was to flash 4.4.2 stock using Odin. But you said not to use it unless I've bricked my phone. So now I'm lost. Lol. Do I flash the stock with the above mentioned method? Or do I flash a kernel and then a ROM? I apologize for my inexperienced questions. I'm including my device info below in hopes you can tell me the very first step I should take. Thank you for all your help!!!
Baseband N900TUVUCNB4
KERNEL- 3.4.0-660648 [email protected]#1
BUILD #- KOT49H.N900TUVUCNB4
SE FOR ANDROID STATUS- ENFORCING SEPF_SM-N900T_4.4.2-0005
SECURITY SOFTWARE VERSION- MOF v1. Release 2
Sent from my SM-N900T using xda app-developers app
helterkelter said:
OK I'm sorry but I'm a little confused. One solution mentioned was to flash 4.4.2 stock using Odin. But you said not to use it unless I've bricked my phone. So now I'm lost. Lol. Do I flash the stock with the above mentioned method? Or do I flash a kernel and then a ROM? I apologize for my inexperienced questions. I'm including my device info below in hopes you can tell me the very first step I should take. Thank you for all your help!!!
Baseband N900TUVUCNB4
KERNEL- 3.4.0-660648 [email protected]#1
BUILD #- KOT49H.N900TUVUCNB4
SE FOR ANDROID STATUS- ENFORCING SEPF_SM-N900T_4.4.2-0005
SECURITY SOFTWARE VERSION- MOF v1. Release 2
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
You are already on the 4.4 bootloader so you can no longer use the Darthstalker rom, you can only use Kit Kat 4.4.2 and above roms from here on out. Next question would be have your rooted your phone since the update and have a custom recovery. If you have not rooted, then you will need to use Odin to run the CF_Autoroot, but that will trip your Knox to 0x1. Thus voiding your warranty.
Yes I rooted. But every time I try flashing CWM or Twrp it bootloops. And to get out of bootloop I have to boot in download and then cancel download and it reboots normal again. Is this a kernel or boot loader issue?
Sent from my SM-N900T using xda app-developers app
helterkelter said:
Yes I rooted. But every time I try flashing CWM or Twrp it bootloops. And to get out of bootloop I have to boot in download and then cancel download and it reboots normal again. Is this a kernel or boot loader issue?
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
Which cwm and twrp are you trying to flash. The only 2 that will work on Kit Kat are PHilz touch latest one, and TWRP 2.7
Twrp 5.7.3
Sent from my SM-N900T using xda app-developers app
So do I flash stock as mentioned from another member or do I flash a kernel? I'm not sure what to do next
Sent from my SM-N900T using xda app-developers app
helterkelter said:
So do I flash stock as mentioned from another member or do I flash a kernel? I'm not sure what to do next
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
oh sorry for the late response. Just got back from boy scouts. Anyway. No you don't need to flash back to stock, Your just flashing the wrong version of TWRP. You can go to the android originial development thread and download the TWRP 2.7 and flash via recovery and you will be all good to go. Also, download the latest Wootever kernel just to make sure you have both angles covered. Both downloads are found in the same section.
Ok thanks so much. Im a little scared to flash in TWRP as it always puts me in bootloops. I did download philz and I was considering flashing that via Odin as I can't boot into recovery. Would that be the next best thing to do? Oh and dont apologize!! I can't thank you enough!
Sent from my SM-N900T using xda app-developers app
helterkelter said:
Ok thanks so much. Im a little scared to flash in TWRP as it always puts me in bootloops. I did download philz and I was considering flashing that via Odin as I can't boot into recovery. Would that be the next best thing to do? Oh and dont apologize!! I can't thank you enough!
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
Yes, odin the custom recovery and you should have no more issues. As for the bootloops with TWRP, you only had issues with that, because the version you were trying to use was outdated and does not work on Kit Kat
Hmm found an interesting possible solution and would greatly appreciate your guidance. I found a ROM that supports KK and I think in this thread that it may indicate why I bootloop when trying to bootbin recovery. http://www.infamousdevelopment.com/...-recover-from-a-bad-flash-updated-for-kitkat/
I'm seriously considering following this whole tutorial of his to the letter. Would it be wise to do?
Sent from my SM-N900T using xda app-developers app
helterkelter said:
Hmm found an interesting possible solution and would greatly appreciate your guidance. I found a ROM that supports KK and I think in this thread that it may indicate why I bootloop when trying to bootbin recovery. http://www.infamousdevelopment.com/...-recover-from-a-bad-flash-updated-for-kitkat/
I'm seriously considering following this whole tutorial of his to the letter. Would it be wise to do?
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
You have already upgraded to Kit Kat, that part is done. and you ran CF_Autoroot correct in Odin correct? If you have done both steps all that is left is to Odin the Philz Touch Recovery that you downloaded.
Ok and yes I did both the first two steps you asked above. After I do flash philz can I flash a ROM it CM or PacMan as long ad they're 4.4.2?
Sent from my SM-N900T using xda app-developers app
helterkelter said:
Ok and yes I did both the first two steps you asked above. After I do flash philz can I flash a ROM it CM or PacMan as long ad they're 4.4.2?
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
As long as they are AOSP Roms that support both bootloaders yes, and as i've been told most if not all the AOSP Roms do support the Kit Kat bootloader that you are already on.
Ok thank you again. I will likely flash philz tonight (if hubby allows me to cuz I usually stay up all night til I got my phone the way I want it, ie no boot loops lol) I will report back to let you know if it works. This phone has been through hell and back with me but I've learned a lot!! Especially from contributors such as yourself. :thumbup:
Sent from my SM-N900T using xda app-developers app
Cool. I'm glad I read this thread. I too had same problems.
Sent from my NOTE 3 using Tapatalk