TWRP for Nexus 6 and 9 Available, Unofficial CM12 Alpha for HTC Explorer! – XDA TV

Team Win Recovery Project for the Nexus 6 and Nexus … more

Jolla Tablet Announced: The Second Sailfish OS Device

A little over a year ago, Jolla released its first smartphone with the brand new Jolla … more

Android One Devices Get Unofficial CM12 Port

Android One was initially announced right before Android Lollipop. By releasing these cheap, yet … more

WhatsApp Decides to Protect Your Data

When Facebook bought WhatsApp for the absurdly large sum of $19bn back in February, they took the tech … more

Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

Note 3 Failure: Problems with Kernel and Recovery

OP KoolCharisma

14th March 2014, 05:07 PM   |  #1  
KoolCharisma's Avatar
OP Member
Flag College Park,, MD
Thanks Meter: 3
 
35 posts
Join Date:Joined: Apr 2013
More
Hey guys, I don't post here often, but I'm not new to this. It was through this forum that I first started rooting with mfy s3.

I just got a note 3 through Sprint. I've gotten used to getting off the grid, so I immediately jumped to root it. I decided on Jellybomb after reading some reviews. Then I downloaded everything necessary to make the jump: Odin, 1.85 and 3.09, jellybomb, cwm 6.0, twrp 7, auto-root, and the original roms in case I had to hop back.

First I went with Chainfires auto-root. I didn't seem to have any problem flashing that. The problem came with flashing twrp and the new rom. I can't remember which one was giving me trouble (I've been fighting it almost a week now). Somehow some way the phone has been stuck in an autoboot that says "seandroid not enforcing" and either "warranty bit: recovery" or "warranty bit: kernel". I tried new kernels. I tried things in different order. I can get into recovery but only after going immediately after autoroot. Even there you have a broken android.

Please help. I've been without a phone for a week.
Last edited by KoolCharisma; 14th March 2014 at 05:21 PM.
14th March 2014, 10:59 PM   |  #2  
Senior Member
Thanks Meter: 325
 
1,132 posts
Join Date:Joined: Oct 2012
Quote:
Originally Posted by KoolCharisma

Hey guys, I don't post here often, but I'm not new to this. It was through this forum that I first started rooting with mfy s3.

I just got a note 3 through Sprint. I've gotten used to getting off the grid, so I immediately jumped to root it. I decided on Jellybomb after reading some reviews. Then I downloaded everything necessary to make the jump: Odin, 1.85 and 3.09, jellybomb, cwm 6.0, twrp 7, auto-root, and the original roms in case I had to hop back.

First I went with Chainfires auto-root. I didn't seem to have any problem flashing that. The problem came with flashing twrp and the new rom. I can't remember which one was giving me trouble (I've been fighting it almost a week now). Somehow some way the phone has been stuck in an autoboot that says "seandroid not enforcing" and either "warranty bit: recovery" or "warranty bit: kernel". I tried new kernels. I tried things in different order. I can get into recovery but only after going immediately after autoroot. Even there you have a broken android.

Please help. I've been without a phone for a week.


This one is the International Note 3 forum.

You should ask for actual details in the specific Sprint Note 3 forum:

http://forum.xda-developers.com/note-3-sprint


You should also pay more attention to the fact that the questions should be posted in the Q&A subforum.
15th March 2014, 12:09 AM   |  #3  
KoolCharisma's Avatar
OP Member
Flag College Park,, MD
Thanks Meter: 3
 
35 posts
Join Date:Joined: Apr 2013
More
Thanks
Quote:
Originally Posted by xclub_101

This one is the International Note 3 forum.

You should ask for actual details in the specific Sprint Note 3 forum:

http://forum.xda-developers.com/note-3-sprint


You should also pay more attention to the fact that the questions should be posted in the Q&A subforum.

Cheers! It looks from your sig though that you have found a work around on your international version. Are they really that different, that need entirely separate instructions. Obviously I downloaded all of the suggested software for Sprint and followed Sprint suggested, but I'm frustrated because I simply don't understand how I could do something the same way everyone else did and yet have it fail on me like this.
15th March 2014, 07:34 AM   |  #4  
Anonymous777's Avatar
Member
Flag Salt Lake City
Thanks Meter: 11
 
86 posts
Join Date:Joined: Jun 2012
More
I am having the exact same problem...at first i was able to flash 'openrecovery-twrp-2.6.3.0-hltetmo.img.tar and it would boot my phone back to normal. I have now run into this problem again and my first original fix isn't working anymore. If I can figure out a way I will definitely let you know!
15th March 2014, 08:17 AM   |  #5  
KoolCharisma's Avatar
OP Member
Flag College Park,, MD
Thanks Meter: 3
 
35 posts
Join Date:Joined: Apr 2013
More
Talking Getting Answers
Quote:
Originally Posted by Anonymous777

I am having the exact same problem...at first i was able to flash 'openrecovery-twrp-2.6.3.0-hltetmo.img.tar and it would boot my phone back to normal. I have now run into this problem again and my first original fix isn't working anymore. If I can figure out a way I will definitely let you know!

Hey man, thanks for reaching out. I realized I should probably have been in the Sprint form so I created a new thread there and I've been getting some help!

If you want: shoot over there and see if the tips can help you: http://forum.xda-developers.com/show...php?p=51096673
The Following User Says Thank You to KoolCharisma For This Useful Post: [ View ]
16th March 2014, 12:10 PM   |  #6  
KoolCharisma's Avatar
OP Member
Flag College Park,, MD
Thanks Meter: 3
 
35 posts
Join Date:Joined: Apr 2013
More
Quote:
Originally Posted by Anonymous777

I am having the exact same problem...at first i was able to flash 'openrecovery-twrp-2.6.3.0-hltetmo.img.tar and it would boot my phone back to normal. I have now run into this problem again and my first original fix isn't working anymore. If I can figure out a way I will definitely let you know!

Hey man we've made a lot of headway at the above thread Thanks to Macmars. You should check it out and see if we can help each other.

Sent from my SM-N900P using xda app-developers app
16th March 2014, 12:40 PM   |  #7  
Anonymous777's Avatar
Member
Flag Salt Lake City
Thanks Meter: 11
 
86 posts
Join Date:Joined: Jun 2012
More
Quote:
Originally Posted by KoolCharisma

Hey man we've made a lot of headway at the above thread Thanks to Macmars. You should check it out and see if we can help each other.

Sent from my SM-N900P using xda app-developers app

I figured out what to do, use odin 3.9 and flash this, it took about 15 minutes to go through the whole process. Once my phone boot up it froze at the T-Moble logo or whatever, so I waited like 20 minutes and then powered it off, went into recovery and did a factory reset which then solved all my problems. I lost root, but no big deal to me. Better than buying a new phone!!! Btw the only place I could find this file is off sammobile.com. You have to sign up for a free membership thing but at least they give you the stock firmware.


TMB-N900TUVUCNB4-20140305155920/N900TUVUCNB4_N900TTMBCNB4_N900TUVUCNB4_HOME.tar.md 5
16th March 2014, 05:30 PM   |  #8  
KoolCharisma's Avatar
OP Member
Flag College Park,, MD
Thanks Meter: 3
 
35 posts
Join Date:Joined: Apr 2013
More
Quote:
Originally Posted by KoolCharisma

Hey man we've made a lot of headway at the above thread Thanks to Macmars. You should check it out and see if we can help each other.

Sent from my SM-N900P using xda app-developers app

Right on man!

Sent from my SM-N900P using xda app-developers app

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes