Is there a ROM for this yet? And link to how to root and install and unlock BL?
cell2011 said:
Is there a ROM for this yet? And link to how to root and install and unlock BL?
Click to expand...
Click to collapse
Unfortunately for the xt1609 there is no bootloader unlock method available, no root method available, and therefore no roms available for it. Verizon has the xt1609 on complete lockdown.
classic757 said:
Unfortunately for the xt1609 there is no bootloader unlock method available, no root method available, and therefore no roms available for it. Verizon has the xt1609 on complete lockdown.
Click to expand...
Click to collapse
This is partially incorrect, it DOES have a root method, just not a bootloader unlock method. Got to the auto#initroot thread by searching XT1609, mine is rooted and works fine. Like I said though, no bootloader unlockage yet. Nor custom ROMs.
Voltz100999 said:
This is partially incorrect, it DOES have a root method, just not a bootloader unlock method. Got to the auto#initroot thread by searching XT1609, mine is rooted and works fine. Like I said though, no bootloader unlockage yet. Nor custom ROMs.
Click to expand...
Click to collapse
Yep, I know all about it.
However, at the time of my posting it was correct that there was no bootloader unlock/root method available for the xt1609.
Also If you look through the auto#initroot thread you will see I've posted several times there.
Appreciate the fyi though.
Thanks.
classic757 said:
Yep, I know all about it.
However, at the time of my posting it was correct that there was no bootloader unlock/root method available for the xt1609.
Also If you look through the auto#initroot thread you will see I've posted several times there.
Appreciate the fyi though.
Thanks.
Click to expand...
Click to collapse
I remember you, and I agree, at the time it was correct. And I have been working on a BL unlock. It might happen, since I am able to flash BLs no issue, we could possibly just use an unlocked bootloader from an XT1601 or something of the sort, since it is a harpia device, it should in theory work.
Voltz100999 said:
I remember you, and I agree, at the time it was correct. And I have been working on a BL unlock. It might happen, since I am able to flash BLs no issue, we could possibly just use an unlocked bootloader from an XT1601 or something of the sort, since it is a harpia device, it should in theory work.
Click to expand...
Click to collapse
You are able to flash unlocked bootloaders from other harpia's
onto the xt1609?
classic757 said:
You are able to flash unlocked bootloaders from other harpia's
onto the xt1609?
Click to expand...
Click to collapse
That's what I'm working on, finding an unlocked BL file to use, or, if I can, edit mine so that I can test it. If it works, I'll upload the file, if it does not, I will try to figure out the whole deal about blowing a QFuse.
Voltz100999 said:
That's what I'm working on, finding an unlocked BL file to use, or, if I can, edit mine so that I can test it. If it works, I'll upload the file, if it does not, I will try to figure out the whole deal about blowing a QFuse.
Click to expand...
Click to collapse
Where you able to flash one?
TechOut said:
Where you able to flash one?
Click to expand...
Click to collapse
Yes, as the /dev folder is not write protected*, but I wasn't able to boot it, locked BL. I flashed twrp3.1.1.0-harpia and it DID flash, but like I said, locked BL.
*As root anyways.
---------- Post added at 04:52 AM ---------- Previous post was at 04:51 AM ----------
Voltz100999 said:
Yes, as the /dev folder is not write protected*, but I wasn't able to boot it, locked BL. I flashed twrp3.1.1.0-harpia and it DID flash, but like I said, locked BL.
*As root anyways.
Click to expand...
Click to collapse
Disregard that, I made a mistake post. And no, could not find a BL from one of those devices that was pre-unlocked.
Voltz100999 said:
Yes, as the /dev folder is not write protected*, but I wasn't able to boot it, locked BL. I flashed twrp3.1.1.0-harpia and it DID flash, but like I said, locked BL.
*As root anyways.
---------- Post added at 04:52 AM ---------- Previous post was at 04:51 AM ----------
Disregard that, I made a mistake post. And no, could not find a BL from one of those devices that was pre-unlocked.
Click to expand...
Click to collapse
So anyway to get a custom ROM as of right now?
TechOut said:
So anyway to get a custom ROM as of right now?
Click to expand...
Click to collapse
Locked bootloader means no custom ROMs unless a permanent root exploit is identified for this model.
TechOut said:
So anyway to get a custom ROM as of right now?
Click to expand...
Click to collapse
As far as I know, no. I'll ask jcase if he will add support for out devices.
http://bits-please.blogspot.com.br/2016/02/unlocking-motorola-bootloader.html?m=1
evangelico793 said:
http://bits-please.blogspot.com.br/2016/02/unlocking-motorola-bootloader.html?m=1
Click to expand...
Click to collapse
This is very interesting but appears to be a little beyond my means at this time. :|
Related
It appears that real soon we may have root for locked bootloader devices running Lollipop.
Read here for more info.
zoid_99 said:
It appears that real soon we may have root for locked bootloader devices running Lollipop.
Read here for more info.
Click to expand...
Click to collapse
One thing has nothing to do with the other.
Lollipop requires some changes to have root access and that was only possible with a modified kernel.
Now Chainfire managed to root the Lollipop without a custom kernel.
But installing ZIP file of root need a custom recovery , so still need to have the device with unlocked bootloader .
I've done the root Lollipop using this new root method of Chainfire.
Junior Passos said:
One thing has nothing to do with the other.
Lollipop requires some changes to have root access and that was only possible with a modified kernel.
Now Chainfire managed to root the Lollipop without a custom kernel.
But installing ZIP file of root need a custom recovery , so still need to have the device with unlocked bootloader .
I've done the root Lollipop using this new root method of Chainfire.
Click to expand...
Click to collapse
If you read the article it appears that there is no need to install a zip in a custom recovery to get root with this method.
" the need for ramdisk modifications was concerning for many users of bootloader-locked devices for which no unlock is available (yes, they do unfortunately exist). The answer to their prayers is now here"
zoid_99 said:
If you read the article it appears that there is no need to install a zip in a custom recovery to get root with this method.
" the need for ramdisk modifications was concerning for many users of bootloader-locked devices for which no unlock is available (yes, they do unfortunately exist). The answer to their prayers is now here"
Click to expand...
Click to collapse
Hmmm interesting.
Then the process should be with CF-Auto-Root .
I used one of those before when I first root in Lollipop.
But thought the command "mfastboot boot cf-auto-root.img" only work with unlocked bootloader and not the locked too.
Amazing.
Me excite!
You can only flash signed zips, so this only makes it easier because you dont need a device specific package for rooting
godutch said:
You can only flash signed zips, so this only makes it easier because you dont need a device specific package for rooting
Click to expand...
Click to collapse
Translated... Will it work on moto x vzw?
GatorsUF said:
Translated... Will it work on moto x vzw?
Click to expand...
Click to collapse
No.
cam30era said:
No.
Click to expand...
Click to collapse
OF course
This revelation means that Android 5.0 users*no longer need to run a modified kernel to gain root access via SuperSU (or other root solutions). While not a huge problem on Nexus devices with unlockable bootloaders, the need for ramdisk modifications was concerning for many users of bootloader-locked devices for which no unlock is available (yes, they do unfortunately exist). The answer to their prayers is now here, and we can present an exclusive explanation of the changes needed. At least for now (until/unless Google patch this), it is possible to gain root access and then install and use SuperSU on a stock Android 5.0 device, without any kernel ramdisk tweaking. The reason for this is the need for SuperSU to run a service as root, to allow for unconstrained root access on SELinux-protected devices.
Bump. We need root. Can't believe nobody seems to be working on a workaround. No safestrap? No kexec? No root? What happened to our glorious hackers?
neh4pres said:
Bump. We need root. Can't believe nobody seems to be working on a workaround. No safestrap? No kexec? No root? What happened to our glorious hackers?
Click to expand...
Click to collapse
The glorious hackers are/have tried. Security continues to be more and more difficult to break. Jump in the pool and get it done if you want it sooner. Otherwise, buy a pure edition so you can unlock the boot loader
neh4pres said:
Bump. We need root. Can't believe nobody seems to be working on a workaround. No safestrap? No kexec? No root? What happened to our glorious hackers?
Click to expand...
Click to collapse
Thanks Motorola -_-
Buy a nexus 6. That's what I did. Still have the moto x for my wife so I can play with it
Can't afford it right now. If I knew programming, you bet I would be working on it. God I hate Verizon, but been here so long it's my cheapest option.
matt99017d said:
The glorious hackers are/have tried. Security continues to be more and more difficult to break. Jump in the pool and get it done if you want it sooner. Otherwise, buy a pure edition so you can unlock the boot loader
Click to expand...
Click to collapse
Will the pure edition work on Verizon?
GrandMstrBud said:
Will the pure edition work on Verizon?
Click to expand...
Click to collapse
From what I understand, if you pop an activated Verizon SIM card into it, it'll work. Read that it'll work on the unlocked Nexus 6 too.
GreenMunky said:
From what I understand, if you pop an activated Verizon SIM card into it, it'll work. Read that it'll work on the unlocked Nexus 6 too.
Click to expand...
Click to collapse
LTE should work but what about CDMA side of it?
GreenMunky said:
From what I understand, if you pop an activated Verizon SIM card into it, it'll work. Read that it'll work on the unlocked Nexus 6 too.
Click to expand...
Click to collapse
GrandMstrBud said:
LTE should work but what about CDMA side of it?
Click to expand...
Click to collapse
No, CDMA will not work, nor 3G. So you will be confined only to LTE service and Google Voice (or similar).
matt99017d said:
The glorious hackers are/have tried. Security continues to be more and more difficult to break. Jump in the pool and get it done if you want it sooner. Otherwise, buy a pure edition so you can unlock the boot loader
Click to expand...
Click to collapse
Looks like your idea will not work and maybe that's the reason for this thread? Pure Edition won't work on VZW
I think that my phone is already unlocked. To be honest I'm not 100% sure. I am running a deodexed rooted version of lollipop right now, but I did all this stuff almost 2 years ago and haven't messed with any of it since. I do have an icon of unlocked padlock when booting up my phone. I think that means the bootloader is unlocked, but I'm not sure if that is what it means or not. Someone on reddit shared a link to an article by jdrch (Sorry can't link to it, still new here) about unlocking the bootloader and installing CyanogenMod 13 for G900V. The first thing he has you do is check your eMMC, but the article says this:
"As of this writing, it does not work for S5s with 11 Toshiba eMMCs. Due to the possibility of the bootloader unlock exploit being patched in the Marshmallow update, I’d highly suggest doing this BEFORE updating to any stock Marshmallow OTA."But if I intend to go straight to CM13 (if that is possible) does it even matter that I don't have correct eMMC?
EDIT: Nevermind. I see now that my bootloader is not unlocked and after doing some more searching through the forums. I have found that it is not possible for the Toshiba eMMC chip. :crying: I need a new phone.
thetillmiester said:
I think that my phone is already unlocked. To be honest I'm not 100% sure. I am running a deodexed rooted version of lollipop right now, but I did all this stuff almost 2 years ago and haven't messed with any of it since. I do have an icon of unlocked padlock when booting up my phone. I think that means the bootloader is unlocked, but I'm not sure if that is what it means or not. Someone on reddit shared a link to an article by jdrch (Sorry can't link to it, still new here) about unlocking the bootloader and installing CyanogenMod 13 for G900V. The first thing he has you do is check your eMMC, but the article says this:
"As of this writing, it does not work for S5s with 11 Toshiba eMMCs. Due to the possibility of the bootloader unlock exploit being patched in the Marshmallow update, I’d highly suggest doing this BEFORE updating to any stock Marshmallow OTA."But if I intend to go straight to CM13 (if that is possible) does it even matter that I don't have correct eMMC?
Click to expand...
Click to collapse
You are NOT unlocked and do not pretend you are.
You cannot flash CM13. The unlock icon when you boot is simply a result of having a custom binary installed.
Nandr0idC0nsumer said:
You are NOT unlocked and do not pretend you are.
You cannot flash CM13. The unlock icon when you boot is simply a result of having a custom binary installed.
Click to expand...
Click to collapse
Nobody is PRETENDing anything. I already said I wasn't sure if I was or not.
thetillmiester said:
Nobody is PRETENDing anything. I already said I wasn't sure if I was or not.
Click to expand...
Click to collapse
You were talking about flashing CM13, which will brick you if you're not unlocked
Nandr0idC0nsumer said:
You were talking about flashing CM13, which will brick you if you're not unlocked
Click to expand...
Click to collapse
Okay so if I unlock then flash CM13 will it work even though my eMMC is the 11 Toshiba?
EDIT: Nevermind, see edit on OP.
thetillmiester said:
EDIT: Nevermind, see edit on OP.
Click to expand...
Click to collapse
Yes it sucks that 11s cannot unlock
@GeTex and the others are working on an unlock but its not looking good for now.
When trying to unlock bootloader it says that your device does not qualify for bootloader unlocking?
Why?
Invoker jb said:
When trying to unlock bootloader it says that your device does not qualify for bootloader unlocking?
Why?
Click to expand...
Click to collapse
A little more information. Is it an Amazon version because if it is, then it can't be unlocked.
No
Tel864 said:
A little more information. Is it an Amazon version because if it is, then it can't be unlocked.
Click to expand...
Click to collapse
No
Tel864 said:
A little more information. Is it an Amazon version because if it is, then it can't be unlocked.
Click to expand...
Click to collapse
That's not true, I have an amazon version and successfully unlocked the bootloader and installed twrp for example
---------- Post added at 05:40 PM ---------- Previous post was at 05:39 PM ----------
Invoker jb said:
When trying to unlock bootloader it says that your device does not qualify for bootloader unlocking?
Why?
Click to expand...
Click to collapse
Did you tried to get the unlock code on the Motorola page? It's mentioned in rooting guide.
Its solved
Invoker jb said:
Its solved
Click to expand...
Click to collapse
Please tell us how you solved it and where exactly was the problem, so others with similar issues can read your solution instead of starting new threads, because they don't find answers.
When copying the string had some space between string that's
So when copying string check clearly if there is a space.
strongst said:
That's not true, I have an amazon version and successfully unlocked the bootloader and installed twrp for example
Click to expand...
Click to collapse
They "fixed" that error now. Amazon phones are not unlockable anymore. If you install an OTA, your phone will be "fixed" too.
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/87215
SoNic67 said:
They "fixed" that error now. Amazon phones are not unlockable anymore.
Click to expand...
Click to collapse
So I'm lucky to have an older one any source about this? Cause it must be new since some days
strongst said:
So I'm lucky to have an older one any source about this? Cause it must be new since some days
Click to expand...
Click to collapse
Source? It's all over the G4 forums and confirmed by Amazon and Motorola.
Another source besides the official Moto page that I linked above?
Also is this thread from Moto G4:
http://forum.xda-developers.com/moto-g4/how-to/psa-7-19-2016-amazon-prime-g4-eligible-t3422447
Tel864 said:
Source? It's all over the G4 forums and confirmed by Amazon and Motorola.
Click to expand...
Click to collapse
SoNic67 said:
Another source besides the official Moto page that I linked above?
Also is this thread from Moto G4:
http://forum.xda-developers.com/moto-g4/how-to/psa-7-19-2016-amazon-prime-g4-eligible-t3422447
Click to expand...
Click to collapse
So that clearly describes, that not all phones from Amazon can't be unlocked. Because I don't have this ad version, but bought with prime, so all ok. I have mine since 14 days and all ok with unlocking.
Oh, no, that was ONLY for the Amazon ad-sponsored versions! The other ones bought from Amazon (including mine) are fine.
strongst said:
So that clearly describes, that not all phones from Amazon can't be unlocked. Because I don't have this ad version, but bought with prime, so all ok. I have mine since 14 days and all ok with unlocking.
Click to expand...
Click to collapse
Yeah this is true. Only the ones that come with amazon ads are locked. The rest should be unlock able.
Please help me.... I can't able to unlockbootloader of my g4 plus,
slot -count not found
Slot -suffixes not found
Slot -suffixes not found
Showing
Where do I find the new logo 7.0 in bin format? I want to remove the warning
Is there a way to root Moto G4 XT1625 Amazon Edition? with Kingroot or something like that?
someone already tried kingroot? at least to temp root and install Adaway, remove bloatware and stuff
stkpxl said:
You would need to unlock the bootloader, which Motorola will no longer do for that version. I don't think there is any other way to root it.
Click to expand...
Click to collapse
That's not true. It worked just fine for me. I just followed Motorola's instructions.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
You'll need a motorola account. The page I just posted will ask you to create one.
---------- Post added at 01:51 AM ---------- Previous post was at 01:25 AM ----------
stkpxl said:
You would need to unlock the bootloader, which Motorola will no longer do for that version. I don't think there is any other way to root it.
Click to expand...
Click to collapse
ewtoombs said:
That's not true. It worked just fine for me. I just followed Motorola's instructions.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b
You'll need a motorola account. The page I just posted will ask you to create one.
Click to expand...
Click to collapse
Oh wait, Amazon Edition? Well, beats me, then. You can try, I guess. Mine's an XT1625, anyway.
Apparently there are some Amazon editions that will allow you to unlock and others that won't I do not know the difference between the two since I have the regular version. All you can do is check on the Motorola website and try to get an unlock code for your phone. If they give you one you are in luck, otherwise trying the methods on this site to unlock it has proven to be a bad idea for some who have bricked their phones.
I have nougat already and was expecting for a easier way to unlock bootloader than in Marshmallow so I waited for it. Now with Nougat I see it very impossible to root or get Lineage. So can someone please do a guide for my problem please?
Lscastro2000 said:
I have nougat already and was expecting for a easier way to unlock bootloader than in Marshmallow so I waited for it. Now with Nougat I see it very impossible to root or get Lineage. So can someone please do a guide for my problem please?
Click to expand...
Click to collapse
Lots of guides already.
It's the same process. Downgrade bootloader to unlockable version, unlock, flash TWRP, flash ROM, flash Gapps. Pays to read and search player.
I agree readling through all these threads its mass confusion. Some say it works with nougat some say it bricks there devices. Is there a simple one click root like wugfresh has with the nexus devices
z45123qqq said:
I agree readling through all these threads its mass confusion. Some say it works with nougat some say it bricks there devices. Is there a simple one click root like wugfresh has with the nexus devices
Click to expand...
Click to collapse
I am in the same boat :c . lineage root. Magisk root . SuperSU root. No one explains
Lscastro2000 said:
I have nougat already and was expecting for a easier way to unlock bootloader than in Marshmallow so I waited for it. Now with Nougat I see it very impossible to root or get Lineage. So can someone please do a guide for my problem please?
Click to expand...
Click to collapse
Try axon7toolkit, it is supposed to work with all devices
---------- Post added at 03:31 AM ---------- Previous post was at 03:30 AM ----------
z45123qqq said:
I agree readling through all these threads its mass confusion. Some say it works with nougat some say it bricks there devices. Is there a simple one click root like wugfresh has with the nexus devices
Click to expand...
Click to collapse
yeep, axon7toolkit. Actually bkores (the man behind the tool) was based on wugfresh's stuff if I recall correctly
CLaudioman2009 said:
I am in the same boat :c . lineage root. Magisk root . SuperSU root. No one explains
Click to expand...
Click to collapse
Many guides explains very well. If you are unsure about what you are going to do with your device then my advice is that you stay on stockrom until you understand and know what you are up to.
Smedslund said:
Many guides explains very well. If you are unsure about what you are going to do with your device then my advice is that you stay on stockrom until you understand and know what you are up to.
Click to expand...
Click to collapse
This kind of answers are sh** . if you want to be helpful just give us a link or don't answer . thanks
CLaudioman2009 said:
This kind of answers are sh** . if you want to be helpful just give us a link or don't answer . thanks
Click to expand...
Click to collapse
Well to be fair you can just look things up for yourself. He does have a point, stay on the stock rom so you can learn more about the device. Read all the guides that you can find. No need to be rude, thank you.
CLaudioman2009 said:
This kind of answers are sh** . if you want to be helpful just give us a link or don't answer . thanks
Click to expand...
Click to collapse
Oh okay, let's just assume that you know what EDL mode, DFU mode, and FTM mode are. And that you know what happens if you get a DFU brick, what is the solution... Read a bunch of guides and help threads before doing anything, especially if this is your only phone or if you can't use the warranty
To be fair, there isn't a guide for using MiFlash to downgrade the device from Nougat to MM.
I'd suggest you look for the MiFlash download link in the Download Center sticky and then download the necessary MM ROM for your device.
From then on you can just follow a guide to unlock the bootloader using axon7tool and install twrp etc.
greencartim said:
Well to be fair you can just look things up for yourself. He does have a point, stay on the stock rom so you can learn more about the device. Read all the guides that you can find. No need to be rude, thank you.
Click to expand...
Click to collapse
Or you can assume people asking that here ddidnt fimd a good guide or thread about and just help posting a link.
Or be a mor** and say... Yeah yeah. "Use google" answers. What is his 4chan?
---------- Post added at 03:03 PM ---------- Previous post was at 03:02 PM ----------
zaphy42 said:
To be fair, there isn't a guide for using MiFlash to downgrade the device from Nougat to MM.
I'd suggest you look for the MiFlash download link in the Download Center sticky and then download the necessary MM ROM for your device.
From then on you can just follow a guide to unlock the bootloader using axon7tool and install twrp etc.
Click to expand...
Click to collapse
This is a good answer.
Again with the rudeness, no need for that friendo. Since you really want a link, here it is http://bfy.tw/CdYq.
greencartim said:
Again with the rudeness, no need for that friendo. Since you really want a link, here it is http://bfy.tw/CdYq.
Click to expand...
Click to collapse
Very nice, but I think his problem is that he needs to downgrade to Marshmallow before he even attempts to unlock the bootloader.
I'm an A2017G user, not a 2017/2017U user, so it might be slightly different for you guys (didn't think it was?), but I believe that you can't unlock the bootloader if your device is already on Nougat, it must be downgraded first.
zaphy42 said:
Very nice, but I think his problem is that he needs to downgrade to Marshmallow before he even attempts to unlock the bootloader.
I'm an A2017G user, not a 2017/2017U user, so it might be slightly different for you guys (didn't think it was?), but I believe that you can't unlock the bootloader if your device is already on Nougat, it must be downgraded first.
Click to expand...
Click to collapse
Yes you do need to downgrade, there's a toolkit that does everything for you and I believe it was mentioned a few times in this thread.