Database Info

-SOLVED- [Q] Trying to root, but can't boot into CWM...can anyone help?

I was using this guide http://forum.xda-developers.com/showthread.php?t=1078019 to unlock, install CWM, and then root. Unlocking was fine, installing that version of CWM seemed okay, but when I enter command "fastboot reboot", then hold down the volume - button after 3 seconds of the Moto logo showing, then pressing the volume + key, I get only 1 option....-->Android Recovery. I press the Volume + key, get "Entering Android Recovery Mode", and below that "Reading ODM Fuse 1", then the screen switches to an android with a yellow hazard sign in his tummy.
From that screen, if I press Volume + and power, I see:
Android system recovery <3e>
Use volume keys to highlight; power button to select.
reboot system now
apply update from USB drive
wipe data/factory reset
wipe cache partition
I don't get a choice to apply something from the microSD card I have installed with the WiFi_RootTool_3.1.zip I put on the card.
Has anyone had this happen? I can't ask in the development forum. I also just got the Xoom back from a repair, and it was wiped to stock, then I did the 3.1 update when I got it back this morning. Is the fuse thing something they may have done to block rooting?

Have you tried reformat your sd card?

becu4xda said:
Have you tried reformat your sd card?
Click to expand...
Click to collapse
I'll try that. But would that stop it from going into recovery?

becu4xda said:
Have you tried reformat your sd card?
Click to expand...
Click to collapse
I reformatted my sd card, but I still can't get CWM to work and boot into recovery. Same message-
-->Android Recovery
Entering Android Recovery Mode
Reading ODM fuse: 1
And that's it....no options to load the root zip from an SD card or anything. Is there a way to push root without using the SD card? Or is that ODM fuse thing making it impossible?

becu4xda said:
Have you tried reformat your sd card?
Click to expand...
Click to collapse
Nothing at all to do with CWM.
OP: Try flashing the recovery again. To get into recovery, type adb reboot recovery, or use an app such as Quick Boot.
Edit: You can't use CWM to root, you need to do that first.

siscim23 said:
Nothing at all to do with CWM.
OP: Try flashing the recovery again. To get into recovery, type adb reboot recovery, or use an app such as Quick Boot.
Edit: You can't use CWM to root, you need to do that first.
Click to expand...
Click to collapse
I have to root first? I'm not sure how to do it....can't find any other methods of rooting 3.1....everything on Google just points me to the same method, using the SD card that won't work cuz I can't boot into recovery. Ugh.

Hey jump hour PM me.

Hey guys,
I called JumpHour and we tried to troubleshoot this over the phone. We aren't able to get into the recovery because of error "reading odm fuse: 1". The OP is using Windows 7 64 BIT and has the SDK installed properly. He updated the sources and installed them so those are up to date. We also verified that USB debugging was enabled and that the correct files were in the tools section in the SDK folder.
We ran the commands:
adb reboot bootloader
fastboot-recovery ........ (we typed it in correctly accoriding the thread)
fastboot reboot
and we get that error message.
This was all initiated while the Xoom was powered on. JumpHour stated that he had to send his Xoom back to Moto because his Xoom got messed up during the re-locking process when he unrooted a one click root and re-locked.
We then went ahead and downloaded the recovery image again and replace the one in the tools folder. We ran the commands again and we were getting the same error.
Does anyone have any idea what is going on with this process? Are we missing something? Is something broken?

Get the official images. I am assuming you have a USA 3g or wifi model.
Follow the steps to return the device to stock. But do not issue the reclock bootloader command. There is no need to relock.
From there power up the device and turn on USB debugging.
Then adb reboot into recovery. That should bring you to the stock recovery.
If all goes well from here just do what ever else you where intending to do in the first place.
You most likely can just flash the stock recovery but I would just do a full flash back to official images minus relocking bootloader.
Sent from my Xoom using Tapatalk

Then let the ota update it to 3.1 and so on.
Sent from my Xoom using Tapatalk

What's the status JumpHour? Did you get it to work. I told you it may have been due to the images. Hopefully that fixes your issue. Take care dude.

gqstatus0685 said:
What's the status JumpHour? Did you get it to work. I told you it may have been due to the images. Hopefully that fixes your issue. Take care dude.
Click to expand...
Click to collapse
Hi, thanks for the response. I'm gonna try it now. I was up REALLY late last night, and just got up a little while ago. I'll definately respond after I try it out.

Finally, I did it!
Okay, I fixed it finally. Reloaded the stock images, and it's now rooted with SD support. Yay! Only took 2 days!
Thanks for all your help guys.

Can reflashing with original images fix recovery mode mount problem?
Does any window is flashing to the original images can restore access to the sdcard IF the recovery mode in the official recovery mode (not CWM) says that you cannot mount the sdcard?

Is my Xoom bricked?

Hey All,
I know there are a lot threads like this on here, so I made sure I tried everything possible before asking for help.
First off, It is a MZ604 wifi version.
Ok, upon powering up my Xoom, it will get to the Motorola screen/ dual core and stall.
I am able to get into recovery, however the version I am running, 5.8.3.1 apparently does not allow sd card mounting, so I am unable to restore or flash a new rom.
A factory reset/ data wipe does nothing.
I have tried to flash a new rom via ADB, however my computer will not install the Xoom drivers. It will say "installing device drivers" for about 2 minutes or so before failing. I have tried using moto helper and the other Motorola usb drivers
I am unable to boot into android to enable usb debugging
I have tried all of the above on my laptop too and to the same result.
My question is, is this a brick? or can it be solved.
Thanks for your time

Yes it can be fixed, if you can access recovery then it means you can access fastboot. So what you do is once you're in the fastboot protocol, is flash in TWRP recovery http://forum.xda-developers.com/showthread.php?t=1782235
With that recovery you can mount SD cards, so use a computer to download the ROM you want then flash. Hopefully you get the idea, but I can post in more detail if you want.

Chaosgod27 said:
Yes it can be fixed, if you can access recovery then it means you can access fastboot. So what you do is once you're in the fastboot protocol, is flash in TWRP recovery http://forum.xda-developers.com/showthread.php?t=1782235
With that recovery you can mount SD cards, so use a computer to download the ROM you want then flash. Hopefully you get the idea, but I can post in more detail if you want.
Click to expand...
Click to collapse
Thanks for responding, I appreciate it. The thing is that my xoom cannot connect to my computer, and therefore and cannot use fastboot to send it the image correct?
I could fix all of this if I could just get the drivers to install, but because of my xoom's condition, the drivers cannot install no matter what.

Hmm usually fastboot drivers should automatically install. Does your recovery have an option to boot into fastboot? Once you're in fastboot it should automatically install the drivers, and in the android sdk folder in CMD (assuming you're running windows) put in this command: fastboot devices
It should show up your XOOM if not install this http://www.motorola.com/Support/AU-EN/Support-Homepage/Software-and-Drivers/USB-PC-Charging-Drivers
And try again

Hi all!
I got the same problem...
I can connect it to PC and do fastboot, I've flashed it many times, but it didn't affect my Xoom, i've reflashed the recovery to a lower version (tiamat rc4) but the recovery still shows version 5.8.3.1...
I even tried RSD, but it still the same...
no errors, and no effects...
is my Xoom bricked?

^I heard of this before, sounds like your new recovery image just gets overwritten by the current recovery. Though I thought it was only for stock recovery.

but, how can I overwrite it? it seems like they are read only...

It's all about timing, to access recovery once you see the Moto logo wait 2-3 seconds then vol + then vol + again. This is right after you flashed in your new recovery.
You can also access your fastboot like that as well, instead of pressing vol + again, press vol - then vol +.

Chaosgod27 said:
It's all about timing, to access recovery once you see the Moto logo wait 2-3 seconds then vol + then vol + again. This is right after you flashed in your new recovery.
You can also access your fastboot like that as well, instead of pressing vol + again, press vol - then vol +.
Click to expand...
Click to collapse
that's not the problem... of course I can access the recovery, fastboot and RSD, the problem is that I whatever I do to the xoom just don't work... and it reports no error at all... it's just succeed, but nothing happened... It's like a PC running windows with DeepFreeze installed...
Anyone got the same problem? can anybody help me?:crying:

No you're missing the whole point, after you flashed your new recovery it may get overwritten if you don't reboot into recovery straight way. It never happened to me but I have read that people has that issue.

Acer A700 Bricked ----

Hellooooooooooooooooooooooooooooooooo!!!
this is my first thread in this forum, mi name is Nicolas and i ve a very big problem with my new tablet.
I was trying to install the new Jelly Bean (OS_Acer_RV09RC08.WW.GEN1_A41J_A) and everything was OK
I unlocked the bootloader .......and....
I try to root and just bricked....
Everytime i turn on the tablet i can see the "Acer logo" and the line: Bootloader Version JB-653b3d3 (Unlock Mode)
I cant get into the recovery mode.....
Sorry for my bad english....i need your help ppl!!!!
Thanks for ur time.
Nicolas.

May you can get into Fastboot mode and reflash the recovery.
Give it a try =)

Do you have a androids of your original ROM?
I did the exact same thing just yesterday...
If you have a JB image to work from, get it in fastboot mode and look at the thread on CWM Recovery 6.0.1.5...
Sent from my A700 using xda premium

thks for the replies.....
i downloaded the stock rom from the Acer web page
i tried with:
"adb reboot-bootloader" and NOTHING.....i ve the line: <waiting for the device> ....and ....5 min later nothing.
then:
tried to get the fastboot mode (vol + & PWR) and the tablet just get the same boot = nothing.
:crying:

freejack84 said:
thks for the replies.....
i downloaded the stock rom from the Acer web page
i tried with:
"adb reboot-bootloader" and NOTHING.....i ve the line: <waiting for the device> ....and ....5 min later nothing.
then:
tried to get the fastboot mode (vol + & PWR) and the tablet just get the same boot = nothing.
:crying:
Click to expand...
Click to collapse
To get into fastboot mode, it's the following combination;
- Press [vol-] + [power]
- As soon as the tablet vibrates, let go [power] then cycle your rotation lock button left and right till you see the the text start to appear.
Unless you;re going to try and fastboot a system image setup or recovery image or another boot.img, not sure what you wish to accomplish.
I would guess you would be better off installing maybe the GB full version JellyBean update.
Also, I understand there,s a a700 ICS service rom out there somewhere. That might help you also.
But these are just guesses at this point.
What would help, is to know exactly what you did to get yourself into this situation. Like What root procedure from what post? If you tried one of the ICS Boot.image flashes, when you had JB updated, well, no wonder it borked up. If that's the case, it's simple just to fastboot a JB Boot.img back in.
So which thread did you get the root procedure from EXACTLY?
One more thing, this thread belongs in Q&A Forum, so I put in a request to have it moved.
MD

Moscow Desire said:
To get into fastboot mode, it's the following combination;
- Press [vol-] + [power]
- As soon as the tablet vibrates, let go [power] then cycle your rotation lock button left and right till you see the the text start to appear.
Unless you;re going to try and fastboot a system image setup or recovery image or another boot.img, not sure what you wish to accomplish.
I would guess you would be better off installing maybe the GB full version JellyBean update.
Also, I understand there,s a a700 ICS service rom out there somewhere. That might help you also.
But these are just guesses at this point.
What would help, is to know exactly what you did to get yourself into this situation. Like What root procedure from what post? If you tried one of the ICS Boot.image flashes, when you had JB updated, well, no wonder it borked up. If that's the case, it's simple just to fastboot a JB Boot.img back in.
So which thread did you get the root procedure from EXACTLY?
One more thing, this thread belongs in Q&A Forum, so I put in a request to have it moved.
MD
Click to expand...
Click to collapse
Thks MD for ur instant reply.
Sorry for dont put my thread into the Q&A Forum. It was a mistake. Sorry again
My situation is: "like i remember" i tried to make the root with the "flash-ICS-patchedBoot.bat".....i know that BAT is for ICS and not for JB but i take that mistake doing the thing really fast. :angel:
Ok...i need them to get the fastboot with the JB Boot.img like you said.
The JB Boot.img is into the Rom??? because i saw the boot.img into the JB update.zip
Can u tell me the command to get that flash? Is "fastboot flash boot boot.img"?
Thks for ur patience

freejack84 said:
Thks MD for ur instant reply.
Sorry for dont put my thread into the Q&A Forum. It was a mistake. Sorry again
My situation is: "like i remember" i tried to make the root with the "flash-ICS-patchedBoot.bat".....i know that BAT is for ICS and not for JB but i take that mistake doing the thing really fast. :angel:
Ok...i need them to get the fastboot with the JB Boot.img like you said.
The JB Boot.img is into the Rom??? because i saw the boot.img into the JB update.zip
Can u tell me the command to get that flash? Is "fastboot flash boot boot.img"?
Thks for ur patience
Click to expand...
Click to collapse
It's no problem.
So you fastbooted an ICS boot.img on a JB rom
So, you need to see if you can manually get it into fastboot mode with the procedure I pointed out above (note it will probably wipe your user data, but who cares)
If you get it in fastboot mode, verify via windows device manager, then just put a JB Boot image in there. I have a little package in my Boot.image thread Full /System RW-Root. Don't use the boot mage in it, as it's for a 701. Just copy your JB boot.image in there and fastboot it. You have the correct command.
Verboth has a new rom, that contains an unsecure boot.img for the 700 JB. You can use that one also. It's what you were trying to do originally, just with a wrong image (ICS)
The reason ADB doesn't see it, is because the system isn't running. The newer CWM recoveries should have adb enabled through CWM, but I don't think you put that in yet.
Hopefully you'll get it fastbooted.
MD

Moscow Desire said:
It's no problem.
So you fastbooted an ICS boot.img on a JB rom
So, you need to see if you can manually get it into fastboot mode with the procedure I pointed out above (note it will probably wipe your user data, but who cares)
If you get it in fastboot mode, verify via windows device manager, then just put a JB Boot image in there. I have a little package in my Boot.image thread Full /System RW-Root. Don't use the boot mage in it, as it's for a 701. Just copy your JB boot.image in there and fastboot it. You have the correct command.
Verboth has a new rom, that contains an unsecure boot.img for the 700 JB. You can use that one also. It's what you were trying to do originally, just with a wrong image (ICS)
The reason ADB doesn't see it, is because the system isn't running. The newer CWM recoveries should have adb enabled through CWM, but I don't think you put that in yet.
Hopefully you'll get it fastbooted.
MD
Click to expand...
Click to collapse
Okay, so since I just did this, I'm going to try and give you a "how to" on how I fixed it...
MD and pawitp both are the authorities on this, but I think this will help and I a, sure they will correct me where I go wrong.
First, use the manual process for getting your A700 in fastboot.. power button + down vol, wait for the first buzz then release only the power button, wait for the second buzz then press the up volume button. Your tab should now be in fastboot mode.
Connect it to your computer.
Get a copy of the proper recovery image "recovery-a700-6015" and the following ROM ( http://forum.xda-developers.com/showthread.php?t=1952124) and save them to a directory where you can find it easily.
Pull the SD card from your tab and put the ROM from above in the base directory and put it back in your tab.
From the c prompt on your computer use the following fastboot command:
Fastboot devices
----#make sure that the computer sees your a700
Fastboot boot <save directory>recovery-a700-6015.img
----#your tab will reboot into CMR Recovery
In recovery format system, data, cache, dalvik
Still in recovery install the ROM from your external SD card.
The Aroma Installer will guide you through it, but make sure you tell it to install the new firmware.
Reboot.
You should be on the stock rooted ACER Great Britain release.
From there you can download and install CM10 (which is what I did), or any other ROM you would like.
Sent from my A700 using xda premium

well.......30 minutes with the tablet and:
I put the tablet in Recovery state with the last instructions.....but now i ve too much errors lines:
Important: all this error are "before" flash again the recovery
The recovery cant:
mount /cache/recovery/command
mount /cache/recovery/log
mount /cache/recovery/last_log
cant open cache/recovery/log
and.....
cant mount SDCARD, EXTERNALSD, SYSTEM, CACHE, etc etc...
when i try to flash again the recovery: <waiting the device> and nothing......i cant put the tablet in fastboot mode.

i have the same problem before. 無得整的, 要上acer換底版的

NEWS:
Finally i get the fastboot mode (Vol - & PWR and then CYCLE THE ROTATION LOCK). :good:
First: reflash the recovery and DONE
All the errors just gone.
Now.....install again the JB.....and DONE
My Acer go back to normally conditions. :victory:
Thks for ur support. :laugh:

freejack84 said:
NEWS:
Finally i get the fastboot mode (Vol - & PWR and then CYCLE THE ROTATION LOCK). :good:
First: reflash the recovery and DONE
All the errors just gone.
Now.....install again the JB.....and DONE
My Acer go back to normally conditions. :victory:
Thks for ur support. :laugh:
Click to expand...
Click to collapse
Uhmmmm.... didn't I state that the other day?
Glad you got it going Mate :good:
MD

thks ppl

freejack84 said:
NEWS:
Finally i get the fastboot mode (Vol - & PWR and then CYCLE THE ROTATION LOCK). :good:
:
Click to expand...
Click to collapse
I didnt have the same exact issue like the other users BUT this key combination to finally get back into fastboot during a hanging ACER logo bootup with a red failure msg at the corner was the LIFE SAFER!!!!!
VOL - (left button with two knobs) & PWR and then CYCLE THE ROTATION LOCK
tattoo this on your arms!!! :laugh:

LukeRG said:
I didnt have the same exact issue like the other users BUT this key combination to finally get back into fastboot during a hanging ACER logo bootup with a red failure msg at the corner was the LIFE SAFER!!!!!
VOL - (left button with two knobs) & PWR and then CYCLE THE ROTATION LOCK
tattoo this on your arms!!! :laugh:
Click to expand...
Click to collapse
LOL

pls step step explain ı recovery my tablet but ı want to back syock rom tablet internal storage not ready in pc ı cant see internal storage ı see only sc card camera dont workk how back to syock rom pls help..

thank's man
freejack84 said:
NEWS:
Finally i get the fastboot mode (Vol - & PWR and then CYCLE THE ROTATION LOCK). :good:
First: reflash the recovery and DONE
All the errors just gone.
Now.....install again the JB.....and DONE
My Acer go back to normally conditions. :victory:
Thks for ur support. :laugh:
Click to expand...
Click to collapse
Thank's... you just safe my problem today

u welcome .......

Hello everybody,
I think I have NOT exactly the same problem but very similar.
Let me explain how I got there:
I had JB bootloader and CM11 installed for long and working fine.
Last days I tried out the CM12.1 unofficial rom with successful installation.
I noticed that the camera focus was not working. Usually I never use the camera and was not sure if it worked before. So I went back to CM11 to look if it is rom dependent. In CM11 it still was not working and I went back to stock. The stock rom I found was Android 4.0.4 and I tried to make OTA update what showed me a “not allowed to your device” –error.
However, at this moment I was quite sure that the camera focus is a hardware defect and wanted to go on testing the new CM12.1. I installed it again from CWM recovery and it was not booting anymore.
The problem is, that the stock rom flashed an ICS bootloader which is not compatible anymore. I also cannot boot into recovery anymore but fastboot is working.
Power-On:
shows Bootloader Version ICS-MR1-a055314 (Unlock Mode) and nothing more
Power-On + Vol.Down:
Bootloader Version ICS-MR1-a055314 (Unlock Mode)
Erasing Cache before SD update…
SD update cnd: recovery
--update_package=SDCARD:update.zip
Booting recovery kernel image
Then for just a second CWM is shown:
CWM-based Recovery v6.0.5.1
Finding update package
E:unknown volume for path [SDCARD:update.zip]
E:Can't mount SDCARD:update.zip
Installation aborted.
Rebooting...
Then it holds on Bootloader Version ICS-MR1-a055314 (Unlock Mode)
I could not find any button combination to boot something else.
What I tried and what did not make any changes:
Flashing the recovery.img again
Erase userdata, cache, system
Please help me to boot up recovery again and flash a JB bootloader and new rom.
Thanks and kind regards,
Gandlz

Well, in between I found a solution and can answer my own question now:
The trick is to flash the CWM Recovery not to the recovery partition but to the boot partition. (fastboot flash boot recovery.img)
After restarting the tablet it boots directly into CWM Recovery.
I found a newer stock rom with jelly bean android and installed it to come back to JB-Bootloader. Now I could install CM10.2 CM11 or CM12.1 again.
The stock rom is from a german forum:
android-hilfe.de/thema/a700-zurueck-aufs-deutsche-stock-rom-flashen-anleitung-imagefile.329590
By the way: I’m running CM10.2.1 and it is very much faster than CM11 or CM12.1. I don’t need the newer features and like the old design even more. And also the camera focus is working now, so it is definitely a software issue with newer CM versions.
Best regards,
Gandlz

[Q] [A510] Just stopped working (can boot into CWM)

Hi guys,
My A510 just turned itself off with no apparent reason. Now I'm experiencing the following, looping :
- It tries to boot,
- freezes on the boot logo (previously "NoThrills", now "Acer"),
- vibrates and reboots.
I can boot in recovery (CWM). When I do, CWM apparently can't access the logs. Here's what I tried :
- wiping everything (data, cache, dalvik)
- restoring Nandroid backup (it was previously a NoThrills JB, now it's back to a stock JB) but I get an error when it tries to restore /data ("Error while restoring /data!").
My computer doesn't detect the tablet when it's plugged in... so I think I can't push or adb anything.
I guess it might be a hardware problem, but does anyone have any idea ? Maybe I could try to diagnose the problem?
Thanks a lot!

You can try to put a full update.zip on your sdcard, and flash it with your recovery
(a custom ROM or a full Acer Stock ROM)
You can also try to format every partitions via fastboot and then, reflash a proper ROM

Hey Shreps,
Thanks for your answer.
- I tried flashing NoThrills' CM10 from the external SD card, it didn't throw any error (although it skipped formatting the boot partition as well as extracting the files to the data partition, I don't know if it's a valuable information or not). Now instead of having the Acer logo during boot, the screen is doing weird stuff and it still won't boot. I can still boot into recovery though.
- I'm not sure how to use fastboot on this device. I get the option to boot into fastboot on my Moto G, but not on my A510. Do I need to flash a more recent CWM to enable it?
Thanks!

Boot in Fastboot via physical button http://forum.xda-developers.com/showthread.php?t=1747802

Thanks!
Volume down + Power on + Rotation switch got me to a black screen with the Acer logo and the following on top :
"Bootloader Version JB-d0ca683 (Unlock Mode)" -> that's normal
"Bootloader VJB-d0ca683(UnlockMode): Starting Fastboot USB download protocol" -> It's stuck there and I'm not sure it completes the operation.
My PC doesn't detect the A510, and "fastboot devices" returns nothing in the terminal.
Any idea?
Thank you!

Ghoorg said:
Thanks!
Volume down + Power on + Rotation switch got me to a black screen with the Acer logo and the following on top :
"Bootloader Version JB-d0ca683 (Unlock Mode)" -> that's normal
"Bootloader VJB-d0ca683(UnlockMode): Starting Fastboot USB download protocol" -> It's stuck there and I'm not sure it completes the operation.
Click to expand...
Click to collapse
That's normal/ok
Ghoorg said:
My PC doesn't detect the A510, and "fastboot devices" returns nothing in the terminal.
Any idea?
Thank you!
Click to expand...
Click to collapse
Should work, try to proper install the Acer drivers & check your USB Cable/port
"fastboot devices" should return a device with its ID

Still no luck after reinstalling the acer drivers... I think some components may be fried at this point?

There's something I'm wondering, it seems I can't mount anything from my pc but I can see files and folders from CWM. Is there any way I could copy everything on the external SD card that's in my A510?
Thanks!

Reply
Ghoorg said:
There's something I'm wondering, it seems I can't mount anything from my pc but I can see files and folders from CWM. Is there any way I could copy everything on the external SD card that's in my A510?
Thanks!
Click to expand...
Click to collapse
With the Tablet in CWM Recovery you can do a Backup on an SD Card
search for cwm recovery backup on the net
lists you the possibilities.
I had the same Problem, fastboot did not list my device because the mode was for receiving data only. But you can try this:
Tablet off.
Enter the Fastboot Commands in the Command-Line
Then turn your tablet in fastboot-mode.
Good luck.

Probably bricked my zenfone 3 ultra... :/

So I was interested in getting a root, did fastboot boot twrp.img, the version you get from shakala's megaupload page and tried to do a mtp mount to copy the supersu in. That didn't work because I'm on mac and I rebooted... surprise phone doesn't boot. It's just stuck on the 'asus, in search of incredible' screen that comes up 1 second after booting.
Tried to instead flash twrp to recovery, no dice, black screen. Tried flash stock recovery from the shakala's page, I get the droid belly up with an exclamation mark over the open belly...
Tried fastboot boot twrp.img and then sideload the actual OTA firmware, no dice. It won't even try to flash and just gives the 1001 error.
I have tried and unpacked 3 different stock images I've found
UL-ASUS_A001-WW-14.1010.1702.36-user.zip
UL-ASUS_A001-WW-14.1010.1703.42-user.zip
UL-ASUS_A001-WW-14.1010.1704.46-user.zip
and flash the sytem.new.dat to the system partition, no dice again. Phone just doesn't boot.
TL;DR
Something got wonky, phone doesn't boot
Recovery is broken, flashing stock recovery from shakala's page produces belly-up-android image
Without stock recovery, I can't sideload a full system update...
Halp? Ideas?

Got a little bit progress...
The TWRP black screen can be fixed by just turning off the display via the power button and then pressing it again, and you can see the twrp. Looks like even the normal one
Next hurdle was that /cache and /system couldn't be mounted for sideloading so in the end I had to go to the adb shell and format them manually. Then the wiping of system was possible and there were no more errors from TWRP.
So I went ahead and tried sideloading again, it put the image in nicely and everything looks good. Go to reboot screen and it say 'no OS installed'.
I guess those 1.7G images don't exactly have the full OS so a /system formatted Zenfone 3 Ultra can't be restored from those?

Alrighty, got stuff working. Sharing for people who might run into this later.
At this time, you need the stock recovery working to be able to `adb sideload` a full image. The TWRP goes to 50% and then actually doesn't unconditionally push the stock ROM into the partition. I saw the difference when using TWRP/Stock Recovery.
My biggest failure was not to recognize that the green android belly up with an exclamation mark on top of it actually meant that the stock recovery was working. You have to do a little bit more finger juggling to actually enter the recover commands section of the recovery. Mainly after the android appears, volume up+power for a few seconds, release volume up. Illustrated here:
https://www.asus.com/zentalk/in/thread-121896-1-1.html
From the stock recovery, you can then wipe caches and start adb sideload, and using your pc to sideload the image (or from sd card if you so wish).

blosphere said:
I guess those 1.7G images don't exactly have the full OS so a /system formatted Zenfone 3 Ultra can't be restored from those?
Click to expand...
Click to collapse
I can testify that the 1.7G image contains a full OS on /system.
If you read META-INF/com/google/android/updater-script inside the UL-ASUS_A001-WW-14.1010.1704.46-user.zip, you will see the official recovery do use system.transfer.list and system.new.dat in the zip to flash /dev/block/bootdevice/by-name/system.
Recovery is broken, flashing stock recovery from shakala's page produces belly-up-android image
Click to expand...
Click to collapse
When you see the belly-up-android image, press Power + Volume-Up. The stock recovery menu comes up. I was confused at the beginning, too.
From you id Tokyo, did you buy the phone in Japan? If so, it is a JP_Phone, and need some tweak to the initrd in boot.img to flash WW firmwares.
Oh, glad to see you've already solved it! You might want to mark the thread title as "[SOLVED]".