Related
May have been asked before, but I tried searching and didnt find much luck.
I think my SDCard slot finally gave up, it just will not be read (tried two different 8gb cards that both worked fine on the computer). On Cyan 4.2.9.1.
Anyway, is there a way to flash the phone without the sdcard? I was trying to think how that would be possible, but I think its not right?
Just looking for a quick def. answer so I can know if i need to go phone hunting . Or do something different , which would be much better.
Appreciate it .
Happy holidays btw
You should be able to using ADB, not sure the command lines for that. As well, you might want to try getting a can-o-air and blowing out the SD card slot on your phone.
Lastly, this is the wrong section, should of been posted in Q&A.
pjcforpres said:
You should be able to using ADB, not sure the command lines for that. As well, you might want to try getting a can-o-air and blowing out the SD card slot on your phone.
Lastly, this is the wrong section, should of been posted in Q&A.
Click to expand...
Click to collapse
I didnt really think of adb, yeah that might work. Maybe someone knows them?
Maybe
adb shell recovery flash location/zip ?
Tried the canned air, didnt change. Good thinking though.
And lastly, I did debate which place, but I was thinking I saw a utility here or I am looking for the command lines and thought maybe alittle more technical than a general question? It will fall shortly anyway (hopefully after the commands ) or get moved/deleted.
If someone nandroided, they could just send you their system.img and you could fastboot it onto the phone. Provided you have the engineering/danger SPL.
persiansown said:
If someone nandroided, they could just send you their system.img and you could fastboot it onto the phone. Provided you have the engineering/danger SPL.
Click to expand...
Click to collapse
Thats a pain, and I dont think there are many of those out there...
No adb commands? Ive been searching but it seems scarce
EDIT:
Ok I tried my idea anyway,
adb shell recovery flash update.zip
And it just hangs (no errors though)...probably missing something?
Are you able to warranty your phone for the bad SDCard Reader??
If so, I started this thread and came up with an answer, but it will bring you back to fully stock cupcake
http://forum.xda-developers.com/showthread.php?t=560254
Search for a webpage , how to root/flash/hack g1. It's has everything you need.
You need to go into fastboot
Fastboot update update.zip. somthing like that or do like the website shows 1 at a time.
There might be an adb for it, but I've never used it. Fastboot only option I believe.
bildo said:
Search for a webpage , how to root/flash/hack g1. It's has everything you need.
You need to go into fastboot
Fastboot update update.zip. somthing like that or do like the website shows 1 at a time.
There might be an adb for it, but I've never used it. Fastboot only option I believe.
Click to expand...
Click to collapse
That is the better answer, thanks for continuing. If you just left that first sentence I would have said re-read my problem, I cannot use my sdcard (the normal way rom is flashed).
As for the fastboot, I will look into that. I appreciate it, thanks.
Im getting
No android-info.txt
No android-product.txt
In the package when i try to do this command while in fastboot:
fastboot update update.zip
I found android-info in the update file from htc, but I cannot resign right now. Im also guessing it will still yell about the android-product.txt anyway, so any ideas where to get that file?
If all you're trying to do is flash a .img (system.img, userdata.img, recovery.img) and you have a developer, or hardspl, you can flash using fastboot.
Code:
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata.img
flashing an update.zip is only possible through recovery mode, but can still be accomplished using the /cache partition
Code:
adb push update.zip /cache
and you should be able to do the update from cache.
haykuro said:
flashing an update.zip is only possible through recovery mode, but can still be accomplished using the /cache partition
Code:
adb push update.zip /cache
and you should be able to do the update from cache.
Click to expand...
Click to collapse
Using you're SPL, is it still possible to place an update.zip into /cache with the partition table having been re-written??''
I'm assuming yes, since you jumped in and posted that method, I was just curious
jackslim said:
Using you're SPL, is it still possible to place an update.zip into /cache with the partition table having been re-written??''
I'm assuming yes, since you jumped in and posted that method, I was just curious
Click to expand...
Click to collapse
Well you're cache partition should have 30720K (about 30MB)
the last cyanogen rom was 37 MB =[
my other recommendation for you is to push the updates to your sdcard through your phone. (just re-read your post and noticed the SD card is functional in your phone)
Code:
adb push update.zip /sdcard/update.zip
then just proceed as usual.
@theslam08
Your signature say's your using the "Danger SPL" Judging by that you could reflash your spl from fastboot to the hard spl
Code:
fastboot flash hboot spl.bin
Then use the method described above by Haykuro pushing updates to /cache with adb
Thanks for the responses guys .
As for pushing to sdcard while in phone, thats where the problem remains. The sd reader IN the phone is busted it would seem as it just says no sd card found (cannot mount) with 3 different cards I tried (all working on the computer).
Ok so if I flash back the spl will I have more than 40mb free on the cache partition? Because yeh, the most recent update from CM is ~40mb, so it wont fit currently.
ANd once pushed to /cache, how would I go about doing the actual update? You said "you should be able to do the update from the cache part.), not sure how, just give the location?
console: flash update /cache/update.zip ?
Thank you.
theslam08 said:
Thanks for the responses guys .
As for pushing to sdcard while in phone, thats where the problem remains. The sd reader IN the phone is busted it would seem as it just says no sd card found (cannot mount) with 3 different cards I tried (all working on the computer).
Ok so if I flash back the spl will I have more than 40mb free on the cache partition? Because yeh, the most recent update from CM is ~40mb, so it wont fit currently.
ANd once pushed to /cache, how would I go about doing the actual update? You said "you should be able to do the update from the cache part.), not sure how, just give the location?
console: flash update /cache/update.zip ?
Thank you.
Click to expand...
Click to collapse
i forgot the exact command to force a boot-recovery and have it flash through cache (the traditional method)
but if your on cyanogen's recovery you can do
Code:
adb shell mount -t yaffs2 /dev/block/mtdblock4 /sdcard
this should mount cache into /sdcard, allowing you to flash.
haykuro said:
i forgot the exact command to force a boot-recovery and have it flash through cache (the traditional method)
but if your on cyanogen's recovery you can do
Code:
adb shell mount -t yaffs2 /dev/block/mtdblock4 /sdcard
this should mount cache into /sdcard, allowing you to flash.
Click to expand...
Click to collapse
Excellent, that seemed to be the trick (after going back to HSPL because yeah, I didnt have enough room with haykuro's). Though some bugs with that.
I got it to copy once after making that partition mount, and I was able to see the update file. I updated, and everything went well (even though I wondered how in the middle of the update it says formatting cache, yet it still worked).
Now, I went to put on a theme file and it says out of room. I hit 'update from sdcard' in recovery and it says E: No zip files found or something like that, just no files. So if it gets 'wiped' how is there no space? Is there a manual format I should do?
And I dont think this has happened to anyone yet, so thanks for going through this , im sure others down the road will find it helpful.
Not to get off-topic or picky about anything, but having the phone without an SD card being able to be read seems kind of pointless.
After all, you won't be able to run A2SD, or move the cache. The phone's going to run as if it was "stock."
akapoor said:
Not to get off-topic or picky about anything, but having the phone without an SD card being able to be read seems kind of pointless.
After all, you won't be able to run A2SD, or move the cache. The phone's going to run as if it was "stock."
Click to expand...
Click to collapse
Not being blunt but, thats the point. I have 'no' other choice right now, I cannot get a new phone for a while (and warranty is over, its a yr and 3 months since pur)
I obviously know I cannot use A2SD, so I need to get it to run 'stock', and thats proving to be a trick (stock but not). I almost have it, but cache doesnt seem to wipe on its own, which is the new problem. Once that is cleared, then I should be all set .
theslam08 said:
Not being blunt but, thats the point. I have 'no' other choice right now, I cannot get a new phone for a while (and warranty is over, its a yr and 3 months since pur)
I obviously know I cannot use A2SD, so I need to get it to run 'stock', and thats proving to be a trick (stock but not). I almost have it, but cache doesnt seem to wipe on its own, which is the new problem. Once that is cleared, then I should be all set .
Click to expand...
Click to collapse
Ah, okay - now it makes sense. I didn't understand the purpose at first.
Well I screwed the pooch on this one...
While browsing on the streak the battery died and after that I had force close issues for just about every user and system app on the phone. Normally that can be something corrupted on the sdcard from the shutdown and you can typically find the folder and remove it. The alternative would be running fix permissions in terminal, adb, or rom manager. That's not the case here (that I've found). It happens or has happened to me on my sgs before but not my nexus or g1 before that so I'm not sure what specifically triggers it. While trying to find the corrupted file I I tried to install Rom Manager but I can't get into the market despite clearing the cache. I can't install any apps at all actually - it will reboot the phone.
It seems to be a permissions problem. When the issue started like 8 hours ago the sdcard, system, and data were all read only. I fixed the sdcard by mounting to my computer and fixing the permissions in windows by changing the folder properties. I eventually fixed the system permissions (I believe) when I fastboot flashed the boot and system.img for the "performance fixes"; however, I can't for the LIFE of me fix the permissions of the /data and whatever else still is read-only. Flashing the system.img did change that to read-write though which was a major step in the right direction. Seriously, I've tried wiping in recovery (it says it works but doesn't wipe when rebooting), fastboot erase /data to name another attempt with no results after rebooting. It just doesn't erase anything like recovery, fastboot, and everything else doesn't have permission to erase, delete, or modify the data partition.
I can't install apps normally or adb.
I can't wipe data - I get errors in adb about it being read-only.
I can't wipe data in Recovery. It wipes, then reboots, with none of the data wiped.
I can't wipe in Fastboot using Fastboot erase /data - same thing as above.
I can't install root explorer only I'm pretty sure that won't work if fastboot doesn't.
I can't fix permissions using any method that I know of...
Is there anything I'm missing on ways to erase/format /data and everything else that might have this permission problem?
Logcat: http://db.tt/0bzhUQi
*edit:
So I also have root when booting amidst all the force closing (tested with titanium backup) I have but ADB doesn't. I can only get su with adb when I run OneClickRoot again and I get the "failed to copy rateagainstthecage to /data/local/tmp/rageagainsthecage. Read-only filesystem. Then says "unbalbe to chmod /data/local/tmp/tageagainsthecage read-only file system which is what I got also when I tried fixing the permissions for that folder. With that - I only have temporary root only in adb - fully rooted otherwise...
Same problem here cant save or delete. Very time I start up I get the welcome screen and I have to input all my info then all of my apps start to crash. I tried flashing the boot and system.img with fastboot but that did nothing so I decided to see what will happens if I erased all of my partitions (system, boot, userdata, recovery and cache) Fastboot reports back that my partitions all got erased but when I boot up (it shouldn't boot up because all partitions are deleted)it start up to the welcome screen and I back to the same problem that I cant permanently wright or delete to the internal drive
Ya - I'm at a total loss. Keep me posted on what you try and I'll do the same. I won't be able to mess with it until later today and not really sure of what I'll try next. As of now it's essentially worthless to use...
Sorry what will happen if you factory reset now and erase tablet storage? (option 4 with volume up +power button)?
At least you have almost nothing more to lose here right.
Otherwise the only solution I think is to wait for CWM recovery image to come out then...
Sorry that this happened to your DS7. I struggled with quite some issue with mine too, it is pretty annoying.
I tried that factory reset over 10 time. All of the same files that I had on the streak7 before this problem stay intact. Factor rest from the recover mode dont seem write to the streak7
killahbeatz said:
I tried that factory reset over 10 time. All of the same files that I had on the streak7 before this problem stay intact. Factor rest from the recover mode dont seem write to the streak7
Click to expand...
Click to collapse
+1. I even fastboot erased /data or attempted to. Seems like the command works but when you reboot everything is still there.
Found the other post which I didn't find http://goo.gl/xlO6y earlier.
I'm wondering if we tried setting permissions with adb with the mounts they're finding in this thread http://goo.gl/wOynl
I'll post back if I can find the chmod commands. That info might help though.
I tried fastboot -w to erase the data from the device. It boots with no force close issues now but I still can't wipe anything (still read only). I think I can install apps now though so hopefully I can install Rom Manager and Root Explorer to fix permissions and see what I can find out. Doubt it will work but hey, if I started out with read only sdcard, data, and system, and now have read-only data, that's progress I suppose.
I only have it for another few days before returning. I received the replacement yesterday and have to mail it back soon.
I had an experience the other night that I found rather frightening and enlightening, and felt the need to contribute my learning. I attempted to install a new ROM on my Nexus 5 and encountered a freeze during the /system write process. I waited 30 minutes and decided it wasn’t going to finish, so I powered off. As an avid and experienced ROM flasher I knew this could hurt, and knew it was an inevitable requirement.
Upon rebooting back to recovery (I had already wiped /system /data, etc. in preparation for a new ROM) I found that I was unable to mount /data and subsequently /sdcard. I received a few different errors depending on which recovery I attempted (fastboot flashed). I was given neat things like “Enter password to decrypt /data” – TWRP, or “E: Unable to mount /data, invalid argument”, “E: Error mounting /data”, “E: Error mounting /sdcard”.
During all of this I realized I could get an ADB shell going from within Philz recovery (I am not sure if TWRP or CWM do this, nor did I try). After much research, and very much to my dismay, I was unable to find a complete guide or walkthrough for how to go about recovering from this. This is the procedure I glued together from my own digging and manual learning of the commands required. This procedure may or may not work in all cases but is a viable step to recovering your /data partition before going the nuke & pave route with the factory image!
(NOTE: I’ll try to keep this as simple as possible. I am not a dev. I do this for fun/learning in the little free time I get and am not typically available to assist, so please use this only if you feel comfortable with the material. Flashing a ROM/Kernel/etc. is one thing. Digging in the innards of the Android partitions/file system is a whole other beast! To be VERY clear: I am not responsible for damages or loss incurred by the use or misuse of this information.) Also note, if you have an ADB enabled recovery, you can probably try this process against your devices partitions as well.
The following instructions assume you are unable to mount /data or /sdcard on the Nexus 5 and are receiving errors. This also assumes that the wipe /cache function is not resolving the issue for you (as this seems to work for some depending on the issue).
Prerequisites:
- Philz recovery for LGE Nexus 5 (http://forum.xda-developers.com/showthread.php?t=2565174)
- Android ADB interface drivers and software (Available from existing root toolkits and SDK)
- Fastboot executable (Also available from existing root toolkits and SDK)
***Note: I performed all of this from Windows 8. The toolkit I used was Wug’s Nexus Root Toolkit (http://forum.xda-developers.com/showthread.php?t=2517778). If you are a Windows user, read and follow the toolkit instructions to install the drivers. Use the Advanced Utilities[Launch]->Manual Input[Launch CMD Prompt] to bring up a Command prompt and perform the steps below.
- For simplicity, ensure that the ADB and Fastboot binaries are in the same location if you are gathering these binaries from the SDK or other source.
- Create a folder that you can later use to pull recovered files from your phone. (if so desired)
Terminologies used:
- Terminal = Command Prompt (Windows), Bash/etc (Linux), Terminal (MacOSX)
- Fastboot = Application that interfaces with the Bootloader (flash/wipe partitions, etc)
- ADB = Android Debug Bridge (Provides an interface to interact with Android filesystem)
- Binaries = Files containing executable code (for this context, ADB and Fastboot applications)
- Bootloader = Think of it as the EFI or BIOS equivalent for your phone. (Accessed with VOLDN+PWR)
- Recovery = CWM/TWRP/Philz (We will be using Philz, as this was what I used to write this guide)
Steps:
1. Install all required drivers and prerequisites listed above.
a. Use Wug’s toolkit or whatever method gets your drivers installed for your OS.b. If you are not familiar with this process, then please research!
2. Power off your phone and connect via USB to your PC.
3. Power your phone into the bootloader by holding the PWR+VOLDN keys
4. In a Terminal, browse to the location of your fastboot binaries. (See prerequisite note for Wug’s)
a. Enter ‘fastboot devices’ to verify that your phone is detected. If it returns a “<serialnumberofdevice> fastboot” then you may proceed. If it does not, please check your driver installation and start over.
5. Flash and boot to Philz recovery:
a. Extract the ‘recovery.img’ file from Philz Recovery ZIP and place in the same location that fastboot and adb binaries are located.b. Enter ‘fastboot flash recovery recovery.img’ (without quotes) in the Terminal. This will write the new recovery.c. Once complete (takes a brief second usually), use the VOLUP/DN keys until the Bootloader shows “Recovery Mode” and press the power key. Your phone should now be booting into Philz recovery.
6. Use ADB to launch a root shell from within Philz recovery
a. Ensure that the drivers are now detecting your device as an ADB ready device by entering: ‘adb devices’. If it returns “<serialnumberofdevice> recovery” then you are ready to proceed. If it does not, please verify your ADB driver installation and check again.b. Enter: ‘adb shell’ to gain full root shell access to the Android file system. (You should see a “~#” prompt to show that you’re now in a root shell)
7. Attempt repair of /data partition. This partition includes /sdcard and dalvik. (/sdcard is linked to /data/media) At the ~# prompt:
a. Enter: ‘e2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata’b. You should now be prompted to repair or fix errors. Press [Enter] key to use the default answer of for yes. If you are not, then this fix may not apply to you.c. Continue pressing [Enter] until the process completes.d. Proceed to next step if you have gotten this far.
8. Attempt to manually mount the data partition.
a. We are going to mount /data as read-only for now. To do this, enter: ‘mount /dev/block/platform/msm_sdcc.1/by-name/userdata /data’b. If mount is successful, it will simply drop down to the next blank shell prompt. If it fails, you will receive an error. If you receive an error, then the repair has failed.c. If you did not receive an error, you can now browse to your /data and /sdcard partitions. This is accomplished by entering: ‘cd /data’ for /data, and ‘cd /data/media/0’ OR ‘cd /sdcard’ for your /sdcard (/sdcard is a link that will drop you directly to /data/media/0)
9. BACKUP YOUR ENTIRE SDCARD TO YOUR COMPUTER!!! (Optional, but highly recommended)
a. Enter: ‘adb pull /data/media <path_on_computer>’b. <path_on_computer> will be a folder you created in the prerequisites.c. Wait for this process to complete.
Congratulations! You may now proceed to launch recovery and flash at will. I highly recommend after making the backup in step 9 that you perform a full factory reset to correct any potential lingering issues with the partitions. You can then push the files back to your /sdcard by mounting /data as RW using ADB shell through Philz recovery (please reference the ‘mount’ and ‘adb’ command utilities for information about how to do this).
If you find yourself in the unfortunate position to have to use this, please share your results in the forum for others. If you find something does not work, please post it (I will check occasionally and update as I can). I do not frequent my PM’s, and again, I am not available to provide support. Please understand this and use at your own risk.
If this helped you, then my job here is done . Thanks for reading!
(I am not affiliated with any of the devs that provide these tools. Be sure to thank them if you used their tools, as they deserve all credit for enabling and teaching us to do these things – even when we do break our own stuff!)
Nice guide I'm sure this is going to be very useful for a lot of people. :thumbup::thumbup:
Sent from my Nexus 5 using Xparent BlueTapatalk 2
Really helpful guide, I corrupted the data and cache partition while updating (via official OTA by sideload) to 4.4.1 (full stock Nexus 5), and I had to format all flashing then factory image and losing all the data...
Now if it does happens another time, I'll know what to do.
Thanks
Good write up but, I don't recommend tool kits. You can do all this with fastboot commands. You could just flash userdata image with fastboot
As a Linux admin, I'd wanna format /data after pulling off any files I wanted to keep rather than just rely on fsck . Is that an option? Is mkfs even on the recovery?
Sent from my BN NookHD+ using xda app-developers app
Thanks for sharing.
My nexus5 cant mount cache partition and i cant flash to stock factory，this maybe helpful.
Thank you again.
ywt474000158 said:
Thanks for sharing.
My nexus5 cant mount cache partition and i cant flash to stock factory，this maybe helpful.
Thank you again.
Click to expand...
Click to collapse
Can you fastboot flash the cache.img?
razholio said:
As a Linux admin, I'd wanna format /data after pulling off any files I wanted to keep rather than just rely on fsck . Is that an option? Is mkfs even on the recovery?
Sent from my BN NookHD+ using xda app-developers app
Click to expand...
Click to collapse
I'm no Linux admin but there's a wipe /data button which does that in TWRP and also probably in CWM.
Sent from my Galaxy Nexus using Tapatalk
Somehow it seems as though all of my partitions have been wiped/corrupted and I was directed to this thread as possible help. When trying to run step 7 command(had to do it with CWM v6.0.4.5 as it doesn't seem to want to keep philz when sideloading or fastboot flashing it), it gives me the following response:
e2fsck: 1.41.14 (22-Dec-2010)
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/platform/msm_sdcc.1/by-name/userdata
The super block could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device>
My phone was having freezes and shutdowns so I decided to flash a new ROM to freshen things up and it failed and aborted. After that I've got no android to boot into and I can't mount or access any of the partitions. I've got fastboot and adb, but no clue where to begin as it seems like I have to recreate my partition table but can't find any info on doing that for the nexus 5 itself
tidoubleger said:
Somehow it seems as though all of my partitions have been wiped/corrupted and I was directed to this thread as possible help. When trying to run step 7 command(had to do it with CWM v6.0.4.5 as it doesn't seem to want to keep philz when sideloading or fastboot flashing it), it gives me the following response:
e2fsck: 1.41.14 (22-Dec-2010)
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/platform/msm_sdcc.1/by-name/userdata
The super block could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device>
My phone was having freezes and shutdowns so I decided to flash a new ROM to freshen things up and it failed and aborted. After that I've got no android to boot into and I can't mount or access any of the partitions. I've got fastboot and adb, but no clue where to begin as it seems like I have to recreate my partition table but can't find any info on doing that for the nexus 5 itself
Click to expand...
Click to collapse
Have you tried this yet http://forum.xda-developers.com/showthread.php?p=47156064
jd1639 said:
Have you tried this yet http://forum.xda-developers.com/showthread.php?p=47156064
Click to expand...
Click to collapse
Yes I tried it by using the flash-all.bat, flashing individually, and even Wug's toolkit as a last resort there but got nothing. When flashing the bootloader and radio it sends over fine but then gives me FAILED (remote: flash write failure) and finishes. When trying to flash the system or userdata it gives me FAILED (remote: failed to erase partition) and ends.
tidoubleger said:
Yes I tried it by using the flash-all.bat, flashing individually, and even Wug's toolkit as a last resort there but got nothing. When flashing the bootloader and radio it sends over fine but then gives me FAILED (remote: flash write failure) and finishes. When trying to flash the system or userdata it gives me FAILED (remote: failed to erase partition) and ends.
Click to expand...
Click to collapse
I'm thinking your emmc went bad. Rma is probably your option right now
jd1639 said:
I'm thinking your emmc went bad. Rma is probably your option right now
Click to expand...
Click to collapse
Well as far as Google knowing it, if I am able to successfully reset the tamper flag and lock the bootloader am I good to go or will they still find out?
tidoubleger said:
Well as far as Google knowing it, if I am able to successfully reset the tamper flag and lock the bootloader am I good to go or will they still find out?
Click to expand...
Click to collapse
If all your positions are corrupted I doubt you'll be able to reset the tamper flag. But also, no one will be able to see the tamper flag. But try to reset it and try to relock the bootloader. I don't think anyone will be able to tell if you modified anything or not.
not know
Did not know this could be done
jd1639 said:
If all your positions are corrupted I doubt you'll be able to reset the tamper flag. But also, no one will be able to see the tamper flag. But try to reset it and try to relock the bootloader. I don't think anyone will be able to tell if you modified anything or not.
Click to expand...
Click to collapse
Hmm, I can see that the tamper flag is still true even after running that zip because it still fails because it can't mount /cache. I'm getting the feeling that the partitions aren't corrupted but have just been wiped or something. When I booted into TWRP through fastboot I was able to adb push to the sdcard and it showed up in the list when trying to install a zip, however the Internal Storage still read 0MB. I won't be able to RMA it for a few more days so if any other ideas come about, I'm all for it as I'd rather not have to RMA this lol
tidoubleger said:
Hmm, I can see that the tamper flag is still true even after running that zip because it still fails because it can't mount /cache. I'm getting the feeling that the partitions aren't corrupted but have just been wiped or something. When I booted into TWRP through fastboot I was able to adb push to the sdcard and it showed up in the list when trying to install a zip, however the Internal Storage still read 0MB. I won't be able to RMA it for a few more days so if any other ideas come about, I'm all for it as I'd rather not have to RMA this lol
Click to expand...
Click to collapse
In twrp 2.6.3.4 have you tried going into wipe and then format data?
@tidoubleger I am going to call in some RCs that were having this problem on an N7. They eventually got it sorted and up and running. They might be able to help.
@demkantor @MameTozhio @kilometers4
Fellas, would you be able to help this person out the same way you did here.
jd1639 said:
In twrp 2.6.3.4 have you tried going into wipe and then format data?
Click to expand...
Click to collapse
Yeah it fails due to being unable to mount /cache.
Woody said:
@tidoubleger I am going to call in some RCs that were having this problem on an N7. They eventually got it sorted and up and running. They might be able to help.
@demkantor @MameTozhio @kilometers4
Fellas, would you be able to help this person out the same way you did here.
Click to expand...
Click to collapse
Thanks Woody, I appreciate the call to arms I'm currently at Disneyworld, so I won't be able to test anything until this evening but will do my best to answer questions until then
tidoubleger said:
Somehow it seems as though all of my partitions have been wiped/corrupted and I was directed to this thread as possible help. When trying to run step 7 command(had to do it with CWM v6.0.4.5 as it doesn't seem to want to keep philz when sideloading or fastboot flashing it), it gives me the following response:
e2fsck: 1.41.14 (22-Dec-2010)
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/platform/msm_sdcc.1/by-name/userdata
The super block could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device>
My phone was having freezes and shutdowns so I decided to flash a new ROM to freshen things up and it failed and aborted. After that I've got no android to boot into and I can't mount or access any of the partitions. I've got fastboot and adb, but no clue where to begin as it seems like I have to recreate my partition table but can't find any info on doing that for the nexus 5 itself
Click to expand...
Click to collapse
I had the same problem. This is how I got it sorted.
follow these steps and you should get it sorted
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash bootloader bootloader.img
fastboot flash recovery recovery.img
once it flashes, boot into recovery.
format sdcard (i believe it is)
Now adb sideload ROM and gapps
I have class until this afternoon, but that should get it fixed
If you have any hangups post it here and I'll help you when I'm free.
Good Luck
Ok So I have an HTC One m7. and I had CyanogenMod installed. Then jsut today I decided I would go back to Sense 6. So I download Android Revolution HD 71.1 for m7 install it on my phoen. Then CWM(Which I hate btw and can't uninstall no matter what I do) says your phone is not rooted would you like to root it when I click reboot phone. No matter which I click I get stuck on the HTC logo boot logo. I don't care if I lose my data or anything so I click factory reset, then wipe cache, then wipe dalvik cache. Then I get the error were it constantly says cant mount /cache or whatever. So to fix it i wipe Dalvik Cache again. Then I try sideloading ViperOne Rom. Guess what It give me *failed to write 'protocol fault <no status> *
Then I tried formatting my data with CWM which took 2 hours and still didn't complete so I rebooted(which led to more problems) Now I cant say install from sdcard because it gives me the error E: Can't Mount /sdcard. So that means I cant adb push Viper /sdcard. I have no Idea what to do. Help me please!
radsherwin said:
Ok So I have an HTC One m7. and I had CyanogenMod installed. Then jsut today I decided I would go back to Sense 6. So I download Android Revolution HD 71.1 for m7 install it on my phoen. Then CWM(Which I hate btw and can't uninstall no matter what I do) says your phone is not rooted would you like to root it when I click reboot phone. No matter which I click I get stuck on the HTC logo boot logo. I don't care if I lose my data or anything so I click factory reset, then wipe cache, then wipe dalvik cache. Then I get the error were it constantly says cant mount /cache or whatever. So to fix it i wipe Dalvik Cache again. Then I try sideloading ViperOne Rom. Guess what It give me *failed to write 'protocol fault <no status> *
Then I tried formatting my data with CWM which took 2 hours and still didn't complete so I rebooted(which led to more problems) Now I cant say install from sdcard because it gives me the error E: Can't Mount /sdcard. So that means I cant adb push Viper /sdcard. I have no Idea what to do. Help me please!
Click to expand...
Click to collapse
its simple to fix, your problem is simply cwm recovery, you need to use twrp to flash either of those rom's, so start there, recommended is 2.6.3.3, its the most problem free.
Code:
fastboot flash recovery recovery_name.img
fastboot erase cache
fastboot reboot-bootloader
then enter recovery, select wipe then format data, push or sideload a rom then flash it.
ViperOne Install Instructions
1. Download the the latest ViperOne full ROM zip from the download section
2. Place the file somewhere on your phone storage. Alternatively, if you have a USB OTG cable (I have this exact one), you can place the rom on a USB key (FAT32, NTFS are all supported).
3. Confirm the MD5 on the download page matches the MD5 of the file on your phone (ES File Explorer will show the MD5 of the file)
4. Reboot to TWRP Recovery
5. Backup current ROM if desired
6. Install ROM using TWRP and select wipe during aroma install if coming from another base
7. Reboot and Enjoy
Seanie280672 said:
its simple to fix, your problem is simply cwm recovery, you need to use twrp to flash either of those rom's, so start there, recommended is 2.6.3.3, its the most problem free.
Code:
fastboot flash recovery recovery_name.img
fastboot erase cache
fastboot reboot-bootloader
then enter recovery, select wipe then format data, push or sideload a rom then flash it.
ViperOne Install Instructions
1. Download the the latest ViperOne full ROM zip from the download section
2. Place the file somewhere on your phone storage. Alternatively, if you have a USB OTG cable (I have this exact one), you can place the rom on a USB key (FAT32, NTFS are all supported).
3. Confirm the MD5 on the download page matches the MD5 of the file on your phone (ES File Explorer will show the MD5 of the file)
4. Reboot to TWRP Recovery
5. Backup current ROM if desired
6. Install ROM using TWRP and select wipe during aroma install if coming from another base
7. Reboot and Enjoy
Click to expand...
Click to collapse
Ok I'm currently sideloading ViperRom but at first it was stuck at 2% so I cancelled it now it's stuck at 26% for like 30 min
radsherwin said:
Ok I'm currently sideloading ViperRom but at first it was stuck at 2% so I cancelled it now it's stuck at 26% for like 30 min
Click to expand...
Click to collapse
did you format data first ? any unable to mount messages, you could also try advanced wip and select everything in the list.
try pushing it instead
with the phone in twrp main screen only, no sub menu's and the rom in the same folder as adb and fastboot on your computer type:
Code:
adb push (name_of_rom).zip /sdcard/
takes a while and will look unresponsive, but the cmd window will let you know when its done. Make sure you unplug your phone before flashing.
Seanie280672 said:
did you format data first ? any unable to mount messages, you could also try advanced wip and select everything in the list.
try pushing it instead
with the phone in twrp main screen only, no sub menu's and the rom in the same folder as adb and fastboot on your computer type:
Code:
adb push (name_of_rom).zip /sdcard/
takes a while and will look unresponsive, but the cmd window will let you know when its done. Make sure you unplug your phone before flashing.
Click to expand...
Click to collapse
ok I 've been sitting here for a while and the cmd prompt just shows a blinking line under my command. The file is in my sdcard but is it complete?
Seanie280672 said:
did you format data first ? any unable to mount messages, you could also try advanced wip and select everything in the list.
try pushing it instead
with the phone in twrp main screen only, no sub menu's and the rom in the same folder as adb and fastboot on your computer type:
Code:
adb push (name_of_rom).zip /sdcard/
takes a while and will look unresponsive, but the cmd window will let you know when its done. Make sure you unplug your phone before flashing.
Click to expand...
Click to collapse
also it doesnt let me format data wipe. It gives me error like E: Unable to mount '/cache/
radsherwin said:
also it doesnt let me format data wipe. It gives me error like E: Unable to mount '/cache/
Click to expand...
Click to collapse
with your phone in fastboot, type fastboot format cache
Seanie280672 said:
with your phone in fastboot, type fastboot format cache
Click to expand...
Click to collapse
doesn't work either.. I tried everything nothing is working. I can't even get ViperOne Rom on my phone.
anyone? I need help! I'm looking all over the internet for solutions and apparently every has solved their problem but me. HELP!
Seanie280672 said:
with your phone in fastboot, type fastboot format cache
Click to expand...
Click to collapse
anymore help? When ever I try to ADB sideload It gets stuck on 1% forever. Whenever I try to adv push it does nothing and doesnt tell me anything. everytime I try to format It says successful but it still gives me error saying E: / cant mount cache. PLEASE HELP ME
radsherwin said:
anyone? I need help! I'm looking all over the internet for solutions and apparently every has solved their problem but me. HELP!
Click to expand...
Click to collapse
I recommend you start from scratch
from the bootloader / power down
wait a couple min and boot back to fastboot
plug the phone into the PC
from your command prompt type
fastboot devices
see your device serial number
type
fastboot erase cache
type
fastboot reboot-bootloader
now try sideload your rom from TWRP 2.6.3.3 /advanced/sideload
clsA said:
I recommend you start from scratch
from the bootloader / power down
wait a couple min and boot back to fastboot
plug the phone into the PC
from your command prompt type
fastboot devices
see your device serial number
type
fastboot erase cache
type
fastboot reboot-bootloader
now try sideload your rom from TWRP 2.6.3.3 /advanced/sideload
Click to expand...
Click to collapse
when I try fastboot erase cache it says
"******** Did you mean to fastboot format this partition?
erasing 'cache'...
FAILED (status read failed (Too many links))
finished. total time: 0.293s
So you have CWM / TWRP installed? Try copying a ROM to the external SD card, and install it that way. Clear everything in recovery first, cache, dalvik, etc... I had the same problem with the M8 and it drove me nuts until I did it all from the SD. If not, I would suggest trying the full RUU, it has saved me many a time.
hack14u said:
So you have CWM / TWRP installed? Try copying a ROM to the external SD card, and install it that way. Clear everything in recovery first, cache, dalvik, etc... I had the same problem with the M8 and it drove me nuts until I did it all from the SD. If not, I would suggest trying the full RUU, it has saved me many a time.
Click to expand...
Click to collapse
I have the m7 not the m8. So I have no sd card. What is the RUU method? I have TWRP installed right now.
This is getting on my nerves. Ive been sitting here for 6 hours and I posted 4 times and I still have not fixed this problem!!!!!!!! No one can explain clearly or respond to me even. Half my problems are being ignored. and half the things I say are being ignored.
radsherwin said:
I have the m7 not the m8. So I have no sd card. What is the RUU method? I have TWRP installed right now.
Click to expand...
Click to collapse
Oh that's right dang it. When I had my M7 I converted it to a Dev Edition by changing the CID and then using a file like this:
http://dl4.htc.com/RomCode/Source_and_Binaries/m7ul-3.4.10-g77e9ea0.zip
Mine was an ATT version so MID matched.
---------- Post added at 07:28 PM ---------- Previous post was at 07:27 PM ----------
radsherwin said:
This is getting on my nerves. Ive been sitting here for 6 hours and I posted 4 times and I still have not fixed this problem!!!!!!!! No one can explain clearly or respond to me even. Half my problems are being ignored. and half the things I say are being ignored.
Click to expand...
Click to collapse
Hey, hey, hey, patience my friend, we are here to help, ALL of us, we are trying.
Scratch that link, it doesn't like direct posts, find the Brighstar WWE RUU by searching at: http://www.htcdev.com/devcenter/downloads, or find the ATT, or TMobile. Not sure what your carrier is, but the Dev Edition is the way to go.
hack14u said:
Oh that's right dang it. When I had my M7 I converted it to a Dev Edition by changing the CID and then using a file like this:
http://dl4.htc.com/RomCode/Source_and_Binaries/m7ul-3.4.10-g77e9ea0.zip
Mine was an ATT version so MID matched.
---------- Post added at 07:28 PM ---------- Previous post was at 07:27 PM ----------
Hey, hey, hey, patience my friend, we are here to help, ALL of us, we are trying.
Click to expand...
Click to collapse
The link just sends me to the htc website. Also what does converting my m7 to dev edition do exactly? Will it help with the Sideload problem or the cant mount cache problem?
And I know you guys are trying to help me. Im just mad because everything I do is not working. Im searching all over the internet and nothing is helping. Errors lead to more errors. Reminds me of the time I tried learning progrramming and I made a simple program but It wouldnt work. I posted it on 3 websites and no one could help me. So I'm sorry for going off like that.
radsherwin said:
The link just sends me to the htc website.
And I know you guys are trying to help me. Im just mad because everything I do is not working. Im searching all over the internet and nothing is helping. Errors lead to more errors. Reminds me of the time I tried learning progrramming and I made a simple program but It wouldnt work. I posted it on 3 websites and no one could help me. So I'm sorry for going off like that.
Click to expand...
Click to collapse
I know it can be frustrating, but nothing you can do to the M7 can hurt it. Try the link above HTC doesn't like direct links.
hack14u said:
I know it can be frustrating, but nothing you can do to the M7 can hurt it. Try the link above HTC doesn't like direct links.
Click to expand...
Click to collapse
ok im doing it right now. Im AT&T btw.
I seem to have fixed the E: Can't mount cache problem. All i did was go to advance and click only on cache. Now all I need is to sideload or pus my ViperOne rom over to my HTC. Then hopefully nothing goes wrong. What do I do once the zip file is done downloading?
That might not be the right one, it should be an exe around 1 GB in size, sorry. Look around for it, if it's not still posted at the HTC Dev site, then it is around here somewhere. There are also some nandroids I have seen that should help you restore to stock. Nonetheless, once you have that Viper Rom on there, you should be able to flash anything you want. A full RUU will restore your phone to the state in which you bought it in, just like brand new.
Hi there!
I have a TX1085, it is already unlocked and rooted and has the CM Recovery installed. But before the CM Recovery I had the TWRP Recovery installed and tried to use it to flash CM12, which I had put on the SD-Card. It kept on telling me that mounting the system failed. Unfortunately I wiped everything via TWRP Recovery without creating a backup. Then I installed the CM Recovery to try again. Now, if I try to flash via CM Recovery (apply update) it doesn't show anything in my internal storage and I can't connect via adb using Ubuntu (Terminal tells me either "device not found" or "device offline".)
Any suggestions?
Greets
I have no idea what I'm talking about, I'm still learning all this, but in your case, from what I've learnend so far I'd maybe try the "fastboot boot recoveryfile.img" command, loading TWRP or CMrecovery into the ram of the phone and start flashing from there?! (just an idea)
psssss said:
I have no idea what I'm talking about, I'm still learning all this, but in your case, from what I've learnend so far I'd maybe try the "fastboot boot recoveryfile.img" command, loading TWRP or CMrecovery into the ram of the phone and start flashing from there?! (just an idea)
Click to expand...
Click to collapse
Thanks for your suggestion! Unfortunately I don't know how to get access to my phone again via computer, which is - I think - because I deleted the system on it. Or how else could I get into the ram? This is my first time to flash a phone, so I really need some guidance.
pyq said:
Thanks for your suggestion! Unfortunately I don't know how to get access to my phone again via computer, which is - I think - because I deleted the system on it. Or how else could I get into the ram? This is my first time to flash a phone, so I really need some guidance.
Click to expand...
Click to collapse
Go to bootloader first the use the commands fastboot boot recovery.img
Try using twrp, everybody is working with it now.
Sent from xt1096 with Marshmallow!
josuearisty said:
Go to bootloader first the use the commands fastboot boot recovery.img
Try using twrp, everybody is working with it now.
Sent from xt1096 with Marshmallow!
Click to expand...
Click to collapse
I tried, but the Terminal gives me that:"cannot load 'recovery.img': No such file or directory". I'm in fastboot, is that correct? Is there another way?
Right now I can't (or don't know how to) switch back to TWRP, but I'll keep it in mind. Thanks for your help!
did you installed android sdk and adb drivers? if yes try to open cmd in sdk directory
pyq said:
I tried, but the Terminal gives me that:"cannot load 'recovery.img': No such file or directory". I'm in fastboot, is that correct? Is there another way?
Right now I can't (or don't know how to) switch back to TWRP, but I'll keep it in mind. Thanks for your help!
Click to expand...
Click to collapse
Look for adb in 15 seconds and install it, go to directory where fastboot is located.
Download twrp image and rename it or something and copy recovery.img to fastboot directory.
If there is no recovery.img in that directory it will fail.
After you copy and rename recovery.img then you will be able to do what I told you.
If you are new at modding, you have to take it easy and ask everything before doing it.
Sent from xt1096 with Marshmallow!
kaktusmaier125 said:
did you installed android sdk and adb drivers? if yes try to open cmd in sdk directory
Click to expand...
Click to collapse
I am using Linux without Android SDK, but I have working fastboot and adb installed.
josuearisty said:
Look for adb in 15 seconds and install it, go to directory where fastboot is located.
Download twrp image and rename it or something and copy recovery.img to fastboot directory.
If there is no recovery.img in that directory it will fail.
After you copy and rename recovery.img then you will be able to do what I told you.
If you are new at modding, you have to take it easy and ask everything before doing it.
Sent from xt1096 with Marshmallow!
Click to expand...
Click to collapse
I managed to get TWRP working again. I have the .zip-File in my Internal Storage, but can not mount System. How can I do this?
Edit: Wiping data seems to be working but I get the output "E:Unable to mount '/system'". When I try to install the ROM it fails to mount an unmount /system and gets stuck at "Patching system image unconditionally..."
pyq said:
I managed to get TWRP working again. I have the .zip-File in my Internal Storage, but can not mount System. How can I do this?
Edit: Wiping data seems to be working but I get the output "E:Unable to mount '/system'". When I try to install the ROM it fails to mount an unmount /system and gets stuck at "Patching system image unconditionally..."
Click to expand...
Click to collapse
try to flash stock firmware
kaktusmaier125 said:
try to flash stock firmware
Click to expand...
Click to collapse
How do I do it? Just put the stock.zip on the phone and flash with TWRP?
pyq said:
How do I do it? Just put the stock.zip on the phone and flash with TWRP?
Click to expand...
Click to collapse
see this post http://forum.xda-developers.com/moto-x-2014/general/guide-return-to-stock-official-status-t3274121
what the model you have
---------- Post added at 09:32 AM ---------- Previous post was at 09:26 AM ----------
file factory is slow so try https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg!h9FWBQha
and flow this insturction http://forum.xda-developers.com/moto-x-2014/general/guide-return-to-stock-official-status-t3274121
pyq said:
How do I do it? Just put the stock.zip on the phone and flash with TWRP?
Click to expand...
Click to collapse
Next time, please ask everything you need before doing something.
I have been modding my phones since the Motorola L7 and I always ask for everything on a new device before start modding.
That way I never bricked my phones.
Sent from xt1096 with Marshmallow!
kaktusmaier125 said:
see this post http://forum.xda-developers.com/moto-x-2014/general/guide-return-to-stock-official-status-t3274121
what the model you have
---------- Post added at 09:32 AM ---------- Previous post was at 09:26 AM ----------
file factory is slow so try https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg!h9FWBQha
and flow this insturction http://forum.xda-developers.com/moto-x-2014/general/guide-return-to-stock-official-status-t3274121
Click to expand...
Click to collapse
This post seems to be aiming for Windows users, but I am using Linux. Could I still use it? If yes, how?
josuearisty said:
Next time, please ask everything you need before doing something.
I have been modding my phones since the Motorola L7 and I always ask for everything on a new device before start modding.
That way I never bricked my phones.
Sent from xt1096 with Marshmallow!
Click to expand...
Click to collapse
That is why I asked you how to get CM installed with TWRP. I had the mounting problem at the very beginning already. How can I get CM installed now?
pyq said:
That is why I asked you how to get CM installed with TWRP. I had the mounting problem at the very beginning already. How can I get CM installed now?
Click to expand...
Click to collapse
The commands I wrote before, use the same steps but instead use the cm recovery.
I hope you understand!
Sent from xt1096 with Marshmallow!
pyq said:
I managed to get TWRP working again. I have the .zip-File in my Internal Storage, but can not mount System. How can I do this?
Edit: Wiping data seems to be working but I get the output "E:Unable to mount '/system'". When I try to install the ROM it fails to mount an unmount /system and gets stuck at "Patching system image unconditionally..."
Click to expand...
Click to collapse
In the newer versions of TWRP the first screen should show a Mount button. In that screen you should be able to mount any of the partitions.
josuearisty said:
The commands I wrote before, use the same steps but instead use the cm recovery.
I hope you understand!
Sent from xt1096 with Marshmallow!
Click to expand...
Click to collapse
If I use the "fastboot boot CM_recovery.img" command the phone installs it and then starts into TWRP. Except for that nothing changes. How can I continue?
rotorbudd said:
In the newer versions of TWRP the first screen should show a Mount button. In that screen you should be able to mount any of the partitions.
Click to expand...
Click to collapse
If I try to make a tick (as to mount) system the phone vibrates but doesn't tick system, so I can't mount it this way.
pyq said:
This post seems to be aiming for Windows users, but I am using Linux. Could I still use it? If yes, how?
Click to expand...
Click to collapse
Yes you can