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.
So I recently grabbed me a Grouper recently to *cough* remember my first Android powerhouse (before I met the Optimus G) and decided to tinker with it as usual. I've owned 6 (now 7) different Groupers in this lifetime and have great experience with it, how to get those pesky drivers working, etc. This is my first 32GB model ever. Anyways, I unlocked the BL, rooted and flashed TWRP (thanks to WugFresh's toolkit) and decided to play with the newer roms (last time I owned one, KitKat was a rumor) and kernel combos. Anyways, I decided I prefer its stock performance and battery, and that maybe I'd use Xposed to tweak apperance instead. My mistake was, I should have flashed a flashable stock rom. But NOOOOO...I decided to flash it back to stock with the fastboot method (which we have various threads on, and toolkits including WugFresh's). Trying the manual method, I followed the following guide using a 4.4 image zip file:
http://forum.xda-developers.com/showthread.php?t=1907796
Claims that the sysem.img doesnt exist when it gets to that part. I extracted the entire file and it DOES exist. Anyways, I tried WugFresh's tk and sort of gives me the same ending (after literally almost an hour of waiting TWICE due to my old PC).
THERE WAS A GUIDE I SAW SOMEWHERE while Googling "how to" get back to stock on Google which actually point ou how to MANUALLY flash each .img yourself one by one via fastboot, which I really intended on doing instead of the above methods (DIY anyone?) but I can't find that guide and I'm not even sure if the post was here on XDA or Android Central. I should have done all Google search on the PC instead but ATM the tablet seemed more convenient for a search.
Anybody know the guide I am mentioning or know what I am talking about? I am assuming that method will solve my dilemma, and I like doing these things manually at times anyways....
EDIT: To my disappointment, found the post, but no good:
http://www.androidbeat.com/2013/11/flash-factory-image-nexus-device/
Apperantly everything flahes fine until it gets to the system.img part...adb/fastboot just freezes there and wont budge at all. Since I noticed that it did flash things, I've decided to flash TWRP and just flash a rom from my flash drive (thanks to a USB OTG) but I would still like to actually FIX the thing properly and return it 100% stock. Any ideas?
Crossvxm said:
I should have flashed a flashable stock rom. But NOOOOO...I decided to flash it back to stock with the fastboot method
Click to expand...
Click to collapse
I'm not sure what you mean by stock. Are you trying to flash a "Stock" rom from the community or the stock images provided by google?
If you are using nakasi-ktu84p image, the flash script contains:
Code:
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
sleep 10
fastboot -w update image-nakasi-ktu84p.zip
You can see here the exact process of getting back to stock.
The boot, cache, recovery, system, and userdata are erased.
Then an attempt to flash the bootloader. This will fail on nakasi-ktu84p and several images back.
Google has been negligent in addressing this issue.
I was able to find success with bootloader-grouper-4.23.img which I extracted from nakasi-krt16s.
You could save time and bandwidth from acquiring it here.
This bootloader also failed to flash for me!
If you have flashed a custom bootloader in the past, you may need to go all the way back to JDQ39 bootloader-grouper-4.18.img.
fastboot flash that, and then you will be able to flash 4.23 from krt16s.
Once you have passed this small ordeal you should be able to install the latest ROM.
In summary, you should be able to do the following from a system that has the fastboot binary:
Code:
EXTRACT nakasi-ktu84p-factory-76acdbe9.tgz
OVERWRITE bootloader-grouper-4.23.img with one acquired from krt16s
Code:
nakasi-ktu84p bootloader-grouper-4.23.img
MD5 = 5bdb2e87370cdb1a7ea14bb0c3e21390
krt16s bootloader-grouper-4.23.img
MD5 = df53028033c9eccf4fe5ba7bc198ce24
Code:
run flash-all.sh or flash-all.bat
PS.
I have been lured by the idea of stock stability, performance, and battery life. Something about Xposed seems dirty to me.
Battery life and Performance have always been better on a custom ROM / Kernel in my experience.
Stability can be rock solid when you've got a good system.
My favourite solution is to have the stock image installed and stripped down for size. This always you to boot in and update your apps from playstore.
I then install a custom ROM alongside via multiRom. This rom also has extras stripped out and no gapps installed.
From Rom 1 you can copy your apks into Rom 2 as needed.
I tend to avoid any apps that would be incompatible with this method!
crache said:
I'm not sure what you mean by stock. Are you trying to flash a "Stock" rom from the community or the stock images provided by google?
If you are using nakasi-ktu84p image, the flash script contains:
Code:
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
sleep 10
fastboot -w update image-nakasi-ktu84p.zip
You can see here the exact process of getting back to stock.
The boot, cache, recovery, system, and userdata are erased.
Then an attempt to flash the bootloader. This will fail on nakasi-ktu84p and several images back.
Google has been negligent in addressing this issue.
I was able to find success with bootloader-grouper-4.23.img which I extracted from nakasi-krt16s.
You could save time and bandwidth from acquiring it here.
This bootloader also failed to flash for me!
If you have flashed a custom bootloader in the past, you may need to go all the way back to JDQ39 bootloader-grouper-4.18.img.
fastboot flash that, and then you will be able to flash 4.23 from krt16s.
Once you have passed this small ordeal you should be able to install the latest ROM.
In summary, you should be able to do the following from a system that has the fastboot binary:
Code:
EXTRACT nakasi-ktu84p-factory-76acdbe9.tgz
OVERWRITE bootloader-grouper-4.23.img with one acquired from krt16s
Code:
nakasi-ktu84p bootloader-grouper-4.23.img
MD5 = 5bdb2e87370cdb1a7ea14bb0c3e21390
krt16s bootloader-grouper-4.23.img
MD5 = df53028033c9eccf4fe5ba7bc198ce24
Code:
run flash-all.sh or flash-all.bat
PS.
I have been lured by the idea of stock stability, performance, and battery life. Something about Xposed seems dirty to me.
Battery life and Performance have always been better on a custom ROM / Kernel in my experience.
Stability can be rock solid when you've got a good system.
My favourite solution is to have the stock image installed and stripped down for size. This always you to boot in and update your apps from playstore.
I then install a custom ROM alongside via multiRom. This rom also has extras stripped out and no gapps installed.
From Rom 1 you can copy your apks into Rom 2 as needed.
I tend to avoid any apps that would be incompatible with this method!
Click to expand...
Click to collapse
Your on the right track that's exactly what I was looking for, but to me it doesn't work on the system.img flashing part, it stays stuck there forever without a hint of movement at all. I left it flashing from 4am to 7am with no progress. I though it was working as the Windows Task Manager was showing fast boot constantly changing in CPU usage as it does when its at work. But sadly, it gets stuck there for good. Then closing fast boot won't work, I have to shut down the PC in order for it to leave
Crossvxm said:
Your on the right track that's exactly what I was looking for, but to me it doesn't work on the system.img flashing part, it stays stuck there forever without a hint of movement at all. I left it flashing from 4am to 7am with no progress. I though it was working as the Windows Task Manager was showing fast boot constantly changing in CPU usage as it does when its at work. But sadly, it gets stuck there for good. Then closing fast boot won't work, I have to shut down the PC in order for it to leave
Click to expand...
Click to collapse
I'm not familiar with the tools you are using. Have you used the commands directly from the command line, and what is the output?
crache said:
I'm not familiar with the tools you are using. Have you used the commands directly from the command line, and what is the output?
Click to expand...
Click to collapse
WugFresh is a toolkit made to root, unlock boot loader, relock, restore to stock, etc. And yeah I used the fastboot erase and fastboot flash commands via ADB/fast boot and as I said, everything goes well except the part where its time to flash the system.img, it just hangs there doing nothing. Tried and left it for several hours and still nothing
Try a different USB port on you computer or a different USB cable... or both.
Crossvxm said:
...
....it doesn't work on the system.img flashing part, it stays stuck there forever without a hint of movement at all.
...
Click to expand...
Click to collapse
Hi, Crossvxm...
This seems to be a relatively common problem, and I always seem to have it myself when fastboot flashing factory stock.
I've no idea why, but the fastboot connection seems to 'time-out' when fastboot flashing 'system.img'.
Now normally, and just prior to running any fastboot flash commands, you should run this command...
Code:
fastboot devices
This command doesn't actually do anything; it's essentially just diagnostic and is used to confirm you have a viable fastboot connection prior to flashing anything. If do you have a fastboot connection, you should see something like this (with the N7 booted into the bootloader)...
Code:
015d2d42xxxxxxxx fastboot
This is the Nexus 7's unique serial number followed by the word 'fastboot'. If you don't see this, then you likely have a driver problem...
...BUT HOWEVER, I KNOW I DON'T HAVE A DRIVER PROBLEM.. so when having problems with 'sending system', and upon opening a second command prompt window on my Windows laptop, and typing fastboot devices again, the Nexus 7's serial number now no longer appears... and this is AFTER the bootloader and boot img's have been sent and written successfully.
At this point, I can only conclude, and that for unknown reasons, my fastboot connection has 'died'... and 'sending system' is now permanently 'stuck'.
And the fastboot flash attempt has failed.
-----------------------------------------------------
The solution for me, was to change to a different USB port on my laptop. Another possibility might be to try a different USB cable... I haven't tried this... just a change of USB port on my laptop was sufficient, and the problem with flashing system.img was resolved.
Either way, reboot the N7's bootloader using a differerent USB port on your computer or a different USB cable... and attempt the flash again.
One final point... 'sending system' does take longer than the other .img's, probably due to it's size... but it really should take no longer than around 5 minutes... 10 minutes maximum.
Hope this helps... and good luck.
Rgrds,
Ged.
Hi everyone,
tonight I was trying to install the Stagefright OTA using this guide: http://forum.xda-developers.com/moto-x/general/xt1053-222-27-5-stagefright-ota-update-t3210786
The only thing I got was an android with a red triangle on it. So I went back, did a total phone reset, reinstalled the TWRP (fastboot flash twrp.img) and restored my backup. Sadly, the phone keeps rebooting to the TWRP as if there's nothing on it except the TWRP.
I've got the eu model and I can't find any factory image (or image in general) to flash on the device.
EDIT:
I manage to get something to work by simply boot via the "BT Tools" fastboot menu voice.
I don't exactly know why, but this way I manage to boot on a clean Android install and then restore my TWRP backup.
There's just a little problem: if I boot normally the system goes straight to the TWRP and won't boot.
I always need to go in the fastboot menu and select "BT Tools".
i was going through a similar reboot process last night. I realized that my issue was that I had xposed installed and had to uninstall it. however, I realized that after I wiped internal storage.
thus, my solution was to wipe everything (cache, dalvik, data, & internal storage), then mfastboot the stock ROM, then flash TWRP, then restore nandroid.
however, make sure to copy your nandroid to your computer first - you can transfer it back to the phone after flashing TWRP. you may have to perform a small nandroid via TWRP just to setup the right folder names, but you can still transfer the nandroid folder to your phone while the phone is in recovery.
hope this helps.
jco23 said:
i was going through a similar reboot process last night. I realized that my issue was that I had xposed installed and had to uninstall it. however, I realized that after I wiped internal storage.
thus, my solution was to wipe everything (cache, dalvik, data, & internal storage), then mfastboot the stock ROM, then flash TWRP, then restore nandroid.
however, make sure to copy your nandroid to your computer first - you can transfer it back to the phone after flashing TWRP. you may have to perform a small nandroid via TWRP just to setup the right folder names, but you can still transfer the nandroid folder to your phone while the phone is in recovery.
hope this helps.
Click to expand...
Click to collapse
First of all, thanks for your reply.
I manage to get something to work by simply boot via the "BT Tools" fastboot menu voice.
I don't exactly know why, but this way I manage to boot on a clean Android install and then restore my TWRP backup.
There's just a little problem: if I boot normally the system goes straight to the TWRP and won't boot.
I always need to go in the fastboot menu and select "BT Tools".
Any hint on why this is happening?
edmael said:
First of all, thanks for your reply.
I manage to get something to work by simply boot via the "BT Tools" fastboot menu voice.
I don't exactly know why, but this way I manage to boot on a clean Android install and then restore my TWRP backup.
There's just a little problem: if I boot normally the system goes straight to the TWRP and won't boot.
I always need to go in the fastboot menu and select "BT Tools".
Any hint on why this is happening?
Click to expand...
Click to collapse
you could be missing this line: mfastboot getvar max-download-size
I used the guide here: http://forum.xda-developers.com/moto-x/general/xt1060-lollipop-5-1-ota-fxz-thread-t3139519
granted, you appear to have a different model than mine, but the process should be the same.
jco23 said:
you could be missing this line: mfastboot getvar max-download-size
I used the guide here: http://forum.xda-developers.com/moto-x/general/xt1060-lollipop-5-1-ota-fxz-thread-t3139519
granted, you appear to have a different model than mine, but the process should be the same.
Click to expand...
Click to collapse
Yes, I skipped that line and removed it from the .xml of the images I flashed because I found some guides that suggested it.
Now I'm really tempted to re-flash everything using that command first.
edmael said:
Yes, I skipped that line and removed it from the .xml of the images I flashed because I found some guides that suggested it.
Now I'm really tempted to re-flash everything using that command first.
Click to expand...
Click to collapse
All removing that line does is prevent the system partition from error-ing out during the flashing process, which is why it's suggested to remove the line if you are using RSD-Lite to flash an image
mastarifla said:
All removing that line does is prevent the system partition from error-ing out during the flashing process, which is why it's suggested to remove the line if you are using RSD-Lite to flash an image
Click to expand...
Click to collapse
I flashed it using the -P option so I guess it's just the same as using that line, right?
Also: the removal of that line was not only in your guide so I immediatly deleted it
edmael said:
I flashed it using the -P option so I guess it's just the same as using that line, right?
Also: the removal of that line was not only in your guide so I immediatly deleted it
Click to expand...
Click to collapse
Flashing with mfastboot with the -P option is the same, you can verify the option exists by just typing in mfastboot in the command line, it will show you all the commands and what they do
I didn't want to have people dependent on using RSD-Lite (or any particular program) to flash the System Image, as it then makes a Windows machine the only thing possible to flash this image plus it uses Internal Moto Only software (legal issues), so I tried to find a better way to make mfastboot work properly for all types of computers
another thing I have noticed is that my phone kept getting stuck on the boot image screen (failed to proceed to the boot animation screen). to resolve this, I made sure to flash SU via TWRP after flashing my ROM via TWRP (or restoring a nandroid).
mastarifla said:
Flashing with mfastboot with the -P option is the same, you can verify the option exists by just typing in mfastboot in the command line, it will show you all the commands and what they do
I didn't want to have people dependent on using RSD-Lite (or any particular program) to flash the System Image, as it then makes a Windows machine the only thing possible to flash this image plus it uses Internal Moto Only software (legal issues), so I tried to find a better way to make mfastboot work properly for all types of computers
Click to expand...
Click to collapse
I really appreciated that (proud Linux User here), I tried mfastboot on Linux and even RSD-Lite on my Windows machine, but both of them failed to get my phone working with the files you provided in the other thread.
Now I'm stuck with this problem: every boot I need to select BT Tools and wait some minutes for my phone to boot.
I still don't get why it only boot in TWRP and I still don't get how to fix this
edmael said:
I really appreciated that (proud Linux User here), I tried mfastboot on Linux and even RSD-Lite on my Windows machine, but both of them failed to get my phone working with the files you provided in the other thread.
Now I'm stuck with this problem: every boot I need to select BT Tools and wait some minutes for my phone to boot.
I still don't get why it only boot in TWRP and I still don't get how to fix this
Click to expand...
Click to collapse
you may need to wipe internal storage and mfastboot everything from scratch...
jco23 said:
you may need to wipe internal storage and mfastboot everything from scratch...
Click to expand...
Click to collapse
Already did that (the first time I didn't even tried booting with BT Tools, but the effects were the same), but nothing new happened.
edmael said:
I really appreciated that (proud Linux User here), I tried mfastboot on Linux and even RSD-Lite on my Windows machine, but both of them failed to get my phone working with the files you provided in the other thread.
Now I'm stuck with this problem: every boot I need to select BT Tools and wait some minutes for my phone to boot.
I still don't get why it only boot in TWRP and I still don't get how to fix this
Click to expand...
Click to collapse
Have you tried flashing the TWRP System Backup that I provided? It may fix the issue that you are seeing currently
mastarifla said:
Have you tried flashing the TWRP System Backup that I provided? It may fix the issue that you are seeing currently
Click to expand...
Click to collapse
Yes, tried, but nothing happens (except that it boots when I go into BT Tools).
I think there's something wrong with my partition scheme because it always go straight to TWRP.
If I were on a GNU/Linux distro I'd check the grub config because it seems it boot from the wrong partition, but on Android I don't know if/how that's possible.
does it boot up when you flash the stock recovery? perhaps you may need to let it boot up first before installing TWRP?
did you happend to type "mfastboot flash boot twrp.img"? that could be the issue, as the command should be "mfastboot flash recovery twrp.img, right?
sorry I can't be more helpful, as I'm sure this is frustrating for you. just trying to grasp at straws here....
jco23 said:
does it boot up when you flash the stock recovery? perhaps you may need to let it boot up first before installing TWRP?
sorry I can't be more helpful, as I'm sure this is frustrating for you. just trying to grasp at straws here....
Click to expand...
Click to collapse
Don't be sorry, you're helping me!
Also: I'm not much frustrated since I have a working phone right now, I just need do avoid rebooting it
I tried to flash the stock recovery (found here: http://forum.xda-developers.com/moto-x/general/official-collection-firmwares-fxz-sbf-t3146628, used this: XT1052_GHOST_RETEU_5.1_LPA23.12-15_cid7_CFC.xml.zip) but if I'm not wrong (did that yesterday in the late night) it just booted to the Android with the red triangle on it (so, no booting for me).
EDIT:
No, I don't think I did that. But let's suppose I did, how can I revert it?
Also: is there a way to see my partition scheme so I'm sure everything's fine?
edmael said:
Don't be sorry, you're helping me!
EDIT:
No, I don't think I did that. But let's suppose I did, how can I revert it?
Also: is there a way to see my partition scheme so I'm sure everything's fine?
Click to expand...
Click to collapse
You can revert it by taking the boot.img from the 5.1 zip and flashing that using the command...
mfastboot flash boot boot.img
The partitioning you are mentioning is probably the gpt.bin, but that is typically done near the very beginning of the flashing process
here's what I would do:
boot into recovery
connect phone to PC, copy your nandroid and any other files from the SDcard to your PC
within recovery, wipe cache/dalvik/data/internal storage
reboot to bootloader
run the mfastboot commands as shown (but use the getvar-download....) in place of editing the xml zip file
after running the mfastboot commands, let the phone boot up to stock and establish itself
reboot to bootloader and flash TWRP
again, just a suggestion on what I would do - seems like @mastarifla is a great resource and is more knowledgeable than me, so maybe you'll get some confirmation.
good luck!
Ok, I still haven't solved this issue.
I tried with re-flashing everything, but I still get the problem.
I think it's a problem with the partition scheme because even by flashing just partition gpt.bin and motoboot.img when I launch reboot-bootloader it reboot the phone into TWRP.
I think the TWRP is in the wrong partition and/or I've got a wrong partition scheme, but I don't know how to check it or how to fix it.
edmael said:
Ok, I still haven't solved this issue.
I tried with re-flashing everything, but I still get the problem.
I think it's a problem with the partition scheme because even by flashing just partition gpt.bin and motoboot.img when I launch reboot-bootloader it reboot the phone into TWRP.
I think the TWRP is in the wrong partition and/or I've got a wrong partition scheme, but I don't know how to check it or how to fix it.
Click to expand...
Click to collapse
So your phone thinks that the bootloader is your recovery?
That is actually pretty strange, you could take a look at the Linux kernel on Motorola's GitHub and see if it has any info on the partitioning structure or what happens when a reboot-bootloader command is sent to the phone
It sounds as if the recovery and the bootloader swapped places, as the fastboot menu is considered a part of the bootloader, and if you are not seeing that on the hardware key bootup, then there is something definitely wrong, if you do reboot-recovery does it take you to the bootloader/fastboot menu?
After accidentally and stupidly update the latest official Android update the cell keeps rebooting in TWRP.
I can temporarily solve the issue going to bootloader and choose start or factory mode but when I turn off the phone it goes back to TWRP.
What can I do? I don’t mind deleting everything cos I have everything backed up.
Any idea or suggestion is highly appreciated. Thanks in advance, Joe!
Joe2090 said:
After accidentally and stupidly update the latest official Android update the cell keeps rebooting in TWRP.
I can temporarily solve the issue going to bootloader and choose start or factory mode but when I turn off the phone it goes back to TWRP.
What can I do? I don’t mind deleting everything cos I have everything backed up.
Any idea or suggestion is highly appreciated. Thanks in advance, Joe!
Click to expand...
Click to collapse
>Reboot into bootloader
>get adb/fastboot setup
>use below commands
* Fastboot oem fb_mode_set
* Fastboot oem fb_mode_clear
You need to try this code few more times if doesn't work for first time.
If this command doesn't work for you (even after using many times) then there is no other way than flashing complete stock ROM.
____Mdd said:
>Reboot into bootloader
>get adb/fastboot setup
>use below commands
* Fastboot oem fb_mode_set
* Fastboot oem fb_mode_clear
You need to try this code few more times if doesn't work for first time.
If this command doesn't work for you (even after using many times) then there is no other way than flashing complete stock ROM.
Click to expand...
Click to collapse
Thaks for your help! Unfortunately it didnt work.
Where can I get the latest flashable stock through TWRP for moto g4 plus?
Joe2090 said:
Thaks for your help! Unfortunately it didnt work.
Where can I get the latest flashable stock through TWRP for moto g4 plus?
Click to expand...
Click to collapse
As strongst has said you in another thread,
You can't flash Stock ROM through TWRP, stock firmware is flashable only by fastboot method.
And for your problem, TWRP flash (of custom or stock modified) will not work, you need to flash complete ROM by fastboot method.
It will erase your data, so take backup of internal memory.
Follow this [ https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138 ]
Thread, and keep your discussion to only one thread, don't use multiple thread for same question.
I apologize for the multithread post, it was no my intension…
Hope you have read the other post since I couldn’t get it connected to my PC through USB, fastboot can’t see the device and I can’t enter the phone, it keeps going into TWRP.
I finally solved the problem!!!
I just want to say thank you for your help and other people from the forum. I hope it can help others in the same situation.
Everybody can find the solution here
https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138
Best regards!!1 Joe.
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