am I just mistiming the enter button or something, or do I have a bad download again.
It was asked last month in the root the aria thread with no resolve so if I could figure it out this might help some others out including myself, and I thought getting adb working was the hard part...
here is the code exactly
Code:
-- Install from sdcard..
Finding update package...
Opening update package...
Verifying update package...
hit enter as per instructed (tried before after and all around this moment)
Code:
Installing update...
E:Error in /sdcard/update.zip (status 0)
Installation aborted.
just run the two commands again.
adb push ota.zip /sdcard/update.zip
then type: adb push update.zip /sdcard/update.zip
but select update.zip on the phone and press power first and when it says "verifying" hit enter on the keyboard.
If it still doesnt work try reformatting the sd card
I'm such a freaking newb I forgot to put the first update.zip /sdcard/update.zip
trying in a few moments
and wham bam thank you mam I have root.
so if you get error 0 make sure you read carefully and don't try to perform root almost asleep.
I was redoing the ota.zip not the update.zip silly me
Mine says the same thing, but I made sure I copied it to the sdcard first along with a ROM and ota.zip, and root.zip.
I also noticed that on my command prompt that it says error: device not found.
Right before it says device not found in my command prompt, the batch file it typing adb push ota.zip //sdcard/update.zip.
right after i type rootme2 the batch file also types in my command prompt clr, but an error comes out 'clr' is not recognized as an internal or external command operable program or batch file. "Please Wait..." This is the time where I am trying to time the apply sdcard:update.zip in my recovery console on my phone with hitting enter for the second time after typing rootme2.
Any suggestions? Am I missing something? Am I mistiming it still? Is it that difficult to time it correctly?
I do have an HTC Android phone USB device under disk drives and a E:\ under portable devices without an exclaimation mark in my device manager. However if I try to double click drive e: in my computer it says to enter a disk.
ANY advice is GREATLY appreciated!!
BTW I have made sure adb is running in task manager and I have tried unplugging and replugging in my usb cord.
I was having problems getting my slide running. It was suggested in the slide forums to install the free version of pda net onto the pc. It will find the right drivers for your device. I know the aria and slide are very simmilar. Alsp, it sounds silly, but I couldn't get root usinf my primary pc running win 7 64 bit. I dug an old xp 32 bit laptop out of my closet and got everything perfect on the first try.
Hope it helps some.
Sent from my rooted Mytouch Slide using XDA app.
Thank you for your reply. I already took the initiative to try it with an XP 32-bit system. Both systems seem to not be able to contact the device while it is in recovery state. No problems with the device while it is on and connected to either machine.
This is an Eris I am trying to root by the way. Everything seems to go like it is supposed to until the last part. The rootme2 command.
Thanks again, any other advice is appreciated!
Sorry that none of that has worked. I saw eris and read aria......
Either way, I wrote it up, maybe it will help someone.
I have been folowing the aria since my father in law had me root his. I used the exact computer and same process to do both. I only got root on the aria, never installed a rom or anything, he just wanted swipe like my wife and I have. I followed one thread or another, and it reccomended running an app called usbdeview. I deleted all htc drivers that were using usb. I then followed advice on another thread to install pda.net with links. Then follow eugene373's htc root method. When it finally worked it was easy. I did it another 10 times before I finally figured out how to get clockwork to take.
Only other thing to make sure you have is the newest java installed. Not the normal one but the one for developers. If ya are stuck, try reading a little in the htc esspresso (mytouch slide) forums. The two phones are pretty much the same on the inside. Different wifi and a few other things. See if ya stumble onto your exact problem. I am not saying to flash slide roms or anything.
Best of luck to you
Sent from my rooted Mytouch Slide using XDA app.
How about...
Move your adb installation to something like c:\android. Put all of the files you are working with into c:\android\tools
The change directory to your android tools folder and try it again.
Sent from my rooted Mytouch Slide using XDA app.
This is what I am getting from windows console both the same result with windows 7 64-bit and windows xp 32-bit...
C:\android\tools>rootme2
C:\android\tools>clr
'clr' is not recognized as an internal or external command,
operable program or batch file.
"Please Wait..."
C:\android\tools>adb push ota.zip /sdcard/update.zip
error: device not found
"OK! Congratulations, your phone is almost ready to be rooted"
"Here is the tricky part..."
""
"To access the controls in recovery, press Volume Up+Power"
"From here, use the Volume buttons to go up and down and the Power button to sel
ect"
""
"IMPORTANT:"
"You will select apply update.zip, but within 1/2 sec of doing this you must pre
ss enter to continue this script"
"If it is not done in the timely manner, you can try again by rerunning this scr
ipt"
C:\android\tools>pause
Press any key to continue . . .
C:\android\tools>adb push update.zip /sdcard
error: device not found
"From here, you should see ClockWork Recovery by Koush, and can install any ROM
you would like!"
"If you liked the work in this, send a donation to Wes Garner or Eugene_373 (lin
ks in the ReadMe)"
On the phone I get...
Android system Recovery <2e>
Use volume key to highlight: click power key to select. (I navigate to Apply sdcard:update.zip and hit power button. (when I see the red triangle in the background on the phone turn to green circle, I immediately press enter on my console on my windows machine and get the following)
E:Can't open /cache/recover/command
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
E:Error in /sdcard/update.zip
(Status 0)
Installation aborted.
I have done this a half a million times already with the same results. I tried at different times of the process with the same results. I do see HTC Android Phone USB device in my device manager with no errors. I do not see an Android adapter with My HTC in the device manager at all while in recovery mode like I do when the phone is all the way on and booted into the system.
I have tried everything listed in this thread and have been following wesgarner's post in forum.xda-developers.com/showthread.php?t=713347 which is based on Eugene_373's instructions. I found this thread with someone that appeared to have the same problem as I, and I tried what he tried and no luck.
Any further advice is GREATLY appreciated!! Thank You in advance!!
Has no one had this problem?
Factory wipe will just take me back to the version that I got this phone with, correct (2.1, replacement phone)?
Thank You!!
the push is
adb push update.zip /sdcard/update.zip
for case 0
I was trying to push this again and getting error 0
adb push ota.zip /sdcard/update.zip
I am haveing the same problem where after fastboot/boot loader screen comes up I go to recovery it brings me to the screen with the phone , triangle and exclamation.I next push power and up volume button and it brings me to the android system recovery. <2e>. In yellow at the bottom it says E:Can't open /cache/recovery/command, before i even touch anything else. I then go to apply sdcard:update.zip and given the error:
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:failed to open /sdcard/update.zip (no such file or directory)
E: signature verification failed
Installation aborted
I have formated the sd card to FAT32 many times and now wondering if someone has the ability to send me their files that worked to boot up their phone with similar problems. Or even the clockwork backup files from the clockwork mod nan backup.
geske001 said:
Thank you for your reply. I already took the initiative to try it with an XP 32-bit system. Both systems seem to not be able to contact the device while it is in recovery state. No problems with the device while it is on and connected to either machine.
This is an Eris I am trying to root by the way. Everything seems to go like it is supposed to until the last part. The rootme2 command.
Thanks again, any other advice is appreciated!
Click to expand...
Click to collapse
if you're having issues with drivers and ADB connectivity, install HTC Sync and it should install the proper drivers for your device. i have done that on a 64x windows 7 machine and a 32x XP machine.
http://www.htc.com/us/support/droid-eris-verizon/downloads/
cemysh33 said:
I am haveing the same problem where after fastboot/boot loader screen comes up I go to recovery it brings me to the screen with the phone , triangle and exclamation.I next push power and up volume button and it brings me to the android system recovery. <2e>. In yellow at the bottom it says E:Can't open /cache/recovery/command, before i even touch anything else. I then go to apply sdcard:update.zip and given the error:
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:failed to open /sdcard/update.zip (no such file or directory)
E: signature verification failed
Installation aborted
I have formated the sd card to FAT32 many times and now wondering if someone has the ability to send me their files that worked to boot up their phone with similar problems. Or even the clockwork backup files from the clockwork mod nan backup.
Click to expand...
Click to collapse
the initial error is expected if you're attempting to access clockwork recovery the old way, (attempting to plug the usb cable in at the right time, pushing the commands, etc) which is now not needed. to root your phone, simply use the unrevoked teams method. http://forum.xda-developers.com/showpost.php?p=6952379&postcount=1
cemysh33 said:
I am haveing the same problem where after fastboot/boot loader screen comes up I go to recovery it brings me to the screen with the phone , triangle and exclamation.I next push power and up volume button and it brings me to the android system recovery. <2e>. In yellow at the bottom it says E:Can't open /cache/recovery/command, before i even touch anything else. I then go to apply sdcard:update.zip and given the error:
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:failed to open /sdcard/update.zip (no such file or directory)
E: signature verification failed
Installation aborted
I have formated the sd card to FAT32 many times and now wondering if someone has the ability to send me their files that worked to boot up their phone with similar problems. Or even the clockwork backup files from the clockwork mod nan backup.
Click to expand...
Click to collapse
ur zip file is not signed properly...try to sign it or install through toggle signature verification in CWM recovery
My phone is a Samsung galaxy S3 SCH-S968c, Verizon Networked for Straight Talk. I ran into having my phone stall after the Samsung logos boot up and then the tracfone logo appears and stalls there. The issue started after i tried installing multiple tweeks using a popular app for rooted devices (i cant think of the apps name at the moment). I have a version of CWM on it. After reading threads here in XDA i found that my CWM will not work correctly on this phone. Retired Forum Moderator "edfunkycold" said "It's not really a bug with the recoveries which where modded. It's part of whatever Samsung has done to keep people from rooting and flashing roms." so i downloaded both CWM_mod2.img and TWRP_mod2.img.
So between the soft bricking and the usless cwm i cannot flash anything or access the internal or external sd cards. I tried using ADB and these commands:
adb push .img /sdcard/.img
adb shell
su
dd if=/sdcard/.img of=/dev/block/mmcblk0p18
I just get the Android Debugging Bridge version...............
I also tried other methods found in XDA using ADB.
I tried Samsung Kies, 4 versions of Odin, SkipSoft Android Toolkit and some other java executable program that didnt work.
I can boot into both recovery mode and download mode.
Recovery mode does nothing....
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
E: Can't mount /sdcard
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
.....etc. etc.
In Download mode, Odin recognizes that the phone is connected but when i try loading anything it wont connect. example: trying to load a bootchain file it says:
checking MD5 finished successfully..
Leave CS..
All threads completed. (succeed 0 / fail 0)
Other attempts show the RED FAIL square.
Im having trouble finding the correct Files to Flash. Im guessing the SCH-I535 is the non-straight talk equivalent to my straight talk phone so i have downloaded file: Samsung-Updates.com-SCH-I535-VZW-I535VRALF2_Kernel.zip
and Rom: Sons Of Android - cm-10.2-20130928-UNOFFICIAL-jewel.zip
Bottom line is I DONT CARE what version of android (stock or ROM) as long as it's compatible and need the correct flash files necessary. I THINK it originally has jellybean 4.2.2??? PLEASE help. ive been messing with this for 3 weeks now :crying:
Thanks
try "fastboot flash boot boot (recovery.img location on your computer). " It will remove your rom, so put one on the sd card.
jbaker22 said:
try "fastboot flash boot boot (recovery.img location on your computer). " It will remove your rom, so put one on the sd card.
Click to expand...
Click to collapse
ADB is not recognizing my phone. Odin still is. I tried to flash recovery with Odin last night. The process completed with success but when i restarted the phone i was not able to gain access back to the recovery. Now I can only get into download mode. Is this why ADB is not working, cuz it has to be in recovery mode?
Also I am confused on how the file structure should be when i put a rom on the sd card. I know they go in the root..... do i just extract them from the ZIP straight over to the SD? Is there a way to convert ZIP files to an Odin flashable file?
FIXED!!!! w/ Straight Talk Stock Firmware SCH-S968C
I FINALLY found a working download link for the correct firmware!!! Thanks to an old post by Kenny1974 who posted the name of the file. I googled it and found only one available!
https://www.dropbox.com/s/j2uc1hkm4...8CTFNAMH1_1304014_REV09_user_low_ship.tar.md5
I Flashed with Odin and Presto!
If this link becomes invalid, p.m. me and i will send you a link or the file.
I have a J7 prime, on7xelte, g610f, oreo 8.1.0, stock firmware, no custom recovery. I wanted to root it and for that wanted to install twrp. I did NOT use Samsung Antiroot Removal Tool, RMM State Bypass zip, No Verify Encrypt zip. I tried to flash it using adb but no matter what it wont detect my phone in recovery/fastboot, only when its on or sideload. On sideload i got an error. So i tried to do it with odin, since odin detects my phone EVEN though windows doesnt. After doing that somehow my system got corrupted. i couldnt mount /data once in twrp and trying to boot it up caused bootloop. i couldnt get it to mount usb either. then i force restarted it into download mode and reinstalled stock firmware, retried the twrp .tar, and failed again. and again. then i saw a video rooting j7 prime with a root file The link to the video:
. the file was for g610fd, i thought the "d" was a typo and flashed it anyway. Now I boot up into the stock recovery with the exact following lines:
Installing system update (loading)
no command (exclamation triangle)
(after a while)
Android recovery
samsung/on7xeltedd/on7xelte
8.10/MIAJQ/G610FDDS1CTE3
user/release-keys
[the regular options here]
#fail to open recovery_cause(no such file or directory)#
#Reboot Recovery Cause is [UNKNOWN]#
File based OTA
supported API: 3
E: unknown volume for path [/odm]
E: unknown volume for path [/vendor]
E: unknown volume for path [/odm]
E: unknown volume for path [/vendor]
#MANUAL MODE V1.0.0#
Successfully verified dmverity hash tree
:/ so apparently at this point, only the volume buttons work. i mean i can only go up and down but not select a thing. its bad. so i tried force rebooting into the download mode. THERE, the VOLUME buttons dont work. means i cant confirm and proceed into the download mode fully. my pc doesnt recognize the device in either states so i cant command in adb. one thing is that even before this error my pc didnt notice my phone in either states. so i might be missing the right drivers. my wire isnt flawed, i have 3 wires. i have hand typed everything here so will be great if you take your precious time to type any advice here for this poor fellow who is scared of losing his only phone.
Hello,
Here's what I've been doing. Unlocked my phone and gained root. Then I installed Linage OS 18 using twrp. First startup went fine. Went into settings to confirm I was on Android 11. Then I rebooted my phone just to discover it fails to boot. I get lots of errors on my display. In fact my whole display gets cluttered up by lines of error (see examples below). If I'm doing a normal restart my phone gets stuck in boot loop. I can get it to load up bootloader, but if I choose recovery I just get lots of errors. After several minutes it goes into Linage recovery. I've tried doing a factory reset in Linage recovery, but still these errors show up and it doesn't make a difference. I've tried pretty much everything here without luck. Whatever I do I get these same errors.
Help! By the looks of it I have completely messed up my phone
Example of errors:
E: inotify_add_watch failed: No such file or directory
E: [libfs_mgr] Skipping mounting '/dev/block/bootdevice/by-name/cache'
E: [libfs_mgr] Failed to open '/dev/block/bootdevice/by-name/bache": No such file or directory
E: Failed to mount /cache: No such file or directory
This list goes on and on...
One thing I've learned after over 10 years of HTC phones is they're hardly ever COMPLETELY bricked. Or I'm just that good... I dunno. I've never actually not been able to recover one. So you mentioned it was LOS 18.... Was it a GSI? Because if not, it had to of been a ROM for a different device... And that complicates things. I'm gonna try and help though.
sibbe83 said:
One thing Hello,
Here's what I've been doing. Unlocked my phone and gained root. Then I installed Linage OS 18 using twrp. First startup went fine. Went into settings to confirm I was on Android 11. Then I rebooted my phone just to discover it fails to boot. I get lots of errors on my display. In fact my whole display gets cluttered up by lines of error (see examples below). If I'm doing a normal restart my phone gets stuck in boot loop. I can get it to load up bootloader, but if I choose recovery I just get lots of errors. After several minutes it goes into Linage recovery. I've tried doing a factory reset in Linage recovery, but still these errors show up and it doesn't make a difference. I've tried pretty much everything here without luck. Whatever I do I get these same errors.
Help! By the looks of it I have completely messed up my phone
Example of errors:
E: inotify_add_watch failed: No such file or directory
E: [libfs_mgr] Skipping mounting '/dev/block/bootdevice/by-name/cache'
E: [libfs_mgr] Failed to open '/dev/block/bootdevice/by-name/bache": No such file or directory
E: Failed to mount /cache: No such file or directory
This list goes on and on...
Click to expand...
Click to collapse
I'm aware of the usual tips for this but nothing seems to be working for me. I currently have three phones (S3 Mini with stock android, OPO and HTC U11 with Lineage). I've just installed the latest Lineage release on my HTC and everything seemed to be working. However, I can no longer boot into recovery. TWRP (from which I've just installed the Lineage update) doesn't show up at all. It just boots into a blackscreen that turns into what seems to be a Lineage recovery with these error messages:
E:inotify_addd_watch failed: No such file or directory
E:[libfs_mgr]Skipping mounting '/dev/block/bootdevice/by-name/cache'
E:[libfs_mgr]Failed to open '/dev/block/bootdevice/by-name/cache' : No such file or directory
E:[libfs_mgr]Failed to mount /cache: No such file or directory
E:Failed to clear BCB message: failed to open /dev/block/bootdevice&/by-name/misc: No such file or directory
E:inotify_addd_watch failed: No such file or directory
E:[libfs_mgr]Skipping mounting '/dev/block/bootdevice/by-name/cache'
E:[libfs_mgr]Failed to open '/dev/block/bootdevice/by-name/cache' : No such file or directory
E:[libfs_mgr]Failed to mount /cache: No such file or directory
At this point I'd use ADB to flash TWRP and hope a newer version works but I can't connect my phone to my PC. And I've tried all three phones with different cables with my PC and laptop (both Win10) but not once did a computer even play the "something connected" sound, the USB preferences on every phone are greyed out, and the phones don't show the USB connection notification. I was currently trying to reinstall Magisk but I have to get into the recovery for that (and the Lineage recovery doesn't allow me to flash the .img file edited by the Magisk Manager). I just don't know what I could do to fix this.
Edit: I unfortunately have zero information on why it works now but after rebooting the phone for the 100th time it showed up in adb.