Hi there , after soft bricking my phone intentionally because i wanted to downgrade form O to MM which i thought it would be relatively easy to find a stock firmware(the full one) well ...(i was wrong), Xda is not as content rich as you may think, and no one seems to offer any advice or answer for that matter, compared to other forums it lacks a lot.
After flashing more than 5 corrupted firmwares i found one that is working perfectly fine.
Steps:
1-Enter fastboot ( power + vol up)
2- Run (flashall_AFT.cmd) , download link below.... (this is the full firmware no bull**** no missing files) .
That's it... piece of cake
First impression: the bass is more rich and vibrant as many have said so cause the O version was an absolute rubbish like it's battery life , i'm yet to see the battery performance on this MM and i'll be updating the thread with SOT SS after flashing Magisk and installing debloater module.
Download link :
<Mod edit: Link removed>
There are some other newer N full versions but i haven't tested them.
[
i already had that file which i got a few months ago but never used it. i was a noob about this zenfone.
but ur title says its mm, its not , its nougat, 7.11. its the last nougat b4 oreo was released, it uses the same base fw, iirc, as my post about manually flashing 7.11 but without the radios, https://forum.xda-developers.com/zenfone-3-zoom/how-to/manually-update-to-7-11-t3815703
my memory could be wrong though, but file name suggests its 7.11
- [firmware27]WW_ZE553KL_71.60.139.30_MR4_user_20180306173656_release.zip
long story short i eventually flashed it a couple of weeks ago, it does flash successfully, well most of the time, and looks legit, i just wish i knew its original source, i think it was someone named marco, as theres lots of files within that zip.....but it seems legit.
but why are u hosting it on the clickbait site. i might up it to androidfilehost which is a no bs hosting site.
i did create a twrp flashable full stock 6.01 mm firmware, im still testing it as it doesnt always flash completely in twrp, about 8 out of 10 times it flashes correctly. but its hard to test on a dead no display/no touch screen phone
edit: correction, not clickbait, but need to signup
vincom said:
[
i already had that file which i got a few months ago but never used it. i was a noob about this zenfone.
but ur title says its mm, its not , its nougat, 7.11. its the last nougat b4 oreo was released, it uses the same base fw, iirc, as my post about manually flashing 7.11 but without the radios, https://forum.xda-developers.com/zenfone-3-zoom/how-to/manually-update-to-7-11-t3815703
my memory could be wrong though, but file name suggests its 7.11
- [firmware27]WW_ZE553KL_71.60.139.30_MR4_user_20180306173656_release.zip
long story short i eventually flashed it a couple of weeks ago, it does flash successfully, well most of the time, and looks legit, i just wish i knew its original source, i think it was someone named marco, as theres lots of files within that zip.....but it seems legit.
but why are u hosting it on the clickbait site. i might up it to androidfilehost which is a no bs hosting site.
i did create a twrp flashable full stock 6.01 mm firmware, im still testing it as it doesnt always flash completely in twrp, about 8 out of 10 times it flashes correctly. but its hard to test on a dead no display/no touch screen phone
Click to expand...
Click to collapse
Yeah i saw your post a couple of days ago and it is legit , about the file hosting it's not clickbait it's just 4shared and this little guy is older than the xda :laugh::laugh: , i agree that the androidfilehost is faster and more convenient but i'm not the uploader , i just copied it from another source, it would be great if you re-upload it for others and i will update the link.
Now we come to testing: i tested this myself and it is 6.0.1 for sure but i don't remember which release it was cause i updated to 7.1.1 20.32.67.25 release for various reasons, mainly for battery life (spoiler: not much difference and it's still poor) and i will keep flashing / debloating apparently in (in search of incredible) but i'm quite sure this phone is hopeless without a custom ROM from scratch as the amount of services and wakelocks are enormous.
Why don't you participate and use your knowledge in the "allegedly upcoming" Lineage 15.1 hopefully we get a working build before the end of the year :cyclops: i'm sure you are aware of the situation.
And if you're into kernels then kernelwise this phone's kernel was made by noobs ,ASUS put an AMOLED display and they are not using it's features as the blacks are lit and power consumption by the screen is well above an LCD one of the same size.
Long story short buying this phone was/is a mistake.
I actually found the site firmware27 that was hosting 8 ww fw and a couple of cn and jp sku fw.
I tested all 8 ww skus, only 2 work without effort, 6.0.1 dated deb 2017, and the 7.1.1 which I had from a couple of months ago and use the img files in my other thread and which i though u linked here.
Ill be posting a thread and links to both of these files that i ul to afh, and my usage of them, I came to the conclusion that they are asus's fw given to their authorized service centers, they include everything not even available through asus's fw from their site.
Too bad he got most of the files corrupted when he ul'd them to g-drive, my guess
at least now we got 2 fw files to work with, but its a pia to make it a twrp non wipe flashable zip, beyond my skills at this point in time.
edit: i have the one u have linked here which i got a couple of months ago, WW-ZE553KL-11.40.86.71-MR0-user-20170410214554-release.zip,
but firmware27 doesnt have it, and i cant remember where i got it, and by its date youre correct it must be 6.0.1, nougat fw starts with "V20".
so there are actually 3 working fastboot flashable FW out in the wild, boy arent we lucky
i have this phone because a couple of months ago i helped my friend flash fw on it because he was getting poor data signal, i soft bricked and had to learn how to unbrick it, which i did.
its mine as a couple of weeks ago, he dropped it a few feet onto ceramic floor and the screen is dead, no display, no touch, lcd is cracked under the top glass which actually has no cracks, and thats how im using it lol.
i was going to use it as a security camera but i had to learn how to control it remotely, which i did, that was a flashing adventure w/out a working screen
vincom said:
I actually found the site firmware27 that was hosting 8 ww fw and a couple of cn and jp sku fw.
I tested all 8 ww skus, only 2 work without effort, 6.0.1 dated deb 2017, and the 7.1.1 which I had from a couple of months ago and use the img files in my other thread and which i though u linked here.
Ill be posting a thread and links to both of these files that i ul to afh, and my usage of them, I came to the conclusion that they are asus's fw given to their authorized service centers, they include everything not even available through asus's fw from their site.
Too bad he got most of the files corrupted when he ul'd them to g-drive, my guess
at least now we got 2 fw files to work with, but its a pia to make it a twrp non wipe flashable zip, beyond my skills at this point in time.
edit: i have the one u have linked here which i got a couple of months ago, WW-ZE553KL-11.40.86.71-MR0-user-20170410214554-release.zip,
but firmware27 doesnt have it, and i cant remember where i got it, and by its date youre correct it must be 6.0.1, nougat fw starts with "V20".
so there are actually 3 working fastboot flashable FW out in the wild, boy arent we lucky
i have this phone because a couple of months ago i helped my friend flash fw on it because he was getting poor data signal, i soft bricked and had to learn how to unbrick it, which i did.
its mine as a couple of weeks ago, he dropped it a few feet onto ceramic floor and the screen is dead, no display, no touch, lcd is cracked under the top glass which actually has no cracks, and thats how im using it lol.
i was going to use it as a security camera but i had to learn how to control it remotely, which i did, that was a flashing adventure w/out a working screen
Click to expand...
Click to collapse
All you need is one fw to start with and after that you can update to whichever release you want without any problem , strait forward from asus site and update via sd card even if it's rooted or bootloader unlocked, you can do anything and even get updates as FOTA app works as soon as you boot cause asus update procedure is very primitive HOWEVER it should be on stock recovery and honestly twrp is pretty much useless here and i didn't seem to need it in anything with this device!! (i use magisk to root), it's not like there's half a dozen of custom ROMs to flashed , the only possible modification is within the stock fw and that's our limit.
If you find a screen replacement under 50$ it is worth it , i knew that 2.5D glass is poor engineering and very fragile, so screen protector and case was crucial since day 1.
Notes:
Don't trust asus download center's description cause i downloaded the latest nougat release before the Oreo (as described in their section) and it turned out to be the first release of their lousy O fw.
cheapest on ebay is over $70can for aftermarket from china. cheap clone? idk
i'll stick w/my note 4 can version as my dd.
i'll upload the working fw i found for redundancy and to give users more options, 4 fw as of now.
i do have the last 7.1.1 b4 oreo
these are actual service tech fw's available to them for restoring phones. supposedly can be use by asus flash tool which i haven't used yet.
they dont change the bootloader lock status or the frp/google account status (to do that use fastboot wipe config)
since it is in a raw format the individual files can be flashed via fastboot for those that would need it.
fyi all fw are exactly the same except for the recovery, boot, system and , emmc_appsboot_8953.mbn(bootloader ?), the radios and other files are the same
i cant use the builtin updater because i cant seem to get the right button combo to work in stock recovery to flash the update and thats after i reinstall the stock recovery and remove root, flashing from bootloader is a breeze.
the only one i can't get adb enabled so i can mirror the screen is the mm 11.40.86.71, the same one you have linked here
when i try to make a custom stock flashable rom it always fails to boot, would u know why?,
vincom said:
cheapest on ebay is over $70can for aftermarket from china. cheap clone? idk
i'll stick w/my note 4 can version as my dd.
i'll upload the working fw i found for redundancy and to give users more options, 4 fw as of now.
i do have the last 7.1.1 b4 oreo
these are actual service tech fw's available to them for restoring phones. supposedly can be use by asus flash tool which i haven't used yet.
they dont change the bootloader lock status or the frp/google account status (to do that use fastboot wipe config)
since it is in a raw format the individual files can be flashed via fastboot for those that would need it.
fyi all fw are exactly the same except for the recovery, boot, system and , emmc_appsboot_8953.mbn(bootloader ?), the radios and other files are the same
i cant use the builtin updater because i cant seem to get the right button combo to work in stock recovery to flash the update and thats after i reinstall the stock recovery and remove root, flashing from bootloader is a breeze.
when i try to make a custom stock flashable rom it always fails to boot, would u know why?,
Click to expand...
Click to collapse
I would say let's find a solution to the easy problem and not the to hard one, you want to take 2 blurry steps instead of 2 obvious ones !! i can help you with stock ones just explain more what's the exact problem ? i didn't understand so correct me if i'm wrong : you have no visual indication as the screen is dead right ? or can't boot into the stock recovery at all ?
if you have the bootloader unlocked and no screen indication :
power up wait for the vibration and press volume down 4 times then press power to boot into recovery
wait 10 sec and press volume down 2 times to (update form sd card)
rename the fw .zip file to A so it can be sorted first and it should be in root directory and alone to prevent any miss hits and press volume down 1 time.
and if that didn't work just flash the fw that's provided and redo the steps if you want to update , congratulations now you have a working internals and up to date phone that you can't even boot into it's home screen cause the boot confirmation by email and password is near impossible to bypass without a working display. (there is some methods though )
I don't see the point of a phone without a display at least temporary.
This phone is a joke in it's normal condition let alone in the non , don't waste your time and sell it as parts, if you get 40$ take it.
sam.fisher190 said:
I would say let's find a solution to the easy problem and not the to hard one, you want to take 2 blurry steps instead of 2 obvious ones !! i can help you with stock ones just explain more what's the exact problem ? i didn't understand so correct me if i'm wrong : you have no visual indication as the screen is dead right ? or can't boot into the stock recovery at all ?
if you have the bootloader unlocked and no screen indication :
power up wait for the vibration and press volume down 4 times then press power to boot into recovery
wait 10 sec and press volume down 2 times to (update form sd card)
rename the fw .zip file to A so it can be sorted first and it should be in root directory and alone to prevent any miss hits and press volume down 1 time.
and if that didn't work just flash the fw that's provided and redo the steps if you want to update , congratulations now you have a working internals and up to date phone that you can't even boot into it's home screen cause the boot confirmation by email and password is near impossible to bypass without a working display. (there is some methods though )
I don't see the point of a phone without a display at least temporary.
This phone is a joke in it's normal condition let alone in the non , don't waste your time and sell it as parts, if you get 40$ take it.
Click to expand...
Click to collapse
not impossible, very doable to use a phone even with a dead screen.
after alot of trials and error ...from a new flashed stock thats was completely wiped, i can get to a remotely controlled/viewed phone in about 10mins .
i will write up a tut on that.
i can get that done with all the availabe working raw fw except with the mm 2017/04 release
yes, i have a completely dead screen, no display, no touch. all other phone functions work.
the reason for stock recovery procedure was to update to oreo, but i really dont care if i get it. just seeing if its doable.
playing with it for giggles, going to be a security camera as the cam is vg, useless as a phone that has no working screen.
i can be the sacrificial tester if need be, pretty hard to hardbrick this phone as i also have the back cover off so to disconnect the battery connector for those hard soft brick occasions and/or to make sure phone was completely off b4 doing something
I think I killed my phone please help Asus ze553kl
This was happened my phone is Asus ze553kl android Oreo NOTE: I already rooted my phone unlocked bootloader using Asus tool installed twrp and magisk...
when I was using whatapp suddenly my screen got frozen and I restarted my phone it stuck in Asus logo I tried does it goes into twrp even twrp also stuck in logo then I tried flashing using adb and fastboot while doing that I entered this COMMAND fastboot format or erase boot after I flashed everything I rebooted this time it gone worse there is no logo I see only powered by android then no hope after I saw this thread and planned to downgrade downloaded 2gb file and I made clean flashing manually no use i don't see the logo again then I went for auto flashall command when I clicked that something happens it said searching for your device but
After waited for so long I unplugged the cable try to on the phone it's fully blank no sign of power pls help guys I'm begging you all please reply and give me a solution
Nikido2930 said:
This was happened my phone is Asus ze553kl android Oreo NOTE: I already rooted my phone unlocked bootloader using Asus tool installed twrp and magisk...
when I was using whatapp suddenly my screen got frozen and I restarted my phone it stuck in Asus logo I tried does it goes into twrp even twrp also stuck in logo then I tried flashing using adb and fastboot while doing that I entered this COMMAND fastboot format or erase boot after I flashed everything I rebooted this time it gone worse there is no logo I see only powered by android then no hope after I saw this thread and planned to downgrade downloaded 2gb file and I made clean flashing manually no use i don't see the logo again then I went for auto flashall command when I clicked that something happens it said searching for your device but
After waited for so long I unplugged the cable try to on the phone it's fully blank no sign of power pls help guys I'm begging you all please reply and give me a solution
Click to expand...
Click to collapse
sounds like a hardware failure not a software/firmware problem, let it rip, time for another phone, phone not worth getting it repaired even if u do it yourself
vincom said:
sounds like a hardware failure not a software/firmware problem, let it rip, time for another phone, phone not worth getting it repaired even if u do it yourself
Click to expand...
Click to collapse
sam.fisher190 said:
Hi there , after soft bricking my phone intentionally because i wanted to downgrade form O to MM which i thought it would be relatively easy to find a stock firmware(the full one) well ...(i was wrong), Xda is not as content rich as you may think, and no one seems to offer any advice or answer for that matter, compared to other forums it lacks a lot.
After flashing more than 5 corrupted firmwares i found one that is working perfectly fine.
Steps:
1-Enter fastboot ( power + vol up)
2- Run (flashall_AFT.cmd) , download link below.... (this is the full firmware no bull**** no missing files) .
That's it... piece of cake
First impression: the bass is more rich and vibrant as many have said so cause the O version was an absolute rubbish like it's battery life , i'm yet to see the battery performance on this MM and i'll be updating the thread with SOT SS after flashing Magisk and installing debloater module.
Download link :
<Mod edit: Link removed>
There are some other newer N full versions but i haven't tested them.
Click to expand...
Click to collapse
THREAD CLOSED and download link removed. 4shared.com requires to have an account for downloading i.e. not accepted as file host on XDA.
Please advise the moderators' team when ready to provide a download link from an accepted file host.
I waited to write here, if the March 2020 patches solved the problem, but unfortunately it is not...
several nokia comunity users have the same problem and nokia is not responding about It.
having Nokia 8.1, I gave Nokia 7.1 to my girlfriend last year ... great smartphone, the Android 10 update work very well, but the February 2020 patch was a disaster!
Probably it didn't install well, and then the phone asked for a factory restart.
the problem is that the Factory reset did not come back to a pre-February patch state, but always brings it to the point of "restarting the phone to finish installing the February patch".
and immediately the restart is requested, which can be postponed, but not indefinitely, so after fifteen days the smartphone restarts by itself, and freezes again asking for a factory reset!
in an endless loop!
I think I have to do a system flash to bring the phone back to a previous stable state, right?
Can you help me on the procedure to follow?
I have never unlocked the bootloader and all the rest
thank you guys
My friend has the same issue.
well you have two solutions here
1) Pause your updates so your phone never installs them
2)Get your phone flashed with the stock firmware , and if you want get it unlocked.
I have spent about 2 months trying to fix the issue but in the end I got the phone flashed which fixed the problem.
The issue comes due to your phone not being able to verify the selected partitions for boot which is why it asks you to reset.
thanks for the answer!
the guarantee is still active,
I think I will send it to nokia assistance, as soon as next week I will be able to see my girlfriend (for the emergency covid19 I haven't seen her for 60 days, but next week there is the unlock down).
meanwhile I took for her a Nokia 4.2 to be used as a replacement.
I hope Nokia's lab assistance will flash the system quickly and better than what I could do
PCIHD said:
well you have two solutions here
1) Pause your updates so your phone never installs them
2)Get your phone flashed with the stock firmware , and if you want get it unlocked.
I have spent about 2 months trying to fix the issue but in the end I got the phone flashed which fixed the problem.
The issue comes due to your phone not being able to verify the selected partitions for boot which is why it asks you to reset.
Click to expand...
Click to collapse
Can you show me to a thread or video for option 2)?
Hey, So yesterday I got the stupid idea to try out Android 13 QRP Beta 1.
I heard praise of Pixel-Flasher which helps out in Updating & maintaining root. Around 2 weeks ago I updated from Android 12 Stable to Android 13 Stable using ADB sideload & lost root, booting with magisk-patched img results in bootloop, So I ran the phone with my banking apps broken and without root for 2 weeks. I had enough and thought let's start fresh on QRP with proper root. So, I backed up all my data and prepared my Pixel 6 for formatting.
Finally, I tried my shot with Pixel-Flasher and read all instructions for usage, it was running pretty laggy on my M1 MBP. NOTE: I'm not Blaming the developer of Pixel-Flasher for anything, and I'm completely responsible for probably performing the wrong steps coming below.
I downloaded the factory zip for the latest Android 13 Sep Update [was running Aug], extracted and patched the boot.img using Pixel-Flasher and Magisk on my Pixel 6. Chose the option to WIPE Data and selected the patched-magisk.img and proceeded to flash. And I'm pretty sure this is where I screwed up by not selecting the stock img. The procedure went through and finally, my Phone flashed Phone is corrupted and will not boot, clicked the Power Button & it got stuck on the Google Logo. As it was stuck there I forced it to reboot and it went into fastboot d. I was sure I did something wrong so I powered it off and tried to boot into fastboot now... Black Screen no response, Connected charger... no response, Connected USB and held power + vol down for 60 secs... no response. The phone was at 95% so not battery dead by any chance.
This is where I diagnosed that I bricked the Motherboard. To add fire to the pot, I live in India & got this phone from my Uncle. No warranty in India.
Now I'm sitting here with regret and a 200g Paperweight. There is a Repair Shop called ShatterFix here in India that services Pixel 6 unofficially, and I'm considering sending in the phone for diagnosis. What I'm worried about is that the Motherboard replacement part itself costs close to ₹20,000 - ₹25,000 INR.
Any suggestions or help is welcome for a boy in misery. Had a great time with my Pixel 6 for 8 months, fell back to using my OnePlus 6T now.
Thanks, this is my first time posting a large essay thread like this. Sorry if it had useless info or if anything wasn't clear.
If you haven't tried https://flash.android.com/ then I'd suggest giving it a shot. You never know if it works..
I had the same issue on my 4a a while ago, nothing seemed to be working but then i used this, it detected the phone and flashed the latest version.
Aks said:
If you haven't tried https://flash.android.com/ then I'd suggest giving it a shot. You never know if it works..
I had the same issue on my 4a a while ago, nothing seemed to be working but then i used this, it detected the phone and flashed the latest version.
Click to expand...
Click to collapse
I did try that, as I can't even boot the phone into fastboot or ADB, the device is not detected
suhas2k said:
Hey, So yesterday I got the stupid idea to try out Android 13 QRP Beta 1.
I heard praise of Pixel-Flasher which helps out in Updating & maintaining root. Around 2 weeks ago I updated from Android 12 Stable to Android 13 Stable using ADB sideload & lost root, booting with magisk-patched img results in bootloop, So I ran the phone with my banking apps broken and without root for 2 weeks. I had enough and thought let's start fresh on QRP with proper root. So, I backed up all my data and prepared my Pixel 6 for formatting.
Finally, I tried my shot with Pixel-Flasher and read all instructions for usage, it was running pretty laggy on my M1 MBP. NOTE: I'm not Blaming the developer of Pixel-Flasher for anything, and I'm completely responsible for probably performing the wrong steps coming below.
I downloaded the factory zip for the latest Android 13 Sep Update [was running Aug], extracted and patched the boot.img using Pixel-Flasher and Magisk on my Pixel 6. Chose the option to WIPE Data and selected the patched-magisk.img and proceeded to flash. And I'm pretty sure this is where I screwed up by not selecting the stock img. The procedure went through and finally, my Phone flashed Phone is corrupted and will not boot, clicked the Power Button & it got stuck on the Google Logo. As it was stuck there I forced it to reboot and it went into fastboot d. I was sure I did something wrong so I powered it off and tried to boot into fastboot now... Black Screen no response, Connected charger... no response, Connected USB and held power + vol down for 60 secs... no response. The phone was at 95% so not battery dead by any chance.
This is where I diagnosed that I bricked the Motherboard. To add fire to the pot, I live in India & got this phone from my Uncle. No warranty in India.
Now I'm sitting here with regret and a 200g Paperweight. There is a Repair Shop called ShatterFix here in India that services Pixel 6 unofficially, and I'm considering sending in the phone for diagnosis. What I'm worried about is that the Motherboard replacement part itself costs close to ₹20,000 - ₹25,000 INR.
Any suggestions or help is welcome for a boy in misery. Had a great time with my Pixel 6 for 8 months, fell back to using my OnePlus 6T now.
Thanks, this is my first time posting a large essay thread like this. Sorry if it had useless info or if anything wasn't clear.
Click to expand...
Click to collapse
Sounds like you never flashed, at the minimum, the A13 bootloader, or the A13 image, to the other slot and when you ran into problems your phone reverted to the other slot which still had A12 on it, therefore causing you to brick your phone due to the new ARB (anti-rollback protection).
Not familiar with things in India, but I would at least try contracting Google and explaining that your phone died and you think it was because of the new anti-rollback protection they implemented in the A13 bootloader. From observations, they seem to be pretty good at either fixing or replacing devices that have run into this problem, maybe even without a warranty. Worth a shot...
suhas2k said:
I did try that, as I can't even boot the phone into fastboot or ADB, the device is not detected
Click to expand...
Click to collapse
Did you install the drivers from Google for ADB and fastboot?
Without these, the device can't be detected.
Cheers
tom1807 said:
Did you install the drivers from Google for ADB and fastboot?
Without these, the device can't be detected.
Cheers
Click to expand...
Click to collapse
Yes, for past 8 months I was updating with root using adb side load so yes, both fastboot & adb drivers are properly installed.
Lughnasadh said:
Sounds like you never flashed, at the minimum, the A13 bootloader, or the A13 image, to the other slot and when you ran into problems your phone reverted to the other slot which still had A12 on it, therefore causing you to brick your phone due to the new ARB (anti-rollback protection).
Not familiar with things in India, but I would at least try contracting Google and explaining that your phone died and you think it was because of the new anti-rollback protection they implemented in the A13 bootloader. From observations, they seem to be pretty good at either fixing or replacing devices that have run into this problem, maybe even without a warranty. Worth a shot...
Click to expand...
Click to collapse
Looks like you are right, it's ARB issue.
I did try contacting the B2X Service Centers in India and they only service now 6a but not the 6.