[Q] Need help with internal memory partition structure on Incredible - Droid Incredible Q&A, Help & Troubleshooting

I have an Incredible, rooted (and I have issues)... I appear to have repartitioned my internal memory area. Thankfully, the phone is useable, but it's not quite right as some programs don't work properly, the video recorder hangs hard, and I have either corrupt data or areas stomped on by other areas due to incorrect partition information. If certain files get touched, then the phone immediately protects itself by flagging the internal memory as read only. I did find a workaround to the phone automatically going into ReadOnly at boot by simply adding a ".nomedia" file in the root of MP3 (where some corrupt files happen to reside). As long as the system doesn't touch the files, the file system remains R/W.
I stupidly did this to myeself. I did it while using a Partitioning tool (specifically Acronis, making a "secure zone") on my PC while my incredible was charging in the USB port and I accidentally used the wrong drive. It was one of those "oh crap" moments. If I connect the phone to my PC, the internal drive comes up as being unformatted and windows asks if I want to format. Another disk utility (EASEUS) sees the drive, can show how its partitioned, and I can explore within the partitions to see that files exist.
I've been searching for a long while to find someone somewhere who might have info on how to fix the Internal SD partition information, but have yet to find anything. Reflashing the factory ROM, "factory reset", etc. appear to just repopulate the already partitioned areas. The closest thing I have found to my problem is a post called "Challenge to members... Help me fix internal partitions without recovery" on the Incredibleforums elsewhere (can't post external links yet). Unfortunately, trying those solutions doesn't fix the issue. That post deals with /dev/mount/mmcblk0p1 and /dev/mount/mmcblk0p2. My issue appears to be in /dev/mount/mmcblk0p3. Parted doesn't like that one much. I have attached a couple of files that show parted output for all of the drives that get mounted, per /etc/fstab & /etc/recovery.fstab. This was done in ADB while the phone was booted into recovery.
If anyone can point me in the right direction how to properly (and safely) repartition the *internal* areas back to how they should be, I'd really appreciate the help!
Thanks,
Blue

I ran across this:
http://talk.maemo.org/showthread.php?t=15746
.... hope it helps send you in the right direction anyway. Good luck!

Formating instructions i think it would be a better idea to try using the ruu.exe tool to reflash your phone and it should format that partition back and put all the old apps it came with back in proper order. Since the phone is use able right now you could also try a factory reset first if you don't want to try the ruu.exe.

Thanks for the link and tip for RUU.
sfdisk does not appear to be a useable command on my DInc. Is there an Android version/port? Also, that link suggests that the partition should be msdos, but isn't the boot sector type supposed to be ext2/3 or yaffs2 (?) on the DInc?
I have already tried the factory reset as well as reformatting the phone areas using CWM Recovery (3.0.0.8). I also reflashed a factory stock ROM found in the lastest RUU. I also flashed the 2nd to latest ROM from that RUU (2.1). All of these only reformatted and re-installed stock ROM. Unfortunately, doing so only reformats the existing partitions, but does not fix the screwed up partition sizing. As far as I can determine, setting my phone back to S-ON and running the RUU will do nothing different than what I did by placing the stock PB31IMG.zip in the root of my (external) SD card and flashing it from HBOOT.
If the RUU truly repartitions the internal memory, then I'm game to set S-ON and try that. However, all indications are that doing so will be no different than flashing PB31IMG.zip. Is that correct?
Thanks again,
Blue

Related

[Q] CDMA; attempting to replace the recovery

Please bare with me, as there's a lot to explain. I am in dire need for your help.
Starting off, my specs are as follows:
HTC Desire CDMA from U.S. Cellular
Rooted via Unrevoked (with unrevoked forever)
Current Recovery: ClockworkMod 2.5.0.9
Current ROM: CyanogenMod 6.1.0
Current SD: 8GB
The phone is barely over a week old. I rooted it last week, flashed Cyanogen, and customized everything. Well one thing I wished I had done before was partition a part of my SD to allow for more internal phone space. Even with
Cyanogen's FroYo (2.2.1) capability to move apps to the SD, I kept running a thin line on low memory. This is because, as most of you know, not the entire app is moved. I was faced with the decision of removing apps that I frequently used, or look for other storage solutions.
I found out that there was a way to make the phone think it has extra memory by partitioning a part of your MicroSD card to an Ext3. I researched how to do this with the tools I already had available (this being ROM Manager & ClockworkMod). I first tried ClockworkMod's recovery, which give me the option to partition the SD. I selected 512MB for the size (it's more than enough for me) and a swap size of 0. It completes, and I reboot the phone. I checked the internal storage space, and it's still low (< 15MB). Upon more research, I found that it may have only been an Ext2, and not Ext3. Upon plugging my phone back into the USB/Computer, I noticed the overall size for my MicroSD went from 7.5x GB to 6.9x GB. If the partition didn't work like I wanted, I wanted my space back.
So for hours I scour the forums with nothing helpful in return. I tried Partition Magic to try and merge the partition back to my original card, but it couldn't see it. It only saw a SD card that was 6.9x GB. So further research showed me that ClockworkMod was pretty bad at partitioning the SD card to Ext3, and everyone suggested AmonRa. I found a version of AmonRa that was designed for the HTC Desire. I placed the .img file on the root of my SD card and opened up ROM Manager. The option to "Flash Alternate Recovery" was greyed out, despite the fact that the image was on my SD Card (which was mounted; USB Storage for the PC was turned OFF). So further reading said I needed the premium version of Rom manager. I bought it, installed it, and re-fired it up. The option is still greyed out.
Frustrated, I look for alternate methods. I found one that recommended Terminal and the flash_image script.
I tried doing this with the AmonRa recovery image (which I renamed to recovery.img on my SD card). I rebooted into recovery, but instead of ClockworkMod or AmonRa appearing, I just got the HTC logo with the white
background where it would ultimately freeze. I performed a hard reset and tried again. Same thing. I reboot, went into ROM Manager and tried flashing ClockworkMod 2.5.0.9. It said it installed, so I reboot into recovery. Same HTC Logo freeze.
Freaking out, I tried other solutions, involving one where I placed a script on my SDcard. From there, I would go into Terminal and type the following:
su
sh /sdcard/FR-flashRec-v03.txt
And after the 2nd or 3rd time trying this, I reboot my phone, and instead of going into recovery, it dumps me back into Fastboot. Every time I tried selecting Recovery from bootloader, it would take me to Fastboot. I'm freaking out about now. So I fired up Unrevoked, the tool I used to originally root my phone. After the 2nd attempt, it successfully flashed ClockworkMod back to my phone.
Relieved but still unsolved, I continue to look for a reason why I'm not able to flash a different recovery image. Then I found a thread which dates back to June 2010 and applied to the CyanogenMod 5.0.x Eclair build. There was a disclaimer that read:
DO NOT USE ROM MANAGER TO FLASH YOUR RECOVERY.
DO NOT USE flash_image SCRIPT TO FLASH YOUR RECOVERY IN THE LIVE SYSTEM.
So I figured the problem was with my current ROM. Sure, that referred to CyM 5.0.x, and I'm running 6.1, but there was no documentation saying that the issue had been fixed, and there weren't any other threads regarding my issue.
Not wanting to take a risk losing my current recovery, I restored a backup from my stock ROM I received from U.S. Cellular. I installed ROM Manager and tried to flash the recovery image via the "Flash Alternate Recovery". The option was once again greyed out. I bought premium again and still, the option is still greyed out.
Running out of ideas, I restored my CyanogenMod state I made before I did any changes. And this is where I am.
I'm running out of internal phone space rapidly.
[*]I don't know how to restore the partition I made to get my SD storage space back (in fact, since I made that partition, it's been slower).
[*]I don't know how I can flash AmonRa, or if it's even possible with CyanogenMod.
[*]I don't know how to use ADB shell.
I found a site that has a collection of AmonRa images, and for the Desire, they have the following: recovery-RA-desire-v2.0.0-AW.img, recovery-RA-desire-v2.0.0-CM.img, and finally recovery-RA-desire-v2.0.0.img. I don't know which one I need to install for my HTC Desire CDMA.
If you've made it through this entire thread. Thank you. I really need some answers, and I don't know where else to look or to even ask. Can you please help me?
First of all making a ext partition won't magically provide more space, there is more behind it. See the second post in this thread under 'Still low storage for apps'.
And the partition made with rom manager should be fine however if you want something else use Gparted (can run of a linux live cd so no need to install anything)
For the restoring of the partition also use Gparted.
Not 100% sure but i believe that with unrevoked you can flash a alternative recovery image even if you are already rooted, but if you use Gparted there is no real reason for doing so.
For adb there are enough tutorials.
Hmm, many of these AmonRa releases are designed for HTC Desire GSM. Will these releases also work for CDMA devices?
Also, GParted will not work under Windows 7, and I don't use linux. All these other partitioning programs cannot detect the missing 1GB from my 8GB MicroSD. I have no idea how to restore it.

Complete SD Card Corruption with A2SD+

Hi,
Tonight I installed some updates for apps on my phone running Leedroid 2.2d A2SD+. Some of them stubbornly decided to stay on the SD card so I went to move them (I haven't managed to get pm setInstallLocation 1 to work, though I have yet to try it from ADB and that was the way I got setInstallLocation 2 to work before I rooted). I moved several at once and suddenly had the applications manager restart itself and found one of my games that was being moved (Cordy) was no longer working and couldn't be moved either to or from the phone (said move failed). So I tried restarting the phone incase that would fix it.
The phone wouldn't get past the HTC logo so I thought it might be a corrupt A2SD partition, but since it was ext3 that I could probably just get fsck on the computer to replay the journal. Upon putting the card in the computer (using an SD adapter) and booting into Ubuntu 10.10 I tried running disk utility with 'check filesystem' and it reported an error and that the filesystem was not clean and changed the partition to unknown. The same thing happend for the FAT32 partition and I couldn't mount that either. I tried running fsck from a terminal and it said something along the lines of 'Bad superblock or possible short write' and was unable to check the partitions and exited immediately (sorry I have since rebooted and assumed the same error would occur next time so didn't write it down specifically).
I restarted into Windows 7 to see if it could fix the FAT32 partition so I could get my Nandroid backup I made yesterday and it worked fine and said the partition was fine! Usefully Nandroid makes an md5 checksum of the backup so I was able to confirm at least that was intact and make a copy (I didn't really have anything else not backed up on the card as I only rooted a week ago).
I then rebooted back into Ubuntu and it now reports the FAT32 partition as clean, and actually makes some attempt at repairing the EXT3 partition but reports huge quantities of nasty errors like multiply allocated blocks and allocated blocks marked as free and an error with the journal when I run from terminal using 'fsck -t ext3 /dev/sdb2'. I don't really have any experience with fsck as I mostly use windows but there were a lot of errors that sounded pretty unresolvable (from memories of my couple of lectures on ext at university).
Yesterday I flashed an UOT theme using (ClockworkMod 2.5.0.7 as installed by Unrevoked3) install from zip for battery percentage and some icon changes, I chose Leedroid 2.3d from the file list. I had also installed DSPManager using the flashable zip on the Leedroid site.
My card was partitioned using GParted with FAT32 first followed by a 512MB EXT3 partition as recommended on the Leedroid site. I was sure to create the EXT3 partition second as I noticed adding it first at the end made it the first partition in the table. The card had been made a goldcard (though this might be gone as I erased the card with disk utilities Format drive button which may have deleted the MBR, I'm not really sure).
I'm guessing somehow Android tried to do multiple writes at once but I was under the impression these kinds of issues were solved by putting the partitions in the correct order, besides, shouldn't Andorid work correctly with its built-in support for ext anyway like any other version of linux? If this is a known, common problem with A2SD+ why doesn't every ROM have a big warning about this like Data2SD ROMS generally have about SD wear and being able to persist system settings?
PS: I realise there are some other threads on this but they are fairly old and seem to all involve connecting the phone to the computer or after a reboot.

[Q] DHD cant mount/read SD card!!!

Ok I have a rooted DHD running Cyanogenmod 7. Everything worked fine until I wanted to do a complete factory reset to just sort of clean the slate. I did do a backup of Titanium backup before I did it.
The process went like this I clicked the power button went into reboot recovery and clicked on wipe data/ factory reset, then everything finished. It then rebooted with cyanogenmod 7 which was ok and saw that my SD card wasnt erased.
So what I did was did another factory reset through settings. Then the phone restarted and cyanogenmod 7 starts up and now it cant read my SD card it says its either blank or unsupported file format.
What happened? anyway to recover it?
YAY!!!!!
Figured it out!!! What i did was i went down to the local store looking into buying a new SD card. I asked him if he could check to see if the SD card worked before I bought another one, so he stuck the SD card into his computer with one of those MicroSD to SD adapters and it popped up on his screen and he reformatted it and viola it was done and now my DHD recognizes it. Also he gave me the adapter for free sweet!
I have the same issue and have NOT solved it!
I had flashed the latest LeeDrOiD GB ROM (after doing ext4 wipe) and made a mistake, which ended up with my phone reverting itself back to stock after a wrong selection in bootloader. DOH!
Anyways, after my very brief experience on GB....and very good it was too - my phone was back at 1.32.405.6 with the standard radio.....absolutely back to bog standard.
I was advised on another thread that it was because id left an old stock rom on the SD card ........
After, again seeking advice on here, i removed the PD98.IMG file from the SD Card root. I then set about trying to re root and eng s-off/ radio s-off. This went smoothly ( to the best of my knowledge) i reloaded ROM manager and CWM and booted into recovery. This step went smoothly right up until i tried to select the .zip from the /sd card but an error came up saying something like " E:Can't mount /sdcard"
I rebooted the DHD and got the same message again I decided to copy over the card contents to a temp folder on my laptop and formatted the SD card with default settings and then copied back the card contents. This did not work either.
I have another sd card that i have also tried after formatting and i get exactly the same result. The cards contents are fine and can be read on either PC or laptop. I believe there is a setting/fault on the handset itself.
I dont know whether it has anything to do with SuperCID, as i did opt for that option when using the radio s-off tool.
i am now stuck with a DHD that is useless......
PLEASE HELP SOMEBODY......PLEASE????
Ive been trying literally since 8Oclock this morning..............
There may be a cash reward involved for the solution leading to my systems recovery......
All The best
@ LandUzu
Have you checked the settings in menu / settings / SD & phone storage / mount sdcard
If already mounted, try unmount / mount
Edit2:
If you can't boot system;
Turn off phone & boot into bootloader (Hold vol down, keep pressed & then press power button once)
Recovery
Mounts & storage
Are you able to "mount USB storage" and see the 'drive' on your PC, or able to "mount sdcard" as well?
Also try;
Removing battery for a bit (not too sure what effect, if any)
Remove sdcard and physically look in the sdcard slot (use strong light) for bad / damaged contacts
Edit3:
* FULL format (not quick) in PC sdcard to fat32 default allocation
Sent from my Desire HD using XDA Premium App
Thanks for your suggestions......
UpInTheAir said:
@ LandUzu
Have you checked the settings in menu / settings / SD & phone storage / mount sdcard
If already mounted, try unmount / mount
Edit2:
If you can't boot system;
Turn off phone & boot into bootloader (Hold vol down, keep pressed & then press power button once)
Recovery
Mounts & storage
Are you able to "mount USB storage" and see the 'drive' on your PC, or able to "mount sdcard" as well?
Also try;
Removing battery for a bit (not too sure what effect, if any)
Remove sdcard and physically look in the sdcard slot (use strong light) for bad / damaged contacts
Edit3:
* FULL format (not quick) in PC sdcard to fat32 default allocation
Sent from my Desire HD using XDA Premium App
Click to expand...
Click to collapse
Hi there UpInTheAir,
Thanks for your suggestions, but i have already tried all of them prior to posting mate.
If i look via settings> sd & storage the card is 'unavailable' to mount or unmount.
If i attempt a mount via bootloader>recovery, i get 'Error mounting /sdcard'
And if i try to mount USB storage, i get 'E:Unable to write ums lunfile (No such file or directory)'
See why im banging my head against the wall?!
The contacts dont appear to be in any particular bad way and i have given it a good blow down the gap in case there was any dust........just cant work it out. The worst bit about all this, is that i had Lee's GB rom running SWEET n SMOOTH when i decided to reboot and all this happened. Im GUTTED!!!
Any further suggestions apart from send it back to HTC?
Regards
Most research points to a bad sdcard. But as you've posted earlier, you've tried two and both work on the PC.
If you cannot find a better or simple solution,...........have another idea;
Flash a stock RUU via PC. I helped Turkish Soldier try a couple months ago, but his was really bricked as his bootloader was already corrupted. We gave it a try, but the phone didn't end a communicating with the PC, so was back to HTC unfortunatey. But yours is different, you still have root & ENG S-off, so should work.
If the sdcard is still not accessable after, maybe it is a hardware fault.
Follow this guide:
[GUIDE] Installing RUU's
Follow the guide exactly and you should be right. Basically, you DL the test ROM and extract the 1.15 Utility. DL the 1.32 RUU and use the 1.15 utility to push it to your phone.
You can also DL the 2 required ROM's from here:
http://shipped-roms.com/index.php?category=android&model=Ace
If all goes well;
You'll need to do all the Visionary - S-Off - ENG S-Off etc again if your able to mount the sdcard. If not, I don't know, as I said, maybe hardware fault.
I hope someone comes up with a simple solution for you, best of luck
Thanks again,
UpInTheAir said:
Most research points to a bad sdcard. But as you've posted earlier, you've tried two and both work on the PC.
If you cannot find a better or simple solution,...........have another idea;
Flash a stock RUU via PC. I helped Turkish Soldier try a couple months ago, but his was really bricked as his bootloader was already corrupted. We gave it a try, but the phone didn't end a communicating with the PC, so was back to HTC unfortunatey. But yours is different, you still have root & ENG S-off, so should work.
If the sdcard is still not accessable after, maybe it is a hardware fault.
Follow this guide:
[GUIDE] Installing RUU's
Follow the guide exactly and you should be right. Basically, you DL the test ROM and extract the 1.15 Utility. DL the 1.32 RUU and use the 1.15 utility to push it to your phone.
You can also DL the 2 required ROM's from here:
http://shipped-roms.com/index.php?category=android&model=Ace
If all goes well;
You'll need to do all the Visionary - S-Off - ENG S-Off etc again if your able to mount the sdcard. If not, I don't know, as I said, maybe hardware fault.
I hope someone comes up with a simple solution for you, best of luck
Click to expand...
Click to collapse
Thankyou for this lifeline, i will try right now and report back my out come.
Cheers matey.
LandUzu said:
Thankyou for this lifeline, i will try right now and report back my out come.
Cheers matey.
Click to expand...
Click to collapse
Well thew results are in, and they aint good!! i tried both methods in that tut and neither could awaken the acknowledgement of the /sdcard by the DHD.
Im now intrigued more than upset as to what is causing the lack of comms between the 2, but that is a quirk of modern technology i guess.
Thanks again UpInTheAir for your valued assistance. I think we can safely say the DHD is f**ked.
I have organised a repair and hope to hell my carrier doesnt replace it with an unflashable software version number!!!
Kind Regards & thanks once again.
LandUzu
No worries.
I did you manage to "downgrade" to stock RUU via PC ?
Or you downgraded, but sdcard still wouldn't mount?
If you managed to flash the stock somehow, would have removed the CWM recovery & HBOOT. All I think you need to do now is use jkoljo's tool to S-On, and it will be stock as, except for your sdcard-DHD-sdcard inoperable.
To go back to S-ON:
Flash stock ROM (RUU, not over 1.7)
Temproot using Visionary
Use my tool, do Stock CID and S-ON (enter brand CID if you had a branded device, see second post)
Enjoy your factory-state phone
Click to expand...
Click to collapse
Just to be safe, check with another card at the HTC service center, never know........
Sorry I can't help further, never know, could be an easy fix somewhere, but seems unlikely.
Managed to downgrade but still no cigar!!
UpInTheAir said:
No worries.
I did you manage to "downgrade" to stock RUU via PC ?
Or you downgraded, but sdcard still wouldn't mount?
If you managed to flash the stock somehow, would have removed the CWM recovery & HBOOT. All I think you need to do now is use jkoljo's tool to S-On, and it will be stock as, except for your sdcard-DHD-sdcard inoperable.
Just to be safe, check with another card at the HTC service center, never know........
Sorry I can't help further, never know, could be an easy fix somewhere, but seems unlikely.
Click to expand...
Click to collapse
Thanks, i didnt know whether to bother doing that or not, may as well save any hassle from the carrier or HTC.
Ive been searching the house high and low for an sdcard to tes....out of interest, what is the minimum suitable size for the DHD to run (basics)
Regards
LandUzu
I have read somewhere in the downgrade forums that a min of 2gb needed for goldcard, but as for as actual use goes, not to sure. In any case full format fat32 default allocation prior to any test.
Sent from my Desire HD using XDA Premium App

[Q] Error when formatting /data...

My phone was working fine until I upgraded two apps (I can't recall which ones) and my phone rebooted on its own; weird. I am running CM7 BTW.
I figured "No problem, I'll just flash my backup through Clockworkmod; not so. I keep getting "error formatting /data" regardless of any wipe, format I do.
I am not sure what to do from here. Please help. Searching revealed some RUU advice, but those were in other phone forums and I want to make sure I don't screw this up.
evil_elf said:
My phone was working fine until I upgraded two apps (I can't recall which ones) and my phone rebooted on its own; weird. I am running CM7 BTW.
I figured "No problem, I'll just flash my backup through Clockworkmod; not so. I keep getting "error formatting /data" regardless of any wipe, format I do.
I am not sure what to do from here. Please help. Searching revealed some RUU advice, but those were in other phone forums and I want to make sure I don't screw this up.
Click to expand...
Click to collapse
What version of cwm are you using?
Sent From My Optimized HTC Incredibly Dinc
It was the orange, but I upgraded it to see if it would work. uh, oh, as I write this, I fear worse...
Upgrading changed cwm to blue, but still same problems. It is almost as if the data directory has no write permissions.
I got impatient and used the ruu.exe from pvillecomp and now it gets stuck at the red eye droid screen and is on a reboot loop.
I can't get into recovery now, I get the phone icon with the red ! triangle. I figure cwm is gone now, so what, use unrevoked again? This would flash a new recovery, correct? Otherwise, how would I get the zip file onto the sd card now to flash via hboot? Even with a cwm, I imagine I will have the same formatting issues, unless the rom upate utility corrected those.
evil_elf said:
My phone was working fine until I upgraded two apps (I can't recall which ones) and my phone rebooted on its own; weird. I am running CM7 BTW.
I figured "No problem, I'll just flash my backup through Clockworkmod; not so. I keep getting "error formatting /data" regardless of any wipe, format I do.
I am not sure what to do from here. Please help. Searching revealed some RUU advice, but those were in other phone forums and I want to make sure I don't screw this up.
Click to expand...
Click to collapse
Try manually mounting /data before wiping it.
EDIT: Nevermind just read your other post about loosing cw recovery. Are you still s-off?
yeah, I tried every combination of mounting and formatting and it always failed with the same message. I am still S-off, so I imagine from here I can use unrevoked to flash cwm back onto it then I can try to restore from a saved ROM I have on my card. Should I do that?
I could copy the file to flash cwm file to my card instead I guess, but my card would have to be FAT32 I assume.
Well I flashed ClockworkMod 5.0.2.0 using HBOOT and now I am back to my original problem: Error while formatting /data! I can mount /data, but not format it, even through the mount menu option. Any ideas?
I don't know much about the file structure but does this not seem like a permissions issue to you guys? Fix permissions in CWM and factory resets don't help either.
evil_elf said:
Well I flashed ClockworkMod 5.0.2.0 using HBOOT and now I am back to my original problem: Error while formatting /data! I can mount /data, but not format it, even through the mount menu option. Any ideas?
I don't know much about the file structure but does this not seem like a permissions issue to you guys? Fix permissions in CWM and factory resets don't help either.
Click to expand...
Click to collapse
Do you have a ext2/3/4 partition on your sdcard?
cmlusco said:
Do you have a ext2/3/4 partition on your sdcard?
Click to expand...
Click to collapse
By partition, do mean directories? I formatted the card to FAT32 but did not partition it in any way. I don't believe I had separate partitions on it before, but I could be wrong. Wouldn't the partitions have shown up in my Windows OS when I plugged the card in to the reader?
evil_elf said:
Well I flashed ClockworkMod 5.0.2.0 using HBOOT and now I am back to my original problem: Error while formatting /data! I can mount /data, but not format it, even through the mount menu option. Any ideas?
I don't know much about the file structure but does this not seem like a permissions issue to you guys? Fix permissions in CWM and factory resets don't help either.
Click to expand...
Click to collapse
factory reset in hboot is different. It will probably wipe programming so you'll have to *228 1 and *228 2 to yet reprogram your phone. It'll probably wipe sdcard and emmc too. I've not tried so this is at your own risk. see if there are better options first.
Sent from my ADR6300 using Tapatalk
tiny4579 said:
factory reset in hboot is different. It will probably wipe programming so you'll have to *228 1 and *228 2 to yet reprogram your phone. It'll probably wipe sdcard and emmc too. I've not tried so this is at your own risk. see if there are better options first.
Sent from my ADR6300 using Tapatalk
Click to expand...
Click to collapse
I've already tried it before. It did not touch my card but did reset my phone's programming.
The restore function in CWM only touches the internal memory, correct?
evil_elf said:
By partition, do mean directories? If so, yes. I formatted the card to FAT32 but did not partition it in any way. I don't believe I had separate partitions on it before, but I could be wrong. Wouldn't the partitions have shown up in my Windows OS when I plugged the card in to the reader?
Click to expand...
Click to collapse
No windows would not see it if its there you would need to use a program called "gparted" on your pc to get rid of it or reformat it. Also when you tried the factory reset from hboot were you on a stock recovery then or cwm?
cmlusco said:
No windows would not see it if its there you would need to use a program called "gparted" on your pc to get rid of it or reformat it. Also when you tried the factory reset from hboot were you on a stock recovery then or cwm?
Click to expand...
Click to collapse
I tried the Factory Reset from HBOOT and also the Wipe Data/Factory Reset from CWM. Occasionally I am getting the 5 vibrations and a black screen when trying to turn off and on; battery pull allows me to boot up into ROM or HBOOT.
CM7 is working now, but the hard button bindings are screwed up along with a bunch of other stuff. CWM is able to restore the system, but fails on data so it makes sense. I can't receive calls either. I was so hoping the ruu would have fixed this...
The card should have no bearing on flashing a ROM? Or am I not understanding this?
Oh, I also tried to restore and format data manually without the card in to no avail. The Wipe Data/Factory Reset formats the data folder without errors but not the manually method of formatting or the restore method.
Could this help? http://forum.xda-developers.com/showthread.php?p=18287267
Just tried this: http://forum.xda-developers.com/showthread.php?t=1006556
Still same error.
To return my phone under warranty to a Verizon store, do I need to make sure that the stock ROM is flashed and the phone is unrooted with S-ON again? I am starting to think this is the route I am heading down and I only have a week left on my warranty.
Very short answer.........YES!!!
A kind soul helping me at http://forum.cyanogenmod.com/topic/32272-error-formatting-data-when-restoring/
*Possible Solution* If still an issue
If it is still an issue I had the same problem with my incredible.
I was playing a racing game on my phone and it just restarted on its own. When I turned it back on the phone had reset itself. Every time I would restart the phone from then on it would delete every thing I had saved like it was doing a factory reset. So I tried to do a wipe and restore and no luck. I kept getting the same errors you were getting in clockwork. I also tried the e2fsck commands from the link in the prior post and no luck.
1. I got a working HTC Incredible and booted into recovery and mounted all partitions.(/system, /data, etc.)
2. Then I used adb to pull the filesystem from the working phone with this command.
c:\android\adb pull / filesystem
This puts all the files from the phones root folder into a folder named filesystem in the same directory as the adb files.
3. After that finished I hooked the phone with the messed up partitions to the computer, booted into recovery, and mounted all partitions.
4. Then I used adb to push the filesystem from the working Incredible to the Incredible with the messed up partitions with this command.
c:\android\adb push c:\android\filesystem /
5. When it finished I rebooted the phone. It booted up and I got a few force close errors but nothing major, so I restarted and booted into recovery. When I tried to format /data it formatted like it should have.
6. Finally I downloaded the stock+ rooted rom and flashed it with clockwork and the phone booted up fine with no force closes and doesn't reset after reboot.
This worked for me and should work for anyone else that has this filesystem problem.
Can i get those files?
i dont have a working incredible. can you post a link to the working filesystem.
Thanks.
androidi1 said:
If it is still an issue I had the same problem with my incredible.
I was playing a racing game on my phone and it just restarted on its own. When I turned it back on the phone had reset itself. Every time I would restart the phone from then on it would delete every thing I had saved like it was doing a factory reset. So I tried to do a wipe and restore and no luck. I kept getting the same errors you were getting in clockwork. I also tried the e2fsck commands from the link in the prior post and no luck.
1. I got a working HTC Incredible and booted into recovery and mounted all partitions.(/system, /data, etc.)
2. Then I used adb to pull the filesystem from the working phone with this command.
c:\android\adb pull / filesystem
This puts all the files from the phones root folder into a folder named filesystem in the same directory as the adb files.
3. After that finished I hooked the phone with the messed up partitions to the computer, booted into recovery, and mounted all partitions.
4. Then I used adb to push the filesystem from the working Incredible to the Incredible with the messed up partitions with this command.
c:\android\adb push c:\android\filesystem /
5. When it finished I rebooted the phone. It booted up and I got a few force close errors but nothing major, so I restarted and booted into recovery. When I tried to format /data it formatted like it should have.
6. Finally I downloaded the stock+ rooted rom and flashed it with clockwork and the phone booted up fine with no force closes and doesn't reset after reboot.
This worked for me and should work for anyone else that has this filesystem problem.
Click to expand...
Click to collapse
Here try this one http://dinc.does-it.net/Touch_of_Blue/filesystem.zip, im interested to see if this works for you too. It seems quite a few people have been having issues with /data latley.
I get error
Code:
push: filesystem/sys/devices/platform/android_pmem.0/power/wakeup -> /sys/devices/platform/android_pmem.0/power/wakeup
failed to copy 'filesystem/sys/devices/platform/android_pmem.0/power/wakeup' to '/sys/devices/platform/android_pmem.0/power/wakeup': Operation not permitted
i get this error trying to push the filesystem. any workaround?

[Q] Unable to find files internal storage?

Hello Again, I have found a few threads with the same issue but something in the middle is different, this has happened on my Nexus 5 before, and it pissed me off because i never got it resolved.
I want to convert my HTC One M8 ATT to GPE later today, but first i'm on sense with NvROM.
The ROM isn't the issue since it's been working fine for a 2 weeks now, here is the story.
What i did-
Recovery (Wanted to try out CarbonROM)
Flashed LiquidSmooths kernel ontop of Carbon, got "Unfortunately phone has stopped".
Went to recovery again to attempt to flash liquidsmooth only.
E: Unable to mount /data
E: Unable to mount /system
E: Unable to mount /cache
E: Unable to mount /sdcard
E: Wiping /data /system /cache failed!
Now, i rebooted and those errors are non existent i can flash again.
But on LiquidSmooth , The Gallery can not find my Pictures.
The Music app can not find the music anymore.
Whenever i use a File Manager , magically my files are still there.
Anybody got ideas on this one? Thanks.
>Pics related<
Try to connect the phone to a PC, and use Device Manager to format the internal memory. Backup any personal data first, if needed (and if possible).
I've heard that , that causes the eMMc or internal storage to go into Read Only mode?
anyone correct me when i`m totally wrong here.
hasn't this something to do with the so called fused location of your sd-card ?
On my phone the locations of the sdcard is shown different then when i locate them trough recovery or shell.
In android the location is something like: /root/storage/sdcard (internal memory)
the real location in my case was shown in recovery as: /root/storage/emulated/0/
And i think because i had previously installed a cm11 based rom and kernel.
And when i completely wiped my phone for a newly rom, afterwards i still had all my data on my phone, because it didn't wipe the /emulated/0 location.
so all the files are still found with a file manager because the two location i mentioned before are fused. But your apps still has the old location in his settings somewhere..
You can try to do a media rescan so your phone search for new media.... But i believe that is also done when you reboot your phone.
I had that happen to me and I was able to fix it by using the "Format" option in TWRP recovery. That, of course, wipes everything on the device but everything will be mounted correctly and properly again.
Guys, I ended up fixing it.
TWRP format fixes it but i needed a backup. Also first attempt at formatting it on TWRP had issues. E:Can't format , E: Data isn't mounted.
Ended up just going ahead and doing the Google Play Edition Conversion and that fixed the whole issue, Thanks for your time!
@TarekElsakka @djmarkd @redpoint73
i4GS said:
Guys, I ended up fixing it.
TWRP format fixes it but i needed a backup. Also first attempt at formatting it on TWRP had issues. E:Can't format , E: Data isn't mounted.
Ended up just going ahead and doing the Google Play Edition Conversion and that fixed the whole issue, Thanks for your time!
@TarekElsakka @djmarkd @redpoint73
Click to expand...
Click to collapse
so wait, aren't you going to tell us what you mean by it fixed the whole issue? were you able to back up the data first?
I'm having a slightly different (maybe similar) issue.. my at&T m8 was working fine on insertcoin (previously viper/venom) and i decided to try a very stock AT&T debloated rom.
forgot to flash the firmware first, so booted into fastboot, and was going to do that.. but it wouldn't work, gave me an error..
booted back into recovery (TWRP 2.7.0.2) and my internal storage WILL NOT MOUNT. hence, nothing works... I can see microSD files, I can attempt to flash things ,but, due to the internal "sd" (not my microsd, just using old fashioned android terminology) not mounting, every operation fails. interestingly, I can mount / (root partition) and it has the correct structure, and even some vestiges of my files.. when i say mount, i mean in recovery on the device.. not on a computer via USB.
any ideas? i'm stuck
I know i can probably format the /media/data blahblah partition (the internal storage) but I have very important photographs of my best friend's wedding and my children's recent visit to their grandparents'.. so i really really want to restore those files.. I do this kind of thing (file forensics) on OSX, windows, and some linux drives, all the time at work.. I just don't know how to access the storage on an android phone, in order to run the forensics scans etc.
thanks!!
sneef said:
so wait, aren't you going to tell us what you mean by it fixed the whole issue? were you able to back up the data first?
I'm having a slightly different (maybe similar) issue.. my at&T m8 was working fine on insertcoin (previously viper/venom) and i decided to try a very stock AT&T debloated rom.
forgot to flash the firmware first, so booted into fastboot, and was going to do that.. but it wouldn't work, gave me an error..
booted back into recovery (TWRP 2.7.0.2) and my internal storage WILL NOT MOUNT. hence, nothing works... I can see microSD files, I can attempt to flash things ,but, due to the internal "sd" (not my microsd, just using old fashioned android terminology) not mounting, every operation fails. interestingly, I can mount / (root partition) and it has the correct structure, and even some vestiges of my files.. when i say mount, i mean in recovery on the device.. not on a computer via USB.
any ideas? i'm stuck
I know i can probably format the /media/data blahblah partition (the internal storage) but I have very important photographs of my best friend's wedding and my children's recent visit to their grandparents'.. so i really really want to restore those files.. I do this kind of thing (file forensics) on OSX, windows, and some linux drives, all the time at work.. I just don't know how to access the storage on an android phone, in order to run the forensics scans etc.
thanks!!
Click to expand...
Click to collapse
Sorry, but what i did was different, and MIGHT factory reset your internal storage, i can't verify 100%.
You can do two things,
Either flash the RUU
for 4.4.3 STOCK HTC [ATT]
or Flash Google Play edition RUU and revert back to sense which will fix it too.
SENSE: http://forum.xda-developers.com/showthread.php?t=2733523
GPE: http://forum.xda-developers.com/showthread.php?t=2708589

Categories

Resources