Related
why my camera sometimes can't be used and there is a notification "Camera Failed".?
please help me...
I had this issue too..just reboot your phone and everything will works normaly again..
i hv this issue alsi when i'm using lower class memory card. now using class 10 16gb card with bionic rom without this camera failed problem.
Sent from my GT-I8150 using XDA
rinopermana said:
I had this issue too..just reboot your phone and everything will works normaly again..
Click to expand...
Click to collapse
i have reboot my phone, but that problem happen again for a next time.
please help me...
shade2112 said:
i have reboot my phone, but that problem happen again for a next time.
please help me...
Click to expand...
Click to collapse
Try to flash a new Camera.apk to you phone. Hopefully that is only software problem.
yewsiong said:
Try to flash a new Camera.apk to you phone. Hopefully that is only software problem.
Click to expand...
Click to collapse
how to flash a new Camera.apk ?
I really don't know.
I had the same problem and I solved it by uninstalling oovoo....it's only a case???
shade2112 said:
i have reboot my phone, but that problem happen again for a next time.
please help me...
Click to expand...
Click to collapse
do u have cwm on ur phone? reboot ur phone into recovery then choose advance and choose fix permission, wait until finish, then reboot ur phone after it finish
Unfortunately I have the same problem. My camera does not work anymore. I just receive the message "Camera failed". I still have the stock rom installed and I did not modify too much (I just installed some apps). I have already reset the phone to factory settings which did not solve my problem. Does anybody have an idea what I could try to fix the problem?
Please help...
I just have formatted my device and flashed it with a stock rom. Unfortunately it did not solve my problem with the camera. I still got the error message "camera failed" when I click on the camera app. Any ideas? Is it a hardware problem? Should I flash a custom rom?
I got that message once, and I panicked. Fortunately, rebooting did it just fine.
Perhaps there is something wrong with the firmware...I searched the net and found this article, maybe useful, IDK.
Thanks for the reply and for the link. Unfortunately I do not understand step 3. When I scroll to "Camera" I do not see a 2nd option which should be named as "user". I just see "camera" and "camcorder". What should I do? Do I have to root the phone?
ok, I have rooted my phone and I have tried the fix described in the link above again. However, I was not successfull. I do not get these options described in the link ("user"). Maybe I am using a wrong version of Pro Launcher. I just downloaded the new version from market...Anyone with a suggestion/idea?
Camera failed
I used to face this problem quite a lot when i was using the stock rom, but after flashing to cow's rom, the problem went away, no more camera failed anymore
Yesterday after upgrade to baseband v. i8150dxlc1 Kernel [email protected]#3 (KIES UPGRADE) i dont have that problem anymore
Hi,
I am fairly new to rooting (infact this is my first post).So,please be gentle if i am violating any rules.
I had put JELLY BAM on my GNEX and it was running fine. I tried partitioning my memory which did not go well so then I tried reflashing my ROM , which again did not go well and accidentally i deleted my ROM and all of my backups. So basically I am not able to use my GNEX .
I have no ROM and was only able to access bootloader and recovery menu (TWRP) . So i tried flashing it thru NRT(by wugsfresh) and since then I am stuck in bootloop(Was trying to flash stock JDQ39) & upon that I am back to stock recovery of android. Also, now PC is not ready to detect my GNEX as ADB device.
Please help me out, I am in dire need of it. Cant find a simillar issue any where else.
Thanks in advance.
follow this: http://forum.xda-developers.com/showthread.php?t=1626895
work in progress
Zepius said:
follow this: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
Thanks for the prompt reply. Halfway thru ..
Zepius said:
follow this: http://forum.xda-developers.com/showthread.php?t=1626895
Click to expand...
Click to collapse
Nopes, still stuck in bootloop. Tried the tutorial twice now.
Also, earlier i was following the same procedure albeit from NRT.
Please suggest what is wrong with my phone and a possible solution
madforsoccer said:
Nopes, still stuck in bootloop. Tried the tutorial twice now.
Also, earlier i was following the same procedure albeit from NRT.
Please suggest what is wrong with my phone and a possible solution
Click to expand...
Click to collapse
put simply you probably trashed your partitions. you might have to use ODIN to repartition
madforsoccer said:
Nopes, still stuck in bootloop. Tried the tutorial twice now.
Also, earlier i was following the same procedure albeit from NRT.
Please suggest what is wrong with my phone and a possible solution
Click to expand...
Click to collapse
I had a similar problem. I thought it was because my disk was partitioned-screwed. So I tried this: http://forum.xda-developers.com/showthread.php?t=2065470
It didn't work for me, but it's worth a shot for you. Give it a go.
Will try the ODIN method.
Also, do you think I am experiencing persistent boot-looping because I wiped off my 'system' (did it for the first time)
coz i have been flashing ROM's and kernels on weekly basis now and this has never happened before.
Still not working, tried the ODIN part also, still stuck in boot-loop.
I jus want to know what exactly is the problem here..!!
getting frustrated now.
Hi all,
Since I am facing difficulties flashing ROM. IF only someone can share a backup image of ROM (CWM/TWRP) with me I can get it restored and flash another ROM later on as need be.
You said you partitioned your memory. What exactly do you mean by this, what did you do?
cupfulloflol said:
You said you partitioned your memory. What exactly do you mean by this, what did you do?
Click to expand...
Click to collapse
I was trying to implement swapper on my gnex , which when failed led to this mess i am in currently.
Hey guys,
I´m quite new in this area. I rooted my phone a couple of days ago, and today an update for HTC something came up. I updated right away, muscle reflex, and not thinking about that it was rooted. Right after the update was finished downloading and installing, it required a reboot to finalize the installation. Rebooted, and started to use the phone again. After about 15-20 seconds (I can do whatever I want in this time), it starts to reboot again and again and again. No idea idea why, but I guess it could be the update that is trying to finish.
I guess I can do a factory reset to remove the update, but is there anything else I can do?
edit: Since so many people are experiencing the same problem, I'll post the solution here and AnDruid's reply which explains the process.
"I solved it by clicking the Supersu app, which then asked me what kind of recovery i used. I didn´t have time to read through it all, so don't know what it specifically said, but I chose TWRP and it had to reboot and start installing some kind of script (God I feel like a noob saying some kind).
Booted up again, no restarts."
AnDruid - "The SuperSu app asked about recovery and the option to chose was TWRP/CWM (I am on TWRP). SuperSu itself seemed to reboot the phone and invoked the "OpenrRcoveryScript" installs the "update.zip" (which I am not sure but could be the HTC Update file? Or it could be something related to supersu itself)."
This thing happened to my Moto G couple of months back,
the rebooting is happening mainly due to root. before taking OTA you need to remove the root completely.
try to delete the super su or chainfire in that 20 sec interval.
I don't think deleting Supersu will stop ota.You can choose survive mode in supersu which will allow you to take ota and you will have root access.As long as you don't change/modify system you will be able to take ota.
I don't think he got an OTA, a software update was released recently that is installed directly within Android, but still requires s reboot.
No idea about the question though...
Cheers for the answers guys.
I solved it by clicking the Supersu app, which then asked me what kind of recovery i used. I didn´t have time to read through it all, so no what it specifically said, but I chose TWRP and it had to reboot and start installing some kind of script (God I feel like a noob saying some kind).
Booted up again, no restarts.
Thanks again!
orphe0 said:
Cheers for the answers guys.
I solved it by clicking the Supersu app, which then asked me what kind of recovery i used. I didn´t have time to read through it all, so no what it specifically said, but I chose TWRP and it had to reboot and start installing some kind of script (God I feel like a noob saying some kind).
Booted up again, no restarts.
Thanks again!
Click to expand...
Click to collapse
I was in the same boat as you, phone out of order for the whole morning today. I followed the same steps as you and phone is stable after the reboot (Thanks!).
In case someone wants to dig deeper, the SuperSu app asked about recovery and the option to chose was TWRP/CWM (I am on TWRP). SuperSu itself seemed to reboot the phone and invoked the "OpenrRcoveryScript" installs the "update.zip" (which I am not sure but could be the HTC Update file? Or it could be something related to supersu itself).
AnDruid said:
I was in the same boat as you, phone out of order for the whole morning today. I followed the same steps as you and phone is stable after the reboot (Thanks!).
In case someone wants to dig deeper, the SuperSu app asked about recovery and the option to chose was TWRP/CWM (I am on TWRP). SuperSu itself seemed to reboot the phone and invoked the "OpenrRcoveryScript" installs the "update.zip" (which I am not sure but could be the HTC Update file? Or it could be something related to supersu itself).
Click to expand...
Click to collapse
Yeah that's exactly it! Glad I could help with my vaguely described solution Could someone briefly describe what the update.zip file updates?
orphe0 said:
Cheers for the answers guys.
I solved it by clicking the Supersu app, which then asked me what kind of recovery i used. I didn´t have time to read through it all, so no what it specifically said, but I chose TWRP and it had to reboot and start installing some kind of script (God I feel like a noob saying some kind).
Booted up again, no restarts.
Thanks again!
Click to expand...
Click to collapse
You're a life saver! Here I was thinking I messed it all up, and would need to do a factory reset
orphe0 said:
Cheers for the answers guys.
I solved it by clicking the Supersu app, which then asked me what kind of recovery i used. I didn´t have time to read through it all, so no what it specifically said, but I chose TWRP and it had to reboot and start installing some kind of script (God I feel like a noob saying some kind).
Booted up again, no restarts.
Thanks again!
Click to expand...
Click to collapse
This worked for me! Was just about to do a full restore, so this saved me a bunch of time
orphe0 said:
Cheers for the answers guys.
I solved it by clicking the Supersu app, which then asked me what kind of recovery i used. I didn´t have time to read through it all, so no what it specifically said, but I chose TWRP and it had to reboot and start installing some kind of script (God I feel like a noob saying some kind).
Booted up again, no restarts.
Thanks again!
Click to expand...
Click to collapse
Thank you so much for sharing this. Made my day!
I'm glad I read this post. Thank you!
orphe0 said:
cheers for the answers guys.
I solved it by clicking the supersu app, which then asked me what kind of recovery i used. I didn´t have time to read through it all, so no what it specifically said, but i chose twrp and it had to reboot and start installing some kind of script (god i feel like a noob saying some kind).
Booted up again, no restarts.
Thanks again!
Click to expand...
Click to collapse
you da man bro
This was a lifesaver. My phone was doing the exact same thing, and I was really worried I had messed something up badly.
Is there a way to avoid the message you get when you reboot after unlocking the Bootloader? The black screen where you can wait 5 seconds or tap the power to go on...
I understand that is correct to show it...but it's boring and I'm already aware of it.
http://forum.xda-developers.com/nextbit-robin/general/guide-install-twrp-root-robin-t3334171/page7
maybe try and follow the instruction on post number 69
Thanks for the reply but that's for Moto X. Actually before Robin I was using a Moto X and I know that procedure, point is that on Moto X was just a screenshot before booting and nothing else, here looks a bit different and you can also skip it pressing the power button. Plus I would avoid to flash/use the logo.bin of Moto X...
Can anyone of Nextbit team provide any info? Thanks !
I also don´t like the screen... the opportunity to hide would be great.
here's the same, maybe someone can make a xposed module?
kcl0801 said:
here's the same, maybe someone can make a xposed module?
Click to expand...
Click to collapse
Hi, firmware/bootloader guy here - work for a Android vendor so I decided to have a quick look at the bootloader for you guys..
It's stored in the bootloader (aboot) if you are interested so you can't make a xposed module, it runs before Android (before init or zygote) does (or the Linux kernel). I haven't checked if Secure boot is on (if not, I suppose I could build a replacement aboot and just patched out the logic for that screen ) but I hope it's on for security reasons.
uberlaggydarwin said:
Hi, firmware/bootloader guy here - work for a Android vendor so I decided to have a quick look at the bootloader for you guys..
It's stored in the bootloader (aboot) if you are interested so you can't make a xposed module, it runs before Android (before init or zygote) does (or the Linux kernel). I haven't checked if Secure boot is on (if not, I suppose I could build a replacement aboot and just patched out the logic for that screen ) but I hope it's on for security reasons.
Click to expand...
Click to collapse
got it, in that case i will keep this message, but just hope it can pass faster, it says 5 secs but i feel it's about 30s to skip it...
kcl0801 said:
got it, in that case i will keep this message, but just hope it can pass faster, it says 5 secs but i feel it's about 30s to skip it...
Click to expand...
Click to collapse
Hey everyone, our team is looking into that nag screen. One of our devs pointed it out, so we're trying to see what we can do. :good:
any luck on the nag screen yet? maybe gone in the july update? =D lol
I get this message Everytime, any ideas? Help would be great
Akoolive said:
I get this message Everytime, any ideas? Help would be great
Click to expand...
Click to collapse
Make sure that the recovery.img is in the same folder as your adb/fastboot files. Let me know if that works!
makbomb said:
Make sure that the recovery.img is in the same folder as your adb/fastboot files. Let me know if that works!
Click to expand...
Click to collapse
Thanks that worked
Akoolive said:
I get this message Everytime, any ideas? Help would be great
Click to expand...
Click to collapse
Replace "recovery.img" at the end with the actual twrp filename and it should work.
I'd love to get rid of that error message on my new Robin, but I'm confused about whether or not the previous two posts were a solution to the problem. I had flashed TWRP after unlocking the bootloader, and the recovery was in the same folder as the ADB and Fastboot files, but I'm not sure what that has to do with removing the error message.
Thanks in advance!
Saaber said:
I'd love to get rid of that error message on my new Robin, but I'm confused about whether or not the previous two posts were a solution to the problem. I had flashed TWRP after unlocking the bootloader, and the recovery was in the same folder as the ADB and Fastboot files, but I'm not sure what that has to do with removing the error message.
Thanks in advance!
Click to expand...
Click to collapse
The last several message in this thread regarding 'recovery.img' was for someone trying to flash TWRP in fastboot, it has nothing to do with the 5-second nag screen.
Since khang never responded, I'm assuming this won't change and the nag screen will remain. I'm so used to keeping my finger on the power button when i reboot that it's almost habit now, so really doesn't bother me too much.
How can a device that is marketed for its unlockable bootloader and warranty coverage have an jnlockable bootloader experience that is worse than basically all devices. You don't see unlocked Sony or LG phones having boot screens that require user input. The only device I know of that is worse is the Pixel c, which has a 30 second "integrity check" if the bootloader is unlocked.
Nextbit_Khang said:
Hey everyone, our team is looking into that nag screen. One of our devs pointed it out, so we're trying to see what we can do. :good:
Click to expand...
Click to collapse
IS this going to change? really annoyed by it
..It's only 5 seconds, the only reason it seems longer is the fact that the message merges in with the boot logo
Nextbit_Khang said:
Hey everyone, our team is looking into that nag screen. One of our devs pointed it out, so we're trying to see what we can do. :good:
Click to expand...
Click to collapse
Very old thread here, but could you guys maybe release an optional "developer/enthusiast" bootloader update that gets rid of that nag screen? Or at least give the option to confirm the warning in future updates, like "I have read and understood this warning. Don't show again."
I am posting hoping some progress may or may not have been made on this. Its atrocious.
Hello,
Does anyone know how to decrypt the OnePlus 3 yet? I used Garak's latest recovery image.
I tried rooting my OnePlus 3 that arrived in the mail today. To root, I had to OEM unlock the phone. I followed this guide : http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733. I got to the rooting part of the guide, but I was dumb and formatted 'userdata', since the phone started bootlooping. Now I'm in a situation where adb sideload won't upload the ROM 100% (Oxygen OS 3.1.3 found here: http://forum.xda-developers.com/oneplus-3/how-to/stock-firmare-oxygenos-3-1-3-oneplus-t3400384) (always fails at ~50%), TWRP unable to mount storage due to encryption, and no installed operating system. Even worse, I didn't save a backup.
Could anybody help me out? Thanks!
PROBLEM SOLVED!
Loose wires = bad
Appending the command "fastboot format userdata" again fixed the encryption issue and granted me access to my device's storage, which allowed me to fix my other problems.
kentexcitebot said:
PROBLEM SOLVED!
Loose wires = bad
Appending the command "fastboot format userdata" again fixed the encryption issue and granted me access to my device's storage, which allowed me to fix my other problems.
Click to expand...
Click to collapse
Hi, you used format instead of erase?
mirko8054 said:
Hi, you used format instead of erase?
Click to expand...
Click to collapse
Yes. Use the format command.
Next time, create a new thread instead of responding to an old post.
Red "unable to mount storage" line in TWRP boot sequence
kentexcitebot said:
Yes. Use the format command.
Next time, create a new thread instead of responding to an old post.
Click to expand...
Click to collapse
Hi,
I'm posting here since I couldn't really find any thread related for the OP3.
I happen to have this red "unable to mount storage" line during my twrp booting sequence, right after inputting my PIN or password. Even though after that I'm able to get to TWRP and back to my system with everything "apparently" working fine.
I've joined a pic of the sequence, and would like to know if this IS a problem and/or anything to solve it.
Thanx in advance.
FlyingMachete said:
Hi,
I'm posting here since I couldn't really find any thread related for the OP3.
I happen to have this red "unable to mount storage" line during my twrp booting sequence, right after inputting my PIN or password. Even though after that I'm able to get to TWRP and back to my system with everything "apparently" working fine.
I've joined a pic of the sequence, and would like to know if this IS a problem and/or anything to solve it.
Thanx in advance.
Click to expand...
Click to collapse
If decrypt was successfull it shouldn't ask you to enter pin, you could try to repeat process and flash twrp again.
mirko8054 said:
If decrypt was successfull it shouldn't ask you to enter pin, you could try to repeat process and flash twrp again.
Click to expand...
Click to collapse
Thanx for your reply, though it's asking for my security pin cause I have one for entering the system like you would have a scheme or password. It doesn't ask it if I take it off in the OS. And like you can see on the screenshot, decryption is still happening after that and is succesful. I've already gone through updates of twrp by the past but always had this "line" as far as I remember. Still can't figure out what that is.
FSociety 4 Life
FlyingMachete said:
Hi,
I'm posting here since I couldn't really find any thread related for the OP3.
I happen to have this red "unable to mount storage" line during my twrp booting sequence, right after inputting my PIN or password. Even though after that I'm able to get to TWRP and back to my system with everything "apparently" working fine.
I've joined a pic of the sequence, and would like to know if this IS a problem and/or anything to solve it.
Thanx in advance.
Click to expand...
Click to collapse
Its perfectly normal. Its happening like this
1-twrp tries to mount partitions but storage is encrypted
2-then it asks for password
3-then twrp decrypts it
4- boom its done and decrypted partitions are mounted
Dupleshwar said:
Its perfectly normal. Its happening like this
1-twrp tries to mount partitions but storage is encrypted
2-then it asks for password
3-then twrp decrypts it
4- boom its done and decrypted partitions are mounted
Click to expand...
Click to collapse
That's how I was seeing it, Thanx a lot for your reply!
FSociety 4 Life
FlyingMachete said:
That's how I was seeing it, Thanx a lot for your reply!
FSociety 4 Life
Click to expand...
Click to collapse
How long does it really take to decrypt new phone without any apps? Just to have an idea. When I started TWRP it asked for password and I used the PIN assigned to login to screen ... now going on for 5 minutes now. Following on the screen:
Mount
Try Decryption
Updating partition details...
....done
Unable to mount storage
Full SELinux support present
----------------------------------------------------- blue animation
junostik said:
How long does it really take to decrypt new phone without any apps? Just to have an idea. Mine is going on for 5 minutes now. Following on the screen:
Mount
Try Decryption
Updating partition details...
....done
Unable to mount storage
Full SELinux support present
----------------------------------------------------- blue animation
Click to expand...
Click to collapse
It takes just a few seconds for me.
FlyingMachete said:
It takes just a few seconds for me.
Click to expand...
Click to collapse
Should I reboot? I am worried it might cause an issue, please advise.
junostik said:
Should I reboot? I am worried it might cause an issue, please advise.
Click to expand...
Click to collapse
Force reboot it. Then First you should look for the very last modified TWRP that came out 2-3 days ago. Called 3.0.2-0 v11 Blu spark. Only if you're already using f2fs partition. As it's now fully compatible with nougat and f2fs. You can flash it via fastboot or if you can still access your system, via flashify.
FlyingMachete said:
Force reboot it. Then First you should look for the very last modified TWRP that came out 2-3 days ago. Called 3.0.2-0 v11 Blu spark. Only if you're already using f2fs partition. As it's now fully compatible with nougat and f2fs. You can flash it via fastboot or if you can still access your system, via flashify.
Click to expand...
Click to collapse
Thank you, any idea where can I download TWRP 3.0.2-0 v11 Blu spark for 3T? sorry, not able to find any where.
junostik said:
Thank you, any idea where can I download TWRP 3.0.2-0 v11 Blu spark for 3T? sorry, not able to find any where.
Click to expand...
Click to collapse
I'm not on 3T but almost sure i saw something about it on the 3T forums. Search there if not look for the Blu spark team threads or repositories on github. You can also search the posts by developer @eng.stk here on XDA.
junostik said:
Thank you, any idea where can I download TWRP 3.0.2-0 v11 Blu spark for 3T? sorry, not able to find any where.
Click to expand...
Click to collapse
latest modified TWRP by eng.stk here https://forum.xda-developers.com/devdb/project/dl/?id=22429
Sent from my ONEPLUS A3000 using XDA-Developers Legacy app
Flashed this one and I still can't decrypt my storage in recovery. Any other ideas that are working?
Dr. MadMan said:
Flashed this one and I still can't decrypt my storage in recovery. Any other ideas that are working?
Click to expand...
Click to collapse
Hello, can you please confirm if your storage is ext4 or f2fs?
it's ext4
Dr. MadMan said:
it's ext4
Click to expand...
Click to collapse
Then you are is same boat as many of us. No twrp recovery has support for nougat on ext4 file system. Eng stk has made a compatible recovery with f2fs file system. The only workaround I have found is to use that recovery with no password/pin for system. It will work flawlessly then. I anyways need twrp rarely so it's no hassle for me.