Database Users

Need help with WiFi Xoom partial brick

Basically last year I was unlocked and rooted...I went back stock when ICS first dropped and havent been rooted since. However, I can't relock my device. I was trying to watch a movie i rented from the Play Store and kept getting "error fetching licence". So I assumed that even though I was able to get my OTA official from Google for Jellybean direct from Google while Unlocked that the cause was DRM and i needed to relock my device. I did just that (locked Xoom) and now I am stuck at Motorola symbol. I get that red linux error..Well i used to until I tried the FIRST Root My Xoom.
I have been in ADB all day and last-night and can not get it do anything other than lock and unlock over and over again and neither does anything. So I decided to say screw it if it's easier just to root and flash a custom ROM because I NEED my tablet ASAP.
I tried EASY ADB and I can control the reboots and put it in fastboot and all that. I get an error when attepting to flash recovery through ADB "error: cannot load 'recovery-Tiamat-R4c-10061-1150-cwm.img" : No Error
I guess it can't read the SD because no ROM is there. I suppose the OTA is just an update to the last version and not the full ROM maybe so when I locked it that caused it to wipe and there's nothing there to restore from and that caused my loop.
Now what I need from you guys is a possible ONE CLICK option. Tried searching the forum and one guys lAIOS thingy I can't figure out for anything. The other one click was deleted by the OP..I really need help and I appreciate anyone that can point me because the last 14hrs of ADB is driving me insane.
THANK YOU IN ADVANCE!!!!!!!!!!!
UPDATE
I was able to get em all set. Up and running 4.2 now. I guess a MOD can delete this or close it now.

Flash Stock image
Your best bet is to flash back to a stock image (which will basically be Honeycomb). Download the correct img from your model and use the instructions from this site:
rootzwiki.com/topic/1586-stock-images
On your computer running ADB use the following commands
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot erase userdata (if no img in zip)
(Warning: If you have an external SD card, remove it. This will save you a lot of headache. I found that Stock Honeycomb would not update with a external SD card inside). Once you get Honeycomb successfully on, you can use OTA to update til you get to Jellybean (if you have the Wifi Model, or ICS if you have a 4G model).
Good Luck
Freshly_Snipes said:
Basically last year I was unlocked and rooted...I went back stock when ICS first dropped and havent been rooted since. However, I can't relock my device. I was trying to watch a movie i rented from the Play Store and kept getting "error fetching licence". So I assumed that even though I was able to get my OTA official from Google for Jellybean direct from Google while Unlocked that the cause was DRM and i needed to relock my device. I did just that (locked Xoom) and now I am stuck at Motorola symbol. I get that red linux error..Well i used to until I tried the FIRST Root My Xoom.
I have been in ADB all day and last-night and can not get it do anything other than lock and unlock over and over again and neither does anything. So I decided to say screw it if it's easier just to root and flash a custom ROM because I NEED my tablet ASAP.
I tried EASY ADB and I can control the reboots and put it in fastboot and all that. I get an error when attepting to flash recovery through ADB "error: cannot load 'recovery-Tiamat-R4c-10061-1150-cwm.img" : No Error
I guess it can't read the SD because no ROM is there. I suppose the OTA is just an update to the last version and not the full ROM maybe so when I locked it that caused it to wipe and there's nothing there to restore from and that caused my loop.
Now what I need from you guys is a possible ONE CLICK option. Tried searching the forum and one guys lAIOS thingy I can't figure out for anything. The other one click was deleted by the OP..I really need help and I appreciate anyone that can point me because the last 14hrs of ADB is driving me insane.
THANK YOU IN ADVANCE!!!!!!!!!!!
UPDATE
I was able to get em all set. Up and running 4.2 now. I guess a MOD can delete this or close it now.
Click to expand...
Click to collapse
---------- Post added at 04:38 PM ---------- Previous post was at 04:18 PM ----------
Wanted to add, there are 2 methods of flashing imgs to you your machine.
You can flash from the tablet using recovery, or you can flash from a another machine running the Android development kit. My post uses the second method, so it should not matter which recovery image is on your machine.

johnsry said:
Your best bet is to flash back to a stock image (which will basically be Honeycomb). Download the correct img from your model and use the instructions from this site:
rootzwiki.com/topic/1586-stock-images
On your computer running ADB use the following commands
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot erase userdata (if no img in zip)
(Warning: If you have an external SD card, remove it. This will save you a lot of headache. I found that Stock Honeycomb would not update with a external SD card inside). Once you get Honeycomb successfully on, you can use OTA to update til you get to Jellybean (if you have the Wifi Model, or ICS if you have a 4G model).
Good Luck
---------- Post added at 04:38 PM ---------- Previous post was at 04:18 PM ----------
Wanted to add, there are 2 methods of flashing imgs to you your machine.
You can flash from the tablet using recovery, or you can flash from a another machine running the Android development kit. My post uses the second method, so it should not matter which recovery image is on your machine.
Click to expand...
Click to collapse
You must have missed the update at the bottom of the post. I got it to go now. Thank you though so much for offering help.
Sent from my Nexus 4 using Tapatalk 2

[ZE500KL] Can't load invalid boot image!

Hello,
I tried to root my Zenfone 2 ZE500KL but i didn't see that the method don't work with Android 6. Now, when I start my phone i have the message "ERROR: Can't load invalid boot image" with the ASUS Logo.
I tried a lot of things using ADB, like go to the recovery mode for format, installing from the ROM again from my SD. But the message stay...
I need your help now, car I don't find anything... Thanks !

CzeroXCI said:
Hello,
I tried to root my Zenfone 2 ZE500KL but i didn't see that the method don't work with Android 6. Now, when I start my phone i have the message "ERROR: Can't load invalid boot image" with the ASUS Logo.
I tried a lot of things using ADB, like go to the recovery mode for format, installing from the ROM again from my SD. But the message stay...
I need your help now, car I don't find anything... Thanks !
Click to expand...
Click to collapse
Download this boot.img for Marshmallow v.13.10.7.1
https://drive.google.com/file/d/0B7F3ZXr565GkV2N3WjBoeEZXUUU/view?usp=drivesdk
The command from fasboot mode:
fastboot flash boot boot.img

Muminek111 said:
Download this boot.img for Marshmallow v.13.10.7.1
https://drive.google.com/file/d/0B7F3ZXr565GkV2N3WjBoeEZXUUU/view?usp=drivesdk
The command from fasboot mode:
fastboot flash boot boot.img
Click to expand...
Click to collapse
My phone version is 13.10.10.34 can I flash this boot image????

Sharashchandra said:
My phone version is 13.10.10.34 can I flash this boot image????
Click to expand...
Click to collapse
You need to boot.img from stock rom v 13.10.10.34.
Stock rom you can download from Asus website and then extract boot.img from this stock rom.

Sharashchandra said:
My phone version is 13.10.10.34 can I flash this boot image????
Click to expand...
Click to collapse
Plz help I used twrp v2.8.7.7seven max then
Its booted and showing in modified partition.ileave it as it is and I just backup the system but after backup when I press reboot system it will just freezed .then manually I switched on its showing "ERROR: Can't load invali boot image" two phones are under same condition plz help me its my friends phone.
Help me as fast as possible
---------- Post added at 01:13 PM ---------- Previous post was at 01:11 PM ----------
Muminek111 said:
You need to boot.img from stock rom v 13.10.10.34.
Stock rom you can download from Asus website and then extract boot.img from this stock rom.
Click to expand...
Click to collapse
Plz help I used twrp v2.8.7.7seven max then
Its booted and showing in modified partition.ileave it as it is and I just backup the system but after backup when I press reboot system it will just freezed .then manually I switched on its showing "ERROR: Can't load invali boot image" two phones are under same condition plz help me its my friends phone.
Help me as fast as possible

Sharashchandra said:
Plz help I used twrp v2.8.7.7seven max then
Its booted and showing in modified partition.ileave it as it is and I just backup the system but after backup when I press reboot system it will just freezed .then manually I switched on its showing "ERROR: Can't load invali boot image" two phones are under same condition plz help me its my friends phone.
Help me as fast as possible
---------- Post added at 01:13 PM ---------- Previous post was at 01:11 PM ----------
Plz help I used twrp v2.8.7.7seven max then
Its booted and showing in modified partition.ileave it as it is and I just backup the system but after backup when I press reboot system it will just freezed .then manually I switched on its showing "ERROR: Can't load invali boot image" two phones are under same condition plz help me its my friends phone.
Help me as fast as possible
Click to expand...
Click to collapse
I don't understand what your problem.
For Marshmallow use this TWRP.
https://drive.google.com/file/d/0B7F3ZXr565GkY28yUjhfRkd5MUk/view?usp=drivesdk
Another possibility how to fix your phone is flash stock rom from stock recovery. It's the easiest way.

Muminek111 said:
I don't understand what your problem.
For Marshmallow use this TWRP.
https://drive.google.com/file/d/0B7F3ZXr565GkY28yUjhfRkd5MUk/view?usp=drivesdk
Another possibility how to fix your phone is flash stock rom from stock recovery. It's the easiest way.
Click to expand...
Click to collapse
After flashing also the same problem persists
Thankyou

Sharashchandra said:
After flashing also the same problem persists
Thankyou
Click to expand...
Click to collapse
Do you tried to flash Asus stock rom v.13.10.10.34(1.4gb) from Asus stock recovery v.13.10.10 34. I don't mean flash from TWRP.

Hello M having ASUS ZenFone 2 laser ze550kl model with marshmallow version.. I tried to unlock boot loader but m unable to do so.. Please help me..

just flash this zip https://yadi.sk/d/0NFnYyTG36XzWv using TWRP recovery(in menu "install").
just flash this..
it works perfectly fine

make sure you use the latest TWRP for your device.

Hey bro you can watch this video and follow the steps then your phone will definitely right back.....
https://youtu.be/_Ca10N-XQJk

I have also this problem .
But i can't enter in the recovery menu , it doesn't work.
P.S. sorry for my english

Muminek111 said:
Do you tried to flash Asus stock rom v.13.10.10.34(1.4gb) from Asus stock recovery v.13.10.10 34. I don't mean flash from TWRP.
Click to expand...
Click to collapse
Well, i can feel some doubt in your post...but h*ll yeah! I'm currently facing the same problem; where flashing stock rom, downloaded from their site, using their stock recovery, adb, and adb sideload....
the rom flashes successfully, but still boots with the same error...To be frank, i'm fed up...and almost about giving up on this phone...
-i believe i'll give it another shot this very night, trying different methods...funny ones though; if and when they work, i will definitely update my post again... my phone version is Z00ED, in case anybody cares to know -
UPDATE:
=======
Aaaaaanyway, I downloaded 2 kinds of stock roms from the Asus official site;
1. UL-ASUS_Z00E-WW-13.1010.1612.53-user (the latest:- M) and...
2. UL-ASUS_Z00E-WW-12.8.5.222-user (and older version:- actually, the pre-installed version)
after flashing the first one over and over again; after and before wiping my phone and cache over and over again, NOTHING HAPPENED; no change!!! still kept throwing back the error message.
So I decided to flash the second one, and for a split second, I was happy cos the error had disappear...only for me to wait for eternity and in vain for the phone to boot (that is, even if it could). suddenly, I realized what had happen....the phone couldn't boot pass the ASUS logo, neither could it load recovery again (as it used to). It only boots into ADB, but of course, that will require USB DEBUG MODE to be ON to be able for the phone to be detected through ADB (which is far from possible due to the numerous wipes I performed).
CURRENT SITUATION: I can't ADB, I can't get into recovery, and I'm stacked with the logo at boot......when the phone is completely turned off and placed on charge, the battery shows an empty battery with the loading (status) sign (but it charges, even without the OS being able to display the process).
Don't know whether anyone is facing same, or I can start a new thread with this? and I need help before taking it to a 3rd party repairs (since we don't hv Asus customer care in our country yet).
Will be glad to find help.
PS: The computer still detects the phone as an ADB Android device, and to me, that's a beacon of hope.

abodan09 said:
Well, i can feel some doubt in your post...but h*ll yeah! I'm currently facing the same problem; where flashing stock rom, downloaded from their site, using their stock recovery, adb, and adb sideload....
the rom flashes successfully, but still boots with the same error...To be frank, i'm fed up...and almost about giving up on this phone...
-i believe i'll give it another shot this very night, trying different methods...funny ones though; if and when they work, i will definitely update my post again... my phone version is Z00ED, in case anybody cares to know -
Click to expand...
Click to collapse
This problem will resolve to open the bootloader.

Muminek111 said:
This problem will resolve to open the bootloader.
Click to expand...
Click to collapse
I don't think I got that...do u mind explaining further??? thank you!

abodan09 said:
I don't think I got that...do u mind explaining further??? thank you!
Click to expand...
Click to collapse
You can not flash the older version stock rom from stock recovery.
Flash latest stock rom.
Download this twrp: https://drive.google.com/file/d/0B7F3ZXr565GkY28yUjhfRkd5MUk/view?usp=drivesdk
Download this ulock bootloader: https://drive.google.com/file/d/0B7F3ZXr565GkMWNwUkZJa1BUVUU/view?usp=drivesdk
Download this supersu: https://drive.google.com/file/d/0B7F3ZXr565GkOTcxb2VPbmQzT2M/view?usp=drivesdk
Restart to fasboot mode.
Command: fastboot boot twrp.img
From twrp flash first zip ulock bootloder then flash zip supersu.
Reboot.
---------- Post added at 08:39 PM ---------- Previous post was at 08:15 PM ----------
Android 6
Must be first opened bootloader then can modified boot image.

Same ERROR,you just need to flash the unlock bootloader file
UnlockBL.zip
Click to expand...
Click to collapse
https://goo.gl/nVq9e7

i have installed new firmware on my zenfone laser 2 (ze500kl),but when restarts it says error cant load invalid boot image...then i fastbooted boot.img..but when i restarts the phone it again shows the errror...
pls help me..

christin7 said:
i have installed new firmware on my zenfone laser 2 (ze500kl),but when restarts it says error cant load invalid boot image...then i fastbooted boot.img..but when i restarts the phone it again shows the errror...
pls help me..
Click to expand...
Click to collapse
Test:
Try to flash boot.img of your firmware version from fastboot mode but use command: fastboot boot boot.img. Reboot system. Then let me know.

infinite boot loop.

for my unhappiness after using a rom for a short time on my handset locked and hung alone.
now the device is in infinite loop, only the logo of the leeco and restarts all the time.
recovery mode does not start, only in fastboot mode.
I tried the full rom by fastboot, tried mode any HSM with QDLoader 9008, and none worked.
Can someone help me?

it looks like my device is without bootloader, or with a different one.
How to fix this?

https://forum.xda-developers.com/showpost.php?p=73810875&postcount=226

Unfortunately, it did not work.

Thanks in advance for all those who tried to help me more
my device does not start in recovery mode, only in fastboot.
I have already performed all the procedures I knew and it was indicated here, only the logo of the leeco appears and restarts.
attempts:
1 - Here we go:
1. Download .zip containing files from Mega: https://mega.nz/#!5boxDYrL!_O-oD05yh...hV5LKwyHa39bWM
2. Extract files to path where you are able to flash them using fastboot (ie. Same folder with fastboot)
3. Boot your phone to bootloader (Vol- & Power)
4. Flash everything:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot format data <- THIS WILL WIPE YOUR PHONE INCLUDING INTERNAL STORAGE
fastboot flash cmnlib64 cmnlib64.mbn
fastboot flash ddr ddr.mbn
fastboot flash cmnlib cmnlib.mbn
fastboot flash hyp hyp.mbn
fastboot flash pmic pmic.elf
fastboot flash tz tz.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash devcfg devcfg.mbn
fastboot flash xbl xbl.elf
fastboot flash keymaster keymaster.mbn
fastboot flash modem NON-HLOS.bin
fastboot flash dsp adspso.bin
fastboot flash bluetooth BTFM.bin
fastboot flash devinfo devinfo.bin
it was no use.
2 - official recovery flash
3 - FlashOne2.0, qfil Flash. https://forum.xda-developers.com/le-pro3/how-to/guide-unbrick-le-pro3-tested-t3622340.
4 - FlashOne2.0 fastboot.
for my little knowledge some of these procedures should work.
Is there a solution? Can someone help me where I could get help?

Try it as I did:
- Flash TWRP.img in Fastboot mode
- Restart in Recovery : power and volume +
- Once in TWRP, Connect to PC mode MTP, copy a custom ROM
- Clean with wipe and install ROM

AGE1266 said:
my device does not start in recovery mode, only in fastboot.
I have already performed all the procedures I knew and it was indicated here, only the logo of the leeco appears and restarts.
Click to expand...
Click to collapse
Do you have any solution? I had the same problem last night

So there is no recovery on the phone and you can't load a recovery on it either? Don't tell me... the bootloader locked itself? Which stock ROM version were you on? Which model---x722, x720, x727? Apparently eUI 5.9 forcibly locks the bootloader and prevents all bootloader unlocks. So if this is the case, then there's no way to unlock the bootloader, unfortunately.
Otherwise it's an internal partition issue. The internal partition is messed up and you have to rebuild it manually which is close to impossible unless you're a coder used to Linux filesystems with access to your phone's exact model's partition setup. I doubt this is the case though.
Keep trying OP. Don't give up. You might as well try everything--heck, go and post on those Chinese forums using Google Translate and you will likely get a response.

Gynlemon said:
Try it as I did:
- Flash TWRP.img in Fastboot mode
- Restart in Recovery : power and volume +
- Once in TWRP, Connect to PC mode MTP, copy a custom ROM
- Clean with wipe and install ROM
Click to expand...
Click to collapse
I've tried all methods with fastboot, including the complete rom!

thacvu said:
Do you have any solution? I had the same problem last night
Click to expand...
Click to collapse
unfortunately I have not solved anything yet, if you have any solutions please advise here!

sk8223 said:
So there is no recovery on the phone and you can't load a recovery on it either? Don't tell me... the bootloader locked itself? Which stock ROM version were you on? Which model---x722, x720, x727? Apparently eUI 5.9 forcibly locks the bootloader and prevents all bootloader unlocks. So if this is the case, then there's no way to unlock the bootloader, unfortunately.
Otherwise it's an internal partition issue. The internal partition is messed up and you have to rebuild it manually which is close to impossible unless you're a coder used to Linux filesystems with access to your phone's exact model's partition setup. I doubt this is the case though.
Keep trying OP. Don't give up. You might as well try everything--heck, go and post on those Chinese forums using Google Translate and you will likely get a response.
Click to expand...
Click to collapse
is X720 and was using the 18S version, I installed the Rom JUI 15-09-17 for X720 modified by Bahuy2003, after 2 days after using the device it froze and had to restart the force, but after that it never worked again!

use flashone 2.0 method
AGE1266 said:
is X720 and was using the 18S version, I installed the Rom JUI 15-09-17 for X720 modified by Bahuy2003, after 2 days after using the device it froze and had to restart the force, but after that it never worked again!
Click to expand...
Click to collapse
google flashone restore for your phone.

Ab20000 said:
google flashone restore for your phone.
Click to expand...
Click to collapse
believe me if you want, I've spent more than once FlashOne2.0 and still not solve! worst of all is that there is no one with the same status as me, that is impossible. Would someone buy my device to take advantage of?

my leeco le 3 pro restarted alone after installation of Rom JUI, is in infinite bootloop, but the device is very new and little time purchased, can anyone tell me how can I sell it to someone else to enjoy the components?

r u using real pro3 files or not?
---------- Post added at 04:21 PM ---------- Previous post was at 04:20 PM ----------
AGE1266 said:
believe me if you want, I've spent more than once FlashOne2.0 and still not solve! worst of all is that there is no one with the same status as me, that is impossible. Would someone buy my device to take advantage of?
Click to expand...
Click to collapse
AGE1266 said:
my leeco le 3 pro restarted alone after installation of Rom JUI, is in infinite bootloop, but the device is very new and little time purchased, can anyone tell me how can I sell it to someone else to enjoy the components?
Click to expand...
Click to collapse
r u using real pro3 files or not? this method even fixes phones which are dead. u need to reinstall drivers or do this on some other pc.

I had the same problem like AGE1266, but I installed OmniRom + Blackscreen 3.6 kernel. It worked well for 2-3 days, and suddenly it restarted and restarted several times but not successfully. It can't boot to recovery too. I've flashed with FlashOne2.0, everything seems fine, but it still can't boot. Does anyone have solution for that case? Thank you (and sorry for my English).

Too many problems with le pro 3 and its versions :/

I have the same problem as bootloop, when boot to logo then reboot, when boot to recovery then rebootม even though install twrp in fastboot mode(fastboot mode just find).
I found this as similar problem.
If we found the kernel that can turn off big-core or similar, may be we can solve the problem, but we cant. T-T

First thing what is your model you have?
Sent from my LEX727 using xda premium
http://forum.xda-developers.com/showthread.php?p=69627992
Go here if you 727 you can try but if you read all before trying it.

AGE1266 said:
for my unhappiness after using a rom for a short time on my handset locked and hung alone.
now the device is in infinite loop, only the logo of the leeco and restarts all the time.
recovery mode does not start, only in fastboot mode.
I tried the full rom by fastboot, tried mode any HSM with QDLoader 9008, and none worked.
Can someone help me?
Click to expand...
Click to collapse
and Now I have the same problem
I think its hardware related so :crying:

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

Severe Issues after uninstalling Magisk - Motorola XT1926-7 G6 Plus

I will try to be as brief as possible, but explain in detail what happened to my moto g 6 plus XT1926-7.
I was running the stock firmware from the:
RETLA
Channel from march 27, 2019:
XT1926-7_EVERT_RETLA_9.0_PPWS29.116-11-2
I unlocked the bootloader using the info provided by motorola.
I used a TWRP installer which I found in this website and successfully installed twrp 3.2. I quickly realized that this version did not decrypt the data partition.
No problem, using the boot command in fastboot, I can load TWRP 3.3 which does decrypt the data partition.
I installed magisk V19.2
I then installed 2 magisk modules:
Viper equalizer
Pixel 3 ( something ) which makes the UI a little nicer.
The phone worked with no problems for months until the July OTA "update unsuccessful" nag screen started showing up every 10 seconds.
I read from several sources that an unlocked bootloader phone from motorola won´t take OTA updates. Fine. I lived with it for a couple of weeks until the nagging screen became unbearable.
I decided to unroot, relock the bootloader get the OTA and move on with my life.
I uninstalled magisk from the magisk manager and the phone immediately went into boot loop.
I´ve been using TWRP for years now with several phones, and each time i´ve had a problem, i just restored from the last backup ( which i do at least once a month ) and move on.
This time i used the full twrp backup from a couple of weeks ago, but it didn´t work.
The phone still bootlooped. It either rebooted at the "verity disabled" screen or it went straight into TWRP 3.2
I decided to use the original backup i did several months back when i first installed magisk and it didn´t work either. First time in years that a TWRP backup didn´t work.
I read in several threads on several websites that the only thing left to do was to flash stock rom from motorola in fastboot basically file by file.
So I did it and flashed the original stock rom for my device from the RETLA channel:
XT1926-7_EVERT_RETLA_8.0.0_OPWS27.113-89-5
The phone booted into android but both IMEI and wifi mac address were gone. So no carrier signal and no wifi.
I read from several threads that a backup from the EFS and persist partitions would solve this, so I tried both backups of these partitions i had, but nothing worked.
fastboot would read the IMEI number with the get vars command, but android would not recognize them.
Then i found a post here from a couple of days ago of a person who had the same problem and by flashing the latest stock rom fixed this.
So i downloaded:
XT1926-7_EVERT_RETLA_DS_9.0_PPWS29.116-11-6
from the RETLA channel and again proceeded to flash via fastboot file by file.
this time android booted and it did load the both IMEIs and the wifi mac address BUT, wifi disconnects every 10 seconds and the carrier signal is worse.
I then tried the lenovo assistant as suggested in another thread in this website and used the flash / recover feature. Same thing happened. android boots but wifi signal is lost every 10 seconds and carrier signal gets cut off at regular intervals and is very weak.
This has rendered my phone basically useless. I had been using a Moto G2 for many years with no problem and i bought this one just a couple of months ago.
I don´t mind flashing the phone again, and i´m good at following step by step procedures.
It would be super cool if someone would point me in the right direction on how to fix this.
Thanks in advance

This is how I managed to fix my Moto G6 plus
I was able to fix my phone so I will reply to my own post:
It took me almost 4 days to fix the phone. It took a lot of reading and MANY hours of trial and error, so I´m going to describe what I did in order to help anybody with the same problem to save themselves a LOT of time.
As it happens, I found out that a lot of people have run into the same problem of bootloops after uninstalling magisk and then even after flashing the stock rom, had no wifi and no carrier signal. Hence, a useless phone.
Prerequisites for this solution:
Be able to boot your phone into bootloader mode.
If you don´t know what bootloader mode is, do your research. It´s very simple to get to it. Just power off your phone and then press the power and volume down buttons simultaneously for a couple for a couple of seconds. How to use it is another matter entirely. Again... do your research.
1. Before disaster strikes... Do not use an installer script to force install TWRP on a phone which has A / B boot slots. If you plan to install Magisk later, do not force instal TWRP. Moto G6 Plus is such a phone. This is written very clearly in the Magisk troubleshoot wiki. I wish I had read this before.
If you want to use TWRP ( and you should ), load TWRP 3.3 or newer temporarily from fastboot with the boot command. It will be able to decrypt your phone´s data. TWRP 3.2 does not.
To decrypt you will need to have a pin or pattern unlock set previously on your phone.
I used a script to force install twrp 3.2 to my phone. It´s useless since it can´t decrypt the phone and it was surely the cause of all this mess.
I´m not blaming TWRP or Magisk. This mess was all my fault. I´ll tell you about it later.
2. I have a TWRP 3.3 full decrypted backup of ALL the partitions of the phone from last week. I always do regular backups. I´ve been using TWRP for years and it has always served me well. This time it didn´t. My bad, not TWRP´s. I flashed the backup to the phone and it kept bootlooping. I flashed the backup about 20 times!
3. If you´re in this mess already because you forced install TWRP and you uninstalled magisk and your phone is bootlooping, you will probably have to wipe your phone and flash the stock ROM appropriate to your model. Trust me, if you´re not an android / linux guru, your only way to get your phone back will be to wipe your phone completely. I realized this the hard way.
Don´t flash the original ROM for the G6 plus ( android 8 ). Use the latest build. It seems motorola took note of so many people having the "no carrier / no wifi signal" problem, so they have included a fix for this in the latest android 9 releases. This has worked for other people, It worked for me. I don´t know for sure if it will work for you.
4. Here´s one important piece of info. For motorola phones it is very important to have a backup of these two partitions:
EFS
PERSIST
I´m not 100% percent sure of all the info they have or the entire purpose that they serve, but I now know 1 thing. These two partitions have critical and unique information about your phone.
They provide the unique IMEI info. Wifi Mac address info. Baseband info, which is all the technical carrier signal communications stuff, etc..
How do you back up these partitions? Use a custom recovery like TWRP or similar. If you want to mod your phone, please do your research on the software you are going to install. I usually do it, this time around I just winged it, and look where it got me.
5. Here´s another important piece of information to take note of BEFORE disaster strikes. Write down on a piece of paper and store in a safe place ( a txt file on your pc will do ) the following:
Your phone´s exact model Nº. Mine is:
XT1926-7
Go to settings: tap System, tap about phone and write down which software channel you are on.
Mine is: RETLA
This is important because it determines which stock ROM you will need to download, as not all ROMS for this device are the same. The XT1926-7 is a dual SIM phone so NO. Not all versions of the stock rom will work.
6. In order to download the correct stock ROM for your phone, on your computer, go to:
mirrors .lolinet .com /firmware/moto/evert/official/
This website is one of several which offer stock roms for motorola phones. You can use this one or search around for another one.
The website will show you a directory structure of all the different software channels available for the motorola Moto G6 Plus. Choose the folder appropriate for your phone.
Remember mine was the RETLA channel?
These are the only channels which offer stock roms for the XT1926-7
RETLA
or
TEFCO
or
TEMX
or
TIGCO
If your phone is factory unlocked you will probably have to use the RETLA versions.
Within the correct folder, look for the latest ROM for your model. Pay close attention to the name of the rom. The first section will indicate what model it´s intended for. For example, in the RETLA folder there´s ROMS for 2 different models:
XT1926-6
XT1926-7
The correct file for my phone was:
XT1926-7_EVERT_RETLA_DS_9.0_PPWS29.116-11-6_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
Please do your research and download the right file for your phone. If you´re not careful, it will lead to bigger problems.
Please also download the original factory version of android 8 ( oreo ) made for your phone. you´re gonna need 2 files from that ROM. In my case the file was:
XT1926-7_EVERT_RETLA_8.0.0_OPWS27.113-89-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
The stock roms are about 2 gigs in size.
6. Next you´ll need to download the right tools to flash the stock rom to your phone.
I´m assuming you have downloaded and installed the latest motorola USB drivers for your computer and installed them. If you haven´t. The time is now.
The internet will tell you to download the Android SDK platform tools. This package will give you fastboot and ADB.
Don´t download it. The "vanilla / run of the mill" version of fastboot won´t help you.
Motorola created a modified version of fastboot for their phones, which flashes a motorola phone in specific ways. It´s called: mfastboot
I saw the procedure differences while running mfastboot in the DOS window. In the end I was able to fix my phone because of the differences which mfastboot offers. You´re gonna have to trust me on this one.
Since the motorola version of fastboot is small in size, i´m going to attach it to this comment. Look for the attached file named:
mfastboot_adb_tools.zip
7. Create a folder on your hard drive. It doesn´t matter how you call it. Just remember where it is. Unzip / decompress the entire contents of the file:
mfastboot_adb_tools.zip
you just downloaded to that folder. it should look like this:
Then unzip / decompress the entire contents of the:
XT1926-7_EVERT_*YOUR-CHANNEL*_DS_9.0_PPWS29.116-11-6
to the same folder. it should look like this:
Now we will need just 2 files from the:
XT1926-7_EVERT_*YOUR_CHANNEL*_8.0.0_OPWS27.113-89-5
Unzip these two files to the same folder where you have unzipped everything else:
8. It is now time to boot your G6 Plus into bootloader mode. With the phone turned off, press the power and volume down buttons simultaneously for about 5 seconds.
You´ll get a black screen with the android robot laying on its back. At the bottom of the screen you will see a piece of text which reads:
Connect USB Data cable.
Do it. Connect the usb cable to your computer and then connect it to the phone. the connect data cable message will change to a green sentence which reads:
Transfer mode: USB connected
9. On your computer, return to the folder where you placed all the files. Look for a blank space with no files within that folder and press the shift key + mouse right click. out of the context menu you get, select:
open command window here
You will get a black screen with a white prompt.
Now let´s make sure your phone is connected to your computer. In that black window type:
mfastboot devices
The result should be your phones serial number followed by the word fastboot.
If you got nothing or any sort of error it means you phone is not connected properly or some drivers are missing. troubleshoot that and come back when your phone is actually connected.
10. OK... let´s start flashing the files. The following series of commands I copied from another post in this website. I did not come up with this set of commands and I will repeat that i´m no expert. This worked for my particular situation and by no means i can guarantee that it will work with your phone. All I´m saying is that if you´re desperate and at the current moment you have a soft bricked phone, go ahead and try this.
In that black window, start copying these commands 1 by 1. Wait for them to execute and get an OK message from the phone. If you get an error try that command again. to paste the command in the black window ctrl + v does not work. you have to right click your mouse on top of that window and paste the command that way. When you´ve pasted the command, press enter to execute.
These are the commands:
Code:
mfastboot getvar max-sparse-size
mfastboot oem fb_mode_set
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot flash modem_a NON-HLOS.bin
mfastboot flash fsg_a fsg.mbn
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash bluetooth_a BTFM.bin
mfastboot flash dsp_a dspso.bin
mfastboot flash logo_a logo.bin
mfastboot flash boot_a boot.img
mfastboot flash system_a system.img_sparsechunk.0
mfastboot flash system_a system.img_sparsechunk.1
mfastboot flash system_a system.img_sparsechunk.2
mfastboot flash system_a system.img_sparsechunk.3
mfastboot flash system_a system.img_sparsechunk.4
mfastboot flash system_b system_b.img_sparsechunk.0
mfastboot flash system_b system_b.img_sparsechunk.1
mfastboot flash oem_a oem.img
mfastboot flash oem_b oem_other.img
mfastboot flash vendor_a vendor.img_sparsechunk.0
mfastboot flash vendor_a vendor.img_sparsechunk.1
mfastboot erase carrier
mfastboot erase userdata
mfastboot erase ddr
mfastboot oem fb_mode_clear
press power button on the phone and restart it.
It might take a while to boot, but if and when you see and hear the "hello moto" greeting, it means your phone has been fixed.
You might end up with a restored phone, but no wifi and no carrier signal. Then what you will need to do is to flash the backup of your EFS and Persist partitions using TWRP, and then retry the whole procedure again.
This is the way I fixed my Moto G6 plus.
It wasn´t a perfect fix for me. Since I had forced installed TWRP 3.2 with an installer script, that did something to the boot partition and now even after reflashing the entire phone I don´t have any type of recovery.
No stock recovery of any kind. It´s not a problem since we can boot TWRP temporarily from mfastboot and in bootloader mode just like the procedure we did with the stock rom. All the rest is back to perfect working condition.
I was also able to make a new full phone backup.
I will tell you this, now I know that all this mess is not TWRP´s or Magisk´s fault. They are fine programs. It was my fault due to a lack of research. I shouldn´t have mixed them both in the way I did.
I forced installed TWRP to my phone because it was what I was used to and I didn´t read any instructions for Magisk which I had never used. I come from the SU era.
I hope this wall of text will be of help to anyone going through the same situation with a Moto G6 plus.
Unfortunately nobody replied to my original post so I had to solve this on my own. The good thing is that I did manage to fix it.
I will repeat it one more time. I´m not an android expert. Not by far. I´m not saying this procedure will work for your particular problem. I´m only sharing what worked for me and I hope it will work for you. If it doesn´t. Keep looking and researching.
GOOD LUCK.

hello, i have the exact same problem but my stock rom dowes not have any system_b file ( my rom is RETAR) what should i do?
Edit: sorry, i had another update file, pien not oreo. On oreo zip it appears
---------- Post added at 01:07 AM ---------- Previous post was at 12:21 AM ----------
Ok, so now i followed your guide exactly as you did it but it doesn't boot. It bootloops
Do you know what's happening?

juampapo546 said:
hello, i have the exact same problem but my stock rom dowes not have any system_b file ( my rom is RETAR) what should i do?
Edit: sorry, i had another update file, pien not oreo. On oreo zip it appears
---------- Post added at 01:07 AM ---------- Previous post was at 12:21 AM ----------
Ok, so now i followed your guide exactly as you did it but it doesn't boot. It bootloops
Do you know what's happening?
Click to expand...
Click to collapse
Sorry for spamming the thread, i got out of the boorloop by installing again the oreo stock rom (with no imei nor mac). After doing it i did the whole procedure again and it booted but still having the wifi/mobile data resetting. I will redo everything againand if after several times i get to nothing i will post another question here.
Sorry and thank you

Still doesn't work

juampapo546 said:
Still doesn't work
Click to expand...
Click to collapse
Do you have a backup of your EFS and Persist partitions from when the phone was in working condition?
You could use those to restore you Emei and wifi mac address and then flash Pie again.

lcmp said:
Do you have a backup of your EFS and Persist partitions from when the phone was in working condition?
You could use those to restore you Emei and wifi mac address and then flash Pie again.
Click to expand...
Click to collapse
No, I don't have one. I thought that in this guide I didn't need the backup but apparently there is no solution for now if there is no backup.
Thank you

juampapo546 said:
No, I don't have one. I thought that in this guide I didn't need the backup but apparently there is no solution for now if there is no backup.
Thank you
Click to expand...
Click to collapse
Like I said in my post, i´m not an expert. I just posted the procedure which worked for me.
I did have a backup of those partitions and I used them several times and it did not work. Are you using mfastboot instead of regular fastboot?
I would try the procedure several times.
Buena Suerte.

lcmp said:
Like I said in my post, i´m not an expert. I just posted the procedure which worked for me.
I did have a backup of those partitions and I used them several times and it did not work. Are you using mfastboot instead of regular fastboot?
I would try the procedure several times.
Buena Suerte.
Click to expand...
Click to collapse
I tried it several times but as I said previously there is no point doing it with no backup ( not my words, I talked to a guy that develops most of the g6 Plus roms and told me for now there is no solution without the backup, it was over the Spanish telegram group. I highly recommend it, if you want to join talk to me at the PM because I can't share social network on posts)
Thank you for your advise, if I am able to solve it I will let you know

lcmp said:
Like I said in my post, i´m not an expert. I just posted the procedure which worked for me.
I did have a backup of those partitions and I used them several times and it did not work. Are you using mfastboot instead of regular fastboot?
I would try the procedure several times.
Buena Suerte.
Click to expand...
Click to collapse
I screwed up my efs/persist and didn't have a backup (a few months ago).
So can I please have a copy of the backed up efs and persist partitions? I should be able to go through and replace any ids (mac address and imei) with my own. If I figure it out, I'll write a guide on it too .
I have the same device model as you (XT1926-7 RETLA).
I've also been looking at this (https://forum.xda-developers.com/razr-i/development/pds-partition-fix-risky-faint-heart-t2813292) which is for a different problem with a different phone where someone posted their pds/persist partition, but it looks like the data in those partitions are just stored plainly in binary.

stevendoesstuffs said:
I screwed up my efs/persist and didn't have a backup (a few months ago).
So can I please have a copy of the backed up efs and persist partitions? I should be able to go through and replace any ids (mac address and imei) with my own. If I figure it out, I'll write a guide on it too .
I have the same device model as you (XT1926-7 RETLA).
I've also been looking at this (https://forum.xda-developers.com/razr-i/development/pds-partition-fix-risky-faint-heart-t2813292) which is for a different problem with a different phone where someone posted their pds/persist partition, but it looks like the data in those partitions are just stored plainly in binary.
Click to expand...
Click to collapse
Well yes, but actually no. You can't use another's device efs/persist because these files can only be read by the device that created them
However I found a magisk module that fixes several persist issues. It is called PIXELARITY

However I found a magisk module that fixes several persist issues. It is called PIXELARITY
Click to expand...
Click to collapse
Does this actually fix the persist issues permanently? Or does it just work around them while it is installed? I am in the same boat as others without a proper backup of efs/persist. If it fixes anything I will be happy.
Also, how are you getting the Magisk module installed? I have no wifi or cell service so the Magisk app can't download the module. Tried just downloading the module repo .zip file and manually installing from that, but magisk is not recognizing it as a valid module. I almost never install Magisk at all let alone modules, so I am a bit in the dark on the general procedures.
Edit: Wound up getting it installed with a USB ethernet dongle to get some form of connection. But the PIXELARITY mod did absolutely nothing in my case. Flashed stock and I have IMEI and Wifi MAC Address back, but they are now both cutting out in the same way as yours. The Magisk module did nothing there either.

I forgot to post it, for mi actually it just partially worked ( permanent). I said partially because I lost my IMEI.
I am now trying to use the efs that doesn't have an IMEI to patch it up with mine and maybe make it "universal" and share it to other people and they just patch their IMEI.
However it is quite complicated and I am not having a really advanced progress on this.
---------- Post added at 12:33 PM ---------- Previous post was at 12:29 PM ----------
I have just seen the edit.
What worked for me I believe it was a chance and I can't recall exactly what I did before it "workerd", I did a lot of things, as I believe you also did.
I would try following the guide up here and installing the module, maybe that's what I did.

Fixed the signal drop with no backups here the link
https://forum.xda-developers.com/g6-plus/how-to/guide-how-to-solve-wifi-mobile-data-t3994827