I don't know if anyone has experienced this but: I ran TP Toolbox to resize my partitions, and it performed a file system check. It ended up repair a LONG list of stuff, and now CM9 just bootloops. Is there anyway I can fix this short of reformatting? Obviously, I'd rather not if possible, as my installation is 6 years old or so and all my daughter's data is on it.
Related
I've gone thru the paces numerous times, even rolled a rooted install back to a full install of 1.0.1 and reapplied the HC v.4 (following all instructions carefully). I don't have any problems with the file extraction and get the Done message. However, when I reboot the nook it gives me a Loading screen then flickers a few times and then an ANDROID_ (flashing curson) and hangs. I've gotten this far every time I've tried to apply the zip. Once in awhile it will flash between the Loading and ANDROID_ screens a few times but ultimately I end up with ANDROID on my screen and nothing else.
Any ideas or direction I can move in? I'm anxious to try this out but prefer to run it from internal memory instead of an SD card...
There does seem to be one disparity between the instructions and the actual application of them, there doesn't appear to be a way to unmount /boot that I recall, only format it.
Make sure data and system have been formatted without issues before flashing the zip.
If that doesn't work, you might have a system partition size issue. Download shad0wf0x's stock image and dd it to your mmcblk0p5 partition (see specific thread). Then try flashing zip after having formatted both data and system.
Sent from my HTC Desire using XDA App
During the formats I haven't gotten any error messages, just a simple Done. when the format of each completes. I do hang when boot is done but a hard reboot, per the instructions, allows me to continue from there and I making sure /system and /data aren't mounted.
I'll give this a shot and let you know how it works out.
Thanks.
That didn't seem to do the trick. The last time I did this I started from a complete reinstall of 1.0.1 with an image I got from this thread.
http://forum.xda-developers.com/archive/index.php/t-914690.html
I'm able to boot into the stock install without difficulty, register the nook, setup my gmail association and then root. If I had a corrupted systems directory would I be able to do all those things?
I was using the AOSP ICS build posted by jt1134 (at rootzwiki dot com/topic/11697-rom-cdma-aosp-ics-cm9-build101-0418/) for the Galaxy Tab CDMA. The first couple of nightlies worked OK on the tablet, but the camera never worked right. Someone else insisted that the camera works correctly on new builds, so they suggested I use CWM to wipe system, and I took it to mean wipe everything so as to start from scratch, and I wiped /data too. Apparently this triggered the emmc erase bug or something, so now my internal SD is useless.
Nobody over in that thread appears to be willing to make a build that works around the issue. I've already tried partitioning my SD card and editing vold.fstab and updater.rc inside the ROM, but these are apparently useless unless init.rc in the boot image (zimage I guess) is changed. A person attempted that but seems to have gotten the filesystem type wrong in the build (ext2 instead of ext4), and is unwilling to make another attempt. I don't know anything about compiling a custom ROM myself. I've looked into decompressing/recompressing the zimage, but it's too much for me.
What I'm asking here is, can anyone help get a build of ICS to me that I can flash, that will ignore the internal SD and use the external? This site is awash with reports and fixes for Encryption Unsuccessful for other phones and tablets, so I'm hoping somene here can understand my frustration. I haven't been able to use the tablet for over a month now, I think, and I'm not getting anywhere on my own. TIA
Bump
I'm in the same boat after trying the same rom. I gave up on the old Tab, and doubt you'll get any help here. I'm still holding on to it in case Samsung releases a fix, but that might never happen.
PookiePrancer said:
I'm in the same boat after trying the same rom. I gave up on the old Tab, and doubt you'll get any help here. I'm still holding on to it in case Samsung releases a fix, but that might never happen.
Click to expand...
Click to collapse
Another fellow who had the same thing happen to him posted a guide over on rootzwiki on how to remove the offending chip. After removal you can partition an external SD and fiddle with a ROM and install it. The SD card will need 3 partitions, an ext4 /cache partition (not sure of the size of the regular one, made mine 512MB which I think is overkill), an ext4 /data partition (2GB is the default on these tablets), and the remaining space on the card can be used as the /sdcard partition (FAT). The only thing is I don't think you'll be able to go back to a stock rom ever again. There doesn't seem to be an easy way to change anything in roms that flash in heimdall or odin. CWM recovery based roms can be used, because they're just files in a zip. You have to change a few files referencing the locations of the partitions, including updater.sh and /system/etc/vold.fstab. On my tab the /cache is pointed at /dev/block/mmcblk0p1, the /data at mmcblk0p2 and the /sdcard at mmcblk0p3. I did manage to find a CWM recovery ROM that is based on CM7 GB 2.3.5 that works pretty good, but there are still some bugs with the camera (can't record video on front facing camera). I've resigned myself to sticking with this ROM, since it's otherwise completely stable for me, but I'm still trying to see if there's a way to transplant the working camera software from the verizon stock rom to replace the broken one I have now.
Thread for chip removal / rom installation:
rootzwiki dot com/topic/33743-external-sd-card-only-guide/
Thread for CM7 ROM "beta kang":
rootzwiki dot com/topic/4110-cdma-vzwtab-cm7-beta-kang-unofficial-1101/
Sorry about the broken links but I'm still too green on this forum to be trusted with posting actual links.
hi,
prior to today i had a cm9 + webos touchpad.
i did a lot of stupid things today, some accidental, some carelessly
now all my restore backups are gone (the worst that happened)
my cm9 still boots up.........., but i have 16gig of my 32gig touchpad "damaged"
and my webOS does still boot up, just that it takes about a good 40 min........
-----------------------------------------------
it all started when i decided i wanted to upgradd to Evervolv AOSP Android 4.3.1 JB (20131110)
before i began i wanted to make sure i have 512mb boot alloted, i followed and flashed the zip file
update-cm-tenderloin-system_resize_512-0.4.zip
but it didn't work, so i tried this other repartition zip from the thread
http://forum.xda-developers.com/showthread.php?t=2477806
sys_512mb_data_plus_16384mb-signed.zip
and now i can't get anything downloaded to do anymore upgrading because i don't have a sdcard established
---------------------------------------------------------------
i need a solution, but it must not involve using the micro usb port and a computer. that port has been dead for about a year now (which is why i didn't bother upgrade all this time)
anyone got a solution?
Have you tried using the WebOS program called Tailor? Tailor can resize partitions and attempts to 'fix' errors.
Do you guys know if tailor formats anything if i add space to my system partition?
Sent from my TouchPad using Tapatalk 4
BuffMcBigHuge said:
Do you guys know if tailor formats anything if i add space to my system partition?
Sent from my TouchPad using Tapatalk 4
Click to expand...
Click to collapse
I used tailor resizing my data partition. All my files are still there.
I have two HP Touchpads, a 16GB and a 32GB. Both have CM installed by me. The 16 ran for about a month and then crashed & won't reboot ("unfortunately Trebuchet has stopped"). It seems that /cache is corrupted but I have tried every function of TPToolbox and TWRP to repair delete resize or wipe and each one fails due to /cache problems. Reinstall also fails. Grateful for any insight / assistance.
Same problems on my wife's old unit. Tried almost every option and no go on retreading this tire. What's sad is if WebOS Recovery was still available, this would be an easy fix, but all my attempts running this process and doing a complete reset back to webOS have also filed. WebOS partially works, but repartitioning using Preware tools (Tailor) have also failed to fix corrupt storage.
Suspect I'll need Linux to ADM and reformat the partitions, but no go with this either and would love some help from some Linux junkie who may have a suggest.
Maybe someone can help both of us and please let us know if you make progress and I'll do same.
Sorli...
webOS recovery doesn't help me - reinstall fails
I can still boot webOS but it doesn't have much space. I bought a 32GB motherboard and am going to try installing it.
BB
Hi,
I recently exchanged my old 64 GB Nexus 6 for a new/refurbished one due to a failed USB port. I installed the latest stock ROM, unlocked the bootloader, rooted, and used Titanium Backup to restore the data to a handful of apps. While doing this, I got a warning about my device being low on space. From research, I learned that I should've disabled Mount Namespace Separation in SuperSU. So now, no matter what I do, my system files are taking up 35 GB after doing a complete wipe with TWRP and reinstalling the stock ROM.
Is this a problem with the partition table? No matter what the issue is, does anyone know how to fix it? I'm not super experienced with rooting beyond basic tasks, so I'm struggling to come up with ideas.
Thanks!
Nevermind!
It looks like resizing the partitions in TWRP fixed my problem. Sorry for being a noob .
For future reference, don't flash userdata.img in the stock images if you want to avoid resizing partitions in TWRP. That image resizes internal storage to 32GB and ignores the remainder, leading to /system taking more space than it should.