Database Users

[Q] How to flash a ROM through twrp adb sideload?

I flashed 1.2.5 Malladus on 12B OTA rooted for Verizon using twrp 2.6.3.3. When I booted the LG logo appears for a second and the screen turns black. Reading from a previous post Malladus wont boot if you're on 12B OTA. I can't boot my phone flashing this rom. I would like to adb sideload through twrp. I don't want to mess phone up to brick I'm a noob I don't have adb tools on my computer I wouldn't know where to place them.
Please help me with a step by step.
Thank you

atticustcx said:
I flashed 1.2.5 Malladus on 12B OTA rooted for Verizon using twrp 2.6.3.3. When I booted the LG logo appears for a second and the screen turns black. Reading from a previous post Malladus wont boot if you're on 12B OTA. I can't boot my phone flashing this rom. I would like to adb sideload through twrp. I don't want to mess phone up to brick I'm a noob I don't have adb tools on my computer I wouldn't know where to place them.
Please help me with a step by step.
Thank you
Click to expand...
Click to collapse
Hey man here's a link;
http://teamw.in/ADBSideload
If you need more help let me know..
.make sure that your enviromentals are set too so your PC can understand commands

RubbleTea said:
Hey man here's a link;
http://teamw.in/ADBSideload
If you need more help let me know..
.make sure that your enviromentals are set too so your PC can understand commands
Click to expand...
Click to collapse
I'm having trouble installing adb i'm following this guy I installed adb but when I open device manager I don't see adb.exe or fastboot in C:\Windows

atticustcx said:
I'm having trouble installing adb i'm following this guy I installed adb but when I open device manager I don't see adb.exe or fastboot in C:\Windows
Click to expand...
Click to collapse
OK hey so you have adb all set up and set in enviromentals right? And you have a ROM ready? And drivers installed? For ease of doing things rename the ROM "ROM" so it should be ROM.zip
---------- Post added at 12:10 PM ---------- Previous post was at 12:00 PM ----------
Once you have that done place the rom into the same folder as your adb.exe is.......now plug in your phone to PC a and have recovery open.....then go to advanced the click sideload ROM....then swipe....
..now open a command prompt...then type adb devices to heck if your device is shown....if it is go ahead and type" adb sideload ROM.zip" ...then wait til it finishes...then unplug from PC and flash the ROM.......if your driver won't show your device try koush universal drivers....sorry man I'm at work now

I had a similar issue and I was able to flash clean rom but I still reboot to twrp. Do I need to flash a boot image or something.?
from my Note Thrizzle

RubbleTea said:
OK hey so you have adb all set up and set in enviromentals right? And you have a ROM ready? And drivers installed? For ease of doing things rename the ROM "ROM" so it should be ROM.zip
---------- Post added at 12:10 PM ---------- Previous post was at 12:00 PM ----------
Once you have that done place the rom into the same folder as your adb.exe is.......now plug in your phone to PC a and have recovery open.....then go to advanced the click sideload ROM....then swipe....
..now open a command prompt...then type adb devices to heck if your device is shown....if it is go ahead and type" adb sideload ROM.zip" ...then wait til it finishes...then unplug from PC and flash the ROM.......if your driver won't show your device try koush universal drivers....sorry man I'm at work now
Click to expand...
Click to collapse
I don't have adb installed and environmentals. I don't have a ROM ready because I'm not sure which one is safe to flash over 12B OTA.
I only have LG drivers 2.11.1.0 installed. Every time I connect my phone it says to install drivers but it can't find VS980 drivers and says unsuccessful install

atticustcx said:
I don't have adb installed and environmentals. I don't have a ROM ready because I'm not sure which one is safe to flash over 12B OTA.
I only have LG drivers 2.11.1.0 installed. Every time I connect my phone it says to install drivers but it can't find VS980 drivers and says unsuccessful install
Click to expand...
Click to collapse
Try downloading a stock ROM with the ota should be one, and download koush universal drivers anyway.....for adb android SDK will have it and have instructions to setup....Google will help.....environment settings will make it so your computer understands adb commands...
---------- Post added at 01:39 PM ---------- Previous post was at 01:37 PM ----------
rawb123456 said:
I had a similar issue and I was able to flash clean rom but I still reboot to twrp. Do I need to flash a boot image or something.?
from my Note Thrizzle
Click to expand...
Click to collapse
So you flash a ROM and it goes to twrp, did you accept the ota with a custom recovery? For you might have to flash to stock image(there's a thread in general forum) but first try another rom

RubbleTea said:
Try downloading a stock ROM with the ota should be one, and download koush universal drivers anyway.....for adb android SDK will have it and have instructions to setup....Google will help.....environment settings will make it so your computer understands adb commands...
---------- Post added at 01:39 PM ---------- Previous post was at 01:37 PM ----------
So you flash a ROM and it goes to twrp, did you accept the ota with a custom recovery? For you might have to flash to stock image(there's a thread in general forum) but first try another rom
Click to expand...
Click to collapse
After trying for hours to get my drivers installed so my phone can be read by computer I gave up. I followed this http://forum.xda-developers.com/showthread.php?t=2448960 took my phone back to stock on 11A.

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

Root Kernel HD8 5.3.2 (2016)

Other question.
Can anyone Post rooted Boot.img for 8hd 6th. One of the Last working Firmware versions.
Will try to Boot insecure using this Boot.img
http://whiteboard.ping.se/Android/Rooting
Thx

And then if booted insecure Flash root.

Attached is the insecure boot image for HD 8 5.3.2.
Please use one of this tutorials to gain root.
http://whiteboard.ping.se/Android/Rooting
http://android.stackexchange.com/questions/18606/create-my-own-boot-img-for-rooting
-------------------
Next, type fastboot devices into the command prompt you opened earlier, and check that your phone is in the list.
Now we have to soft-boot an insecure boot image by typing
fastboot boot boot.img
When the phone has rebooted, open settings, and go to Settings -> Applications -> Development and check in the USB debbuging option.
Now execute all of these following commands, after each other, in the command prompt:
adb root
adb remount
adb push su /system/bin
adb push Superuser.apk /system/app
adb shell chmod 06755 /system/bin/su
adb shell chmod 06755 /system/app/Superuser.apk
Now your device should be rooted and ready.
Credits to the above mentioned link authors.

As an alternative:
unpack firmware using 7zip
exchange boot.img.
repack
install
proceed according above mentioned instructions

[deleted]

HD 8 - 5.3.2
Root Kernel fir HD 8 - 5.3.2 (2016 )
extract using 7z
rename to boot.img
proceed as above
Alternatively you can put the in the original Update Firmware and Flash this according to brick Recovery instruction

thebrainkafka said:
Root Kernel fir HD 8 - 5.3.2 (2016 )
extract using 7z
rename to boot.img
proceed as above
Alternatively you can put the in the original Update Firmware and Flash this according to brick Recovery instruction
Click to expand...
Click to collapse
This method will not work as the boot loader is factory locked.

new kernel inkluding adb insecure

dokihara said:
This method will not work as the boot loader is factory locked.
Click to expand...
Click to collapse
why. you are not flashing the kernel. just loading it in fastboot.

Will not work, you can't fastboot into boot.img on locked hardware. So quit posting your boot image.

Hi! I just received a Fire 8 HD (2016) 32GB model yesterday, and have successfully gotten the Google Play store on it so far. I updated over night to 5.3.2. Is this kernel being posted supposed to allow root? Just a little confused about it...

Will not work. Fastboot using boot.img does not work on locked hardware. Period.

shawnchalfant said:
Will not work, you can't fastboot into boot.img on locked hardware. So quit posting your boot image.
Click to expand...
Click to collapse
Bad luck

No bad luck, locked down hardware!

Do you know if fastboot allows flashing Update.zips ?

Yes, only SIGNed update packages. Signature verification is enforced.

shawnchalfant said:
Yes, only SIGNed update packages. Signature verification is enforced.
Click to expand...
Click to collapse
Where to get the Keys?
How to sign?
I have donloaded the source. Are the Keys in there?

NO!
---------- Post added at 09:10 PM ---------- Previous post was at 09:08 PM ----------
Give up, doubt you understand what you are doing, Asking a question like that gives us a window to your knowledge.

shawnchalfant said:
NO!
---------- Post added at 09:10 PM ---------- Previous post was at 09:08 PM ----------
Give up, doubt you understand what you are doing, Asking a question like that gives us a window to your knowledge.
Click to expand...
Click to collapse
Stop spaming noob or are you the super Moderator here. Havent read any idea or hint from you so far

Silent
---------- Post added at 11:53 PM ---------- Previous post was at 11:41 PM ----------
I'm not spamming, just look at the facts. Locked bootloader, no custom recovery at this point and signature verification enforced. Root not possible yet. Lack of interest in forums, look at last year's model, nothing other than root and Google Play Store. Go over to Fire 7 page. Custom recovery, CM and Nexus roms available.

Any new update about new BlankFlash?

as you guys know June update killed a lot of athenes and same thing happened with my athene. and the BlankFlash is also not working after this update. so is there any update for blankFlash, post a link here.

no updated blankflash ... we should wait la
:crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:
siddhesh9146 said:
as you guys know June update killed a lot of athenes and same thing happened with my athene. and the BlankFlash is also not working after this update. so is there any update for blankFlash, post a link here.
Click to expand...
Click to collapse
sad..... my athne toooooo dead .... we should hope get updated soon... most of moto g4 plus athene dead ...... i dont who gonna make new updated blankflash to recover....... thanks in advance who make new one..... or any other solution... already a post is here but it didnot work out at allll..... pls someone geeks solve this
...... ISSUES LOTS OF MOTO G4 PLUS DEADDD..... EVERYTHING TRIED NO LUCK[ATHENE]XT1643]:crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:

tamil2692 said:
:crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:
sad..... my athne toooooo dead .... we should hope get updated soon... most of moto g4 plus athene dead ...... i dont who gonna make new updated blankflash to recover....... thanks in advance who make new one..... or any other solution... already a post is here but it didnot work out at allll..... pls someone geeks solve this
...... ISSUES LOTS OF MOTO G4 PLUS DEADDD..... EVERYTHING TRIED NO LUCK[ATHENE]XT1643]:crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
Nothin

new blankflash HERE : https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761

Does not enter recovery or boot up system
as soon as the blankflash file is updated i flashed it and worked
then i flashed updated gpt and bootloader
then i tried to enter recovery mode but its not entering
and also when i unplug usb cable it is turning off
then i flashed stock rom
but still recovery and system booting are not working,enters only to fastboot that too on charging.
guyss please help me it means a lot to me.Thanks in advance

Geek_manoj said:
as soon as the blankflash file is updated i flashed it and worked
then i flashed updated gpt and bootloader
then i tried to enter recovery mode but its not entering
and also when i unplug usb cable it is turning off
then i flashed stock rom
but still recovery and system booting are not working,enters only to fastboot that too on charging.
guyss please help me it means a lot to me.Thanks in advance
Click to expand...
Click to collapse
Are you mentioning that your device only boots to fastboot now? If you press 'start', does that boot to system or not?
Which stock ROM did you flash, and can you confirm if the flash worked? How did your device brick in the first place?

echo92 said:
Are you mentioning that your device only boots to fastboot now? If you press 'start', does that boot to system or not?
Which stock ROM did you flash, and can you confirm if the flash worked? How did your device brick in the first place?
Click to expand...
Click to collapse
he didn't flashed stock rom yet, he is only trying to flash custom roms zips from recovery. someone please him that this won't work in this case:cyclops:

Blank Flash Files Moto G4 Plus
Yes I have the correct blank flash files for Moto G4 Plus. I was used it on my device XT1643 and it is working.

echo92 said:
Are you mentioning that your device only boots to fastboot now? If you press 'start', does that boot to system or not?
Which stock ROM did you flash, and can you confirm if the flash worked? How did your device brick in the first place?
Click to expand...
Click to collapse
yes,the device boots only to fastboot that too only when charged.if i press start that doesn't boot to system.I flashed "ATHENE_NPJS25.93-14-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip".I bricked by doing softare update after reflashing stock rom.it also doesnt enter recovery
---------- Post added at 02:09 AM ---------- Previous post was at 02:05 AM ----------
siddhesh9146 said:
he didn't flashed stock rom yet, he is only trying to flash custom roms zips from recovery. someone please him that this won't work in this case:cyclops:
Click to expand...
Click to collapse
sorry if you dont understand.but i flash stock rom "ATHENE_NPJS25.93-14-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" in stock recovery.if u could help me please let me know.thanks in advance

Geek_manoj said:
yes,the device boots only to fastboot that too only when charged.if i press start that doesn't boot to system.I flashed "ATHENE_NPJS25.93-14-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip".I bricked by doing softare update after reflashing stock rom.it also doesnt enter recovery
---------- Post added at 02:09 AM ---------- Previous post was at 02:05 AM ----------
sorry if you dont understand.but i flash stock rom "ATHENE_NPJS25.93-14-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" in stock recovery.if u could help me please let me know.thanks in advance
Click to expand...
Click to collapse
I knew that, that file was for flashing in fastboot mode
but you flashed in recovery

Geek_manoj said:
yes,the device boots only to fastboot that too only when charged.if i press start that doesn't boot to system.I flashed "ATHENE_NPJS25.93-14-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip".I bricked by doing softare update after reflashing stock rom.it also doesnt enter recovery
---------- Post added at 02:09 AM ---------- Previous post was at 02:05 AM ----------
sorry if you dont understand.but i flash stock rom "ATHENE_NPJS25.93-14-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" in stock recovery.if u could help me please let me know.thanks in advance
Click to expand...
Click to collapse
As siddhesh9146 had mentioned, the Athene stock ROM cannot be flashed in stock recovery, it is not a flashable zip file. You need a computer and ADB set up, extract the zip on your computer and use the flashing commands in the fastboot ROM thread to flash a stock ROM.
Until you've flashed the stock ROM, I'm not even sure if you have stock recovery, or a stock system on your device. The supplied blank flash does not appear to have a functioning recovery included with it.

echo92 said:
As siddhesh9146 had mentioned, the Athene stock ROM cannot be flashed in stock recovery, it is not a flashable zip file. You need a computer and ADB set up, extract the zip on your computer and use the flashing commands in the fastboot ROM thread to flash a stock ROM.
Until you've flashed the stock ROM, I'm not even sure if you have stock recovery, or a stock system on your device. The supplied blank flash does not appear to have a functioning recovery included with it.
Click to expand...
Click to collapse
I m sorry.I must have described in a better way.I actually mean that i used computer extracted the firmware and then i ran oem_flash,which is the actual way i suppouse in fastboot mode(i ommited for fastboot as stock recovery in previous post,sorry).but i dont know why it still doesnt enter recovery or enter into system or work without plug.i even tried flashing updated gpt.bin and bootloader files again followed by the rom,but noting happened
---------- Post added at 04:24 PM ---------- Previous post was at 04:19 PM ----------
echo92 said:
As siddhesh9146 had mentioned, the Athene stock ROM cannot be flashed in stock recovery, it is not a flashable zip file. You need a computer and ADB set up, extract the zip on your computer and use the flashing commands in the fastboot ROM thread to flash a stock ROM.
Until you've flashed the stock ROM, I'm not even sure if you have stock recovery, or a stock system on your device. The supplied blank flash does not appear to have a functioning recovery included with it.
Click to expand...
Click to collapse
siddhesh9146 said:
I knew that, that file was for flashing in fastboot mode
but you flashed in recovery
Click to expand...
Click to collapse
hey,i ommited in the post telling that i did it in recovery(sorry for that)actually it doesnt enter recovery,which i already mentioned.thanks for being concerned

Geek_manoj said:
I m sorry.I must have described in a better way.I actually mean that i used computer extracted the firmware and then i ran oem_flash,which is the actual way i suppouse in fastboot mode(i ommited for fastboot as stock recovery in previous post,sorry).but i dont know why it still doesnt enter recovery or enter into system or work without plug.i even tried flashing updated gpt.bin and bootloader files again followed by the rom,but noting happened
---------- Post added at 04:24 PM ---------- Previous post was at 04:19 PM ----------
hey,i ommited in the post telling that i did it in recovery(sorry for that)actually it doesnt enter recovery,which i already mentioned.thanks for being concerned
Click to expand...
Click to collapse
So, you booted your device to the bootloader screen (not to recovery), connected your device to your computer, and you've flashed using the OEM_flash script, and yet you're unable to reboot to recovery?
Sounds like your stock ROM flash did not work the first time, leaving you without a recovery or a system. Try the following just to confirm:
1) Ensure your adb folder contains the extracted NPJS25.93-14-8 stock ROM (all the files), should be about 2 GB for the stock ROM. Also confirm that the OEM flash script is in the same location (so your adb folder should have the stock ROM, the flash script and the adb and fastboot.exe and adb.dlls)
2)Reboot your device to the bootloader (power down, then press the power and volume down keys to boot to bootloader) and connect your device to your computer.
3)In the adb terminal, type 'fastboot devices', without the quotes. If communicating, you should see your device respond with its serial number.
4)If communicating, run the OEM flash script again.
5)If your device does not boot properly, then reboot to bootloader.
5a)Copy each of the commands from the script (you can open the script in a text editor) and paste them in the adb terminal window and run each one by pressing Enter on your keyboard. You should see the command report [OKAY] if it's flashed. Any errors, let us know, that might point more accurately to what might be going on.
As an aside, this is one of the reasons why downgrading isn't a good idea....

echo92 said:
So, you booted your device to the bootloader screen (not to recovery), connected your device to your computer, and you've flashed using the OEM_flash script, and yet you're unable to reboot to recovery?
Sounds like your stock ROM flash did not work the first time, leaving you without a recovery or a system. Try the following just to confirm:
1) Ensure your adb folder contains the extracted NPJS25.93-14-8 stock ROM (all the files), should be about 2 GB for the stock ROM. Also confirm that the OEM flash script is in the same location (so your adb folder should have the stock ROM, the flash script and the adb and fastboot.exe and adb.dlls)
2)Reboot your device to the bootloader (power down, then press the power and volume down keys to boot to bootloader) and connect your device to your computer.
3)In the adb terminal, type 'fastboot devices', without the quotes. If communicating, you should see your device respond with its serial number.
4)If communicating, run the OEM flash script again.
5)If your device does not boot properly, then reboot to bootloader.
5a)Copy each of the commands from the script (you can open the script in a text editor) and paste them in the adb terminal window and run each one by pressing Enter on your keyboard. You should see the command report [OKAY] if it's flashed. Any errors, let us know, that might point more accurately to what might be going on.
As an aside, this is one of the reasons why downgrading isn't a good idea....
Click to expand...
Click to collapse
Hey,thanks for bothering.But,it didnt work.i have got no error.But still mobile enters only fastboot that too when charging( only fastboot again).

I tried to clear cache memory by booting my g4 plus in recovery mode. the phone hanged up and switched off now unable to boot. tried the blank flash file to update but the same is not working. Can any one help !!

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).