I have a White Galaxy Note which came with Gingerbread 2.3.6 N7000DXKL2 preinstalled. However, since Chainfire does not support KL2 firmwares, I've opted to upgrade it to N7000DXLC1 via Kies. When I tried the Chainfire CF-Root flasher method (including the correct zImage) here's what happened:
---------------------------------------------------------------
Initial CF-Root flasher, by Chainfire
Credits:
Easy rooting toolkit by DooMLoRD
zergRush by Revolutionary Team
Gingerbreak/Honeybomb by The Android Exploid Crew
---------------------------------------------------------------
[*] This script will:
(1) root ur device using zergRush exploit
(2) flash CF-Root
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device
(2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
(7) !!! PUT A CF-ROOT zImage FILE IN THE zImage FOLDER !!!
---------------------------------------------------------------
CONFIRM ALL THE ABOVE THEN
Press any key to continue . . .
--- STARTING ----
--- WAITING FOR DEVICE
--- cleaning
--- pushing zergRush"
2251 KB/s (23052 bytes in 0.010s)
--- correcting permissions
--- executing zergRush
[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.
[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android E
[+] Found a GingerBread ! 0x0002e118
[+] Found a Samsung, running Samsung mode
[*] Scooting ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 149 zerglings ...
[*] Sleeping a bit (~40s)...
[*] Waking !
[*] Sending 189 zerglings ...
[-] Hellions with BLUE flames !
--- WAITING FOR DEVICE TO RECONNECT
if it gets stuck over here for a long time then try:
disconnect usb cable and reconnect it
toggle "USB DEBUGGING" (first disable it then enable it)
--- DEVICE FOUND
---------------------------------------------------------------
We should have (temporary) root now
We will try to flash CF-Root kernel now
Please watch for any errors beyond this point!
---------------------------------------------------------------
Press any key to continue . . .
--- pushing zImage
2650 KB/s (8387840 bytes in 3.090s)
--- flashing zImage
/dev/block/mmcblk0p5: cannot open for write: Permission denied
--- cleaning up
--- rebooting
---------------------------------------------------------------
If all is well, CF-Root should be flashed
Your device should be rebooting now
Please check if you have root and CWM after boot completes!
---------------------------------------------------------------
It still isn't rooted. Is there another method? I don't want a full wipe of the phone and I don't want to change to Custom ROMS because my sole purpose of rooting the device is to backup its current firmware since there's been a lack of pure stock roms for the SGN in my country and I wish to provide an unadulterated ROM to my fellow countrymen. Plus I need something to get back to since SamFirmware isn't a very reliable source.
Details
Samsung Galaxy Note White
Version 2.3.6
Baseband Version N7000DXLC1
Build Number GINGERBREAD.DXLC2
Region: XTC (Philippines: Open Line)
Your decision was wrong, you didn't fully understood the chainfires advise OR you have not read it completely. Here what you have missed in chainfire's thread.
-Your previous ROM was likely rootable,b'coz upto KL3 most of ROM is directly rootable it is not necessary to have same kernel to use.
Read this
chainfire have clearly said :
Don't worry too much, just find the matching download and use it. What if there is no matching download ? You can ask me to make one, but I can tell you right now, I very very rarely make CF-Root's for kernels on request, unless it is the very latest kernel that has been released by Samsung. In the latter case, be sure to let me know. If there's no match and I'm not making one, try finding the closest match. You should treat "KJ4" as a number, but instead of 1-9, we have 1-9, A-Z (where A would be 10, and Z would be 35). "KJ3" is really close to "KJ4", "KF1" is not close to "KG4" at all. I hope that makes sense.
Click to expand...
Click to collapse
So it is clear that you need to use Kl1 kernel to root your ROM
Another thing you have missed is.
Read this from chainfire
1.2. If you are not rooted yet: Using the zergRush exploit This method no longer works on KL* and newer firmwares!
Click to expand...
Click to collapse
So hear again you did wrong, you have updated to LC1
That is non rootable, Cf have provided kernel for LC1, but it can't root your ROM LC1. it is for updating kernel, but you need to have root.
So Now you have option to root is
Downgrade to any directly rootable ROM, Root it, then update to latest ROM with Mobile odin/CWM
You can dowload guide form last link on my signature to get detail assistance for total procedure.
dr.ketan said:
Your decision was wrong, you didn't fully understood the chainfires advise OR you have not read it completely. Here what you have missed in chainfire's thread.
-Your previous ROM was likely rootable,b'coz upto KL3 most of ROM is directly rootable it is not necessary to have same kernel to use.
Read this
So it is clear that you need to use Kl1 kernel to root your ROM
Another thing you have missed is.
Read this from chainfire
So hear again you did wrong, you have updated to LC1
That is non rootable, Cf have provided kernel for LC1, but it can't root your ROM LC1. it is for updating kernel, but you need to have root.
So Now you have option to root is
Downgrade to any directly rootable ROM, Root it, then update to latest ROM with Mobile odin/CWM
You can dowload guide form last link on my signature to get detail assistance for total procedure.
Click to expand...
Click to collapse
Well, it's not easy to read and it's very easy to misunderstood on what he said. Contrary to what you said, it's not even close to clear and what you said about the previous firmware is rootable contradicts to what chainfire said about KL firmwares.
Please don't say that "it is clear", It's insulting my intelligence. I read it a lot of times and I also read some comments (that's how I got the idea of upgrading to get root availability). I've already upgraded it to ICS so the topic is now irrelevant. Now I'm trying to figure out how to backup the firmware without rooting and sending it to the community so that at least our country has an entry on samfirmware.com. I lost hope in rooting the Note and since it's not mine (it's my sister's) and most apks just run fine even without root, I don't think I'd pursue having it rooted unless it can enable me to format the microSD card to a better file system aside from FAT32.
Why you are asking Questions If You are that much intelligent....???
Dr. Ketan is one of Most Respected Senior member Of XDA.. Look his Thanks meter.... You are very lucky that Dr.Ketan was Replied You.
Now Don't be angry with me... I am posting this becouse We Respect him...
No Need to Reply... I am not going to visit This Thread again...
Related
Hey guys - self-admitted n00b here : )
I've been trying for the past couple hours to follow ND1 Razors guide to root 2.3.4. NOTE: I tried to provide the link but I'm new to the forums so it won't let me
All was going well up to step 10...
When using SuperOneClick and following Razors detailed directions, I get the following failure:
SuperOneClick v2.1.0.0
Checking drivers...
Killing ADB Server...
OK
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK
Waiting for device...
OK
Getting manufacturer...
END:36496
OK
Getting model...
END:94500
OK
Getting version...
END:22067
OK
Checking if rooted...
False
OK
Installing BusyBox (temporary)... - Step #1
1253 KB/s (1062992 bytes in 0.828s)
OK
Installing BusyBox (temporary)... - Step #2
END:8949
OK
Rooting device... - Step #1
1220 KB/s (585731 bytes in 0.468s)
OK
Rooting device... - Step #2
END:7192
OK
Rooting device... - Step #3
END:8007
OK
Rooting device... - Step #4
END:39931mmap() failed. Operation not permitted
FAILED
ANY help here would be AWESOME - I am VERY MUCH looking forward to root and using cyanogen.
I'll be purchasing an HTC Sensation pretty soon and from the research I've done, it sounds like root will be achieved sometime in September on that device once HTC unlocks the bootloader! I'm trying to root my N1 now so I am a bit more "seasoned" before I go bricking a purdy new and EXPENSIVE device
HELP!?!? lol please and thanks of course
Actually s-off on the sensation is going on right now, for the past few days even.
To answer your question, just passimg back to original and root from there, or even just fastboot oem unlock and root.
Thanks for the quick reply Evil - but like I said - I'm VERY n00bish when it comes to root.
I'm on FRG33 right now - superoneclick is failing at the point I mentioned above
My drivers are up to date (I believe) and have SDK
since its possible to root without unlocking - that was my first choice but I will do WHATEVER I CAN do.
Getting to step 10 out of 17 and then failing SUCKS.
Any SPECIFIC answers to get me root (using the above method or otherwise) would be appreciated
Have you tried the other methods in the wiki?
http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Guides_&_Tutorials#Root
Make sure your rooting with the rageagainstthecage method cause if you try to use the gingerbreak method it won't work.
I am having the exact same issues. I am also a total n00b at rooting, and SuperOneClick is failing at "Rooting device- Step #4 mmap() failed. Operation not permitted FAILED"
If you are running 2.3.4, there isn't any way to run an exploit and get root. The only way to root the phone is to: 1. unlock the bootloader and flash a custom recovery taht allows you to flash a zip containing the necessary files (which if you are want to install CM, it isn't necessary to root it at that point as you can just install CM from the custom recovery) --or-- 2. Use the passimg method to bring your phone back to a froyo version and use SuperOneClick's rageagainstthecage exploit to gain root access.
fre3vo might work for 2.3.4, but needs testing, and I don't have the time to test.
http://forum.xda-developers.com/showthread.php?t=1150006
How to run:
http://forum.xda-developers.com/showthread.php?t=1178912
Dear all,
I would like to announce that the current software cannot root the Hong Kong Version of Black P970 born with v10b at all.
If I flash v10a by KDZ updater, it stops at 50% and looping with LG logo forever.
For original born with v10b, I use the following method by many many times.
gingerbreak 1.2
SOC 1.9.5(with command post, in xda)
SOC 2.1.1(fixed)
ALL FAILED!
I am going to give up. Can anyone help?
Sorry for my poor english
I did the mistake and upgraded to v10b and now I am facing the same problem.
Prior to the upgrade I had no problems rooting my device with the GingerBreak 1.2 although know after upgraded to V10b it is failing...
[I CAN ROOT NOW]By UPK3
i can root it now, but how long is just depending on your luck
[LG P970] Upgrade Kit 3 (13/9) | Firmwares, Flashing, Rooting..
Mainly use driver, SOC2.1+SRP+CWM
http://forum.xda-developers.com/showthread.php?t=1111771
The files is on Megaupload, however, Hong Kong ip is blocked. So, I upload the main required files to Mediafire.
Please dont complain that I upload the source files since many HK people really need these file. However, we really cannot access to megaupload normally.
Please download both of them if you want to root you v10b,c,d...
http://www.mediafire.com/?eiukasb7zewp9ja
http://www.mediafire.com/?vuss1yezyxprval
Remember, be patient, I use these files for 5 times to root it. Good luck!
sonicpeter said:
i can root it now, but how long is just depending on your luck
[LG P970] Upgrade Kit 3 (13/9) | Firmwares, Flashing, Rooting..
Mainly use driver, SOC2.1+SRP+CWM
http://forum.xda-developers.com/showthread.php?t=1111771
The files is on Megaupload, however, Hong Kong ip is blocked. So, I upload the main required files to Mediafire.
Please dont complain that I upload the source files since many HK people really need these file. However, we really cannot access to megaupload normally.
Please download both of them if you want to root you v10b,c,d...
http://www.mediafire.com/?eiukasb7zewp9ja
http://www.mediafire.com/?vuss1yezyxprval
Remember, be patient, I use these files for 5 times to root it. Good luck!
Click to expand...
Click to collapse
So for everyone who is having this problem they need to make sure they have the drivers installed and then try the SOC2.1+SRP method? Where does CWM come into the initally rooting process?
TomByrne94 said:
Where does CWM come into the initally rooting process?
Click to expand...
Click to collapse
Nowhere. It has nothing common with rooting process.
I also have a P970 with Hong Kong stock rom v10b but I did succeed in rooting my phone.
Try the method described in post #34 of this thread
http://forum.xda-developers.com/showthread.php?t=1171672&page=3#30
All I needed was SOC 1.9.5.
noranyan said:
I also have a P970 with Hong Kong stock rom v10b but I did succeed in rooting my phone.
Try the method described in post #34 of this thread
http://forum.xda-developers.com/showthread.php?t=1171672&page=3#30
All I needed was SOC 1.9.5.
Click to expand...
Click to collapse
This Method I have tried,BUT 1.9.5 is quite difficult for new comer and quite depends on your luck.
So, I would like to suggest a easier, less complicated and higher chance for rooting OB. That is, the #3. the attached file in #3 are same as megaupload one. It is UPK v3.
I have used for SOC 1.7, 1.9.5 and 2.1. I think you should try the 2.1 if you are stuck in freezing during rooting. remember using CWM.exe during stuck
Besides, the newer version of UPK v3.3 is ready, although there is no difference for rooting your OB
Sorry for my poor english
I am also in Hongkong with Lg P970 Version B rooted successfully
Hi Guys,
I have rooted successfully the version 10B LG P970. I used UPK here is how i did it:
save the UPK file in your computer C drive. Click the superoneclick 2.1.1 when it opens click root selecting auto it will stop at step 4 at that time open task manager in windows by using the combination key ctrl+alt+delete. you should see the process adb two process running kill the two process of adb. Thats it you are done your device will get rooted.
Fahimxda said:
Hi Guys,
I have rooted successfully the version 10B LG P970. I used UPK here is how i did it:
save the UPK file in your computer C drive. Click the superoneclick 2.1.1 when it opens click root selecting auto it will stop at step 4 at that time open task manager in windows by using the combination key ctrl+alt+delete. you should see the process adb two process running kill the two process of adb. Thats it you are done your device will get rooted.
Click to expand...
Click to collapse
I tried superoneclick 2.1.1 before and stuck at step 4. So I flash back to 10A. Your method is so simple. I want to try it.
You try it out if you find any difficulties let me know.
I just need superoneclick2.1.1, no need UPK, right?
Its better if you have UPK. If you dont have please download else first try without UPK and let me know the result.
I only want to root 10B. What is the program I need to run in the UPK package?
I rooted my phone which has 10b version with UPK
Sorry, I don't understand. I upgraded to 10b from LG PC suite.
I want to try to root it using superoneclick 2.1.1. When it hangs at step 4, then press ctrl-alt-del to kill the two process of adb as described from previous thread #8. And the phone will be rooted.
So I don't understand why I need UPK.
you need it cuz SOC get stuck on #4. Then you have to launch SRP(reset) to continue root process.
this method needs 2 steps to make it work
By killing task as you mentioned, I can go through step 4, but the rootingg failed like this...............
SuperOneClick v2.1.1.0
Checking drivers...
Killing ADB Server...
OK 1.08s
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK 4.15s
Waiting for device...
OK 0.05s
2.2.2
Getting manufacturer...
lge
OK 0.02s
Getting model...
LG-P970
OK 0.02s
Getting version...
LG-P970-V10b.420D83F1
OK 0.02s
Checking if rooted...
False
OK 0.05s
Installing BusyBox (temporary)... - Step #1
3407 KB/s (1062992 bytes in 0.304s)
OK 0.35s
Installing BusyBox (temporary)... - Step #2
OK 0.01s
Rooting device... - Step #1
3050 KB/s (585731 bytes in 0.187s)
OK 0.23s
Rooting device... - Step #2
OK 0.02s
Rooting device... - Step #3
OK 0.01s
Rooting device... - Step #4
property service neutered.
killing adbd. (should restart in a second or two)
OK 9.79s
Rooting device... - Step #5
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK 4.07s
Remounting /system with read-write access...
error: device not found
FAILED
Would you give some suggestions?
Thanks!!!
Ilko said:
you need it cuz SOC get stuck on #4. Then you have to launch SRP(reset) to continue root process.
this method needs 2 steps to make it work
Click to expand...
Click to collapse
What is SRP? Where can I get it?
Thanks
link is on my signature. download the kit and follow instructions
jackkwan said:
By killing task as you mentioned, I can go through step 4, but the rootingg failed like this...............
SuperOneClick v2.1.1.0
Checking drivers...
Killing ADB Server...
OK 1.08s
Starting ADB Server...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK 4.15s
Waiting for device...
OK 0.05s
2.2.2
Getting manufacturer...
lge
OK 0.02s
Getting model...
LG-P970
OK 0.02s
Getting version...
LG-P970-V10b.420D83F1
OK 0.02s
Checking if rooted...
False
OK 0.05s
Installing BusyBox (temporary)... - Step #1
3407 KB/s (1062992 bytes in 0.304s)
OK 0.35s
Installing BusyBox (temporary)... - Step #2
OK 0.01s
Rooting device... - Step #1
3050 KB/s (585731 bytes in 0.187s)
OK 0.23s
Rooting device... - Step #2
OK 0.02s
Rooting device... - Step #3
OK 0.01s
Rooting device... - Step #4
property service neutered.
killing adbd. (should restart in a second or two)
OK 9.79s
Rooting device... - Step #5
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
OK 4.07s
Remounting /system with read-write access...
error: device not found
FAILED
Would you give some suggestions?
Thanks!!!
Click to expand...
Click to collapse
hello, i am back and i would like to help you.
since i have also faced the same result, i am now going to tell you what's going on.
the red word you have highlighted are what i encountered during rooting. I want to say it again. you have to do the rooting again, since it seems that protection machanism stars at the red line, you need to root it again.
BE PATIENT! my friend, if you have download what i said in this thread and follow the instruction
http://forum.xda-developers.com/showpost.php?p=17990469&postcount=3
finally, YOU MUST GET ROOT ACCESS, dont worry about it.
JUST BE PATIENT.
I have do a stupid test on my phone. that is , back to the stock rom and root it again. and the result is, i need to root it for 10 TIMES for root access.
so, just do the instruction and finally you can root your phone
hi every expert and non expert for rooting SGN,
kiddo here got some simple questions need helpout, thks in 1st.
my country: malaysia
my divice: Samsung galaxy note
divice age: about 1 months plus, still got about 10 months original warrenty
android version: 2.3.5
baseband: N7000DXKJ3
kernel version: 2.6.35.7-N7000DXKK1-CL706642
[email protected]#2
root status: not yet root before
latest update: not yet official or non official update before, but just got a sms regarding new update has arrived, still thinking want to update or not.
question:
1.i just want to root the divice for some rooting required app like gamecih. etc. any suggestion on it? it's better with tutorial on step by step. by the way, my divice have't link to pc before, and my home pc has no internet line=.=, they are normally use for game playing.
2.about the update, should i update 1st or rooting 1st? and after rooting can i update anymore in the future if there is a new update?
3.after update or rooting will my app, data, phonebook etc. will gone too?
4.i heard that in galasy note, if u rooting it the samsung company will notice it, but last time when i was using LG optimus one, with the rooting using "One Click GingerBreak" app, then i sent for repairing at the lg company, they still accept it.
how do they find out? is there anyway to prevent them form knowing i have root the nate?
sorry if the above question is so noob T.T,but i really hope that u guys can help me out. a hundred million TQ to all of u guys, kiss kiss, and happy valentine day!!
1. Here's DrKetan's comprehensive guide to rooting your Note:
http://forum.xda-developers.com/showthread.php?t=1329360
2. Do not update, root first. New updates are not directly rootable, you're better of with your existing Rom for rooting purposes.
3. No.
4. Do your rooting carefully, following DrKetan's instructions to the letter, and you'll be able to unroot your phone should the need arise.
Hope this helps.
chasmodo said:
1. Here's DrKetan's comprehensive guide to rooting your Note:
http://forum.xda-developers.com/showthread.php?t=1329360
2. Do not update, root first. New updates are not directly rootable, you're better of with your existing Rom for rooting purposes.
3. No.
4. Do your rooting carefully, following DrKetan's instructions to the letter, and you'll be able to unroot your phone should the need arise.
Hope this helps.
Click to expand...
Click to collapse
+1
Just want to add line for answer for Q2 n 3
You can update over OTA but it will erase your root.
N in case of manual update
Wipe or non wipe depends on ROM you are updating. If ROM which you installing is wipe version, it will wipe off data, if it is non wipe it won't
Sent from my GT-N7000 using xda premium
chasmodo said:
1. Here's DrKetan's comprehensive guide to rooting your Note:
http://forum.xda-developers.com/showthread.php?t=1329360
2. Do not update, root first. New updates are not directly rootable, you're better of with your existing Rom for rooting purposes.
3. No.
4. Do your rooting carefully, following DrKetan's instructions to the letter, and you'll be able to unroot your phone should the need arise.
Hope this helps.
Click to expand...
Click to collapse
thks 1st
i got this coming out on runme.bat
Easy rooting toolkit (v4.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using zergRush exploit (21 Nov 2011)
(2) install Busybox (1.18.4)
(3) install SU files (binary 3.0.5 and apk: 3.0.6)
(4) some checks for free space, tmp directory
(will remove Google Maps if required) [*] Before u begin:
(1) make sure u have installed adb drivers for ur device. (2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
blue: it will remove google maps? does that means i can't use maps anymore after rooting?
red: what is adb drivers? where do i get them?
green: the divice is my note right? or come out on the cpu monitor?
thks 1st again.
dr.ketan said:
+1
Just want to add line for answer for Q2 n 3
You can update over OTA but it will erase your root.
N in case of manual update
Wipe or non wipe depends on ROM you are updating. If ROM which you installing is wipe version, it will wipe off data, if it is non wipe it won't
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
thaks
does that means if i root ady then go update then i have to root again?
and if unfortunately after the update and there is no new software for that time beeing to root my note, my phone superuser(root) will be removed?
vtkm831125 said:
blue: it will remove google maps? does that means i can't use maps anymore after rooting?
red: what is adb drivers? where do i get them?
green: the divice is my note right? or come out on the cpu monitor?
Click to expand...
Click to collapse
You can always install Google Maps from the Market. I have no idea what the software would remove, maybe just downloaded maps? If so, the come back when you use the app.
ADB drivers are needed for the USB connection to your PC. Search on this form, there is a link to the correct ones for the Note.
The prompt to install 'companion software' will be on the phone, I believe. I have never seen it, so am not sure, but to me 'device' means phone, not PC.
Good luck!
vtkm831125 said:
thks 1st
i got this coming out on runme.bat
Easy rooting toolkit (v4.0)
created by DooMLoRD
using exploit zergRush (Revolutionary Team)
Credits go to all those involved in making this possible!
---------------------------------------------------------------
[*] This script will:
(1) root ur device using zergRush exploit (21 Nov 2011)
(2) install Busybox (1.18.4)
(3) install SU files (binary 3.0.5 and apk: 3.0.6)
(4) some checks for free space, tmp directory
(will remove Google Maps if required)
[*] Before u begin:
(1) make sure u have installed adb drivers for ur device. (2) enable "USB DEBUGGING"
from (Menu\Settings\Applications\Development)
(3) enable "UNKNOWN SOURCES"
from (Menu\Settings\Applications)
(4) [OPTIONAL] increase screen timeout to 10 minutes
(5) connect USB cable to PHONE and then connect to PC
(6) skip "PC Companion Software" prompt on device
blue: it will remove google maps? does that means i can't use maps anymore after rooting?
red: what is adb drivers? where do i get them?
green: the divice is my note right? or come out on the cpu monitor?
thks 1st again.
Click to expand...
Click to collapse
I think this msg is for some device which have very small rom. You hav nothing to worry for note, it has still more than 60 mb space empty, n root just need 1-2mb only. Nyway you hav not to do anything with map.
Installing latest kies enough to install adb driver
green - ignore this msg
Sent from my GT-N7000 using xda premium
vtkm831125 said:
thaks
does that means if i root ady then go update then i have to root again?
and if unfortunately after the update and there is no new software for that time beeing to root my note, my phone superuser(root) will be removed?
Click to expand...
Click to collapse
You hav to root first, if you update over kies or ota, you will lose root, as well you can't root it anymore. B'coz newer update is not direct rootable. So you have to use cwm or mobile odin to update as well keep root intact.
Download my guide from last link of my signature to get further assistance.
Sent from my GT-N7000 using xda premium
hurray!! i have just rooted my note a while ago,
my biggest thks to all the helpers and expert who helped me out
love u guys, and happy valentine day!!
Thread Ended, Forum Master Please Delete it, TQ for all the support
Thread Ended, Forum Master Please Delete it, TQ for all the support
Hi,
I used the 'Easy Root for various Xperia devices' in this link:
http://forum.xda-developers.com/showthread.php?t=2784900
My FW is 10.5.1.A.0.283.
Kernel: 3.4.0-perf-ge2ad053-00925-g7f21499.
I got it from a standard Sony update, I didn't flash it myself.
The download (towelzxperia) succeeds, I have installed adb and obviously allowed for usb debugging.
Nonetheless, when I try to run the root script I get this screen:
Waiting for towelzxperia to exploit...
towelzxperia by zxz0O0 (EasyRootTool Version)
libexploit by geohot
libzxploit.so created
doing the magic
creating vm (loljavasucks)
And nothing happens (for a really long time!)...
I work for 12-14 hours a day, I don't have much time to deal with this but I can manage with some guidance.
So..... help please
Hi!
Follow this thread in General Section: http://forum.xda-developers.com/xperia-z/general/guide-how-to-root-10-5-1-0-283-t2872873
You basically have to flash the older kernel, boot, root, and flash the new kernel. No wiping, no losing data.
Pretty fast, easy and neat. You just have to make sure you have installed the drivers.
Good luck.
I take no responsibility for what happens to your device if you follow this guide. Rooting or modifying carries risks, however I have tested this procedure many times with 100% success on my SM-t805. It should work for any device, but I can't confirm, so feedback please if it works for your device.
1. Firstly you need to downgrade your device to a XXU1ANF8 or earlier firmware suitable for your particular model. This is available at http://samsung-updates.com/ or you can use this one XSG-T805XXU1ANF8-20140625 which is for the T805 model only.
https://www.androidfilehost.com/?fid=23501681358555496 T800 only
Download and then install the firmware on your device with ODIN.
If you are still on Kitkat then there is no need to wipe the data partition. However if you are running Lollipop after successful installation you will need to boot into recovery POWER + HOME + VOL UP then select WIPE DATA/RESET -
YOU WILL LOSE ALL YOUR USER DATA SO BACK UP ANYTHING YOU NEED TO THE SD CARD FIRST!
NOTE: IF THE INSTALL FAILS AT HIDDEN.IMG OR CACHE.IMG SIMPLY BOOT INTO RECOVERY AFTERWARDS AND WIPE CACHE THEN CARRY ON WITH THE REST OF THE PROCEDURE.
2. Once booted into Android, set up your wifi and google account and skip everything else (this wont be needed if you didn't wipe the data partition)
3. Next we need to install a Few apps, so go ahead and install these apps from Play Store:
System app remover(root)
Root Validator
Terminal Emulator For Android
KINGROOT 4.1
Kingroot updates and earlier versions if posted version doesn't work:
http://androidxda.com/download-kingroot-application
Kingroot 4.5 (latest version)
We also need to download the package from this LINK
4. Using the built in File Manager extract the zip package to your internal SD card. Once extracted, inside the extracted folder is another folder called MRW.
THIS FOLDER NEEDS TO BE MOVED TO THE ROOT OF YOUR INTERNAL SD CARD OR THIS WON'T WORK.
5. Next go to Settings set your display timeout to 10 mins.
Now Run KINGROOT then wait for it to do it's thing. If it reboots part way through the process then after rebooting unlock your device, but don't touch anything for a couple of mins. The app should restart and continue. If you are successful you can move to the next step. If not, exit the app and run it again, it may take several attempts before you eventually achieve root.
6. After success uninstall the KINGROOT app (NOT KINGUSER) (not required with v4.5) and the other blue app with Chinese writing.
Now reboot - DO NOT RUN THE KINGUSER APP
7. Let your device fully boot then run the Terminal Emulator and wait for the command prompt
NOTE: IF AT ANY POINT YOU SEE A POP UP BOX WITH CHINESE WRITING ASKING YOU TO UPDATE THE KINGUSER APP SELECT CANCEL.
Now type or copy and paste the following command into the Terminal window:
su
It will ask for root permission, so select ALLOW.
Without closing the terminal emulator window, hit the HOME button and run the SYSTEM APP REMOVER app. (The app is red and simply called UNINSTALL)
The app will ask for root permission, hit ALLOW.
Look for the KINGUSER app then select it and uninstall it. Exit from the app.
Re-open the terminal emulator window and type the following:
sh /sdcard/mrw/root.sh
This will run a script, you will see a bunch of warnings, just ignore them .At then end of the script the SUPERSU app will run.
8. Hit CONTINUE then NORMAL.
Next you may see another message that 'Samsung knox has been detected'. When you see this message select CANCEL.
Once completed you should see a message saying that installation has been successful. Hit OK.
If you see the message again 'Samsung knox has been detected' select CANCEL then exit the SUPERSU app.
9 . Now check with ROOT VALIDATOR that you have root and everything looks ok.
DO NOT REBOOT.
The root is only temporary, if you reboot you will lose root.
10. The next step is to install our ROM of choice with Flashfire.
For more info on FLASHFIRE see here: http://forum.xda-developers.com/general/paid-software/flashfire-t3075433
11. Run FLASHFIRE and grant it root.
12. Agree to the disclaimer and then hit the Red circle with a white +.
Next select 'Flash firmware package' and then navigate to the firmware you want to install (in this case the stock tar package) and select it.
Wait until it finishes scanning the archive.
Next you will see the list of partitions to be flashed, all that is really required is BOOT, RECOVERY and SYSTEM. You can flash the others if you wish.
When you're happy hit the TICK and then you will see a list of what will be flashed. If you tap any one of them you will be able to change the options. Tap the REBOOT option then select DOWNLOAD from the list. This is so we can boot into download mode after the flashing process to flash the Lollipop BOOTLOADER. If not upgrading to lollipop just select REBOOT
I'd advise to leave the rest as is and then hit FLASH
NOW WATCH CHAINFIRES MAGIC!
13. After reboot it should boot directly into DOWNLOAD mode or REBOOT if not updating to Lollipop.
If updating to Lollipop we need to flash a Lollipop BOOTLOADER. I have provided a link below for the T800 and T805. If you have a T700/705/T807/T707 or if the ones provided don't work then you will have to extract it from the Lollipop stock ROM and then TAR it up.
T800XXU1BOCC_BOOTLOADER.tar
T805XXU1BOCC_BOOTLOADER.tar
Latest T800 boot loader thanks DUHasian skillz.
T800XXU1BOE3 bootloader
Flash the BOOTLOADER with ODIN.
If successful then after reboot you should have a rooted version of Lollipop or whatever rom you decided to install and an untripped Knox counter(hopefully)
Good luck and please give feed back.
If you wish you can give feedback to Chainfire at the link posted at the beginning of this post.
NOTE: If you wish to change roms or update and wish to keep root you will have to use the same procedure with Flashfire.
Also note that if you flash a custom KERNEL or BOOTLOADER then it may trip KNOX. Custom ROMs with stock KERNEL and BOOTLOADER should be OK(but don't hold me to that)
CREDITS TO CHAINFIRE FOR FLASHFIRE AND SUPERSU, KINGTEAM FOR ROOT AND WOLFDROID FOR THE KINGROOT REMOVAL SCRIPT.
My god I've been waiting for a thread like this one for a long time.
I don't have time to try it today but I'll give you feedback in a day or two.
Feedback here http://forum.xda-developers.com/showpost.php?p=61296003&postcount=12
Moderators, this thread should be sticked
Just so that I understand the limits of this method I need to ask. Is this method specific to achieve rooted (SuperSU) Lollipop 5.0.2 without tripping Knox or can further changes be made? For example:
1) Remove system apps (removing bloat).
2) Adding system apps such as Viper4Android, busybox, which must be installed in /system/priv-app
3) The Lollipop/Samsung compatible XPosed framework and modules
4) Installing a Tab S model compatible recovery (e.g. TWRP) as I would really like nandroid backups.
I only ask as in the Tab S Kingroot thread there was a post which mentioning that despite Kingroot having successfully achieved root without tripping Knox if you messed with the /system partition files there was the possibility of tripping Knox.
The comment in step 12 "... then navigate to the firmware you want to install ..." suggests that you could install one of the model compatible custom ROMs (e.g. CM). Is that a correct assumption or right now are you restricted to Lollipop stock? Some of those ROMs are from Lollipop 5.1.1 AOSP source (e.g. CM 12.1) which may be going too far with this method and still not trip Knox.
One last question, if I did implemented this could I go back to a pure unrooted stock kitkat/lollipop using Odin or Flashfire without tripping Knox? Odin would be fine.
I greatly appreciate the effort and quality of your post. I had hoped that a "Knox off" SuperSU lollipop root would be found for my month old Tab S 10.5 as I'm used to the low risk flashing on the Nexus devices and have had a mean itch to root without obvious risk to my warranty.
Thanks again
This method can be used to root any Rom.
Once you have root you can practically do what you please.
As for tripping Knox if you mess with the system partition, that's the whole point of root it already messes with the system partition. It shouldn't trip Knox, but never say never.
Just ensure once you have root you remove everything Knox related.
I can't confirm if a custom Rom will trip Knox, but as already stated as long as the bootloader and kernel are stock I believe it won't trip Knox.
Custom recovery may trip Knox.
You can go back to stock any time you wish.
ashyx, as I'm a Linux user its taken me a while to set up a Windows machine but I finally have KIES working and Odin recognizing my Tab S. Now I'm doing my "read your how-to OP twice and root once" prework, but I'm left with a bit of confusion. In my case I am already on Lollipop 5.0.2 so have downloaded stock 4.4.2. When I read steps 12 and 13 I became a bit confused.
What I want is to be rooted (SuperSu) on stock lollipop (T800XXU1BOE2) so I'm assuming that in step 12 I will be using Flashfire to flash boot, recovery and system from the Samsung stock 5.0.2 lollipop firmware file. My confusion comes in step 13 as it seems redundant to flash the lollipop bootloader I just flashed in step 12. Is step 13's flashing the bootloader redundant if you flashed it in step 12?
I apologize if this is a noob question but I just want to get things right and avoid a bricked device especially when the bootloader is involved. At this point I'm only looking to remove bloat and add specific apps that require root so rooted stock is good enough but I'll be in position to try a custom ROM if I feel the need.
Thanks again
3DSammy said:
ashyx, as I'm a Linux user its taken me a while to set up a Windows machine but I finally have KIES working and Odin recognizing my Tab S. Now I'm doing my "read your how-to OP twice and root once" prework, but I'm left with a bit of confusion. In my case I am already on Lollipop 5.0.2 so have downloaded stock 4.4.2. When I read steps 12 and 13 I became a bit confused.
What I want is to be rooted (SuperSu) on stock lollipop (T800XXU1BOE2) so I'm assuming that in step 12 I will be using Flashfire to flash boot, recovery and system from the Samsung stock 5.0.2 lollipop firmware file. My confusion comes in step 13 as it seems redundant to flash the lollipop bootloader I just flashed in step 12. Is step 13's flashing the bootloader redundant if you flashed it in step 12?
I apologize if this is a noob question but I just want to get things right and avoid a bricked device especially when the bootloader is involved. At this point I'm only looking to remove bloat and add specific apps that require root so rooted stock is good enough but I'll be in position to try a custom ROM if I feel the need.
Thanks again
Click to expand...
Click to collapse
Good question. DO NOT flash bootloader in step 12 (newer bootloader) as Knox is likely to be tripped when you flash the 4.4.2 bootloader via odin in step 13. That was the instruction in Mobile odin (which could not flash bootloader). Flashing bootloader in step 12 is redundant.
shayind4
shayind4 said:
Good question. DO NOT flash bootloader in step 12 (newer bootloader) as Knox is likely to be tripped when you flash the 4.4.2 bootloader via odin in step 13. That was the instruction in Mobile odin (which could not flash bootloader). Flashing bootloader in step 12 is redundant.
shayind4
Click to expand...
Click to collapse
Firstly, nowhere does it state to flash the kitkat bootloader on a lollipop Rom in step 12 or 13.
By step 13 you should be running a lollipop Rom.
Secondly Knox should not trip when flashing a stock bootloader. The bootloader can be flashed independently in Odin.
Lastly Flashfire does NOT flash bootloaders.
If you don't flash the bootloader your Rom won't boot.
I suggest you digest the guide again.
3DSammy said:
In my case I am already on Lollipop 5.0.2 so have downloaded stock 4.4.2. When I read steps 12 and 13 I became a bit confused.
What I want is to be rooted (SuperSu) on stock lollipop (T800XXU1BOE2) so I'm assuming that in step 12 I will be using Flashfire to flash boot, recovery and system from the Samsung stock 5.0.2 lollipop firmware file. My confusion comes in step 13 as it seems redundant to flash the lollipop bootloader I just flashed in step 12. Is step 13's flashing the bootloader redundant if you flashed it in step 12?
Click to expand...
Click to collapse
It doesn't state to flash the boot loader in step 12? :what:
Your boot loader will be replaced when you downgrade to kitkat via Odin.
You need to reflash the lollipop boot loader after using Flashfire to install your Lollipop Rom or it won't boot.
Do i need to use a prerooted rom with flashfire, to maintain root, or can i just flash any original samsung room even if its not prerooted?
Paddiii said:
Do i need to use a prerooted rom with flashfire, to maintain root, or can i just flash any original samsung room even if its not prerooted?
Click to expand...
Click to collapse
No, this is the whole point of the post. Flashfire will root for you.
ashyx said:
It doesn't state to flash the boot loader in step 12? :what: ...
Click to expand...
Click to collapse
My bad, I saw the word "Boot" in step 12 and incorrectly assumed that was referring to a bootloader image.
Thanks for correcting me and your patience.
Sorry for being so long to give the feedback I promised.
I have one thing to say: thank you ! Your method works perfectly ! I am now running stock samsung lollipop on my T800 with knox untripped (0x0).
Little thing: your 4.4 file for the T800 isn't working (something wrong when flashing for the Hidden img). I took the same file but in XEF (I'm in France).
I just have a few questions now that could help other users:
-You say you are not sure about flashing another rom as long as it is with stock kernel and bootloader. But on a scale from 0 to 10 how sure are you about it working ? (I know you don't have any responsability in what happens, I just want a piece of advice).
- If for any reason I want to go back to stock, I just need to reflash the firmware with Odin ?
-Can I uninstall apps like the knox related ones without any risk about tripping knox ? (I think it is okay) (Edit: Ok I did it and knox not tripped. I used this tool http://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294 that is very convenient for that purpose )
Again thank you for this tutorial !
bibihub said:
Sorry for being so long to give the feedback I promised.
I have one thing to say: thank you ! Your method works perfectly ! I am now running stock samsung lollipop on my T800 with knox untripped (0x0).
Little thing: your 4.4 file for the T800 isn't working (something wrong when flashing for the Hidden img). I took the same file but in XEF (I'm in France).
I just have a few questions now that could help other users:
-You say you are not sure about flashing another rom as long as it is with stock kernel and bootloader. But on a scale from 0 to 10 how sure are you about it working ? (I know you don't have any responsability in what happens, I just want a piece of advice).
- If for any reason I want to go back to stock, I just need to reflash the firmware with Odin ?
-Can I uninstall apps like the knox related ones without any risk about tripping knox ? (I think it is okay) (Edit: Ok I did it and knox not tripped. I used this tool http://forum.xda-developers.com/android/software/debloater-remove-carrier-bloat-t2998294 that is very convenient for that purpose )
Again thank you for this tutorial !
Click to expand...
Click to collapse
The hidden.img failure is because its carrier/region related.For some it will flash ok, for others it will fail. It isn't actually required at all. Even if it fails to flash the rest of the Rom will.
All that needs to be done after that failure is to wipe cache in recovery.
As regards flashing custom roms. Remember your Rom is already custom as you have modified it.
I would say a good chance custom stock roms won't trip Knox as long as it's build properties reflect its a stock Rom.
However something like Cyanogen probably would trip Knox as its not based on stock.
I won't say this is for sure, but I think it's the general consensus.
Over one thousand views and literally only one person has bothered posting feed back.
ashyx said:
Over one thousand views and literally only one person has bothered posting feed back.
Click to expand...
Click to collapse
OK now two. I successfully applied your instructions yesterday. I really appreciate your guide.
What I did, differently is flashed with Odin using a Virtualbox Windows guest VM from my Ubuntu 14.04 host PC. It took a few days of false starts to get that working. Here is a "[How-To] Linux, Virtualbox and ODIN for your Samsung device", that I just posted to help others who do not have access to Windows machines.
Of the whole procedure the scariest moment was after flashing 4.4.2 stock with Odin over my devices 5.0.2 install. The reboot was too fast for me to get into recovery to wipe user data. I could not power off the SM-T800 and holding POWER + VOL DOWN just rebooted where it would hang displaying "SAMSUNG".
Booting into recovery ( POWER + VOL UP + HOME) had no effect what so ever. Finally I found that if I was fast enough I could reboot (POWER + VOL DOWN) and as soon as the screen went blank hold down the "POWER + VOL UP + HOME" buttons, then the tablet booted into recovery where wiping user data worked as described in your guide.
After completing your guide I am on stock Android 5.0.2 with Knox 0x0000.
My root apps so far:
Busybox
Titanium backup
GMD Gestures.
ES File Explorer with RW access to all partitions
System Uninstall Pro
Universal init.d
See Update below: "Unfortunately so far Viper4Android is not working as I cannot get SELinux permissive enabled either by the SELinux app or an init.d shell script using the "setenforce 0" command. From what I've read that is due to the Samsung stock bootloader."
V4A now works, see: "[HOW-TO] Installing Viper4Android (V4A) Audio on a Lollipop Tab S"
I took the high road and only froze the following KNOX related apps using titanium backup:
com.sec.enterprise.knox.attestation
KLMS Agent
KNOX
KNOX
KNOX II
KNOX SetUpWizardClient
So far I debloated 117Mgs of other apps using System Uninstall Pro. I bought the pro version of Flashfire just to show respect for Chainfire's development efforts. I have not tried to see if Flashfire's backups can be successfully restored yet.
Thanks again for your guide.:good:
Thanks for the feedback, it's constructive and encouraging for others to know It's successful.
For future reference you can disable auto reboot in Odin then manually reboot with POWER + VOL DOWN + HOME then as soon as it restarts switch to VOL UP while continuing to hold the other buttons.
The above procedure can be used at any point and will restart the device and get you into recovery every time.
just registered to suport OP, it works
I thought I did not need to run the su script as I could use kinguser w/o problems. But the flashfire is not compatible with other kinguser. Hope chainfire could remove this restriction. Maybe there is another way to flash rom or other mobile odin alternatives.
The OP could add a link about how to use odin for newbies like me. The odin 3.10 have different wording than previous version.
One more thing to mention is that the kingroot will work if you downgrade. I was in kitkat XXU1ANFB which is only one version up. The kingroot failed 20 times. XXU1ANF8 only takes 3 times to work.
After debloating in lolipop, the system is not smoother than before. The display has less contrast and dimer than kitkat. I did not wipe data/cache so my setting stays the same.
I rooted only for better battery performance as charging will take 10+ hours and could not hold charge at use with power cord plugged. It seems that the performance is not improved for this device after debloating.
vancities said:
I thought I did not need to run the su script as I could use kinguser w/o problems. But the fireflash is not compatible with other root authorization app. Hope chainfire could remove this restriction. Maybe there is another way to flash rom or other mobile odin alternatives.
The OP could add a link about how to use odin for newbies like me. The odin 3.10 have different wording than previous version.
One more thing to mention is that the kingroot will work if you downgrade. I was in kitkat XXU1ANFB which is only one version up. The kingroot failed 20 times. XXU1ANF8 only takes 3 times to work.
After debloating in lolipop, the system is not smoother than before. The display has less contrast and dimer than kitkat. I did not wipe data/cache so my setting stays the same.
I rooted only for better battery performance as charging will take 10+ hours and could not hold charge at use with power cord plugged. It seems that the performance is not improved for this device after debloating.
Click to expand...
Click to collapse
I'm not quite sure what you're saying, but I think youre saying you had success?
Regarding Odin, it is not the intention of this post to spoon feed every single step, some knowledge is expected prior to following this guide. Anything relating to the actual process in this guide is explained in detail. Any other information you would ever require is already posted on XDA.
ashyx said:
I'm not quite sure what you're saying, but I think youre saying you had success?
Regarding Odin, it is not the intention of this post to spoon feed every single step, some knowledge is expected prior to following this guide. Anything relating to the actual process in this guide is explained in detail. Any other information you would ever require is already posted on XDA.
Click to expand...
Click to collapse
I had success. What I mean is the step 6 7 8 9 are not necessary if flashfire could work with kinguser.
Also kingroot only works on XXU1ANF8 and maybe lower. I mentioned this because in other thread about kingroot, someone got success but most did not.
So my feedback . everything was great , was a little confused about Odin at first but like you said everything can be found on xda. Need to be on the most recent Odin which I believe is 3.10. Kingroot took forever to root but I believe it has something to do with connectivity to the servers. So my tab s is rooted no Knox counter. I'm hoping the custom tw rom doesn't revert all the hard work ? thanks again op.