Hi folks, my A1 device is stuck in weird bootloop situation.
This is what I did.
- oem unlock
- boot with a twrp recovery image
- edit build.prop (Added persist.camera.HAL3.enabled=1 on top)
- reboot
- first bootloop (reboot after mi logo)
- flashed with tissot_images_7.12.7_7.1 version
- succeed boot but the device couldn't recognize usim
- factory reset from android setting menu
- second bootloop (reboot after mi logo)
- flashed with tissot_images_7.12.7_7.1 version
- still bootloop (reboot after mi logo). Since this, it always reproduces bootloop even I had flashing again.
- reboot with twrp and checked /sdcard directory. It was empty. There was only 'TWRP' directory
- after searching, I assumed that it was partition broken issue. (http://en.miui.com/thread-970194-1-1.html)
- Followed this article to fix partition problem. https://forum.xda-developers.com/xiaomi-mi-3/general/guide-instruction-to-restore-mi4-mi3-t3279927
- After flashing, went to hardbrick(edl_mode). After several trying, could flash again.
- Different type of bootloop. Could pass mi logo and android one logo. But after few second after, it reboots.
Last bootloop(current status) does not depend on special action. Even when I skipped few task(setup network, account, etc), it still reboots.
Maybe it could depend on time. I think something was broken in the background.
Does anyone know about this kind of problem?
I searched for two days, but A1 is newer device so there is not much information for troubleshooting.
Please help me :crying:
Try flashing the persist.img through fastboot by typing fastboot flash persist persist.img .
I guess you're fimiliar about how fastboot flashing works. I did got my phone with the similar issue fixed doing that, but later the persist image couldn't be flashed and I ended up hard bricking the device as my PC restarted while I was flashing using MiFlash and service guys had to replace the entire motherboard.
You can try doing that but do note that flashing the persist.img many times is strictly prohibited.
Use MiFlash to flash the rom completely. Did you try to preserve user data when flashing?
Seems that unless you are rooted, playing with the build.prop from TWRP or some other method is a bad idea.
FAILED (remote: Error: This image isn't allow download)
Edwin Hamal said:
Try flashing the persist.img through fastboot by typing fastboot flash persist persist.img .
I guess you're fimiliar about how fastboot flashing works. I did got my phone with the similar issue fixed doing that, but later the persist image couldn't be flashed and I ended up hard bricking the device as my PC restarted while I was flashing using MiFlash and service guys had to replace they mother.
You can try doing that but do note that flashing the persist.img many times is strictly prohibited.
Click to expand...
Click to collapse
Thanks very much for you helping Edwin!
I tried the command that you let me know, but it returns following error.
./fastboot flash persist images/persist.img
target reported max download size of 536870912 bytes
sending 'persist' (4720 KB)...
OKAY [ 0.160s]
writing 'persist'...
FAILED (remote: Error: This image isn't allow download)
finished. total time: 0.180s
I searched cases for this error, but couldn't find working answer.
Do you have any idea about this?
Thanks! Have a great day!
Try emptying the userdata partition using fastboot.
I heard that the low version of the driver also causes errors. Update the driver's fastboot, and try to flash again.
Try manually flashing the firmware by following this guide
http://en.miui.com/thread-942449-1-1.html
after completing the last step given in the guide,type "fastboot reboot".
Also this only works with unlocked bootloader
pitzcarraldo said:
Thanks very much for you helping Edwin!
I tried the command that you let me know, but it returns following error.
./fastboot flash persist images/persist.img
target reported max download size of 536870912 bytes
sending 'persist' (4720 KB)...
OKAY [ 0.160s]
writing 'persist'...
FAILED (remote: Error: This image isn't allow download)
finished. total time: 0.180s
I searched cases for this error, but couldn't find working answer.
Do you have any idea about this?
Thanks! Have a great day!
Click to expand...
Click to collapse
Try restoring the persist.img from the August build. I think that error occurs because the size of persist is different in those two builds.
Oh My Savior!!!!!!!!!!!!!!
Edwin Hamal said:
Try restoring the persist.img from the August build. I think that error occurs because the size of persist is different in those two builds.
Click to expand...
Click to collapse
Finally, it is fixed!!!!!!!!!
Thank you sooooooo much my savior!
God bless you!
I really really owe you!
Happy holiday!
You're my Santa Clause!
pitzcarraldo said:
Finally, it is fixed!!!!!!!!!
Thank you sooooooo much my savior!
God bless you!
I really really owe you!
Happy holiday!
You're my Santa Clause!
Click to expand...
Click to collapse
I'm really glad that I could help. I had this issue too and I can recall how painful it was. I think more people need to know about this fix, can you post the august persist.img file here so more people can access that easily?
persist.img
Edwin Hamal said:
I'm really glad that I could help. I had this issue too and I can recall how painful it was. I think more people need to know about this fix, can you post the august persist.img file here so more people can access that easily?
Click to expand...
Click to collapse
Sure. Here is persist.img file that I used to fix my case.
Thanks.
Happy Holidays!
pitzcarraldo said:
Sure. Here is persist.img file that I used to fix my case.
Thanks.
Happy Holidays!
Click to expand...
Click to collapse
I was in a very similar scenario, however, I could not find any persist.img I could flash through fastboot. Can't erase it also.
I also tried to get it working though using twrp and downloading the latest stable build from Xiaomi.
Booting temporally into the TWRP, sending the persist.img found into the build files and using the following cmd:
dd if=/sdcard/persist.img of=/dev/block/mmcblk0p27
No luck. Device boots, goes to setup wizard, then reboots a few seconds later. =(
Not sure what to try anymore. Xiaomi doesn't officially sell phones in my country so I can't contact warranty.
rlsin said:
I was in a very similar scenario, however, I could not find any persist.img I could flash through fastboot. Can't erase it also.
I also tried to get it working though using twrp and downloading the latest stable build from Xiaomi.
Booting temporally into the TWRP, sending the persist.img found into the build files and using the following cmd:
dd if=/sdcard/persist.img of=/dev/block/mmcblk0p27
No luck. Device boots, goes to setup wizard, then reboots a few seconds later. =(
Not sure what to try anymore. Xiaomi doesn't officially sell phones in my country so I can't contact warranty.
Click to expand...
Click to collapse
Brother persist.img file size 32mb no 4 MB size Google searching mi a1 persist partition repair my telegram +90594461388 add me bro
Byramklc said:
Brother persist.img file size 32mb no 4 MB size Google searching mi a1 persist partition repair my telegram +90594461388 add me bro
Click to expand...
Click to collapse
Thanks for helping mate! Though this specific google search I found some additional information on this matter (not kidding).
I was able to flash persist by downgrading back to the august nougat build. Then flashed the original persist file.
The instructions don't work if you are in any newer build, I guess I first misunderstood that part (or it just worked after a couple of tries).
Though now it doesn't recognize my sim card, so I'll keep working on it.
Best regards.
rlsin said:
Thanks for helping mate! Though this specific google search I found some additional information on this matter (not kidding).
I was able to flash persist by downgrading back to the august nougat build. Then flashed the original persist file.
The instructions don't work if you are in any newer build, I guess I first misunderstood that part (or it just worked after a couple of tries).
Though now it doesn't recognize my sim card, so I'll keep working on it.
Best regards.
Click to expand...
Click to collapse
Bro IMEI number 0 or normal
Byramklc said:
Bro IMEI number 0 or normal
Click to expand...
Click to collapse
Spot on! IMEI number 0. Trying to rewrite it somehow...
rlsin said:
Spot on! IMEI number 0. Trying to rewrite it somehow...
Click to expand...
Click to collapse
Bro agus security using 7.8.23 rom
Dualwrite IMEI. Used
Hi Guys, got the same problem here. Out of the blue my phone doesn't boot anymore (no root, no flash, nothing).
I tried flashing, with MiFlash and Fastboot, 7.1 December and Oreo January, but it didn't work unfortunately.
Now after reading your last posts I'm looking for august update. Could you please tell me where you got it.
It's weird because if i flash correctly (fastboot 7.1) i get the Android One Logo, a glitch and then it reboots, but when i try 8.0 or MiFlash i only get the Xiaomi logo and then it reboots :/
Trying to flash persist (both with 4.6MB and 32MB images through DD and TWRP) might have slightly changed the behavior ...
No clue about IMEI numbers being wiped out or not :/ (but i have the phone box with them in need)
Thanks for you help anyways
gridaz said:
Hi Guys, got the same problem here. Out of the blue my phone doesn't boot anymore (no root, no flash, nothing).
I tried flashing, with MiFlash and Fastboot, 7.1 December and Oreo January, but it didn't work unfortunately.
Now after reading your last posts I'm looking for august update. Could you please tell me where you got it.
It's weird because if i flash correctly (fastboot 7.1) i get the Android One Logo, a glitch and then it reboots, but when i try 8.0 or MiFlash i only get the Xiaomi logo and then it reboots :/
Trying to flash persist (both with 4.6MB and 32MB images through DD and TWRP) might have slightly changed the behavior ...
No clue about IMEI numbers being wiped out or not :/ (but i have the phone box with them in need)
Thanks for you help anyways
Click to expand...
Click to collapse
I am stuck at bootloop again while tinkering with imei codes. Probably killed my phone...
You can find august build and others here:
https://xiaomifirmware.com/roms/download-official-roms-xiaomi-mi-a1/
Thanks for the links, unfortunately it doesn't boot either.
It looks like it's going too, android one logo, color animation and then it reboots :/ I don't really know what i can try more.
Related
I went to flash the latest version of Mahdi ROM, which I have done many times without a problem. This time, however, the patch.zip that I downloaded failed to install and then I was stuck in a fastboot. I found another post on here where someone said that putting certain commands into the prompt would fix it so I made sure that I had all the right files for my LS980 and went ahead and did it.
These are the commands I followed that got me to this point:
fastboot erase boot
fastboot erase aboot
fastboot erase recovery
fastboot erase laf
fastboot flash boot 6-boot.img
fastboot flash aboot 4-boot.img
fastboot flash recovery 10-recovery.img
fastboot flash laf 11-laf.img
fastboot reboot
But now I can't seem to bring up anything and I've tried powering it on, going into recovery, and going into download mode but none of those things seem to be working. When I plug it into my computer, it makes the little sound and it's recognized but only as an E: drive with one lonely folder in it titled "image" and then I get a bunch of pop ups saying that "You need to format the disk in drive S: (and other various letters) before you can use it".
I really hope someone here can help me and that I haven't completely ruined my phone because there's no way that I have the money or means to replace it.
cookierobots said:
I went to flash the latest version of Mahdi ROM, which I have done many times without a problem. This time, however, the patch.zip that I downloaded failed to install and then I was stuck in a fastboot. I found another post on here where someone said that putting certain commands into the prompt would fix it so I made sure that I had all the right files for my LS980 and went ahead and did it.
These are the commands I followed that got me to this point:
fastboot erase boot
fastboot erase aboot
fastboot erase recovery
fastboot erase laf
fastboot flash boot 6-boot.img
fastboot flash aboot 4-boot.img
fastboot flash recovery 10-recovery.img
fastboot flash laf 11-laf.img
fastboot reboot
But now I can't seem to bring up anything and I've tried powering it on, going into recovery, and going into download mode but none of those things seem to be working. When I plug it into my computer, it makes the little sound and it's recognized but only as an E: drive with one lonely folder in it titled "image" and then I get a bunch of pop ups saying that "You need to format the disk in drive S: (and other various letters) before you can use it".
I really hope someone here can help me and that I haven't completely ruined my phone because there's no way that I have the money or means to replace it.
Click to expand...
Click to collapse
I have the same problem and haven't found an answer yet. Please let me know if you do.
arethosereal said:
I have the same problem and haven't found an answer yet. Please let me know if you do.
Click to expand...
Click to collapse
I wasn't able to fix it at all and ended up going to Sprint and getting a new phone. I basically just said it stopped charging correctly and then I woke up one morning and it wouldn't turn on. They took it as a hardware issue and I got it replaced. Thank goodness for Total Equipment Protection. I'm not sure who your carrier is, but Sprint gives two free replacements (as long as it is hardware or something similar) and then it's $25 for every replacement after that. Needless to say, I am going full stock and sticking with Nova Launcher this time around.
arethosereal said:
I have the same problem and haven't found an answer yet. Please let me know if you do.
Click to expand...
Click to collapse
You could have tried to flash stock firmware. Exactly same thing happened to me. Flashing stock firmware solved the problem.
http://forum.xda-developers.com/showthread.php?p=45293512
Te$la said:
You could have tried to flash stock firmware. Exactly same thing happened to me. Flashing stock firmware solved the problem.
http://forum.xda-developers.com/showthread.php?p=45293512
Click to expand...
Click to collapse
That's what I did. Thanks.
arethosereal said:
That's what I did. Thanks.
Click to expand...
Click to collapse
What problem did u face in flashing stock firmware?
Is your phone working now? How did u solve it?
Te$la said:
What problem did u face in flashing stock firmware?
Is your phone working now? How did u solve it?
Click to expand...
Click to collapse
I should have said I fixed the problem by flashing stock. All is ok now.
I just rooted again and am trying to figure out how to avoid the same problem, which happened when I tried to install TWRP via AutoRec. The thing is, I have the F320K version and it doesn't seem to like the custom TWRP in AutoRec. But I don't see an alternative, yet.
I'm missing something.
arethosereal said:
I should have said I fixed the problem by flashing stock. All is ok now.
I just rooted again and am trying to figure out how to avoid the same problem, which happened when I tried to install TWRP via AutoRec. The thing is, I have the F320K version and it doesn't seem to like the custom TWRP in AutoRec. But I don't see an alternative, yet.
I'm missing something.
Click to expand...
Click to collapse
Install the Autorec specific to your model. There should not be any problem cause most of us used autorec to install twrp.
Te$la said:
Install the Autorec specific to your model. There should not be any problem cause most of us used autorec to install twrp.
Click to expand...
Click to collapse
I did that, but got the white line issue and didn't see the fix from Cloudyfa until today. I guess I'll try it again, knowing I'll get the white lines. Kind of freaked me out a little.
I'll let you know after the process, tomorrow. Thanks.
Hello to everybody, so i was thinking my nakasi was really dead this time, the last thing i did was flashing a 5.1.1 rom next when i rebooted got stuck on lolipop boot loop so i restarted the tablet
manually to access the recovery, and to my awe, i couldn't no more access the recovery ! (latest twrp) tried again and again nothing, no recovery no bootloader, can't start the OS
always stuck on google logo with the options above, start, bootloader, recovery etc, today i realized i could access the bootloader and fastboot mode (ADB recognize my device when i type fastboot devices)
so i tried flashing stock image and stuff with no luck, tried many stock roms, tried wug's toolkit and the flash all.bat still no luck, i get all kind of error messages here is a screenshot, help is really appreciated if there is anything i can do to save it :
View attachment 3305126
the problem seems to be that i can't write the things i send to the tablet via ADB, tried the NVflash recovery today and got :
View attachment 3306049
Have you tried not imputing the full file address as you have the emulator already running from that location.
So recovery command would be.
Fastboot flash recovery "name of recovery Img file here"
Just make sure that the image file is in the platform-tools folder.
Probably not your issue but its going to save you some typing.
Good luck
gaosphappy said:
Have you tried not imputing the full file address as you have the emulator already running from that location.
So recovery command would be.
Fastboot flash recovery "name of recovery Img file here"
Just make sure that the image file is in the platform-tools folder.
Probably not your issue but its going to save you some typing.
Good luck
Click to expand...
Click to collapse
Thank you for the tip I'll certainly use it, but i don't think it is the culprit since as you can see in the screenshots
the files get sent successfully but cannot be written, my bootloader is unlocked by the way
Homurato said:
Thank you for the tip I'll certainly use it, but i don't think it is the culprit since as you can see in the screenshots
the files get sent successfully but cannot be written, my bootloader is unlocked by the way
Click to expand...
Click to collapse
Did you try the latest factory image? I noticed you are flashing a very old bootloader, possibly the first one? 4.23 is the current version.
Where is flatline_grouper.img coming from? I've never seen that.
adomol said:
Did you try the latest factory image? I noticed you are flashing a very old bootloader, possibly the first one? 4.23 is the current version.
Where is flatline_grouper.img coming from? I've never seen that.
Click to expand...
Click to collapse
Hello kind sir, of course at first i tried the 5.1.1 full factory image with the NRT toolkit and got the same writing errors next i tried many bootloaders
(one of them found it here as a 100% working bootloader) the Flatline is the recovery of the NVflash tool where you can access it to unbrick full bricked N7s
if you got blobs.bin of your N7 backed up (clearly not my case)
the flashing writing error i get it with everything i try to flash, recoverys bootloader system etc
when i send them with the flash all command they got sent to the tablet okay, but when writing i get the errors
i don't know but there is a small informations if that can help, before it broke my system was in EXT4 and all the rest in F2FS
It's entirely possible your memory has failed. I'm reading more and more people running into corrupted memory issues.
You can get a replacement motherboard cheap on eBay if nothing else works.
fwayfarer said:
It's entirely possible your memory has failed. I'm reading more and more people running into corrupted memory issues.
You can get a replacement motherboard cheap on eBay if nothing else works.
Click to expand...
Click to collapse
I'm still hoping for a software solution since my fastboot works fine, I'll let the motherboard solution my last i guess
Hello some news about the still staggering situations : when the tablet is off and i put the charger i get the battery refiling animation ! so that mean the bootloader isn't broken
and i still can access fastboot mode, even when i push a bootloader i get a signature match message, but the problem is still that the things i push can't be written as i'm still getting a :
FAILED <Remote: <FileWriteFailed>> changed usb cables, changed ports, the last time the tablet was working i had the system on EXT4 and the rest on F2FS, maybe if i can convert everything to EXT4 ?
Hey,
After hard bricking my Mi A1 and flashing an official android 8.0 stock rom, it is restarting every few minutes. First goes the unlock boot loader warning screen, then the mi screen and android one screen. It then goes onto the setup menu. I am able to go only to the point to enter my name. Depending on my setup speed, it becomes unresponsive at about that point, just restarts and goes back onto the lock boot loader warning screen. I tried re-locking the boot loader, but it only went to the mi screen, and again the process repeats. Please note that I can't flash a boot.img partition, says partition table doesn't exist.
**********************************************************
SOLUTION:
Place persist.img into the root of phone(not in any folder), flash twrp.img INTO THE BOOT PARTITION, and then reboot to recovery. You will see the TWRP loading screen. Go to Advanced-->Terminal--> and execute the following:
dd if=/sdcard/persist.img of=/dev/block/mmcblk0p27
And go back to Restart--> Reboot to system.
The persist should b back!
Now use Qualcomm IMEI write tool to restore your IMEI and MAC address!
Try flashing a custom ROM, then reflash Mi A1 stock OS
kvn95ss said:
Try flashing a custom ROM, then reflash Mi A1 stock OS
Click to expand...
Click to collapse
Where should I flash a custom rom from? Don't have TWRP since when I try installing TWRP, it says that recovery partition table doesn't exist.
CoolPlushBear said:
Hey,
After hard bricking my Mi A1 and flashing an official android 8.0 stock rom, it is restarting every few minutes. First goes the unlock boot loader warning screen, then the mi screen and android one screen. It then goes onto the setup menu. I am able to go only to the point to enter my name. Depending on my setup speed, it becomes unresponsive at about that point, just restarts and goes back onto the lock boot loader warning screen. I tried re-locking the boot loader, but it only went to the mi screen, and again the process repeats. Please note that I can't flash a boot.img partition, says partition table doesn't exist. Would be grateful if someone could help me!
Click to expand...
Click to collapse
seems you have corrupted the persist partition
you need to flash it again
go thru this thread maybe it can help you
https://forum.xda-developers.com/mi-a1/help/ruined-modem-partition-please-help-t3733909
Rawwr said:
seems you have corrupted the persist partition
you need to flash it again
go thru this thread maybe it can help you
https://forum.xda-developers.com/mi-a1/help/ruined-modem-partition-please-help-t3733909
Click to expand...
Click to collapse
Tried erasing and re-flashing persist.img , but get FAILED (remote: Error: This image isn't allow download
) Please help!
CoolPlushBear said:
Tried erasing and re-flashing persist.img , but get FAILED (remote: Error: This image isn't allow download
) Please help!
Click to expand...
Click to collapse
Service cente is your only hope now mate
Rawwr said:
Service cente is your only hope now mate
Click to expand...
Click to collapse
There has to be a way to manually make the persist partition writable, since the service center somehow knows how to do that...
CoolPlushBear said:
There has to be a way to manually make the persist partition writable, since the service center somehow knows how to do that...
Click to expand...
Click to collapse
nope there isnt, if you have flashed every rom available using mi flash tool hasnt solved your issue.
only hope you have is clean flash stock ROM with locked bootloader, go to service center and tell them it happened after you updated to the latest security patch.
first they will flash using EDL cable (deep flash) if that doesnt help they will replace the whole motherboard (that's how my issue was solved)
i recommend you to follow this procedure.
Rawwr said:
nope there isnt, if you have flashed every rom available using mi flash tool hasnt solved your issue.
only hope you have is clean flash stock ROM with locked bootloader, go to service center and tell them it happened after you updated to the latest security patch.
first they will flash using EDL cable (deep flash) if that doesnt help they will replace the whole motherboard (that's how my issue was solved)
i recommend you to follow this procedure.
Click to expand...
Click to collapse
Were you charged for it? I don't think they would have replaced it for free.
guy_infinity said:
Were you charged for it? I don't think they would have replaced it for free.
Click to expand...
Click to collapse
Nothing was charged not even a single penny, i just told them it started after i updated to oreo, even they said its happening because of oreo, but you gotta have a locked bootloader.
Rawwr said:
Nothing was charged not even a single penny, i just told them it started after i updated to oreo, even they said its happening because of oreo, but you gotta have a locked bootloader.
Click to expand...
Click to collapse
Oh. That's great!
Pretty sure I'm gonna try this once I corrupt my persist partition too.
guy_infinity said:
Oh. That's great!
Pretty sure I'm gonna try this once I corrupt my persist partition too.
Click to expand...
Click to collapse
Did you guys already try flashing persist thru ADB shell on pc:
dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist
guy_infinity said:
Oh. That's great!
Pretty sure I'm gonna try this once I corrupt my persist partition too.
Click to expand...
Click to collapse
haha great xD
---------- Post added at 04:55 PM ---------- Previous post was at 04:54 PM ----------
CoolPlushBear said:
Did you guys already try flashing persist thru ADB shell on pc:
dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist
Click to expand...
Click to collapse
yeah i did, i said service center guys flashed the whole ROM but that couldnt help it.
Help
Hello friend, did you manage to solve it? At this moment I am in the same problem. I appreciate you if you can help me.
Hello i've bricked my OnePlus 6T and i can't get out of fastboot mode.
When i try to boot twrp it fails with:
FAILED (remote: Failed to load/authenticate boot image: Load Error)
i have formatted everything inclusive the recovery because it wasn't booting. When i try to flash recovery and boot it, it doesn't work. I tried many tools and things that are in the internet but nothing has worked hope you guys can help me thx.
Use the MSM tool.
https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
Jager said:
Use the MSM tool.
https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
Click to expand...
Click to collapse
I've already tried using it without success because it didn't detect my device, but luckily i managed to repair my phone by changing the slots with fastboot command line tools where i still had oxygenos running.
Thanks though, how do i mark the thread as solved?
GamePro360BG said:
I've already tried using it without success because it didn't detect my device, but luckily i managed to repair my phone by changing the slots with fastboot command line tools where i still had oxygenos running.
Thanks though, how do i mark the thread as solved?
Click to expand...
Click to collapse
The MSM tool requires special drivers and your phone to be in a special boot mode, something like holding volume up while plugging it in or something.
Glad you got it fixed without the MSM tool though!
As for marking the thread solved I can't help with that unfortunately, sorry .
GamePro360BG said:
I've already tried using it without success because it didn't detect my device, but luckily i managed to repair my phone by changing the slots with fastboot command line tools where i still had oxygenos running.
Thanks though, how do i mark the thread as solved?
Click to expand...
Click to collapse
Just edit and change Title with solved in it
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