Database Develop

CWM Recovery [GT-P6810][wifi]

Hi,
Please find port of Clockwork Mod Recovery 5.0.2.7 for GT-P6810.
(this is not a kernel replacement- just a cwm recovery image)
This is ported from the garyd9 6210 cwm recovery so please go thank him. (in 7.0+ forums)
Modified to work on 6810.
Incorporates garyd9 patches for sd card handling.
also thanks to ezynow and kassemja - for advice and bug fixing
based on stock firmware.
I have tried backup & restore, wipe cache , wipe dalvik-cache and so far has worked.
New version 2012-02-01: data wipe and then restore, backup to external and to internal (internal is now the default).
But we need some further testers.
Please only try if you what you are doing & know how to flash with odin.
Requirements: you need to be rooted.
Please know how to recover your device independently before using this!
DO NOT ATTEMPT TO USE ON ANY OTHER DEVICE. THE PARTITIONS ON THE P6810 ARE DIFFERENT!
Ok - first identified issue: If we are backing up to the external sdcard. This is fat32. So we have a file size limitation.
Also there may be a tool set size limitation in the binaries (as ported). This mainly affects "data", as this seems to include
pictures, video etc from the /data/media directories. So looks like to me data > 2G wont restore. Although it does create
(in my example 3.5G file and checksum is ok). I found that the 3.5G would not load. I retarred with all stuff in /data/media
deleted, (and fixed the nandroid checksum) then the data file loads (about 900M) and my device is recovered. I'm expecting if you try to back up more than 4G, the file will not be usable due to FAT32. I Hope this is clear.
So please check your file sizes (and nandroid sums) before attempting a restore.
So with this in mind,
Update: 2012-02-01: now backing up in the CWM tradition by default to the internal sd (which is ext4), and there are extra options enabled in the backup/restore menu. Please remember we are still in test mode. I think It is now working as intended and not backing up /data/media its easy to tell from the size of the data nandroid file.
So please backup your precious videos, pics etc from the /data/media directory independently.
Odin tar file (in the pda):

davp said:
Hi,
Please find port of Clockwork Mod Recovery 5.0.2.7 for GT-P6810.
(this is not a kernel replacement- just a cwm recovery image)
This is ported from the garyd9 6210 cwm recovery so please go thank him. (in 7.0+ forums)
Modified to work on 6810.
Incorporates garyd9 patches for sd card handling.
also thanks to ezynow and kassemja - for advice and bug fixing
based on stock firmware.
I have tried backup & restore, wipe cache , wipe dalvik-cache and so far has worked.
But we need some further testers.
Please only try if you what you are doing & know how to flash with odin.
Requirements: you need to be rooted.
Please know how to recover your device independently before using this!
DO NOT ATTEMPT TO USE ON ANY OTHER DEVICE. THE PARTITIONS ON THE P6810 ARE DIFFERENT!
Odin tar file (in the pda):
Click to expand...
Click to collapse
Big applause!
I've just tried to install CWM Recovery on my GT-P6810.
Wipe: works fine
Backup: seems to work fine
Restore: MD5 mismatch! error
I tried the following.
adb shell
# cd /sdcard/clockworkmod/backup/2012-01-30.**.**.**
# rm nandroid.md5 (error)
# md5sum *img > nandroid.md5
My GT-P6810 started to restore. But after reboot, nothing changed...

padebije said:
Big applause!
I've just tried to install CWM Recovery on my GT-P6810.
Wipe: works fine
Backup: seems to work fine
Restore: MD5 mismatch! error
I tried the following.
adb shell
# cd /sdcard/clockworkmod/backup/2012-01-30.**.**.**
# rm nandroid.md5 (error)
# md5sum *img > nandroid.md5
My GT-P6810 started to restore. But after reboot, nothing changed...
Click to expand...
Click to collapse
You installed via odin from above link? Any other source (market, another thread will not work on the P6810)
Thanks for trying.
Replacing the md5s is probably not a safe thing to do, the md5s are to ensure the backup is good. It would have been better to check the md5s and see which file is damaged.
Suggest:
Try a different microsd
Make sure your external microsd card is working correctly and has enough space
Move or delete the existing backup you did
Make another backup
check the md5sums of the files match the nandroid.md5 (cat nandroid.md5 ; md5sum *)
check the file sizes make sense (recovery and boot are 8M exactly, system ~684M, data varies)
If recovery and boot are not 8M, or any sums dont match what is in nandroid.md5, dont try to restore.
report back (please)

davp said:
You installed via odin from above link? Any other source (market, another thread will not work on the P6810)
Thanks for trying.
Replacing the md5s is probably not a safe thing to do, the md5s are to ensure the backup is good. It would have been better to check the md5s and see which file is damaged.
Suggest:
Try a different microsd
Make sure your external microsd card is working correctly and has enough space
Move or delete the existing backup you did
Make another backup
check the md5sums of the files match the nandroid.md5 (cat nandroid.md5 ; md5sum *)
check the file sizes make sense (recovery and boot are 8M exactly, system ~684M, data varies)
If recovery and boot are not 8M, or any sums dont match what is in nandroid.md5, dont try to restore.
report back (please)
Click to expand...
Click to collapse
Could you tell me the URL of Odin you mentioned above?
I installed via Odin3-v1. 85...

Ok guys, looks like there are file size issues due to fat32 external sdcard etc.
I believe the tool can still be useful, but be aware its limitations.
Have documented this in the first post as an issue.
The download is the same (I cant fix the fat32 limits).
padebije said:
Could you tell me the URL of Odin you mentioned above?
I installed via Odin3-v1. 85...
Click to expand...
Click to collapse
I use the one I had installed months ago (for phone). It the same version (downloaded mine from Intratech's gs2 official rom thread).
Sent from my GT-I9100 using XDA App

BRAVOOOOO!!!!!
I deleted all movie files > 2GB, and tried backup, wipe data, and restore again.
This time, I could make it thanks to your advice!

davp & ezy now, looks like you're famous.
http://www.theandroidsoul.com/new-g...or-both-3gwifi-edition-and-wifi-only-edition/

Thanks for your help with this kassemja!
cheers
Update posted in first post.

Hi davp,
You should push source to git hub, perhaps we could enlist Koush or Codeworkx to assist us. of all the options i have tried with recovery.fstab i was never happy.
i could never get both internal and external sd cards to mount. when i had them both setup the menu options for flashing and restore / backup will show option for internal sd cards.
IMHO, recovery should back up to external, as if you really bung up your device you will not have access to internal memory. The fact most of us only have 16gb internal memory its makes more sense to back up to external sd card.
i remember the nook colour, had a simalar debacle when they 1st released CWM mod for it. you could look there. i really havn't had a chance to dig into this. perhaps over the weekend i get more time
davp said:
Thanks for your help with this kassemja!
cheers
Update posted in first post.
Click to expand...
Click to collapse

Any chance somebody could please extract stock recovery and send me a target version?
Sent from my GT-P6810 using XDA Premium App

Tar not target...
Sent from my GT-P6810 using XDA Premium App

Help
Hi Guys,
EDIT: - I flashed an incomplete tar file as the download had not finished when I copied to sd card.
Got a small issues,
I have a Tab 7.7 running HC 3.2.
I gained root access and then install mobile odin pro.
I then proceeded to install this CWM and its not stuck at the galaxy tab 7.7 black and white screen at boot.
I selected the file i downloaded here using the recovery option to flash in mobile odin.
any ideas what i can do to get this working again?
Many Thanks
Syl

[RECOVERY] TWRP v2.4.4.0 - GMod v0.1.1 for unlocked devices

Hey there!
Because there is still no TWRP released, I decided to build it.
I used to code in C++ since 2005. Made alot of stuff. Now I'm moving to android.
I used the official CM10.1 sources (+kholk's) and the official TWRP sources to compile it on OS X Mountain Lion 10.8.3 (initial release was compiled on Ubuntu 12.10. With GMod I'm using OS X)
It's using kernel 3.1.10 (extracted from boot.img) and some files from its ramdisk.
The output was a working TWRP recovery. Internal Storage (/data/media) works to use it as backup storage.
External SDCard should also be working, since you can change where to backup in TWRP settings (internal/external). I did not try that, cause I don't own an external sdcard
To boot recovery just hold down Power+Vol-Down.
To install zips navigate to /emmc (internal) or /sdcard (external)
Note: If you have a folder called 0 inside /sdcard, then move its content to the root of /sdcard and delete the folder 0 (/sdcard/0). Otherwise TWRP will act weird and the internal storage doesn't get properly mounted but would still be fully functional.
How to install (some methods, you can choose one of them):
1) Using fastboot:
Code:
adb reboot oem-unlock
fastboot flash recovery twrp2440-recovery.img
fastboot reboot
2) Using adb or Terminal Emulator (place on root internal storage[/sdcard])
When using adb
Code:
adb shell
then, same when using adb or Terminal Emulator
Code:
su
cat /sdcard/twrp2440-recovery.img > /dev/block/mmcblk0p1
sync
That's it. Hope it works well for you as it does for me.
Changelog:
Code:
v0.1.1
Added Aroma Filemanager
Added Clockworkmod Touch 6.0.3.0
v0.1
Changed theme default color from blue to green
Now internal and external storage support
First working Reboot to recovery option for P880
Added Extras Menu in Advanced page - functions are not implemented (comming soon!)
gordon0001

Re: [RECOVERY] TWRP v2.4.4.0 for unlocked devices
Thaaaaanks !!! TWRP is much better , easier , and faster than CWM .
It's always good to see new development threads :good:
Sent from my LG-P880 using xda app-developers app

Updated.
Decided to customize TWRP.
Aroma Filemanager, CWM, and more will come soon to be included in my custom TWRP.
Changelog:
Code:
v0.1
Changed theme default color from blue to green
Now internal and external storage support
First working Reboot to recovery option for P880 (Reboot recovery in recovery)
Added Extras Menu in Advanced page - functions are not implemented (comming soon!)

gordon0001 said:
Updated.
Decided to customize TWRP.
Aroma Filemanager, CWM, and more will come soon to be included in my custom TWRP.
Changelog:
Code:
v0.1
Changed theme default color from blue to green
Now internal and external storage support
First working Reboot to recovery option for P880 (Reboot recovery in recovery)
Added Extras Menu in Advanced page - functions are not implemented (comming soon!)
Click to expand...
Click to collapse
Great!

Updated.
Changelog:
Code:
v0.1.1
Added Aroma Filemanager
Added Clockworkmod Touch 6.0.3.0
To access them go to Advanced --> Extras

This looks very nice gordon0001! Thanks for posting. Can I use this as an alternative to CWM, since it doesn't work for me properly? Can it use zip packages with no incompatabilities?

Feregorn said:
This looks very nice gordon0001! Thanks for posting. Can I use this as an alternative to CWM, since it doesn't work for me properly? Can it use zip packages with no incompatabilities?
Click to expand...
Click to collapse
Most zip archives that works for clockworkmod works also for twrp. just flash my modded recovery and you have both.

Cant mount sd-card!
I cant mount sd-card in recovery, extsd is working tought...
Any ideas?
EDIT: I can see the log says "E: Unable to find partition size for ' /sdcard'"

eliel1301 said:
I cant mount sd-card in recovery, extsd is working tought...
Any ideas?
EDIT: I can see the log says "E: Unable to find partition size for ' /sdcard'"
Click to expand...
Click to collapse
As soon as I'm getting a microsd card I'll try to fix that.
BTW: Internal sdcard is mounted at /emmc (TWRP default)

Thanks!! Installed without problems (v.0.1.1) and menu is working fine so far.
Haven't used it to install zips/roms yet though.
Sent from my LG-P880 using xda premium

i wont update this thread anymore, since a made something new. that combines cwm&twrp.
http://forum.xda-developers.com/showthread.php?t=2220302
next update will have alot of improvements and twrp 2.5.0.0 included

is it possible to restore a cwm backup from TWRP rec?I get FAIL CHECKING MD5 SUMS

no

@gordon0001, any news with your recovery?
@GRG13, your signature is terrible big and ugly and the link to your "How to enable developer options [...]" is wrong. :laugh:

Thanks a lot for TWRP recovery .. Happy time to have it .. Thumbs up

[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

[RECOVERY][Experimental][OS2SD/Internal][f2fs]TWRP2.8.0.0-multi

TWRP 2.7.1.0 multi-mode recovery. 2.7.1.0 v3 was the first release for p500, (thanks to @HardLight for advising, testing, and posting it. And for making a p500 OS2SD ROM to justify it.)
v1 and up are for thunderc (Optimus V/S), there's a separate thread over there in the appropriate forum.
Now with f2fs! Thanks @HardLight
OS2SD/Internal All-In-One. Switch modes under Advanced. It tells you on the title bar which mode it's in.
It'll flash gapps or PurePerformances or what have you to either the p2/p4 sdcard partitions for OS2SD or the internal partitions.
This has a special partitioner to set up your card for OS2SD. In OS2SD mode, go to Advanced then Partition. Set your sizes, it isn't aware yet of the whole card size (yet) so it'll just tell you if you go over and refuse to format it.
Whatever is left after your system/swap/data is your /sdcard size.
If it's in Internal mode the partitioner does sd-ext and swap instead. same deal, the leftover space is your /sdcard size.
Under the Wipe -> advanced menu, you can now select either system or data and press the 'repair or change filesystem' bar at the bottom, select change filesystem, select f2fs.
TLS enabled, system/data MTD swap on internal mode to match post-7/12/2014 androidarmv6 builds. Won't flash older ROMS or ones without the MTD swap correctly.
I am working on making it compatible with older builds too... but not yet. You may have to use a new update-binary to flash older zips. Or grab the older one from this zip file.
download, shared folder here:
Experimental, may be glitchy! Enjoy!
source on github

reserved
reserved against whatever need

reserved
I suspect I'll need more than one extra post to cover important stuff that won't fit in the OP.

On the portal today was announced a recovery-switcher app. One could have the mtd swapped and not-mtd swapped recoveries, or a cwm and a twrp recovery on the sdcard and use the app to switch between them. Do not know if this baby would work on a P500, though.
Would rather have a decent all-in-one, but that 5meg limitation may make this impractical (for example, the cwm has lost its sdcard partitioning functions).

bigsupersquid said:
TWRP 2.7.1.0 multi-mode recovery. v4. ...
OS2SD/Internal All-In-One. Switch modes under Advanced. It tells you on the title bar which mode it's in.
It'll flash gapps or PurePerformances or what have you to either the p2/p4 sdcard partitions for OS2SD or the internal partitions.
Experimental, may be glitchy! Enjoy!
source on github
Click to expand...
Click to collapse
So if understand correctly i'll flash the mod "buttons search<->power" & other zip files normally and not have to put the files into the rom manually or edit the updater script etc.:victory: thanks a lot
testing...

Dovidhalevi said:
On the portal today was announced a recovery-switcher app. One could have the mtd swapped and not-mtd swapped recoveries, or a cwm and a twrp recovery on the sdcard and use the app to switch between them. Do not know if this baby would work on a P500, though.
Would rather have a decent all-in-one, but that 5meg limitation may make this impractical (for example, the cwm has lost its sdcard partitioning functions).
Click to expand...
Click to collapse
that thing on portal reflashes the recovery every time to change it.
you could just as easily use flashable zip recoveries...
xdema said:
So if understand correctly i'll flash the mod "buttons search<->power" & other zip files normally and not have to put the files into the rom manually or edit the updater script etc.:victory: thanks a lot
testing...
Click to expand...
Click to collapse
that specific mod, you'd have to fix the updater-script to use it for os2sd, because it specifies MTD mounts.
mount("yaffs2", "MTD", "system", "/system");
pa_gapps and CrossBreeder and other more generic zips use
busybox mount /system
//edit: proper syntax:
run_program("/sbin/busybox","mount","/system");
instead of trying to call out the filesystem type.

bigsupersquid said:
that thing on portal reflashes the recovery every time to change it.
you could just as easily use flashable zip recoveries...
that specific mod, you'd have to fix the updater-script to use it for os2sd, because it specifies MTD mounts.
mount("yaffs2", "MTD", "system", "/system");
pa_gapps and CrossBreeder and other more generic zips use
busybox mount /system
instead of trying to call out the filesystem type.
Click to expand...
Click to collapse
i'll check the updater script, thanks for the pureperformance thinks, i discover a another method to speed up the p500 :fingers-crossed:

bump
f2fs enabled for OS2SD.
uses updater script like so:
mount("f2fs", "EMMC", "/dev/block/mmcblk0p4", "/data");
to use f2fs /data go into Wipe menu, advanced, select data checkbox, press 'repair or change filesystem' bar, change filesystem, f2fs. accept.
you only have to do that once to change from the default ext4 partition type.
it handles /system f2fs as well.
mount("f2fs", "EMMC", "/dev/block/mmcblk0p2", "/system");
change the filesystem the same way as data.
new 3.0.101 kernel but I noticed no differences in recovery except the working f2fs. Thanks @HardLight.
for now, attached .img for you who really have to experiment. I haven't tested this one very much on thunderg, just thunderc. basics tested on thunderg.
flashable zip added to shared folder linked in OP.
there's a little something extra in the shared folder...
I'm also uploading ROMs for the adventurous.
f2fs-system and f2fs-data os2sd builds if you're brave enough to try them. change both system and data to f2fs in recovery before flashing the rom unless you've already done that with an earlier version.
I don't have cell service to test but it's basically an androidarmv6 build plus 3.0.101 kernel and f2fs os2sd. everything else looks like it works to me.
I added Email, Apollo, Speech Recorder (which tunes up voice search I think), emojii in messaging and aosp keyboard, and extra wallpapers. Including Grass live wallpaper (which does actually work on armv6, it just looks for some network function and errors out ... I patched it,) and it reverts to building libcamera. Plus hackers keyboard because I like arrow and tab in terminal. No voice search in hackers keyboard though.
...

bump for twrp 2.8.0.0
no other fixes or anything, just a rev up for twrp.
I'll upload in an hour or so. //edit: well, maybe not so soon. I can't test at the moment since my o1 went into a no-boot loop. perfectly good running rom on it too. bah.
take me the evening to fix it.

bigsupersquid said:
bump for twrp 2.8.0.0
no other fixes or anything, just a rev up for twrp.
I'll upload in an hour or so. //edit: well, maybe not so soon. I can't test at the moment since my o1 went into a no-boot loop. perfectly good running rom on it too. bah.
take me the evening to fix it.
Click to expand...
Click to collapse
i'm testing your's 0509
in this you made the on boot fix?
##fix "add_tid_to_cgroup failed to write" errors
chmod 0660 /dev/cpuctl
# allow reading kernel command line
chmod 0644 /proc/cmdline
Click to expand...
Click to collapse
thanks
could you say to me if it's normal this:
i make the wipe of the /system in twrp, then if i go to "repair or change fs" it show size 390mb, used 110mb
but if i make a wipe or a "change fs", used space shouldn't be 0mb?
is the same for /data.
i un/mounted the partitions before, but have always some mb used in both.
hum minitool show me that the two f2fs partitions are fully used, maybe it can't read the f2fs, however i've formatted the partitions again in ext4 and now retry the f2fs format via twrp
edit: however, after 2nd format in the end /data have 144 mb used, /system 110mb. so i suspect it's normal

xdema said:
i'm testing your's 0509
in this you made the on boot fix?
thanks
could you say to me if it's normal this:
i make the wipe of the /system in twrp, then if i go to "repair or change fs" it show size 390mb, used 110mb
but if i make a wipe or a "change fs", used space shouldn't be 0mb?
is the same for /data.
i un/mounted the partitions before, but have always some mb used in both.
hum minitool show me that the two f2fs partitions are fully used, maybe it can't read the f2fs, however i've formatted the partitions again in ext4 and now retry the f2fs format via twrp
edit: however, after 2nd format in the end /data have 144 mb used, /system 110mb. so i suspect it's normal
Click to expand...
Click to collapse
looks normal to me, ext4 uses "only" about 16MB after format but f2fs uses a lot more.
minitool will only work right if your kernel supports f2fs and I doubt m$ware does right now.
and the fix din't get migrated from the overrides in thunderc to p500 yet, sorry, was a 'for fun' build to share after a recent repo sync.
this one probably has a built libcamera instead of the froyo as well. (reversion)

reverted to twrp 2.7.1.0
2.8 kept bootlooping my o1.
one too many passes with kdz, it's total blackout no power, and I'll have to jtag it now.
be a while before I release another update unless I find an o1 with fastboot.

bigsupersquid said:
reverted to twrp 2.7.1.0
2.8 kept bootlooping my o1.
one too many passes with kdz, it's total blackout no power, and I'll have to jtag it now.
be a while before I release another update unless I find an o1 with fastboot.
Click to expand...
Click to collapse
My 01 does have fastboot e.e

andrea210701 said:
My 01 does have fastboot e.e
Click to expand...
Click to collapse
I meant that I can use. HardLight pointed me to the method to enable it... if I hadn't completely fried my firmware. no backlight even, much less lg logo or emergency mode.
eventually I'll find another p500 for development (I can't use gsm phone on my service) but the going rate on ebay is $50 and I can't justify that for a hobby.
unfortunately it's too tweaky and time consuming for me to remotely develop by having someone else debug, so any more p500 stuff will be untested and slightly sketchy because of that.

Project [F2FS] [OS2SD]
[F2FS] [OS2SD] it can work with any other rom? Thanks.

cwm6.0.5.3oldMTDmounts_p500.zip
I do not know what it is? Sorry for the little understood...

Any PlayStore said:
cwm6.0.5.3oldMTDmounts_p500.zip
I do not know what it is? Sorry for the little understood...
Click to expand...
Click to collapse
clockwork mod v 6.0.5.3 for pre-tls roms (before androidarmv6 swapped the system and data Mount points in the kernel) used for kitkat roms around July 2014 or earlier or other 4.4 roms without the MTD partition swap

How to install TWRP custom recovery (no MCU updates possible afterwards)

pakidermo5000 said:
Ok, I need some help here to understand pretty basic things. I think I am trying to do the wrong thing. I get into bootloader mode. I get the black screen and detection of "class for rockchip" in device manager.
Now, I want to flash TWRP. My idea was to get into bootloader mode and use ADB to flash TWRP. But, I cannot connect to HuiFei when in bootloader mode because adb does not see any device.
Instead, if I boot the unit and use Wifi ADB, then I can connect to the unit.
So, should I flash TWRP through wifi ADB with the unit booted, or should I do it through bootloader mode? I could probably do it via recovery, but I do not really know how (just do update from sd card and select the TWRP I downloaded from 1-2-hak ?) otherwise, how do I do it if my adb does not detect any device?
sorry for the basic questions, but it is the first time I am doing this...
Click to expand...
Click to collapse
You dont need bootloader to flash TWRP. You just need to know how to get there if something goes wrong.
Check this link http://www.freaktab.com/showthread....itions-from-android-No-PC-needed-For-rockchip
get the flash_image from the link.
the get your wifi adb going
do a
adb push flash_image /sdcard/flash_image
adb push TWRP_KGL-7650G /sdcard/TWRP_KGL-7650G
then i go to adb shell
usually just cp them to dev
cd /sdcard
cp flash_image /dev/flash_image
cp TWRP_KGL-7650G /dev/TWRP_KGL-7650G
then flash it
/dev/flash_image recovery /dev/TWRP_KGL-7650G
then if you want to test
reboot recovery
you will need an mouse attached.
I am gong to see if I can get the touch working in this when I get my unit back.
Do a backup of the whole system in TWRP.
Then you are pretty well set.
Not sure if you need original recovery to update new MCU.images. When i uploaded mine I just flashed back the original recovery in the same way.
You can back up the original recovery by the steps in the link above. Which is good to have a complete copy of what you have now before tinkering too.
Hope that helps.

v3 with init.d support!
Here are v3 images for both screen resolutions in both KGL and KLD variants:
KVV_KitKat_XRESxYRES_yymmdd_rooted_light_reparted_init.d_v3:
rooted:
- ClockworkMod's Superuser apk, su binary and root daemon (root daemon needed on 4.3+ roms)
reparted: (seems popular these days )
- system reduced from 768MB to 512MB
- oem reduced from 128MB to 64MB
- data increased from 1GB to 3GB
- internal sd in now a bit less than 4GB
removed apks:
- Gmail2 (available on Play Store)
- Maps (available on Play Store)
- GoogleSearch (available on Play Store)
- VoiceSearch (included in GoogleSearch on Play Store)
- Talkback (available on Play Store)
- Google TTS and its libs and files (available on Play Store)
- Adobe Reader and its libs (available on Play Store)
- Instructions (surely useless, not relevant and badly translated from chinese...)
- Chinese and Japanese Keyboards (also removed their libs that are now useless)
- Navgear (just a stupid shortcut to the selected nav app in settings...)
updated/added apks:
- Google Play Store (updated to latest version)
- Google Play Services (updated to latest version with libs correctly installed so no more Google Play Services errors! Fixed on 1024x600 v3.1 thanks to @ESTIMULO)
- Browser bookmarks sync adapter (added, missing in KLD and KGL)
- Google calendar sync adapter (added, missing in KGL)
- Google contacts sync adapter (added, missing in KGL)
modded:
- init.d support added (late in boot process so every external storages are mounted), you can drop your scripts to /etc/init.d (chmod 755)
- added compatibility symlinks for storage mount points (it may fix issues with apps using hard-coded path to access sdcards and usb, if not it won't hurt anywway!)
- flash_image binary by Androtab, with dump_image and erase image symlinks to flash/erase/dump full partitions (dump_image return an error at the end but you can ignore it, dump is valid)
IT WILL WIPE YOUR DATA AND INTERNAL SD so backup first!
Please note that 1024x600 versions are untested as I don't own such a device but it's modded the same way so it should work flawlessly.
Updated TWRP image
This is an updated Team Win Recovery Project image based on 2.7.0.0 by Abdul from freaktabs (most credits goes to him! )
Updated fstab to new KK part scheme (was mounting kpanic and oem instead of system and internal sd)
updated kernel, modules and config files (full SElinux support)
Still no touchscreen you have to use a mouse. I've spent days trying to make touchscreen work but no luck, I'm starting to think that touchscreen is handled by mcu which then emulates a touch device or some weird things like that...
Now with a 1024x600 image
Please note that 1024x600 version is untested as I don't own such a device but it's Updated the same way so it should work.
Download latest versions HERE
How to flash recoveries back and forth to backup/restore data over flashes
Install Jack Palevich's Terminal Emulator for Android from Play Store and use a root explorer to save the apk file to your sd card or usb storage.
Download flash_image binary and use a root explorer to copy it to /system/bin and change permission to 755 rwxr-xr-x (if you are on one of my modded fw it's already installed you can skip this step).
Launch Terminal Emulator and type su to gain root, then type cd /path/to/recovery/folder, then type flash_image recovery twrp.img
You now have twrp installed, type reboot recovery to reboot to twrp.
In twrp use a mouse and go to backup menu to backup data (do not backup to internal sd it will be formatted by update).
Now reboot to system and place update.img at the root of you external sd or usb storage but don't update if prompted
Launch Terminal Emulator and type su to gain root, then type cd /path/to/recovery/folder, then type flash_image recovery recovery.img
You now have standard recovery installed, type reboot recovery to reboot to recovery.
Now you can flash update.img from the menu using power button.
When back into Android use backed up Jack Palevich's Terminal Emulator for Android apk to reinstall it quickly without having to set up google account.
Launch Terminal Emulator and type su to gain root, then type cd /path/to/recovery/folder, then type flash_image recovery twrp.img
You now have twrp installed, type reboot recovery to reboot to twrp.
In twrp use a mouse and go to restore menu to restore data.

webdude12 said:
Just a quick update.
I have copied over multiple different SU using TWRP to my stock 1024 x 600 4.4.2 unit. All them result in the same thing. Superuser not being able to use it. I have confirmed its there, messed with permissions on su and the system folders.
On thing I noticed through the TWRP command line is that SELinux is enabled. So thinking I might to research that to figure out if I need to do anything to get around that.
Back to the drawing board.
Click to expand...
Click to collapse
I've updated the twrp image for 1024x600 with 100% scaling factor so it should fit the whole screen now. Grab it HERE if you want to try.
Why don't you just flash a superuser zip from twrp, it will take care of the files, permissions and starting the daemon for you. You can grab ClockworkMod's superuser installer here: http://download.clockworkmod.com/superuser/superuser.zip

Note:
You can get required files here: https://docs.google.com/file/d/0B3FXCUVt554Mb1Nnai14eWM2cWc/edit
This is not provided by me! I copied the link from @pakidermo5000's old OP-Post
With TWRP MCU-Updates are no longer possible!
Normally you do not need TWRP as any custom roms can and have to be flashed using original recovery

coudu said:
I've updated the twrp image for 1024x600 with 100% scaling factor so it should fit the whole screen now. Grab it HERE if you want to try.
Why don't you just flash a superuser zip from twrp, it will take care of the files, permissions and starting the daemon for you. You can grab ClockworkMod's superuser installer here: http://download.clockworkmod.com/superuser/superuser.zip
Click to expand...
Click to collapse
"Twrp image" Link is dead

Guy I know this is bringing up a thread from the dead but a question. I did install TWRP but my issue is when in TWRP to do a backup it is only backing up about 60MB of data even w/ all partitions chosen. It shows 0MB in data, is there a way I can back up the entire ROM like you can do on my android based phones w/ TRWP or CM recovery? Also I've read how to switch to stock recovery but whenn I go to TWRP and backup it just backs up TWRP backup files (ext4.win) no .img file is created. I think I just need a copy of the stock recovery.img and then i'd be golden. Am I wrong? If im not, does anyone know where I can find that?
Thanks
Dave

TT_Vert said:
Guy I know this is bringing up a thread from the dead but a question. I did install TWRP but my issue is when in TWRP to do a backup it is only backing up about 60MB of data even w/ all partitions chosen. It shows 0MB in data, is there a way I can back up the entire ROM like you can do on my android based phones w/ TRWP or CM recovery? Also I've read how to switch to stock recovery but whenn I go to TWRP and backup it just backs up TWRP backup files (ext4.win) no .img file is created. I think I just need a copy of the stock recovery.img and then i'd be golden. Am I wrong? If im not, does anyone know where I can find that?
Thanks
Dave
Click to expand...
Click to collapse
Yea i need the same, managed to lose my back up of it.

Have you guys ever gotten this to back up the data partition? It always says 0mb.

Was able to take the recovery.img from a joying update.. if someone needs it let me know ill send a link.

PLEASE!!

TT_Vert said:
PLEASE!!
Click to expand...
Click to collapse
Pm'd, xda isn,t letting me post links just yet. I guess i can not be trusted. Let me know if that works for you!

Must appreciated man, it was perfect. It seems TWRP is pretty much useless on these devices for bare metal backup/recovery like they are on phones.
Courtesy of jgarci44. Stock joying recovery

hi, this talk is the TWRP recovery for rockchip 3188? Excuse my intrusion would like to know how to install on my unit "kit kat 4.4.4"

don't waste your time currently.

TT_Vert said:
don't waste your time currently.
Click to expand...
Click to collapse
Why are you saying this ? Explain.

bettuccio said:
Why are you saying this ? Explain.
Click to expand...
Click to collapse
If you have to ask how to do it, most likely you won't be able to do anything with it at this point.
Sent from my Nexus 5X using XDA-Developers mobile app
---------- Post added at 08:37 PM ---------- Previous post was at 08:31 PM ----------
bettuccio said:
Why are you saying this ? Explain.
Click to expand...
Click to collapse
If you must here is a website where I got it (although not much you can do with it) be sure to have a mouse as the touch screen doesn't work. If you need to revert, which you will if you plan to update you will need to find a copy of the stock recovery.
http://freaktab.com/forum/main-category/freaktab-downloads/11780-twrp-2-7-0-0-for-rockchip-s
Sent from my Nexus 5X using XDA-Developers mobile app

rollback recovery stock
Hi.
Do you have any idea how to get back to the recovery stock version? I installed the TWRP under Rk3188 Stereo Card, it works fine but at the time of updating the file upgrade.img does not work.
Thanks you for your help.

I have a post on this somewhere. Search for it but here is what I have documented. Here is the joying stock recovery if that'll help you. https://www.dropbox.com/s/h5o46v24911nbsp/Joying stock recovery.img?dl=0 Same process as my post on installing TWRP on these except you use this image.
Dave

Ok, let me get this straight...
1. With TWRP you can't flash mcu.img (but you can flash update.img? how does this exactly work? how do I flash an update.img from TWRP? or do I lose the ability to flash update.img as well?)
2. The ROMs do not come with recovery images and overwrite TWRP? I thought they did, like other ROMs...