Hi everybody,
I'm back with a new problem in my Honor 8 (FRD-L04)... I was one of the user who installed the faulty version 15.0 of the Magisk update, so as you can imagine my phone went into bootloop and had to go all over from a backup I did the past September. I was running the firmware version B385, and because I lost many important things for no backing up lately, I decided I would just update to the firmware version B389. My phone was rooted, so I had to flash a stock recovery and do a full package download for the update. Everything went smooth and the update worked well. I had to do a full wipe because after the update the bootloader locked and I unlocked it to root the phone once again. This happened 2 days ago, and today I tried to use the camera and this is were everything started going down. The camera simply doesn't load, if I clear the data and cache of the app and reopen the app, it shows the initial screen where you need to swipe it to start using the camera but after that it goes in some kind of opening closing loop, until finally it closes. When I try to open it again, it stays in a black screen until it closes. I have restarted the phone and cleared the dalvik/cache in TWRP but the problem persists. I don't know if this is important, but after starting the camera app and failing launching it, the flashlight stops working too. If i restart the phone, and start the flashlight it works well. I have been thinking in reinstalling the camera app, but I can't find the apk for it.
Hope somebody can help me with this small issue, so thanks in advanced
Rommco05 said:
Try to downgrade to an older version
Click to expand...
Click to collapse
Thanks for replying Rommco05... You mean to downgrade to the B385 update? or rollback to B381?
I have found the update.zip file for the B389 upgrade here http://gsmtube.com/android-tips-tri...89-android-7-0-nougat-update-europe-9747.html but the links appear to be broken..
Rommco05, can you help me how to downgrade? I'm a noob at this and your help would be greatly appreciated! thanks
Related
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.
I got a Nexus 5 been using CM on it for a while now. Currently i have 11-20140708-SNAPSHOT-M8
the build date is july 8. I've been getting CM update for a new version for like a month now, tried installing it a couple of times, when i press to reboot and install it says it installed it, and after the phone reboots, it's still the same old version, and i keep getting the notification to upgrade, but i can't.
So I waited for another new build, thinking this is just some bug in the update. Yesterday a new version prompted for a update, but the same happened. So i tried to download the zip from CM website and flash it on recovery manually. And i got an error:
Can't install this package on top of incompatible data. (Status 7) installation aborted.
I used to update with no problems, but I seem to be stuck on the july 8 build.
Anyone else dealing with this, or know how to fix this?
Is your bootoader up-to-date? CM often require you to have latest bootloader
No. I haven't upgraded it. I've found multiple threats about it, I'm not sure which one is the right to do so. As i'm not really familiar with this kind of stuff.
EDIT: My BL version is HHZ11K. From what i gathered it's the most recent one.
TheSidiO said:
Can't install this package on top of incompatible data. (Status 7) installation aborted.
Click to expand...
Click to collapse
Sounds like you're dirty flashing but something in your current set up has been corrupted. You may need to factory reset or do a clean install.
Wakamatsu said:
Sounds like you're dirty flashing but something in your current set up has been corrupted. You may need to factory reset or do a clean install.
Click to expand...
Click to collapse
Was thinking if I can salve the problem without doing that. But i did a factory reset and it fixed the problem.
Thanks for the responses.
problems updating monthly snapshots of CM
Hi, I have been looking everywhere to see why I am having difficulties updating Cyanogen snapshots every month. I found this post but I don't really know if it pertains to my problem. I have a google rooted nexus 5 and every month when I try to update my phone begins acting up. It starts saying unfortunately google play services has stopped working. I see my apps trying to install but all I get are error notification icons at the top and they won't download. I posted on g+ and someone says it has to do with titanium. Im at a loss. Its very frustrating as I've tried almost everything I can think of to no avail. I try to go to the playstore and it's like I have no connection. I do have and use titanium backup for the apps I want to restore. I spoke to someone that has the same phone and he tells me to just flash the update without wiping but it doesn't work for me. I don't know if its a setting I'm missing on titanium or what it is but it sucks. With the 2 last updates this has happened. Leaving me with no option but to download the CM snapshot along with gapps. Wipe my phone and flash both the snapshot and gapps and start from scratch. I hope you can help me. Hopefully I'm in the right place. Tx you
acf150 said:
Hi, I have been looking everywhere to see why I am having difficulties updating Cyanogen snapshots every month. I found this post but I don't really know if it pertains to my problem. I have a google rooted nexus 5 and every month when I try to update my phone begins acting up. It starts saying unfortunately google play services has stopped working. I see my apps trying to install but all I get are error notification icons at the top and they won't download. I posted on g+ and someone says it has to do with titanium. Im at a loss. Its very frustrating as I've tried almost everything I can think of to no avail. I try to go to the playstore and it's like I have no connection. I do have and use titanium backup for the apps I want to restore. I spoke to someone that has the same phone and he tells me to just flash the update without wiping but it doesn't work for me. I don't know if its a setting I'm missing on titanium or what it is but it sucks. With the 2 last updates this has happened. Leaving me with no option but to download the CM snapshot along with gapps. Wipe my phone and flash both the snapshot and gapps and start from scratch. I hope you can help me. Hopefully I'm in the right place. Tx you
Click to expand...
Click to collapse
So here is what i would try to do. reboot into recovery. do a factory reset, make sure you backup your files as this cleans them. And then make the update from the updater or download it manually from cm website.
updating CM snapshot monthly problems
TheSidiO said:
So here is what i would try to do. reboot into recovery. do a factory reset, make sure you backup your files as this cleans them. And then make the update from the updater or download it manually from cm website.
Click to expand...
Click to collapse
Almost what I did, i l always do a nandroid backup before flashing anything in recovery, I downloaded the snapshot and the gapps, wiped, and installed snapshots along with gapps. So your telling me to just do a backup in recovery before updating that it cleans my files, then without wiping to try to update just the CM update from either my phone or their website? No gapps? Will try next time thanks.
I got this update a few days ago on my rooted Tmobile G2. Applying the update bricked my phone, as it was stuck in a recovery boot loop. Had to use this:
http://forums.androidcentral.com/ge...ricked-lg-g2-stuck-twrp-no-download-mode.html
to get it unstuck. Also, I tried the LG Support Tool to pull the update, but it was trying to download a 1.7gig update. I cancelled it before the install process in the fear that it would bork my phone.
Has anyone gotten the update to install successfully on their phone? (rooted)
I got the update but didn't run it. I learned my lesson last time. I'd love to know what it brings and how to install it though.
Sent from my LG-D801 using XDA Free mobile app
sidog said:
I got this update a few days ago on my rooted Tmobile G2. Applying the update bricked my phone, as it was stuck in a recovery boot loop. Had to use this:
http://forums.androidcentral.com/ge...ricked-lg-g2-stuck-twrp-no-download-mode.html
to get it unstuck. Also, I tried the LG Support Tool to pull the update, but it was trying to download a 1.7gig update. I cancelled it before the install process in the fear that it would bork my phone.
Has anyone gotten the update to install successfully on their phone? (rooted)
Click to expand...
Click to collapse
I'm there but can't figure out how to type in terminal command, can you help me out with this? I'm stuck in the recovery boot loop.
*EDIT* nevermind I figured it out after a factory reset though UGH!
I also got the update notification. I deleted 213MB upgrade file in cashe. It was in the root of cashe folder not in /cashe/foa/. I still get the stupid upgrade notification. How can we kill it? I have Titanium backup but software MUC is not an option on our phones.
OK found how to turn it off. Long press the update, App Info pops up, uncheck show notifications. Clear cashe and then reboot.
You can use stomproot (brute force method) to root this OTA. towelroot won't work. Before applying OTA, make sure custom recovery is replaced with stock recovery. Otherwise you will end up in boot loop.
sam298 said:
You can use stomproot (brute force method) to root this OTA. towelroot won't work. Before applying OTA, make sure custom recovery is replaced with stock recovery. Otherwise you will end up in boot loop.
Click to expand...
Click to collapse
Can confirm this works...thanks...autorec still works as well
If I have not installed a custom recovery, but just rooted the phone with AutoRec, will it soft brick my phone? Since I don't have TWRP or CWM, I would have no way to enter adb shell. So, it sounds like if I soft brick it, I'd have to restore factory settings to get it to boot, right? Are there any significant improvements to the 20g versus the 20e? Thanks.
I got this this morning and installed it...no issues whatsoever. Not sure what its for, but I got it.
Im stock unrooted.
I ended up going with the LG support tool method and installed the update (1.7gigs)...not really sure what the changed though. Root was lost, but I used Stump Root to get it back and everything is normal again. If anyone has the list of changes, plz post
tpaxadpom said:
I also got the update notification. I deleted 213MB upgrade file in cashe. It was in the root of cashe folder not in /cashe/foa/. I still get the stupid upgrade notification. How can we kill it? I have Titanium backup but software MUC is not an option on our phones.
OK found how to turn it off. Long press the update, App Info pops up, uncheck show notifications. Clear cashe and then reboot.
Click to expand...
Click to collapse
Where exactly do I "long press the update? I deleted the update file from cache but can't find this App Info popup menu. Is it within the file explorer or the settings menu?
Sent from my LG-D801 using XDA Free mobile app
As long as you deleted the update you can safely press the install button...it may or may not actually power off...but if it doesn't just reboot after pressing and the notification will be gone...also to prevent it from downloading in the future you can dial 3845#*80X# and click wlan test then ota setting and click disable...you can re-enable by going through the same process and pressing enable...works for most variants
Mine tried to update: it rebooted, said it was installing while showing a progress bar and then it stopped and restarted. Nothing changed.
Does anyone know what this update is? Preliminary to the lollipop update?
Any idea why my nearly stock system didn't take the update. I am rooted with towel root and several apps disabled and frozen with Titanium.
Thanks
Gilon
you press and hold on the update in the notification bar and app info will popup.
nolig2278 said:
Mine tried to update: it rebooted, said it was installing while showing a progress bar and then it stopped and restarted. Nothing changed.
Does anyone know what this update is? Preliminary to the lollipop update?
Any idea why my nearly stock system didn't take the update. I am rooted with towel root and several apps disabled and frozen with Titanium.
Thanks
Gilon
Click to expand...
Click to collapse
Same here, just rooted, no custom recovery and went through the update process. Completed update, still on e not upgraded to g
Plugged into LG Mobile Support Tool and updated that way, ran STUMPROOT and bruteforced. Rebooted and had root ^_^ Updated SuperSU binaries and rebooted once more and ran AutoRec. Now time to update everything again and remove the bloat they put back on.
Also to find the dialer code to update touch software, knock on isn't working. :silly:
---------- Post added at 10:00 AM ---------- Previous post was at 09:59 AM ----------
nolig2278 said:
Mine tried to update: it rebooted, said it was installing while showing a progress bar and then it stopped and restarted. Nothing changed.
Does anyone know what this update is? Preliminary to the lollipop update?
Any idea why my nearly stock system didn't take the update. I am rooted with towel root and several apps disabled and frozen with Titanium.
Thanks
Gilon
Click to expand...
Click to collapse
From what I saw on androidpolice it includes in-flight wifi stuff and some patches. Probably blocking some of the older rooting methods
Took the update last night, i was rooted with stock recovery but it went through just fine. Now when i try to root via StumpRoot it says my device is rooted before i even do anything. I don't have root access though.
Anyone else experience this problem? I've already tried a factory reset but still no-go.
this "update" seems absolutely useless. however, it could be nice to get a flashable radio from it.
mannequin said:
this "update" seems absolutely useless. however, it could be nice to get a flashable radio from it.
Click to expand...
Click to collapse
No change in radio...still same version
FIX
snowlin said:
Took the update last night, i was rooted with stock recovery but it went through just fine. Now when i try to root via StumpRoot it says my device is rooted before i even do anything. I don't have root access though.
Anyone else experience this problem? I've already tried a factory reset but still no-go.
Click to expand...
Click to collapse
I had the same issues and figured it out!
http://forum.xda-developers.com/lg-g2/help/fix-trouble-putting-download-mode-t2979318
when i am trying to do that its says ( NO UPGRADE ITEMS TO FIX ) any idea guys.............
I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?
I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine
Jst flash a newer modem in recovery
mugoftee said:
I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?
Click to expand...
Click to collapse
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.
PivotMasterNM said:
I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine
Click to expand...
Click to collapse
That won't help, flashing an older build than what was previously installed without wiping properly will cause problems.
KURDKiNG said:
Jst flash a newer modem in recovery
Click to expand...
Click to collapse
Modem has nothing to do with this.
Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine
KURDKiNG said:
Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine
Click to expand...
Click to collapse
Most likely pure coincidence.
Thanks your reply!
Heisenberg said:
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.
Click to expand...
Click to collapse
Actually this is what I did in the very first beginning but I encountered the same rebooting symptoms like after the OTA update. Since it didn't seem to change anything I didn't mention it. I used cm-12.1-YOG4PAS1N0-bacon-signed.
Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.
mugoftee said:
Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.
Click to expand...
Click to collapse
I don't think you have any other option unfortunately.
Anyone else met with this issue with the latest beta? I keep getting this error, none of my SIMs work and trying to go into settings-SIM&Network crashes settings.
I used to have Google dialer framework (Magisk) and Google Phone installed, removed them but the problem persists... Cleared Phone's data, set the OP phone as default app, nothing works - I can't receive or make calls, and the OP dialer just gives me a black screen.
Any ideas?
Can I go back to OB3 without wiping everything?
[EDIT] ahhh local upgrade won't let me downgrade...
krakout said:
Anyone else met with this issue with the latest beta? I keep getting this error, none of my SIMs work and trying to go into settings-SIM&Network crashes settings.
I used to have Google dialer framework (Magisk) and Google Phone installed, removed them but the problem persists... Cleared Phone's data, set the OP phone as default app, nothing works - I can't receive or make calls, and the OP dialer just gives me a black screen.
Any ideas?
Can I go back to OB3 without wiping everything?
[EDIT] ahhh local upgrade won't let me downgrade...
Click to expand...
Click to collapse
I'm on latest beta 4 using a IN2025 OP8Pro. I used the full ROM not the incremental update to upgrade from OB3. I am rooted also. No issues you are experiencing. Sounds like you need to flash the full ROM from fastboot mode and complete wipe for a clean install and start from there.
./
Thanks for the input. How big is the partial update? Because the one I flashed was almost 3GB...
So, no real way to downgrade to OB3 again?
3gb is full ROM not the incremental update.
So that's not the explanation then... I wonder if factory resetting will fix the problem?
Any ideas anyone?