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.
Related
Guys, I'm RETARDED. PLEASE HELP ME.
I was going to update to JesusFreke's RC30v1.3, but when booted up pressing HOME + END, I saw that for some reason, I didn't have the recovery image that uses the test keys while i did have the modded boot image (getprop ro.secure returned 0)
I tried following the guide here since I still had root from the adb shell, but when I tried to do it, I got stuck. When I tried to do the following line,
Code:
cat /data/local/recovery.img > recovery.img
I got this:
Code:
write: No space left on device
No problem, I thought. I'll just wipe the phone and then try it again!
It didn't work.
I then started experimenting with different things, even though I know I shouldn't have... and then I accidentally deleted my recovery.img file. ****.
As you may have surmised from the title of the post, I have root access from within the OS and from ADB and I also have the ADP1 bootloader on my phone. When I try going to the recovery menu, it just takes me to the bootloader (with the skateboarding 'droids). Also, I have installed manup's Bluestar 5 theme. I don't know since when my recovery image had reverted, but I know it was some time after I installed the ADP1 bootloader.
I've tried to do the stuff in the post mentioned above again, but it still gives me the damn
Code:
write: No space left on device
... I think it's mocking me.
The REALLY ironic part was that the first thing that I was going to do when I installed v1.3 was make a NANDroid backup.
Guys, PLEASE help me with this if you can. I know I was a retarded noob, but I'll learn from my mistakes. In the meantime, I can at least USE the phone... just with JF's RC30v1.2 and without Stericson's new theme (which I was gonna apply after backing up from NANDroid after installing RC30v1.3)
Thanks for your time,
~Ankush
The reason you are having write errors is JF has pushed the storage of /system partition to the limit. But flash_image can take any source location. Just put recovery.img in /data and then run
flash_image recovery /data/recovery.img
I saw that for some reason, I didn't have the recovery image that uses the test keys while i did have the modded boot image (getprop ro.secure returned 0)
Click to expand...
Click to collapse
This is a documented bug in v1.2. The new v1.3 recovery has a very distinct background image so there's no more ambiguity.
When I try that, I can boot into the Recovery menu, but when I try to apply the v1.3 update.zip, it fails at the "verifying update package" step and says:
Code:
E:Corrupt file:
data/recovery.img
E:Verification failed.
Installation aborted.
I redownloaded the recovery.img file and tried it again several times, but it didn't work either...
Thanks for the reply though.
~Ankush
P.S: HAPPY NEW YEAR! (at least in EST)
After you have done flash_image, rm recovery.img from /data. Also you might want to check your MD5 of update.zip
Yeah. I ended up downloading the 1.3 update again and then unzipping the recovery.img from that and applying it.
I saw the weird background along with the NANDroid 2.1 option so I applied the update.zip of the redownloaded JFv1.3 update.
I think that the main problem was the md5...
Oh well, it's all dandy now!
Thanks a BUNCH jashsu, have a happy new year!
Hi,
Last Friday I turned my phone off and when I turned it back on it got stuck on the loading screen and has been like that since.
I tried removing the battery loads, with no joy. I tried factory reset and clearing cache through the recovery menu, still nothing. So now I want to flash it but I'm having trouble.
I can't get the phone to boot so can't use adb to push a file to the sdcard and I'm stuck with fastboot commands (which I'm not that familiar with other than what I've found on here!). I downloaded the OTA update (from links found in these forums) for my phone to take it to 4.0.3 as I thought it was worth doing. I renamed it to update.zip but when I try the command "fastboot update update.zip" I get the message:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
I then tried the full ROM from this thread: http://forum.xda-developers.com/showthread.php?t=1063664
but got the same message.
I don't know what these missing files are, or if I can create them myself! I've found other threads where people said they used replacements found elsewhere but I don't know where to find them!!
I can't find a way to get the update file onto the sdcard so can't use that recovery option.
I'd rather not have to send it back to samsung as that takes two weeks and I'm pretty sure they'd just flash it anyway!
I have the Nexus S still with stock ROM (2.3.6) and unrooted.
Any help will be greatly appreciated!! Ideally I'd like a way to transfer the update file to the sdcard and recover using the phone recovery. Failing that, I'd like to flash it using fastboot.
cheers
First you need to download this : http://www.4shared.com/zip/2L09-JyW/Root_Nexus_S.html
Just unpack , connect your phone and click run.bat....
After that you need : remove install-recovery.sh just in .....
run in windows-> Start->at the search bar write cmd and navigate into your android sdk is installed
For me :
C:/"Programs and Files (x86)"/Android/android-sdk/tools/>adb shell
# rm /system/etc/install-recovery.sh
#exit
or with Root Explorer into system/etc/install-recovery.sh just renam it (ex. : .sh.old)
thanks for the reply.
What will this do exactly?
I thought adb commands only worked when the phone was booted up?
just had a look at the bat. So it seems this will wipe and root the phone adding superuser privelages?
Is this the only way I can get it working again and once I've done this, how do I undo it as to get the stock version of ICS do I not need to be unrooted or will flashing the stock version from the link in my OP automatically unroot the phone and replace the recovery image etc?
thanks again for your help - I'm a bit of a noob when it comes to rooting and ROMs!
Forgot to say, I have GT-i9020 model if it makes any difference.
Skyap said:
Forgot to say, I have GT-i9020 model if it makes any difference.
Click to expand...
Click to collapse
My tools will root your device and installed CWM ...after that you can do anything you want....
I'm now rooted and have cwm recovery. Had some issues transferring files to the sdcard but seem to have moved a couple of files, but when I try to update using them I get...
Finding update package...
Opening update package...
E:Can't open /sdcard/name-of-file.zip
(bad)
Installation aborted.
I get this whether its the full stock ROMs found on here or the update only packages found on here.
Any ideas?
Skyap said:
I'm now rooted and have cwm recovery. Had some issues transferring files to the sdcard but seem to have moved a couple of files, but when I try to update using them I get...
Finding update package...
Opening update package...
E:Can't open /sdcard/name-of-file.zip
(bad)
Installation aborted.
I get this whether its the full stock ROMs found on here or the update only packages found on here.
Any ideas?
Click to expand...
Click to collapse
Trying to mount sdcard into CWM and see what happens.
---------- Post added at 07:37 PM ---------- Previous post was at 07:34 PM ----------
Reboot into recovery.
Go into "mounts and storage"
Select "mount sdcard"
Select "mount USB storage"
Shortly after your SD Card will be mounted on your computer.
please help my sh-12c stuck in boot
hi my sh-12c stuck in boot wont open could you hrelp me to guide ?
i enable su and and i change permission in settings thats all in hope if morelocal2 works but it doesnt work and was not problem to use but , i restart in hope if it work , but it stuck in the boot logo Auuos moving any way to restore ?
Friends,
Having issues with flashing a custom rom to just rooted HTC One X 2.20 (ATT). First Android phone for me, got it a week ago, and first run at any and all of these issues (just switched from iPhone, but still doing all of this using a Macbook Air). Here's the spread:
Unlock went fine, no issues.
Installed TWRP, DID NOT INSTALL SUPERUSER.
Managed to choke and wipe OS (along with caches, sdcard). Fastboot and adb work. I have full access to TWRP, however I cannot mount /sd to computer (Mac simply notes, when mounting, that the device is unreadable).
I managed to push both the rom I was hoping to install (aokp_evita_jb_build-4.zip), and gapps to sdcard with ADB, however neither file would show in TWRP's file manager (I placed them in the root dir of the phone). I attempted to run the ROM via fastboot to no avail. I did push the boot.img as directed.
As I did not install SuperUser when I was supposed to, I attempted to install the superuser.apk with ADB after the fact, with the resulting error stopping me in my tracks: /sbin/sh: pm: not found. The only resolution to this issue I could find did not seem to apply to my situation.
Are the lack of permissions granted by SuperUser the reason the rom and gapp .zip files do not appear in TWRP file manager? Can/should I continue to attempt installing the superuser.apk file? After digging through all of these godawful help requests (mine included), can/should I attempt to lock the bootloader and flash RUU? What am I missing that is painfully obvious to those with real experience in this mess?
emp1re07 said:
Friends,
Having issues with flashing a custom rom to just rooted HTC One X 2.20 (ATT). First Android phone for me, got it a week ago, and first run at any and all of these issues (just switched from iPhone, but still doing all of this using a Macbook Air). Here's the spread:
Unlock went fine, no issues.
Installed TWRP, DID NOT INSTALL SUPERUSER.
Managed to choke and wipe OS (along with caches, sdcard). Fastboot and adb work. I have full access to TWRP, however I cannot mount /sd to computer (Mac simply notes, when mounting, that the device is unreadable).
I managed to push both the rom I was hoping to install (aokp_evita_jb_build-4.zip), and gapps to sdcard with ADB, however neither file would show in TWRP's file manager (I placed them in the root dir of the phone). I attempted to run the ROM via fastboot to no avail. I did push the boot.img as directed.
As I did not install SuperUser when I was supposed to, I attempted to install the superuser.apk with ADB after the fact, with the resulting error stopping me in my tracks: /sbin/sh: pm: not found. The only resolution to this issue I could find did not seem to apply to my situation.
Are the lack of permissions granted by SuperUser the reason the rom and gapp .zip files do not appear in TWRP file manager? Can/should I continue to attempt installing the superuser.apk file? After digging through all of these godawful help requests (mine included), can/should I attempt to lock the bootloader and flash RUU? What am I missing that is painfully obvious to those with real experience in this mess?
Click to expand...
Click to collapse
Check the settings in TWRP. You should have everything mounted as writeable. Root files may not show up otherwise.
iElvis said:
Check the settings in TWRP. You should have everything mounted as writeable. Root files may not show up otherwise.
Click to expand...
Click to collapse
TWRP Settings does not appear to contain an options relating to this: Zip file sig. verification/Force MD5 check/Use rm -rf/ Skip MD5 generation/Enable MD5 verification/Ignore image size errors/Simulate actions for theme testing
Tried to use ADB sideload to load the ROM, didn't work.
I've continued searching through threads to find a situation similar to mine, no luck.
EDIT: Rebooted a couple of time, retried pushing gapps-jb-20120726-signed.zip and the aokp rom mentioned above. They now appear under /sdcard
Tried to install both .zip files, and was met with a FAIL for the following reasons: E: Unable to mount '/sdcard' and E: Unable to mount storege
Hi. This is my first post and I hope I didn't have to post in some other section just for present myself, since I'm doing it now.
Anyway, I tried to flash a new rom since my HTC Sensation (no 4g nor XE) was totally stucked. I even installed the minimum software that I needed, and the result was a phone that could barely make calls.
So I did a backup of all my datas, then proceeded to a factory reset.
After that I followed the procedure on the htcdev website to unlock the bootloader and everything went smooth.
The first problem happened when, following a video explanation of a french guy that didn't say that I needed a wire, I had to improvise with what I could find at a late time in the night, and it was some iron wire insulated with some paper. At first the phone reeboted but not like I needed, and the following tries were totally useless so I used that software called rumrunner that claims to do be able to turn S-OFF without the wire trick.
I don't really know if it worked or not: I have S-OFF but during the process in the cmd there was "WTF: what are you doing" and "process stopped" even if I didn't touch anything.
Anyway, let's assume that I have S-OFF:
I then tried to flash the recovery 4-EXT using a software called like "Sensation_All-In-One_Kit_v3.1". I didn't noticed any significant change, nor the other functions were working properly since everything said "phone not found". So I used cmd and flashed "recovery-clockwork-touch-5.8.0.9-pyramid" and it worked flawlessy.
Then I rooted the phone using the recovery and installing from the sdcard the file "su-2.3.6.3-efgh-signed".
Then I downloaded cm12.1 by ivanich and installed it, but I forgot to do a backup before that and when I turned on the phone, nothing was loading. It was a black screen with the superior bar. The touch was not working, the on/off button the same. So I reopened the recovery, wiped out the data and cache to factory reset, and did again the SU and custom SO install.
Now the phone boots but it's again the factory reset version, not the one that I installed. I see that from all the bloatware still there. Also, its version is wrong. It's android 4.0.3, while there wasn't that version when it was produced.
I need help.
edit: I found out that when I try to install the rom I get only errors saying :
[the first part is missing since I can't scroll up]
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: no such file or directory
unmount of /system failed; no such volume
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: no such device
unmount of /data failed; no such volume
patching system image unconditionally...
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: no such file or directory
unmount of /system failed; no such volume
script succeded: result was [0.200000]
Install from sdcard complete.
FINAL EDIT:
I searched in many places for help. I found the man in a IRC chat. Seems that I had to change the recovery app and install twrp. Then it worked flawlessy.
Ciome said:
Hi. This is my first post and I hope I didn't have to post in some other section just for present myself, since I'm doing it now.
Anyway, I tried to flash a new rom since my HTC Sensation (no 4g nor XE) was totally stucked. I even installed the minimum software that I needed, and the result was a phone that could barely make calls.
So I did a backup of all my datas, then proceeded to a factory reset.
After that I followed the procedure on the htcdev website to unlock the bootloader and everything went smooth.
The first problem happened when, following a video explanation of a french guy that didn't say that I needed a wire, I had to improvise with what I could find at a late time in the night, and it was some iron wire insulated with some paper. At first the phone reeboted but not like I needed, and the following tries were totally useless so I used that software called rumrunner that claims to do be able to turn S-OFF without the wire trick.
I don't really know if it worked or not: I have S-OFF but during the process in the cmd there was "WTF: what are you doing" and "process stopped" even if I didn't touch anything.
Anyway, let's assume that I have S-OFF:
I then tried to flash the recovery 4-EXT using a software called like "Sensation_All-In-One_Kit_v3.1". I didn't noticed any significant change, nor the other functions were working properly since everything said "phone not found". So I used cmd and flashed "recovery-clockwork-touch-5.8.0.9-pyramid" and it worked flawlessy.
Then I rooted the phone using the recovery and installing from the sdcard the file "su-2.3.6.3-efgh-signed".
Then I downloaded cm12.1 by ivanich and installed it, but I forgot to do a backup before that and when I turned on the phone, nothing was loading. It was a black screen with the superior bar. The touch was not working, the on/off button the same. So I reopened the recovery, wiped out the data and cache to factory reset, and did again the SU and custom SO install.
Now the phone boots but it's again the factory reset version, not the one that I installed. I see that from all the bloatware still there. Also, its version is wrong. It's android 4.0.3, while there wasn't that version when it was produced.
I need help.
edit: I found out that when I try to install the rom I get only errors saying :
[the first part is missing since I can't scroll up]
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: no such file or directory
unmount of /system failed; no such volume
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: no such device
unmount of /data failed; no such volume
patching system image unconditionally...
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: no such file or directory
unmount of /system failed; no such volume
script succeded: result was [0.200000]
Install from sdcard complete.
FINAL EDIT:
I searched in many places for help. I found the man in a IRC chat. Seems that I had to change the recovery app and install twrp. Then it worked flawlessy.
Click to expand...
Click to collapse
you just had a very old version of recovery
i assume that guy gave you the proper twrp because there is a false one which messes up with emmc after using wipe option
rzr86 said:
you just had a very old version of recovery
i assume that guy gave you the proper twrp because there is a false one which messes up with emmc after using wipe option
Click to expand...
Click to collapse
No he just told me to get the last version for my phone.
Ciome said:
No he just told me to get the last version for my phone.
Click to expand...
Click to collapse
actually i am saying the same thing
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.