Zenfone 2 not booting to Android and cannot access Recovery. - ZenFone 2 Q&A, Help & Troubleshooting

Hey everyone,
I am one of the people who tried the office bootloader unlock and now I have a problem. My phone will not boot to android. I get the android with the exclamation mark that flashes. I can reboot and select recovery at the bootloader, but when I hit power and vol+ I get the recovery screen for about 4 seconds before it goes back to the android with exclamation mark. I can see the following last few lines repeat:
E: cant mount cache (invalid argument)
E: failed to mount /cache/recovery/locale
I tried to erase the cache in fastboot, but I get the error "FAILED (remote: can not mount the necessary partition)". I cannot access adb as I cannot get the recovery to pull up. I am pretty sure my bootloader is still locked. It is like my partitions have been messed up. I know that Asus is aware of the issue with the bootloader app, but any updates pushed in apk format or that require the recovery will not be of help to me.
Is there anyway to rebuild the partitions or reflash the firmware via fastboot with a locked bootloader? I am used to an old Nook Tablet that you can boot from an sd card to fix issues like this.

Have you tried flashing your device?
http://forum.xda-developers.com/showthread.php?t=3096596
Follow the steps with adb sideload command, hope it'll work out for you.

Related

[Q] rom wont boot and cant acces clockwork recovery

Hello,
im in some big trouble.
I tried installing the new sense gingerbread rom.
It would not boot and i accidently formatted my sd card.
Now i cant boot the rom (loops at the android splash logo) and can no longer get into clockwork recovery.
All i can do is get into standard android system recovery.
if i use apply sdcard: update.zip i get the feeling it tries to go to clockwork
it says: e:cant mount /dev/block/mmcblk0p1 (invalid argument)
When i try to flash the recovery trough adb it says "flash is not recognized as an internal or external command....
Is there a way to get this phone again...rooted or unrooted?
Please help me
Flash the recovery in fastboot mode with S-Off.
Have you tried formatting card again? And to be sure, is there ext3 after fat32?
i reformatted. i have 7300mb fat32 and 600mb ext3.
cant get into fastboot. it brings me to a black screen with a phone with a red triangle and a explenation mark. it leads me to the standard recovery and says.
e: cant open /cache/recovery/command
its driving me crazy......
Found this on another forum:
When you get the to warning triangle.
hold down the power button, then push vol down, then vol up
Then you get to the system recovery screen.
Click to expand...
Click to collapse
i tried, but then i get to normal recovery, and when i select apply sdcard :update.zip it errors...see first post.
i cant instal RUU either because when i fastboot it wont say fastboot usb but instead go to the red triangle....
so i guess my only option is flash clockwork again but my adb doesnt recognise "flash recovery c:/recovery.img as an internal or external command....
When i use the command "adb devices" when at the red triangle it does find my telephone.
back on track using paul obriens r6 root method.
Thanks everybody.

[Q] Infinite boot loop - accessing phone memory possible?

I have messed up while trying to run Backtrack 5 on my Defy. As I got some errors when executing the bt script, I attempted to install the busybox several times. The effect is that, after reboot, I have an infinite boot loop. I can access the recovery (unfortunately the stock version), however it opens with the following errors:
E:Can't open /cache/recovery/command
E:Can't open /cache/recovery/caller
and after wiping the cache I get:
E:Can't mount CACHE:recovery/log
Is it possible to somehow fix the filesystem without performing the factory reset?
If not, then is it possible to access the phone memory in order to backup stuff such as messages, before the factory reset or flashing new ROM?
Any ideas much appreciated!
It looks like you're stuck :/.
If you had usb debug on before having problems then maybe you could try using adb during the bootloop? I don't know how to use it though.
CM7 + CM9 double boot
crakeron said:
It looks like you're stuck :/.
If you had usb debug on before having problems then maybe you could try using adb during the bootloop? I don't know how to use it though.
CM7 + CM9 double boot
Click to expand...
Click to collapse
If you have done up and set adb correctly , run
Code:
adb logcat
Herpderp Defy.
Thanks for your suggestions!
I'm pretty sure I left the USB debugging switched on. However the phone isn't detected by ADB interface (adb devices). The "adb logcat" is waiting for the device throughout the whole boot loop, as well as when accessing recovery and bootloader menus.
Only in the bootloader menu, the computer installed the drivers for Motorola Flash Interface, and I can see a device called S Flash OMAP3630 plugged in.
Is it possible to access the memory using this interface?

HELP! Stuck on some weird screen

I just used the all in one tool kit to flash CWM I have a virgin mobile one v. I went into the fastboot after and clicked on recovery, and now I am stuck on a screen with the HTC quietly brilliant. Underneath it says in red letters "this build is for development purposes only Do not distribute outside of HTC without HTC's written permission, etc. Any idea how to get out of it? I tried all the buttons I could think of.
I managed to get it by holding the power button for about 15 seconds. I can't seem to get into the recovery I just supposedly flashed. This isn't normal compared to other androids I'm use to.
Mate.... you flashed a wrong recovery that meant for GSM device.
Use this one : http://forum.xda-developers.com/showthread.php?t=1749798
Nice of the guy to specify in his OP...
Ok well I flashed to new recovery, however I till can't turn my phone on, it stays at that one screen. I can get into bootloader, and fastboot usb, that's about it.
someone please help, i'm stuck
anytime I try to run anything I get "C:\Users\Home\Desktop\data>pause
Press any key to continue . . ." and then it reboots into that HTC quietly brilliant screen with all the red letters on it.
Can you tell how did you flash the CDMA recovery from the link that I gave just now ?
I put it in the data folder for the all in one tool kit, under recoveries and flashed it with the toolkit. I also tried to do it through the fastboot cmd. I also tried TWRP. I was able to get into the custom recovery, but when I make any selection they are all empty(reboot, install zip, wipe date, wipe cache.)
I never use the one tool kit, so I can't comment anything.
But I always use fastboot command. For your CDMA recovery as it is named as cwmrecovery.img
the fastboot command will be:
fastboot flash recovery cwmrecovery.img
fastboot reboot-bootloader
fastboot erase cache
the go to recovery through hboot menu.
what I understand the cwmrecovery.img is non-touch version so you need to use the volume button to scroll and power button to select.
http://forum.xda-developers.com/showpost.php?p=28577991&postcount=13
Or you can try the touch recovery http://forum.xda-developers.com/showthread.php?t=1764183
fastboot flash recovery twrprecovery.img
fastboot reboot-bootloader
fastboot erase cache
If still problem, post your problem in their related thread. The OP may help you.
I can't do much as I own only a GSM device.
ok I followed those instruction, got to the custom recovery and at the bottom it says:
cwm-based recovery v5.5.0.4
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last-log
E:Can't open /cache/recovery/last-log
Nickdroid86 said:
ok I followed those instruction, got to the custom recovery and at the bottom it says:
cwm-based recovery v5.5.0.4
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last-log
E:Can't open /cache/recovery/last-log
Click to expand...
Click to collapse
I should also mention I tried flashing the 1.5Ghz kernel. Through the all in one tool kit, and also tried flashing it through fastboot by renaming it to Boot.img and typing the command for it.
There is no custom kernel for CDMA yet.... that is for GSM only. It will not work for your device, and it won't boot.
And don't worry about those E:Can't mount/cache..bla..bla... , we have that for GSM too.
I think you should stop using the One Tool Kit before it bring more harm to your device. It's nothing wrong with the tool but a user must know how to use it properly for a CDMA device, you need to change a few files on your own before you can safely using it.
Yeah I know what I'm doing, just new to this phone, and the thread for the tool kit didn't seem to mention it being for GSM. Is there a way I can use fastboot to fix this? by flashing a stock rooted rom or something?
Still unable to select anything in the recovery by the way, It just goes blank.
Flash the stock boot.img and see how it goes. If not then you need to run RUU and redo the whole process again.
the stock boot.img for VM/CDMA here : http://forum.xda-developers.com/showpost.php?p=28218226&postcount=11
flash in fastboot? Do you know the commands?
fastboot flash boot boot_signed.img
fastboot reboot-bootloader
fastboot erase cache
Yeah I think I need to use this RUU you speak of, I noticed one thing, when I reboot the bootloader and HBOOT does that scanning thing, the first two say the .img is either missing or damaged.
Downloading the RUU file, what next? Also I downloaded a stock rooted odex'ed .zip if I can just flash that from fastboot?

[Q] Recovery can't mount /sdcard/

I have scoured the earth and multiple forums for my answer.
My Device: VZW-toro-GNEX
Current State:
FASTBOOT MODE - OK
ODIN MODE - OK
ANDROID RECOVERY - OK
ADB - OK
RECOVERY MODE - accessible only with fastboot boot foo.img
NORMAL BOOT - 'Unlocked Google Splash' screen freeze
Symptoms:
1) fastboot flash recovery foo_recovery.img returns OKAY [ 0.493s]; finished. ... so far so good...
However, when I select 'Recovery mode' and press power, it boots me back into PRIMELA03 except this time with heading FASTBOOT MODE - NO BOOT OR RECOVERY IMG
2) NORMAL BOOT - After a minute or so, the 'Google Splash' screen begins tearing and fading to gray. I have waited for up to an hour for it to resolve, but always ending up pulling the batt. An image of the screen tearing is attached.
3) fastboot -w update foo_stock_image_from_google.zip reports OKAY, however fixes nothing
4) attempts to access /sdcard/ from within recovery results in E:Can't mount /sdcard/
What I've already tried:
1) flashing a stock image using recovery E:Can't mount /sdcard/
2) flashing a stock image using flashboot - Screen tearing upon boot splash
3) flashing a stock image using Odin3 - Screen tearing upon boot splash
4) using a couple different popular toolkits (wtf, why not) - LOL
5) adb install foo_image.zip - does not contain manifest.xml... Surely I'm not using this command correctly
Any ideas where to go next?
Mind if I ask what is foo? And why are you using this over CWM or TWRP?
Also sdcard can't be mounted, because Gnex has no sdcard to be mounted. It only has internal storage and that's it. You can always use adb when on recovery when you need to transfer files
I would love to help you, but I've never heard of foo.img :/
4) attempts to access /sdcard/ from within recovery [(aka CWM aka TWRP aka FOO )] results in E:Can't mount /sdcard/
Click to expand...
Click to collapse
Yes, I know that there is no physical sd card. I'm not trying to mount an sd card. CWM is trying to *mount* /sdcard. (aka /data/media)
I can transfer files all I want using adb, but even when I do, there is still the issue that CWM can't flash anything because it fails to *mount* /sdcard/ in order to access whatever_image_I_might_be_using_however_it_doesnt_really_matter_in_this_context_hence_I_call_it_foo.zip
This suggests a problem with the partition table, possibly. Also, other posts of users seeing the same error are typically resolved with
just flash a stock image, bro
Click to expand...
Click to collapse
keep in mind that's ultimately what I'm trying to do here.
try to erase all partitions (except bl) from fastboot and reflash with flash-all.sh. run it with root privileges.
the other option could be omapflash, your call.
Sent from my i9250

Stock HTC M9 stuck on HTC splash screen after battery died

[Unsolved] Phone sent to HTC service.
Hey Guys,
I'm back again and this phone is breaking my heart. My phone is still stock from the last time I had a similar problem.
My battery died, when I plugged it back in and hit the power button it powered up as far as the splash screen and hangs there.
When I go into recovery mode the log says
Supported API: 3
handle_cota_install: install cwpkg to /cache/cota/cwpkg.zip
handle_cota_install: install cwprop to /cache/cota/cw.prop
E:Fail to open file: /sys/devices/platform/android_usb/host_mode
Write host_mode error handle_cota_install: Can't mount /sdcard
I've tried clearing the cache/partition and rebooting but I'm in work and don't have access to save my info so I don't want to factory reset yet. Is there any thing else I can do or am I stuck with doing a factory reset ..... AGAIN!
Jamballs said:
Hey Guys,
I'm back again and this phone is breaking my heart. My phone is still stock from the last time I had a similar problem.
My battery died, when I plugged it back in and hit the power button it powered up as far as the splash screen and hangs there.
When I go into recovery mode the log says
Supported API: 3
handle_cota_install: install cwpkg to /cache/cota/cwpkg.zip
handle_cota_install: install cwprop to /cache/cota/cw.prop
E:Fail to open file: /sys/devices/platform/android_usb/host_mode
Write host_mode error handle_cota_install: Can't mount /sdcard
I've tried clearing the cache/partition and rebooting but I'm in work and don't have access to save my info so I don't want to factory reset yet. Is there any thing else I can do or am I stuck with doing a factory reset ..... AGAIN!
Click to expand...
Click to collapse
If you can get into bootloader or download mode try "fastboot erase cache"
Thanks for the suggestion thicklizard, I'll give it a shot when I get home and update the post.
Thanks!
?
You unlock Bootloader ,make Root or Soff ? Can you use warranty in HTC.
If u can go to Bootloader you can use Erase option ,or if is RUU for yours Htc verion you can flash to stock.
I dont know what is in without root and unlocked bootloader :/
I always have Unlocked bootloader ,Soff ,root and latest TWRP
If u have TWRP you can flash Rom for yours Firmware version
Sorry for my ENG
Well after a good few hours at the phone last night I'm still in the same position. My hands are a bit tied as I still have S-On but I don't know if I can even get S-off while stuck where I am. I can get in to bootloader/download/ recovery. Have tried Thicklizards suggestion above which didn't work, have also tried a hard reset. Also tried to flash a new recovery image but the error which popped up told me that I can't flash that partition with S-On. I have tried to run a RUU but I may have downloaded the wrong one, also the error which came up during install was that the battery was below 30%, I'm assuming that's an issue as I'm trying to run it from bootloader, I've tried looking around and I can't find any resource that would tell me if trying to run the RUU from bootloader would cause that error. Ive also tried to run the RUU as an image on the SD card but I got an error 99 that said I had a failure with the RU. I'll be away from my laptop for 2 days now but when I get back I'll try this RUU from Nikolay82, I don't know how I missed it before http://forum.xda-developers.com/one-m9/help/htc-one-m9-3-35-401-12-ruu-installer-t3318517. The only issue is that this is an upgrade to 3.35.401.12 and I'm already at 3.35.401.12. The struggle continues.
If your bootloader is locked you can't flash a recovery, is it looked or unlocked?.
but you can try to flash the OTA, still you're with 3.35.401.12, by Nikolay82's method...
bzhmobile said:
If your bootloader is locked you can't flash a recovery, is it looked or unlocked?.
but you can try to flash the OTA, still you're with 3.35.401.12, by Nikolay82's method...
Click to expand...
Click to collapse
Bootloader is unlocked, I did actually try to lock it again using fastboot oem lock and it failed with "unknown command". I think I'll send it away for repair this time instead of fixing it myself again, but that means my phone will be gone for who knows how long.
For the fastboot command, do you have open terminal windows from the fastboot folder?
bzhmobile said:
For the fastboot command, do you have open terminal windows from the fastboot folder?
Click to expand...
Click to collapse
Hi BZH yes I was opening the terminal from the fastboot folder. Fastboot devices command and a few other fastboot commands were working but any fastboot oem command wasn't working.
still searching where the mistake is coming from ???
Jamballs said:
Bootloader is unlocked, I did actually try to lock it again using fastboot oem lock and it failed with "unknown command". I think I'll send it away for repair this time instead of fixing it myself again, but that means my phone will be gone for who knows how long.
Click to expand...
Click to collapse
Could try fastboot oem relock
Thanks for that Thicklizard, That didn't work either I'm afraid. The phone is off to HTC service now so we'll see what comes of that. I'll mark this thread as solved ... or rather unsolved.

Categories

Resources