Is my GNote GT-N7000 rooted or not?! - Galaxy Note GT-N7000 Q&A, Help & Troubleshooting

My GNote is confused.
On the one hand, BusyBox installer says that it is rooted
but the install fails.
But, when I run RootChecker, it says "Sorry, this device
does not have proper root access.
I have only had this SGN for about two weeks and I would
like very much to have a working root so as to install
and use BusyBox, Titanium Backup, SSH, SFTP, rsync, et.al.
suggestions appreciated for a noob.
ta

May be its partial root.
Download philz kernel xxlri from his thread and flash it from recovery. Reboot and update the su binaries. It should be rooted

"philz kernel xxlri"
OK, I'll go check it out. :good:
ta

to know if you are rooted: download a root explorer, there are many free ones (solid explorer...), go to /system, and try to create a new file. if it is forbidden, you have partial root. if you may, your phone is rooted.
otherwise, just dl philz kernel, flash through cwm, and you will be rooted. but the question is: which philz kernel?
depends on the rom you have. check the rom you have, and dl the appropriated kernel in philz thread.
my advice is to always have on your phone a zip of a rom, and the zip of the associated kernel. if you do something wrong, you always have the possibility to reflash easily a rom only by cwm.
good luck !

Related

Help: Stock GB to ICS stunner transition problem.

Facing big problem:
- Over a stock phone: flashed SGN_XX_OXA_KJI using PC odin.
- Flashed CF root kernal + CWM using BAT file. (KJ1)
- Phone was rooted and CWM installed.
- When it says flash CF kernel by placing on SD card, it think i did a mistake and using mobile odin I flashed KJ1 kernel again (I dont know which kernel to be flashed and where to get that).
- Seemingly phone got bricked and wont boot.
Somehow I managed to access the download mode.
- Flashed stock firmware GTN-7000_CPW_Blah
- Phone came back to life
- flashed SGN_XX_OXA_KJI using PC odin again
- Flashed CF root kernal + CWM using BAT file. (KJ1)
- Phone was rooted and CWM installed.
- Straightaway rebooted to CWM, did a full wipe and installed ICS stunner 1.4.19
- Phone booted.
Now the problems:
- Can't access root. No mobile odin, no CWM.
- Can't copy files to int/ext card. Phone hangs/PC hangs.
- Am able to access the download mode though.
- Please help. In case someone from India can share his phone number with me and guide me how to come out of this.
rockstar1630 said:
Facing big problem:
- Over a stock phone: flashed SGN_XX_OXA_KJI using PC odin.
- Flashed CF root kernal + CWM using BAT file. (KJ1)
- Phone was rooted and CWM installed.
- When it says flash CF kernel by placing on SD card, it think i did a mistake and using mobile odin I flashed KJ1 kernel again (I dont know which kernel to be flashed and where to get that).
- Seemingly phone got bricked and wont boot.
Somehow I managed to access the download mode.
- Flashed stock firmware GTN-7000_CPW_Blah
- Phone came back to life
- flashed SGN_XX_OXA_KJI using PC odin again
- Flashed CF root kernal + CWM using BAT file. (KJ1)
- Phone was rooted and CWM installed.
- Straightaway rebooted to CWM, did a full wipe and installed ICS stunner 1.4.19
- Phone booted.
Now the problems:
- Can't access root. No mobile odin, no CWM.
- Can't copy files to int/ext card. Phone hangs/PC hangs.
- Am able to access the download mode though.
- Please help. In case someone from India can share his phone number with me and guide me how to come out of this.
Click to expand...
Click to collapse
Follow this to the dot !!
http://forum.xda-developers.com/showthread.php?t=1614443
Flashed rooted stock odex GB
Now root checkers are confirming that phone is rooted
But can't copy any file in system folder
shall i go ahead and patch the abyss kernel?
Edit:
Was able to copy files in system folder using x explorer after granting r/w rights to the system folder.
Shall I proceed ahead to patch abyss kernel.
abyss kernel patched successfully with CWM. Installed latest stunner. But cant get tablet functionality. :-(
Please help.
Never ever ever ever trust root checkers. The only way to know for sure if you really have root access is to try and paste a file into /system folder. If you can do it, you have root. If you cannot, you have no root, it's as simple as that.
This means that you never had GB root in the first place, hence you ICS root problems.
chasmodo said:
Never ever ever ever trust root checkers. The only way to know for sure if you really have root access is to try and paste a file into /system folder. If you can do it, you have root. If you cannot, you have no root, it's as simple as that.
This means that you never had GB root in the first place, hence you ICS root problems.
Click to expand...
Click to collapse
...totally agree...that is one of my first mistake flashing the first cooked rom
giogroove said:
...totally agree...that is one of my first mistake flashing the first cooked rom
Click to expand...
Click to collapse
I was able to copy paste in system folder in gb after granting rw permission. Now in pics able to do the same. Anyways can someone summarize the entire steps that I should take from scratch that will bring the desired functionality. Do post the file links along. I ll really appreciate.

[Q] Rom manager vs mobile odin where is cwm?

I was previously on HTC desire hd rooted and bought Rom manager.
Now I've got a new note and pc odin flashed lpy the 638mb one.
I then rooted by copying the zips of su busybox and cwm to use in recovery. Not chainfire.
Recovery install from ext sd. Cwm then su.
That went fine. Have root.
But no clockworkmod installed.
Rom manager offers but asks which phone I have and the note isn't there! Just galaxy s1 and 2 atandt stuff etc.
Id like to flash other stuff in the future and feel naked without cwm.
1. Please what do?
2. Should I pay for mobile odin now? Is Rom manager not good. this board talks Always about mobile odin.
3. What's this I hear about super su? What's wrong with su? She getting old droopy woman?
The method you used will only give you a temporary CWM, and after you reboot your mobile (as what you did), its back to stock recovery without CWM.
If you really want CWM in your recovery, the only way is to flash the kernel with CWM. You can use mobile odin to flash the ZImage file (kernel with cwm).
Good luck.

Is Galaxy S advance supported with Rom Manager? If Not, other ways to change ROMs?

Hello,
I have recently purchased a Galaxy S Advance phone, and I am quite new to the android os.
I have read already many guides and forums about the whole process of rooting / flashing etc, so I have some knowledge of the terminology.
I already have a rooted phone with GB on it (yes, I know JB is about to come out officially ) and I wanted to change some of the UI elements.
I installed the rom manager app by koush, but yet to use it because I saw that in the past that the phone wasn't supported.
My question is: Does ROM Manager support this phone? Can I go ahead and flash CWM on it from the rom manager app, and then use it to flash other roms?
If not, which is the best solution to backup and replace roms? ODIN?
Thanks,
Одг: Is Galaxy S advance supported with Rom Manager? If Not, other ways to change ROM
YMatrix said:
Hello,
I have recently purchased a Galaxy S Advance phone, and I am quite new to the android os.
I have read already many guides and forums about the whole process of rooting / flashing etc, so I have some knowledge of the terminology.
I already have a rooted phone with GB on it (yes, I know JB is about to come out officially ) and I wanted to change some of the UI elements.
I installed the rom manager app by koush, but yet to use it because I saw that in the past that the phone wasn't supported.
My question is: Does ROM Manager support this phone? Can I go ahead and flash CWM on it from the rom manager app, and then use it to flash other roms?
If not, which is the best solution to backup and replace roms? ODIN?
Thanks,
Click to expand...
Click to collapse
Other way to change roms is custom recovery. On GB TWRP, on JB CWM.
Sent from Galaxy S Advance
Thanks fro your quick reply!
And what about ROM Manager? Does it work in this device?
YMatrix said:
Thanks fro your quick reply!
And what about ROM Manager? Does it work in this device?
Click to expand...
Click to collapse
I think it is not working. It is not supported. Way we install custom ROMs: download ROM zip, transfer to SD, then go to recovery and install it from there.
I checked TWRP supported devices list (tried to link it but forum wont allow new users to link ) and I don't see the galaxy advance S on their list either.
Is there a special mod version for this device?
And another question, if installed, will this wipe the current phone data or just the recovery loader? Since I want to backup my current ROM (+ contacts, settings etc.) before doing anything sketchy...
YMatrix said:
I checked TWRP supported devices list (tried to link it but forum wont allow new users to link ) and I don't see the galaxy advance S on their list either.
Is there a special mod version for this device?
And another question, if installed, will this wipe the current phone data or just the recovery loader? Since I want to backup my current ROM (+ contacts, settings etc.) before doing anything sketchy...
Click to expand...
Click to collapse
You have GB? Look here.
On I9070 recovery is on the same partition as kernel. So it can't be installed separatly. It is ported. You need to install this kernel, or CoCore. If you install with Odin - you will increase binary counter. For installation with ADB shell, or Terminal emulator (app from market) you need root - and it will not increase bc.
So I am guessing I will use the dd command line way since it doesn't increase the binary counter (why would we want to do that ).
Is it possible to backup the current ROM before flashing it with the TWRP modified ROM?
And another thing, since I will be using other ROMs, how can i add the TWRP recovery loader to them (you said that the recovery is on the same partition as the kernel, making me believe that each ROM I load will need to have TWRP on it)?
YMatrix said:
So I am guessing I will use the dd command line way since it doesn't increase the binary counter (why would we want to do that ).
Is it possible to backup the current ROM before flashing it with the TWRP modified ROM?
And another thing, since I will be using other ROMs, how can i add the TWRP recovery loader to them (you said that the recovery is on the same partition as the kernel, making me believe that each ROM I load will need to have TWRP on it)?
Click to expand...
Click to collapse
No, only JetMOD have embendend kernel too. And it have TWRP.
Hm, another thing. You better use non binary counter increaing root method. But it need you to flash whole firmware with Odin. And maybe you loose data. But if you do not do factory reset - it will be ok.
Sorry, I didn't understand your last post.
YMatrix said:
Sorry, I didn't understand your last post.
Click to expand...
Click to collapse
If you want to get TWRP with dd command you need to root your phone first.
There are 2 root methods. One that increase binary counter, and one that do not..
With one that do not increase - you need to flash whole firmware with Odin. And by doing that you might need to do factory reset. That will cause your data and app delete. You can try to boot, maybe it will be ok.
Oh, I already said I have a rooted device, so this wont be an issue.
What I asked was:
1) If I can backup my current ROM before installing the TWRP ROM you linked (in case something goes wrong).
2) When I install other modified ROMs, will they override the TWRP I installed, or just change the kernel system leaving TWRP in the recovery?
Одг: Is Galaxy S advance supported with Rom Manager? If Not, other ways to change ROM
YMatrix said:
Oh, I already said I have a rooted device, so this wont be an issue.
What I asked was:
1) If I can backup my current ROM before installing the TWRP ROM you linked (in case something goes wrong).
2) When I install other modified ROMs, will they override the TWRP I installed, or just change the kernel system leaving TWRP in the recovery?
Click to expand...
Click to collapse
Didn't pay attention.
You have backup option in TWRP, and you can restore it.
Custom roms do not have connection with kernel, just JetMod who do have kernel with TWRP too.
P.S. lol you confuse me. TWRP is kernel related, nothing to do with ROM.
When you want stock kernel back, just flash your firmware from sammobile.com.
So you need to change kernel to get TWRP. And with TWRP you do backup of system.
Sent from Galaxy S Advance
Bos manForu
Hmmmm, now I am a little confused.
Since I don't want to touch the kernel (yet), all I want to do is change the ROM (as in UI changes etc...).
I wanted to backup my current ROM and then load other ROMS.
I started off with ROM Manager because it seemed to answer what I wanted to do, but as you said ROM Manager doesn't support this phone and we went from there to TWRP.
Since I now get that TWRP is kernel related only and not ROM management, what would you advise right now for:
1) Backing up the current ROM
2) Loading other ROMs to the device?
YMatrix said:
Hmmmm, now I am a little confused.
Since I don't want to touch the kernel (yet), all I want to do is change the ROM (as in UI changes etc...).
I wanted to backup my current ROM and then load other ROMS.
I started off with ROM Manager because it seemed to answer what I wanted to do, but as you said ROM Manager doesn't support this phone and we went from there to TWRP.
Since I now get that TWRP is kernel related only and not ROM management, what would you advise right now for:
1) Backing up the current ROM
2) Loading other ROMs to the device?
Click to expand...
Click to collapse
You can do that only with TWRP.
And did you read ROM manager description?
* Flash your recovery to the latest and greatest ClockworkMod recovery.
Click to expand...
Click to collapse
For ROM manager you need custom recovery. And for I9070 that is embended in kernel. Full stop.
And it is connected to CWM, not to TWRP. We do not have CWM for Android 2.3.6. ported.
P.S. So to close this:
- You can't do any backup, installation of ROMs without custom recovery (in our case TWRP) on our phone.
- Custom recovery couldn't be installed separatly - it is embended inside kernel file - and has nothing to do with ROM.
It is clear now?
I think I got you now
1) CWM doesn't work on my phone because the recovery is attached to the kernel.
2) In order for me to backup my ROM I need to install the kernel with TWRP embedded (the one you linked me).
3) I also can't backup my current kernel without TWRP so in order for me to have TWRP I will be doing #2 without any backup? I am guessing this is the part where bricking has a chance of occurrence?
YMatrix said:
I think I got you now
1) CWM doesn't work on my phone because the recovery is attached to the kernel.
2) In order for me to backup my ROM I need to install the kernel with TWRP embedded (the one you linked me).
3) I also can't backup my current kernel without TWRP so in order for me to have TWRP I will be doing #2 without any backup? I am guessing this is the part where bricking has a chance of occurrence?
Click to expand...
Click to collapse
CWM = TWRP
Both are custom recoveryes. Not the same, but same purpose.
1) Our phone have same partition for kernel and recovery. So we can't install it separatly
2) You can backup kernel, but you will need Terminal emulator, and similiar command like instalation of other kernel
Code:
$ su
# dd if=/dev/block/mmcblk0p15 of=/sdcard/boot.bin
# reboot
This will backup your stock kernel on your sdcard. You can install it later this way (ofcourse if boot.bin file is on your sd)
Code:
$ su
# dd if=/sdcard/boot.bin of=/dev/block/mmcblk0p15
# reboot
You always can flash your stock kernel, Download mode do not have anything to do with kernel and recovery partition.
If this is little hard for you, just install custom kernel with TWRP. Or do not do anything. :laugh:
P.S. Trust me, you can't hard brick device with installing kernel. I am tester, and I flashed at least 10 non booting kernels, and 50+ booting ones.
I do trust you, just trying to get an understanding of how the things work on these devices.
So I now understand the backing up and flashing commands (I would like to know how you knew the mmcblk0p15 was the kernel partition for this phone), so where does the "Download mode" come in handy if u can flash directly from a terminal window?
If for some reason the flash wasn't successful, can you enter download mode and restore the backup you created?
YMatrix said:
I do trust you, just trying to get an understanding of how the things work on these devices.
So I now understand the backing up and flashing commands (I would like to know how you knew the mmcblk0p15 was the kernel partition for this phone), so where does the "Download mode" come in handy if u can flash directly from a terminal window?
If for some reason the flash wasn't successful, can you enter download mode and restore the backup you created?
Click to expand...
Click to collapse
Most likely you will have to flash whole firmware if something goes wrong. I told you what I know.
And if you can go in TWRP recovery, it can restore krenel with other things you backed up. And you can flash new kernel in TWRP too.
Somewhere is written what partition is for what. I do not know that. And developers told us what partition is for kernel and recovery.
I do not think that that thing with restoring downlaod mode will work. Newer tried or heard of it.
I tried to explain you, but maybe I was little confusing. :angel: My english is not great, and I didn't provide 1, 2, 3... steps explanation. Like I throw everything to you. :laugh::laugh::laugh:
:laugh: More or less I understand you :laugh:
So to sum up:
1) Create a backup of the current kernel
2) Flash Stock Kernel + TWRP
if all goes well....
3) Create full phone phone backup from TWRP
4) flash custom ROMs (or kernels) with TWRP
Hows that?
YMatrix said:
:laugh: More or less I understand you :laugh:
So to sum up:
1) Create a backup of the current kernel
2) Flash Stock Kernel + TWRP
if all goes well....
3) Create full phone phone backup from TWRP
4) flash custom ROMs (or kernels) with TWRP
Hows that?
Click to expand...
Click to collapse
That is ok.
And you backup old kernel that you can easy go back to stock one. Without flashing whole firmware, when you want stock. Like you want to go to service for warranty or something like that...

Unable to flash from 4.4.2 to stock or rooted Lollipop

I tried what I was advised here: http://forum.xda-developers.com/not...pgrading-stubborn-software-t3228423?nocache=1
I can successfully flash it but Kit Kat still boots up every time. I don't know what to do. Maybe twrp? How do I do that.
May also be relevant that I cannot seem to boot into recovery to do the fixes after I flash. 4.4.2 stil comes up.
Cheers!
You could just use Odin to go back to stock, always worked for me. The only reason I could think that you could have problems is that you have a custom rom already that changes your build and model.
Sent from my SAMSUNG-SM-N900A using Tapatalk
If you need to install stock rom you need to make sure build number is N900AUCUCNC2 and then use odin to install .
If you need to install root rom install Towelroot from play store and make sure wifi or data network is on during root then install SuperSU
BusyBox (open BusyBox and install from inside ), "Safestrap-HLTEATT-NC2-3.75-B03" recovery from fourm put your prerooted rom in sd card open Safestrap and boot to recovery you will be able to install rooted rom from there .

Backup tool

Will be getting my tab S2 710 in 2 days and would like to root it ofc from the start, but like everyone is saying first make a backup!. Is there a tool or a program that will make an backup of not rooted device? And if anything goes wrong while rooting I would be able to restore that backup? Thx for the help!
not that I know of. I rooted and made backup with TWRP before changing kernels or any other modifications and had no problem. Good luck.
Backup with TWRP BEFORE making any changes or rooting.
but TWRP is a custom recovery right? So first I need to flash your TWRP port then make a backup and then flash kernel and root via Odin?
You don't need to flash a kernel just backup with twrp then flash supersu 2.65 with twrp.
But if my device will be with 5.1.1 I will have to use your custom kernel for root to work, right? So if I understand you correctly I need to do all these things to get backup + root:
1. Flash TWRP with Odin from here: http://forum.xda-developers.com/tab-s2/development/recovery-twrp-2-8-7-x-lollipop-5-1-1-t3205686
2. Backup with TWRP
3. DL latest stable SuperSu form here: https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip
4. Flash it
Thats all?
Correct
Got my 710 and it's 5.0.2 will this root method still work? btw its from Poland region T710XXU2AOJ4. SO I need to flash only the twrp_2.8.7.1_LL_5.0.2_t710 ? BTW is there any noticeable difference with 5.1.1 ? Can I upgrade to this - http://www.sammobile.com/firmwares/download/54572/T710XXU1BOH7_T710BNN1BOH7_BNN/ as I understand I would have to flash it with Odin. Thx for your help a lot!

Categories

Resources