UAPM is an advanced tool designed for advanced users. UAPM is the only application
universally thought, addition to being the safest, never use shell to manage the
system partitions of your device.
Please, see all screenshots here to get a better sense of application.
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 APP
* before installing 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.
*
* THIS APPLICATION WAS NOT MADE FOR BEGINNERS, IF YOU ARE A BEGINNER, USE ANOTHER APPLICATION
* FOR EXAMPLE RASHR OR FLASHIFY, THE MAIN OBJECTIVE OF THIS SOFTWARE IS MANAGING ALL PARTITIONS
* AND NOT JUST BOOT AND RECOVERY! AND YES, THIS APPLICATION USES THE GLORIOUS DD BINARY...
* THE REST OF THE SAME SOFTWARE CATEGORY!
*
*/
Features
Flash and Backup partitions.
Generate MD5 built-in partition.
Check MD5 of your files easily.
Get outputs processes with logging.
Set block size for writing partitions.
Quick Power Menu.
Auto reboot after flash.
Requirements
Any device running Android 4.1.2+
Device with root and busybox.
Partition layout of your device.
Changelog
Release v1.41 - CURRENT
Fixed critical issue on Flash.
Click to expand...
Click to collapse
Release v1.0
Initial release
Click to expand...
Click to collapse
Release v1.1
Added Strings (if you are willing to translate this, PM me)
Little change in method to create folders on the /sdcard to avoid I/O errors
Added option to clean logs:fingers-crossed:
Click to expand...
Click to collapse
Release v1.2
Implemented new logs messages for easy outputs indetification
Added Power menu feature(If you have a hardware problem or simply a quick option):fingers-crossed:
Added Auto Reboot feature(To save your time, now an optional to auto restart after flash):fingers-crossed:
Small fix on Strings(Wrong Strings:angel
Cleaned/Optimized code:good:
Click to expand...
Click to collapse
Release v1.21
Removed unused resources(Some unused .png and .db files):silly:
Fix Hardcoded Strings(Missing strings)
Enabled ZipAlign and ProGuard(Minify) for this build:fingers-crossed:
Fixed SharedPreferences commit issues:good:
Click to expand...
Click to collapse
Release v1.22
Optimized template.
Click to expand...
Click to collapse
Release v1.3
Now the application search for root at startup and not before operations.
Reduced the number of calls in operations.
Reduced the number of operations after the Runtime.exec call.
Added new logs to better error identification.
Added MD5 verification in your files.
Fixed runtime errors!
New dialogs to identify the exact exception.
Click to expand...
Click to collapse
Release v1.4 - CURRENT
Reduced the number of calls BufferredWrite() on Logger()
Now the BufferredWrite() is called only if input is valid.
Improved the accuracy of controls, now the result
comes from OnPostExecute() and not the catch block in AsyncTask.
Added the feature "Command Preferences", you can now
configure the write block size to increase performance.
Small FIX to delete the logs. Prior to erase written
log a new file was not created causing problems.
Implemented new md5sum algorithm, Now this is same to TWRP md5 checking!
Click to expand...
Click to collapse
Get it on DOWNLOAD page.
XDA:DevDB Information
UAPM, App for all devices (see above for details)
Contributors
ferreirawax
Version Information
Status: Stable
Created 2014-12-18
Last Updated 2015-01-07
Before you upgrade to v1.4, uninstall the previous version and delete the UAPM folder to not create problems!
To use MD5 is very easy, just put in the same directory the file with the md5
hash of the same name of the file you will use to flash, for example, Your file
is called "mypartition-12-15-15.img", The hash must be named "mypartition-12-15-15.img.md5".
The contents of the hash is like this:
Code:
63221739e3a5624583a31391a63b361c mypartition-12-15-15.img
Code:
This is MD5 hash This is file name
Recalling that the backups made using UAPM already have MD5 hash. It is not necessary
to have a md5 hash to flash using UAPM, but it is highly advisable.
I think the power of it scares alot of us lol. But great job!!
xsteven77x said:
I think the power of it scares alot of us lol. But great job!!
Click to expand...
Click to collapse
Thanks for the feedback! UAPM is a "Intelligent GUI" for those who frequently use the binary "dd", Using carefully certainly not will bring problems
Uh, sounds great! Must try.
Nice App
Very Useful
New release guys, Checkout changelog! :fingers-crossed:
Oooh yay! I have been trying to repartition my Find5 but couldnt get it to work so I put that project on ice a few days ago.
With this it might work!
Gonna try it tomorrow and will let you know how it goes.
Sent from my FIND7 using XDA Free mobile app
I got "error while phase package"…
Ps. I'm on ICS 4.0.3
Sorry for my bad English...
Sent from my HTC Desire 200 using XDA Premium 4 Mobile app
Maybe a simple reason for error.
ferreirawax said:
Requirements
Any device running Android 4.1.2+
Click to expand...
Click to collapse
dicks93277 said:
I got "error while phase package"…
Ps. I'm on ICS 4.0.3
Click to expand...
Click to collapse
Requirements state Android 4.1.2+ so that could be reason.
Interesting app. for that
dicks93277 said:
I got "error while phase package"…
Ps. I'm on ICS 4.0.3
Sorry for my bad English...
Sent from my HTC Desire 200 using XDA Premium 4 Mobile app
Click to expand...
Click to collapse
Later I've the possibility to work on 4.0+.
New update guys, with new features!
ferreirawax said:
Later I've the possibility to work on 4.0+.
Click to expand...
Click to collapse
Still not working…
Sorry for my bad English...
Sent from my HTC Desire 200 using XDA Premium 4 Mobile app
dicks93277 said:
Still not working…
Sorry for my bad English...
Sent from my HTC Desire 200 using XDA Premium 4 Mobile app
Click to expand...
Click to collapse
Currently only 4.1.2 or higher is supported, I am thinking of the possibility to support 4.0+.
New small update guys! To avoid losing the pace
New update v1.22
Hi @ferreirawax,
Is this safe to use (even if its just to take a BACKUP in case anything happens "other" than the use of your App, that could be used to RESTORE original partition layout...?) on Samsung Galaxy Note (N7000) which suffers from eMMC brickbug, that if used with wrong kernel could potentially corrupt/kill the device...??
ie: Will this be fine to use on N7000, that suffers from an eMMC bug....?
- Neat App, and GUI btw...
Thanks, Lister
Lister Of Smeg said:
Hi @ferreirawax,
Is this safe to use (even if its just to take a BACKUP in case anything happens "other" than the use of your App, that could be used to RESTORE original partition layout...?) on Samsung Galaxy Note (N7000) which suffers from eMMC brickbug, that if used with wrong kernel could potentially corrupt/kill the device...??
ie: Will this be fine to use on N7000, that suffers from an eMMC bug....?
- Neat App, and GUI btw...
Thanks, Lister
Click to expand...
Click to collapse
UAPM does not have the power to restore partitions (Repartition the device). You can only flash/backup all partitions.
It is safe to use with responsibility.
Can i make swap partition on external sdcard?
@ferreirawax
I've wrote a few months ago a function which automatically detects the recovery and boot partition of a device
http://pastebin.com/rddAAQNW
it does not work on all devices, but for the most ones.
Related
CyanogenMod is a free, community built distribution of Android 2.3 (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. Update your radio! New radio from HTC 2.2+ roms is required (Desire Radio Thread).
4. WIPE (wipe data/factory reset + wipe cache partition)
5. Install the ROM
6. Optionally install the Google Addon
- Upgrading from earlier CM6?
1. Do a Nandroid Backup!
2. Install the ROM (your Google apps will be backed up automatically)
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.0.3-Desire - 06/05/2011
Download: update-cm-7.0.3-Desire-signed.zip
Also available for download via ROM Manager
MD5Sum: bb8145548867e2bc6b463d3803f99175
cyanogen said:
The 7.0.3 update is *ONLY* for people using 7.0.2* stable builds. You'll hose your system if you install it on a nightly from the last week (2.3.4/GRJ22).
Click to expand...
Click to collapse
Google Addon: 20110307 Universal
Download: http://goo-inside.me/google-apps/
Battery drain issue:
Set wifi sleep policy to never
settings -> wireless & networks -> wifi settings
press menu -> advanced and set wifi sleep policy to Never
press menu -> save
CM7 HBOOT by Alpharev | xda thread
Change partition table size 130/5/302 (system/cache/size)
Require nightly #18 or newer
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-cm7.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!
WOW great RC1 !!!
is the MMS issue already fixxed in this release?
thc ahead guys !!!!
dkm111
Awesome news! Flashing...
Thanks and keep up the good work!
finally rc1 - a lot of work in it...
great I will try it right now!
mad-murdock said:
finally rc1 - a lot of work in it...
Click to expand...
Click to collapse
hey how about a simpler changelog specific for desire ... like what works and what doesnt work of the essential hardware.....
eg: notification light works, camera doesnt work, proximity sensor works.....
stuff like that
hispeedworm said:
hey how about a simpler changelog specific for desire ... like what works and what doesnt work of the essential hardware.....
eg: notification light works, camera doesnt work, proximity sensor works.....
stuff like that
Click to expand...
Click to collapse
Yeah, that would be cool!
excellent! Great job guys! flashed up perfectly!
but I tried a reboot and I'm stuck on the boot screen/freezes and goes again lol. will restore backup and try again I guess
have been waiting for this, thanx
Finally
Roscopcoletrain said:
excellent! Great job guys! flashed up perfectly!
but I tried a reboot and I'm stuck on the boot screen/freezes and goes again lol. will restore backup and try again I guess
Click to expand...
Click to collapse
tried a 2nd time, and success rebooted just in case and all is well. Great job again folks!
hispeedworm said:
hey how about a simpler changelog specific for desire ... like what works and what doesnt work of the essential hardware.....
eg: notification light works, camera doesnt work, proximity sensor works.....
stuff like that
Click to expand...
Click to collapse
Short and simple:
what (should) work: everything but hd recording
What doesn't work: hopefully nothing
At least that's the experience from nightlies
Swyped with cyanogenmod 7 powered HTC Desire HD. Excuse typos
damn net is downloading it damn slow. grrr~~~
Great to see RC cyanogen rocks. Let me flash it today
LuffyPSP said:
damn net is downloading it damn slow. grrr~~~
Click to expand...
Click to collapse
You are probably not the only one downloading cm got huge network capabilities, but even those are used up when enough users download
Swyped with cyanogenmod 7 powered HTC Desire HD. Excuse typos.
Just about to give this a shot. Upgrading from the nightly build #23.
hey, any idea why my charging led turns green after it being in 90%? Anyone experiencing this problem as well?
RC1 is amazing no more launcher laggy issue, smoother than every other builds
just one thing , the time display on toolbar ,still no fix,it shows always 12hrs format 3:00 in the morning shows just 3:00 ,and 24hrs format just does'nt work ,always the same...hmm ,but no biggy
thank your great efforts and hard work
ParagonDevil said:
hey, any idea why my charging led turns green after it being in 90%? Anyone experiencing this problem as well?
Click to expand...
Click to collapse
Thats normal! When it hits 90 percent it turns green
Sent from my HTC Desire using XDA App
i read somewhere we need the new Clockworkmod for this?
is this true? because your installation post mentions nothing of it...
Because of the way the recovery is packed into boot, this will not work with all kernels / ROMs. It is known to work with CM7.2 and CM9.1.0. It will probably work with most other MTD-based ROMs and kernels but will not work with any BML ROM or kernel. Use at your own risk! Installing a new ROM or kernel may end up replacing your install of TWRP. Also note that TWRP is *not* compatible with CWM backups. We are not based on CWM, we wrote our own recovery based on AOSP. With that said, I hope that you will get a chance to at least see how fast and easy-to-use TWRP is.
In addition to the on-screen keyboard, TWRP now supports using the hardware keyboard on the Epic 4G. Unfortunately the screen doesn't rotate, but hey, the hardware keyboard does work.
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s 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.
Phone look:
Tablet look:
CHANGELOG for 2.6.3.0:
-Proper backup and restore of SELinux contexts (thanks to Tassadar)
-Pull in some ROM information for backup name generation
-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
-Add 1200x1920 theme (thanks to Tassadar)
-A few other fixes and tweaks
CHANGELOG for 2.6.1.0:
-Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
-Initial support for f2fs file system formatting (Moto X)
-Update SuperSU install for 4.3 ROMs
-Fixed a permissions bug on files created during backup
-Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
-Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
-Ignore lost+found folder during backup and size calculations
-Various other minor bug fixes and tweaks
CHANGELOG for 2.6.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!
-Can encrypt a backup to prevent theft of private data from your backup files
-Updated graphics / icon courtesy of shift
-Updated exFAT to latest commits
-Fixed a problem with Samsung TouchWiz decryption
-Update SuperSU binary
-Fixed saving of backup partitions list
-Fixed saving of last used zip install folder
-Fixed backup of datadata on devices that use a separate partition for datadata
-Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
-Fixed some problems with partitioning a SD card
-Various other bug fixes and tweaks
Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.
Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.
DOWNLOAD:
You can find more information and download links on our website!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
First. Thanks.
×Marcusant
Sick!!!"
Sent from my SPH-D700 using xda premium
Wow, this looks great, can't wait to try it out. Thanks TeamWin
Sent from my SPH-D700 using XDA
This will probably work on all mtd roms afaik.
×Marcusant
Niiiice
Part of the trick with this build of TWRP is the inclusion of a new utility that I've started working on called injecttwrp. It's a work in progress. I'll be building upon this to inject our recovery ramdisk into existing Samsung boot images so that you can choose to keep TWRP installed as you install new ROMs or kernels regardless of what recovery is included with the kernel or ROM that you are installing.
https://github.com/TeamWin/Team-Win-Recovery-Project/blob/master/injecttwrp/injecttwrp.c
Note that this utility is not restricted to just working with TWRP. It could be used to inject any recovery that you wanted.
Awesome, I use this for my Kindle Fire and love it. It also is the only current recovery that works with the new 3.0 kernel, but I think that is mainly a fire issue. I will try it when I get some time!
anyone confirm it works on ics (aokp particularly)?
This looks awesome
Just a thought.. marcusant.. could you build this recovery into nyan for sayyy cm7?
Sent from my SPH-D700 using XDA
Found the install for epicmtd... and as soon as it finished it booted me into recovery and attempted to flash and gave me a status 7... which is usually a signing failure.
Sent from my SPH-D700 using xda premium
Of course on the day I'm busiest is when this is released lmao. Thanks for the hard work guys, I'll be playing with this tomorrow for sure!
Sent from my SPH-D700 using xda premium
ÜBER™ said:
Found the install for epicmtd... and as soon as it finished it booted me into recovery and attempted to flash and gave me a status 7... which is usually a signing failure.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
The failure was an oddity with the formatting of our flash_image on ics as far as I can tell
×Marcusant
I might just have to yank the zip until I can figure it out, the manual install should work and I have it working in CM9 too.
Dees_Troy said:
I might just have to yank the zip until I can figure it out, the manual install should work and I have it working in CM9 too.
Click to expand...
Click to collapse
I mean it goes through everything but then stops towards the end... write_flash_image has an error and it shows E: /sdcard/goomanager/twrp.zip ... and aborts.. so what marcus said about the flash image.
Sent from my SPH-D700 using xda premium
hmm.. a nice shiny new touch recovery to play with (since we heard rumors about CWM Touch for the Epic but it never materialized.)
Might have to give this a shot.
Thanks!
pvtjoker42 said:
hmm.. a nice shiny new touch recovery to play with (since we heard rumors about CWM Touch for the Epic but it never materialized.)
Might have to give this a shot.
Thanks!
Click to expand...
Click to collapse
........interface similar to Epic CM Team's test touch recovery; will await sign from Dees_Troy + flash again.
.........sent from today's android = 4.0.4
I believe that the zip install should now be working!
Can't get it to download... won't show in my goomanager folder I made the mistake of enabling check signiture toggle and now it won't disable it when it tries to install it fails... and is not in the folder so I can toggle the sig verification and reflash via cwm....
Then I tried to share the link, copy it and then download via the browser its in the download folder now... I tried to flash that it says installation aborted (bad). Wtf?
Sent from my SPH-D700 using xda premium
ÜBER™ said:
Can't get it to download... won't show in my goomanager folder I made the mistake of enabling check signiture toggle and now it won't disable it when it tries to install it fails... and is not in the folder so I can toggle the sig verification and reflash via cwm....
Then I tried to share the link, copy it and then download via the browser its in the download folder now... I tried to flash that it says installation aborted (bad). Wtf?
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
I couldn't get it to install on cm7 says error installing blah blah (bad).. tried to download it twice.. both times errors
Sent from my SPH-D700 using XDA
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s 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.
Phone look:
Tablet look:
CHANGELOG for 2.6.3.0:
-Proper backup and restore of SELinux contexts (thanks to Tassadar)
-Pull in some ROM information for backup name generation
-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
-Add 1200x1920 theme (thanks to Tassadar)
-A few other fixes and tweaks
CHANGELOG for 2.6.1.0:
-Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
-Initial support for f2fs file system formatting (Moto X)
-Update SuperSU install for 4.3 ROMs
-Fixed a permissions bug on files created during backup
-Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
-Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
-Ignore lost+found folder during backup and size calculations
-Various other minor bug fixes and tweaks
CHANGELOG for 2.6.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!
-Can encrypt a backup to prevent theft of private data from your backup files
-Updated graphics / icon courtesy of shift
-Updated exFAT to latest commits
-Fixed a problem with Samsung TouchWiz decryption
-Update SuperSU binary
-Fixed saving of backup partitions list
-Fixed saving of last used zip install folder
-Fixed backup of datadata on devices that use a separate partition for datadata
-Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
-Fixed some problems with partitioning a SD card
-Various other bug fixes and tweaks
Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.
Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
OR:
You can find more information and download links on our website!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
XDA:DevDB Information
[RECOVERY] TWRP 2.6.3.0 touch recovery [2013-09-16], a Tool/Utility for the AT&T HTC One X
Contributors
eyeballer, dees_troy, bigbiff
Version Information
Status: Stable
Current Stable Version: 2.6.3.0
Stable Release Date: 2013-09-16
Created 2013-09-16
Last Updated 2013-09-16
first
thanks guys
very nice! closed up my unofficial one
Sweet bring on the flash addiction
Sent from my HTC One X using xda premium
I decided to take this for a test drive by flashing cleanrom 2.1. It seems that it does not get installed properly. Is this a fail of the recovery or the rom itself? Someone else want to try?
z28james said:
I decided to take this for a test drive by flashing cleanrom 2.1. It seems that it does not get installed properly. Is this a fail of the recovery or the rom itself? Someone else want to try?
Click to expand...
Click to collapse
Flash it then go to advanced and "copy recovery.log to sdcard" then get me the log. Ideally come to #twrp on freenode and pastebin it for us there - webchat link in OP if you don't know how to use IRC.
z28james said:
I decided to take this for a test drive by flashing cleanrom 2.1. It seems that it does not get installed properly. Is this a fail of the recovery or the rom itself? Someone else want to try?
Click to expand...
Click to collapse
seems to be scripting problem
chainfires superSU flashes fine..
Tried usb mount, but no go..
me too
stuck..
No usb is a known issue listed on our website...
seems adb is not working...
niceppl said:
seems adb is not working...
Click to expand...
Click to collapse
yup, same issues as mine, no usb storage or adb... working on it!
niceppl said:
seems adb is not working...
Click to expand...
Click to collapse
Known problem
Sent from my HTC One X using XDA
designgears said:
yup, same issues as mine, no usb storage or adb... working on it!
Click to expand...
Click to collapse
thanks,
well if adb is working...usb is not that important...
good
very nice！
Very interesting and intriguing, but I have a few questions:
1) does it charge the battery when in the recovery (I think CWM doesn't?)
2) are you planning on fixing the two issues listed, including compatibility with CWM backups?
fixed adb access!
unofficial build: http://www.gigashare.in/3fbf1
designgears said:
fixed adb access!
unofficial build: http://www.gigashare.in/3fbf1
Click to expand...
Click to collapse
So I just flashed this and I still have no adb. Any ideas?
androidoholic said:
So I just flashed this and I still have no adb. Any ideas?
Click to expand...
Click to collapse
try flashing it again, make sure you have adb drivers installed as well.
Zarboz said:
seems to be scripting problem
chainfires superSU flashes fine..
Click to expand...
Click to collapse
I woldnt be quick to call it a scripting problem because its the identical script to my other ICS ROMS that DO work on twrp (Rezound and Evo 3D).
But who knows, I could be wrong. But generally speaking, if it works on one Recovery and not another then I would think the Recovery would be the issue and not the script.
I will flash this and test it myself and see what the deal is. The scripting I use with my ROM is pretty basic.
Format, mount, extract, symlink, unmount. Nothing fancy there.
I'll join IRC channel after I have to time to play to help T/S if OP wants?
EDIT: BTW: I love twrp and its always been my recommended recovery. I have been bugging Con24 who ported twrp to Rezound to do this for us so I am really happy to see twrp here!!!!!!
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.
*/
This is a preview build of Android JellyBean 4.2 from AOSP source code based on the CyaogenMod device tree for Acer A700. I have made this build to gauge how difficult it would be to port JellyBean 4.2 to current devices.
Kernel Source Code: https://github.com/pawitp/android_kernel_acer_t30/tree/jellybean-next
Device Tree: None yet available (Only notable part: patch for TinyHAL: https://gist.github.com/4104332)
Downloads
ROM: http://goo.im/devs/pawitp/a700/a700_aosp_jb42_20121116.zip
Google Apps: Currently integrated due to lack of gapps package for 4.2
SuperSU: http://download.chainfire.eu/282/SuperSU/CWM-SuperSU-v0.98.zip (Currently, only SuperSU is compatible with 4.2)
Installation
Note: due to new /data/media layout in 4.2 for multiple user support, your data in /data/media (/sdcard) will be moved to /data/media/0. This may cause problems in restoring backups in recovery, you may fix it by moving data /data/media/0 back to /data/media via adb in recover prior to restoring data.
Install CWM recovery from http://forum.xda-developers.com/showthread.php?t=1791165
Do a Nandroid Backup!
Install the ROM using ClockworkMod Recovery
Optionally install the Google Addon
Wipe data if coming from stock
Known Issues
Camera does not work
Bluetooth sometimes freezes bringing down Wi-Fi with it
Reporting Bugs
You are allowed to report bugs only in this thread. Note that this is a preview release and non-device specific bugs will not be accepted. The development of this preview will also cease once enough progress has been made in CyanogenMod.
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.
gonna grab this later
Wow! This ROM is awesome. Please make it more stable. And the Performance is not so good as other ROMs.
Webitu
Webitu said:
Wow! This ROM is awesome. Please make it more stable. And the Performance is not so good as other ROMs.
Webitu
Click to expand...
Click to collapse
For stability: Please report crashes as mentioned in the OP, without logs, there'd be no way to know what broke.
For performance: Please report where and how performance differs.
Note that generic "please make this better" report do not help, please be more specific.
Runs so far, unfortunately I can not get a wifi connection. 'm Back to 4.1 back.
Fooox1 said:
Runs so far, unfortunately I can not get a wifi connection. 'm Back to 4.1 back.
Click to expand...
Click to collapse
Next time, please get a logcat.
pawitp said:
For stability: Please report crashes as mentioned in the OP, without logs, there'd be no way to know what broke.
For performance: Please report where and how performance differs.
Note that generic "please make this better" report do not help, please be more specific.
Click to expand...
Click to collapse
Okay sorry. The launcher laggs sometimes and the Antutu benchmark results are not really good.
The GPU test results are 967 points. (3D = 674, 2D = 293)
The fps are 31. In the stock ROM i had 42 fps i think.
And i havn´t any crashes but it seems like its a little bit unstable but it can be also the apps who are not official for 4.2
But very good work! :good:
Sorry for my bad English.
Webitu
The graphic issue can't really be helped, Android 4.2 requires new graphic drivers and the current binaries used are optimized for the Nexus 7. As there are closed-source binaries, there is no way to modify them. The situation may change in the future as compatibility layers are introduced or new drivers are released.
pawitp said:
The graphic issue can't really be helped, Android 4.2 requires new graphic drivers and the current binaries used are optimized for the Nexus 7. As there are closed-source binaries, there is no way to modify them. The situation may change in the future as compatibility layers are introduced or new drivers are released.
Click to expand...
Click to collapse
Okay thank you. I already thought so. Hopely Acer brings a new Update with 4.2
Webitu
Nvidia is the same xxx as samsung (
Is A701 supported?
It will work on A701, but 3G will not work.
BTW, CM10.1 preview. Nearly everything working (including Camera, etc.). Nightlies should start soon and I'll make a new thread then.
http://goo.im/devs/pawitp/a700/cm-10.1-20121216-UNOFFICIAL-a700.zip
pawitp said:
It will work on A701, but 3G will not work.
BTW, CM10.1 preview. Nearly everything working (including Camera, etc.). Nightlies should start soon and I'll make a new thread then.
http://goo.im/devs/pawitp/a700/cm-10.1-20121216-UNOFFICIAL-a700.zip
Click to expand...
Click to collapse
Yeah. Big thanks for your work! I will try it out now. Did you recognized that when you set a wallpaper on CM10 only half of the wallpaper is used on the homescreen? Don`t know how to log this issue.
OCmylife said:
Yeah. Big thanks for your work! I will try it out now. Did you recognized that when you set a wallpaper on CM10 only half of the wallpaper is used on the homescreen? Don`t know how to log this issue.
Click to expand...
Click to collapse
It's due to our screen size and peculiar wallpaper handling, so the default wallpapers don't scale too well.
pawitp said:
It's due to our screen size and peculiar wallpaper handling, so the default wallpapers don't scale too well.
Click to expand...
Click to collapse
Yeah I`ve tried logcat in the terminal, before I read your command. It shows no error-message when I changed the wallpaper. But I think I could live with this one.
I`ve encountered one minor Issue. You could change the default page size in the trebutchet settings, but it doesn`t take effect on your pages on the homescreen. Yeah really minor issue, but otherwise I haven`t found a bug so far. But I will search further.
Again. CM 10.1 looks absolutely awesome on the Acer A700 and I would recommend everybody who has CWM on his A700 to try this one out. :highfive:
Has anyone tried twrp recovery on the A700? I`m frightened every time to flash on my A700, cause I experienced the freeze issue also(one time so far, after I switched from CM10 to Iconian 2.2).
Trying to install CM10.1 but until now only bootscreen for 20 mins :/
Edit: hmm almost 40 minutes -.-
Tried Wiping Data/System/Cache now, but still Bootscreen loading and loading..
Chris0706 said:
Trying to install CM10.1 but until now only bootscreen for 20 mins :/
Edit: hmm almost 40 minutes -.-
Tried Wiping Data/System/Cache now, but still Bootscreen loading and loading..
Click to expand...
Click to collapse
Use adb to get a logcat, it'll tell you what's wrong. Normally, it's caused by not wiping data when coming from a stock ROM, but since you've said that you've wiped data, maybe there's some other cause.
pawitp said:
Use adb to get a logcat, it'll tell you what's wrong. Normally, it's caused by not wiping data when coming from a stock ROM, but since you've said that you've wiped data, maybe there's some other cause.
Click to expand...
Click to collapse
Which command parameters should i use ? Its a load of text.
If i want to save the log in a file with the -f parameter i always get the error, that the output file couldnt be openend and that my filesystem is read-only ..
Chris0706 said:
Which command parameters should i use ? Its a load of text.
If i want to save the log in a file with the -f parameter i always get the error, that the output file couldnt be openend and that my filesystem is read-only ..
Click to expand...
Click to collapse
adb logcat > log.txt
Sent from my GT-I9000 using xda app-developers app
So now i got the logcat attached, hopefully you find the error..
☆Root required☆
☆It supports all Samsung devices!☆
It's aimed to support all Samsung devices running Android 2.3+ for the EFS feature.
This application let you save a backup of your EFS partition on any Samsung device running Android 2.3+, this help you to keep your IMEI safe from getting corrupted after any bad Rom flashing issues, this is a common issue with Samsung devices, if somehow you lost your IMEI, you won't be able to get registered and connected to any mobile network.
User will be prompted to choose which partition to backup within all partitions list when there is no EFS partition on his device.
With this application you can also backup any other partition, just make sure you have enough space for bigger partition on your device sdcard.
What's new compared to other EFS backup Apps?
This application was made to be a generic solution for all Samsung devices, it does NOT use any static block numbers.
This App support 3 backup formats:
Stock image copy (img)
Tar archived image (No compression)
Compressed GZ image (Small size)
Notes:
The backups are saved on /Sdcard/EFSBackups.
Do NOT leave the EFS backup on your Sdcard, make sure it is saved on a safe place
It supports stock and custom Roms (CM, Omni...)
Bugs reports:
Post your Exact device model
PM me your logcat (you can use Syslog App)
Download.
Changelogs:
1.2.2:
- Few compatibility improvements for older devices.
1.2.1:
- Improved multi-partitions backup process
- Improve sdcard mount point detection
- Many other compatibility fixes with custom Roms (CM, Omni...)
- Add and option to remove ads
- Expand support to all Android devices (User will be prompted to choose which partition to backup when there is no EFS partition on his device).
1.2.0:
- Add partitions backup option
- Bug fixes
1.1.0:
- Minor bug fix
- Add some sanitation checks
1.0.2:
- Minor bugs fixes
- Add restoration feature.
- Sanitize the restoration.
- Remove a useless permission
1.0.1:
- Minor bugs fixes
- Add restoration feature.
- Sanitize the restoration.
Suggestions are welcome, if you like the application please rate it.
Useful tool,used and my efs are saved.Thnx
Envoyé de mon SM-N910F en utilisant Tapatalk
Tested in galaxy note 2 and it works well
Thanks
@wanam any chance of gingerbread update?
killoid said:
@wanam any chance of gingerbread update?
Click to expand...
Click to collapse
Yes, it can be done, i restricted the min api level to 3+ only because i need a tester for older devices.
I will PM you later.
@killoid Here is an update with untested Gingerbread support, try it and let me konw if it works.
this supports note 4 (910F) ?
SavanTorian said:
this supports note 4 (910F) ?
Click to expand...
Click to collapse
Yes (see second post), it supports all Samsung devices.
wanam said:
@killoid Here is an update with untested Gingerbread support, try it and let me konw if it works.
Click to expand...
Click to collapse
@wanam it can't detect my efs partition.screenshot attached.
Successfully created a backup for my SGS Captivate running CM10.1.3 (Also transferred to my laptop with my first adb pull.)
I hope I never have a need for it.
Thank you wanam.
You are a start Wanam. Actually FIVE of them :=
Works great on Galaxy Note 3 with 4.4.2:good:
Famous Work, Mr. Wanam! Many THX for your always hard developing work!
dawgdoc said:
Successfully created a backup for my SGS Captivate running CM10.1.3 (Also transferred to my laptop with my first adb pull.)
I hope I never have a need for it.
Thank you wanam.
Click to expand...
Click to collapse
And,
it worked just as well with my SGS3 d2att running TMS3 (4.3) Rom
thanks
wanam said:
☆Root required☆
☆Samsung devices only! ☆
Thank you wanam... App worked beautifully..
Click to expand...
Click to collapse
wanam said:
@killoid Here is an update with untested Gingerbread support, try it and let me konw if it works.
Click to expand...
Click to collapse
killoid said:
@wanam it can't detect my efs partition.screenshot attached.
Click to expand...
Click to collapse
it can work if you make option to choose partition by user
and user can extract the kernel and check fstab its efs partition point and put it and backup
Jasi2169 said:
it can work if you make option to choose partition by user
and user can extract the kernel and check fstab its efs partition point and put it and backup
Click to expand...
Click to collapse
Great idea, it's in my todo list.
Is it work on custom rom? like ParanoidAndroid?
The app successfully located the EFS location. So I try to make a backup, and it says successful. But, I don't see any folder called EFSBackups on sdcard directory. (both sdcard0 and sdcard1 (even sdcard2)
Samsung Galaxy SIII Mini (GT-I8190) running ParanoidAndroid-4.6-Beta5-unofficial.
While I can't make any efs backup, I just translated your apps to Indonesia through the app menu Maybe there should be an option to save the EFS on custom location. Will PM the syslog.
blacky2198 said:
Is it work on custom rom? like ParanoidAndroid?
The app successfully located the EFS location. So I try to make a backup, and it says successful. But, I don't see any folder called EFSBackups on sdcard directory.
Samsung Galaxy SIII Mini (GT-I8190) running ParanoidAndroid-4.6-Beta5-unofficial.
While I can't make any efs backup, I just translated your apps to Indonesia through the app menu Maybe there should be an option to save the EFS on custom location. Will PM the syslog.
Click to expand...
Click to collapse
I am facing the same problem: I can't find the EFSBackups folder anywhere.... I can locate my EFS folder though.
Would really like to be able to choose a specific backup lcoation.
ROM: CM11 unofficial
Device: Note 3 N9005