Related
Hey guys, i've a big problem.
Yesterday, suddently my nexus s didn't boot. It was stucked on Google logo.
It's rooted and it has the cm7 rom.
I tryed to reflash with cw recovery but i have an issue.
I cannot copy nothing on the sdcard partition.
I mount it with recovery and correctly copy the img from my pc. After i sync and dismount but if i remount the sdcard i cannot see the file that i've copied before.
It seems strange because if i try to format sdcard from recovery it says "done" but the data still remain.
After that i tried to lock and reunlock my phone but it fail.
I launch the command fastboot oem unlock, correctly the two-choices window appear, i select yes but on my pc i see (erase fail) and bootload remain unlocked.
Please give me some advice to resurrect my phone.
Thanks for the support, and sorry for my bad english.
Emiliano
fastboot oem unlock wont lock it, use fastboot oem lock.
i need to unlock it. i've locked now i need to unlock.
But the procedure
fastboot oem unlock
fail with erase fail errore.
I had almost the exact same problem yesterday. Tried literally everything and nothing worked. In fact it kept getting a little worse with every battery pull/reboot.
I purposely re locked the boot loader, right before I went to Sprint and paid $38 for a working replacement.
Probably be a good long while before I root another phone.
Sent from my Nexus S 4G using Tapatalk
After 4.0.4 OTA update device is bricked.
I have experienced the same issue you are discussing here.
A couple of days ago I received an OTA update to android 4.0.4 for my Nexus S device, vodafone UK. My phone is NOT rooted or OEM unlocked. The update downloaded but fails to install on reboot. The phone just returns to the original state, with the update waiting to install.
Any app or software will not work on the device, force closes error. If I attempt to restore to any factory settings or wipe / format the phone by any method you can come up with in a google search!, once the device reboots this change is ignored. If I copy any file on the Mass storage via usb, after the phone reboots the file is gone.
I've attempted to unlock the oem to flash the device in an attempt to resolve this, however when using ./fastboot oem unlock I get the following error:
... FAILED (remote: Erase Fail)
It seems the device has been screwed some how after receiving this update. It can only be a hardware error now....
Who is now responsible to fix this? i have had this Nexus S over 1 year now, can I take to Samsung or Vodafone for these guys to get repaired?
Sounds like hardware issue. Have you tried formatting the sdcard in windows or running chkdsk /F.
I Have Same Problem how can i fix it?
LeeVidor said:
I have experienced the same issue you are discussing here.
A couple of days ago I received an OTA update to android 4.0.4 for my Nexus S device, vodafone UK. My phone is NOT rooted or OEM unlocked. The update downloaded but fails to install on reboot. The phone just returns to the original state, with the update waiting to install.
Any app or software will not work on the device, force closes error. If I attempt to restore to any factory settings or wipe / format the phone by any method you can come up with in a google search!, once the device reboots this change is ignored. If I copy any file on the Mass storage via usb, after the phone reboots the file is gone.
I've attempted to unlock the oem to flash the device in an attempt to resolve this, however when using ./fastboot oem unlock I get the following error:
... FAILED (remote: Erase Fail)
It seems the device has been screwed some how after receiving this update. It can only be a hardware error now....
Who is now responsible to fix this? i have had this Nexus S over 1 year now, can I take to Samsung or Vodafone for these guys to get repaired?
Click to expand...
Click to collapse
please anyone can help me how can i fix my mobile ...
You can't. It's a hardware common issue without any solution. Better sent it to repair. My two cents
Sent from my
( •_•)
( •_•)>⌐■-■
Nexus S
(⌐■_■)
YYYYYYYEEEEEAAAAAAAAAAHHHHHHHHHHHH
sammme problem har you fix it?
benazhack said:
i need to unlock it. i've locked now i need to unlock.
But the procedure
fastboot oem unlock
fail with erase fail errore.
Click to expand...
Click to collapse
please help me if u get the solution plz
zaherrrr said:
please help me if u get the solution plz
Click to expand...
Click to collapse
Already been posted, you can't, warranty repair or you need to replace the main board(guessing £100-200?)
Sent from my ice cream powered Nexus S
DarkhShadow said:
Already been posted, you can't, warranty repair or you need to replace the main board(guessing £100-200?)
Sent from my ice cream powered Nexus S
Click to expand...
Click to collapse
Just figured something out, i had the same issues as described above, could only boot the phone with a hair dryer
The new update Jelly Bean 4.1.1 is more forgiving when it comes to booting (probably voltages of the internal SD!! I'm still testing, but as far as i can see now, the phone boots normally again now (no more stuck on the google logo)
My problems:
- Not able to unlock bootloader (erase failed).
- Not possible to boot normally due to faulty internal SD card (only able to boot with the 'hairdryer' trick).
What did i do:
- Just tried the same as the trick on booting: use the hairdryer when fastbooting!!!
- Have everything ready; cmd, fastboot files, drivers etc, phone connected to computer with USB.
- Try to boot it first after heating the phone with the hairdryer (get past the google logo) and then immediately remove the battery.
- Then boot into fastboot mode (power and vol. up).
- Immediately execute the 'fastboot oem unlock' command.
Voila, that did the trick for me. Status OKAY and my bootloader was unlocked.
Then ROOT and update the phone to 4.1.1 with the following instructions:
(not able to unclude link, see webtrickz dot com/guide-to-manually-update-nexus-s-i9020ti9023-to-android-4-1-1-jelly-bean)
That did the trick for me!
NO MORE HAIRDRYER FOR ME!!
OEM unlock FAILED (remote: Erase Fail)
Hi
I'm replying to this message to share my experience about the same issu i had.
I bought a broken nexus s on google, auction described the phone as messed up during some software update. When cell got here:
- Bootloader was loading and locked
- Bootloader was reporting no boot image and no recovery
- Recovery was flashed with cwm 6.0.1.0
When trying to oem unlock, I was getting "FAILED (remote: Erase Fail)" no matter what I try. My config was good i've unlocked many nexus s with the same setup.
In recovery I was not able to mount sdcard, system, boot, nothing was working as it should.
After many frustrating hours, i saw this post.. What a stupid idea.. But I have nothing to loose at this point.
I don't have a hair dryer but I do have an oven. I figured the idea was to get the phone really hot..
Set the oven to 170, convection on and cooked the phone without the battery and cover for about 5 minutes until it was really hot but not melting.
Did the oem unlock and guess what.. It worked on first try.
After that I was able to update bootloader, radio, recovery and installed latest cm10. I've wipped the phone a couple of time, tried everything I could think of to test if something is not working, but everything does..
No hair dryer?
Just cook you phone at 170 for 5 minutes.
Worked for me.. go figure..
hetile
TimeClypse said:
Just figured something out, i had the same issues as described above, could only boot the phone with a hair dryer
The new update Jelly Bean 4.1.1 is more forgiving when it comes to booting (probably voltages of the internal SD!! I'm still testing, but as far as i can see now, the phone boots normally again now (no more stuck on the google logo)
My problems:
- Not able to unlock bootloader (erase failed).
- Not possible to boot normally due to faulty internal SD card (only able to boot with the 'hairdryer' trick).
What did i do:
- Just tried the same as the trick on booting: use the hairdryer when fastbooting!!!
- Have everything ready; cmd, fastboot files, drivers etc, phone connected to computer with USB.
- Try to boot it first after heating the phone with the hairdryer (get past the google logo) and then immediately remove the battery.
- Then boot into fastboot mode (power and vol. up).
- Immediately execute the 'fastboot oem unlock' command.
Voila, that did the trick for me. Status OKAY and my bootloader was unlocked.
Then ROOT and update the phone to 4.1.1 with the following instructions:
(not able to unclude link, see webtrickz dot com/guide-to-manually-update-nexus-s-i9020ti9023-to-android-4-1-1-jelly-bean)
That did the trick for me!
NO MORE HAIRDRYER FOR ME!!
Click to expand...
Click to collapse
hetile said:
Hi
I'm replying to this message to share my experience about the same issu i had.
I bought a broken nexus s on google, auction described the phone as messed up during some software update. When cell got here:
- Bootloader was loading and locked
- Bootloader was reporting no boot image and no recovery
- Recovery was flashed with cwm 6.0.1.0
When trying to oem unlock, I was getting "FAILED (remote: Erase Fail)" no matter what I try. My config was good i've unlocked many nexus s with the same setup.
In recovery I was not able to mount sdcard, system, boot, nothing was working as it should.
After many frustrating hours, i saw this post.. What a stupid idea.. But I have nothing to loose at this point.
I don't have a hair dryer but I do have an oven. I figured the idea was to get the phone really hot..
Set the oven to 170, convection on and cooked the phone without the battery and cover for about 5 minutes until it was really hot but not melting.
Did the oem unlock and guess what.. It worked on first try.
After that I was able to update bootloader, radio, recovery and installed latest cm10. I've wipped the phone a couple of time, tried everything I could think of to test if something is not working, but everything does..
No hair dryer?
Just cook you phone at 170 for 5 minutes.
Worked for me.. go figure..
hetile
Click to expand...
Click to collapse
I'm speechless..hair dryer works for me too!!! THANK YOU GUYS!
Hi I have stock Nexus S GT-9020T UK running ICS 4.0.3 (which I installed after the stock update failed - by placing the file on SD/Card in recovery mode and installing) . However I'm having problems with battery, radio (Wireless & 3G) and it won't re-boot after it's turned off. (I get round this by heating it up with a hairdryer then it will re-boot eek!).
So to try and resolve some of these issues I have tried to unlock the phone with fastboot. Fastboot runs ok 'fastboot devises' shows serial number but I get a failed message rather than an unlock. Phone just goes back to recovery screen as if nothing happened.
I was hoping to unlock, root and then try a different OS.
So next I have tried to re-install 4.0.3 but when in recovery mode I can't access the SD/Card to run the file. I get a failed to access E:/drive message.
Can anyone give me any pointers to help either unlock and root phone or re-install 4.0.3?
I have been following the relevant guides on these forums but am now stuck for ideas!
Thanks Dinger
I read somewhere about having to heat it up for it to boot. Ended up the nand chip was dying/dead. Exchange if you can else it looks like a hardware failure.
Sent from my SAMSUNG-SGH-I727 using xda premium
Thanks. bit disappointing, Samsung customer services suggested I tried Samsung Kies but my Nexus S was not recognised by that either. As it boots into recovery mode I was hoping it was a software problem rather than hardware.
Hello to you all, I am new to XDA and it is because of this problem I am having.
The other day, my N5 shut down unexpectedly and kept that virtual power button pressed (I've seen this happen to a lot of people). The next day, it stopped doing that, but the next big issue started: The phone was stuck on boot animation. Since then, I am not able to boot the phone, so I entered the bootloader (which is still functional) and tried to unlock the bootloader (I blame myself for not doing this since the beginning) from my PC but every time it reboots the phone to keep the changes, the bootloader locks itself again, preventing me to fastboot an image to my device
This is the main issue here, I can't start up my phone, the bootloader won't unlock and somehow, I can't ADB because my PC won't recognize the device. In other words, it seems my Nexus is bricked (may be the first Nexus in the history to be bricked).
I believe there must be a solution for this problem, can anyone help me please!?!?!
Thank you all!
this is how I fix mine.
Can you boot into recovery?
hongkongking said:
this is how I fix mine.
Can you boot into recovery?
Click to expand...
Click to collapse
Hey, thanks for this help, I'll let you know how that goes. And yes, I can boot into recovery.
My device isnt recognized on ADB, and everytime I try to unlock the bootloader, when the device restarts, immeditaly locks the bootloader again.
did u factory reset and wipe dalvik / cache? did u install a correct PC driver? did you ever using adb to connect to your phone?
I remember someone said sometimes you need to unlock the bootloader several times to get it unlocked.
from this and this, your nand flash seems has problem.
Try using LG Flash Tool to flash facory image, it doesn't need to unlock bootloader, but i think it's better not to write anything to nand flash as you don't know if it has problem or not, do so might make your phone completely bricked.
hi - i have in my nexus 5 only the google logo and the unlocked key is on the screen;
when i get to fast boot it does see the device.
when ienter " fastboot oem device-info
igot device tampered true
device unlock true
off mode charge - true
when i try to write twrp recovery it says sending recovery okay and writing recovery okay.
but ucant enter to the recovery of twrp.
when i try to flash an image it says:
writing bootloader
failed (remoteflash write failure)
rebooting into bootloader okay
writing radio - failed remoteflash write failure
target reported max size of 1073741824bytes
is there any way to save my phone?
i can enter adb its says on the phone "now send the package you want to apply to the device with "adb sideload filename"..
how do i can send an image?
thank u
re
i try to flash with the lg flash rool - i did everything ok and it stuck in 6% and says"user data erase fail" what can i do?
You're using the batch commands included with the stock ROM to re-flash?
Hi my Nexus 5 also suddenly die too. And I have the same exact problem that you have when trying to flash it. I looked for hours on the internet tried formatting, erasing and many other alternatives and nothing. There are some people experiencing this same problem like us. For no reason the memory is getting corrupt or died. I get mant errors on the cache when I boot to regular recovery. The only recovery that I have manage to boot to (except for the original one) is Clockworkmod using fastboot boot "therecoveryname.img". With clockworkmod I have adb working but still can get the phone to boot or accept factory images. I can't lock the bootloader either.
I think this error was cause by the software. There was a very similar problem that never got fixed for the nexus 7 when lollipop came out.
Do you need to lock the bootloader? Once locked, you cannot flash anything via fastboot commands, not even a stock ROM.
No I don't need to. I tried just to see if the phone will relock itself. I read somewhere in the internet that if you can't relock/unlock the device the nand if fried.
If you look for these errors there are people with LG G2 and LG G3 that are having something similar happen. I think LG hardware is partly behind the problem. I call Google and told them about it and the put me through LG which want me to send the phone for repairs but not free. My guess is that it will be way to expensive to repair and that is not worthy.
Hopefully someone with real repair skill can give us light if this is something fixable by software.
audit13 said:
Do you need to lock the bootloader? Once locked, you cannot flash anything via fastboot commands, not even a stock ROM.
Click to expand...
Click to collapse
I had two different Nexus 5 phones that were stuck in a bootloop with the spinning coloured KK animation.
Every time I unlocked the bootloader, the bootloader would always re-lock itself when rebooting. Even when I managed to unlock the bootloader, I could not re-flash a stock ROM because the bootloader kept relocking itself.
Whenever I unlocked the bootloader, the phone would only take 2 ot 3 seconds to wipe the phone which is too fast.
In the end, I purchased a nexus 5 with a smashed screen to use its motherboard in my defective N5.
I have never come across a post where someone was able to solve the problem unless they had LG replace the motherboard with a new imei.
Anyone have this problem and solved it? I have an ASUS Zenfone Max Plus M1 (ZB570TL ) - (X018D) and i have tried every Rom you can think of from WW to CTC to CN, also tried dump firmware but nothing will stick and let this device actually fully boot up after flashing it, it just goes to the POWERED BY ANDROID screen and after 30 secs it will reboot itself back to the POWERED BY ANDROID screen and then reboot again and so on..
HOLDING VOL+ and POWER buttons in gets me to the:
- RECOVERY MODE - Just reboots back to Powered by Android screen and back to bootloop, no android guy recovery...
- FASTBOOT - Lets me have Fastboot but i cant flash anything or unlock bootloader as it errors and shows its Locked...
- NORMAL BOOT - Just reboots back to the Powered by Android and then reboots after 30 secs right back there....
There is no RECOVERY MODE that i can Factory Reset, Update.zip, clear cache...
I Flashed with SP Flashtool over 20 Firmwares and all finish with the popup Finished and green checkmark and i watch the flash process all the way without error, unplug the device and turn it on and back to Powered by Android screen and reboots itself after 30 secs... THIS IS CRAZY its like its a GAG Phone or something just messing with me like ( Jokes on you big guy ) ive never seen anything like it, its like the locked bootloader is telling the device not to allow any Firmware to install by tricking the SP Flashtool that yes it did install but didnt allow it to write to the actual system or let you get into recovery mode to factory reset the device or update from sdcard... im just wondering if its a waste of time to bother finding a UFI Box flasher that doesnt need the dongle so i could try flashing the EMMC files if that would help or not... its not a hardware problem or it wouldnt accept flashing or let it power on and enter fastboot mode....
Is this a GAG Device or has anyone actually had this exact problem and has solved it? If i could just get it to boot up into the system i could use Magisk and make a patched-boot.img thats unlocked bootloader and root but theres no ZenUI or anything but the Powered by Android screen....
Any Help would be awesome as i just put new screen, battery, back cover and buttons on this device thinking it would be a good little phone for my daughter... i cant even get any info on the device as theres no box or sticker with IMEI or Serial Number or info on the last working Firmware its all a shot in the dark... Anyways if anyone has the way to get this device working or has backup rom or links to an actual way thats not ASUS as they are just waste of time for 30 mins then you need to take it in to our service center and pay more money and im done putting money in this and could have bought her a new phone for what ive got into this Gag Phone....
Thankz...... Kixx
Judging from the whole situation, you screwed up several things honestly.
The fact it goes stuck on the splash screen and refuses to neither boot on recovery nor the system itself seems to tell 2 things:
the boot.img and recovery.img got screwed up way too much- or literally got flashed for the wrong device, hence the whole rejection to boot;
i assume SP Flashtool, even if got tricked, got a bit of a mess on the internal partitions to be flashed thru. Sounds like a big red flag because ADB can be highly of help (i don't own an X01BD but an X00HD- still an asus device- but i used simple ADB instead of things like QFIL or SP Flashtool to get things going);
On second point, if you wanna try to unlock the bootloader (since fastboot is the only one to be alive and usable- this means your device will be salvageable...atleast by a significant chunk):
you can give it an attempt by checking over my own collection post.
There you will find at the bottom some tiny guide on how to unlock the bootloader-
if you don't have a secondary rooted device, you can always rely using a laptop or pc.
What really matters is that you'll have ADB downloaded on your machine, because it could be of help to progress thru with the stuff.
After unlocked the bootloader, you can slowly approach to flash TWRP for your own device- even tho, it seems nobody so far has done anything for this specific model...
Atleast, on the bright side, unlocking the bootloader will give you the chance to flash manually the partitions via ADB, and maybe the official zendesk site for it can help if unpacking one of the update zips and see the contents inside- or generally pushing the following .zip update file via ADB and wait for the magic to happen.
I'm not sure on how to help with the region tho.
I guess, if you have the box of the device, it could give you a clue if it is a WW (WorldWide), CN (China), JP (Japan), etc. model- afterall, these letters do not lay around without a reason.
Of course, if you flash the wrong region to the wrong regional model:
then the recovery and system partitions get to screw up big time, just like the scenario you're having right now.
As a last thing, the patched boot.img file only gets to work after you got android to work-
otherwise, patching the pre-rooted boot.img file will be of no use since a functioning ROM isn't there at all.
Sadly, i don't own the device nor never had such screw-ups of this kind, but i hope it will help you up.
Ya i can flash the firmware correctly in SP Flashtool it comes back with green checkmark, all the firmware is for the correct device, its just when i had it given to me it had broken screen and bad battery, so i buy new screen, battery, backcover for it and when i booted it up it just sticks on the first screen shown ( Powered by Android ) then after like 30 secs it reboots back to that screen.. I can hold the vol + and power and get the menu to pick RECOVERY or FASTBOOT or REBOOT, recovery just reboots to powered by android screen then reboots after 30 secs, fastboot lets me use adb and fastboot but cant flash it says failed locked, and fastboot oen unlock or any of the commands to do with unlocking or flashing just gets me failed locked, but fastboot does work. Only way to root or unlock bootloader the device needs full boot into system so i can enable adb debugging or usb debug in developer settings so the computer will let the device get past the failed error locked part....
Do you know how to get the usb debugging turned on so the computer can grant full access to the device then il be able to actually crack into it and flash through fastboot..
Or where the usb debugging file is in the system.img if i extract it, use text editor and give the bool a yes that its been accepted then repack the system,img and flash it usinh sp flashtools, then i might ge able yo get it up and running....
After flashing all kinds of firmware for this device they all pass the flashing except for a few of them, ones that dont work wont even let the device boot to show system thing, then flashing correct firmware it allows the first screen again and the menu to pick fastboot but wont fully boot up..
Im thinking there must be somekind of lock the device put on from letting you oem unlock bootloader or booting into recovery mode because the firmware is working or it wouldnt take it using SP Flash Tools or even let it boot up as it would either reboot instantly or not even turn on, if the boot partition or recovery partition was courupt or broken or damaged it wouldnt take it during the flashing process it would fail....
If you know how i can activate the usb in developer settings from a file in system.img file after ectracting it then thats prob my BEST OPTION OR BUY A USED MOTHERBOATD OFF EBAY...
Lol
KixxTheManz said:
Ya i can flash the firmware correctly in SP Flashtool it comes back with green checkmark, all the firmware is for the correct device, its just when i had it given to me it had broken screen and bad battery, so i buy new screen, battery, backcover for it and when i booted it up it just sticks on the first screen shown ( Powered by Android ) then after like 30 secs it reboots back to that screen.. I can hold the vol + and power and get the menu to pick RECOVERY or FASTBOOT or REBOOT, recovery just reboots to powered by android screen then reboots after 30 secs, fastboot lets me use adb and fastboot but cant flash it says failed locked, and fastboot oen unlock or any of the commands to do with unlocking or flashing just gets me failed locked, but fastboot does work. Only way to root or unlock bootloader the device needs full boot into system so i can enable adb debugging or usb debug in developer settings so the computer will let the device get past the failed error locked part....
Do you know how to get the usb debugging turned on so the computer can grant full access to the device then il be able to actually crack into it and flash through fastboot..
Or where the usb debugging file is in the system.img if i extract it, use text editor and give the bool a yes that its been accepted then repack the system,img and flash it usinh sp flashtools, then i might ge able yo get it up and running....
After flashing all kinds of firmware for this device they all pass the flashing except for a few of them, ones that dont work wont even let the device boot to show system thing, then flashing correct firmware it allows the first screen again and the menu to pick fastboot but wont fully boot up..
Im thinking there must be somekind of lock the device put on from letting you oem unlock bootloader or booting into recovery mode because the firmware is working or it wouldnt take it using SP Flash Tools or even let it boot up as it would either reboot instantly or not even turn on, if the boot partition or recovery partition was courupt or broken or damaged it wouldnt take it during the flashing process it would fail....
If you know how i can activate the usb in developer settings from a file in system.img file after ectracting it then thats prob my BEST OPTION OR BUY A USED MOTHERBOATD OFF EBAY...
Lol
Click to expand...
Click to collapse
Well, as far as i can tell and did unlock 2 asus devices of the same model (still, X00HD):
i didn't needed to go thru android, since Asus never had an "OEM Unlock" thing to enable once unlocked dev settings-
yet, i'm speaking about the X00HD since, again, i never owned an X01BD, but i am trying to apply the same reasoning even if it is an entire different model but still same brand.
Dunno, in my case i was able to get the bootloader unlocked by going getvar all and got the secret key to unlock it just as easily by experimenting and finding cmds to use over this device's forum in here while being in Fastboot mode.
Before stepping my feet to Fastboot, tho, i even tried to get my hands at an OEM Unlocker apk made by Asus:
but to no avail it only worked on devices with really old firmware and since my device was updated to the latest Oreo FW, it was impossible to perform since things got patched overtime.
Sadly, i really don't know how to modify values over system.img files myself and tick up variables by inspecting over hex editors and such.
Least i know is getting the Brotli binaries and some other specific tool on GitHub to extract stuff from Android .img files, but that's all my skills really get limited to since i'm no dev myself nor either someone who can reverse engineer things just as well.
I think you could be out of luck on that regard.
Only thing that remains is going to a particular mode where it is required putting the phone apart and touch 2 specific pins on the board to enter it.
I currently forgot the name of this mode, but i do know by fact it's a common thing between Huawei devices.
If even this thingie won't help, then i really dunno myself.
Maybe someone else could be of help instead of me lol.
Ya ill try touching the two pins but what two oins and touch them with whst? Give me a roll out on what to do, i just dont understand why it accepts firmware but wont let me boot up into it or recovery mode or flash anything because at first it flashes then when it completes it fails and says remote unknown locked
Also im going to try find a way to format or partition the main system partitions maybe the system.img is landing on a different section of the harddrive... just need tge partitions for thus device
KixxTheManz said:
Ya ill try touching the two pins but what two oins and touch them with whst? Give me a roll out on what to do, i just dont understand why it accepts firmware but wont let me boot up into it or recovery mode or flash anything because at first it flashes then when it completes it fails and says remote unknown locked
Click to expand...
Click to collapse
Aight, to start with: i'll share out a couple of links.
First, here's a picture on where the testpoints of the device are.
As of second, you need some tweezers or something that is able to touch such testpoints inside the board (unrelated, but the GH page to PotatoNV has a guide what to do with the testpoints- even tho, the page redirects you to a tool that only works with Huawei devices. Don't test it on that asus device.).
Not sure about the flashing tool, honestly, but i do know for a fact i couldn't share software in here due to rules of this forum.
Since this is, i suppose, a device with a Qualcomm SoC:
maybe you could use stuff like QFIL Flash Tool for the job (dunno about partitions, for that you should get some linux knowledge- since android uses the linux kernel to communicate with everything inside the device).
Also, i've got something intriguing right now:
apparently the forum for the X01BD effectively exists over XDA lol (turns out the X01BD is a Zenfone Max Plus M2 and not an M1).
Maybe you can check out here for further custom ROMs and recoveries, plus more proper help on the matter- as of firmware dumps, you could try hopping over Android FileHost, firmware.mobi, or steep your feet into some unknown forum that has the firmware dumps of this specific device and restore it logically (or simply doing a google search by doing [insert model number here] firmware dump - if google only gets you to shady sites, stick to the XDA forum on the device).