FORUMS

Analysis & Opinion

Top Forum Discussions

[24sept12]How to Root/Unroot Samsung Galaxy Note + CWM

22,398 posts
Thanks Meter: 41,357
 
By dr.ketan, Recognized Contributor on 2nd November 2011, 09:53 AM
Post Reply Subscribe to Thread Email Thread
4th January 2012, 05:22 PM |#511  
dr.ketan's Avatar
OP Recognized Contributor
Flag Gujarat
Thanks Meter: 41,357
 
Donate to Me
More
wat i am seeing is, when you gets update from Rooted old version to KL3, this weired thing happens.
I am on KL3 and i have rooted 3 Notes on same but never found any error.
So I think better way shud be, you shud get unrooted, factory reset, thn shud update to KL3
- Alternate is use Mobile odin pro and keep root intact.
And have anyone tried putting device on download mode and then use zergrush ??
shud try this
 
 
4th January 2012, 05:35 PM |#512  
thay's Avatar
Senior Member
Thanks Meter: 38
 
More
DooMLoRD's Easy Rooting Toolkit [v4] (zergRush Exploit) released
Hope this helps users with new firmware rooting
http://forum.xda-developers.com/show...32&postcount=1
http://forum.xda-developers.com/show....php?t=1312859
Last edited by thay; 4th January 2012 at 05:44 PM.
4th January 2012, 07:17 PM |#513  
dr.ketan's Avatar
OP Recognized Contributor
Flag Gujarat
Thanks Meter: 41,357
 
Donate to Me
More
zergrush exploit V4 is here, will updae op tomorrow
Last edited by dr.ketan; 4th January 2012 at 07:20 PM.
4th January 2012, 10:34 PM |#514  
GallardosEggrollShop's Avatar
Senior Member
Flag The Hill
Thanks Meter: 27
 
More
Tried method #2 and i keep getting this message after "flashing zImage"

/dev/block/mmcblk0p5: cannot open for write: Permission denied

I believe this step not being able to finish is the reason why my root doesn't go through. I'm running KL7 and I checked all the prerequisites before I started this root method. Can anyone help :'(
Last edited by GallardosEggrollShop; 4th January 2012 at 10:56 PM.
5th January 2012, 12:40 AM |#515  
progene81's Avatar
Member
Flag Singapore
Thanks Meter: 7
 
More
Quote:
Originally Posted by dr.ketan

Many time i have seen weired things, but can't short out exact cause.
Still you can always back to original stock, you can find link to that in my signature.
I advised to reset once b4 flashing back to original stock. and later if you need to update latest firmware, try usin Mobile Odin, which keeps Root intact, while flashing new firmware.


Correct me if I'm wrong. Your advise is
> Factory format
> flash back original stock
> root
> mobile Odin to new firmware with root intact.

Sent from my GT-N7000 using XDA Premium App
5th January 2012, 05:22 AM |#516  
dr.ketan's Avatar
OP Recognized Contributor
Flag Gujarat
Thanks Meter: 41,357
 
Donate to Me
More
Quote:
Originally Posted by progene81

Correct me if I'm wrong. Your advise is
> Factory format
> flash back original stock
> root
> mobile Odin to new firmware with root intact.

Sent from my GT-N7000 using XDA Premium App

Exactly, this shud work
5th January 2012, 08:09 AM |#517  
Member
Thanks Meter: 3
 
More
Quote:
Originally Posted by dr.ketan

wat i am seeing is, when you gets update from Rooted old version to KL3, this weired thing happens.
I am on KL3 and i have rooted 3 Notes on same but never found any error.
So I think better way shud be, you shud get unrooted, factory reset, thn shud update to KL3
- Alternate is use Mobile odin pro and keep root intact.
And have anyone tried putting device on download mode and then use zergrush ??
shud try this

Putting Note on download mode, zergrush cannot detect device ....?

noob, adb shell does not work.


Update:
DidNotReset; Odin with KL1; Zergrush v4; MobileOdin KL3 w/everroot ; Rooted now.
Last edited by qazokm123; 5th January 2012 at 09:04 AM.
5th January 2012, 08:28 AM |#518  
norge-xda's Avatar
Senior Member
Flag Salerno
Thanks Meter: 30
 
More
Hi all,
just a silly question. Following the method root+cmw, the file zImage to put into the zImage folder is the file zImage already present in the .rar file downloaded?
In a word: do I have to do something more than download the file -> extract -> run "already rooted" .bat?
Last edited by norge-xda; 5th January 2012 at 08:34 AM.
5th January 2012, 08:52 AM |#519  
Junior Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by GallardosEggrollShop

Tried method #2 and i keep getting this message after "flashing zImage"

/dev/block/mmcblk0p5: cannot open for write: Permission denied

I believe this step not being able to finish is the reason why my root doesn't go through. I'm running KL7 and I checked all the prerequisites before I started this root method. Can anyone help :'(

I am in the same situation...but mine is a SHV-E160L,
dont know if it would be a problem..
anyone?
5th January 2012, 09:04 AM |#520  
dr.ketan's Avatar
OP Recognized Contributor
Flag Gujarat
Thanks Meter: 41,357
 
Donate to Me
More
Quote:
Originally Posted by norge-xda

Hi all,
just a silly question. Following the method root+cmw, the file zImage to put into the zImage folder is the file zImage already present in the .rar file downloaded?
In a word: do I have to do something more than download the file -> extract -> run "already rooted" .bat?

This has to be put if you downloaded it from CF's post, Here you just follow proedure which i have mention. it is ready to proeed, without putting it, B'coz i have done it already.
The Following User Says Thank You to dr.ketan For This Useful Post: [ View ]
5th January 2012, 09:10 AM |#521  
norge-xda's Avatar
Senior Member
Flag Salerno
Thanks Meter: 30
 
More
Quote:
Originally Posted by dr.ketan

This has to be put if you downloaded it from CF's post, Here you just follow proedure which i have mention. it is ready to proeed, without putting it, B'coz i have done it already.

Another "thanks" for u dr.ketan!
I was reading chainfire thread and simulated the root by downloading his cr-rootflasher: no zImage there in fact. You made a good (and tough) job definitely

Read More
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes