Ive seen many questions in the Q & A forum about this CWM and figured the best way is to get developers and other main contributors to look at the issues some of the "little people" have about using it. DAF was convenient and easy for all because it was one click for the people who could get that far, and since CWM, there where the 3 versions and this one has yet to really be well touched upon as a full tutorial with the copy to SD not being needed any more. I feel as do many others that a main "sticky" thread be made for it with a few FAQ on this section of the forum so they do not have to search too far away from the main thread they are using and get completely confused.
1. Will doing a backup and changing ROMs using CWM with different partition delete my backup?
2. Will doing a backup KEEP my partition?
3. Is it possible to do a partition from CWM or is the partition need to be carried on a computer?
(this to me seemed to defeat the purpose of CWM with some DEVs making their own partition layouts and not using the main ones that were originally laid out for use, no aim towards DEVs because I know they work hard)
4. If I put multiple ROMs on my SD card do I need to change the partition every time if I want to change them?
5. Is there a way to know which backups are from which ROMs I had used?
(I guess this is asking if they can change the name?)
6. How do I know when to "Wipe Cache Partition"?
I know there is *THIS* thread, however there are surely some differences between the copy of those files and not needing to copy amongst other things to which the "new" people do not understand.
If this is just a bother and hindrance to you all, I understand the deletion of this thread, however it did take quite a while to plan out what to write, and what not to should you choose to do so and I would give the answers, however even I do not know all of them and so I leave this to you all for debate. NO PUBLIC BASHING PLEASE
Dude, this forum is for posting dev projects. Why on earth do you think its ok to post a questions topic in here when we have a dedicated questions forum?!?!
TheATHEiST said:
Dude, this forum is for posting dev projects. Why on earth do you think its ok to post a questions topic in here when we have a dedicated questions forum?!?!
Click to expand...
Click to collapse
I said it could be moved or deleted just the questions are not very well maintained in that DEDICATED (? HA) forum there are multiple posts of the same and I felt that since there is a sticky thread here that could answer the forum issue of the DEVELOPED CWM program this should be brought to the attention and as such is a DEV related issue. It can and most likely will be moved, do you have an answer to any of the issues the people asked?
TheATHEiST said:
Dude, this forum is for posting dev projects. Why on earth do you think its ok to post a questions topic in here when we have a dedicated questions forum?!?!
Click to expand...
Click to collapse
now that it's been moved, nobody will discuss the answers and it's a pointless post.
harrystone33 said:
1. Will doing a backup and changing ROMs using CWM with different partition delete my backup?
Click to expand...
Click to collapse
No this will not delete your back up as it is saved on yor SD card when you do the back up.
harrystone33 said:
2. Will doing a backup KEEP my partition?
Click to expand...
Click to collapse
This I am not really sure of as I am not a dev but I think it does as the backup is just a backup of your settings, personal information, your gmail account associated with your Android, boot data, and any cache data that you have built up.
harrystone33 said:
3. Is it possible to do a partition from CWM or is the partition need to be carried on a computer?
(this to me seemed to defeat the purpose of CWM with some DEVs making their own partition layouts and not using the main ones that were originally laid out for use, no aim towards DEVs because I know they work hard)
Click to expand...
Click to collapse
You can partition your SD card with CWM but I do not think you can do a system portion as CWM is what creats the system portion when you flash it. It creates a partition in the CWM.
harrystone33 said:
4. If I put multiple ROMs on my SD card do I need to change the partition every time if I want to change them?
Click to expand...
Click to collapse
Once again I am not a dev (yet) and I am not 100% sure of this. But I would say if the ROMs you have stored on SD card need different portition sizes then yes you will need to change the partition size when you change ROMs. If they require the same partition size then no you do not need to change the partition size.
harrystone33 said:
5. Is there a way to know which backups are from which ROMs I had used?
(I guess this is asking if they can change the name?)
Click to expand...
Click to collapse
You should be able to manually go into your SD card with a computer and change the name on the backup file, but I do not know if this will interfer with CWM being able to detect the backup file. So you might want to write down the original full name of the file befor you change it.
harrystone33 said:
6. How do I know when to "Wipe Cache Partition"?
Click to expand...
Click to collapse
As a rule of thumb I would not delete my cache unless I was about to flash a new ROM.
Also check out my guide I wrote in linked in my sig, you might find it useful.
Hope this helps you out some.
Is there anyway to export the backups created in clockwork? I have a couple of roms setup the way I like and backed up. I want to export them to my computer to clear some room on my sd card but want to make sure I can flash them as needed. Any issues with just cutting and pasting them?
crxin said:
Is there anyway to export the backups created in clockwork? I have a couple of roms setup the way I like and backed up. I want to export them to my computer to clear some room on my sd card but want to make sure I can flash them as needed. Any issues with just cutting and pasting them?
Click to expand...
Click to collapse
I've never done it, but I don't see why copying them to your Pc would mess things up. I think that would work just fine. I'd do a test run if I were you, but should be fine.
EDIT: and before someone else says it this really belong in Q&A not development.
ok sorry maybe someone could move it for me.
There ain't be a Q&A section in these parts.
cstrife999 said:
I've never done it, but I don't see why copying them to your Pc would mess things up. I think that would work just fine. I'd do a test run if I were you, but should be fine.
EDIT: and before someone else says it this really belong in Q&A not development.
Click to expand...
Click to collapse
To the OP. Yes you can. Just copy the backup onto your computer and you can delete it from your SD card. And if you want it back, just copy it back on. No problems at all
Awesome thanks for the information.
Sent from my DROIDX using XDA App
Cleaned. In the future, you can all keep your testy comments to yourselves and just PM me to move the thread, which I will almost certainly find and move anyway (like I did this one.) Keep it civil. You just clutter the thread with flaming, which makes it harder for n00bs to find answers, which results in... more threads in the wrong section!
It's the great Circle of Life.
Consider this thread your one place to chat or anything else related to jellybean on the Asus Transformer.
I need everyones help to keep this thread somewhat sane, report any trolling or flaming and don't respond to it.
All other threads on this topic will be closed.
Keep all your posts in this thread polite and make sure you follow the rules
For all your JB needs go [GUIDE]Upgrade your TF300t to Jellybean, recovery, root & remove bloatware[Noobproof]
and
[INDEX][08 OCT 12] INDEX of ROMS/RECOVERY/ROOT/GUIDES/FIRMWARE/KERNEL/VIDEOS/etc..
I request you to stop posting:
- 'Thanks this helped'
- 'Yeah Me too'
-'+1'
These kind of posts are useless instead use the thanks button to show your appreciation
Click to expand...
Click to collapse
1. Search before posting.
Use one of our search functions before posting, whether you have a question or something new to share, it's very likely someone already asked that question or shared that news.
2. Member conduct.
2.1 Language: XDA is a worldwide community. As a result what is ‘ok’ to say in your part of the world may not be ok in someone else’s part of the world. Please think about who is reading what you write. Keep in mind that what you think of as acceptable use of language may not be acceptable to others. Conversely, while reading member posts, remember that word you find offensive may not be to the writer. Tolerance is a two way street.
2.2 Nudity: XDA is used by people of all ages, including minors. It's not acceptable to post nude/pornographic imagery, which includes exposure of the male or female genitalia or of female breasts.
2.3 Flaming: XDA was founded as a group of people sharing information about certain mobile phones. Sharing does not involve virtual yelling (flaming) it does involve working together to solve problems in an environment of mutual respect and understanding. Losing your temper and flaming another member, or group of members, is not acceptable behavior.
2.4 Personal attacks, racial, political and/or religious discussions: XDA is a discussion forum about certain mobile phones. Mobile phones are not racial, political, religious or personally offensive, therefore none of these types of discussions are permitted on XDA.
2.5 Courtesy towards other Members: Treat new members the way you would like to have been treated when you were a new member. When dealing with any member, provide them with guidance, advice and instruction when you can and always with respect and courtesy. Never post in a demanding, argumentative, disrespectful or self-righteous manner.
2.6 All members are expected to read and adhere to the XDA rules.
3. Post only using a clear subject and message.
You're most likely to receive a helpful answer to your question if you use a short subject title that describes your problem and a message that explains in detail what your problem is and what you've tried to solve it.
4. Use the English language.
We understand that with all the different nationalities not everyone speaks English well, but please try. If you're really unable to post in English use an online translator, You're free to include your original message in your own language below the English translation.
5. Post a message only once.
As a large forum we don't need unnecessary clutter, You're free to edit your message as you like, so if you do not receive an answer revisit your message and see if you can describe your problem better. Not everyone is online at the same time, it might take a while before you receive an answer.
6. Do not post warez.
If a piece of software requires you to pay to use it, then pay for it. We do not accept warez nor do we permit any member to promote or describe ways in which Warez, cracks, serial codes or other means of avoiding payment, can be obtained. This is a site of developers, i.e. the sort of people who create such software. When you cheat a software developer, you cheat us as a community
7. Do not spam.
If you wish to advertise a product, contact us we provide ads. But do not post it in the forums, it will be removed and you're likely to receive a ban.
You are however allowed to sell used goods like your own device, parts of your device or accessories for your device in the marketplace forum, please read the rules there before posting. (This rule includes signatures, if you use a signature it will appear in your post)
8. Donations.
We appreciate all donations to xda-developers.com, it keeps our forum online and well maintained. As a user you're allowed to ask for donations in your signature as a thank you for your hard work. However donations up front are not allowed, this forum is about sharing, not about getting paid to do something, that's what your job is for.
9. Don't get us in trouble.
Don't post copyrighted materials or do other things that will obviously lead to legal trouble. If you wouldn't do it on your own homepage, you probably don't want to do it here either. This does not mean we agree with everything the software piracy lobby try to impose on us, it simply means you cannot break any laws here, since we'll end up dealing with legal hassle caused by you. Please use common sense: respect the forum, its users, and those that write great code.
10. Help others if you can.
If you see posts from others where you can help out, please do. This place exists because people are helping each other, and even if you are relatively new to the matter, there's probably already quite a few people newer than you that would benefit from what you've learned. Don't be shy.
11. Don’t post with the intention of selling something.
Don’t use XDA to advertise your product or service. Proprietors of for-pay products or services, may use XDA to get feedback, provide beta access, or a free version of their product for XDA users and offer support, but not to post with the intention of selling. This includes promoting sites similar/substantially similar to XDA-Developers.com.
Do not post press releases, announcements, links to trial software, or commercial services. unless you’re posting an exclusive release for XDA-Developers.com.
Encouraging members to participate in forum activities on other phone related sites is prohibited.
Off-site downloads are permitted if the site is non-commercial and does not require registration.
Off-site downloads from sites requiring registration are NOT encouraged but may be permitted if the following conditions are met:
A) the site belongs to a member of XDA-Developers with at least 1500 posts and 2 years membership who actively maintains XDA-Developers' support thread(s) / posts, related to the download,
B) the site is a relatively small personal website without commercial advertising/links (i.e. not a competitor forum-based site with purposes and aims similar to those of XDA-Developers.com.)
12. Using the work of others.
If you are developing something that is based on the work of another Member, you MUST first seek their permission, and you must give credit to the member whose work you used. If a dispute occurs about who developed / created a piece of work, first try to settle the matter by private message and NOT in open forum. If this fails then you may contact a moderator with clear evidence that the work was created by you.
Convincing evidence will result in copied work being removed. If there is no clear evidence you created the work then in the spirit of sharing all work will remain posted on the forums.
As an addition, developers have the right to hold exclusivity over their work for as long as it is deemed necessary by the dev or freely share it. However, if the work is claimed as exclusive, it must remain as such. No selective sharing will be allowed (ie allowing certain people to use it and not others). Should the dev decide to start sharing the work with others, the work automatically becomes fair game for all to use.
In regards to permissions, same rules remain for this but if permission was already given, unless there is a very valid reason, it cannot be revoked (same applies to major updates on the work). Under that same premise, permissions cannot be denied unless the work is exclusive or under severe circumstances.
In plain English: If you want to keep your work exclusive, go for it. However, if you are going to share your work, do it fairly.
These rules apply to all software posted on XDA (including but not limited to ROMs, RUUs, apps, games, kernels, themes, icons, etc) unless that software comes with a license that waives these rules.
13. Advertising and Income Generation
Commercial advertising, advertising referral links, pay per click links and other income generating methods are forbidden. Do not use xda-developers as a means to make money.
14. Create only one User Account
You are allowed one User Account at xda-developers. If you create additional accounts, Moderators will disable them and your original account may also be disabled or infracted.
15. Keep posts/threads on-topic
Whilst a minor amount of off-topic posting may be overlooked, the general rule is your posts / threads must be relevant to the Forum / thread in which you are posting.
16. Bumping Threads (posting simply to force a thread to the top of the thread queue)
Do not "bump" a thread more than once per 24 hours.
Click to expand...
Click to collapse
Thanks,
It's good to remember that we have rules in xda.
If you are a new member, junior member or young senior member, force yourself to read these rules.
This is to avoid to close your OP or delete your post.
And then especially seek and read a bit more before posting anywhere.
TF300T users are welcome
and enjoy some good time on this thread and share your passion for your device
Hi guys I have a tf300T
I must say my tf300 was updated 7 days ago to JB from OTA asus update, so I don't need if there is something locked features I need to un lock...any help would be very appreciated...
I followed all the steps, but when I launch the "fastboot" I got this message
Microsoft Windows XP [Versione 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\mezzalana>cd documenti
C:\Documents and Settings\mezzalana\Documenti>cd downloads
C:\Documents and Settings\mezzalana\Documenti\Downloads>cd tablet
C:\Documents and Settings\mezzalana\Documenti\Downloads\tablet>adb reboot bootlo
ader
C:\Documents and Settings\mezzalana\Documenti\Downloads\tablet>fast boot -i 0x0b0
5 flash recovery tf300t-jb.blob
sending 'recovery' (6524 KB)...
OKAY [ 2.625s]
writing 'recovery'...
FAILED (remote: (InvalidState))
finished. total time: 5.891s
C:\Documents and Settings\mezzalana\Documenti\Downloads\tablet>adb reboot bootlo
ader
C:\Documents and Settings\mezzalana\Documenti\Downloads\tablet>adb reboot bootlo
ader
C:\Documents and Settings\mezzalana\Documenti\Downloads\tablet>
Click to expand...
Click to collapse
then if I try to select the rck icon and flash the superuser zip file I got a dead android with a red exclamation mark on his stomach...
any help?
I solved, we need to download an pak directly from asus it is called "boorloader unlock" in this way you unlock the device and you can Apply all the steps. I think is better to say this, some noob like me could be very confused.
the asus link is
http://www.asus.it/Tablet/Transformer_Pad/ASUS_Transformer_Pad_TF300T/#download
In the guide there is the name of the apk bloatware files...but how can I delete them? Root explorer?
marcomesa said:
I solved, we need to download an pak directly from asus it is called "boorloader unlock" in this way you unlock the device and you can Apply all the steps. I think is better to say this, some noob like me could be very confused.
In the guide there is the name of the apk bloatware files...but how can I delete them? Root explorer?
Click to expand...
Click to collapse
Ah ah ah, you are really a joker.
Do you think that I give the pain to write and update an index for TF300TF / TG for nobody reads it.
and in this index, you will find the unlock tool and the download link
You will find the link to this index in a large number of posts and the OP.
Therefore take care, and give you the time to read and to search for a little!!!!
Ok thanks for the teaching...you need patience with people like me, I'm still learning
marcomesa said:
Ok thanks for the teaching...you need patience with people like me, I'm still learning
Click to expand...
Click to collapse
And for your information, you will find a "THANKS" button just left down.
It will be cool to write thanks, but it will be better to click "THANKS"
Since my thread got closed, even though it was about the "general procedure" and not specifically discussing Jelly Bean in any way, just asking if I might as well use the WW version of a JB-based ASUS official FW instead of the recommended US one, siberian tiger requested me to post this here.
Hey there! I'm getting a TF300 pretty soon and just wanted to make sure I got the necessary steps for some fun with it right..
1st: Rooting
2nd: Bootloader Unlocking
3rd: Upgrading to JB without losing root
This correct so far? Is the US Update mentioned in the 3rd step really necessary or can I use an equivalent WW version of the Update?
Please don't hit me with the stick, I'm just trying to get the most out of the TF300 without turning it into a doorstop.
twiitar said:
Since my thread got closed, even though it was about the "general procedure" and not specifically discussing Jelly Bean in any way, just asking if I might as well use the WW version of a JB-based ASUS official FW instead of the recommended US one, siberian tiger requested me to post this here.
Hey there! I'm getting a TF300 pretty soon and just wanted to make sure I got the necessary steps for some fun with it right..
1st: Rooting
2nd: Bootloader Unlocking
3rd: Upgrading to JB without losing root
This correct so far? Is the US Update mentioned in the 3rd step really necessary or can I use an equivalent WW version of the Update?
Please don't hit me with the stick, I'm just trying to get the most out of the TF300 without turning it into a doorstop.
Click to expand...
Click to collapse
Your thread has been closed in order to regroup all the discussions on JB in general and especially to avoid having too many posts unnecessary and repetitive.
Don't take it as a punishment or anything else. It's not.
It is more convenient to manage the answers.
And for all of your questions, I can say that it's correct
You can buy your TF300T quietly
Does your microsd slot work after update to JB?
gabor94 said:
Does your microsd slot work after update to JB?
Click to expand...
Click to collapse
Yes without problem.
I have a 32 Gb sd card class 10 - it's partitioned: 20 Gb NTFS format (for the movies) - and the rest to Fat32
be care !!!!!! i bricked my tf300t
Hi All..
My TF300t is unlocked and rooted . I installed the new JB and then I was trying to install CWM. I used fastboot to push it to the device. When I rebooted, holding down the volume button, It came up to the menu with RCK, USB, etc. I selected wipe data by accident. It sat there for a while saying it was going to wipe and go into the boot loader. After a while I shut it off thinking it was hung. Now when I power on the device I get only the ASUS startup screen. Volume up or down don't affect the mode. It just says "The Device is Unlocked" at the top, and the static ASUS logo in the middle. When I plug in the USB to my Windows 7 computer I get nothing in the device listing.
i install universal naked driver
and could enter in APX mode and my pc show apx driver
how can i restore my bootloader and fastboot
i did not have nvflash backup
many thanks
---------- Post added at 03:31 PM ---------- Previous post was at 03:17 PM ----------
Hi All..
My TF300t is unlocked and rooted . I installed the new JB and then I was trying to install CWM. I used fastboot to push it to the device. When I rebooted, holding down the volume button, It came up to the menu with RCK, USB, etc. I selected wipe data by accident. It sat there for a while saying it was going to wipe and go into the boot loader. After a while I shut it off thinking it was hung. Now when I power on the device I get only the ASUS startup screen. Volume up or down don't affect the mode. It just says "The Device is Unlocked" at the top, and the static ASUS logo in the middle. When I plug in the USB to my Windows 7 computer I get nothing in the device listing.
i install universal naked driver
and could enter in APX mode and my pc show apx driver
how can i restore my bootloader and fastboot
i did not have NVFLASH backup
many thanks
arch.fadi said:
Hi All..
i install universal naked driver
and could enter in APX mode and my pc show apx driver
how can i restore my bootloader and fastboot
i did not have NVFLASH backup
Click to expand...
Click to collapse
Warning: Uninstall any previous driver package's you may have installed and also manually remove drivers by attaching your phone and going to Windows device manager and right click the entry for your phone and select "Uninstall" on the next prompt make sure to select "Delete the driver software for this device" then hit OK and reboot before installing these drivers
Click to expand...
Click to collapse
It's writing in the OP of the Universal naked drivers. Have you uninstalled your old packages ?
So actually, it's better to uninstall all your packages from your computer, reboot, and re-install U.N.Drivers
And never forgotten to making always backup. It's better to do more than none
Try this and report a feedback
philos64 said:
It's writing in the OP of the Universal naked drivers. Have you uninstalled your old packages ?
So actually, it's better to uninstall all your packages from your computer, reboot, and re-install U.N.Drivers
And never forgotten to making always backup. It's better to do more than none
Try this and report a feedback
Click to expand...
Click to collapse
sorry. but what you mean whit old packages ?
i installed APX driver successfully ,and my pc recognized the tablet as APX device
but the question : any hope to restore bootloader or fastboot in APX mode
thenks
I think that it will be good to read this, if it help you:
Tegra3 Guide: nvflash
Have you made this ?
To do this please reboot your tablet into APX mode by holding down the volume up key during the reboot process. If successful the screen should remain blank and be detected over USB by your computer as an NVIDIA APX mode device.
Click to expand...
Click to collapse
if it's run, you can make this:
To “bootstrap” into nvflash using wheelie simply run the following command:-
Code:
$ wheelie --blob blob.bin
If successful your device will boot into nvflash mode and the bootloader screen will appear on the device.
Click to expand...
Click to collapse
or
Have you got those symptoms on your TF ?
- Blank screen,
- apx only detected,
- holding power down does nothing
and if you have those symptoms, the only solution seems RMA, if you don't have a working bootloader and didn't made the nvflash setting process you're done, or backup.
philos64,
Does the stock JB 4.1.1 kernel support NTFS mounting with R/W? How about exFAT?
CrimsonKnight13 said:
philos64,
Does the stock JB 4.1.1 kernel support NTFS mounting with R/W? How about exFAT?
Click to expand...
Click to collapse
I have a 32 Gb sd card class 10 - it's partitioned: 20 Gb NTFS format (for the movies) - and the rest to Fat32
I don't know if it works in Stock, but I'm use it on CleanRom and on JB Overclock without problem.
You can try and make a report after.
Thanks
philos64 said:
I have a 32 Gb sd card class 10 - it's partitioned: 20 Gb NTFS format (for the movies) - and the rest to Fat32
I don't know if it works in Stock, but I'm use it on CleanRom and on JB Overclock without problem.
You can try and make a report after.
Thanks
Click to expand...
Click to collapse
I'll be sure to do that & let you know. I'll be getting a brand new 64GB UHS-1 MicroSDXC card by Thursday, so I'll test it out then.
CrimsonKnight13 said:
I'll be sure to do that & let you know. I'll be getting a brand new 64GB UHS-1 MicroSDXC card by Thursday, so I'll test it out then.
Click to expand...
Click to collapse
I use the NTFS format for the movies, cause I have some movies (for my child) in MKV format (1GB ~3GB)
philos64 said:
I use the NTFS format for the movies, cause I have some movies (for my child) in MKV format (1GB ~3GB)
Click to expand...
Click to collapse
FAT32 supports up to 4GB file size. Anything beyond 4GB would need NTFS or exFAT.
https://en.wikipedia.org/wiki/Comparison_of_file_systems#Limits
You probably don't need NTFS at all unless you are gaining the added benefits of it within JB.
Trying to fix my Bluetooth issue, as chronicled in detail here.
Wanted to ask you devs where Bluetooth configuration or a related error log is stored on the i9505G so I can take a look at it; something is stopping my BT from being able to turn on; it used to work fine pre-root (heck, even post-root for a day or so).
I figured the developers would be the best people to ask since you'd be familiar with the folder structure and config files.
KrossX said:
Trying to fix my Bluetooth issue, as chronicled in detail here.
Wanted to ask you devs where Bluetooth configuration or a related error log is stored on the i9505G so I can take a look at it; something is stopping my BT from being able to turn on; it used to work fine pre-root (heck, even post-root for a day or so).
I figured the developers would be the best people to ask since you'd be familiar with the folder structure and config files.
Click to expand...
Click to collapse
Sent from my GT-I9505G using Tapatalk 2
KrossX this is the second time you have posted questions in the development forum. As I stated before these are for Q&A NOT here. Please refrain from posting your questions here and READ the XDA users guide and forum rules again. There is a reason for this. I am glad your part of the community and your questions and comments are noteworthy you just need to put them in the right place. We read those threads as well! MJ
This is for Development ONLY
Yes PLEASE no name calling we all make mistakes and this thread will be moved soon to the proper place
And to answer your question Kriss you could do a logcat but if your not familiar with that do a search and provide more info on what your trying to do ( configuration?)
Sent from my GT-I9505G using Tapatalk 2
MJHawaii said:
Yes PLEASE no name calling we all make mistakes and this thread will be moved soon to the proper place
And to answer your question Kriss you could do a logcat but if your not familiar with that do a search and provide more info on what your trying to do ( configuration?)
Sent from my GT-I9505G using Tapatalk 2
Click to expand...
Click to collapse
I thought that since I was aiming this more at the devs it would've been in the Dev forums. Sorry for having you move yet another thread of mine.
Didn't mean to cause a ruckus; never really got a chance to read the post by deaffob above before it was edited by the mod so no offense from whatever name-calling was done, haha.
Thanks MJHawaii; I will search for logcat and see what I can pull up.
Any ideas (referring to attached pic)? I filtered at the Error level in the logs for the term "Bluetooth"
Sent from my GT-I9505G using Tapatalk 4
KrossX said:
Any ideas (referring to attached pic)? I filtered at the Error level in the logs for the term "Bluetooth"
Sent from my GT-I9505G using Tapatalk 4
Click to expand...
Click to collapse
The first error there looks like it may be relevant, but you'll need to get a more thorough logcat in order to trouble shoot it more. Please grab one with adb and post it to pastebin or here in a [ code][ /code] box.
xHausx said:
The first error there looks like it may be relevant, but you'll need to get a more thorough logcat in order to trouble shoot it more. Please grab one with adb and post it to pastebin or here in a [ code][ /code] box.
Click to expand...
Click to collapse
Good news and bad news.
Bad news: I am unable to run logcat; I am unable to access my device via USB ever since the root and when I tried doing the logcat steps, yet again it couldn't connect to my device.
Good news: I believe the solution to this issue (being unable to access my device via USB) may also lie in the logs along with the bluetooth issue. The reason why is because of this error message I received while trying to reinstall the USB driver (attached pic); it points to not being able to "start" a device. I think this will all eventually tie-in with some services not running correctly on my phone.
So, is there another way for me to post a log for you kind folks to review on here via my phone directly?
If I can do that via catlog app on my device, let me know what sort of log (which options) I'd need to run and post. Thanks!
Well, did a restore to stock + root. That didn't help. It changed the Baseband, Kernel, and Build versions but did nothing to fix my issues with BT and USB connectivity.
I think I am going to start researching ways to start from scratch. Like a factory reset/wipe back to first-use condition. If anyone can point me towards some reading material on how to do that safely and wisely, it would be much appreciated!
I just ended up doing a factory reset (Menu-->Settings-->Backup & Reset-->Factory Data Reset) and that resolved the issue (while wiping my phone).
Bluetooth issue is resolved; tested it just now and it works just fine again. As is the USB issue; as soon as the phone was connected to the same exact PC as before, it was recognized and showed up as a device that I could open and explore.
My Kernal/Baseband/Build versions are all back to the ones I had when I got the phone from the Google Store, so that's comforting too.
Thanks to all those who attempted to help!
On my Moto Z griffin with LineageOS latest nightly, after I've done a nandroid backup with TWRP, it seems that apps can't write anymore to the SD (adoptable).
For example WhatsApp can't download images or video, can't do a backup of the chats, apps don't update (error code: 963).
I've tried to chmod 777 the whole data folder, but it just doesn't change permission.
I've tried to do another nandroid backup, but nothing.
I've updated the the latest nightly, but nothing.
I've formatted cache and dalvik, but nothing.
What else is left before doing a factory reset?
Andrea
andrea_x said:
On my Moto Z griffin with LineageOS latest nightly, after I've done a nandroid backup with TWRP, it seems that apps can't write anymore to the SD (adoptable). For example WhatsApp can't download images or video, can't do a backup of the chats, apps don't update (error code: 963)...
Click to expand...
Click to collapse
In case you didn't know, the following is a dedicated area on the Forum for your specific device.
https://forum.xda-developers.com/moto-z
With that stated...
I don't have your specific device but, your issue does seem to be a toss up in posting your issue within the following LineageOS or TWRP threads for your device.
https://forum.xda-developers.com/showthread.php?t=3546612
https://forum.xda-developers.com/showthread.php?t=3547672
If all else fails, your best bet is to post this question within the following noob help thread for your device.
https://forum.xda-developers.com/showthread.php?t=3408921
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
I thought that this was more of a general LineageOS problem than a device one.
I'll move it
andrea_x said:
I thought that this was more of a general LineageOS problem than a device one.
I'll move it
Click to expand...
Click to collapse
I never stated (nor intended to state) that it was a device issue but, the first 2 links on my last post are to the Official LineageOS thread for your device as well as the TWRP thread for your device too.
Go to the LineageOS thread and post your issue to, hopefully, get a response from a member with some further guidance.
It never hurts to ask...
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE