Database Info

[Q] Superuser/SDcard Issues

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

HTC Sensation: Can't install zip from SD card & WiFi "Error" stopped working.

HTC Sensation: Can't install zip from SD card & WiFi "Error" stopped working.
Hello
I recently rooted my HTC Sensation (Pyramid) Z710e using KINGORoot and it was a successful root, unlocked bootlader and got SuperUser.
Security is still on (S-ON) as I don't need or wish to turn this off.
I have tried using CWM recovery 5.8.0.9 but flashing the ROM which was MADE for the Pyramid failed, then I tried using TWRP 2.1.0 but I got the same result, and then I also tried CWM recovery 5.0.2.0 but still the same result (error below).
The problem: When I try flashing a new custom ROM after doing data wipe, cache wipe and dalvik cache wipe it gives me the following error message:
' E: Error in /sdcard/'zipname'.zip
(Status 0 )
Installation Aborted. '
All recoveries downloaded were specific to my phone (obvoiusly) so all were named with Pyramid in them (ex. "twrp-pyramid-2.1.0.img") and so were the custom ROMs, specific to the sensation.
I read something about changing the META-INF File from the new ROM zip to a working META-INF file for the Pyramid but when I tried this it didn't work either, got me an error Status 1 message if I remember correctly.
I'm currently running a downloaded zip of ICS (Ice Cream Sandwich) Android 4.0.3 which is like the OS I had before I formatted everything except SD Card. However my WiFi isn't working anymore since I flashed this downloaded ICS zip and what I mean by not working I mean that when you flip the switch to turn WiFi on it flips to On and then to Off again immediately, and in the settings menu it says there's an Error, but that's it. I tried using the Wifix manager app with the code but that didn't work at all.
Any help is greatly appreciated as to what I can do regarding why I can't install a zip successfully from recovery or as to how I can fix my WiFi problem on my Sensation.
Thanks

Hello
Please wait for the moderation team to move this thread to relevant section.
Do register an account on xda for better access and privileges.
Have a good day !

Flash the boot.img of the rom via fastboot command
The command is fastboot flash boot boot.img
And I suggest to use 4ext recovery since you are on S-ON

Still not working :/
Thank you for the reply
Ok I did what you said, I'm currently trying to get the new latest version of CM12 - Lollipop for my sensation.
And yes I'm using 4ext recovery aswell.
I flashed the boot.img file in my phone and it was a success, however after wiping cache, davlik, and data and formatting all partitions except sd card I go to flash the CM12 ROM but it's giving me a status 0 error again.
Am I missing something?
Here is the log of when I try installing the CM12 zip
"
Installing: /sdcard/cm-12-20150203-UNOFFICIAL-pyramid.zip
Finding update package...
I:Update location: /sdcard/cm-12-20150203-UNOFFICIAL-pyramid.zip
Opening update package...
Installing update...
Warning: No file_contextsminzip: Extracted 3 file(s)
about to run program [/tmp/install/bin/backuptool.sh] with 2 args
grep: /system/build.prop: No such file or directory
Not backing up files from incompatible version: 12
run_program: child exited with status 127
about to run program [/tmp/install/bin/otasigcheck.sh] with 1 args
about to run program [/tmp/install/bin/backuptool.sh] with 2 args
grep: /system/build.prop: No such file or directory
Not backing up files from incompatible version: 12
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/system, assuming ext4
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
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/userdata, assuming ext4
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: No such file or directory
unmount of /data failed; no such volume
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/system, assuming ext4
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: No such file or directory
E:Error in /sdcard/cm-12-20150203-UNOFFICIAL-pyramid.zip
(Status 0)
Installation aborted.
"
Thanks

Spitfire98 said:
Thank you for the reply
Ok I did what you said, I'm currently trying to get the new latest version of CM12 - Lollipop for my sensation.
And yes I'm using 4ext recovery aswell.
I flashed the boot.img file in my phone and it was a success, however after wiping cache, davlik, and data and formatting all partitions except sd card I go to flash the CM12 ROM but it's giving me a status 0 error again.
Am I missing something?
Here is the log of when I try installing the CM12 zip
"
Installing: /sdcard/cm-12-20150203-UNOFFICIAL-pyramid.zip
Finding update package...
I:Update location: /sdcard/cm-12-20150203-UNOFFICIAL-pyramid.zip
Opening update package...
Installing update...
Warning: No file_contextsminzip: Extracted 3 file(s)
about to run program [/tmp/install/bin/backuptool.sh] with 2 args
grep: /system/build.prop: No such file or directory
Not backing up files from incompatible version: 12
run_program: child exited with status 127
about to run program [/tmp/install/bin/otasigcheck.sh] with 1 args
about to run program [/tmp/install/bin/backuptool.sh] with 2 args
grep: /system/build.prop: No such file or directory
Not backing up files from incompatible version: 12
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/system, assuming ext4
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
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/userdata, assuming ext4
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata at /data: No such file or directory
unmount of /data failed; no such volume
could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/system, assuming ext4
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: No such file or directory
E:Error in /sdcard/cm-12-20150203-UNOFFICIAL-pyramid.zip
(Status 0)
Installation aborted.
"
Thanks
Click to expand...
Click to collapse
did you flash the latest version of 4ext recovery?
if not take it from here
http://d-h.st/rG7
extract the recovery.img and flash it via fastboot command

Spitfire98 said:
Thank you for the reply
Ok I did what you said, I'm currently trying to get the new latest version of CM12 - Lollipop for my sensation.
And yes I'm using 4ext recovery aswell.
[]
E:Error in /sdcard/cm-12-20150203-UNOFFICIAL-pyramid.zip
(Status 0)
Installation aborted.
Click to expand...
Click to collapse
1.) Make sure you have at least 4ext recovery v1.0.0.6 RC2 in order to install new ROMs. Otherwise you will very likely get a status 0 error with most ROMs.
2.) I suggest to use CM11 as a daily driver, Lollipop so far has not been stable enough on the Sensation, I had different kinds of problems. Still seems to be a bit experimental to me.

WiFi + ROM (status 0) ~ Problem SOLVED!
Okay, first of all, a huge thanks to everyone that replied and took the time to help me with my problem!
The WiFi problem occurred because I had the incorrect ROM Build name even though it was like the old untampered Ice Cream Sandwich (my stock O.T.A.update ICS was 3.32.x and the one I had downloaded and flashed myself was a stock ICS to bring back my phone's old OS but it was 3.33.x).
The problem of the status 0 error was that at first I was forgetting to flash the Boot.img file in the phone, but then it was because I had version 1.0.0.5 of 4ext recovery not 1.0.0.6 (the latest) as you guys suggested. I can't believe it was that simple but it's solved atleast now and I am infact currently running the latest CM12 Lollipop on my Sensation which looks amazing but since its still unofficial it has a few small bugs.
Once again Thanks all
Happy Devving!

adb sideload does not finish

I was following this tutorial wiki.lineageos.org/devices/walleye/install and I am stuck with sideloading Lineage
I run `adb sideload lineage-17.1-20201013-nightly-walleye-signed.zip` while phone shows "Starting ADB sideload feature" then comes "Installing zip file '/sideload/package.zip'" and then I can see the progress bar below moving, but nothing more, no percentage or more textes or whatever. And it does that now for multiple hours.
Before when I tried it, it stopped completely and the progress bar was frozen.
So I guess something is not working here?! I use Lineage from here, 20201013 download.lineageos.org/walleye

I even cannot push the zip to /sdcard
$ adb push lineage-17.1-20201013-nightly-walleye-signed.zip /sdcard
adb: error: failed to copy 'lineage-17.1-20201013-nightly-walleye-signed.zip' to '/sdcard/lineage-17.1-20201013-nightly-walleye-signed.zip': no response: Success
Click to expand...
Click to collapse

Maybe you can use twrp

armuttaqin said:
Maybe you can use twrp
Click to expand...
Click to collapse
In a way Iam using TWRP, like in the tutorial. So I start the adb sideloading within twrp, how else could i use it? So how can I put the zip onto the phone to use twrp install?

and when I did the format data wipe, I got the errors
failed to mount '/system' (invalid argument)
failed to mount '/vendor' (invalid argument)
Click to expand...
Click to collapse

ok I managed to install from OTG usb I again got the error about /vendor, and also "warning no OS installed" before I rebooted, but then I booted into LOS and it seems to work now....

Hi, just wondering if you have any specifics regarding the steps you followed for OTG USB install? I'm new here and I seem to be having a very similar issue with a newer version of the walleye build

Seriously could use help flashing custom ROM to Oneplus 8t (Tmo-variant) I am at my wit's end

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.

Question Help ASUS Rog 5 Phone (Tencent Edition)

Hey all,
I am really hoping someone will be able to help me out here.
So I made such a rookie mistake, I ended up flashing boot to TWRP instead of recovery, but after alot of trail and tribulation I managed to get the boot.img out of the latest ROG 5 payload.bin.
My issue is when I adb push the zip file, TWRP runs into issues and I can't seem to get the stock firmware on, it gives me the following 5 errors:
Failed to mount '/system_root' (Block device required)
Failed to mount '/product' (Block device required)
Failed to mount '/vendor' (Block device required)
Failed to mount '/odm' (Block device required)
Failed to mount '/system_ext' (Block device required)
What step am I missing? I have searched and searched but couldn't find any answers, I really would like to get my phone up and running again (without the random shut downs before I screwed it up).
Yes I do have it rooted, I also have the whole payload.bin extracted (all the img files in a folder).
Any and all help would be great.