Database Users

[RECOVERY] [CWM Touch Recovery 6.0.2.8] [Updated 03-07-13]

Disclaimer
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
What is It
This is the latest version of CWM Touch Recovery (6.0.2.8) that I've built for the Touchpad.
It is a flashable zip so simply download the file and flash in your installed recovery.
It is also should be compatible to use with ACMEInstaller3.
I've uploaded the Touch version of CWM but touch doesn't work. However this version of CWM still has the enlarged icons like CWM Touch Recovery. It's really a CWM Touch Recovery but touch just isn't working yet. Touch should be working sometime this weekend. You can still navigate in this recovery with the hardware keys.
Changelog
CWM Touch 6.0.2.8 has the ability to "Install zip from sideload" while jcsullin's doesn't.
This allows you to use adb to install packages from your computer. Essentially you choose that option than run adb sideload flashable_zip_name (where flashable_zip_name is the path to the zip you want to flash). This prevents you from having to go into USB mode to copy over files to flash. Instead you just activate this and get it directly installed.
This was an intentional thing on jcsullin's recovery but has been fixed/enabled in this version (so basically not a problem with CWM itself).
This is probably not going to really sway very many of you but just keep in mind there are probably plenty of under the hood changes and ones I simply don't know.
Obviously, now this is the touch version of CWM but touch isn't working yet. Just use the hardware keys for now.
If I get any further changes I will post them here.
Downloads
Download No Touch Version Here
Download Touch Version Here
Bugs/Issues
If you have any issues please feel free to post them in this thread.
If someone thinks I should add more information to the OP just ask.

Hi, can you tell us what the difference is between your version and jcsullins version 6.0.1.9 please..
Thanks

these version numbers always confuse me. b/c if i look at cwm on google play store they list:
Updated:
February 16, 2013
Current Version:
5.5.2.3
is cwm 6x a beta or something? i can't find any info on the cwm website, or a changelog

x000x said:
these version numbers always confuse me. b/c if i look at cwm on google play store they list:
Updated:
February 16, 2013
Current Version:
5.5.2.3
is cwm 6x a beta or something? i can't find any info on the cwm website, or a changelog
Click to expand...
Click to collapse
I think what you are referring to is Rom Manager which is specifically designed to work with CMW much like Goo Manager is designed to work with TWRP an alternative to CMW.
The version I was referring to was written by jcsullins to overcome earlier versions corrupting the system along with moboot and the latest cm10 which most other versions for our TouchPad appear to be based on.

Works great so far! Thanks! :highfive:

-SGA- said:
Works great so far! Thanks! :highfive:
Click to expand...
Click to collapse
SGA can you tell us how this differs from jcsullins version. Thanks.

haha you're absolutely right sstar. when trying to find changelogs etc, i clicked on it through the clockwork website, and thought it was the same thing

sstar said:
Hi, can you tell us what the difference is between your version and jcsullins version 6.0.1.9 please..
Thanks
Click to expand...
Click to collapse
There is no official changelog for CWM so the answer is no I don't know the changes right now.
-SGA- said:
Works great so far! Thanks! :highfive:
Click to expand...
Click to collapse
Thanks for the feedback!
x000x said:
haha you're absolutely right sstar. when trying to find changelogs etc, i clicked on it through the clockwork website, and thought it was the same thing
Click to expand...
Click to collapse
It appears koush doesn't really say what every version has in it.

Remolten said:
There is no official changelog for CWM so the answer is no I don't know the changes right now.
Thanks for the feedback!
It appears koush doesn't really say what every version has in it.
Click to expand...
Click to collapse
Thanks for your reply but in the op you've said that you built this, so what changes have you made?

Re: [RECOVERY] [Remolten's CWM 6.0.2.8] [02-28-13]
The cwm recovery is made from the recovery.img after compiling the CyanogenMod source. It's likely a stock CWM6 recovery image.
Sent from my SAMSUNG-SGH-T989 using xda premium

Anyone know Koush? If so, ask him for some details and post them here.

-SGA- said:
The cwm recovery is made from the recovery.img after compiling the CyanogenMod source. It's likely a stock CWM6 recovery image.
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Thanks for your reply . My understanding was that jcscullins developed one that did not corrupt the system as posted by nevertells.
Maybe I'm wrong, just don't like the idea of flashing something the poster/ developer can't give any details about.

-SGA- said:
The cwm recovery is made from the recovery.img after compiling the CyanogenMod source. It's likely a stock CWM6 recovery image.
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
SGA explains it perfectly.
sstar said:
Thanks for your reply . My understanding was that jcscullins developed one that did not corrupt the system as posted by nevertells.
Maybe I'm wrong, just don't like the idea of flashing something the poster/ developer can't give any details about.
Click to expand...
Click to collapse
I can't give any information as I don't know what koush edits and such in CWM I just built it for the Touchpad.
Only change that I can vouch for is the version has been bumped.

You can see the commits do dot really go into any kind of detail as to what the changes are: https://github.com/CyanogenMod/android_bootable_recovery/commits/jellybean
Many of the moves to a higher version are only committed with a version number update.

-SGA- said:
You can see the commits do dot really go into any kind of detail as to what the changes are: https://github.com/CyanogenMod/android_bootable_recovery/commits/jellybean
Many of the moves to a higher version are only committed with a version number update.
Click to expand...
Click to collapse
Noticed that too.
Also I noticed that the latest version of CWM for the Nexus devices is 6.0.2.3 so I'm not sure how the version incrementals work since CWM is available on loads of different devices. I've successfully built a CWM Touch for the Touchpad with no touch (however it has the enlarged icons but no touch yet). Will post soon if you just want a recovery with enlarged look.

Added changes (changelog) from jcsullin's CWM6 release.

Remolten said:
Added changes (changelog) from jcsullin's CWM6 release.
Click to expand...
Click to collapse
Thanks, where are they?

sstar said:
Thanks, where are they?
Click to expand...
Click to collapse
Sorry took time to write look for section called changelog.

Re: [RECOVERY] [CWM 6.0.2.8] [No Touch] [02-28-13]
Is there a way to configure Rom Manager to recognize this version of CWM Recovery?
Sent from my cm_tenderloin using xda app-developers app

masterosok said:
Is there a way to configure Rom Manager to recognize this version of CWM Recovery?
Sent from my cm_tenderloin using xda app-developers app
Click to expand...
Click to collapse
I would have to become the CWM Recovery Device Maintainer which isn't going to happen anytime soon as I'm not a prominent developer yet
Short answer is not yet.
Why do you need to use Rom Manager? Just download the file and flash in your current version of CWM Recovery.

[Discussion][ROM][6.x][CM13.x] CyanogenMod 13 (Android Marshmallow 6.x) Official Nigh

CyanogenMod 13.x (Android 6.x) Official Nightlies Discussion Thread
CyanogenMod builds a new "nightly" version generally every 24 hours for each of the devices it supports. This includes the most up-to-date changes to its version of the Android (AOSP) source code.
Click to expand...
Click to collapse
Source: wiki.cyanogenmod.org
Changelog: http://cmxlog.com/13/bacon
Bug Reports (and votes): https://jira.CyanogenMod.org/browse/NIGHTLIES
Download Links:
1. CM13 ROM: http://download.cyanogenmod.org/?device=bacon
2. Android 6.x Gaaps: OpenGApps | BanKS GApps 6.x | more to come..
Flashing Instructions
Comprehensive installation instructions for CM on the OnePlus One can be found on the CyanogenMod Wiki: http://wiki.cyanogenmod.org/w/Install_CM_for_bacon
Note: If you are flashing from previous CM versions, you MUST flash 6-compatible gapps immediately after flashing the ROM!
(More to come)

## Reserved for future content ##

First !!! Very happy for CM13 now !!! First bug today on this first nightly : data does not work. Nevertheless, thank you for your great job !

OK, guys tell me whether you have mobile data working...
And... I have a weird bug when trebuchet gets FC on other device users except Owner. So it makes this feature useless
Sent from my A0001 using Tapatalk

For me also no mobile data. Tried to create custom APN and delete everything else but no joy.

I guess I'll give it sometime to stabilize until I try it.
awesome update!
---------- Post added at 10:12 AM ---------- Previous post was at 10:11 AM ----------
BTW, which gapps is required?

Same here, no mobile data.

is there a new baseband version?

Seeing the changelog, tomorrow's nightly also might not have the fix for this.

clean flash. mobile data worked for me.
Malaysia Celcom.

lockmunk said:
clean flash. mobile data worked for me.
Malaysia Celcom.
Click to expand...
Click to collapse
Really????
Sent from my A0001 using XDA Free mobile app

jokermithun said:
Really????
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Didn't work for me, even though clean flash. Tried numerous different APN settings.
BiBoB (Telenor), Denmark

xcalibur666 said:
Didn't work for me, even though clean flash. Tried numerous different APN settings.
BiBoB (Telenor), Denmark
Click to expand...
Click to collapse
For me the same
O2 Germany

What version of TWRP are you using?
2.8.7? Does it successfully flash everything?
or maybe 2.8.6.X

Same here try everything in flashing no data work

They say, toggle flight mode will do the job??

accuphase said:
For me the same
O2 Germany
Click to expand...
Click to collapse
No issues with O2 Germany with this build
http://forum.xda-developers.com/showpost.php?p=63980263&postcount=1121

Ad Away 3.1 can't write sources, so it does not work too.

gaja22 said:
Ad Away 3.1 can't write sources, so it does not work too.
Click to expand...
Click to collapse
CM is switching from Busybox to Toybox. The switch is not completed yet, which results in apps not being able to write to system (mount system as rw). I don't know but I believe that apps maybe need to be updated to work with toybox.
So far everything posted here has already been discussed in the numerous cm13 build threads.

AcmE85 said:
No issues with O2 Germany with this build
http://forum.xda-developers.com/showpost.php?p=63980263&postcount=1121
Click to expand...
Click to collapse
Exactly, this mentioned build is running fine, it has an accordant commit cherry-picked

Why not include the vendor file in the zip?

Just curious why I need to flash the vendor image after a ROM instead of just having it flash as part of the installation? Not that it's a big deal, just wondering if there is a specific reason. Seems like it could just be put in the zip and save a step. Thanks!

because it only needs to be flashed once per month/google release?

Soulfly3 said:
because it only needs to be flashed once per month/google release?
Click to expand...
Click to collapse
In some cases like Temasek it has to be flashed right beforehand too every time you install it or it won't boot (specifically the image, at that). I'm pretty sure the reason is that it'd mean swelling the size of every build by nearly 100mb, as opposed to having people download it serpaately which means its just one 100ish mb download a month. Also in the case of Temasek only flashing the vendor IMG works, not the zip so it wouldn't be practical.

vermiciouskanid666 said:
Just curious why I need to flash the vendor image after a ROM instead of just having it flash as part of the installation? Not that it's a big deal, just wondering if there is a specific reason. Seems like it could just be put in the zip and save a step. Thanks!
Click to expand...
Click to collapse
Why are you complaining about a prepackaged zip? That is for folks too lazy to flash radio and boot images manually. You need to update those every major google update listed on Nexus Factory Image host.

zymphad said:
Why are you complaining about a prepackaged zip? That is for folks too lazy to flash radio and boot images manually. You need to update those every major google update listed on Nexus Factory Image host.
Click to expand...
Click to collapse
And this is why I don't post any of my own ROM builds or participate on XDA anymore. Thanks for your contribution.

vermiciouskanid666 said:
And this is why I don't post any of my own ROM builds or participate on XDA anymore. Thanks for your contribution.
Click to expand...
Click to collapse
You are complaining about something other folks took the time to make it easier for people to update their boot/radio/vendor files. Thanks for your whining? You build ROMs and you don't know you only need to update that once every major update from google? Huh...
Sent from my Nexus 5 using Tapatalk

Thread closed per OP request.

News gapps arm64 by z010d and other movils

Hello, I download the new updated GAPPS always from the following URL because I have no problems with the downloads (I just downloaded the STOCK versions, they are all for 64 BITS CPUs like our Z010D:
Https://github.com/opengapps/arm64/releases
They are for all versions of ANDROID, from 5.0 to 7.1
You have to choose the finished files in .zip and to install them just like MOD ROMS.
A very cordial greeting to all.

Why is this thread exist?
Most of people have already known...
On every CM-based ROMs development thread...
Sent from my ASUS_Z00A using XDA Labs

krasCGQ said:
Why is this thread exist?
Most of people have already known...
On every CM-based ROMs development thread...
Sent from my ASUS_Z00A using XDA Labs
Click to expand...
Click to collapse
I just wanted to show another place where to download the gapps for our modified roms that did not give problems to download because the official website of gapps to me quite a few times gives me download errors.

Frank 1 said:
I just wanted to show another place where to download the gapps for our modified roms that did not give problems to download because the official website of gapps to me quite a few times gives me download errors.
Click to expand...
Click to collapse
Open GApps' website has it mentioned explicitly.
All downloads are hosted on the same server.
Sent from my ASUS_Z00A using XDA Labs

Rom Talk & Links

I've been meaning to make a thread for what seems to be a rather scattered dev scene so far for walleye that has migrated away from XDA and I'm not quite sure why. Everything seems to be G+ now.
AICP
I'm running AICP and have been since late Feb. Hector's got weekly builds for walleye going now and you can flash them like you're used to in TWRP (without formatting & sideloading)
His instructions:
adb reboot-bootloader <--> *check you are in slot_a
fastboot boot twrp-3.2.1-2-walleye.img
adb shell mkdir /sdcard/ROMS/
adb push aicp_walleye_o-13.1-UNOFFICIAL-20180320.zip /sdcard/ROMS/
flash aicp-rom
Wipe Dalvik
reboot
So basically just transfer to phone and flash, wipe cache and reboot. Ignore No OS message.
Errors: vendor mismatch and modem service FC. Neither affect function or performance.
Remember to re-flash twrp after flashing the rom.
Download- His G+ post: https://plus.google.com/u/0/104399241323212354617/posts/HKwZVqcgGY2
Feel free to post other roms here. I'm trying to make one thread where we can form some clarity regarding our rom options. I'm not here for support, but I'll help where I can. Very thankful to all developers contributing to this device. Hopefully nothing I'm doing here is illegal.

I'm on a custom ROM made by Frankie T (R3Ds). It can be found on his ROM Telegram "SiX Penguins"

SiX Penguins ROM

jascolli said:
I'm on a custom ROM made by Frankie T (R3Ds). It can be found on his ROM Telegram "SiX Penguins"
Click to expand...
Click to collapse
Link to the telegram please

nezebilo said:
Link to the telegram please
Click to expand...
Click to collapse
both can be found here:
https://plus.google.com/collection/kxuLqB

Is DU rom available for pixel2?
Sent from my Pixel 2 using Tapatalk

nickporwal said:
Is DU rom available for pixel2?
Click to expand...
Click to collapse
Unofficial build from 3/06 in RomDev thread, link to Google drive for OP. That's the last build Iam aware of

Why no xsa?

bambam126 said:
Why no xsa?
Click to expand...
Click to collapse
What's xsa?