I'm trying to flash twrp.I have gone step by step I can't think of anything that I forgot to do, I did everything that was mentioned here and other places even my device is detected in both adb & fastboot.but I can't flash twrp
I tried these:
1-adb devices
returned a serial number
2-rebooted to bootloader using:
adb reboot bootloader
3-fastboot devices
returned device id(I think)
4-fastboot flash recovery.img
returned error
5-fastboot flash recovery recovery.img
returned error either "command not allowed" or "Operation is not permited"
6-Different combinations of above commands plus flashing command
What is flashing .... in fastboot.It doesn't work. It acts like an unknown command. Does anyone know how to use it correctly? Help of fastboot didn't help
(Attached screenshots=CMD:Command Line in Windows,SCL-U31:My phone screen in fastboot mode)
See it for yourself in screenshot please
Thanks in advance!
P.S I read a lot of other threads,I Couldn't Find anything that helped me solving the problem,So,Any further idea?
No luck still
Guys I'm tryings to flash an stupid twrp recovery or at least get back to original recovery(All firmware packages are in UPDATE.app format and I can't flash it since It says "recovery image verification failed) . System needs its original recovery to do factory reset,right?
Tell me where to go!!!
Any luck? At least please tell me where to go!! I even mentioned it in a lot of other related xda threads they simply tell me it's a stupid OFF Topic replay or thread. I might be a junior member in xda but it's been years that I worked with a lot of phones and now I'm pretty experienced. Bad luck of mine I damaged my note 3 and got this stupid Y6. It was hard to root unlocking bootloader and now I can't flash twrp in fastboot or whatever. Wishing there was a proper tool like odin for devices like this so it was easy to flash twrp. Anyway.
HELP ME PLEASE!!
flightover588 said:
Any luck? At least please tell me where to go!! I even mentioned it in a lot of other related xda threads they simply tell me it's a stupid OFF Topic replay or thread. I might be a junior member in xda but it's been years that I worked with a lot of phones and now I'm pretty experienced. Bad luck of mine I damaged my note 3 and got this stupid Y6. It was hard to root unlocking bootloader and now I can't flash twrp in fastboot or whatever. Wishing there was a proper tool like odin for devices like this so it was easy to flash twrp. Anyway.
HELP ME PLEASE!!
Click to expand...
Click to collapse
What error gave you when you tried to do this command "fastboot flash recovery twrp.img"
Be sure to have usb debugging enabled.
Thespartann said:
What error gave you when you tried to do this command "fastboot flash recovery twrp.img"
Be sure to have usb debugging enabled.
Click to expand...
Click to collapse
Of course I did. And also device is being detected in both adb and fastboot.
As I already mentioned I used flash recovery recovery.img(or twrp.img I have two versions of recovery that I can flash)
The error is=remote operation is not allowed or sometimes operation is not permitted(which seems to have same meaning )
flightover588 said:
Of course I did. And also device is being detected in both adb and fastboot.
As I already mentioned I used flash recovery recovery.img(or twrp.img I have two versions of recovery that I can flash)
The error is=remote operation is not allowed or sometimes operation is not permitted(which seems to have same meaning )
Click to expand...
Click to collapse
OK then.
You can root your device with kingroot/kingoroot, it worked in the past for Huawei Y6, after you rooted your device install flashify and press on "Recovery image" after you granted root access to the app.After that click on select file, download this recovery for y6: https://www.androidfilehost.com/?fid=962187416754472815 and flash the recovery with Flashify.
Done!
I am not responsible for Bricked devices!
After you done all of that you can flash an custom ROM and I recommend to root with magisk. Always make an backup when flashing a ROM!
If I helped a Thanks is appreciated
Thespartann said:
OK then.
You can root your device with kingroot/kingoroot, it worked in the past for Huawei Y6, after you rooted your device install flashify and press on "Recovery image" after you granted root access to the app.After that click on select file, download this recovery for y6: https://www.androidfilehost.com/?fid=962187416754472815 and flash the recovery with Flashify.
Done!
I am not responsible for Bricked devices!
After you done all of that you can flash an custom ROM and I recommend to root with magisk. Always make an backup when flashing a ROM!
If I helped a Thanks is appreciated
Click to expand...
Click to collapse
You uploaded a twrp recovery on AFH just for me? Thank you,man!I appreciate your help. I really do! But Believe it or not I already tried flashify,Rashr and flashfire. These three cause same thing,when I reboot to recovery it says "recovery image verification failed"Then quickly goes to fastboot&rescue mode where I can't still flash twrp using flash command. Referring to firstb post
flightover588 said:
You uploaded a twrp recovery on AFH just for me? Thank you,man!I appreciate your help. I really do! But Believe it or not I already tried flashify,Rashr and flashfire. These three cause same thing,when I reboot to recovery it says "recovery image verification failed"Then quickly goes to fastboot&rescue mode where I can't still flash twrp using flash command. Referring to firstb post
Click to expand...
Click to collapse
Not nice to hear that.
What you could try to do is:
Factory reset/Install an update.app made for SCL-U31 from recovery
Enable Usb debugging again
Reinstall usb drivers (HiSuite)
Lock&Unlock your bootloader again
Try to flash TWRP
Im happy if this worked and i am sorry if i wasted your time, sometimes this happens if you don't have HiSuite installed.
You could try this too:
adb reboot bootloader
adb kill-server
fastboot flash recovery recovery.img
fastboot reboot
Attention, install HiSuite to your PC, Connect the Phone to the PC with the cable, make sure You have usb debbuing is enabled and accept any dialogs that show in your home screen(They do not show on lockscreen) wait so HiSuite installs on the phone(An dialog should show up on the PC) and try flashing TWRP again.
Good luck
flightover588 said:
Guys I'm tryings to flash an stupid twrp recovery or at least get back to original recovery(All firmware packages are in UPDATE.app format and I can't flash it since It says "recovery image verification failed) . System needs its original recovery to do factory reset,right?
Click to expand...
Click to collapse
Is your boatloader unlocked?
You can find about by typing
fastboot oem devices-info
Related
OK, so I was rolling along just fine...
Got Fastboot up and running, got myself an unlocked bootloader, got myself the latest TWRP image, and no matter WHAT I DO, I can not get TWRP to flash to my device, and it is driving me absolutely INSANE. Below is what i am getting from command prompt. Any help is GREATLY appreciated.
Code:
C:\Users\saltam\Downloads\TWRP>fastboot flash recovery recovery.img
sending 'recovery' (13186 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.000s
I am pulling what little hair I have out over here, and I am no beginner when it comes to this stuff. Please help if you can.
Only a couple of things I can think, which I'm sure you've already done. Have you re-downloaded the image file and you have renamed it recovery.img?
Edit, is your bootloader unlocked?
Sent from my Nexus 5 using XDA Free mobile app
Boot loader is unlocked, tried everything besides a different computer. Tried different cord, different USB port, everything. It's like once I unlocked the boot loader the tablet stopped communicating with fast boot. Anything I try to do hangs until I hit reboot fast boot then it fails. Irritating the hell out of me...
have you tired using the wugs Nexus root toolkit? http://forum.xda-developers.com/nexus-9/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2945451
I was having some trouble TWRP installing as well., and it was able to install TWRP just fine
Close any other running programs, especially Chrome. Then if still not doing it, install CWM Recovery instead, and if you still want TWRP flash it from CWM Recovery.
My N5 won't let me have TWRP, so if you just want the functions of a recovery, try a different one.
blakeslee14 said:
have you tired using the wugs Nexus root toolkit? http://forum.xda-developers.com/nexus-9/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2945451
I was having some trouble TWRP installing as well., and it was able to install TWRP just fine
Click to expand...
Click to collapse
Tried Wug's, and got the same result when I got to it sending the fast boot commands. Prompt just hangs until I select reboot fast boot.
craig.buckie said:
Close any other running programs, especially Chrome. Then if still not doing it, install CWM Recovery instead, and if you still want TWRP flash it from CWM Recovery.
My N5 won't let me have TWRP, so if you just want the functions of a recovery, try a different one.
Click to expand...
Click to collapse
I'm at my end right now, because I want to remove all this dumb Google bloatware so badly. Was thinking about trying to flash stock image, or relock and unlock boot loader again to see if that does anything, but I'm very nervous that those options might not work because of the fact that fast boot commands aren't working. Certainly don't want to end up with a $400 paperweight...
SwoRNLeaDejZ said:
Tried Wug's, and got the same result when I got to it sending the fast boot commands. Prompt just hangs until I select reboot fast boot.
I'm at my end right now, because I want to remove all this dumb Google bloatware so badly. Was thinking about trying to flash stock image, or relock and unlock boot loader again to see if that does anything, but I'm very nervous that those options might not work because of the fact that fast boot commands aren't working. Certainly don't want to end up with a $400 paperweight...
Click to expand...
Click to collapse
I assume you're on 5.0.1. Flash the boot or recovery image from the factory image in fastboot. See if that works. That might rule out a fastboot issue. If it flashed it won't do anything negative to your device
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
I assume you're on 5.0.1. Flash the boot or recovery image from the factory image in fastboot. See if that works. That might rule out a fastboot issue. If it flashed it won't do anything negative to your device
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Going to give this a shot now..
Worth mentioning, I ran an OEM Lock command, and successfully relocked the bootloader, so it appears fastboot is at least partially working. Going to attempt to flash the bootloader in the image from Google, because that is all there is. Just bootloader and image, no recovery image. I will post results here. I don't know why fastboot commands are broken after unlocking bootloader, but there is one thing that seems odd to me:
When I run fastboot devices, it returns the following (has been like this from the beginning):
Code:
C:\Users\saltam\Downloads\TWRP>fastboot devices
???????????? fastboot
Thoughts?
Something's not right. Do you have the newest fastboot?
di11igaf said:
Something's not right. Do you have the newest fastboot?
Click to expand...
Click to collapse
Yes, recently updated it via the minimalist fastboot/adb tool. This is REALLY irritating the hell out of me at this point... Been trying to get recovery on this stupid tablet all damn day...
I am starting to think this is a read/write error.. It is getting the error whenever it tries to write to the tablet... (sending boot.img results in the error every time)... Anyone know of fastboot/adb commands to check/fix read and write errors
**EDIT**
So, much to my chagrin, it appears to just be my computer... Tried on a different laptop, and was able to get it rooted.. For some odd reason though, I don't think TWRP is installing correctly ??
I am going to try and boot into recovery, but every time i try to flash it with fastboot flash recovery recovery.img it says it was successful, but a boot into recovery mode comes up as the dreaded NO COMMAND laying down Android icon. Super frustrating..
**EDIT 2**
So after much trying of different methods, I was able to successfully flash TWRP with Flashify. Not sure why I couldn't do it manually through fastboot but I'm good now. Thanks for all the replies and suggestions. This can be marked as closed or solved. Thanks!
SwoRNLeaDejZ said:
I am starting to think this is a read/write error.. It is getting the error whenever it tries to write to the tablet... (sending boot.img results in the error every time)... Anyone know of fastboot/adb commands to check/fix read and write errors
**EDIT**
So, much to my chagrin, it appears to just be my computer... Tried on a different laptop, and was able to get it rooted.. For some odd reason though, I don't think TWRP is installing correctly ??
I am going to try and boot into recovery, but every time i try to flash it with fastboot flash recovery recovery.img it says it was successful, but a boot into recovery mode comes up as the dreaded NO COMMAND laying down Android icon. Super frustrating..
**EDIT 2**
So after much trying of different methods, I was able to successfully flash TWRP with Flashify. Not sure why I couldn't do it manually through fastboot but I'm good now. Thanks for all the replies and suggestions. This can be marked as closed or solved. Thanks!
Click to expand...
Click to collapse
To your first edit, twrp is probably working correctly. Lollipop forces the stock recovery. There are two files, one in /system and one in /system/bin that force the stock recovery upon boot. You can remove those files or first
fastboot boot twrp.img
Then flash supersu in twrp, then
fastboot flash recovery twrp.img
Sent from my Nexus 9 using XDA Free mobile app
Got the right USB driver
Dirty Unicorns /Uber / Beanstalk Yuga adm.
xtcdk said:
Got the right USB driver
Dirty Unicorns /Uber / Beanstalk Yuga adm.
Click to expand...
Click to collapse
Kind of mystified with your response... Had nothing to do with the USB drivers. Found out afterward that the problem was the security that my company had setup on my laptop (was using my company thinkpad). Switching laptops solved the problem.
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
hi all,
i have a rooted vivo air lte with supersu.
i wanted to install magisk with the manager 8.0.3 (the boot.img from stock rom i extracted to downloads folder) by choosing direct install.
now the phone hangs on the bootlogo.
i can boot into recovery and choose "apply update from adb"
i installed fastboot and adb on the pc.
in the terminal command "adb devices" i see "devicenr sideload".
when i enter fastboot devices, there is no device shown.
im not sure if i have unlocked the bootloader when i rooted the phone a year ago..
so what do i have to do now to get it booting again?
thanks for the help!
schlunk said:
in the terminal command "adb devices" i see "devicenr sideload".
Click to expand...
Click to collapse
Device is configured to get booted in "Sideload" mode what is a variant of ADB mode.
Try this
Code:
adb devices
adb reboot
to return to "Normal" mode.
no, this is what i have chosen in the recovery, otherwise i dont get any device listed in the terminal..
@schlunk
Once being in the Android Recovery Mode and you select option Reboot system the Android device simply gets restarted: the actually configured ADB mode herewith doesn't get changed / reset.
when i enter "adb reboot" in the terminal its "error closed"..
is ther e something i can sideload then to solve this, when the phone is waiting for the package to sideload?
thanks for helping!
schlunk said:
when i enter "adb reboot" in the terminal its "error closed"..
is ther e something i can sideload then to solve this, when the phone is waiting for the package to sideload?
thanks for helping!
Click to expand...
Click to collapse
QFIL is the answer.
this is a flasher like odin?
so can i just flash the boot.img, that magisk wrote back to the stock one?
and like i said im not sure if the bootloader is unlocked, does it play a role in this?
schlunk said:
this is a flasher like odin?
so can i just flash the boot.img, that magisk wrote back to the stock one?
and like i said im not sure if the bootloader is unlocked, does it play a role in this?
Click to expand...
Click to collapse
https://firmwarefile.com/blu-vivo-air-lte-v0010uu
https://www.youtube.com/watch?v=MdknZvaTwl4
thats exactly the file i downloaded to extract the boot.img and see what happend
i dont want to flash the complete stock firmware again with the risk that my phone is bricked after that.
there must be some easier solution for this??
cant i just flash what magisk messed up?
schlunk said:
there must be some easier solution for this??
cant i just flash what magisk messed up?
Click to expand...
Click to collapse
Nope, I don't think there is.
Depends if that boot is same that was in your device. See the video
and the thread too: https://forum.hovatek.com/thread-31476.html
The boot should be the same, the firmware is exactly the same like in the phone regarding the label.
So with this linked method, flashing a single partition means, the boot.img can be flashed solo, without the need of flashing the whole firmware?
And when that doesnt work, i still could flash the whole firmware then as last resort?
That what I would do... Good luck!
I recently found my old HTC desire 526g and I decided to flash a custom ROM, but its volume buttons aren't working so I had to use adb, I am not really an good in these types of things. I tried to flash TWRP on my htc using adb (Followed a YouTube tut) but this is coming up.
I have attached a screenshot below.
After unlocking bootloader (probably would have done it earlier) did you allow the usb debugging.
2) try installing adb+fastboot, platform tools and your htc drivers and keep your recovery file in the platform tools and open cmd there use the appropriate command to flash it
Rajveer chauhan said:
After unlocking bootloader (probably would have done it earlier) did you allow the usb debugging.
2) try installing adb+fastboot, platform tools and your htc drivers and keep your recovery file in the platform tools and open cmd there use the appropriate command to flash it
Click to expand...
Click to collapse
Hello, Thanks for replying! I think I have done everything in correct manner, but still coming thiss error, I have rooted my phone too. BTW, is there any way you can navigate through system recovery without using volume buttons (as they are not working) I mean any commands, to navigate in recovery mode using adb
YourLocalClown69 said:
Hello, Thanks for replying! I think I have done everything in correct manner, but still coming thiss error, I have rooted my phone too. BTW, is there any way you can navigate through system recovery without using volume buttons (as they are not working) I mean any commands, to navigate in recovery mode using adb
Click to expand...
Click to collapse
So if you're rooted so you can flash recovery via twrp app on playstore, or if magisk installer for twrp exists for your phone or by flashfire if you have your working recovery
'adb reboot bootloader' will bring you fastboot mode.
'fastboot flash recovery recovery.img' (while TWRP image or CWM image is renamed recovery.img and placed into the fastboot folder)will bring you TWRP/CWM.
'fastboot reboot recovery' will bring you into TWRP or CWM installed.
'fastboot reboot' will reboot you phone in case you are stuck.
LR7875 said:
'adb reboot bootloader' will bring you fastboot mode.
'fastboot flash recovery recovery.img' (while TWRP image or CWM image is renamed recovery.img and placed into the fastboot folder)will bring you TWRP/CWM.
'fastboot reboot recovery' will bring you into TWRP or CWM installed.
'fastboot reboot' will reboot you phone in case you are stuck.
Click to expand...
Click to collapse
This comes later now lol, Due to my lack of knowledge and not enough patience, I tried to flash custom recovery through TWRP app, and I didn't found my phone model on device list, SO i just selected random htc model phone and now it is restarting over and over again, Is there any fix to this? I am obviously a complete noob in this field.
If possible find stock recovery of that firmware version (be serious abt version) and flash it by fastboot
2) find how to unbrick htc by downloading stock rom this will make you lose all data
Rajveer chauhan said:
If possible find stock recovery of that firmware version (be serious abt version) and flash it by fastboot
2) find how to unbrick htc by downloading stock rom this will make you lose all data
Click to expand...
Click to collapse
Even If I find the this whatever you said, how am I supposed to fix it, as I mentioned,Volume buttons aren;t working and its stuck in bootloop, it won't past its manufacturers logo, so adb is no help in it, Only way to fix it would be to fix sound buttons. sad me, Well, R.I.P. HTC Desire 526g dual sim 2015-2021
I hope that this phone is not your primary driver
YourLocalClown69 said:
I recently found my old HTC desire 526g
Click to expand...
Click to collapse
Rajveer chauhan said:
I hope that this phone is not your primary driver
Click to expand...
Click to collapse
He unearthed his phone from some drawer, so this is not his daily driver.
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