Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Please let me know of any issues you may run into.
What's new:
Kit Kat compatibility
Prevent scroll drifting in swipe recovery
minui: Allow devices to blank/unblank using LCD backlight
verifier: update to support certificates using SHA-256
Start healthd in recovery
copy logs to cache more aggressively
fix adb secure in recovery
fix mounting vold managed partitions
menu fixes
Add option: quick install from last location
cleanup code
allow clean reboots
Do data/media checks first in format_device()
Add support for performance control
Define paths for recovery settings files in a separate header
Adjust font size for tf700t 240dpi
su: Update for latest su daemon compatibility
install: Support downgrade scenarios
install: Fix possible overflow condition in the updater "scanner"
correctly mount tmpfs as /tmp in recovery
Use cat for adb backup
Fix up bu restore
New mount/format capabilities function for Mounts menu
Enable perf mode only in tar(.gz) compress/extract wrappers
Do not use performance mode during package install
Fix mkfs.f2fs calling in roots
Fix recovery reboot command by adding the init sys.powerctl property
Things I've tested and verified working:
Backups
Restores
Flashing update.zip files
Formatting partitions
Instructions:
Code:
fastboot -i 0x0B05 flash recovery recovery-kk-6047.img
fastboot -i 0x0B05 reboot
Code:
su
dd if=recovery-kk-6047.img of=/dev/block/mmcblk0p4; reboot
Download
Help? Click here...
Donate to the devs:
dasunsrule32
Source: https://github.com/CyanogenMod/android_device_asus_tf700t
Reserved...
Good News.
Download link is up.
Did the both of you receive your devices
Sent from my SPH-D710 using Tapatalk 2
gmfeny said:
Did the both of you receive your devices
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
xplodwild got his, I'm waiting on mine. It's out for delivery.
Is this better than the TWRP recovery?
Schrotty35 said:
Is this better than the TWRP recovery?
Click to expand...
Click to collapse
It's a different recovery, test it and see. This isn't touch recovery. I'll build touch recovery soon.
Rock on!! Great to see the explosion of new stuff for our Infinitys, thanks and hats off to the devs.
Any chance someone has a guide on how to change between TWRP and CWM, or vice versa?
pbrauer said:
Rock on!! Great to see the explosion of new stuff for our Infinitys, thanks and hats off to the devs.
Any chance someone has a guide on how to change between TWRP and CWM, or vice versa?
Click to expand...
Click to collapse
Well, look out for official CM10 soon.
You should just be able to fastboot flash it.
pbrauer said:
Rock on!! Great to see the explosion of new stuff for our Infinitys, thanks and hats off to the devs.
Any chance someone has a guide on how to change between TWRP and CWM, or vice versa?
Click to expand...
Click to collapse
It's in the OP, just replace the desired recovery in the command.
This is old skool CW right? Friggin love non-touch version. Its what I'm use too!
chugger93 said:
This is old skool CW right? Friggin love non-touch version. Its what I'm use too!
Click to expand...
Click to collapse
Yes. I'm going to build CWM touch though soon. It'll be a separate thread.
dasunsrule32 said:
Yes. I'm going to build CWM touch though soon. It'll be a separate thread.
Click to expand...
Click to collapse
great job bud, lookin forward to your CM10 version for the TF700 as well!!
Deduped and incremental backups!? Awesome. Going to have to test this out tonight.
Awaiting the touch version then, I can't stand using those mushy volume keys to navigate lol
GREAT!!
Finally! I can't stand TWRP. I've been using CWM for so long, I can't believe it's finally here for the TF700T. Thanks for the hard work (I already hit the Thanks button).
psych2l said:
Awaiting the touch version then, I can't stand using those mushy volume keys to navigate lol
Click to expand...
Click to collapse
You may be waiting a bit. I've got some more bugs to work out, but if you can wait, then cool.
Nice CWM
Though I got a problem
I flashed it trough fastboot and it boots into cwm just fine, but the volume buttons doesnt do a thing, So I can't change in the menu. The power button works just fine.
Flashed the JB from the TF300 so I got that bootloaded, maybe that is the problem?
rdejager said:
Nice CWM
Though I got a problem
I flashed it trough fastboot and it boots into cwm just fine, but the volume buttons doesnt do a thing, So I can't change in the menu. The power button works just fine.
Flashed the JB from the TF300 so I got that bootloaded, maybe that is the problem?
Click to expand...
Click to collapse
Yeah, make sure you're on the tf700 b/l.
Related
CyanogenMod is a free, community built distribution of Android 2.3.7 (Gingerbread) which greatly extends the capabilities of your phone.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
cyanogen said:
This is an AOSP-based build with extra contributions from many people which you can use without any type of Google applications. I found a link from some other project that can be used to restore the Google parts, which can be found below or elsewhere in the thread. I've still included the various hardware-specific code, which seems to be slowly being open-sourced anyway.
Click to expand...
Click to collapse
Visit the CHANGELOG for a full list of changes and features!
All source code is available at the CyanogenMod Github!
If you'd like to to contribute to CyanogenMod, checkout our Gerrit instance (howto).
INSTRUCTIONS:
- First time flashing CM 7 to your Desire (or coming from another ROM)?
1. Root your device and install Clockwork Recovery (Unrevoked method is recommended).
2. Do a Nandroid backup!
3. WIPE (wipe data/factor reset + wipe cache partition)
5. Install the ROM
6. Optionally install the Google Addon
HOW TO REPORT BUGS OR PROBLEMS?
- Was it a hard reboot? Go into recovery and dump the "/proc/last_kmsg" file.
- Was it a soft reboot or a "boot loop"? Run "adb logcat" and get send the full output.
- Pastebin links preferred
- Please use the issue tracker whenever possible!
Please visit the CyanogenMod Wiki for step-by-step installation walkthroughs and tons of other useful information.
This is the latest release candidate so any and all feedback is appreciated!
The preferred method of installation is via ROM Manager, or you can head over to the CM Forums for manual downloads.
Latest version: 7.2.0-bravo - 18/03/2012
Download: CyanogenMod Mirror Network
Also available for download via ROM Manager
Google Addon:
Download: http://goo-inside.me/google-apps/
CM7 HBOOT r2 by Alpharev | xda thread
Change partition table size 145/5/287 (system/cache/size)
Upgrade instruction:
1) Nandroid backup in recovery.
2) Verify the MD5SUM of the file you downloaded against the one in the table.
3) Flash HBOOT with your phone in fastboot mode (Back+POWER) -> 'fastboot flash hboot bravo_alphaspl-cm7r2.img'
4) 'fastboot reboot-bootloader'
5) 'fastboot erase cache'
6) Boot recovery, wipe everything, advanced restore system & data, install CM7 again (same version or a newer one).
Legacy App2SD:
Simple2Ext (Easy with a GUI)
CM7 Legacy App2SD Addon Script (For Advanced user, Command Line)
Thank you to EVERYONE involved in helping with testing, coding, debugging and documenting! Enjoy!
reserved for future use
Thank you!
Cant wait to see first CM9 Nightlies (yes i know it will be difficult to do because of HTC and QCOM but i still have hope)
Gr8!I'm downloading now,i know it takes too much to have such another rc version,thank you devs!
Sent from my HTC Desire using XDA
Download is very very slowly... :-(
Inviato dal mio HTC Desire usando Tapatalk
Quit complaining about the downloadspeed. Do you have any idea how many of us are probably downloading this rom right now?
via xda app
i try all rom,not all but many,and today is my first cyanogenmod
thanks
Jordywild said:
Download is very very slowly... :-(
Click to expand...
Click to collapse
http://www.cyanogenmod.com/blog
7.2RC1 is out for "only" 70 devices
Its probably placebo but this release candidate seems a lot smoother than the last nightlies. So issues so far. :thumbup:
via xda app
Im having problems installing market applications like:
SMS backup and restore
Call logs backup and restore
and other applications
Just in case you have successfully installed one of the following please post it. Maybe its my installer or something.
Thanks!
SMS backup and restore is fine. I just had my messages restored. Same with the other apps. I would suggest a clean install if you are having trouble.
via xda app
Thanks for everyones hard work on this. If upgrading from 7.1 can someone confirm if I need to do a wipe?
Thanks,
Womble
Update from CM 7.1.0 work? Because i get bootloop...
19blacktiger77 said:
Update from CM 7.1.0 work? Because i get bootloop...
Click to expand...
Click to collapse
Have you got EXT4 partition?
Is Cyano 7.2 compatible with EXT4 o EXT3 partition?
Jordywild said:
Have you got EXT4 partition?
Is Cyano 7.2 compatible with EXT4 o EXT3 partition?
Click to expand...
Click to collapse
I'm running 7.2.0RC1 with an ext3 partition. I have S2E installed for app2sd. I didn't upgrade from 7.1 though, I did a full wipe when I installed 7.2.0RC1.
frankoid said:
I'm running 7.2.0RC1 with an ext3 partition. I have S2E installed for app2sd. I didn't upgrade from 7.1 though, I did a full wipe when I installed 7.2.0RC1.
Click to expand...
Click to collapse
Full wipe?
I've got "only" 90 app installed.
Ok: I need a backup with Titanium.
You need to modify mountsd on the initd folder prior to flashing if you want the rom to see your ext4 partition... or flash ManU kernel.
http://forum.xda-developers.com/showpost.php?p=23017080&postcount=6689
via xda app
GPS does not works with this version... back to 7.1
Home button does not work... buggy...
Back to 7.1!
Jordywild said:
Have you got EXT4 partition?
Click to expand...
Click to collapse
Yes!
stankyou said:
You need to modify mountsd on the initd folder prior to flashing if you want the rom to see your ext4 partition... or flash ManU kernel.
http://forum.xda-developers.com/showpost.php?p=23017080&postcount=6689
via xda app
Click to expand...
Click to collapse
carval2k said:
GPS does not works with this version... back to 7.1
Click to expand...
Click to collapse
I will stay on 7.1 too...
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.1 (Jelly Bean), which is designed to increase performance and reliability over stock Android for your device.
WARNING: I've bricked my tablet into APX mode around the 10th time of flashing this ROM (recovery froze and it rebooted into APX). The new (Update 1) recovery should be safer than the old one, but flash at your own risk!
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Device-specific source code for the Acer A700 are available from https://github.com/CyanogenMod/android_device_acer_a700 and https://github.com/CyanogenMod/android_kernel_acer_t30
Do not submit bug on CyanogenMod issue tracker
Downloads
Latest Nightly: http://get.cm/?device=a700
Google Apps: http://goo.im/gapps
Installation
Install CWM recovery from http://forum.xda-developers.com/showthread.php?t=1791165 (note that the old touch version will not work because of incorrect default.prop from CWM builder)
Do a Nandroid Backup!
Install the ROM using ClockworkMod Recovery
Optionally install the Google Addon
Wipe data if coming from stock
Changelog
A rough changelog is (will be) available here:
http://changelog.bbqdroid.org/#/cm10/a700 or http://cm10log.appspot.com/?device=a700
Reporting Bugs
You are allowed to report bugs only in this thread.
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. The following is a useful format to follow.
Code:
What is your--
Phone model:
Radio (baseband):
CM version:
CM Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
CMSettings/Performance settings (other than stock):
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
Older pre-nightly Download
See this post.
Note to Official JB Users
Jelly Bean bootloader is only supported on 201212023-EXEPRIMENTAL and later NIGHTLIES.
Awesome!
will flash it later when back from work and provide feedback (too annoyed with the stock rom atm) so i will give it a go!
cheers
Awesome! Pace is speeding up. Thanks for your efforts.
pawitp said:
...
[*]Install CWM recovery from http://www.mediafire.com/?9usi98fs7jpdf7w (the touch version in the other thread will not work because of incorrect default.prop from CWM builder)
...
Click to expand...
Click to collapse
The CWM is not the one from the "CWM Recovery 6.0.1.0 for A700" thread, right?
Cheers
Peter
aticatac said:
Awesome! Pace is speeding up. Thanks for your efforts.
The CWM is not the one from the "CWM Recovery 6.0.1.0 for A700" thread, right?
Cheers
Peter
Click to expand...
Click to collapse
No, read inside the brackets
The "CWM Recovery 6.0.1.0 for A700" has broken build prop and will cause the device check to fail.
pawitp said:
No, read inside the brackets
The "CWM Recovery 6.0.1.0 for A700" has broken build prop and will cause the device check to fail.
Click to expand...
Click to collapse
Actually, I did read inside the brackets, but the CWM in the mentioned thread is not a touch version, or so I thought, that's why I asked.
EDIT: Now I realised that we were talking about the exact same thread title.
Anyways, I will flash this one, give it a whirl and read twice or more next time.
Jeez, where is my mind...
Thanks again.
Does the CM10 include the performance update?
does anyone else get e:Can't mount /sdcard/ ?
cwm tells me can't mount sdcard and emmc but data, cache and system mount fine (backup even stores on the sdcard under cwm folder)
Can you give us the MD5 CWM recovery ? Thx
ups forgot the most important screen
just redid it same error
PS:
(used your recovery.img as stated above)
Buster99 said:
ups forgot the most important screen
just redid it same error
PS:
(used your recovery.img as stated above)
Click to expand...
Click to collapse
dou you have an external sd card?
looking forward for cm on the a511. have fun with your a700
Sent from my A511 using XDA Premium HD app
What size should do the Nandroid Backup ? Mine do 15Mo !
Blindie said:
dou you have an external sd card?
Click to expand...
Click to collapse
yes but took it out prior flashing the recovery.img so atm no - no 2nd sdcard
Does it wipe the internal storage ?
imtheyoyo said:
What size should do the Nandroid Backup ? Mine do 15Mo !
Click to expand...
Click to collapse
mine is 165mb
aibo said:
Does it wipe the internal storage ?
Click to expand...
Click to collapse
should not since after successfull install you wipe cahce and dalvik not sd
i just reflashed the recovery - still no joy
Very nice ! Tanks a lot !
But no sound for me ...
Have you got sound ?
enico64 said:
Very nice ! Tanks a lot !
But no sound for me ...
Have you got sound ?
Click to expand...
Click to collapse
I have sound.
So far so good, thank you.
I do enjoy the lack of bloat.....
aibo said:
Does it wipe the internal storage ?
Click to expand...
Click to collapse
The installer doesn't, but you'll need to wipe data for it to boot successfully. Wiping data won't wipe your internal sdcard though.
I'm getting the triangle of death after flashing the recovery in the OP...
I had the other CWM you posted in the other thread which the tablet seemed to boot into just fine.
i'm running a a700 with the a701 rom from way back, is that my issue?
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
*/
..:: Introducing Skinny ROM ::..
Based on KOT49I.V4101d
Stock Kernel
Debloated
Deodexed
Zipaligned
Rooted
Busybox
Init.d Support
More to come!
..:: Flashing Instructions ::..
1. Download ROM and save to sdcard
2. Boot into TWRP Recovery
3. Perform a full backup
4. Factory reset, wipe cache and system
5. Flash ROM
6. Reboot
7. Enjoy! (Optional)
..:: Downloads ::..
Skinny ROM v410
XDA:DevDB Information
Skinny ROM for v410, ROM for the LG G Pad 10.1
Contributors
timmytim
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: V410 Only
Based On: Stock
Version Information
Status: Beta
Current Beta Version: 1.0
Beta Release Date: 2015-03-02
Created 2015-03-03
Last Updated 2015-03-02
Reserved
..:: Known Issues ::..
Upon first boot, the Google and AT&T Folder on the Homescreen have missing icons. - Delete both folders and recreate if desired
Do we have any chance on porting this for the v400?
Thanks Tim. I very much appreciate the slimmed down ROM! This should hold me over till you get around to porting Candy!
Thanks for this. I haven't had a chance to try it yet due to work, but I definitely will this weekend. Thanks for taking the time to create ROMs for the v410.
izzet3838 said:
Do we have any chance on porting this for the v400?
Click to expand...
Click to collapse
I only have the v410 but if you can get me system and boot dumps I can probably whip something up for you v400 owners
timmytim said:
I only have the v410 but if you can get me system and boot dumps I can probably whip something up for you v400 owners
Click to expand...
Click to collapse
Is right? Do you compile for v400?
And you can compile cm12? Please
eduardozeassesme said:
Is right? Do you compile for v400?
And you can compile cm12? Please
Click to expand...
Click to collapse
If you or someone else can get me system and boot dumps for the v400 I can make a deodexed deflated rom.
Can up any twrp backup?
ok bro do you just need a cwm backup or what do you mean by system backup?
tell me and i'll make and send them to you
(device is rooted and cwm installed so shouldn't be a problem)
Got this installed and it is running great! Thanks for giving this tablet new life. I guess I should take down the 'for sale' ad on craigslist now. I'm excited to see what's ahead for us here!
izzet3838 said:
ok bro do you just need a cwm backup or what do you mean by system backup?
tell me and i'll make and send them to you
(device is rooted and cwm installed so shouldn't be a problem)
Click to expand...
Click to collapse
I need both system and boot images, you may wanna grab your recovery while you're at it.... You'll need to get them from ADB or if you're careful you can get them from a Terminal Emulator app.
...YOU MUST BE ROOTED TO RUN THESE COMMANDS...
Run the following commands from ADB shell or Terminal Emulator...
First you need to acquire root
Code:
su
Grab System Partition
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/system of=/sdcard/system.img
Grab Boot Partition
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/sdcard/boot.img
Grab Recovery Partition
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/sdcard/recovery.img
This will spit out 3 images on your internal sdcard so make sure that there is room on there. Should be about 2GB of stuff, maybe a little more...
After they are on your sdcard copy them to your computer and upload them somewhere please.
I tried with the android terminal emulator app but it didn't work can you please gibe me some specific info om how to do it
izzet3838 said:
I tried with the android terminal emulator app but it didn't work can you please gibe me some specific info om how to do it
Click to expand...
Click to collapse
Hey, sorry I should have mentioned that you must be rooted to run these commands. I went ahead and updated the post with the commands above to include acquiring root. Let me know if you still need more help.
I stalled this ROM last night. Works great. Hangs on the AT&T logo for a bit on first boot (like any ROM), so don't think it's frozen, just give it a few minutes.
Sent from my LG-V500 using XDA Free mobile app
Bro i'm uplouding the system file now it's 2gb but i have a useless uploud speed so it will probably take a while when done i'll dm the files too you
LeighR said:
I stalled this ROM last night. Works great. Hangs on the AT&T logo for a bit on first boot (like any ROM), so don't think it's frozen, just give it a few minutes.
Sent from my LG-V500 using XDA Free mobile app
Click to expand...
Click to collapse
Were you able to advance restore data from previous backup after Skinny Rom installation? Or did you even try?
Flashed this last night... Forgot to enable WiFi... Clean install + 50 apps hurts the data....
Flashed this last night, and I can definitely tell a difference between this and stock. I'm still not overly impressed with this tablet, I hope this is just the beginning.
I've been away from android for some time now. Do we still have access to compile and flash custom kernels?
Hoping the biggest issue with this tablet isn't the 1gb of ram. It's really sluggish at times.
Swizzle82 said:
Were you able to advance restore data from previous backup after Skinny Rom installation? Or did you even try?
Click to expand...
Click to collapse
I didn't try. I do have a back up but I didn't need it.
Sent from my LG-V500 using XDA Free mobile app
CM13.0 (Marshmallow) unofficial builds for the TATE
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 6.0 (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at any of us for messing up your device, we will laugh at you.
* Collectively, and at the same time.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review.
download:
new: https://www.mediafire.com/folder/u7sb7p10ik7v0/tate
old:https://www.mediafire.com/folder/5a97vbv93k24n/tate
old:https://www.mediafire.com/folder/w9nh7oyabwvww/tate
backup before flash, gapps need for upgrade, don`t flash SuperSU
deep sleep fixed
http://opengapps.org/ (arm, 6.0)
Kernel auditor - Low memory killer - Very aggressive
If you install Gapps after the ROM has been booted for the first time you either need to wipe data and reboot. Without this Gapps will crash constantly. This is due to the new permissions-system in M.
bluetooth lte-version fix: https://forum.xda-developers.com/ki...elp/kindle-fire-hd-8-9-bluetooth-rom-t3315904
Great, now it's time to bring TWRP 3.0.0.0 for better results.
alexander_32 said:
Great, now it's time to bring TWRP 3.0.0.0 for better results.
Click to expand...
Click to collapse
TWRP 3 is not really a necessity. People have been flashing MM numerous times with 2.8.x.x builds for a while now without trouble.
build 20160215 (backup before flash, gaaps need for upgrade): http://www.mediafire.com/download/pj2994j9p358tit/cm-13.0-20160214-UNOFFICIAL-tate.zip
xWolf13 said:
TWRP 3 is not really a necessity. People have been flashing MM numerous times with 2.8.x.x builds for a while now without trouble.
Click to expand...
Click to collapse
Look at TWRP changelog:
https://twrp.me/site/update/2016/02/05/twrp-3.0.0-0-released.html
It has sense!
I'll try to compile it later (I don't know when).
alexander_32 said:
Look at TWRP changelog:
https://twrp.me/site/update/2016/02/05/twrp-3.0.0-0-released.html
It has sense!
I'll try to compile it later (I don't know when).
Click to expand...
Click to collapse
If you do plan on compiling, use transi's github repos (found here). I have a prebuilt manifest with the repos already configured that you can place in the hidden .repo folder of your Android build environment if you need it up on my GitHub here.
(I recommended transi's repos because they're more up to date, and there's also that custom Marshmallow boot logo. )
Sent from my Amazon Jem using XDA Labs
monster1612 said:
If you do plan on compiling, use transi's github repos (found here). I have a prebuilt manifest with the repos already configured that you can place in the hidden .repo folder of your Android build environment if you need it up on my GitHub here.
(I recommended transi's repos because they're more up to date, and there's also that custom Marshmallow boot logo. )
Sent from my Amazon Jem using XDA Labs
Click to expand...
Click to collapse
Thank you very much :good::good::good:
@transi1 Great rom! Very fluid. Only issue is the lack of deepsleep. Do you have an idea what might be causing it?
Also I flashed the ROM with Twerp 2.7.x.x so Twerp 3.0 is not required (but if you guys build it,i'll still take it )
Thanks for bringing CM13!
hope this rom to be official
build 20160218 (backup before flash, gapps need for upgrade, don`t flash SuperSU): http://www.mediafire.com/download/j18vp0uo1mca0qa/cm-13.0-20160218-UNOFFICIAL-tate.zip
deep sleep fixed
Screenshots please??
transi1 said:
build 20160218 (backup before flash, gapps need for upgrade, don`t flash SuperSU): http://www.mediafire.com/download/j18vp0uo1mca0qa/cm-13.0-20160218-UNOFFICIAL-tate.zip
deep sleep fixed
Click to expand...
Click to collapse
My battery thanks you. From what I can tell, everything that was working in cm12.1 also works in cm13. Along with very aggressive memory killer recommended from OP, I'm also using max cpu freq 1500MHz with performance governor and deadline scheduler with 512kB read-ahead in kernel adiutor and the performance is good. In cm12 I remember several crashes with the same cpu oc but for now it seems stable.
How do I get root for cm13? I dare not flash SuperSU.
Sent from my Amazon Tate using Tapatalk
Jrhoop said:
How do I get root for cm13? I dare not flash SuperSU.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
LOL! Definitely don't flash supersu! Just got my kindle back up from soft bricking it that way.
Jrhoop said:
How do I get root for cm13? I dare not flash SuperSU.
Click to expand...
Click to collapse
Isn't the risk of flashing stuff half the fun? If you like flashing stuff on tate you should pick up a fastboot cable as good practice, you can grab one from china for <$4.
Anyway, supersu works just fine, you just have to make sure it doesn't install in systemless mode by default which patches boot incorrectly.
Simply pass this line in TWRP (advanced>terminal) before flashing supersu zip:
Code:
echo SYSTEMLESS=false>>/data/.supersu
You'll see it say "System mode" in the output from flashing if you've done it correctly. If not, make sure you don't reboot yet, and just re flash a working rom zip to restore boot.img (like cm13 from OP).
r3t3ch said:
Isn't the risk of flashing stuff half the fun? If you like flashing stuff on tate you should pick up a fastboot cable as good practice, you can grab one from china for <$4.
Anyway, supersu works just fine, you just have to make sure it doesn't install in systemless mode by default which patches boot incorrectly.
Simply pass this line in TWRP (advanced>terminal) before flashing supersu zip:
Code:
echo SYSTEMLESS=false>>/data/.supersu
You'll see it say "System mode" in the output from flashing if you've done it correctly. If not, make sure you don't reboot yet, and just re flash a working rom zip to restore boot.img (like cm13 from OP).
Click to expand...
Click to collapse
Yes I guess, but usually not sensible to do the opposite of what the developer said. I have a fast boot cable, actually two as I thought I had lost one. My attempt at flashing twrp last week using flasify didn't go so all. Anyway fixed that up and the kindle lives on.
I'm on philz recovery and not twrp but I'm guessing the instructions are fairly similar?
Sent from my Amazon Tate using Tapatalk
Jrhoop said:
Yes I guess, but usually not sensible to do the opposite of what the developer said. I have a fast boot cable, actually two as I thought I had lost one. My attempt at flashing twrp last week using flasify didn't go so all. Anyway fixed that up and the kindle lives on.
I'm on philz recovery and not twrp but I'm guessing the instructions are fairly similar?
Click to expand...
Click to collapse
If you can enter fastboot you have nothing to fear. TWRP is the only recovery that is consistently updated and is highly recommended over philz/cwm. Download TWRP 2.8.7.0 and extract the img from the zip.
I've never been a fan of flashing tools from within android. It's much simpler to just go into fastboot and use:
Code:
fastboot -i 0x1949 flash recovery kfhd7-twrp-2.8.7.0-recovery.img
You don't need to flash SuperSU. Enable dev mode then select dev settings and change the root setting
Maromi said:
You don't need to flash SuperSU. Enable dev mode then select dev settings and change the root setting
Click to expand...
Click to collapse
Hey what rom are you running on the KFHD?
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Code:
#include <std_disclaimer.h>
/*
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
Features:
- sdcard
- Decryption works
- Otg works
- F2FS support
- Fastboot boot command support
- Fastbootd
Not working:
- backups
- other?, you tell me
DANGER:
- NO SLOT CHANGER (BRICK DEVICE)
Download:
UPDATE 01-03-2023
This project it abandoned , I don't have the phone to continue the development
last android supported it A11 not flash on 12+ and
(stableR.25) (LAST) (finally for end support support a11-)
(stableR.21)(old)
To Flash the TWRP:
INSTALL RECOVERY (PERM INSTALL)
Code:
fastboot flash recovery twrp.img
BOOT RECOVERY (TEMP BOOT)
Code:
fastboot boot recovery twrp.img
Reccomended ADB and Fastboot binaries (FOR MOTOROLA DEVICES):
TinyFastbootScript
Source code:
https://github.com/Teamwin/android_bootable_recovery
https://github.com/Moto-tree-folders
COFFE:
Paypal
BETAR (R) = BETA
=============================================
=============== CHANGELOG ================
=============================================
UPDATE 01-03-2023
This project it abandoned , I don't have the phone to continue the development
stable r.25
update TWRP source to 3.5.1-r10.0 (source for dynamic)
stable r.21
- fix touch for ft8756 display
- improve partitions
fix backups and rework dt
- reduce 67mb to 35mb recovery
stable r1 (final betar )
- fix Decryption
betar 18 ()
- fix sdcard
- Decryption don't works (break for now)
betar 17 (private)
- private build
betar 16
- update source code to TWRP 3.5.0_10 (build with - - -OMNI/AOSP 10)
betar 15
: build fastbootD (install work c
touch work in nova display
===============================================
============= TOUCH NO WORK?? ===============
===============================================
report you display
USE:
adb shell
ls /sys/class/touchscreen
and send me you display name in telegram
I thought it was a personalized recovery alternative! I'm still expecting. :confuso: :confuso:
ramasterdev said:
I thought it was a personalized recovery alternative! I'm still expecting. :confuso: :confuso:
Click to expand...
Click to collapse
yep , twrp is custom recovery
Thank you Sebastian for your efforts.
I tried this TWRP by "fastboot boot recovery.img" without flashing it.
Because I'm rooted I checked my sys/class/touchscreen to see if I had a novatek screen.
NVT-ts
Novatek_ts
Thanks for confirming that this was the correct screen Sebastian!
sebastian3567HD said:
Reserved
changenlog:
beta 15
: build fastbootD (install work c
touch work in nova display
no work touch report you display
adb shell
ls /sys/class/touchscreen
and send me you display name
telegram https://t.me/seba_3567
Click to expand...
Click to collapse
My display is ft8756
Thanks
ReneZeiss said:
View attachment 5153427
Click to expand...
Click to collapse
work
Kikowtf said:
My display is ft8756
Thanks
Click to expand...
Click to collapse
I'm still working to put that screen to work!
ReneZeiss said:
Thank you Sebastian for your efforts.
I tried this TWRP by "fastboot boot recovery.img" without flashing it.
Because I'm rooted I checked my sys/class/touchscreen to see if I had a novatek screen.
NVT-ts
Novatek_ts
Thanks for confirming that this was the correct screen Sebastian!
Click to expand...
Click to collapse
test in NVT-ts (work) (use fastboot boot recovery.img for test you display )
Hi Sebastian,
I also have a new Moto G9 Plus and the touchscreen is ft8756. I've tried various TWRP images with the same result; unable to enter anything on the touchscreen.
I understand from the posts that you are still working on this touchscreen.
I have searched Google and the forums and cannot find a feasible answer. I am unable to create a full backup on internal or external storage due to the error seen in the screenshot (it gets stuck in the same position with the same error on both storages). Can someone point me in the right direction or assist me in rectifying the issue? Thanks in advance.
Have new g9 plus and after recovery flash end up in bootloop TWRP can't control because touch screen not working.... 200€ bye bye.....
Waiting for new Odessa file
hampik said:
Have new g9 plus and after recovery flash end up in bootloop TWRP can't control because touch screen not working.... 200€ bye bye.....
Waiting for new Odessa file
Click to expand...
Click to collapse
turn the phone off, boot into fastboot, and flash the stock image (you'll have to search for how to flash stock image on this phone), and see if that will fix the issue
Not-working touch screen I'm bypass this issue
by using PC mouse put USB receiver in phone trough USB-c to USB from Samsung box
now I'm root with new type of display
+1 touchscreen ft8756, is it possible to use it with other twrp?
Miha1l said:
+1 touchscreen ft8756, is it possible to use it with other twrp?
Click to expand...
Click to collapse
Here's a link to a tested working copy of TWRP for Odessa: https://www.androidfilehost.com/?fid=17248734326145738599
A working copy of TWRP 3.5.0 that works with ft8756 touchscreen. I have personally tested it - https://www.androidfilehost.com/?fid=17248734326145738599
hampik said:
Have new g9 plus and after recovery flash end up in bootloop TWRP can't control because touch screen not working.... 200€ bye bye.....
Waiting for new Odessa file
Click to expand...
Click to collapse
can you explain that better?
hampik said:
Not-working touch screen I'm bypass this issue
by using PC mouse put USB receiver in phone trough USB-c to USB from Samsung box
now I'm root with new type of display
Click to expand...
Click to collapse
can you give me information about your problem?