I tried Euphoria ROM and came back to stock by flashing the 04-05 all.zip and the latest patch.... Note surprisingly the rotation is reversed!! I rebooted but no change... Can anyone give me a solution for this??... I'm on stock ROM and kernel.
vinay235 said:
I tried Euphoria ROM and came back to stock by flashing the 04-05 all.zip and the latest patch.... Note surprisingly the rotation is reversed!! I rebooted but no change... Can anyone give me a solution for this??... I'm on stock ROM and kernel.
Click to expand...
Click to collapse
Factory reset maybe....
Tried that too....wiped everything and installed stock ROM but problem persists.
The problem began after I tried some xposed modules but after wiping everything it shudve gone right??
vinay235 said:
Tried that too....wiped everything and installed stock ROM but problem persists.
The problem began after I tried some xposed modules but after wiping everything it shudve gone right??
Click to expand...
Click to collapse
Yes, a reset "should've" fixed everything but now its sounding like you have hardware problem.
Anyway to confirm that??
just go to build.prop with text editor or something and change the value for hwrotation. it's probably upside down. haha
Is it in /system/ folder? And I didn't find the hwrotation value itself.. Could u please guide me?
vinay235 said:
Is it in /system/ folder? And I didn't find the hwrotation value itself.. Could u please guide me?
Click to expand...
Click to collapse
yea, you'll need root explorer, go to system and open build.prop with text editor, find hwrotation and change the value (if the value is 0, change it to 180 and vice versa if the value is 180) and save, reboot.
Hakim Farouk said:
yea, you'll need root explorer, go to system and open build.prop with text editor, find hwrotation and change the value (if the value is 0, change it to 180 and vice versa if the value is 180) and save, reboot.
Click to expand...
Click to collapse
Got it Hakim but didn't find hwrotation value so added a ro.sf.hwrotation in the build prop and tried all values but no change....and my problem mainly is wen I turn 90 to the left the screen reverses..just so that my problem is clear...shud I give any other property to that?
vinay235 said:
Got it Hakim but didn't find hwrotation value so added a ro.sf.hwrotation in the build prop and tried all values but no change....and my problem mainly is wen I turn 90 to the left the screen reverses..just so that my problem is clear...shud I give any other property to that?
Click to expand...
Click to collapse
you seem to have a calibration problem with your gyro. i've never tried this method but it's worth the shot i think. https://forums.oneplus.net/threads/rotation-sensor-calibration.358538/
Hakim Farouk said:
you seem to have a calibration problem with your gyro. i've never tried this method but it's worth the shot i think. https://forums.oneplus.net/threads/rotation-sensor-calibration.358538/
Click to expand...
Click to collapse
This is what I got from dialling that number...
vinay235 said:
This is what I got from dialling that number...
Click to expand...
Click to collapse
did you follow the instruction for a factory reset, skip the google log in and go straight to calibrate?
Hakim Farouk said:
did you follow the instruction for a factory reset, skip the google log in and go straight to calibrate?
Click to expand...
Click to collapse
hey i just noticed that the screen flips only after like 65 degrees of rotation so i think it has to be calibrated properly which im not able to do...any other way to calibrate my sensors...apps in play store say its been calibrated but sadly no change...
Same
Did the problem solve for you? I also flashed 04all zip.. And auto rotation is reversed
sarthakspiker said:
Did the problem solve for you? I also flashed 04all zip.. And auto rotation is reversed
Click to expand...
Click to collapse
Yes! Just wipe everything including system except internal storage and flash the stock ROM ... That worked for me!
vinay235 said:
Yes! Just wipe everything including system except internal storage and flash the stock ROM ... That worked for me!
Click to expand...
Click to collapse
Lol.. It was due to old firmware.. This issue was there in 2.1.2.. So solved after update
Sent from my ONE E1003 using Tapatalk
I have this problem after installing CM13. Tried wiping all of it and doing a fresh install and performing the "*#808# with no luck, just brings up a window that says "running USSD code" then it closes. Not sure what could possibly be the issue at this point. Any help?
I think u should wipe everything, install latest stock, then try clean install of cm13
Install at least 2.1.3 stock then it would be fine ..
Sent from my ONE E1003 using Tapatalk
I think I have the same problem. For me, portrait mode is fine but when I tilt the device into landscape mode (90° counterclockwise) then the screen is rotated clockwise instead. Analogously, when I put it in reverse landscape mode (90° clockwise), the screen is rotated counterclockwise. So the screen contents are always upside down in landscape mode. Did you guys have the same problem?
I tried everything suggested here. I first noticed the problem in OxygenOS 2.2.0-X. Tried installing an older OxygenOS version (2.1.3), the problem persisted. Then I flashed TWRP, rooted the device and installed a custom ROM, the problem persisted. I also tried a factory reset and wiping everything (including system), the problem persisted.
Does anyone have any other suggestions on what I could try? Or do you think this is a hardware issue? The device fell down once, do you think this could have broken the sensor?
I appreciate any kind of help.
Related
Hi all, i'am italian and i have a problem.
I have upgrade my s3 on 4.1.2 official and i have installed de GDFI02 file for my camera whit this tutorial.
Now, the camera is reversed (up to down) but the frontal camera is normal.
I tried to reinstall the rom with Odin (before I did reset to factory default, format /system and /sdcard) but the problem has remained.
I tried to go on *#0*# on megacam and also here there is the problem. I have tried to go on *#0*# and "Sensor" --> "Gyro Selftest" and the test is passed.
I tried to make a deep clean but the problem is still present.
I tried to re-installa SamsungCamera.apk. I copied the apk on system/app with root explorer (with permission), paste in the folder and reboot. The problem is still present.
I tried to install CyanogenMod but the problem is still present.
I'm disperate!! Please help me!!!
Sorry for my bad english!
That's a weird problem. Posting in hopes that someone who knows will see it because I have no idea. Your English is good btw
Sent from my GT-I9300 using xda app-developers app
7
pietro18m said:
Hi all, i'am italian and i have a problem.
I have upgrade my s3 on 4.1.2 official and i have installed de GDFI02 file for my camera whit this tutorial.
Now, the camera is reversed (up to down) but the frontal camera is normal.
I tried to reinstall the rom with Odin (before I did reset to factory default, format /system and /sdcard) but the problem has remained.
I tried to go on *#0*# on megacam and also here there is the problem. I have tried to go on *#0*# and "Sensor" --> "Gyro Selftest" and the test is passed.
I tried to make a deep clean but the problem is still present.
I tried to re-installa SamsungCamera.apk. I copied the apk on system/app with root explorer (with permission), paste in the folder and reboot. The problem is still present.
I tried to install CyanogenMod but the problem is still present.
I'm disperate!! Please help me!!!
Sorry for my bad english!
Click to expand...
Click to collapse
This is because you installed a camera firmware that is not for your phone. You must install the proper one. Before upgrading it did you see what was your previous camera firmware? ZDFI02 is not for all sgs3 phones.
Don't panic. If you find the proper cam firmware it gets fixed. Also a factory reset can do nothing. Cam fw has nothing to do with a Rom.
sachilleas said:
7
This is because you installed a camera firmware that is not for your phone. You must install the proper one. Before upgrading it did you see what was your previous camera firmware? ZDFI02 is not for all sgs3 phones.
Don't panic. If you find the proper cam firmware it gets fixed. Also a factory reset can do nothing. Cam fw has nothing to do with a Rom.
Click to expand...
Click to collapse
Yes, this is my screen before the upgrade.
I have installed the GDFI02.zip
Oh my god... is it different? Z and G... my error...
Now?
EDIT: the screenshot is when i had 4.1.1 !! I don't have the screen of 4.1.2
You had ZDFE02 installed but the latest version for your camera was ZDFF03.
Search and download one of these two camera firmwares (preferably the second one cause it's the latest) and follow the tutorial you quoted in order to install it! If you have a problem let me know.
Edit :I just found for you that you can download the files from : http://forum.xda-developers.com/showthread.php?t=2006128
sachilleas said:
You had ZDFE02 installed but the latest version for your camera was ZDFF03.
Search and download one of these two camera firmwares (preferably the second one cause it's the latest) and follow the tutorial you quoted in order to install it! If you have a problem let me know.
Edit :I just found for you that you can download the files from : http://forum.xda-developers.com/showthread.php?t=2006128
Click to expand...
Click to collapse
PERFECT! I just solved the problem with the ZDFF03.
I don't know why i have installed the GDFI02.
Thanks a lot!!!!!
pietro18m said:
PERFECT! I just solved the problem with the ZDFF03.
I don't know why i have installed the GDFI02.
Thanks a lot!!!!!
Click to expand...
Click to collapse
I am glad I have helped you! You are lucky that you took a screenshot of your phone and we didn't have to go into too much trouble. Enjoy your cam!
This is the ONLY thread you guys will talk about the CrDroid ROM.
DONT post questions or whatever at the other leaked AOSP ROM thread else it'll create much confusion
So far annoyances thats been reported are:
• Random reboots (at least for some people)
• Auto-brightness
• Underclocked CPU
• Not working HDR & Panaroma (solved with workaround)
DOWNLOAD LINK FOR CRDROID ROM
http://pan.baidu.com/s/1bnzqPBL
Reserved
Via the Internet
Regarding Random Reboots !
I have been using the ROM since yesterday though i have yet not observed a single reboot . I have tried following things as suggested in AOSP thread however it does not give me a reboot. Auto Brightness is the only lingering issue i faced !
Any pointers to reproduce the reboots ?
M3gAtR0N said:
I have been using the ROM since yesterday though i have yet not observed a single reboot . I have tried following things as suggested in AOSP thread however it does not give me a reboot. Auto Brightness is the only lingering issue i faced !
Any pointers to reproduce the reboots ?
Click to expand...
Click to collapse
LKspro said:
after u have the first reboot, cover the upper sensors and touch the screen while it is off. Then the screen should freeze and rebbot after a while
Click to expand...
Click to collapse
This is from @LKspro
Via the Internet
TiTAN-O-One said:
This is from @LKspro
Via the Internet
Click to expand...
Click to collapse
I have reproduced the same however it did not cause a reboot for me ! Thats why asked !! Is this the encountered random reboot occurrence ?? Or do we have something else too ?
Good rom lots of settings but useless... always reboot..
M3gAtR0N said:
I have reproduced the same however it did not cause a reboot for me ! Thats why asked !! Is this the encountered random reboot occurrence ?? Or do we have something else too ?
Click to expand...
Click to collapse
Yeah, first time it happens random, but if it once happens to you, then you will be able to reproduce it.
Anyone try to use the boot.img from leaked AOSP ROM and put I to this ROM? If yes do the random reboot still happening?
wai10691 said:
Anyone try to use the boot.img from leaked AOSP ROM and put I to this ROM? If yes do the random reboot still happening?
Click to expand...
Click to collapse
I can try this but not sure of the exact steps to follow... I like the CM rom very much.. blazing fast with ART, but random reboots quite often. I am now using wakelock to control the reboots. if you think changing the boot.img can help, i will try it out. lemme know what to do for tht
krispuniq said:
I can try this but not sure of the exact steps to follow... I like the CM rom very much.. blazing fast with ART, but random reboots quite often. I am now using wakelock to control the reboots. if you think changing the boot.img can help, i will try it out. lemme know what to do for tht
Click to expand...
Click to collapse
Before flashing the ROM zip simply replace the boot.img in the crdroid with the one from aosp.
I can try this later but I'm outside now
wai10691 said:
Before flashing the ROM zip simply replace the boot.img in the crdroid with the one from aosp.
I can try this later but I'm outside now
Click to expand...
Click to collapse
Done... Flashing went ok but after booting all my apps are gone (I didnt do a clean wipe while flashing.. only wiped dalvik)
The apps are gone anyway.. so i went back to recovery and did another clean flash.. Reboot the phone, but no mobile network. Unable to latch on to network even manually.. so may be there is something missing in the boot.img ?
Back key
Anyone can confirm back key in this rom didnt behave as it should after deleting pre-install files such as baidu services apps
edit 1 - looks like it has been warned by the dev as do not delete keyboard input method or else back button wont work..
Where is the link to the ROM. I'd update OP. Also, is there any bugs with the ROM? Or is it working like AOSP?
Via the Internet
Download link
http://pan.baidu.com/s/1bnzqPBL
DISCLAIMER:-I'm not responsible for bricked or problems arising from this fix do this at your own risk.
It's rather simple. Just follow the steps.
Pre-requisites:-
1.Rooted and unlocked bootloader.
3.ES file explorer with root access.
4.Stock kernel
5.Brains.(if you missed that there was '2' missing)
Method:
Open ES FILE explorer.
Go to 'device /'
Set path / and /system to rw from ro in mount rw menu
open system
open etc
scroll down till you find 'mixer_paths.xms'
open it with ES note editor
find and edit
<ctl name="RX3 Digital Volume" value="84" /> SET VALUE TO 91 From 84
scroll down
find and edit
<ctl name="Speaker Boost" value="DISABLE" /> CHANGE IT TO "ENABLE"
press the arrow on top left and save. then reboot
and dont forget to thank.
oemaritradey said:
It's rather simple. Just follow the steps.
Click to expand...
Click to collapse
This is just an temporary workaround. Do this on your own risk. However, i have been using value 89 for RX3, no issues so far.
This thread should be on General section, Mods please move it.
Sent from my AO5510 using XDA Free mobile app
Cant Attend/Dial call after changing values
I changed the values as per your Post but now i m unable to recieve and call.Its hanging on calling screen.
I cant hear any voice too.
I restored the original mixer_paths.xml but the issue is still there
i have rebooted and cleared dalvik/cache too.but issue is still there.
Please help
farzii said:
I changed the values as per your Post but now i m unable to recieve and call.Its hanging on calling screen.
I cant hear any voice too.
Please help
Click to expand...
Click to collapse
did you reboot the phone?
tell me exactly what you did.
oemaritradey said:
did you reboot the phone?
tell me exactly what you did.
Click to expand...
Click to collapse
Did exactly what u said in OP.
went to system/etc/mixer_paths.xml changed values of RX3 to 91 and changed speaker boost to ENABLED.
Rebooted.
Since then i m unable to pick up calls and dial calls.Call screen comes but when i drag the phone icon to green/Red icon it hangs there itself
farzii said:
Did exactly what u said in OP.
went to system/etc/mixer_paths.xml changed values of RX3 to 91 and changed speaker boost to ENABLED.
Rebooted.
Since then i m unable to pick up calls and dial calls.Call screen comes but when i drag the phone icon to green/Red icon it hangs there itself
Click to expand...
Click to collapse
are you on stock kernel?
you need to be on stock rom as well as stock kernel. if you weren't then i cant guarantee things. use ES file explorer to change the permission to r/w from ro and change it back again as well.
if not reflash the stock rom.
oemaritradey said:
are you on stock kernel?
Click to expand...
Click to collapse
Yes
farzii said:
Yes
Click to expand...
Click to collapse
I hope you had root and unlocked bootloader.
2nd i pmd you a link to yuforums for a guide to reflashing stock rom hope it helps.
oemaritradey said:
I hope you had root and unlocked bootloader.
2nd i pmd you a link to yuforums for a guide to reflashing stock rom hope it helps.
Click to expand...
Click to collapse
Thanks,I have custom recovery and nandroid backup.I'll restore it.
farzii said:
Thanks,I have custom recovery and nandroid backup.I'll restore it.
Click to expand...
Click to collapse
well you should have done that before xD i have absolutely no clue what went wrong. i changed my value back just in case and rebooted and changed it back again. i didn't find that bug. :3 well cheerio.
Hi @oemaritradey,
This same method had worked on my previous smartphone (Redmi 1s), and expectedly, works on Yureka as well. I have published a detailed guide (and a video) based on this method on my blog here: http://www.droidiser.com/2012/04/rooting-your-android-device.html
Just thought it would make sense to post about it in this thread.
Thanks Man.. It worked for me
mythreya said:
Thanks Man.. It worked for me
Click to expand...
Click to collapse
you're welcome
Thnx bro worked for me also.....
HELP!!
I followed the guide and now there is no audio... I also set the original values back but the problem persists.... Phone is rooted... HELP!! Will factory reset fix this??
EDIT: Did a factory reset.. Still no audio! i am screwed!! HELP!!
I am also facing a similar issue post this fix. No Sound on the phone and cannot play music files.
I have already tried wiping Dalvik and Cache
sayak_life said:
I followed the guide and now there is no audio... I also set the original values back but the problem persists.... Phone is rooted... HELP!! Will factory reset fix this??
EDIT: Did a factory reset.. Still no audio! i am screwed!! HELP!!
Click to expand...
Click to collapse
OK I fixed the problem by reflashing stock rom.... Audio is working now...
oemaritradey,Thanks bro it's working....
Yes.. Its work properly. Its awesome.. Can we do same for camera also like improving photo quality or etc ???
I wish I knew exactly what caused this to happen. I was using a Malaysk ROM and starting having the issues. I thought maybe it was the ROM so I downgraded back to the original ROM that came with my unit and I'm still having the same issues. I downgraded through system updates in settings.
I can get it to boot into recovery, but it's just a black screen with pulsating light blue lights on the side of my unit. I have a Joying RK3188 1024x600 with the touch buttons on the left side.
Also when the unit boots up I don't get the Android splash screen anymore, it's also black. The first sign of life is when the car logo screen pops up.
There have also been multiple cases where when I am using the unit the screen has turned black ( if the radio is playing it will continue to play though ) and I can't do anything on the screen. This has to be a related issue.
Does anyone have any idea whats going on here?
I appreciate any help I can get!
Anyone have any ideas?
ahfunaki said:
Anyone have any ideas?
Click to expand...
Click to collapse
Try reflashing both MCU and ROM.
Use USB method for recovery of brick unit.
Or try reflashing from GPS card by mimicking procedure as it should be done on screen working even if you don't see it (look for screenshots of recovery and try to perform needed actions - somewhere here was such hint for someone whose screen brightness was completely darked out and has to perform factory reset from recovery on the blind).
pa.ko said:
Try reflashing both MCU and ROM.
Use USB method for recovery of brick unit.
Or try reflashing from GPS card by mimicking procedure as it should be done on screen working even if you don't see it (look for screenshots of recovery and try to perform needed actions - somewhere here was such hint for someone whose screen brightness was completely darked out and has to perform factory reset from recovery on the blind).
Click to expand...
Click to collapse
What is USB method? Just load the files on to a flash drive?
And I've found a picture of the recovery menu and I've tried that multiple times with no success.
Thank you for your help!
pa.ko said:
Try reflashing both MCU and ROM.
Use USB method for recovery of brick unit.
Or try reflashing from GPS card by mimicking procedure as it should be done on screen working even if you don't see it (look for screenshots of recovery and try to perform needed actions - somewhere here was such hint for someone whose screen brightness was completely darked out and has to perform factory reset from recovery on the blind).
Click to expand...
Click to collapse
Putting the stock MCU and ROM on the GPS card fixed it! I did the update from the settings menu and it worked! I have recovery again! Thank you so much for the help!
I really want to install the custom ROM again, but I really don't want to keep having this issue though. Does anyone have any idea what is causing this to happen?
ahfunaki said:
Putting the stock MCU and ROM on the GPS card fixed it! I did the update from the settings menu and it worked! I have recovery again! Thank you so much for the help!
I really want to install the custom ROM again, but I really don't want to keep having this issue though. Does anyone have any idea what is causing this to happen?
Click to expand...
Click to collapse
I had bad experience with MCU v2.83
After some time it started to make touch screen not working, factory settings pass not recognising standard 126 etc.
After restart - all normal. Then for no reasons next day problems rrapear...
Reverting to stock v2.80 resolves issue. And Nalaysk ROM works with no prob.
So, if you upgraded MCU - that may be a reason.
If not, then maybe your ROM file was corrupted. Or your internal memory got corrupted somehow.
My prob with newer MCU, not working on cold morning first start but working after reset, points out that there is some HW related issue. With new version only though! Figure it out...
pa.ko said:
I had bad experience with MCU v2.83
After some time it started to make touch screen not working, factory settings pass not recognising standard 126 etc.
After restart - all normal. Then for no reasons next day problems rrapear...
Reverting to stock v2.80 resolves issue. And Nalaysk ROM works with no prob.
So, if you upgraded MCU - that may be a reason.
If not, then maybe your ROM file was corrupted. Or your internal memory got corrupted somehow.
My prob with newer MCU, not working on cold morning first start but working after reset, points out that there is some HW related issue. With new version only though! Figure it out...
Click to expand...
Click to collapse
I never updated the MCU so I'm really not sure what happened.
I'm actually don't mind using the stock ROM minus the fact I've already ran out of storage, is there anything I can do about that? So many things are working better for me now. Before I wasn't able to get an OBDII adapter to connect to torque and now it works perfect.
I'd love to go back to the Malaysk ROM but I just had so many issues...
Use link2sd to store your apps on an external sd card.
Sent from my SM-G920F using Tapatalk
ahfunaki said:
I never updated the MCU so I'm really not sure what happened.
I'm actually don't mind using the stock ROM minus the fact I've already ran out of storage, is there anything I can do about that? So many things are working better for me now. Before I wasn't able to get an OBDII adapter to connect to torque and now it works perfect.
I'd love to go back to the Malaysk ROM but I just had so many issues...
Click to expand...
Click to collapse
There is also another ROM, look for thread named Interesting ROM with FUSE support.
It is almost stock but with FUSE partitioning so you have all space for both sys app and data.
BTW your prob with OBD2 is known issue in Malaysk ROM if you enabled xposed BT module.
gk66 said:
Use link2sd to store your apps on an external sd card.
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
I actually tried that, but I couldn't get it to run on boot. It didn't seem like it was working too well for me but maybe I was just doing something wrong.
pa.ko said:
There is also another ROM, look for thread named Interesting ROM with FUSE support.
It is almost stock but with FUSE partitioning so you have all space for both sys app and data.
BTW your prob with OBD2 is known issue in Malaysk ROM if you enabled xposed BT module.
Click to expand...
Click to collapse
I will look into this, thanks again!
ahfunaki said:
I actually tried that, but I couldn't get it to run on boot. It didn't seem like it was working too well for me but maybe I was just doing something wrong.!
Click to expand...
Click to collapse
You need to root your head unit. Use the root code from the wiki. Then install super su and give permissions to link2sd. Remember to properly partition sd card ss well
Sent from my SM-G920F using Tapatalk
gk66 said:
You need to root your head unit. Use the root code from the wiki. Then install super su and give permissions to link2sd. Remember to properly partition sd card ss well
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
Thank you for the help, I ended up just installing that other rom with FUSE so everything is good now.
Really enjoying this thing...
ahfunaki said:
Putting the stock MCU and ROM on the GPS card fixed it! I did the update from the settings menu and it worked! I have recovery again! Thank you so much for the help!
I really want to install the custom ROM again, but I really don't want to keep having this issue though. Does anyone have any idea what is causing this to happen?
Click to expand...
Click to collapse
How did you doing this, did you do this from the system update menu? I have same problem but if I try your way, I only get a black screen.
MueKo said:
How did you doing this, did you do this from the system update menu? I have same problem but if I try your way, I only get a black screen.
Click to expand...
Click to collapse
Please check the solution here:
http://forum.xda-developers.com/showpost.php?p=66415327&postcount=3139
oscyp said:
Please check the solution here:
http://forum.xda-developers.com/showpost.php?p=66415327&postcount=3139
Click to expand...
Click to collapse
Thank you for your support. My problem was that my recovery image was damaged. I fixed it by reflashing the recovery image.
thx
I have the same problem now. I just went into recovery mode and installed update_4_4_4_FUSE_1024X600_RK3188_17_MAL_23_04_2016.
All was well until the Android loader image just sat there pulsing. The unit still had not started up after 40 mins of this logo being on screen.
Going into recovery mode just shows a black screen now. So my unit is effectively dead, or can it be rescued?
RS-TLS said:
I have the same problem now. I just went into recovery mode and installed update_4_4_4_FUSE_1024X600_RK3188_17_MAL_23_04_2016.
All was well until the Android loader image just sat there pulsing. The unit still had not started up after 40 mins of this logo being on screen.
Going into recovery mode just shows a black screen now. So my unit is effectively dead, or can it be rescued?
Click to expand...
Click to collapse
Anybody able to help me out here?
RS-TLS said:
Anybody able to help me out here?
Click to expand...
Click to collapse
Is it possible to start your device normal?
No. It just sits at the bootloader.
Sent from my SM-G928F using Tapatalk
Try in recovery mode to enter back in normal boot mode. It's difficult to explain in englisch. I had to pin a small needle into my radio and ca. 0,5 seconds before the LED are flashing, stop with pushing. When you stop pushing you must wait 5-10 second and see if you device boot up normal.
You have to try this often to find the correct moment. Thats how I entered back to normal boot mode.
installing..,
Installed on my wife's Pixel 3 with flash-all (minus -w). Rooted with Magisk 18.1 via TWRP .img instance and installed ElementalX 1.06 with EX Kernel Manager auto. Made one custom prop setting. No issues at all.
Any idea what fixes are in this one?
davidstjohn1 said:
Any idea what fixes are in this one?
Click to expand...
Click to collapse
https://source.android.com/security/...019-04-01.html
https://source.android.com/security/...language=zh_cn
davidstjohn1 said:
Any idea what fixes are in this one?
Click to expand...
Click to collapse
https://source.android.com/security/bulletin/pixel/2019-04-01.html
Hi everyone, I need some help/advice,
I tried flashing the April factory image (minus -w), and am now on "Can't load Android System. Your data may be corrupt" error. Everytime I reboot the device it just goes to "No Command" or this error screen.
I uninstalled Magisk, and was on Sultan's kernel. Does anyone have any suggestions on how to restore my system without having to factory reset? I know some people suggested flashing stock kernel, but I can't seem to find the link to it (I thought the stock kernel was with the factory image).
Any help would be appreciated!
I am dling the factory image now, but boot.img should be in there. Are you sure it was not a bad dl?
-Boot.img is in there. Extract the zip then open the "image-blueline....zip" it is in there. If it is not then something is wrong with your dl.
sliding_billy said:
Installed on my wife's Pixel 3 with flash-all (minus -w). Rooted with Magisk 18.1 via TWRP .img instance and installed ElementalX 1.06 with EX Kernel Manager auto. Made one custom prop setting. No issues at all.
Click to expand...
Click to collapse
What prop setting are you making. Just curious, I haven't seen any prop editing threads for the pixel 3.
FilthyFord said:
What prop setting are you making. Just curious, I haven't seen any prop editing threads for the pixel 3.
Click to expand...
Click to collapse
Native tethering. This method works on my 3 XL as well as my wife's "little" 3 on T-Mobile.
https://forum.xda-developers.com/pixel-3-xl/how-to/how-to-native-tethering-rooted-pixel-3-t3858662
atu567 said:
Hi everyone, I need some help/advice,
I tried flashing the April factory image (minus -w), and am now on "Can't load Android System. Your data may be corrupt" error. Everytime I reboot the device it just goes to "No Command" or this error screen.
I uninstalled Magisk, and was on Sultan's kernel. Does anyone have any suggestions on how to restore my system without having to factory reset? I know some people suggested flashing stock kernel, but I can't seem to find the link to it (I thought the stock kernel was with the factory image).
Any help would be appreciated!
Click to expand...
Click to collapse
I had the same issue, cant find stock kernel either.
extracted the zip, fastboot flash boot boot.img, fixed.
jk didnt work oddly enough.
got to login then wouldnt let me use my screen. no touch input.
edit again: update platform tools fixed problem. https://dl.google.com/android/repository/platform-tools_r28.0.2-windows.zip
sliding_billy said:
Installed on my wife's Pixel 3 with flash-all (minus -w). Rooted with Magisk 18.1 via TWRP .img instance and installed ElementalX 1.06 with EX Kernel Manager auto. Made one custom prop setting. No issues at all.
Click to expand...
Click to collapse
hey,bro!I would like to ask if magisk can pass the safetynet check after installing the April Updata. My pixel 3 feedback me ‘’the return value is invalid’’
wssxzzzz said:
hey,bro!I would like to ask if magisk can pass the safetynet check after installing the April Updata. My pixel 3 feedback me ‘’the return value is invalid’’
Click to expand...
Click to collapse
No problem with safetynet here.
sliding_billy said:
No problem with safetynet here.
Click to expand...
Click to collapse
Ok, thank you, I think that is my problem.
wssxzzzz said:
Ok, thank you, I think that is my problem.
Click to expand...
Click to collapse
What is the problem?
Obviously quite subjective, but the camera appears to be opening faster for me when double clicking power. There was also a Google Camera update from the Play Store this morning, so could have been that as well, but this has been a major bug bear of mine since getting the Pixel 3, so hope it stays like that!
benj! said:
Obviously quite subjective, but the camera appears to be opening faster for me when double clicking power. There was also a Google Camera update from the Play Store this morning, so could have been that as well, but this has been a major bug bear of mine since getting the Pixel 3, so hope it stays like that!
Click to expand...
Click to collapse
Def the cam app I noticed too and I'm on Jan update, it's nice tho!
I installed the April update to fix the flashing bug of the ambient display, bit it is still there. Any body else having this issue? Also, is there any fix for this?