Related
UnBrick Guide
This is a little guide How to unbrick A100
this will only work if the fastboot is unlocked
you shouldn't be use it on a locked bootloader, or an official acer rom, otherwise you be locked out by the bootloader
1. download this tools and extrackt -night.nerdcamp.net
2. get into fastboot power of device then power on hand hold down Volume Down when the first screen appears push the screen lock below are 2 pictures
3.in fastboot connect usb and run the first script this will copy the recovery (A100 TWRP recovery (TeamWin Recovery Project) 2.1.1+)
4. boot recovery connect usb on win pc it will install a driver MTP-USB if don´t install automatically download the driver for a100 from Acer an install an point at the directory
5. copy a rom in the tools directory zb CM9 and run the 2. script this will copy all files from tools to the internal flash on the tap you can install this rom an reboot an ready to fly
THX TO
TeamWin Recovery
pio_masaki for Flashing Toolkit
and all other XDA Dev´s
Here's a little video www.youtube.com/watch?v=7U35BT7WemU
NighPlayer32 said:
UnBrick Guide
This is a little guide How to unbrick A100
this will only work if the fastboot is unlocked
1. download this tools and extrackt http://www.multiupload.nl/L8ZV0PTJ4U
2. get into fastboot power of device then power on hand hold down Volume Down when the first screen appears push the screen lock below are 2 pictures
3.in fastboot connect usb and run the first script this will copy the recovery (A100 TWRP recovery (TeamWin Recovery Project) 2.1.1+)
4. boot recovery connect usb on win pc it will install a driver MTP-USB if don´t install automatically download the driver for a100 from Acer an install an point at the directory
5. copy a rom in the tools directory zb CM9 and run the 2. script this will copy all files from tools to the internal flash an on the tap you can install this rom an reboot an ready to fly
THX TO TeamWin Recovery
pio_masaki for Flashing Toolkit
and all other XDA Dev´s
Click to expand...
Click to collapse
Looks promising thanks for putting this up! I look forward to seeing if this successfully works on the various types of bricks.
Edit: Not sure what's up with your links or hosting, but yeah...doesn't work, just ads, then redirect to ....another ad. No download.
Edit2: Ok I've tried 6 times, no download, and I should mention links like this are frowned upon by XDA Mods, so you may want to switch to a host that doesn't require going through steps to get to the download, like dev-host. Looks like now I can't go past unless I sign up for something, which I may or may not agree with, which is kind of forcing users. Or I'm blind and not seeing it, always an option too lol
Tapatalked from my Galaxy S II.
I will upload it on my FTP wenn it´s done I´ll post it here
NighPlayer32 said:
multiupload.nl/L8ZV0PTJ4U
I will upload it on my FTP wenn it´s done I´ll post it here
Click to expand...
Click to collapse
Np just thought I'd report what was happening. I can mirror on my dev-host as well if you'd like.
Tapatalked from my Galaxy S II.
pio_masaki said:
Np just thought I'd report what was happening. I can mirror on my dev-host as well if you'd like.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
yes you can do this
In my case it does not serve for anything. Because as it does not recognize me the tablet by any means. The usb does not even sound when I connect it .... it is a pity, tomorrow a messenger comes to take her to him to the SAT. but thanks for the work
I have a photo of the current condition of the tablet, but they do not stop me to place external links...
I made a little video maybe this helps
asi se encuentra mi tablet. h t tp ://w w w .youtube.com/watch?v=G-TDTX-wvy4&feature=youtu.be
ok I tried it but it fails .. is there anyway to unbrick it if its in locked mode?
but this defiantly got me farther then any other thing
bigcgt0127 said:
ok I tried it but it fails .. is there anyway to unbrick it if its in locked mode?
but this defiantly got me farther then any other thing
Click to expand...
Click to collapse
This won't get any farther then any other current method on a locked boot loader. This is for those having issues with recovery not responding so a rom install isn't possible.
What kind of brick do you have? There's a few kinds now.
Tapatalked from my Galaxy S II.
I don't know what type it is if I had to guess I would call it a complete brick but fastboot works (locked mode) and it sometimes will work with adb (also in locked mode)
The last step...
-- Install /sdcard/cm9-7-9-B29-a100-PM.zip ...
E:failed to mount /data (No such file or directory)
E:Can't mount /sdcard/cm9-7-9-B29-a100-PM.zip
E:failed to mount /data (No such file or directory)
Error flashing zip '/sdcard/cm9-7-9-B29-a100-PM.zip'
Click to expand...
Click to collapse
So close... but failed
NighPlayer32 said:
UnBrick Guide
This is a little guide How to unbrick A100
this will only work if the fastboot is unlocked
you shouldn't be use it on a locked bootloader, or an official acer rom, otherwise you be locked out by the bootloader
1. download this tools and extrackt -multiupload -night.dyndns.org
2. get into fastboot power of device then power on hand hold down Volume Down when the first screen appears push the screen lock below are 2 pictures
3.in fastboot connect usb and run the first script this will copy the recovery (A100 TWRP recovery (TeamWin Recovery Project) 2.1.1+)
4. boot recovery connect usb on win pc it will install a driver MTP-USB if don´t install automatically download the driver for a100 from Acer an install an point at the directory
5. copy a rom in the tools directory zb CM9 and run the 2. script this will copy all files from tools to the internal flash on the tap you can install this rom an reboot an ready to fly
THX TO
TeamWin Recovery
pio_masaki for Flashing Toolkit
and all other XDA Dev´s
Here's a little video http://youtu.be/WDF45vTwrD0
Click to expand...
Click to collapse
I keep getting a md5 file is missing. seams like it is a great tool. please help
max69power said:
I keep getting a md5 file is missing. seams like it is a great tool. please help
Click to expand...
Click to collapse
Turn off the md5 checking in recovery.
Tapatalked from my A100 - Kuroikaze Personal V2
I keep getting a md5 file missing. i had just installed the rom manager and started a ti backup. when i woke up the tablet was frozen when i reset it it just went to black now i cant get back i finally got it to fast boot and installed this app but it keeps failing when i try to install it says. it is unlocked and rooted but that is all i had done.
E: failed to mount /data (no such file or directory)
E: unable to mount /data/media during gui startup
E: can't open /dev/block/mmcblkop5
(no such file or directory)
E: failed to mount /cache/recovery/comand
* verfying filesystems...
* verifying partition sizes...
E: unable to mount /system
E: unable to mount /data
E: unable to mount /cache
E: unable to mount /sdc
E: unable to stat '/flexrom/.'
running boot script...
finished running boot script.
E: failed to mount /data (No such file or directory)
E: failed to mount /data (No such file or directory)
E: unable to mount /data
E: failed to mount /data (No such file or directory)
E: failed to mount /cache (No such file or directory)
E: can't mount /cache/recovery/log
E: can't open /cache/recovery/log
E: failed to mount /cache (No such file or directory)
E: failed to mount /data (No such file or directory)
E: failed to mount /sdc (No such file or directory)
E: failed to mount /data (No such file or directory)
E: failed to mount /data (No such file or directory)
E: failed to mount /sdc (No such file or directory)
E: failed to mount /data (No such file or directory)
E: failed to mount /data (No such file or directory)
E: failed to mount /data (No such file or directory)
E: failed to mount /data (No such file or directory)
E: failed to mount /data (No such file or directory)
-- verfying md5 for /sdcard/cm-9-7-9-b29-a100-pm.zip
-- no md5 file found, ingoring
-- Install /sdcard/cm9-7-7-b29-a100-pm.zip ...
E: failed to mount /data (no such file or directory)
Can't mount /sdcard/cm9-7-9-b29-a100-pm.zip
E: failed to mount /data (no such or directory)
error flashing zip '/sdcard/cm9-7-9-b29-a100-pm.zip'
E: failed to mount /data (no such file or directory)
E: failed to mount /data (no such file or directory)
That md5 error is normal, and isn't causing the install to fail, its the pretty much brick status your device is in that's causing that. Basically all those errors are saying you have no partitions on your device, so it can't do anything until that's corrected.
any idea where to start or how to get it back so i can return under waranty
max69power said:
any idea where to start or how to get it back so i can return under waranty
Click to expand...
Click to collapse
Get it back how? Acer knows of the problem so just use the warranty.
Edit: sorry just realized what you meant. Sorry but no in its bricked state you can't restore it back to normal. You could try to fast boot the stock recovery and adb the stock boot loader, but it may or may not work. Doing any if the Modding voids the warranty anyways.
Tapatalked from my Galaxy S II.
i ment to remove the recovery and the unlocker
What's the command for flashing the stock bootloader blob file?
Sent from my HTC Evo 4G using XDA app
I had an older custom ROM and CWM 6.0.10 and I wanted to update to a newer 4.4 ROM (Omni) so I booted into recovery and proceeded to do a factory reset along with a format of /sdcard and /system. Now when I reboot, I enter recovery automatically.
I managed to push the ROM .zip to the phone using "adb push ROM.zip /sdcard/ROM.zip". The problem is that when I try to install from zip (withing CWM) the install fails with this message:
SymlinkingApplyParsedPerms: removexattr of /system/addon.d/50-hosts.sh to 0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
set_metadata_recursive: some changes failed
E:Error in /sdcard/omni-4.4.4-20140825-maguro-FML.zip
(Status 7)
Installation aborted
I'm stuck here and I'm guessing that I shouldn't have formatted /sdcard and /system as the directory "/0" that the error message refers to isn't on /sdcard anymore (it used to be). Not sure what to do at this point.
I've tried flashing TWRP, but fastboot waits forever with a "<waiting for device>". I thought TWRP might let me sideload the ROM (I was thinking that this manner of installing might create some default partitions on the SD card, as needed.
I welcome any suggestions. BTW, this is all on a Galaxy Nexus GSM
Adrian
hello,
does someone know what problem i have and how i should fix this?
first of all, when i was wiping my phone it all went fine but it took to long so i turned off my phone and turned it back on, i got in an boot loop and couldnt even get into recovery mode because that would also led me into a ''teamwin'' bootloop, anyway i reflashed my recovery so luckily i can get back into recovery, but i still have bootloop for the system so i cant start up, but now i also face this problem.
i wanted to flash stock rom and this is the full error log i get ( i also tryed with custom rom but same problem)
_____________________________________________________________________________________________
E: could not mount /data and unable to find crypto footer.
E: unable to mount /data
E: unable to recreate /data/media folder.
updating partition details...
E: unable to mount /data
... done
E: unable to mount storage.
E: unable to mount /data/media during GUI startup
Full SELinux support is present.
E: unable to mount /data/media/twrp. twrps when trying to read settings file.
E:unable to mount /data
MTP enabled
E: unable to mount /data
E: unable to mount /data
E: unable to mount /data
Installing external_sd/UL-Z00A-WW-2.20.40.174-user.zip ...
Checking for MD5 file...
Skipping MD5 check: no MD5 File found
Device image SKU:
OTA image SKU: WW
assert failed: getprop ("ro.build.asus.sku") == ''WW''
E: Error executing updater binary in zip '/external_sd_UL-Z00A-WW-2.20.40.174-user.zip'
Error flashing zip '/external_sd_UL-Z00A-WW-2.20.40.174-user.zip'
Updating Partition Details...
E:unable to mount /data
... done
E: unable to mount storage.
Failed
----------------------------------------------------------------------------------------------------------------------------------------------------------------
I also tryed wiping my phone, i tryed advanced wipe and full wipe and also factory reset, but i always get this same kinda error.
anyone know a fix for this?
Which version of twrp do you use?
i use Twrp 2.8.7.3
Try the last one : https://dl.twrp.me/Z00A/twrp-3.0.0-0-Z00A.img.html
Your zenfone 2 is WW or CN?
its CN
sorry for the kinda late answer tho,
well i wanted to flash the 3.0 twrp version, but it gives me an weird kind of bootloop, so thats why i downgraded to 2.8.7 :/
that's strange, are you sure it was for Z00A?
Look at this : http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596 to change to WW version.
Hi,
Nice to be here after so much years of reading !
My LG G3s (d722) was fine with Cyanogenmod 13 and encryption enabled. I've made a Titanium backup for my apps (& cie...) on the SD card, and reboot in TWRP 3.0.2-0, enter my password to mount storage, and I've wiped all partitions exept the SD card.
Then I've flashed the CM14 zip file, and get these error in the process :
"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: Unkown error 200 unmount of /data failed; no such volume"
"Failed to mount '/data' (No such device)"
Since then :
- if I reboot into recovery, TWRP doesn't ask me the password to decryp the partition
- if I reboot in CyanogenMod ask me the password, but the tells me :
Decryption unsuccessful
The password you entered is correct but unfortunately your data is corrupt.
To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google Account.Then it reboot into TWRP
Any ideas ?
How could I mount ext4 partition in TWRP ? Or restore stock recovery ?
Thanks a lot for your advices
resolving !
Hi myself and everyone from another time,
I've resolved this mess by :
- installing LG drivers
- downloading kitkat stock-rom D72210d_00.kdz
- open LG Flash Tool 2014 and load D72210d_00.kdz, and start a CSE Flash
Then stard android 4, root it... etc
Best
I bought a used OnePlus 7T Pro (256GB). I followed these instructions: https://wiki.lineageos.org/devices/hotdog/install
Unlocking the bootloader worked without problems. To install a recovery, I had to replace "recovery" in the command with "boot_b", but then it worked fine. The copy partitions script also seems to have succeeded. But then I can't install LineageOS and many other recovery features do not work, either, both in the LineageOS recovery and in TWRP.
When I start TWRP (and set my usual vibration, brightness etc. settings), I get the log output from the attached image. I wanted to copy it, but writing the log to /data/media fails because of this issue, too, so here it is hand-transcribed, hopefully correctly:
Failed to mount '/system_root' (Block device required)
Failed to mount '/vendor' (Block device required)
E:Unable to open /system_root/system/apex
E:Unable to load apex images from /system_root/system/apex
Updating partition details...
Failed to mount '/system_root' (Block device required)
Failed to mount '/system_ext' (Block device required)
Failed to mount '/product' (Block device required)
Failed to mount '/vendor' (Block device required)
Failed to mount '/odm' (Block device required)
...done
Unable to mount storage
Failed to mount '/system_root' (Block device required)
E:Unable to open /system_root
Full SELinux support is present.
Unable to mount /data/media/TWRP/.twrps
Unable to mount /data/media/TWRP/.twrps
Failed to mount '/system_root' (Block device required)
Many things I try in both recoveries fail with similar mounting errors. I tried everything wipe related, but none of it helped, most didn't even work. I also cannot install LineageOS from TWRP (instead of ADB sideload), because no files are listed on the internal SD card, likely because of this mounting issue.
How can I fix this? Since the phone is new anyway, I would be willing to reset anything.
Fabian R�ling said:
I bought a used OnePlus 7T Pro (256GB). I followed these instructions: https://wiki.lineageos.org/devices/hotdog/install
Unlocking the bootloader worked without problems. To install a recovery, I had to replace "recovery" in the command with "boot_b", but then it worked fine. The copy partitions script also seems to have succeeded. But then I can't install LineageOS and many other recovery features do not work, either, both in the LineageOS recovery and in TWRP.
When I start TWRP (and set my usual vibration, brightness etc. settings), I get the log output from the attached image. I wanted to copy it, but writing the log to /data/media fails because of this issue, too, so here it is hand-transcribed, hopefully correctly:
Failed to mount '/system_root' (Block device required)
Failed to mount '/vendor' (Block device required)
E:Unable to open /system_root/system/apex
E:Unable to load apex images from /system_root/system/apex
Updating partition details...
Failed to mount '/system_root' (Block device required)
Failed to mount '/system_ext' (Block device required)
Failed to mount '/product' (Block device required)
Failed to mount '/vendor' (Block device required)
Failed to mount '/odm' (Block device required)
...done
Unable to mount storage
Failed to mount '/system_root' (Block device required)
E:Unable to open /system_root
Full SELinux support is present.
Unable to mount /data/media/TWRP/.twrps
Unable to mount /data/media/TWRP/.twrps
Failed to mount '/system_root' (Block device required)
Many things I try in both recoveries fail with similar mounting errors. I tried everything wipe related, but none of it helped, most didn't even work. I also cannot install LineageOS from TWRP (instead of ADB sideload), because no files are listed on the internal SD card, likely because of this mounting issue.
How can I fix this? Since the phone is new anyway, I would be willing to reset anything.
Click to expand...
Click to collapse
It seems to me that you have to flash the super partition, try first using TWRP and if it can't deal with then try through fast boot.
SubwayChamp said:
It seems to me that you have to flash the super partition, try first using TWRP and if it can't deal with then try through fast boot.
Click to expand...
Click to collapse
I have never heard of a "super partition". How do I do that?
Fabian R�ling said:
I have never heard of a "super partition". How do I do that?
Click to expand...
Click to collapse
Sometimes can be an error from TWRP itself, an older version that can't manage to mount those partitions, but sometimes it happens that the super partition is corrupted, you could find it from your stock ROM and then extracted and flash it either through TWRP or using fastboot.
SubwayChamp said:
Sometimes can be an error from TWRP itself, an older version that can't manage to mount those partitions, but sometimes it happens that the super partition is corrupted, you could find it from your stock ROM and then extracted and flash it either through TWRP or using fastboot.
Click to expand...
Click to collapse
Do you have a link to a tutorial or so for that?
BTW, the preinstalled operating system boots just fine, so I would be surprised if any partitions were corrupted. I'm also using the latest version of TWRP, at least it's the one that I got on their website yesterday.
Fabian R�ling said:
Do you have a link to a tutorial or so for that?
BTW, the preinstalled operating system boots just fine, so I would be surprised if any partitions were corrupted. I'm also using the latest version of TWRP, at least it's the one that I got on their website yesterday.
Click to expand...
Click to collapse
Super partition is where some logical partitions are grouped like system, vendor, odm, product, etc.; it depends on the device we're talking about.
As you got a used device, it seems that the last owner did some stuff with it, probably unlocked bootloader (then relocked it) and mess with some custom ROMs (maybe). You can totally fix it by flashing the stock ROM and starting from there, being sure first that you can log in without issues in Google Play (that your account is authorized).
To have this partition readable, you may read this https://forum.xda-developers.com/t/...-mount-system-rw-super-rw-read-write.4247311/ in case this doesn't solve flashing the super partition it is a part of the process to flash the stock ROM.
SubwayChamp said:
flashing the super partition it is a part of the process to flash the stock ROM
Click to expand...
Click to collapse
You mean it's in some script in that zip file? Because what I found online just tells me to do the same "adb sideload" with the OxygenOS zip. And that doesn't work because of the same access issue. Or is there something else I should do first?
The link you gave says that it requires a rooted ROM, which I don't have yet.
Fabian R�ling said:
You mean it's in some script in that zip file? Because what I found online just tells me to do the same "adb sideload" with the OxygenOS zip. And that doesn't work because of the same access issue. Or is there something else I should do first?
The link you gave says that it requires a rooted ROM, which I don't have yet.
Click to expand...
Click to collapse
You can update through the stock recovery in case your TWRP have actually some issues, flash the stock recovery through fastboot (get it from your stock ROM) and then do the sideload through stock recovery, it's probable that the stock recovery can mount super partition and made readable again the system files that´s within, or you can simply flash this or that partition using fastboot commands, for this you need an unlocked bootloader, nothing more.
BTW did you try formatting data?.
And this tool should work for you https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4217855/
That tool says it only works for Windows. I have gotten rid of my last Windows system last year.
Not sure what you mean with getting the stock recovery from the stock ROM, since the zip only contains "payload.bin" (extension suggests binary file, no idea how to read that one), a small txt file and a small "META-INF", but here is a download at least: https://forum.xda-developers.com/t/oos-all-stock-boot-stock-recovery-oxygenos-11-0-0.4251221
There's even a Magisk version, which I'll try first, since I want that anyway. But for now, I'll sleep. I'll comment again once I've tried it.
BTW, can I stop this website from jumping to the category overview after a few seconds, while I'm trying to just read a post? It's really annoying.
Fabian R�ling said:
That tool says it only works for Windows. I have gotten rid of my last Windows system last year.
Not sure what you mean with getting the stock recovery from the stock ROM, since the zip only contains "payload.bin" (extension suggests binary file, no idea how to read that one), a small txt file and a small "META-INF", but here is a download at least: https://forum.xda-developers.com/t/oos-all-stock-boot-stock-recovery-oxygenos-11-0-0.4251221
There's even a Magisk version, which I'll try first, since I want that anyway. But for now, I'll sleep. I'll comment again once I've tried it.
BTW, can I stop this website from jumping to the category overview after a few seconds, while I'm trying to just read a post? It's really annoying.
Click to expand...
Click to collapse
The ROM to be flashed through recovery contains a payload.bin file within others one, this file can be unpacked, not sure if it contains a recovery image though, but you should get it from the full ROM that in some variant comes in oplus format and can be decrypted too, this full ROM contains all the images, it's useful to unbrick a OP device.
Linux doesn't have a counterpart of the Windows applications for smartphones and vice versa in regard to Android development, this is one of the reasons why I have a dual boot machine.
As per the last part it could be an issue from your browser, I didn't have this kind of behaviors from the XDA site.
For "boot.img" and "recovery.img" in the "EU" and the "global" section I get "fastboot: error: boot partition is smaller than boot image". The Magisk version can be installed, but then I get a Qualcomm crash screen when I try to actually start it.
Apparently I have a "OnePlus 7 Pro", not a "OnePlus 7T Pro". I bought that accidentally, but the specs are fine. Actually following the instructions for the correct device worked, who would have thought…