[Q] Installing multiple recoveries - TouchPad Q&A, Help & Troubleshooting

Installed CWM 6.03.6-datamedia recovery to install CM11 (Milaq) 12/24 CM11 ROM build. And then did a nandroid backup and backed up apps and system data with TiBU.
Now I wish to install several other new Kit Kat experimental ROMs (Evervolv and invisiblek) to test how the updated Kernel upgrades are coming along.
To prepare for the Evervolv ROM I installed open-recovery TWRP 2.6.3.0 (Sep12-2013). Was very easy to install TWRP by renaming as uImage.TWRP and copying to /boot. (thanks for the info from nevertells)
But not sure how to install Invisiblek CWM update which supports SE Linux as required by invisiblek ROM.
cwm_selinux_6.0.5.4_datamedia.uImage
I renamed the new recovery as "uImage.cwm_selinux_6.0.5.4_dm" and moved to /boot. And indeed it appears in the moboot menu. But when I select it I observe the following error:
Loading '/boot/uImage.cwm_selinux_6.0.5.4_dm' ... OK
Checking uImage... Invalid Size
I've re-downloaded and re-installed twice and the issue repeats itself.
I do not wish to destroy my existing CWM 6.0.3.6 (non selinux) recovery install.
So is it possible to install the newer CWM recovery so both CWM recovery tools can coexist and be accessible via the moboot menu at the same time?

woodytrain said:
Installed CWM 6.03.6-datamedia recovery to install CM11 (Milaq) 12/24 CM11 ROM build. And then did a nandroid backup and backed up apps and system data with TiBU.
Now I wish to install several other new Kit Kat experimental ROMs (Evervolv and invisiblek) to test how the updated Kernel upgrades are coming along.
To prepare for the Evervolv ROM I installed open-recovery TWRP 2.6.3.0 (Sep12-2013). Was very easy to install TWRP by renaming as uImage.TWRP and copying to /boot. (thanks for the info from nevertells)
But not sure how to install Invisiblek CWM update which supports SE Linux as required by invisiblek ROM.
cwm_selinux_6.0.5.4_datamedia.uImage
I renamed the new recovery as "uImage.cwm_selinux_6.0.5.4_dm" and moved to /boot. And indeed it appears in the moboot menu. But when I select it I observe the following error:
Loading '/boot/uImage.cwm_selinux_6.0.5.4_dm' ... OK
Checking uImage... Invalid Size
I've re-downloaded and re-installed twice and the issue repeats itself.
I do not wish to destroy my existing CWM 6.0.3.6 (non selinux) recovery install.
So is it possible to install the newer CWM recovery so both CWM recovery tools can coexist and be accessible via the moboot menu at the same time?
Click to expand...
Click to collapse
Your /boot partition does not have enough space for cwm_selinux_6.0.5.4_datamedia.ulmage, and you will need to clean up your /boot partition to make room for it.

goog888 said:
Your /boot partition does not have enough space for cwm_selinux_6.0.5.4_datamedia.ulmage, and you will need to clean up your /boot partition to make room for it.
Click to expand...
Click to collapse
I tried "cwm_selinux_6.0.5.4_datamedia.uImage", but it does not work with uImage.CyanogenMod. It caused this error "Checking uImage. Invalid Size", and I had to restore the backup to fix the issue.
However, I found out that Flemmard's "openrecovery-twrp-2.6.3.0-tenderloin-selinux.zip" can work very well with Invisblek's "cm-11-20131227-UNOFFICIAL-tenderloin.zip".
1. You should be able to flash Invisbleh's ROM over Milag's build to get 3.4 kernel.
2. The known black box issue has been fixed.
3. Playing video on YouTube could cause system reboot occasionally.

I have decided to go back to 10.2.
I am waiting for a cm11 release which includes a more stable 3.4 kernel.

Actually "cwm_selinux_6.0.5.4_datamedia.uImage" is functional, after I cleaned up my /boot folder.
And because it supports datamedia, it can restore my cm10.2 backup without any issue.

goog888 said:
Actually "cwm_selinux_6.0.5.4_datamedia.uImage" is functional, after I cleaned up my /boot folder.
And because it supports datamedia, it can restore my cm10.2 backup without any issue.
Click to expand...
Click to collapse
How did u clean it up?

Moody66 said:
How did u clean it up?
Click to expand...
Click to collapse
My /boot folder didn't have enough space for two different CWM.
You will need to download the free application "Rom Toolbox Lite" from the Store.
First I backed up and removed the original uImage.ClockworkMod (rev 6.0.3.6) from the /boot folder to save 5.8MB.
Then Invisiblek's "cwm_selinux_6.0.5.4_datamedia.uImage" (7.1MB) is renamed to uImage.ClockworkMod and "moved" to /boot folder.

Thanks. Recovery is driving me nuts. So many roms. Each wanting a different recovery. I try to help by testing rooms but I guess I will just stick to one as its to difficult to keep up with them all. Had to Webos doctor several times this week. Back to mom data media for me. Thanks again!

Related

[RECOVERY] Safestrap Recovery v3.7x [05/15/2014 V3.73 - TWRP 2.7.0.0]

SAFESTRAP v3.73 (2nd-System Bootstrap / Recovery)
ATTENTION: I will be stopping official Safestrap support on 9/1/2014. For more information please see:
https://plus.google.com/111109372727398356624/posts/AtoJ3xLj35b
** INSERT STANDARD DISCLAIMER: I'm not responsible for any damage you do to your phone using my tools. Always have a fastboot available for disaster recovery. **
Download the APK Installer:
Mirror 1: Goo.im
Mirror 2: Crackflasher
FOLLOW THESE INSTRUCTIONS: How to Safestrap
[ DOUBLE-CHECK you have the "Targa" version ]
NOTABLE TWRP-BASE CHANGES:
Key/button vibration in recovery and MANY more 2.7.0.0 updates
Screen saving in recovery. Can set the timeout under Advanced->Settings->Screen *Don't freak out of the screen is dark, try the power button.
SElinux support in recovery (1st boot won't take so long)
and much much more.. check the TWRP changelog here: http://www.teamw.in/project/twrp2
DEVICE SPECIFIC SAFESTRAP CHANGES:
[05/15] (3.73) Bugfix for dual SD card UMS mounting and pull in TWRP changes
[04/14] (3.72) Mostly other device updates
[01/15] (3.71) Code cleanup
[01/15] (3.71) Minor hijack updates
[12/18] (3.70) Mount cleanup during hijack / debugging output
[12/18] (3.70) Splashscreen: Instant stock boot key (needs to be set for Moto OMAP4's still)
[11/13] (3.65) recovery init.rc cleanup
[11/13] (3.65) fix updater build for cm 10.1 and 10.2
[09/20] (3.60) Better handling for virtual images > 2gb
[09/20] (3.60) Much improved block device handling
[09/20] (3.60) Bugfix in script translation
[09/20] (3.60) hijack / init.rc tweaks
[09/20] (3.60) update to TWRP 2.6.3.0 base recovery
[09/06] (3.53) Fixed mass_storage in recovery (via Mount menu)
[09/06] (3.53) Added Webtop to partition backup list (optional)
[09/06] (3.53) New virtual systems created will be 640mb (got reset 600mb)
[09/06] (3.53) Fixed file selector when changing from internal to external storage (previously location wouldn't update)
[09/05] (3.52) added "Reboot to Recovery" in APK
[09/04] (3.51) Disabled screen blank while creating a rom-slot
[09/04] (3.51) Fixed openrecovery script processing for stock slot to re-inject hijack after .zip install (cmupdater on stock now works)
[08/30] (3.50) If running a new CM10.1/CM10.2 ROM (08/30 or later) you *should* be able to install Safestrap and update the recovery w/o having to go back to stock. If Safestrap shows "recovery not installed" while you're on a ROM-slot, then that ROM hasn't been updated and it won't work. Swap back to stock ROM and update Safestrap from there.
[08/30] (3.50) Worked on stock ROM flashing and *should* work with CM10.1/CM10.2 builds on or after 08/30 *WILL NOT WORK WITH OLDER ROMs.*
[08/30] (3.50) Battery meter is back
[08/30] (3.50) Updated TWRP theme
[08/30] (3.50) Added partition sizes to ROM-slot screen when it's ACTIVE
[08/30] (3.50) Added "Check FS" function to ROM-slot screen when it's ACTIVE
[08/30] (3.50) Complete re-write against TWRP 2.6 base (up from version 2.2.2.1): TWRP changelog for reference
[12/29] (3.11) Allow use of custom updater-binary in .zip files for flashing on stock ROM (virtual slots still use prebuilt updater-binary in recovery).
[12/29] (3.11) BUGFIX: Fixed fake flash error at the end of a .zip install. (No real error, .zip installs fine)
[12/29] (3.10) Early support for booting custom ROMs on stock partitions.
[12/29] (3.10) Enable flashing to stock ROM *BE CAREFUL -- NEW FEATURE -- STILL TESTING*
After .zip installations, nandroid restore or system wipe on the stock ROM: the current Safestrap files are restored to the system partition (Doesn't include the APK in /data -- so if you're restoring an old backup, be sure to update the Safestrap APK)
During the Safestrap files restore a check is done to be sure there are minimal files on /system to re-enter Safestrap
[12/29] (3.10) New virtual system partitions will be 640mb (closer match to stock RAZR/D4)
[12/27] (3.07) Bugfix: missed some changes in Safestrap 3.06
[12/26] (3.06) Bugfix/Update for JB4.1 OTA for DroidRAZR (Non-JB devices can also use)
[10/17] (3.05) Fixed SD card / emmc sharing in recovery (UMS)
[10/17] (3.05) Fixed recovery installation/removal from ROM-slots
[10/14] Updated to v3.04 BETA.
[10/14] Recovery is now based off TWRP 2.2.2.1 (fully featured touch-based recovery)
[10/14] Can create up to 4 Virtual ROM-slots to flash ROMs to and when "Active" ALL TWRP functions affect that ROM-slot (For example: Flashing .zips, Backup and Restore)
[10/14] Nearly instant swapping from ROM to ROM
[10/14] User selectable data partition sizes during ROM slot creation: 1GB, 2GB or 3GB
[10/14] ROM slots are saved on the internal emmc space so that preinstall and webtop partitions are no longer used and shouldn't break OTAs.
[10/14] Charging in recovery
[10/14] Supports "Reboot Recovery" from Android OS
Entry to recovery via Splashscreen on boot-up. The screen stays up for around 8-10 seconds and if you hit the menu button, it takes you to Safestrap Recovery.
SPECIAL THANKS TO:
The entire TWRP team who has built an AMAZING recovery system.
The testers which have helped in past and present versions of Safestrap, knowing that it could mean they brick their devices.
As always, let me know what you think!
SCREENSHOTS (showing slightly older TWRP base)
First! Thanks Hash!
Nice one. Will be checking all this out later just got a free bionic
Sent from my DROID BIONIC using XDA App
What's the correct procedure for updating versions of Safestrap? Do I need to be in unsafe system or uninstall first or ?
Awesome, Thanks!
Love this app/recovery. Thanks!
Sent from my BIONIC using Tapatalk
Does anyone have suggestions for when switching back to the primary, and it errors out on original data restore?
I did do the proper backups and normal toggle. The original back up refused to boot. Even initiate boot.
The only way I got back to primary was to install eclipse in safe system, back it up. Then do a hard toggle to non safe, and restore the Eclipse back up.
Is there any other way, or a way to verify toggle back ups? I am aware of the verify in the back up menu, but as far as I can tell it only verifies full system back ups.
Suggestions on what I may have done wrong, or a less time consuming remedy should it happen again?
Apologies if I left something out.. typed while putting the mag stripes on iTunes cards... only 600,000 to go... weeeeeee
And thanks fir your hard work and great tool for the bionic, Hash.
Sent from my DROID BIONIC using xda premium
I've never had that problem. Are you using your internal or external sd card for safe mode? The internal is faster and less likely to have problems.
Sent from my DROID BIONIC using Tapatalk
Does Bionic Bootstrap have to be removed/uninstalled before installing Safestrap? Can BB just be frozen?
Thanks.
EDIT: Okay, I see it does need to be removed.
cappiez said:
The only way I got back to primary was to install eclipse in safe system, back it up. Then do a hard toggle to non safe, and restore the Eclipse back up.
Is there any other way, or a way to verify toggle back ups? I am aware of the verify in the back up menu, but as far as I can tell it only verifies full system back ups.
Click to expand...
Click to collapse
I've seen this happen a handfull of times, most of which were due to a nearly full /emmc partition (internal SD card).
When you hard toggle and restore the Eclipse back up here's what happened:
- The "/system" backup goes back onto your /preinstall partition (where it also lives in 2nd-system) -- The only item which will get restored to your primay system is a backup of "/systemorig". And that's important because if you were to restore the 2nd-system back to the original system.. You'd brick because of partition renaming, etc.
- /data and /cache are restored normally.
You did the right thing in hard toggling and then advanced restore your data from a previous backup. Just know that your 2nd-system data wasn't stashed when you do the hard toggle. So there may be an issue when you want to go back to the 2nd-system.
I have noticed trying to make my first back up, i get an error. I am trying to save the back up to external sd card. Also what is safestrap?
For some reason the safestrap apk won't install the recovery program. When I hit install recovery it gains su permissions, shows a loading bar, says installation successful, but still says "Recovery State: Not installed" and there is no new splash screen on reboot. I just rooted this phone for the first time and have no other bootstrap to uninstall first. Any ideas?
JohnnyAn said:
For some reason the safestrap apk won't install the recovery program. When I hit install recovery it gains su permissions, shows a loading bar, says installation successful, but still says "Recovery State: Not installed" and there is no new splash screen on reboot. I just rooted this phone for the first time and have no other bootstrap to uninstall first. Any ideas?
Click to expand...
Click to collapse
I've seen this happen when Superuser has just been updated. It's like Safestrap thinks it has su priv, but Superuser never gives it out. Or something odd. I would try removing and reinstalling Safestrap so that Superuser can re-add it to the "allowed" list.
waffleb051 said:
I have noticed trying to make my first back up, i get an error. I am trying to save the back up to external sd card. Also what is safestrap?
Click to expand...
Click to collapse
Safestrap is the recovery system that lets Bionic users utilize an alternate recovery firmware to install alternate ROMs. That's what this entire thread is about.
It almost sounds like you trying to make your backup through ROM Manager. ROM Manager looks for Clockwork Recovery (that gets installed with Bionic Bootstrap and not Safestrap). Safestrap is an entirely different system that ROM Manager won't recognize.
Make sure you reboot your phone and manually enter into Safestrap so that you can make a backup. It will work properly that way.
http://youtu.be/UbGE_xxWSZ4
if it helps anyone, here's a video i made installing Safestrap 1.7 and ICS4Bionic.
Thanks Hashcode for all you've done!
I am wondering if i safestrap and want to go back to koush's bootstrap how do i go about it and can i recover the space used for the 2nd system?
Never mind i figured it out.
Would it somehow be possible to load a stock 5.5.886 image with kernel and everything stock like using the full 5.5.1_84_DBN-55 image? Then being able to update it through the upgrade path then flash it to the normal phone system? I mean using the 2nd partition created by safe strap to do all the steps before flashing to the normal phone partition.
I was also wondering is it possible to copy a backup from CWM into the folder this creates for backups and be able to flash that?
twinkyz1979 said:
I was also wondering is it possible to copy a backup from CWM into the folder this creates for backups and be able to flash that?
Click to expand...
Click to collapse
Safestrap does not interact with CWM backups from the other bootstrapper.
projektorboy said:
Safestrap does not interact with CWM backups from the other bootstrapper.
Click to expand...
Click to collapse
Although you can still copy the backup from CWM to safestrap and still restore it and it will work. i have done this.
I Loose boot after safe mode enabled
I rooted the .886, then used the OTA and lost root.
I had to factory reset so i could R3L3AS3dRoot and 4ever root, I then used the OTA to come from .886 system to the .893 system.
I am rooted and have the recovery state installed.
When I install the safe strap I loose the ability to boot, I then have to uninstall it to gain boot once again.
EDIT:
Safe strap enabled, had to flash a custom rom over the one which wouldn't boot. I'm sure it would work if i reflashed stock over the safestrap.
Thank you!

[RECOVERY][TWRP&CWM][Updated: 6-Feb-2013]Stock Kernel on Official Jellybean

Note: This has been deprecated in favour of LK for Xperia T
This kernel image is based on stock using the FreeXperia ramdisk method of loading stock and recovery. It also includes the new FOTA partition trick by Dees_Troy for easy updates in the future to TWRP.
Dees_Troy and I worked on figuring out the reason recovery binaries would not load on the stock kernel without patches, fixed this up in bionic, and rebuilt recovery linked against the fixed bionic.
F.A.Q
Q. The title says TWRP and CWM but when I boot recovery I only see TWRP. How do I get CWM?
A. TWRP is the default recovery, if you want CWM you should download the CWM update.zip in the second post and flash it with twrp.
Technical Info​
In 3.4 Qualcomm have changed the fb_var_screeninfo struct slightly. They have added an extra field called colorspace which increases the size of the stuct by __u32. When a binary linked against bionic tries to pass a struct the size of the old fb_var_screeninfo to kernelspace the application breaks as the kernel is expecting more data than it was given.
The patch to fix this in kernel solves the problem by removing one of the reserved fields, bringing the struct back to the same size it was prior to the new field being added. While this keeps compatibility with older recovery binaries, it does introduce the problem of needing a custom kernel to run recovery. Sony have not yet released source for 9.1.A.0.489 which means the kernel cannot be rebuilt without issues such as WiFi not working. The patch that Dees_Troy applied to the build system was to add the new colorspace field into the header for bionic which means the new recovery binary can run on an unmodified stock Sony kernel.
Flashing​
Boot device in fastboot mode:
Code:
adb reboot bootloader
Flash image with fastboot:
Code:
fastboot flash boot mint489stock.img
Source for TWRP available from here.​
Updates:
1. Updated image in first post to fix bug where creating a backup would fail and crash twrp.
2. Updated first post to show CWM in title and answer questions about how to get CWM.
Flashable zips:
In the first post it is mentioned about using the FOTAKernel trick by Dees_Troy to offer easy updates. The 2 zips attached to this post are examples of the ease of use.
flashCWM.zip - This will flash CWM to the FOTAKernel and replace TWRP as your recovery.
flashTWRP.zip - This will flash TWRP to the FOTAKernel and replace TWRP that is built into the image that was flashed to your device by fastboot, or to replace CWM with TWRP again if you used the flashCWM.zip
This also makes updates easier as you do not need to replace the kernel image you currently have flashed to your device.
Re: [RECOVERY][TWRP]Stock Kernel on Official Jellybean
Many thanks, can you just clear up one thing please, does Wi-Fi work on this image?
Sent from my LT30p xda premium app.
How do I customise the signature on xda premium app?
gregbradley said:
Many thanks, can you just clear up one thing please, does Wi-Fi work on this image?
Sent from my LT30p xda premium app.
How do I customise the signature on xda premium app?
Click to expand...
Click to collapse
Yes, wifi does work because it is just the stock kernel with TWRP added. I am running it right now with no problems.
I thought so, but I just wanted to make it obvious to all users as it was not 100% clear from the OP. I didnt have time to flash myself and check as I was just abbout to leave for work, now I am at work I will also flash it....
lilstevie said:
This kernel image is based on stock using the FreeXperia ramdisk method of loading stock and recovery. It also includes the new FOTA partition trick by Dees_Troy for easy updates in the future to TWRP.
Dees_Troy and I worked on figuring out the reason recovery binaries would not load on the stock kernel without patches, fixed this up in bionic, and rebuilt recovery linked against the fixed bionic.
Technical Info​
In 3.4 Qualcomm have changed the fb_var_screeninfo struct slightly. They have added an extra field called colorspace which increases the size of the stuct by __u32. When a binary linked against bionic tries to pass a struct the size of the old fb_var_screeninfo to kernelspace the application breaks as the kernel is expecting more data than it was given.
The patch to fix this in kernel solves the problem by removing one of the reserved fields, bringing the struct back to the same size it was prior to the new field being added. While this keeps compatibility with older recovery binaries, it does introduce the problem of needing a custom kernel to run recovery. Sony have not yet released source for 9.1.A.0.489 which means the kernel cannot be rebuilt without issues such as WiFi not working. The patch that Dees_Troy applied to the build system was to add the new colorspace field into the header for bionic which means the new recovery binary can run on an unmodified stock Sony kernel.
Flashing​
Boot device in fastboot mode:
Code:
adb reboot bootloader
Flash image with fastboot:
Code:
fastboot flash boot mint489stock.img
Source for TWRP available from here.​
Click to expand...
Click to collapse
Such a good news!I will port it to TX JellyBean firmware if you don' mind
gregbradley said:
I thought so, but I just wanted to make it obvious to all users as it was not 100% clear from the OP. I didnt have time to flash myself and check as I was just abbout to leave for work, now I am at work I will also flash it....
Click to expand...
Click to collapse
only for unlocked bl, correct?
hi,
i wanted to create with this version a backup, but it doesn't work.
it was just created the folder system,
the other folders such as data and boot not.
the created folder system, that was created after backup, is empty.
the 'backup' also takes only a few seconds, then the 'backup' is done.
what have i done?
installed the .img with instructions above.
boot xt into recovery, push backup, select system, data & boot, choose destination folder and start backup.
where is my failure?
hkjr said:
only for unlocked bl, correct?
Click to expand...
Click to collapse
Yes
MysticEnforcer said:
hi,
i wanted to create with this version a backup, but it doesn't work.
it was just created the folder system,
the other folders such as data and boot not.
the created folder system, that was created after backup, is empty.
the 'backup' also takes only a few seconds, then the 'backup' is done.
what have i done?
installed the .img with instructions above.
boot xt into recovery, push backup, select system, data & boot, choose destination folder and start backup.
where is my failure?
Click to expand...
Click to collapse
Same here....seems backup is not working
MysticEnforcer said:
the 'backup' also takes only a few seconds, then the 'backup' is done.
Click to expand...
Click to collapse
Updated first post with a fixed image.
Thank you very much, this is the best message of day.
Just flashed new image
Doing a backup and it seems to work...will update in few minutes when it is finished
EDIT:
It works
Backup complete in 385 seconds
FYI,
both times on rebooting system from recovery I initially got the grey triangle, both times it was only for 10-15 seconds before the phone rebooted...
Testing it now ....
Edit:
[Backup completed in 461 seconds] External SD card with compression on. No Grey triangle for me.
[Restore completed in 192 seconds] Restored backup without any problems. No grey triangle on second reboot either.
Seems to work great for me.
(only clock seems to be incorrect. 7 hours and 16 minutes behind)
Edit 2: thirth boot up seems to get stuck on grey triangle for about 15 seconds
Edit 3: Seems only the first time reboot after using the recovery the grey triangle is there. Rebooted the phone 4 times and only got the triangle 1 time.
Updated first and second post
USB storage does not work at all both on TWRP and CWM
tested 2nd version, works fine for me & no grey triangle :good:
romcio47 said:
USB storage does not work at all both on TWRP and CWM
Click to expand...
Click to collapse
Noticed that to
romcio47 said:
USB storage does not work at all both on TWRP and CWM
Click to expand...
Click to collapse
This appears to be more of a technical limitation.
The internal storage space is formatted ext4, so only linux would be able to mount that by default so it doesn't offer that.
With the MicroSD the issue seems to be a little more complex and may possibly need a custom kernel.
lilstevie said:
This appears to be more of a technical limitation.
The internal storage space is formatted ext4, so only linux would be able to mount that by default so it doesn't offer that.
With the MicroSD the issue seems to be a little more complex and may possibly need a custom kernel.
Click to expand...
Click to collapse
Thanks for the reply I guess we just have to wait for the kernel sources to be published
Besides another issue - in CWM wiping dalvik-cache does not work.
romcio47 said:
Besides another issue - in CWM wiping dalvik-cache does not work.
Click to expand...
Click to collapse
I can't reproduce this, if I wipe dalvik-cache in CWM it removes /data/dalvik-cache as it should.

[Q] Updated CWM and resized partition, now CWM can't find my folder structure

I just updated my CWM to 6.0.4.6 in preparation for upgrading my CM10 to CM11. Here's what I did:
Backup app data using Titanium.
Cleared both caches, installed the new CWM zip.
Rebooted to CM10:
copied my old nanroid backup to my computer.
Rebooted into CWM:
made a new nandroid backup.
Rebooted into webos:
resized my system partition from 400 to 600 mb.
When I booted in CWM to install the 4.4 rom all my folders were missing. All I can see is
/sdcard/
-0/
-clockworkmod/
The only folder in 0/ is clockworkmod/backup/[mynewnandroidbackup]/
Any idea what I need to do to get things straightened out?
CM10 still boots fine and my files show up in /sdcard0/. There is no sign of a folder called /sdcard/. Same story if I explore the device with a computer.
I should mention that I also moved my nandroid backup to my computer, off the touchpad to save space before I resized my partitions. I then moved it back into the folder. I wouldn't be opposed to wiping the thing and starting over to get 4.4 working.
Any ideas?
kspanks04 said:
I just updated my CWM to 6.0.4.6 in preparation for upgrading my CM10 to CM11. Here's what I did:
When I booted in CWM to install the 4.4 rom all my folders were missing. All I can see is
/sdcard/
-0/
-clockworkmod/
The only folder in 0/ is clockworkmod/backup/[mynewnandroidbackup]/
Any idea what I need to do to get things straightened out?
Click to expand...
Click to collapse
First, this issue that you observe has been discussed ad nauseam in various CM11 ROM development threads.
Second, you did not post which specific CM11 ROM you are planning to employ. So I assume it is Milaq's CM11 ROM (kernel 3.0+).
At any rate, what you are observing in an inability to directly access the /external_sd partition (on the TouchPad), which is accessible in previous CM builds, but is no longer directly accessible in Milaq's recent CM11 builds (Kernel 3.0.101) or in his recent CWM recoveries.
http://forum.xda-developers.com/showpost.php?p=49216229
• Milaq and others have suggested you can use ADB to mount the partition manually (sorry no instructions).
• Some have posted you can use Invisiblek's recovery (CWM 6.0.5.4 selinux datamedia) to flash Milaq's recent CM11 (Kernel 3.0+) ROM's
• You may be able to find a version of TWRP that can access the /external_sd partition.
On a related note, the new DataMedia storage paradigm which is the future of Android, has been designed into the newer CM11 and other KitKat ROM and recovery builds. Thus you need to increase the size of your /data partition.
You can use the Tailor app within WebOS to reduce the size of /media partition, then increase the /data partition size. And there are some scripts available that do similarly.
Best to read the specific ROM thread (including the OP) for more info on how DataMedia applies to the ROM build you are employing, and then be sure to read later posts in the thread regarding the inaccessibility of /external_sd: http://forum.xda-developers.com/showthread.php?t=2542353
It is possible that future builds of the CM11 ROM (kernel 3.0+) might provide access to /external_sd once again. Will see. Fingers crossed.
I tried invisiblek's cwm recovery and it did not provide access to /external_sd
(and there is confusion on the recoveries specific version number)
http://forum.xda-developers.com/showpost.php?p=49423381
There is another recovery on invisiblek's site: openrecovery-twrp-2.6.3.0-tenderloin.zip
Anyone have experience with that recovery version, ability to access /external_sd or "compatibility" with Milaq's newer CM11 ROM builds?
Yes sorry, Milaqs rom that you linked is the one I was working from. I don't have ten posts so that's why I'm posting here. I read through most of that forum and tried searching for my issue with no luck.
I went back and saw a couple posts that matched my problem with the following solution:
http://forum.xda-developers.com/showpost.php?p=49154585&postcount=471
When I get home I will try this although I didn't remember seeing that folder when I explored my device on Windows.
Thank you for the reply and sorry for the redundancy!
Ok so I browsed my sd storage and there is no 0 folder in /sdcard0/media
Not sure what to do now
kspanks04 said:
Ok so I browsed my sd storage and there is no 0 folder in /sdcard0/media
Not sure what to do now
Click to expand...
Click to collapse
Hey buddy,
Make sure your file browser is using root. Personally I use Es file explorer. Turn on root explorer (find it at the bottom in the side panel) and make system writeable (By clicking on 'root explorer' then 'Mount R/W'). I'm sure most file managers will have something similar in their settings.
Then go to the root of your device by clicking '/' at the top. From there you should be able to follow the post you linked above by gabhroo123. And yes i tried his method and indeed i could see the files i pasted into the folder.
Good Luck
Here is another trick that worked for me. Recover a previous stored ROM that supported both sd1 and sd0. Use file manager to copy the files you want from sd1 to sd0. Then go back to the new ROM and you will have access to your files on sd0.
Merfy said:
Hey buddy,
Make sure your file browser is using root. Personally I use Es file explorer. Turn on root explorer (find it at the bottom in the side panel) and make system writeable (By clicking on 'root explorer' then 'Mount R/W'). I'm sure most file managers will have something similar in their settings.
Then go to the root of your device by clicking '/' at the top. From there you should be able to follow the post you linked above by gabhroo123. And yes i tried his method and indeed i could see the files i pasted into the folder.
Good Luck
Click to expand...
Click to collapse
Ahhh thank you. I had tried this with a different file explorer in root. Es did the trick.
Now I need figure out how to fix these black screens that lock up after a good amount of inactivity.
Greeting HP Touchpad Expert: I need help.
I didn't mean to post this thread but I have same issue.. only I have this..
I also updated my CWM to http://milaq.exnet.me/downloads/tenderloin/misc/recovery-clockwork-6.0.4.7-tenderloin.zip
in preparation for upgrading my CM09 to CM11 (Milanq 4.4 Kitkat). Here's what I did:
Backup app data using Titanium.
Cleared both caches, installed the new CWM zip.
Rebooted to CM9:
copied my old nanroid backup to my computer.
Rebooted into CWM:
made a new nandroid backup.
I have not yet resize system partition.
Now, when I want reboot to CWM install the 4.4 rom all my folders were missing.
All I can see is
/sdcard/
-0/
-clockworkmod/
-clockworkmod/backup
Yes I have tried to ES File Explorer (R+W root) and following gabhroo123's notes above
I do not have
/data/media nor /data/media/0 folder
only empty /data folder.... I am able to write to copy older recovery-clockwork to /data but not "/" ...
When reboot to CWM 6.0.4.7 I still don't see any zip file.. (No files found message show).
Can someone at least point me the right URL or discussion xda-developers.com thread so I can read them.
I am not sure what I did wrong...
What extra steps I suppose to do ...because I have HP Touchpad with CWM 5.x.x + Android 4.0.1.x + CM 9 + mobo 0.35 ?
My planning steps were
#1) upgrade CWM to 6.0.4.7
#2) upgrade CM 11
#3) upgrade Gapps
Reference http://forum.xda-developers.com/showthread.php?t=2542353
([ROM] [NIGHTLY] [KitKat] [4.4] CyanogenMod 11.0 nightlies [3.0 kernel])
I do see /sdcard/clockworkmod/backup/backupfolder.. in CM 9 and I did put CM 11 and Gapps in several place in
/media , /sdcard/media, /sdcard/cminstall etc.. but nothing.. kept saying file not found..
Should I downgrade CWM back to 5.x.x ? I do not see any install zip file at all ...how?
HELP!
Thank you

[Solved] No sdcard after flash The_apes Flashable zip in clockwork

Hi !
I have a 32 Gb Touchpad on CM10.1 and i'd like to upgrade on CM11 with Milaq ROM.
So, i downloaded The_apes Flashable zip (this one : sys_512mb_data_plus_24576mb-signed.zip) and i flash it with ClockworkMod 5.x. I've got 2 errors like this.
After that, i flashed with the new ClockworkMod 6.x, but, now, when i want to flash ROM, i've got only 0/ and obb/ folders. I can't acces to sdcard/cminstall.
Boot on Android works fine, but, what i have to do to finish my upgrade on CM11 ?
Thanks a lot for your help !
Edit : on ES Explorer you have to activate root access to see /data/media/0
Bristow69 said:
Hi !
I have a 32 Gb Touchpad on CM10.1 and i'd like to upgrade on CM11 with Milaq ROM.
So, i downloaded The_apes Flashable zip (this one : sys_512mb_data_plus_24576mb-signed.zip) and i flash it with ClockworkMod 5.x. I've got 2 errors like this.
After that, i flashed with the new ClockworkMod 6.x, but, now, when i want to flash ROM, i've got only 0/ and obb/ folders. I can't acces to sdcard/cminstall.
Boot on Android works fine, but, what i have to do to finish my upgrade on CM11 ?
Thanks a lot for your help !
Click to expand...
Click to collapse
Welcome to the world of DataMedia.
In CM10.1 use a Root Browser app (e.g. ROM Toolbox lite) or a file manager app with root permissions (e.g. ES File Explorer or X-Plore) to move your CM11 ROM zip to a directory accessible to your new CWM recovery.
Myself I store all my ROM and recovery zips in the Download directory, where Chrome and Firefox also download files to.
e.g.
/storage/sdcard0/Download
/data/media/0/Download
Thanks woodytrain for your quick reply.
I tried to put my ROM /storage/sdcard0/Download but it's the same, i don't see this folder.
In /data, i've no folder
I tried to find obb/ with ES Explorer and it found it on /mnt/, is it normal ?
Last thing, i gone in WebOS in order to use Tailor and found this partition layout, i think it's not ok to flash KitKat :
USB (media) = 25.43 Gib
Android (system) = 408 Mib
Android (cache) = 200 Mib
Android (data) = 1.5 Gib
Unused Space = 8 Mib
I don't knom how to install KK on my touchpad. I don't understand because i don't thing to be a newbie, i flashed i9000 on CM 10.2, Touchpad on CM10.1, but KK made me crazy !
Thanks for your help !
You need to change your partition sizes. At the very least need to increase /system
And if you want to install a DataMedia (DM) ROM, you need to make additional adjustments.
Right now there are three (or four) KitKat (4.4.2) ROM's for the TouchPad (tenderloin) to choose from:
CM11 - 3.0 kernel (Milaq) - DM
CM11 - 3.4 kernel (invisiblek) - DM
Evervolv - AOSP - 3.4 kernel (flintman) - (two version:- one DM and one not)
If you want to install KitKat on your TouchPad will need to do some reading. Keep in mind all these KK 3.x kernel based ROMs are in development (experimental and/or for testing). Each has its own pros and cons, and various TouchPad features are not yet working, features you might have observed working in previous JB 2.6 kernel ROMs.
If you want to stay with JB, until KK is better baked for the TouchPad you may want to try out the new JB 3.x kernel ROM just released from jcscullins (01-25-14). It is NOT a DM ROM, whereas Milaq's CM10.2 (JB) is a DM ROM.
http://forum.xda-developers.com/showthread.php?t=1811480
Suggestions:
1. For each ROM you are interested in thoroughly read the OP. And suggest reading, at the minimum the last five pages of each thread.
2. Then visit [ROM GUIDE] How to Update/Install Android 4.2, 4.3 and 4.4 Builds on the HP TouchPad
http://forum.xda-developers.com/showthread.php?t=2321397
3. Be sure to read the info on how to update your partition for DM support. If you decide to go with a DM ROM, I would suggest using Tailor to change your partitions since you have Tailor installed on your device already.
4. Backup your device before proceeding. Generate a nandroid backup in your recovery as well as back up your app/data with Titanium Backup
5. A "full wipe" in your recovery (factory reset, including clearing caches, formatting /system) is generally recommended when doing major upgrades (not just a nightly flash of the same ROM).
Once you have chosen a ROM to install, and have downloaded the zips for both the matching ROM and Recovery zips (note each ROM has it's own specific recovery version matched to the ROM), then you should be ready to upgrade.
If you have questions before upgrading post your SPECIFIC questions/issues, identifying the ROM version you are coming from and going to.
Thanks woodytrain for your help.
I understood what i missed : root explorer button on Es Explorer
So, now, i can see my files with clockwork Recovery, yes ! I put them in /data/media/0/Download.
After that, i'm gone on Tailor to resize my partitions.
Now, i have :
600 Mb for system
200 Mb for cache
15 Go for media
and ~ 6 Go for data, it's not enough but don't care now...
So, i flashed my rom (Milaq CM11) and gapps (after factory reset, format /system, clear /cache) but now, when i boot on cyanogen, i've cyanogen logo and that's all... only a blank screen, i think i'will made an other post except if you have an idea
Bristow69 said:
So, i flashed my rom (Milaq CM11) and gapps (after factory reset, format /system, clear /cache) but now, when i boot on cyanogen, i've cyanogen logo and that's all... only a blank screen, i think i'will made an other post except if you have an idea
Click to expand...
Click to collapse
Not sure what is meant by "15 Go for media". Recommend you follow the partition instructions as listed in the OP of Milaq's CM11 ROM thread. At any rate...
Before you started the process did you do a nandroid, and backup your apps and data with TiBu or helium?
Then when you did the wipe, did you clear Dalvick cache as well?
And then did you flash the CWM recovery version listed in the OP of Milaq's CM11 ROM thread (CWM 6.0.4.6)? You MUST use that version.
http://milaq.exnet.me/downloads/tenderloin/misc/recovery-clockwork-6.0.4.6-tenderloin.zip
You might want to redo the process and hold off installing gapps until you have booted into CM11. Then go back to recovery and install the gapps listed in the OP. Or install one of the PA-gapps packages.
With a few more posts you receive the right to post to the ROM dev thread. Joy!
I reply only to increase my posts and because i made a big big mistake after this post, i formated all partitions on clockworkmod (6.0.4.6 ). So i will create an other thread on forum...
Mad and Confused
I was duped into updating to 4.4 evervolv when i was on their 4.3.1 rom and im not understanding the layout of my sd-card now. i know all my info is still there but unsure how to reformat so i can use all my space. 32gb touchpad. i will use root explore app to get all my data but can i use onboard storage app to format? Really pissed im in this situation at all. Stupid to be on a 4.3.1 rom and update only to find out it's now a 4.4 rom and my sd-card is different. Thanks much
Nevermind, got it sorted. Good excuse to repartition and reformat everything. Still want nothing from evervolv but there 16mb Gapps package, mwahaha

[Q] Newbie stuck trying to upgrade from CM9 to CM11. Cannot access ROM Zips in CWM?!

Hello all - I am trying to upgrade from CM9 to CM11 using [ROM] [NIGHTLY] [KitKat] [4.4] CyanogenMod 11.0 nightlies [3.0 kernel],
I repartitioned the drive with Tailor as suggested, and upgraded my CWM to (6.0.4.7)
My problem now is how do i get access the ROM/GAPPs zips? I can copy them over USB on my Win7 Machine to this folder, but CWM doesnt see them/cant access them.
I only have access to this folder in Win7. tried doing a clean install, and still no look.
Computer\cm_tenderloin\SD Card\rom.zip
the only options i have under "choose zip" in CWM are
/sdcard/0/clockworkmod - how do i get the rom zips there? i am totally stumped. i tried ADP to sideload a rom but the device isnt found. thanks in advance!!
Complete install of Android on the device
HI
I was in the same position I'd tried everything. In the end I decided to start from the beginning. What I did was pretty hardcore. I completely uninstalled Android. You need to erase the usb drive in Webos. you do this by booting into WebOS, going to settings/device info/reset options/erase USB drive. Remember before you do any of this get all you data of your device to you PC. Once this is done you are ready to install Android again. Now I found it was easier to upgrade from CM10.2 Data/Media build to CM11. So I installed Android on the device using these four files;
- moboot_38
- CM10.2,update-cm-10.2-20140126-UNOFFICIAL-tenderloin.zip
- update-gapps-jb4.3-20130813-signed.zip
- update-recovery-clockwork-no_metadata-6.0.3.6-20130926-tenderloin.zip
These files are available as a package at rootzwiki.com. There you will also find instructions on how to install android again and how to unistall android as well. Once android is installed now you need to resize the media and data partitions with tailor in webos. Now that this done you are ready to upgrade to CM11. So then booted up my device into Android. Then I connected it to my PC. enable USB conductivity on the device. I created a folder on the device on the now larger data partition (I used the same cminstall name for the folder).Transfered the CM11 (milaq version), Gapps and CMW 6.04.7 to this folder.
I would then boot into recovery. Now were going to update the CMW. choose install from zip find the folder and the CMW 6.0.4.7 file. install it.
once installed boot back into recovery. Now were going to inst CM11. First you need Perform a factory/data reset and wipe/format cache partition. Once this is done your ready to install CM11 and the Gapps. Choose install from zip. Find the cminstall folder you made install. then do exactly the process with the Gapps.
Android CM11 Milaq should work. This worked for me.
Hope this helps.
cheers
Data media install guide
Here is my full guide for installing Data Media Builds:
[ROM GUIDE]How to install Android 4.4.2 Data Media builds on the HP TouchPad
I have this problem
tgg05 said:
HI
I was in the same position I'd tried everything. In the end I decided to start from the beginning. What I did was pretty hardcore. I completely uninstalled Android. You need to erase the usb drive in Webos. you do this by booting into WebOS, going to settings/device info/reset options/erase USB drive. Remember before you do any of this get all you data of your device to you PC. Once this is done you are ready to install Android again. Now I found it was easier to upgrade from CM10.2 Data/Media build to CM11. So I installed Android on the device using these four files;
- moboot_38
- CM10.2,update-cm-10.2-20140126-UNOFFICIAL-tenderloin.zip
- update-gapps-jb4.3-20130813-signed.zip
- update-recovery-clockwork-no_metadata-6.0.3.6-20130926-tenderloin.zip
These files are available as a package at rootzwiki.com. There you will also find instructions on how to install android again and how to unistall android as well. Once android is installed now you need to resize the media and data partitions with tailor in webos. Now that this done you are ready to upgrade to CM11. So then booted up my device into Android. Then I connected it to my PC. enable USB conductivity on the device. I created a folder on the device on the now larger data partition (I used the same cminstall name for the folder).Transfered the CM11 (milaq version), Gapps and CMW 6.04.7 to this folder.
I would then boot into recovery. Now were going to update the CMW. choose install from zip find the folder and the CMW 6.0.4.7 file. install it.
once installed boot back into recovery. Now were going to inst CM11. First you need Perform a factory/data reset and wipe/format cache partition. Once this is done your ready to install CM11 and the Gapps. Choose install from zip. Find the cminstall folder you made install. then do exactly the process with the Gapps.
Android CM11 Milaq should work. This worked for me.
Hope this helps.
cheers
Click to expand...
Click to collapse
I am starting from a cm10.2 rom and i am encountering the same problem that the original poster is.

Categories

Resources