Related
Alright guys, I've got a question. I have my brothers nexus s that has had CM9 A11 on it and we decided to move to the latest CM9. Long story short, I am no longer able to boot the phone up, but can only access CWM Recovery and Bootloader/Fastboot mode. Trying to boot results in a bootloop. I need help getting this thing back to stock however I can. I've tried to flash recovery.img via fastboot but cannot get my computer to recognize the phone in order to do what I need. He would like his phone back ASAP and I hate to tell him its bricked for a few days. Thanks!
Download full OTA ROM from the link in my signature. Boot into CWM, mount USB storage, and transfer the file to SD card. Flash it. Done.
Just make sure you download the correct ROM for your phone model.
Sent from my Nexus S using xda premium
Video on that page will show you how to install drivers on a windows-based machine to recognise the phone for fastboot, and provide files to do so.
Also, can't you go into CWM --> mounts and storage --> mount usb storage (while plugged into the computer) then copy over any files you need, then flash through recovery.
I forgot to mention that I am getting this when trying to format cache:
E:Can't find misc
E:failed to find "cache" partition to mount at "/cache"
E:Can't mount /cache/recovery/command
E:Can't find misc
E:failed to find "cache" partition to mount at "/cache"
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to find "cache" partition to mount at "/cache"
E:Can't mount /cache/recovery/latest_log
E:Can't open /cache/recovery/latest_log
E:Can't find misc
E:failed to find "cache" partition to mount at "/cache"
I tried to install the OTA update like you said but got the following:
assert failed: write_raw_image("/tmp/boot.img".
"boot")
E:Error in /sdcard/(OTA file name here)
(status 7)
Installation aborted.
Maybe the internal SD card is bad? Any thoughts?
When you get the drivers installed, download the latest 5.0.2.0 CWM from here.
Alright, so I got fastboot to recognize the phone, but am having another problem. It gave me an error when I gave the command to flash the new CWM. I tried to install pdanet for the drivers, and the phone says at the bottom "FASTBOOT STATUS - FAILInvalid Command". I really think something has been corrupted, any ideas on how to fix it/restore it? Thanks for all the help guys.
Fastboot status is not a command.
Fastboot devices is the command you use to test if it sees the device . The serial number will show.
uh oh sounds like someone flashed brickROM V1
Sent from my Nexus S 4G using XDA App. Developer of brickROM, and OP of XDA Thread of The Year 2011.
I have a rather confusing problem that requires knowledgeable folks.I will lay out the entire situation to the best of my ability. Please, read through to the end. A few things that should be clarified: I am a 48 year old adult who is fairly skilled with tech. Linux, however is a bit of a weak point. I am pretty intelligent, methodical, and thorough. I researched my phone project well, and was operating from clear instructions. I met several problems along the way, and spent about 30 hours reading, researching, and attempting things before i exhausted my resources and posted here. I point these things out from the start because I abhor taking the time to write a detailed post requesting information, only to get one line answers telling me to "look it up." That being said, here is the situation.
Equipment
T-Mobile Samsung Galaxy S (SGH-T959V)
Stock USB data transfer cable
Desktop computer running Windows 8.1 64 bit
Software Used/Available
Android SDK
Odin 3 v1.85
Heimdall v1.4rc1 win32
Heimdall v1.4rc2 win32
Semaphore 2.7.4
CyanogenMod 10.1.3 galaxysmtd
CyanogenMod 10.2.0 galaxysmtd
Procedure
I began by following the procedure detailed on the CynaogenMod site (wiki.cyanogenmod.org/w/Install_CM_for_galaxysmtd) It instructed me to download Semaphore's ClockworkRecovery Mod and Heimdall, boot into download mode, and flash the kernel, which I did, though it was not trouble free. Heimdall had trouble sending the data, but after fiddling a bit with drivers and cables, it completed.
Continuing on their instructions, I downloaded CyanogenMod 10.2.0 and placed it on the root of the sdcard using adb (adb push cm-10.2.0-galaxysmtd.zip /sdcard/) I then booted to recovery mode and performed the following actions in this order:
Select and execute the option to wipe data/factory reset.
Select install zip from sdcard.
Select choose zip from sdcard.
Select the CyanogenMod file you placed on the sdcard.
Optional: Install any additional packages you wish using the same method.
Once the installation finished, returned back to the main menu, and selected the reboot system now option.
At this point, the device should have booted into CyanogenMod.
Instead, It started to load cyanogen, but stalled at "Waiting for /sdcard to mount", counted down from 20 to 0, and then rebooted, ad infinitum.
Current Status
Now, it boots into CWM-based Recovery v6.0.4.5, and the following printout under the command list:
E: failed to find "cache" partition to mount at "/cache"
E: failed to find "cache" partition to mount at "/cache"
E: Can't mount /cache/recovery/command
E: failed to find "cache" partition to mount at "/cache"
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: failed to find "cache" partition to mount at "/cache"
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
E: failed to find "cache" partition to mount at "/cache"
E: failed to find "cache" partition to mount at "/cache"
Error mounting /cache!
I can't boot into download mode. I cannot mount /cache, /datadata, /system, or /data. I cannot format them, either. I have tried a few times from badly worded instruction posts to push the file again and install from zip, but heimdall fails saying "Is a directory." I dont understand sideloading sufficiently to use it, but I suspect it wouldn't help until i can resolve the mounting issue.
Things I Have Tried, and why they didn't work
In googling "cant mount /sdcard" issues, I have seen many posts suggesting to "Use Odin and revert to stock." Currently, when my phone is plugged into USB, my computer recognizes only two disk drives, both classed as "Linux File - CD Gadget USB Device" Odin doesn't see it at all, and I suspect that it is because it isn't in download mode, and the compter doesnt see it as a phone. If there is a way around this, i would be grateful to hear it.
I have also seen a few posts suggesting to "reflash cwm_mod." I assume this is suggesting that by reverting to just a clean system and CWM, I could try to install the mod, or a stock rom, again. I do not know how this is possible when I cant mount /sdcard. It seems that this single issue is the crux of the matter.
Request For Help
I am totally stumped. I am willing to work with anyone who can either walk me through some steps or point me to a well written resource. I have looked up many guides, but frankly, a lot of them are so poorly written as to be nearly incomprehensible. All siggestions are humbly accepted, and greatly appreciated. I will be home all day, and in front of the computer waiting.
Thank you for reading.
If you can get into download mode try this.
http://forum.xda-developers.com/showthread.php?t=2258628
☞Sent from here☜
Hey I was in the same boat as you, try this and it will take you back to gingerbread but you will be able to reflash newer updates and mods.
just click the download link in the thread and open it after you download.
Then put your phone into download mode to connect with heimdall and once it says connected click the flash button and once its done you'll be back to stock gingerbread.
I was stumped for a few days because I thought I had to use odin but its very simple heres the link to the thread.
http://forum.xda-developers.com/showthread.php?t=1358498
baseballfanz said:
If you can get into download mode try this.
http://forum.xda-developers.com/showthread.php?t=2258628
☞Sent from here☜
Click to expand...
Click to collapse
You did like me; I didn't realize this post is referring to a Galaxy S 4G, not the Galaxy S4. I don't believe you'd want to follow that particular bit of advice being that it's not the same model.
hi,
I tried upgrading my tf300t from cm10.1 to cm10.2 . after a few failed attempts during which I am not exectly sure what I did wrong i got the device into a condition in which it only boots directly into CWM v6.0.2.3 without any option to do anything else. pressing power+volume down does not stop it from directly booting into recovery.
inside the recovery it says:
"E:Can't mount / cache/recovery/command/
E:Can't mount / cache/recovery/log/
E:Can't open / cache/recovery/log/
E:Can't mount / cache/recovery/last_log/
E:Can't open / cache/recovery/last_log/",
and i cannot mount any partition on the device. trying to access it from fastboot\adb has not been successful.
Any help would be appreciated.
thanks a lot,
guy
I now recall that at some point after trying to flash cm10.2 didn't work I tried flashing the offical asus firmware blob. after that the device successfully booted but when I tried to return to the recovery mode I still could not mount the /data partition. after that I tried some more flashing which brought me to the current situation.
new development -
after installing the universal naked driver i was able to boot into the boot loader using adb and I even can boot the device to the os, though no change when inside the recovery mode. if the device reboots it automatically goes into recovery and to reboot it I have to use adb again.
Ghtm said:
new development -
after installing the universal naked driver i was able to boot into the boot loader using adb and I even can boot the device to the os, though no change when inside the recovery mode. if the device reboots it automatically goes into recovery and to reboot it I have to use adb again.
Click to expand...
Click to collapse
Flash the updated stock ROM again via fastboot to reset it back to stock. then flash the correct TWRP and then flash the CM 10.2 ROM you wanted.
cmendonc2 said:
Flash the updated stock ROM again via fastboot to reset it back to stock. then flash the correct TWRP and then flash the CM 10.2 ROM you wanted.
Click to expand...
Click to collapse
how do i flash a rom using fastboot?
Ghtm said:
how do i flash a rom using fastboot?
Click to expand...
Click to collapse
like this:
http://www.theandroidsoul.com/how-to-restore-asus-transformer-tf300t-back-to-stock/
Code:
fastboot -i 0x0B05 flash system blob
cmendonc2 said:
like this:
Code:
fastboot -i 0x0B05 flash system blob
Click to expand...
Click to collapse
I've tried that and the device does not seem to be responding to the idea. in fact I dont think it gets anything I've tried to flash at all. the files do transfer but do not seem to install. after starting a flash with fastboot the device stops responding.
Ghtm said:
I've tried that and the device does not seem to be responding to the idea. in fact I dont think it gets anything I've tried to flash at all. the files do transfer but do not seem to install. after starting a flash with fastboot the device stops responding.
Click to expand...
Click to collapse
plus, the bootloader screen does not show the usb icon at all. I am flashing when the device is in the bootloader.
at the bootloader screen there is a message: "key driver not found"
Ghtm said:
I've tried that and the device does not seem to be responding to the idea. in fact I dont think it gets anything I've tried to flash at all. the files do transfer but do not seem to install. after starting a flash with fastboot the device stops responding.
Click to expand...
Click to collapse
OK you said it can boot into Android though. Use terminal emulator to install the TWRP and then flash the stock ROM from inside TWRP. Just make sure the TWRP matches your bootloader.
---------- Post added at 04:52 PM ---------- Previous post was at 04:51 PM ----------
Ghtm said:
plus, the bootloader screen does not show the usb icon at all. I am flashing when the device is in the bootloader.
at the bootloader screen there is a message: "key driver not found"
Click to expand...
Click to collapse
That means you are on the 4.2.1 or 4.2.2 bootloader. That bootloader doesnt have a USB icon, it goes directly to fastboot if it is detected and that is completely normal.
cmendonc2 said:
OK you said it can boot into Android though. Use terminal emulator to install the TWRP and then flash the stock ROM from inside TWRP. Just make sure the TWRP matches your bootloader.
---------- Post added at 04:52 PM ---------- Previous post was at 04:51 PM ----------
That means you are on the 4.2.1 or 4.2.2 bootloader. That bootloader doesnt have a USB icon, it goes directly to fastboot if it is detected and that is completely normal.
Click to expand...
Click to collapse
it says permission denied (cause i do not have root access?)
Ghtm said:
it says permission denied (cause i do not have root access?)
Click to expand...
Click to collapse
Oh i thought you still had CM10.1 on it. Can you flash ROMs from that CWM or is the /data thing messing it up.
cmendonc2 said:
Oh i thought you still had CM10.1 on it. Can you flash ROMs from that CWM or is the /data thing messing it up.
Click to expand...
Click to collapse
the /data prevents me from accessing anything on the sdcard so i cant flash anything from inside the recovery itself.
so, after doing as the guy in this thread - http://forum.xda-developers.com/showthread.php?t=2425581 says, I managed to make the device successfully reboot to the os by default and even make it reinstall the stock rom and than twrp recovery. the problem no is when entering recovery, it asks for a password which i do not know. when choosing cancel it gets me in but now it displays:
"E: unable to find partition size for /misc
E: unable to find partition size for /staging
E: unable to find partition size for /data
E: unable to find partition size for /recovery
E: unable to find partition size for /boot
updating partition details...
E: unable to mount /system
E: unable to mount /cache
E: unable to mount /cache
E:TWFunc::copy_log -- cant open destination log file: /cache/recovery/log
E:unable to set emmc bootloader message
E: unable to mount /cache"
when trying to install a different rom the recovery mode fails to access the internal/external sdcard.
thanks in advance,
guy
Ghtm said:
so, after doing as the guy in this thread - http://forum.xda-developers.com/showthread.php?t=2425581 says, I managed to make the device successfully reboot to the os by default and even make it reinstall the stock rom and than twrp recovery. the problem no is when entering recovery, it asks for a password which i do not know. when choosing cancel it gets me in but now it displays:
"E: unable to find partition size for /misc
E: unable to find partition size for /staging
E: unable to find partition size for /data
E: unable to find partition size for /recovery
E: unable to find partition size for /boot
updating partition details...
E: unable to mount /system
E: unable to mount /cache
E: unable to mount /cache
E:TWFunc::copy_log -- cant open destination log file: /cache/recovery/log
E:unable to set emmc bootloader message
E: unable to mount /cache"
when trying to install a different rom the recovery mode fails to access the internal/external sdcard.
thanks in advance,
guy
Click to expand...
Click to collapse
that means you probably flashed the wrong version of TWRP. Are you on the stock 10.6.1.8 or on a later version of bootloader? Those are different.
cmendonc2 said:
that means you probably flashed the wrong version of TWRP. Are you on the stock 10.6.1.8 or on a later version of bootloader? Those are different.
Click to expand...
Click to collapse
stock rom version 10.6.1.27.5 (build number JOP40D.US_epad-10.6.1.27.5-20130902)
TWRP 2.6.3.0
are those not compatible?
*
trying TWRP 2.5.0.0 or 2.4.2.0 made no difference.
Ghtm said:
stock rom version 10.6.1.27.5 (build number JOP40D.US_epad-10.6.1.27.5-20130902)
TWRP 2.6.3.0
are those not compatible?
*
trying TWRP 2.5.0.0 or 2.4.2.0 made no difference.
Click to expand...
Click to collapse
Using twrp 2.6.3.0 -4.2 ? Or -jb?
cmendonc2 said:
Using twrp 2.6.3.0 -4.2 ? Or -jb?
Click to expand...
Click to collapse
I do not remeber which I've tried. which one should it be?
*
I tried them both again. both require a password at start and both fail mounting the partitions, showing
"E: unable to find partition size for /misc
E: unable to find partition size for /staging
E: unable to find partition size for /data
E: unable to find partition size for /recovery
E: unable to find partition size for /boot
updating partition details...
E: unable to mount /system
E: unable to mount /cache
E: unable to mount /cache
E:TWFunc::copy_log -- cant open destination log file: /cache/recovery/log
E:unable to set emmc bootloader message
E: unable to mount /cache"
Ghtm said:
I do not remeber which I've tried. which one should it be?
*
I tried them both again. both require a password at start and both fail mounting the partitions, showing
"E: unable to find partition size for /misc
E: unable to find partition size for /staging
E: unable to find partition size for /data
E: unable to find partition size for /recovery
E: unable to find partition size for /boot
updating partition details...
E: unable to mount /system
E: unable to mount /cache
E: unable to mount /cache
E:TWFunc::copy_log -- cant open destination log file: /cache/recovery/log
E:unable to set emmc bootloader message
E: unable to mount /cache"
Click to expand...
Click to collapse
Use the 4.2 one. The jb will result in a very bad brick.
cmendonc2 said:
Use the 4.2 one. The jb will result in a very bad brick.
Click to expand...
Click to collapse
seems to be working! thank you very much, I really appreciate the help! :laugh::victory:
Ghtm said:
seems to be working! thank you very much, I really appreciate the help! :laugh::victory:
Click to expand...
Click to collapse
No problem, Merry Christmas!
I Think my Internal sdcard is corrupted!
Please Help! Reflashing android won't work. I think the partition is corrupted!
Device: Google Nexus 5
Original OS: Android 5.1.0_r1 (LMY47D)
Recovery: TWRP 2.8.6.0
One day I turned my phone off, and later i decided to go into recovery. I believe I went inside Advanced Options and clicked "Fix Permissions." Then I proceeded to reboot. I was busy at the time, so when I remembered about my phone, I saw that it was still booting. It had been at least 30 minutes so I knew it was in a bootloop. I decided to go back into recovery and reflash the system.img onto it. No luck. I realized I had to try flashing the entire Nexus image (using the flash-all.bat). The phone would still not turn on. I tried flashing different versions of android, and here are my findings:
Android 5.1.0_r3, 5.1.0_r1, 5.0.1: all cause my phone to not be able to boot up (stuck on the 4 color flying animation)
Android 4.4.4, CyanogenMod (cm-11-20141008-SNAPSHOT-M11-hammerhead.zip): Allow my phone to boot up.
However, after I found that I could boot onto Android 4.4.4 and CyanogenMod, I realized that I could not get access to the sdcard!
Here are my findings:
When I go to the phone's root folder, I see a FILE called "sdcard"
When I go to \storage, I see a FILE called sdcard0
When I open camera, the app crashes (possibly because it stores pictures on the sdcard).
I tried to delete these files when I had root access with CyanogenMod but the file manager said "can't delete file." When I am in recovery mode (TWRP) however, I can see the sdcard folder and the contents. Just through every system boot, the sdcard is inaccessible.
After I realized that the problem wasn't due to the data on my phone (after flashing many system images), I realized my data partition might be corrupted. Then I went to this site and followed the directions: http://forum.xda-developers.com/goo...o-repairing-corrupted-data-partition-t2577447
The e2fsck command didn't do anything as cmd said "The superblock could not be read or does not describe a correct ext2 filesystem."
Afterwards, my friend told me to try mke2fs /dev/block/platform/msm_sdcc.1/by-name/userdata
I typed that in adb shell and something happened. I started processing blocks or something. Unfortunately now, I am unable to mount the data partition at all. I am also unable to flash the userdata.img onto my phone through fastboot.
UPDATE: When I open up twrp recovery and look in the log I see the following:
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'
E: Unable to mount '/cache/
E: Unable to mount '/persist'
...done
E: Unalbe to mount storage.
E: Unable to mount /data/media during GUI Startup.
E: Unable to mount '/cache'
Full SELinux support is present.
E: Unable to mount '/cache'
E: Unable to Mount '/cache'
E: Unable to mount /data/media/TWRP .twrps when trying to read settings file.
E: Unable to mount '/data'
MTP Enabled
Anyone know how to fix this? Please help, I owe you so much if you can solve this! Reply to me if you're able to help, I'm also new to xda so I don't really know how messages work. Thanks!
Try taking it out and putting it back in. It happened to me too.
mygoldeneye said:
Try taking it out and putting it back in. It happened to me too.
Click to expand...
Click to collapse
By sdcard I mean the internal sdcard (/storage/emulated/0). Nexus 5 does not have an external sdcard slot anyways.
So you are saying you have no apps, no widgets, nothing... /storage/emulated/0 is your main storage which INCLUDES your system files (unless you have a phone or tablet that has a separate internal SD card - would be /storage/emulated/1 ... I am guessing)
Hello everyone
I bet you have heard this before, but I can't seem to install CM on my Asus TF300T. Here are all my specs and things I used:
Tablet: Asus Transformer Pad tf300t
Environment: Mac OS X 10.11
Asus OS: 4.1, Flashed to JellyBean 4.2.1
TWRP Version: twrp-2.8.7.0-tf300t.img
CM Version: cm-12.1-20151007-SNAPSHOT-YOG4PAO337-tf300t.zip
I followed this guide here for Installing CM:
wiki.cyanogenmod.org/w/Install_CM_for_tf300t
The only thing I can think of that I did wrong is that doing step
fastboot -i 0xb05 flash recovery twrp-2.8.7.0-tf300t.imgwas that the first time i actually used the md5 file file twrp-2.8.7.0-tf300t.img.md5. I am not sure if this unmounted anything or what, but just letting you know what happened. I figured out the link i clicked was an MD5 file and not the .img file. I downloaded correct version and redid fast boot
Everything else I did as the guide mentioned. Yet, when I try to install CM with
adb push cm-12.1-20151007-SNAPSHOT-YOG4PAO337-tf300t.zip /sdcard/
It works fine, but when I try to install through twrp, Many errors popup saying failed to mount.
E: Unable to find partition size for '/misc'
E: Unable to find partition size for '/staging'
E: Primary block device '/dev/block/mmcblk0p8' for mount point '/data' is not present|
E: Unable to mount '/data'
E: Unable to recreate /data/media folder.
E: Unable to find partition size for '/recovery'
E: Unable to find partition size for '/boot'
Updating partition detail...
E: Unable to mount '/system'
E: Unable to mount '/cache'
E: Unable to mount '/data'
...done
E: Unable to mount storage.
E: Unable to mount /data/media during GUI startup
E: Unable to mount '/cache'
Kernel does not have support for reading SELinux contexts.
E: Unable to mount '/cache'
E: Unable to set bootloader message.
E: Unable to mount '/cache'
E: Unable to mount /data/media/TWRP/. tarps 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'
E: Unable to mount '/data'
Error flashing zip '/sdcard/cm-12.1-20151007-SNAPSHOT-YOG4PAO337-tf300t.zip'
E: Unable to mount '/system'
E: Unable to mount '/cache'
E: Unable to mount '/data'
...done
E: Unable to mount storage
Failed
What I can still do:1) fastboot
2) Get into JellyBean 4.2 through adb bootloader
3) adb
What I can't do:1) Install CM
2) Apparently mount anything through trwp.
I have checked many other solutions on here, but I can't really find any that work for me. I have used differing version of twrp, even custom versions saying old version of tarp (2.3ish) had a bug on 4.2.1 systems. But I reuploaded 2.8 since its lot newer, and it seemed maybe those bugs were fixed.
Thanks in advanced, and I hope you guys can help me. I would really love to start modifying CM for custom builds, but I always get stuck on problems such as this.
Bump for visibility.
Trying to get this to work. I would like to add some features to CM so this is quite critical. I hope someone can help.
Solved: used CM 11 not 12
Hello All,
Seems like I found the issue. But there is another issue as I progress. I try to do the ./extract-files.sh and it says error: device offlineIf I plug my CM 11 Tablet, the device opens in file explorer, but I guess the adb cannot find it. Any solutions to this problem?
singledigit said:
Hello All,
Seems like I found the issue. But there is another issue as I progress. I try to do the ./extract-files.sh and it says error: device offlineIf I plug my CM 11 Tablet, the device opens in file explorer, but I guess the adb cannot find it. Any solutions to this problem?
Click to expand...
Click to collapse
Hey,
Got it working now.
I made sure if USB debugging was turned on. It was, but I unchecked the notification whenever you connect to computer.
I also did used command adb shell to check if I could log into adb shell. It did. then I tried to ./extract-files.sh again, and it worked perfectly fine.
Sorry if I am flooding the Forums with perhaps meaningless information, but just wanted to keep you guys updated. Thanks for reading.