Related
To start I am a newb
I Have a galaxy nexus with the 4.1 Jelly Beans ( not stock, installed via ROM from here xda). That's fine. This week a new "system" update was available for my phone. So I downloaded it and the phone reboot, when the phone starts it goes to the cwm recovery screen saying the update failed. I would like to have some HELP, I found other threads, but I really don't want to do anything worng.
My questions:
How can i get the updates to work again?
DO i need to get ICS back to update the phone?
How should i do it?
Can I do that without losing my data ( would be great, but i am ok if there is no way)
I am just afraid if i go back to ICS, and the update don't show up.
Jpcsilva said:
To start I am a newb
I Have a galaxy nexus with the 4.1 Jelly Beans ( not stock, installed via ROM from here xda). That's fine. This week a new "system" update was available for my phone. So I downloaded it and the phone reboot, when the phone starts it goes to the cwm recovery screen saying the update failed. I would like to have some HELP, I found other threads, but I really don't want to do anything worng.
My questions:
How can i get the updates to work again?
DO i need to get ICS back to update the phone?
How should i do it?
Can I do that without losing my data ( would be great, but i am ok if there is no way)
I am just afraid if i go back to ICS, and the update don't show up.
Click to expand...
Click to collapse
Flash your phone back to stock... then do the ota update... profit...
Sent from my Galaxy Nexus using xda app-developers app
Everything must must be bone stock to install an ota.
Jellin' like a felon
The issue at hand here is that you have a custom recovery. I can't say that if you remove CWM that you'll be able to OTA update, but that's at least what was the problem there. Now, if you want to keep all your apps and update to the OTA jelly bean instead of the Google I/O preview build, you can flash this here: http://forum.xda-developers.com/showthread.php?t=1737849
Follow the instructions on that post to update. This is what I did and it worked perfectly.
Camera not working after JB update!
Hi! I recently installed JB on my Dad's Galaxy Nexus, whilst everything seems to work fine, I've noticed that the camera has stopped working. The screen goes blank if i access the camera. I've tried installing 3rd party applications for camera, but none of them work! Please help me! Is it a hardware or a software fault?
nishantbhatia84 said:
Hi! I recently installed JB on my Dad's Galaxy Nexus, whilst everything seems to work fine, I've noticed that the camera has stopped working. The screen goes blank if i access the camera. I've tried installing 3rd party applications for camera, but none of them work! Please help me! Is it a hardware or a software fault?
Click to expand...
Click to collapse
What Rom? Custom or stock
What kernel? Custom or stock
Sent from my Galaxy Nexus using Tapatalk 2
And how do i do that? I really dont know how to flash it
Sent from my Galaxy Nexus using xda app-developers app
Stock JB Rom & stock kernel!
I'm gonna go back to ICS and check if that resolves the issue! What say?
Sent from my Galaxy Nexus using xda premium
nishantbhatia84 said:
Stock JB Rom & stock kernel!
I'm gonna go back to ICS and check if that resolves the issue! What say?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
first try factory reset, otherwise yes go back to stock ics and check.
Jp182
atifsh said:
first try factory reset, otherwise yes go back to stock ics and check.
Click to expand...
Click to collapse
But going to factory reset will not remove the cwm recovery... right? If i go to factory data reset on my phone ( remember i am using a 4.1 rom) will it go back to ics and delete all roms / root? Cause this sounds like the best way to do it, but you were the first one that said that. Bought my phone from Amazon unlocked ( do you guys think it is gonna update?)
I did that, no help! I think it's a hardware fault. Thanks anyway!
Sent from my Galaxy Nexus using xda premium
I don't get it. What did you do? Factory reset? Installed the stock?
Sent from my Galaxy Nexus using xda app-developers app
HELPPPPPP
nishantbhatia84 said:
I did that, no help! I think it's a hardware fault. Thanks anyway!
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
PLZ, tell me!! If I do the factory reset is it gonna remove CWM, and all stuff i have installed?
You said you downloaded your ROM from here, but you didn't say which one. There was at least one (Koush's) that was an image of the stock ROM, taken from the OTA update that went out to the phones given out at Google I/O. If you have that ROM (and the corresponding radio), you can just use CWM to install the OTA update. I know this works because I did it myself.
If you really have one of the custom ROMs, your only choice is to return to stock if you want the official OTA. And yes, this will remove CWM and wipe your entire phone (including anything in /sdcard)... so backup anything you want to keep before you try this. See efrant's excellent guide here: http://forum.xda-developers.com/showthread.php?t=1626895
ok
phazerorg said:
You said you downloaded your ROM from here, but you didn't say which one. There was at least one (Koush's) that was an image of the stock ROM, taken from the OTA update that went out to the phones given out at Google I/O. If you have that ROM (and the corresponding radio), you can just use CWM to install the OTA update. I know this works because I did it myself.
If you really have one of the custom ROMs, your only choice is to return to stock if you want the official OTA. And yes, this will remove CWM and wipe your entire phone (including anything in /sdcard)... so backup anything you want to keep before you try this. See efrant's excellent guide here: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
Sorry man, I know i am not giving a lot of information, but that's cause i really don't know. I did a random "how to update your galaxy nexus to 4.1" tutorial, and i don't even remember where...... I just know the links i download were from here.
So what i am going to do:
1: Factory data reset
2: I think it's going back to ICS
3: Just do the normal system update that should just pop up.
My only fear is if the phone does not ask for update.
If you restore to stock using efrant's guide, it will be ICS since Google has not yet posted Jelly Bean firmware images. If you don't get the OTA notification or don't want to wait for it, you can just download and apply it manually (see here: http://forum.xda-developers.com/showthread.php?t=1419170)
Factory reset factory reset
phazerorg said:
If you restore to stock using efrant's guide, it will be ICS since Google has not yet posted Jelly Bean firmware images. If you don't get the OTA notification or don't want to wait for it, you can just download and apply it manually (see here: http://forum.xda-developers.com/showthread.php?t=1419170)
Click to expand...
Click to collapse
I want to restore it VIA FACTORY RESET. Cant i?
Jpcsilva said:
I want to restore it VIA FACTORY RESET. Cant i?
Click to expand...
Click to collapse
No, that will just wipe data. You'll have a clean phone, but with the same ROM you currently have. The phone doesn't keep a copy of the stock firmware hidden away or anything like that. Efrant's guide is the proper way to restore everything back to stock.
So, a while back, i decided to convert my ATT galaxy s3 to a tmobile build so i could run LTE from tmobile on it. Now, my problem is, i want to revert back to full att again, in which i have tried, but im getting something wrong (Status 7 errors and what not, i feel related to the changeover) and i don't want to brick my phone trying over and over. I could use some help with what ill need to FULLY get back to at least stock so i can root and install a fresh kitkat rom. Any help is appreciated!
I attached a screen of my build as well.
How exactly did you go about this? What were the zips you used to do this? What zips are you trying to flash? These are all things that can help us out in figuring out what went wrong.
Well i had read around of a test rom created especially for tmobiles GS3 variant that ran on att in order to run their LTE. So i flashed that rom and i believe custom kernels and a modem. Only thing is i cant backtrack what i did and the original files i used are lost.
Anybody? Hehe I really need to get to a computer soon ..
That's an easy fix.
Odin back to a stock 4.1.x, rooted or unrooted.
Then on first boot hold volume up + home button and to a factory reset. Done.
PS: make sure you're not running 4.3 OTA latest bootloader or you will get a semi reversible brick.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Ok awesome! Ill look up the odin stock guide on here....but you daid it jad tp be 4.1.x right? And what about updating it later on?
Also, as another option, what would I be able to flash it to to keep it in its current tmobile state but updated to a shiny new rom.
Your cwm is out of date.
Update your recovery at that error will go away when flashing
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
So ive succesfully fladhed back to stock att 4.1.1 and rooted it. Flashed in CWM Touch too. Now Im trying to update to a custom rom and its telling me that my device is a d2vzw in the recovery log then status 7. Any takes on that? Heres a screen.
Alright! All is well as I've finally gotten it flashed to gummy 4.4. Its running so smooth...thank you guys for the help!
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
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
hi guys i just joined this, my sph-l900 is stuck on boot loop it says no os and every time i try to install any recovery roms (ive tried so many) it always fails in odin. it says wrong majic string. i cant install any roms i just want to go back to stock. i accidentally installed the dn3 thats meant for a n7100 and ever since that i havent been able to get it back to any stock roms. anyone please help as i dont have another phone and i need it for work. thanks
Have you tried this?:
http://forum.xda-developers.com/showthread.php?t=2086769
[ROM][RESTORE][5-12-13]Back to UNROOTED Stock with Auto Flash Count Reset
Sent from a Sprint Note 2 GSM unlocked
I'm assuming you have upgraded to some other model kitkat rom and want to revert back to sprint rom. I had the same problem yesterday it turns out knox on those kitkat roms forbids you from going back to lower version rom. What I did was to odin ne2 rom and it went smoothly.
jocarog said:
Have you tried this?:
http://forum.xda-developers.com/showthread.php?t=2086769
[ROM][RESTORE][5-12-13]Back to UNROOTED Stock with Auto Flash Count Reset
Sent from a Sprint Note 2 GSM unlocked
Click to expand...
Click to collapse
If you use the link above do not take any updates or you will soft brick your device.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Hi All,
I purchased my Note 4 from Swappa, it already came in with Knox 0x1 (4) but it was restored back to stock everything. I recently upgraded to 5.1.1 (via Official OTA) and Sprint has turned my phone into an Ad Beacon. I get all sorts of stuff get installed from Sprint Zone to Avatars for Voicemail and a ton of apps that I need out of my phone.
I decided to try the CF-Auto-Root method. This worked for me in the past with my Note II. Well, I was not so lucky this time. I booted to Download Mode, ran Odin, and PDA installed the autoroot TAR.
I got the red pirate droid screen, and then the phone rebooted. Since then it's been stuck in a reboot loop over and over.
Is my phone bricked? I realize I made a very dumb mistake by doing this now. Because I need my phone the next 2 days and I might have to call Sprint and have them re-activate one of my dumb phones if I can't figure this out.
Question is, is the phone done for? Or is there a way I can bring it back from the dead? I am currently download what I think is the stock FW for the Note 4 (5.1.1) from Sammobile. Its going at 200kb/s so It won't finish for another 2 hours. Only problem is. I have no idea what to do with this file once I get it.
If someone here can please point me in the right direction. I'd greatly appreciate it.
CF autoroot does not work on 5.1.1....odin stock sprint rom and then flash a custom rom with root baked in the rom...recommend Sprint HybridX ver3 as it has anything you could want in a rom and is very stable...you'll need to install custom recovery such as TWRP to flash the custom rom
Sent from my SM-N910P using Tapatalk
gdempsey1 said:
CF autoroot does not work on 5.1.1....odin stock sprint rom and then flash a custom rom with root baked in the rom...recommend Sprint HybridX ver3 as it has anything you could want in a rom and is very stable...you'll need to install custom recovery such as TWRP to flash the custom rom
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thanks for the response. I'm currently flashing using:
ALL_SPT_N910PVPU4COG5_N910PSPT4COG5_CL5303209_QB5691107_REV00_user_low_ship_MULTI_CERT.tar.md5.zip
It's doing it's thing at the moment.
I tried flashing TWRP earlier, but had no luck. Could you please point me at any resource that can help me get that? Assuming this stock I'm using will work.
EDIT: It finished, rebooted. Now stuck at the Sprint Spark screen for about 5 minutes now.
EDIT2: It's preparing device for first time use. Looks like the stock made it through.
Just need to know how to flash TWRP at this moment and if you can kindly point me to that HybridX ROM I'd be grateful!
Go to XDA developer (install app from playstore) and the go to sprint samsung galaxy note4 forum under android development and find sprint hybrid x rom thread...at the beginning of thread are all the file downloads you'll need and instructions to install....when you're done give @tx (the developer) a thank you...he's an awesome developer and creates the best roms out there for our devices.
Sent from my SM-N910P using Tapatalk
Thanks for the headsup. I managed to get TWRP working and I booted to it.
I'm just confused regarding Deodexed vs Nondeodexed roms. What's the difference? That's my last obstacle in my way.
Again, I appreciate your help.
Odexed is for performance and deodexed is for mods...deodexed alittle slower but highly customizable (themes..5way boot...etc.)...odexed is fast but can't customize.
Sent from my SM-N910P using Tapatalk
gdempsey1 said:
Odexed is for performance and deodexed is for mods...deodexed alittle slower but highly customizable (themes..5way boot...etc.)...odexed is fast but can't customize.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
So unfortunately I rebooted from TWRP after testing that it works and I'm back to the boot loop.. I get the Sprint logo and it keeps rebooting....
When I was in TWRP, before I rebooted it asked it I wanted to installed SuperSU and I agreed. Could that have done it?
Does that mean I need to reflash again?
Possibly incompatible...you flashed a stock rom and tried to add SU without root....reflash stock...and then flash the Hybrid X rom if you want root and SU as they are baked into the rom so when you reboot you'll have everything you need...no need to add anything else.
Sent from my SM-N910P using Tapatalk
---------- Post added at 08:38 PM ---------- Previous post was at 08:32 PM ----------
After you install xda read some of the threads....you'll learn alot on the peculiarities of the new 5.1.1 update and OG5 problems and workarounds....much info in these threads...especially Hybrid X threads
gdempsey1 said:
After you install xda read some of the threads....you'll learn alot on the peculiarities of the new 5.1.1 update and OG5 problems and workarounds....much info in these threads...especially Hybrid X threads
Click to expand...
Click to collapse
Looks like I managed to boot into HybridX finally. My only worry at this point is it looks like I lost LTE. I only see 3G connection now.
I'm guess that's what you're referring to with OG5 problems?
EDIT: I can't really tell at this point. Whenever I reboot. I see the LTE logo. I ran the browser real quick managed to load a page fast. But lost the signal and went back to 3G. I'll have to give this a full day of testing before I judge it.
That being said, I got rid of all the Sprint junk and I think the phone runs a bit faster. So thank you for all your help!
You're welcome...and the lte/3g will switch back and forth depending on the available signals inorder to maintain the most stable data connection for your location....not to worry....you probably won't even notice the difference other than the icons
Sent from my SM-N910P using Tapatalk
---------- Post added at 10:21 PM ---------- Previous post was at 10:12 PM ----------
You're gonna love the battery usage...and all the bells and whistles like audio mods that @tx baked into the rom
Sent from my SM-N910P using Tapatalk
I had this same thing happen to me. My phone is stuck in a boot loop. Where do I get the file I need to flash to restore everything back to normal? I'm inexperienced in rooting so any help would be appreciated.
frenchiethefry94 said:
I had this same thing happen to me. My phone is stuck in a boot loop. Where do I get the file I need to flash to restore everything back to normal? I'm inexperienced in rooting so any help would be appreciated.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=62241991&postcount=56
You'll need Beastmode kernel and SuperSU zip links from that post. There's also notes that will help if you continue to experience boot loops.
Sent from my SM-N910P using Tapatalk
Hey guys I'm in the same boat using 910W8 Telus reboot loop. What do I need to do to unbrick this note 4 fairly new to this and bit off way more than I could chew lol please helppp
Easy Root for SM-G900T1 klte (Any Device) Lollipop 5.0-5.1.1 or CFAutoRoot btloop fix
Will work on any device. So I was having the same issue and had actually just wasted 2 whole days trying to root my S5 with the 5.1.1 and couldnt seem to find a working download link for the 4.4.2 Gingerbread so being the stubborn ass I am when it comes to hacking and finding faster alt. solutions by like editing script or binary persay. So out of irritation and many times flashing back to my previous firmware lol I had a crazy idea. I used the CF Auto Root and sure enough bootloop, but....then I thought well I need the TWRP recovery if I wanna try and maybe manually update or swap the boot.img or security protocol somehow so I flashed TWRP recovery and all I had to do to end the bootloop was install update from ext sdcard<SuperSU v1.65 update which it just so happens I coincidentally copied and pasted onto my sd card (via sd card adapter in laptop or the mass storage mode when hooked to usb) and boom it booted up and started perfect as if I didnt even have Lollipop 5.1.1 lol made my night/morning at 6 am previously frustrated and about to give up. So to sum it up....
1. Download/Install: Odin v3.10.6
2. Download/OdinFlash: CF Auto Root
3. Download/OdinFlash: openrecovery-twrp-2.7.0.0-klte
4. Download: SuperSU-v1.65-update
5. Recovery Reboot
6. Install Update: SuperSU-v1.65-update
slide to flash it, wipe Dalvik cache, reboot normally and wahlah you've now rooted you Galaxy S5 klte on Lollipop 5.1.1 and up (when they update the klte this method should still work guaranteed due to the fact its more of a technical loophole in the firmware than the exploit package itself)