Develop Bugs

Zenfone 2 failed update, can't flash stock firmware

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...***

Moto G7 Play XT1952-4 Recovery

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.

bricked

Hi i have a pixel xl. I had it rooted via magisk and I had LOS on it. But then i decided to go back to stock. I did that but i forgot that I had to uninstall magisk so i locked the bootloader and wound up with a stock rom rooted. It worked for a while them it started crashing. Im not too sure what happened or what i did it was a year ago. So anyway when i turn it on it says the bootloader is corrupt which it did before. Android flash tool did not work wok. I can boot into recovery but i dont know what to mdo no.
can someone please help me.
Also I am able to use fastboot I just tried from my pc. I just dont know what to do to fix this. I know I have to somehow get twrp back on the phone and flash the magisk uninstall.zip. But this was so long ago i dont even remember which version of magisk I was using or which magisk uninstall file to flash.

i was able to get a flash-all .bat to work but im still in the same position. Basically the phone gives me the message your device cant be checked for corruption then goes on to the google screen and eventually the screen goes blank and it starts over so it is bootlooping i guess.
Can anyone tell me how i can flash twrp.img on the phone with fastboot? Right now the current active slot is b. I tried typing fastboot flash b then the twrp.img file name and it gives me an error. Am I supposed to be flashing to a certain partition?
Please someone help I am not very good with the command line. I dont know all the lingo

[SOLVED] boot loop after i tried to fix broken root

I tried for like 3 hours to find a boot.img and i had root on my phone, but without wifi and sound.
a quick google search showed me that it was because i had a wrong version of the boot.img, afterwards i found another one and now after i have tried installing twrp, booting and flashing using adb (stock and modified versions of boot.img) but it just keeps bootlooping. in twrp i cant wipe, make a backup, see any files in /storage/ and i have no clue what to do next.

What model 7T do you have? HD1907? What was the rom that you were using before you installed TWRP on? OOS12 does not support TWRP. Custom rom A13 does not support TWRP. Only a few custom rom A12 and OOS11 support TWRP.

Idk but I'm just wondering if flashing the last working rom image (dirty flash)? That would eliminate TWRP(?) and eliminate Magisk(?) while hopefully keeping the device from being wiped possibly?
*** Hopefully someone could/would verify this before you attempt... ***

i was on android 11 but i cant remember the version, i have HD1903 (EU ver). i THINK i had the one from the oneplus website(https://service.oneplus.com/us/search/search-detail?id=2096229) but idk anymore

I JUST RANDOMLY TRIED BOOTING MY PHONE AGAIN AND IT WORKED imma check if everything works and will regardless still look at this thread bc it can prob break easily
nah wifi and sound still dont work, but im not in bootloop anymore

MimKA22 said:
I JUST RANDOMLY TRIED BOOTING MY PHONE AGAIN AND IT WORKED imma check if everything works and will regardless still look at this thread bc it can prob break easily
nah wifi and sound still dont work, but im not in bootloop anymore
Click to expand...
Click to collapse
Msmtool back to oos11

can you describe how to use it or send a link to tutorial or smth thx man <3

MimKA22 said:
can you describe how to use it or send a link to tutorial or smth thx man <3
Click to expand...
Click to collapse
[OP7T][OOS 11.0.5.1 HD65AA/BA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com

i cant find the file for my current version and it doesnt work if i try it with the only version that is android 11

and i cant turn my phone back on
and after i installed the drivers i had to restart my pc and now there is this thing at the bottom right:
testmode
windows 10 pro
...

i waited until my phone had no more battery charge and now im bootlooping again :/

nvm it just booted

im downgrading it now and i dont get the error "smth communication smth" in msmtool anymore
alr it worked my phone is wiped again but i can turn on wifi and sound
but how do i root my phone now? I have an Idea, im gonna write step by step what i think gets me a rooted phone please confirm if that would not break my phone ^^' (bootloader already unlocked)
1. enable usb debugging and allow my pc
2. download and install the latest magisk version from the github
3. download magisk patched boot.img for ver 11.0.5.1BA BUT since i cant find anything on the internet im gonna have to use the zip file from the unbrick tool thing (https://onepluscommunityserver.com/list/Unbrick_Tools/OnePlus_7T/EU_HD65BA/R/) and then patch the boot.img using magisk myself
4. then use platform tools and type following commands: "adb reboot fastboot", "fastboot flash boot {the patched boot image file}"
5. then use magisk to direct install the root thing

i just realisized the unbrick thing that i wanted to use instead of a boot.img doesnt have a boot.img in it... WHERE CAN I FIND A BOOT.IMG brooo androidfilehost.com doesnt have it the unbrick tool doesnt have it
omg i realized i could update my phone to 11.0.9.1 then download the same version from official website and use the dumper to get the boot.img **** meee

wait it sais its 11.0.9.1HD65 AA and not BA **** me

k nvm i just changed the site settings to germany and now its BA

i just went for it and now my phone is rooted thank you very much for your help i would've prob tried to revert back to stock for like 2 weeks and then cry that i cant root my phone thank you so much xd

Question Google pixel 6 pro bootloops after root

I have been trying for a while now to root my phone with magisk. Everytime I go to root it at the end I go into a boot loop and can't go to recovery then I have to reinstall the version of Android 13 I'm using but still never rooted when I do so.

Samuel1307 said:
I have been trying for a while now to root my phone with magisk. Everytime I go to root it at the end I go into a boot loop and can't go to recovery then I have to reinstall the version of Android 13 I'm using but still never rooted when I do so.
Click to expand...
Click to collapse
Do you have TWRP installed?

webhook said:
Do you have TWRP installed?
Click to expand...
Click to collapse
No

Samuel1307 said:
I have been trying for a while now to root my phone with magisk. Everytime I go to root it at the end I go into a boot loop and can't go to recovery then I have to reinstall the version of Android 13 I'm using but still never rooted when I do so.
Click to expand...
Click to collapse
Rooting pixel phones are pretty straight forward and not much difficulties. Two different approaches:
1. If you are an experienced user and 100% sure what you are doing, then go back to your rooting process step by step to make sure you didn't miss anything.
2. If you are not sure that you have done everything correctly, then I would suggest you that you follow the steps which describe in this thread, believe it still the most detail explanation for rooting the pixel phones even today. https://forum.xda-developers.com/t/...ootloader-update-root-pass-safetynet.4356231/
Also posting your question on this thread could get you quicker response.
If after your trying of everything you still couldn't get it done, then describe your entire process when you ask for help without people have to guess what could went wrong.
PS: The only information which you shouldn't follow with that thread is "NOT" to use the latest platform tool, stay with version 33.0.3, version 34.0.1 has problem.

Samuel1307 said:
I have been trying for a while now to root my phone with magisk. Everytime I go to root it at the end I go into a boot loop and can't go to recovery then I have to reinstall the version of Android 13 I'm using but still never rooted when I do so.
Click to expand...
Click to collapse
I had the same issue. Right after flashing when booting for the first time it got stuck in a boot loop. Factory reset fixed it.

Stupid question also could be the wire your using and usb port

If you guys are bootlooping after flashing Magisk patched image...
You should use the Google's official Android Flash Tool to reset your device to a working state...
Then you should use badabing2003's PixelFlasher to root; it automates most of what's needed to root, and it has checks and protocols to make sure files are correct, versions are correct, and the right procedure happens in the right order -- taking out a lot of guesswork or mis-steps that might be happening that is causing bootloops.
Many/You would be surprised how many times PixelFlasher succeeds where many have failed; almost miraculously and/or inexplicably! It's why it's become rather famous tool for Pixels...

Samuel1307 said:
I have been trying for a while now to root my phone with magisk. Everytime I go to root it at the end I go into a boot loop and can't go to recovery then I have to reinstall the version of Android 13 I'm using but still never rooted when I do so.
Click to expand...
Click to collapse
fluxfield said:
I had the same issue. Right after flashing when booting for the first time it got stuck in a boot loop. Factory reset fixed it.
Click to expand...
Click to collapse
Previously rooted with Magisk modules?
Incompatibility with newer updates is more often than not the cause of bootloops.
Rebooting into safe mode will disable them.
Press and hold volume down when the bootloader unlocked warning screen appears. Then let go as soon as you feel a vibration.
You will boot into safe mode and modules will be disabled.
Then reboot normally and go into Magisk and re-enable only safe modules such as USNF.
Test the others one by one until you find the culprit. Usually it will be a font changing module or an AOSP mod .

It's pretty straightforward provided you have an unlocked bootloader, USB debugging and platform tools, The latest works for root alone btw.
In terminal
Code:
adb devices
Authorise adb in the popup window
Code:
adb reboot bootloader
If fastboot isn't recognising your phone install the USB driver
You may find it easier to install the driver in fastboot.
Code:
fastboot flash boot <path_to_magiskboot.img>
Code:
fastboot reboot
Profit.
Assuming you've patched the right boot.img file from the .zip within the factory image zip file and you're using magisk from github.

fil3s said:
You may find it easier to install the driver in fastboot.
Code:
fastboot flash boot <path_to_magiskboot.img>
Click to expand...
Click to collapse
Accidental mistake.... "image" was meant, not "driver".
...don't want OP chasing down an issue because of a miscommunication or confusion...
PixelFlasher is truly the easiest & most straightforward, honestly....

simplepinoi177 said:
Accidental mistake.... "image" was meant, not "driver".
...don't want OP chasing down an issue because of a miscommunication or confusion...
PixelFlasher is truly the easiest & most straightforward, honestly....
Click to expand...
Click to collapse
I meant that sometimes the google USB driver is easier to install in fastboot. Regards

fil3s said:
I meant that sometimes the google USB driver is easier to install in fastboot. Regards
Click to expand...
Click to collapse
aaahh...i see now...
sorry, i just made that assumption because you put the fastboot command to installing/flashing the image right after the sentence -- i made the mistake of connecting the two...
i should've known better as i was already initially confused as you don't install the driver AS a fastboot command...!