Related
I was once rooted and the problem started then. Now im back to stock with the latest OTA update, but "SuperUser" app still shows up on my phone.
I am having an issue where i cannot use copy/paste
no matter which application i am on , as soon as i choose copy the app crash.
sometimes i receive a testservice stopped working.
There is another thread in the ATT S 3 forum but the only response was to flash another rom.
Any ideas on how I can fix this stock?
Thank You
derryj3 said:
I was once rooted and the problem started then. Now im back to stock with the latest OTA update, but "SuperUser" app still shows up on my phone.
I am having an issue where i cannot use copy/paste
no matter which application i am on , as soon as i choose copy the app crash.
sometimes i receive a testservice stopped working.
There is another thread in the ATT S 3 forum but the only response was to flash another rom.
Any ideas on how I can fix this stock?
Thank You
Click to expand...
Click to collapse
Try a full wipe... Data.. Dalvik... Cache... Reflash or Odin stock and see.
Sent from my SPH-L710 using xda premium
I'm on the Verizon s3 and have the same issue. No luck doing all that for me either. Kind of weird.. just thought I'd chime in.
Sent from Tapatalk 2
mrbracht said:
I'm on the Verizon s3 and have the same issue. No luck doing all that for me either. Kind of weird.. just thought I'd chime in.
Sent from Tapatalk 2
Click to expand...
Click to collapse
same here
shmag18 said:
same here
Click to expand...
Click to collapse
guys try this : http://forum.xda-developers.com/showthread.php?t=1842468
Hello all,
Ok this may seem a bit long, so I apologize in advance. I have been at this for a week and haven't been able to find a fix. I don't use my camera much so I am not sure when the problem started but I was running LiquidSmooth on my s3 and one fine day I get this error when I start the camera app, "Camera Error : Cant connect to camera" . I started restarting, clearing cache, no luck. So I restored stock ROM through Odin, and strangely the error still persists. Only difference is on a stock rom it shows up as "Warning: Camera failed". I searcehd xda and other sites and found other people having similar problems, but there is no guaranteed fix to this.
One possible fix is described here - http://forum.xda-developers.com/showthread.php?t=2006128 . I tried this but when I try to check my firmware version using the dialer code, i get an error " Factory test has stopped"
There are a number of other suggestions that U tried as well, some of them include finding the correct "SLIM_ISP.bin file and placing them on your /root folder, but so far no luck. I also have a spare camera module that I swapped but the damn thing still won't work.
Any suggestions would be greatly appreciated!
Look a few posts down. Might be your bootloader.
There is another thread.. Think in development regarding bootloaders with flashable zip files.
Good luck
Sent from my SGH-I747 using xda premium
I updated my bootloader and modem before the rom. That broke the camera for me. Updating the rom to 4.1.2 fixed it for me. Make sure your bootloader matches your rom.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
waiters said:
Look a few posts down. Might be your bootloader.
There is another thread.. Think in development regarding bootloaders with flashable zip files.
Good luck
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
Well, I just tried doin that, but no luck. I am currently on DLK3 stock rom. and I flashed the odin file from this post. http://forum.xda-developers.com/showpost.php?p=41503727 .. Were you referring to something else?
If you are running a 4.1.1 rom with the mg2 4.1.2 bootloader cam gets borked. There's an app that will tell you what bootloader you have. Vice versa I believe. Running the lk3 4.1.1 bootloaders on a 4.1.2 cam will bork.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
blaker13 said:
If you are running a 4.1.1 rom with the mg2 4.1.2 bootloader cam gets borked. There's an app that will tell you what bootloader you have. Vice versa I believe. Running the lk3 4.1.1 bootloaders on a 4.1.2 cam will bork.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thanks for your reply I flashed the mg2 boot loaderg and modern and changed the Rom to mg2 (4.1.2) but nothing I still get the same error. Any other suggestions would bee greatly appreciated!
avishek_32 said:
Thanks for your reply I flashed the mg2 boot loaderg and modern and changed the Rom to mg2 (4.1.2) but nothing I still get the same error. Any other suggestions would bee greatly appreciated!
Click to expand...
Click to collapse
Flash the new intergalactic rc5 a few pages back from last post and let me know if the cam starts working... Wipe dalvic ect after flash. Also get root checker from market and make sure your on mg2bootloader just to make sure it's not only the mg2 modem
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
blaker13 said:
Flash the new intergalactic rc5 a few pages back from last post and let me know if the cam starts working... Wipe dalvic ect after flash. Also get root checker from market and make sure your on mg2bootloader just to make sure it's not only the mg2 modem
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Tried that , doesnt work, also i verified that the bootloader is mg2. I did a little more digging , if you go to /root/sys/class/camera/rear, you can see the firmware for the rear camera, mine only shows up as (null) (null), no matter which ROM or bootloader I install. The front cam firmware shows up fine. Dont know if that will help you guys identify the problem, just thought I would mention it. Any other suggestions?
Camera not connected
Weird, after having a lot of problems when I flashed the official I9300XXUGMK6 Official Samsung ROM JB 4.3 the phone any more could register to the net, looked and looked every where and many solutions appeared, I was afraid to apply some of them but then hierarchy666 suggested to apply the Ultima v 15 ROM and the patch for that version, did so but selecting the xxemh1 modem and the speedmod kernel , and yes it did work, my phone was alive again , but then I tried to take some photos and my camera presented the Camera not connected error.
So I reinstalled the ROM and patched etc etc etc and still I´m presenting the problem, then I decided to try the same Samsung Kernel included in the Ultima Titan ROM and after rebooting I had camera but no registered to the net, kind of weird and think something is missing or corrupted .
Any idea
Regards
Ultima ROM seems to be great and if it could work 100 % could be the best ROM to try.
Hey Avishek were you able to fix your camera problem... I have the exact same problem as yours and the can rear fw shows null null in my case too...
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
lilpyxie said:
Hey Avishek were you able to fix your camera problem... I have the exact same problem as yours and the can rear fw shows null null in my case too...
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
For all those who are having problems with CM or in my case even Gummy not being able to connect to camera. After scowering for 3 hours the internet I have finally fixed my problem. What I did was to flash CM and Gapps, making sure to wipe cache even before installing Gapps after CM. But this time instead of running camera straight off, I went into the file browser with root access. Navigated to my /system/cameradata folder and immediatlely 777 all the Slims.bin's..My camera now works like a charm! (for now)..
I noticed that when trying to change permissions after running camera for the first time, there were some .bin's that had different permissions than others (on some of them I didn't have to check as many permission options). When I went in before running it, any x or r were completely blocked, so I did my 777 and now all works correctly. I hope this helps anyone having this frustrating problem! I did NOT want to go back to stock rom, copy files, re-flash CM, paste files..or some other fixes that were out there..
Good Luck! (I hope this is in the proper area, I don't usually post in forums so forgive me if it is)..LOVE XDA! Has helped me solve countless problems!
hey guys, having the same issue, so Skype works (front camera) , If I launch straight into it after a boot., can't switch to the back camera
I tried factory reset, then I unlocked the BL and put on CM12 , the camera app would open and just hang there , when try to open again it would have camera cannot connect.
Run hardware info from Play Store, it sees both camera fine, this is just the strangest error...
EDIT:didn't see the post above will try that tonight
Yeahh this is an ongoing issue for both stock Os and asop OS
Not sure why.. sem to he an issue hardware wise
Hey guys,
I have looked around for the solution to this but can't find one.
Starting out rooted, I updated my phone to SkyNote 4.3 (not sure if that helps) and still had root for a minute. I went through the process of setting up the phone how I like it, and after a few restarts, the root went away. This has happened twice. I've read posts where people talked about Android 4.3 deleting root but here's where the story gets interesting:
The threads/posts that people are pointing to to fix it is pretty much centered around Chainfire's post on Google+ https://plus.google.com/+Chainfire/posts/Jkuu84odnx6 .
The difference between the similar posts are that Chainfire has updated the version over the months. I have tried flashing that update zip over and over but I still have no root and the SU app is still buried in my system/app folder, which of course I can't delete because I have no root. I guess my questions are does anyone know how to delete this system/app apk for SU without wiping and starting from another ROM or know how to correct it in general?
Thanks you guys for reading.
Search the skynote thread your answer is there its called 1click
Sent from my SAMSUNG-SGH-I317 using Tapatalk
420techcloud said:
Search the skynote thread your answer is there its called 1click
Sent from my SAMSUNG-SGH-I317 using Tapatalk
Click to expand...
Click to collapse
Thanks, I didn't think about that, but because of my unique situation, I couldn't even get 1click to recognize my phone. So after searching more and more, the answer is exactly what I was doing but a more updated SU zip. It's in the second post of SkyNote 4.3 http://forum.xda-developers.com/showpost.php?p=46798454&postcount=2
That may help another Android 4.3 ROM user
**
I have the exact same issue with my SGH_I317M. I rooted with CF-Root, flashed TWRP, flashed Skynote 4.3, flashed the update, flashed the Rogers modem and flashed the WIFI fix all with ODEN. Everything works. Even WIFI. But I lost Root. I made 2 full backups with TWRP. 1st. right after flashing TWRP still with 4.1.2 ROM and the 2nd after flashing 4.3 and all the patches. When I restore back to 4.1.2 all is good. When I restore to 4.3 Skynote, I loose Root. I tried flashing the SuperUser Update but it fails. Any help would be much appreciated.
Sent from my SAMSUNG-SGH-I317M using xda app-developers app
StevieG_007 said:
I have the exact same issue with my SGH_I317M. I rooted with CF-Root, flashed TWRP, flashed Skynote 4.3, flashed the update, flashed the Rogers modem and flashed the WIFI fix all with ODEN. Everything works. Even WIFI. But I lost Root. I made 2 full backups with TWRP. 1st. right after flashing TWRP still with 4.1.2 ROM and the 2nd after flashing 4.3 and all the patches. When I restore back to 4.1.2 all is good. When I restore to 4.3 Skynote, I loose Root. I tried flashing the SuperUser Update but it fails. Any help would be much appreciated.
Sent from my SAMSUNG-SGH-I317M using xda app-developers app
Click to expand...
Click to collapse
My last comment should help. When you flash the update, make sure it's the one from the post above. It carries the latest SU. If that doesn't work, I'm not sure what to do, but it worked for me because the SU binaries want to update but it needs the correct one.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Thank you Deon. I was reading this thread yesterday using the XDA app on my mobile for the first time. I downloaded the updated binary from this thread using my mobile. After several install failures I opened propertie for the zip and discovered it was empty. I downloaded the update from the OP through my PC, transferred the file to my SD and now all is good again with my root. CHEERS!
Sent from my SAMSUNG-SGH-I317M using xda app-developers app
Is there any chance that flashing the zip on ChainFire's page will brick your phone?
doran10 said:
Is there any chance that flashing the zip on ChainFire's page will brick your phone?
Click to expand...
Click to collapse
It won't brick your phone its pretty hard to trust me lol I used cf auto root tho
Hello and thanks to all those before me who give great advice on troubleshooting....
Here's my situation:
Phone is Rooted.
I downloaded an app a few days ago from the Play Store, so I could move my app installs to the sdcard. When i installed the app it said that there was something wrong " can't remember the exact message " and it needed to fix it. My dumbass allowed it to fix it and here is where my problems began.
Right after that I began receiving a message "Shell has been granted Super User", phone began to run sluggish and the Play Store App would always say it was crashing.
So I figured, screw it I would format and start w/a new ROM anyway.... I did not have any sort of backup (of course dumbass)
However I loaded up the latest version of Odin 3.09 and just incase I installed the root.zip again incase that was destroyed. Then I installed the latest version of OUDHS CWM-Based Recovery 1.0.3.3 ( Previously I had TWRP )
I downloaded a few different roms so I could see what I wanted...However...here's where things get interesting, and I did do some research on it but couldn't find a way to resolve the 1st problem.
When I first started to install a ROM, don't remember which one I was getting a signature verification failed....I had read that it could be 2 things, one the MD5 was bad, I verified that, so that wasn't the issue. Then I came across that it may have been a ROM that my device(Samsung) somehow knew wasn't approved, therefore prevented it from being installed....OK fine...
Next I found a ROM that was going to work via installing...So i picked the CM10.2 and wiped/format/davik/cache...etc... Installation took a few mins...Then when I rebooted, it's been on the Cyangenmod screen for 45 mins +....
Is there anyway I can do some verification that something further isn't interfering w/my installs?
Thanks in advance and any guidance is GREATLY appreciated...
Regards
Erik
Odin to stock and try that, always the best choice
Sent from my SGH-M919 using xda app-developers app
aamir123 said:
Odin to stock and try that, always the best choice
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Actually I tried that and I used this one from stockroms.net TMB-M919UVUAMDL-1366964131.zip
the verification failed immediately, however, when I checked it w/the MD5 hash on my computer it checks out...That's where I'm wondering if there is something else going on...
Or are you talking about something else regarding stock? If so could you clarify...Thanks
Use sam mobile.com
And flash the mdl fw from there. Also you may have to unzip the original file to get a tar file
Sent from my SGH-M919 using xda app-developers app
aamir123 said:
Use sam mobile.com
And flash the mdl fw from there. Also you may have to unzip the original file to get a tar file
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Just wanted to say thank you for your help. Both the flashing the recovery back to default and the default ROM worked. Now in the future no more clicking yes when I don't have a backup
Have a great weekend!!
oregongreen said:
Just wanted to say thank you for your help. Both the flashing the recovery back to default and the default ROM worked. Now in the future no more clicking yes when I don't have a backup
Have a great weekend!!
Click to expand...
Click to collapse
glad it worked out for you, I know it can be scary to think you screwed up your phone.
Glad you solved it, ALWAYS MAKE A BACKUP
Sent from my customizable brickable device
mrhughy said:
Glad you solved it, ALWAYS MAKE A BACKUP
Sent from my customizable brickable device
Click to expand...
Click to collapse
This can nvr be said enough.
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