Database Users

[Q] Amatuer Noob needs help

I just got my NC and decided to give this a try instead of buying a N2A card.
Android Version 2.3.7
Kernel version 2.6.32.9
Mod Version CyanogenMod-7.1.0-encore
build Number GWK74
ClockworkMod 3.2.0.1
When I initially booted off the memory card everything was smooth until gapp. It loaded but when it came to selecting the apps when I clicked on one it flashed and just continued to set up. It didn't let me select any. No big deal because it worked fine.
I had force close issues so I ran Fix Permissions through ROM Manager and this seemed to help except for a few apps.
I used LCDDensity and changed that to 161 with Kill All which cleared up my force close issues on Words With Friends and Tweetcaster.
I get on today and notice videos are now missing from the market main screen and apps that I had yet to install are now no longer compatible with my device. They were last night but I was picking and choosing what I wanted on here. Why the sudden change? I rebooted the device just a few minutes ago and now the sudden change.
I also read about clearing davlik cache but how do you do this? I am not a programmer or developer so I have no clue. I have spent hours reading here everyday since Christmas and my mind is melting. I tried rebooting into recovery but I do not get the option to do anything. The penguin appears and a few things scroll down the screen and it reboots. I tried using the emulator and that won't work either unless I am typing something in wrong.
Are there any other tweaks or things I need to do to keep things stable and running smoothly? Are their certain things I need to clear regularly i.e. davlik cache, application cache or data?
I appreciate all the hard work and the time everyone puts into this. Please help. Like I said I need kindergarten instructions. Thank you.

First off, I've never had much success running from uSD. Even as far back as NookieFroyo. Once I made the move to running from eMMC most of my issues disappeared.
Davlik can be wiped from the Advanced selection when you boot to CWM as can Fix Permissions.

If you are going to run from SD then it is highly advisable to use a Sandisk Class 2 or 4 card. The brand does make a difference and others have found that other makes lead to slow downs and instabilities.
I would also recommend starting again following the veryGreen SD install method
http://forum.xda-developers.com/showthread.php?t=1000957
and using the MiRaGe KANG ROM.
http://forum.xda-developers.com/showthread.php?t=1344873
This is CM7 but with the latest improvements including kernel adding to stability and performance.

Also, never use Windows to format your uSD. The format utility in Windows can (and does) screw up the format. Use this freebie. Has always worked well for me. You would be surprised how many problems that involve uSDs are traced back to a bad format.

I used LCDDensity and changed that to 161
Click to expand...
Click to collapse
Setting to 161, you are asking for more issue.
Suggestion: set it back to 160.

skeeterpro said:
First off, I've never had much success running from uSD. Even as far back as NookieFroyo. Once I made the move to running from eMMC most of my issues disappeared.
Davlik can be wiped from the Advanced selection when you boot to CWM as can Fix Permissions.
Click to expand...
Click to collapse
How do I get to the Advance section and boot to CWM? When I try it through ROM Manager the device restarts with the penguin and after a few lines it says the system is ****ting down. It does not give me any menu options.
votinh said:
Setting to 161, you are asking for more issue.
Suggestion: set it back to 160.
Click to expand...
Click to collapse
I read that this was recommended and when I do it my apps that have issues work and they work well. No more force close issues.
Thanks for the advice guys. Like I said I have no experience with any of this. I am learning though and love to tinker with things and figure out how they work.

bobtidey said:
If you are going to run from SD then it is highly advisable to use a Sandisk Class 2 or 4 card. The brand does make a difference and others have found that other makes lead to slow downs and instabilities.
I would also recommend starting again following the veryGreen SD install method
http://forum.xda-developers.com/showthread.php?t=1000957
and using the MiRaGe KANG ROM.
http://forum.xda-developers.com/showthread.php?t=1344873
This is CM7 but with the latest improvements including kernel adding to stability and performance.
Click to expand...
Click to collapse
I did the veryGrenn SD install. Is there a link on how to install a new ROM. I read the link but I just do not understand it.

jsnake said:
I did the veryGrenn SD install. Is there a link on how to install a new ROM. I read the link but I just do not understand it.
Click to expand...
Click to collapse
To update the ROM on an SD card install power down, remove card then you put the card back onto the PC and copy the new ROM zip onto it but named as update-cm-*.zip. Put the card back in the Nook and power up with N button pressed until you see the screen flash. Choose reboot recovery and the new zip will be installed.
However, if you are doing a major ROM switch and haven't invested too much time installing apps etc yet then I would recommend just doing the VeryGreen install from the beginning to get a clean install.

I did a clean install and so far things are working well. Base off of the veryGreen install are there any "must have" settings or tweaks I need to do to keep things smooth? Any nook or CM7 apps you guys would recommend. I know it has been answered 50,000 times but I am losing sleep reading the forums here.
Thanks again for the help and your patience.

There are so many of apps that suitable for each individual personality, for me:
+ news: usatoday, bbc
+ sport: Y!spectacular, mobile sport
+ movie: flixter, moviefone
+ picture viewing: quickpic (must have)
+ time: clocksync (must have)
+ file navigate: file expert (must have), astro file manager
+ player: rockplayer
+ ebook: Mantano (recommended)
+ weather: fancy widget
+ web browser: Opera (like better), dophin HD
+ calculator: TI-83/86 emulators, also mortgage cal. and real science cal.
+ game: none
+ sex pos.: forget the name
+ few others that occasionally use.

Every one gets their own favorite apps to suit their interests. I personally go for ES file explorer for general file navigation and accessing my computers' shares wirelessly, Dolphin HD browser for the gesture navigation, moboplayer for playing media, and QuickPic for photo viewing.
But don't forget Nook Tweaks. This allows you to tweak the kernel and benefit from some of the good things in there that distinguish the Dalingrin CM7 kernel. Like overclocking to get a really good boost in performance (most people go for 1200MHz max for stability), undervolting to stretch the battery a bit, audio settings to make the stock feeble audio considerably louder (set DAC boost about 50%), and USB hosting if you want to connect USB peripherals.

jsnake said:
How do I get to the Advance section and boot to CWM? When I try it through ROM Manager the device restarts with the penguin and after a few lines it says the system is ****ting down. It does not give me any menu options.
Really? You are sure it's CWM 3.2.0.1? When you boot to recovery you don't get a Menu? If not, methinks your CWM is hosed. Have to say I do not ever recall not getting a CWM Menu. Nor can I call up seeing a "penguin"?
Have to say also ROM Manager is quirky at best. Used it a long time ago and found that it whacked my NC. Uninstalled and never used again. Found it was incompatible with other devices.
You might consider a new uSD install.
Click to expand...
Click to collapse

skeeterpro said:
Really? You are sure it's CWM 3.2.0.1? When you boot to recovery you don't get a Menu? If not, methinks your CWM is hosed. Have to say I do not ever recall not getting a CWM Menu. Nor can I call up seeing a "penguin"?
Have to say also ROM Manager is quirky at best. Used it a long time ago and found that it whacked my NC. Uninstalled and never used again. Found it was incompatible with other devices.
You might consider a new uSD install.
Click to expand...
Click to collapse
I'm not using SD CM7 currently myself but my recollection when I did is that the recovery is not a full clockwork but a stripped down one just designed to install update zips. As such you don't get the full menu and operation from ROM manager isn't going to work properly.

skeeterpro said:
Really? You are sure it's CWM 3.2.0.1? When you boot to recovery you don't get a Menu? If not, methinks your CWM is hosed. Have to say I do not ever recall not getting a CWM Menu. Nor can I call up seeing a "penguin"?
Have to say also ROM Manager is quirky at best. Used it a long time ago and found that it whacked my NC. Uninstalled and never used again. Found it was incompatible with other devices.
You might consider a new uSD install.
Click to expand...
Click to collapse
On this clean install I finally got it to work and there is no penguin. Just the menu that I should see so I finally cleared davlik cache.
I downloaded nook Tweaks as well.

jsnake said:
On this clean install I finally got it to work and there is no penguin. Just the menu that I should see so I finally cleared davlik cache.
I downloaded nook Tweaks as well.
Click to expand...
Click to collapse
Excellent! So all is well?
---------- Post added at 01:09 AM ---------- Previous post was at 01:09 AM ----------
bobtidey said:
I'm not using SD CM7 currently myself but my recollection when I did is that the recovery is not a full clockwork but a stripped down one just designed to install update zips. As such you don't get the full menu and operation from ROM manager isn't going to work properly.
Click to expand...
Click to collapse
Makes sense. Thanks for the clarification.

bobtidey said:
To update the ROM on an SD card install power down, remove card then you put the card back onto the PC and copy the new ROM zip onto it but named as update-cm-*.zip. Put the card back in the Nook and power up with N button pressed until you see the screen flash. Choose reboot recovery and the new zip will be installed.
However, if you are doing a major ROM switch and haven't invested too much time installing apps etc yet then I would recommend just doing the VeryGreen install from the beginning to get a clean install.
Click to expand...
Click to collapse
So I have done a clean install of veryGreen exactly as posted except that I have the latest stable instead of a nightly. So do I simply download that ROM file and do as you stated for MiRaGe Kang? Just asking because on that link there is a bunch of different things listed and I get kind of lost. All I need is the ROM file and follow what you said quoted above?
Thanks again.
I tried renaming the file but it says the name cannot contain * so what am I doing wrong. Searched the forums and can't find the answer.

jsnake said:
So I have done a clean install of veryGreen exactly as posted except that I have the latest stable instead of a nightly. So do I simply download that ROM file and do as you stated for MiRaGe Kang? Just asking because on that link there is a bunch of different things listed and I get kind of lost. All I need is the ROM file and follow what you said quoted above?
Thanks again.
I tried renaming the file but it says the name cannot contain * so what am I doing wrong. Searched the forums and can't find the answer.
Click to expand...
Click to collapse
The * is just shorthand for any name. You can't include * in the actual name as it is a wildcard character that matches any part of a name. The important part is that the new name starts with update-cm- so you can just put that on the front of the MiRaGe zip (which is all you need).

Thank you. I figured it out kind of. I downloaded that ROM and followed the instructions and rooted my nook which I did not want to do. I wanted to dual boot off the memory card. It is all a learning experience.
I did a factory restore and all was good again. Started fresh and was going for a new verygreen install and my memory card slot no longer locks the card in. I am so thankful I had completed the factory reinstall. My wife went to B&N today and exchanged it for me with no issue.
So for now I think I will stick to the verygreen install and tweak it to my liking until something stable for ICS comes about.
Thanks for your patience and help. Some really good people here helping out.

[Q] Nexus 7: A Beginners Quest!

Hi guys!
I bought a Nexus 7 a few days ago, This is my first Android device, my first tablet and my first attempt at rooting anything. so I was hoping for some help from the experienced folks because frankly i don't know what I'm doing I was hoping you could help me with a sort of beginners guide for rooting, like what i should look out for, whats the safest and easiest toolkit, rom, kernel to use. I know i have so much to learn from you guys and I've been reading some of the threads and im starting to get a bit of it already just asking for a step by step of what i should do im mainly going to use my tablet for torrents, games, and some light photo editing and lots of comics! so how do i start? hope to hear from you guys soon THANKS IN ADVANCE!

For rooting the tablet ..its safe ,the important thing is to follow the instructions .so to root it you can use one of the toolkits in the development section,I preferred wugfresh toolkit more ..but its up to you the other one is also good ... Here's a video which explains the root procedure
https://www.youtube.com/watch?v=wI0_ylxyrWA&feature=youtube_gdata_player
btw update your phone before rooting it
And for flashing Roms there are a lots of guides on how to do it..just use Google
If you got stuck in any boot loops just use the toolkit you first used, to restore to stock or restore with a nandroid backup
Most important thing when you root. before touching a file ..do a nandroid backup in recovery to always stay safe ..
That's it enjoy the forums
Sent from my Nexus 7 using xda premium

BigJoey010 said:
For rooting the tablet ..its safe ,the important thing is to follow the instructions .so to root it you can use one of the toolkits in the development section,I preferred wugfresh toolkit more ..but its up to you the other one is also good ... Here's a video which explains the root procedure
https://www.youtube.com/watch?v=wI0_ylxyrWA&feature=youtube_gdata_player
btw update your phone before rooting it
And for flashing Roms there are a lots of guides on how to do it..just use Google
If you got stuck in any boot loops just use the toolkit you first used, to restore to stock or restore with a nandroid backup
Most important thing when you root. before touching a file ..do a nandroid backup in recovery to always stay safe ..
That's it enjoy the forums
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
well said, but here are some more tips: DO NOT PANIC!! when something goes wrong, which is likely, as you are a newbie to rooting, one thing you must not do is panic. calm down and troubleshoot, what did i do wrong? how do i fix it? and according to my experience, whenever a door slams shut behind you, a new window opens. if one method doesn't work, try another method.
also, read through the entire procedure list before start doing the steps. make sure you understand what is required and how to do it before accidentally doing something stupid. believe me, its happened to me b4, not a pleasant experience when you realise you dont actually meet the criteria to install something. btw, here is a list of common names given to the nexus 7: Nexus 7 (duh!), N7, grouper (wifi only) Tilapia (wifi+3g)
good luck rooting!

Read through the stickied threads and try to understand them. It won't happen right away though; your head will probably spin the first couple of times through.
There is really no "overnight" learning curve to this stuff - even if you are an old hand with Linux/Unix.
BTW, it is important to point something out: There should be no reason for you to feel like you should be in a hurry to root. The N7 is a fantastic device, even when used in a pure stock experience.. You are not going to be missing out by not rooting immediately. Spend some time with your device getting used to the Android way of doing things, and start reading XDA with a relaxed frame of mind. There is plenty of time. It would be different if you have lots of prior Android experience - but you said it - this is your first Android device.
OK, rooting. To try and keep you safe while you are a noob, I'll give this recommendation:
If you see the word "flash" (verb) near the word "bootloader", RUN AWAY!.
The most dangerous thing you can do to an N7 is mess around with the bootloader. You can turn your device into a useless object by getting things wrong, and it is a little bit rare that you need to flash a bootloader anyway. You have been warned.
So, make sure you know the difference between bootloader and "boot partition".
Most Android devices have a single flash memory chip in them which is divided up into a number of partitions. There are 5 principal partitions and about the same number of less frequently used partitions:
THE 5 PRINCIPAL ANDROID PARTITIONS:
(B) boot - a raw blob of binary data containing a "kernel" and a "ramdisk"
(B) recovery - another raw blob of binary data containing a "kernel" and a "ramdisk"
(F) system - The "ROM" part of Android - all the factory (or customized) software, used read-only
(F) data - User data and customizations. A "factory reset" simply erases all the files here
(F) cache - a scratch area used for downloading files and other maintenance operations
B = binary, bootable
F = Filesystem
Now, the two bootable partitions - boot and recovery - are very similar in structure, but extremely different in purpose. (In fact, in stock devices, they both use a private copy of the same kernel) The "boot" partition can produce a UI (User Interface) after it starts up only in conjunction with healthy /system and /data filesystems containing the Android software. But the "recovery" partition can produce a minimal UI even if the /data and /system filesystems are completely empty of files; so it (the recovery boot) is used to do all maintenance operations - including things like installing new /system software or erasing all user data.
So, and Android "rooter" will usually replace the very minimal (and locked-down-security) stock recovery partition with a "custom recovery" that is more friendly, and the vast amount of the "flashing" operations will take place using this custom recovery.
When people talk about "ROMs", they generally mean only TWO of those five partitions mentioned above: the "boot" partition and the "system" partition. When a "ROM" is flashed using the system partition, the usual procedure is:
- The rooter makes a full Nandroid backup.
- The rooter performs a "factory reset" procedure which erases the /data*** and /cache filesystems
- The rooter then "flashes a ROM", which puts in place a new boot partition, erases the /system partition, and then re-populates the /system partition with changed Android system software.
Upon booting an Android phone/tablet after this procedure, the device will behave as if it just came from the factory - but now with a different custom version of Android software. Note that this means that all the things you customized in the previous ROM - wallpapers, settings, home screen app icons, widgets, market apps downloaded, etc - will all be gone. So, folks that make a habit of hopping from ROM to ROM generally have some tricks up their sleeves for making the re-customization of a freshly-installed ROM a little less tedious. (Things like using custom launchers that allow you to save homescreen customizations, apps to restore previously-used market apps & their data, etc, etc, etc)
*** there is some funny business with Android devices that have no removable SDcard storage devices such as the Nexus 7 - the user's "SD card" is emulated, and the files that are stored there are actually stored in the /data filesystem. So, custom recoveries usually have a "factory reset" procedure which deletes all files in /data while scrupulously avoiding erasing things in this /sdcard area ( == /data/media ). This allows you to keep things safe from wiping (pictures, music, ROM files, backups) while still installing a fresh and un-initialized ROM. Note that the stock recovery in the N7 does not do this - when you use the "factory reset" of the stock recovery, EVERYTHING in /data gets erased - everything!
While you are reading about Android, here are some questions/searches to look up that concern rooting activities... have fun!
- What is the difference between grouper/tilapia (or nakasi/nakasig )?
- What does it mean to "install a new launcher" or "install a new home app"?
- What is Android fastboot used for?
- What is the Android ADB (Android Device Bridge) program used for?
- What is the difference between a boot image and a bootloader?
- How do I go about making a Nandroid Backup?
- What are the Carbon and Titanium Backup apps for? What can they do?
- What file browsers on the market are "root aware"?
- What Android settings can be saved by the Google Play Store, and automatically restored into a new ROM?
- Is there a difference between the "Superuser" and "SuperSU" root kits?
- What are the special Hardware Button Combinations used by the Nexus 7?
- What is the Google Android SDK?
- What custom recoveries are available for the Nexus 7?
- How many unique operating modes does the Nexus 7 bootloader display? What are they called?
- What is a MD5 signature? How can it help me stay out of trouble?
- What does soft-booting a bootable image with fastboot do?
- How many (Windows PC) drivers are needed to use ADB (with both the custom recovery and also the regular OS) and fastboot (with the bootloader), 2 or 3?
- Suppose I soft-brick my N7 - how will I transfer files to and from the N7 in this situation?
- What is the difference between adb push/pull and adb sideload?
- What does "sideloading an app" mean?
- Is an Android ".apk" file the same thing as a .zip file, or different?
- In what folder in /data are market apps (.apk files) found? Same question for /system and system apps (.apk files)?
- How do I enable the developer options on my N7 tablet?
- What are the limitations of MTP or PTP file transfer modes?
- Where does the custom recovery tool store backups?
- Are the Android tools "adb" and "fastboot" available for Mac or Linux?
- What are the limitations of the Google Factory Images for the Nexus 7? How are they installed?
- I have a problem using the recovery. Where is the log file stored?
- What is the big stumbling block involved in unlocking the N7 bootloader?
- What operations can you perform using fastboot and the bootloader which you can not do any other way?
OK, that's enough for now.

Thanks Everyone!
bftb0 said:
Read through the stickied threads and try to understand them. It won't happen right away though; your head will probably spin the first couple of times through.
There is really no "overnight" learning curve to this stuff - even if you are an old hand with Linux/Unix.
BTW, it is important to point something out: There should be no reason for you to feel like you should be in a hurry to root. The N7 is a fantastic device, even when used in a pure stock experience.. You are not going to be missing out by not rooting immediately. Spend some time with your device getting used to the Android way of doing things, and start reading XDA with a relaxed frame of mind. There is plenty of time. It would be different if you have lots of prior Android experience - but you said it - this is your first Android device..
Click to expand...
Click to collapse
I do appreciate everyones input! yeah i think ill make do with the stock for a couple weeks while i study up on rooting and firmwares. well the main reason i wanted to root was for the games, as much as i want to buy the games i like, i dont have the means to

This is great. Wish I had been fortunate enough to have such great help when I first started.
And the most important rule is the one about reading before you root or flash. This will save you some heartache down the road.
Sent from my Nexus 7 using XDA Premium HD app

How's rooting related to games ? You mean overclocking ?
Sent from my Nexus 7 using xda premium

BigJoey010 said:
How's rooting related to games ? You mean overclocking ?
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
sad to say i will have to torrent my games as much as i wanna pay and support the game devs i already blew all my money on steam and buying the N7. ive read somewhere that if u are using the the stock version and you try to run a torrented game it automatically shuts down

No it doesn't ...i be downloaded tons of games(torrents) and I'm on stock and they are working normally
Sent from my Nexus 7 using xda premium

UrbabBear said:
sad to say i will have to torrent my games as much as i wanna pay and support the game devs i already blew all my money on steam and buying the N7. ive read somewhere that if u are using the the stock version and you try to run a torrented game it automatically shuts down
Click to expand...
Click to collapse
All the help you were given....then you bring this up.
I doubt further help will come your way as pirating software is very much frowned upon at xda.
Sent from my cell phone telephone....

kj2112 said:
All the help you were given....then you bring this up.
I doubt further help will come your way as pirating software is very much frowned upon at xda.
Sent from my cell phone telephone....
Click to expand...
Click to collapse
i never really liked pirating software...believe me im a huge fan of steam and i practically buy alll my games legit for the pc.. since steam wallet codes are available at a local store here.. okay i promise i wont pirate and ill try to look for the means to buy from the google store , the thing is i dont have a credit card... and i dont know if google has have something equivalent to steam wallet cards for the google play store.. i could borrow a cc and pay for it.. but is the google play store a safe place to purchase ? i nkow some people disputing alot of charges from google play to everyone, i meant no disprespect.. i was thinking along the lines of test the game if there is no lite version, then when i can i will buy the game :< im still new to the whole tablet arena and im gonna need all the help that i can get

UrbabBear said:
i never really liked pirating software...believe me im a huge fan of steam and i practically buy alll my games legit for the pc.. since steam wallet codes are available at a local store here.. okay i promise i wont pirate and ill try to look for the means to buy from the google store , the thing is i dont have a credit card... and i dont know if google has have something equivalent to steam wallet cards for the google play store.. i could borrow a cc and pay for it.. but is the google play store a safe place to purchase ? i nkow some people disputing alot of charges from google play to everyone, i meant no disprespect.. i was thinking along the lines of test the game if there is no lite version, then when i can i will buy the game :< im still new to the whole tablet arena and im gonna need all the help that i can get
Click to expand...
Click to collapse
a good way to get started is to get yourself a prepaid credit card from 7eleven and use that for purchases from the play store.

Billchen0014 said:
a good way to get started is to get yourself a prepaid credit card from 7eleven and use that for purchases from the play store.
Click to expand...
Click to collapse
as much as that service would be convenient its not available in my country thanks! i hope somebody brings it here ... i found a workaround already now just a matter of saving up for the good apps! so in the mean time lite versions here i come!

UrbabBear said:
as much as that service would be convenient its not available in my country thanks! i hope somebody brings it here ... i found a workaround already now just a matter of saving up for the good apps! so in the mean time lite versions here i come!
Click to expand...
Click to collapse
http://play.google.com/about/giftcards/ use this to see if any retailers near you sell.
Sent from my Nexus 7 using xda premium

Hey guys, what do you think are the most basic and necessary apps that i should get ? running on stock
, ive checked some and go a file manager

If you think you are going to root down the road...
If you think there is a good chance that you are going to root down the road, I would suggest unlocking the bootloader in the near future. You'll need to do this and it wipes everything on the tablet. Even if you don't root, there's isn't any major downside to having the bootloader unlocked and you can always relock it later.
It's better to do that before you've put a lot of time into customizing your tablet to perfection and then have to redo it all.

[Q] Samsung Galaxy Tab 4 8.0 AT&T SM-T337A Root but NO Recovery

Hi Devs,
I've just joined and am uncertain of the proper place for this thread. Apologies if inaccurately posted.
I have the T337A, which I have rooted on ANF4, but I cannot find a recovery. I have read and read but am not finding the solution to my little project. I would like to get a safestrap on this locked bootloader so that I can install and learn to write custom ROMs. I have tried a safestrap but it was not for this specific device and did not work. I have also installed and purchased CWM Recovery and TWRP Recovery, in my learning process. The problem with the recovery is that there is no custom recovery written for this device and the bootloader is locked, as this is the AT&T WiFi/LTE version. So it looks to me like I need to figure out the partitioning image somehow in order to make a safestrap work on this device...as step 1. Is there anything else that I can do with this locked bootloader? I would love to have some help in writing a custom recovery and ROM for this device but I am a tiny tiny noob here and not a hard core programmer. If I could get some feedback on places to start for such a daunting task, it would be great. I guess one thing that I do not understand is why I cannot make my current rooted ROM the default recovery in TWRP. It asks me to choose from the list of supported devices. I understand that it goes: NAND --> aboot.img/bootloader --> recovery/or/kernel --> OS/or/ROM? If this is close to accurate then I would have to write something to the NAND?, which I'm not sure what is yet, in order to hijack the factory bootloader and then write the partitions on the sdCard for the ROM, like the safestrap folks wrote? It looks to me like they also included a version of TWRP touch which I used on the S4 yesterday and was really cool, so I guess that would be needed as well and is also why TWRP does not work for me now...it cannot hijack the locked bootloader. How do I hijack this hard headed thing? fastboot does not work to this device. In the process of this project, I have also run into a roadblock trying to update the /system/framework/framework-res.apk, in the manner that a flash needs to be done, I think. I want to change the /res/values/bools/bools.xml switch "voice_capeable" to true. AT&T or Samsung disable this on this version of the tablet, I guess to sell tethering or something else I'm not familiar with...but the way it looks to me, everything is configured on the device and I have a phone number provisioned for data at least. Why can't I turn on this switch and use the phone portion of the device? Any time I tickle the running framework-res.apk, it kills the OS. I tried compiling an update.zip aligned and signed with test keys or something like that but when I flash it, it fails with wrong footer and invalid signature...then it wipes me back to the stone ages. I warned I was a noob..! ...but not scared to brick some shtuff in order to learn this and write some custom solutions. An after thought...is there a solution for a bootable extSdCard for Android? This might lead to some options if it is possible.
Gathering phone info...
Collecting information. Be patient! Do NOT disconnect the phone!
Model: SM-T337A
Android Version: 4.4.2
Sales Code: ATT
PDA Version: T337AUCU1ANF4
Phone Version: T337AUCU1ANF4
CSC Version: T337AATT1ANF4
Product Code: SM-T337AZWAATT
HIDSw Version: T337AUCU1ANF4/T337AATT1ANF4/T337AUCU1ANF4/T337AUCU1ANF4
Board Platform: MSM8226
Serial Number: R32FA00PMRF
Imei: 3534.............
Unique Number: C1604.......
Connections: AT,MTP,MTP
Battery Status: 4.28V (94%)
Network Type: GSM
SuperSU Pro v2.40
TWRP donate latest
CWM donate v5.5.3.7
BusyBox Stericson donate v1.23.0
Titanium Backup Pro latest
xPosed v2.7.1
Wanam xPosed v3.3.1
NinjaMorph Pro v2.8.2
ROM Toolbox Pro v6.0.6.5
RootLogger Pro v1.9
Nandroid Backup v4.4.5
Next Launcher 3D Shell v3.20
Root Firewall Pro v2.1
SetCPU v3.1.2
w/respect. PitPin

Sir,
Please wait until mods will move this thread to the device specific forum for more relevant answers.
Stand by
Good luck

We had a dev working to get safestrap, but he struck out. So if you can get it, I'll test. I too have the 337a. Sucks to have a locked bootloader and no dev interest.

pre4speed said:
We had a dev working to get safestrap, but he struck out. So if you can get it, I'll test. I too have the 337a. Sucks to have a locked bootloader and no dev interest.
Click to expand...
Click to collapse
Thanks pre4speed. I am taking a look at the two tasks again tonight and decided to take the res/bool = voice_capable issue on first since this will determine how brickable this device can be for me. If I can use it as a regular modem phone then I might be a bit more careful with the bootloader project I did some more tinkering with the framework-res.apk ...specifically the /res/values/bools/bools.xml resource and tried the following:
-------
Factory wipe
Flashed sammobile.com T337AATT1ANF4 firmware
Rooted
SuperSU
Busybox
Froze AT&T update service and others involved
Titanium backup and pulled a good backup
Online Nandroid and pulled a good backup
Installed my XDA app. of course..!
-------
Framework-res.apk:
Used total commander to copy the running apk off to the sdCard and then my PC.
Decompilled in APKStudio2.0.3b-Windows (I am also using Ubuntu 14.04 if there is a better way here..also Android Studio on both OS...just learning).
Edited my value.
Recompiled with zip align/sign option.
***Now here in lies the problem, if I haven't already created one above ***
The random article I dug up said that in order to get past the wrong footer and signature issue, and stone-age wipe, when attempting this via abd sideload with an update.zip, is to now copy the edited file back into the original APK using 7zip in order to retain the original signing keys. When I open the original APK archive, it does not show the resource folders deemed "important and I should not jack with them" in the compiled APK (mainly values/* folder). The article mentioned the resource folders such as res/values/bools are compiled and hidden and that I needed to copy over the new resources.arsc file. I see this in the newly compiled APK I made but it also put the Manifest.xml and /res folder in there. Do I need to copy all of that or just the compiled resources.arsc file? I did all and it boot looped me so I'm guessing that I either did something wrong or this was not the right answer. The last part was to chmod the new APK, use total commander to mount the folder as rw, copy over the file, and reboot. All of that worked and I had to reboot many many times...loop.
That is where I am on the modem part and am going to attempt copying just the resources.arsc in a few. I will post more on the bootloader side soon, as I've been researching what goes on from the time I push the power button until the time I swipe the first screen. Lots of reading
w/respect - PitPin

Copying only the resources.arsc file from within the newly compiled apk back to the original framework-res.apk made some progress. Now I have the phone dialer app icon in my apps drawer... but it is failing complaining about contacts. On to the next round of research..!

PitPin said:
Copying only the resources.arsc file from within the newly compiled apk back to the original framework-res.apk made some progress. Now I have the phone dialer app icon in my apps drawer... but it is failing complaining about contacts. On to the next round of research..!
Click to expand...
Click to collapse
Stalled out temporarily on the tab project as laptop hard drive bought the farm. Back in action and made some progress on the tab voice_capable issue. Everything appears to be there and in working order but the SMS modules. I think this has something to do with why the contacts app is blowing up but not sure yet. GoSMS and EXDialer seem to work together without blowing up but the dialer taps the modem and then dies. Taking a break from this to start a thread on rooting the AT&T Alpha. I'm about half way through the exploit on that project. Any input on what might be my SMS problem on the tab 4 would be appreciated. Attached are a few screens.

Does anyone know how to removed the caution sign on the left corner it keep telling me unauthorized action have been detected.

I am in the same boat, I so wish this would come through because I do love this little tab.

same boat
/baker said:
I am in the same boat, I so wish this would come through because I do love this little tab.
Click to expand...
Click to collapse
so did you finally get it going or what?I have been wanting to get my Tab going as well. I've Rooted it and paid for an unlock even, which worked fantastic by the way...Thanx XDA!!! The rooting guide I got from here was right on point,no problem at all!!But anyways, I have it on metro pcs now on the unlimited $60 plan which is awesome (.REAL unlimited internet with NO THROTTLING ) for me because now at home I run pda.net, which gives me very good, fulltime, internet for my home computers as well as the ability to stream everything onto a large screen or even via windows when we want to watch with all the bells and whistles! No lag at all usually,and I don't use my hotspot because of the usb internet connect on pda.net. When I do use the wireless connect, it doesn't take any of the allotted hotspot usage up either!!All in all it's a great deal for me. I just got a new sim for it, called in the imei to metro ,which in turn gave me a phone number and data account, and presto!Been on the net ever since! Now that I've had it for over a month ,I wanna get the voice capability to work as well, being that I am paying for 2 lines now. Although I can use the old trusty hangouts dialer with the GoogleVoice easily enough. I want to be able to use my metro number mainly because these phone companies charge and charge and charge, never caring about us,or our need to have communication at our disposal at all times.Cell phones are by far not inexpensive and the internet wasn't started for us to pay aan arm and a leg to use.Anytime I come out good while dealing with a wireless company. it's a stupendous event,I'm telling you!! Heck ,I'm writing from my home computer now, going through the Tab at this very moment! Nevertheless, I'm wanting for the devs, to come through as well. With maybe even a new rom,sans the at&t stuff, of course, since I do now have a different carrier? Heck, the Tab is even great for when we travel! 24/7 unlimited internet /streaming , and the screen size is much better than the phone screen ever was!I just really wanted to thank XDA for the work they put in to help us part - timers out,Ive been rooting and unlocking and bricking and un-bricking for quite some time now,I even repair phones now actually,but the programming and the putting it all out here for guys like me to have fun and tinker with these phones would be entirely impossible without the DEV'S and their hard work for SURE...Thanx Guys!!You ROCK!

WileyFox Swift 2 Plus observations

The WileyFox Swift 2 Plus is not a bad looking phone, the case feels good in my hand. It is almost small and light enough to fit into my shirt pocket should I need to.
It runs CyanogenOS which is an improvement on the standard bloated Google Android and is to be applauded.
3Gb for the System and 32Gb Storage, 2.4GHz WiFi, Dual Sim, External SDCard, NFC, Android Pay, Android Beam , FingerPrint recognition, 4G, 16Mp/8Mp cameras, 5" screen - great stuff especially for the price. It is however, designed as a city phone not an everywhere phone that much is apparent.
There are a number of downsides :crying:
The second SIM slot doubles up as the Ext SDRam slot - one or the other not both - what an epic fail !!!
Can't actually use the SDcard for backups or data or media - bit of a waste of space really. You need to root the phone and install SD Fix or similar.
It only works with 2.4GHz WiFi which is a disgrace given my ancient Xperia T covers 5GHz as well.
There is no real GPS only A-GPS which needs an internet connection to work - no good if you have a poor or zero mobile signal. This is really such a waste of time even implementing this instead of the real thing.
Only the Google versions of photo album and media player (which don't find local files), mail(gmail) , calendar, calculator etc are installed. If you like having to use a data connection and Google knowing everything you do then fine. I don't which means I have to install apps covering those functions. Shame I can't just install those I used on my Sony Xperia. If you already have favourites its not a big deal. If you don't then you have to start loading and trying out Apps to find the one you like.
Having set up the phone to your liking it would be nice to be able to save it that way. Which you can't without Rooting the phone.
To make the best of it you need to Root the phone - this is to be able to install effective anti-virus, firewall and anti-theft software. To be able to install Titanium Backup in order to actually backup the current state of the phone including apps and data to the SDcard as well as the cloud.
And remove the Apps that you don't use or don't care to have installed.
Would you use a PC without that type of software ? I suspect not - So why make a phone that you can't install the protective software on to ?
It is very simple to unlock the Bootloader and then Root the phone using SuperSU just using the phones developer options. No need to install ADB on the PC or install TWRP on the phone if you don't want to use a custom ROM. Unfortunately it invalidates the manufacturers warranties. :crying::crying::crying:
This could have so easily been a perfect phone, unfortunately a couple of poor cost cutting decisions have more or less ruined it.
Me ? I have already given away this phone after just 3 days, much to my disappointment.

Isn't A-GPS built on top of GPS and purely there for lock startup speed?

You're right, this "review" is full of nonsenses
1. The SD card slot is shared with second SIM slot, it is right. But SD card can be use to backup data or to extend the internal storage space (marsmallow feature)! You don't really need root and SD fix...
2. A-GPS is used to improve startup speed, which is really impressive (snapdragon!)
3. Photo album and media player, mail, ...? You could install whatever you want, there is a google play store
4. Root. No phones come with builtin root, but if you really need it, it is possible and easy to install.
I believe that there will be a community CaynogenMod ROM in the future - just like for the original Wileyfox Swift 1...
I'm very satisfied with this phone. Yeah there are some drawbacks - it has only 720p display (instead of full HD), it can be a bit smaller (just like the previous Swift) and the CyanogenOS has some bugs (for example the theme provider is time to time crashing...), but I hope it will be fixed in the future...

Even better
You can delete easily what you want with titanium backup. And whitout lag (not like a Miui rom).
The bootloader is probably one of the most easier than I've done in my life (not like a xiaomi one).
The SD cart can be use to save your backup, even my 128gb is working.
The screen it's just the perfect size & definition is the perfect combo for not to drain the battery.
Waiting the LineagOS for the marmite :fingers-crossed:

Just managed to pick up one of these practically brand new for only £100 for a friend.
Really nice build quality and look of the phone and packaging. CM13.1 looks nice and any bloat can be quickly disabled or even uninstalled. 3GB Ram is great as sitting here now, this phone has 2GB just sat there free. (Unlike the Nexus 9 for example!) If I was nit picking, the screen could be better and the fingerprint reader isn't as fast as my One Plus 3, (Not to be expected given the price.)
If I had this in front of me, a P9 Lite, and the standard Moto G4 for the same cash, I'd pick the P9 Lite due to its better screen. I'd pick this second due to the extra RAM and fingerprint reader, and the Moto last. If I had to pick a phone to last 2 years, I'd pick this over the P9 as CM13 is better than the strange Huawei stuff.
If Wileyfox could drop the price to £160, I think they'd be onto a real winner.

bahjesaispas said:
You can delete easily what you want with titanium backup. And whitout lag (not like a Miui rom).
The bootloader is probably one of the most easier than I've done in my life (not like a xiaomi one).
The SD cart can be use to save your backup, even my 128gb is working.
The screen it's just the perfect size & definition is the perfect combo for not to drain the battery.
Waiting the LineagOS for the marmite :fingers-crossed:
Click to expand...
Click to collapse
Just bought today can you give run down how to unlock bootloader:good:

stevegtrlmk said:
Just bought today can you give run down how to unlock bootloader:good:
Click to expand...
Click to collapse
On the Nougat ROM:
Enabled developer options (tap build number several times)
Go to developer options
Enable the "OEM unlocking" option
Not so sure about the rest:
reboot into fastboot (adb reboot bootloader)
fastboot oem unlock
It seems like unlocking will wipe your phone... (At the fastboot step... I only recently got mine, haven't tried this yet)

Demostrike said:
Isn't A-GPS built on top of GPS and purely there for lock startup speed?
Click to expand...
Click to collapse
Nope A-GPS is a cheap replacement for real GPS.
http://www.diffen.com/difference/A-GPS_vs_GPS
If you are running a WileyFox Swift with Cyanogen you will find that any of the GPS test apps will say there is no GPS.
A-GPS does NOT work without an internet connection.
Some phone use A-GPS to speed up their lock within built up areas.
Having said that the Swift running the Android v7.1.1 Nougat package the GPS has been enabled and the GPS Test tools now work.
Go figure why it wasn't enabled in the first place.

rivierakid said:
You're right, this "review" is full of nonsenses
1. The SD card slot is shared with second SIM slot, it is right. But SD card can be use to backup data or to extend the internal storage space (marsmallow feature)! You don't really need root and SD fix...
Depends what you want to use the SD card for, maybe something like saving your Titatium backups which can be removed from the phone if it is dead. And if you want dual SIM you can't use the SD card. And you need to root the phone to use the Marchmallow SD card unlock.
If you let the phone use the SD card as extended memory it is encrypted and you can't read it without that phone - thanks Google.
2. A-GPS is used to improve startup speed, which is really impressive (snapdragon!)
Nope SOME phones use A-GPS to speed up lock within built up areas but it is really a cheap replacement for real GPS.
http://www.diffen.com/difference/A-GPS_vs_GPS
check your facts.
3. Photo album and media player, mail, ...? You could install whatever you want, there is a google play store
And if you don't like the pre-installed versions you need something like Titanium to remove them.
4. Root. No phones come with builtin root, but if you really need it, it is possible and easy to install.
And the UPDATES stop the moment you unlock the BootLoader let alone Root the phone.
Anti-Theft, Anti-Virus, Anti-Malware, Titanium Backup, Nandroid Backup all need ROOT.
The Cyanogen Anti-Theft stopped working when the website closed.
The point I was making is why should you have to 'break' your phone to protect your investment?"
I believe that there will be a community CaynogenMod ROM in the future - just like for the original Wileyfox Swift 1...
LOL - no Cyanogen is no more , although there is a movement to Lineage which may grow into a Cyanogen replacement
I'm very satisfied with this phone. Yeah there are some drawbacks - it has only 720p display (instead of full HD), it can be a bit smaller (just like the previous Swift) and the CyanogenOS has some bugs (for example the theme provider is time to time crashing...), but I hope it will be fixed in the future...
Click to expand...
Click to collapse
Yes I also like the phone and its even better running v7.1.1 Nougat - even though the Zen app is not needed.

SMessy said:
Yes I also like the phone and its even better running v7.1.1 Nougat - even though the Zen app is not needed.
Click to expand...
Click to collapse
Get your facts right, just about all phones use aGPS. And all phones lose updates when rooted. You make generic points and a tribute them to a particular device. Sad.
Sent from my Lenovo P2a42 using Tapatalk

MoHaG said:
On the Nougat ROM:
Enabled developer options (tap build number several times)
Go to developer options
Enable the "OEM unlocking" option
Not so sure about the rest:
reboot into fastboot (adb reboot bootloader)
fastboot oem unlock
It seems like unlocking will wipe your phone... (At the fastboot step... I only recently got mine, haven't tried this yet)
Click to expand...
Click to collapse
Reboot into fast boot is that within the phone or when your connected to computer :good:

stevegtrlmk said:
Reboot into fast boot is that within the phone or when your connected to computer :good:
Click to expand...
Click to collapse
If you use the adb command, on the computer...
(I can reboot into bootloader from the advanced reboot menu on the phone as well)

MoHaG said:
If you use the adb command, on the computer...
(I can reboot into bootloader from the advanced reboot menu on the phone as well)
Click to expand...
Click to collapse
Hey thanks unlocked boot but can't get twrp to flash. Download the newest marmite version put in adb folder tried to flash but nothing

stevegtrlmk said:
Hey thanks unlocked boot but can't get twrp to flash. Download the newest marmite version put in adb folder tried to flash but nothing
Click to expand...
Click to collapse
Hi,
I choose to unlock my swift 2 bootloader and flash TWRP using fastboot commands. If you have unlocked bootloader then using minimal ADB and fastboot command use: fastboot flash recovery recovery.img replacing recovery.img with the one you downloaded. So mine was fastboot flash recovery twrp-3.1.1-0-marmite.img as I am on the current official build.

image45 said:
Hi,
I choose to unlock my swift 2 bootloader and flash TWRP using fastboot commands. If you have unlocked bootloader then using minimal ADB and fastboot command use: fastboot flash recovery recovery.img replacing recovery.img with the one you downloaded. So mine was fastboot flash recovery twrp-3.1.1-0-marmite.img as I am on the current official build.
Click to expand...
Click to collapse
Thanks for that I have not tried yet but will do soon much appreciated:good:

image45 said:
Hi,
I choose to unlock my swift 2 bootloader and flash TWRP using fastboot commands. If you have unlocked bootloader then using minimal ADB and fastboot command use: fastboot flash recovery recovery.img replacing recovery.img with the one you downloaded. So mine was fastboot flash recovery twrp-3.1.1-0-marmite.img as I am on the current official build.
Click to expand...
Click to collapse
Do you have to have the file on root of device or in the adb folder as I am just getting error cannot flash twrp

stevegtrlmk said:
Do you have to have the file on root of device or in the adb folder as I am just getting error cannot flash twrp
Click to expand...
Click to collapse
Minimal ADB and Fastboot is a PC based program. I have provided link below for you.
https://freeandroidroot.com/download-minimal-adb-and-fastboot-all-versions/
Once installed you place the file to be flashed in the program folder with the other installed core program files in directory.
If you run the program you get the command prompt window as displayed in post. This is where you run the Fastboot common I advised you about in earlier post.
So in the command window type and execute:
fastboot flash recovery twrp-3.1.1-0-marmite.img
You might wish to read this thread too on XDA
https://forum.xda-developers.com/showthread.php?t=2317790
Hope this helps Robert.

TWRP 3.2.1 for H901

The following is the latest version of TWRP compiled for the T-mobile V10 Model H901.
https://androidfilehost.com/?fid=818070582850501883
MD5SUM: b89d341cd61da31a5348d8f6b3c75c97
The heavy lifting was done by the twrpbuilder project who were generous enough to compile TWRP for our device. They also provide their services to see TWRP is available for devices that don't yet have it. I've personally used this version to do a backup and restore but can't guarantee there won't be issues. If there are while you are still in twrp you should go to the advanced section and copy the log to your external sd card. This log will help them diagnose any issues.
The project is located at: https://twrpbuilder.github.io
Their XDA thread is located here: https://forum.xda-developers.com/android/apps-games/twrpbuilder-t3744253
If you already have TWRP installed installation is as follows: Click Install, choose Image file, navigate to where the TWRP img file is located on your external sdcard and flash that img to the recovery partition. Back out to the root dir and you can select reboot then recovery...it should bounce you right back into recovery and you should see the new version loaded. If you have root in the rom and run into issues the app "flashify" can reflash TWRP 3.0 so make sure you also have it's img available.
This is pretty much only for folks who already have twrp to update to the latest. If you are on nougat you are still stuck until an exploit is released that works for nougat the way dirtycow did for marshmallow and below. *update* an exploit to give root to nougat users is now available thanks to @runningnak3d here: https://forum.xda-developers.com/tmobile-lg-v10/general/root-h901-nougat-t3773942

Reserved Post #1

Reserved Post #2

famewolf said:
The following is the latest version of TWRP compiled for the T-mobile V10 Model H901.
https://www.androidfilehost.com/?fid=8180705828505018
MD5SUM: b89d341cd61da31a5348d8f6b3c75c97
Click to expand...
Click to collapse
Looks to me like that URL should read
https://androidfilehost.com/?fid=818070582850501883
[ EDIT ] Yup, confirmed.. The URL I listed works fine.
Thanks for the file!
:laugh::silly:

NYLimited said:
Looks to me like that URL should read
https://androidfilehost.com/?fid=818070582850501883
[ EDIT ] Yup, confirmed.. The URL I listed works fine.
Thanks for the file!
:laugh::silly:
Click to expand...
Click to collapse
You are correct. For some reason a few characters got truncated. I've corrected the url in post #1.

famewolf said:
The following is the latest version of TWRP compiled for the T-mobile V10 Model H901.
https://androidfilehost.com/?fid=818070582850501883
MD5SUM: b89d341cd61da31a5348d8f6b3c75c97
The heavy lifting was done by the twrpbuilder project who were generous enough to compile TWRP for our device. They also provide their services to see TWRP is available for devices that don't yet have it.
Click to expand...
Click to collapse
Just as an aside, this version seems to correct (mostly) the date issue of previous TWRP versions for the V10. Versions before this one used to generate a default date (folder name) for the backup dating back to the 1970s as I recall.
This one has the correct month and day and time and the year is only 1 off - it showed 2017 on my very quick attempt to play with it.
One additional note to those installing it via TWRP itself - after selecting image flash , MAKE SURE you specify RECOVERY partition, not BOOT! Specifying BOOT will most likely have some less than desirable results.. :laugh:

NYLimited said:
Just as an aside, this version seems to correct (mostly) the date issue of previous TWRP versions for the V10. Versions before this one used to generate a default date (folder name) for the backup dating back to the 1970s as I recall.
This one has the correct month and day and time and the year is only 1 off - it showed 2017 on my very quick attempt to play with it.
One additional note to those installing it via TWRP itself - after selecting image flash , MAKE SURE you specify RECOVERY partition, not BOOT! Specifying BOOT will most likely have some less than desirable results.. :laugh:
Click to expand...
Click to collapse
I've passed on the date issue. Uncertain if he'll generate another build though.

famewolf said:
I've passed on the date issue. Uncertain if he'll generate another build though.
Click to expand...
Click to collapse
Seems that either nobody is using this version or nobody knows about it or they just have nothing to say..
Anyway, as you know, I have spent a fair amount of time recently working with this and installing it. A couple of observations that may be worth noting..
I double checked and I did set a screen timeout on TWRP. Previous versions would first, dim the screen, followed by turning it off completely. If you had the device near you on a desk while backing up the screen lighting up again when TWRP completed was a sure signal that it was finished.
This version of TWRP dims the screen but the screen is never turned off completely. A minor annoyance I suppose but something is different from previous versions.
During the /data partition backup I noted a (to me) new display in yellow: "Backups of data do not include any files in internal storage such as pictures or downloads"
Seriously? Is this something new? Certainly the display is but I always kinda relied on all that being backed up with /data and having the ability to restore them. This is a more serious issue for me which may make me consider going backward..
Thoughts?

NYLimited said:
Seems that either nobody is using this version or nobody knows about it or they just have nothing to say..
Anyway, as you know, I have spent a fair amount of time recently working with this and installing it. A couple of observations that may be worth noting..
I double checked and I did set a screen timeout on TWRP. Previous versions would first, dim the screen, followed by turning it off completely. If you had the device near you on a desk while backing up the screen lighting up again when TWRP completed was a sure signal that it was finished.
This version of TWRP dims the screen but the screen is never turned off completely. A minor annoyance I suppose but something is different from previous versions.
During the /data partition backup I noted a (to me) new display in yellow: "Backups of data do not include any files in internal storage such as pictures or downloads"
Seriously? Is this something new? Certainly the display is but I always kinda relied on all that being backed up with /data and having the ability to restore them. This is a more serious issue for me which may make me consider going backward..
Thoughts?
Click to expand...
Click to collapse
I use my v10 as my backup phone now. On my HTC U11 life when I make a nandroid it shows that it is not backing up files on internal storage. I think this is normal now on the latest version of twrp.

NYLimited said:
Seems that either nobody is using this version or nobody knows about it or they just have nothing to say..
Anyway, as you know, I have spent a fair amount of time recently working with this and installing it. A couple of observations that may be worth noting..
I double checked and I did set a screen timeout on TWRP. Previous versions would first, dim the screen, followed by turning it off completely. If you had the device near you on a desk while backing up the screen lighting up again when TWRP completed was a sure signal that it was finished.
This version of TWRP dims the screen but the screen is never turned off completely. A minor annoyance I suppose but something is different from previous versions.
During the /data partition backup I noted a (to me) new display in yellow: "Backups of data do not include any files in internal storage such as pictures or downloads"
Seriously? Is this something new? Certainly the display is but I always kinda relied on all that being backed up with /data and having the ability to restore them. This is a more serious issue for me which may make me consider going backward..
Thoughts?
Click to expand...
Click to collapse
On your last issue this is business as usual...twrp has NEVER backed up the internal SDCARD unless you selected the sdcard entry in the list of sections to be backed up. DCIM (pictures) and the Downloads folder/dir have never been included.
As to the dimming, you can check in settings to see if something can be configured however each person compiling twrp can set their own options as to how they want it to function. There is no guarantee or expectation that Person B is going to use the same options as Person A. You are of course free to compile your own copy configured the way you would prefer it to behave but the process was enough of a pain in the butt I just requested twrpbuilder to generate one as I kept getting errors. The process to compile it also appears poorly documented.

sabresfan said:
I use my v10 as my backup phone now. On my HTC U11 life when I make a nandroid it shows that it is not backing up files on internal storage. I think this is normal now on the latest version of twrp.
Click to expand...
Click to collapse
I kinda suspected that but that is, at best, a questionable choice since I don't even have the option to check or uncheck a selection for it. Not happy..
famewolf said:
On your last issue this is business as usual...twrp has NEVER backed up the internal SDCARD unless you selected the sdcard entry in the list of sections to be backed up. DCIM (pictures) and the Downloads folder/dir have never been included.
Click to expand...
Click to collapse
Not quite. INTERNAL is not the SD Card. Internal is emulated sd on /0. In TWRP if you tap select storage, for example, you can pick "internal" or "SD" for backup destination, as one example.
I keep a fair number of things in /Download - things I grab in my travels, things I save there for later use.. whatever. I'll have to device a Tasker module or something for copying all those to the actual SD card...

NYLimited said:
I kinda suspected that but that is, at best, a questionable choice since I don't even have the option to check or uncheck a selection for it. Not happy..
Not quite. INTERNAL is not the SD Card. Internal is emulated sd on /0. In TWRP if you tap select storage, for example, you can pick "internal" or "SD" for backup destination, as one example.
I keep a fair number of things in /Download - things I grab in my travels, things I save there for later use.. whatever. I'll have to device a Tasker module or something for copying all those to the actual SD card...
Click to expand...
Click to collapse
A fairly recent app/utility created by @kdrag0n called Tipatch brings a long-needed resolution to the table regarding "full backups" of Data using TWRP. In a nutshell, Tipatch installs to your Android device as a basic APK. Within the simple GUI, once root permissions are granted (In-Place Patching) Tipatch will decompile, patch, recompile and flash the patched TWRP to /recovery, effectively patching your TWRP build to backup the contents of Internal Storage (emulated SD card) as part of Data itself, so that backups will now include those Internal Storage contents such as downloads, photos, videos, game data, and other various files. I've tried it on this particular build of TWRP and it works without any issues. There are options to patch TWRP without root permissions as well. There are Windows, Mac & Linux versions available too. If you are patching TWRP on a device with an A/B partitioning scheme, the patched TWRP can be installed on both A & B using a one-click option. Of course, one insurmountable caveat to patching TWRP with Tipatch is that wiping Data now will also wipe Internal Storage (emulated SD card). In short, the utility works on pretty well all device types and chipset platforms (Exynos, Kirin, Snapdragon, MediaTek, etc.). The latest Tipatch update, v1.6, includes support for TWRP builds that use LZMA compression, and removes the now-misleading notification previously listed when backing up Data -- that Internal Storage (/data/media/ path / emulated SD card) contents are not backed up. Anyway guys, here is a link to the Tipatch Discussion & Support thread: https://forum.xda-developers.com/android/apps-games/app-twrp-tipatch-backup-internal-t3831217
The latest Tipatch v1.6 app is also available on the Play Store and many other app & apk repos for Android. Versions for Windows, Mac and Linux can be downloaded using the above link.