I got an unlocked ph-1 phone for my son. When it starts it says the bootloader could not be checked and then boots into android. How do I know if it is rooted or not?
tornadog said:
I got an unlocked ph-1 phone for my son. When it starts it says the bootloader could not be checked and then boots into android. How do I know if it is rooted or not?
Click to expand...
Click to collapse
You could use DevCheck, which will not only tell you whether the device is rooted, but provides a lot of other information about the hardware and operating system of the device as well. In DevCheck, go to the System tab and scroll down to the Operating Sytem panel. There's a "Root access" item which will say "Device is rooted" or "Device is not rooted" as applicable.
Related
This tablet was bought from a online warehouse as a returned item. Just for kicks I powered up using the power and - volume. There is Four icons "RCK, Android, USB, and Wipe Data. I have up graded to the JB OTA and I know it had been reset before I got it. Now if I am right has someone tried to root this tablet? I base that on the RCK icon which when selected just shows the android on his face with a red exclamation.
There is no text showing that the boot loader has been unlocked. So where do I go from here to unlock and root ?
That's the normal ASUS JB bootloader, if there isn't any text when turning the tablet on saying: "Device unlocked" it isn't. So if you want to unlock download the unlocking tool apk from ASUS website, install and run on your tablet. After unlocking just check the development section of the forums and get informed on how to install recovery (CWM or TWRP), root and custom ROMs.
Thanks
jgaf said:
That's the normal ASUS JB bootloader, if there isn't any text when turning the tablet on saying: "Device unlocked" it isn't. So if you want to unlock download the unlocking tool apk from ASUS website, install and run on your tablet. After unlocking just check the development section of the forums and get informed on how to install recovery (CWM or TWRP), root and custom ROMs.
Click to expand...
Click to collapse
Thanks for the quick reply. I would of been surprised if it had of been rooted and Amazon.com's techs hadn't of caught it when it was returned.
Going to hold off rooting it until the warrantee is gone. Still having nightmares about my Viewsonic gTablet turning into a cyborg tablet thingy and attacking me. All because I just had to try every ROM I could cram down it.
Although unlikely, it could still be rooted if it was done prior to the jb update, and it could still be locked even if rooted. Download root checker from the market and you can safely test this.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Okay, so I have this phone and the info attached to the imei DCNO Prod Test phone. It has the following build listed N900VVREBMJ5 test-keys. I checked for root access with a app and it didn't have root access. I tried to root with odin3 root_de_la etc and it came up with an error and was basically soft bricked. Was able to reload the pit file and eventually get it working again. I clearly don't know what I'm doing and bought this phone online and have learned very little since last night. It loads up with the custom logo etc etc. I'm looking load a regular stock rom onto or just a custom one, but no matter what I do I get an error.. Can anybody help.. thanks
Use kingo root.... Google it. It works on all of the builds for n900v.
Sent from my SM-N900V using Tapatalk
shiftr182 said:
Use kingo root.... Google it. It works on all of the builds for n900v.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
as stated on the general tab, the most important thing is to check if secureboot is enabled first!!! Turn phone off, turn on holding power, home, volume down and check to see if it say secureboot enabled. If it says disabled you might be famous
2swizzle said:
as stated on the general tab, the most important thing is to check if secureboot is enabled first!!! Turn phone off, turn on holding power, home, volume down and check to see if it say secureboot enabled. If it says disabled you might be famous
Click to expand...
Click to collapse
It's enabled. Btw, it says rooted already, but it fails to remove root or reroot. I also can't load anything on it...
topurdue said:
It's enabled. Btw, it says rooted already, but it fails to remove root or reroot. I also can't load anything on it...
Click to expand...
Click to collapse
Anyways, my problem is this. It says I'm rooted. I installed SuperSU it says "There is no SU binary installed and SuperSU cannot install it. This is a problem!" Safestrap reads, "not rooted not active". Kingo states root "yes". I don't know what to do any help whould be great
topurdue said:
Anyways, my problem is this. It says I'm rooted. I installed SuperSU it says "There is no SU binary installed and SuperSU cannot install it. This is a problem!" Safestrap reads, "not rooted not active". Kingo states root "yes". I don't know what to do any help whould be great
Click to expand...
Click to collapse
Anyways, i wiped deleted restarted and now i have root access.. blah blah ill be back im sure.
Greetings all. I was under the impression that one could download the latest OTA's from the images page from Google and sideload them so the phone wouldn't wipe itself in the process.
My version number is still at the April security patch but I downloaded the May patch MTC19T, followed the instructions on the google page but for some reason it didn't sideload. In fact after I issued the command to sideload it said it was loading it but the came back with a "no device connected." No I know it WAS connected because I ran the "adb devices" before I issued the load command and it did indeed return my device serial #.
Any help or ideas? I'm using terminal on mac and I've never had problems before. I used my mac and terminal to return the device to factory original after running Pure Nexus for months (because of work stuff) so I know it works. I'm bootloader locked (is that the problem?) and factory stock image, stock recovery...just the way the IT department likes it
Vref said:
Greetings all. I was under the impression that one could download the latest OTA's from the images page from Google and sideload them so the phone wouldn't wipe itself in the process.
My version number is still at the April security patch but I downloaded the May patch MTC19T, followed the instructions on the google page but for some reason it didn't sideload. In fact after I issued the command to sideload it said it was loading it but the came back with a "no device connected." No I know it WAS connected because I ran the "adb devices" before I issued the load command and it did indeed return my device serial #.
Any help or ideas? I'm using terminal on mac and I've never had problems before. I used my mac and terminal to return the device to factory original after running Pure Nexus for months (because of work stuff) so I know it works. I'm bootloader locked (is that the problem?) and factory stock image, stock recovery...just the way the IT department likes it
Click to expand...
Click to collapse
Have you tried switching ports?
Bootloader locked will cause a problem..
You need to be unlocked to issue the fastboot commands
I had the same issue with the no device found after issuing the ./adb sideload "ota.zip" command.. I simply unplugged the cable from the machine and plugged it back in, and the system found the device and pushed the .zip. However, I've also noticed that after pushing the update (done this three times now) it still boots up showing the April 2nd patch update instead of the May patch.
edit: Forgot to note that I'm also using a Mac, no root, stock, etc, etc...
DJBhardwaj said:
Have you tried switching ports?
Click to expand...
Click to collapse
Nope...didn't think that would be an issue but I can always try.
brichardson1991 said:
Bootloader locked will cause a problem..
You need to be unlocked to issue the fastboot commands
Click to expand...
Click to collapse
Is there no other way to load the OTA? When I hit "Check for updates" it always comes back with "system up to date."
I can see the device with ./adb devices, but there's no way to sideload while locked bootloader?
mgrass said:
I had the same issue with the no device found after issuing the ./adb sideload "ota.zip" command.. I simply unplugged the cable from the machine and plugged it back in, and the system found the device and pushed the .zip. However, I've also noticed that after pushing the update (done this three times now) it still boots up showing the April 2nd patch update instead of the May patch.
edit: Forgot to note that I'm also using a Mac, no root, stock, etc, etc...
Click to expand...
Click to collapse
Sounds like with locked bootloader we may be stuck with the April update. I just don't understand why when I force it to look for the update it says there isn't one when there clearly is one...its on Googles own site
brichardson1991 said:
Bootloader locked will cause a problem..
You need to be unlocked to issue the fastboot commands
Click to expand...
Click to collapse
You're talking about flashing the factory images with fastboot, he's talking about sideloading the full OTA.
Vref said:
Nope...didn't think that would be an issue but I can always try.
Is there no other way to load the OTA? When I hit "Check for updates" it always comes back with "system up to date."
I can see the device with ./adb devices, but there's no way to sideload while locked bootloader?
Sounds like with locked bootloader we may be stuck with the April update. I just don't understand why when I force it to look for the update it says there isn't one when there clearly is one...its on Googles own site
Click to expand...
Click to collapse
Your bootloader status is irrelevant. I'm not sure why it isn't working for you but it definitely isn't because of your bootloader.
Heisenberg said:
Your bootloader status is irrelevant. I'm not sure why it isn't working for you but it definitely isn't because of your bootloader.
Click to expand...
Click to collapse
Roger that. Thanks Heisenberg... I'll give it another go tonight.
Vref said:
Roger that. Thanks Heisenberg... I'll give it another go tonight.
Click to expand...
Click to collapse
Can we get a confirmation that you are using the proper file? Mind posting the zip name?
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Can we get a confirmation that you are using the proper file? Mind posting the zip name?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
LOL...what, no faith in my reading skills? :laugh::laugh:
It was the correct file. Just tried it again and initially got the same result, adb devices returns the phone serial# but commands won't sideload. Swapped ports three times (on a macbook with only two USB ports ) and it finally updated. Checked build# afterwards and I'm now on 19T. Thanks guys(gals? who knows, its the internet)!
Vref said:
LOL...what, no faith in my reading skills? :laugh::laugh:
It was the correct file. Just tried it again and initially got the same result, adb devices returns the phone serial# but commands won't sideload. Swapped ports three times (on a macbook with only two USB ports ) and it finally updated. Checked build# afterwards and I'm now on 19T. Thanks guys(gals? who knows, its the internet)!
Click to expand...
Click to collapse
How in the world did it finally work? Lol well as long as things are running fine, that's great! I use a mac as well so I was hoping it wasn't anything specific to Apple causing trouble.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
How in the world did it finally work? Lol well as long as things are running fine, that's great! I use a mac as well so I was hoping it wasn't anything specific to Apple causing trouble.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Dunno how or why it finally took but this isn't the first time I've had to switch from port to port (like a drunken sailor) to get it to see the phone but I've always attributed that to Android File Transfer being a little b!tch. I can tell you when I restored from Pure Nexus and relocked the bootloader two weeks ago it worked 4.0....not a clue as to why it got all fussy today.
Vref said:
Nope...didn't think that would be an issue but I can always try.
Is there no other way to load the OTA? When I hit "Check for updates" it always comes back with "system up to date."
I can see the device with ./adb devices, but there's no way to sideload while locked bootloader?
Sounds like with locked bootloader we may be stuck with the April update. I just don't understand why when I force it to look for the update it says there isn't one when there clearly is one...its on Googles own site
Click to expand...
Click to collapse
my friends nexus 6 was showing the same problem "system upto date" even though it had april patch. i tried updating all his google apps via playstore. after updating all his google apps i tried "Check for updates" and voilà it was working, it downloaded the 60mb may update.
billamin said:
my friends nexus 6 was showing the same problem "system upto date" even though it had april patch. i tried updating all his google apps via playstore. after updating all his google apps i tried "Check for updates" and voilà it was working, it downloaded the 60mb may update.
Click to expand...
Click to collapse
Cool. Glad you got it working.
Hello:
I am trying to follow the instructions to unlock the bootloader on my Sprint G900P Galaxy S5.
I installed the ADB SDK, the Samsung USB driver, turned on USB debugging on my phone, and connected it to my computer.
I typed adb reboot bootloader and the phone rebooted into a screen to download software to it.
Next, I typed fastboot oem unlock and I get a message on the screen < waiting for any device >
and it does nothing.
This is strange because obviously the computer was able to send the adb command to the phone so there is communication.
Why would is stop at the fastboot step?
Any ideas?
Thanks,
Neil
Ummm dude your booloader is already unlocked since it's from Sprint. You just go into your Dev options and toggle on OEM UNLOCK and your all set
gurnsey101 said:
Ummm dude your booloader is already unlocked since it's from Sprint. You just go into your Dev options and toggle on OEM UNLOCK and your all set
Click to expand...
Click to collapse
When I go to Developer Options, I do not see an OEM UNLOCK option. Any ideas?
NeilAgg said:
When I go to Developer Options, I do not see an OEM UNLOCK option. Any ideas?
Click to expand...
Click to collapse
It's most likely already unlocked.
kicker63 said:
It's most likely already unlocked.
Click to expand...
Click to collapse
I went to Google Play Store and installed the Root Checker by Clivin Inc.
When I ran the app, it says: Your device is not rooted
I am not sure where to go from here.
NeilAgg said:
I went to Google Play Store and installed the Root Checker by Clivin Inc.
When I ran the app, it says: Your device is not rooted
I am not sure where to go from here.
Click to expand...
Click to collapse
Hi,
Just wondering what are you going to achieve ...
1. Don't bother with any "oem unlock" options as there is no any in your phone model. Your bootloader is uncloked by default and that's it.
2. Rooting is different story - if you didn't root your device yet then the root checkers will tell you exactly this -> so you need to root your phone to get different reply
Many40 said:
Rooting is different story
Click to expand...
Click to collapse
I did not realize that. Thanks for the info.
I used the SkipSoft Unified Toolkit to root the device.
Thanks,
Neil
i know there are a few ways to root the S10+, now we are a half year futher and my question is; what is the easiest way to root the S10+???? because i can't get it done.....
Dont rkot you will regret it
Hi, you can root only if you own an Exynos model, check this first...
The easiest way is to root with magisk without twrp in my opinion, all instructions are in S10 Rom thread, it is the same for S10+. Remember that it will trip KNOX and you will not be able to use Samsung pay, all other apps as far as i know you can get work properly. For me SPay was not relevant, because it is not working in my country.
I have rooted my phone a month ago, installed AdAway and AfWall, some addition open sourse apps and i am totally happy with it=)
lambik333 said:
i know there are a few ways to root the S10+, now we are a half year futher and my question is; what is the easiest way to root the S10+???? because i can't get it done.....
Click to expand...
Click to collapse
I am stuck on canary Magisk not allowing me to patch the standard AP file I loaded onto my phone. It constantly spins "Checking for updates" and never lets me go to install and then patch the AP. Yes I have booted into recovery and erased al data and caches and checked that OEM unlock is greyed out and boot loader is unlocked.
https://imgur.com/lrZSjEm
[Imgur](https://i.imgur.com/lrZSjEm.jpg)
Sahmadsaab said:
Dont rkot you will regret it
Click to expand...
Click to collapse
What will we miss or why will we regret?
Issues rooting
Hey guys,
I am having issues rooting an S10 +, I used the guide to patch the AP file using magisk and then flashed it using odin, followed the rest of the guide to the letter.
Then once the device finally booted, it showed me the set up screen, then we back to the Samsung splash screen and had a a warning in red across the top of the screen that said "Only official binarys are allowed" and just kept on boot looping.
I then flashed the stock rom using odin, I have used the same process on an S10 without any issues.
Does anyone know where I may have gone wrong ?
AlienSexGod said:
I am stuck on canary Magisk not allowing me to patch the standard AP file I loaded onto my phone. It constantly spins "Checking for updates" and never lets me go to install and then patch the AP. Yes I have booted into recovery and erased al data and caches and checked that OEM unlock is greyed out and boot loader is unlocked.
https://imgur.com/lrZSjEm
[Imgur](https://i.imgur.com/lrZSjEm.jpg)
What will we miss or why will we regret?
Click to expand...
Click to collapse
Hi I'm having the same problem!
I found a solution because I wanted to restore the root of the device because I needed it