Database Users

[GUIDE]Unlock Bootloader - Moto E [UPDATED]

UNLOCK YOUR BOOTLOADER​
WARNING: UNLOCKING YOUR BOOTLOADER VOIDS YOUR WARRANTY.PROCEED AT YOUR OWN RISK.
NOTE: Unlocking the bootloader will Wipe/ factory reset your device, and will delete all personal data from your device such as apps, photos, messages, and settings.
INSTRUCTIONS:
Make sure to take a backup of your entire device data.
Download the Android SDK OR Download the Minimal ADB and Fastboot
Install the latest Motorola USB Drivers on your desktop. Download here.
Put your device in fastboot mode (power off, then press the power and volume down buttons simultaneously).
Open Command Prompt on androidsdk/platform-tools/ (Hold Shift and right click and press open command window here)
Connect your Phone to PC
Type this in the CMD prompt window - fastboot oem get_unlock_data
You will get a return string. Copy it. [Right Click-Mark- Mark the text by pressing the shift key-Now press Ctrl+C]
Paste all the lines together in a notepad. Remove the empty spaces.
Now go to the Motorola Site.Sign in using your Google account or Motorola ID. Scroll down the page and paste the copied string in the field at step #6. Then click on ‘Can my device be unlocked?’, after which a "REQUEST UNLOCK KEY" button will appear at the bottom of page.
To get your unlock key, select the ‘I Agree’ option. Note: You will receive an email with your Unlock Key at the email address you used to log in there.
Important – Copy the 20-character key that Motorola sent you via email. Make sure your device is connected.
Then in CMD type: fastboot devices (To check your device is connected)
Then type: fastboot oem unlock UNIQUE_KEY
NOTE: In above command, replace the word ‘UNIQUE_KEY’ with the unlock code that you got via email. Then hit enter and the unlocking process should begin. Wait for a while and soon you’ll see ‘Bootloader Unlocked’ warning on your Moto E.
To relock the bootloader:
Go to Fastboot and give the command fastboot oem lock
You can always appreciate my work by pressing the Thanks Button.:good:
Good Day

Video Tutorial
FAQ
[SIZE=+1]Q1:How to remove the unlocked bootloader message? [/SIZE]
Download the logo.zip.
Extract all the files
Reboot to fastboot mode (power + vol down)
Now open cmd and use cd command to go to the directory where you placed the file.
Now Type the command: fastboot flash logo logo.bin
Reboot from the recovery (use vol up to select and vol down to navigate)
Now your bootlogo should be restored back to the normal version
​

Want to Get OTA updates even after Rooting your Device? Here's how.
Use the full unroot option from the Super Su
Flash the stock recovery Use Code : mfastboot flash recovery recovery.img
Now you'll be able to get OTA updates as before

awesome..:good:

bhushan2k said:
awesome..:good:
Click to expand...
Click to collapse
Thank You.
If you have got the MOTO E can you test the root exploit too?

Falcon G said:
Thank You.
If you have got the MOTO E can you test the root exploit too?
Click to expand...
Click to collapse
m yet to get it..hope @varunangirash and @rdxkaddi can try since they have it..

Nice work bro but elaboration of the guide to more understandable way for noobs around would be more helpful. I successfully Unlocked my bootloader (so, it's not for me). If you want I can elaborate these steps a bit clearer. Anyways. Nice work :good:

Mrtoxicgamer10 said:
Nice work bro but elaboration of the guide to more understandable way for noobs around would be more helpful. I successfully Unlocked my bootloader (so, it's not for me). If you want I can elaborate these steps a bit clearer. Anyways. Nice work :good:
Click to expand...
Click to collapse
Can you tell me what steps need elaboration

Falcon G said:
reserved
Click to expand...
Click to collapse
Hey will I still be able to get OTA updates after unlocking Bootloader?

SArnab©® said:
Hey will I still be able to get OTA updates after unlocking Bootloader?
Click to expand...
Click to collapse
Yes you can.
But don't root for ota

SArnab©® said:
Hey will I still be able to get OTA updates after unlocking Bootloader?
Click to expand...
Click to collapse
Yes you can.
---------- Post added at 07:08 PM ---------- Previous post was at 07:05 PM ----------
Falcon G said:
Can you tell me what steps need elaboration
Click to expand...
Click to collapse
Only one step is missing bro that the device needs to be connect.

Falcon G said:
Yes you can.
But don't root for ota
Click to expand...
Click to collapse
Well I was thinking of flashing TWRP Recovery to root.
Can't I simply use Full Unroot option of SuperSu to unroot when an ota is available to Download and update?

I think we can perform the bootloader unlocking process using ADB & Fastboot files plus USB drivers, and overcome the need to download the 510 MB Android SDK. Is that possible?

mayurjango said:
I think we can perform the bootloader unlocking process using ADB & Fastboot files plus USB drivers, and overcome the need to download the 510 MB Android SDK. Is that possible?
Click to expand...
Click to collapse
Yes. Only adb files are needed,

Thanks. Link to latest ADB files please.

mayurjango said:
Thanks. Link to latest ADB files please.
Click to expand...
Click to collapse
Here you are has both ADB and Fastboot all in a tiny, easy to use package http://forum.xda-developers.com/showthread.php?t=2317790.
Sent from my SCH-I535 using XDA Premium 4 mobile app

SArnab©® said:
Well I was thinking of flashing TWRP Recovery to root.
Can't I simply use Full Unroot option of SuperSu to unroot when an ota is available to Download and update?
Click to expand...
Click to collapse
I am not sure if it would work. But you can try for yourself.
shimp208 said:
Here you are has both ADB and Fastboot all in a tiny, easy to use package http://forum.xda-developers.com/showthread.php?t=2317790.
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Added to the OP

Just a Friendly Reminder. I am receiving PM from a lot of guys on how to unlock their bootloader. I will help all of you, you know I will. But if you consider appreciating my work by pressing the thanks button it would be great for me and will help me serve you better. :good:

Mrtoxicgamer10 said:
Yes you can.
---------- Post added at 07:08 PM ---------- Previous post was at 07:05 PM ----------
Only one step is missing bro that the device needs to be connect.
Click to expand...
Click to collapse
Added to the OP Thanks :good:

Step-by-Step Guide to Unlock Moto E Bootloader: http://webtrickz.com/how-to-unlock-bootloader-on-moto-e/
Hope you find it helpful.
P.S. Remove the link if you consider it as spam.

Your device is corrupt. It can't be trusted and may not work properly. help!

Long story short, hopped over to android following years and years of using IOS.
Bought a nexus 6p, learnt about root, gained root access to the 6p, and began installed root apps.
This morning, i installed Gsam battery monitor root companion, found out it broke the normal Gsam battery monitor app, tried to uninstall the gsam root companion several times. Everytime i uninstalled it and rebooted, it would just reappear on the phone and wouldn't actually uninstall properly at all.
On the third go, it rebooted into the red triangle " Your device is corrupt. It can't be trusted and may not work properly." and is stuck on the google logo.
Accessed recovery and tried to restore the nandroid backup, no luck, still boots up to red triangle and is stuck on google logo.
Accessed recovery and tried to restore to factory default, no luck, still boots up to red triangle and is stuck on google logo.
How do i fix my phone now? Any help would be greatly appreciated.

red triangle with the android mascot logo?
if so, put it into fastboot and reinstall recovery and see if that worked

gd6noob said:
red triangle with the android mascot logo?
if so, put it into fastboot and reinstall recovery and see if that worked
Click to expand...
Click to collapse
Its just a red triangle with an exclamation mark inside.
I can't post an image because i am a new member and need at least 10 posts.

https://support.google.com/nexus/answer/6185381?hl=en - It says it should dismiss by itself.

chichu_9 said:
- It says it should dismiss by itself.
Click to expand...
Click to collapse
The red logo does disappear and the device transitions to the black and white google boot logo.
It is here where the device becomes hung, i assume it is because the boot.img or boot files have been damaged, but i'm just guessing. What i am confused about is if the boot files are damaged, the nandroid restore should fix this problem (shouldn't it?), but it doesn't.

radaga5t said:
Long story short, hopped over to android following years and years of using IOS.
Bought a nexus 6p, learnt about root, gained root access to the 6p, and began installed root apps.
This morning, i installed Gsam battery monitor root companion, found out it broke the normal Gsam battery monitor app, tried to uninstall the gsam root companion several times. Everytime i uninstalled it and rebooted, it would just reappear on the phone and wouldn't actually uninstall properly at all.
On the third go, it rebooted into the red triangle " Your device is corrupt. It can't be trusted and may not work properly." and is stuck on the google logo.
Accessed recovery and tried to restore the nandroid backup, no luck, still boots up to red triangle and is stuck on google logo.
Accessed recovery and tried to restore to factory default, no luck, still boots up to red triangle and is stuck on google logo.
How do i fix my phone now? Any help would be greatly appreciated.
Click to expand...
Click to collapse
After a root went bad I had the same thing happen. I just used SkipSoft ToolKit and restored back to a stock image (MDB08L).
The corruption message disappeared.

Take a look at this guide By Heisenberg as it will help with some details.
The few times I flashed/reset the phone, I accidentally muddled up some steps. Specifically the flashing the boot and bootloader images.
Code:
[U]fastboot flash bootloader X:/bootloader.img[/U]
fastboot reboot bootloader
fastboot flash radio X:/radio.img
fastboot reboot bootloader
[U]fastboot flash boot X:/boot.img[/U]
fastboot erase cache
fastboot flash cache X:/cache.img
fastboot flash recovery X:/recovery.img
fastboot flash system X:/system.img
fastboot flash vendor X:/vendor.img
I would accidentally flash the bootloader.img image over the boot.img and cause the error, specifically the one you mentioned. I had to go through the flashing process VERY carefully again, and when flashing .imgs for root acess over to the stock ones.
I know is sounds trivial and I'm not saying you don't understand it, but give it a try and see if this resolves the issue. double check your lines and triple check your images (make sure there are NO spaces in the bootloader/boot img file directories. or_replace_spaces_with_underscores). I don't know how many times I have screwed up and it was because of a dash in the wrong spot or space in the .img directory. Let us know how you go.

Awesome!
Thank you very much everyone. I will try once i get home from work.
You have all been so helpful. Such a good community.

I hoped it worked out for you

urbanpitch said:
I hoped it worked out for you
Click to expand...
Click to collapse
Yep i was able to restore the phone via the heisenberg guide. Thanks!

radaga5t said:
Yep i was able to restore the phone via the heisenberg guide. Thanks!
Click to expand...
Click to collapse
Was just about to post a link to my guide but it looks as though you already got everything sorted out. I'm glad my little guide was able to assist you.

Heisenberg said:
Was just about to post a link to my guide but it looks as though you already got everything sorted out. I'm glad my little guide was able to assist you.
Click to expand...
Click to collapse
I'm having the very same issue and I don't understand what I'm supposed to do. Exact same issue a OP. I use the Mskip toolkit to the letter and that got me a bootloop. I have TWRP installed and I can access it. How can I recover my phone? Thanks in advance
---------- Post added at 11:24 PM ---------- Previous post was at 11:17 PM ----------
radaga5t said:
Awesome!
Thank you very much everyone. I will try once i get home from work.
You have all been so helpful. Such a good community.
Click to expand...
Click to collapse
Hey man, could you tell me the exact steps you took to fix yours? I'm having the same exact issue after having use that toolkit.

barondebxl said:
I'm having the very same issue and I don't understand what I'm supposed to do. Exact same issue a OP. I use the Mskip toolkit to the letter and that got me a bootloop. I have TWRP installed and I can access it. How can I recover my phone? Thanks in advance
Click to expand...
Click to collapse
Just go to my guide and follow the instructions in section 9. You'll need to look at the prerequisites section at the beginning of the OP first so you can install the latest version of adb/fastboot via the SDK.

Heisenberg said:
Just go to my guide and follow the instructions in section 9. You'll need to look at the prerequisites section at the beginning of the OP first so you can install the latest version of adb/fastboot via the SDK.
Click to expand...
Click to collapse
Cool ill give it a shot. Thank you. I'm all out of thanks for today
---------- Post added at 11:53 PM ---------- Previous post was at 11:35 PM ----------
Heisenberg said:
Just go to my guide and follow the instructions in section 9. You'll need to look at the prerequisites section at the beginning of the OP first so you can install the latest version of adb/fastboot via the SDK.
Click to expand...
Click to collapse
Im sorry but I'm completely lost. I have downloaded the factory images of my build, I have extracted the files but there isn't any bootloader.img and radio.img. When I click the extracted file it asks me if I want to download a windows application to open it.

barondebxl said:
Cool ill give it a shot. Thank you. I'm all out of thanks for today
---------- Post added at 11:53 PM ---------- Previous post was at 11:35 PM ----------
Im sorry but I'm completely lost. I have downloaded the factory images of my build, I have extracted the files but there isn't any bootloader.img and radio.img. When I click the extracted file it asks me if I want to download a windows application to open it.
Click to expand...
Click to collapse
You'll need to find a program that can extract the "tar.gz" compression format.

Heisenberg said:
You'll need to find a program that can extract the "tar.gz" compression format.
Click to expand...
Click to collapse
Ok thank you. 7zip works

barondebxl said:
I'm having the very same issue and I don't understand what I'm supposed to do. Exact same issue a OP. I use the Mskip toolkit to the letter and that got me a bootloop. I have TWRP installed and I can access it. How can I recover my phone? Thanks in advance
---------- Post added at 11:24 PM ---------- Previous post was at 11:17 PM ----------
Hey man, could you tell me the exact steps you took to fix yours? I'm having the same exact issue after having use that toolkit.
Click to expand...
Click to collapse
Basically i followed step 9 of Heisenberg's guide.
Code:
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
So i flashed all of the above minus the user data and re-locking the bootloader.
Let me know if you need any more info.

radaga5t said:
Basically i followed step 9 of Heisenberg's guide.
Code:
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
So i flashed all of the above minus the user data and re-locking the bootloader.
Let me know if you need any more info.
Click to expand...
Click to collapse
Thanks bud. I'm lost still. I have all the files needed in a folder I called " images" on my desktop. Do I have to write these commands you posted word for word? I mean I know I have to replace with my file name but for example I have the MDB08L so do I do : fastboot flash bootloader C:\angler\images\bootloader-angler-angler-02.01.img ( in my case) even though the folder is on my desktop?
Edit: I tried and it gave me an error saying it cant load it. So frustrating

barondebxl said:
Thanks bud. I'm lost still. I have all the files needed in a folder I called " images" on my desktop. Do I have to write these commands you posted word for word? I mean I know I have to replace with my file name but for example I have the MDB08L so do I do : fastboot flash bootloader C:\angler\images\bootloader-angler-angler-02.01.img ( in my case) even though the folder is on my desktop?
Edit: I tried and it gave me an error saying it cant load it. So frustrating
Click to expand...
Click to collapse
You got an error because you're pointing fastboot to a location where the file doesn't exist. If you had followed my guide and placed the files in C:\angler\images\ then the command would be correct, but you've placed the files in a different location, therefore you need to type the commands so that they include the path to where the files are actually located on your PC.
There's an easy way to do it, type the first portion of the command, for example "fastboot flash bootloader " (make sure there's a space after the last character), then you can grab the appropriate file with your mouse and drag/drop it into the command terminal window and the file path will be completed automatically for you, then just hit enter to execute the command.

Heisenberg said:
You got an error because you're pointing fastboot to a location where the file doesn't exist. If you had followed my guide and placed the files in C:\angler\images\ then the command would be correct, but you've placed the files in a different location.
You need to type the commands so that they include the path to where the files are actually located on your PC. There's an easy way to do it, type the first portion of the command, for example "fastboot flash bootloader " (make sure there's a space after the last character), then you can grab the appropriate file with your mouse and drag/drop it into the command terminal window and the file path will be completed automatically for you, then just hit enter to execute the command.
Click to expand...
Click to collapse
Thanks guys I finally figured it out. I'm at flashing the system and its taking a while obviously. Its actually easy...when you know what youre doing. Thank you so very much to the both of you!
Edit: back up and running! I was just frustrated cause I just got the phone this afternoon that's why. You guys are awesome
---------- Post added at 01:48 AM ---------- Previous post was at 01:36 AM ----------
barondebxl said:
Thanks guys I finally figured it out. I'm at flashing the system and its taking a while obviously. Its actually easy...when you know what youre doing. Thank you so very much to the both of you!
Edit: back up and running! I was just frustrated cause I just got the phone this afternoon that's why. You guys are awesome
Click to expand...
Click to collapse
One last question, whats the best method to root MDB08L? I want that chroma rom

Need Blu Vivo Air LTE Stock ROM!

Anyone know where I can get a stock rom for my Vivo Air LTE?

I have a system.IMG and boot.img
I have a system.IMG and a boot.img if you still need it?

i need it. I accidentally deleted a system/lib file. thought i put it there. I did not... how would I go about installing? I'll google the steps in the mean time.

trentag1988 said:
i need it. I accidentally deleted a system/lib file. thought i put it there. I did not... how would I go about installing? I'll google the steps in the mean time.
Click to expand...
Click to collapse
After downloading system.img to your computer you need to put the vivo air LTE in fastboot mode by turning it completely off. Then hold down power+volume up. Then choose reboot to bootloader connect the phone to your computer. Make sure you have adb and fastboot installed via Android SDK where adb resides such as the platform-tools directory put system.img in that folder and in that folder open it. Right click any white space while holding down shift on your keyboard and click open command from here. Then you can enter fastboot commands. fastboot devices make sure your device is detected then fastboot -w then fastboot format system then fastboot flash system system.img is your recovery still stock? here are three files system.img if your recover is messed too then i include recovery as well im not too sure if you need the boot.img but i included it in this link:
https://drive.google.com/drive/folders/0B4_9-6sS8dFeTGpSLVVSN015STA?usp=sharing
let me know how it goes ok??
---------- Post added 28-09-2016 at 12:10 AM ---------- Previous post was 27-09-2016 at 11:26 PM ----------
I also created a checksum file.chk use ubuntu's md5sum -c file.chk. To check md5

Recovery is still stock. I got 15 second adb installer. Is that the same as android SDK? I'll have to try this tonight. Google drive is requesting that I get permission. Allow when you can. Thank you! I'll attempt this tonight
---------- Post added at 05:07 PM ---------- Previous post was at 05:05 PM ----------
Is it okay that I didn't allow USB debug before bricking?

sorry i dunno if i shared it correctly on my google drive try this
trentag1988 said:
Recovery is still stock. I got 15 second adb installer. Is that the same as android SDK? I'll have to try this tonight. Google drive is requesting that I get permission. Allow when you can. Thank you! I'll attempt this tonight
---------- Post added at 05:07 PM ---------- Previous post was at 05:05 PM ----------
Is it okay that I didn't allow USB debug before bricking?
Click to expand...
Click to collapse
try this link i shared it to all
https://drive.google.com/drive/folders/0B4_9-6sS8dFeTGpSLVVSN015STA?usp=sharing
https://drive.google.com/drive/folders/0B4_9-6sS8dFeTGpSLVVSN015STA?usp=sharing

Downloading now. Can't wait to try!!! Thank you so much. That little phone is surprisingly amazing

here's the kicker though... i tried to 'restart to bootloader', i get stuck on blu splash screen. after getting rid of that one file, it's stayed stuck at blu screen. ever encountered this?

Blu vivo screen
When you are in recovery and reboot into bootloader that's where the Blu vivo air sign is stuck but you can execute fastboot commands

So, I got it to work. I had to terminal fastboot command, then reboot to bootloader, and it finally stuck. You are a life saver.
Was much easier to do in Linux than it was in Windows.

I put it in root with "sudo -s" command then "fastboot install system system.img" do I need to leave the bootloader unlocked??
---------- Post added at 01:42 AM ---------- Previous post was at 01:40 AM ----------
I was thinking of compiling a twrp for this phone, but I'm a little not sure exactly how to do it. I've seen tutorial, but vague

Blu vivo air lte
Alright, that's what I wanted to hear!! Glad you got your phone back...Sux there's no Roms and custom recovery for this phone but at least you got it working glad to have helped!

About the system.img
trentag1988 said:
here's the kicker though... i tried to 'restart to bootloader', i get stuck on blu splash screen. after getting rid of that one file, it's stayed stuck at blu screen. ever encountered this?
Click to expand...
Click to collapse
OK I had to root this vivo air LTE via king root to backup system image so if you want full stock you need to root your phone again with king root and then install super Sume from play store to remove KingRoot and have it replaced with SuperSU. Then you can fully unroot with SuperSU!!! I tried playing Pokemon go and it wouldn't let me because it thought my phone was rooted so that's one way to fix that!

Ohhhhhhh I was wondering how you got the image files ? I haven't had any issues with it so far. It's back to its wonderful goodness. By the way, how do you quote someone on here?? I see everyone doing it, but I don't know how

Quotes
Not too sure

sideloading adb firmware

So I am really stuck and don't know what to do. Unlocked the bootloader, installed twrp just fine and rooted. then I went to install a custom rom after I made sure it was working and then it kicks me back to the normal recovery. twrp is gone and I can't fastboot the firmware cause I wiped it to flash a rom. Now when I go to adb sideload I keep getting error 21 footer is wrong and signature verification has failed. Can someone please point me in the right direction to fix my phone? thanks

Download stock firmware and flash it via fastboot,all the instructions included in the link https://www.essential.com/developer/current-builds

gm007 said:
Download stock firmware and flash it via fastboot,all the instructions included in the link https://www.essential.com/developer/current-builds
Click to expand...
Click to collapse
Fastboot isn't enabled cause I wiped to flash a rom. and every time I try to sideload it with adb it fails.

tommyjames1992 said:
Fastboot isn't enabled cause I wiped to flash a rom. and every time I try to sideload it with adb it fails.
Click to expand...
Click to collapse
To use fastboot u need to boot ur phone to bootloader mode not to recovery,just follow the information in the link i gave you to know how to flash the firmware.

gm007 said:
To use fastboot u need to boot ur phone to bootloader mode not to recovery,just follow the information in the link i gave you to know how to flash the firmware.
Click to expand...
Click to collapse
Nothing pops up when I type in the command fastboot devices. My phone doesn't show.

tommyjames1992 said:
Nothing pops up when I type in the command fastboot devices. My phone doesn't show.
Click to expand...
Click to collapse
This phone is tricky to get recognized,try changing the usb cable, different usb port and make sure you have the correct drivers installed,and the latest adb fastboot files.

gm007 said:
This phone is tricky to get recognized,try changing the usb cable, different usb port and make sure you have the correct drivers installed,and the latest adb fastboot files.
Click to expand...
Click to collapse
weird thing is I can get it to show when I type fastboot -i 0x2e17 but I am not sure how to use that to flash the firmware. I believe I have all the lastest drivers since I unlocked my bootloader yesterday.

tommyjames1992 said:
weird thing is I can get it to show when I type fastboot -i 0x2e17 but I am not sure how to use that to flash the firmware. I believe I have all the lastest drivers since I unlocked my bootloader yesterday.
Click to expand...
Click to collapse
I had my phone for a week now and happened the same for me ,my pc wasn't recognizing the phone.
All I did is searched for drivers and new adb fastboot files and that did the trick.
Try to remove the phone from device managers on ur pc and install the drivers manually.
Good luck.
---------- Post added at 07:35 PM ---------- Previous post was at 07:15 PM ----------
Try this adb fastboot files,but remove the older one first
https://androidfilehost.com/?fid=3700668719832240948

gm007 said:
I had my phone for a week now and happened the same for me ,my pc wasn't recognizing the phone.
All I did is searched for drivers and new adb fastboot files and that did the trick.
Try to remove the phone from device managers on ur pc and install the drivers manually.
Good luck.
---------- Post added at 07:35 PM ---------- Previous post was at 07:15 PM ----------
Try this adb fastboot files,but remove the older one first
https://androidfilehost.com/?fid=3700668719832240948
Click to expand...
Click to collapse
So I am still got getting fastboot working to flash stock firmware but I managed to reflash twrp and install AICP custom rom. So at least I can use the device. I will figure out the fastboot stuff later I guess lol.

mod please remove

mod please remove this thread

oh hell, i've followed every step exactly and got a bootloop. 1922-5 brazilian model. is it because of the last update?
---------- Post added at 07:20 PM ---------- Previous post was at 07:18 PM ----------
and why does my phone show as a moto e4 now????
---------- Post added at 07:26 PM ---------- Previous post was at 07:20 PM ----------
just a thing: i obviously got some backups and i could revert the bootloop by just flashing the stock boot back into the phone.

if you took the update you have to reflash the updated stock firmware after the update. if need be ill walk you through it ive already done it with one person over facebook messenger and after that they were successful. unfortunately they havent commented on saying so lol or thanked the post. sorry for the late reply also i just got off work lol also if links are dead i got dev access on afh now so ill be putting the new links on here ina bit . also tbh i have no clue why it says moto e4 when we put the twrp recovery on but it doesnt affect anything. it would be nice if we had an official twrp
blowingoff said:
oh hell, i've followed every step exactly and got a bootloop. 1922-5 brazilian model. is it because of the last update?
---------- Post added at 07:20 PM ---------- Previous post was at 07:18 PM ----------
and why does my phone show as a moto e4 now????
---------- Post added at 07:26 PM ---------- Previous post was at 07:20 PM ----------
just a thing: i obviously got some backups and i could revert the bootloop by just flashing the stock boot back into the phone.
Click to expand...
Click to collapse

Moto G6 Play XT1922-3
ninjakira said:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards, fires, rigged elections, ligma,
* thermonuclear war, or your mom getting upset with you for being on the computer all day
Please
* Ensure you have an advanced understanding of this device before flashing it! YOU are choosing to make these modifications or your own free will.
*/
I've decided to make a new guide for our jeter devices because the other guide is a little sloppy now lol. I have no problem with having this taking down if the op for the original guide decides to clean theirs up. this one should help clear up stuff now at least lol
This has been confirmed to work on:
XT1922-3 Model
XT1922-4 Model
XT1922-5 Brazilian Model
XT1922-7 Boost Mobile
XT1922-9 Model
Please make backups using TWRP IN CASE OF FAILURE.
Original stock firmware can be found here. https://mirrors.lolinet.com/firmware/moto/jeter/official/
The steps listed in this process WILL wipe your userdata. If you have anything you need to save back it up first.
Prerequisites:
Unlocked bootloader.
ADB/Fastboot installed on your machine ( https://developer.android.com/studio...platform-tools ) If you have issues with commands make sure you have a current build of ADB and fastboot.
Minimal adb/fastboot v1.4.3 installer can be found here. https://androidfilehost.com/?fid=746010030569952951
Step 1.) Download twrp image to the ADB/Fastboot folder on your computer. https://www.androidfilehost.com/?fid=1322778262904017969
Step 2.) Reboot to your bootloader. You can do this by turning on your device and holding power and both volume buttons at the same time.
Step 3.) Once the device reboots to the bootloader type the following from your computer with your phone connected via USB.
Code:
fastboot boot moto-g6-play-jeter-patched-twrp.img
Step 4.) Once TWRP boots from your computer type (it may take a bit to boot because it is trying to decrypt your userdata, but it will fail and prompt for a password. Just click cancel):
Code:
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/boot stockboot.img
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/recovery stockrecovery.img
This will backup your stock boot and recovery images if you to revert to stock later.
Step 5.) Code:
adb reboot bootloader
Step 6.) Run the following command from your computer to install the TWRP image to your device.
Code:
fastboot flash recovery moto-g6-play-jeter-patched-twrp.img
Step 7.) Use the volume keys on the device to select boot to recovery and TWRP will boot up again. When it prompts for a decryption password select cancel again.
Step 8.) From your computer type the following into your command prompt/terminal from your adb/fastboot folder:
Code:
adb shell mount -o,rw /dev/block/platform/soc/7824900.sdhci/by-name/vendor /vendor
Step 9.) Download and extract https://www.androidfilehost.com/?fid=1322778262904017972 this patched fstab.qcom boot image into the ADB/Fastboot folder on your PC.
Step 10.) Run the following command from command prompt/terminal on your computer:
Code:
adb push fstab.qcom /vendor/etc/fstab.qcom
Step 11.) Next click the "Wipe" button in TWRP and slide "Swipe to Factory Reset" THIS WILL WIPE YOUR DATA ON YOUR PHONE. Ensure you have backup.
Step 12.) Download the Magisk Beta 17.2 zip file from https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 to your ADB/Fastboot folder.
Step 13.) Run the following command to push the boot image to your device
Code:
adb push Magisk-v17.2.zip /tmp
This will push the Magisk-v17.2.zip to your /tmp folder
Step 14.) Flash Magisk-v17.2.zip from TWRP using the install option and navigate to the /tmp folder to select it and install it.
Step 15.) Reboot your device
Step 16.) It will say N/A in the top corner of your device for a few seconds. Then it will boot the the Motorola boot screen and you can setup your device as a new phone.
Step 17.) Verify Magisk Manager is installed and the root functionality works. if force encrytion is checked just uncheck it, click install then whatever option magisk recommends then reboot.
step 18.) have fun.
Step 19.)DOWNLOAD STOCK FIRMWARE HERE https://mirrors.lolinet.com/firmware/moto/jeter/official/ UNZIP STOCK FIRMWARE TO YOUR ADB/FASTBOOT FOLDER TO FLASH IT. TO REVERT BACK TO STOCK YOU HAVE TO REFLASH STOCK FIRMWARE FROM THE BOOTLOADER if your device is bootlooped or bricked or not working right you have to reflash the stock firmware your device came with. PLEASE INPUT THESE COMMANDS ONE AT A TIME DO NOT DO THEM ALL AT ONCE. I KNOW ITS A HASSLE BUT IT GUARANTEES A SUCCESSFUL REFLASH. I CANNOT EMPHASIZE THIS ENOUGH
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash oem oem.img
fastboot flash vendor vendor.img
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot flash logo logo.bin
fastboot oem fb_mode_clear
fastboot reboot
if you guys think anything should be edited from this let me know and ill fix it. like im not 100% sure if we still have to use the modified fstabs.qcom i just used it still after i took the update and re-rooted. so if someone can tell me they didnt use the fstabs.qcom and still got the same results please let me know
Credits: @kwiksi1ver for making the original guide. and @topjohnwu for magisk. and @shimp208 for minimal adb/fastboot.
Click to expand...
Click to collapse
It still doesn`t work,i flashed the stock JETER_RETAIL_8.0.0_OPPS27.91-35-3_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml,code by code with fastboot and gpt.bin,bootloader.img and oem.img fail flashing.
What should i do?
Every time i boot the phone normally or into bootloader it says bad key,and i also dont see my baseband anymore.
Help me!

ninjakira said:
if you took the update you have to reflash the updated stock firmware after the update. if need be ill walk you through it ive already done it with one person over facebook messenger and after that they were successful. unfortunately they havent commented on saying so lol or thanked the post. sorry for the late reply also i just got off work lol also if links are dead i got dev access on afh now so ill be putting the new links on here ina bit . also tbh i have no clue why it says moto e4 when we put the twrp recovery on but it doesnt affect anything. it would be nice if we had an official twrp
Click to expand...
Click to collapse
I could imagine it was because we have no official twrp. what do you mean by updated stock image? I'm oj build opp27.91-87.

You sir need to also use this https://mirrors.lolinet.com/firmware/moto/aljeter/official/RETAIL/. Go to step 19 and follow the reflashing stock firmware instructions. Use the most recent firmware. You can tell which one is new by dates
blowingoff said:
I could imagine it was because we have no official twrp. what do you mean by updated stock image? I'm oj build opp27.91-87.
Click to expand...
Click to collapse

ninjakira said:
You sir need to also use this https://mirrors.lolinet.com/firmware/moto/aljeter/official/RETAIL/. Go to step 19 and follow the reflashing stock firmware instructions. Use the most recent firmware. You can tell which one is new by dates
Click to expand...
Click to collapse
mine is the brazilian one, xt1922-5. the downloads are for the 1922-2. can i use it?
---------- Post added at 05:49 PM ---------- Previous post was at 05:45 PM ----------
oh, I think you didn't understand me. I've already reverted the bootloop, my phone is working. but if I flash magisk, it goes to bootloop

I just got off the phone with Moto they confirm your device is also the aljeter so those firmwares should work for you.
blowingoff said:
mine is the brazilian one, xt1922-5. the downloads are for the 1922-2. can i use it?
---------- Post added at 05:49 PM ---------- Previous post was at 05:45 PM ----------
oh, I think you didn't understand me. I've already reverted the bootloop, my phone is working. but if I flash magisk, it goes to bootloop
Click to expand...
Click to collapse

ninjakira said:
I just got off the phone with Moto they confirm your device is also the aljeter so those firmwares should work for you.
Click to expand...
Click to collapse
great. so i'll flash the firmware and try to root from it
---------- Post added at 06:40 PM ---------- Previous post was at 06:25 PM ----------
well. i got an update. I just flash magisk with no modified boot image, no fstab.qcom and such. just flash twrp and then magisk.
phone rooted, safetynet passed. wow!!!!!!!!!!

blowingoff said:
great. so i'll flash the firmware and try to root from it
---------- Post added at 06:40 PM ---------- Previous post was at 06:25 PM ----------
well. i got an update. I just flash magisk with no modified boot image, no fstab.qcom and such. just flash twrp and then magisk.
phone rooted, safetynet passed. wow!!!!!!!!!!
Click to expand...
Click to collapse
Awesome you just helped confirm a couple things on my end to lol like the fstabs.qcom. I'm glad I could be of assistance to you and I'm glad the guide worked. I'll be removing the fstabs.qcom link since they are no longer needed now

I'm pretty sure there's already a Jeter root guide. What's the point in creating a new one?

Dadud said:
I'm pretty sure there's already a Jeter root guide. What's the point in creating a new one?
Click to expand...
Click to collapse
The other one was confusing people, and starting to cause more harm than anything. I've already helped a couple people in bootloop that tried to use the old guide and couldn't.

ninjakira said:
The other one was confusing people, and starting to cause more harm than anything. I've already helped a couple people in bootloop that tried to use the old guide and couldn't.
Click to expand...
Click to collapse
Seems like those people weren't following the the guide TO A T (very important) /skimming thinking it works the old way. I've seen those types of people all over these forums. You're adding more unnecessary clutter to these already cluttered and poorly moderated forums. I'm also pretty sure you don't have permission from kwiksilver to use his files

I've already talked to a mod about this there looking Into it and trust me man I literally have gone on rants to the people about not skimming before I helped fox there devices. I'm just trying to help everyone the best way I can think of all at once. People before the OTA and after no longer need a patched boot.img because the latest magisk does it. Furthermore we don't need the patched fstabs.qcom as I've recently learned. The device can be unencrypted without all that now thanks to magisk. I've already also told quiksi1ver I'm willing to have mine taking down if he cleans his up and updates it.also a couple devices like the xt1922-3 and 5 are aljeter not Jeter but it seems the xt1922-5 still apply to this guide.
Dadud said:
Seems like those people weren't following the the guide TO A T (very important) /skimming thinking it works the old way. I've seen those types of people all over these forums. You're adding more unnecessary clutter to these already cluttered and poorly moderated forums.
Click to expand...
Click to collapse

Also in my post I put the link for the stock firmware along with the proper adb commands to flash said stock firmware from bootloader which ALOT of people also need

lol this thread is much clearer than the earliest. and also: i've followed the steps from the original thread but i got no response from anyone there. hehhe

blowingoff said:
lol this thread is much clearer than the earliest. and also: i've followed the steps from the original thread but i got no response from anyone there. hehhe
Click to expand...
Click to collapse
Thank you for that lol I just wanna actually try to help out our fellow g6 play users lol

Thanks for creating this new thread, it really is cleaner than before.
Got it working on XT1922-5, brazilian model. Managed to get root and everything is working fine.
But just for curiosity, is there a way to revert it to stock with locked bootloader at all? Already flashed stock rom, my only problem is not being able to relock it.
Hope to see some new roms coming for our device soon!

AcTSkull said:
Thanks for creating this new thread, it really is cleaner than before.
Got it working on XT1922-5, brazilian model. Managed to get root and everything is working fine.
But just for curiosity, is there a way to revert it to stock with locked bootloader at all? Already flashed stock rom, my only problem is not being able to relock it.
Hope to see some new roms coming for our device soon!
Click to expand...
Click to collapse
Removed commands for bootloader relock because they don't work ignore this post

ninjakira said:
I personally have not used this yet to relock my bootloader so I cannot say 100% this will work. So please don't get mad at me if not. If it works for you please let me know and I'll add it to the post
Click to expand...
Click to collapse
Of course not! We are all here to learn, share and have fun with it.
Anyway, it didn't work. Still boots up with the Bad Key at the top and grayed out "unlocked oem" at developer options.
Let's wait and see if (when available around here, not OTA) flashing a new firmware will fix it, perhaps, as it updates the version to 27.91-147 (will confirm it later).