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.

Bootloop after hardreset after forgot lock pattern, HELP

hi.; title says all. i forgot the lock pattern, and then i got to the google log in screen. i kept logging in but there was no internet so it would not move forward.
then i pressed home and vol down to hard reset. it took me to the twrp recovery/.
there i went to wipe and reset menu and reset, everything. even system, dalvik, data.
now it is in lg boot loop. i cant do anything.
i have tried again to reset but only data and dalvik and still boot loop.
IMPORTANT NOTE, MY PHONE IS D800, it has cloudy rom before this bootloop and working fine. it showed D802 in about phone but removing cover shows D800.
what to do? i dont want to go to stock because i have all my images and videos in this also contacts. pls help

What about download mode work or no
---------- Post added at 12:11 PM ---------- Previous post was at 12:09 PM ----------
U have boot loop because u wipe system

amin44 said:
What about download mode work or no
---------- Post added at 12:11 PM ---------- Previous post was at 12:09 PM ----------
U have boot loop because u wipe system
Click to expand...
Click to collapse
yes i can go to download mode. im actually downloading the stock rom, but still if anyone can help and tell me any solution other than stock rom, that would be helpful a lot because i have got a lot of important family photos and also some personal documents in this which i dont want to lose
PS: in download mode it even shows ROOTED in bottom. any solution?

To remove "rooted" flash tot mothed. Can u enter twrp

amin44 said:
To remove "rooted" flash tot mothed. Can u enter twrp
Click to expand...
Click to collapse
yes i can enter twrp, when i press vol down and power, it asks me to press power again to confirm to reset and then takes me to twrp. i dont want tot, that is my last resort. i want anyother solution if possible.

Do u have ROM zip in sdcard

amin44 said:
Do u have ROM zip in sdcard
Click to expand...
Click to collapse
i wish i had it.... and it was just last week i removed the back up from mobile as well ...

There is way to flash ROM zip via PC usbdisc for PC just search in Google and for USB u need otg cable
---------- Post added at 12:28 PM ---------- Previous post was at 12:25 PM ----------
I will try to give u YouTube video

amin44 said:
There is way to flash ROM zip via PC usbdisc for PC just search in Google and for USB u need otg cable
---------- Post added at 12:28 PM ---------- Previous post was at 12:25 PM ----------
I will try to give u YouTube video
Click to expand...
Click to collapse
that will be helpful. also can u tell if i can save my images and files in this state? i think its impossible but still anyway?

i dont know . see this https://www.youtube.com/watch?v=YP1LVOKgwQM

aami.aami said:
hi.; title says all. i forgot the lock pattern, and then i got to the google log in screen. i kept logging in but there was no internet so it would not move forward.
then i pressed home and vol down to hard reset. it took me to the twrp recovery/.
there i went to wipe and reset menu and reset, everything. even system, dalvik, data.
now it is in lg boot loop. i cant do anything.
i have tried again to reset but only data and dalvik and still boot loop.
IMPORTANT NOTE, MY PHONE IS D800, it has cloudy rom before this bootloop and working fine. it showed D802 in about phone but removing cover shows D800.
what to do? i dont want to go to stock because i have all my images and videos in this also contacts. pls help
Click to expand...
Click to collapse
You can also use adb sideload to flash the ROM. Install kouch universal adb drivers and download minimal adb and fastboot both can be downloaded from a Google search. Then on your phone go to twrp advanced and adb sideload. Then put the ROM.zip folder in the minimal adb and fastboot folder. Then hold shift right click and press run command line here. Type "adb devices" if it finds your device then use this command "adb sideload *ROMNAME.ZIP*. Replace * and ROM name with the proper name of your zip file.
Sent from my LG-D800 using Tapatalk

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

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.

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