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

[Q] Note 3 - Killed by my incompetence

OP DariusMk

16th June 2014, 10:19 AM   |  #1  
OP Junior Member
Thanks Meter: 0
 
3 posts
Join Date:Joined: Jun 2014
So hello everyone. This is my first post and i am already groveling for help to see if my Note can be salvaged.

Yesterday I decided to put CyanogenMOD on. I had it on my 1st Gen. Note and I loved it! Problem is, the app they provide for installation does not yet support Note 3, so I went down the old road of doing it manualy. Never done it before though, so something was bound to happen.

Problem caused by impatience and ignorance

In short, i did the following -

1) Installed CF AutoRoot, which, of course, installed SuperSU
2) Installed MobileOdin
3) Put CM11 on my SD card
4) Booted into stock OS and attempted to install CM using MOdin
5) Failed to install - ODIN kept saying its not meant for my phone (i go the hlte image and the image was supposedly meant for hltexx etc.)
6) I followed to instructions to delete a line from the install script which would allow me to install the same image with no problems.
7) Last step obviously unzipping and rezipping file
8) Phone gives another big FU and says this is not the right image now

And this is where I firmly believe i messed up

8) Frustrated, i uploaded an unzipper folder
9) Picked the file 'boot.img' as targer file in Mobile Odin (Why? Why did I do that?)

Result - boot process is stuck at the Samsung SM-N9005 etc. logo with the top two lines saying:

KERNEL IS NOT SEANDROID ENFORCING
Set Warranty Bit : kernel

After a good 15-20s pause the phone just shuts down.


Question
What the verdict? This thing is salvageable or should I start weeping?
16th June 2014, 02:07 PM   |  #2  
Dan-SRi's Avatar
Senior Member
Flag Dorset
Thanks Meter: 61
 
245 posts
Join Date:Joined: Aug 2010
More
Try taking the battery out for about 10 seconds and then hold home and volume up and then insert the battery. Should boot into download mode where you can use odin on desktop to flash original ROM. Solved a similar issue for me.
17th June 2014, 12:56 AM   |  #3  
OP Junior Member
Thanks Meter: 0
 
3 posts
Join Date:Joined: Jun 2014
Quote:
Originally Posted by Dan-SRi

Try taking the battery out for about 10 seconds and then hold home and volume up and then insert the battery. Should boot into download mode where you can use odin on desktop to flash original ROM. Solved a similar issue for me.

Worked like a charm! Phone is back to normal, although i am not quite down trying to get CMMod on it
17th June 2014, 04:34 AM   |  #4  
Senior Member
Flag London
Thanks Meter: 215
 
709 posts
Join Date:Joined: Dec 2010
More
Quote:
Originally Posted by DariusMk

So hello everyone. This is my first post and i am already groveling for help to see if my Note can be salvaged.

Yesterday I decided to put CyanogenMOD on. I had it on my 1st Gen. Note and I loved it! Problem is, the app they provide for installation does not yet support Note 3, so I went down the old road of doing it manualy. Never done it before though, so something was bound to happen.

Problem caused by impatience and ignorance

In short, i did the following -

1) Installed CF AutoRoot, which, of course, installed SuperSU
2) Installed MobileOdin
3) Put CM11 on my SD card
4) Booted into stock OS and attempted to install CM using MOdin
5) Failed to install - ODIN kept saying its not meant for my phone (i go the hlte image and the image was supposedly meant for hltexx etc.)
6) I followed to instructions to delete a line from the install script which would allow me to install the same image with no problems.
7) Last step obviously unzipping and rezipping file
8) Phone gives another big FU and says this is not the right image now

And this is where I firmly believe i messed up

8) Frustrated, i uploaded an unzipper folder
9) Picked the file 'boot.img' as targer file in Mobile Odin (Why? Why did I do that?)

Result - boot process is stuck at the Samsung SM-N9005 etc. logo with the top two lines saying:

KERNEL IS NOT SEANDROID ENFORCING
Set Warranty Bit : kernel

After a good 15-20s pause the phone just shuts down.


Question
What the verdict? This thing is salvageable or should I start weeping?

Sounds like you just flashed the cm11 kernel boot.img

Just flash the latest twrp recovery, backup your existing setup in twrp.. format system, cache, data and internal storage if you want.. then flash cm11 and then gapps

Sent from my SM-N9005
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes