N7000 Easily and Safely Root Stock ICS without Odin or CWM.Zip - Galaxy Note GT-N7000 General

Pretty much a redundant thread, seeing as everyone is doing it now. (But not before I ported the method from SGS II by Phil 3759 http://forum.xda-developers.com/member.php?u=4666971 )
Still makes interesting reading though.....

Thank you for your feedback and link here
But your post links are broken as you copy pasted and forum shortcuts them
So, original thread here:
http://forum.xda-developers.com/showthread.php?t=1746794
Also linked in my signature
Please, ask questions there, I will not monitor this thread for support, so cannot answer questions

Phil3759 said:
Thank you for your feedback and link here
But your post links are broken as you copy pasted and forum shortcuts them
So, original thread here:
http://forum.xda-developers.com/showthread.php?t=1746794
Also linked in my signature
Please, ask questions there, I will not monitor this thread for support, so cannot answer questions
Click to expand...
Click to collapse
Thank you - (fixed it)

shoey63 said:
Possibly the easiest method yet! (Unless you want to PC Odin custom kernel and use potentially dangerous Triangle away to reset counter and get rid of yellow triangle)
1) Download this file:- http://forum.xda-developers.com/attachment.php?attachmentid=1256643&d=1344771266 (comes from this thread - http://forum.xda-developers.com/showthread.php?t=1746794 Kudos to Phil 3759)
2) Copy to external SD card
3) Reboot into stock recovery and select "apply update from external storage"
4) Select "CWM_Root_SuperSU.0.94-Busybox.1.20.2-S2-signed.zip" and wait for Superuser and Busybox to install
5) Go back and reboot system.
Done! You now have fully rooted stock ICS (works on 4.04). Don't forget you are also on stock kernel so NO WIPING!!!
If u want custom kernel, use mobile Odin afterwards.
(BTW dont forget to open superSU after reboot to update binary)
Click to expand...
Click to collapse
That's not rooting - that's rooting AND installing busybox. Sometimes installing busybox can cause problems on a device.
To root, it's simple:
Go to Chainfire's SuperSU thread
Download the latest "CWM-flashable" version
Put on external SD
Flash from recovery
This WON'T also add busybox which can sometimes cause problems.
The reason this works: With ICS updates for I9100/N7000/I777/probably others, Samsung started permitting ZIPs signed with testkeys to be flashed from recovery.
This does not appear to work on newer devices - fails on N8000/N8013 for example.

Hello,
Does this mean if I do this to my note running N7000DDLR6 (don't if its required to mention this), I'll be able to under-clock it and remove system apps without anything more? and that It will be totally safe?
what precautions need to be taken while doing this and after that?
Regards
Sujai

sujaishukla said:
Hello,
Does this mean if I do this to my note running N7000DDLR6 (don't if its required to mention this), I'll be able to under-clock it and remove system apps without anything more? and that It will be totally safe?
what precautions need to be taken while doing this and after that?
Regards
Sujai
Click to expand...
Click to collapse
Ofcourse not, after rooting you are not safe anymore.
If you delete something vital your phone won't boot anymore.
So only root after reading and understanding what you are doing or intent to do...

Entropy512 said:
That's not rooting - that's rooting AND installing busybox. Sometimes installing busybox can cause problems on a device.
...
This WON'T also add busybox which can sometimes cause problems.
Click to expand...
Click to collapse
It can be true under some circumstances, but:
- Many good applications will not run without busybox installed in /system/xbin. Some can chose to go without them, others no. Until developers start including their busybox under their app folder (like Titanium Backup), there will be no other choice if you do need those applications
- Without busybox, you loose a lot of commands under the terminal console. End users do not care, until they need debugging...
- CWM recovery installs busybox in /sbin, it is even completely built into his recovery. So, every time you have cwm installed, you end up with busybox (Most if not all custom kernels/ROMs are concerned that way, include CF-Root kernels...)
- Installing busybox from a market installer is a real mess while installing it through a recovery script can be fully undone

Entropy512 said:
...
Click to expand...
Click to collapse
I'm sorry, but wasn't the CWM.zip the problem for fast few weeks? How come out of nowhere it's "OK" to install the flashable/temporary CMW and it is the Busybox causing the problem?
Please make it clear - is it the CMW.zip counting as "Unsafe" or it is something else?

Spo0f said:
I'm sorry, but wasn't the CWM.zip the problem for fast few weeks? How come out of nowhere it's "OK" to install the flashable/temporary CMW and it is the Busybox causing the problem?
Please make it clear - is it the CMW.zip counting as "Unsafe" or it is something else?
Click to expand...
Click to collapse
The root methods mentioned above can be done from stock recovery skipping the cwm temporary step
Busybox can cause issues with some applications that rely on a generic busybox copy under /system/xbin
This is caused by the fact that each busybox build can have different valid commands. The application cannot know if the commands it needs are supported unless it is bundled with its own busybox copy. It will rely on the compiler of busybox to implement the commands.
Until now, I never encountered such problems with last busybox, but, it doesn't mean one of your apps will never behave strangely...
This is a problem related to the application its self, not busybox specifically

So to summarize this in clear words for note users it should be:
-Note users can easily get root only by flashing supersu or superuser (CWM flashable zips) through stock rom recovery directly,no need for CWM.ZIP at all.
-Note users can also get root + busybox by flashing CWM.ZIP old safe non touch v 4.x through stock recovery first,then to flash supersu/superuser+busybox zip through the temp CWM 4.
Am i right guys? plz do confirm...
Also what about wiping now through temp CWM4 with ICS rooted stock kernel? is it safe now??
↖(^▽^)↗ Sent from Rego Galaxy Note ↖(^▽^)↗

Entropy512 said:
That's not rooting - that's rooting AND installing busybox....
Click to expand...
Click to collapse
OK thanks, forgot to mention that, I'll amend OP

Already answered

eng.rego said:
So to summarize this in clear words for note users it should be:
-Note users can easily get root only by flashing supersu or superuser (CWM flashable zips) through stock rom recovery directly,no need for CWM.ZIP at all.
-Note users can also get root + busybox by flashing CWM.ZIP old safe non touch v 4.x through stock recovery first,then to flash supersu/superuser+busybox zip through the temp CWM 4.
Am i right guys? plz do confirm...
Also what about wiping now through temp CWM4 with ICS rooted stock kernel? is it safe now??
↖(^▽^)↗ Sent from Rego Galaxy Note ↖(^▽^)↗
Click to expand...
Click to collapse
All is ok, except wipe
I cannot certify it is safe. Entropy512 which is involved in CM dev said it is safe for CWM4. I never tested, cannot confirm
Also, CWM6 is still unknown state on stock kernel, until some dev can confirm it

eng.rego said:
So to summarize this in clear words for note users it should be:
-Note users can easily get root only by flashing supersu or superuser (CWM flashable zips) through stock rom recovery directly,no need for CWM.ZIP at all.
Click to expand...
Click to collapse
Correct.
eng.rego said:
-Note users can also get root + busybox by flashing CWM.ZIP old safe non touch v 4.x through stock recovery first,then to flash supersu/superuser+busybox zip through the temp CWM 4.
Click to expand...
Click to collapse
Haven't tried it that way because it involves an extra unnecessary flash. Anyway best to steer clear of any CWM.zip. I bricked my note wiping on touch version. Why use it if u don't have too?

but ultimately we have to used odin to flash a safe kernel after this proceedure.
can we use this to 'cure' the 'partial root' phenomenon many face after flashing even recent ics custom roms ?
i admit installing busybox from market successfully can be a real pain .....
we need busybox for many things like supercharger script etc etc
some apps wont work if you dont have the upgraded version of bb

Some like to stay on stock Ics kernel because of stability. (only unsafe if wipes are performed on them) If u want custom kernel then obviously mobile odin pro/lite is the way to go. At least this way u dont raise flash counter and then have to use potentially dangerous triangle away app. As far as "partial root" goes - not sure. It will install SuperSU. Just open it to update binary and uninstall any other superuser apps that are already on phone
Sent from my GT-N7000 using xda app-developers app

Let me get this straight:
The "official" root thread for Note [02Feb12]How to Root/Unroot Samsung Galaxy Note + CWM says this:
Using CWM.zip (temporary/Touch recovery)method to root is said to be unsafe by entropy, and till safe release don't use it
Read This http://forum.xda-developers.com/show....php?t=1810954
Click to expand...
Click to collapse
Now there is new release which is CWM 6.
Is the old method safe with the new release?

No need for ANY CWM.zip (safe or not). Just flash file in OP on stock kernel recovery from external sd card. Job done .
Sent from my GT-N7000 using xda app-developers app

Yes... Can confirm this has worked for me... Followed instructions in OP, and copied the Uninstaller to my SD Card in the even that I need to return the phone... Flashed in Stock Recovery, rooted and done..
Thanks a million for this...:good:

New Procedure updating to My this thread in 1 hr ( I am working on it)
http://forum.xda-developers.com/showthread.php?t=1329360
new method based on What Entropy have guided us few post back
No need to use CWM at all
No need to flash SUperSU busybox installer (as Entropy said this can cause problem)

Related

XXLPH[3/10] Can't install from market/Move app to SD/Restore Titanium Backup-SOLUTION

Do you face problem moving app to SD card!
Do you have problem restoring from Titanium Backup!
Do you face problem installing some apps from Market!
It seems the problem happened after rooting "CF-Root-SGS2_XX_OXA_LPH-v5.2-CWM5.tar" ; Always thanks to (Chainfire)
NEW SOLUTION: Siyah Kernel ICS-(Retouched) 3.0alpha2-LPH
I've just installed Siyah Kernel ICS and everything working fine with me
Please check and update thread if you face any problem.
(Always, Don't forget to backup)
DOWNLOAD LINK: http://gokhanmoral.desean.net/siyahkernel/v3.0/ICS-Only-For-Samsung-ROMS-Not-CM9/siyah3-alpha2.tar
Full details of Siyah Kernel ICS link: http://www.gokhanmoral.com/gm/2012/03/08/siyahkernel-ics-retouched-3-0alpha2-lph
Also, you can use EXTweaks from market: https://play.google.com/store/apps/details?id=com.darekxan.extweaks.app
__________________________________
OLD SOLUTION:
Well, Here is two steps solution: Thanks to (donalgodon)
First:
Flash zImage of LPH Kernel original* (by CWM Manager - Flash Kernel**).
. -phone will reboot after flashing kernel
Second:
Flash zImage of LPH CF-Root LPH v5.2 kernel* (by CWM Manager - Flash Kernel**).
. -phone will reboot after flashing kernel
* zImage (LPH Original + LPH Root Kernels) download link = www.mediafire.com/?vw8xib282b2pg1i
** How to video = http://youtu.be/ug4c2oG9LBs
That's all........
- Super user is working.
- CWM Manager is working.
- Moving app to SD Card is working.
- Restoring from Titanium Backup is working.
- Installing apps from Market (such as Ant Smasher game) is working.
Hope I added helpful solution.
great its working now good work bro
NOMIOMI said:
great its working now good work bro
Click to expand...
Click to collapse
You are most welcome
thnks its working now good work
kiriakos1963 said:
thnks its working now good work
Click to expand...
Click to collapse
Glad it works with you
this is the only workaround possible but one drwaback would be if you want cwm recovery again, you have to flash the cf root tar file via odin again
Please remove
Is this not the same workaround Chainfire has been discussing weeks ago?
http://forum.xda-developers.com/showpost.php?p=22138788&postcount=4211
Chainfire said:
Ok, so now I've tested a lot of things, a lot of tries, I'm not sure if it sticks in my head correctly.
I can only get the SD problem when transationing from official kernel + 0 counter to unofficial counter.
Afterwards, it seems flashing back the official kernel (triangle disappears) with ODIN, then flashing back CF-Root with CWM app or Mobile ODIN (preferred) solves the issue for me, every time.
I've also seen it appear/disappear with change of signatures, and then I couldn't reproduce the problem anymore, but the above procedure seems to work.
Click to expand...
Click to collapse
crachel said:
Is this not the same workaround Chainfire has been discussing weeks ago?
http://forum.xda-developers.com/showpost.php?p=22138788&postcount=4211
Click to expand...
Click to collapse
Yes, it is, but people are still asking this question without bothering to search(or don't know the terms so are unable to find) and the answer is buried under a few pages of posts.
Maybe this thread is necessary for those people but this has been discussed before so your call.
I did and it works. Thanks.
bala_gamer said:
this is the only workaround possible but one drwaback would be if you want cwm recovery again, you have to flash the cf root tar file via odin again
Click to expand...
Click to collapse
I did not understand (maybe because my english is terrible eheh).
Now, with this method, I have my phone rooted but stock recovery. Is there a way to get cwn recovery and no sd problem?
whats with people rating this thread down. sigh...
Mate thank you so muchGave you 5 stars.Flashed the zImage and got all my apps finally over to the SD as the LP6 wouldnt flash on my version of ROM for some reason.If I need to Ill flash the CF-Root back for a CWM backup.Well done.
I dont quite follow this either. I have flashed the zImage of original XXLPH kernel, but now what??
Do I need to flash the kernal again via Odin to get CWM back fully operational??
I have a diff. Firmware, CheckRom6 & Redpill Kernel 1.3. And despite of Download Counter 0 I have the problem with Titanium some apps' not flashing back, too. (had the problem already with CheckRom4 / Syiah, too).
nickmax1 said:
I dont quite follow this either. I have flashed the zImage of original XXLPH kernel, but now what??
Do I need to flash the kernal again via Odin to get CWM back fully operational??
Click to expand...
Click to collapse
Just flash the CF-Root kernel's zImage file via the CWM app and you will get root & CWM working again.
akbarhash said:
Yes, it is, but people are still asking this question without bothering to search(or don't know the terms so are unable to find) and the answer is buried under a few pages of posts.
Maybe this thread is necessary for those people but this has been discussed before so your call.
Click to expand...
Click to collapse
Even though got to solution by try & error; Yes, it is there in the deep of long thread.
Just want to put it up in simple well detailed steps since many people facing such problems and asking for.....
I followed the advice in Chainfire's very long thread after finding it here, and it worked for me.
I used this procedure:
1. rooted via CF-Root using Odin.
2. flashed the old bootloader using Odin.
3. reset flash counter via Jig.
4. flashed the ICS bootloader using Odin.
5. flashed the stock kernel using CWM app.
6. flashed the CF-kernel using CWM app.
SD works fine and root is retained.
ahh thank you!
thanks, this works fine for me.
you mean after flashing the zimage kernel you need to flash the http://download.chainfire.eu/147/CF-Root/SGS2/CF-Root-SGS2_XX_OXA_LPH-v5.2-CWM5.zip
to get CWM working again?

Information for those got paritial root after flashing from GB rom

Any fully rooted GB rom before process the upgrade to Criskelo or Cassies ICS Rom please install SuperSU (Chainfire) first and those already done please click and update if available and somehow will update the binary , if successful, you can now flash the ICS and gain full root. otherwise partial root will most likley occur.
Once flashed the new ICS rom then update the the SuperSU again. Then you are done with fully rooted rom without issues.
I have tried twice and worked fine. it was very painful to have partial root and flashing CF root LQ3 with mobil odin did not resolve my partial root problem
I personally like Cassies rom and speedmod together. Working very well.
I Hope these help.
help!
husky168 said:
Any fully rooted GB rom before process the upgrade to Criskelo or Cassies ICS Rom please install SuperSU (Chainfire) first and those already done please click and update if available and somehow will update the binary , if successful, you can now flash the ICS and gain full root. otherwise partial root will most likley occur.
Once flashed the new ICS rom then update the the SuperSU again. Then you are done with fully rooted rom without issues.
I have tried twice and worked fine. it was very painful to have partial root and flashing CF root LQ3 with mobil odin did not resolve my partial root problem
I personally like Cassies rom and speedmod together. Working very well.
I Hope these help.
Click to expand...
Click to collapse
hi i have a similar problem: my original firmware was gingerbread 2.3.6 lc1 acording to dr. ketan guide fi only way to get root was a downgrade wich i did i flash trought odin the kj1 2.3.5 pre rooted rom everything went well got full root only problem was the null null keyboard besides that superuser updated binaries just fine...
The trouble started when i flashed abysskernel to wipe completely and flashes kingdroid v7 trought the aroma installer , make my choices and the kernel that i picked was speedmod k11-3, restarted... room boted just fine... but i realized superuser app was changed too super su , i open it, tried to update binaries but failed , tried to install new busybox trought ericcson app and failed also... so then i tried to flash trough mobile odin the cf kernel but that was a failure and it end with loosing root,,,
now im on kingdroid v7 supersu updated fine , but i still cant write or mount system files , still on speedmod k 11-3... will doing these step you wrote end in gaining full root again on the rom that i have?
thank u for ur answer!:fingers-crossed::fingers-crossed:
if you choose CF root in aroma while installation you boot up fully rooted,
once booted check your root situation, update binaries if need be , then you can change kernel to your preference
Solution
After update to ICS using mobile odin, if you find partially rooted, i think SuperSU busyboxinstaller,zip still work from recovery and will update inary and will get full root.
@Vailord
Wat you have need to use abyss once you are on safe GB ROM ?
There is no such thing as partial root...
it's like being married, you are married or you are not,
there is no such thing a being partially married
friedje said:
There is no such thing as partial root...
it's like being married, you are married or you are not,
there is no such thing a being partially married
Click to expand...
Click to collapse
agreed ,partial root is a myth ,the only thing causing the so called "partial root" is a corruption in the system partition causing it to refuse to mount\unmount
the solution is to flash a kernel that does not automatically mount system partition during recovery (like CM9 kernels) ,and then format system partition and then flash\ nandroid restore your ROM.
other than that partial root is a myth!
source: Entropy512
friedje said:
There is no such thing as partial root...
it's like being married, you are married or you are not,
there is no such thing a being partially married
Click to expand...
Click to collapse
It is like 'commited'
It allows you to use many appl like titanium but dont allow to mount system n that's why it is partially rooted.
Sent from my GT-N7000 using xda premium
true, being on a custom rom and saying we dont have root , its a self- contradictory statement
but the term is being used now for want of a better one......

Confusing Root Status

Hello everyone,
I'm kind of new here in the forum but I have been around as a guest for a while. I own a Tab 10.1 3G and followed the instructions in the forum to update my tab to 4.0.4 XXLQ8 successfully. I'm so thankful to you guys.
But when I tried to gain root access after the update. It's unrooted again. It took me long enough with a little help from my friend to be able to flash CWM into the tab to be able install .zip files in the /sdcard again. But something is still wrong. With all the files I found in the forum, none has successfully given a proper root access (even though I followed the instructions exactly and did all the things needed). The thread is here:
http://forum.xda-developers.com/showthread.php?t=1807219
I have attached with this post 3 screenshots just to try to tell you what is going on.
1st image is BusyBox: It says my device has Root. And I have SuperUser installed in the drawer.
2nd image is SuperUser Fixer Update blah blah blah saying gaining root access failed.
3rd image is SDMaid telling me my device doesn't have root access.
So I can safely concluded that it is NOT ROOTED. BUT WHY? I did correctly everything.
I would like to know your opinion about this matter
Thank you so much
This is what I would say the best thing to do is.
1. Uninstall all su & busybox apps & preferably factory reset.
2. If your CWM version 6.x you can ignore this. Otherwise download the newest recovery for your tab from droidbasement and install using Odin. This is to make sure you don't accidentally invoke the "super bug" and brick your tablet
3. Make sure to download the zip in the sticky by Sockmonkey. Extract it and put the small flashable zip on to your tab
4. Install the root zip through Cwm. Now test by checking an app that needs root, like Titanium Backup.
To be honest it's probably easiest that if you want a completely stock rom with root just install something like tasks or toldos instead.
Sent from my GT-P7510 using XDA Premium HD app
Problem solved.
scaryshark said:
This is what I would say the best thing to do is.
1. Uninstall all su & busybox apps & preferably factory reset.
2. If your CWM version 6.x you can ignore this. Otherwise download the newest recovery for your tab from droidbasement and install using Odin. This is to make sure you don't accidentally invoke the "super bug" and brick your tablet
3. Make sure to download the zip in the sticky by Sockmonkey. Extract it and put the small flashable zip on to your tab
4. Install the root zip through Cwm. Now test by checking an app that needs root, like Titanium Backup.
To be honest it's probably easiest that if you want a completely stock rom with root just install something like tasks or toldos instead.
Sent from my GT-P7510 using XDA Premium HD app
Click to expand...
Click to collapse
I found a way, finally.
This is a video instructions how to root galaxy tab 10.1 (4.0.4)
Youtube video name: Hi-Tik How TO : Root GALAXY Tab 10.1 (Android 4.0.4)
It has been there since August 23rd but I don't know how come I couldn't find it earlier. Maybe I search the wrong keywords.
Anyway, the correct Root .zip file in there really did solve the problem and now I'm running SuperSU with root access

[Q] CMW success, SU fail :(

Hello, first time poster. I recently tried rooting my phone using CWM method. I'm running sph-l720 with software version vpaumf9 and android version 4.2.2. I installed CWM (this version SPH-L720 OUDHS Recovery) with odin with success. Then flashed SuperUser v.099. Everything went smooth until I opened up super user and tried to install binaries and it says "Install failed". I'm wondering if I didnt have the wrong beginning firmware and i needed to (but didnt) install that pre-kernel. I'm also wondering if I have to download the original firmware and have to flash to stock in order to "unroot" even though I didnt finish the SuperUser process, or is their a way to delete the super user app and try to install it again using the same CWM i have already on the phone. I hope this isn't confusing. I'm not a complete novice to rooting, but no expert. I rooted my galaxy s2 but went to Iphone for a while, but now I'm back and a little dissapointed with myself at this fail. Any suggestions? Do i have to go to stock first? Was I using the wrong files for my initial firm ware and need the pre kernel? Am I blabbering on? (yes) Thanks in advance.
jonraymond21 said:
Hello, first time poster. I recently tried rooting my phone using CWM method. I'm running sph-l720 with software version vpaumf9 and android version 4.2.2. I installed CWM (this version SPH-L720 OUDHS Recovery) with odin with success. Then flashed SuperUser v.099. Everything went smooth until I opened up super user and tried to install binaries and it says "Install failed". I'm wondering if I didnt have the wrong beginning firmware and i needed to (but didnt) install that pre-kernel. I'm also wondering if I have to download the original firmware and have to flash to stock in order to "unroot" even though I didnt finish the SuperUser process, or is their a way to delete the super user app and try to install it again using the same CWM i have already on the phone. I hope this isn't confusing. I'm not a complete novice to rooting, but no expert. I rooted my galaxy s2 but went to Iphone for a while, but now I'm back and a little dissapointed with myself at this fail. Any suggestions? Do i have to go to stock first? Was I using the wrong files for my initial firm ware and need the pre kernel? Am I blabbering on? (yes) Thanks in advance.
Click to expand...
Click to collapse
Grap CF-Autoroot from here
Follow the instructions here:
Boot back to phone. Open up SU and update binaries.
Then
Go to Playstore and download/install GooManager
Open GooManager and then press the 'menu' button (capicitive button next to Home Button) and choose to install recovery (I like TWRP).
Then let it do it's thing.
If you'd like a real easy way to get 'into recovery mode' from the phone I use the Quickboot app
Also make sure that if you are going to flash ANY ROMs you follow the instructions the developer suggests - many suggest specific recoveries be used
leaderbuilder said:
Grap CF-Autoroot from here
Follow the instructions here:
Boot back to phone. Open up SU and update binaries.
Then
Go to Playstore and download/install GooManager
Open GooManager and then press the 'menu' button (capicitive button next to Home Button) and choose to install recovery (I like TWRP).
Then let it do it's thing.
If you'd like a real easy way to get 'into recovery mode' from the phone I use the Quickboot app
Also make sure that if you are going to flash ANY ROMs you follow the instructions the developer suggests - many suggest specific recoveries be used
Click to expand...
Click to collapse
thank you! do i need to do anything before i do this? (Like using odin to revert back to stock?)
i ask because i already have CWM installed
I did the auto root, and open SuperSU and it doesnt ask to update binaries...does that mean it is already done. I didnt find the option in the settings.
jonraymond21 said:
thank you! do i need to do anything before i do this? (Like using odin to revert back to stock?)
i ask because i already have CWM installed
I did the auto root, and open SuperSU and it doesnt ask to update binaries...does that mean it is already done. I didnt find the option in the settings.
Click to expand...
Click to collapse
As long as your on some kind of TW/Stock based ROM you should be Okay.
However if you want to go back to straight (AND ROOTED) stock you can use one of rwhilco12's 'one-click' restores.
The one click downloads as a zip. decompress and then run the one -click. If you've never run a oneclick read here
It will give you a stock ROM, rooted, MF9 Modem, Stock recovedry, and Stock kernel. You'll then have to use GooManger method to get custom recovery.
leaderbuilder said:
As long as your on some kind of TW/Stock based ROM you should be Okay.
However if you want to go back to straight (AND ROOTED) stock you can use one of rwhilco12's 'one-click' restores.
The one click downloads as a zip. decompress and then run the one -click. If you've never run a oneclick read here
It will give you a stock ROM, rooted, MF9 Modem, Stock recovedry, and Stock kernel. You'll then have to use GooManger method to get custom recovery.
Click to expand...
Click to collapse
man thanks so much. so i definitly got super user access. I'm about to do the goo manager. since you suggested the twrp i think i'm going to try that. since i have CWM recovery installed, do u think that will create any issues if I go to install TWRP from goo manager
actually i googled and it seems that goo manager will seamlessly overwrite cwm. sorry for the questions before searching. appreciate the help. i almost didn't come on here, which would of lead me to reverting to stock, doing cwm again, then being upset that i needed twrm for most roms lmao. I owe u one. If u ever need to learn how to make bad decisions, just shoot me a pm. I got u covered.
No it will just replace it.
I actually (and many around here too) prefer TWRP 2.5.0.2.
You can download the zip for that here, boot to recovery you have now (CWM) and then install that. Or use Goo to install lates TWRP and boot to recovery and then install zip and choose the 2.5.02 you downloaded and then save to your sd card
scratch what i posted here. I ended up having to download ROMmanager and update CWM, then used CWM to install the zip you provided me. thanks so much man. Do you have a favorite stable ROM you recommend using TWRP. I value your advice
jonraymond21 said:
scratch what i posted here. I ended up having to download ROMmanager and update CWM, then used CWM to install the zip you provided me. thanks so much man. Do you have a favorite stable ROM you recommend using TWRP. I value your advice
Click to expand...
Click to collapse
Glad you got it.
As for ROMs you really have to try them out for yourself. There are some really great TW ROMs ; Sacs, negalite, triforce and others. For CM/AOSP there are a whole bunch to choose from. I mess with just about all of them. But my daily driver has to be one hundred percent working and reliable so for that I'm usually on a stock debloated and modified TW ROM. Take some time to read through the OPs of the devs and just as importantly through the follow up posts to see what works what doesn't ahs how to fix or get what you need.
Good luck
Sent from my SPH-L720 using XDA Premium 4 mobile app
leaderbuilder said:
Glad you got it.
As for ROMs you really have to try them out for yourself. There are some really great TW ROMs ; Sacs, negalite, triforce and others. For CM/AOSP there are a whole bunch to choose from. I mess with just about all of them. But my daily driver has to be one hundred percent working and reliable so for that I'm usually on a stock debloated and modified TW ROM. Take some time to read through the OPs of the devs and just as importantly through the follow up posts to see what works what doesn't ahs how to fix or get what you need.
Good luck
Sent from my SPH-L720 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Try this Rom!
http://forum.xda-developers.com/showthread.php?t=2327692&page=43
works great!

Magisk

Dear advisors,
Iam using stock samsung note 4 SM-910G. Snapdragon 805. Android 6.0.1. Marshmallow. I need advise on to how to install magisk on my device. Can it be done? Appreciate on a step by step instruction on how do i install it.
I don' think this is the right place for this, but it't not my job to decide.
Anyways, which ROM are you using? Are you on stock TouchWiz?
No roms its just stock. Ive rooted on my note 2 previously but i wanna know how on note 4 but rooting via magisk.
So where do i need to post this question?
Firdhaus81 said:
No roms its just stock. Ive rooted on my note 2 previously but i wanna know how on note 4 but rooting via magisk.
So where do i need to post this question?
Click to expand...
Click to collapse
You should've asked in the Q&A section. Thread moderators will probably move this one as soon as they notice, don't worry, you're a relatively new user so you can't know everything yet.
By the way, you can't root with Magisk, if you're not rooted with other methods, because your bootloader is still locked and neither stock recovery or Odin would allow it. You first need to get root access by using some specific software such as ChainFire Autoroot. There are some guides available, but first you have to search for the zip file on the ChainFire website (link), pay attention to the model and check if Odin is included with the package. If it's not, just do a Google search for a fairly recent version. When you have everything you need, use this guide to root your device (link), just go to the second post for the exact procedure.
Once you're done, use some software to verify root access, then download Flashify from Play Store. Go to the TWRP website and get the latest recovery (version 3.1.1) for your device. N910G codename should be 'trlte', better verify yourself to avoid issues. You can now flash the recovery using Flashify.
You're now at a good point, your device is ready for further steps to get Magisk. I'll post the rest of the procedure as soon as you're ready, I just want to warn you that Magisk could possibly create some issues like app instability or inability to use certain services. I got rid of it after few months and flashed SuperSU instead, which is the better option in my opinion. I've never used it on TouchWiz so I can't tell you anything specific about that, you may want to backup your current ROM into an external MicroSD using TWRP, just in case.
Black Shade said:
You should've asked in the Q&A section. Thread moderators will probably move this one as soon as they notice, don't worry, you're a relatively new user so you can't know everything yet.
By the way, you can't root with Magisk, if you're not rooted with other methods, because your bootloader is still locked and neither stock recovery or Odin would allow it. You first need to get root access by using some specific software such as ChainFire Autoroot. There are some guides available, but first you have to search for the zip file on the ChainFire website (link), pay attention to the model and check if Odin is included with the package. If it's not, just do a Google search for a fairly recent version. When you have everything you need, use this guide to root your device (link), just go to the second post for the exact procedure.
Once you're done, use some software to verify root access, then download Flashify from Play Store. Go to the TWRP website and get the latest recovery (version 3.1.1) for your device. N910G codename should be 'trlte', better verify yourself to avoid issues. You can now flash the recovery using Flashify.
You're now at a good point, your device is ready for further steps to get Magisk. I'll post the rest of the procedure as soon as you're ready, I just want to warn you that Magisk could possibly create some issues like app instability or inability to use certain services. I got rid of it after few months and flashed SuperSU instead, which is the better option in my opinion. I've never used it on TouchWiz so I can't tell you anything specific about that, you may want to backup your current ROM into an external MicroSD using TWRP, just in case.
Click to expand...
Click to collapse
Thank you for the advices. I did root following all those steps u gave me. For rooting i dont have a problem but its only after which when im tryin to install magisk i get error sayin that magisk only works for lollipop. Abit confused there. From my knowledge i knew that to install magisk i need to unroot superSu which i did & kept my twrp custom recovery. But somehow i cant seem to keep the twrp recovery & thats where i cant flash the 13.3v magisk.
Firdhaus81 said:
Thank you for the advices. I did root following all those steps u gave me. For rooting i dont have a problem but its only after which when im tryin to install magisk i get error sayin that magisk only works for lollipop. Abit confused there. From my knowledge i knew that to install magisk i need to unroot superSu which i did & kept my twrp custom recovery. But somehow i cant seem to keep the twrp recovery & thats where i cant flash the 13.3v magisk.
Click to expand...
Click to collapse
As I thought, Magisk won't work with the stock ROM. The main issue here is the kernel, which doesn't allow such modification. ChainFire has found a workaround to bring SuperSU on TouchWiz, but the fact it's not open source doesn't allow Magisk developers to use the same method. The head developer, few months ago, said that he was working on it and he was making some progress, but apparently it's not ready yet. I think it's not worth trying again, it won't work at the moment. I suggest keeping an eye on the thread, in case there are some updates. At the moment, I recommend either using SuperSU (which I recommend anyways), or flashing a different ROM, since deodexed TouchWiz ROMs with H-Vitamin or RAM Kernel do actually support Magisk, I tried myself.
Thread moved to proper section
The thing is ive seen in youtube they do get to root via magisk. I need this as to get my pokemon go workin.. :laugh:
Firdhaus81 said:
The thing is ive seen in youtube they do get to root via magisk. I need this as to get my pokemon go workin.. [emoji23]
Click to expand...
Click to collapse
Black Shade is right about the kernel. Using the wrong kernel will cause the install to fail. I'm on an n910t3, using ramrom v3 kernel, and I'm using magisk 13.3 for Android pay and viper audio. There's an official magisk 13.3 thread on xda somewhere. You should try there as a start.
Sent from my SM-N935S using Tapatalk
Attached my kernel info if u can help to check?
Found working magisk root method note 4 sm-n910g
Hello, I'm unsure if it'll work for you but it did for me.
1. Downloaded latest firmware from sammobile & flashed it to phone. (You can just try and find your current boot.img and skip to step 4)
2. Opened stock ROM zip & md5 file - using 7zip
3. Extracted boot.img
4. Place onto SD-CARD
5. Install Magisk apk
6. Magisk > settings > output format > change to ".tar" file
7. Magisk > patch boot.img
8. Locate "patched boot.img" > flash in Odin AP
Done
Worked for my galaxy note 4 SM-N910G
thanks, followed your instruction and it works for me. now i am able to flash magisk on my stock Note 4 though i had to surf more inform on xda using tar-Tool_Odin3-v3.10.7
Worked for my galaxy note 4 SM-N910G[/QUOTE]
MagiskFan said:
Found working magisk root method note 4 sm-n910g
Hello, I'm unsure if it'll work for you but it did for me.
1. Downloaded latest firmware from sammobile & flashed it to phone. (You can just try and find your current boot.img and skip to step 4)
2. Opened stock ROM zip & md5 file - using 7zip
3. Extracted boot.img
4. Place onto SD-CARD
5. Install Magisk apk
6. Magisk > settings > output format > change to ".tar" file
7. Magisk > patch boot.img
8. Locate "patched boot.img" > flash in Odin AP
Done
Worked for my galaxy note 4 SM-N910G
Click to expand...
Click to collapse
Hi, I know is kind of old post here. Just wanna ask, have you try the latest version of Magisk on your note 4 SM-N910G? New version of magisk does not have the option to choose the output format to ".tar" file.
pippideniro said:
thanks, followed your instruction and it works for me. now i am able to flash magisk on my stock Note 4 though i had to surf more inform on xda using tar-Tool_Odin3-v3.10.7
Worked for my galaxy note 4 SM-N910G
Click to expand...
Click to collapse
[/QUOTE]
Hi, I know is kind of old post here. Just wanna ask, have you try the latest version of Magisk on your note 4 SM-N910G? New version of magisk does not have the option to choose the output format to ".tar" file.
@lhooipg Were you asking to help him, or do you wanna know yourself?
bmwdroid said:
@lhooipg Were you asking to help him, or do you wanna know yourself?
Click to expand...
Click to collapse
I wanna know myself, I am facing the same issue as him. Thank you.

Categories

Resources