EDIT 5
In addition to the two methods highlighted below, I'm sharing a third method which was brought up in the thread. This one is much easier, however, root is required. This method works for many, however, it is not confirmed by me. Again, no one takes responsibility for this or the previous method.
Ask someone with working sensors to share the following folder with you: root/mnt/vendor/persist/sensors. Please ensure the device they have is the same as yours (Pixel 3 (blueline) and Pixel 3 XL (crosshatch) are NOT the same devices). They should, ideally, share it as a *.tar file to keep the permissions of subfiles intact.
Instructions to generate this tar file are here: https://forum.xda-developers.com/pixel-3-xl/how-to/android-10-sensors-bug-t3964904/post80833171
On your rooted phone running Android 10, navigate to: root/mnt/vendor/persist/ and first of all, backup your /sensors/ folder. Then, paste the contents of the tar file in there so you have the sensors folder from the working device that was shared with you.
Reboot and report. You should have working sensors now.
EDIT 4
TWRP Developers are working on fixing the root cause of this issue. More details here: https://forum.xda-developers.com/showpost.php?p=80248406&postcount=1218
EDIT 3
We now have an update from Google: Here is the email we received (posting it verbatim after redacting any personal or confidential information).
We now have a root cause for this issue and a fix will rollout in October.
The short summary is that in Q qualcomm added some checks that prevented sensors from starting when it found corrupted calibration files. In Pi it was more forgiving and continue to function even though the calibration files may have been corrupted. The fix will revert back similar to what Pi was doing. The upside is sensors will continue to work. The downside is, some of the sensors may not function as effectively if the calibration files are corrupted due to external reasons. Regular users who do not touch persist partition would not hit this issue.
Thanks all for your support. Please do let us know if you are seeing any other issues post Android 10 rollout that need attention. We will start ramping up the rollouts next week.
Click to expand...
Click to collapse
EDIT 2
Thanks to many members of this thread, I am sharing a second method which does not involve flashing a new /persist/ partition that was shared before. This method works for many, however, it is not confirmed by me. Again, no one takes responsibility for this or the previous method.
Steps below (not my work; thanks to others on this thread):
We assume you are on Android 10 for these steps.
Backup your current persist partition since you will be changing it. On a rooted adb shell, run dd if=/dev/block/by-name/persist of=/sdcard/persist.img (this will backup your persist to your sdcard)
Navigate to root/mnt/vendor/persist and delete the cache folder completely. This stores TWRP's cache and log files and is the root cause of the problem in the first place.
Flash Android 9 (PIE) from bootloader. YOU DO NOT NEED TO WIPE your data so you can remove the "-w" flag
Let the phone boot (it will bootloop; that is normal) for 2-3 minutes. This step will "fix your broken persist files" according to users
Reboot to bootloader and flash Android 10. Again, YOU DO NOT NEED TO WIPE your data, so you may remove the "-w" flag.
Reboot and report if this works.
EDIT 1
This issue was fixed. The problem is with the persist partition getting corrupted on some devices. The reasons are not clear, but we have strong reasons to believe this is due to TWRP's implementation of leaving logs and cache files on the /persist partition, which is limited in size. The log files often exceed 20MB in size and cause the sensor config and calibration files to become corrupted on that partition.
Steps to get this fixed:
Obtain a working persist.img from someone (it is device specific. You can find the ones for crosshatch and blueline on this thread, but will have to ask someone else for other devices)
Replace your persist partition with the persist.img you obtained. This needs to be done using an advanced command (dd) and you need to be on Android 9 in TWRP (rooted) to do this. Read the thread (around page 19) for more details.
Flash Android 10 (does not need to be a clean install, but clean install is always recommended).
WARNING: replacing your persist partition with someone else's (even the same device) WILL replace your original, unique factory calibration data with someone else's. This includes audio config files, camera calibration files, sensor calibration files. Backup your original /partition image before doing this and only do this if it is absolutely necessary. You have been warned!
No one on this thread assumes responsibility for anything bad happening to your device. It worked for all of us, but is not guaranteed to work for you. Still no news from Google, who are still investigating.
ORIGINAL THREAD
Starting a new thread here from the old one: https://forum.xda-developers.com/pixel-3-xl/how-to/android-10-final-version-release-t3963794/page7
What is the problem?
Many users of Pixel 3 XL, Pixel 3, Pixel 2 XL and even the OG Pixel are reporting a major bug after upgrading to Android 10. All the sensors seem to be disabled.
This includes Active Edge, Proximity Sensor, Ambient Light Sensor, Auto-brightness, Accelerometer (Auto-rotation, flip to shhh, double tap to wake and lift to wake). All of these are dead on Android 10.
What we know:
Whether we upgrade directly from Android Pie or do a clean install using the factory images does not seem to matter. The issue only affects a certain set of users and only goes away if we revert to Pie. The phone works perfectly then.
Manually erasing all partitions and installing from the image does not work either.
Installing Android 10 individually on partitions A and B does not help either.
Re-locking the bootloader and returning completely to stock does not work either.
The only thing in common for all of us is that we were all rooted and/ or using a custom kernel in the past. However, some others who had been rooted and using custom kernels/ ROMs report they do not face this issue.
Interestingly, for users on the beta program, they started noticing this issue around Beta 6. Post-that, even if they reverted to an older Beta 3,4 or 5 which did not have this problem, they would face this problem after Beta 6. And this is continues with the public version now.
Some users suspect this could be happening due to "something left-over somewhere hidden on the phone." (not verified, but makes sense, in theory)
Coverage
This issue is widely covered now:
https://bgr.com/2019/09/05/android-10-update-for-pixel-phones-sensors-bug-explained/
https://www.androidauthority.com/pixel-sensors-android-10-1026027/
https://9to5google.com/2019/09/05/pixel-active-edge-sensors-android-10/
https://mobilesyrup.com/2019/09/05/pixel-users-experience-dead-sensors-post-android-10-update/
... and many more
Next steps:
If you face this issue, please add your comments and what you have tried here and update the bug on Google's issue tracker that we have filed here:
https://issuetracker.google.com/issues/140476661
There is also a help center article on Google's support forum that you can upvote here: https://support.google.com/pixelphone/thread/13511202?hl=en
So the 3A and 3A XL aren't affected? I have 10 on mine now after sideloading the OTA last night and aside from the 20 minute reboot cycle, I've seen no problems as of yet.
BigOkie said:
So the 3A and 3A XL aren't affected? I have 10 on mine now after sideloading the OTA last night and aside from the 20 minute reboot cycle, I've seen no problems as of yet.
Click to expand...
Click to collapse
No idea about the other models. I've just posted the ones that I could find on forums, including mind (3XL).
There is something in common here for everyone that we seem to be missing. In the interest of getting to the root of it, I am posting my pre-android 10 update configuration:
Pixel 3XL, hardware model MP1.0
Rooted with magisk 19.3
Recovery: TWRP
Kernel: Kirisakura Kernel v3.4.5
Magisk modules installed: youtube vanced, busybox, energized, systemless hosts, zRAM/ SWAP manager to enable zram
Apart from this, I had naptime installed working in root mode
And tweaked a few kernel settings: color settings, changed scheduler for graphics, zram compression algorithm and I/O scheduler.
Anyone else facing this problem see something in common?
That is sooooo weird... I've never seen that on my phone
nikhilnangia said:
Interestingly, for users on the beta program, they started noticing this issue around Beta 6. Post-that, even if they reverted to an older Beta 3,4 or 5 which did not have this problem, they would face this problem after Beta 6. And this is continues with the public version now.
Click to expand...
Click to collapse
I would rather say this is related to the bootloader that after flashing beta 6 doesn't get downgraded when returning to an older beta version or even Pie. Since only a part of the users is affected I would guess that a specific hardware revision doesn't play nice with Android 10. As I am not affected I can't do further testing and you should take what I wrote above as an educated guess .
alpinista82 said:
I would rather say this is related to the bootloader that after flashing beta 6 doesn't get downgraded when returning to an older beta version or even Pie. Since only a part of the users is affected I would guess that a specific hardware revision doesn't play nice with Android 10. As I am not affected I can't do further testing and you should take what I wrote above as an educated guess .
Click to expand...
Click to collapse
Thanks for the ideas! I can confirm that the hardware version is not the problem since some others with the same hardware version as myself (MP1.0 - which can be checked on About Phone->Hardware) do NOT face this issue.
As far as the bootloader goes, that's certainly plausible. @ultimatepichu and @FcukBloat has any of you tried this? i.e change the bootloader version to an older version and flash 10?
nikhilnangia said:
As far as the bootloader goes, that's certainly plausible. @ultimatepichu and @FcukBloat has any of you tried this? i.e change the bootloader version to an older version and flash 10?
Click to expand...
Click to collapse
the first thing in flash-all is to send the bootloader to the phone . But even if the bootloader is not downgraded, then I should get sensor problem in Pie as well right?
But no, I didn't try what you said.
After majorly screwing up my first attempt to jump from Pie to 10, I finally made it, and sure enough, I am a victim of this bug as well.
On an unrelated note, for the Magisk users out there, attached is the patched boot.img across 4 RAR archives for the Pixel 3 XL 10.0.0 (QP1A.190711.020, Sep 2019) image to save you some time making one yourself.
The SHA-256 hash for the image contained across the archives is:
Code:
dbdc828777fd8b734986998d0732c1c4e3e565fc66499c310f3a23c85abe383b
Just listening... can't figure this one out too...in the GSI build I found a Qualcomm driver for sensors for Crosshatch, but I don't know how to flash it, downloaded the bin and Qualcomm installer but afraid to go thru it might kill my phone. I do an average a day of flashing, my phone might get crazy???
---------- Post added at 01:14 AM ---------- Previous post was at 01:10 AM ----------
Me and FCUCKBloat has been discussing this since beta 6 came out. All my sensors used to work on beta 5, with kernels and TWRP installed, but after I tried flashing custom ROM and eventually beta6 came out flashed it thru fastboot, regular update and so on, sensors won't worked anymore. So, I decided to go back to beta 5 but sadly sensors don't worked anymore, when it used to worked before.:crying:
This happened to me since Pie. And Google seem doesn't do anything about it.
httpss://support.google.com/pixelphone/thread/3086868?hl=en
installed the GSI BUILD 10 from google and all sensors are working, flash it came from Bootleggers ROM. The only thing I can't find is the gesture Nav, maybe someone can help me activate it, so far all the sensors, dark mode are working.
imna357 said:
installed the GSI BUILD 10 from google and all sensors are working, flash it came from Bootleggers ROM. The only thing I can't find is the gesture Nav, maybe someone can help me activate it, so far all the sensors, dark mode are working.
Click to expand...
Click to collapse
please can you provide a step by step guide to flash GSI and fix this problem so other guys can also try this and eventually report the results in the bug tracker site to inform Google specialists? please!
tia
FcukBloat said:
please can you provide a step by step guide to flash GSI and fix this problem so other guys can also try this and eventually report the results in the bug tracker site to inform Google specialists? please!
I just downloaded it from the android 10 from here: https://developer.android.com/topic/generic-system-image/releases
then downloaded this version ARM64+GMS, problem only is the gesture navigation and phone apk, gestures is not present, while phone I can't here anything, I can call but nothing on the earpiece, and no voice output from the other side
---------- Post added at 01:20 AM ---------- Previous post was at 01:12 AM ----------
this thing is smooth, but I am not sure is a daily driver, good thing is sensors are working, maybe will just have to wait for a custom 10 ROM or I will try the TREBLE ROM : https://t.me/androidqgsi
Click to expand...
Click to collapse
imna357 said:
FcukBloat said:
please can you provide a step by step guide to flash GSI and fix this problem so other guys can also try this and eventually report the results in the bug tracker site to inform Google specialists? please!
I just downloaded it from the android 10 from here: https://developer.android.com/topic/generic-system-image/releases
then downloaded this version ARM64+GMS, problem only is the gesture navigation and phone apk, gestures is not present, while phone I can't here anything, I can call but nothing on the earpiece, and no voice output from the other side
---------- Post added at 01:20 AM ---------- Previous post was at 01:12 AM ----------
this thing is smooth, but I am not sure is a daily driver, good thing is sensors are working, maybe will just have to wait for a custom 10 ROM or I will try the TREBLE ROM : https://t.me/androidqgsi
Click to expand...
Click to collapse
thanks my friend, but how flashed system.img and vbmeta.img? i mean all steps coming from bootleggers please. so I can replicate and also inform google people so they maybe understand what is wrong in the official Q image.
about phone, in the google site I see:
Phone Audio - When using the integrated dialer, you may not hear any audio on the phone. This is due to a change in the telephony service installation location in Android 10.
did you try any other dialer? maybe that will fix the phone voice issue?
Click to expand...
Click to collapse
FcukBloat said:
imna357 said:
thanks my friend, but how flashed system.img and vbmeta.img? i mean all steps coming from bootleggers please. so I can replicate and also inform google people so they maybe understand what is wrong in the official Q image.
about phone, in the google site I see:
Phone Audio - When using the integrated dialer, you may not hear any audio on the phone. This is due to a change in the telephony service installation location in Android 10.
did you try any other dialer? maybe that will fix the phone voice issue?
Click to expand...
Click to collapse
I am trying it right now, looking for dialer that will work.
I flashed it this way, from Bootleggers ROM did not wipe anything just boot to fastboot then:
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot erase system
fastboot flash system system.img
fastboot -w
fastboot reboot
---------- Post added at 01:52 AM ---------- Previous post was at 01:43 AM ----------
I went on flashing the official 10, not sure what will happen=)
---------- Post added at 01:53 AM ---------- Previous post was at 01:52 AM ----------
will update in a few
Click to expand...
Click to collapse
imna357 said:
FcukBloat said:
I am trying it right now, looking for dialer that will work.
I flashed it this way, from Bootleggers ROM did not wipe anything just boot to fastboot then:
fastboot --disable-verification flash vbmeta vbmeta.img
fastboot erase system
fastboot flash system system.img
fastboot -w
fastboot reboot
---------- Post added at 01:52 AM ---------- Previous post was at 01:43 AM ----------
I went on flashing the official 10, not sure what will happen=)
Click to expand...
Click to collapse
thanks sir! let us know! I am doing some tests here too soon.
ps. fastboot -w erase all user data btw, correct? also internal storage I think
Click to expand...
Click to collapse
yup
---------- Post added at 01:55 AM ---------- Previous post was at 01:54 AM ----------
copy your storage first on a computer
---------- Post added at 02:07 AM ---------- Previous post was at 01:55 AM ----------
well flashing to official 10, sensors stop working again...what the, i will try to factory reset
would like to try to replace the system and vbmeta images in stock Q with the ones in the
GSI package, but in GSI we have a single system.img file while in stock Q there are two (system.img and system_other.img) so don't know how I could do
alternatively I could try just fastboot flashing system and vbmeta images from stock Q, but again I wouldn't know how to manage the two system images... :silly:
---------- Post added at 08:30 AM ---------- Previous post was at 08:11 AM ----------
@imna357 I can't erase system and install GSI system image, I go in bootloader (fastboot mode) and i can flash vbmeta image, but when I try to erase or flash system image, it says this must be done in fastbootD...
>fastboot flash system system.img
Invalid sparse file format at header magic
Sending sparse 'system_a' 1/9 (261528 KB) OKAY [ 6.370s]
Writing 'system_a' FAILED (remote: 'Partition should be flashed in fastbootd')
fastboot: error: Command failed
:silly:
FcukBloat said:
would like to try to replace the system and vbmeta images in stock Q with the ones in the
GSI package, but in GSI we have a single system.img file while in stock Q there are two (system.img and system_other.img) so don't know how I could do
alternatively I could try just fastboot flashing system and vbmeta images from stock Q, but again I wouldn't know how to manage the two system images... :silly:
---------- Post added at 08:30 AM ---------- Previous post was at 08:11 AM ----------
@imna357 I can't erase system and install GSI system image, I go in bootloader (fastboot mode) and i can flash vbmeta image, but when I try to erase or flash system image, it says this must be done in fastbootD...
>fastboot flash system system.img
Invalid sparse file format at header magic
Sending sparse 'system_a' 1/9 (261528 KB) OKAY [ 6.370s]
Writing 'system_a' FAILED (remote: 'Partition should be flashed in fastbootd')
fastboot: error: Command failed
:silly:
Click to expand...
Click to collapse
this thing happened to me last night, if you can't erase the system it will not go thru, but after flashing bootleggers then let it settle with magisk, reboot to bootloader, it worked
---------- Post added at 02:55 AM ---------- Previous post was at 02:51 AM ----------
were you on pie rooted?
---------- Post added at 02:58 AM ---------- Previous post was at 02:55 AM ----------
ok, your on Q, will not work, last night I was on Q it did not work, need to be on PIE...sorry busy flashing my phone back to bootleggers, will try the TREBLE ROM tomorrow
I came from pie rooted avb and encryption disabled an took the ota when booting it said it was corrupted had to factory reset booted and worked fine all sensors any way except the mobile data sucks worse but I'm on Google Fi in East Tennessee. Also there's 2 builds for Android 10 on the dev site maybe try both builds and worst case scenario go back to pie and disable avb and encryption then set phone up then try taking the ota.
To disable avb and encryption boot to twrp then advance wipe,format data then sideload this zip and flash then reboot.
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389/amp/
Related
Hi All!
I'm brand new to this forum, so thanks for reading this in advance.
I am totally new at this.
My XT926 crashed while I was wiping the google cache and a phone call came in, and now won't get past the motorola logo on bootup. I've tried calling Verizon and Motorola but their solutions have not helped. I have done the factory reset from the recovery menu, and attempted to flash Jelly Bean 4.1.2 using RSD lite and the recovery menu. Having a bit of an issue with installing AdbWinApi.Dll (or some such file)
Here are the issues I'm having:
I don't know how to determine which version of software might possibly be still on the phone. The Verizon Tech seemed to think that all the software on the phone is gone, including the startup file. The fastboot menu
reads:
AP Flashboot Flash Mode (S)
10.9B(*) (sha-61146a2, 2014-07-29 00:54:49)
eMMC Info: Size 32GB
Device is LOCKED, Status Code: 0
Battery OK
Transfer Mode:
USB Connected
I'm not sure if there is a way to get back to the stock software. The phone is out of warranty so if rooting or any other kind of exploit is the way to go, I'm all for it.
I realize you guys have a lot of more exciting things to do, so thanks for any help you can provide. Thanks!
Was the firmware on a 4.1.2 build when it crashed?
93zx7 said:
Was the firmware on a 4.1.2 build when it crashed?
Click to expand...
Click to collapse
What version of Version of android were you using?
---------- Post added at 03:57 AM ---------- Previous post was at 03:55 AM ----------
Cheesehut said:
Hi All!
I'm brand new to this forum, so thanks for reading this in advance.
I am totally new at this.
My XT926 crashed while I was wiping the google cache and a phone call came in, and now won't get past the motorola logo on bootup. I've tried calling Verizon and Motorola but their solutions have not helped. I have done the factory reset from the recovery menu, and attempted to flash Jelly Bean 4.1.2 using RSD lite and the recovery menu. Having a bit of an issue with installing AdbWinApi.Dll (or some such file)
Here are the issues I'm having:
I don't know how to determine which version of software might possibly be still on the phone. The Verizon Tech seemed to think that all the software on the phone is gone, including the startup file. The fastboot menu
reads:
AP Flashboot Flash Mode (S)
10.9B(*) (sha-61146a2, 2014-07-29 00:54:49)
eMMC Info: Size 32GB
Device is LOCKED, Status Code: 0
Battery OK
Transfer Mode:
USB Connected
I'm not sure if there is a way to get back to the stock software. The phone is out of warranty so if rooting or any other kind of exploit is the way to go, I'm all for it.
I realize you guys have a lot of more exciting things to do, so thanks for any help you can provide. Thanks!
Click to expand...
Click to collapse
what version of android were you using?
OGdroidster said:
What version of Version of android were you using?
---------- Post added at 03:57 AM ---------- Previous post was at 03:55 AM ----------
what version of android were you using?
Click to expand...
Click to collapse
Mine just started freezings suddenly
Cheesehut said:
Hi All!
I'm brand new to this forum, so thanks for reading this in advance.
I am totally new at this.
My XT926 crashed while I was wiping the google cache and a phone call came in, and now won't get past the motorola logo on bootup. I've tried calling Verizon and Motorola but their solutions have not helped. I have done the factory reset from the recovery menu, and attempted to flash Jelly Bean 4.1.2 using RSD lite and the recovery menu. Having a bit of an issue with installing AdbWinApi.Dll (or some such file)
Here are the issues I'm having:
I don't know how to determine which version of software might possibly be still on the phone. The Verizon Tech seemed to think that all the software on the phone is gone, including the startup file. The fastboot menu
reads:
AP Flashboot Flash Mode (S)
10.9B(*) (sha-61146a2, 2014-07-29 00:54:49)
eMMC Info: Size 32GB
Device is LOCKED, Status Code: 0
Battery OK
Transfer Mode:
USB Connected
I'm not sure if there is a way to get back to the stock software. The phone is out of warranty so if rooting or any other kind of exploit is the way to go, I'm all for it.
I realize you guys have a lot of more exciting things to do, so thanks for any help you can provide. Thanks!
Click to expand...
Click to collapse
What what version ofvandroivwere you using?
---------- Post added at 04:48 AM ---------- Previous post was at 04:48 AM ----------
93zx7 said:
Mine just started freezings suddenly
Click to expand...
Click to collapse
Is it still freezing?
OGdroidster said:
What what version ofvandroivwere you using?
---------- Post added at 04:48 AM ---------- Previous post was at 04:48 AM ----------
Is it still freezing?
Click to expand...
Click to collapse
Not since I did a hard reboot. It does it sometimes after it sits in suspended state overnight/while charging. It also doesn't seem like any specific app is triggering it. It happens on different apps
93zx7 said:
Not since I did a hard reboot. It does it sometimes after it sits in suspended state overnight/while charging. It also doesn't seem like any specific app is triggering it. It happens on different apps
Click to expand...
Click to collapse
What exactly have you tried to do to solve your situation.
OGdroidster said:
What exactly have you tried to do to solve your situation.
Click to expand...
Click to collapse
So far, the only thing I have done is uninstall several apps I didn't need/use anymore and cleared cache. So far so good. If it starts doing it again, I will be reflashing the firmware is RSD lite. Worse come to worse, I buy another mb/lb and replace the current board in it.
Doesn't sound like hardware
OGdroidster said:
Doesn't sound like hardware
Click to expand...
Click to collapse
What version of rsd are you using?
Some time ago I bought a Honor 6 bricked by a firmware upgrade.
I done some reading, I asked friends but I couldn't fix it. I opened a topic here and many people tried to help me. Nothing worked... I contacted some experienced people from this, and a Romanian forum, but no success. I was trying to fix it for 2 months now.
Eventually, I came across a solution made by DC-Unlocker Team.
I bought some credits to be able to run the solution and with a few mouse clicks my phone was repaired. Now it works perfectly. I do have some questions to ask about several issues in Honor 6, but let me describe how I fixed my phone with this solution.
I would like to underline that I am in no way related to the DC-unlocker Team.
The software can repair most of the Honor firmware problems:
Bricked phones, bootloop, stuck in fastboot mode
It can write full firmware update.app in fastboot mode
Can flash phones with locked bootloader or FRP. (No need to get the bootloader unlock code)
The whole procedure is detailed here, but let me describe the steps which I took. I also attach few screenshots of the process.
1. Make sure, that you install Huawei Hisuite (for drivers), or Universal ADB driver.
2 Enter fastboot mode on the phone and connect it to your computer. Remove the SD card if there is one installed in the phone.
3. Check if computer detects the phone is fastboot mode, run fastboot devices command
4. The firmware repair process will need 15 credits (which will cost 15 euro). You can buy the credits here
Credits are deducted immediately, but you can flash the same phone any time you want for 72 hours.
5. After you buy the credits, download the software client here
Supported models and features here
6. Start the program. It will ask your credentials for the DC-unlocker server. You receive those credentials when you buy the first time credits.
7. In the DC Phoenix software, select fastboot mode, select "App files" tab.
8. Carefully chose the update.app for recovery. Be careful, not to flash a different hardware variant (in a H60-L12 flash only H60-L12 firmware and so on). Not doing so will probably break your phone forever. The program does not check compatibility, nor the phone in this mode.
9. Open the update app by clicking right end of the line "Update file".
10 Click "Update". Program will unpack the update.app and will start to flash all the chosen img packs.
Here I got really scared, because first write was unscuccessful, I got this message: "PTABLE partition UPDATE ... FAILED
I thought that I threw away my money. But program managed really well: "Activating Backdoor: DONE"
After this step, everything went well: "Writing device finished OK"
11. Power cycle your phone. It should start normally.
12. On the dc-unlocker site they say: "Then you need to repeat flashing, but now in upgrade mode". I did not ran this step. I made a full factory reset and started OTA upgrades. Phone is now version: EMUI4.0.1_H-60-L12_6.11.1.
It has Android 6, EMUI 4.0.1.
At one moment I thought that is better to go back to a previous version and flashed an older tested firmware, it worked without any problems..
Although my experience is limited to this phone only, I recommend this solution. Please feel free to ask, I will try to answer any questions.
So the software deactivates itself after 72h?
zinko_pt said:
So the software deactivates itself after 72h?
Click to expand...
Click to collapse
Hi
The recovery process starts only after validated by the server.
Validation occurs when you have enough credits on your account, or if you already paid for that phone not more than 72 hours ago.
janos666 said:
Hi
The recovery process starts only after validated by the server.
Validation occurs when you have enough credits on your account, or if you already paid for that phone not more than 72 hours ago.
Click to expand...
Click to collapse
But is there any refund in case it doesn't work?
zinko_pt said:
But is there any refund in case it doesn't work?
Click to expand...
Click to collapse
No, there are no refunds, but if you have a phone with only firmware error and you chose the right firmware, there are big chances that the program will recover your phone.
But if security damaged, you will need factory file.
method 2 can help in 99% cases, but only if there 100% compatible file.
They have only H60-L04 factory file.
Repairing by this method, will erase phone security data (simlock, IMEI and other numbers)
You will lose all numbers!, IMEI will be 0000000000000000
You can repair missing numbers with third party software, like HCU client
You can use DC-unlocker credits on HCU client, software will require 8 credits for repair service.
Thanks. When there's no other solution it might be handy.
i'm intrested in this.
I have an Honor 6 plus pe-ul00 i can't fix the brick.
with that can i flash any firmware for my device (pe-ul00) and get it to work?
Split74 said:
i'm intrested in this.
I have an Honor 6 plus pe-ul00 i can't fix the brick.
with that can i flash any firmware for my device (pe-ul00) and get it to work?
Click to expand...
Click to collapse
Hi!
I don't see this device on the supported phones list.
You should contact their support to confirm if the program works with your device.
They are very kind and helpful. If you need a contact email, I can send in private.
Best regards,
Janos
janos666 said:
Hi
The recovery process starts only after validated by the server.
Validation occurs when you have enough credits on your account, or if you already paid for that phone not more than 72 hours ago.
Click to expand...
Click to collapse
U shouldn't need to do this to flash back to stock. Sounds like a scam
Tmobilefan906 said:
U shouldn't need to do this to flash back to stock. Sounds like a scam
Click to expand...
Click to collapse
It seems that you did not understand me.
If you read this topic you will learn that in some cases, flashing back the 4 img's will not help.
In some cases you cannot access 3 button recovery or TWRP (although you flashed it correctly), to be able to do a complete flash write.
This was the case when this program (which you call a scam!) proved a life-saver.
I am very happy that I could restore my phone because I like it very much.
janos666 said:
It seems that you did not understand me.
If you read this topic you will learn that in some cases, flashing back the 4 img's will not help.
In some cases you cannot access 3 button recovery or TWRP (although you flashed it correctly), to be able to do a complete flash write.
This was the case when this program (which you call a scam!) proved a life-saver.
I am very happy that I could restore my phone because I like it very much.
Click to expand...
Click to collapse
It was my OPINION dude. Didn't mean to offend.
Tmobilefan906 said:
It was my OPINION dude. Didn't mean to offend.
Click to expand...
Click to collapse
Yep, the SW works OK ..
First it extracts the IMG files from the UPDATE.APP - same as Huawei Update Extractor. Then it flashes all IMG files (+-) using fastboot - but here is the catch.. it uses an undocumented feature of fastboot:
fastboot.exe oem backdoor get
And then generates the necessary unlock file/sequence which it then feeds to the phone using:
fastboot.exe flash slock XXX_Unlockcode.bin
So indeed it does work - I've used it, you can go between EMUI3.1 and 4.0/0.1 no problem - if we knew how to generate the unlock file for the "backdoor" - we would be all set However we don't and the generated file changes with every "oem backdoor get" request..
But 15EUR seems almost reasonable for this (I'd prefer 10EUR hehe) - otherwise, we would need to use parted and dd the necessary partitions which is more dangerous and we don't have a large enough community of users to dump the necessary partitions..
janos666 said:
Hi!
I don't see this device on the supported phones list.
You should contact their support to confirm if the program works with your device.
They are very kind and helpful. If you need a contact email, I can send in private.
Best regards,
Janos
Click to expand...
Click to collapse
It worked! Fail on normal flash the It issued that damn BACKDOOR install and now i'm back!
Got only 2 "problems":
1. I got 2 IMEI CODES
2.I can't see all my internal storage:
I tried a wipe internal storage + factory reset with emui rec and with twrp, but nothing. TWRP say something like: Can't wipe ..data/... No such directory
Inviato dal mio PE-UL00 utilizzando Tapatalk
I will think about this issue, but a quick idea is: you could try a full firmware update from SD card with the 3 button method and a factory restore after.
Happy to hear that buddy... I threw away a honor 6 about two months ago, was stuck in fastboot for more than a month, if had it, I am sure, this would have fixed it.:crying:
Another Honor 6 saved with this method, this time a H60-L02
I guess you really threw away your money, because you can extract the update.app with huaweiupdateextractor( free ) and flash the cust.img system.img boot.img and recovery.img with adb and fastboot. But if you had the “Command not allowed error“ when you try to flash, even your software wouldnt have helped you, because it basically does the same as i explained above.
Sent from my H60-L04 using XDA-Developers Legacy app
---------- Post added at 12:24 AM ---------- Previous post was at 12:15 AM ----------
Edit: the unlock bin can be easily made by editing one current .bin, by replacing it with the current unlock code.
Sent from my H60-L04 using XDA-Developers Legacy app
I can confirm i fix my Honor 6 hard brick with Dc Phoenix
---------- Post added at 06:58 PM ---------- Previous post was at 06:57 PM ----------
Lukalion said:
I guess you really threw away your money, because you can extract the update.app with huaweiupdateextractor( free ) and flash the cust.img system.img boot.img and recovery.img with adb and fastboot. But if you had the “Command not allowed error“ when you try to flash, even your software wouldnt have helped you, because it basically does the same as i explained above.
Sent from my H60-L04 using XDA-Developers Legacy app
---------- Post added at 12:24 AM ---------- Previous post was at 12:15 AM ----------
Edit: the unlock bin can be easily made by editing one current .bin, by replacing it with the current unlock code.
Sent from my H60-L04 using XDA-Developers Legacy app
Click to expand...
Click to collapse
It was impossible for my L02 to be fixed using unbrick fuction of multi tool
You did not do the step i said in Edit
Sent from my H60-L04 using XDA-Developers Legacy app
This TWRP can decrypt data partition and you can find 1 click to root function in "advanced" menu (bottom left).
This TWRP is for EMUI 4.1 only!
Instructions:
1. Unlock bootloader and keep your unlock code in record (force flash stock ROM will re-lock the phone)
2. Turn off "Find My Phone"
3. Download the file below and unzip
4.1 Run the exe, it's Chinese UI, but you can see "...bootloader" button for unlock, "...recovery" button is for flash bootloader.
4.2 Or manually flash recovery files via fastboot
5. Root function is located at Advanced menu at bottom left button.
Download (MEGA)
or
http://www.mirrorcreator.com/files/12YBC2XZ/
Source: http://club.huawei.com/forum.php?mod=viewthread&tid=11334720&page=1&authorid=6362185
Wow, tried?
Sent from my Nexus 6 using XDA-Developers Legacy app
siggey said:
Wow, tried?
Sent from my Nexus 6 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Got my device soon, but I see screenshots of TWRP is working.
The link appears to be dead, but in the meantime I'll try a download from the forum you linked.
---------- Post added at 08:09 AM ---------- Previous post was at 07:18 AM ----------
Just flashed it, and succesfully rooted the device. Thanks for sharing.
Mvs1989 said:
The link appears to be dead, but in the meantime I'll try a download from the forum you linked.
---------- Post added at 08:09 AM ---------- Previous post was at 07:18 AM ----------
Just flashed it, and succesfully rooted the device. Thanks for sharing.
Click to expand...
Click to collapse
Glad to hear that.
I just put up the link this morning and I'll check it up after work.
If anyone was also wondering if Xposed works, I can only say that it does install, it does boot, but the phone 'settings' force closes (no message, just returns to previous window).
Steps taken:
Installed Xposed installer 3.1.1
Installed version 87 (not from recovery)
Rebooted
Reboot takes a long time, but eventually boots. Seems to work fine until I went to the phone settings and it wouldn't open.
Opened the Xposed installer again
Uninstalled (not from recovery)
Maybe results will vary with an older xposed or doing it properly from recovery, not risking it at the moment.
Mvs1989 said:
The link appears to be dead, but in the meantime I'll try a download from the forum you linked.
---------- Post added at 08:09 AM ---------- Previous post was at 07:18 AM ----------
Just flashed it, and succesfully rooted the device. Thanks for sharing.
Click to expand...
Click to collapse
I've updated the link, thanks for pointing out the error.
Just tried flashing Xposed 86 (tried 87 before) through the recovery, also disabled resource hooks in the xposed installer app.
Now everything seems to work.
For anyone that is interested .
Thank you. This worked for me.
What I did:
- unlock bootloader
- access phone bootloader with phone connected to computer
- click app's "...recovery" button and select TWRP recovery file provided with app (the installation is almost instantaneous)
- boot phone into recovery (TWRP will be in Chinese but English is available)
- root phone from TWRP advanced menu (clicking the "root" button will install supersu)
Where was this, when the 5x started development? I already flashed, and rooted my 5x, but would this tool work on that? If so, I can archive it for later use, if needed, or change it, so it could work with the 5x, since they both(at this time) have EMUI 4.1. Is it possible?
---------- Post added at 05:00 AM ---------- Previous post was at 04:55 AM ----------
Mvs1989 said:
If anyone was also wondering if Xposed works, I can only say that it does install, it does boot, but the phone 'settings' force closes (no message, just returns to previous window).
Steps taken:
Installed Xposed installer 3.1.1
Installed version 87 (not from recovery)
Rebooted
Reboot takes a long time, but eventually boots. Seems to work fine until I went to the phone settings and it wouldn't open.
Opened the Xposed installer again
Uninstalled (not from recovery)
Maybe results will vary with an older xposed or doing it properly from recovery, not risking it at the moment.
Click to expand...
Click to collapse
I heard that EMUI has a problem with xposed, it's at the start of the honor 5x forums, in development.
Is it easy to unlock bootloader?
I have not yet gotten a 6x, but will soon. Trying to plan custom rom and etc in advance. Its really great that the device has such activity!
In G7, bootloader unlock requires getting a code from Huawei website and took some time before the phone model was on the website. It also did a factory reset after applying the code for which it gave no warning for.
I imagine its similar bit Honor, seeing as Huawei is their parent.
Sent from my Huawei Ascend G7 using XDA Labs
drakenabarion said:
Is it easy to unlock bootloader?
I have not yet gotten a 6x, but will soon. Trying to plan custom rom and etc in advance. Its really great that the device has such activity!
In G7, bootloader unlock requires getting a code from Huawei website and took some time before the phone model was on the website. It also did a factory reset after applying the code for which it gave no warning for.
I imagine its similar bit Honor, seeing as Huawei is their parent.
Sent from my Huawei Ascend G7 using XDA Labs
Click to expand...
Click to collapse
Yes, it's almost the same for 6x to unlock.
reggjoo said:
Where was this, when the 5x started development? I already flashed, and rooted my 5x, but would this tool work on that? If so, I can archive it for later use, if needed, or change it, so it could work with the 5x, since they both(at this time) have EMUI 4.1. Is it possible?
---------- Post added at 05:00 AM ---------- Previous post was at 04:55 AM ----------
I heard that EMUI has a problem with xposed, it's at the start of the honor 5x forums, in development.
Click to expand...
Click to collapse
For 5X, there is only TWRP, not with the 1-click root function.
Anyone done this on a BLN-L24 yet?
I was gonna wait a while to mess with this thing but I just switched carriers and I need to try and get around the hotspot provisioning check.
jerryhou85 said:
For 5X, there is only TWRP, not with the 1-click root function.
Click to expand...
Click to collapse
Yes, but you simply have to flash SuperSU zip to root.
Andromeda_Station said:
Anyone done this on a BLN-L24 yet?
I was gonna wait a while to mess with this thing but I just switched carriers and I need to try and get around the hotspot provisioning check.
Click to expand...
Click to collapse
This one should work on all models of Honor 6x, but again, you have to take the risk...
jerryhou85 said:
This one should work on all models of Honor 6x, but again, you have to take the risk...
Click to expand...
Click to collapse
Success
Was able to find the offending files in system/app that were initiating the carrier hotspot/tethering check...deleted them and now I'm in business.
Also, if anyone is having trouble getting viper4android working (I was), there is a flashable zip in this thread that works. :good:
Andromeda_Station said:
Success
Was able to find the offending files in system/app that were initiating the carrier hotspot/tethering check...deleted them and now I'm in business.
Also, if anyone is having trouble getting viper4android working (I was), there is a flashable zip in this thread that works. :good:
Click to expand...
Click to collapse
Glad it works!
How can I lock the bootloader in case I have to use warrancy?
hanset said:
How can I lock the bootloader in case I have to use warrancy?
Click to expand...
Click to collapse
WinDroid Toolkit v3.1
I have stock rom on my Oneplus 6. After the new OTA update 9.0.5 it downloads (aprrox 94 Mb) but installation failed. After 2 tries it says download full rom. then I rebooted my device, It stuck into fastboot mode. I called customer care they flashed the device remotely, now device is booted normally but all sensors are not working like proximity, autorotate etc. by dialing *#808# engineering menu tries to self-test & calibrate sensors but it shows only grey screen. Also sensor test & CPU-z app from play store also not showing any sensors.
dear members is it possible that flashing currupted my sensor files in system, could it possible to flash sensor file.
I tried to downgrade to 9.0.4 via update from local, says downgrade not possible. I tried Beta 16 update , problem still persist.
help me guys ASAP.
try to flash with msmdownloadtool, just search "op6 unbrick tool", if no success, try to flash via fastboot persist.img (pretty common issue with Xiaomi/OnePlus that comes to my repair shop) from working OP6. good luck.
https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3903272
---------- Post added at 08:13 PM ---------- Previous post was at 08:12 PM ----------
acmerw said:
try to flash with msmdownloadtool, just search "op6 unbrick tool", if no success, try to flash via fastboot persist.img from working OP6. good luck.
Click to expand...
Click to collapse
Hah. Great minds think alike Posted the same thing
please provide details/link for these procedures.
acmerw said:
try to flash with msmdownloadtool, just search "op6 unbrick tool", if no success, try to flash via fastboot persist.img (pretty common issue with Xiaomi/OnePlus that comes to my repair shop) from working OP6. good luck.
Click to expand...
Click to collapse
I am a noob, so I don't know how to do these procedures even if I download above mentioned file (msmsdownloadtool, persist.img) or my downloaded files are compatible with my oneplus 6. Could you give me links for further details.
Thanks
divvykev said:
https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3903272
---------- Post added at 08:13 PM ---------- Previous post was at 08:12 PM ----------
Hah. Great minds think alike Posted the same thing
Click to expand...
Click to collapse
Thats what I wanted, a detailed post esp having video showing all steps. I will try this & inform you soon.
All you seniors thanks for help.
not suceeded
playxda said:
Thats what I wanted, a detailed post esp having video showing all steps. I will try this & inform you soon.
All you seniors thanks for help.
Click to expand...
Click to collapse
I download the software & do all the steps, now my oneplus 6 is booted to os 9.0.2 but the sensors still not working. Do i need flash_persist.img. if yes, where do I get it for my device & how to use it.
detials needed
playxda said:
I am a noob, so I don't know how to do these procedures even if I download above mentioned file (msmsdownloadtool, persist.img) or my downloaded files are compatible with my oneplus 6. Could you give me links for further details.
Click to expand...
Click to collapse
where do I get fastboot persist.img & how to use it. as this is the next procedure after msmsdownload tool did not solve the problem.
playxda said:
where do I get fastboot persist.img & how to use it. as this is the next procedure after msmsdownload tool did not solve the problem.
Click to expand...
Click to collapse
I think you have a faulty phone now. Probably why you had a problem to start with. Msm takes you back to factory reset. Should work but if the problem is still there looks like its hardware. ?
I have a Google pixel 1 with locked bootloader, it bootloop on installing Android Q beta. I cant downgrade to pie or oreo. Any help will be highly appreciated. Recovery and bootloader are working fine, Thanks as i await response
Verizon Google pixel bootloop with Android Q
I have the same problem. But my os is the android 10 stable version.
So, I need help too...
If your pc can recognise your device in fastboot mode you could try switching slots with either fastboot set_active A or fastboot set_active B. It should tell you what slot your in in bootloader mode then switch to the previous slot which should put you back into the previous system set up you were running.
Hope that helps
junglism93 said:
If your pc can recognise your device in fastboot mode you could try switching slots with either fastboot set_active A or fastboot set_active B. It should tell you what slot your in in bootloader mode then switch to the previous slot which should put you back into the previous system set up you were running.
Hope that helps
Click to expand...
Click to collapse
I don't understand about slot A or B but attached is everything you want to know...moreso, how do i switch slots
Okay, you are currently on slot a. Here's a simple explanation, you can also check this out on Google's developer site for more comprehensive info.
These devices have 2 slots for for the seamless update set up. One will have you're current system on it and the the other will be updated with the next OTA, once you reboot after an ota it will move onto the next slot( say from b to a) if the update doesnt work you should be able to roll back to the previous slot with the old unchanged system still in place via the fastboot command.
If you dont have ADB and fastboot on a pc you will need to install the ADB and fastboot tools from the Android developers site https://developer.android.com/studio/releases/platform-tools
Once installed and set up the ADB and fastboot and you have your device drivers set up on your PC you will be able to issue a few commands that may get you up and running again
See here for details on setting up ADB and fastboot and how to use it.
https://wiki.lineageos.org/adb_fastboot_guide.html
Good luck
junglism93 said:
Okay, you are currently on slot a. Here's a simple explanation, you can also check this out on Google's developer site for more comprehensive info.
These devices have 2 slots for for the seamless update set up. One will have you're current system on it and the the other will be updated with the next OTA, once you reboot after an ota it will move onto the next slot( say from b to a) if the update doesnt work you should be able to roll back to the previous slot with the old unchanged system still in place via the fastboot command.
If you dont have ADB and fastboot on a pc you will need to install the ADB and fastboot tools from the Android developers site https://developer.android.com/studio/releases/platform-tools
Once installed and set up the ADB and fastboot and you have your device drivers set up on your PC you will be able to issue a few commands that may get you up and running again
See here for details on setting up ADB and fastboot and how to use it.
https://wiki.lineageos.org/adb_fastboot_guide.html
Good luck
Click to expand...
Click to collapse
I tried oreo and pie update but installations was incompleted with this error like old software
Serowhite said:
I tried oreo and pie update but installations was incompleted with this error like old software
Click to expand...
Click to collapse
Forget Oreo and pie, you cannot downgrade to an earlier Android version.
Just have a read of what I suggested and if it's not any good to you have a search of the forum, it's a mine of information if you take your time and search as it's saved me many a time.
If you have working adb as it sounds like you do as youve tried downgrading then you could also try downloading the Q beta OTA image you tried or the latest Android 10 OTA image. Just make sure your ADB is the latest version and make sure the OTA file downloaded fully.
Edit: removed minor rant and tried to be a bit more helpful, rough day at the office.
junglism93 said:
Forget Oreo and pie, you cannot downgrade to an earlier Android version.
Just have a read of what I suggested and if it's not any good to you have a search of the forum, it's a mine of information if you take your time and search as it's saved me many a time.
If you have working adb as it sounds like you do as youve tried downgrading then you could also try downloading the Q beta OTA image you tried or the latest Android 10 OTA image. Just make sure your ADB is the latest version and make sure the OTA file downloaded fully.
Edit: removed minor rant and tried to be a bit more helpful, rough day at the office.
Click to expand...
Click to collapse
OTA file or full factory image; which is better?
Serowhite said:
OTA file or full factory image; which is better?
Click to expand...
Click to collapse
OTA mate, you can't flash full images as you bootloader is locked
junglism93 said:
OTA mate, you can't flash full images as you bootloader is locked
Click to expand...
Click to collapse
This is the result im getting on sideloading OTA
failed to verify whole-file signature
E: Signature verification failed
E: error: 21
Hmm! If your download completed fully and you verified the checksum then it looks like something in a partition may be corrupted causing the OTA to fail.
If your bootloader was unlocked I'd have suggested doing a full wipe and then flashing a full stock image as I've had to a few times over the years when things got borked.
All I can suggest is maybe try it again via another usb port or another lead and see if it's works or hopefully someone else will chime in and have a workaround that may get you up and running.
Might be worth searching 'ota update error 21' and try to find any info you can on resolving it in the meantime.
---------- Post added at 09:27 PM ---------- Previous post was at 09:02 PM ----------
As a last ditch you could try using the fastboot continue command, remember a few people having success using it to get things booted. Other than that I'm out of ideas
Good luck and if you do get it booted unlock your bootloader.
junglism93 said:
If your pc can recognise your device in fastboot mode you could try switching slots with either fastboot set_active A or fastboot set_active B. It should tell you what slot your in in bootloader mode then switch to the previous slot which should put you back into the previous system set up you were running.
Hope that helps
Click to expand...
Click to collapse
But that can not change slot or update with the previous version OTA package without unlock. :crying:
mingkingwm said:
But that can not change slot or update with the previous version OTA package without unlock. :crying:
Click to expand...
Click to collapse
If you have tried sideloading the same OTA image or newer and tried switching slots or any of the bits I've offered up and had no luck then have a search for 'pixel bootloop OTA' or 'bricked pixel' or 'soft bricked pixel' or similar. The search button is your friend in these circumstances, as I said before it has saved me in the past and it will probably do so again if I run into trouble with my pixel, just have a thorough read of what you find and you may find the answer to your problem.
Good luck
junglism93 said:
If you have tried sideloading the same OTA image or newer and tried switching slots or any of the bits I've offered up and had no luck then have a search for 'pixel bootloop OTA' or 'bricked pixel' or 'soft bricked pixel' or similar. The search button is your friend in these circumstances, as I said before it has saved me in the past and it will probably do so again if I run into trouble with my pixel, just have a thorough read of what you find and you may find the answer to your problem.
Good luck
Click to expand...
Click to collapse
Can i flash official Q to Verizon pixel?
Serowhite said:
Can i flash official Q to Verizon pixel?
Click to expand...
Click to collapse
Never had a Verizon device so no idea mate but if you was on the Q beta I can't see why not unless they supply a specific tag for them in the factory OTA and images?
Up to you, it's your device
junglism93 said:
Never had a Verizon device so no idea mate but if you was on the Q beta I can't see why not unless they supply a specific tag for them in the factory OTA and images?
Up to you, it's your device
Click to expand...
Click to collapse
I tried the Verizon Android 10 OTA file but its not flashing as well
Serowhite said:
I tried the Verizon Android 10 OTA file but its not flashing as well
Click to expand...
Click to collapse
No idea then mate, all I can suggest is searching through the pixel bootloop, soft bricked pixel or similar threads and hopefully you'll find something else you can try in one of them that'll get your pixel up and running again.