Ok so I cannot figure out what I did to my phone. I have s-off and my phone was rooted with TWRP Custom Recovery. I do not know why I did this but I installed the CWM app and installed the newest CWN recovery for the HTC One. I rebooted into CWM and tried wiping data. It got stuck on that so I rebooted and it gets stuck on the HTC boot up screen. When I go back into the bootloader and try installing the TWRP recovery using fastboot flash recovery recovery.img it gives me a remote: not allowed. When I do fastboot oem lock it says phone is already locked. I then do fastboot oem rebootruu and I get (bootloader) [err] command error!!! When I try rebooting into cwm I just get E: can't mount /cache/recover/commad, E: can't mount /cache/recovery/log and a bunch of other e: cant mount and open errors. Not sure how to get my phone to install the TWRP recovery and get a custom rom back on there. Anyone have any solutions?
slaz13 said:
Ok so I cannot figure out what I did to my phone. I have s-off and my phone was rooted with TWRP Custom Recovery. I do not know why I did this but I installed the CWM app and installed the newest CWN recovery for the HTC One. I rebooted into CWM and tried wiping data. It got stuck on that so I rebooted and it gets stuck on the HTC boot up screen. When I go back into the bootloader and try installing the TWRP recovery using fastboot flash recovery recovery.img it gives me a remote: not allowed. When I do fastboot oem lock it says phone is already locked. I then do fastboot oem rebootruu and I get (bootloader) [err] command error!!! When I try rebooting into cwm I just get E: can't mount /cache/recover/commad, E: can't mount /cache/recovery/log and a bunch of other e: cant mount and open errors. Not sure how to get my phone to install the TWRP recovery and get a custom rom back on there. Anyone have any solutions?
Click to expand...
Click to collapse
Isn't it "fastboot oem reboot ruu" ?
Its
fastboot oem rebootRUU
Are you still s-off?
Sorry guys I actually some how got everything working again. Thanks!!
Related
Hi i've messed up in partition menu in recovery and as a result my phone boots in fastboot, from fastboot i can get to bootloader only cant get to recovery because it stops on htc screen. Ive always used custom recovery to change roms because ive got hboot 0.83.0001 and my mobile always stopped on htc screen every time i tried to fire up recovery using power button + down.
I used android sdk and find out that only fastboot commands work ie can see my device number (when I use fastboot devices command it gives me HT07PPL01815 fastboot). I've tried to restore android backup using fastboot flash system, fastboot flash boot, fastboot flash recovery but it gives me
sending boot <2560 kb> .....okay [0.401s]
writing "boot"......INFOsignature checking....
failed <remote signature verify fail>
My boot image is missing as well, is there anybody how can help me what to do?
You can of course not flash your backup using a s-on hboot as it only allow files signed by HTC.
If I were you I would flash a stock Rom, which can be done via fastboot. Then just reroot afterwards
I have used RUU for SLCD screens and it helped
Okay, so I tried my best to search the forums and read the Q+A first, but the suggestions I've found so far didn't help me solve my problem.
I started with Hasoon200's tool kit and successfully unlocked the boot loader. Then, however, I got stuck at installing CWRM (it just wouldn't boot into recovery after installing). So I gave it a try with the "One X one Click" tool kit. I downloaded the n3okernel v34 and -modules as well as the newest nightly build of Cyanogen Mod (cm-10.1-20130414-NIGHTLY-endeavoru).
Now my HOX is caught in a boot loop. No matter which option I choose (fastboot / hboot, recovery, factory reset), it'll always go to the white HTC screen and stay there. Since Q+A's Q11 mentions it: yes, the last time I could boot into the OS (then still the stock image) I disabled fast boot in power settings.
Currently I can only access my HOX via fastboot, I already got a stock image and extracted the boot + recovery images, which I then flashed with the fastboot utility, as suggested in the Q+A's Q9. I erased the cache and rebooted to no avail. I also tried the firmware executable (RUU_ENDEAVOR_U_ICS_40_O2_DE_1.26.207.2_Radio_1.1204.90.13_release_251288_signed) to no avail.
Q+A's Q15 suggests sideloading via adb, but adb won't recognize my device.
I've also relocked the bootloader, this was suggested in another online ressource after flashing the stock boot+recovery images.
The phones HBOOT Version is 1.36.0000. I've noticed a different radio version than the one mentioned in my downloaded RUU; phone says 5.1204.162.29, downloaded file says 1.1204.90.13. I've not yet found a working download link with the right version number.
Please help.
Unlock it, make a full wipe in the custom recovery, install cm10.1, install gapps, flash the boot.img from the cm10.1 Rom and reboot.
So
Unlock it, flash a custom recovery (if you havent got one). If you still have trouble entering it you do this command in the bootloader
Fastboot erase cache
Mr Hofs said:
Unlock it, make a full wipe in the custom recovery, install cm10.1, install gapps, flash the boot.img from the cm10.1 Rom and reboot.
So
Unlock it, flash a custom recovery (if you havent got one). If you still have trouble entering it you do this command in the bootloader
Fastboot erase cache
Click to expand...
Click to collapse
Unlocking the bootloader works, but I'm not able to enter the recovery mode. It only shows a black screen (see attached picture).
EDIT: ok, wait... after flashing the clockwork recovery, I'm now getting into recovery mode. Will now try the next steps you suggested and give feedback later. Thanks a lot so far!
Press the Power and Volume down buttons which will take you the the hboot screen. From there select fastboot and flash a custom recovery like CWM via fastboot.
Now select hboot again and then select recovery!
Okay, so I successfully flashed CWM. I'm now able to boot into recovery. I also succeeded in flashing a boot.img which i took from cm-10.1-20130414-NIGHTLY-endeavoru.zip
c:\One\One\Data>fastboot flash boot boot.img
sending 'boot' (4960 KB)...
OKAY [ 0.684s]
writing 'boot'...
(bootloader) Format partition LNX done
OKAY [ 0.498s]
finished. total time: 1.186s
Now - when selecting hboot - the phone gets to another screen, the one where it displays the "HTC One" logo; I tried flashing the CM-image using fastboot (adb still doesn't work), but got following error message:
c:\One\One\Data>fastboot flash /sdcard update.zip
sending '/sdcard' (200098 KB)...
OKAY [ 25.507s]
writing '/sdcard'...
FAILED (remote: not allowed)
finished. total time: 25.716s
So close, yet so far...
So you have a working CWM installed right?
After flashing the boot.img... do "fastboot erase cache"
now go to CWM(recovery) and mount your sd card... copy the CM10ROM.zip and the gapps.zip to your HOX...
after that select wipe data and then wipe dalvic and cache...
Now select install zip from SD and install the ROM and then the gapps... reboot!
The problem is that I can't - or could'nt - transfer files any other way than using fastboot. However, I've now flashed Team Win TWRP2, and finally I'm able to access my phone over adb or just mount it and access it via explorer. Phew.
FINALLY!
So, if another noob like me finds this thread in the future...
After installing the TWRP2 recovery with flashboot flash twrp2.img, then booting into recovery and mounting my device, I was able to copy the CM-ROM-zip file onto the HOX. Then I rebooted into fastboot again and flashed the boot.img from aforementioned zip-file using "fastboot flash boot boot.img".
Booted again, selected the recovery system, installed ROM from zip file.
I'm getting too old for this ****. Almost had a heart attack when I thought I had bricked my phone. Thanks everyone for holding my hand, I appreciate it.
Good mate !
CASE CLOSED !
i think i've ****ed up my zenfone 2.
i can only go to fastboot and i can flash boot.img , droidboot.img and recovery.img
but i can't flash system.img (it says error: cannot load 'system.img') and everytime i try to go to recovery , it just freeze on asus logo and that's it.
i can't flash asus zip file (from asus site) because the size of the file is too large and i receive error.
i was using a custom rom and decided to return to stock.
how can i fix my phone?
Your system.img is corrupted somehow, if you are using shakalaca's img just delete the current one in your folder and unzip like you did before, that worked for me after the same thing happened to me while flashing.
okay.i have some good news (for myself )
i can now get into Recovery mode.it's stock recovery with and android robot in it and saying "installing System Update"
but after a few seconds it says error and that's it.
i use "adb devices" but there's no device connected.same for "fastboot devices"
now what should i do?
p.s : i get error everytime i want to "fastboot flash system system.img" and everytime i use "fastboot -w".for flashing system it gives the "error: cannot load 'system.img'" and for -w it says "FAILED (remote: flash_cmds error! )"
edit: now i have TWRP recovery.it's the UN-Tethered one.so i don't think i can install stock rom.right?
what should i do if i want to install stock rom?
edit 2:finally.i installed a custom rom for now.everything is ok.the phone is up and running.
but now i want to return to stock rom.how?
Good day.
I am having trouble flashing a kdz through download mode. My phone shows that the kdz is being flashed but somehow when it reboot it hangs at the LG logo. Plus the Flash tool hangs at 99% and gives me the error message "LGUserCSTool LGMobile Application stopped working".
A little background:
Well first of all i had flashed a custom rom "LG G3 ResurrectionRemix-M-v5.6.3-20160210-d855.zip" it was working fine. One day it shut down on its own, it couldn't reboot. It was stuck in a boot loop.
I entered recovery mode and tried reflushing Resurrection Remix but it gave me the error message "failed to mount /system (invalid argument) .../data .../efs..." etc. Then i tried wiping the data, system, dalvik and cache. It gave me the same "failed to mount /system (invalid argument) .../data .../efs..." etc.
After that I tried booting into download mode but it bypassed it and entered fastboot mode. In fastboot mode I entered the command "fastboot boot recovery.img (recovery.img was a TWRP recovery for LG G3) and tried to flash a custom rom but it gave me the same error messages "failed to mount /system (invalid argument) .../data .../efs..." etc.
After that i returned to fastboot mode and issued the command "fastboot flash laf.img" and it failed. I then tried "fastboot boot laf.img" and it entered into download mode. In download mode I tried flashing a KDZ i found at a site which I had to enter the device's IMEI code. But then at the phone reboots and hangs at the LG logo. After that the LG Flash tool gets stuck and crashes at 99%.
PLEASE, ANY ASSISTANCE WOULD BE APPRECIATED
i have the same problem.. how you slved it?
Please help. I'm stuck with this issue too
Same here guys !
Hi help,
I did something wrong with firmware flash.
So phone is bricked.
I followed on XDA the OP3 Unbrick forum, now my phone can turn on.
but I have an older bootloader. Also I het failed, when I press recovery, I can also only connect with fastboot and not ADB.
Help.
HELP ME
YourTheBest said:
HELP ME
Click to expand...
Click to collapse
flash this TWRP http://forum.xda-developers.com/devdb/project/dl/?id=21835&task=get
First go into fastboot then flash by typing fastboot flash recovery <name of the twrp you downloaded above><a
You can now flash latest OOS from TWRP
strumaticjoker2 said:
flash this TWRP http://forum.xda-developers.com/devdb/project/dl/?id=21835&task=get
First go into fastboot then flash by typing fastboot flash recovery <name of the twrp you downloaded above><a
You can now flash latest OOS from TWRP
Click to expand...
Click to collapse
I did that, thanks.
Doesn't work. I can do fastboot boot twrp.img
but when I install OOS or other ROM i get this error: ERROR 7 *unknow command and
failed to mount /cache (invalid argument)
failed to mount /system (invalid argument)
[email protected]#$%^&*()_
I get stupid error: when phones start/reboot.
md5 checkum failed
boot failed
recovery failed
My whole #!#$$#@ life failed.
Had the same few nights ago. Check the forum for the unbrick guide - method 2.
orlexx said:
Had the same few nights ago. Check the forum for the unbrick guide - method 2.
Click to expand...
Click to collapse
Then I lost al my WhatsApp messages... Right?
I can see the data files.
I still have issues!
Help