{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Project Open Cannibal presents...
Cannibal Open Touch v2.1 for Samsung Nexus S 4G
About Cannibal Open Touch:
Cannibal Open Touch is the next generation of custom recoveries. Jam-packed with cool and useful features, it can handle just about anything you can throw at it.
Main Features:
1. Support for both Edify and Amend scripting (flash all ROMS!)
2. Theme support
3. Touch screen button controls!
4. GooManager support!
5. Internal e2fsprogs for size
6. Backported “retouch binaries” patch for ICS/JB compatibility
7. Advanced Backup
8. Delete old backups!
9. Persistent settings
10. User-defined backup locations!
11. ADB Sideload
12. Touchscreen calibration
Why the name Cannibal Open Touch?
Because we can. The name also embodies everything that Cannibal Open Touch is. It is no longer just a variant of ClockworkMod Recovery, it is it's own recovery by itself. Combining features from ClockworkMod 5, Team UtterChaos' Sony Xperia recovery, AmonRa 3.0.6, Xionia CWMA and a heaping helping of our own special enhancements it is truly revolutionary.
What to do when an error occurs:
DO NOT simply say "xxxx doesn't work" as that is highly unhelpful and will probably be ignored. Instead, post the recovery log! To grab a log when an error occurs, simply open a terminal (or command prompt if on Windows), "cd" to an easily accessible directory and execute:
Code:
adb pull /tmp/recovery.log
Paste the log as an attachment (don't paste the text inside, as it can be quite lengthy), or paste it on pastebin.com.
WARNING!
If you are upgrading from a previous version of Cannibal Open Touch you must delete the settings.ini file located in the cotrecovery folder on your sdcard!
Flashing instructions:
1. Download the Cannibal Open Touch recovery image.
2. Reboot your device to bootloader mode (adb reboot bootloader)
3. Flash the image with fastboot (fastboot flash recovery /path/to/recovery.img)
4. Reboot to recovery mode
5. PROFIT!
Main Recovery Screenshots
Main Gallery (external link)
Available Themes:
Themes Gallery (external link)
Download Cannibal Open Touch v2.1:
Note: The below link is an external link to the Project Open Cannibal forums. We do not require registration to download any public release, but we'd sure appreciate it if you stopped by to say hello
WARNING!
This has only been tested on the NS4G models (crespo4g); while it is hightly probable this will work on the Nexus S (crespo) we cannot confirm this at this time (at best I would expect assert errors with rom zips).
Cannibal Open Touch Download
Awesome, the Blood Red theme looks 3D kinda, or maybe... . Have gone through some of the basic's, dalvik cache, flashing zips (kernels), fixing permissions, mounting USB mass storage, mounting/un-mounting other partitions, haven't played around with any of the features you'd use to flash a new ROM (at least flashing them the right way) or the NANDROID features, although there is a settings menu for the actual Cannibal Recovery which include some things you might want to change depending on which recovery you were using before switching and for the prompts (no no no yes no no). It also includes calibrate touchscreen which you want to do first thing, use the volume rockers to get to the the calibration then you can use the software buttons on the bottom with precision. For some reason when you go to partition management though, you click on it, then the screen flashes and your back where you just were, then when you click on partition management again it actually goes into the menu. Another thing is that the settings are not persistent, hopefully I'm just missing something. It's really not that big of a deal, just remembering to do it....I really like this recovery
Seems interesting, might try it later tonight...
Sent from my ns4g using Tapatalk 2
Will this work for the GSM Nexus S?
Sent from my Nexus S using Tapatalk 2
Sblood86 said:
WARNING!
This has only been tested on the NS4G models (crespo4g); while it is hightly probable this will work on the Nexus S (crespo) we cannot confirm this at this time (at best I would expect assert errors with rom zips).
Click to expand...
Click to collapse
I've never seen a recovery that worked for both gsm & cdma nexus s. So, my bet is no.
Sent from my ns4g using Tapatalk 2
p1gp3n said:
I've never seen a recovery that worked for both gsm & cdma nexus s. So, my bet is no.
Sent from my ns4g using Tapatalk 2
Click to expand...
Click to collapse
I will give this a try. Its not like it could brick my phone is something.
Sent from my Nexus S using Tapatalk 2
sgtkid12 said:
I will give this a try. Its not like it could brick my phone is something.
Sent from my Nexus S using Tapatalk 2
Click to expand...
Click to collapse
Make sure you have a recovery img file to flash back. Their website specifically states this is ONLY for ns4g
Sent from my ns4g using Tapatalk 2
p1gp3n said:
Make sure you have a recovery img file to flash back. Their website specifically states this is ONLY for ns4g
Sent from my ns4g using Tapatalk 2
Click to expand...
Click to collapse
I do. I'll test here in a bit.
Sent from my Nexus S using Tapatalk 2
"Unable to mount SDCard"
Sent from my ns4g using Tapatalk 2
p1gp3n said:
"Unable to mount SDCard"
Sent from my ns4g using Tapatalk 2
Click to expand...
Click to collapse
Try booting to android and then back to recovery. I had that the first time I flashed it in too.
Sent from my Nexus S 4G using Tapatalk 2
hlxanthus said:
Try booting to android and then back to recovery. I had that the first time I flashed it in too.
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
Just tried this 4 times, still no dice
Sent from my ns4g using Tapatalk 2
Are any of you getting persistence across reboots? I'll change all the COT Settings just to have to re-change them after rebooting out of the recovery. Can the recovery partition even have persistence?
And here's the pastbin for the bug's I listed in my first post (second post of the thread).
recovery.log pastbin
vinnypel2ella said:
Are any of you getting persistence across reboots? I'll change all the COT Settings just to have to re-change them after rebooting out of the recovery. Can the recovery partition even have persistence?
And here's the pastbin for the bug's I listed in my first post (second post of the thread).
recovery.log pastbin
Click to expand...
Click to collapse
The settings aren't saved in the recovery partition, but as a file in the COT folder in your "SD" partition. If they're not sticking, report with a log (how to pull it is in the OP) and SBlood and Drew will work on fixing it.
The colors thing was a known issue, might have re-emerged.
vinnypel2ella said:
Are any of you getting persistence across reboots? I'll change all the COT Settings just to have to re-change them after rebooting out of the recovery. Can the recovery partition even have persistence?
And here's the pastbin for the bug's I listed in my first post (second post of the thread).
recovery.log pastbin
Click to expand...
Click to collapse
I would try using a file manager to delete the /sdcard/cotrecovery/setting.INI
Then try rebooting.
Sent from my Nexus S 4G using Tapatalk 2
p1gp3n said:
Just tried this 4 times, still no dice
Sent from my ns4g using Tapatalk 2
Click to expand...
Click to collapse
boot into android, connect phone to computer, obviously make sure USB debugging is enabled, put the Cannibal recovery .img you downloaded from the first post in your platform-tools folder on your PC (or where ever your adb/fastboot files are located) and just to make is easy rename the file "recovery" (obviously without quotes, I'm going off of no knowledge of your...technical ability). open a command prompt in your platform-tools folder from the android sdk (or again, where ever your adb/fastboot files are located, where you just put recovery.img) by holding shift and left clicking inside the file explorer window where your adb shizz is and then click "Open command prompt here".
This will be in line by line format what you must enter into the command prompt with // being used for comments about what the command is doing (do not type those):
//to see if your device is being recognized by adb and get the server running type
adb devices
//you should see a little table with a device ID underneath the "device" column, this is good. if you dont, you need to install you phones ADB drivers or put it in adb debugging mode
//If your phone was recognized, then type
adb reboot bootloader
//Your phone should reboot into the booloader, and this is where things might get difficult
//Were in the process of fastboot flashing this recovery, so to see if your phone is recognized as being in fastboot mode (in the bootloader) type
fastboot devices
//as with the command adb devices, you should see your phone listed (the device ID)
//If all this clears out then your ready to flash the recovery
//To fastboot flash a recovery you want to type
fastboot flash recovery recovery.img
//I will explain the syntax so you know whats going on, but at this point it should of gave you some sort of feedback that the device was flashed or the image/file was transferred and now just use your volume rocker keys on the phone to click recovery from the bootloader menu and you should now see your shiny new recovery
As for the syntax of the fastboot command, I'll break it down string by string (word by word):
fastboot
.EXE application from the Android SDK that is run in the command prompt for interfacing with the devices bootloader.
flash
Busybox command used to, for lack of a better term, flash partitions on the device.
recovery
By typing "recovery" after the busybox "flash' command, the recovery partition is selected as the partition to run the command on.
recovery.img
Location of image file that we want to flash. We did not have to type in a full path to the file because our command prompt was open in the directory the file "recovery.img" is located. I believe the issue you guys are having (the limited post's I saw in this thread so far) is that you are trying to flash the recovery from your /sdcard and if the /sdcard is not mounted, or is mounted as read only then you will receive an error. Also, if you are trying to use your computers command prompt and ADB interface to flash the recovery, but have the .img file saved lets say, to your android-sdk folder instead of the actual platform-tools folder. Whenever your referencing a path in the command prompt, if there is a space between any of the file/folder names the whole path has to be inside quotes.
Example:
fastboot flash recovery C:\Program Files(x86)\Android\android-sdk\recovery.img
This would return an error saying it cannot find the path "C:\Program
The correct syntax would be:
fastboot flash recovery "C:\Program Files(x86)\Android\android-sdk\recovery.img"
Any other questions, feel free to PM me or just post em up on here. I really like this recovery so I'll be checking back often for updates
Apparently I failed to subscribe to/bookmark this thread; my apologies, this has been corrected and I will be keeping a closer eye on peoples issues, sorry again.
Can u make one with touch blocks like twrp and multiple boot options so u can switch ROMs instantaneously?
Thanks for the great post, vinnypel2ella.
I followed your steps and successfully loaded the Open Cannibal recovery on my phone. I did have an unexpected occurrence during one of the steps, so I thought I'd share:
++ Everything went as expected through the step below.
//If your phone was recognized, then type
adb reboot bootloader
++ Once my phone was at the bootloader, Windows popped up the 'Found New Hardware' wizard. I canceled it, and tried to proceed with your steps, but was unable to go any further until (from my phone) I rebooted back into the bootloader and allowed the Found New Hardware wizard to do its thing and install a few files. After that, the remaining steps went fine and COT is now installed.
The below issue re: COT Recovery not mounting my SD Card may be a non-issue after all. I booted back into recovery one last time and, while the message was still displayed, after moving around and trying out a few different menus/options (viewing the log, calibrating the touchscreen, fixing permissions) it seems as though COT was able to mount my SD Card at some point during my 'visit'. I was then able to successfully create a Nandroid backup.
I wanted to post my recovery.log file in case anyone was interested, but the 'adb pull /tmp/recovery.log' command returned the following error:
++ remote object '/tmp/recovery.log' does not exist
I thought this was a bit strange since I was able to view the log when in COT Recovery. Did I do something wrong in the above command?
Thanks,
sleepy
[ON HOLD]
I do, however, have the same problem as p1gp3n in that the recovery says it is unable to mount my SD Card. It said this on the initial boot to recovery, and after booting into Android and then back into recovery several times. I have tried deleting the settings.ini file when in Android and then booting into recovery but it did not help. I will pull a log file and submit to the COT team. Do you (or anyone else) have any ideas in the meantime?
[/ON HOLD
sleepyEDB said:
Thanks for the great post, vinnypel2ella.
I followed your steps and successfully loaded the Open Cannibal recovery on my phone. I did have an unexpected occurrence during one of the steps, so I thought I'd share:
++ Everything went as expected through the step below.
//If your phone was recognized, then type
adb reboot bootloader
++ Once my phone was at the bootloader, Windows popped up the 'Found New Hardware' wizard. I canceled it, and tried to proceed with your steps, but was unable to go any further until (from my phone) I rebooted back into the bootloader and allowed the Found New Hardware wizard to do its thing and install a few files. After that, the remaining steps went fine and COT is now installed.
The below issue re: COT Recovery not mounting my SD Card may be a non-issue after all. I booted back into recovery one last time and, while the message was still displayed, after moving around and trying out a few different menus/options (viewing the log, calibrating the touchscreen, fixing permissions) it seems as though COT was able to mount my SD Card at some point during my 'visit'. I was then able to successfully create a Nandroid backup.
I wanted to post my recovery.log file in case anyone was interested, but the 'adb pull /tmp/recovery.log' command returned the following error:
++ remote object '/tmp/recovery.log' does not exist
I thought this was a bit strange since I was able to view the log when in COT Recovery. Did I do something wrong in the above command?
Thanks,
sleepy
[ON HOLD]
I do, however, have the same problem as p1gp3n in that the recovery says it is unable to mount my SD Card. It said this on the initial boot to recovery, and after booting into Android and then back into recovery several times. I have tried deleting the settings.ini file when in Android and then booting into recovery but it did not help. I will pull a log file and submit to the COT team. Do you (or anyone else) have any ideas in the meantime?
[/ON HOLD
Click to expand...
Click to collapse
The logs will only be present in tmp when you are in recovery; I seem to recall them being lost on reboot.
You can export the recovery log to you sdcard from the recovery menu : COT Options -> Recovery Debugging -> Report Error (will copy the log to sdcard/cotrecovery/
Definitely some weirdness going on there though, let us know when you have that log.
Sblood86 said:
The logs will only be present in tmp when you are in recovery; I seem to recall them being lost on reboot.
You can export the recovery log to you sdcard from the recovery menu : COT Options -> Recovery Debugging -> Report Error (will copy the log to sdcard/cotrecovery/
Definitely some weirdness going on there though, let us know when you have that log.
Click to expand...
Click to collapse
Thanks for the reply, and the tip re: the recovery.log. I've got a copy and it's posted below. Again, sorry for not being able to use pastebin:
Code:
Starting recovery on Wed Feb 6 17:24:07 2013
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /sdcard vfat /dev/block/platform/s3c-sdhci.0/by-name/media (null) 0
2 /system ext4 /dev/block/platform/s3c-sdhci.0/by-name/system (null) 0
3 /cache yaffs2 cache (null) 0
4 /data ext4 /dev/block/platform/s3c-sdhci.0/by-name/userdata (null) 0
5 /misc mtd misc (null) 0
6 /boot mtd boot (null) 0
7 /recovery mtd recovery (null) 0
8 /bootloader mtd bootloader (null) 0
9 /radio mtd radio (null) 0
10 /wimax mtd wimax (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
W:failed to mount /dev/block/platform/s3c-sdhci.0/by-name/media (No such file or directory)
Unable to mount sdcard,
loading failsafe setting...
Settings will not work
without an sdcard...
W:failed to mount /dev/block/platform/s3c-sdhci.0/by-name/media (No such file or directory)
I:Language code: en
I:Theme loaded!
I:Loading hydro resources...
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (480 x 800)
I:Processing arguments.
mtd: successfully wrote block at 0
I:Set boot command "boot-recovery"
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.boot.serialno= <Deleted by me. Not sure if this should be posted online.>
ro.boot.bootloader=D720SPRKE1
ro.boot.baseband=D720SPRLF2
ro.boot.info=0x4,0x4,1
ro.boot.carrier=SPR
ro.serialno=<Deleted by me. Not sure if this should be posted online.>
ro.bootmode=unknown
ro.baseband=D720SPRLF2
ro.bootloader=D720SPRKE1
ro.hardware=herring
ro.revision=34
ro.emmc=0
ro.boot.emmc=0
ro.factorytest=0
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.sys.usb.config=adb
ro.build.id=JRO03L
ro.build.display.id=full_crespo4g-eng 4.1.1 JRO03L eng.drewwalton.20121201.132311 test-keys
ro.build.version.incremental=eng.drewwalton.20121201.132311
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1.1
ro.build.date=Sat Dec 1 13:23:53 MST 2012
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=drewwalton
ro.build.host=thefed
ro.build.tags=test-keys
ro.product.model=Full Android on Emulator
ro.product.brand=Android
ro.product.name=full_crespo4g
ro.product.device=crespo4g
ro.product.board=herring
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=unknown
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=s5pc110
ro.build.product=crespo4g
ro.build.description=full_crespo4g-eng 4.1.1 JRO03L eng.drewwalton.20121201.132311 test-keys
ro.build.fingerprint=Android/full_crespo4g/crespo4g:4.1.1/JRO03L/eng.drewwalton.20121201.132311:eng/test-keys
ro.build.characteristics=default
ro.cm.device=crespo4g
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.carrier=unknown
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
ro.kernel.android.checkjni=1
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
init.svc.ueventd=running
init.svc.recovery=running
service.adb.root=1
init.svc.adbd=running
I:Checking for extendedcommand...
W:failed to mount /dev/block/platform/s3c-sdhci.0/by-name/media (No such file or directory)
Unable to mount sdcard,
loading failsafe setting...
Settings will not work
without an sdcard...
W:failed to mount /dev/block/platform/s3c-sdhci.0/by-name/media (No such file or directory)
I:Language code: en
I:Theme loaded!
I:Loading hydro resources...
I:Skipping execution of extendedcommand, file not found...
mtd: successfully wrote block at 0
I:Set boot command ""
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
mtd: successfully wrote block at 0
I:Set boot command ""
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
mtd: successfully wrote block at 0
I:Set boot command ""
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
I:Can't format unknown volume: /external_sd
I:Can't format unknown volume: /emmc
Starting recovery on Wed Feb 6 17:24:42 2013
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /sdcard vfat /dev/block/platform/s3c-sdhci.0/by-name/media (null) 0
2 /system ext4 /dev/block/platform/s3c-sdhci.0/by-name/system (null) 0
3 /cache yaffs2 cache (null) 0
4 /data ext4 /dev/block/platform/s3c-sdhci.0/by-name/userdata (null) 0
5 /misc mtd misc (null) 0
6 /boot mtd boot (null) 0
7 /recovery mtd recovery (null) 0
8 /bootloader mtd bootloader (null) 0
9 /radio mtd radio (null) 0
10 /wimax mtd wimax (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
I:COT Settings loaded!
Switching to dedupe!
I:Language code: en
I:Theme loaded!
I:Loading hydro resources...
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (480 x 800)
I:Processing arguments.
mtd: successfully wrote block at 0
I:Set boot command "boot-recovery"
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.boot.serialno=<Deleted by me. Not sure if this should be posted online.>
ro.boot.bootloader=D720SPRKE1
ro.boot.baseband=D720SPRLF2
ro.boot.info=0x4,0x4,1
ro.boot.carrier=SPR
ro.serialno=<Deleted by me. Not sure if this should be posted online.>
ro.bootmode=unknown
ro.baseband=D720SPRLF2
ro.bootloader=D720SPRKE1
ro.hardware=herring
ro.revision=34
ro.emmc=0
ro.boot.emmc=0
ro.factorytest=0
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.sys.usb.config=adb
ro.build.id=JRO03L
ro.build.display.id=full_crespo4g-eng 4.1.1 JRO03L eng.drewwalton.20121201.132311 test-keys
ro.build.version.incremental=eng.drewwalton.20121201.132311
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1.1
ro.build.date=Sat Dec 1 13:23:53 MST 2012
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=drewwalton
ro.build.host=thefed
ro.build.tags=test-keys
ro.product.model=Full Android on Emulator
ro.product.brand=Android
ro.product.name=full_crespo4g
ro.product.device=crespo4g
ro.product.board=herring
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=unknown
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=s5pc110
ro.build.product=crespo4g
ro.build.description=full_crespo4g-eng 4.1.1 JRO03L eng.drewwalton.20121201.132311 test-keys
ro.build.fingerprint=Android/full_crespo4g/crespo4g:4.1.1/JRO03L/eng.drewwalton.20121201.132311:eng/test-keys
ro.build.characteristics=default
ro.cm.device=crespo4g
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.carrier=unknown
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
ro.kernel.android.checkjni=1
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
init.svc.ueventd=running
init.svc.recovery=running
service.adb.root=1
init.svc.adbd=running
I:Checking for extendedcommand...
I:COT Settings loaded!
Switching to dedupe!
I:Language code: en
I:Theme loaded!
I:Loading hydro resources...
I:Skipping execution of extendedcommand, file not found...
mtd: successfully wrote block at 0
I:Set boot command ""
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
I:Can't format unknown volume: /external_sd
I:Can't format unknown volume: /emmc
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
mtd: successfully wrote block at 0
I:Set boot command ""
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
WTF?!?!?failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
I should note that when I rebooted into COT to grab the log file, the message about not being able to mount my SD Card was again displayed, but the recovery performed as if it was mounted. I was able to view the different partitions and enter the Storage Management area, view existing Nandroid backups, etc. Maybe the warning message is just being displayed in error?
sleepy
Related
Hi,
iam getting sdcard mount error message. I tried to flash with odin froyo 2.2 with partition checked 512 and every file properly loaded and also with ezrom.
Then i tried to adb push some files to /sbin/ which are
e2fsck
mke2fs
parted
resize2fs
sdparted
tune2fs
which worked. i type adb shell and i get /# sign. Then i try to change directory typing /sbin/ and i get a message permission denied.
What iam doing wrong. I have searched and tried a lot. My i9000 was running darky 10.1 before sdcard mount issue.
Code:
--Copying media files...
E:failed to mount /sdcard (File exists)
E:copy_dbdata_media:Can't mount /sdcard your storage not prepared yet. please use ui menu for format and reboot actions.
Meida files copy failed.
--Wiping data...
Formating /data...
E:format_volume: rfs format failed on /dev/block/mmcblk0p2
Formating /dbdata...
Formating /cache...
Data wipe failed.
--Applying /Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/xee/system/'.
Sucessfully applied multi-csc
indianx said:
Hi,
iam getting sdcard mount error message. I tried to flash with odin froyo 2.2 with partition checked 512 and every file properly loaded and also with ezrom.
Then i tried to adb push some files to /sbin/ which are
e2fsck
mke2fs
parted
resize2fs
sdparted
tune2fs
which worked. i type adb shell and i get /# sign. Then i try to change directory typing /sbin/ and i get a message permission denied.
What iam doing wrong. I have searched and tried a lot. My i9000 was running darky 10.1 before sdcard mount issue.
Code:
--Copying media files...
E:failed to mount /sdcard (File exists)
E:copy_dbdata_media:Can't mount /sdcard your storage not prepared yet. please use ui menu for format and reboot actions.
Meida files copy failed.
--Wiping data...
Formating /data...
E:format_volume: rfs format failed on /dev/block/mmcblk0p2
Formating /dbdata...
Formating /cache...
Data wipe failed.
--Applying /Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/xee/system/'.
Sucessfully applied multi-csc
Click to expand...
Click to collapse
just reflash...next time post in the proper section
I have reflashed at least 10 times. Getting the same message over and over again.
Is Android UI loaded correctly? If so, go to settings and format your internal SD
its not booting up. no menu nothing.
i can get into recovery and download.
I'm also stuck @ same problem still unsolved!!
but buddy this is not the section a mod would close it !!
and here's the link to my thread!
http://forum.xda-developers.com/showthread.php?t=1249641
Try this while in recovery (clockwork) via adb:
adb shell
mount /sdcard
su
parted /dev/block/mmcblk0
rm 1
rm 2
rm 3
quit
Now odin with repartition and your phone maybe will be resurrected . I tried this to my phone and worked
Alberto96 said:
Try this while in recovery (clockwork) via adb:
adb shell
mount /sdcard
su
parted /dev/block/mmcblk0
rm 1
rm 2
rm 3
quit
Now odin with repartition and your phone maybe will be resurrected . I tried this to my phone and worked
Click to expand...
Click to collapse
Thanks this resurrected my phone , yeah !!!
ghettino said:
Thanks this resurrected my phone , yeah !!!
Click to expand...
Click to collapse
You are welcome
Hi there, I installed CM9 successfully however when it rebooted, there was no radio. I downloaded the file 403radios_btldr.zip and tried to apply it via CWM recovery and keep getting the following error.. i have also downloaded it twice from different sources. Is that the correct radio? Any ideas?
Code:
Starting recovery on Sat Mar 24 15:43:56 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (720 x 1280)
ClockworkMod Recovery v5.5.0.4
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /system ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/system (null) 0
2 /cache ext4 /dev/block/platform/omap/omap_hsmmc.0/by-name/cache (null) 0
3 /data auto /dev/block/platform/omap/omap_hsmmc.0/by-name/userdata (null) 0
4 /misc emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/misc (null) 0
5 /boot emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/boot (null) 0
6 /recovery emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/recovery (null) 0
7 /sbl emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/sbl (null) 0
8 /xloader emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/xloader (null) 0
9 /radio emmc /dev/block/platform/omap/omap_hsmmc.0/by-name/radio (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
W:Unable to get recovery.fstab info for /sdcard during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
I:Processing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.sys.usb.config=adb
ro.build.id=ICS_MR0
ro.build.display.id=full_toro-eng 4.0.1 ICS_MR0 eng.koush.20111215.170401 test-keys
ro.build.version.incremental=eng.koush.20111215.170401
ro.build.version.sdk=14
ro.build.version.codename=REL
ro.build.version.release=4.0.1
ro.build.date=Thu Dec 15 17:04:31 PST 2011
ro.build.date.utc=1323997471
ro.build.type=eng
ro.build.user=koush
ro.build.host=Koushik-Lion.local
ro.build.tags=test-keys
ro.product.model=Full Android on Emulator
ro.product.brand=Android
ro.product.name=full_toro
ro.product.device=toro
ro.product.board=toro
ro.product.cpu.abi=armeabi
ro.product.manufacturer=unknown
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=unknown
ro.build.product=toro
ro.build.description=full_toro-eng 4.0.1 ICS_MR0 eng.koush.20111215.170401 test-keys
ro.build.fingerprint=Android/full_toro/toro:4.0.1/ICS_MR0/eng.koush.20111215.170401:eng/test-keys
ro.build.characteristics=default
keyguard.no_require_sim=true
ro.com.android.dataroaming=true
ro.com.android.dateformat=MM-dd-yyyy
ro.config.ringtone=Ring_Synth_04.ogg
ro.config.notification_sound=pixiedust.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=0146975B0401F00E
ro.bootmode=unknown
ro.baseband=��������������������
ro.carrier=unknown
ro.bootloader=PRIMEKL01
ro.hardware=tuna
ro.revision=9
init.svc.recovery=running
init.svc.adbd=running
I:Checking for extendedcommand...
I:Running extendedcommand...
Waiting for SD Card to mount (20s)
I:using /data/media, no /sdcard found.
SD Card mounted...
Verifying SD Card marker...
5a8985a48c9f5d61b0f5440da38a35c4
I:Running script:
I:
ui_print("ROM Manager Version 5.0.0.6");
ui_print("March 24, 2012");
ui_print("Preparing to install ROM...");
run_program("/cache/dowipedalvikcache.sh");
assert(install_zip("/sdcard/Download/403radios_btldr.zip"));
parse returned 0; 0 errors encountered
ROM Manager Version 5.0.0.6
March 24, 2012
Preparing to install ROM...
about to run program [/cache/dowipedalvikcache.sh] with 1 args
mount: mounting /dev/block/platform/omap/omap_hsmmc.0/by-name/userdata on /data failed: Device or resource busy
mount: mounting /dev/block/platform/omap/omap_hsmmc.0/by-name/cache on /cache failed: Device or resource busy
mount: can't find /sd-ext in /etc/fstab
umount: can't umount /sd-ext: Invalid argument
run_program: child exited with status 1
-- Installing: /sdcard/Download/403radios_btldr.zip
Finding update package...
I:Update location: /sdcard/Download/403radios_btldr.zip
I:using /data/media, no /sdcard found.
Opening update package...
Installing update...
installing samsung updater extensions
installing samsung updater extensions for toro
Writing bootloader...
Writing LTE radio...
Writing CDMA radio...
Unable to open modem device (No such file or directory)
IOCTL_MODEM_GOTA_START failed: (-1)
script aborted: assert failed: samsung.update_cdma_modem(
package_extract_file("radio-cdma.img"))
assert failed: samsung.update_cdma_modem( package_extract_file("radio-cdma.img"))
E:Error in /sdcard/Download/403radios_btldr.zip
(Status 7)
Installation aborted.
result was NULL, message is: assert failed: install_zip("/sdcard/Download/403radios_btldr.zip")
I:using /data/media, no /sdcard found.
It looks to me that your baseband is showing up as unknown and the assert failed because of that.
I would try flashing back to stock (starting from scratch) in fastboot with the official images from google. http://code.google.com/android/nexus/images.html
First I will give you the usual response (not trying to be a douche though lol ) : should've put this in Q&A section, should've checked for other threads about this first since I'm sure there are others, look through development section for the appropriate radios thread that will answer your questions, etc. etc...
Now to answer, I'm assuming by "no radio" you mean no functioning signal i.e. no data/sms/calls? if so I'd recommend looking in the development section either here or at Rootzwiki (recommend there first since they have a sticky thread with all current radios/roms) for a flashable zip... if you want to do it a better way I would suggest learning about ADB and Fastboot and doing it through those means, it does require a little bit of computer savvy to set up but is immensely helpful in many ways... also I don't believe the zip you are trying to flash is the correct one, or you may be flashing it wrong... I am on the go on my GNex but can give links if you can't find anything
blazing through on my Nexus Prime via XDA app
seems to me that the cwm zip you're using is not doing it right. attach that cwm zip for us to look at it, or a link to it.
better yet, use fastboot as suggested.
doh sorry for being in the wrong thread.. if a mod can move to Q&A..
thanks for the replies, i was able to get the google roms and update successfully. Here are the versions I was using and commands for anyone else..
fastboot flash bootloader bootloader-maguro-primekj10.img
fastboot reboot-bootloader
fastboot flash radio radio-maguro-i9250xxkk1.img
fastboot reboot-bootloader
fastboot -w update image-yakju-itl41f.zip
nfoman said:
doh sorry for being in the wrong thread.. if a mod can move to Q&A..
thanks for the replies, i was able to get the google roms and update successfully. Here are the versions I was using and commands for anyone else..
fastboot flash bootloader bootloader-maguro-primekj10.img
fastboot reboot-bootloader
fastboot flash radio radio-maguro-i9250xxkk1.img
fastboot reboot-bootloader
fastboot -w update image-yakju-itl41f.zip
Click to expand...
Click to collapse
thx for posting your solution.. i hate it when people find a solution and abandon the thread
nfoman said:
doh sorry for being in the wrong thread.. if a mod can move to Q&A..
thanks for the replies, i was able to get the google roms and update successfully. Here are the versions I was using and commands for anyone else..
fastboot flash bootloader bootloader-maguro-primekj10.img
fastboot reboot-bootloader
fastboot flash radio radio-maguro-i9250xxkk1.img
fastboot reboot-bootloader
fastboot -w update image-yakju-itl41f.zip
Click to expand...
Click to collapse
Those are commands for GSM images.
So... According to your OP you had flashed a CDMA rom on a GSM device. Then were trying to flash CDMA radios?
That is the reason why you had no service and the .zip file wouldn't flash.
Make sure you flash the correct ROM's the future.
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
Here are the facts:
my tablet was throwing errors about google app and google search box crashing. I restarted the tablet and it got stuck at boot loop.
K00E with firmware,UL-K00E-WW-7.6.0.0-user, not rooted.
what I've tried:
factory reset under droidboot:
Code:
E:failed to mount /cache (Invalid argument)
unable to mount /cache! we skip check debricking
SD download of the latest RAW file under under droidboot:
again
Code:
E:failed to mount /cache (Invalid argument)
unable to mount /cache!
Installing the firmware zip file using custom recovery:
I used this to run CWM. I cleared cache, user data, factory reset and then tried to install using external SD zip file.
Code:
failed to mount /dev/block/mmcblk0p8 at /system: Invalid argument
trying to re partition the internal SD:
from here
I tried to run parted to fix it but I am getting this
Code:
~ # parted
parted
/sbin/parted: line 1: syntax error: unexpected word (expecting ")")
~ #
I added no arguments to parted, and still it is giving me this error. I even tried pushing another copy of parted and chmodding it to execute it, still the same thing occurs.
I also tried this
on running th second command I have
Code:
~ # tune2fs -O extents,uninit_bg,dir_index -C 1 /dev/block/mmcblk0p8
tune2fs -O extents,uninit_bg,dir_index -C 1 /dev/block/mmcblk0p8
tune2fs 1.41.11 (14-Mar-2010)
tune2fs: Bad magic number in super-block while trying to open /dev/block/mmcblk0
p8
Couldn't find valid filesystem superblock.
~ #
any ideas how to move forward?
HI
I have a HTC one M9 hima. Lastly, it has suddenly rebooted. I have not use it.
But it have not stuck in boot. It has boot to the withe Logo screen then go off and boot again, again and again.
If i push power + vol down, the Black screen with e HTC logo comes and the loop go faster.
The only way to come to the bootloader ist to push power + vol down + vol up.
From there i come to the recovery or download Mode. I have twrp installed.
In twrp i discovered that some Partitions can not mount:
mount: mounting /dev/block/mmcblk0p65 on /cache failed: Invalid argument
mount: mounting /dev/block/mmcblk0p67 on /data failed: Invalid argument
mount: mounting /dev/block/mmcblk0p36 on /devlog failed: Invalid argument
mount: mounting /dev/block/mmcblk0p50 on /carrier failed: Invalid argument
mount: mounting /dev/block/mmcblk0p69 on /cota failed: Invalid argument
mount: mounting /dev/block/mmcblk0p68 on /preload failed: Invalid argument
mount: mounting /usb_otg on vfat failed: No such file or directory
mount: mounting /sd-ext on ext4 failed: No such file or directory
I tried:
- wipe Data --> mount error
- formate Data --> mount error
- flash new rom --> mount error
- install new Firmware --> requiret new start then loop
- mount manuel over adb --> invalied argument
- e2fsck /dev/block/mmcblk0p* --> bad magic number in super-block
- flash rom with fastboot --> invalid zip file
- new recovery --> after flash and boot to recover: exist old recovery <-- with dd, twrp and with fastboot
- twrp repair or change File System --> mount error
- twrp resize File System --> end with ERROR: 8
- twrp Change File System --> ERROR: 8
pls help me!!
sorry for my bad English
anyone here who knows the solution for above errors please? coz it did happen to me also. Thanks XDA for your help.
my has expanded. after After my m9 has lain a long time to empty the battery. I can only boot to the bootloader. If i try to boot to recovery or DownloadMode(Fastboot) comes a message "Fail to boot to *".
Radianer said:
my has expanded. after After my m9 has lain a long time to empty the battery. I can only boot to the bootloader. If i try to boot to recovery or DownloadMode(Fastboot) comes a message "Fail to boot to *".
Click to expand...
Click to collapse
On my htc m9, I could still boot to TWRP Recovery but in the Download Mode, it says "Failed to boot to Download"
kmx0101 said:
On my htc m9, I could still boot to TWRP Recovery but in the Download Mode, it says "Failed to boot to Download"
Click to expand...
Click to collapse
As I allready said... maybe flashing signed hosd file fix it...but it isn't sure...
some devices work after... some don't.
shivasrage said:
As I allready said... maybe flashing signed hosd file fix it...but it isn't sure...
some devices work after... some don't.
Click to expand...
Click to collapse
Thanks shivasrage. Let me try ur suggestion but where I could find a signed hosd file?
kmx0101 said:
Thanks shivasrage. Let me try ur suggestion but where I could find a signed hosd file?
Click to expand...
Click to collapse
https://forum.xda-developers.com/one-m9/help/download-modepossible-fix-t3555678