Related
Hello xda folks,
I have no sound whatsoever on my cyanogen N5, version 11-20140726-NIGHTLY. No sound preview during chosing ringtones, no alarm sound, no spotify, google music, apollo crashes seconds after trying to play local stored tracks. Weirdly enough only Pocket Casts and calling work fine.
Any solution to this? custom kernel? apps tweaking? anything?
removed pocket casts - no effect
factory reset - no effect
flashing same rom again - no effect
tehWev said:
Hello xda folks,
I have no sound whatsoever on my cyanogen N5, version 11-20140726-NIGHTLY. No sound preview during chosing ringtones, no alarm sound, no spotify, google music, apollo crashes seconds after trying to play local stored tracks. Weirdly enough only Pocket Casts and calling work fine.
Any solution to this? custom kernel? apps tweaking? anything?
removed pocket casts - no effect
factory reset - no effect
flashing same rom again - no effect
Click to expand...
Click to collapse
Try a CAF based kernel (or switch to another rom/nightly)
Primokorn said:
Try a CAF based kernel (or switch to another rom/nightly)
Click to expand...
Click to collapse
I'll try to do that, what are the benefits of switching to different kernel?
Dump CM.
Aerowinder said:
Dump CM.
Click to expand...
Click to collapse
wow thanks that is super helpful - and why would I do that and where should I go?
tehWev said:
wow thanks that is super helpful - and why would I do that and where should I go?
Click to expand...
Click to collapse
Try ElementalX (cm version) or Chaos or any other CAF based kernel.
Install UKM (Universal Kernel Manager) to tweak your kernel settings. You will understand the differences with custom kernels
Primokorn said:
Try ElementalX (cm version) or Chaos or any other CAF based kernel.
Install UKM (Universal Kernel Manager) to tweak your kernel settings. You will understand the differences with custom kernels
Click to expand...
Click to collapse
Thanks man, I'll look for it right away. Any advice for flashing visual glitches in cwm recovery?
tehWev said:
Thanks man, I'll look for it right away. Any advice for flashing visual glitches in cwm recovery?
Click to expand...
Click to collapse
I always used TWRP... But why do u want to flash glitches???
Primokorn said:
I always used TWRP... But why do u want to flash glitches???
Click to expand...
Click to collapse
not "flashing" glitches like "loading" them - its the glitches that are flashing on the screen - some kind of caleidoscopic pixelized ****. Maybe this could be bug in the kernel?
Same here. Just got my Nexus back from LG. Was on 7-5-2014 nightly which worked fine. Now stock works just fine, but neither the M8 stable or 8-01 nightly have sound. Mic doesnt seem to work either.
kenney001 said:
Same here. Just got my Nexus back from LG. Was on 7-5-2014 nightly which worked fine. Now stock works just fine, but neither the M8 stable or 8-01 nightly have sound. Mic doesnt seem to work either.
Click to expand...
Click to collapse
hey thanks fot the heads up mate, my N5 is hard bricked now but will probably coma back to pure stock if the service will manage to revive it
mokee is good
tehWev said:
Hello xda folks,
I have no sound whatsoever on my cyanogen N5, version 11-20140726-NIGHTLY. No sound preview during chosing ringtones, no alarm sound, no spotify, google music, apollo crashes seconds after trying to play local stored tracks. Weirdly enough only Pocket Casts and calling work fine.
Any solution to this? custom kernel? apps tweaking? anything?
removed pocket casts - no effect
factory reset - no effect
flashing same rom again - no effect
Click to expand...
Click to collapse
mokee OS is good , its from china .
The 26th nightly had a sound bug. flash a newer one and it´ll be fixed. But sadly cm has many other bugs and hard lags while playing even the slightest demanding games like hill climb racing. I would recommend something else than cm at the time :cyclops::good:
Hard brick help?
om22 said:
The 26th nightly had a sound bug. flash a newer one and it´ll be fixed. But sadly cm has many other bugs and hard lags while playing even the slightest demanding games like hill climb racing. I would recommend something else than cm at the time :cyclops::good:
Click to expand...
Click to collapse
okay guys now I do have a hard bricked device - I managed to get into the secondary bootloader and recovery (freezes phone permanently sometimes) - adb and fastboot does not detect my device so I cannot flash stock puch any kernel or whatever. How should I proceed to repair my device?
tehWev said:
okay guys now I do have a hard bricked device - I managed to get into the secondary bootloader and recovery (freezes phone permanently sometimes) - adb and fastboot does not detect my device so I cannot flash stock puch any kernel or whatever. How should I proceed to repair my device?
Click to expand...
Click to collapse
Wow how did you do that? Fastboot really doesn't work? Even no undetected device in device manager on windows?
Does the fastboot mode work at all?
kernel
om22 said:
Wow how did you do that? Fastboot really doesn't work? Even no undetected device in device manager on windows?
Does the fastboot mode work at all?
Click to expand...
Click to collapse
I tried to flash hells core kernel - it perma ****ed my device, just today looked up on the net that I'm not alone in this - hells core app is known for downloading and flashing wrong kernel - mine was either uncertified or was for nexus 4 - so yeah, second bootloader, no idea how to push proper linux 3.4.0 (?) kernel. no fastboot response no adb response - just <waiting for the device>
tehWev said:
I tried to flash hells core kernel - it perma ****ed my device, just today looked up on the net that I'm not alone in this - hells core app is known for downloading and flashing wrong kernel - mine was either uncertified or was for nexus 4 - so yeah, second bootloader, no idea how to push proper linux 3.4.0 (?) kernel. no fastboot response no adb response - just <waiting for the device>
Click to expand...
Click to collapse
Oh wow that app should be fixed. try that: http://forum.xda-developers.com/google-nexus-5/general/bootloader-bootloader-nexus-5-t2746343 does only work on linux sadly...
looked up this guy but no idea how to use this knowledge
http://forum.xda-developers.com/google-nexus-5/general/bootloader-bootloader-nexus-5-t2746343
n5 partition table
http://forum.xda-developers.com/google-nexus-5/general/info-partition-list-nexus-5-t2517503
http://www.bloglovin.com/viewer?pos...me_type=a&blog=5233323&frame=1&click=0&user=0
any ideas?
tehWev said:
looked up this guy but no idea how to use this knowledge
http://forum.xda-developers.com/google-nexus-5/general/bootloader-bootloader-nexus-5-t2746343
n5 partition table
http://forum.xda-developers.com/google-nexus-5/general/info-partition-list-nexus-5-t2517503
http://www.bloglovin.com/viewer?pos...me_type=a&blog=5233323&frame=1&click=0&user=0
any ideas?
Click to expand...
Click to collapse
You need a linux PC. A live DVD/USB stick would be enough. Then open terminal and type those 2 commands while you are in the second bootloader:
Code:
su
dd if="/dev/block/mmcblk0p11" of="/dev/block/mmcblk0p6"
Parted Magic
om22 said:
You need a linux PC. A live DVD/USB stick would be enough. Then open terminal and type those 2 commands while you are in the second bootloader:
Code:
su
dd if="/dev/block/mmcblk0p11" of="/dev/block/mmcblk0p6"
Click to expand...
Click to collapse
I've used parted magic multiple times before - its linux based if I recall - can I run these commands there?
So with the Sony binaries and Marshmallow sources released, I figured it was worth trying a build.
I don't have my Z3C on me so no idea how well it'll work but here you go. Roasted Marshmallow, hot off the build server
EDIT: Title is probably wrong, as pointed out by a mod. I based it on the Git ref being "6.0_r1", which I thought meant "6.0.1". This is really 6.0. Specifically, a build based on the exact instructions posted by Sony.
MOD EDIT by @gregbradley
I edited the title for you .
Flashed on a 5803 on T-Mobile USA and it isn't seeing the SIM card. Also, when it unlocks, it gets hung up for a few seconds.
thatguy222 said:
Flashed on a 5803 on T-Mobile USA and it isn't seeing the SIM card. Also, when it unlocks, it gets hung up for a few seconds.
Click to expand...
Click to collapse
dmesg suggests that this may be due to lack of modem.mdt. I'll look into it.
EDIT: From what I can see this looks like a proprietary Sony file that they haven't released. It may also be built with the kernel but that I can't say. Either way I opened a bug on Github that they can hopefully address.
Okay great
---------- Post added at 02:29 AM ---------- Previous post was at 02:15 AM ----------
Gairtial said:
dmesg suggests that this may be due to lack of modem.mdt. I'll look into it.
EDIT: From what I can see this looks like a proprietary Sony file that they haven't released. It may also be built with the kernel but that I can't say. Either way I opened a bug on Github that they can hopefully address.
Click to expand...
Click to collapse
Bummer. Thanks for nothing, Sony!
thatguy222 said:
Okay great
---------- Post added at 02:29 AM ---------- Previous post was at 02:15 AM ----------
Bummer. Thanks for nothing, Sony!
Click to expand...
Click to collapse
Don't jump the gun. There are a lot of files in a standard Android build and I don't know if it comes from them or if it's a product of the build process. It could just be a misconfiguration on my part. The bug is for info, not because it's their fault.
http://forum.xda-developers.com/xperia-z-ultra/orig-development/rom-marshmallow-6-0-z-ultra-t3224321
They seem to have fixed the modem by using the files from the current firmwares.
Just refreshing the page for a build with working modem as i don't have the environment neither the skill to build from scratch
aniket_ said:
http://forum.xda-developers.com/xperia-z-ultra/orig-development/rom-marshmallow-6-0-z-ultra-t3224321
They seem to have fixed the modem by using the files from the current firmwares.
Click to expand...
Click to collapse
I tried that last night using one of the files from the various vendor repos but no luck. The kernel module threw errors about the data being invalid. I'll try extracting from official firmware when I get home. Also that thread doesn't yet have anyone confirming that it works :/
fratzika said:
Just refreshing the page for a build with working modem as i don't have the environment neither the skill to build from scratch
Click to expand...
Click to collapse
I don't have my Z3C with me so I'm unlikely to be able to do anything helpful for ~9h, when I get home. You'll have to be a little patient
Okay, got a build up to date with Git and with a modem copied from one of the latest firmwares (ripped it from the SLIM stock ROM). Wouldn't get your hopes up but it might work
EDIT: No luck. It doesn't seem there's an available modem that's likely to work. Unless someone can suggest another device with close enough hardware and a working Marshmallow modem (seems doubtful), we're lost until someone can extract one from a legitimate Sony firmware or Sony releases it to us (seems unlikely).
Thanks for doing this Gairtail, let's hope you get it up and running soon (if Sony or someone else uploads the modem file..)
Jerpelea says modem is now working on shinano, using the new kernel blobs.
(Just forwarding information I've been told that you might find useful.)
http://www.xperiablog.net/2015/10/2...lable/?utm_source=dlvr.it&utm_medium=facebook refer here to get that modem from the ftf that sony relased for both z3 and z3c !
someone755 said:
Jerpelea says modem is now working on shinano, using the new kernel blobs.
(Just forwarding information I've been told that you might find useful.)
Click to expand...
Click to collapse
Theliakos said:
http://www.xperiablog.net/2015/10/2...lable/?utm_source=dlvr.it&utm_medium=facebook refer here to get that modem from the ftf that sony relased for both z3 and z3c !
Click to expand...
Click to collapse
Thanks. I tried to do a compile today but there were some issues in the repo that broke it (qcom media stuff). I'll try in another day or two and hopefully things will have settled down.
Since you're talking about the modem parts, and i seem to have a problem with my WiFi, is anybody in here able to provide the /persist and /modem folder from the stock MM rom? Mine seems to have been lost after flashing an alternative rom
Gairtial said:
Thanks. I tried to do a compile today but there were some issues in the repo that broke it (qcom media stuff). I'll try in another day or two and hopefully things will have settled down.
Click to expand...
Click to collapse
I built on Novenber 5th, worked just fine. Just synced and started another build, but the November security update isn't here yet, bummer. (I reckon another 24 hours should do it.)
If you'd like, I can upload the build for you.
Apo14 said:
Since you're talking about the modem parts, and i seem to have a problem with my WiFi, is anybody in here able to provide the /persist and /modem folder from the stock MM rom? Mine seems to have been lost after flashing an alternative rom
Click to expand...
Click to collapse
I don't know for sure, but wouldn't flashing a stock FTF solve this?
Overall, I'm starting to like AOSP. Camera now works on every boot (unlike Nougat, because of the memory allocation gone bad), though AF and AE are a bit off, and it's stable enough to use as a daily driver.
Also, not sure if you guys also get this, but I've been getting the dwc3-msm wakelock a lot. Happens because of kernel bug that keeps phone awake, thinking it's connected to a power source even after it's been disconnected. Drained my battery for 17 hours before I even noticed. I don't know if the official method with prebuilt kernels also has this, but I build the upstream sonyxperiadev/kernel repo myself. If you use a kernel source too, instead of using the prebuilt kernels, you could try picking this. Looks to be working for me, but it hasn't been merged yet, so take that as you will.
EDIT: Noticed this isn't upstream Marshmallow, but r1. Bummer.
You should really switch to 6.0.1, the 1.3.3 kernel is much better than 1.2.2 (and without the memalloc reboots caused by media/video). Though if you prefer not to switch, you could still add my uploads to the OP alongside yours if you want? That way we have 6.0 and 6.0.1 under one roof?
@someone755 so should i be able to extract those files without the need to flash?
Apo14 said:
@someone755 so should i be able to extract those files without the need to flash?
Click to expand...
Click to collapse
No reason to avoid flashing, really. Make a backup of system and boot, don't wipe userdata, and have a recovery image handy. Flash FTF, flash recovery, restore system and boot.
The only things that get updated are your modem and bootloader etc, your system and data stay untouched.
Though depending on when you last flashed an FTF, it may be a good idea to wipe your data in recovery before you flash (and back it up, of course). Some firmware can only be updated after Android has booted, like NFC for example.
So best would be to completely start from scratch and wipe everything i guess? Do you have any links to guides for FTF etc? Im not that into these things :/
Apo14 said:
So best would be to completely start from scratch and wipe everything i guess? Do you have any links to guides for FTF etc? Im not that into these things :/
Click to expand...
Click to collapse
I'm not saying it's best, but it could help you avoid potential issues. I don't know what all you've been doing with your device, so I can't make the call for you. Just telling you how it is.
This is a nice thread: http://forum.xda-developers.com/z3-compact/general/list-stock-firmwares-d5803-d5833-t2906706 You'll also need FlashTool if you go down this route, you can Google it to download.
EDIT: @Gairtial I have today's 6.0.1 source in a nice zip. https://www.androidfilehost.com/?w=files&flid=127723
There's also a folder with the kernels for 6.0.1/7.0/7.1 that I'll try to keep up to date, if there's any interest for that. (The kernel zip will flash to any of the three Android versions, so long as the ROM is AOSP-based. Other than that, it's version-independent.)
Another note would be that I didn't make any changes to the ROM build. GApps will have issues starting unless you do some adb wizardry, and you'll get your recovery overwritten with the useless AOSP one if you flash the ROM zip in recovery. (You could also just try flashing system and boot through fastboot, though I haven't tried.)
someone755 said:
Overall, I'm starting to like AOSP. Camera now works on every boot (unlike Nougat, because of the memory allocation gone bad), though AF and AE are a bit off, and it's stable enough to use as a daily driver.
Click to expand...
Click to collapse
I'm tired of using stock Sony roms, and I'm starting to hate them. Still waiting for those latest camera blobs though for AOSP. I've tried your uploaded build, but it's causing a bootloop somehow. Didn't flash the separate kernel, but I don't see the need for that since there is one included in rom zip. Not sure what is the problem...
I am not able to understand these white/blue spots across the images. Please see the attached images and zoom in to look in the highlighted areas. It's not dust for sure as I have cleaned the lens and the photos were shot in auto mode (no change in ISO etc). IS there an issue with Nougat beta camera or is my sensor damaged?:crying:
What variant you have (L09 or L04) and which firmware you're running (B1..)?!
I am sorry for hijacking this forum, but I have an Honor V8 variant (the big sized version) with EMUI 5.0. beta. There is no xda forum on this model, hence I posted here. I am not sure if the s/w is the issue as I tried it with other camera apps as well producing the same issue
try a 3rd party camera to see if it is still there, if so try reflash stock rom.
If 3rd party apps don't work, then look if there's an update for your phone
I am on latest nougat beta (b355) for V8. I dont think its a camera issue as other camera apps give the same result. Before I reflash the stock rom, I need to know if this could be a hardware/sensor issue?
linom said:
I am on latest nougat beta (b355) for V8. I dont think its a camera issue as other camera apps give the same result. Before I reflash the stock rom, I need to know if this could be a hardware/sensor issue?
Click to expand...
Click to collapse
yes it is probably a hardware issue, but you will have to flash stock to completely rule out a software issue. back up data using twrp
linom said:
I am on latest nougat beta (b355) for V8. I dont think its a camera issue as other camera apps give the same result. Before I reflash the stock rom, I need to know if this could be a hardware/sensor issue?
Click to expand...
Click to collapse
Its a 50 50 situation, some early buyers of honor 8 had the same issue, but after an OTA it's gone.
If it's a hardware issue, return it back if you have warranty.
A friend of mine had the same issue but it was fixed after the update.
Neil6684 said:
A friend of mine had the same issue but it was fixed after the update.
Click to expand...
Click to collapse
Do you mean those spots on zooming in? I have been through 2 beta-Nougat updates, but its not yet resolved. I will factory reset over this weekend and check.
linom said:
I am on latest nougat beta (b355) for V8. I dont think its a camera issue as other camera apps give the same result. Before I reflash the stock rom, I need to know if this could be a hardware/sensor issue?
Click to expand...
Click to collapse
Did you experience this problem when you were using the original version of android that came preinstalled on your device? If you did then it's probably a hardware problem. Which can only be fixed by the manufacturer.
Ok, before I factory reset, I just realized that RAW format is completely fine. However the same jpegs are showing these dead pixels (or bright spots). Is this something s/w related or hardware? Are the raw images processed by s/w or sensor & s/w?
linom said:
Ok, before I factory reset, I just realized that RAW format is completely fine. However the same jpegs are showing these dead pixels (or bright spots). Is this something s/w related or hardware? Are the raw images processed by s/w or sensor & s/w?
Click to expand...
Click to collapse
It's a software issue, don't worry.
If RAW images are fines, then it's just a problem of processing when taking a JPEG photo
An update should fix this
DarkGuyver said:
Did you experience this problem when you were using the original version of android that came preinstalled on your device? If you did then it's probably a hardware problem. Which can only be fixed by the manufacturer.
Click to expand...
Click to collapse
Some images rendered perfect while images taken in bright light show these spots/pixels. I did check my initial pics and most of them turn out to be fine. Also, as I mentioned in my later post, the Raw formats are good, but their jpegs are with these spots.
@CronaMell, thanks. I will still reset and update here. It will be an expensive affair to send this device back to China from India. It's better I sell it off here.
linom said:
Some images rendered perfect while images taken in bright light show these spots/pixels. I did check my initial pics and most of them turn out to be fine. Also, as I mentioned in my later post, the Raw formats are good, but their jpegs are with these spots.
@CronaMell, thanks. I will still reset and update here. It will be an expensive affair to send this device back to China from India. It's better I sell it off here.
Click to expand...
Click to collapse
It's better for you, and when you buy a device make sure it's officially supported in your country (like honor 8) .
All the best
linom said:
Some images rendered perfect while images taken in bright light show these spots/pixels. I did check my initial pics and most of them turn out to be fine. Also, as I mentioned in my later post, the Raw formats are good, but their jpegs are with these spots.
@CronaMell, thanks. I will still reset and update here. It will be an expensive affair to send this device back to China from India. It's better I sell it off here.
Click to expand...
Click to collapse
I'd contact Honor directly and ask them about the problem. Maybe they will release a software patch for it. But I have never heard the Honor 8 had this problem.
I just did a factory reset. The issue persists. Is there a way I could downgrade to EMUI 4.1 rom? I am on Nougat beta and that could be still an issue which I need to exclude. Factory reset keeps the same version of the ROM, I need to downgrade to EMUI 4.1 (Marshmallow) and check.
Also, I suspect the raw images are not processed correctly. Is there a way to change any library associated with image processing? I am able to process raw files on my computer without any issues. I am not rooted, but willing to take that step if it solves this issue.
linom said:
Also, I suspect the raw images are not processed correctly. Is there a way to change any library associated with image processing? I am able to process raw files on my computer without any issues. I am not rooted, but willing to take that step if it solves this issue.
Click to expand...
Click to collapse
Unfortunately, we don't know the exact files (libs that are responsible for image processing)
linom said:
I just did a factory reset. The issue persists. Is there a way I could downgrade to EMUI 4.1 rom? I am on Nougat beta and that could be still an issue which I need to exclude. Factory reset keeps the same version of the ROM, I need to downgrade to EMUI 4.1 (Marshmallow) and check.
Click to expand...
Click to collapse
You would have to contact Honor directly for instructions on how to restore Marshmallow back onto your device. They will also be able to provide you with a link to the Marshmallow firmware for your device.
Hi.
Today appeared fw CLT-L29C432B131.
I have updated with hurupdater method.
So far they have included camera improvements.
The zoom button is places at lower screen part, they changed the circle into square.
More impressions After testing.
CLT-L29C432B131 Camera
Screenshot
Well, that's definitely new!
tamaskurti said:
Hi.
Today appeared fw CLT-L29C432B131.
I have updated with hurupdater method.
So far they have included camera improvements.
The zoom button is places át lower screen part, they changed the circld into square.
More impressions After testing.
CLT-L29C432B131 Camera
Click to expand...
Click to collapse
Thanks as you know you might be the First one with the NEW rom 131 so we all need your thoughts especialy about camera, daylight photos oversharpines....Most of users saying that daylight photos are good but most of the times HDR makes them unnatural with oversharpines effect with AI on or off....
What do you think about that after update???
Whats the changelog given? I already have 131 on my india model out of the box...want to compare the changelog with mine
halleyrokz said:
Whats the changelog given? I already have 131 on my india model out of the box...want to compare the changelog with mine
Click to expand...
Click to collapse
From FirmwareFinder:
This update optimizes system performance and stability.
Optimizes power consumption for longer usage.
Improves system performance and stability for smoother operations.
Optimizes the wallpaper display for a better experience.
Fixes an issue where the other party's voice was occasionally delayed when answering calls while using OK Google.
1. This update will not erase your personal data, but we recommend that you back up any important data before updating.
2. The system will restart after the update. This will take about 5 minutes.
3. If you experience any issues during the update, please call the Huawei customer service hotline or visit an authorized Huawei service center for assistance.
tsiglas said:
Thanks as you know you might be the First one with the NEW rom 131 so we all need your thoughts especialy about camera, daylight photos oversharpines....Most of users saying that daylight photos are good but most of the times HDR makes them unnatural with oversharpines effect with AI on or off....
What do you think about that after update???
Click to expand...
Click to collapse
OK. Sure.
But it will take time.
I'm not a professional shooter, so basically I probably won't notice the differences too fast.
One thing I have observed is that the portrait selfie mode was improved, it's more natural.
Others I will test.
But again: with HuRupdater you can update easely.
(downloading 3 of 4 files from update packages: the choice is between clt-l09 and clt-l29, after that renaming and flash via twrp. See corresponding thread)
Interesting.. so it seems indeed that many of the under the hood changes are not always mentioned in the change log.
Yeah please keep us posted on the camera improvements and performance and power consumption.
tamaskurti said:
Hi.
Today appeared fw CLT-L29C432B131.
I have updated with hurupdater method.
So far they have included camera improvements.
The zoom button is places at lower screen part, they changed the circle into square.
More impressions After testing.
CLT-L29C432B131 Camera
Screenshot
Click to expand...
Click to collapse
I updated it to it yesterday but besides the zoom button form nothing changed the selfie camera still creey as before and the video recording also no stabilisation for 4k and no 60 f0s for 4k, huawei is doing nothing
tamaskurti said:
So far they have included camera improvements.
Click to expand...
Click to collapse
How about the front-camera, can you turn off beauty mode? i set it to 0 but still on almost the same.
I've just tried to update using the HuRUpdater method but wasn't able to boot afterwards. Tried flashing twice but it just wouldn't boot to system. I've restored the TWRP backup I made before flashing and got back into system, now settings says I'm on .131 but I can't be if I just restored a .128 backup, right?
What's everyone's update method? Did you place custom recovery in the folder too or flash without? Wipe cache/dalvik after? Boot to system first before flashing Magisk or just flash directly after HuRUpdater script?
Want to try again but just wanted to check if I've missed something? Thanks!
just flashed with hurupdater, no problems at all, had to reflash twrp and magisk though... i guess the real improvement are the june security patches
kaiowas82 said:
just flashed with hurupdater, no problems at all, had to reflash twrp and magisk though... i guess the real improvement are the june security patches
Click to expand...
Click to collapse
Reckon it would be safe to flash using the NoCheck Recovery method?
danifilth4king said:
Reckon it would be safe to flash using the NoCheck Recovery method?
Click to expand...
Click to collapse
i don't know mate, i used hurupdater, as i said before, and all went smooth...
kaiowas82 said:
i don't know mate, i used hurupdater, as i said before, and all went smooth...
Click to expand...
Click to collapse
Did you use official or unofficial TWRP?
You need to use unofficial twrp as only that one can decrypt storage (remove security settings first: no pin/ fingerprint).
danifilth4king said:
Did you use official or unofficial TWRP?
Click to expand...
Click to collapse
unofficial
kaiowas82 said:
unofficial
Click to expand...
Click to collapse
Tried re-downloading the firmware and flashing again without including TWRP in the flashing process and still got bootloop! I just can't figure out why it's not working. I'm tempted to try to update using NoCheck Recovery but that's how I bricked last time, so I'm apprehensive :/
danifilth4king said:
Tried re-downloading the firmware and flashing again without including TWRP in the flashing process and still got bootloop! I just can't figure out why it's not working. I'm tempted to try to update using NoCheck Recovery but that's how I bricked last time, so I'm apprehensive :/
Click to expand...
Click to collapse
I created a new folder with inside the hurupdater script and the three zips downloaded from firmware finder, no recovery img or else.
flashed the script, wiped cache and dalvik and rebooted straight to system.
rebooted to fastboot to reflash the praetoriano recovery, reboot to recovery to flash magisk and that's it.
I'm afraid i cannot help further
I see here P20 Pro users get new update 131, but just with FunkyHuawei and TWRP manual. No one gets updated from OTA. And if you looking the Huawei offical (in China) forum, they still didnt release new updates. So is this a beta updated from FunkyHuawei or how did they get it?
isko01 said:
I see here P20 Pro users get new update 131, but just with FunkyHuawei and TWRP manual. No one gets updated from OTA. And if you looking the Huawei offical (in China) forum, they still didnt release new updates. So is this a beta updated from FunkyHuawei or how did they get it?
Click to expand...
Click to collapse
The cn firmware was updated too to version B123.
Remember, they have different numbers. Ex. Their B123 version is newer than our B131.
Look at production numbers in Fw.
I just flashed Resurrection Remix ROM and then my wifi doesn't turn on and when I watch youtube videos no sound will come out from the speakers. Please help.
Mine doesn't work too. Tried Evolution X (10), Lineage (11), Nitrogen (11), Pixel Experience (10). Tried also flashing the original persist.img, none of them makes wifi work.
Hey guys, I found the solution to those of you who still haven't fixed it. You should be flashing a vendor image/Xiaomi Miui rom and then flashing the custom rom on top of it and everything should work from there. The instructions are somewhat unclear as wiping data on my end completely wiped the original vendor image/rom. Once you do that you should be golden.
The process to my understanding is
install vendor/miui rom
install custom rom
format data
and you should be fine
https://sourceforge.net/projects/nitrogen-project/files/surya/10.0/firmware+vendor/
If I'm too vague, please reply and I'll try clarifying it to the best of my ability.
ZenovajXD said:
install vendor/miui rom
install custom rom
format data
and you should be fine
https://sourceforge.net/projects/nitrogen-project/files/surya/10.0/firmware+vendor/
If I'm too vague, please reply and I'll try clarifying it to the best of my ability.
Click to expand...
Click to collapse
Unfortunately flashing NOS fw is sometimes not enough, at least for me I needed to flash whole xiaomi.eu rom and then it worked for me with steps you posted... After you flash xiaomi.eu rom you will have working wifi...
i try Lineage-OS 18 with your process and it worked
thanks
After researching and researchig and RESEARCHINNG, I have (I think) found the solution. I also do have this problem and I did not solve even until now (maybe tomorrow?). So here is my Story:
I flashed Lineage OS 14 by Dev. Andi on my Samsung Galaxy Tab 2 P5110. The custom ROM does work although sound and youtube videos don't. I downloaded build.prop editor from the PlayStore. I looked at it and it seems the audio has less properties than before. So I was like, "Let me try another ROM, it might work". Tried Oni ROM (something like that) and its faster than the Lineage OS ROM but can't play youtube videos and no AUDIO AGAIN! So I researched for about 5 hrs? Then so I concluded that I need to install the stock ROM of my device to basically regain all the audio and media properties on my device. I hope this helps and might work for me as well. Also, don't forget to backup your previous ROM so that if its fixed, try restoring it in Recovery Mode. That's all & thanks!
SoIomon said:
After researching and researchig and RESEARCHINNG, I have (I think) found the solution. I also do have this problem and I did not solve even until now (maybe tomorrow?). So here is my Story:
I flashed Lineage OS 14 by Dev. Andi on my Samsung Galaxy Tab 2 P5110. The custom ROM does work although sound and youtube videos don't. I downloaded build.prop editor from the PlayStore. I looked at it and it seems the audio has less properties than before. So I was like, "Let me try another ROM, it might work". Tried Oni ROM (something like that) and its faster than the Lineage OS ROM but can't play youtube videos and no AUDIO AGAIN! So I researched for about 5 hrs? Then so I concluded that I need to install the stock ROM of my device to basically regain all the audio and media properties on my device. I hope this helps and might work for me as well. Also, don't forget to backup your previous ROM so that if its fixed, try restoring it in Recovery Mode. That's all & thanks!
Click to expand...
Click to collapse
Wrong forum
its the same method as the Xiaomi phones
SoIomon said:
its the same method as the Xiaomi phones
Click to expand...
Click to collapse
Not really. People having problems with WiFi or audio on their X3 are using the wrong Vendor. Flashing the correct Vendor fixes the problem
Noter2017 said:
Not really. People having problems with WiFi or audio on their X3 are using the wrong Vendor. Flashing the correct Vendor fixes the problem
Click to expand...
Click to collapse
isn't that the point? I will go back to Stock ROM to retrieve all the properties I lost when I installed a Custom ROM.
not sure, but thats what works for me.
SoIomon said:
isn't that the point? I will go back to Stock ROM to retrieve all the properties I lost when I installed a Custom ROM.
Click to expand...
Click to collapse
I use a custom ROM and everything works. The opening post of each custom ROM actually tells you which firmware/vendor the ROM needs and when you use it, WiFi and audio and everything else will work.
it works now with what I did.