Hi guys
I decided to try and and unlock and root my phone as soon as I got it. But somewhere along the line things didn't go to plan, and I've got a phone with TWRP (3.0.2-b-b10) on it, and that's about it (stupidly I didn't do a back up as I'd not set anything up on the phone yet). I can still put it into Factory Test Mode, and run 'adb reboot edl' to put into a place where I can communicate with it using tenfar's tool.
First time out, everything seemed to go fine, but when I booted up the phone after running through the process, the wifi wasn't working. This meant I couldn't get through the first stage of phone set up (select language, then wifi, nothing I tried would get me beyond that, as I guess a phone without wifi isn't much use).
So I went back into wiped a few things, tried tenfar's tool again with no luck; wifi still no working. I followed the steps on here, but the ADB commands failed.
Code:
C:\Users\Stephen\AppData\Local\Android\sdk\platform-tools>adb shell dd if=/dev/z
ero of=/dev/block/bootdevice/by-name/modemst1 bs=16384
dd: /dev/block/bootdevice/by-name/modemst1: Permission denied
After some more messing, I wiped the OS (yeah, idiotic). Anyway, so I download Draken's boot and stock from another post, but when trying to flash them via TWRP, they failed. I downloaded them on mac, and copied them to a exFAT SD card. It complains about failed to mount /firmware and no MD5 file found, then I get:
Code:
Could not find 'META-INF/com/google/android/update-binary' in the zip file
And it finishes. Same with the stock file. So now I'm in the process of downloading the B20.zip from here in the hope there is something in there I can flash to get the OS back on the phone. any other suggestions?
Thanks in advance,
Sok
Had the same issue with rooting using Tenfar's tool. I used TWRP to flash a fresh B10 and start over. Send a PM if you need/want help.
Now I'm following the instructions here, and I keep getting the error:
Code:
Failed to mount '/firmware' (Invalid argument)
Then it tells me that the B20 zip file from Draken is corrupt.
Related
I tried to follow this thread: http://forum.xda-developers.com/showthread.php?t=1356257
But I am getting the errors: adb: not found -or- adb permission is denied. how can I solve this? I have the original framework-res.apk. However, I screwed up with the one on my kindle and now it is bricked at the logo screen.
HELP?
i was having the same problem - where i was going wrong was not remounting the kindle device via adb
once i ran adb remount i was able to get the file back in place.
Sorry, but I really can't mount ADB Remount.
No adb commands will work for me. I either get:
-exec '/system/bin/sh' failed; No such file or directory (2)
-or-
adb: permission denied
-or-
the other error listed above.
My question; can someone walk me through step by step what to do if I bricked by messing up the framework-res.apk? Please?
Do you have TWRP? Did you take a backup first? You shouldn't be messing with system files that are required for booting without doing this first. The procedure for recovering should just be booting into TWRP and restoring your backup. Backups backups backups.
If you don't have a backup, but do have TWRP, does adb work in TWRP so you could try it there? (I'm at work so I can't double check that)
If none of these work, you might be able to get the system to boot into fastboot and get TWRP on there, Vashypooh or one of the TWRP guys would be more helpful than I would be for that. The only other option is a factory cable (there's at least one thread on here for that).
Tl;dr - 1) download zip from asus 2) download tethered recovery 3) copy the zip to the sd card 4) run tethered recovery utility 5) install via twrp/cwm menus
I am creating this thread to document my experience with a failed update and being stuck in a brick state with the seemingly random but present permission denied error when trying to fastboot flash. Most of this is not new, but rather a collection of existing resources with a focus on a specific, uncommon issue(s)
Tomorrow I will edit this message with links to the threads and posts which got me going again today. This is currently a workaround to restore the system, the bootloader is still falling.
Recommended reading:
-ansebivi's wonderful ota flash guide - links all the major files, lays out all the theory
-the official tethered recovery thread, my missing link
-thebugruss's permission denied thread, alludes to the magic system recovery properties of tethered recovery and had some great information
- all the other xda and Google hits that reference these errors
I had been putting off the .137 ota update for a while and finally decided to let in download and install. My z551 was not rooted and had a locked boot loader. the update failed and re booted back into .97 without issues for a few minutes before turning off. When I rebooted, I was stuck in the wonderful boot loop. Reading through the boot loop recovery section of the ota thread, I start top down and found my fastboot would not properly install anything. Error permission denied. Then I tried the adb sideload which failed with a cannot read error on the pc. Finally I went to try the install via zip in the external storage, but recovery would not start. Instead the ZenFone either fell back to fast boot our started at the powered by Android screen. Many posts referenced wiping the cache via fast boot, ask permission denied fire me. Having seen some success discussion with vampirefo tethered recovery, I was able to at least get back to recovery and poke around adb shell. Adb shell here had no root privileges and could not even read /sdcard, but at least usage-wise my /data looked whole, /system was empty and /recovery did not look right. Adb sideload failed in this recovery, wiping the caches here did nothing, the install from zip menu options did not work. Encouraged by the process, I found the latest stock tethered recovery utility updated back in July and trying twrp instead of cwm I was finally able to get install from zip working. Side load did not work under twrp, but gave a different error than stock and cwm
I never wiped /data and had a found all my settings and and data intact. Fastboot still gives permission denieddenied errors, but that will have to be fixed another day.
From all my reading, there doesn't seem to be a common reason for permission debuted in fast boot (threads exist of rooted, un rooted, never rooted, locked and unlocked bootloader). At least one post indicated a result of the ww fastboot on a cn or tw device. For most, permission denied still allows for some writing. My current guess is that each subsequent attempt and failure corrupted system and recovery
Next steps:
Perform a property nand backup in twrp
Check if my fast boot matches my phone sku
Fix fastboot (preferably without unlocking the bootloader, but definitely i will need to root to investigate
-f
permission denied
fg said:
Tl;dr - 1) download zip from asus 2) download tethered recovery 3) copy the zip to the sd card 4) run tethered recovery utility 5) install via twrp/cwm menus
I am creating this thread to document my experience with a failed update and being stuck in a brick state with the seemingly random but present permission denied error when trying to fastboot flash. Most of this is not new, but rather a collection of existing resources with a focus on a specific, uncommon issue(s)
Tomorrow I will edit this message with links to the threads and posts which got me going again today. This is currently a workaround to restore the system, the bootloader is still falling.
Recommended reading:
-ansebivi's wonderful ota flash guide - links all the major files, lays out all the theory
-the official tethered recovery thread, my missing link
-thebugruss's permission denied thread, alludes to the magic system recovery properties of tethered recovery and had some great information
- all the other xda and Google hits that reference these errors
I had been putting off the .137 ota update for a while and finally decided to let in download and install. My z551 was not rooted and had a locked boot loader. the update failed and re booted back into .97 without issues for a few minutes before turning off. When I rebooted, I was stuck in the wonderful boot loop. Reading through the boot loop recovery section of the ota thread, I start top down and found my fastboot would not properly install anything. Error permission denied. Then I tried the adb sideload which failed with a cannot read error on the pc. Finally I went to try the install via zip in the external storage, but recovery would not start. Instead the ZenFone either fell back to fast boot our started at the powered by Android screen. Many posts referenced wiping the cache via fast boot, ask permission denied fire me. Having seen some success discussion with vampirefo tethered recovery, I was able to at least get back to recovery and poke around adb shell. Adb shell here had no root privileges and could not even read /sdcard, but at least usage-wise my /data looked whole, /system was empty and /recovery did not look right. Adb sideload failed in this recovery, wiping the caches here did nothing, the install from zip menu options did not work. Encouraged by the process, I found the latest stock tethered recovery utility updated back in July and trying twrp instead of cwm I was finally able to get install from zip working. Side load did not work under twrp, but gave a different error than stock and cwm
I never wiped /data and had a found all my settings and and data intact. Fastboot still gives permission denieddenied errors, but that will have to be fixed another day.
From all my reading, there doesn't seem to be a common reason for permission debuted in fast boot (threads exist of rooted, un rooted, never rooted, locked and unlocked bootloader). At least one post indicated a result of the ww fastboot on a cn or tw device. For most, permission denied still allows for some writing. My current guess is that each subsequent attempt and failure corrupted system and recovery
Next steps:
Perform a property nand backup in twrp
Check if my fast boot matches my phone sku
Fix fastboot (preferably without unlocking the bootloader, but definitely i will need to root to investigate
-f
Click to expand...
Click to collapse
Asus Memo Pad 8 181c... I got tablet with WW-3.1.23.150 & have done consecutive updates through a thread on XDA (tablet would not update) starting with a full firmware flash using CWM Tethered recovery of the .172, & flashing two OTA's offered on same thread of .183 & .189. I eventually got a link for an Asus download through Asus Memo Pad G+ community to get the .191. Trying to do a system.img & boot.img pull I get the permission denied part just trying to do a ls -al /dev/block/platform/dw_mmc/by-name is getting me "Permision Denied", just trying to get mount points!
Does this mean I have something corrupted?
zach
Did you have a lock screen password enabled before you got bricked?
That would prevent any flashing. You have to somehow disable that.
Sent from my ASUS_Z00AD using XDA Premium HD app
Can't flash via TWRP, "failed mount system", twrp sideload not working either.. stuck
I need my phone for work tomorrow so any help would be greatly appreciated.
I'm on TWRP 3.2.3-1 and was using the latest stock oreo rom from here: https://forum.xda-developers.com/g5...o-twrp-flashable-stock-builds-coming-t3830482
My phone suddenly didn't have a reception today, after rebooting I regained reception but couldn't make calls. I rebooted to recovery and tried to dirty flash the same stock twrp flashable oreo rom that I was using and it failed. Apparently the OS got corrupted. I tried repeatedly to flash the ROM and then noticed I was getting an error : failed to mount system , invalid argument. I couldn't mount system via the Mount tab in TWRP and I couldn't find anything helpful to resolve this error.
I did some more research downloaded the fastboot flashable ROM from here : https://forum.xda-developers.com/g5-plus/how-to/moto-g5-plus-fastboot-flash-stock-oreo-t3848433 and tried to flash the rom via adb using adb sideload in twrp but twrp doesn't seem to load that function correctly. In the elevated command prompt in the adb directory I type adb sideload filename.zip and it just freezes up my PC. My device does show up with the adb devices command and shows " *Serial Number* RECOVERY ".
I don't understand what to do with the instructions in the fastboot flash stock thread I posted above and I'm at the limit of my knowledge. No idea how to proceed... any help is greatly appreciated.
I tried extracting the xml.zip into the adb folder and rebooted to bootloader/AP Fastboot Flash Mode and was going to try the commands in the fastboot Rom thread but my device only shows up in adb devices when I load twrp. uhhhhgggghhhhhh guess I'll have to buy a backup phone tomorrow while I try to get this one working
Holy hell.... I didn't realize since I was in the fastboot/bootloader I had to use "fastboot devices" command to see the device. Tried that and saw the device listed, so I created a .bat file using the commands in the fastboot roms thread above and I have a functional device again. Whohoooooo!
Did you try to format /System/ as EXT4?
Hello, i am in dire need of help. I bought the new g7, flashed TWRP to recovery, installed Magisk Manager, and was happy for a bit. Long story short, a security update for my phone was released, pop ups saying "Update Failed" were getting annoying, so I naively decided it was a good idea to uninstall magisk, install the update, and reinstall magisk. Easy right? NOPE. I think Magisk messed up my partitions somehow. My phone is soft bricked, bootloops, endlessly. I can get into bootloader settings, (power + volume down), but nothing works. I can't boot into factory mode, i can't boot into TWRP. The phone shows up in fastboot, but I can't flash TWRP to recovery, it says "recovery partition not found". I am very lost, and my pictures of my Europe vacation are stuck on there. Are there any options for restoring my phone, or at least salvaging my files? Thanks in advance..
Hi There.
Maybe you can try this in order to boot into TWRP:
Code:
fastboot boot twrp-xxx.img
FoxShadow said:
Hi There.
Maybe you can try this in order to boot into TWRP:
Code:
fastboot boot twrp-xxx.img
Click to expand...
Click to collapse
Thank you for your time. I pushed TWRP to my phone, it booted fine, but I can't find my backups. My sdcard directory is filled with random folders with gibberish names, I don't know if it's encrypted or what. I had a TWRP backup in my internal storage, but as i said i can't find it. I thought maybe if i reinstalled Magisk, the bootloop would stop and i wouldn't lose information. I downloaded the .zip file to my PC, but ADB won't push to internal storage.
Terminal input (while phone is in TWRP): >adb push C:\Users\[me]\Downloads\Magisk-v19.3.zip
Output: --adb: usage: push requires an argument.
Any ideas on how to get my system back without losing my files?
gunnergilson said:
Thank you for your time. I pushed TWRP to my phone, it booted fine, but I can't find my backups. My sdcard directory is filled with random folders with gibberish names, I don't know if it's encrypted or what. I had a TWRP backup in my internal storage, but as i said i can't find it. I thought maybe if i reinstalled Magisk, the bootloop would stop and i wouldn't lose information. I downloaded the .zip file to my PC, but ADB won't push to internal storage.
Terminal input (while phone is in TWRP): >adb push C:\Users\[me]\Downloads\Magisk-v19.3.zip
Output: --adb: usage: push requires an argument.
Any ideas on how to get my system back without losing my files?
Click to expand...
Click to collapse
Dont worry. We can fix this.
No. The adb command is wrong.
Code:
adb push C:\Users\[me]\Downloads\Magisk-v19.3.zip /data/
/data is the folder in the phone where you would like to copy the Magisk file
I will make it easy for you.
Step 1. Download MagiskUninstaller from
https://github.com/topjohnwu/Magisk/releases/download/v19.3/Magisk-uninstaller-20190604.zip and save it in PC and Open a terminal/cmd in the download folder
Step 2. Boot into TWRP using
Code:
fastboot boot twrp-xxx.img
Step 3. Go to Advanced
Step 4. Press AdbSideload
Step 5. in the terminal/cmd opened in the step 1 enter
Code:
adb sideload MagiskUninstallerxxx.zip
Step 6. It will began to flash the uninstaller and Hopefully your phone will be saved.:good:
Thank you for the input, however this didn't work.
I tried sideloading the uninstaller. Here's the log:
-current boot slot: _b
-Mounting system
-Mounting vendor
-Device is system-as-root
-Device platform: arm64
!Cannot access /data, please uninstall with magisk manager
-Unmounting partitions
Updater process ended with ERROR: 1
Any other ideas? I can put files on my micro sd card, and TWRP can see that. I did that to flash the uninstaller the second time, when sideload didn't work. No luck still. I also tried installing Magisk.zip again, but still there is a bootloop. I had a full system backup made by TWRP, in my internal storage. If I could flash that, maybe it would fix the problem, but I can't seem to even find internal storage. Thanks for all the help, and I hope we can figure this out.
gunnergilson said:
Thank you for the input, however this didn't work.
I tried sideloading the uninstaller. Here's the log:
-current boot slot: _b
-Mounting system
-Mounting vendor
-Device is system-as-root
-Device platform: arm64
!Cannot access /data, please uninstall with magisk manager
-Unmounting partitions
Updater process ended with ERROR: 1
Any other ideas? I can put files on my micro sd card, and TWRP can see that. I did that to flash the uninstaller the second time, when sideload didn't work. No luck still. I also tried installing Magisk.zip again, but still there is a bootloop. I had a full system backup made by TWRP, in my internal storage. If I could flash that, maybe it would fix the problem, but I can't seem to even find internal storage. Thanks for all the help, and I hope we can figure this out.
Click to expand...
Click to collapse
You cannot find your data or you can only find gibberish filenames is because you are booting from the TWRP image. try to flash TWRP and then reboot to recovery. Then you could see the files that weren't accessible earlier.
Reference Link : https://forum.xda-developers.com/moto-g7/how-to/moto-g7-twrp-root-t3914112
Hi,
I have an international 6t and trying to install Lineage 18.1. After the following steps, I get the qualcomm crash dump error:
- Use MSM to install: ANDROID+10+OOS+10.3.2+fajita_41_J.44_200222
- System Update to latest version of OOS: 11.1.2.2
- Unlock bootloader (tried via both ADB and TOOL ALL IN ONE)
- Flash: twrp-installer-3.6.0_9-0-fajita (tried via both ADB and TOOL ALL IN ONE)
- Qualcomm crash dump error
Am I doing anything wrong? I have looked at different guides and seems to be the right steps.
I also tried using MSM to install an older (9) ROM and didn't uprade. Found here that I could get TWRP working... However, after flashing Lineage Rom I got stuck in fastboot loop.
Some hours later...
OK, so I just tried it again, following this guidance exactly (and with Lineage Recover rather than TWRP) : https://lineageosroms.com/fajita/
Without TWRP I didn't have the crash dump error... but when I came to finally Reboot the System, I got another error:
Can't load Android System. Your data may be corrupt......
Then with this text at the bottom:
E: Failed to bind mount /mnt/stagin/emulated/0 to /storage/emulated: No such file or diretory
E Emulated failed to bind mount /mnt/stagin/emulated/0 to /storage/emulated: No such file or diretory
Any help very much appreciated!
benh77 said:
Hi,
I have an international 6t and trying to install Lineage 18.1. After the following steps, I get the qualcomm crash dump error:
- Use MSM to install: ANDROID+10+OOS+10.3.2+fajita_41_J.44_200222
- System Update to latest version of OOS: 11.1.2.2
- Unlock bootloader (tried via both ADB and TOOL ALL IN ONE)
- Flash: twrp-installer-3.6.0_9-0-fajita (tried via both ADB and TOOL ALL IN ONE)
- Qualcomm crash dump error
Am I doing anything wrong? I have looked at different guides and seems to be the right steps.
I also tried using MSM to install an older (9) ROM and didn't uprade. Found here that I could get TWRP working... However, after flashing Lineage Rom I got stuck in fastboot loop.
Some hours later...
OK, so I just tried it again, following this guidance exactly (and with Lineage Recover rather than TWRP) : https://lineageosroms.com/fajita/
Without TWRP I didn't have the crash dump error... but when I came to finally Reboot the System, I got another error:
Can't load Android System. Your data may be corrupt......
Then with this text at the bottom:
E: Failed to bind mount /mnt/stagin/emulated/0 to /storage/emulated: No such file or diretory
E Emulated failed to bind mount /mnt/stagin/emulated/0 to /storage/emulated: No such file or diretory
Any help very much appreciated!
Click to expand...
Click to collapse
You should have already know by now that TWRP version is not compatible with OOS11.
You can try to restore your Phone with MSM tool and try again with this version [file attached]
Thanks
s.seila said:
You should have already know by now that TWRP version is not compatible with OOS11.
You can try to restore your Phone with MSM tool and try again with this version [file attached]
Click to expand...
Click to collapse
Thanks, I just tried with this... although with TWRP I am unable to switch on ADB Sideload. It just times out forever.
With Lineage Recovery instead of TWRP I could use ADB, although got other errors as in initial message.
benh77 said:
Thanks
Thanks, I just tried with this... although with TWRP I am unable to switch on ADB Sideload. It just times out forever.
With Lineage Recovery instead of TWRP I could use ADB, although got other errors as in initial message.
Click to expand...
Click to collapse
I thought sideload worked on that twrp. But you can try booting that twrp then install lineage recovery or another version of twrp from twrp.
Thanks, I think there is an underlying issue with my phone or I am just out of my depth. Pretty much followed every set of instructions I can find and always results in a bricking, bootloop or qualcomm crash dump. Was a second hand phone, so just got it back to 11.1.2.2 and will re-sell.
Got my trusted Z5 Compact onto 17.1 and that will do me for a few years yet!