Database Users

How to install CM9 -- brick proof -- guaranteed :)

Galaxy Note N7000.
Was running stock ICS-ROM Samsung.
Always wanted to install and use a custom ROM but was always afraid of BRICKS..
But yesterday ended up being sucessfully running CM9.
Steps I undertook were as follows:
1. Installed Samsung Kies.
2. Check for update from Samsung Kies and updated Kies.
3. Connected my phone to Kies and checked if Kies detected the phone properly.
After sucess, exit Kies.
4. Downloaded PC Odin from this link
http://forum.xda-developers.com/attachment.php?attachmentid=815370&stc=1&d=1323799721
password:samfirmware.com
5. Download pre rooted GingerBread ROM
SGN_XX_OXA_KJ1_FACTORYFS.zip (thx dr.ketan)
http://d-h.st/HJM
6. Run PC odin
7. Reboot Note in download mode
vol. down+home+power buttons
8. Connect Download mode note to PC
9. PC odin ID:COM turns yellow:
(ALL THE BEST NOW)
10. In PC ODIN
Auto Reboot and F.Reset Time ---> Ticked
Others --> Unticked
10. Click PDA and select the SGN_XX_OXA_KJ1_FACTORYFS.zip you had downloaded.
Click start.
Wait for 10minutes.
Your phone will restart.
11. WOW..!!! now ur on a GB Rom
And its a safe kernel
Now you can play around
Plus already rooted
12. Now to get this GB Rom working
go to recovery mode (vol up + home + power)
clean dalvik cache and wipe data and factory reset
13. Time to install CM9
14. Download
CM9 latest nightly:
http://get.cm/?device=n7000
Googleapps:
http://goo.im/gapps/gapps-ics-20120429-signed.zip
15. Copy these 2 files in the internal SD card anywhere (do not rename)
16. Reboot into recovery mode:
vol up + home + power
17. Flash the 2 files from where you saved them:
"install zip from sd card" option in recovery mode
now flash cm9 file
then flash gapps file
18. DO A DATA WIPE / FACTORY RESET
19. Reboot
And wow..
Enter the world of custom ROMS
[[[to switch to another ROM, follow steps 1 to 17, and after that flash the ROM of your choice]]]

Steps 6 and 9
it shud be PC Odin Not Mobile

sorry dr. ketan
my mistake
corrected
thanks

So...
So i have galaxy note gt n700 purchased in germany and brickbug app said that i have dangeros ...something something.... I mean i have mmc bug which will make my phone in paperpress if i mess up. Question is: does step by step guide is safe for my mmc bug? Can i safely follow it and not ruin my phone, because i think i have a bad warranty.

dr.ketan said:
Steps 6 and 9
it shud be PC Odin Not Mobile
Click to expand...
Click to collapse
Noticed that u are very experienced contributor, so mybe u can answer on my question, does the step by step guide is safe for galaxt note with brickbug? I realy want to flash, but i want to do it if i am on the safe side

Latvianization said:
So i have galaxy note gt n700 purchased in germany and brickbug app said that i have dangeros ...something something.... I mean i have mmc bug which will make my phone in paperpress if i mess up. Question is: does step by step guide is safe for my mmc bug? Can i safely follow it and not ruin my phone, because i think i have a bad warranty.
Click to expand...
Click to collapse
Yes, you can follow this guide safely. Actually, this is the best guide I've seen so far, I wish I had this one the moment I wanted to start messing around with my phone because I spent more than 48 hours total reading and reading and getting more confused each time.
So go ahead and do it.
And thank you to the OP for putting this up.
Sent from a GNote, hell yeah!

SirRhor said:
Yes, you can follow this guide safely. Actually, this is the best guide I've seen so far, I wish I had this one the moment I wanted to start messing around with my phone because I spent more than 48 hours total reading and reading and getting more confused each time.
So go ahead and do it.
And thank you to the OP for putting this up.
Sent from a GNote, hell yeah!
Click to expand...
Click to collapse
And the last one, probably silly question, what CM9 rom is this? Will i have GB or ICS? And if thats GB where can i find safe ICS rom?

Before Galaxy Note, I used to rock HTC Wildfire and didn't wanted to mess around with custom roms because it was just low-end device. Third-party launchers did the job for me when it comes to customization.
When I bought Galaxy Note, I was looking forward to flashing Cyanogenmod or maybe something different (I like Paranoid Android rom and the hybrid mode). I was very disappointed to see that there is a brick bug.
Even though I'm a IT engineer and I have been using computers since Commodore 64, I don't have experience in flashing custom roms so this post is very useful if it's the best way to do it.
Do I have to flash different stock GB before rooting, because I have XXLA6 kernel (baseband: xxla4) and I believe that this version is not directly rootable? Correct me if i'm wrong?
What is the best way to return from custom rom (ie. CM9) to stock GB?
In fact, I've been reading for a good amount of time today but there is just too much information, so sorry for the noobish questions.

I installed rom before 2 days and had similar doubts.
Just want to share what problem I faced :
The mobile should be in ON state when rooting CF I was doing it in OFF download mode

Latvianization said:
And the last one, probably silly question, what CM9 rom is this? Will i have GB or ICS? And if thats GB where can i find safe ICS rom?
Click to expand...
Click to collapse
CyanogenMod 9 is based on ICS, CM7 is based on Gingerbread. There wasn't a CM8 because Google never released the source code for Honeycomb.
And what you need is a safe kernel, because the kernel is what sends a erase command to a chip inside the phone and that's when you brick it (I think). That happens when you do a factory reset.
Now, what I always do when I want to change ROMS is to use AbbysNote 4.2 as a safe GB kernel so I can then flash the ROM/Kernel of my choice.
You can find it here: http://forum.xda-developers.com/showthread.php?t=1362424&highlight=abyssnote
So let's say you want to go from CM9 to LiquidSmooth (or pretty much any other), which is the one I use now:
You go to CWM recovery, from there you flash AbyssNote.
Once the flashing is completed, you DO NOT exit CWM, instead you go to "Advanced" and then "Reboot to Recovery" so the phone will restart but it will go directly to CWM again, but now with AbyssNote installed.
AbyssNote has a TOUCH based recovery, so it is easier to use. Don't use the physical power and volume buttons to navigate.
From there you can safely do a factory reset, format cache, format Dalvik, flash a new ROM and Kernel.
AbyssNote will then disappear because it will be overwritten by the new Kernel of your choice. So every time I want to change to a new ROM, I repeat the steps above I haven't had any problems whatsoever.
I hope I'm right with my technicalities, but the procedures the OP and I describe are safe to try as long you follow the exact instructions, so before you try anything, read and re-read and you will be just fine.
---------- Post added at 12:38 PM ---------- Previous post was at 12:34 PM ----------
tribalkg said:
Before Galaxy Note, I used to rock HTC Wildfire and didn't wanted to mess around with custom roms because it was just low-end device. Third-party launchers did the job for me when it comes to customization.
When I bought Galaxy Note, I was looking forward to flashing Cyanogenmod or maybe something different (I like Paranoid Android rom and the hybrid mode). I was very disappointed to see that there is a brick bug.
Even though I'm a IT engineer and I have been using computers since Commodore 64, I don't have experience in flashing custom roms so this post is very useful if it's the best way to do it.
Do I have to flash different stock GB before rooting, because I have XXLA6 kernel (baseband: xxla4) and I believe that this version is not directly rootable? Correct me if i'm wrong?
What is the best way to return from custom rom (ie. CM9) to stock GB?
In fact, I've been reading for a good amount of time today but there is just too much information, so sorry for the noobish questions.
Click to expand...
Click to collapse
This is the thread you need to read: http://forum.xda-developers.com/showthread.php?t=1329360

Thanks for the useful information and for putting to rest some of my safety concerns.
Now you've wetted my appetite and I have to give it a go soon.
Sent from my GT-N7000 using xda premium

Thanks for this great guide! I haven't gotten my Note yet as I just ordered it yesterday but I have been lurking around the forums already and trying to understand how flashing roms and kernels works around here. Like someone already said before some of the guides / threads are 'a little' confusing for newcomers. I was really confused with the brick bug that people were writing about. This thread clarified things a lot for me and I believe it will help many more Note-newbies!
So, new Note community member reporting to duty here! :highfive: It's gonna be pretty neat upgrade considering from what phone I come from. Well, the Huawei at least was great step stone to android world gotta admit. I just got somewhat bored with the not so great custom scene.

SirRhor said:
This is the thread you need to read: http://forum.xda-developers.com/showthread.php?t=1329360
Click to expand...
Click to collapse
Believe me, I know about that thread.
One more question for you. Does flashing abyss kernel bring yellow triangle and raise binary counter? I've heard on one of Zedomax's channels on youtube that he recommends flashing this kernel whenever you need to move from one ROM to another.
Cheers mate!

tribalkg said:
Believe me, I know about that thread.
One more question for you. Does flashing abyss kernel bring yellow triangle and raise binary counter? I've heard on one of Zedomax's channels on youtube that he recommends flashing this kernel whenever you need to move from one ROM to another.
Cheers mate!
Click to expand...
Click to collapse
Dont worry about AbyssNote, is safe in both respects. That's the one I always use to do anything that is flashing related.
If, for some reason, you start seeing that dreaded triangle at boot, you can use TriangleAway from Chainfire on Google Play.
Sent from a GNote, hell yeah!

Thanks bro, I appreciate the effort to answer these noobish questions.
I will stay on CM9 (and CM10 when it comes) as long as is stable to use it as a daily driver. I don't like the TW interface and I don't need all that S-Pen stuff and pressure sensitivity. Apps from the Play Store are enough for me (Papyrus for example) so there's no need to stay on stock rom.

tribalkg said:
Thanks bro, I appreciate the effort to answer these noobish questions.
I will stay on CM9 (and CM10 when it comes) as long as is stable to use it as a daily driver. I don't like the TW interface and I don't need all that S-Pen stuff and pressure sensitivity. Apps from the Play Store are enough for me (Papyrus for example) so there's no need to stay on stock rom.
Click to expand...
Click to collapse
Dont worry, I'm glad I can help you.
You can try Marker and Jotter as well, they work well.
Sent from a GNote, hell yeah!

thanks
thanks for the guide.

I have the brickbug firmware also. So am I correct in assuming that if I follow these directions and flash a different GB rom that I will be okay?
Will flashing this India GB rom change my kernel to a more stable one?
And if I flash this India GB rom will it be able to update to ICS through Kies or OTA?
I'm not new to flashing as I used to rom my EVO a lot... I just haven't done it in about a year and this brickbug mess has me standoff-ish.
Sent from my GT-N7000 using Tapatalk 2

maddog2727 said:
I have the brickbug firmware also. So am I correct in assuming that if I follow these directions and flash a different GB rom that I will be okay?
Will flashing this India GB rom change my kernel to a more stable one?
And if I flash this India GB rom will it be able to update to ICS through Kies or OTA?
I'm not new to flashing as I used to rom my EVO a lot... I just haven't done it in about a year and this brickbug mess has me standoff-ish.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
If you are on GB already, you just have to root the ROM and flash CWM because the brick bug is present only on ICS kernels. 99% sure.
There are some GB Stock ROMs that you cannot root directly, so it depends.
OTA updates from Samsung to ICS I'm not sure, you should ask someone else. When I got my Note it already had ICS, so I never did an OTA update. I don't use Kies at all.
I was very weary at first too, but with the instructions above you will be fine.
Sent from a GNote, hell yeah!

I've followed the guide from OP and now I'm rockin' CM9! No problems at all.
My content on the internal memory was intact (apps data, games data, etc), it's all there and I've flashed Indian ROM and then CM9. Have I made a mistake or what?

How to replace custom kernel?

Hello, using Purity ROM + Semaphore kernel and I want to try another kernel. Maybe matr1x. What are steps? I need to flash stock kernel, than custom or I can flash custom kernel without stock?
Thank you

You don't have to flash stock first.

Just flash custom over custom...no need to flash stock

DrFredPhD said:
You don't have to flash stock first.
Click to expand...
Click to collapse
Mashed_Potatoes said:
Just flash custom over custom...no need to flash stock
Click to expand...
Click to collapse
Use caution. There are cases where flashing one kernel over another has proven to cause stability issues. Whilst for the majority of cases it's not necessary to flash stock kernel first, be prepared to do so. In other words, have a stock kernel downloaded as a back up in case you do have issues with the phone after the kernel exchange.

Mr_JMM said:
Use caution. There are cases where flashing one kernel over another has proven to cause stability issues. Whilst for the majority of cases it's not necessary to flash stock kernel first, be prepared to do so. In other words, have a stock kernel downloaded as a back up in case you do have issues with the phone after the kernel exchange.
Click to expand...
Click to collapse
I've been flashing custom over custom on my ex-Note II and everything was fine. And of course, always wipe cache

Mashed_Potatoes said:
I've been flashing custom over custom on my ex-Note II and everything was fine. And of course, always wipe cache
Click to expand...
Click to collapse
Good for you. Still doesn't mean the best advice we can give someone here is to "don't worry about it, just do it, it'll be fine". You don't know what ROM / Kernel people are coming from / going to and you certainly don't know how future ROMs / Kernels will behave. Again, there ARE examples on this forum where some kernels don't like being flashed over other non-stock kernels, problems have arisen and the only option was to flash a stock kernel first.
The best advice we can give someone on this forum is to be prepared for something to not go 100%. Like you I've never had a bad flash be-it ROM, radio or kernel but I still make sure I have a nandroid of the previous working state, stock ROM, radio and Kernel downloaded and know how to flash them before I do anything. That way, should it go wrong I'm covered.
I can not stress enough how wrong it is to just say "yeah, nothing will go wrong". It DOES go wrong and it goes wrong every day. For someone.

Mr_JMM said:
Good for you. Still doesn't mean the best advice we can give someone here is to "don't worry about it, just do it, it'll be fine". You don't know what ROM / Kernel people are coming from / going to and you certainly don't know how future ROMs / Kernels will behave. Again, there ARE examples on this forum where some kernels don't like being flashed over other non-stock kernels, problems have arisen and the only option was to flash a stock kernel first.
The best advice we can give someone on this forum is to be prepared for something to not go 100%. Like you I've never had a bad flash be-it ROM, radio or kernel but I still make sure I have a nandroid of the previous working state, stock ROM, radio and Kernel downloaded and know how to flash them before I do anything. That way, should it go wrong I'm covered.
I can not stress enough how wrong it is to just say "yeah, nothing will go wrong". It DOES go wrong and it goes wrong every day. For someone.
Click to expand...
Click to collapse
Umm, a recovery backup is something everyone should have. A backup of everything, including EFS for the clumsy ones that lose their IMEI's.
If you have a full backup of your system, it is okay to say "don't worry everything will be alright". If something goes wrong, you just do a system restore.
But that's just me, i can't be bothered with flashing stock kernels and roms all the time.

[Q] Verizon galaxy note 3 om Toubles!

Hi guys, I have a question regarding some roming stuff with the verizon version of the galaxy note 3. I am not new to roms by any means and I have been searching frantically to find one place with the complete answer im looking for. I made the early mistake of taking the OTA upgrade for KK, therefore I am currently running 4.4.2 with the NC4 build and NC4 baseband. Now while i have easily rooted my phone at this point with the towelroot. I also have had no problem getting the new 3.72 safestrap installed and running on my phone. My question now at this point is trying to figure out my next step with a new ROM I am trying install....I have been looking at all of my info to get the Hyperdrive ROM installed and I cant seem to find all the info I need in one location. Can I or can I not flash a new ROM to the NC4 baseband? I have seen some information where some people say I might be able to flash the NC2 kernal using ODIN and others say just trying to flash any ROM in general creates a black screen in which a battery pull needs to be done...yada yada.....? So in short, am I able to flash a ROM to the note 3 at this point or am I S.O.L?

sickorsane1 said:
Hi guys, I have a question regarding some roming stuff with the verizon version of the galaxy note 3. I am not new to roms by any means and I have been searching frantically to find one place with the complete answer im looking for. I made the early mistake of taking the OTA upgrade for KK, therefore I am currently running 4.4.2 with the NC4 build and NC4 baseband. Now while i have easily rooted my phone at this point with the towelroot. I also have had no problem getting the new 3.72 safestrap installed and running on my phone. My question now at this point is trying to figure out my next step with a new ROM I am trying install....I have been looking at all of my info to get the Hyperdrive ROM installed and I cant seem to find all the info I need in one location. Can I or can I not flash a new ROM to the NC4 baseband? I have seen some information where some people say I might be able to flash the NC2 kernal using ODIN and others say just trying to flash any ROM in general creates a black screen in which a battery pull needs to be done...yada yada.....? So in short, am I able to flash a ROM to the note 3 at this point or am I S.O.L?
Click to expand...
Click to collapse
Yes you can!! As long as the rom says that they support it you can. It says right here in red on the hyperdrive op-" This Rom is able to be installed on the Verizon Galaxy Note 3 On KitKat Bootloader with KK Safestrap" so make a backup with safestrap and try it out! And since it doesn't say anything about what specific one to use (I see what you are talking about) you won't have any harm with a backup. By the way the reason why a lot of roms were/are based on NC2 was because it was way more leniant than NC4 but now most if not all roms will support it. Just read the op.
Sent from my GalaxyAwesome

K03WL3R said:
Yes you can!! As long as the rom says that they support it you can. It says right here in red on the hyperdrive op-" This Rom is able to be installed on the Verizon Galaxy Note 3 On KitKat Bootloader with KK Safestrap" so make a backup with safestrap and try it out! And since it doesn't say anything about what specific one to use (I see what you are talking about) you won't have any harm with a backup. By the way the reason why a lot of roms were/are based on NC2 was because it was way more leniant than NC4 but now most if not all roms will support it. Just read the op.
Sent from my GalaxyAwesome
Click to expand...
Click to collapse
Hmmm....well I tried to do the jasmine rom and I seem to have had the same problem that quite a few people are having. I put it in slot 1, created the rom slot and such, reboots into the recovery mode on ss just fine but then it goes to a black screen as if it's off. Have to battery pull. Maybe gonna try a different rom and see where I end up.

I'm running JasmineRom on the stock slot, but I also have the NC2 kernel..
Sent from my GalaxyAwesome

K03WL3R said:
I'm running JasmineRom on the stock slot, but I also have the NC2 kernel..
Sent from my GalaxyAwesome
Click to expand...
Click to collapse
Should I try stock slot then? I used slot 1 with 3.75

You could try that (I would), or just flash the Nc2 stuff, then boot up (on stock), boot back to recovery and flash JasmineRom on stock. Those steps are just what I did and it worked for me. I'm really sorry but for the life of me that's the best I can remember about what I did. If none of that works, I'll try to install Jasmine onto a rom slot when I can.
Sent from my GalaxyAwesome

K03WL3R said:
You could try that (I would), or just flash the Nc2 stuff, then boot up (on stock), boot back to recovery and flash JasmineRom on stock. Those steps are just what I did and it worked for me. I'm really sorry but for the life of me that's the best I can remember about what I did. If none of that works, I'll try to install Jasmine onto a rom slot when I can.
Sent from my GalaxyAwesome
Click to expand...
Click to collapse
I flashed Nc2 from a post on here and still didn't work....I'm about to give up

Have you tried just making a backup and starting over from fresh stock?
Sent from my GalaxyAwesome
---------- Post added at 11:35 PM ---------- Previous post was at 11:27 PM ----------
Also ask here- http://forum.xda-developers.com/showthread.php?t=2780031
Sent from my GalaxyAwesome

You need to flash the rom after you've wiped everything, then reboot to download mode and install the unified firmware via odin. That should work.
Sent from my GalaxyAwesome

K03WL3R said:
You need to flash the rom after you've wiped everything, then reboot to download mode and install the unified firmware via odin. That should work.
Sent from my GalaxyAwesome
Click to expand...
Click to collapse
That did not work as that was the original plan of action. Only to come to a nice black screen

Okay, the dev just posted instructions in his last post on the JasmineRom thread. Check it out, it took me a while for it to work on my phone, it seems like a couple people are like us too.. Just a mix of trial and error
Sent from my GalaxyAwesome
Edit: and sorry I couldn't help so far, I don't really want to go back to stock considering this is my daily and I need a bigger sd card to make a full backup. [emoji53]

K03WL3R said:
Okay, the dev just posted instructions in his last post on the JasmineRom thread. Check it out, it took me a while for it to work on my phone, it seems like a couple people are like us too.. Just a mix of trial and error
Sent from my GalaxyAwesome
Edit: and sorry I couldn't help so far, I don't really want to go back to stock considering this is my daily and I need a bigger sd card to make a full backup. [emoji53]
Click to expand...
Click to collapse
All good! I finally got it working thanks to you saying the dev mentioned something! Jasmine up and running with no issues!

Jasmine V2
I never sign up for web sites but the Jasmine Rom is just so good I had to say thanks. Also concerning the excess power usage, I noticed that when plugged into AC charger the Android OS goes from 40% down to the 20's. Hope it helps. Again thanks to hsbadr for being a great DEV.
PS: K03WL3R I see you helping on hsbadr's forum, please convey my thanks and suggestion to him, for as I am a new member I can not post on his forum.
Thanks

Sorry it took me so long, there's an open discussion in the general/help section for jasminerom! I'm pretty sure new users can post there?

[Q] Phone refuses to boot with a rom

Hi, I've been trying to install a custom rom (at this point ANY custom rom) on my friend's phone. I have worked on several phones before, including my own sprint GS3, but this is my first time trying to work around a locked bootloader, and BOY is it a pain, haha. I'm no dev, but I would like to think that I'm pretty competent.
First a few things to note, are that the phone is currently on NI1 (Been too much of a sissy to go to NJ4 in case it screws something up, I don't even know why), it is the 16Gb version, I am using an external sd card to flash everything, and yes I am flashing loki-doki after everything.
So what I've done so far is:
- Try to install TWRP
- Find out that won't work and finally figure out I need safestrap
- Successfully install safestrap after using towelroot by ODIN-ing the NC1 kernel then going back to the NI1 kernel
- Try to flash Resurrection Remix and KToonsez kernel using a new rom-slot, and wind up soft-bricking (stuck on bootloader screen, can get to download mode)
- ODIN NB1 tar then ODIN NI1 update
- Repeat the last few steps several times because I'm too idiotic to realize that it JUST ISN'T GOING TO WORK!
- Finally find a reference to flashing the ATT kernel modules after the rom. That got me past the soft brick and safestrap screen, but I don't even see a boot animation
As of right now my sequence to successfully not soft-bricking (what an accomplishment) is to flash the rom>gapps>ATT kernel module>supersu>loki-doki>wipe dalvik/cache
Now, is it worth it having already spend a good 7 hours, just to get a custom rom? Of course not, it's not my phone and my friend isn't picky. He'd be just fine with rooted TW. However, It kills me that I don't know what's going on, so here I am lol.
TL;DR: Phone has safestrap, is rooted, but any time I flash a rom it gets past the boot loader/safestrap screen and never shows a boot animation, or anything past that. Can anyone help figure out what's going on please?
Thanks in advance.

You can only flash touch wiz based roms with safestrap and you can't flash kernels with safestrap. That's been your problem with soft bricking.
Edit, see this for roms you can flash http://forum.xda-developers.com/showthread.php?p=53758227
Sent from my Nexus 9 using XDA Free mobile app

http://forum.xda-developers.com/showthread.php?t=2616221

Thanks guys. I thought I read through the whole thread, but there is so much information, it's pretty scattered, I must have missed the thing about only TW roms working.
Now a few more questions:
1) Is it worth updating to NJ4? The phone is new and doesn't have any app data or anything that would be missed by updating. I see quite a few roms in 4.4.4, but it looks like most of them are AOSP based, which leads me to my next question...
2) Is there a way to get AOSP roms to work? I see all of these AOSP based roms, obviously for this phone, but it would be pointless to make them if they don't work.

Masterjuggler said:
Thanks guys. I thought I read through the whole thread, but there is so much information, it's pretty scattered, I must have missed the thing about only TW roms working.
Now a few more questions:
1) Is it worth updating to NJ4? The phone is new and doesn't have any app data or anything that would be missed by updating. I see quite a few roms in 4.4.4, but it looks like most of them are AOSP based, which leads me to my next question...
2) Is there a way to get AOSP roms to work? I see all of these AOSP based roms, obviously for this phone, but it would be pointless to make them if they don't work.
Click to expand...
Click to collapse
It wouldn't hurt to update to nj4. But it's not going to help you either. Only phones on mdb or mdl bootloader can flash non touch wiz based roms using loki. And you can't go back to those bootloaders
Sent from my Nexus 9 using XDA Free mobile app

Alright then. Hyperdrive looks pretty good, I'll try that along with Ktoonsez kernel. I'll report back later to let you know how it goes. Thanks again!

Masterjuggler said:
Alright then. Hyperdrive looks pretty good, I'll try that along with Ktoonsez kernel. I'll report back later to let you know how it goes. Thanks again!
Click to expand...
Click to collapse
Again, you can't flash a kernel in safestrap
Sent from my Nexus 9 using XDA Free mobile app

Oh, I get it now. That didn't quite register before. So just to confirm, after I flash the rom (which already has its own custom kernel included), I still need to flash the stock ATT kernel, correct?

Flash the rom, super su, and the att module for your base. Hyperdrive is a very good rom, good luck. Also the rom doesn't include a kernel, your original kernel stays put. That's why only tw roms work, because your new rom has to be compatible with the kernel already on your phone.

Just reporting in, I now have the phone up and running using Hyperdrive Rom. Thanks for the help!
I actually had a problem where it would not shut down correctly, but found out it was because I was installing the rom in a rom-slot in safestrap. As soon as I tried the stock rom slot, it worked flawlessly.

[GUIDE] How To Root SM-N9208

Hello Friends
I have been searching the internet for days on how to root the Note 5 N9208 dual sim and finally found something that seem stable.
DISCLAIMER: I am by no means taking credit for this root method, I am just sharing what I found because I know how hard the information can be to find on the internet. As you should already know, with flashing there is always a risk so you are always responsible for you own device
1. First you are going to want to enable OEM Unlock and USB debugging in the developer option.
2. Go to Samsung app store and get the CROM service app. (this is needed so you can flash custom roms, on some phones you won't be able to flash anything if you don't do this step)
3. Download Permissive kernel (from xiaolu) for N9208 with auto root: N9208-TW-Root (0909) .tar flash it with Odin3.10.7 (extract tar-file from zip, put it in section and flash AP)
At this point you should now have root, beyond this step will explain how to get TWRP recovery.
4. Official TWRP for Samsung Galaxy Note 5 DUOS you can found here ... (download tar-file, put it in AP section and flash with Odin3.10.7).
This information was accumulated by searching the web. My thanks goes out to all developers who help me to arrive at a root solution. If you, a developer come here and see a violation that I overlooked please inbox me and I will rectify it right away Thanks again

Thanks for the guide. Do you have more information on the kernel?

Elmar1801 said:
Thanks for the guide. Do you have more information on the kernel?
Click to expand...
Click to collapse
Sad to say, I didn't find much information on the web about the performance of this kernel. It just showed up as a way to gain root.
Not being about to accumulate any data on the kernel I kinda was back and forth in my mind if I should use it or not. after hours of thinking and really wanted root I decided to give it a go in a all or re-flash moment(nothing).
Turn out to be pretty good with no change in performance vs the stock kernel. Once flashed I saw superSU there installed and ready to go.
Now I was concern about the random reboots I heard about with other kernels but I have been using the phone for 3 days now and I haven't encountered any lags, no reboots, no drop of signals or calls. I have not yet installed any games on my phone so I don't know how it will be with heavy usage of that nature.
If you decide to give this a try please post any findings of abnormalities here. Thank you

dreskullz said:
Sad to say, I didn't find much information on the web about the performance of this kernel. It just showed up as a way to gain root.
Not being about to accumulate any data on the kernel I kinda was back and forth in my mind if I should use it or not. after hours of thinking and really wanted root I decided to give it a go in a all or re-flash moment(nothing).
Turn out to be pretty good with no change in performance vs the stock kernel. Once flashed I saw superSU there installed and ready to go.
Now I was concern about the random reboots I heard about with other kernels but I have been using the phone for 3 days now and I haven't encountered any lags, no reboots, no drop of signals or calls. I have not yet installed any games on my phone so I don't know how it will be with heavy usage of that nature.
If you decide to give this a try please post any findings of abnormalities here. Thank you
Click to expand...
Click to collapse
i used the same process and files on my 9208 to achieve root. going on 3-days with stock ROM, the root kernel and latest xposed for TW and haven't had one reboot.

cortez.i said:
i used the same process and files on my 9208 to achieve root. going on 3-days with stock ROM, the root kernel and latest xposed for TW and haven't had one reboot.
Click to expand...
Click to collapse
That's awesome
I thought xposed for our phone was only possible with Deodexed roms? if this is possible for our Odexed stock rom can you kindly point me into the direction to get this done?

dreskullz said:
That's awesome
I thought xposed for our phone was only possible with Deodexed roms? if this is possible for our Odexed stock rom can you kindly point me into the direction to get this done?
Click to expand...
Click to collapse
Enjoy . i thought the same; be sure to get V74 for arm64 devices.

cortez.i said:
Enjoy . i thought the same; be sure to get V74 for arm64 devices.
Click to expand...
Click to collapse
Thank you I will go give this a try right now

dreskullz said:
Sad to say, I didn't find much information on the web about the performance of this kernel. It just showed up as a way to gain root.
.........
If you decide to give this a try please post any findings of abnormalities here. Thank you
Click to expand...
Click to collapse
Thanks for your reply. I will give it a go.

i am giving this kernel a try also.....to many random reboots on another one

edwardob said:
i am giving this kernel a try also.....to many random reboots on another one
Click to expand...
Click to collapse
Let us know about any abnormalities you find just in case we have missed something

No problems at all. No reboots or lags.

Nice guide for obtaining root!
I already have rooted my Note 5 using the SpaceX kernel, but as some of you know this kernel has the random reboot issue.
What would be the procedure for me to flash this kernel. Can I just flash over the current SpaceX kernel or would I have to go another route?
Appreciate the help.

daffie said:
Nice guide for obtaining root!
I already have rooted my Note 5 using the SpaceX kernel, but as some of you know this kernel has the random reboot issue.
What would be the procedure for me to flash this kernel. Can I just flash over the current SpaceX kernel or would I have to go another route?
Appreciate the help.
Click to expand...
Click to collapse
just the same way...directly over old o one

edwardob said:
just the same way...directly over old o one
Click to expand...
Click to collapse
Cheers for the quick help! So just Odin flash this kernel directly over my current setup...will get right to it
Flashed the kernel and rebooted...all seems well. Now further testing and hopefully no weird issues like random reboots and/or deep sleep bug.

and We still don't know where it came from ??
but it Works
I seen it on a russian site thats all I know
but it works !!

Indeed...it's all rather strange No dev, no nothing...but it does work :good:
I got 4% battery usage in some 10 hours standby and that's pretty decent in my book.
Performance seems on par with stock kernel. Now for another couple of days of further testing to see if it holds up...(no random reboots and such).

I was at about 6%at 7hrs.....but I have one drive syncing. ..but before I had 15-20%....
and no reboots and I am rooted!!!!

edwardob said:
and We still don't know where it came from ??
but it Works
I seen it on a russian site thats all I know
but it works !!
Click to expand...
Click to collapse
lol yup, there is no data at all on this kernel as far as I can search. one thing I can say for sure is that its doing very well in terms of performance. I play games, listen to music, make calls on both sims, send emails and have dual whatsapp going all day. with all that activity I manage to get 13 hours out of the phone, I plug in at 18%. to me thats good. What do you guys think?

l think we have a rooted in 9208 dual sim that doesnt reboot and works fine
curiousty leads me toWonder Where it came from and whats been done to it

Guys, will this work with the hong kong version (9200)?
Sent from my SM-N9200 using Tapatalk