Related
Hi,
Just recently changed my phone from Desire to Desire S. I rooted and S-Off'ed using Revolutionary. Everything was fine for the last day. Phone is still new so wanted to run the battery down till flat then recharge fully to calibrate it.
Turned my phone on this morning and it just stays at the white HTC logo screen. Tried to boot into 4ext recovery and it start loading up. It then reads system 0 cache 0 and the recovery crashes.
Tried to use factory reset option from bootloader and it freezes. Had to pull battery.
Tried to wipe everything using Fastboot commander. Fails erasing cache, sytem, etc.
What do I do now?
It was working fine yesterday even rebooted it a couple of times and it was fine. But can't get it to do anything this morning.
-Revolutionary-
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3805.06.02.03_M
eMMC-boot
Please help.
Thanks
What I would do is to go to HBOOT and flash new Clockworkmod (or any other recovery tool) from the Android Flasher.
Android Flasher: http://forum.xda-developers.com/showthread.php?t=794638
CWM: http://downloads.saga-lbc-mod.de/recovery-images/PG88IMG-RECOVERYIMG-3.2.0.0.zip
Just connect the phone to PC via USB and start Android Flasher (while in HBOOT). Click recovery and choose unzipped recovery.img (from the PG88IMG file). If your new recovery is working just mount USB storage (in recovery), put some ROM there and install zip from sdcard.
I guess you can try to fix this differently, but this is the fastest method if you don't know what exactly is wrong.
Thanks for the quick reply.
It didn't work. Android Flasher crashes. Just says not responding.
Any other ideas?
I also get these errors in recovery:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Is my eMMC dead? Don't understand what its all about.
Is it fixable?
Thanks
abhi63 said:
I also get these errors in recovery:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Is my eMMC dead? Don't understand what its all about.
Is it fixable?
Thanks
Click to expand...
Click to collapse
Seriously, a quick look in the general's section will land you to the correct guide about it:
[GUIDE] Possible FIX for the infamous eMMC problem..
Note: I INTENTIONALLY did not link the guide so YOU will be searching for it.
Check the guide on my sig first.
I did follow all the instructions in the guide. Can't even get adb to recognise my device.
Fastboot freezes whenever I use any commands.
Can't flash anything.
I have been through a similar prblem recently. Ensure you're in recovery to utilise the adb shell (this flummoxed me for hrs lol)
If it's emmc related try the following to verify whether the chip is defective.
Ensure you are in recovery when utilising the adb shell (this took me hrs to work out as my device wasn't listed!) I was in fastboot ot Hboot mode.
To be sure that you really are effected by the emmc issue (and not other partition corruption issues that show similar symptoms) you have to look at the kernel messages when booted to clockworkmod recovery. Do to this boot the phone into recovery and then (in and adb shell) issue the following command:
Code:
cat /proc/kmsg | grep mmc0
or
Code:
dmesg | grep mmc0
If you see output like (not necessarily in this order) :
Code:
mmc0: failed to get card ready
mmc0: reinit card
mmc0: Starting deferred resume
mmc0: Deferred resume failed
then you are effected by this issue.
Basically the emmc chip does not initialize any more after the first attempt to access it in write mode.
Based on our current knowledge this is a hardware issue and can not be cured.
---------- Post added at 03:11 PM ---------- Previous post was at 03:08 PM ----------
You need adb setup for this, use one of the stickys to get started with adb
1, start up adb and type these in.
Code:
adb reboot recovery
2, after the device starts up in recovery, enter this
Code:
adb shell
3, and then this, your serial number should come up after mmc0:0001
Code:
cat /proc/kmsg | grep 'mmc0:0001'
It looks like M4G2DE 2.10 GiB is the bad one, judging from what the #G2root devs say, but lets see what our side is.
Thanks
And unfortunaly I got the bad one too, rooted with gfree, this is what I got
<6>[ 8.328460] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB
Thanks for the reply.
I just gave up in the end and got a replacement from Orange.
Thanks
1) Accidentally wiped all data including Internal Storage
2) Twrp 3.0 is working, but can't able to install any rom, Getting E:failed to mount / cache (Invalid argument) etc etc..
3)Getting "NO OS Installed" message in TWRP &- Internal Storage size is 0 (TWRP)
4) Followed Steps to flash factory image (WINDOWS)
Download the factory image fastboot package
Extract the contents of the fastboot package into a folder.
Download this flashing tools package
Extract the contents of the flashing tools zip into the same folder
To make sure, check that system.img, boot.img etc files are in the same folder as flash-all.bat, fastboot.exe etc
Connect your phone in fastboot mode, steps for which are : -
a. Power off your phone
b. Press and hold the Volume Up key
c. With the Volume Up key, connect the phone to your PC/Laptop with USB cable
d. You can let go off the Volume Up key when Fastboot Mode is displayed on the screen
Run flash-all.bat by double clicking on it.
A command window will open and flashing procedure will start
DO NOT disconnect the device during flashing procedure
The command window will close after the flashing process is over.
Disconnect the USB cable, and boot the phone normally by long pressing the Power button
But getting this error while flashing: http://imgur.com/g3NozUJ
After reboot,phone is stuck at YU logo..
Yuphoria stuck at YU Logo.
I had got notification for the OTA Cyanogen 12.1 Update and I had updated it. But even after reboot, the same 12.1 Update-notification would still appear again.
Later, I switched off Yuphoria to take out the External-SD-Card for data-transfer. Then when I switched on the Yuphoria, this Yu-Logo Boot-Loop Problem has started.
Now, My Yuphoria is Stuck at Yu-Logo on boot... and showing 'cannot mount partitions' errors when I boot custom-recovery twrp.
I have unlocked the bootloader.
From what I read online, I guess the memory partition-tables have got corrupted.... Now how can we solve this corrupted memory problem ?
I read about fastboot-flashing database.rfs or dbdata.rfs in some xda-developers Threads.
-----------------------------------------
I tried flash-all.bat with latest Cyanogen Official 12.1 ROM signed-fastboot.zip file... but still stuck at Yu-Logo on boot....
I fastboot boot trwp 2.6 custom-recovery.img and installed Cyanogen 12.1 ROM signed.zip file from external-sd card. But trwp says cannot mount partitions '/data', '/system', '/cache' etc...
---------------------------------------
I ran the command e2fsck /dev/block/bootdevice/by-name/system in terminal.
Then this message came : 'superblock has an invalid journal (inode 8) ext4'
I entered yes for correction multiple times and the process completed....
But still stuck at YU Logo on reboot.... Please Help.
-----------------------------------
I erased persist, then flashed persist.img.
Then I booted into twrp recovery, and adb sideload cm-12.1-YPG4PAS8A8-lettuce-signed.zip
The sideload started and then stopped with error : failed to unmount /cache ; failed to unmount /data ;
-----------------------------------
I boot into twrp 2.8.7.2 from fastboot-mode using command : sudo fastboot -i 0x2a96 boot twrp.img
Selected Wipe → advanced wipe → selected data :
It shows :
Mount Point : /data , File system : ext4 , Present: Yes, Removable: No, Size:0MB, Used: 0MB, Free 0MB, Backup Size: 0MB
Then I tapped on change/repair file system → change file system → EXT4 → Swiped IT...
Error : Format Failed.
E: Unknown MTP message type: 1
Failed to unmount '/data' (Invalid argument)
Error changing file system.
Updating Partition details.......
Failed to unmount '/system', '/data', '/cache' (Invalid arguments)
....done
Unable to mount storage.
After 'Change File System' Failed, I tried 'Repair File System' and 'Resize File System' also... all Failed similarly....
Only TWRP 2.8.7.2 and lower versions boots successfully in my Yuphoria.
TWRP 3.0.0 will not boot successfully. The TWRP logo will appear and then show command errors, and the phone will restart.
Please help me reinstall OS in my softbricked Yuphoria.
Goodison14 said:
I had got notification for the OTA Cyanogen 12.1 Update and I had updated it. But even after reboot, the same 12.1 Update-notification would still appear again.
Later, I switched off Yuphoria to take out the External-SD-Card for data-transfer. Then when I switched on the Yuphoria, this Yu-Logo Boot-Loop Problem has started.
Now, My Yuphoria is Stuck at Yu-Logo on boot... and showing 'cannot mount partitions' errors when I boot custom-recovery twrp.
I have unlocked the bootloader.
From what I read online, I guess the memory partition-tables have got corrupted.... Now how can we solve this corrupted memory problem ?
I read about fastboot-flashing database.rfs or dbdata.rfs in some xda-developers Threads.
-----------------------------------------
I tried flash-all.bat with latest Cyanogen Official 12.1 ROM signed-fastboot.zip file... but still stuck at Yu-Logo on boot....
I fastboot boot trwp 2.6 custom-recovery.img and installed Cyanogen 12.1 ROM signed.zip file from external-sd card. But trwp says cannot mount partitions '/data', '/system', '/cache' etc...
---------------------------------------
I ran the command e2fsck /dev/block/bootdevice/by-name/system in terminal.
Then this message came : 'superblock has an invalid journal (inode 8) ext4'
I entered yes for correction multiple times and the process completed....
But still stuck at YU Logo on reboot.... Please Help.
-----------------------------------
I erased persist, then flashed persist.img.
Then I booted into twrp recovery, and adb sideload cm-12.1-YPG4PAS8A8-lettuce-signed.zip
The sideload started and then stopped with error : failed to unmount /cache ; failed to unmount /data ;
-----------------------------------
I boot into twrp 2.8.7.2 from fastboot-mode using command : sudo fastboot -i 0x2a96 boot twrp.img
Selected Wipe → advanced wipe → selected data :
It shows :
Mount Point : /data , File system : ext4 , Present: Yes, Removable: No, Size:0MB, Used: 0MB, Free 0MB, Backup Size: 0MB
Then I tapped on change/repair file system → change file system → EXT4 → Swiped IT...
Error : Format Failed.
E: Unknown MTP message type: 1
Failed to unmount '/data' (Invalid argument)
Error changing file system.
Updating Partition details.......
Failed to unmount '/system', '/data', '/cache' (Invalid arguments)
....done
Unable to mount storage.
After 'Change File System' Failed, I tried 'Repair File System' and 'Resize File System' also... all Failed similarly....
Only TWRP 2.8.7.2 and lower versions boots successfully in my Yuphoria.
TWRP 3.0.0 will not boot successfully. The TWRP logo will appear and then show command errors, and the phone will restart.
Please help me reinstall OS in my softbricked Yuphoria.
Click to expand...
Click to collapse
Exact same problem for me... someone please help..
I too have been stuck up with the same problem, but in Yu Yureka...Brothers, Don't we really have a solution for this issue?!?!?...Please do something dear nerds lot of thanks!!
same prblm
anyone got solution for this ??
Exact problem.........
I ve gave it micromax service center, they asked 400 and began their work. after some time the man came out and sad, this is a board problem, you have to change the board. My friend is an embedded service engineer. He is saying its just a soft brick and the device is perfectly working. Those knowledgeless idiots dont want to find solution for this, the simply trying to change the board. Friends the problem we have is 100% a software issue, pls dont fall in their trap............
Same issue
Guys anyone got the solution ? Please help ...
Anybody got solutions, please respond
Same here
I tried everything but nothing seems to work. Someone help....
Seems to be Soft-Brick Software issue....
TWRP Recovery is not able to mount the /system , /cache and /data partitions...
but inside TWRP Recovery FileManager , we can open and browse all partiton files and system folders/files in /dev directory....
Also the TWRP Terminal shell can be used to run e2fsck and mke2fs commands...
So I think the /system, /cache and /data , and other corrupted android partitions like /misc can be repaired and mounted again, using the right steps and procedures....
Then I believe TWRP Recovery will mount partitons again and work, and we will be able to install/flash new ROM... Phone will boot into OS again...
We need Somebody with enough technical know-how to run Terminal Shell commands and repair corrupted android partitions.
Please if someone can help, would be greatful...
I used my Yuphoria for 10 months... now lying useless for one year...
---------- Post added at 11:42 AM ---------- Previous post was at 11:05 AM ----------
This XDA-Developers Thread has people trying and finding solutions to our problem.... Some even claim to have found the solution.
[Soft Brick] [Flash Stock] [Recovery] [ADB Driver] Yuphoria [Solution] by EssArr , 119 replies.
https://forum.xda-developers.com/yu-yuphoria/help/bricked-t3174710
Will try and find out a method there...
Got solved?
chattboyz said:
I ve gave it micromax service center, they asked 400 and began their work. after some time the man came out and sad, this is a board problem, you have to change the board. My friend is an embedded service engineer. He is saying its just a soft brick and the device is perfectly working. Those knowledgeless idiots dont want to find solution for this, the simply trying to change the board. Friends the problem we have is 100% a software issue, pls dont fall in their trap............
Click to expand...
Click to collapse
So did you get the soultion for it? If yes, what?
The post is of no help
Goodison14 said:
TWRP Recovery is not able to mount the /system , /cache and /data partitions...
but inside TWRP Recovery FileManager , we can open and browse all partiton files and system folders/files in /dev directory....
Also the TWRP Terminal shell can be used to run e2fsck and mke2fs commands...
So I think the /system, /cache and /data , and other corrupted android partitions like /misc can be repaired and mounted again, using the right steps and procedures....
Then I believe TWRP Recovery will mount partitons again and work, and we will be able to install/flash new ROM... Phone will boot into OS again...
We need Somebody with enough technical know-how to run Terminal Shell commands and repair corrupted android partitions.
Please if someone can help, would be greatful...
I used my Yuphoria for 10 months... now lying useless for one year...
---------- Post added at 11:42 AM ---------- Previous post was at 11:05 AM ----------
This XDA-Developers Thread has people trying and finding solutions to our problem.... Some even claim to have found the solution.
[Soft Brick] [Flash Stock] [Recovery] [ADB Driver] Yuphoria [Solution] by EssArr , 119 replies.
https://forum.xda-developers.com/yu-yuphoria/help/bricked-t3174710
Will try and find out a method there...
Click to expand...
Click to collapse
This is of no help as partitions are not getting mounted.
stuck at yu logo
i accidentially wiped my yu yurekas internal storage and got stucked at yu logo
i approched about 3 local service centers bt they said
it cannot be repaired because of failed to connect with their software box
and atlast i reched another localservice center come sales shop and they also advoced tge same bt understanding my sady situation the service boy at the shop asked me that "may i check it for further options if you allow to took the device as DEAD CONDITION for servicing bcz it may completely dead after this"
i agreed it
after a day he contacted me and said the problem has fix thank god
now its working fine
if any one want to know more details
such as about service centre
feel free to contact me through
[email protected]
thankyou:good:
Have anyone try to Flash stock rom?
nischait said:
Have anyone try to Flash stock rom?
Click to expand...
Click to collapse
Same problem here !!
Tried to flash the ROM with QFIL but the port is not detected by the software.
Also tried with fastboot.exe method still the same sometimes it says write failed for Size too large of system.img and if I change the default size limit (with -S option) it says "Error : Write failed"
degrader said:
Same problem here !!
Tried to flash the ROM with QFIL but the port is not detected by the software.
Also tried with fastboot.exe method still the same sometimes it says write failed for Size too large of system.img and if I change the default size limit (with -S option) it says "Error : Write failed"
Click to expand...
Click to collapse
Try annabathina method
nischait said:
Try annabathina method
Click to expand...
Click to collapse
Hi, can you share the link please?
degrader said:
Hi, can you share the link please?
Click to expand...
Click to collapse
Your device model please
Device is not getting detected
Hi,
I want to flash my Yuphoria. But, when i connect my device in Fastboot mode, my LAP (Windows 7 32 bit) is showing "Unknown USB". How to solve this issue??? please help me.
shashankdatta1218 said:
Hi,
I want to flash my Yuphoria. But, when i connect my device in Fastboot mode, my LAP (Windows 7 32 bit) is showing "Unknown USB". How to solve this issue??? please help me.
Click to expand...
Click to collapse
Install adb and fastboot drivers first
Hello community XDAdevelopers ,
I'm looking for help with my phone HTC ONE AT & T_ ( M7 ) , it stopped working and displays the following error:
E: missing bitmap oem_unlock_bg
(Code-1)
E: missing bitmap oem_unlock_bg_yes
(Code-1)
E: missing bitmap oem_unlock_bg_no
(Code-1)
Write host_mode success
handle_cota_install: Can't mount /sdcard, 1 times
handle_cota_install: Can't mount /sdcard, 2 times
handle_cota_install: Can't mount /sdcard, 3 times
handle_cota_install: Can't mount /sdcard, 4 times
handle_cota_install: Can't mount /sdcard, 5 times
I can managed through command line with BootLoader and unlock with the code that HTC sent me , however I can not load any ROM or RRU I downloaded
Descripcion:
***unlocked***
M7_UL PUT SHIP S-ON
HBOOT-1.61.0000
RADIO-4M.32.3218.06
OpenDSP-v35.120.274.0718
OS-7.23.502.1
eMMC-boot 2048MB
Mar 11 2015, 14:09:46.24069
Please if anyone can give me guidance on the subject, I so appreciate with that and if be a solution i can donating for the help. The phone will only work nine months
Hello and thank you for using XDA Assist,
please create an account and ask your question here:
AT&T HTC One (M7) Q&A, Help & Troubleshooting
The experts there will help you.
Kind regards
Trafalgar Square
XDA Assist
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.