Develop Bugs

DO NOT FLASH CWM TOUCH through ROM Manager, KILLS IMEI and 4G DATA!

I see that there is a growing number of people losing their IMEIs and their 4G data service from T-Mobile, as I had the same problem after trying to flash CWM Touch through ROM Manager. After flashing the recovery, I turned of the phone and turned it back on only to receive EDGE speeds. After further research I also realized that my phone has a IMEI of 0. Even after restoring my IMEI through GEEK's method, my data speeds are still EDGE even after flashing complete stock rom through ODIN, data speeds are still EDGE. Just want to know if anyone else had the same issue, after flashing CLOCKWORK Recovery or Clockwork Touch Recovery through ROM Manager.
UPDATE: Would like to know if anyone flash Clockwork TOUCH Recovery through ROM Manager and not the regular clockwork, as I remember when I flashed the regular clockwork first, everything was fine until I paid the 2 bucks and got TOUCH Recovery, is when my IMEI and 4G were lost.
I originally had CWM touch 5.5.0.4 by using the DD method through terminal emulator in order to preserve my binary counter, but then I flashed the standard clock work recovery through ROM manager and then CWM Touch which caused my IMEI and 4G to go bye bye.

I flashed cwm through Rom Manager last week and everything seems to be working fine.
Pebble Blue Samsung Galaxy S3 (T-Mobile Style)

I've flashed this way. Still have imei
Sent from my SGH-T999 using xda app-developers app

dave2metz said:
I flashed cwm through Rom Manager last week and everything seems to be working fine.
Pebble Blue Samsung Galaxy S3 (T-Mobile Style)
Click to expand...
Click to collapse
Me too. Touch version. Everything is fine. IMEI I believe is lost by using wrong root method.
Sent from my SGH-T999 using xda premium

elracing21 said:
I've flashed this way. Still have imei
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
+1
Sent from a Galaxy 3759295 light years away.
Thank me if I helped

I flashed touch recovery through ROM manager as well with no issues.

Is flashing the Sprint way when the phone first came out the wrong root method?I rooted that way but have stayed on stock bc of this imei method. What is the"correct way"to root?
Sent from my SGH-T999 using Tapatalk 2

Me too lol... what did you flash after OP?
Sent from my SGH-T999 using xda premium

fatboy547 said:
Is flashing the Sprint way when the phone first came out the wrong root method?I rooted that way but have stayed on stock bc of this imei method. What is the"correct way"to root?
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
I would like to know this as well. I rooted using the Sprint way and have not flashed one single thing because of the imei issues.

I used that method(sprint) and still have my imei. I've flashed FreeGS3 a bunch of times and a couple of themes without iussue so far.
Sent from my SGH-T999 using xda app-developers app

I used the Sprint method, and pretty much immediately flashed CapRom then redrum's FreeGS3 and Lean build, along with the Adama003 kernel. Then even flashed CM9 and AOKP. All of this was through the Sprint CWM. I finally got ancy and pushed TWRP through terminal emulator(since nobody had issues with losing IMEI with that recovery), so I would feel safe flashing JB AOKP.
I would suggest backing up your IMEI so you don't have to worry about it anymore, push a different recovery, and then go flash crazy! Here is the link to backup/restore: http://forum.xda-developers.com/showthread.php?p=29514187.
Happy flashing! I'm really digging the new Wicked blue ROM!
Sent from my SGH-T999 using xda app-developers app

I used the sprint cwm & odin...via some video found in this forum that said it won't trip the counter. Lost imei & only edge. The vid did say that it would work for tmo & I read other users posts after they had done it. I didn't do anything else after that, I only wanted it rooted. Not sure what I did wrong and I really want to know.
Curious...what do they do with the phones that are returned by a customer?

You guys can back up your imei now. Its in the development section. There's even a video walkthrough.

I've flashed, backed up, and restored through different ROMs including CM9, CM10, TW roms, and EuroSkank builds...IMEI is still intact.
Used Odin to Flash recovery then used ROM Manager Premium to update to latest CWM.

Lakeshow423 said:
You guys can back up your imei now. Its in the development section. There's even a video walkthrough.
Click to expand...
Click to collapse
I'm scurred to even try anything now on my phone. All I wanted was the root ability.

yellaChocolate said:
I'm scurred to even try anything now on my phone. All I wanted was the root ability.
Click to expand...
Click to collapse
Dont be, especially for that.
Sent from my SGH-T999 using xda premium

i used odin to flash CWM but then i try to flash CWM through rom manager and it freezes??
any help guys?
Thanks

This thread needs to be renamed as there is no proof at all to what the op said, they lost their IMEI and want some one to blame sadly they try to blame the peeps behind rom manager and cwm touch, the same people who put tons of energy and free time to make every phone better for us.
Please op change the title or mods change it, it is not fair to the devs who work hard to have one person who has 1 post to blame them

This post is a little bit misleading. I'm sure that Kush over at Rom Manager would not appreciate a post that scares people away from using his application. This may have happened to a few people, but to state that you will lose your IMEI when you flash Rom Manager is just not true. I may be wrong, but losing your IMEI probably has a lot to do with not taking the proper steps to correctly flash a ROM.

Omg guyz iz flashed a I9300 ROM and it screwed my phone! But it was probably the CWM! Stay away from CWM guyz!
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2

[Q] How do I ditch cm10?

alrighty then. I have been playing with my phone for about 2 hours now trying to figure out how to get rid of CM10 so I can flash a new ROM. (had to find dev options etc.) I tried flashing a recovery image through the SGS tool kit, still had CM10. I tried re-rooting (not advised, had a small stroke while figuring out if I bricked or soft bricked) I just did a system wipe, also ill advised, it warned me that I had no OS (thats why we make nandroids like good lil boys and girls.)
For the love of Jeebus someone please tell me how to get CM10 off of my phone so I can flash a new ROM. can I un-root and re-root and start from scratch that way? is that proper? is there an easier way? Why am I asking all these questions?! (because no matter what, I will always be a NooB -.-')
I appreciate any insight you guys can give me, thanks in advance!

gorealmighty said:
alrighty then. I have been playing with my phone for about 2 hours now trying to figure out how to get rid of CM10 so I can flash a new ROM. (had to find dev options etc.) I tried flashing a recovery image through the SGS tool kit, still had CM10. I tried re-rooting (not advised, had a small stroke while figuring out if I bricked or soft bricked) I just did a system wipe, also ill advised, it warned me that I had no OS (thats why we make nandroids like good lil boys and girls.)
For the love of Jeebus someone please tell me how to get CM10 off of my phone so I can flash a new ROM. can I un-root and re-root and start from scratch that way? is that proper? is there an easier way? Why am I asking all these questions?! (because no matter what, I will always be a NooB -.-')
I appreciate any insight you guys can give me, thanks in advance!
Click to expand...
Click to collapse
Fairly simple just download another non cm10 ROM as you did to install cm10 in the first place. If you are unsure of what to do read the instructions in the OP of the ROM you want.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app

mjg688 said:
Fairly simple just download another non cm10 ROM as you did to install cm10 in the first place. If you are unsure of what to do read the instructions in the OP of the ROM you want.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
I appreciate the reply, im hesitant to flash over cm10 though. I seem to remember always having to reflash back to stock (root) before flashinga new ROM, I never encountered any problems when doing so.

gorealmighty said:
I appreciate the reply, im hesitant to flash over cm10 though. I seem to remember always having to reflash back to stock (root) before flashinga new ROM, I never encountered any problems when doing so.
Click to expand...
Click to collapse
Just wipe data, cache and dalvik then flash new rom. No reason whatsoever to flash another stock rom to flash the one you want
I like to break stuff!

-EViL-KoNCEPTz- said:
Just wipe data, cache and dalvik then flash new rom. No reason whatsoever to flash another stock rom to flash the one you want
I like to break stuff!
Click to expand...
Click to collapse
this so goes against every instinct. I guess Ill give it a try though, I cant see another way around it. thank you!

gorealmighty said:
this so goes against every instinct. I guess Ill give it a try though, I cant see another way around it. thank you!
Click to expand...
Click to collapse
Idk who told you you needed to go back to stocm b4 flashing another rom but they were wrong. I've been flashing roms for a few years on 7 different phones and 5 tablets and never once went back to stock before changing roms
I like to break stuff!

-EViL-KoNCEPTz- said:
Idk who told you you needed to go back to stocm b4 flashing another rom but they were wrong. I've been flashing roms for a few years on 7 different phones and 5 tablets and never once went back to stock before changing roms
I like to break stuff!
Click to expand...
Click to collapse
its a habit from the Vibrant. flashing back to stock prevented the possibility of "ghost files." it just kind of ensured everything rolled along smoothly. The reality is that flashing over CM10 is looking like my only option without having to break out good Ol' Command Prompt lol. I appreciate your help guys.!

gorealmighty said:
its a habit from the Vibrant. flashing back to stock prevented the possibility of "ghost files." it just kind of ensured everything rolled along smoothly. The reality is that flashing over CM10 is looking like my only option without having to break out good Ol' Command Prompt lol. I appreciate your help guys.!
Click to expand...
Click to collapse
Just wipe in recovery to get rid of the last roms data and files. You could always odin to stock if you really wanted to but its just extra steps that aren't needed
I like to break stuff!

-EViL-KoNCEPTz- said:
Just wipe in recovery to get rid of the last roms data and files. You could always odin to stock if you really wanted to but its just extra steps that aren't needed
I like to break stuff!
Click to expand...
Click to collapse
got stuck n a boot loop a dozen times, finally said to hell with it and found a stock .tar.MD5 and Odin'd this pig. Again, I appreciate y'alls' help.

Don't forget to nandriod before flashing. It will help you when you need it most.
What recovery were you using? I have used twrp with no problems
Sent from my SPH-L710 using Xparent Green Tapatalk 2

loumoli said:
Don't forget to nandriod before flashing. It will help you when you need it most.
What recovery were you using? I have used twrp with no problems
Sent from my SPH-L710 using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
TWRP. I was trying to flash Jellybam over CM10 . I got stuck in a boot loop, soft bricked it twice and removed my OS once (able to recover from TWRP) im playing around with it tonight.

[Q] Factory Reset Rooted Phone?

Hello everyone...Noob Here
I have Epic Touch 4g that im going to sell. I wanted to factory reset it. But i know if i do that, i'll get stuck in an endless loop because of the root.
I've been on the Note 2 since it came out and i dont know what build Epic Touch is?
I currently have 4.1.2 Jellybean on the it and the build number is FK23
What build should i upgrade/downgrade to? Can i do it safely without bricking my phone?
What should i do?
Any help would be great
Thank You,
Major <3

Factory reset will not cause a boot loop, it also will not remove root. You need to use a One-Click restore.
Sent from my SPH-D710 using xda premium

Majorcrafter said:
Hello everyone...Noob Here
I have Epic Touch 4g that im going to sell. I wanted to factory reset it. But i know if i do that, i'll get stuck in an endless loop because of the root.
I've been on the Note 2 since it came out and i dont know what build Epic Touch is?
I currently have 4.1.2 Jellybean on the it and the build number is FK23
What build should i upgrade/downgrade to? Can i do it safely without bricking my phone?
What should i do?
Any help would be great
Thank You,
Major <3
Click to expand...
Click to collapse
Just did this to return to Sammy for repair. Btw, in the future, questions go in the q&a, not general. Kennyglass is awesome, and will move this promptly I'm sure . But in the meantime, first, while rooted, run triangle away. Then use Mobile Odin to flash the gb27(sprint), gb28(vm), or gc01(boost) unrooted restore. When that is done, after reboot, format your internal hard drive (and external if you are selling that) and you will be good to go. Good luck.
Sent from my PC36100 using xda app-developers app

Possible to damage Recovery section?

Hello all
I unfortunately had to get a replacement for my S3 because the charging port got screwed up.
I tried to root the phone by installing CWM and it seemed to go fine. I did this with Odin using qbking77's methods and files.
I went to look for my zip file to flash and I could find no zip files at all.
It kept saying that E won't mount and stuff like that.
I had a stock recovery tar file for my GalaxyS3 from qbking77 that I used before to get to stock recovery for updates
I flashed it with odin and it said it flashed fine.
Phone seems to be working fine.
I went back to make sure it was there and it showed the little android guy with his heart spinning and then turning red and he died!
Several error messages came up in red.
Anyone ever hear about this and what did I do wrong?
I am sure I used the files I have used for my Galaxy before.
The phone still works so far thankfully!
Any advise and help would be appreciated.
Mike

mikeinstlouis said:
Hello all
I unfortunately had to get a replacement for my S3 because the charging port got screwed up.
I tried to root the phone by installing CWM and it seemed to go fine. I did this with Odin using qbking77's methods and files.
I went to look for my zip file to flash and I could find no zip files at all.
It kept saying that E won't mount and stuff like that.
I had a stock recovery tar file for my GalaxyS3 from qbking77 that I used before to get to stock recovery for updates
I flashed it with odin and it said it flashed fine.
Phone seems to be working fine.
I went back to make sure it was there and it showed the little android guy with his heart spinning and then turning red and he died!
Several error messages came up in red.
Anyone ever hear about this and what did I do wrong?
I am sure I used the files I have used for my Galaxy before.
The phone still works so far thankfully!
Any advise and help would be appreciated.
Mike
Click to expand...
Click to collapse
The issue is because of a change that was made to the Newer Devices. Use one of the Recoveries from THIS THREAD.

If it's a new s3 its a known issue with the phone...u need a modded recovery. Check here http://forum.xda-developers.com/showthread.php?t=2391616
Sent from my SPH-L710 using xda app-developers app

I am hoping that this means that I haven't fried that part of my phone and I can still install a recovery. Are these recoveries that I could use to root my phone or custom recoveries that I can revert to to get over the air updates. Thank you very much for your help you guys. I'm still kind of new with this even though I've been doing it for years
Sent from my SPH-L710 using XDA Premium HD app

mikeinstlouis said:
I am hoping that this means that I haven't fried that part of my phone and I can still install a recovery. Are these recoveries that I could use to root my phone or custom recoveries that I can revert to to get over the air updates. Thank you very much for your help you guys. I'm still kind of new with this even though I've been doing it for years
Sent from my SPH-L710 using XDA Premium HD app
Click to expand...
Click to collapse
Yes you can still use these Recoveries. I doubt you " fried " your device. Use these Recoveries in the Root process where you would use the older ones. Yes you can Revert them Back.

Then how can I revert back to get over the air updates? The stock recovery that I flashed showed the little Android guy had died..
Sent from my SPH-L710 using XDA Premium HD app

I think this should work for you just fine. Just be sure to not miss the step about the factory reset.
http://forum.xda-developers.com/showthread.php?t=1904099
[ROM/RESTORE][!MD4 OTA!](5-10)Quick Return to UNROOTED STOCK WITH FLASH COUNT RESET
Sent from my SPH-L710 using Tapatalk 2

From what I read you have to have a recovery to flash this.. I have no recover... And CWM won't let me do anything... That's my problem.. This new style of phone won't let me put on a functional recovery.. Does that make sense?
Sent from my SPH-L710 using xda premium

mikeinstlouis said:
From what I read you have to have a recovery to flash this.. I have no recover... And CWM won't let me do anything... That's my problem.. This new style of phone won't let me put on a functional recovery.. Does that make sense?
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
In the OP of the thread I linked you it gives instructions on how to push the Recovery with ADB. It also has Recoveries you can do through ODIN.
TEAM MiK
MikROMs Since 3/13/11

Note 3 issues with CWM/Goo Manager recovery bootloops

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