I found (on this website) an LGUP tool (version) that is for the MS330. So it works (albeit not so consistently). The LGUP tool was able to flash a .kdz file after several trials. Apparently when LGUP connects, it puts the MS330 in bootloader mode, waits 15 seconds for the device to respond and then begins flashing.
Now, here's the problem. I have a .tot file I'd like to flash. When trying to flash a .tot file, 15 seconds is not enough time for the device to respond, and I get an error for what appears to be an asynch error. That is to say, the MS330 took a second or two more that the 15 seconds to respond saying, yes I'm in bootloader mode.
Is there any way to give it a bit more time? Surely the members who use LGUP tool would have encountered this behavior, and would have found a solution.
Tried changing ports, cables, computers. No improvement
Words of wisdom, anyone?
BigZ1 said:
I found (on this website) an LGUP tool (version) that is for the MS330. So it works (albeit not so consistently). The LGUP tool was able to flash a .kdz file after several trials. Apparently when LGUP connects, it puts the MS330 in bootloader mode, waits 15 seconds for the device to respond and then begins flashing.
Now, here's the problem. I have a .tot file I'd like to flash. When trying to flash a .tot file, 15 seconds is not enough time for the device to respond, and I get an error for what appears to be an asynch error. That is to say, the MS330 took a second or two more that the 15 seconds to respond saying, yes I'm in bootloader mode.
Is there any way to give it a bit more time? Surely the members who use LGUP tool would have encountered this behavior, and would have found a solution.
Tried changing ports, cables, computers. No improvement
Words of wisdom, anyone?
Click to expand...
Click to collapse
What is going on? Wierd error/problem here.
OK! All of this above is OBE. I managed to get the bootloader unlocked, so I am now free to load custom roms. Well, sort of. I rooted the system, and tried to install TWRP from the playstore. When I got to the part about flashing recovery with the TWRP image, it fails. Just says Flash failed.
So, I went back to using adb and fastboot. I used "flashboot flash recovery TWRPfilename". That worked. Then "adb reboot recovery" took me to TWRP. So far, so good. When I shut down the phone and use the power/volume keys to boot into recovery, I get the stock rom recovery, not TWRP. If I connect the usb cable and use "fastboot reboot recovery" I get TWRP
What is going on here? Anybody who has a clue, please share your thought of the problem and/or possible fixes.
Thanks!
BigZ1 said:
What is going on? Wierd error/problem here.
OK! All of this above is OBE. I managed to get the bootloader unlocked, so I am now free to load custom roms. Well, sort of. I rooted the system, and tried to install TWRP from the playstore. When I got to the part about flashing recovery with the TWRP image, it fails. Just says Flash failed.
So, I went back to using adb and fastboot. I used "flashboot flash recovery TWRPfilename". That worked. Then "adb reboot recovery" took me to TWRP. So far, so good. When I shut down the phone and use the power/volume keys to boot into recovery, I get the stock rom recovery, not TWRP. If I connect the usb cable and use "fastboot reboot recovery" I get TWRP
What is going on here? Anybody who has a clue, please share your thought of the problem and/or possible fixes.
Thanks!
Click to expand...
Click to collapse
One more tidbit of info. I tried flashing TWRP (installed from the playstore) several times. At first all I got was Flash Failed. Now (for no apparent reason) it was able to flash the TWRP file. So I thought I'd test it out. No change. Still can't boot into recovery by using vol-and pwr. Still takes me to stock rom recovery. But (same as before) adb reboot recovery takes me right to TWRP, and it's working fine.
I am not doing any data wipes, formatting, changing permissions, etc. . Anybody have any experience with this problem, or any thoughts on how to fix it????
BTW, this is for an LG K7 MS330m1.
Related
Mods, feel free to move it it's the wrong spot!
*second update* Someone suggested using Odin to flash the files in download mode. No connections appear in Odin v3, and in Odin v1.85 nothing happens past "setupconnection". I have all of the stock .img files combined into a .tar file, placed in the PDA section. Nothing happens, it just sits like this http://i.imgur.com/oqx5T.jpg until the battery on the phone dies.
*update* Figured out the version issue was because I didn't have the host file set up properly. I did that, but whenever the updater switches from "download" to "update", it changes my phone to Recovery mode. It won't boot into recovery, just Download mode. Everything else gives the secure boot error.
Running the Bell LG Optimus LTE p930, had it on CM10 nightlies until Saturday night, when it randomly died in an update. Follow this unbricking guide: http://forum.xda-developers.com/showthread.php?t=1597488&highlight=bell Trying to do a CWM restore failed; advanced restore worked on the Boot but not on the System of the rom I had backed up.
When it booted, it came up in English, as Version 20e, apparently unrootable with SuperOneClick (I used 2.3.1, 2.3.2, and 2.3.3), so I used this guide to root it: http://www.androidauthority.com/optimus-4g-lte-p930-bell-root-android-4-0-4-update-v20e-109991/
The bootloader is still locked - trying to reboot in recovery gives this:
-----------
Secure boot error!
Cause: boot certification verify
----------
----------
Enter the fastboot...
Enter the fastboot...
Long time no see!
------------
Attempted to push the original ATT images to the phone (through the original XDA guide), everything went great until I pushed the system.img file. Screen went blank, wouldn't light up/unlock, and now any reboots give me the fastboot error.
I can't repeat any of the unbricking guides, because the LG Software tells me "Version is current, so no need to update!"
I can still get the phone into Download mode, but that's about it. Trying to boot into recovery/do a factory reset gives me the dialogue ("press power to confirm"), but then I get the fastboot issue again.
Am I boned?
liqdnitro said:
Mods, feel free to move it it's the wrong spot!
*second update* Someone suggested using Odin to flash the files in download mode. No connections appear in Odin v3, and in Odin v1.85 nothing happens past "setupconnection". I have all of the stock .img files combined into a .tar file, placed in the PDA section. Nothing happens, it just sits like this http://i.imgur.com/oqx5T.jpg until the battery on the phone dies.
*update* Figured out the version issue was because I didn't have the host file set up properly. I did that, but whenever the updater switches from "download" to "update", it changes my phone to Recovery mode. It won't boot into recovery, just Download mode. Everything else gives the secure boot error.
Running the Bell LG Optimus LTE p930, had it on CM10 nightlies until Saturday night, when it randomly died in an update. Follow this unbricking guide: http://forum.xda-developers.com/showthread.php?t=1597488&highlight=bell Trying to do a CWM restore failed; advanced restore worked on the Boot but not on the System of the rom I had backed up.
When it booted, it came up in English, as Version 20e, apparently unrootable with SuperOneClick (I used 2.3.1, 2.3.2, and 2.3.3), so I used this guide to root it: http://www.androidauthority.com/optimus-4g-lte-p930-bell-root-android-4-0-4-update-v20e-109991/
The bootloader is still locked - trying to reboot in recovery gives this:
-----------
Secure boot error!
Cause: boot certification verify
----------
----------
Enter the fastboot...
Enter the fastboot...
Long time no see!
------------
Attempted to push the original ATT images to the phone (through the original XDA guide), everything went great until I pushed the system.img file. Screen went blank, wouldn't light up/unlock, and now any reboots give me the fastboot error.
I can't repeat any of the unbricking guides, because the LG Software tells me "Version is current, so no need to update!"
I can still get the phone into Download mode, but that's about it. Trying to boot into recovery/do a factory reset gives me the dialogue ("press power to confirm"), but then I get the fastboot issue again.
Am I boned?
Click to expand...
Click to collapse
Exact same here
Secure boot error!
Im Still Working On It If I get A Fix Ill Post
ANyone else:crying:
Batesinc said:
Exact same here
Secure boot error!
Im Still Working On It If I get A Fix Ill Post
ANyone else:crying:
Click to expand...
Click to collapse
I Did A Lg Update Tool Fix Brought It Back To Life
Hi guys, after 10 hours of trying to get my P760 to life I finally, as a last resort, decided to open this threadh. Heres the deal, my friend gave me his P760 which was stuck at the boot logo, I firstly tried to fix it with LG mobile support tool but it got stuck at 15% after countless tries. Then I tried fixing it with Lg flash tool but it also gave me some errors "omap factory download fail lg p760". After that I couldnt access S/W mode anymore nor did the phone turn on, only black screen. When I connect it to my pc it just makes sounds of new device connected/disconnected. I tried this fastboot method http://forum.xda-developers.com/showthread.php?t=2292828 but couldnt make it work. Is the phone completely dead or is there anything more I can try? Any help is appreciated, thank you very much.
What was done to brick it in the first place?
Sent from my KYOCERA-C6745 using Tapatalk
I am not sure, my friend brought it to me and he didnt know the reason. Anyway I managed to get into fastboot on another computer and i tried to flash x loader and uboot with the bulit in options and i get the following error "FAILED (remote partition doesnt exist). What can I do next? Thank you for the reply.
EDIT I have tried to get the phone in S/W mode using this guide http://forum.xda-developers.com/showpost.php?p=44325657&postcount=4 but I couldnt do it.
I am sure I have to flash something in fastboot so it would be great if someone could point me to exactly what. Thanks again.
EDIT 2 I tried to flash xloader and u boot from post #7 http://forum.xda-developers.com/showthread.php?t=2242444 and it gave me the remote partition error failed again. Is the phone "officially" dead?
My experience with this phone is that it is basically unbrickable, at least software wise, thanks to omap4boot. Fastboot is basically telling you the partition you specified doesn't exist. Check you are using the correct syntax. It should be fastboot flash u-boot u-boot.img and fastboot flash x-loader x-loader.img (I am assuming the files are named u-boot.img and x-loader.img).
Another possibility is that the partition table of the phone somehow got corrupted. In my opinion this is very unlikely, but it could happen if the phone is disconnected while flashing the GTP table with LGFlashTool. Let's hope that's not the case.
Good luck.
@EdwinMoq thanks for the reply. I checked and I was using the correct syntax altough the files were named p1 and p2 both in bin format so I typed fastboot flash u-boot p1.bin and p2.bin respectively. Ive just noticed that they are from ICS and I am not sure what android version was installed prior to the brick. Can you point me where to find the JB files so I can try them if it makes any difference.
Maha23 said:
@EdwinMoq thanks for the reply. I checked and I was using the correct syntax altough the files were named p1 and p2 both in bin format so I typed fastboot flash u-boot p1.bin and p2.bin respectively. Ive just noticed that they are from ICS and I am not sure what android version was installed prior to the brick. Can you point me where to find the JB files so I can try them if it makes any difference.
Click to expand...
Click to collapse
I don't think the u and x boot version makes any difference. The fastboot script here comes with with the files for both p760 and p769. Or you can ask a p760 user with the jb boot to dump them and post it here.
EdwinMoq said:
I don't think the u and x boot version makes any difference. The fastboot script here comes with with the files for both p760 and p769. Or you can ask a p760 user with the jb boot to dump them and post it here.
Click to expand...
Click to collapse
Well using that script was the first thing I did after I couldn access S/W mode and I got the partition error, I tried both ICS and JB. Well it would be great if someone could dump their JB boot so I can try that, if it doesnt work I guess Ill throw the phone away
Maha23 said:
Well using that script was the first thing I did after I couldn access S/W mode and I got the partition error, I tried both ICS and JB. Well it would be great if someone could dump their JB boot so I can try that, if it doesnt work I guess Ill throw the phone away
Click to expand...
Click to collapse
I'm seeing you using lelus method to fastboot...
1) Be sure you are in fastboot whith this command: fastboot devices
2) if the l9 is still in lg logo, just flash a recovery img into boot and recovery partition:
a) fastboot flash boot recovery.img
b) fastboot flash recovery recovery.img3)reboot the device, it must enter in recovery mode by force.
4) once in recovery just flash a custom rom as you wish
Yes i am using lelus method and I see the device when I enter fastboot devices, the phone wont turn so there is no lg logo and I can not enter S/W mode. Where can I find the recovery.img and boot.img ?
EDIT Okay I tried this too http://forum.xda-developers.com/showthread.php?t=2585161 but when I issue the erase command it just gives me the remote partition error again. The chances that this is a hardware issue are pretty big.
Sent from my LG-D855 using XDA-Developers mobile app
A few tricks that might help:
-After a failed attempt to enter D/L mode via the volume key, force hard reset. Then switch on phone for an extra time and perform the hard reset again. This really makes a difference.
-If after unbricking the phone with a stock rom the puny LG recovery dialog resides on screen, perform the stock rom installation for a second time, phone should perform a normal boot then. Otherwise there's trouble with rooting and TWRP installation later.
-Fastboot still does not work for me(all?) in Win10, as it didn't in Win8.1,but did in Win7.
The only method to go on seems to root stock rom with Kango Root or a similar tool, then install Twrp, with Rashr or flashify.
lecorbusier said:
A few tricks that might help:
-After a failed attempt to enter D/L mode via the volume key, force hard reset. Then switch on phone for an extra time and perform the hard reset again. This really makes a difference.
-If after unbricking the phone with a stock rom the puny LG recovery dialog resides on screen, perform the stock rom installation for a second time, phone should perform a normal boot then. Otherwise there's trouble with rooting and TWRP installation later.
-Fastboot still does not work for me(all?) in Win10, as it didn't in Win8.1,but did in Win7.
The only method to go on seems to root stock rom with Kango Root or a similar tool, then install Twrp, with Rashr or flashify.
Click to expand...
Click to collapse
Thanks for the reply. How do I perform the force hard reset? Yes, I couldnt get fastboot to work on win 10, on win 7 it works flawlessly.
Sent from my LG-D855 using XDA-Developers mobile app
Hello,
I have exactly the same problem with my p760, fastboot works so far but remote partition error and the phone stays always completely black.
Is there someone who has a new idea to fix it?
Hey,
I found this: http://massimoronca.it/2016/03/17/fastboot-failed-remote-partition-does-not-exist.html
but i dont really understand it, can someone help me?
Maha23 said:
Yes i am using lelus method and I see the device when I enter fastboot devices, the phone wont turn so there is no lg logo and I can not enter S/W mode. Where can I find the recovery.img and boot.img ?
EDIT Okay I tried this too http://forum.xda-developers.com/showthread.php?t=2585161 but when I issue the erase command it just gives me the remote partition error again. The chances that this is a hardware issue are pretty big.
Sent from my LG-D855 using XDA-Developers mobile app
Click to expand...
Click to collapse
readme again... try to flash a recovery.img into the boot partition
fastboot flash boot recovery.img
and then reboot... this foce the l9 to enter in recovery and then you can fotmat partitions in wipe options
---------- Post added at 08:55 PM ---------- Previous post was at 08:52 PM ----------
Elsewhere you must need a technician with a box like octopus box to recompone ESD partitions of the L9 phone
Hard reset is 10s power.
Such a swap of recovery and kernel could have happened after unbricking the phone, when the key combo for fastboot produces the LG recovery. That's why I flash stock twice, then it's right again & ready to root, install TWRP etc.
Thanks for the help guys, I tried everything possible...I think I did, but the phone just wouldnt unbrick so it is going into parts. Thanks again.
Maha23 said:
Thanks for the help guys, I tried everything possible...I think I did, but the phone just wouldnt unbrick so it is going into parts. Thanks again.
Click to expand...
Click to collapse
you must need a technician with a box like octopus box to recompone ESD partitions of the L9 phone
puntoazul said:
fastboot flash boot recovery.img
Click to expand...
Click to collapse
Srsly?
recovery partition image on boot?
Probably true. That would explain the strange behaviour of the key combos during boot, after unbricking the phone for the first time. The recovery has replaced the kernel, but the phone can still boot. Strange. Fastboot is unavailable, and the key combo for the recovery shows the "dead droid" and performs a factory reset.
Groszexxx said:
Srsly?
recovery partition image on boot?
Click to expand...
Click to collapse
Yes... is an effective method to boot by forced on TWRP or other recovery and then proceed to format all partitions and flash any rom consecutively. After flashing any rom the boot partition is rewrited by the boot.img of the rom.
I did this before on my own L9 for repair and other friends devices. Is totally safe
By the way, I'm not in warn
I have used LGUP to install software (Nougat) and it's working fine..
I then install TWRP as normal, no issues reported during install (I can see via cmd screen).
I then proceed to reboot to recovery using methods I have been using for months, and it goes to yes, yes selection.
It then doesn't load TWRP but carries on wiping my phone to basics again.
Have tried various methods of putting TWRP on but does anyone think is something to do with Nougat as the bootloader unlocked screen is different, larger text etc
Have now tried a KDZ for marshmallow and recovery still won't go to TWRP.
It's almost like the recovery area is now not accessible?
Any suggestions please?
alienex said:
I have used LGUP to install software (Nougat) and it's working fine..
I then install TWRP as normal, no issues reported during install (I can see via cmd screen).
I then proceed to reboot to recovery using methods I have been using for months, and it goes to yes, yes selection.
It then doesn't load TWRP but carries on wiping my phone to basics again.
Have tried various methods of putting TWRP on but does anyone think is something to do with Nougat as the bootloader unlocked screen is different, larger text etc
Have now tried a KDZ for marshmallow and recovery still won't go to TWRP.
It's almost like the recovery area is now not accessible?
Any suggestions please?
Click to expand...
Click to collapse
Hmm strange. Have you tried rebooting using "adb reboot recovery" ?
I would suggest you flash recovery and boot straight into it not allowing the phone to boot into android. So flash recovery, remove battery, then try booting into recovery. Im pretty sure recovery can be lost if you boot into android before flashing SUPERSU (https://download.chainfire.eu/696/supersu/)
But i could be wrong
You have to do the following:
1) Flash the TWRP trouch Fastboot, don't reboot
2) Remove the battery, put it back, don't turn on the phone normally!
3) Use the button combination to enter in recovery
Ok have flashed again and it has "Stuck" this time after pulling battery before reboot so TWRP back!
Now to flash again and chill
Thanks both
I screwed up my phone lol, when I was updating it to oreo, I didn't know that the update.zip file was corrupted.
Now I'm stuck on
Error!
Func NO : 9 (hifi image)
Error NO : 1 (security image failed)
My version was...
STF-L09C185B170
What i tried to install that failed is...
STF-L09C185B361 (8.0.0.361)
I can still go to fastboot with everything unlocked, I can also flash a twrp recovery, but only by typing flash recovery_ramdisk(instead "recovery"), and when I try to do the update method by pressing vol up, vol down, and power, it doesnt take me to the update section, it just show me a crashed screen, then goes back to error message.
I also tried volup and power, I can't seem to go to twrp(I think booting to twrp and flashing zip files can be one of the only ways to fix this). Is there a way to go to twrp recovery using fastboot?
I've also tried flashing extracted files from update.app manually, it doesn't work. Some files can be flashed, while some can't.
Please I'm begging u guys, pls halp :crying:
also I guess the lesson here is: double check if your file is corrupted before installing/flashing
First, what is the way you took triying to update ?
(When done from system UI, official or FF, there is an integrity check of downloaded files.)
It seems you got oreo partition scheme during your failed update.
First see this guide:
https://forum.xda-developers.com/mate-8/general/fastboot-erecovery-recovery-upgrade-mode-t3543441
Try to restore using erecovery. (download and update firmware via wifi)
If not working you could use HWOTA8.
For launching recovery (stock or twrp) from bootloader type "fastboot reboot recovery".
oslo83 said:
First, what is the way you took triying to update ?
(When done from system UI, official or FF, there is an integrity check of downloaded files.)
It seems you got oreo partition scheme during your failed update.
First see this guide:
https://forum.xda-developers.com/mate-8/general/fastboot-erecovery-recovery-upgrade-mode-t3543441
Try to restore using erecovery. (download and update firmware via wifi)
If not working you could use HWOTA8.
For launching recovery (stock or twrp) from bootloader type "fastboot reboot recovery".
Click to expand...
Click to collapse
I downloaded the oreo file using a browser and installed it with HWOTA, everything got inserted into my device, but the update failed and it gave me the error when I reboot. Also I can't get to erecovery or upgrade mode(that's the crashed screen), and "fastboot reboot recovery" doesn't work, it just show me a list of commands(which I assume happens if the command is invalid).
Ok I'll try HWOTA8, but I need to configure it so it recognizes my device, only my adb recognizes it.
Do 'fastboot devices work'?
Try english hwota8.
oslo83 said:
Do 'fastboot devices work'?
Try english hwota8.
Click to expand...
Click to collapse
Nah, I figured it out, I backed up my adb folder and just merged hwota8 with it. Yes, it does work.
Btw how do I fully turn off the device? it just keeps bootlooping if i hold down the volup and power key, maybe this is the reason why I can't get into twrp recovery.
My only hope is that I can flash something on fastboot that will let me go to update mode(or erecovery) or twrp.
Like.. anything, even boot.img fails when I try to flash it. It must be stuck on oreo partition.
Also I did considered dc phoenix, but I don't have the money to pay for an account. Man, why is unbricking not free on huawei devices? That guy prolly made a fortune by now(for holding everyone with unbrick leverage lel), and it's a huge mistake for me to fiddle with a huawei device, it has so many problems with twrp and root.
If anyone can find a way to do unbrick it, like anything, that would be great.
So you didn't manage to use honor9's hwota8 ?
oslo83 said:
So you didn't manage to use honor9's hwota8 ?
Click to expand...
Click to collapse
I used it but it didn't worked, I need to be either booted in the phone's os or inside twrp recovery bec. all of the commands executed by hwota8 are adb shell, not fastboot. Like I said, I only have access to fastboot, but I'll try again tomorrow. This is taking a lot of my time and I'm having panic attacks that I may not be able to fix this lol. Oh yeah, thanks for helping out.
Note: Since Oreo, partitions names have changed ; "recovery" changed to "recovery_ramdisk" now.
Use this command to flash recovery: fastboot flash recovery_ramdisk YourStockOrTwrpRecovery.img
Use oreo stock recovery or oreo twrp.
But I thought with hwotas available for honor 9 you started from bootloader...
oslo83 said:
Note: Since Oreo, partitions names have changed ; "recovery" changed to "recovery_ramdisk" now.
Use this command to flash recovery: fastboot flash recovery_ramdisk YourStockOrTwrpRecovery.img
Use oreo stock recovery or oreo twrp.
But I thought with hwotas available for honor 9 you started from bootloader...
Click to expand...
Click to collapse
I already did that, read the OP. Like I said, I can't boot into any recovery, not twrp not stock, not even upgrade mode, nothing.
As for hwota8, nope, it doesnt start from the bootloader, it's already trying to use the adb shell commands.
Anyway I'm taking all chances, I'm trying to research oreo's partitions names, and I'm also trying to find out how to bypass this message "FAILED (remote: Command not allowed)" bec. it might be the only way I can salvage this phone.
edit: ok im trying hwota8 again, maybe i missed something, and yes it has fastboot, sorry i was rushing but im trying again now, i'll post my progress later
I recently bought an unlocked Moto G Play 2021 with the intent of learning how to flash custom rom's etc. The steps I've done so far are below.
Went to Motorola's site and got the code to unlock the bootloader
Waited for the "OEM Unlock" button to be available in the Developer Options menu.
Followed the directions Here to try to get an unofficial version of TWRP installed.
when I type fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img Using the vbmeta.img from the link above, I get some kind of anti-rollback error and can't boot to recovery.img
So far, what I've found says I need to be on Android 10 for this to work but I can't find a stock rom of Android 10 for this device. Electimon posts AOSP builds for this phone Here so I assume there's a way to get this to work, I just don't know what it is and I've gone through these threads a few times now and can't piece it together. Any assistance would be greatly appreciated.
Additionally, thanks Electimon for doing those AOSP builds.
Try to download Miracle Thunder Modified (Withouth Box) like there are other tools, but if not, just try to root. kind of for you to root, download the TWRP app and install or use Flashify to flash img using root
Luiz Vinicius said:
Try to download Miracle Thunder Modified (Withouth Box) like there are other tools, but if not, just try to root. kind of for you to root, download the TWRP app and install or use Flashify to flash img using root
Click to expand...
Click to collapse
I'm not sure entirely what happened, but after I used the TWRP app my phone bricked and I had to use the Lenovo rescue app on my pc to factory reset it.
First update your phone
Then download twrp from
https://forum.xda-developers.com/t/...st-port-but-everything-works-amazing.4330775/
Then adb reboot bootloader
Then fastboot flash recovery MotoGuamnaFixed2.img
then you have twrp installed then you can go thru the steps at
https://forum.xda-developers.com/t/rom-12-0-guamna-aosp-12-0-monthly-builds.4392303/#post-86610039
to get Android 12 couatom rom
svoc said:
First update your phone
Then download twrp from
https://forum.xda-developers.com/t/...st-port-but-everything-works-amazing.4330775/
Then adb reboot bootloader
Then fastboot flash recovery MotoGuamnaFixed2.img
then you have twrp installed then you can go thru the steps at
https://forum.xda-developers.com/t/rom-12-0-guamna-aosp-12-0-monthly-builds.4392303/#post-86610039
to get Android 12 couatom rom
Click to expand...
Click to collapse
Thank you for the response!
I made sure my phone was on wi-fi and checked for updates. I then rebooted to fastboot and flashed recovery to the MotoGuamnaFixed2.img. I still got a blank screen when I tried to reboot to recovery. I then rebooted to fastboot manually and did
fastboot flash recovery_a MotoGuamnaFixed2.img
fastboot flash recovery_b MotoGuamnaFixed2.img
It said ok both times, and when I try to reboot to recovery, I get a blank screen that I can't interact with. Pressing the power and volume buttons does nothing. Rebooting and letting the phone go through the boot process, to include waiting for the warning about the unlocked bootloader to go away results in a blank screen.
I also tried booting to fastboot and selecting "Recovery Mode" from the fastboot menu. Same result. That being said, I followed the instructions in the second link anyway, which are
fastboot -w
fastboot update (filename).zip
Now my phone has a blank screen I cannot interact with, but when I type "adb devices" I see the phone. Typing "adb shell ls -l" shows there is definitely a file structure there.
Just download the rom for the version that your device is unzip it and manual flash each one to the correct spot except recovery flash the twrp and then reboot and let me know look at flash file.xml to see where to flash each IMG and bin to make shur you download your rom and not another one for the same device but different carrier what it sounds like to me is happening is you downloaded the wrong ROM when you tried to do a force update
Send me a screenshot of your about device screen please I might need to make a change to a few things to get it working
I'm stuck in a boot loop right now. WIll the output from fastboot getvar work?
What carrier do you have
Download your rom first then follow my last post to get it back out of a bootloop
svoc said:
What carrier do you have
Click to expand...
Click to collapse
It's an unlocked phone, no carrier, no SIM. I did the factory reset with the Lenovo rescue tool and sent you the screen shot of the device info page.
Update - svoc has spent a crap ton of his personal time trying to help me with this. I've learned a bunch and wanted to publicly acknowledge his willingness to go way above and beyond trying to get this working.
I don't understand why I can't get twrp to boot I'm not for shut what the problem is if any one has any idea please let me and I will try
Big thanks to svoc for all the phone calls and troubleshooting my device, that is apparently possessed by at least 3 demons and a donkey. There are two links below. The first is the link to the intstructions that worked.
The second is to the compressed file that gave me a degoogled android. It's really, really basic and you'll have to side load the app store of your choice onto the device but it works.
*NOTE* I have not used a sim card or tested the cellular capability. If you do the things below and it doesn't work, reboot to bootloader and flash the radio.img with the one from your stock rom, which can be obtained from lolinet.
Any custom ROMs out there for Moto g play 2021 (guamna)?
Can't find any custom ROMs for this device. I guess it is too early. I'll probably have to get another phone. Can't even find a twrp for it. New to this. Any suggestions?
forum.xda-developers.com
https://github.com/phhusson/treble_experimentations/releases/download/v412/system-squeak-arm64-ab-vanilla.img.xz