Ok i have been sure to be careful in every step of this root but when i get to recovery mode my phone states E:Can't open /sdcard/update.zip(no such file or directory) Installation aborted i have triple checked that the file is there and spelled correctly has anyone had this issue or have an idea how to get by this draw back thanks
Ok i have been sure to be careful in every step of this root but when i get to recovery mode my phone states E:Can't open /sdcard/update.zip(no such file or directory) Installation aborted i have triple checked that the file is there and spelled correctly has anyone had this issue or have an idea how to get by this draw back thanks
Hello everyone,
I decided to finally replace my phone's rom with Cyanogenmod. This post will most likely cover the things that I have done so far and I'd appreciate if you can identify where I could have gone wrong or what I still need to do.
I first went to the site and looked through the wiki on how to install it.
I used the unrevoked method. At first I had difficulties with trying to get it to work as the software didn't seem to detect my phone. So I googled around and found out that one way to fix it was to install the HTC Sync software (thus installing the needed drivers to be able for unrevoked to identify my phone). I found this at some blog I found in the comments section of theUnlockr.
So I run unrevoked and it worked. I now have root access to my phone. Tested it on the terminal by typing su.
I downloaded the Rom Manager from the market (following the step in the cyanogenmod wiki) and updated ClockworkMod to 2.5.0.7
After a couple of tinkering I found out that there's this error when I start recovery mode.
Code:
E:Can't find MISC:
E:Can't mount CACHE:recovery/command
E:Can't find MISC:
E:Cant' mount CACHE:recovery/log
E:Can't find MISC:
I didn't pay attention to this.
So the next step for me would be to back up everything. SMS, apps, and then finally do a backup of the rom.
So back to the recovery mode. I go on and select 'backup and restore' from the recovery menu and I get this error:
Code:
SD Card space free: 664MB
backing up boot...
Error while dumping boot image!
E:Can't mount CACHE:recovery/log
E:Can't find MISC:
Ugh... So I google around for some info on this and found out a similar problem with mine. The recommended solution was to install AlphaRev on the phone, but unfortunately did some damage to the phone. The poster can only get as far as the bootloader and recovery. Has something to do with the phone being PVT4. I think the newer version of Alpharev handles that already.
Now I look around tutorials on how to install alpharev on my phone to gain S-OFF, but most of the tutorials I found recommends that I do a backup. How I could I do that if it doesn't work in the first place?
So then I decided to replace Clockwordmod with Amonra (lots of googling again) then I stumble upon this site where one can install Amonra in three ways: bootloader, Rom Manager, and terminal. Though not sure whether it would be applicable to my phone, I gave it a shot.
Bootloader: I downloaded the PC36IMG.zip file, placed in on the sdcard. Started on bootloader and crossed my fingers. Didn't work.
Rom Manager: I downloaded the free app. Unfortunately, the "Flash Alternative Recovery" is disabled.
terminal: typed this
Code:
flash_image recovery /sdcard/recovery-RA-supersonic-v2.3.img
and just gave me a "flash_image not found"
Okay... by then I'm getting a little bit frustrated. I started this endeavor around 10am and got to this step at around 4pm. It's 8pm now as I'm typing.
Back to my problem. Now I decide to try to replace using unrevoked. I try to use the software again but now there's an error that says that unrevoked cannot get to root and that the firmware may be a new version.
TL;DR
1. successfully rooted HTC Desire using unrevoked
2. Having trouble with Clockworkmod (Can't do backups)
3. Unable replace Clockworkmod with Amonra.
I am now at wit's end. I really don't know what to do now. I wouldn't attempt to install Alpharev without doing a back up. Even more so with trying to install cyanogenmod.
Any form of help is greatly appreciated.
Hi,
I hope someone can help me. I managed to get locked out of my new galaxy note 9 and decided to try to flash fresh software onto it. I have flashed phones a few times before and never had an issue.
Whilst the software was flashing in Odin it seemed to get stuck and so I used the shortcut to exit download mode and unplugged the USB from my computer thinking I could just try again. Since I have just had the phone stuck on a loop of a blue screen "installing system update", followed by "no command" and then a black screen which I have attached a picture of. I have tried all combinations of keys with no hope of entering download or recovery mode. If I hold both volume up and down as well as power button I get to the samsung loading screen but then this simply loops and goes back to what I described before if I release the buttons.
I really hope someone can help as it seems I have bricked by new phone. Sorry if this isn't the right place to post but I'm a new member here.
Cheers in advance,
John
What's on the black screen:
#Reboot Recovery Cause is [BL: Recovery mode set by key]#
E: failed to mount/cache: Invalid argument
Support SINGLE-SKU
Block based OTA
Supported API: 3
'MANUAL MODE v1.0.0#
E:Failed to mount /cache:Invalid argument
E:Failed to mount /cache:Invalid argument
E:Failed to mount /cache:Invalid argument
E:Failed to mount /cache:Invalid argument
E:Can't mount /cache/recovery/last_locale
johnwick27 said:
What's on the black screen:
#Reboot Recovery Cause is [BL: Recovery mode set by key]#
E: failed to mount/cache: Invalid argument
Support SINGLE-SKU
Block based OTA
Supported API: 3
'MANUAL MODE v1.0.0#
E:Failed to mount /cache:Invalid argument
E:Failed to mount /cache:Invalid argument
E:Failed to mount /cache:Invalid argument
E:Failed to mount /cache:Invalid argument
E:Can't mount /cache/recovery/last_locale
Click to expand...
Click to collapse
Can you get it to boot to a screen that says something like "encountered an issue, connect to Smart Switch"? If so, you "should" still be able to flash it via Odin or connect to Smart Switch and flash the device to recover it.
Or, you can try a USB jig made for Samsung devices, it's a tool that forces the device into download mode, they are only about $3 - $4 USD on eBay and other locations.
Or you can try the "300k resistor" trick or the "301k resistor" trick. They also can force a Samsung device into download mode, if possible, but there is no guarantee that the jig or the resistor tricks will work.
You are getting signs of life so there "should" be something that can revive the device.
You might have to send it to a shop that offers a JTAG service or replace the motherboard. The JTAG service is also not guaranteed.
Sent from my LGL84VL using Tapatalk
i have similar problem do find a solution??
I recently tried to install a custom ROM in my samsung j6+ but halfway through it my PC turned off.
Then the problem starts i decided to reboot my phone but it shows this error "No command" " #Reboot recovery cause is [[check_bootmode]RebootRecoveryWithKey]#
Block-based OTA
Supported API: 3
# MANUAL MODE v1.0.0#
E:Failed to mount / cache: Invalid argument
The error message keeps appearing for just a fraction of a second then disappear and appear again
I tried to go to recovery mode but no luck i cant get to it
I drained the battery to turn off the device then go download mode but after get to it, it also keep restarting
help me please. thank you
johnwick27 said:
What's on the black screen:
#Reboot Recovery Cause is [BL: Recovery mode set by key]#
E: failed to mount/cache: Invalid argument
Support SINGLE-SKU
Block based OTA
Supported API: 3
'MANUAL MODE v1.0.0#
E:Failed to mount /cache:Invalid argument
E:Failed to mount /cache:Invalid argument
E:Failed to mount /cache:Invalid argument
E:Failed to mount /cache:Invalid argument
E:Can't mount /cache/recovery/last_locale
Click to expand...
Click to collapse
hello sir i have the same problem do you find solution?
I recently tried to install a custom ROM in my samsung j6+ but halfway through it my PC turned off.
Then the problem starts i decided to reboot my phone but it shows this error "No command" " #Reboot recovery cause is [[check_bootmode]RebootRecoveryWithKey]#
Block-based OTA
Supported API: 3
# MANUAL MODE v1.0.0#
E:Failed to mount / cache: Invalid argument
The error message keeps appearing for just a fraction of a second then disappear and appear again
I tried to go to recovery mode but no luck i cant get to it
I drained the battery to turn off the device then go download mode but after get to it, it also keep restarting
help me please. thank you
Ok, first off let me say thank you in advance. I had the Oneplus 7t and (Tmo) and played hell with it trying to root until I found that MSMTool and then had a hayday with it. Now I have the 8t, I have been waiting for a working TWRP because I really like TWRP and I really like Magisk. As of yesterday my stock Rom was fully rooted with TWRP, Magisk, and busybox. It had been that way for several days with no glitches or errors, so obviously bootloader unlocked, phone is carrier unlocked and got my oneplus unlock token last tuesday (5 days ago). On my 7t after trying several ROM's I settled on Havoc-OS so with my 8t I was just going to go straight to Havoc-OS even thought I might try messing around with a kernel update at some point in the near future. BUT...... somehow I have angered the Android God's and am being punished. I have been through much frustration in the past with things Android, have always been able to figure it out thanks to XDA, but today I must humble myself, finally make an account and ask for help. To the best of my recollection here is what I have done with the results.
But before that my current state is, I can boot to TWRP recovery, fastboot, bootloader, EDL and all that but I wiped partitions prior to starting the flashing process so right now I can not boot to system.
I started at techsphinx.com/smartphones/install-havoc-os/ It is a very straighforward guide. but gave error 7, which I believe is wring device error so I checked and it's the kebab havoc like it should be (I think, I'll get to that in a moment) so I look it up and everything says to get in to the file and find the update binary and update script and edit the update script, blah blah EXCEPT that in my copy of havoc-os in the called out directory I have different files. Mine are otacert and metadata. two completely different scenarios. otacert is a binary file while metadata when opened with notepad gives this text:
ota-property-files=payload_metadata.bin:1784:116801,payload.bin:1784:1262105569,payload_properties.txt:1262107411:156,care_map.pb:737:1000,metadata:69:621
ota-required-cache=0
ota-streaming-property-files=payload.bin:1784:1262105569,payload_properties.txt:1262107411:156,care_map.pb:737:1000,metadata:69:621
ota-type=AB
post-build=OnePlus/havoc_kebab/OnePlus8T:11/RQ3A.210805.001.A1/eng.kshiti.20210826.065117:userdebug/release-keys
post-build-incremental=eng.kshiti.20210826.065117
post-sdk-level=30
post-security-patch-level=2021-08-05
post-timestamp=1629960471
pre-device=OnePlus8T,OnePlus9R
I can't remember when was supposed to be remarked in the updater-script file but there is nothing like that in this file. That is all that is present in this directory, META-INF/com/google/android
Everything I try to push to the device errors out before it completes with a broken pipe error, adb sideload is similar in that it won't finish the transfer to the phone. Now anything I try to do in TWRP gives me error can't mount partition_name. I had a nandroid backup but I can't use it because partitions can't be mounted.
I wondered if it was the tmobile variant thing so I tried the msm tool for switching tmobile to universal edition first but I can't get msm tool to work in my device manager the now soft-bricked device shows up as the QS BULK device which is not the right one so I install the automatic driver installer for the qualcomm usb drivers, no effect so I follow how to install manually and windows will not let me and tells me it's likely that the driver file is corrupt or has been tampered with.
My frustration level right now is just before the part where I take a hammer to the phone and make as many small pieces as I can.
The state of my phone right now is that I can't even get it into edl mode because I can't get it to turn off. reboot to power off, holding volume up and power both leave it to when I push both volumes in the screen comes on and I am in bootloader mode. I am at a complete and utter loss.
I need my phone for work tomorrow
@Frustrated_AF,
Regarding the QualComm device driver: I've attached my notes on how I installed the MSM Tool (including the QC driver) in case it's of any help to you. (@Unbrick Instructions.zip). Just note that my phone is a KB2000.
If you can get into bootloader mode, than you can flash TWRP. Get it from https://forum.xda-developers.com/t/...recovery-project-8t-kebab-2021-09-04.4302449/
And once you're in TWRP you can install the Havoc rom zip file using the instructions in post #2 in the TWRP thread. Get Havoc from https://forum.xda-developers.com/t/...8-for-oneplus-8t-official-2021-08-26.4293817/.
Note that the Havoc thread installation instructions were written before TWRP for the 8T was available. And, yes, I've installed Havoc using TWRP so I know it works.
BillGoss said:
@Frustrated_AF,
Regarding the QualComm device driver: I've attached my notes on how I installed the MSM Tool (including the QC driver) in case it's of any help to you. (@Unbrick Instructions.zip). Just note that my phone is a KB2000.
If you can get into bootloader mode, than you can flash TWRP. Get it from https://forum.xda-developers.com/t/...recovery-project-8t-kebab-2021-09-04.4302449/
And once you're in TWRP you can install the Havoc rom zip file using the instructions in post #2 in the TWRP thread. Get Havoc from https://forum.xda-developers.com/t/...8-for-oneplus-8t-official-2021-08-26.4293817/.
Note that the Havoc thread installation instructions were written before TWRP for the 8T was available. And, yes, I've installed Havoc using TWRP so I know it works.
Click to expand...
Click to collapse
Thank you, I have one issue (at least) that I can't find anything on in your instructions... I have been unable to install the usb drivers, on 2 different laptops one old one new one running windows and one running Linux with Windows in VMWare. same thing both times. I have tried the oneplus exe file, the qualcomm auto-installer andstlil show up as QUSB_BULK_ CID...... When I try to manually install by clicking on let me choose one Windows won't allow it. Windows says the file is possibly corrupted or tampered with. So I am unable to use any of the MSMTool versions I have tried.
Any ideas on that?
Cancel that. Please forgive me if I seem panicky if I can't get my phone working by tomorrow morning there will be hell to pay at work. So in your instructions where you write:
"If it shows up as QHUSB_BULK, it means Qualcomm driver wasn't installed automatically by Windows Update. Download the latest one from Microsoft website at http://download.windowsupdate.com/c..._fba473728483260906ba044af3c063e309e6259d.cab (source https://www.catalog.update.microsoft.com/Search.aspx?q=qualcomm hs usb 9008 ), extract the files, then install it manually by right clicking on QHUSB_BULK and selecting "Update driver software" and "Browse my computer for driver software" to where you extracted the CAB file and selecting that directory."
I downloaded the file (brought back memories from doing my 7t) and extracted it to a folder on my desktop oddly enough without even updating the driver my edl mode device was detected correctly.
Working on the rest I'll get back to you shortly and once again I can't even begin to express my thanks!
@BillGoss Ok hopefully this will be the last question and it might be a dumb one but I'm not wanting to screw this up any more, In post #2 paragraph 2, bullet point 1 at https://forum.xda-developers.com/t/...recovery-project-8t-kebab-2021-09-04.4302449/
He states "sideload/flash ROM + installer" if I sideload the ROM it's going to install it, I don't see that the installer would go onto the device??? That URL is from the RECOVERY part of it from the ROM part of it at the URL https://forum.xda-developers.com/t/...8-for-oneplus-8t-official-2021-08-26.4293817/ under "installation" it describes a process of altering the RO M files payload.bin and then putting the pieces back together then using ROMinstaller.exe while phone is in fastboot mode.
Could you shine any light on this for me?
Frustrated_AF said:
@BillGoss Ok hopefully this will be the last question and it might be a dumb one but I'm not wanting to screw this up any more, In post #2 paragraph 2, bullet point 1 at https://forum.xda-developers.com/t/...recovery-project-8t-kebab-2021-09-04.4302449/
He states "sideload/flash ROM + installer" if I sideload the ROM it's going to install it, I don't see that the installer would go onto the device??? That URL is from the RECOVERY part of it from the ROM part of it at the URL https://forum.xda-developers.com/t/...8-for-oneplus-8t-official-2021-08-26.4293817/ under "installation" it describes a process of altering the RO M files payload.bin and then putting the pieces back together then using ROMinstaller.exe while phone is in fastboot mode.
Could you shine any light on this for me?
Click to expand...
Click to collapse
Like I said, the Havoc thread instructions relate to the pre-TWRP method. And I've never used that method.
The TWRP instructions say to sideload the rom and installer (TWRP installer zip) because installing the Havoc rom also installs a recovery, thereby replacing TWRP. That's why you need to reinstall TWRP after installing Havoc.
@BillGoss Thank you for your patience with this. I just assumed that learning what I learned when I did my 7t would transfer right on over to this and it would be simple... Haha. So now this... sideloading ROM at 47% from my powershell window it stops and says "adb: failed to read command: No error" On my device:
Flashing A/B zip to inactive slot A
step 1/2
step 2/2
Failed to mount '/system_ext' (Invalid argument)
Failed to mount '/product' (Invalid argument)
Failed to mount '/vendor' (Invalid argument)
Failed to mount '/odm' (Invalid argument)
Updating partition details...
Failed to mount '/system_ext' (Invalid argument)
Failed to mount '/product' (Invalid argument)
Failed to mount '/vendor' (Invalid argument)
Failed to mount '/odm' (Invalid argument)
...done
Devices on super may not mount until rebooting
recovery.
To flash additional zips, please reboot recovery to
switch to the updated slot.
Leaving me clueless as to what has gone wrong or what to do about it. Any ideas on this one?
Edit; It worked! I did nothing else except rebooted it and it came up fine brand new havoc-os so far nothing at all wrong. I have no idea why all the failed to mount errors and I don't think I really care all that much it works!!! I'm going to flash twrp and magisk and be done for the night with it. @BillGoss I can't thank you enough. You have saved my bacon [email protected]!
Frustrated_AF said:
@BillGoss Thank you for your patience with this. I just assumed that learning what I learned when I did my 7t would transfer right on over to this and it would be simple... Haha. So now this... sideloading ROM at 47% from my powershell window it stops and says "adb: failed to read command: No error" On my device:
Flashing A/B zip to inactive slot A
step 1/2
step 2/2
Failed to mount '/system_ext' (Invalid argument)
Failed to mount '/product' (Invalid argument)
Failed to mount '/vendor' (Invalid argument)
Failed to mount '/odm' (Invalid argument)
Updating partition details...
Failed to mount '/system_ext' (Invalid argument)
Failed to mount '/product' (Invalid argument)
Failed to mount '/vendor' (Invalid argument)
Failed to mount '/odm' (Invalid argument)
...done
Devices on super may not mount until rebooting
recovery.
To flash additional zips, please reboot recovery to
switch to the updated slot.
Leaving me clueless as to what has gone wrong or what to do about it. Any ideas on this one?
Edit; It worked! I did nothing else except rebooted it and it came up fine brand new havoc-os so far nothing at all wrong. I have no idea why all the failed to mount errors and I don't think I really care all that much it works!!! I'm going to flash twrp and magisk and be done for the night with it. @BillGoss I can't thank you enough. You have saved my bacon [email protected]!
Click to expand...
Click to collapse
Glad you're ok now. Those error messages are common when installing roms because those partitions (what used to be the system partition and is now a set of virtual partitions inside the physical super (sda15) partition) don't get properly setup until you reboot.
The 8T is a virtual A/B device which makes life more complicated than the old simple partition and straight A/B partition devices.