Related
New MotoX from sprint.
android version 4.2.2
baseband msm8960pro_bp_2323.020.90.00r
kernel 3.4.42.-xline.
system version 139.14.1
build 13.9.0q2.x-116-mx-17-57-1
i did a fair amount of searching but could not find the proper instructions for obtaining root access for the moto x. Need root access or this device would be a deal breaker.
Can someone point me to a link? I would be much appreciated. Thanks Listers!!!
You must of not even attempted to do any real looking. This forum is not that large for the Moto X and there is plenty of information for you to see.
1) you have a sprint phone so you can unlock the Bootloader, install TWRP, get root no matter the Android version
2) there is a clearly titled post in one of the subforums that will tell you how to get root
BrokenWall said:
You must of not even attempted to do any real looking. This forum is not that large for the Moto X and there is plenty of information for you to see.
1) you have a sprint phone so you can unlock the Bootloader, install TWRP, get root no matter the Android version
2) there is a clearly titled post in one of the subforums that will tell you how to get root
Click to expand...
Click to collapse
I did search the web and the forums; I'm sorry. it was a long day, i had just purchased the phone and wanted to make sure i didn't brick it. I have rooted/jailbroken several other devices but wanted to know if the latest ota update would cause a problem for that.
Again, I'm sorry for for the excess forum baggage.
I'll try again.
BrokenWall said:
You must of not even attempted to do any real looking. This forum is not that large for the Moto X and there is plenty of information for you to see.
1) you have a sprint phone so you can unlock the Bootloader, install TWRP, get root no matter the Android version
2) there is a clearly titled post in one of the subforums that will tell you how to get root
Click to expand...
Click to collapse
that simple? i have the tmobile version with an unlocked bootloader but i been looking for ways to root it and i have not been able to do it, so you saying that if i install TWRP that would obtain root automatically?
moises1204 said:
that simple? i have the tmobile version with an unlocked bootloader but i been looking for ways to root it and i have not been able to do it, so you saying that if i install TWRP that would obtain root automatically?
Click to expand...
Click to collapse
I read where a previous method of rooting (pwnmoto or whatever) was shut off by the latest ota.
Please help a new guy out.
http://forum.xda-developers.com/showthread.php?t=2487635
this thread is what I found. Please advise if this is the correct method. Thank you all, and sorry if I'm wanting to be sure I'm doing the right thing.
Thanks listers...I do very much appreciate any help.
bullpen7979 said:
I read where a previous method of rooting (pwnmoto or whatever) was shut off by the latest ota.
Please help a new guy out.
http://forum.xda-developers.com/showthread.php?t=2487635
this thread is what I found. Please advise if this is the correct method. Thank you all, and sorry if I'm wanting to be sure I'm doing the right thing.
Thanks listers...I do very much appreciate any help.
Click to expand...
Click to collapse
ownmoto or whatever?? um... ok... I can tell you haven't browsed the different sections for the Moto X here or you would have seen in the "Moto X Original Android Development" section that its called "PwnMyMoto"
Brokenwall gave you a way to root your sprint device, no matter what stock rom you're running... OTA updates or not. Granted unlocking your bootloader voids your warranty... and he didn't give you a 100% newbie step by step guide which it now seems you were really looking for.
Also in the Moto X Original Android Development is a thread titiled... "[Root] RockMyMoto (Yes, even the first OTA)" which is pretty obvious as to what it is for. If you took a few minutes to read it, you'd know it is what you want if you don't want to unlock your bootloader. Its not a very long thead (141 posts currently) so it wont take long to read. The original post contains everything you need, except how to make sure you have Telnet as part of your Windows install (there are posts in that thread later that say what to do to enable/install Telnet as a Windows Feature inside Add/Remove Programs).
Sorry, if I come across as harsh. I know you just want to root without screwing up your phone, and I get that. But I'm afraid if you haven't been able to look around and find this stuff, you'll likely not be able to properly follow and understand the instructions and will therefore stand a good chance of messing up your phone!!!
OK. I am sorry about the post. I know I'm at the mercy of the forum here.
I was up till 2 am getting this phone unlocked, but when I installed wireless tether it said I was not rooted.
Had to install sdk, get a long unlock code, etc.
Evidently I have yet to attain root access, but its not as though I"m not trying.
I have done rooted/jailbroken a couple times before with my htc evo/iphone, and am fairly computer literate, but I just can't hash this out.
I read this thread, but could not quite make out the steps. http://forum.xda-developers.com/showthread.php?t=2509590., The video has no sound, which makes it a little more difficult.
I have also read about an OTA on 10/7 or so that patched some of the root methods, so, at the risk of getting put in my place, I'm humbly coming to ask for assistance in helping get my phone rooted.
Again, I'm sorry for being stuck here and having to ask the question. I would greatly appreciate the assistance of someone who can speak to my specific situation.
Thank you and regards to those who can help.
Bull
bullpen7979 said:
OK. I am sorry about the post. I know I'm at the mercy of the forum here.
I was up till 2 am getting this phone unlocked, but when I installed wireless tether it said I was not rooted.
Had to install sdk, get a long unlock code, etc.
Evidently I have yet to attain root access, but its not as though I"m not trying.
I have done rooted/jailbroken a couple times before with my htc evo/iphone, and am fairly computer literate, but I just can't hash this out.
I read this thread, but could not quite make out the steps. http://forum.xda-developers.com/showthread.php?t=2509590., The video has no sound, which makes it a little more difficult.
Click to expand...
Click to collapse
The steps taken in the video are exactly explained in the post.
There are a few assumptions.. 1. Your PC has telnet on it, or you know how to install it. (there is a link further in that thread which Windows users can follow. 2. You have ADB Driver and Platform tools from the AndroidSDK installed correctly on your PC, and Moto drivers installed. Again, there are threads on this already, so you'll have to find/follow them.
You could also try to follow this post -> http://forum.xda-developers.com/showthread.php?p=47067076 however, it uses puttytel.exe instead of Telnet so it will look a little different. It too assumes you've properly installed ADB Driver and Platform Toos from the Android SDK along with the Moto drivers.
Another option is the "Tool Kit" -> http://forum.xda-developers.com/showthread.php?t=2477132 which is an "all in one" type tool that should set things up and help you too. I've not used it, but it appears to be a complete package including ADB and the drivers. Only thing would be if you want to use "Flash back to stock" you need to download the ROM file separately.
bullpen7979 said:
I have also read about an OTA on 10/7 or so that patched some of the root methods, so, at the risk of getting put in my place, I'm humbly coming to ask for assistance in helping get my phone rooted.
Click to expand...
Click to collapse
Right now, there is the rom the phone shipped with. If you have that, you use PwnMyMoto process to root it. The "camera update" that was pushed over the air. If you have that, you use RockMyMoto. And as of yesterday, if you have Verizon X, there is KitKat which can not be rooted (unless your carrier allows you to unlock your phone's boot loader)
I tried the puttytel thread, but I kept getting a timeout like this guy did:
"After running cydia impactor I see a popup for a second that says payload and then it disappears. I then try to run puttytel but it just keeps failing with "network error: connection timed out"." That was the error I kept getting.
The other problem I am currently having is not being able to push files to my device because it doesnt show up as a drive letter. I have usb debugging enabled.
I would about paypal someone for some help at this point. Bummed. I just want my device rooted so I can send my daughter the one I promised here.
I tried the puttytel thread, but I kept getting a timeout like this guy did:
"After running cydia impactor I see a popup for a second that says payload and then it disappears. I then try to run puttytel but it just keeps failing with "network error: connection timed out"." That was the error I kept getting.
The other problem I am currently having is not being able to push files to my device because it doesnt show up as a drive letter. I have usb debugging enabled.
I would about paypal someone for some help at this point. I'd even accept remote assistance via logmein. Pretty bummed. I just want my device rooted so I can send my daughter the one I promised her.
I have no idea why this process has been so difficult this time around. I have rooted, downloaded & installed custom roms, etc.
http://forum.xda-developers.com/showthread.php?t=2536200
Please help. I am out of ideas.
jayboyyyy said:
http://forum.xda-developers.com/showthread.php?t=2536200
Click to expand...
Click to collapse
Isn't this just for the verizon model?
Guys/Gals/Developers.... I'm really stuck, and would greatly appreciate some help.
I have read thru the threads.
I can't get my phone to be recognized as a drive. Only a camera. Yes, I installed usb mass storage from play store. No luck.
I can't push files to the root of the device.
I have to believe it can be done, I'm just not getting it for some reason.
I'm really sorry, as I have said in multiple posts. Like I said, I would paypal you a reasonable sum if one of the more experienced people out there want to remote in via logmein and help. I know that sounds lame. I'm normally a guy who likes to research it all himself and do this.
I'm normally the guy who helps other people with this stuff, but I just can't hash this out. I've spent the last three days of my free time reading, researching, trying to get the thing to connect as a drive so I can push files to it and run them via adb.. Even went so far as considering buying a wireless adapter to put the files there wirelessly. I'd try now but I'm exhausted. If you can help, please PM me and we can work out something if you are willing. Thanks to those who have suggested methods. I do appreciate your help. I have tried them all except the last kit kat method which I thought was just for Verizon. I'm with sprint. As tired as I am, I'm afraid to brick the thing. I'm very close to asking for a method to restore the phone and take it back. I really wanted wireless tether. I need it for work and to run the ipad on occasion. Sorry this was a long post/thread.
Sorry I'm not as quick as the rest of you. Just want a rooted phone and can't seem to get it done this time on my own.
Any suggestions?
bullpen7979 said:
Isn't this just for the verizon model?
Click to expand...
Click to collapse
No. That will work for any Moto X Developer Edition or Carrier edition with an unlocked boot loader. So T-Mobile, Sprint, etc.. If you can unlock your boot loader via -> https://motorola-global-portal.cust...e/bootloader/unlock-your-device-a/action/auth then you can root via this process.
bullpen7979 said:
Guys/Gals/Developers.... I'm really stuck, and would greatly appreciate some help.
I have read thru the threads.
I can't get my phone to be recognized as a drive. Only a camera. Yes, I installed usb mass storage from play store. No luck.
I can't push files to the root of the device.
Click to expand...
Click to collapse
To get your phone to show up in windows as Drive Letter, needs USB Mass Storage mode. Ok, You've installed an app for that, fine... but 1. I'm not aware of that app working, and more importantly, 2. I am not aware of any root method in these forums that requires your phone to show as a "drive letter" to work. So I couldn't even begin to suggest what you are doing wrong.
What instructions are you actually trying to follow? Why not post questions on it in that particular thread, including exact details of what you've done, what you see on your phone, any/all errors or messages, etc.???
And if what you really want to do is tether with sprint, I hope you have checked out threads with suggestions on hacks/ways that work to tether on Sprint Moto X before you worry about rooting.
For example, if you want to remain non-rooted, FoxFi could possibly be an option. As I am a Verizon user and haven't used it, I can't say how well it works for Spint, and I can't say how well it works for Verizon, just that Verizon KK users say it doesn't work, but it did with the JB/4.2.2 roms..
KidJoe;
Thanks for your patience. I'm sorry about all of this. I have tried to be as clear as I can be, but I will redouble my efforts. Let me read clearly that last link and I will post back. I do want root access for all the other cool things it enables too, so I'm determined to get it right. I just want to be careful not to miss something and turn a decent phone into a paperweight.
That link you referenced is exactly what I used to unlock. When I reboot the phone, I get a white screen with a red exclamation point that says bootloader unlocked.
Fox Fi is a no go
Update. Just tried Foxfi. Does not work with current status of unlock but not rooted. I need root, but how does one copy files to the device via usb? I remember there being a setting.
I opened a new thread on this subject. http://forum.xda-developers.com/showthread.php?p=47740046#post47740046
Hope that's not against the rules. I really thing the failure is related to my inability (or ignorance of how to ) push files to the device.
Good gravy. This has eaten up WAY too much time.
Apparently its a mixed bag over at sprint. Some can some can't.
http://www.sprintusers.com/forum/showthread.php?t=234246
I have a (previously) rooted D950, and I can't get the OTA At&t update to install. I've completely removed root, and double checked through root checker that it's gone, and the update errors out every time with a message about having been rooted.
I read another thread where some people report being able to retain root after receiving the update THEN downgrading and rooting 4.2.2., then installing the OTA again, but it seems that I jumped the gun and rooted first, which is now causing the install to error out.
Has anyone else experienced this? Found a workaround? Ideas? Totally frustrating.
Sent from my LG-D950 using xda premium
Here is the link to a detailed guide . Dev hyelton's page includes links to AT&T ROMs.
If you need help with LG Flash Tool:
- Connect your phone with usb to laptop/computer and open device manager
- seek for Ports: COM & LPT, right click onto Android LTE usb port connection, click "properties", click "Advanced", then change port number to number 41, click "OK"
- DOWNLOAD LG Flash Tool and install .exe
- DOWNLOAD MegaLock.zip (3kb), unzipped (7kb)
- Exchange MegaLock.dll in your system folder "LG" with the unzipped MegaLock.dll file that you have downloaded
- Open LG Flash Tool, input .dll file of downloaded stock rom.zip folder and input .tot file of this folder
- Click onto USB instead of LAN, then click "OK"
- Left arrow at the window top should be enlightened now
- Click onto this arrow
- Wait for all popup windows telling milky way download and connections to fail
- Wait then for the check of CRC and .dll files
- One or all ports should be opened, "READY" enlightened
- Disconnect your phone from computer
- Connect again and watch the immediate start of the flashing process
- After completion you must install most of the app updates, update your LG and/or AT&T profile before installing kitkat update.zip
If you'll stick in updating stock rom to kitkat, watch my video on YouTube (it's about LS995 Sprint, but AT&T LG Flex will proof the same installation process):
Visit my blog at http://www.myreviewsofreviews.for the detailed description how to avoid bootloop during the installation of LG Kitkat update.zip via ADB sideload
Thanks, but this is not a fix. Unfortunately, that guide is of no use since his links are still down. Further, I was hoping for feedback from others who have experienced this issue, and found a resolution. I have read that this is also happening on devices that have not been rooted.
I am not looking to flash a rom through FlashTool. I'm looking to fix the OTA error. All I want to do is install the OTA update.
lorawithano said:
Thanks, but this is not a fix. Unfortunately, that guide is of no use since his links are still down. Further, I was hoping for feedback from others who have experienced this issue, and found a resolution. I have read that this is also happening on devices that have not been rooted.
I am not looking to flash a rom through FlashTool. I'm looking to fix the OTA error. All I want to do is install the OTA update.
Click to expand...
Click to collapse
Not sure what you were hoping for but the guide is correct process for your problem. You need to flash back to 4.2, don't touch anything in the way of modifying system files or deleting bloatware, sign into your main Google account, update all your apps...then root the phone and when it reboots look for the ota. I would give it a couple min to setup after flashing back to 4.2 so that it successfully finds the update rather than telling you you're on the most current software. I had your exact problem too, I was one of the first AT&T users on here to take the update I tried everything to
A: retain root with supersu features and some root cloaker programs etcetera
B: factory reset, call AT&T, to get them to push the update again because I just could not get it to successfully flash without detecting suspicion of root.
Flashing back to 4.2 to retain root worked for me over 4 times now on 3 different flex phones (I had some hardware and then software issues on my replacement model)
Sent from my LG-D950 using XDA Premium 4 mobile app
brittoking said:
Not sure what you were hoping for but the guide is correct process for your problem. You need to flash back to 4.2, don't touch anything in the way of modifying system files or deleting bloatware, sign into your main Google account, update all your apps...then root the phone and when it reboots look for the ota. I would give it a couple min to setup after flashing back to 4.2 so that it successfully finds the update rather than telling you you're on the most current software. I had your exact problem too, I was one of the first AT&T users on here to take the update I tried everything to
A: retain root with supersu features and some root cloaker programs etcetera
B: factory reset, call AT&T, to get them to push the update again because I just could not get it to successfully flash without detecting suspicion of root.
Flashing back to 4.2 to retain root worked for me over 4 times now on 3 different flex phones (I had some hardware and then software issues on my replacement model)
Sent from my LG-D950 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You say flash back to 4.2, but I am already on 4.2. Never left 4.2. That's the issue. The device is defective. They're sending me a new one.
lorawithano said:
You say flash back to 4.2, but I am already on 4.2. Never left 4.2. That's the issue. The device is defective. They're sending me a new one.
Click to expand...
Click to collapse
You didn't understand my post at all it seems, I gave you the instructions to flash back to STOCK which would have fixed your problem. I did accidentally word my post incorrectly saying "flash BACK to 4.2" obviously I knew you were on 4.2, so clearly I meant use the aforementioned guide to flash back to stock then take the update. Looks like you went another route, congrats
Sent from my LG-D950 using XDA Premium 4 mobile app
Huh? Wut
Not sure where things went wrong here.....
Me thinks some thread cleaning is in order...
Stand-by....
Cleaning finished.
Come on folks, let's relax and take a breath. Sometimes things just don't work and there's little to be done about it. If common known procedures don't work, then hopefully something else will, and just move along to something else.
Or in this case, the device is being returned which of course solves all.
No need for anybody to get all bent out of shape, what started out as being helpful, just took a bad turn somewhere for unknown reasons.
Relax, be cool....
MD
KitKat update on ATT G FLEX running on Tmobile.
This might be a stupid question . I have my ATT G FLEX D950 running on Tmobile. It is on Jellybean . I am unable to pull the Kitkat update and it says "Phone is not registered on network". I am assuming I need to get my phone on ATT network to pull the update. Am I right? is there any other way out ?
santy83 said:
This might be a stupid question . I have my ATT G FLEX D950 running on Tmobile. It is on Jellybean . I am unable to pull the Kitkat update and it says "Phone is not registered on network". I am assuming I need to get my phone on ATT network to pull the update. Am I right? is there any other way out ?
Click to expand...
Click to collapse
Kinda, yes.
I had the same problem. My phone was never activated on the ATT network so it would not recognize it. You have 2 options:
Get a prepaid sim from ATT, use it once and than put your Tmobile sim back in there or ask a friend that has ATT to use the sim for a few minutes. A text or a phone call is all you need.
Worked great for me.
First of all, I have been using custom kernels and later rooting since Pocket PC 2002/Merlin, and I now have bought my first Sony (after just about every other brand of Android phone, no particular reason why I never had a Sony since the SE T68) because it's the only phone I can use with salt water spray on the screen and wet fingers. I do a lot of lobster, crayfish and crab fishing with traps and use an app called Fishing Poins to keep track of my pots and what I get where. Coming from Samsung (S5 was the latest I had) the rooting of a Sony seems rather cumbersome, but I have a few apps that need root access. LIke Air Audio to play music through an Airplay system. DLNA is useless to me, I want to stream the audio that I'm using on the phone directly to the whole house systen.
So can somebody please tell me what I do to get root access on Nougat (which my phone upgraded to before I saw that's what was happening, and no, I'm not big on reading long explanation screens, if it's a new phone and an official upgrade I am used to just doing it before I root on Samsung phones, since I have to unroot to install them later) and nothing else? For now I don't want to use any custom kernels or recovery, if I can avoid it. Just stock, rooted, like I could on my S5 (and Note 2, S4 Active and so on), please!
I did attempt the KingRoot app, but it didn't work. Also I have read a bit about that app that doesn't seem to good (Chinese spy fator app), so I did a full reset after the failed attempt. But if there's something similar that would be the perfect way of doing this. Of course I'm no stranger to ADB, so hooking it up to my pc is not a problem either.
1. Downgrade to any version of stock Marshmallow firmware with Xperifirm and Flashtool. Wipe everything and Exclude nothing (but *.ta - if any). Do not use FSC script! << FSC is now mandatory!
2. Backup your device's TA partition with Universal TA Backup tool.
3. Flash Nougat firmware (again with Xperifirm and Flashtool). Wipe everything and Exclude nothing (but *.ta - if any).
4. Unlock your device's bootloader
5. Follow this instructions to create/flash a custom kernel with root, and also DK.ftf (to fully reactivate sony's drm keys, which is wiped when bootloader is unlocked).
Anyway, try it at your own risk!
Thanks! So that's the method, which of course means deleting everything I've set up on the phone. Is there a chance there may be an easier, less destructive way during the next month or so? I can do without root access for that long.
oh, btw, by "custom kernel" do you mean that it will not be the original setup for the phone? I've been betatesting kernels on many devices, but nowadays I only want a phone that works without any hitches, and I want access to the official updates. That was easy on the Samsung phones, but maybe Sony is more different than I thought?
Oh, btw, maybe it is explained in the long post you directed me to, but I recently had an eye operation, and I would appreciate a shorter answer, before I get to the "how to", which takes me a while to read right now...
NEVER MIND THIS MESSAGE! Now I understand what Xperfirm is...
Also where would be a safe place to download ROMs from? Both the downgrade ROM and the Nougat ROM? I now really wish I hadn't let the thing upgrade before I took the TB backup (I'm still a bit unsure as to why I need that, I don't use any media with any form for DRM, but I guess better safe than sorry).
Mastiff said:
NEVER MIND THIS MESSAGE! Now I understand what Xperfirm is...
Also where would be a safe place to download ROMs from? Both the downgrade ROM and the Nougat ROM? I now really wish I hadn't let the thing upgrade before I took the TB backup (I'm still a bit unsure as to why I need that, I don't use any media with any form for DRM, but I guess better safe than sorry).
Click to expand...
Click to collapse
As far as I know there's no danger to download through Xperifirm, you need TA for guarantee reasons (if your phone need repair, not everywhere but for safety)
THanks, yeah. I have managed to read a bit and found out that Xperifirm downloads from the official Sony servers. Pain in the ass downloading, it breaks the download every couple of minutes. But that's probably Sony's servers, not the program. As for warranty, that's no problem in Norway since we have very strong consumer rights here. If an error can not be prooven to stem from rooting or other software stuff, it will be fixed. If I remember correctly Apple tried really hard to battle with the consumer rights officials about jailbreaking, but they had a very bloody defeat.
Seems like I have a problem. The Telenor Nougat ROM doesn't have a loader, according to Flashtool. Neither do the two other ROMs I have downloaded so far, but I'm trying again with a third, which doesn't have the "customised" moniker. So I hope that has a loader. But how do I upgrade again to Nougat, with the Norwegian version, when the Telenor ROM doesn't have a loader?
Mastiff said:
Seems like I have a problem. The Telenor Nougat ROM doesn't have a loader, according to Flashtool. Neither do the two other ROMs I have downloaded so far, but I'm trying again with a third, which doesn't have the "customised" moniker. So I hope that has a loader. But how do I upgrade again to Nougat, with the Norwegian version, when the Telenor ROM doesn't have a loader?
Click to expand...
Click to collapse
if your phone is locked(Bootloader),fix it using Xperia Companion..that way it upgrades automatically to Nougat.
if not,lock it using Flashtool first.
Well, the message was kind of badly worded, because I need to downgrade first of all. So I'm at the moment trying to get it to MM without messing up the TA partition. So anyway, this thread has been followed by others, I think this can be considered solved since there is only one way to get root on these phones.
What would be the best approach to rooting if you unlock your bootloader before learning about TA backup? I have since downgraded, done TA backup, upgraded, flashed TWRP, flashed SU/Magisk/phhSu, and saw two green checks in Magisk. Tried to continue to get the three checks by installing Sony framework v1 through Magisk and then Andros plus kernel, but got stuck on Sony screen on boot up. So I repeated steps and stopped after I got two checks, however after long use and simple phone restart, I lost root. Please HELP!
I have just moved to XZ1c from Z3c. Rooting the Z3c was so easy, flashtool, bit of old firmware and an exploit and you were away.
Seems that it's much more tricky now.
There is an 'OEM unlocking' option in the developer options, not sure what that does.
Does anyone know if iRoot works and if it's possible to disinfect your phone and replace it with SuperSU afterwards?
I can see lots a couple of generic Sony 'how to's' in the guides thread, but no feedback from anyone who's done it with a real life XZ1c.
Didgesteve said:
There is an 'OEM unlocking' option in the developer options, not sure what that does.
Click to expand...
Click to collapse
That's to allow you to unlock the bootloader, but with no MM ROM available we're unable to back up DRM keys, but with no TWRP.img as yet either flashing a Superuser.zip might be hard. I'm in no rush to root so haven't tried hotbooting a TWRP.img from another ROM.
Iroot / vroot whatever you call it
not sure what happened with the original software but in the present this is nothing but belated adware and spyware it is pure spy when actually not even as well a virus it will not root but gives a false message that it has rooted and install a bunch of crap well on your PC as well as Android device on Android device it will automatically start downloading a bunch of jar files and install some virus apps Android OS if it is sensitive will complain that this seems to be a Malware none of the virus programs including Norton and other hochos will detect this it has to be manually removed file by file folder by folder do not under any circumstances install this so called rooting software
Yes, iRoot is working 100% fine. Good luck.
(I lied, its a malicious app, stay away)
Dean F said:
Yes, iRoot is working 100% fine. Good luck.
Click to expand...
Click to collapse
This is definitely not true!
There is actual no way to root a xperia XZ1 Compact without unlocking the bootloader.
At the XZ1 section you can find manuals how to get root.
But read them with care, because you loose your DRM Keys and you never get them back!
Here some stuff to read:
https://forum.xda-developers.com/xperia-xz1/how-to/how-unlock-sony-xperia-xz1-bootloader-t3758742
https://forum.xda-developers.com/xperia-xz1/how-to/guide-how-to-persistant-root-xperia-xz1-t3718375
https://forum.xda-developers.com/xp...nel-sony-xz1-compact-16-january-2018-t3736068
Dean F said:
Yes, iRoot is working 100% fine. Good luck.
Click to expand...
Click to collapse
iRoot is 100% spyware and IMEI cloning
I rooted my phone with Xperiafix, worked perfectly, full stock functions restored. Perect pictures.
I lied.
Didgesteve said:
iRoot is 100% spyware and IMEI cloning
I rooted my phone with Xperiafix, worked perfectly, full stock functions restored. Perect pictures.
Click to expand...
Click to collapse
thanks for the info (and sorry for the earlier typos.... I talk to my phone but sometimes it becomes deaf ... iPhones I have to say Have a sharper pair of ears than do the best Androids )
just wondered if that Xperia fix website is free or paid service I don't mind either way but it just helps to know .. the biggest problem with locked bootloader is that you cannot Mount system as read write and so on reboot even if you rooted you will lose root. this is where I am stuck right now
sieger007 said:
thanks for the info (and sorry for the earlier typos.... I talk to my phone but sometimes it becomes deaf ... iPhones I have to say Have a sharper pair of ears than do the best Androids )
just wondered if that Xperia fix website is free or paid service I don't mind either way but it just helps to know .. the biggest problem with locked bootloader is that you cannot Mount system as read write and so on reboot even if you rooted you will lose root. this is where I am stuck right now
Click to expand...
Click to collapse
Xperiafix is $20. But it comes with support from sToRm// who wrote it. So if you have any issues, you go back to the website and raise a ticket and he'll help you.
Once you have the correct ADB drivers installed (more difficult than it sounds, Windows10 makes this very tricky), it's pretty much automatic. Start the software, follow the instructions.
You end up with the latest TWRP installed and Magisk systemless root. This works on any version of firmware you have installed.
If you want some reading on how to set the drivers up, have a look at the original thread, although this is in the XZ premium forum, the Xperiafix also works on compacts.
I had been looking for a new phone for awhile. Settled on a Note 9 because I wanted to try using the S Pen for work and dislike the Note 10 design. However, they are still sold at full price where I live, so I bought one secondhand. Everything seems generally fine with it, minus some freezing or weird reactions when it charges for awhile or restarts. But I have been skeptical of throwing passwords (personal and for work) on it to this point. Thats because I read an article about potential root level or firmware level spyware that remains after a reset.
I did a reset AND even took it to an official service center to flash new firmware (but they said they cannot do it there, but they did some kind of more advanced reset?). I checked my Knox counter in the Download menu and it reads 0x00000, maybe more or less zeros. Samsung pass, pay, health, and secure folder all seem to work (I can register for them, use the bio sensor). That all sounds like it has not been tampered with in any way, correct?
Thanks for the help.
IqD said:
I had been looking for a new phone for awhile. Settled on a Note 9 because I wanted to try using the S Pen for work and dislike the Note 10 design. However, they are still sold at full price where I live, so I bought one secondhand. Everything seems generally fine with it, minus some freezing or weird reactions when it charges for awhile or restarts. But I have been skeptical of throwing passwords (personal and for work) on it to this point. Thats because I read an article about potential root level or firmware level spyware that remains after a reset.
I did a reset AND even took it to an official service center to flash new firmware (but they said they cannot do it there, but they did some kind of more advanced reset?). I checked my Knox counter in the Download menu and it reads 0x00000, maybe more or less zeros. Samsung pass, pay, health, and secure folder all seem to work (I can register for them, use the bio sensor). That all sounds like it has not been tampered with in any way, correct?
Thanks for the help.
Click to expand...
Click to collapse
What's the model number?
Sm-n960n. Korean exynos model, 512gb.
IqD said:
Sm-n960n. Korean exynos model, 512gb.
Click to expand...
Click to collapse
If you are worried about remaining spyware of files, download the latest rom from sammobile and then flash with odin.
Just simply search how to use sammobile or how to use odin if you need help. Hundreds of years have posted how good and answered those questions already
I used to flip phones up until a couple years ago. I've bought and sold hundreds, maybe thousands of used phones, most of which had my accounts on them at one point and time. I think as long as the phone is running official firmware, isn't bootloader unlocked/rooted, and you've reset it, it should be fine. Of course you run the risk that someone has hacked it, installed spyware at the system level, and somehow overwritten the status to show as official such that the spyware persists even after a reset, but that's highly unlikely.
Sent from my SM-N960U using Tapatalk
Bober_is_a_troll said:
If you are worried about remaining spyware of files, download the latest rom from sammobile and then flash with odin.
Just simply search how to use sammobile or how to use odin if you need help. Hundreds of years have posted how good and answered those questions already
Click to expand...
Click to collapse
Thanks for the idea. I considered this but would like to avoid just because sammobile is unofficial, so it would still leave me slightly apprehensive even if everyone is using it.
Everything I read seems to suggest that the phone was never rooted if all of the Samsung apps work and the Download KNOX counter is 0x0. Just wanting to confirm by someone more knowledgeable about this.
joshw0000 said:
I used to flip phones up until a couple years ago. I've bought and sold hundreds, maybe thousands of used phones, most of which had my accounts on them at one point and time. I think as long as the phone is running official firmware, isn't bootloader unlocked/rooted, and you've reset it, it should be fine. Of course you run the risk that someone has hacked it, installed spyware at the system level, and somehow overwritten the status to show as official such that the spyware persists even after a reset, but that's highly unlikely.
Sent from my SM-N960U using Tapatalk
Click to expand...
Click to collapse
Thanks. I don't think it has ever been unlocked or rooted, but is there a guaranteed way to know?
IqD said:
Thanks for the idea. I considered this but would like to avoid just because sammobile is unofficial, so it would still leave me slightly apprehensive even if everyone is using it.
Everything I read seems to suggest that the phone was never rooted if all of the Samsung apps work and the Download KNOX counter is 0x0. Just wanting to confirm by someone more knowledgeable about this.
Thanks. I don't think it has ever been unlocked or rooted, but is there a guaranteed way to know?
Click to expand...
Click to collapse
Go to settings > about phone > status and it should say "official". That would tell you if the phones operating system has been modified (rooted). As far as checking for bootloader unlock, I'm not sure on Samsung's but on a Google Pixel once the bootloader is unlocked it'll show an unlocked lock on the bootscreen every time that you reboot the phone. North American snapdragon variants of Note 9's do not have an unlockable bootloader so if your phone is a carrier branded phone, the bootloader can't be unlocked. You can Google your model # to figure out which one you have.
You can also check that all functions work properly. Typically apps like Samsung Pay won't work if the phone is rooted. There are ways around that where you can trick the phone into thinking it's not rooted to get those apps to work so, again, that's not a full proof way to check. For example, I'm using an AT&T variant that's been sim unlocked and flashed with Verizon firmware and it works 100% like a Verizon phone.
I'd say, reboot the phone. If you don't see an unlocked icon it's probably not unlocked. Go into settings and take note of your model #
Then go online and research about Odin and flashing official firmware via your computer. Download the latest official firmware for your phone, flash it using Odin, and then you'll know that there's no spyware on your phone. That would essentially be the equivalent of wiping a computer and reinstalling Windows.
Sent from my SM-N960U using Tapatalk
joshw0000 said:
Go to settings > about phone > status and it should say "official". That would tell you if the phones operating system has been modified (rooted). As far as checking for bootloader unlock, I'm not sure on Samsung's but on a Google Pixel once the bootloader is unlocked it'll show an unlocked lock on the bootscreen every time that you reboot the phone. North American snapdragon variants of Note 9's do not have an unlockable bootloader so if your phone is a carrier branded phone, the bootloader can't be unlocked. You can Google your model # to figure out which one you have.
You can also check that all functions work properly. Typically apps like Samsung Pay won't work if the phone is rooted. There are ways around that where you can trick the phone into thinking it's not rooted to get those apps to work so, again, that's not a full proof way to check. For example, I'm using an AT&T variant that's been sim unlocked and flashed with Verizon firmware and it works 100% like a Verizon phone.
I'd say, reboot the phone. If you don't see an unlocked icon it's probably not unlocked. Go into settings and take note of your model #
Then go online and research about Odin and flashing official firmware via your computer. Download the latest official firmware for your phone, flash it using Odin, and then you'll know that there's no spyware on your phone. That would essentially be the equivalent of wiping a computer and reinstalling Windows.
Click to expand...
Click to collapse
yeah.. i whouldint fall for that system/status official crap. as you can see in the screenshot i posted from my rooted n960n.
the only real way is to check if knox is tripped is in DL mode( turn phone off. hold bixby and vol down button while inserting a usb cable hooked to a computer.).
also flashing a stock firmware on an FRP locked phone wont do **** if someone has had their accounts logged in/registered on it and have not reset it correctly.
surprised you dont know this.
IqD said:
Sm-n960n. Korean exynos model, 512gb.
Click to expand...
Click to collapse
FYI - This phone does have an unlockable bootloader.
I'd recommend using Bobby's advice and flash the latest firmware with Odin. If the phone is not already on the latest update, you could flash one firmware less than current and then let the phone download and install an OTA to the current version. You'll know that its official if the phone successfully downloads and installs the OTA.
Sent from my SM-N960U using Tapatalk
---------- Post added at 07:35 PM ---------- Previous post was at 07:31 PM ----------
bober10113 said:
yeah.. i whouldint fall for that system/status official crap. as you can see in the screenshot i posted from my rooted n960n.
the only real way is to check if knox is tripped is in DL mode( turn phone off. hold bixby and vol down button while inserting a usb cable hooked to a computer.).
also flashing a stock firmware on an FRP locked phone wont do **** if someone has had their accounts logged in/registered on it and have not reset it correctly.
surprised you dont know this.
Click to expand...
Click to collapse
Not sure why you're trying to call me out when I clearly said there are ways for it show official if it's rooted. Also, no one said anything about FRP. If the phone was FRP locked they wouldn't be able to use it at all... Unless you know how to remove an FRP lock, which I do. At that point the phone would work/be a normal phone.
Sent from my SM-N960U using Tapatalk
joshw0000 said:
FYI - This phone does have an unlockable bootloader.
I'd recommend using Bobby's advice and flash the latest firmware with Odin. If the phone is not already on the latest update, you could flash one firmware less than current and then let the phone download and install an OTA to the current version. You'll know that its official if the phone successfully downloads and installs the OTA.
Sent from my SM-N960U using Tapatalk
---------- Post added at 07:35 PM ---------- Previous post was at 07:31 PM ----------
Not sure why you're trying to call me out when I clearly said there are ways for it show official if it's rooted. Also, no one said anything about FRP. If the phone was FRP locked they wouldn't be able to use it at all... Unless you know how to remove an FRP lock, which I do. At that point the phone would work/be a normal phone.
Click to expand...
Click to collapse
point taken on the FRP lock but the real point I was making is that the system status is bogus:
joshw0000 said:
Go to settings > about phone > status and it should say "official". That would tell you if the phones operating system has been modified (rooted).
Click to expand...
Click to collapse
bober10113 said:
point taken on the FRP lock but the real point I was making is that the system status is bogus:
Click to expand...
Click to collapse
You obviously didn't read the entire comment:
"There are ways around that where you can trick the phone into thinking it's not rooted to get those apps to work so, again, that's not a full proof way to check."
Or this comment:
" I used to flip phones up until a couple years ago. I've bought and sold hundreds, maybe thousands of used phones, most of which had my accounts on them at one point and time. I think as long as the phone is running official firmware, isn't bootloader unlocked/rooted, and you've reset it, it should be fine. Of course you run the risk that someone has hacked it, installed spyware at the system level, and somehow overwritten the status to show as official such that the spyware persists even after a reset, but that's highly unlikely."
There are a lot of ways to check. I pointed out some of the simpler ways. None of which are truly bullet proof. Hell, back in the day we could reset knox counters so if someone is going to the extreme to install some spyware and they're smart enough to install anything that would persist a factory reset, even checking knox isn't a full proof method.
And your screenshot really doesn't tell me anything. It's possible to have an unlocked bootloader AND official firmware at the same time. The operating system and bootloader are two different things. It's only when you modify the system that you have to hack the status to make it say official.
Sent from my SM-N960U using Tapatalk
joshw0000 said:
You obviously didn't read the entire comment:
"There are ways around that where you can trick the phone into thinking it's not rooted to get those apps to work so, again, that's not a full proof way to check."
There are a lot of ways to check. I pointed out some of the simpler ways. None of which are truly bullet proof. Hell, back in the day we could reset knox counters so if someone is going to the extreme to install some spyware and they're smart enough to install anything that would persist a factory reset, even checking knox isn't a full proof method.
Click to expand...
Click to collapse
fine but i mean, why ask a user to validate the state of their device via the worst possible method of them all?
he even already posted in OP that he went to DL mode to check the knox fuse status so would supersede by far the need to check via software/status.
edit
and the photo of my device status was just a way to show how i know device actual status and bootlaoder state aren't linked. especialy when rooted devices can spoof software status but none cane spoof fuse state in DL mode. so not sure why you are trying to convince me of something i just proved. u can say u agree next time.
bober10113 said:
fine but i mean, why ask a user to validate the state of their device via the worst possible method of them all?
he even already posted in OP that he went to DL mode to check the knox fuse status so would supersede by far the need to check via software/status.
Click to expand...
Click to collapse
No actually he didn't. He never said he went to DL mode, he just said the knox counter says 0x0. That can be checked via apps from the phone. If the phone was rooted, it could be manipulated to show 0x0 when it's really not.
You're focusing on one sentence dude. Get your panties out of a wod and read the whole comment.
Sent from my SM-N960U using Tapatalk
joshw0000 said:
No actually he didn't. He never said he went to DL mode, he just said the knox counter says 0x0. That can be checked via apps from the phone. If the phone was rooted, it could be manipulated to show 0x0 when it's really not.
You're focusing on one sentence dude. Get your panties out of a wod and read the whole comment.
Click to expand...
Click to collapse
lol. but i did read he went to download menu which i think we can interpret it as download mode. but hey i might wrong. can you show me anywhere in the OS where download menu is?
IqD said:
I checked my Knox counter in the Download menu and it reads 0x00000, maybe more or less zeros.
Click to expand...
Click to collapse
bober10113 said:
lol. but i did read he went to download menu which i think we can interpret it as download mode. but hey i might wrong. can you show me anywhere in the OS where download menu is?
Click to expand...
Click to collapse
What a troll.
Sent from my SM-N960U using Tapatalk
joshw0000 said:
What a troll.
Click to expand...
Click to collapse
that's the spirit!
bober10113 said:
lol. but i did read he went to download menu which i think we can interpret it as download mode. but hey i might wrong. can you show me anywhere in the OS where download menu is?
Click to expand...
Click to collapse
joshw0000 said:
No actually he didn't. He never said he went to DL mode, he just said the knox counter says 0x0. That can be checked via apps from the phone. If the phone was rooted, it could be manipulated to show 0x0 when it's really not.
You're focusing on one sentence dude. Get your panties out of a wod and read the whole comment.
Sent from my SM-N960U using Tapatalk
Click to expand...
Click to collapse
Sorry for the confusion. I was referring to the Download mode by hitting the mentioned buttons on restart. The KNOX reads 0x0000. Also, it says OEM Lock: On. Then you are both saying the phone is safe?
Also, when I first got it, it did find an update OTA and installed it.
IqD said:
Sorry for the confusion. I was referring to the Download mode by hitting the mentioned buttons on restart. The KNOX reads 0x0000. Also, it says OEM Lock: On. Then you are both saying the phone is safe?
Also, when I first got it, it did find an update OTA and installed it.
Click to expand...
Click to collapse
no confusion on my part. i read and understood you correctly the 1st time around.
at first glance your device looks ok but...
additionally, there are ways to check if the device is off a lease with a ESN check. meaning if someone sold you a device still on contract. some sell contractual phones and after a period of time they will get blacklisted since the contract is never payed off fully. so device would appear to work fine and one day they just stop getting a signal and esn/imei get blacklisted.
side note:
surprised that this was not brought up earlier in the conversation as a factor to watch out for by some "experianced in the field flipping devices" user instead of stating the obvious like device status and the unreliable means to check it. especialy since, said user stated buying and selling hundred and even thousands of phones...!? ESN state would be no. 1 in the check list if things to watch out for.
anyways back to the current case, there are ESN/IMEI check services in the web to see status of device: stolen, still on contract...etc. i cannot provide any suggestion to these services unfortunately. this is something you need to check yourself or ask around.
good luck
IqD said:
I had been looking for a new phone for awhile. Settled on a Note 9 because I wanted to try using the S Pen for work and dislike the Note 10 design. However, they are still sold at full price where I live, so I bought one secondhand. Everything seems generally fine with it, minus some freezing or weird reactions when it charges for awhile or restarts. But I have been skeptical of throwing passwords (personal and for work) on it to this point. Thats because I read an article about potential root level or firmware level spyware that remains after a reset.
I did a reset AND even took it to an official service center to flash new firmware (but they said they cannot do it there, but they did some kind of more advanced reset?). I checked my Knox counter in the Download menu and it reads 0x00000, maybe more or less zeros. Samsung pass, pay, health, and secure folder all seem to work (I can register for them, use the bio sensor). That all sounds like it has not been tampered with in any way, correct?
Thanks for the help.
Click to expand...
Click to collapse
Reading this thread I've come to the conclusion that you should sell your rootable and boot unlockable device and buy a locked down USA model.
Thank me later. Least you'll be able to sleep well now.
Sent from my SM-G975U using Tapatalk
IqD said:
Sorry for the confusion. I was referring to the Download mode by hitting the mentioned buttons on restart. The KNOX reads 0x0000. Also, it says OEM Lock: On. Then you are both saying the phone is safe?
Also, when I first got it, it did find an update OTA and installed it.
Click to expand...
Click to collapse
It's about as safe, in terms of spyware, as you'll ever get from a used phone. I would assume you checked the ESN before buying it but if not, run a check with swappa.com/esn and checkesnfree.com to make sure it's clean. Screenshot the results and save them. Depending on your carrier you can likely run a check on their website and/or call support and ask them as well. As with any unlocked phone, know that you may not get all of the features that a carrier branded phone would have (i.e. I couldn't get WiFi calling working on a Korean S10 on Verizon).
Sent from my SM-N960U using Tapatalk