I accidentally allowed the 2.20.40.183 OTA update, which rendered my phone useless. I tried putting MOFD_UPDATE of 2.20.40.174 on my SD card, but that didn't work.
Here's a few other things I tried:
Recovery menu: Updating phone, then dead droid. No menu appears.
adb sideload: adb didn't recognize my phone.
fastboot flash: Permission denied, or something along those lines. The write fails. Tried to flash system.img but it never did and nothing happened.
adb sideload through temporary CWM: Unauthorized device. Couldn't sideload.
Flashing through temporary CWM and temporary TWRP: Fails early on with Status 7. 2.20.40.174 is older, and this is apparently reason enough to deny me.
Does anyone have an idea about what I can do to fix this? Could I flash Cyanogenmod, then flash stock over that, using temporary CWM/TWRP?
My bootloader is not unlocked.
PasserbyPassingBy said:
I accidentally allowed the 2.20.40.183 OTA update, which rendered my phone useless. I tried putting MOFD_UPDATE of 2.20.40.174 on my SD card, but that didn't work.
Here's a few other things I tried:
Recovery menu: Updating phone, then dead droid. No menu appears.
adb sideload: adb didn't recognize my phone.
fastboot flash: Permission denied, or something along those lines. The write fails. Tried to flash system.img but it never did and nothing happened.
adb sideload through temporary CWM: Unauthorized device. Couldn't sideload.
Flashing through temporary CWM and temporary TWRP: Fails early on with Status 7. 2.20.40.174 is older, and this is apparently reason enough to deny me.
Does anyone have an idea about what I can do to fix this? Could I flash Cyanogenmod, then flash stock over that, using temporary CWM/TWRP?
My bootloader is not unlocked.
Click to expand...
Click to collapse
I do the same! Now my phone stuck on boot screen.
Does anybody can help us?
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
mr_gourav2000 said:
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
Click to expand...
Click to collapse
I'm not going to lie, that guide's a bit hard to read. I'll try to follow as best as I can and reply if this works for me.
I'd still appreciate any other advice others have.
PasserbyPassingBy said:
I'm not going to lie, that guide's a bit hard to read. I'll try to follow as best as I can and reply if this works for me.
I'd still appreciate any other advice others have.
Click to expand...
Click to collapse
All necessary to read.
Hope you fix the problem.
Fixed
I managed to fix my phone, but not with the method Mr Gourav so kindly posted. I chose not to use mr_gourav2000's IntelSoC fix because the guide was written in a way that made it very hard to follow, and I was unsure if MOOREFIELD was supposed to flash briefly or stay on the Device Manager. Regardless, I wasn't going to risk bricking my phone beyond help by pushing on without knowing what i was doing.
The key was bypassing Status 7 (or 1), which prevents you from downgrading firmware. If your phone says something like "Installation failed with Status 1" or "Status 7," or you get the "Can't install this package over newer build" error when you attempt to flash a previous firmware, this fix can help you. Funny enough, the fix was posted by the very same person earlier this year:
http://forum.xda-developers.com/showpost.php?p=65995574&postcount=116
First, download the latest full firmware from Asus' support site: https://www.asus.com/Phone/ZenFone_2_ZE551ML/HelpDesk_Download/
Then, open or extract the .zip file, and go to into UL-Z00A-WW-(Firmware.Version.Number)-user.zip\META-INF\com\google\android\ . Select updater-script (no file extension), and open it in a plain text editor like Notepad++.
Remove lines 1-6, beginning with "(!less_than_int" and ending with "getprop("ro.product.device") + "\".");". The result should look like this.
Then, insert the edited updater-script into the .zip file, overwriting the old updater-script. At this point, I should mention that one of the removed lines probably checked your phone's model number to see if it was compatible with the firmware. I sure hope you downloaded the right file for your phone. If not, brick city here you come.
Finally, put the edited .zip into a microSD card, and insert that into your phone. If you want to use the stock recovery to install the firmware, rename the .zip to MOFD-UPDATE.zip and put it in the root of the SD, then restart the phone and let it update. Presumably. I didn't use the stock recovery. I used the temporary ClockworkMod recovery to fix my phone, so I'm not sure if it's that simple. If you're using that temporary CWM, just go to the zip installation menu and apply the zip from external_sd.
If you were going through the same problems I was, your phone should boot into stock, unrooted firmware again. Pat yourself on the back and never do whatever dumb thing you did to get to this point in the first place (like absentmindedly apply an OTA update in the middle of a lecture)!
Once again, thanks to mr_gourav2000 for posting this fix earlier. I may not have understood the IntelSoC fix, but I did understand this one!
.183 after update takes an extremelynlong time to boot after asus screen aa well. Made me think mynphone crashed, took a bout 10-15 minutes on first boot for me
Redtexan said:
.183 after update takes an extremelynlong time to boot after asus screen aa well. Made me think mynphone crashed, took a bout 10-15 minutes on first boot for me
Click to expand...
Click to collapse
If it's the 1st boot it generally will as it is recreating cache, dalvik-cache or ART...
It seems to take forever to clear cache too when using recovery but about a heartbeat when using fastboot.... Just another quirk of the phone...
Thank you much
I gotta say, this got me on the right path. Though my issue was exactly the same the fix was a little different.
I had to use the next patch and that worked. Recovery is working now and I have to manually update, but still have root, so no real big deal.
Thanks again.
mastet68 said:
I gotta say, this got me on the right path. Though my issue was exactly the same the fix was a little different.
I had to use the next patch and that worked. Recovery is working now and I have to manually update, but still have root, so no real big deal.
Thanks again.
Click to expand...
Click to collapse
You need to flash boot, droidboot and recovery for the build you are using.
I use fastboot to do this but make sure developer settings are enabled and USB debugging is ticked before trying to flash.
To find the img files for the above mentioned, go to Shakalaka's pre-rooted rom thread in Android Developement, you don't need to download the rom if you don't want to but it sure makes rooting easy.
Find the version of Android you need and download boot,droidboot and recovery img files. Flash with fastboot using these commands -
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash fastboot droidboot.img
***Make sure the right commands are used or it may result in a brick...***
Related
Hello,
After applying the latest OTA 2.29.405.2 I am unable to boot my phone.
The new firmware was successfully applied, because I could start the phone for the first time.
After I shut it down again it won't got past the HTC logo.
I can get start the hboot but I if i select fastboot or recovery I get stuck again with the HTC logo.
When i select the bootloader "I get no image or wrong image."
I did not root my phone.
Please help.
For a start, unless you have a PB99IMG.zip file on your sd card you will always get that message in the bootloader. It's just telling you it can't find any of the files it looks for on your card so nothing wrong there.
First thing I'd do is try manually reflashing the OTA update. you can get the OTA ZIP file here:
http://fotadl.htc.com/OTA_Bravo_Froyo_HTC_WWE_2.29.405.2-2.10.405.2_R_P_release8gn61bgo3rswcw24.zip
Rename it update.zip and put it on the root of your SD card. Then boot into recovery (if you manage to) and flash it.
If not, go into Fastboot and clear storage (wipe). This should sort you out. If not, download the 2.29.405.2 RUU from my signature and flash that in fastboot and it should see you right if you're still having issues
Did not work unfortunately. I will try to flash it. Any easy to follow tutorial I can use ? I never did this before.
Thank you kindly.
psycho.ro said:
Did not work unfortunately. I will try to flash it. Any easy to follow tutorial I can use ? I never did this before.
Thank you kindly.
Click to expand...
Click to collapse
What didn't work? What I put on my previous post is exactly what you need to do
I downloaded the file and renamed it ot update.zip and copied it to the root of my sdcard. when i select recovery it gets stuck in htc logo.
Then I've cleared storage/user settings and tried again, same thing.
So now do the last thing I suggested
this happened to me also. i downloaded the RUU and just did it via the pc. lost everything i did not backup, but that's my fault. all contacts were on google and and i used appbrain to pull down all my installed apps.
ok, i finally did it and it's fine now. I figured out what i was doing wrong. flashed it and it started now.
thanks for the support, really appreaciate it !
For reference, what were you doing wrong?
i did not go in the fastboot menu when i tried the last thing you suggested and because of this, my phone was not recognized by windows and the flash utility could not do its job.
but now it seems that my phone is restarting from time to time, somewhere between 5-10 minutes.
Might wanna do a hard reset just to make sure things flashed correctly
Hello, I know there have been many people who have been so riddled with battery and temperature issues with their watches that they are ready to throw them away. Here is a guide which may solve your problem. I did this on an SW3 with locked bootloader. It is possible. You just need to be patient. Most of this information I pulled from the linked threads, as such, this is not really my work. Many thanks to NUT for this thread which showed me all of this is possible.
Before we proceed, know that This is risky. You could potentially brick your watch. Know what you are doing when playing with firmware/ system software, and know that I am not responsible if you destroy your device or throw the world off its axis in trying to fix your watch. Consider yourself warned.
Having said that, know that this particular watch is not that difficult to fix AS LONG AS YOU DO NOT MESS WITH THE BOOTLOADER.
Okay, Prerequisites:
Sony SW3
Computer
Working adb drivers for both the watch os and TWRP (on win10, this was the most difficult part).
Working Fastboot drivers
Here we go...
All of this work is either done on your computer or the watch itself with the exception of setting up the watch after you wipe it.
The words in brackets are placeholders for file names of images and zips on your computer.
1) Download the 5.1.1 version of twrp from the thread here. Also, Download the 5.0.1 repacked zip from here (thanks Perpe for making this repak).
2) Using your computer, reboot into fastboot mode
Code:
adb reboot bootloader
3) On your computer, hot boot into adb
Code:
fastboot boot <TWRP.img>
4) Sideload the update for os 5.0.1 <--- This step originally wiped my recovery. Do not freak out. You will probably get it back, and to be honest, you can live without it.
factory reset (if you do not factory reset, it will bootloop, and you will freak out).
On your computer, run this command
Code:
adb push <rom-repacked-stock-rom-swr50-version-t2988087.zip> /sdcard
Then, using the TWRP menu on your watch, install the zip.
Set the watch back up. Congrats! You just rolled your firmware back.If you are ahppy, Yay. If not, Keep reading. Warning, you may not have a recovery now. That is okay, in fact that will prevent auto updates in the future.
Still with me? Okay, you may want to update to the next version (LWX49P), but there will be no way to update to only 5.0.2
There is a solution.
Download the 5.0x version of Twrp from here (we have already proven you need not unlock your bootloader, in fact, you can even replace a reccovery without unlocking, see below). Thanks again Perpe.
Also download the 5.0.2 update. Here is a link to the stock flashable.
Here is a link to the Twrp flashable. Thank you Tadaa and Noonski for those files.
Boot into fastboot
boot into recovery of your choice (you can use TWRP if you downloaded it.
sideload (stock if you have it) or install this update file.
Now, when you reboot, your watch will attempt to update. It needs a recovery to do so, so I deleted mine. Here is how.
Root your watch using twrp for 5.0.x.
Boot to twrp like you did earlier
Then, install Wear-SuperSU-v2.46.zip (like you installed the update before.Install es file explorer which you can download here.
Code:
adb install <esfileexplorer.apk>
Install flashify (I think you have to get this from the play store and then pull it from your phone).
push twrp for 5.1.1 to sdcard (like you did before).
Now, go to your watch.
open falshify
backup recovery
open es file explorer
click on twrp 5.1.1 image
flash to recovery
Your watch will reboot
let it download and install the update (the update will fail because you do not have a working recovery).
Enjoy 5.0.2 without Google nagging you about an update.
I will seed these files soon, but I wanted to give the authors credit for the links.
Thank you again NUT, Perpe, Tadaa, Nooski for your work.
Let me know if you have any questions. Do not panic if you bootloop, it is easy to force this watch into fastboot mode even if you cannot fully boot, as long as the bootloader is in tact, and as you see, you can replace most of the bootimages (i.e. system and recovery which are all you should worry about) without unlocking your bootloader.
Good Luck,
Leko
Can you not simply flash TWRP with fastboot flash recovery? Without needing to use flashify?
Yes and no. Yes if you unlock your boot loader, no if you do not.
So after 2 hours of searching, trying and failing, I just decided to post here and see what help I can get.
Situation is exactly like the title. Had Lineage 14.1 installed, and decided to update the phone. Rebooted the phone and went to TWRP recovery. For whatever reason, I decided to reboot the phone, which ended up in it coming back to TWRP. This repeated until I got the stock recovery, which put me into bootloader instead. Bootloader is now locked, I can no longer get into recovery, and I'm stuck in bootloader for as long as this continues.
So far I have tried:
--------BEFORE TWRP RECOVERY FAILURE AND BOOTLOADER LOCK---------
Factory Resetting
Formatted and flashed ROM
A couple of ADB commands
--------AFTER TWRP RECOVERY FAILURE AND BOOTLOADER LOCK---------
Replaced recovery image file with stock
Idiotically replaced bootloader image file with stock (Locked, can tell since Android N is no longer bugging me with preboot notification which was present before when bootloader was unlocked)
Idiotically replaced the system image file with stock
A slew of fastboot commands (You can comment and I can see if I have attempted them)
Attempted to continue the fastboot process
Attempted to use an automatic rootkit. Did not like my device, so it did nothing at all.
Manually unplugging the battery
Haven't tried:
Placing rom in sd card, like I've seen people say elsewhere. (No SD card available)
Anything else you tell me that I haven't done
I'm not really interested in keeping any files that I've had before, if that is not already made clear.
Anyone that can help me, I really want this to end. :crying: :crying:
BillJake said:
So after 2 hours of searching, trying and failing, I just decided to post here and see what help I can get.
Situation is exactly like the title. Had Lineage 14.1 installed, and decided to update the phone. Rebooted the phone and went to TWRP recovery. For whatever reason, I decided to reboot the phone, which ended up in it coming back to TWRP. This repeated until I got the stock recovery, which put me into bootloader instead. Bootloader is now locked, I can no longer get into recovery, and I'm stuck in bootloader for as long as this continues.
So far I have tried:
--------BEFORE TWRP RECOVERY FAILURE AND BOOTLOADER LOCK---------
Factory Resetting
Formatted and flashed ROM
A couple of ADB commands
--------AFTER TWRP RECOVERY FAILURE AND BOOTLOADER LOCK---------
Replaced recovery image file with stock
Idiotically replaced bootloader image file with stock (Locked, can tell since Android N is no longer bugging me with preboot notification which was present before when bootloader was unlocked)
Idiotically replaced the system image file with stock
A slew of fastboot commands (You can comment and I can see if I have attempted them)
Attempted to continue the fastboot process
Attempted to use an automatic rootkit. Did not like my device, so it did nothing at all.
Manually unplugging the battery
Haven't tried:
Placing rom in sd card, like I've seen people say elsewhere. (No SD card available)
Anything else you tell me that I haven't done
I'm not really interested in keeping any files that I've had before, if that is not already made clear.
Anyone that can help me, I really want this to end. :crying: :crying:
Click to expand...
Click to collapse
What is your IFWI version number in bootloader ?
IFWI Version: 0094.0183
BillJake said:
IFWI Version: 0094.0183
Click to expand...
Click to collapse
Flash raw 4.21.40.184 M with AFT in bootloader
https://forum.xda-developers.com/zenfone2/general/z008-z00a-z00d-z00x-raw-fw-collection-t3448966
Thank you so much. Fixed my phone.
BillJake said:
Thank you so much. Fixed my phone.
Click to expand...
Click to collapse
Marvelous , drop a thank you to realyoti in the link , hit his thanks button too.:good::highfive:
while following these instructions in the youtube video named Moto G6 2018 Install Twrp & Root Easy Tutorial 757 or 12:44 at this part i must have downloaded the wrong file since my build model is XT1922-9 type M373B could someone help me resolve me issue so i can fix my phone and finish the root cause my phone refuses to boot
Provide more info about your device including device variant, os version. More info the better so we know how to help you.
Jleeblanch said:
Provide more info about your device including device variant, os version. More info the better so we know how to help you.
Click to expand...
Click to collapse
It's a moto g6 play android 8 or it still turns on but it's stuck on the bootloader screen and I need help fixing that and finishing the rooting of my phone
kc02141994 said:
It's a moto g6 play android 8 or it still turns on but it's stuck on the bootloader screen and I need help fixing that and finishing the rooting of my phone
Click to expand...
Click to collapse
I figured out that much from your first post, I was referring to which variant specifically (ex: 192x-x) and do you know what the stock factory firmware version is?
Jleeblanch said:
I figured out that much from your first post, I was referring to which variant specifically (ex: 192x-x) and do you know what the stock factory firmware version is?
Click to expand...
Click to collapse
i dont know but all i know is my phones build model is XT1922-9 TYPE M373B the phone still turns on but it goes to the bootloader menu with the error message start up failed your device didint start up successfully use the sofware repair assistant on your computer to repair your device connect your device to your computer to get the software repair assistant AP fastboot flash mode secure error failed to load kernal fastboot reason fall through from normal boot i want to fix my phone and finish rooting it so i can use the wifi tether app and i dont know what to do which is why im asking for help i followed the instructions from that video but i downloaded and put in the wrong file i think my phone can be finished rooting and fixed so if i could just get the file i need i can finish rooting and use my phone again
kc02141994 said:
i dont know but all i know is my phones build model is XT1922-9 TYPE M373B the phone still turns on but it goes to the bootloader menu with the error message start up failed your device didint start up successfully use the sofware repair assistant on your computer to repair your device connect your device to your computer to get the software repair assistant AP fastboot flash mode secure error failed to load kernal fastboot reason fall through from normal boot i want to fix my phone and finish rooting it so i can use the wifi tether app and i dont know what to do which is why im asking for help i followed the instructions from that video but i downloaded and put in the wrong file i think my phone can be finished rooting and fixed so if i could just get the file i need i can finish rooting and use my phone again
Click to expand...
Click to collapse
Hm, ok. If you're getting kernel failed to load errors from the bootloader, then maybe you flashed the wrong boot.img for your device?
Either way, try flashing the XT1922-9_no_dm-verity_boot.img.
To do so, make sure you have TWRP. You don't have to install it, but if you wanna root you can flash it...
So either do..
Code:
fastboot boot moto-g6-play-jeter-patched-twrp.img
Or do..
Code:
fastboot flash recovery moto-g6-play-jeter-patched-twrp.img
After you have TWRP running, then flash the boot.img by doing..
Code:
fastboot flash boot XT1922-9_no_dm-verity_boot.img
All of these instructions are found in the thread for your device [GUIDE][ROOT][Moto G6 Play][JETER] TWRP, Root, and magisk installation guide
There is also a step to flash a modified fstab.qcom file to remove forced encryption as well which you should look into. But honestly I would like to see you get outta this situation you're currently in then we'll get the rest done after
Jleeblanch said:
Hm, ok. If you're getting kernel failed to load errors from the bootloader, then maybe you flashed the wrong boot.img for your device?
Either way, try flashing the XT1922-9_no_dm-verity_boot.img.
To do so, make sure you have TWRP. You don't have to install it, but if you wanna root you can flash it...
So either do..
Code:
fastboot boot moto-g6-play-jeter-patched-twrp.img
Or do..
Code:
fastboot flash recovery moto-g6-play-jeter-patched-twrp.img
After you have TWRP running, then flash the boot.img by doing..
Code:
fastboot flash boot XT1922-9_no_dm-verity_boot.img
All of these instructions are found in the thread for your device [GUIDE][ROOT][Moto G6 Play][JETER] TWRP, Root, and magisk installation guide
There is also a step to flash a modified fstab.qcom file to remove forced encryption as well which you should look into. But honestly I would like to see you get outta this situation you're currently in then we'll get the rest done after
Click to expand...
Click to collapse
ok that problem solved now im stuck on an infinite bootloop after i do the parts where the guy says wipe then download those files from the sd card and when i reboot the phone it does says N/A on the top left and starts boot looping
Jleeblanch said:
Hm, ok. If you're getting kernel failed to load errors from the bootloader, then maybe you flashed the wrong boot.img for your device?
Either way, try flashing the XT1922-9_no_dm-verity_boot.img.
To do so, make sure you have TWRP. You don't have to install it, but if you wanna root you can flash it...
So either do..
Code:
fastboot boot moto-g6-play-jeter-patched-twrp.img
Or do..
Code:
fastboot flash recovery moto-g6-play-jeter-patched-twrp.img
After you have TWRP running, then flash the boot.img by doing..
Code:
fastboot flash boot XT1922-9_no_dm-verity_boot.img
All of these instructions are found in the thread for your device [GUIDE][ROOT][Moto G6 Play][JETER] TWRP, Root, and magisk installation guide
There is also a step to flash a modified fstab.qcom file to remove forced encryption as well which you should look into. But honestly I would like to see you get outta this situation you're currently in then we'll get the rest done after
Click to expand...
Click to collapse
i really need help on this i cant finish the root i dont know what im doing wrong im up to the part in the video i watched and after i finished doing that part it begins infinite rebooting and i dont know what to do i installed the right file did everything he did but instead of getting the message in the center i get N/A on the top left and then infinite reboots
Jleeblanch said:
Hm, ok. If you're getting kernel failed to load errors from the bootloader, then maybe you flashed the wrong boot.img for your device?
Either way, try flashing the XT1922-9_no_dm-verity_boot.img.
To do so, make sure you have TWRP. You don't have to install it, but if you wanna root you can flash it...
So either do..
Code:
fastboot boot moto-g6-play-jeter-patched-twrp.img
Or do..
Code:
fastboot flash recovery moto-g6-play-jeter-patched-twrp.img
After you have TWRP running, then flash the boot.img by doing..
Code:
fastboot flash boot XT1922-9_no_dm-verity_boot.img
All of these instructions are found in the thread for your device [GUIDE][ROOT][Moto G6 Play][JETER] TWRP, Root, and magisk installation guide
There is also a step to flash a modified fstab.qcom file to remove forced encryption as well which you should look into. But honestly I would like to see you get outta this situation you're currently in then we'll get the rest done after
Click to expand...
Click to collapse
new problem i cant install magiks and now it says theres no OS installed this phone is seriously screwed up and its one of my only sources of internet
kc02141994 said:
new problem i cant install magiks and now it says theres no OS installed this phone is seriously screwed up and its one of my only sources of internet
Click to expand...
Click to collapse
Ok, well we're getting somewhere at least. Sounds like you have the right boot.img at the very least. Now we need to find you the right stock firmware (or even at minimum a system.img and vendor.img from some else with the same device).
I'll look around to see what I can find.
Next thing I need from you is to connect your device to the computer and reboot to bootloader and get me the output of..
Code:
fastboot getvar all
and copy/paste it to https://hastebin.com or copy/paste it to a text file and upload the text file as an attachment here (or wherever you want and post the link) so I can review it. That should tell me what I need to know to help you a little better. Do NOT just copy/paste the output into a post please.
Hello, does anybody know when a recovery for the moto G7 play XT1952-4 might be released? I am eager to root my new phone.
I am also looking for the recovery of Moto G7 Play, I unlocked my BootlLoader to make Root and I do not think any Recovery
You don't need TWRP to root the phone. As long as the bootloader is unlocked, you can root with Magisk. Select the Link To Installation Instructions and follow the Boot Image Patching section. It requires using ABD commands, and although it looks/seems complicated, it is actually very easy. Plus, you will have learned something as well as root your phone.
If the G7 Play is actually code-named "Channel", then this link will give you stock firmware for you to download and extract the stock boot image.
Magisk boot.img
Ok I got the retail Canada ROM. Now I am going to extract boot img and patch it with Magisk manager. Once patched I am going to flash it to my phone using abd fastboot? At this point it will be rooted or do I use SuperSU to root? Under software channel on my phone it says "Bell" but the build number and model number matched up. XT1952-4 PPY29. 105-57 so it should be good hopefully.
Thanks
Error: cannot open 'magisk_patched.img'
Must be wrong Rom. Everything worked fine until I had to flash it. I put patched IMG right in adb directory and opened a command window from there but when I tried to flash it I got the error cannot open file. Oh well I think I will wait for a recovery it's the easy way for me.
Thanks
Code named 'channel'
There are 2 more versions of it in the list you provided. Not sure what the abbreviations are before CA for Canada but I will try them too. If I get the same error when flashing these patched boot.imgs I will have to wait for a recovery. Hopefully it won't by be too much longer. I just hope there will be a recovery.
Thanks
Continued error when flashing patched files.
I have tried 3 boot images from 3 different retail Canada firmwares. All 3 patched alright by magisk manager but when I try to fastboot flash boot magisk_patched.img I get the same error cannot open file. I must be doing something wrong. My phone's bootloader is unlocked so unless someone has a solution. I will definitely have to wait for a recovery. Hopefully soon!.
Thanks
Dumb question...when you are attempting to flash your patched boot image, is your phone in fastboot mode? Also, you may be able to extract your boot image via ADB. It's been a while since I've done it and am having trouble finding the proper commands, but you can try this:
adb pull /dev/block/bootdevice/by-name/boot stockboot.img
Click to expand...
Click to collapse
It may or may not work. I hope it does but apologize if it does not.
Furthermore, you will likely have to wait quite a while for a custom recovery (TWRP). The G7 play has A/B partitions, which makes ROM building and recoveries very difficult. There is no separate "recovery" partition with A/B...the recovery is combined within the boot image. FYI - I have a Xiaomi A2 Lite that has A/B partitions. We still don't have a 100% working TWRP after 9 months. Custom ROMs have just been coming out slowly. I was able to root with Magisk using ABD commands though.
This link might provide clearer steps for installing Magisk.
Best of luck!
Yes, it was in fastboot mode. I will keep trying with your new intructions. Thanks for your help.
My mistake
I did not even have adb fastboot installed I was opening a command window out of the folder that was left over from uninstallation. I am about to try it again. It should work now. Stay tuned.
So far
Okay, so I installed adb fastboot and flashed the patched boot file from the RETCA firmware. I got this message " failed (boot a)" . So I tried the flashing the 2nd patched boot file that was from I think BWACA firmware. With this flash I got " not signed or corrupt" then the phone failed to start with bootloader log to confirm.
So I took the original unpatched boot.img from RETCA and flashed it. This fixed the phone so it would start fine making me believe that it's the right boot image but maybe the other firmware boot.img would have fixed the failing to start issue as well. So I think I need to pull the boot.img from the phone itself like you suggested. I am going to read some more and continue. I will figure it out. Any suggestions would be of great value.
Thanks.
Getting Closer
I realized that the magisk zip file that magisk manager downloaded did not get unzipped so that it could patch the boot.img properly. Fixed that. Flashed the boot.img and it said "okay" but said "(bootloader) image signed with key bad key" so I think I will have to pull the boot.img from the phone itself. So I am about to read up on that then I should be able to flash successfully for root access.
Thanks
jwreidmoto said:
I realized that the magisk zip file that magisk manager downloaded did not get unzipped so that it could patch the boot.img properly. Fixed that. Flashed the boot.img and it said "okay" but said "(bootloader) image signed with key bad key" so I think I will have to pull the boot.img from the phone itself. So I am about to read up on that then I should be able to flash successfully for root access.
Thanks
Click to expand...
Click to collapse
A few posts back you said you flashed the stock RETCA boot image. If that's the case, then if you successfully pull the boot image from the phone, you are simply pulling the RETCA boot image you already flashed. It seems that the RETCA boot image is the correct one for you phone. I would start completely from scratch with that. To verify which build number you have, go to Settings>About Phone or ( Settings > About Phone > Software channel) and scroll down to Build Number. Match it up to one from link with all the firmware images.
The only other thing I can say is that you should read and completely understand what to do prior to doing it. I am sorry you are having difficulties with this. It really should not be so hard. As I don't have the phone I cannot be of much more assistance. However, once you figure it out, perhaps you can write a quick guide to help others.
EDIT: You should be rooted. SEE POSTS 10-13. Did you check for root?
EDIT 2: I'm assuming that since you unlocked the bootloader, when you reboot the phone the screen goes black and says "Bad Key", correct? That is normal for Moto phones.
2nd, after you root, when you reboot the phone, the screen should go black and say "N/A". Again that is normal for Moto phones.
I understand what you are saying I would also expect the N/A on the black screen that's when I knew I successfully rooted my old phone. I must have the right boot image if flashing it fixed the startup failure. I am going to start all over again and see.
Have to give up.
Tried and tried it's just not going to work. I think it's the patching because the boot file starts out as 32mb and only 18mb after being patched. Flashing has no effect on my phone even though it says 'okay' when I flash. I never get the N/A on boot unless there is a startup failure. Oh well have to live with ads among other anoyyances. My Moto g4 play is rooted I can use than in case a solution comes up. Thanks for all your help.
jwreidmoto said:
Oh well have to live with ads among other anoyyances.
Click to expand...
Click to collapse
DNS66 is your friend! I have used it on other unrooted phones. It was decent from what I remember. Good luck!
Sorry that root wasn't working.
EDIT - If you are up for a little more testing...I just found this. I don't remember if it's what I had to do for my Xiaomi or not, but it makes sense. (Further research - No I did not have to do this). Scroll down to method #2 and look for the part about A/B partitions:
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
Click to expand...
Click to collapse
Edit #2 - I don't give up easily LOL
After any of your attempts to flash the patched_boot image, did you ever boot the phone and open the Magisk Manager app? Doing so should ask to install Magisk, if not you must tap on the "Install" button. Then choose "Install" > "Direct Install (Recommended)" to install Magisk on the phone, and reboot when finished.
Neither do I
I have been trying everything since we last talked. Just so you know the link labelled as "this" in your last response is not working. I always opened the magisk app after flashing to see if it was either installed or gave me the option to do a direct install unfortunately, it did not. I have magisk manager installed on my rooted Moto G4 plus and it gives me that option to do a direct install. Will definitely try your new info. Thanks so much for more help. I will let you know.
Still no luck
Without the link I got the jist of what you were saying by the quote boot_a boot_b I tried both consequtively and then tried it for ever possible retail Canada image still no luck. Thanks for your help. I don't know why it's so hard for this phone. I will keep researching.
I'm at about the same place where jwreidmoto is. I purchased my unlocked g7play from Best Buy. First I tried the files in the channel/RETUS folder, these all caused a bootloop. I then tried in the RETAIL folder... still no joy. None of the version numbers quite matched up, and none worked to restore the phone. I finally found a matching file in the AMZ folder, which I was able to use to get the phone to boot up again. So I used that boot.img file with magisk and when I flashed, it gave no errors, no indication anything failed. Unfortunately though, I do not have root access. I started over from scratch and did the process over with the AMZ boot img again, and again no errors, but no root. I've never rooted before, so I don't know if there's another part somewhere I missed, but I do feel like I was able to follow the directions on the g7 thread by mingkee, and performed the steps accurately. I supposed it's just the wrong boot img. The about phone says the software channel is US Retail, and the build number is PPY29.105-36. The RETUS folder only has PPY29.105-43 and RETAIL folder has five different zip files, but none were PPY29.105-36.
You are doing it right
You have not missed any steps. If the boot.img fixed the boot loop then it should be the right one. I had the same issue with a startup failure and fixed it with the RETCA boot.img so I am also using the right one also. I think it's an issue with the model of phone, this method just does not work. We might have to wait a while until someone comes up with a solutuon. I know it sucks.