Related
Hi Guys!
I have plan to buy Galaxy S3 in Tmo (in retail) and have a two questions. Is it safe to flash new phone from Tmo to stock android? I don't want to have any Tmo stuff and Tmo's andro version... Question two is, when I'll have stock android on Galaxy, Do I get an OTA when it'll appear? Or I will have to flash manually when new rom will appear?
Thanks for clarification!
dzordzyk
Now someone correct me if im wrong as i still call myself a noob but i do have basic knowledge but you can always root your phone/odin a custom recovery and then flash a stock rom with all the bloat removed. You could always just remove bloat via titanium back up as well tobyour liking. Check out the development thread. Theres alot to read but theres very usefull info to get caught up on. Hope this helps. Oh and in regards to ota, im stock with root injection and im waiting for todays update to try the root keeper method.
Sent from my SGH-T999 using Tapatalk 2
For android builds, or AOSP, there are options. You won't get a pure stock AOSP unless you compile and build it yourself. Though Cyanogenmod and AOKP are modified builds of AOSP that have various mods and tweaks I have been using Cyanogenmod 9 and will switch to 10 once it releases.
You will not receive OTA updates as these are custom roms and updates need to be manually flashed
There is a lot of lingo to learn and lots of mistakes to learn from. You will become addicted to flashing updates and various roms very quickly
Sent from my SGH-T999 using xda premium
Thanks guys for quick response!
Every flash in Samsung which I'd like to do has to be done via Odin? Sorry for 'noob' questions but before SGS3 I had NexusOne - everything was simpler on it
Flashing doesn't void my warranty, right? AFAIK on Samsung we have something called "Flash counter" and if we'd like to use warranty, Flash counter should be "0", that's right?
After buy, Do I have unlock phone or something like that?
Thanks for patience! I appreciate it
dzordzyk
No, you would want to odin a stock injected rom or odin a recovery, boot into recovery and then flash the super user zip. I dont know anything about odins counter but the triangle away seems to be working well on our phones unless someone else knows otherwise.
Confirming that if your on the stock root injected rom, use rootkeeper, do a temp unroot and youll be able to get the ota installed. Mine just rebooted from installation. Working good and glad it was so easy. Abq nm here. Hope i helped.
Sent from my SGH-T999 using Tapatalk 2
nice
so, this is a veeery good question that I've been wondering myself for quite some time...If you flash a stock rom via ODIN, and you are not rooted anymore, will you get that rom's OTA updates when available? Please, someone who's done this, reply with some precise anwser! Thank you very mutch :laugh:
sebbyromania said:
so, this is a veeery good question that I've been wondering myself for quite some time...If you flash a stock rom via ODIN, and you are not rooted anymore, will you get that rom's OTA updates when available? Please, someone who's done this, reply with some precise anwser! Thank you very mutch :laugh:
Click to expand...
Click to collapse
+1 wondering if this is true
If you are running stock do you get OTA updates? Of course.
You will get ota updates if running stock ONLY! You can be rooted, but you must not have a custom bootloader. Otherwise it will not work.
Sent from my SGH-T999 using xda app-developers app
Trying to install a leak thru stock recovery. Does anyone Known how to get past that issue? Thanks
Jake
themadzionist said:
Trying to install a leak thru stock recovery. Does anyone Known how to get past that issue? Thanks
Jake
Click to expand...
Click to collapse
As far as I can tell, I believe it means you're rooted still. I had the same problem so I Odin'd stock UVALH2 and then installed the leak without issue.
Not trying to hijack this thread but have been wondering why do you guys try to install leaks throw stock recovery. It is super easy to root this phone. Why not root install custom recovery then jush flash leaks?
Sent from my SGH-T999
Because you have to be 100% stock to install the leaks. This is the source of the error btw op. Prob not root but a custom recovery. Must be stock everything, modem and kernel must match too.
Sent from my SGH-T999 using xda app-developers app
DocHoliday77 said:
Because you have to be 100% stock to install the leaks. This is the source of the error btw op. Prob not root but a custom recovery. Must be stock everything, modem and kernel must match too.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
This is just not true. I install those OTA leaks every time they are released. Never once used stock recovery to do it.
Aerowinder said:
This is just not true. I install those OTA leaks every time they are released. Never once used stock recovery to do it.
Click to expand...
Click to collapse
Same here, I didn't come from a stock rom. Oh well.
So are you flashing the deodexed roms then?
Im talking about the actual ota you download from somewhere like sammobile.
It patches the existing system (UVDLI8 patches UVALI5) if anything is modded in UVALI5 the patch wont work, or if it does it can cause problems.
If you're flashing roms from development section then yes you can flash normally with custom recovery. But those roms are based on the otas, they're not the actual otas themselves.
Sent from my SGH-T999 using xda app-developers app
I don't bother with TW custom roms. Not really my thing, but I understand why people might want them.
I flash the OTA updates from the link in my signature (sammobile) in order to pull modems. Although there hasn't been a point lately, because you are working at the speed of light. But I flashed UVALEM, UVALH2, I1, 2, 3, 4, 5, 6, you get the idea.
Are you using TWRP? That recovery might not work with the OTA updates, but I've proven myself, and through many other people, that you can indeed flash OTA leaks from sammobile with CWM Touch 6.0.1.2. I'm unsure about the workings of TWRP because I don't use it. I don't use it because I don't like the buggy keyboard.
Yeah i tried everyway possible. The only way that worked was going uvahl2 thru odin, and then thru stock recovery i applied the ota jb uvdli7 from external sd. It was the only way to get it to work. I think the reason why the error message was coming up was because even though i unrooted my phone, the phone status still said "modified". Once i reflashed hl2 and it didn't say modified it updated the leak.
I think its going to take a video to prove you don't need stock recovery for this operation.
Aerowinder said:
I don't bother with TW custom roms. Not really my thing, but I understand why people might want them.
I flash the OTA updates from the link in my signature (sammobile) in order to pull modems. Although there hasn't been a point lately, because you are working at the speed of light. But I flashed UVALEM, UVALH2, I1, 2, 3, 4, 5, 6, you get the idea.
Are you using TWRP? That recovery might not work with the OTA updates, but I've proven myself, and through many other people, that you can indeed flash OTA leaks from sammobile with CWM Touch 6.0.1.2. I'm unsure about the workings of TWRP because I don't use it. I don't use it because I don't like the buggy keyboard.
Click to expand...
Click to collapse
Lol! Im just usually online when they drop! Theres only been a couple where I wasn't.
If cwm touch recovery does flash these otas as is then it just means they've disabled the check the ota does to verify the system meets the requirements. Or they just disable the recovery check/patch to protect their own recovery. I hope its the latter.
Not saying it cant be done but till now I hadn't heard of it. I use TWRP (just personal preference) but actually never bothered to try with it becsuse too many people early on got errors like the OP when anything wasn't matching stock.
I use Mobile Odin for the otas since it not only allows me to meet the stock requirements but it also injects root so you never have to worry about rerooting or anything.
At this point I just want to know how CWM does the otas. Does it completely disable the system check, or just the recovery part of that check.
Sent from my SGH-T999 using xda app-developers app
The zip file still runs the verification process. I've always done it properly, so I don't know what a flashing failure looks like. I have a background in programming, and I'm an amateur for sure, but I suspect that when the update checks for stock recovery, it thinks CWM is the stock recovery. I'm not sure of the code behind this, but I equate it to user-agents in browsers. CWM is saying it is stock recovery, OTA update accepts that, or some such. Without seeing the code, I can't say for sure, but this is my guess.
You get the option to disable the recovery patch, and to keep root when you attempt to exit recovery after the OTA flash.
I never saw much use for Mobile Odin. I did buy it, because the dev is amazing, but I've never used it. It allows you to flash zip files? I've always just done it through CWM. I flash everything through CWM... even other recoveries.
However it does it, I guess it works. Only reason I wanted to know if it bypassed the entire check is because that could cause problems for the more inexperienced.
Yeah, I love Chainfires work. The ability to flash zips with Mobile Odin was just added a few weeks ago and has worked flawlessly for me.
Sent from my SGH-T999 using xda app-developers app
fix it
you need to flash your kernel to man. most stock kernel wouldnt work with cyanogenmod. Update your kernel with unofficial kernel that are compatible with your device
raaaaarrrr!!!
Has no one figured this out yet...i unrooted my phone using odin mobile ...then attempted to do the 4.3 manual update and im getting the same errors! this is bs...i even tried to use odin to flash mdl and it dint do anything to my phone. very unhappy.
atheistics1 said:
Has no one figured this out yet...i unrooted my phone using odin mobile ...then attempted to do the 4.3 manual update and im getting the same errors! this is bs...i even tried to use odin to flash mdl and it dint do anything to my phone. very unhappy.
Click to expand...
Click to collapse
Well, first, there is not an Odin flashable 4.3 file, but you said you tried to flash MDL? Not sure what this is exactly. The most likely issue is you are using an incompatible recovery. Probably one that is too old.
I think you are totally confused between odin flashable files and recovery flashable files....
Okay so maybe this will help...omni version is jfltecan...which is Canadian and my baseband is l720vpuemja ...that's sprint which my phone is...I'm getting no data...and I'm not able to revert back to 4.3 or 4.2.
Sent from my SGH-I337M using XDA Premium 4 mobile app
you should probably consider asking in your devices forum. if you use anything here youll likely brick.
Sent from my T-Mobile MyTouch 3G Slide(HTC Espresso) using Tapatalk 2
wolverine
themadzionist said:
Trying to install a leak thru stock recovery. Does anyone Known how to get past that issue? Thanks
Jake
Click to expand...
Click to collapse
Just downgrade to 4.0.4 and install cwm then flash it through it. it works for me.
I did a search and couldn't find an answer. I got the OTA (Thanks to my wife, while I still sleeping) I did get it rooted and knox disabled. Don't care about the knox flag because my warranty is already gone. So now my question is do any of the 4.3-4.4 ROMS work (Skynote, Ditto etc)? Can I flash TWRP with goo manager?
Thanks in advance!
Geeve
geeve420 said:
I did a search and couldn't find an answer. I got the OTA (Thanks to my wife, while I still sleeping) I did get it rooted and knox disabled. Don't care about the knox flag because my warranty is already gone. So now my question is do any of the 4.3-4.4 ROMS work (Skynote, Ditto etc)? Can I flash TWRP with goo manager?
Thanks in advance!
Geeve
Click to expand...
Click to collapse
I haven't flashed TWRP thru goo manager but I have thru ODIN. You can get it from here.
http://goo.im/devs/OpenRecovery/t0lteatt
I just got done flashing SKY NOTE 4.3 Edition MJ4-4.3 (AT&T Leak).
I can confirm twrp installs from goomanager as thats how I installed it and successfully flashed an aroma addon (just a mod NOT a rom) with no issues
Did you thank your Developer today?
Thanks to both of you! Getting goo now. Not sure if I am brave enough to flash a ROM yet though till i can see what others have done.
Geeve
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
geeve420 said:
Thanks to both of you! Getting goo now. Not sure if I am brave enough to flash a ROM yet though till i can see what others have done.
Geeve
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
I'm not brave enough yet to rom either but I can confirm Xposed installs perfectly and gearbox works just enough that pie controls work.
If you do that don't turn ANYTHING else in gearbox on. Use Wanam to mod out with as its built for the note 2.
Did you thank your Developer today?
Thanks Jspex! Looking into them now
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
4.3 OTA to custom ROM
geeve420 said:
I did a search and couldn't find an answer. I got the OTA (Thanks to my wife, while I still sleeping) I did get it rooted and knox disabled. Don't care about the knox flag because my warranty is already gone. So now my question is do any of the 4.3-4.4 ROMS work (Skynote, Ditto etc)? Can I flash TWRP with goo manager?
Thanks in advance!
Geeve
Click to expand...
Click to collapse
I decided to be the sacrificial lamb and I can confirm that yes definitively you can go from stock 4.3 OTA to a custom 4.3 ROM. I updated to 4.3 OTA (dumb) and just now successfully flashed Ditto 3.1.1.
1. Root 4.3 OTA
2. Flash TWRP
3. Flash custom rom.
4. Run SuperSU
Some additional notes:
Did a dirty flash the first go around. The device didn't boot. Used the pull battery method to get into recovery (probably not necessary but oh well). Reflashed the rom this time using full wipe in AROMA (not in TWRP) and the device booted like a charm (even got an OTA Ditto 3.2 update bonus!).
Additionally AROMA didn't delete my data so I got to keep all my data from 4.3 OTA.
Last note my baseband is still MK6. I guess that's good because Ditto is still on MK5.
Lots of people have done this. What's so scary?
Sent from my GT-N7105 using XDA Premium 4 mobile app
JediMasterX V2 runs great on 4.3 bootloader. If you took the OTA to get to 4.3 then you are ready to go with JediMasterX just download the zip and follow the instructions in the OP.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
4.3 OTA to custom ROM
joe3681 said:
Lots of people have done this. What's so scary?
Sent from my GT-N7105 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you knew this information already, it would have been helpful of you to share this information with the group instead of chiming in after the fact.
Just read this but a quick read anywhere around here would've been an answer
Sent from my GT-N7105 using XDA Premium 4 mobile app
Thanks everyone!!
Why it was scary is when I posted there was a lot going on. I hadn't seen where someone had taken the update, then flashed a ROM. I had seen a lot about the leak but not MK6. There were quite a few folks having trouble restoring backups, soft bricking etc. and it was due to the locked down boot loader being hostile to changes. I just didn't want a soft brick and have to use my Infuse till I could get it back up.
As far as what I have read so far, no one has been able to get back to MK6 after downgrading or roming and the backups of the stock MK6 aren't working. The reason I asked is because not much was being said about how ROMs were acting with the locked bootloader. No one was talking about steps to take if you have the MK6 update to ROM.
I have since flashed and I am running Sky Note Air Vaniila now and all is well. Just wanted to see what troubles if any others were having to help keep ducks in a row That way when folks want to ROM they know which ones work with the new Bootloader.
Geeve
looking to root, install twrp, and flash cleanrom.
i saw a root method that says to use a stock recovery, and i also saw the i shouldn't wipe the cache using twrp... can anyone give me a proper procedure to get to where i need? i have two little kids that are keeping me from doing the proper research myself, otherwise i would.
i am on mk1 firmware btw...
thanks!
wow, no one?
I haven't done this yet as I am kinda hoping there'll be a non-warranty killing approach available soon. I am in much the same boat as you, kids and all, too.
But I think the way to do it is:
1. Root the device with cf auto root: http://honai-android.blogspot.com.au/2013/12/how-to-root-galaxy-note-101-2014.html / http://forum.xda-developers.com/showthread.php?t=2490805
2. Install TWRP via Odin
3. Install cleanROM via TWRP: http://forum.xda-developers.com/showthread.php?t=2577389
I hope this at least gets you started. Let us know how you go as I will probably be following in your footsteps as soon as I can't stand this unrooted tablet any more... which will probably be very darn soon, warranty killing or not.
Or maybe someone else will chime in with better instructions.
Good luck!
+1 I'm about to send my warranty to hell. Stock ROM is ridiculously over bloated. The only thing i need is a working ROM with my "exotic" p605m variation.
I really need working radio / LTE.
Sent from my SM-P605M using XDA Premium HD app
anthropoidape said:
I haven't done this yet as I am kinda hoping there'll be a non-warranty killing approach available soon. I am in much the same boat as you, kids and all, too.
But I think the way to do it is:
1. Root the device with cf auto root: http://honai-android.blogspot.com.au/2013/12/how-to-root-galaxy-note-101-2014.html / http://forum.xda-developers.com/showthread.php?t=2490805
2. Install TWRP via Odin
3. Install cleanROM via TWRP: http://forum.xda-developers.com/showthread.php?t=2577389
I hope this at least gets you started. Let us know how you go as I will probably be following in your footsteps as soon as I can't stand this unrooted tablet any more... which will probably be very darn soon, warranty killing or not.
Or maybe someone else will chime in with better instructions.
Good luck!
Click to expand...
Click to collapse
Excellent, thanks! If I am gonna use TWRP, do I need to flash the stock recovery? Or can I just use the autoroot and then flash TWRP?
Which note 10.1 do you guys have? Wifi only?
Sent from my SCH-I925 using xda app-developers app
grmcrkrs said:
Which note 10.1 do you guys have? Wifi only?
Sent from my SCH-I925 using xda app-developers app
Click to expand...
Click to collapse
Yeah, I have the SM-P600, which is wifi only. We have a confirmed root, custom recovery, and CleanROM, but the Knox counter gets tripped, and for now there is no way around it.
a.demarco said:
Excellent, thanks! If I am gonna use TWRP, do I need to flash the stock recovery? Or can I just use the autoroot and then flash TWRP?
Click to expand...
Click to collapse
TWRP is custom recovery so yes you have to flash it using Odin.
read here: http://forum.xda-developers.com/showthread.php?t=2515656
After that you can download .zip file to storage and then install it using TWRP recovery.
WeedyEyes said:
TWRP is custom recovery so yes you have to flash it using Odin.
read here: http://forum.xda-developers.com/showthread.php?t=2515656
After that you can download .zip file to storage and then install it using TWRP recovery.
Click to expand...
Click to collapse
Yeah, I know that... My question was do I have to flash the stock recovery after rooting if I am gonna flash TWRP? Or can I just use the autoroot and then flash TWRP.
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