Database Info

[Q] Htc Evo 4G LTE Jellybean crashing super su

Hello all i just did the 3.15.651.16 update from viper boy and everything was good until i tried to update Su binary in Supersu.. it crashes the phone completely off and restarts every time.. i have tried updating busybox with no success.. anyone have any ideas on what this could be? I have done a full wipe x3 and a few rom installs and all do the same thing.. thanks in advance!

I'm actually getting the same thing. Not sure why but I tried with SuperSU and Superuser and it happened with both. I'm wondering if this is HTC's doing.....
Oh also, you might want to move this to the Evo forum because I only found this from Google and wouldn't have browsed this section of XDA for this issue.
Sent from my HTC Evo 4G LTE using Tapatalk

Morenicano said:
I'm actually getting the same thing. Not sure why but I tried with SuperSU and Superuser and it happened with both. I'm wondering if this is HTC's doing.....
Oh also, you might want to move this to the Evo forum because I only found this from Google and wouldn't have browsed this section of XDA for this issue.
Sent from my HTC Evo 4G LTE using Tapatalk
Click to expand...
Click to collapse
Yeah I know i posted wrong lol.. I also noticed that whatever you do in /system say edit the build.prop always resets at boot as if the file system is a read only.. also can you see if your Navigation crashed.. youd have to be in a car moving but mine crashes bad

Sure I can check. I also noticed that anytime Titanium Backup runs a batch backup job it causes the phone to restart almost immediately
I'm really surprised this isn't all over the place. We can't be the only ones having this issue....

Morenicano said:
Sure I can check. I also noticed that anytime Titanium Backup runs a batch backup job it causes the phone to restart almost immediately
I'm really surprised this isn't all over the place. We can't be the only ones having this issue....
Click to expand...
Click to collapse
Any update on this? same thing happening to me, installed CWM-SuperSU-v0.99 and still see the instant reboots..

Seek Alternatives
Give the MeanBean ROM by mikeyxda a try! Its great and reliable, worst case if you perform a hard reset flash MeanBean you can go back to your other ROM if you don't like it. At least will let you know if the issues lies in your existing ROM or not. You may even be able to perform a dirty flash back to your present ROM and that could retain the SuperSu from MeanBean.. Hope this helps.
If it did help feel free to hit my thanks button!!

I forgot to check but now when I do it, the phone doesn't restart--it now just says it failed to install the binaries. The phone is still rooted but I guess I can't use advanced features. I still think there's an issue in the /system directory because I can't get Titanium Backup to remove system apps (apps integrated into the ROM).
Sent from my Galaxy Note 10.1 using Tapatalk HD

Morenicano said:
I forgot to check but now when I do it, the phone doesn't restart--it now just says it failed to install the binaries. The phone is still rooted but I guess I can't use advanced features. I still think there's an issue in the /system directory because I can't get Titanium Backup to remove system apps (apps integrated into the ROM).
Sent from my Galaxy Note 10.1 using Tapatalk HD
Click to expand...
Click to collapse
I'm having the exact same issue...still trolling about to find a fix.

http://forum.xda-developers.com/showthread.php?t=2059281
Check here for the kernel fix for the /system issue, installed the new kernel and it works great!

[Q] Nexus 5 camera does not record video

My wife has Nexus 5 (it is completely stock and unrooted with unlocked bootloader) running running Android 4.4.2. Recently, the stock camera app stopped recording videos. Tapping the record button does not do anything while camera works perfectly in photo mode. I factory reset the phone but the problem persists. Any suggestions? Thanks in advance.

lock the bootloader and send it back

shahidhussain said:
My wife has Nexus 5 (it is completely stock and unrooted with unlocked bootloader) running running Android 4.4.2. Recently, the stock camera app stopped recording videos. Tapping the record button does not do anything while camera works perfectly in photo mode. I factory reset the phone but the problem persists. Any suggestions? Thanks in advance.
Click to expand...
Click to collapse
Try to clear data and cache from camera in settings.
If that doesnt work either and you really have done the factory reset, you have to send it to repair bc of an hardware deffect. :crying:

lichti1901 said:
Try to clear data and cache from camera in settings.
If that doesnt work either and you really have done the factory reset, you have to send it to repair bc of an hardware deffect. :crying:
Click to expand...
Click to collapse
I will try that but I think factory resetting clears cache, anyway. The phone camera worked fine previously but now suddenly it stopped.
Thanks anyway.

I have the same problem, when I change the camera app to record nothing happens when I press the red record button. I think the problem started when I upgraded to 4.4.2
Sent from my Nexus 5 using Tapatalk

shahidhussain said:
I will try that but I think factory resetting clears cache, anyway. The phone camera worked fine previously but now suddenly it stopped.
Thanks anyway.
Click to expand...
Click to collapse
And you flashed the right one? Hammerhead-4.4.2
Like i said before, if that doesnt help, you have to send it back to get a replacement.
You need to uncompress each download before use, which creates a new directory for that exact download. That directory contains a ./flash-all.sh script, which handles the various operations, installs the necessary bootloader, baseband firmware(s), and operating system. Note that this operation deletes all user data by default
Click to expand...
Click to collapse
Make yure that data gets wiped also! Dont forget to backup your sdcard bc it gets also wiped.

lichti1901 said:
And you flashed the right one? Hammerhead-4.4.2
Click to expand...
Click to collapse
I did not flash anything. The phone was OTA updated. Please note that the phone received OTA update and when I applied it, it completed its process but did not update (it was still on older android version) and this happened several times (I mentioned this on a separate thread here on XDA old post).

lichti1901 said:
And you flashed the right one? Hammerhead-4.4.2
Like i said before, if that doesnt help, you have to send it back to get a replacement.
Make yure that data gets wiped also! Dont forget to backup your sdcard bc it gets also wiped.
Click to expand...
Click to collapse
I downgraded Nexus 5 from Android 4.4.2 to 4.4 and now the camera is working fine. But I am afraid of updating it back to 4.4.2.

shahidhussain said:
I downgraded Nexus 5 from Android 4.4.2 to 4.4 and now the camera is working fine. But I am afraid of updating it back to 4.4.2.
Click to expand...
Click to collapse
Flash the whole 4.2.2 stock rom in fastboot bro, i have no issues with video recording both on Dalvik and Art runtime

lichti1901 said:
And you flashed the right one? Hammerhead-4.4.2
Like i said before, if that doesnt help, you have to send it back to get a replacement.
Make yure that data gets wiped also! Dont forget to backup your sdcard bc it gets also wiped.
Click to expand...
Click to collapse
gee2012 said:
Flash the whole 4.2.2 stock rom in fastboot bro, i have no issues with video recording both on Dalvik and Art runtime
Click to expand...
Click to collapse
Yes, I did it. Flashed the stock 4.4.2 and everything seems to work fine. However, when I tried updating using OTA after downgrading the update failed and stopped with "Error" message. After flashing 4.4.2 from scratch will hopefully allow smooth future OTA updates. Thanks everyone.

shahidhussain said:
Yes, I did it. Flashed the stock 4.4.2 and everything seems to work fine. However, when I tried updating using OTA after downgrading the update failed and stopped with "Error" message. After flashing 4.4.2 from scratch will hopefully allow smooth future OTA updates. Thanks everyone.
Click to expand...
Click to collapse
Glad you worked it out!
Good thing is - you got a Nexus, so its easy to flash all the stuff and go back to stock/factory image/recovery/...
:highfive:

Any update on this? I have this exact problem. No unlock, not root just pure OTA stock.
1. Video does not record. You press the red button and no timer comes up.
2. A VID_20140126_224910.mp4.tmp file is created 395.54 KB.
3. Time lapse works as do all the other camera functions.
4. The basic Google FAQ has generic instructions if an app does not work so I followed these.
5. in safe mode the camera works fine.
6. Power off and on again. The Video Camera then works fine and creates normal .mp4 files.
Things I have done that may affected the Camera in the first place;
1. Clear cache.
2. Put a .thumbnails file in DCIM to stop the gigantic .thumbnail folder being created.
3. Running nova launcher.
Unlikely these are a factor as I isolated them as an issue and rebooted but worth a mention just in case.
Camera works but have found the it subsequently stopped working again and had to repeat the Google FAQ steps to fix an app.

To answer my own question I found the uninstalling Said It_1.3.37.apk fixed the problem and just to prove it reinstalling brought the problem back.
---------- Post added at 06:01 PM ---------- Previous post was at 05:27 PM ----------
Quick update. the developer emailed me back. He co firmed it does the same on his device and will send an update.

Recovery buggy date/time

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:

Downgrade 5.0 to 4.4.4 and KEEP DATA

So I updated to 5.0 lollipop via ADB flash a couple days ago, and I realized that without xposed + root, I really cannot stand this phone... I need the simplicity that xposed gives me to make using my phone much easier.
So now, I want to downgrade back to 4.4.4 KitKat. Has anyone here tried? What I tried was downloading the 4.4.4 factory images, extracted it, and edited the flash-all.bat file and removed the "-w" command to save my data. It flashes fine, but then the phone is stuck in the boot animation and doesnt get past that.
Has anyone here successfully DOWNGRADED and KEPT THEIR DATA intact? Would appreciate it a lot!

blackdragon12 said:
So I updated to 5.0 lollipop via ADB flash a couple days ago, and I realized that without xposed + root, I really cannot stand this phone... I need the simplicity that xposed gives me to make using my phone much easier.
So now, I want to downgrade back to 4.4.4 KitKat. Has anyone here tried? What I tried was downloading the 4.4.4 factory images, extracted it, and edited the flash-all.bat file and removed the "-w" command to save my data. It flashes fine, but then the phone is stuck in the boot animation and doesnt get past that.
Has anyone here successfully DOWNGRADED and KEPT THEIR DATA intact? Would appreciate it a lot!
Click to expand...
Click to collapse
I personally haven't tried that. But 5.0 does have roottt and hopefully eventually xposed

blackdragon12 said:
So I updated to 5.0 lollipop via ADB flash a couple days ago, and I realized that without xposed + root, I really cannot stand this phone... I need the simplicity that xposed gives me to make using my phone much easier.
So now, I want to downgrade back to 4.4.4 KitKat. Has anyone here tried? What I tried was downloading the 4.4.4 factory images, extracted it, and edited the flash-all.bat file and removed the "-w" command to save my data. It flashes fine, but then the phone is stuck in the boot animation and doesnt get past that.
Has anyone here successfully DOWNGRADED and KEPT THEIR DATA intact? Would appreciate it a lot!
Click to expand...
Click to collapse
You would need to wipe cache and Dalvik for sure. System apps may need data wipes, too. Play by ear.

cgibbons51 said:
I personally haven't tried that. But 5.0 does have roottt and hopefully eventually xposed
Click to expand...
Click to collapse
yes. I did root it and it worked well. However, one of my company apps that I have to use on my phone detects my phone is rooted and won't open.... Xposed had a module (root cloak) to hide the fact that I had root for that app so it worked
Aerowinder said:
You would need to wipe cache and Dalvik for sure. System apps may need data wipes, too. Play by ear.
Click to expand...
Click to collapse
Are there any side effects to wiping cache and Dalvik? If I get stuck on a bootloop again would I have issue flashing 5.0 back if I wipe that?
Sent from my Nexus 5 using XDA Free mobile app

Just flash factory images. You'll be in for some hair pulling if you try to boot your saved data. Why do people try to do these crazy moves..

beekay201 said:
Just flash factory images. You'll be in for some hair pulling if you try to boot your saved data. Why do people try to do these crazy moves..
Click to expand...
Click to collapse
That isn't a solution to my problem. I know I can just wipe everything and flash the images again, but the point here is I want to save my data and apps and not have to setup my phone again (thus the topic title, I want to keep my data)
Sent from my Nexus 5 using XDA Free mobile app

Did you take a nandroid before flashing? You can use TiBU to extract the apps and data from that.

krs360 said:
Did you take a nandroid before flashing? You can use TiBU to extract the apps and data from that.
Click to expand...
Click to collapse
Biggest mistake, no I didnt
Worst case I am stuck with 5.0 lollipop until there is a version of Xposed for ART... or if I can figure out how to use the company app on a rooted device.

I sincerely doubt your phone settings for 5.0 will be compatible with 4.4.x
You will have to wipe. If you're rooted, you can at least restore user apps and data but the android settings, you'll have to do yourself.

blackdragon12 said:
Biggest mistake, no I didnt
Worst case I am stuck with 5.0 lollipop until there is a version of Xposed for ART... or if I can figure out how to use the company app on a rooted device.
Click to expand...
Click to collapse
Seeing as you can't use Xposed, what do you need root for?

rootSU said:
I sincerely doubt your phone settings for 5.0 will be compatible with 4.4.x
You will have to wipe. If you're rooted, you can at least restore user apps and data but the android settings, you'll have to do yourself.
Click to expand...
Click to collapse
I can easily root the device again. What do you mean if I am rooted in can restore user apps and data? How would I back those up and restore? Are you referring to using something like titanium backup?
Thanks.
Sent from my Nexus 5 using XDA Free mobile app

blackdragon12 said:
I can easily root the device again. What do you mean if I am rooted in can restore user apps and data? How would I back those up and restore? Are you referring to using something like titanium backup?
Thanks.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Yes. Not "like". Exactly that.

You can use Helium as well (which doesn't require root)

rootSU said:
Yes. Not "like". Exactly that.
Click to expand...
Click to collapse
Okay. Will look into it.
EddyOS said:
You can use Helium as well (which doesn't require root)
Click to expand...
Click to collapse
Thanks. Rooting isn't an issue so I don't mind titanium since it's more comprehensive I think.
I still want to see if there's an easier way to flash back...
Sent from my Nexus 5 using XDA Free mobile app

blackdragon12 said:
Okay. Will look into it.
Thanks. Rooting isn't an issue so I don't mind titanium since it's more comprehensive I think.
I still want to see if there's an easier way to flash back...
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
There's not. Wipe, flash factory images, restore apps + user data. That's your only option.

_MetalHead_ said:
There's not. Wipe, flash factory images, restore apps + user data. That's your only option.
Click to expand...
Click to collapse
Ah... guess ill do it at some point this week then..

_MetalHead_ said:
There's not. Wipe, flash factory images, restore apps + user data. That's your only option.
Click to expand...
Click to collapse
Just wanted to update everyone.
I used titanium backup to save all my apps+appdata and then flashed 4.4.4 via ADB. Then flashed TWRP and used CF-Auto-Root to root my phone.
Everything is right in my world of android again. 4.4.4, rooted, and no restrictions. Thanks all!

blackdragon12 said:
Just wanted to update everyone.
I used titanium backup to save all my apps+appdata and then flashed 4.4.4 via ADB. Then flashed TWRP and used CF-Auto-Root to root my phone.
Everything is right in my world of android again. 4.4.4, rooted, and no restrictions. Thanks all!
Click to expand...
Click to collapse
Any fix for the pesky OTA System Update notification?
I'm dying for 4.4.4 but cant stand that annoying update notification.
And I can't get rid of it without wakelocks.

Funny enough I haven't gotten the notification for Ota update yet... Maybe because I used cf auto root to root the phone and it modifies the kernel I think.
Sent from my Nexus 5 using XDA Free mobile app

justiiin said:
Any fix for the pesky OTA System Update notification?
I'm dying for 4.4.4 but cant stand that annoying update notification.
And I can't get rid of it without wakelocks.
Click to expand...
Click to collapse
I too am staying with kitkat. I disabled notification in "Google Play Services". Where do I go to see if I'm getting wakelocks?

Apps seem to be reset after cyanogenmod 13 update

I flashed cyanogenmod 13 and gapps for marshmallow (from 6.12.2015) and it boots fine. All apps are installed, as before the update.
BUT
When I start any of these apps they seem to be reset to default as if they are newly installed. For example Threema starts setup process after start.
App data is still present on internal storage (did not wipe), but apps do not seem to have access to any of this data.
Can anyone help what I can try to get the apps back to work with previous data?
Thankful for any help!
Greets
Daniel

At first, try flashing CM13 after a full wipe or try using another rom since CM13 could be buggy.

Primokorn said:
At first, try flashing CM13 after a full wipe or try using another rom since CM13 could be buggy.
Click to expand...
Click to collapse
Thanks for the reply! But well, the phone is working, just the apps are behaving as if they are newly installed ... So a full wipe would not really help as is only deletes more data. The question is why do the apps "think" they are not already set up?

d-trip said:
Thanks for the reply! But well, the phone is working, just the apps are behaving as if they are newly installed ... So a full wipe would not really help as is only deletes more data. The question is why do the apps "think" they are not already set up?
Click to expand...
Click to collapse
That's why we "always" backup user data before flashing a new rom

Primokorn said:
That's why we "always" backup user data before flashing a new rom
Click to expand...
Click to collapse
Full ACK, but data is still available on the internal storage, but the apps do not notice this?
AND this one here (not allowed ot post links... so a missing w at the beginning ww.cyanogenmod.org/blog/a-marshmallowy-cm) says dirty flash from 12.1 to 13 is okay and if the cyanogenmod updater shows cm13 as availabe for update ...
EDIT: Maybe this was a missing info, but it was "just" a normal update via cyanogenmod updater, not a real flash of a new rom!

d-trip said:
Full ACK, but data is still available on the internal storage, but the apps do not notice this?
AND this one here (not allowed ot post links... so a missing w at the beginning ww.cyanogenmod.org/blog/a-marshmallowy-cm) says dirty flash from 12.1 to 13 is okay and if the cyanogenmod updater shows cm13 as availabe for update ...
EDIT: Maybe this was a missing info, but it was "just" a normal update via cyanogenmod updater, not a real flash of a new rom!
Click to expand...
Click to collapse
What do you want me to say? It's always better to full wipe when upgrading to a new Android version. Period.
Moreover, CM13 nightlies are buggy. There are important bugs and fixes everyday. Make a nandroid backup and try from scratch or try another nightly or another custom rom. There's nothing else to say IMO.

Primokorn said:
What do you want me to say? It's always better to full wipe when upgrading to a new Android version. Period.
Moreover, CM13 nightlies are buggy. There are important bugs and fixes everyday. Make a nandroid backup and try from scratch or try another nightly or another custom rom. There's nothing else to say IMO.
Click to expand...
Click to collapse
Just thought it could be possibly just a permission problem, a missing symlink or anything else that could be fixed manually.

d-trip said:
Just thought it could be possibly just a permission problem, a missing symlink or anything else that could be fixed manually.
Click to expand...
Click to collapse
I flashed the first CM13 nighly and I didn't have to do anything to get working apps. Everything has been restored without any issue.