Related
Hi All,
I'm lost, so hope you chaps can help.
Have just purchased a Verizon Moto X developer phone X1060 - its from the USA, I'm in Hong Kong and obviously not using a Verizone sim card - further, I'm a iMac user, so Android is new to say the least to me.
My MX is already "rooted" so want to upgrade to latest 4.4.2, obviously I have to do this via boot loader - big difficulties encountered having download all necessary files and cannot "hard" reboot as getting Andy with Red Triangle - I take it some issue with fast boot or whatever, but after 12 hours effort, absolutely stuck and getting annoyed.
So, time to hit boards and get expert advice me thinks?
I always used OTA updates, but I think that you have to unlock your bootloader, and/or, use RSD LITE like this:
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Many thanks, but
djlucask said:
I always used OTA updates, but I think that you have to unlock your bootloader, and/or, use RSD LITE like this:
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Click to expand...
Click to collapse
Thanks for your input, but as I have a developer Moto X from Verizone and am using it with a mobile provider in Hong Kong, I cannot do OTA update, hence struggling, and struggling because I'm on OSX 10.8 and an iMac, most guides being for PC - have managed to crack half the issue, but flashing ROM's is a big pain presently, particularly when using Terminal!
editor1 said:
Thanks for your input, but as I have a developer Moto X from Verizone and am using it with a mobile provider in Hong Kong, I cannot do OTA update, hence struggling, and struggling because I'm on OSX 10.8 and an iMac, most guides being for PC - have managed to crack half the issue, but flashing ROM's is a big pain presently, particularly when using Terminal!
Click to expand...
Click to collapse
Oh i forgot the iMac issue, I never saw tutorials for OSX, maybe the best choice here is to make an Windows VM, or an Linux, that way would be always easy to mod your phone.
Sorry I don't have any other possible solutions for this
Might be easier to read up on how to change the recovery to TWRP (make sure get version 2.7); sounds like you are on the stock recovery still since you get Andy w/ Red Triangle) then use TWRP to flash a rooted, updated rom from the development section. If you are already rooted (not just unlocked) then you can use an app like Recovery manager (?) to flash TWRP while booted into the regular android system.
Or, you can also flash all the update files from the Bootloader using Fastboot. I don't have a MAC, so I don't know if the Motorola Fastboot file is available for Mac though. If you can't use the Motorola fastboot, you will need to use fastboot to flash the TWRP recovery, and then flash the new ROM system image using a ROM zip file in TWRP recovery instead of Bootloader.
Just make sure you are in the Bootloader when you try and use fastboot, not in the Factory Recovery. I believe the Andy icon indicates you are in the Factory Recovery.
One other tip: when in bootloader, the "volume up" key is the "enter" key to select the option that is highlighted (not the power key like other Android devices I have used).
When you flash TWRP, DON"T reboot, instead, use the bootloader option to boot to recovery directly (without rebooting).
Once you have a custom recovery, and have root, you won't ever need to worry about working on a Mac instead of PC.
jasoraso said:
Might be easier to read up on how to change the recovery to TWRP (make sure get version 2.7); sounds like you are on the stock recovery still since you get Andy w/ Red Triangle) then use TWRP to flash a rooted, updated rom from the development section. If you are already rooted (not just unlocked) then you can use an app like Recovery manager (?) to flash TWRP while booted into the regular android system.
Or, you can also flash all the update files from the Bootloader using Fastboot. I don't have a MAC, so I don't know if the Motorola Fastboot file is available for Mac though. If you can't use the Motorola fastboot, you will need to use fastboot to flash the TWRP recovery, and then flash the new ROM system image using a ROM zip file in TWRP recovery instead of Bootloader.
Just make sure you are in the Bootloader when you try and use fastboot, not in the Factory Recovery. I believe the Andy icon indicates you are in the Factory Recovery.
One other tip: when in bootloader, the "volume up" key is the "enter" key to select the option that is highlighted (not the power key like other Android devices I have used).
When you flash TWRP, DON"T reboot, instead, use the bootloader option to boot to recovery directly (without rebooting).
Once you have a custom recovery, and have root, you won't ever need to worry about working on a Mac instead of PC.
Click to expand...
Click to collapse
Thanks for info, I've managed to setup fast boot, its the actual flashing of the ROM via Terminal that's confusing to say the least - basically, in Mac terminal necessary to change inputting details associated with rooting instructions found on PC - side of the equation, hence why I'm stuck. Would be easier to get someone with a PC laptop to lend a hand, most don't do custom jobs on Android though, so, will have to figure it out myself and then hopefully render help to others.
Republic Wireless Moto X Moto G Discount Code Link URL
$25 Republic Wireless credit at checkout with purchase of your phone using this discount link
editor1 said:
Thanks for info, I've managed to setup fast boot, its the actual flashing of the ROM via Terminal that's confusing to say the least - basically, in Mac terminal necessary to change inputting details associated with rooting instructions found on PC - side of the equation, hence why I'm stuck. Would be easier to get someone with a PC laptop to lend a hand, most don't do custom jobs on Android though, so, will have to figure it out myself and then hopefully render help to others.
Click to expand...
Click to collapse
Have you tried this?
Toolkit for Mac OS under development...
Sent from my XT1060 using Tapatalk 2
imparables said:
Have you tried this?
Toolkit for Mac OS under development...
Sent from my XT1060 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for info, I've not tried Toolkit, or heard of it - any links to assist with this?
Basically, you are going to see more Mac users adopt Android over the coming months, and many like me suffer in an all OSX environment when playing about with PC-structured advice - shame I never adopted a duel boot system on my mac, but its always been for DTP, hence always happy with Adobe in Mac.
Now upgraded to 4.4.2
editor1 said:
Thanks for info, I've not tried Toolkit, or heard of it - any links to assist with this?
Basically, you are going to see more Mac users adopt Android over the coming months, and many like me suffer in an all OSX environment when playing about with PC-structured advice - shame I never adopted a duel boot system on my mac, but its always been for DTP, hence always happy with Adobe in Mac.
Click to expand...
Click to collapse
Thanks for the input, after two days of hell, I'm now fully upgraded to KitKat 4.4.2, my Moto X1060 Dev phone is working as it should be, I've unlocked it, am able to do side-loading, have TWRP installed - a bigger pain as caused a continually boot loop, erased, re-installed all from Moto and re-cracked it.
So it works, and I did all this on a iMac and in terminal, which I don't often use!
Not bad for someone fast approaching 50 - and yes, this is a kids game I'm afraid to say.
I'll admit, I didn't fully understand the root process back when I did this. I don't even remember all the steps I took. I got a locked Verizon (black 16GB) for an upgrade back in March. I always wanted this phone but never had an upgrade available. Well I forgot they had a Dev model out and stupidly got the free one with a new contract renewal.
I am running android 4.4 KK and am currently rooted with Xposed installed. I'm pretty sure the only way I can have write protection disabled is by booting into recovery, correct? Even though I select recovery at the fastboot screen, it just boots like normal. I guess my question is, is there any reason for me to be booting into recovery every time? Is there a way to tell if I have WP disabled on /system and root after a normal boot process? I swear I've had Xposed stop working after a normal boot.
EDIT: I'm seriously considering swapping this out for a new Dev model if they go on sale. I could use the extra storage and can easily just unlock the bootloarder and have root when L comes out for the first gen X.
IEcansuckit said:
I'll admit, I didn't fully understand the root process back when I did this. I don't even remember all the steps I took. I got a locked Verizon (black 16GB) for an upgrade back in March. I always wanted this phone but never had an upgrade available. Well I forgot they had a Dev model out and stupidly got the free one with a new contract renewal.
I am running android 4.4 KK and am currently rooted with Xposed installed. I'm pretty sure the only way I can have write protection disabled is by booting into recovery, correct? Even though I select recovery at the fastboot screen, it just boots like normal. I guess my question is, is there any reason for me to be booting into recovery every time? Is there a way to tell if I have WP disabled on /system and root after a normal boot process? I swear I've had Xposed stop working after a normal boot.
EDIT: I'm seriously considering swapping this out for a new Dev model if they go on sale. I could use the extra storage and can easily just unlock the bootloarder and have root when L comes out for the first gen X.
Click to expand...
Click to collapse
You can try installing something as a system app (App Ops for Root comes to mind https://play.google.com/store/apps/details?id=droidmate.appopsinstaller&hl=en) and see if it works. If it does, than write protection is off. The app on Play store is actually an installer that will put App Ops into your /system folder. If you have Xposed working properly, it might be OK already.
I remember when I rooted my VZW Moto Maker Edition on 4.2.2 (I think) I used SlapMyMoto and MotoWPNoMo (or something weird like that). I ran both and then installed Xposed and the framework failed to install properly (the version numbers in the app were red). I tried a few times and it didn't work. I ran the WP script a second time then Xposed worked fine. I must have missed a step in the WP off procedure.
If you boot normally and Xposed doesn't work, or you can't install to /system then I'd say you don't have WP off when booting normally.
fury683 said:
You can try installing something as a system app (App Ops for Root comes to mind https://play.google.com/store/apps/details?id=droidmate.appopsinstaller&hl=en) and see if it works. If it does, than write protection is off. The app on Play store is actually an installer that will put App Ops into your /system folder. If you have Xposed working properly, it might be OK already.
I remember when I rooted my VZW Moto Maker Edition on 4.2.2 (I think) I used SlapMyMoto and MotoWPNoMo (or something weird like that). I ran both and then installed Xposed and the framework failed to install properly (the version numbers in the app were red). I tried a few times and it didn't work. I ran the WP script a second time then Xposed worked fine. I must have missed a step in the WP off procedure.
If you boot normally and Xposed doesn't work, or you can't install to /system then I'd say you don't have WP off when booting normally.
Click to expand...
Click to collapse
Ok, I installed what you suggested, went into the app and tapped the "Install AppOps Root" button. It asked for root access and then rebooted my phone. So I guess this means that by default on a normal reboot, I have WP disabled and root access? Thanks for help clearing this up! I guess the phone was just acting weird that one time when the Xposed modules wouldn't work.
One last question, is there a reason why I can't get to recovery? Whenever I reboot into Recovery, it just starts up like normal? Is that because the normal recovery has been overwritten by a custom one in the root process?
IEcansuckit said:
Ok, I installed what you suggested, went into the app and tapped the "Install AppOps Root" button. It asked for root access and then rebooted my phone. So I guess this means that by default on a normal reboot, I have WP disabled and root access? Thanks for help clearing this up! I guess the phone was just acting weird that one time when the Xposed modules wouldn't work.
One last question, is there a reason why I can't get to recovery? Whenever I reboot into Recovery, it just starts up like normal? Is that because the normal recovery has been overwritten by a custom one in the root process?
Click to expand...
Click to collapse
If your bootloader isn't unlocked I don't think you can change recovery. You may be able to reflash the stock recovery from fastboot/mfastboot for your proper version, but don't quote me on that.
Someone with more experience can chime in. How are you rebooting to recovery? With an app/button, or via fastboot?
fury683 said:
If your bootloader isn't unlocked I don't think you can change recovery. You may be able to reflash the stock recovery from fastboot/mfastboot for your proper version, but don't quote me on that.
Someone with more experience can chime in. How are you rebooting to recovery? With an app/button, or via fastboot?
Click to expand...
Click to collapse
Correct. No unlock - no custom recovery.
It also depends on which method you used to achieve wp-off. Is rather not get into the finer details because it's really not important...
Are you using VOL+ to select recovery in the bootloader?
Edit: yes, when you rooted your phone, the stock recovery was overwritten to give you Android with write protection off. Looks like normal Android, but you have write access to system.
Good evening and sorry if post a thread of which I see two similar oness
However, I could not find a solution in the other ones and have questions which go a little further and really hit my privacy.
I have two XZ3 and both could go into recovery node when I bought them and after a while could not.
I used the reset to factory seting fo wiping cache etc. quite regularly as I had/have reasons to belive that I was/am spied on.
Sice the recovery mode possibility is gone I feel totally unsafe with both phones.
I tried all possibilities I can find of this website or any other in internet, and all were without success.
As described by others, after pushing the power button, there is no led light and it boots suoer-quicklyto the blue stripe view in which we wait till the boot is complete.
Till two days ago I thought ok, the phone just needs a flash, wipe everything away once and all would be resolved.
Well, two days ago I flashed my phone the first time from lollipop to kitkat, which worked without problems and then rooted it with gifroot and then put back lollipop.
Everything ran smoothly and after the whole process I had a rooted lollipop version with a working recovery. I tried the apps which confirm if the root works abd everything was great.
Tthe morning after, however the recovery possibility was gone. The phone was still rooted for everything, but for recvery mode.
I tried several apps, which I gave superuser access with SuperSu, but even from the apps the boot goes always just the NORMAL way without recovery.
To give it another try today I flashed that xz3 again, then rooted it with Kingo root, which in Kitkat firmware worked lalso super easy, the checked with other apps whihchconfirmed that the root works, but still no recovery possibility, no matter with which app..
I really need a specialist who can explain that to me, as I am going mad to think that someone else has total control over my phones.
How realistic is that some spyware does not allow the recovery as of course it knows that it would be eliminated then.
Please give me your thuoghts or knowledge. Everything helps. And if you know a method with which I can be sure that nothing is keft on the phone, I would appreciate.
Thanks and Regards
iFran72 said:
Good evening and sorry if post a thread of which I see two similar oness
However, I could not find a solution in the other ones and have questions which go a little further and really hit my privacy.
I have two XZ3 and both could go into recovery node when I bought them and after a while could not.
I used the reset to factory seting fo wiping cache etc. quite regularly as I had/have reasons to belive that I was/am spied on.
Sice the recovery mode possibility is gone I feel totally unsafe with both phones.
I tried all possibilities I can find of this website or any other in internet, and all were without success.
As described by others, after pushing the power button, there is no led light and it boots suoer-quicklyto the blue stripe view in which we wait till the boot is complete.
Till two days ago I thought ok, the phone just needs a flash, wipe everything away once and all would be resolved.
Well, two days ago I flashed my phone the first time from lollipop to kitkat, which worked without problems and then rooted it with gifroot and then put back lollipop.
Everything ran smoothly and after the whole process I had a rooted lollipop version with a working recovery. I tried the apps which confirm if the root works abd everything was great.
Tthe morning after, however the recovery possibility was gone. The phone was still rooted for everything, but for recvery mode.
I tried several apps, which I gave superuser access with SuperSu, but even from the apps the boot goes always just the NORMAL way without recovery.
To give it another try today I flashed that xz3 again, then rooted it with Kingo root, which in Kitkat firmware worked lalso super easy, the checked with other apps whihchconfirmed that the root works, but still no recovery possibility, no matter with which app..
I really need a specialist who can explain that to me, as I am going mad to think that someone else has total control over my phones.
How realistic is that some spyware does not allow the recovery as of course it knows that it would be eliminated then.
Please give me your thuoghts or knowledge. Everything helps. And if you know a method with which I can be sure that nothing is keft on the phone, I would appreciate.
Thanks and Regards
Click to expand...
Click to collapse
Spyware cannot affect Recovery unless it is granted root permissions and is embedded on system.
Also do not use KingoRoot, a thread in the SG note 3 forums reported Spyware installed after using it, source. For now steer clear of that application until all claims have been proven false
At any rate, ( assuming you have Unlocked Bootloader ) just flash another kernel with recovery, do a full wipe including formating the system partition and restore your system via flashing a rom
9
Revontheus said:
Spyware cannot affect Recovery unless it is granted root permissions and is embedded on system.
Also do not use KingoRoot, a thread in the SG note 3 forums reported Spyware installed after using it, source. For now steer clear of that application until all claims have been proven false
At any rate, ( assuming you have Unlocked Bootloader ) just flash another kernel with recovery, do a full wipe including formating the system partition and restore your system via flashing a rom
Click to expand...
Click to collapse
i got that problem i cant hard reset my phone i forgott my posswords and the key combo dosent work and i have never rooted before, can you give me a step by step for dummie (me)
petterssonjohan said:
9
i got that problem i cant hard reset my phone i forgott my posswords and the key combo dosent work and i have never rooted before, can you give me a step by step for dummie (me)
Click to expand...
Click to collapse
If you can enter flash mode, flash the latest firmware and software for your device using flash tool.
What is flash mode? I can get the phone in a mode where the indicator lamp turns blue is it that?
get Flashtool @ https://xperiafirmware.com/flashtool/
it includes Xperiafirm so you can download a stock ROM for your device and build an .ftf file
when you have the ftf file, drag it into the main Flashtool window
follow prompts
I've been searching the forum for several hours now. I do not believe the phone I have is a developer edition and I know the bootloader is locked. Everything on it is stock (no root or anything) and it maybe running 4.4 or 5.1, but no longer boots into the OS so i'm not sure.
Ideally I'm just looking for a way to get data off the device. However, if someone could point me in the right direction for getting the whole device up and running again, that would be even better.
I've rooted / installed custom recoveries and roms on many devices before, so I'm not afraid of running any necessary commands.
Thanks in advance for any help and let me know if any more information is needed.
EDIT: Forgot to mention I could not find a place where adb would see the device. The only thing that sees it is fastboot.
J3gb3rt
I just got my bricked Moto X that wouldn't even turn the screen on and it's now downloading the last released OTA. All my data seems to be intact as well (I haven't used this phone in nearly 2 years).
If fastboot (via command prompt) can see your phone, then you should be able to get it working. The main thing that got my phone to boot was the steps in this video: https://youtu.be/njXQYn53SPc Long story short, you basically have to make a bat file that simulates what RSDLite does when installing.
Long story, but after travails with an Amazon-purchased Oneplus 9 Pro due to it being locked (T-Mobile!) and them refusing to unlock it....
I went to OnePlus and got myself a OnePlus 10 Pro Unlocked. Still have the T-Mobile sim, though.
My question....
I have been out of the rooted phone scene for some time. I had a Oneplus 2 rooted and a Samsung Note 4 and 5 rooted. But things are different now, I'm gathering. Plus this is a new phone and I don't want to toss away hundreds of dollars by bricking it.
I used TWRP back in the day. Flashed many a custom rom back then. But with this OnePlus, I already unlocked it which... is that the same as rooting it? And what are the benefits of rooting / flashing roms vs just going with what is currently on this US phone (Oxygen 13 but not 13.1 yet)? I kinda want to see TWRP on here, and back up my whole set up into files I can then copy to my computer(s) for safety's sake. At least I liked that feature when I had it w/ the OP 2 and others.
Trying to get back up to speed in the world of rooting as it stands now.
Thanks.
TWRP on this device is really, "make of it what you will." It doesn't fully support this phone officially, and the leaked versions don't support device decryption, so you'll be forced to not use a passcode on your phone.
You don't need TWRP anymore, you just need to be careful and know what you're doing. There's guides for every model here, although they're all basically the same. Try to avoid flashing anything from your PC to the phone, just flash inside Magisk and BOOT images.
From my knowledge the reason for this is there's hidden partitions from OPPO all over the filesystem and normal flashers don't take this into account, anyone just trying to flash a full zip has bricked.
Which leads me to, there's no full recovery for this device that's free. If you brick a file and end up boot looping both slots, you're gonna have to pay for a restore. Even with TWRP, from what I hear, full backups sometimes fail to restore properly on this device.
TL;DR Be careful, read guides, you'll be fine. Rooting (on this device, with a lack of full recovery, hence no custom ROMs or Kernels) is really just used for audio mods, photo mods like free google photos, extensive app mods, etc. If you're not actively looking into any of these, stock Android is pretty solid.
Prant said:
TWRP on this device is really, "make of it what you will." It doesn't fully support this phone officially, and the leaked versions don't support device decryption, so you'll be forced to not use a passcode on your phone.
You don't need TWRP anymore, you just need to be careful and know what you're doing. There's guides for every model here, although they're all basically the same. Try to avoid flashing anything from your PC to the phone, just flash inside Magisk and BOOT images.
From my knowledge the reason for this is there's hidden partitions from OPPO all over the filesystem and normal flashers don't take this into account, anyone just trying to flash a full zip has bricked.
Which leads me to, there's no full recovery for this device that's free. If you brick a file and end up boot looping both slots, you're gonna have to pay for a restore. Even with TWRP, from what I hear, full backups sometimes fail to restore properly on this device.
TL;DR Be careful, read guides, you'll be fine. Rooting (on this device, with a lack of full recovery, hence no custom ROMs or Kernels) is really just used for audio mods, photo mods like free google photos, extensive app mods, etc. If you're not actively looking into any of these, stock Android is pretty solid.
Click to expand...
Click to collapse
Thanks for this.
I got as far as unlocking the phone and installing Magisk. But haven't gone further until I understand what the next step is.
Can I root non-destructively? Or is the phone wiped?
If you're unlocked and have Magisk installed, rooting is as easy as booting a patched boot image, then using Magisk to install it to your boot image. You have the choice of finding a matching one in one of the guides or pulling your own from a full zip.
It must match the firmware revision, I know for a fact personally that region matters little in case of NE2215/3, as you're only doing a one time boot.
I recommend @g96818 's guide here, you can find almost every firmware's boot image posted there if you prefer patch it yourself using Magisk or just boot an already patched one.
I have a 10 Pro (NE2215) rooted as a daily driver using TMO US.
Unlocked means 2 things in the android phone scene. Either it's carrier unlocked and can take any sim from any phone company or it bootloader unlocked which is needed to root and load custom roms.
There aren't any custom roms for the 10pro because of the lack of a full recovery system. Basically the ability to force full flash a stock rom in case the custom ROM soft bricks the phone. So that leaves rooting as the reason to unlock your bootloader.
I suggest reading the guide for rooting this phone, it's relatively easy. TWRP is unnecessary as it doesn't offer much without custom ROMs. Also you should back up everything on the phone that you don't want to lose because during the rooting process a factory reset will occur (android safety feature).