I'm sure this has been answered a million times an i apologize, I've search high an low for the last 6 hours an cant find a working solution. I've installed the Liquid Smooth 4.4.4 3.2 rom an all is well except the camera wont work. When i try to use the camera i get the "can't connect to camera" error, Any help would be great thanks,
.......
so this is the Q&A section right? Am i the only one getting this error? Am i doing something wrong? Were all here for the same purpose, to have some bad a** devices... ANY help would be great thanks
ice711 said:
so this is the Q&A section right? Am i the only one getting this error? Am i doing something wrong? Were all here for the same purpose, to have some bad a** devices... ANY help would be great thanks
Click to expand...
Click to collapse
Have you tried installing a different rom and or a stock rom to see if the problem persists?
Sent from my SPH-L710 using Tapatalk
beezie42 said:
Have you tried installing a different rom and or a stock rom to see if the problem persists?
Sent from my SPH-L710 using Tapatalk
Click to expand...
Click to collapse
I flashed just about every rom under the original android development section, all still with the same camera error. After no luck i decided to odin back to stock, an the camera now works. I've searched high an low an tried all the cm/aosp camera fix's i could find an no luck
ice711 said:
I flashed just about every rom under the original android development section, all still with the same camera error. After no luck i decided to odin back to stock, an the camera now works. I've searched high an low an tried all the cm/aosp camera fix's i could find an no luck
Click to expand...
Click to collapse
Interesting. Very weird it works on stock but not on aosp. Now that you have odined back to stock have you tried to re flash a aosp rom and check the camera? What stock rom are you odin-ing?
Are you also flashing any other mods or custom kernels?
I would try cm11 with just gapps installed and see what happens.
I doubt it's a hardware issue if it works on stock. Do you use any third party camera apps?
Sorry for lots of questions just trying to narrow down the problem.
Sent from my SPH-L710 using Tapatalk
beezie42 said:
Interesting. Very weird it works on stock but not on aosp. Now that you have odined back to stock have you tried to re flash a aosp rom and check the camera? What stock rom are you odin-ing?
Are you also flashing any other mods or custom kernels?
I would try cm11 with just gapps installed and see what happens.
I doubt it's a hardware issue if it works on stock. Do you use any third party camera apps?
Sorry for lots of questions just trying to narrow down the problem.
Sent from my SPH-L710 using Tapatalk
Click to expand...
Click to collapse
No noo bye all means ask away. I odin to the stock 4.4.2 ND8 tar. After i flashed each rom an gapps an the phone booted up i skipped the normal setup, gmail an such, an tried the camera an it was a no go. So no im not usein any third party cameras. The only rom i didnt flash was the cm11. I came from a nexus 4 an loved the liquidsmooth roms so that was my first choice. I have not re rooted an flashed a recovery as i was pretty madd it didnt work the first time around. I really appreciate ur help. Im open for suggestions
ice711 said:
No noo bye all means ask away. I odin to the stock 4.4.2 ND8 tar. After i flashed each rom an gapps an the phone booted up i skipped the normal setup, gmail an such, an tried the camera an it was a no go. So no im not usein any third party cameras. The only rom i didnt flash was the cm11. I came from a nexus 4 an loved the liquidsmooth roms so that was my first choice. I have not re rooted an flashed a recovery as i was pretty madd it didnt work the first time around. I really appreciate ur help. Im open for suggestions
Click to expand...
Click to collapse
well if you want to have custom stuff just flash Wicked X 8.0 rom just the Bare Bones version....its pretty sweet
6th_Hokage said:
well if you want to have custom stuff just flash Wicked X 8.0 rom just the Bare Bones version....its pretty sweet
Click to expand...
Click to collapse
Ill be sure an try it out. One question for ya.. can u tell me the best method of rooting the S3? I used the android tool kit.. i was thinkng mayb thats the reason for the camera issue. I was considering useing towelroot then flashing TWRP recovery then flashing a rom.. ur opinion?
ice711 said:
Ill be sure an try it out. One question for ya.. can u tell me the best method of rooting the S3? I used the android tool kit.. i was thinking maybe that's the reason for the camera issue. I was considering using TowelRoot then flashing TWRP recovery then flashing a rom.. your opinion?
Click to expand...
Click to collapse
well there's the TowelRoot option that would require you to download SuperSU and BusyBox from the playstore then there's using Odin to flash any Custom Recover for the D2lte then in that recovery flashing Chainfire's SuperSU zip....then the most recommended is using Odin to flash the latest Philz Recovery for the D2lte which has an option to root the current rom that your on, under Philz settings
6th_Hokage said:
well there's the TowelRoot option that would require you to download SuperSU and BusyBox from the playstore then there's using Odin to flash any Custom Recover for the D2lte then in that recovery flashing Chainfire's SuperSU zip....then the most recommended is using Odin to flash the latest Philz Recovery for the D2lte which has an option to root the current rom that your on, under Philz settings
Click to expand...
Click to collapse
Ive never used Philz Recovery.. is it the same idea as TWRP an Clockwork recoveries? Thanks for ur help i appreciate it
ice711 said:
Ive never used Philz Recovery.. is it the same idea as TWRP an Clockwork recoveries? Thanks for your help i appreciate it
Click to expand...
Click to collapse
well it's a touch based Clockwork mod recovery and you can change the colors of all the letters that are visible and there's more options in there to do cool stuff and 2 different factory resets
beezie42 said:
Interesting. Very weird it works on stock but not on aosp. Now that you have odined back to stock have you tried to re flash a aosp rom and check the camera? What stock rom are you odin-ing?
Are you also flashing any other mods or custom kernels?
I would try cm11 with just gapps installed and see what happens.
I doubt it's a hardware issue if it works on stock. Do you use any third party camera apps?
Sorry for lots of questions just trying to narrow down the problem.
Sent from my SPH-L710 using Tapatalk
Click to expand...
Click to collapse
So i tried cm11 an still no go with the camera. I tried TWRP, Clockworkmod, an PhilZ recovery when flashing the rom an still no luck... Any ideas?
ice711 said:
So i tried cm11 an still no go with the camera. I tried TWRP, Clockworkmod, an Philz recovery when flashing the rom an still no luck... Any ideas?
Click to expand...
Click to collapse
did you check if the MD5 sum matched? the numbers on the download page and the numbers shown on Philz right before you flash anything...
6th_Hokage said:
did you check if the MD5 sum matched? the numbers on the download page and the numbers shown on Philz right before you flash anything...
Click to expand...
Click to collapse
yes an all matches up. Im starting to think its my device. i was sent a refurb from sprint an im wondering if the previous owner messed with it...
so i gave wicked x a shot an its way kool and the camera works. still clueless as to why aosp roms camera wont work. Let the fun begin lol. thanks for the help guys i appreciate it
I got the same problem with my GS3. Tried several different roms and different builds of those roms that people reported having no problems with and still no fix.
Going to try Wicked X see what happens.
Ive been flashin roms for about 4years. I love aosp but then i had to try wicked X. Its absolutley amazeing. Ive had no reboots, no freezin, awesome battery life, and best of all... EVERY feature on the rom an of the phone works flawless!!! Try it ull be amazed lol
camera works fine on Wicked x. Don't like the rom though. So I'm switching back to 2.37 LS it worked fine on my previous device
I used LS 3.2 on my previous phone, galaxy nexus 4. For some reason i cant get the camera to work on my s3 on LS
ice711 said:
Ive been flashin roms for about 4years. I love aosp but then i had to try wicked X. Its absolutley amazeing. Ive had no reboots, no freezin, awesome battery life, and best of all... EVERY feature on the rom an of the phone works flawless!!! Try it ull be amazed lol
Click to expand...
Click to collapse
Same here, I never ran stock rom on the phone. First thing I did was to root and flash the room.
I'm so use to LS since I ran it pretty much entire time for past 2 years. Very disappointed with camera issues in v3.0. Hope they get it taken care of soon.
Related
I am sorry if this has been discussed before, and I do remember reading about it somewhere here on XDA, but it seems my entire file system is messed up. I was on Omega 10 before, then went to CM10.1 and back to Omega. Now, it seems I have a folder 0 inside my SD card which has duplicate folders as the ones in the SDCard folder itself.
I would think the only way to fix this would be a complete wipe of the system and reflashing a ROM? Is yes, then how do I go about doing it? Is there any other way? I am really getting frustrated with this
TIA
Back up, format the internal SD through twrp then install the omega ROM again.
Sent from the Rabbit Hole
Thanks for the help. Can it be done through CWM?
Oh, and would I need an external SD card too?
Alright, for those interested, heres what I did
1. Flashed TWRP through ODIN
2. Formatted Internal SD
3. Flashed Stock firmware through ODIN
4. Rerooted and all that good stuff from toolkit (thanks MSkip)
5. Finally flashed Omega v10
Woooo.. I think I am done with flashing for a few days now :silly:
anirudh412 said:
Alright, for those interested, heres what I did
1. Flashed TWRP through ODIN
2. Formatted Internal SD
3. Flashed Stock firmware through ODIN
4. Rerooted and all that good stuff from toolkit (thanks MSkip)
5. Finally flashed Omega v10
Woooo.. I think I am done with flashing for a few days now :silly:
Click to expand...
Click to collapse
Here is a way to do this with CWM my friend... Check my thread here... http://forum.xda-developers.com/showthread.php?t=2092485 and remember... Search is your friend...
yiannisthegreek said:
Here is a way to do this with CWM my friend... Check my thread here... http://forum.xda-developers.com/showthread.php?t=2092485 and remember... Search is your friend...
Click to expand...
Click to collapse
As I VERY CLEARLY mentioned in my first post, I did remember reading about it on XDA some days ago, but wasnt able to find it. I am not new to XDA you know But thanks for pointing out the thread. Bookmarking it for now, even though I think I am done with AOSP ROMS on the Note 2. Just dont see the point what with all the added features on Sammy based ROMS.
anirudh412 said:
As I VERY CLEARLY mentioned in my first post, I did remember reading about it on XDA some days ago, but wasnt able to find it. I am not new to XDA you know But thanks for pointing out the thread. Bookmarking it for now, even though I think I am done with AOSP ROMS on the Note 2. Just dont see the point what with all the added features on Sammy based ROMS.
Click to expand...
Click to collapse
Yea I was in the same boat too...on the S3 the aosp ROMs seemed good because you didn't have to worry about the spen features and such plus it suited the screen size. However after trying aosp on the note 2 it just made the phone less than what its meant to be. So I went back to using custom stock ROMs. so far omega is the way.
Sent from the Rabbit Hole
bushako said:
Yea I was in the same boat too...on the S3 the aosp ROMs seemed good because you didn't have to worry about the spen features and such plus it suited the screen size. However after trying aosp on the note 2 it just made the phone less than what its meant to be. So I went back to using custom stock ROMs. so far omega is the way.
Sent from the Rabbit Hole
Click to expand...
Click to collapse
Or something like the RR Pitch Black Edition
http://forum.xda-developers.com/showthread.php?t=2005675
The concept is perfect. An AOSP themed Sammy custom ROM. Gonna try it out and see how it performs.
Would I be able to do this if I am stuck at boot screen? I'm at work at the moment so will have to try when I finish. I can still get to download mode or recovery mode but after boot it just hangs at the loading screen. Initially had cf auto root and a version of aroma on N7105T
dalemissen said:
Would I be able to do this if I am stuck at boot screen? I'm at work at the moment so will have to try when I finish. I can still get to download mode or recovery mode but after boot it just hangs at the loading screen. Initially had cf auto root and a version of aroma on N7105T
Click to expand...
Click to collapse
Do what?
I just got this new SG3 and was using Rootbox on my last one which I really liked. I noticed they use TWRP in their update options so I figured I would try with this new g3. First time trying TWRP downloaded the latest from their blog openrecovery-twrp-2.4.3.0-d2att.tar. I really like the looks & feel but am having nothing but trouble with flashing roms. Can some one tell me why I should not go back to CWM?
lectron8 said:
I just got this new SG3 and was using Rootbox on my last one which I really liked. I noticed they use TWRP in their update options so I figured I would try with this new g3. First time trying TWRP downloaded the latest from their blog openrecovery-twrp-2.4.3.0-d2att.tar. I really like the looks & feel but am having nothing but trouble with flashing roms. Can some one tell me why I should not go back to CWM?
Click to expand...
Click to collapse
OK so I went back to CWM flashed task650 AOKP, and gapps, not one problem, smooth as can be and now running new rom. Thanks CWM
lectron8 said:
I just got this new SG3 and was using Rootbox on my last one which I really liked. I noticed they use TWRP in their update options so I figured I would try with this new g3. First time trying TWRP downloaded the latest from their blog openrecovery-twrp-2.4.3.0-d2att.tar. I really like the looks & feel but am having nothing but trouble with flashing roms. Can some one tell me why I should not go back to CWM?
Click to expand...
Click to collapse
Umm what kinda problems did you encounter trying to flash anyway?
Sent from my SAMSUNG-SGH-I747 using xda premium
Not sure why your having issues with it. No problems here with TWRP
Wayne Tech S-III
zelendel said:
Not sure why your having issues with it. No problems here with TWRP
Wayne Tech S-III
Click to expand...
Click to collapse
+1 always used TWRP.. Like always
Sent from my SAMSUNG-SGH-I747 using xda premium
Probably me
metalhead2791 said:
Umm what kinda problems did you encounter trying to flash anyway?
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Its probably me but I just couldn't get it to work. I tried to flash from goomanager the right rom & gapps and I also tried from recovery. I didn't think it worked, I didn't see any confirmation of install, so I got scared and restored.
I have since done it with CWM and am ok. Thanks for the response anyway.
How did you end up flashing CWM back over TWRP? I too am having issue and would like to flash back CWM, but can't find a way how to. No flashable .tar file as far as I can find, and ROM manager doesn't list me the option to flash CWM.
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.
Hello all,
I just have a few questions regarding my note 2 sgh-i317 which I've just received from ebay on Thursday. As soon as I got it I rooted and flashed cymod 10.2 because up until this point I didn't want anything stock on my previous galaxies. Before I flashed though, I messed around with s-note and was highly dismayed that I'm not able to mount touchwiz apps. I tried changing apk permissions through es and move to system/app folder to no avail. Then I thought I would settle for Papyrus since thats what my wife has on her rooted/omni rommed note 10.1. I'm not happy with that app or the fact that there is not a 4.4.2 update for the note 2s yet. I'm thinking the only way to get s pen features to work with the good apps it was designed to work with, is to go back to stock.Any input or suggestions would be greatly appreciated as well as the thread link for the stable 4.3 stock rom download as TWRP didn't back it up right before flashing.
Thanks in advance
omen
Galaxy Note II-sgh-i317 Root/CyMod 10.2
Galaxy SIII-sgh-i747 Root/CyMod 10.3
iPhone 4S......wait no I did not just go there:silly:
I was on an aosp and flashed 4.3 alliancerom. Like it a lot. Because of the whole bootloader thing with 4.3 and that I didn't update mine my wifi didnt work as I was told it wouldn't. So I heard somewhere to flash a kernel called devil kernel and it made everything work like a charm not to mention the kernel is awesome. It has a app in the playstore to manage it. It also works on both touch wiz and aosp. The best thing is it also allows for dual boot between aosp and touchwiz. I have a backup that I access from cwm. I go back and forth between CyanogenMod and touchwiz all the time.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Jsouthernindiana said:
I was on an aosp and flashed 4.3 alliancerom. Like it a lot. Because of the whole bootloader thing with 4.3 and that I didn't update mine my wifi didnt work as I was told it wouldn't. So I heard somewhere to flash a kernel called devil kernel and it made everything work like a charm not to mention the kernel is awesome. It has a app in the playstore to manage it. It also works on both touch wiz and aosp. The best thing is it also allows for dual boot between aosp and touchwiz. I have a backup that I access from cwm. I go back and forth between CyanogenMod and touchwiz all the time.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
I can't get any other kernels too flash until I unlock the bootloader though right? Mine had the OTA and I'm still on the MK6 baseband. I found 2 UCUBMK6 Param tar files which are supposed to work but I'm still seeing and unchanged flash count and knox trip displayed while in download mode. I really want to go to alliance and just am not sure what my next step should be. Thanks for your previous input and devil kernel does sound sweet...hopefully I'll get to enjoy it soon:fingers-crossed::fingers-crossed:
omenbass said:
I can't get any other kernels too flash until I unlock the bootloader though right? Mine had the OTA and I'm still on the MK6 baseband. I found 2 UCUBMK6 Param tar files which are supposed to work but I'm still seeing and unchanged flash count and knox trip displayed while in download mode. I really want to go to alliance and just am not sure what my next step should be. Thanks for your previous input and devil kernel does sound sweet...hopefully I'll get to enjoy it soon:fingers-crossed::fingers-crossed:
Click to expand...
Click to collapse
Negatory. Flashing kernel and Alliance will work.
You're stuck on the MK6 bootloader, which is fine. DO NOT try to flash a bootloader !
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