[Q] stuck at teamwin screen? - Verizon Samsung Galaxy Note II

I have a Verizon Note 2 running AllianceRom build 24. I was going to flash build 25 today and I've run into a wall.
AllianceRom has a little script thing to reboot to recovery and I was in there anyway so I just rebooted from there. I'm now stuck at the initial teamwin screen. I can't boot normally, I just keep running into the teamwin screen, and it won't progress to the point that I can actually do anything in twrp.
I can get into download mode so I thought to try odin-ing the latest version of twrp, but I still run into the teamwin screen and full-stop.
It's un-bootable, either into the normal phone or recovery, and I have no idea how to proceed from here. Phone's been fine prior to this - I've been on mj9 and build 24 was running great, so there aren't any major problems I can point to that may have caused this. I'm starting to freak out. Any suggestions would be really, really appreciated.

Odin 4.1.2 stock firmware with pit file then use Casuals method to get back up and running with TWRP is my suggestion

Cool, I'll give that a try, thanks! I'll update with my results.
update:
Returning to stock didn't work either, but (and I really wish I'd tried this first) flashing Philz CWM took care of it. Seems like TWRP just got stuck or something - as soon as I replaced it with CWM it booted right up.
Thanks again for the tip.

Kickass... great idea, when you said that I recalled seeing similar instances of people switching back and forth. It was vice versa scenarios using both phillz and Twrp on another thread.
Enjoy 25 it's sweet

Related

[Q] Can't access recovery

Okay. So. After some trouble with houstonn's latest rom's lately (getting stuck on boot), I decided I'd give one more try for the 4/30 release. Clean wipe, flashed it, flashed minimal apps. Stuck on boot. WOOP WHO CARES?
This time was different - I couldn't access recovery. So I tried like 30 more times to access recovery. Couldn't do it. LGNPST back to the ICS stock bin (11c). Get my OTA update to 4.1.2, rooted with this method http://forum.xda-developers.com/showthread.php?t=2006946. After that, I tried to access recovery mode again. Couldn't do it. So, I was like "what the hell, maybe FreeGee will help." So I continued on to unlock the bootloader with FreeGee and with CWM. Installed quickboot and chose to restart to recovery. SAME THING. Black Screen after LG logo. Can't get into recovery.
Now I'm LGNPSTing back to stock to repeat process. Any ideas on what's going on?
Edit: Running into quite a few problems with LGNPST. Gets stuck at 85% and won't boot even after power cycle.
Edit 2: TeenyBin AltBin let me format my partitions and then the LGNPST worked. Got the OTA. Rooted again, used FreeGee, except this time with TWRP 2.5.0.0. Wouldn't reboot afterwards, so moved on to TeenyBin AltBin again. The phone booted up and everything runs fine. One thing to note: I had some wifi problems when I just TeenyBinAltBin'd and used a restore point for stock 4.1.2 which is why I was so adamant to LGNPST like normal. Still can't flash any of the newer ROMs of houstonn's, but I can others. On the good side, I still have a phone. Hopefully if anyone else has the issue, they can follow this and resolve it.

[q] help!! Note down

So ,im sorry but its a long story. Hopefully someone can help. My note is Rooted Ive been using TWRP. Everything had been fine until 2 days ago. I tried flashing a ROM i found on Goomanger.( I had been running liquid smooth) just wanted to try something different. Anyways it got stuck on a boot loop. Cant remember the name of the Rom. Anyways i was able to get back to recovery, thankfully. But when i wiped and flashed back to liquid smooth it would say optimizing apps, then it would reach a certain number then reboot and star all over again. So then i tried another Rom and the same thing happened. tried flashing back to stock rooted but it would turn on then completely crash and star booting up again. So finally i was able to flash paraandroid 4.1.2 and Gapps, but here is the kicker i have no service (AT&T) says cannot locate network, my IMEI is gone basically the cellular isn't working. Everything else works fine WiFi,apps, camera. Just cant make calls. I really need your guys help please.:crying:
If you have a suggestion please let me know, i hate using an old Iphone
dar101978 said:
So ,im sorry but its a long story. Hopefully someone can help. My note is Rooted Ive been using TWRP. Everything had been fine until 2 days ago. I tried flashing a ROM i found on Goomanger.( I had been running liquid smooth) just wanted to try something different. Anyways it got stuck on a boot loop. Cant remember the name of the Rom. Anyways i was able to get back to recovery, thankfully. But when i wiped and flashed back to liquid smooth it would say optimizing apps, then it would reach a certain number then reboot and star all over again. So then i tried another Rom and the same thing happened. tried flashing back to stock rooted but it would turn on then completely crash and star booting up again. So finally i was able to flash paraandroid 4.1.2 and Gapps, but here is the kicker i have no service (AT&T) says cannot locate network, my IMEI is gone basically the cellular isn't working. Everything else works fine WiFi,apps, camera. Just cant make calls. I really need your guys help please.:crying:
If you have a suggestion please let me know, i hate using an old Iphone
Click to expand...
Click to collapse
Just odin back to stock. Get a complete factory stock image from the main sticky thread and flash it with Odin and Download Mode. There's a bug on one of the TWRP versions with 4.3-based ROMs that will put it into a bootloop by breaking device reboots. I was unable to flash my way out of the problem and was forced to do a complete reimage which solved all the problems and put me right back to clean-out-of-the-box state, then I reinstalled TWRP (though an older version before the boot loop bug) and re-flashed my custom ROM. The package I used was the stock image and Odin tool all in one .exe, just plug in to download mode and run it and it flashed bootloader, recovery, system, kernel, etc. all back to stock.
CalcProgrammer1 said:
Just odin back to stock. Get a complete factory stock image from the main sticky thread and flash it with Odin and Download Mode. There's a bug on one of the TWRP versions with 4.3-based ROMs that will put it into a bootloop by breaking device reboots. I was unable to flash my way out of the problem and was forced to do a complete reimage which solved all the problems and put me right back to clean-out-of-the-box state, then I reinstalled TWRP (though an older version before the boot loop bug) and re-flashed my custom ROM. The package I used was the stock image and Odin tool all in one .exe, just plug in to download mode and run it and it flashed bootloader, recovery, system, kernel, etc. all back to stock.
Click to expand...
Click to collapse
Thanks thats what i did, I just basically had to use KIES to use the emergency recovery, then root my phone again. My question is what version of TWRP causes this? cause i used the newest version i could find off GOO. My other concerne is, will it accept or be safe to use a custom ROM? Well i gues ill find out :laugh: THANKS AGAIN!
Everyone with the sgh-i717 is having problems with the latest TWRP and the most stable version is 2.5.0.0. Go with that one or you'll be starting all over again I imagine. And don't just stop at the download link in the OP's, read the thread and find out what's going on. The problems with TWRP have been going on for a while and the development threads have a lot of comments about the latest build causing problems. Good luck! :good:

Can't flash custom rom (MDK)

Hi All - Long time listener, first time caller.
I have a Verizon S4 and have been running stock root for a while now. I'm looking to install Carbon ROM. For some reason, when I try to flash it, I get the "Unauthorized Software" message that pops up after it completes and reboots. My only option is to boot back into TWRP and restore from backup. Everything that I've read says that it's because my bootloader isn't unlocked, but I can't figure out how to do it.
Is there something else I need to do? I'm on Ubuntu, so I can't really run the Windows things (unless Odin, for example, works through VIrtualbox? I haven't tried because there are general virtual USB issues that have soft bricked other devices I've had.)
I'm definitely on MDK (I froze the Samsung updater) and my initial effort to root was done on a friend's computer with Odin using these instructions: http://forum.xda-developers.com/showthread.php?t=2290798.
Running through the forum, I've tried:
http://forum.xda-developers.com/showthread.php?t=2606501 (Followed the MDK links which go to below)
http://forum.xda-developers.com/showthread.php?t=2578569 (it just talks about rooting which I already have)
I'm sure there's a step somewhere that I've missed, but I can't see the forest through the trees. Anything obvious that I didn't do?
The only other things I can think of that could get me there:
1. Update to the latest firmware and then just give in and use safestrap (not ideal)
2. Could I re-flash to the pre-release kernel and then go directly to CarbonROM? Will I need to reflash to the release-version of MDK after?
Open to suggestions.
FranklinPIerce said:
Hi All - Long time listener, first time caller.
I have a Verizon S4 and have been running stock root for a while now. I'm looking to install Carbon ROM. For some reason, when I try to flash it, I get the "Unauthorized Software" message that pops up after it completes and reboots. My only option is to boot back into TWRP and restore from backup. Everything that I've read says that it's because my bootloader isn't unlocked, but I can't figure out how to do it.
Is there something else I need to do? I'm on Ubuntu, so I can't really run the Windows things (unless Odin, for example, works through VIrtualbox? I haven't tried because there are general virtual USB issues that have soft bricked other devices I've had.)
I'm definitely on MDK (I froze the Samsung updater) and my initial effort to root was done on a friend's computer with Odin using these instructions: http://forum.xda-developers.com/showthread.php?t=2290798.
Running through the forum, I've tried:
http://forum.xda-developers.com/showthread.php?t=2606501 (Followed the MDK links which go to below)
http://forum.xda-developers.com/showthread.php?t=2578569 (it just talks about rooting which I already have)
I'm sure there's a step somewhere that I've missed, but I can't see the forest through the trees. Anything obvious that I didn't do?
The only other things I can think of that could get me there:
1. Update to the latest firmware and then just give in and use safestrap (not ideal)
2. Could I re-flash to the pre-release kernel and then go directly to CarbonROM? Will I need to reflash to the release-version of MDK after?
Open to suggestions.
Click to expand...
Click to collapse
The ROM may not have Loki support...if you are using the older twrp version it may not auto lokify the ROM...try updating your recovery and give it another go
FranklinPIerce said:
Hi All - Long time listener, first time caller.
I have a Verizon S4 and have been running stock root for a while now. I'm looking to install Carbon ROM. For some reason, when I try to flash it, I get the "Unauthorized Software" message that pops up after it completes and reboots. My only option is to boot back into TWRP and restore from backup. Everything that I've read says that it's because my bootloader isn't unlocked, but I can't figure out how to do it.
Is there something else I need to do? I'm on Ubuntu, so I can't really run the Windows things (unless Odin, for example, works through VIrtualbox? I haven't tried because there are general virtual USB issues that have soft bricked other devices I've had.)
I'm definitely on MDK (I froze the Samsung updater) and my initial effort to root was done on a friend's computer with Odin using these instructions: http://forum.xda-developers.com/showthread.php?t=2290798.
Running through the forum, I've tried:
http://forum.xda-developers.com/showthread.php?t=2606501 (Followed the MDK links which go to below)
http://forum.xda-developers.com/showthread.php?t=2578569 (it just talks about rooting which I already have)
I'm sure there's a step somewhere that I've missed, but I can't see the forest through the trees. Anything obvious that I didn't do?
The only other things I can think of that could get me there:
1. Update to the latest firmware and then just give in and use safestrap (not ideal)
2. Could I re-flash to the pre-release kernel and then go directly to CarbonROM? Will I need to reflash to the release-version of MDK after?
Open to suggestions.
Click to expand...
Click to collapse
I would recommend trying out Philz ( cwm ) recovery possibly. There have been random issues like yours reported and usually updating the recovery or just trying a different ROM all together gets better results.
You shouldn't need to go back to stock mdk for anything since you're already rooted and have a custom recovery.
Sent from my SCH-I545 using Tapatalk
Thanks for the suggestions. I did update my recovery, but now that I think of it, I may not have tried to re-flash since upgrading. My preference is to not use CWM, but I will if I have to, I guess.
In either case, I'll try this all out when I get home from work and post back. Thanks for the suggestions.
FranklinPIerce said:
Thanks for the suggestions. I did update my recovery, but now that I think of it, I may not have tried to re-flash since upgrading. My preference is to not use CWM, but I will if I have to, I guess.
In either case, I'll try this all out when I get home from work and post back. Thanks for the suggestions.
Click to expand...
Click to collapse
Let me suggest trying liquid smooth 4.4
Awesome ROM to try.
Sent from my SCH-I545 using Tapatalk
FranklinPIerce said:
Hi All - Long time listener, first time caller.
I have a Verizon S4 and have been running stock root for a while now. I'm looking to install Carbon ROM. For some reason, when I try to flash it, I get the "Unauthorized Software" message that pops up after it completes and reboots. My only option is to boot back into TWRP and restore from backup. Everything that I've read says that it's because my bootloader isn't unlocked, but I can't figure out how to do it.
Is there something else I need to do? I'm on Ubuntu, so I can't really run the Windows things (unless Odin, for example, works through VIrtualbox? I haven't tried because there are general virtual USB issues that have soft bricked other devices I've had.)
I'm definitely on MDK (I froze the Samsung updater) and my initial effort to root was done on a friend's computer with Odin using these instructions: http://forum.xda-developers.com/showthread.php?t=2290798.
Running through the forum, I've tried:
http://forum.xda-developers.com/showthread.php?t=2606501 (Followed the MDK links which go to below)
http://forum.xda-developers.com/showthread.php?t=2578569 (it just talks about rooting which I already have)
I'm sure there's a step somewhere that I've missed, but I can't see the forest through the trees. Anything obvious that I didn't do?
The only other things I can think of that could get me there:
1. Update to the latest firmware and then just give in and use safestrap (not ideal)
2. Could I re-flash to the pre-release kernel and then go directly to CarbonROM? Will I need to reflash to the release-version of MDK after?
Open to suggestions.
Click to expand...
Click to collapse
I would try their suggestions. For future reference though, you can use heimdall instead of Odin on Linux. I love it I think its better than odin
Sent from my unknown using Tapatalk
Ok, so I updated TWRP to the latest and tried again. Got the same message as before about unauthorized software and in the upper left, it said something about "Fail: Kernal"
From there, I had a hard time getting back into recovery. It would either say it was booting into recovery and then shut off or it would freeze. I eventually got back in and am restoring now.
Thanks for the information on Heimdall - I wasn't aware of it. The reason I wanted to go with Carbon is that it has a built-in application to control/override application permissions. Does something like that exist for LiquidRom? Or is it compatible with PDroid or something similar? (I didn't see a mention of it in their features, but might have missed it)
One more thought: I am using the Carbon nightlies for KK. Maybe there's a problem with the source file (I've redownloaded 4 times)? Or maybe I'm just destined to be on stock forever. :crying:
Edit: I just tried putting Philz recovery on and now I can't get into recovery as that's now giving the same unauthorized software message.
Edit2: I was able to get TWRP on eventually by going into Odin mode and hitting "Cancel." Each normal reboot would then give the same unauthorized message, so I just went back to TWRP and it's booting normally again. Ah, yay to Verizon and their locked phones.
Ok, I've tried a few more times tonight with no luck, so I'll give it a break for now and look into it more tomorrow or over the weekend.
FranklinPIerce said:
Ok, so I updated TWRP to the latest and tried again. Got the same message as before about unauthorized software and in the upper left, it said something about "Fail: Kernal"
From there, I had a hard time getting back into recovery. It would either say it was booting into recovery and then shut off or it would freeze. I eventually got back in and am restoring now.
Thanks for the information on Heimdall - I wasn't aware of it. The reason I wanted to go with Carbon is that it has a built-in application to control/override application permissions. Does something like that exist for LiquidRom? Or is it compatible with PDroid or something similar? (I didn't see a mention of it in their features, but might have missed it)
One more thought: I am using the Carbon nightlies for KK. Maybe there's a problem with the source file (I've redownloaded 4 times)? Or maybe I'm just destined to be on stock forever. :crying:
Edit: I just tried putting Philz recovery on and now I can't get into recovery as that's now giving the same unauthorized software message.
Edit2: I was able to get TWRP on eventually by going into Odin mode and hitting "Cancel." Each normal reboot would then give the same unauthorized message, so I just went back to TWRP and it's booting normally again. Ah, yay to Verizon and their locked phones.
Ok, I've tried a few more times tonight with no luck, so I'll give it a break for now and look into it more tomorrow or over the weekend.
Click to expand...
Click to collapse
That's odd that flashing Philz didn't work for you. Its a pain I know but probably if you had wiped the phone with stock mdk then tried again it woukd have worked I bet. I had to do that with this phone when i got it. It came with twrp, but was acting real funny not always getting into recovery or just hanging up on reboot. But you have a working twrp so that's good too.
I don't believe liquid has the built in app permissions you're talking about but maybe I missed it. I don't really mess with permissions. Liquid has everything else though and then some!
I know some Roms were having problems with unified builds. I know liquid does not at this point. Maybe it'd be worth trying just so you're not on stock lol you may want to look into the Loki doki zip that you flash after flashing the ROM. I've seen some people on here using that when they were getting the same error you were. Just an idea.
Good luck man!
Sent from my SCH-I545 using Tapatalk

[Q] Rooted, but can't install custom recovery...

Ok, so I've rooted and put custom roms on numerous phones. I've been trying to put a custom recovery, twrp or cwm, whatever, on my wife's phone, but have got a wall. I know for sure, 100% that I am rooted. I tired to install twrp and cwm via their respective apps, ends up in either bootloop trying to boot into recovery (and FYI, the screen shows that a custom recovery is installed, just doesn't load into recovery and restarts). And tried both via Odin, but got the same result. Have never ran into this problem before with any of my phone's, all of the galaxy's and Galaxy Note's since the S2. Any help would be greatly appreciated. Thanks homies!
Just to add, yes I made sure double checked, triple checked that I was installing the correct recovery for the phone model. Also, she has done all the ota updates that sprint has pushed as of last week (2/9/15).
Psychotic-Cerebellum said:
Ok, so I've rooted and put custom roms on numerous phones. I've been trying to put a custom recovery, twrp or cwm, whatever, on my wife's phone, but have got a wall. I know for sure, 100% that I am rooted. I tired to install twrp and cwm via their respective apps, ends up in either bootloop trying to boot into recovery (and FYI, the screen shows that a custom recovery is installed, just doesn't load into recovery and restarts). And tried both via Odin, but got the same result. Have never ran into this problem before with any of my phone's, all of the galaxy's and Galaxy Note's since the S2. Any help would be greatly appreciated. Thanks homies!
Just to add, yes I made sure double checked, triple checked that I was installing the correct recovery for the phone model. Also, she has done all the ota updates that sprint has pushed as of last week (2/9/15).
Click to expand...
Click to collapse
OK, from your post it looks like you have done this before. To be sure lets go through the motions one more time.
Your device is updated to 4.4.4 NK4 the latest KitKat version. It's rooted you have supersu icon and run a root checker. First download again ( in case you got a bad download ) a copy of Philz CWM version 6.48.4 here is the link https://goo.im/devs/philz_touch/CWM_Advanced_Edition/hlte/ use "phil'z_touch_6.48.6-hlte.tar.md5" . I like to use odin version v1.85 it's little older but very stable, here is a link https://mega.co.nz/#!oA5xzTAL!LXoVWB...ZlOMSWdRGVX6Uo now flash the .tar file with odin. Make sure you let device boot up on it's own back to the OS, do not pull the cable and boot the device yourself. Then try and boot into recovery.
If it bootloops again, I would backup all your data to the PC desktop, and then do a factory reset get back to bone stock ( that means when your in download mode it says Samsung Official status not custom ) so many times I have seen folks with an unrooted device where the bootloader still says custom and you end up with a dirty flash or worse. It may take a couple factory resets to get back to stock, it doesn't always take the first time. When I flash a custom rom and then decide to go back to stock, I flash the rom two or three times to make sure I'm bone stock.
If the factory reset doesn't work you may have to flash a new stock NK4 OS. Then root again and install the recovery. Here is my thread with all the info you need http://forum.xda-developers.com/note-3-sprint/general/samsung-note-3-rom-flashin-basics-t2896440 , Enjoy !!!
Thanks for taking the time to give me a detailed response. Sounds like I'm gonna have to wait till Wednesday or Thursday when im off work and have some time to do this, but yeah, I was thinking maybe just a factory reset, but I'll use your links and try it one more time first. I'll let ya know. Thanks again
Do you have another link to the older Odin (1.85).the link says the file isn't there... Thanks again
Never got to test it out, but she didn't really want a custom rom anyway, just the WiFi hotspot, and I finally found a method that works, big shout out to idone for his awesome app. If anyone else is looking for WiFi hotspot without root that sees this, check out his tread in the apps and themes, for this phone. Worked like a charm. Thanks again jimzweb1. Much appreciate the reply!
Psychotic-Cerebellum said:
Never got to test it out, but she didn't really want a custom rom anyway, just the WiFi hotspot, and I finally found a method that works, big shout out to idone for his awesome app. If anyone else is looking for WiFi hotspot without root that sees this, check out his tread in the apps and themes, for this phone. Worked like a charm. Thanks again jimzweb1. Much appreciate the reply!
Click to expand...
Click to collapse
Awesome, Ya idone is the man when it comes to enabling the mobile hotspot be careful what you click with app. I will correct that link. Thanks
Psychotic-Cerebellum said:
Ok, so I've rooted and put custom roms on numerous phones. I've been trying to put a custom recovery, twrp or cwm, whatever, on my wife's phone, but have got a wall. I know for sure, 100% that I am rooted. I tired to install twrp and cwm via their respective apps, ends up in either bootloop trying to boot into recovery (and FYI, the screen shows that a custom recovery is installed, just doesn't load into recovery and restarts). And tried both via Odin, but got the same result. Have never ran into this problem before with any of my phone's, all of the galaxy's and Galaxy Note's since the S2. Any help would be greatly appreciated. Thanks homies!
Just to add, yes I made sure double checked, triple checked that I was installing the correct recovery for the phone model. Also, she has done all the ota updates that sprint has pushed as of last week (2/9/15).
Click to expand...
Click to collapse
That's the problem Knox security is getting harder flash engineering boot loader again then try rashr in app store to flash philz

Stuck at Sprint Screen; have details on what I did.

Hi, Followed all the amazing walk through like normal. Not sure what 4.x.x.x I was on, never really check to be honest.
First time this phone has been rooted. (I rooted because I was having problems with the phone, last phone I rooted and was able to fix the problems).
1. Used the download file and instructions by qking...
2. Same with TWRP
3. It rebooted, somehow it screwed up MicroSD card, would no longer read it. Then it rebooted again..
4. Stuck on Sprint screen for last couple hours.
I tried to get back into TWRP and do a factory clean and reset, when it rebooted it, sat at the Sprint Screen for hour or so. Then I searched and a few other people just had to use odin and redo it again and worked fine.
So I did odin again relfashed the file and at reboot it is stuck on Yellow Sprint screen..
That is where im stuck at now is Sprint Screen, thanks in advance!
Swaintan said:
Hi, Followed all the amazing walk through like normal. Not sure what 4.x.x.x I was on, never really check to be honest.
First time this phone has been rooted. (I rooted because I was having problems with the phone, last phone I rooted and was able to fix the problems).
1. Used the download file and instructions by qking...
2. Same with TWRP
3. It rebooted, somehow it screwed up MicroSD card, would no longer read it. Then it rebooted again..
4. Stuck on Sprint screen for last couple hours.
I tried to get back into TWRP and do a factory clean and reset, when it rebooted it, sat at the Sprint Screen for hour or so. Then I searched and a few other people just had to use odin and redo it again and worked fine.
So I did odin again relfashed the file and at reboot it is stuck on Yellow Sprint screen..
That is where im stuck at now is Sprint Screen, thanks in advance!
Click to expand...
Click to collapse
OK first pull battery, now reinsert bat and hold the power, home, and volume down buttons at the same time, then press the volume up button to get into download mode. Don't bother trying to get back to TWRP your past that. While in download mode check the status of the device. Is it Official or custom? Let me know the status.
Now lets flash a fresh stock OS with Odin, to save me a lot of typing go here. http://forum.xda-developers.com/note-3-sprint/general/samsung-note-3-rom-flashin-basics-t2896440
Download the version of odin you want both work fine. Download the version of the KK OS you want to flash, I like NK4. You can follow the steps on my thread listed above to flash an OS with one EXCEPTION!!!
EVEN IF THE DEVICE BOOTS UP AFTER YOU FLASH THE OS THE FIRST TIME, ONCE YOU GET PAST THE SET UP FOR FIRST TIME USE WHICH ( STARTS ABOUT 3-5 MIN AFTER THE SAMSUNG LOGO SCREEN BY THE WAY BE PATIENT ) POWER DOWN THE DEVICE GET BACK INTO DOWNLOAD MODE AND ODIN FLASH THE OS AGAIN !!!
This should get you back to bone stock OS. Once it boots up and get passed first time use set up. Now your ready to root, the way I root is first grab a copy of SuperSU ( latest version is fine its on my thread ) with your PC copy and paste it on the SD card. Next power down completely and boot into download mode, Odin flash a custom recovery TWRP is a good one. The device should boot up after the recovery is flashed on its own, don't try boot up the device yourself to soon, give the recovery a chance to flash completely. Now completely power down the device, hold the power, home, and volume up buttons and boot into recovery. Then flash the SuperSu zip then reboot device you should be off and running . . . .
Here is the first part, im working on the rest now.
Current Binary: Custom
System Status: Custom
Swaintan said:
Here is the first part, im working on the rest now.
Current Binary: Custom
System Status: Custom
Click to expand...
Click to collapse
Ok cool, remember that everything has to fit. Meaning depending on what OS you run i.e. KitKat, Lollipop etc everything should updated to match.
Example : If you run KK NC5 OS then Philz CWM recovery 6.9.12 and later works. TWRP 2.8.3.0 or later works.
If you run Lollipop OC5 then Philz CWM recovery 6.48.4 works. ( link is broken I have a copy if you need it ) TWRP 2.8.6.0 or later works.
As for SuperSU you could go all the way back to v 1.94 and still root the binarys will update automatically. The latest (stable ) version is 2.46 from chainfire.
TY Ill keep you updated, file is taking a long time to download, still sitting at 1 hr to finish up download. Once its downloaded ill continue with the rest of the steps and post updates.
Not been very happy with sprint lately, latest update to my Wifes note 2 screwed her phone way up, only way to fix it was root it. So as soon as I saw mine doing the same thing I hurried to root it, but looks like it was to late. Hopefully this fixes it all, I really do appreciate it.
Swaintan said:
Hi, Followed all the amazing walk through like normal. Not sure what 4.x.x.x I was on, never really check to be honest.
First time this phone has been rooted. (I rooted because I was having problems with the phone, last phone I rooted and was able to fix the problems).
1. Used the download file and instructions by qking...
2. Same with TWRP
3. It rebooted, somehow it screwed up MicroSD card, would no longer read it. Then it rebooted again..
4. Stuck on Sprint screen for last couple hours.
I tried to get back into TWRP and do a factory clean and reset, when it rebooted it, sat at the Sprint Screen for hour or so. Then I searched and a few other people just had to use odin and redo it again and worked fine.
So I did odin again relfashed the file and at reboot it is stuck on Yellow Sprint screen..
That is where im stuck at now is Sprint Screen, thanks in advance!
Click to expand...
Click to collapse
Forgot to say why you flash twice, when the device is corrupted or bootloops. 9 times out of 10 its because something was left behind from the previous OS or something didn't flash in from the new OS. Flashing twice I found through ( trial and error pulling my hair out ) solves this problem.
When I get done with a flashaholic binge and need to get back to a daily user, I always flash back to Stock OS twice, install recovery, and root. Then install a custom OS if want run one this way you always start clean. This way if something doesn't work or stops working you right where to start looking for the problem.
---------- Post added at 07:03 AM ---------- Previous post was at 06:55 AM ----------
Swaintan said:
TY Ill keep you updated, file is taking a long time to download, still sitting at 1 hr to finish up download. Once its downloaded ill continue with the rest of the steps and post updates.
Not been very happy with sprint lately, latest update to my Wifes note 2 screwed her phone way up, only way to fix it was root it. So as soon as I saw mine doing the same thing I hurried to root it, but looks like it was to late. Hopefully this fixes it all, I really do appreciate it.
Click to expand...
Click to collapse
Ya I agree rooting stops the updates. Usually I read up on the update first to see what problems it may be causing. Then decide to unroot and take it, I still run my 4.4.4 NK4 deoexed no knox debloated OS just not a fan of Lollipop to many problems with it, besides there's no themes for it.
You are awesome! Followed your directions and links inside your siggy. So this is where I sit;
I installed (from your siggy)
-SPRINT KK 4.4.4 N900PVPUDNK4
Stock rom : DEODEXED, NO KNOX, and DEBLOATED ( #2 )
Busybox / Zipaligned
Rooted / Superuser
No Knox ( Disabled / Removed )
Volume Mod / 300+ Fonts ( Thanks DevilDog512 )
Custom Kernel ****
-SU 2.46 (it auto updated when I installed)
-TWRP Manager 8.0.1.8
-Recovery TWRP 2.8.7.0
Now I have to start redoing apps etc.. THANK YOU SO MUCH!!!
Edit: Add: Now should be safe to install Wicked Green Theme and get all family n friends to send contact info... that part will be harder then what you had me do, TY again!
Swaintan said:
You are awesome! Followed your directions and links inside your siggy. So this is where I sit;
I installed (from your siggy)
-SPRINT KK 4.4.4 N900PVPUDNK4
Stock rom : DEODEXED, NO KNOX, and DEBLOATED ( #2 )
Busybox / Zipaligned
Rooted / Superuser
No Knox ( Disabled / Removed )
Volume Mod / 300+ Fonts ( Thanks DevilDog512 )
Custom Kernel ****
-SU 2.46 (it auto updated when I installed)
-TWRP Manager 8.0.1.8
-Recovery TWRP 2.8.7.0
Now I have to start redoing apps etc.. THANK YOU SO MUCH!!!
Edit: Add: Now should be safe to install Wicked Green Theme and get all family n friends to send contact info... that part will be harder then what you had me do, TY again!
Click to expand...
Click to collapse
Cool, what stock version KK OS did you flash twice before installed my deodexed 4.4.4 NK4 ?
Not sure, i know i followed each one, so it took me to a site where I had to download it specifically for my phone. My dl history says file name was N900PVPUDNK4_SPR it was the bone stock md5, did that one twice.
Swaintan said:
Not sure, i know i followed each one, so it took me to a site where I had to download it specifically for my phone. My dl history says file name was N900PVPUDNK4_SPR it was the bone stock md5, did that one twice.
Click to expand...
Click to collapse
Cool, that will work fine.

Categories

Resources