Related
My nexus s since some days keep rebooting each time i install upgrade an application or move an aplication to sd card.
this thing make me become crazy.
pls pls pls someone help me
give ppl more details [r u rooted, what rom etc]
greg2826 said:
give ppl more details [r u rooted, what rom etc]
Click to expand...
Click to collapse
rooted with matrix 18.5 and jb rom odie sdk port. no problem to copy and read from sd card while in recovery or phone with android working.
spupuz said:
rooted with matrix 18.5 and jb rom odie sdk port. no problem to copy and read from sd card while in recovery or phone with android working.
Click to expand...
Click to collapse
i would flash it again with proper clean install or go for AOSP
greg2826 said:
i would flash it again with proper clean install or go for AOSP
Click to expand...
Click to collapse
yesterday a cleaned up my sd card and got problems also, i also tried to full clean up and install aosp and got same proble i'm worried about an sd hardware problem but i can't imagine whye since 3 days ago it was working.
ii have found also that this actually succed mainly with certain apps
spupuz said:
ii have found also that this actually succed mainly with certain apps
Click to expand...
Click to collapse
going to restore an old 4.0.3 backup to see how it works.
spupuz said:
going to restore an old 4.0.3 backup to see how it works.
Click to expand...
Click to collapse
i gone back to stock 4.0.3 and then to the 4.0.4 restored every apps and tried to move to sd it seems to work correctly.
spupuz said:
i gone back to stock 4.0.3 and then to the 4.0.4 restored every apps and tried to move to sd it seems to work correctly.
Click to expand...
Click to collapse
so it seems to be related to my phone and JBsdk port and JB4.1.1 aosp
i will wait for the offical OTA
I was hoping to try out one of the 4.2 builds tonight, but every time I try to flash one through TWRP it just says "Failed"; I've tried CM10.1 and Eclipse ROM and they both had the same result. Also tried redownloading ROMs and re-copying them to my SD card, still no change. Can anyone tell me what I'm doing wrong here? I've never had a problem flashing any ROM before.
Devilicus said:
I was hoping to try out one of the 4.2 builds tonight, but every time I try to flash one through TWRP it just says "Failed"; I've tried CM10.1 and Eclipse ROM and they both had the same result. Also tried redownloading ROMs and re-copying them to my SD card, still no change. Can anyone tell me what I'm doing wrong here? I've never had a problem flashing any ROM before.
Click to expand...
Click to collapse
What version of TWRP are you running?
If you haven't done it lately, I would suggest updating your twrp to the latest and trying again.
I'm running the newest TWRP (I think), version 2.4.1.0
Devilicus said:
I'm running the newest TWRP (I think), version 2.4.1.0
Click to expand...
Click to collapse
Weird. I am on that same version and have been flashing 4.2 roms for the last few weeks without any issues.
A few things I would try:
-Double check the md5 of the rom you are flashing
-Make sure it is a d2vzw rom
-Wipe caches, delete user data and wipe system
-Put the rom on the internal sdcard before flashing.
Other than that, I got nothing
Relentless D said:
Weird. I am on that same version and have been flashing 4.2 roms for the last few weeks without any issues.
A few things I would try:
-Double check the md5 of the rom you are flashing
-Make sure it is a d2vzw rom
-Wipe caches, delete user data and wipe system
-Put the rom on the internal sdcard before flashing.
Other than that, I got nothing
Click to expand...
Click to collapse
Damn, yeah I can't figure it out; all the ones I've tried were Verizon ones, made sure to wipe everything as usual, tried putting it on the internal SD card and the external, won't work on either one. Very frustrating. But thanks for the help anyway
Ok, I think I figured out the problem (won't be sure until I try it), but I think what happened is I edited my build.prop to the Sprint GS3 to get Google Wallet to work, forgot to change it back, and updated TWRP (which installed the Sprint version, not Verizon), and that's why the flashes are failing. So if any other people are having the same problem, that might be why. Yes I'm an idiot lol. Hopefully this fixes it
Try carbon ROM.
First to work for me.
Sent from my SCH-I535 using xda app-developers app
Devilicus said:
Ok, I think I figured out the problem (won't be sure until I try it), but I think what happened is I edited my build.prop to the Sprint GS3 to get Google Wallet to work, forgot to change it back, and updated TWRP (which installed the Sprint version, not Verizon), and that's why the flashes are failing. So if any other people are having the same problem, that might be why. Yes I'm an idiot lol. Hopefully this fixes it
Click to expand...
Click to collapse
What baseband [modem] do you have installed? ...and some more info if build prop wasn't the issue. Would also be interested if, "but I think what happened is I edited my build.prop", was the issue and you fixed it. Let us know. Goodluck
JohnAreBee said:
What baseband [modem] do you have installed? ...and some more info if build prop wasn't the issue. Would also be interested if, "but I think what happened is I edited my build.prop", was the issue and you fixed it. Let us know. Goodluck
Click to expand...
Click to collapse
Yeah it turns out that was the problem. I edited my build.prop to match the Sprint GS3, so I could download Google Wallet from the Play Store and use it. I just never bothered to change the build.prop back. And when I updated TWRP through GooManager, it assumed I had a Sprint GS3 and installed the wrong recovery. When I flashed the correct Verizon version of TWRP everything worked fine. Thanks for the suggestions everyone
Devilicus said:
Yeah it turns out that was the problem. I edited my build.prop to match the Sprint GS3, so I could download Google Wallet from the Play Store and use it. I just never bothered to change the build.prop back. And when I updated TWRP through GooManager, it assumed I had a Sprint GS3 and installed the wrong recovery. When I flashed the correct Verizon version of TWRP everything worked fine. Thanks for the suggestions everyone
Click to expand...
Click to collapse
Good call. Might be worth mentioning over in the wallet thread. It could save someone the headache you just experienced. Congrats on getting it working.
Sent from my SCH-I535 using Tapatalk 2
Well my mom's tablet(10.1 WiFi, p5113 I guess it is) was horrible working with 4.2.2 so I downgraded it to 4.1. Everything works great, its smooth again, except for Google now. If I update it to the latest version (the one with the buttons in the bottom) it won't open, ever.
Using an older version works.
Any ideas? I did a full backup of the SD card and restored it completely, including the android folder. Could that be the reason?
nlabrad said:
Well my mom's tablet(10.1 WiFi, p5113 I guess it is) was horrible working with 4.2.2 so I downgraded it to 4.1. Everything works great, its smooth again, except for Google now. If I update it to the latest version (the one with the buttons in the bottom) it won't open, ever.
Using an older version works.
Any ideas? I did a full backup of the SD card and restored it completely, including the android folder. Could that be the reason?
Click to expand...
Click to collapse
it is the problem in the update and it is not working on your tab with 4.1 report it to google and in next update i think the problem will be solved i guess
also wipe cache partition in recovery and clear data in apps settings and the latest version might work
good luck :good:
nlabrad said:
Well my mom's tablet(10.1 WiFi, p5113 I guess it is) was horrible working with 4.2.2 so I downgraded it to 4.1. Everything works great, its smooth again, except for Google now. If I update it to the latest version (the one with the buttons in the bottom) it won't open, ever.
Using an older version works.
Any ideas? I did a full backup of the SD card and restored it completely, including the android folder. Could that be the reason?
Click to expand...
Click to collapse
Try it:
Code:
Settings>>Apps>>Google Search>>Clear Data>> Unninstall Updates
then open Google Search set it all again, and then update it...
If it Force close again when updated, report it to Google. :laugh:
Tried everything before this thread, still no luck, I'll stick with the old version then.
Sent from my Nexus 7 using Tapatalk 4
nlabrad said:
Tried everything before this thread, still no luck, I'll stick with the old version then.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
try to uninstall the Google search, reboot then install it again from playstore
Don't forget to hit THANKS button
Tried everything, damnit, i'm goin to try a fresh install, and check if gnow works just after the install, without any other downloaded app.
Thanks.
nlabrad said:
Well my mom's tablet(10.1 WiFi, p5113 I guess it is) was horrible working with 4.2.2 so I downgraded it to 4.1. Everything works great, its smooth again, except for Google now. If I update it to the latest version (the one with the buttons in the bottom) it won't open, ever.
Using an older version works.
Any ideas? I did a full backup of the SD card and restored it completely, including the android folder. Could that be the reason?
Click to expand...
Click to collapse
Hi! Sorry to be annoying but did you backup any apps when you downgraded, if so how? I want to downgrade but ive got loads of stuff I'd rather not lose.
Thanks,
Root in 4.2, use titanium backup, backup the contents of the SD card or tablet storage to your PC, downgrade, restore the storage, restore with TB
Sent from my Nexus 7 using Tapatalk 4
Had anybody seen a situation where the recovery won't keep the correct date and time? I've flashed TWRP 2.7.1.0, 2.8.0.1, and the latest Philz, and all of them kept changing the time, the timezone, and the date... and they were acting a little buggy in their responsiveness.
Thoughts?
WarAxe said:
Had anybody seen a situation where the recovery won't keep the correct date and time? I've flashed TWRP 2.7.1.0, 2.8.0.1, and the latest Philz, and all of them kept changing the time, the timezone, and the date... and they were acting a little buggy in their responsiveness.
Thoughts?
Click to expand...
Click to collapse
I've experienced the same issue since I got my S5. KT TWRP 2.8.1.0 doesn't have that problem. It also fixes the backup to extSD problem, if you were experiencing that.
Ramer84015 said:
I've experienced the same issue since I got my S5. KT TWRP 2.8.1.0 doesn't have that problem. It also fixes the backup to extSD problem, if you were experiencing that.
Click to expand...
Click to collapse
THANKS! I had KT's downloaded but didn't flash it yet... I certainly will now. And yes, the extSD issue bit me, too.
Nope... date is 1/1/2014 and the time is 3 hours lagging for the timezone.
Let's hope at the very least my nandroid backups won't disappear.
WarAxe said:
Nope... date is 1/1/2014 and the time is 3 hours lagging for the timezone.
Let's hope at the very least my nandroid backups won't disappear.
Click to expand...
Click to collapse
Try this: Using something like Root Explorer, look for the TWRP folder on your internal SD card. There's a file called ".twrps". It's the config file for TWRP. Delete it and then boot back into TWRP. You'll have to redo your setting (timezone, screen timeout etc.). See if that fixes it. If that doesn't do it, not sure what else will.
Ramer84015 said:
Try this: Using something like Root Explorer, look for the TWRP folder on your internal SD card. There's a file called ".twrps". It's the config file for TWRP. Delete it and then boot back into TWRP. You'll have to redo your setting (timezone, screen timeout etc.). See if that fixes it. If that doesn't do it, not sure what else will.
Click to expand...
Click to collapse
I had tried peeking into the file with Notepad++ but nothing jumped out at me. Now I feel silly for not trying what you suggested.
I deleted it and it had no effect. The one I deleted and the one it created had the wrong date/time stamps on them... as did the two backups I created (both in metadata and filename convention).
On the bright side... my two backups are as yet undeleted.
WarAxe said:
I had tried peeking into the file with Notepad++ but nothing jumped out at me. Now I feel silly for not trying what you suggested.
I deleted it and it had no effect. The one I deleted and the one it created had the wrong date/time stamps on them... as did the two backups I created (both in metadata and filename convention).
On the bright side... my two backups are as yet undeleted.
Click to expand...
Click to collapse
Very strange, I was sure that was it. My date/time have been correct since using it. The only other thing I may have done was using KT Kernel as well, but I don't think that was it. If you decide to try KT Kernel and want to go back to stock kernel, here's a link for stock: http://forum.xda-developers.com/showpost.php?p=54632862&postcount=1702
Another thought: What version is your firmware? Should be NE5. If not, here's that link: http://forum.xda-developers.com/showthread.php?t=2798079
Ramer84015 said:
Very strange, I was sure that was it. My date/time have been correct since using it. The only other thing I may have done was using KT Kernel as well, but I don't think that was it. If you decide to try KT Kernel and want to go back to stock kernel, here's a link for stock: http://forum.xda-developers.com/showpost.php?p=54632862&postcount=1702
Another thought: What version is your firmware? Should be NE5. If not, here's that link: http://forum.xda-developers.com/showthread.php?t=2798079
Click to expand...
Click to collapse
Thanks for the links.
I didn't flash the KT Kernel because the post said it needed to be flashed onto a TouchWiz based ROM... and right now I have PacMan (AOKP). I had MOAR (NE5) installed for a bit but I'm not used to stock. Truthfully, MOAR had everything I could want... I may just have to get over my snootiness.
Oh, it's coming back to me... with MOAR I was getting a lot of error popups of processes stopping running. i think "acore" was a common one. I could have troubleshot but didn't.
WarAxe said:
Oh, it's coming back to me... with MOAR I was getting a lot of error popups of processes stopping running. i think "acore" was a common one. I could have troubleshot but didn't.
Click to expand...
Click to collapse
Make sure your backup works and come on over I'm a big supporter of MOAR! Do a clean install though and I bet 99.9% of your problems will be solved
Ramer84015 said:
Make sure your backup works and come on over I'm a big supporter of MOAR! Do a clean install though and I bet 99.9% of your problems will be solved
Click to expand...
Click to collapse
There's the main install 2.1, and the new stuff 1.7, and of course Gapps. Do folks typically flash them all together... Or separately sequentially?
My clean install is usually wiping cache, dalvik, data, and system.
WarAxe said:
There's the main install 2.1, and the new stuff 1.7, and of course Gapps. Do folks typically flash them all together... Or separately sequentially?
My clean install is usually wiping cache, dalvik, data, and system.
Click to expand...
Click to collapse
MOAR is TW, so gapps is included. My FAQ and guide for MOAR may help you get a feel for it.
Ramer84015 said:
MOAR is TW, so gapps is included. My FAQ and guide for MOAR may help you get a feel for it.
Click to expand...
Click to collapse
Okay... MOAR's on there now. I'll read up and tweak to the extent I'm able and see if I have any questions.
WarAxe said:
Okay... MOAR's on there now. I'll read up and tweak to the extent I'm able and see if I have any questions.
Click to expand...
Click to collapse
Feel free to post any questions on the Q&A thread. :good:
I am having an issue work my car stereo connecting to "media audio" on my phone. The phone always connects and media audio works fine with all other Bluetooth devices except my car. I can get it to work after the stereo says no connection I toggle media audio and then it connects. It used to auto connect no problem. Any help would be appreciated.
Stereo: Standard 2015 Mitsubishi Outlander Sport
ROM: OOS 10 Stable
Phone Mods: FDE.AI, rooted, bootloader unlock
Magisk modules: Oxytweaker, Google dialer framework, YouTube vanced
I had a similar issue suddenly appear. The first saved Bluetooth device auto connected. None of the others would. Couldn't figure out what to do. In the end I rebooted to TWRP and restored.
RogerNZ said:
I had a similar issue suddenly appear. The first saved Bluetooth device auto connected. None of the others would. Couldn't figure out what to do. In the end I rebooted to TWRP and restored.
Click to expand...
Click to collapse
Were you on 10?
jac0b said:
Were you on 10?
Click to expand...
Click to collapse
Yes, 10.0 with xxxNoLimits
To get the Bluetooth to work right will I need to downgrade back to 9.5.11
RogerNZ said:
Yes, 10.0 with xxxNoLimits
Click to expand...
Click to collapse
What are you running now the same 10.0
10.0.1 with xxxNoLimts
RogerNZ said:
10.0.1 with xxxNoLimts
Click to expand...
Click to collapse
I have updated to 10.0.1 and same issue could you know I am doing wrong i don't use xXx or custom kernel but would like to use 10
SirFronts said:
could you know what I am doing wrong
Click to expand...
Click to collapse
No sorry, I wish I could. But I am not clever with phones.
I restored system. That did not fix it.
I restored vendor. That did not fix it.
I restored data. That fixed it.
It doesn't make sense to me. But that is what I did.
I hope someone else more knowledgeable than you or I can chip into the conversation here.
RogerNZ said:
No sorry, I wish I could. But I am not clever with phones.
I restored system. That did not fix it.
I restored vendor. That did not fix it.
I restored data. That fixed it.
It doesn't make sense to me. But that is what I did.
I hope someone else more knowledgeable than you or I can chip into the conversation here.
Click to expand...
Click to collapse
How do you just restore data I may try that after work today
Thank you not a lot of people will even give me new ideas other then reinstall it or going thru and resetting my Bluetooth, WiFi and mobile data
Or deleting cache and storage under the Bluetooth app
SirFronts said:
How do you just restore data
Click to expand...
Click to collapse
TWRP > Restore > Data
Of course, if you have not previously backed up Data in TWRP, then it will not be possible.
With regards to all those other suggestions you mentioned, none of them worked for me. But if you have not yet tried them, I would still suggest you do.
Good luck!
RogerNZ said:
TWRP > Restore > Data
Of course, if you have not previously backed up Data in TWRP, then it will not be possible.
With regards to all those other suggestions you mentioned, none of them worked for me. But if you have not yet tried them, I would still suggest you do.
Good luck!
Click to expand...
Click to collapse
Bet so I should do a back up of my 9.5.11 and the update to 10.0.1 keep root and then use twrp hit restore and just restore the data right
SirFronts said:
Bet so I should do a back up of my 9.5.11 and the update to 10.0.1 keep root and then use twrp hit restore and just restore the data right
Click to expand...
Click to collapse
There is no point in restoring Data unless your backup was done prior to the issue arising.
If you already have 9.5.11 System, Vendor and Data backed up, and you know at the time of back up there were no Bluetooth issues - then yes restore that. But I don't know the process to downgrade like that. If you are successful in that, then you should be able to upgrade from there afterward. Hopefully without further Bluetooth error.
But I need to remind you. I am not good with phones and can't be sure restoring Data is what actually worked. It doesn't make sense to me that it would.
RogerNZ said:
There is no point in restoring Data unless your backup was done prior to the issue arising.
If you already have 9.5.11 System, Vendor and Data backed up, and you know at the time of back up there were no Bluetooth issues - then yes restore that. But I don't know the process to downgrade like that. If you are successful in that, then you should be able to upgrade from there afterward. Hopefully without further Bluetooth error.
But I need to remind you. I am not good with phones and can't be sure restoring Data is what actually worked. It doesn't make sense to me that it would.
Click to expand...
Click to collapse
No I understand I've already downgraded and upgraded and downgraded the software a few times so I think I got that under control but yeah I'll try restoring data after I update because Bluetooth works on the 9.5.11 update no problem
Thank you again
RogerNZ said:
There is no point in restoring Data unless your backup was done prior to the issue arising.
If you already have 9.5.11 System, Vendor and Data backed up, and you know at the time of back up there were no Bluetooth issues - then yes restore that. But I don't know the process to downgrade like that. If you are successful in that, then you should be able to upgrade from there afterward. Hopefully without further Bluetooth error.
But I need to remind you. I am not good with phones and can't be sure restoring Data is what actually worked. It doesn't make sense to me that it would.
Click to expand...
Click to collapse
Just wanted to update restoring my data put me in a bootloop it's cool IDK what it could be
I don't have this issue... I'm on OSS 10.0.1 stock
SirFronts said:
in a bootloop
Click to expand...
Click to collapse
Sorry to hear that
spinoza23 said:
I don't have this issue... I'm on OSS 10.0.1 stock
Click to expand...
Click to collapse
I'm running 10.0.1
Do you think if I install a new kernel it might start working again that's the only thing I have not tried
RogerNZ said:
Sorry to hear that
Click to expand...
Click to collapse
It happens lol but thanks for the looking out I rather try something then nothing kinda out look just thank God for the MSM Tool lmao ?
SirFronts said:
I'm running 10.0.1
Do you think if I install a new kernel it might start working again that's the only thing I have not tried
Click to expand...
Click to collapse
I don't know, but you have the same model like me...
I'm in completely stock ROM no root, no magisk, no bootloader unlocked.
My car SUV Renault Koleos 2019... Aptx, Aptx-HD works great