CWM has been updated officialy to 3.2.0.1! See the Changelog and FAQ below for more information!
Changelog:
3.0.0.5 - Initial official release for the nook. Only supported ext3. Had bootloop errors with the 1.1.0 update. (Note: Unofficial builds supported ext4 but not both at the same time)
3.0.0.6 - No significant changes to 3.0.0.5 officially. (Note: Unofficial builds supported ext3 or ext4 but not both at the same time)
3.0.0.8 - Broken build. Blame the samsung phones for messed up additions.
3.0.0.9 - Adds official support for ext4 as well as compatability for ext3. (i.e. No need to swap recovery for different ROMs). Fixes "Always boots into recovery" with 1.1.0 updated u-boot.bin
3.0.1.0 - Adds support to for /sd-ext to recovery.
3.0.2.8 - Sets /system to ext2. You can now backup and restore your stock roms! Delete/Update all 3.0.0.5 threads to point to 3.0.2.8 for all rom types. Rom Manager now pushes a recovery kernel as well as the ramdisk!! No need to manually install recovery kernel. Just flash the lastest from RomManager and you are done!
3.2.0.0 - Support for newer nooks with the 5G /data parition! New .32 kernel is included which fixes the freezing after formatting /data! (/data format issues. Don't Use)
3.2.0.1 - Fixes a bug with 3.2.0.0 (actually a build issue) where ext3 (/data and /cache) wouldn't be formatted properly (they were but CWM was bombing out)
*Recommended *
RomManager can now push the recovery kernel. No need to manually install via CWM or ADB! Flash from RomManager and rock and roll.
Q: Why should I upgrade?
As of the official version 3.0.0.9 there CWM supports both ext3 and ext4 ROMs with a single recovery image. This means no more of this swapping back and forth between different versions of CWM! 3.0.2.8 sets /system to ext2 to allow for proper backing up and restoring of stock roms!
This version also fixes issues with the 1.1.0 version of u-boot.bin. Some with this version may experience that your NookColor will always boot back into RomManager. This is now fixed (as of 3.0.0.9)
Click to expand...
Click to collapse
Q: But I have CWM <insert older version> I am good right?
Always use the latest found on this post or on RomManager. Older version are not supported
Click to expand...
Click to collapse
Q: I used RomManager to install CWM but now i can't use backup or restore
This should be fixed. Report any issues to me either on this thread or via PM
Click to expand...
Click to collapse
Q: I upgraded CWM and now my market doesn't work.
Installing CWM doesn't alter any rom or data files which shouldn't have any affect on recovery. There is something else that may have affected your market.
No worries though you can try the following to try and fix it:
If you are using CM7. Upgrade to the latest nightly (which will be after tonight: 3/3)
Try clearing the following: For "My Apps," go to manage apps, market, uninstall updates, clear market cache. Then delete data for Google Framework Services.
Click to expand...
Click to collapse
Q: I have upgraded but now I am having issues?
So some of you are still having issues with this new CWM version. PLEASE PLEASE PLEASE give me the following information:
What you are trying to do/accomplish. Be as detailed as possible
What rom you are running and what rom you are upgrading to (if applicable)
IMPORTANT! Grab a recovery.log from your nookcolor. You can do this either through adb or through the advanced menu. If I don't have this then there is little I can help with.
Click to expand...
Click to collapse
Q: How do i grab the recovery.log?
Method 1: ADB
After setting up adb type:
Code:
adb pull /tmp/recovery.log
You are done. (This is why everyone should learn and setup ADB. It really is stupid simple)
Method 2: Save from the menu
From the ClockworkMod Recovery main screen do the following
Select 'Advanced'
Select 'Report Error'
There is now a copy of recovery.log on your sdcard. Transfer the sdcard to a computer or boot into your rom and mount your sdcard on your computer.
Click to expand...
Click to collapse
Thank you Nemith
i flashed this earlier today, at first it kept bootlooping so i used the remove CW zip and got rid of it. The 2nd install went fine (both times i rebooted before booting into CW)
however CW says it cannot mount system so i'm unable to make a full backup
davidukfl said:
i flashed this earlier today, at first it kept bootlooping so i used the remove CW zip and got rid of it. The 2nd install went fine (both times i rebooted before booting into CW)
however CW says it cannot mount system so i'm unable to make a full backup
Click to expand...
Click to collapse
What rom are you running?
Nice! Thanks!
Sent from my DROIDX using Tapatalk
nemith said:
TL;DR: If you use RomManager go upgrade it in RomManager NOW!
Click to expand...
Click to collapse
My RomManager still sees 3.0.0.5 as the latest version.
Chahk said:
My RomManager still sees 3.0.0.5 as the latest version.
Click to expand...
Click to collapse
I provided a link/instructions to manual flash cwm. This may help.
Stock 2.1 rom
Sent from my DROIDX using Tapatalk
davidukfl said:
Stock 2.1 rom
Sent from my DROIDX using Tapatalk
Click to expand...
Click to collapse
Grab /tmp/recovery.log from your device after you try to do a nandroid backup.
Thanks!
Excellent! I 'll have a new installclockwork.zip and universal bootable sd out here as soon as I get back from skiing
Thanks!
Thanks for the info. I have been waiting for this.
So I'm stuck in the CM boot loop. Can I install from the boot-looping CM or do I flash it from the SD loaded CM?
No problem either way, just curious what the best approach is?
Moar gees with gginggerbread and tapatalk!
John Kotches said:
So I'm stuck in the CM boot loop. Can I install from the boot-looping CM or do I flash it from the SD loaded CM?
Click to expand...
Click to collapse
Either should work since both are ran from RAM.
Can the img file be written to an SDcard? Also, can Nandroids made with 3.0.0.5 be restored using the update?
Homer
nemith said:
Grab /tmp/recovery.log from your device after you try to do a nandroid backup.
Thanks!
Click to expand...
Click to collapse
the tmp folder is empty. In the clockwork folder on the SD card the boot.img file is in there though.
When i create a backup it says cannot mount system, and when i got to advanced and hit mount system it says the same thing
Homer_S_xda said:
Can the img file be written to an SDcard? Also, can Nandroids made with 3.0.0.5 be restored using the update?
Homer
Click to expand...
Click to collapse
Yes. There is nothing special about the images written to an sdcard. You can even rename the files to uImage and uRamdisk to have it boot without the two-finger salute on the sdcard.
davidukfl said:
the tmp folder is empty. In the clockwork folder on the SD card the boot.img file is in there though.
When i create a backup it says cannot mount system, and when i got to advanced and hit mount system it says the same thing
Click to expand...
Click to collapse
There should always be a /tmp/recovery.log. You need to grab this while in recovery via adb
Code:
adb pull /tmp/recovery.log
nemith said:
Either should work since both are ran from RAM.
Click to expand...
Click to collapse
I'll probably shove remove cw onto the bootable sd card and then push cw again from rom manager.
Moar gees with gginggerbread and tapatalk!
I can't mount /system either. Using CM7. I also have a dual-boot partition, but I doubt that matters.
from log:
mounting /system!
W:failed to mount /dev/block/mmcblk0p5 (No such device)
Error mounting /system!
Also:
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:failed to mount /dev/block/mmcblk0p7 (No such device)
edit: Here's the full pastebin
Updated rom manager with cm7 nightly 7. Worked flawlessly.
Related
Okay, I've seen a few people and various threads with this problem:
1. They have a rooted Optimus V
2. they may or may not have flashed a recovery
3. they download ROM Manager and select ROM Manager's Clockwork Recovery
4. they flash a rom and reboot
5. they get stuck in a recovery loop and run around screaming.
This was me yesterday!!
What did I do, then? I downloaded the Fastbootroot tool. That got rid of the ROM Manager's CW Recovery and put in thunderc-v-1.1.0 version recovery... that looped. I tried the 1.2.0 version, which also looped, but I could flash a different recovery, finally. So I downloaded Xionia's Clockwork Recovery and THAT worked. (this next excerpt is from my androidcentral forum post)
here's exactly what I did starting from the thunderc-v-1.2.0 recovery (i'm gonna go into too much detail for other eeijits like me):
download xionia's clockwork recovery and the flash image, unzip both onto your sdcard
put your desired rom on your sdcard (zipped, omg)
get out of usb storage mode
Get ADK Tools if you don't have it (search the forum, this is the easy stuff)
Make sure you're all mounted in mounts and settings in your current recovery.
open cmd, and get into adb shell
(this next part is from zefie's post)
enter the following commands:
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
# cat /sdcard/flash_image > /system/bin/flash_image
# chmod 755 /system/bin/flash_image
# mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system
# flash_image recovery /sdcard/xionia_cwma_12518.6.img
# reboot recovery
it should reboot into xionia's clockwork recovery mod
clean dalvik cache and mount everything
choose 'fix recovery loop' under ... advanced IIRC, I can't check right now as I'm reloading my stuff onto the fixed phone
after the loop's fixed, get back into recovery and load whatever ROM you fancy.
WIN!
Recovery loop from ROM mgr backup restore...tried Kiona, tried mmarz, what next?
Newb here...BUT, in my defense...I DID NOT DO AN ANDROID SYSTEM RESTORE ON MY ROOTED PHONE!! which seems to be most people's problems with boot/recovery looping. My phone is stuck in a recovery loop after restoring a Clockworkmod backup.
History: I rooted my LG Optimus V running 2.2.2 with gingerbreak a couple of months ago. Per all instructions I could find, I installed SuperUser, Rom Manager, Titanium Backup, I also have another backup by Rerware, but I can't remember the name of it. I kept the stock ROM. Everything has been working fine.
I got a 32 gig micro card for Christmas. So, as per instructions found elsewhere, I made a backup to my sd card with ROM Manager, Titanium and Rerware. I copied my sd card to my hard drive, partitioned my new sd card, and loaded the new sd card with the old sd card data. At that point everything looked fine. But the instructions said to restore from my backup which I did with clockworkmod and now I am stuck in a recovery loop.
I completed Kionia CWMA install 1..4 and performed "Fix Recovery Boot Loop" but it did not fix the issue.
I completed Kionia CWMA install 1..6 and performed "Fix Recovery Boot Loop" but it did not fix the issue.
I completed the abd shell instructions "strings/dev/mtd/mtd8" and "flash_eraseall /dev/mtd/mtd8" per mmarz but it did not fix the issue.
I have recovery access. I have ADB running.
What should I do next? Everyone else seems to be fixed with mmarz's suggestion...
Thanks to whoever is out there for any help...
rom manager is mostly no good on V and the new V screen {after sept.} gets ruined alot by rom manager, so i wouldn't use it
get a compatible recovery at the iho wiki and install
then flash the rom of your choice
if that doesn't work there is lots of help for this in the optimus v "development" section
Thanks for your reply. I just wasn't sure what I should do next and your suggestion worked perfectly. And I guess I had to get over the fact that I was going to have to restore from scratch and get over my fear of installing a custom ROM. Luckily, of all the backups I had, Titanium worked BEAUTIFULLY! I was chicken to flash a custom ROM, but I flashed IHO Harmonia and it is beautiful and has been working flawlessly ever since. I shouldn't say flawlessly, I kept getting some gapps error but I was able to look it up easily and fix it.
Live and Learn.
the latest version of rom manager in market has bug... so we can use older version search on google. And it works again
Sent from my LG-P500 using xda premium
I am having a problem when flashing any .zip inside the /sdcard directory. CWM keeps reporting status 0 and aborts the installation. I have tried creating a soft link to the directory so that CWM would read it but installation will never succeed. I am currently using GingerMod and have tried formatting both phone storage and the external sd card. May I ask what is causing this problem and if there is any solution to it?
Thanks in advance.
From the GMod thread: http://forum.xda-developers.com/showpost.php?p=20993382&postcount=2207
@ABOUT STATUS 0 ERROR:
this is sadly a combination of a Kernel and a Package problem...
The binary for the updaters are old, so with the kernel will not work..
BUT
if you change kernel will work
I'll revise them when have a day free, for now use the unmount/mount system trick or change kernel
Click to expand...
Click to collapse
If you want to retain the current kernel do the underlined part.
thanks so much. didn't read thoroughly enough. gave you thanks too!
how to:
unmount/mount system trick ??????
hornetxp said:
how to:
unmount/mount system trick ??????
Click to expand...
Click to collapse
From recovery; it's under mounts and storage if I recall correctly.
My device:
Vpad7 w/ Android 2.2.1
Baseband version PR3.7_125
Kernel version Apps_2.6.32.9
Build number 1008_3_240
SWVer=3.240
Model: FM6-0001
HWVer=107
Desired ROM: EUViewpad7v1.7b-ITE
I tried to follow the [READ FIRST] Vpad7 Dev's thread.
1- Root was ok, su successful (SOC 1.7 and antivirus off);
2- Copied all partitions to sdcard was ok;
3- Error copying flash_image to /system/bin (read-only file system)
solved with:
mount -o remount,rw /dev/block/mtdblock4 /system
cp /sdcard/flash_image /system/bin
chmod 755 /system/bin/flash_image
flash_image recovery /sdcard/cwrecovery.img
4- EUViewpad7v1.7b-ITE.zip copied into sdcard and renamed to update.zip;
5- Backup stock ROM on dev's recovery mode ok;
6- Select 'apply sdcard: update.zip' on dev's recovery mode, with success;
After reboot, the VP7 shows the 3 birds logo, and after that shows an endless animation, on which is a kind of telephone's cabin flying through a cloud tunnel. (no, i'dont use drugs!). The android's graphic interface isn't loaded.
I restored rom bkp from sdcard by dev's recovery mode with success.
Could I use the EUVpad7v1.7b without a previous EUVpad7v1.7 ?
What's going wrong?
It takes a while to load first time. For me it did. I also had a problem like that and had to mount system with latest CMW
What's your CWM's version?
Sent from my ViewPad7 using xda premium
My version is 5.0.2.6
indyend said:
What's your CWM's version?
Sent from my ViewPad7 using xda premium
Click to expand...
Click to collapse
almartin said:
My version is 5.0.2.6
Click to expand...
Click to collapse
Mine is 2.5.1.2
could this be causing that problem?
thks u
indyend said:
What's your CWM's version?
Sent from my ViewPad7 using xda premium
Click to expand...
Click to collapse
almartin said:
My version is 5.0.2.6
Click to expand...
Click to collapse
My CWM's version is 2.5.1.2
I'll try a newer one.
I tried w/ the CWM 5.0.2.6, but after "flash_image recovery /sdcard/cwrecovery i've got an error (No space left on device).
When i use the CWM 2.5.1.2 (from XDA dev's tutorial), flash_image recovery is completed with success.
Is there an intermediate version that solve this issue?
thanks!
Weird. Did you factory reset and wipe?
almartin said:
Weird. Did you factory reset and wipe?
Click to expand...
Click to collapse
That's it!
We get, but when i start the recovery mode on VP7, the CWM version shown is 2.5.1.2 yet! As a newbie i thought to install a new CWM only the "flash_image recovery /sdcard/cwrecovery.img" command was necessary to.
I didn't forget to copy new cwm (downloaded here: http://forum.xda-developers.com/showthread.php?t=1288223 - is it the rigth version?) to sdcard.
Do you have an idea to apply that change?
lucadiq said:
That's it!
We get, but when i start the recovery mode on VP7, the CWM version shown is 2.5.1.2 yet! As a newbie i thought to install a new CWM only the "flash_image recovery /sdcard/cwrecovery.img" command was necessary to.
I didn't forget to copy new cwm (downloaded here: http://forum.xda-developers.com/showthread.php?t=1288223 - is it the rigth version?) to sdcard.
Do you have an idea to apply that change?
Click to expand...
Click to collapse
Yeah!
I gave up to change CWM version. After searching here, i found a very good step by step for newbies (http://forum.xda-developers.com/showthread.php?t=1224825). My 2.5.1.2 CWM has worked fine!
The problem is that i was forgetting to create the ext partition to App2SD, probably.
Thread closed.
CWM Newer than 2.5 maybe cause of some error.
Sent from my ViewPad7 using xda premium
CWM 5.8.0.9 for Huawei MediaPad
WARNING !!! DON'T FORMAT AND DON'T WIPE PARTITIONS USING THESE CWM !
I don't know how much this CWM version improves over the existing one by segler11.
However these build were more aimed at compiling and testing the new kernel sources.
I have tested compiling with both arm-eabi-4.4.0 and arm-eabi-4.4.3 with success on Ubuntu 10.04.
This is experimental, however with the new kernel sources it will just be a matter of time.
I have compiled the kernel included in this CWM recovery image but I didn't recompile the complete image.
I took as base Pyramid CWM 5.8.0.9 and I replaced the files from those found on a stock C232B005 kernel.
As the default build configuration I have used the /proc/config.gz of a C232B005 running kernel.
I have tested this CWM to be able to backup these partitions (I have not tested "restore" yet, just checked the tar archives):
boot.img - 12.582.912 (match 12Mb)
recovery.img - 16.777.216 (match 16Mb)
data.ext4.tar
cache.ext4.tar
system.ext4.tar
custom.ext4.tar
as you can see my hand tweaks to "recovery" require the name of "cust" partition to be "custom" instead but I believe this is a no issue while you backup and restore with the same CWM. Suggestions welcome.
BUGS:
data & time on archives are wrong
mount USB storage does not work
adb not enabled in recovery mode
Formats and Wipes do not work don't use them
The "busybox hwclock" applet doesn't work to set the hardware clock of our device.
The "adb shell" is not active while in CWM recovery, I don't know why and this was my objective so if you have suggestion please help.
As usual flash both "recovery" and "recovery2" partitions using "fastboot" and one of the attached CWM recovery:
Code:
fastboot flash recovery recovery-5.8.0.9-HWMOD-eabi-4.4.3.img
fastboot flash recovery2 recovery-5.8.0.9-HWMOD-eabi-4.4.3.img
fastboot reboot
WARNING !!! DON'T FORMAT AND DON'T WIPE PARTITIONS USING THESE CWM !
.:HWMOD:.
.
Reserved CWM HWMOD
This version seemed to work better for me.Tnx dude!
john9 said:
This version seemed to work better for me.Tnx dude!
Click to expand...
Click to collapse
Thank you for trying it.
Remember to absolutely avoid formatting or wiping partitions.
If you need to format/wipe do it ONLY after reinstalling the original "recovery.img" in both "recovery" and "recovery2" partitions and then reset the device from:
"Settings -> Backup and reset -> Factory reset"
ATTENTION !!! You can safely do a wipe or factory reset only after reinstalling the original recovery image.
Sorry for insisting but I don't want to create problems on users devices and I know those operations will create problems.
.:HWMOD:.
Just a note: I used your 4.4.3 version to try making a nandroid backup last night. Good news and bad news.
This morning I inspected the result using the app Nandroid Browser.
Good: Your CWM does successfully backup /data/data. The other CWM that had been posted here did not do so properly.
Bad: Your CWM also backs up the entire internal SD storage contents inside the folder /data/share. It is customary *not* to include this in a nandroid backup because a) you don't want to inflate the file size unnecessarily, and b) you don't want to overwrite the internal SD on a restore.
Idea: After you fix it, and until you manage to get ADB over USB working, maybe you could add a menu option to make a separate backup archive of internal SD to external SD. This would allow a route to save the internal storage if the device becomes unbootable and requires a data wipe.
cmstlist said:
Just a note: I used your 4.4.3 version to try making a nandroid backup last night. Good news and bad news.
This morning I inspected the result using the app Nandroid Browser.
Good: Your CWM does successfully backup /data/data. The other CWM that had been posted here did not do so properly.
Bad: Your CWM also backs up the entire internal SD storage contents inside the folder /data/share. It is customary *not* to include this in a nandroid backup because a) you don't want to inflate the file size unnecessarily, and b) you don't want to overwrite the internal SD on a restore.
Idea: After you fix it, and until you manage to get ADB over USB working, maybe you could add a menu option to make a separate backup archive of internal SD to external SD. This would allow a route to save the internal storage if the device becomes unbootable and requires a data wipe.
Click to expand...
Click to collapse
Thank you for trying it. I wanted to compile/test a kernel with new sources in a CWM.
Yes, in our device the internal memory "/mnt/sdcard" is also mapped under "/data/share".
Unfortunately I don't have the skills (yet) to build a complete recovery image from scratch,
so what I did was just compiling the kernel part of the recovery image, using the new sources.
Then I simply hex tweaked the "recovery" executable of a 5.8.0.9 Pyramid CWM (HTC Sensation).
So, in conclusion, I have no control over what is copied during the backup process of those partitions.
Though I could control which partition is processed by removing them from "fstab", but there is no gain into it.
We will have to wait somebody with the specific knowledge, or maybe I will have some time to learn once I return from holidays.
.:HWMOD:.
Today i have builded bootable CWM 5.5.0.4 from sources, so now we can adjust all what we need
after_silence said:
Today i have builded bootable CWM 5.5.0.4 from sources, so now we can adjust all what we need
Click to expand...
Click to collapse
well done
HI, can anyone share buckup from working device created by CWM.?
Thanks to all.
Hi,
Is it possible to flash update zips from this CWM recovery (like Beats Audio which is in flashable zip format)?
I don't want to use it for backup-recovery.
...and how about doing wipe cache and wipe dalvik cache?
.dredd. said:
Hi,
Is it possible to flash update zips from this CWM recovery (like Beats Audio which is in flashable zip format)?
I don't want to use it for backup-recovery.
...and how about doing wipe cache and wipe dalvik cache?
Click to expand...
Click to collapse
Haven't tried installing a ".zip" archive from CWM but it should work.
Avoid "wiping" and/or "formatting" partitions, they will be messed up.
hwmod said:
Haven't tried installing a ".zip" archive from CWM but it should work.
Avoid "wiping" and/or "formatting" partitions, they will be messed up.
Click to expand...
Click to collapse
The main reason for use of CWM would be to have the possibility of flashing update zips from CWM... but I am afraid of messing up my device... to understand: no problem if I have to reflash the rom but I would not want to cause mistake which could be repaired only by service.
fastboot is always available if something goes wrong and if you flash cwm you wont be able to install official roms because cwm will overwrite stock recovery
so i was stupid and wiped data and cache - then remembered that it said not to - how do i fix this paperweight? i tried fastbooting all the usual partitions (system, boot, userdata, cache, etc) but still nothing - i can get to fastboot but i cant flash any dload updates. any suggestions are greatly appreciated.
flash stock recovery (2 files) from zipped rom via fastboot and then you should be able to flash stock rom
flashed three different stock recoveries to recovery and recovery2 - still only get the media pad logo twice (flashed androidani intl rom before bricking) cant boot to recovery - think the partition table is screwed. is there a way to create partitions from fastboot, and if so, still would be nice to know the names of the partitions to flash as referenced in tmo stock thread.
byt3b0mb said:
flashed three different stock recoveries to recovery and recovery2 - still only get the media pad logo twice (flashed androidani intl rom before bricking) cant boot to recovery - think the partition table is screwed. is there a way to create partitions from fastboot, and if so, still would be nice to know the names of the partitions to flash as referenced in tmo stock thread.
Click to expand...
Click to collapse
The time needed to reformat and rewrite all the firmware partitions (the first time) will be between 10-15 minutes.
Be patient and give enough time to the device to execute all the needed processes.
When the device finally boot it need to completely regenerate dalvik-cache (the first time).
So try again as instructed above, rewrite "BOTH" partitions named "recovery" and "recovery2", both using the same "recovery.img" file found in the latest stock Huawei firmware.
Now extract the stock Huawei firmware archive on your PC and copy the "dload" folder on an empty formatted SDCard, then insert the SDCard in the MediaPad reboot it and wait until success or failure message.
If you wiped partitions you will have to wait more time (20-30m). It may be that after waiting a while a message about "Encryption not possible" could appear, just say no to encryption and let it reset the device.
It already happened to some of us so hope you are also able to recover your tablet.
thanks i will give it a shot - while it is rewriting partitions, should it be on the huawei logo? or should i see the android / gears turning?
byt3b0mb said:
thanks i will give it a shot - while it is rewriting partitions, should it be on the huawei logo? or should i see the android / gears turning?
Click to expand...
Click to collapse
First time restoration takes time on both moments during the 1st Huawei log and even during animation.
Trying to recover a partition that was wiped takes much longer for the OS to show the error.
When I tried wiping "data" and rebooted the device I recall I went for a long walk and when I returned the device was showing the "Encryption failure / Reset" message (about half an hour later).
So I can only suggest that when you retry you wait at least that amount of time (30 min.) with charger connected, whatever happens leave it alone until it display or ask you do something. Let me know if it works when you have tried.
Download links do not work for me. Can you upload in mediafire please?
Hey everyone,
A few days ago, I decided to downgrade from AICP 11 back to 10 (Android 6.0.1 to 5.1.1), wiped everything but internal storage. When flashing, I got an error, saying that the /vendor partition was missing, and indeed, while it existed, I could only mount it forcefully, because the device was busy.
This lead to a complete wipe, as after a reboot, TWRP asked for an encryption password, which I didn't set. Here, I did a factory reset & wiped everything. After that, I tried flashing again (5.1.1), but after it was completed, I got a line, which said "Couldn't unmount /system", which is true, as it's already unmounted. But when I mount it, all the files that are supposed to be installed seem to be there.
When I reboot the device, it gets stuck on the Google logo.
Frankly, I'm afraid to even flash back to stock, so I was hoping that someone more experienced could help me out.
It should be noted, that I still have access to fastboot, and TWRP.
Thanks in advance,
DecentM
How did you force mount /vendor?
Can you clarify where you are seeing these problems? (TWRP or within Android)
Do you have any nandroid backups to test and see if they work?
dmantilal said:
How did you force mount /vendor?
Can you clarify where you are seeing these problems? (TWRP or within Android)
Do you have any nandroid backups to test and see if they work?
Click to expand...
Click to collapse
I used mount -f and umount -f in the TWRP terminal
I see all these problems in TWRP, since I can't boot/get past the initial Google logo.
I do have a nandroid backuip on my laptop (as I had to wipe the tablet clean), but that's currently unavailable for me to use, I'll reply back when I tried it.
I doubt it will work, because it just extracts data to a predefined path, which seems like the same thing an installer zip does.
DecentM said:
I used mount -f and umount -f in the TWRP terminal
I see all these problems in TWRP, since I can't boot/get past the initial Google logo.
I do have a nandroid backuip on my laptop (as I had to wipe the tablet clean), but that's currently unavailable for me to use, I'll reply back when I tried it.
I doubt it will work, because it just extracts data to a predefined path, which seems like the same thing an installer zip does.
Click to expand...
Click to collapse
Why did you need /vendor mounted in TWRP?
I thought flashing used dd (command) or similar to copy the *.img file to the partition (or, more accurately, the block device). If /vendor is mounted during *.img copy, that would most likely cause errors.
dmantilal said:
Why did you need /vendor mounted in TWRP?
I thought flashing used dd (command) or similar to copy the *.img file to the partition (or, more accurately, the block device). If /vendor is mounted during *.img copy, that would most likely cause errors.
Click to expand...
Click to collapse
I mounted it, because when I initially restored the 5.1.1 rom, I got an error, saying that the /vendor partition wasn't mounted.
DecentM said:
I mounted it, because when I initially restored the 5.1.1 rom, I got an error, saying that the /vendor partition wasn't mounted.
Click to expand...
Click to collapse
You are sure it was complaining about "unmounted", rather than "mounted"?
Do these roms include a vendor.img? You may need to flash the stock 5.1.1 vendor.img.
Either way, unless you mkfs'ed or resize2fs'ed the partitions, they should be fine. Full wipe & go.
dmantilal said:
You are sure it was complaining about "unmounted", rather than "mounted"?
Do these roms include a vendor.img? You may need to flash the stock 5.1.1 vendor.img.
Either way, unless you mkfs'ed or resize2fs'ed the partitions, they should be fine. Full wipe & go.
Click to expand...
Click to collapse
I'm not sure.
I already did a full wipe, but it still had issues. I'll try again tomorrow, and report back on how it went.
DecentM said:
I'm not sure.
I already did a full wipe, but it still had issues. I'll try again tomorrow, and report back how it went.
Click to expand...
Click to collapse
Having a mismatched vendor.img could be your problem.
No ROM I know of includes a vendor.img. I think it is a legal issue, like including GApps with a ROM.
dmantilal said:
Having a mismatched vendor.img could be your problem.
No ROM I know of includes a vendor.img. I think it is a legal issue, like including GApps with a ROM.
Click to expand...
Click to collapse
I don't think that the issue is with the vendor image anymore, but with the partitions in general. I always had a mismatched vendor image, as it only results in a modal box after boot.
My problem is again, with the /system partition not being visible to flashable zip files.
Mismatched vendor.img can also cause bootloops and other quirks like battery-charge percentage inaccuracies.