I have a problem with the screen rotation sensor. after a few hours the sensor stops working. When i restart the device the sensor works again for a few hours.
I set up my device right after the purchase with the lineageos, with the stock rom I have not yet tested, but with superior os (9.0), I have the same problem. Does anyone have an idea how I could solve the problem? Is it possibly a hardware problem?
I have also tested with the firmwares 10.0.3, 10.0.9, 10.0.12 and 10.0.13.
Not exactly a hardware problem. I had the same issue on LineageOS and told the developer to look into the issue but he has abandoned the ROM so we're not gonna get a fix for that. Some Pie ROMs break the sensors of the device. This is not limited to the rotation sensor but also including the proximity sensor and some camera issues. I suggest flashing Oreo in EDL mode and then using another ROM like MIUI (in which everything works the way they should), if you are trusting the developers of that ROM. Cheers.
Thanks for your help. Miui is not an option for me. I operate my mobile without Google services, so Gapps must not be pre-installed. POSP v3.1 would be my first alternative to Lineageos, but I hope someone will develop it further.
Can you still help me how exactly I flash in EDL mode?
counti said:
Thanks for your help. Miui is not an option for me. I operate my mobile without Google services, so Gapps must not be pre-installed. POSP v3.1 would be my first alternative to Lineageos, but I hope someone will develop it further.
Can you still help me how exactly I flash in EDL mode?
Click to expand...
Click to collapse
Download and install MiFlash 20170425, Qualcomm Drivers, ADB drivers and platform tools.
Download stock fastboot images. Extract them in root drive (suck as D:/). Fastboot / EDL do not want folder names with spaces.
Put your phone into fastboot mode (by long pressing Pwr + vol- until Fastboot Mode logo appears)
Type in Command Prompt or PowerShell: fastboot oem edl
Phone will turn black and have blinking LED.
Open MiFlash. Locate the extracted fastboot images folder.
Click refresh. Should display S/N of your phone and its status.
Select 'clean all'. Do NOT select Clean + Lock, as it will lock bootloader or make things worse.
Start flashing by clicking flash button, and wait patiently.
When it display 'success', long press power until you can see 'Device Unlock' warning screen or AndroidOne splash screen.
And you're basically done EDL'ing phone.
counti said:
Thanks for your help. Miui is not an option for me. I operate my mobile without Google services, so Gapps must not be pre-installed. POSP v3.1 would be my first alternative to Lineageos, but I hope someone will develop it further.
Can you still help me how exactly I flash in EDL mode?
Click to expand...
Click to collapse
There are a lot of ROMs you can try. Most of them are more up to date compared to LineageOS. Superior OS, ViperOS, Resurrection Remix are your options. Can you tell me how did you de-googled your phone? Don't you have problems with GPS or other stuff without Google Services on your phone ?
thanks for your help, i'll try to do that in the next weeks
RFD80M-75679 said:
Download and install MiFlash 20170425, Qualcomm Drivers, ADB drivers and platform tools.
Download stock fastboot images. Extract them in root drive (suck as D:/). Fastboot / EDL do not want folder names with spaces.
Put your phone into fastboot mode (by long pressing Pwr + vol- until Fastboot Mode logo appears)
Type in Command Prompt or PowerShell: fastboot oem edl
Phone will turn black and have blinking LED.
Open MiFlash. Locate the extracted fastboot images folder.
Click refresh. Should display S/N of your phone and its status.
Select 'clean all'. Do NOT select Clean + Lock, as it will lock bootloader or make things worse.
Start flashing by clicking flash button, and wait patiently.
When it display 'success', long press power until you can see 'Device Unlock' warning screen or AndroidOne splash screen.
And you're basically done EDL'ing phone.
Click to expand...
Click to collapse
All I have done is not to install gapps
GPS runs without problems without Google services (I use osmand for navigation), Whatsapp I don't use, I have Threema, you can set polling.
Because the Google camera is much better than Open Camera or the standard camera from Lineageos I installed MicroG, so the Google camera works.
marstonpear said:
There are a lot of ROMs you can try. Most of them are more up to date compared to LineageOS. Superior OS, ViperOS, Resurrection Remix are your options. Can you tell me how did you de-googled your phone? Don't you have problems with GPS or other stuff without Google Services on your phone ?
Click to expand...
Click to collapse
Hello, a while ago I had this same problem, but I was successful because my cell phone got wet on the top (where I imagine all the sensors are). From there accelerometer, gyroscope, compass, proximity and light stopped working.
Yesterday I was trying to install DerpFest ROM and I did not succeed, I tried it more or less 15 times and threw myself into bootloop, so I reinstalled stock ROM Pie 10.0.16 and the sensors from nowhere started working again, but after a while, When charging, the device rebooted only 2 times. After such reboot I deactivated the sensors again.
I have tried to fix it by reinstalling Stock ROM and cleaning the system files through the TWRP "Repair" option, but it does not work.
Did anyone find any solution for this?
The solution for this problem is the kernel. The installation of POSP Rom solved the problem, probably because of the included kernel. Actually i have the lineageos rom with the butterfly kernel and it works also, without this kernel i had also this problem with lineageos.
Related
I have a bone stock 2013 Nexus 7 32 Gb Wifi, never had a problem with it. A few weeks ago, it notifies me of an update (Lollipop) so I apply it. Nothing but problems since then. It was very laggy and would glitch every few seconds while playing video (either local files or streamed over Plex, both had same issue). Sometimes when I'd wake it from sleep, the screen would look like an old CRT TV with static (except it wasn't moving, it was a fixed image). It would hang like this for seconds or sometimes minutes. Rebooting would usually resolve this for a while.
Tried a few 'lollipop tuning' tweaks, but when these failed to fix the video glitching and lagginess, I decided to revert to kitkat and followed an online tutorial (exactly like the one here except it had me install a standalone ADB/fastboot instead of full SDK) . No problem installing USB driver or setting nexus into USB mode. No problem getting it into fastboot mode and "fastboot devices" correctly listed the device, and "oem unlock" appeared to work fine as well. Running the flash-all batch file also seemed to go normally. But now my device is even worse than before:
- won't boot/run normally... no boot-up logo or video ever displays (or if it does, it's just a partial static image). Appears to get to a 'welcome' screen but the display is all messed (part of the screen is just repeated several times, so you can't see the entire screen). Unresponsive to touch, though it will make some sounds when you press in certain areas, but the display never changes. If I sleep it and wake it up, it shows the 'CRT static' mentioned above for many seconds before showing slowing showing the tiled/corrupted welcome screen. I can access the nexus' file system over USB on my PC even while it's in this borked state.
- display is now blank when getting into fastboot mode... i can time pushing the down-volume and power button so I know I am in fastboot mode ('fastboot devices' correctly lists the device) but the display is now completely black (not on, no backlight) in this mode.
I tried flashing to factory 4.4.4, 4.3, and 4.2 (always using 2013 wifi images) and it doesn't make a difference. Same results. Is there some bit of code that doesn't get reflashed during this reset that could explain why I'm having these issues? Any advice how to fix?
flyingsherpa said:
I have a bone stock 2013 Nexus 7 32 Gb Wifi, never had a problem with it. A few weeks ago, it notifies me of an update (Lollipop) so I apply it. Nothing but problems since then. It was very laggy and would glitch every few seconds while playing video (either local files or streamed over Plex, both had same issue). Sometimes when I'd wake it from sleep, the screen would look like an old CRT TV with static (except it wasn't moving, it was a fixed image). It would hang like this for seconds or sometimes minutes. Rebooting would usually resolve this for a while.
Tried a few 'lollipop tuning' tweaks, but when these failed to fix the video glitching and lagginess, I decided to revert to kitkat and followed an online tutorial (exactly like the one here except it had me install a standalone ADB/fastboot instead of full SDK) . No problem installing USB driver or setting nexus into USB mode. No problem getting it into fastboot mode and "fastboot devices" correctly listed the device, and "oem unlock" appeared to work fine as well. Running the flash-all batch file also seemed to go normally. But now my device is even worse than before:
- won't boot/run normally... no boot-up logo or video ever displays (or if it does, it's just a partial static image). Appears to get to a 'welcome' screen but the display is all messed (part of the screen is just repeated several times, so you can't see the entire screen). Unresponsive to touch, though it will make some sounds when you press in certain areas, but the display never changes. If I sleep it and wake it up, it shows the 'CRT static' mentioned above for many seconds before showing slowing showing the tiled/corrupted welcome screen. I can access the nexus' file system over USB on my PC even while it's in this borked state.
- display is now blank when getting into fastboot mode... i can time pushing the down-volume and power button so I know I am in fastboot mode ('fastboot devices' correctly lists the device) but the display is now completely black (not on, no backlight) in this mode.
I tried flashing to factory 4.4.4, 4.3, and 4.2 (always using 2013 wifi images) and it doesn't make a difference. Same results. Is there some bit of code that doesn't get reflashed during this reset that could explain why I'm having these issues? Any advice how to fix?
Click to expand...
Click to collapse
So your bootloader is blank right? I would flash a new bootloader asap! And see if that fixes anything
noahvt said:
So your bootloader is blank right? I would flash a new bootloader asap! And see if that fixes anything
Click to expand...
Click to collapse
I have to confess my ignorance here... I'm brand new to flashing android like this so I don't know the answer to your question. If part of tutorial I followed blanks out the bootloader (and doesn't write something in?)... then you're probably right. I shall look into this more tonight when I'm at home with the nexus. Thanks for at least giving me something to look into, that's exactly what I was hoping for!
This sounds more like a hardware issue than software to me. See if you can get a warranty repair or replacement.
From another thread by a user with a blank screen like yours:
Asus_USA said:
a7medmo7eb - We're very sorry to hear of this. Kindly email us at [email protected] with this copied problem description along with the serial number of your tablet and we will do our best to provide you with troubleshooting and servicing options.
If you have any further questions, comments or concerns please do not hesitate to let us know. We will be more than happy to assist you. Once again, thank you for choosing ASUS products and services.
Thank you.
-In Search of Incredible-
Technical Support Department
http://www.asus.com :: http://service.asus.com/
Click to expand...
Click to collapse
nhizzat said:
This sounds more like a hardware issue than software to me. See if you can get a warranty repair or replacement.
From another thread by a user with a blank screen like yours:
Click to expand...
Click to collapse
Thanks, you're probably right. I did read up to understand all this stuff a bit more, so I know it's not lack of a bootloader or anything. All img files install just fine, so my pc can talk to the nexus, just the screen is all wonky no matter what i do.
Unfortunately I bought this 1.5 years ago so I don't think it's under warranty anymore. Everything was fine until I updated to Lollipop! Seems a big coincidence that I had a hardware failure at the same time as that update... I feel like Google ruined my tablet...
There is a bug where sometimes when you unlock the bootloader it zeros out the data partition. This might be the cause of your problem. It happened to me when I unlocked mine and I got stuck in a bootloop where it kept booting into recovery then shutting off. I fixed the problem by using fastboot to format data. Also, the flashall script didnt work for me. I put all the .img files in the same folder as fastboot then used these commands.
fastboot format data
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
after this I booted into recovery and did a factory reset for good measure and the problem was fixed. This may solve your problem. It may also be possible that you got a bad download. I hope this helps you
Masterchief87 said:
There is a bug where sometimes when you unlock the bootloader it zeros out the data partition. This might be the cause of your problem. It happened to me when I unlocked mine and I got stuck in a bootloop where it kept booting into recovery then shutting off. I fixed the problem by using fastboot to format data. Also, the flashall script didnt work for me. I put all the .img files in the same folder as fastboot then used these commands.
fastboot format data
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
after this I booted into recovery and did a factory reset for good measure and the problem was fixed. This may solve your problem. It may also be possible that you got a bad download. I hope this helps you
Click to expand...
Click to collapse
Hmm, thanks for the idea, but fastboot wouldn't do "format data", giving me the error: Formatting is not supported for filesystem with type ' '
Googling that makes it not look good. Weird, thing is, it still technically boots up, just the screen is so wonky you can't see where you are or interact with it properly. Not sure what else to try (opening it up and re-seating touchscreen cables?).
Hello everybody !
Ok, I am use to not ask any help, and to find out by myself. But I have to admit I don't have any idea remaining to solve this problem.
Let me explain you the situation :
I explain everything with details to not waste your time when you will help me !
When I first bought my Zenfone, everything worked properly. Then, I decided to flash a Custom ROM (to remove the bloatware, and to get the others optimizations). So what I did :
- I unlocked the bootloader,
- I flashed TWRP,
- I installed my custom ROM (SuperZen R15, super clean install) => at this moment, everything is working perfectly,
- I installed a custom Kernel (ProjectT, v56) by fastboot => here we are, the problem just appeared.
At this moment, the WiFi issues appear. When I boot the phone, I can turn on the WiFi (in most cases), then, WiFi just turn off. It is impossible to activate it again. In the best case, I can switch on/off the WiFi, but as soon as I download something, the WiFi just turn off immediately. Often, I just don't detect any network. In the worse case, it is impossible to activate again the WiFi, the ON/OFF button is grey.
So here is what I tried to get it back :
1) put the standard kernel with my TWRP backup => no success
2) flash another ROM (CM12, Paranoid Android, Barebone,...etc) => no success
3) flash my whole TWRP backup (system + kernel) => no success
4) flash the official Asus ROM (recovery.img, system.img, boot.img, droidboot.img) => no success
At the moment, I started thinking that maybe the WiFi just "forgot" my WPA key. So I modified the build.prop :
5) modification of the build.prop by adding the line ro.securestorage.support=false (instead of "true") => no success
6) flash the last Asus update 2.20.40... => no success.
...
I haven't any idea remaining !So I need your help ! This problem seems very standard, but I just couldn't find any solution yet !
P.S : I almost forgot. I talked about the wiFi signal, but it is exactly the same for the bluetooth signal : working on first boot, then when I use it, it just stop working and disconnect itself, and then, impossible to activate it again (grey button)
=> My last idea was to flash the radio directly by TWRP, but I didn't find any radio files for the zenfone 2...
Many thanks for your help, and thank you for reading everything !!
Max
Up !
BackDraft647 said:
Up !
Click to expand...
Click to collapse
Try setting your phone as a wifi hotspot. If other devices are able to detect your device, it is a software issue. Or else, you might have to book an appointment with the Asus service center
[email protected] said:
Try setting your phone as a wifi hotspot. If other devices are able to detect your device, it is a software issue. Or else, you might have to book an appointment with the Asus service center
Click to expand...
Click to collapse
You're such a genius ! I will try this evening ! Thanks a lot !
Didn't do anything. It's not working. I was thinking my wifi was just broken, but something creepy happened this morning. The Wi-Fi worked again (I downloaded one thing to be sure !) and then... My phone froze, and reboot... Is the devil inside my phone ??
SOLVED ! If someone has the same problem, just flash the stock ROM via ADB Sideload !
Step by step :
1) You go here, and download your version of the stock ROM : http://www.asus.com/fr/Phones/ZenFone_2_ZE551ML/HelpDesk_Download/
2) (If fastboot/adb drivers are installed) Go into your recovery (Advanced in TWRP)
3) Connect the phone to the PC, type WINDOWS + R , enter 'cmd'
4) Go into your firmware directory you just downloaded, and type : adb sideload 'thenameofthefirmwarefile'.zip
5) Wait (a loooong time), and here we go, reboot, and your phone work again.
BackDraft647 said:
SOLVED ! If someone has the same problem, just flash the stock ROM via ADB Sideload !
Step by step :
1) You go here, and download your version of the stock ROM :
2) (If fastboot/adb drivers are installed) Go into your recovery (Advanced in TWRP)
3) Connect the phone to the PC, type WINDOWS + R , enter 'cmd'
4) Go into your firmware directory you just downloaded, and type : adb sideload 'thenameofthefirmwarefile'.zip
5) Wait (a loooong time), and here we go, reboot, and your phone work again.
Click to expand...
Click to collapse
can you tell me what firmware you used exactly? because i tried to flash the first one, from the asus page.
But it says that i have a newest build and it doesn`t lets me past trough the installing part.
I am also having troubles with my wifi and i would like to fix it
Hello ! I don't remember exactly, I went on a website and selected the right version for my country ! But my problem wasn't solve at all actually... I brought my phone to the store, and they told me my motherboard was just burnt. They changed everything, and now it works like a charm ! Be careful with the custom kernel, I'm pretty sure that's how my phone broke (I'm very careful with batteries,...etc)
Well thanks anyway. I will try to take the phone to te oficial ASUS services from my country but i don´t think they give a new one. I live in Uruguay and this cellphone is not at sale over here
Does sideloading the firmware wipe your apps? Or is every thing still there when its done?
Sent from my ASUS_Z00AD using Tapatalk
I'm sorry if the post is not in the right place.
I own a z2 force that turned itself off and the rear camera did not work.
Putting the "power low" message on the recovery screen, even when the full charge appeared, after a time off "power ok" was displayed.
One moment he did not call any more and I tried bootloader, but without being able to activate usb debugging (my fatal error!), Now the message "your device is corrupted. It can not be trusted and it does not boot" and I can not unlock bootloader nor flash a new rom to boot the device.
obs: camera and battery problems appeared after the upgrade via ota to 8.0 actions
Solved.
eriton carlos said:
I'm sorry if the post is not in the right place.
I own a z2 force that turned itself off and the rear camera did not work.
Putting the "power low" message on the recovery screen, even when the full charge appeared, after a time off "power ok" was displayed.
One moment he did not call any more and I tried bootloader, but without being able to activate usb debugging (my fatal error!), Now the message "your device is corrupted. It can not be trusted and it does not boot" and I can not unlock bootloader nor flash a new rom to boot the device.
obs: camera and battery problems appeared after the upgrade via ota to 8.0 actions
Click to expand...
Click to collapse
I was able to start the device after hours looking for a solution, now I'm flashing a new rom to try to fix the camera problem and automatic shutdown.
How do you solve it?
I usually buy second hand Motorola phones (also this ATT Z2F), but I've never met the problem on individual hardwares yet (like camera, fingerprint sensor). Almost errors can be solved via flashing a right firmware. I think you can now flash fw via Lenovo Moto Smart Assistant (LMSA). If you use flashall.bat method, just take a look at the xml file and compare it to the content of flashall.bat (two types can be opened by Notepad, Notepad++ is recommended). The xml one shows what will be flashed.
For example: in the xml one has oem.img_sparsechunk.0-1-2, but in flashall.bat only has: fastboot flash oem oem.img
If you continue, your phone won't boot.
You have to edit flashall.bat:
fastboot flash oem oem.im_sparsechunk.0
fastboot flash oem oem.im_sparsechunk.1
fastboot flash oem oem.im_sparsechunk.2
Save and continue your works.
The xml is the standard file for RSD Lite. But, RSD seems not to be supported on recent PC hardwares, so step-by-step fastboot or flashall.bat is recently used. Therefore, just take a look before flashsing (other preparations won't be mentioned here). You should flash the equal or higher version to your current fw version on your phone.
Hope this works for you all.
i'm facing same problem,
eriton carlos said:
I was able to start the device after hours looking for a solution, now I'm flashing a new rom to try to fix the camera problem and automatic shutdown.
Click to expand...
Click to collapse
how you get repaired your phone?
Hello,
So the good news is - apparently we can unlock Kirin 970 now. I did the hardware testpoint mode with the HCU Client and it worked just fine! I was replacing the battery anyway so I already had access to the motherboard. The question now is - what happened to LineageOS ROMs? Looks like they just deleted all of them.
Is there anybody out there with one of them on their HDD willing to share? Google cached website is showing two of them:
lineage-16.0-20210211-nightly-charlotte-signed.zip 2/11/21
lineage-16.0-20210204-nightly-charlotte-signed.zip 2/4/21
I'm gonna try to build a custom LineageOS 18.1 (Android 11) soon as well.
Thanks.
RafBB said:
Hello,
So the good news is - apparently we can unlock Kirin 970 now. I did the hardware testpoint mode with the HCU Client and it worked just fine! I was replacing the battery anyway so I already had access to the motherboard. The question now is - what happened to LineageOS ROMs? Looks like they just deleted all of them.
Is there anybody out there with one of them on their HDD willing to share? Google cached website is showing two of them:
lineage-16.0-20210211-nightly-charlotte-signed.zip 2/11/21
lineage-16.0-20210204-nightly-charlotte-signed.zip 2/4/21
I'm gonna try to build a custom LineageOS 18.1 (Android 11) soon as well.
Thanks.
Click to expand...
Click to collapse
Here you are
lineage-16.0-20210211-nightly-charlotte-signed.zip
drive.google.com
RafBB said:
Hello,
So the good news is - apparently we can unlock Kirin 970 now. I did the hardware testpoint mode with the HCU Client and it worked just fine! I was replacing the battery anyway so I already had access to the motherboard. The question now is - what happened to LineageOS ROMs? Looks like they just deleted all of them.
Is there anybody out there with one of them on their HDD willing to share? Google cached website is showing two of them:
lineage-16.0-20210211-nightly-charlotte-signed.zip 2/11/21
lineage-16.0-20210204-nightly-charlotte-signed.zip 2/4/21
I'm gonna try to build a custom LineageOS 18.1 (Android 11) soon as well.
Thanks.
Click to expand...
Click to collapse
Are you use EMUI 9.1 to unlock Bootloader ?
RafBB said:
Hello,
So the good news is - apparently we can unlock Kirin 970 now. I did the hardware testpoint mode with the HCU Client and it worked just fine! I was replacing the battery anyway so I already had access to the motherboard. The question now is - what happened to LineageOS ROMs? Looks like they just deleted all of them.
Is there anybody out there with one of them on their HDD willing to share? Google cached website is showing two of them:
lineage-16.0-20210211-nightly-charlotte-signed.zip 2/11/21
lineage-16.0-20210204-nightly-charlotte-signed.zip 2/4/21
I'm gonna try to build a custom LineageOS 18.1 (Android 11) soon as well.
Thanks.
Click to expand...
Click to collapse
Here is my p20 pro , can I unlock the Bootloader ?
ArthurTsai said:
Here you are
lineage-16.0-20210211-nightly-charlotte-signed.zip
drive.google.com
Click to expand...
Click to collapse
Awesome! Thanks a lot. I've found an UNOFFICIAL rom yesterday and flashed it, but looks like I'll be doing it all over again today with this one.
ArthurTsai said:
Are you use EMUI 9.1 to unlock Bootloader ?
Click to expand...
Click to collapse
Ok so here was the process:
1) Backed up all my data from the device (CLT-L29)
2) Factory reset the device
3) I used Huawei Hisuite software to rollback as far (BACK) as I could. It actually let me downgrade to EMUI 8.
4) Installed HCU and DC Phoenix (timed 72 hour license for both was like 20 euro)
5) Installed NECESSARY drivers on my Windows 10 machine (HUAWEI USB COM 1.0) for the testpoint
6) I opened the phone (I wanted to replace the battery anyway). Unscrew a couple of screws and take a shield to get to the pad.
7) With the phone completely off, short the testpad to ground (I used tweezers) and plug in the USB cable while still shorting out that pad. (USB cable that is connected to your Windows machine that is). Your phone screen will stay completely OFF, but you should hear an USB "ding" sound in you windows machine. Go to the device manager and check for HUAWEI USB COM 1.0 (Your Port). If you don't see it it won't work.
8) Fire up HCU Client, check account, select "Fastboot/XLoader (Hisilicon only)" on phone connection mode.
9) Go to the "Fastboot/Xloader" tab and select CPU (for me Kirin970_T2_A8.1_V5) worked fine.
10) Click Read phone info button, you'll see a progress bar on the bottom, it should take like 2 minutes
11) If everything went fine you'll see a log on the right with your unlock code in it
12) You can unlock it from that software, select "Bootloader lock: unlock", and "Write bootloader code" I also selected "Erase Huawei ID" and click "Repair" button. It will be quick. And that's it!
Now, flashing a custom ROM was a pain. Apparently most of them REQUIRE EMUI 9.0.0.159 (159 is the KEY!). You must get the original firmware and flash it with DC Phoenix. After that the process went something like this...
1) Put the phone in fastboot/rescue mode (hold the volume down button wile inserting USB cable with the phone off)
2) Flash TWRP for charlotte with fastboot from your PC
3) Restart phone into RECOVERY (TWRP) mode
4) Sideload your rom.ZIP file (Lineage for example)
5) Sideload google apps
6) Sideload factory camera app (honestly its the best for that phone)
7) Restart the bootloader (you will be in the fastboot mode again)
8) Upload the ORIGINAL recovery image (it wont boot if you dont do it) you can revert to TWRP after the first boot
9) Go into Huawei recovery mode (power+volume up)
10) Wipe/factory reset
11) Restart and you are done! (now you can flash TWRP again if you want)
It took me an entire day of work to figure it out. All the info (steps) is available online including the location of the test pad and disassembly of the phone. Here's an awesome guide to flashing Lineage (https://depl0y.com/posts/P20-Pro-LineageOS-Guide/). One thing I've noticed if you try to use HiSuite AFTER you unlocked your bootloader it WILL lock it again. I had to do it twice while I was trying to get EMUI 9.0.0.159. The best way was to use DC Phoenix and ROM from androidhost.ru.
Anyway after all that I now have an unlocked P20 Pro with stock android. It's bloatware free and runs great. So far no major issues with the ROM.
RafBB said:
Ok so here was the process:
1) Backed up all my data from the device (CLT-L29)
2) Factory reset the device
3) I used Huawei Hisuite software to rollback as far (BACK) as I could. It actually let me downgrade to EMUI 8.
4) Installed HCU and DC Phoenix (timed 72 hour license for both was like 20 euro)
5) Installed NECESSARY drivers on my Windows 10 machine (HUAWEI USB COM 1.0) for the testpoint
6) I opened the phone (I wanted to replace the battery anyway). Unscrew a couple of screws and take a shield to get to the pad.
7) With the phone completely off, short the testpad to ground (I used tweezers) and plug in the USB cable while still shorting out that pad. (USB cable that is connected to your Windows machine that is). Your phone screen will stay completely OFF, but you should hear an USB "ding" sound in you windows machine. Go to the device manager and check for HUAWEI USB COM 1.0 (Your Port). If you don't see it it won't work.
8) Fire up HCU Client, check account, select "Fastboot/XLoader (Hisilicon only)" on phone connection mode.
9) Go to the "Fastboot/Xloader" tab and select CPU (for me Kirin970_T2_A8.1_V5) worked fine.
10) Click Read phone info button, you'll see a progress bar on the bottom, it should take like 2 minutes
11) If everything went fine you'll see a log on the right with your unlock code in it
12) You can unlock it from that software, select "Bootloader lock: unlock", and "Write bootloader code" I also selected "Erase Huawei ID" and click "Repair" button. It will be quick. And that's it!
Now, flashing a custom ROM was a pain. Apparently most of them REQUIRE EMUI 9.0.0.159 (159 is the KEY!). You must get the original firmware and flash it with DC Phoenix. After that the process went something like this...
1) Put the phone in fastboot/rescue mode (hold the volume down button wile inserting USB cable with the phone off)
2) Flash TWRP for charlotte with fastboot from your PC
3) Restart phone into RECOVERY (TWRP) mode
4) Sideload your rom.ZIP file (Lineage for example)
5) Sideload google apps
6) Sideload factory camera app (honestly its the best for that phone)
7) Restart the bootloader (you will be in the fastboot mode again)
8) Upload the ORIGINAL recovery image (it wont boot if you dont do it) you can revert to TWRP after the first boot
9) Go into Huawei recovery mode (power+volume up)
10) Wipe/factory reset
11) Restart and you are done! (now you can flash TWRP again if you want)
It took me an entire day of work to figure it out. All the info (steps) is available online including the location of the test pad and disassembly of the phone. Here's an awesome guide to flashing Lineage (https://depl0y.com/posts/P20-Pro-LineageOS-Guide/). One thing I've noticed if you try to use HiSuite AFTER you unlocked your bootloader it WILL lock it again. I had to do it twice while I was trying to get EMUI 9.0.0.159. The best way was to use DC Phoenix and ROM from androidhost.ru.
Anyway after all that I now have an unlocked P20 Pro with stock android. It's bloatware free and runs great. So far no major issues with the ROM.
Click to expand...
Click to collapse
Things are not that simple. The HiSuite on Mac have been updated.
I can't find the button that can roll back or check for update after this.
Maybe I should try HiSuite on Windows.
I suddenly remembered that I cannot use HiSuite Windows version to roll back to EMUI 8 , but I can roll back to EMUI 9. Maybe I can roll back to EMUI 8 from EMUI 9. Needing roll back twice ?
ArthurTsai said:
I suddenly remembered that I cannot use HiSuite Windows version to roll back to EMUI 8 , but I can roll back to EMUI 9. Maybe I can roll back to EMUI 8 from EMUI 9. Needing roll back twice ?
Click to expand...
Click to collapse
You *should be able to unlock it with EMUI 9. I rolled it back to 8, just to find out later on I need 9.0.0.159 anyway. So I used HiSuite to update it to 9 - but it wasn't the version I wanted and also doing this in HiSuite removed my bootloader code, so I ended up using HCU Client on EMUI 9 and it worked just fine. After that I used DC Phoenix to flash the 9.0.0.159 (bootloader stayed unlocked). It was a pain, but yeah you SHOULD be able to unlock it with EMUI9.
ArthurTsai said:
I suddenly remembered that I cannot use HiSuite Windows version to roll back to EMUI 8 , but I can roll back to EMUI 9. Maybe I can roll back to EMUI 8 from EMUI 9. Needing roll back twice ?
Click to expand...
Click to collapse
Here's a log from unlocking 9.0.0.168...
Just to let you know that official ROM (lineage-16.0-20210211-nightly-charlotte-signed.zip) is not working on my P20 Pro. It crashes on the first boot. I'm back with (lineage-16.0-20190217_125340-UNOFFICIAL-charlotte.zip) I believe it was made made by LuK1337. Works great. I use it with open gapps pico version.
guys, this is p20 non-pro forum.
why are you discussing this here?
I work for a little repair shop in my village. A customer brought in a phone - got it for his son (14) for his birthday and let him set it all up including making the google account.
The reason why it was brought in was that son forgot the pattern. Asked if we can possibly unlock it or at least recover the photos - we said that 99% that the info will be lost, but we'll see what can be done.
Tried a lot of stuff, but to no avail. Now I'm just trying to reset the phone and wipe it clean but that seems more difficult that it should be. Not sure if it's some protection that Nokia has put in place or what, but seems to be even harder that wiping an iPhone.
Problems I'm facing - can't enter recovery mode.
Only thing I can access is fastboot.
In the CMD it only recognizes fastboot commands but not adb ones.
Using TFM Tool Pro 2.0 I can force to restart it and go into recovery, but no options show up (apparently you have to quickly push volume up and power button when the little broken Android symbol is showing on the screen and the options should come up, but nothing's happening)
Sorry if I've left any info out, but need any suggestions what could be done, what am I missing.
P.s. Quite new to the whole ADB and Fastboot thing.
Used:
Windows 10, Nokia G10
Have a MacBook and a Linux computers available as well if that changes anything. Thanks in advance.
Did follow the instructions here: https://forum.xda-developers.com/t/how-to-enter-recovery-mode-on-nokia-g10-g20.4353903/
Edit:
The command "fastboot reboot recovery" can't find the device, but can do the same thing with the app mentioned above. And holding or pressing the volume up + power button only turns the phone off or if I just press them, no matter for how long, it does absolutely nothing.
Edit2:
Tried the Reboot2Recovery tool - does absolutely nothing (waiting for the device to connect although the fastboot devices in CMD does see the device)
Use the TFM (Pro.7z tool )for Windows can help you
brok5 said:
Use the TFM (Pro.7z tool )for Windows can help you
Click to expand...
Click to collapse
I believe that's the tool I mentioned in the comment already or is it something different?
TomassD said:
I believe that's the tool I mentioned in the comment already or is it something different?
Click to expand...
Click to collapse
This tool will solve your problem, just search for the explanation on YouTube.
TFM will not work. Please download the tool I developed here https://forum.xda-developers.com/attachments/reboot2recoveryv5-zip.5494089/. Please reply here for any help if needed.
TomassD said:
I work for a little repair shop in my village. A customer brought in a phone - got it for his son (14) for his birthday and let him set it all up including making the google account.
The reason why it was brought in was that son forgot the pattern. Asked if we can possibly unlock it or at least recover the photos - we said that 99% that the info will be lost, but we'll see what can be done.
Tried a lot of stuff, but to no avail. Now I'm just trying to reset the phone and wipe it clean but that seems more difficult that it should be. Not sure if it's some protection that Nokia has put in place or what, but seems to be even harder that wiping an iPhone.
Problems I'm facing - can't enter recovery mode.
Only thing I can access is fastboot.
In the CMD it only recognizes fastboot commands but not adb ones.
Using TFM Tool Pro 2.0 I can force to restart it and go into recovery, but no options show up (apparently you have to quickly push volume up and power button when the little broken Android symbol is showing on the screen and the options should come up, but nothing's happening)
Sorry if I've left any info out, but need any suggestions what could be done, what am I missing.
P.s. Quite new to the whole ADB and Fastboot thing.
Used:
Windows 10, Nokia G10
Have a MacBook and a Linux computers available as well if that changes anything. Thanks in advance.
Did follow the instructions here: https://forum.xda-developers.com/t/how-to-enter-recovery-mode-on-nokia-g10-g20.4353903/
Edit:
The command "fastboot reboot recovery" can't find the device, but can do the same thing with the app mentioned above. And holding or pressing the volume up + power button only turns the phone off or if I just press them, no matter for how long, it does absolutely nothing.
Edit2:
Tried the Reboot2Recovery tool - does absolutely nothing (waiting for the device to connect although the fastboot devices in CMD does see the device)
Click to expand...
Click to collapse
Please use version 5.
brok5 said:
This tool will solve your problem, just search for the explanation on YouTube.
Click to expand...
Click to collapse
I watch videos from 10 different guys - they use the tool to boot into recovery and then choose the reset option by pressing volume up + power, but my problem is that when I do that no options come up.
mvikrant97 said:
Please use version 5.
Click to expand...
Click to collapse
I tried version 4 and that did nothing at all. Did not even reboot into recovery.
Hesitant to use version 5 as multiple users complained that the phone stopped loading. Would not want to brick the phone.
mvikrant97 said:
Please use version 5.
Click to expand...
Click to collapse
Just tried even the version 5. It does not see the device
TomassD said:
Just tried even the version 5. It does not see the device
Click to expand...
Click to collapse
No it should not happen and it is just generic script with fastboot commands and nothing else.
If you use Windows PC I can help you with a remote software like teamviewer or anydesk.
I too had/have similar issues with the "waiting for device.."
I resolved it by removing all the drivers and then downloading what I believe is likely to be a more up to date version from here:
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
I also downloaded their version of adb/fastboot in the standalone package from here:
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Together these two resolved my "waiting for device..." issues and I can consistently get through to the Android "no command" screen.
My problem is also that the power plus volume up button no longer seem to work. I downloaded the reboot2recoveryv5-zip batch file and read the thread which produced it but it would appear the method no longer works either. I can, using "fastboot reboot fastboot", get the fastbootd menu to open but it has no option to exit back down into the recovery menu.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Reboot to bootloader simply brings me back to the "FASTBOOT mode..." screen.
I contacted Nokia support and they were as much help as wet socks.
Although it does not help my situation they did suggest something which may help the OP:
****************************************************************************************************
In order to fix the issue that you face with your device please follow the steps below:
1. You should login to the Gmail (that is used on the device) on a PC.
2. Click on "Find your phone"
3. Choose the proper device from the list of devices that will appear. (These are the devices that are using the same Gmail account)
4. Confirm the password of the Gmail once again.
5. Click on "Consider erasing your data" >"Yes, erase"
After the final click a remote factory reset if performed and the device will loose the data unless it was stored in a cloud, but this will remove the pattern and the issue will be solved!
****************************************************************************************************
In my case I don't even have a Google account set up on the phone yet so that didn't help.
Since Nokia refused to help I am forced to turn to you guys for any help/ideas? In the meantime I continue to try various button combinations in desperation.
This is my first, and my last, Nokia. It's also my first new phone in a long time, is this type of factory reset prevention common among manufacturers? I ask as I consider my replacement for this phone if I can't ever manage to reset it.
Peterbd said:
I too had/have similar issues with the "waiting for device.."
I resolved it by removing all the drivers and then downloading what I believe is likely to be a more up to date version from here:
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
I also downloaded their version of adb/fastboot in the standalone package from here:
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Together these two resolved my "waiting for device..." issues and I can consistently get through to the Android "no command" screen.
My problem is also that the power plus volume up button no longer seem to work. I downloaded the reboot2recoveryv5-zip batch file and read the thread which produced it but it would appear the method no longer works either. I can, using "fastboot reboot fastboot", get the fastbootd menu to open but it has no option to exit back down into the recovery menu.
View attachment 5509453
Reboot to bootloader simply brings me back to the "FASTBOOT mode..." screen.
I contacted Nokia support and they were as much help as wet socks.
Although it does not help my situation they did suggest something which may help the OP:
****************************************************************************************************
In order to fix the issue that you face with your device please follow the steps below:
1. You should login to the Gmail (that is used on the device) on a PC.
2. Click on "Find your phone"
3. Choose the proper device from the list of devices that will appear. (These are the devices that are using the same Gmail account)
4. Confirm the password of the Gmail once again.
5. Click on "Consider erasing your data" >"Yes, erase"
After the final click a remote factory reset if performed and the device will loose the data unless it was stored in a cloud, but this will remove the pattern and the issue will be solved!
****************************************************************************************************
In my case I don't even have a Google account set up on the phone yet so that didn't help.
Since Nokia refused to help I am forced to turn to you guys for any help/ideas? In the meantime I continue to try various button combinations in desperation.
This is my first, and my last, Nokia. It's also my first new phone in a long time, is this type of factory reset prevention common among manufacturers? I ask as I consider my replacement for this phone if I can't ever manage to reset it.
Click to expand...
Click to collapse
After this screen please type fastboot reboot recovery and then you will get recovery screen
Wow, that worked!!!
To clarify (for anyone else) I typed "fastboot reboot recovery" whilst the phone was still on the screen I posted in my previous post.
I cannot thank you enough mvikrant97, I was at my wits end pressing and holding buttons. I did download your batch file although I didn't use it I read it and instead ran my own commands but could you not perform this whole process automatically as follows:
:5
fastboot reboot fastboot
timeout /t 10 /nobreak
fastboot reboot recovery
pause
goto :menu
Nokia G10 TA-1334 is dead after performing factory reset from recovery.
It seems /SYSTEM partition was wiped out. How to write firmware on this phone?
Bootloader is locked, can not flash it even with testpoint!
Any ideas??
brok5 said:
This tool will solve your problem, just search for the explanation on YouTube.
Click to expand...
Click to collapse
Yes yes!
HackT3k said:
Nokia G10 TA-1334 is dead after performing factory reset from recovery.
It seems /SYSTEM partition was wiped out. How to write firmware on this phone?
Bootloader is locked, can not flash it even with testpoint!
Any ideas??
Click to expand...
Click to collapse
no need to flash firmware just set your phone in fastboot mode and then type command in CMD
fastboot --set active=b
mvikrant97 said:
no need to flash firmware just set your phone in fastboot mode and then type command in CMD
fastboot --set active=b
Click to expand...
Click to collapse
fastboot --set active = b
fastboot: usage: unknown command active
No luck!
Sorted out, correct syntax was:
fastboot --set-active=b
Setting current slot to 'b'...
OKAY [ -0.000s]
finished. total time: 0.016s
Command worked, phone booted up. Thanks!!
Peterbd said:
I too had/have similar issues with the "waiting for device.."
I resolved it by removing all the drivers and then downloading what I believe is likely to be a more up to date version from here:
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
I also downloaded their version of adb/fastboot in the standalone package from here:
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Together these two resolved my "waiting for device..." issues and I can consistently get through to the Android "no command" screen.
My problem is also that the power plus volume up button no longer seem to work. I downloaded the reboot2recoveryv5-zip batch file and read the thread which produced it but it would appear the method no longer works either. I can, using "fastboot reboot fastboot", get the fastbootd menu to open but it has no option to exit back down into the recovery menu.
View attachment 5509453
Reboot to bootloader simply brings me back to the "FASTBOOT mode..." screen.
I contacted Nokia support and they were as much help as wet socks.
Although it does not help my situation they did suggest something which may help the OP:
****************************************************************************************************
In order to fix the issue that you face with your device please follow the steps below:
1. You should login to the Gmail (that is used on the device) on a PC.
2. Click on "Find your phone"
3. Choose the proper device from the list of devices that will appear. (These are the devices that are using the same Gmail account)
4. Confirm the password of the Gmail once again.
5. Click on "Consider erasing your data" >"Yes, erase"
After the final click a remote factory reset if performed and the device will loose the data unless it was stored in a cloud, but this will remove the pattern and the issue will be solved!
****************************************************************************************************
In my case I don't even have a Google account set up on the phone yet so that didn't help.
Since Nokia refused to help I am forced to turn to you guys for any help/ideas? In the meantime I continue to try various button combinations in desperation.
This is my first, and my last, Nokia. It's also my first new phone in a long time, is this type of factory reset prevention common among manufacturers? I ask as I consider my replacement for this phone if I can't ever manage to reset it.
Click to expand...
Click to collapse
mvikrant97 said:
After this screen please type fastboot reboot recovery and then you will get recovery screen
Click to expand...
Click to collapse
This TOTTALY WORKS!!!! Thanks guys for your excelent explanation! You only have to download updated drivers and to all the commands inside SDK Platform Tools Folder to make it works, I changed the name of folder to easily type the command
Peterbd said:
Wow, that worked!!!
To clarify (for anyone else) I typed "fastboot reboot recovery" whilst the phone was still on the screen I posted in my previous post.
I cannot thank you enough mvikrant97, I was at my wits end pressing and holding buttons. I did download your batch file although I didn't use it I read it and instead ran my own commands but could you not perform this whole process automatically as follows:
:5
fastboot reboot fastboot
timeout /t 10 /nobreak
fastboot reboot recovery
pause
goto :menu
Click to expand...
Click to collapse
thank you, this commands solved my issue.
While the phone in fastboot mode I copied and pasted the command but not worked till I reentered the command from:
fastboot reboot recovery
pause
goto :menu
then it shows the recovery menu without using any key, and I succeeded to rest Nokia G20 phone throw the menu.
Peterbd said:
I too had/have similar issues with the "waiting for device.."
I resolved it by removing all the drivers and then downloading what I believe is likely to be a more up to date version from here:
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
I also downloaded their version of adb/fastboot in the standalone package from here:
SDK Platform Tools release notes | Android Studio | Android Developers
Android SDK Platform-Tools is a component for the Android SDK.
developer.android.com
Together these two resolved my "waiting for device..." issues and I can consistently get through to the Android "no command" screen.
My problem is also that the power plus volume up button no longer seem to work. I downloaded the reboot2recoveryv5-zip batch file and read the thread which produced it but it would appear the method no longer works either. I can, using "fastboot reboot fastboot", get the fastbootd menu to open but it has no option to exit back down into the recovery menu.
View attachment 5509453
Reboot to bootloader simply brings me back to the "FASTBOOT mode..." screen.
I contacted Nokia support and they were as much help as wet socks.
Although it does not help my situation they did suggest something which may help the OP:
****************************************************************************************************
In order to fix the issue that you face with your device please follow the steps below:
1. You should login to the Gmail (that is used on the device) on a PC.
2. Click on "Find your phone"
3. Choose the proper device from the list of devices that will appear. (These are the devices that are using the same Gmail account)
4. Confirm the password of the Gmail once again.
5. Click on "Consider erasing your data" >"Yes, erase"
After the final click a remote factory reset if performed and the device will loose the data unless it was stored in a cloud, but this will remove the pattern and the issue will be solved!
****************************************************************************************************
In my case I don't even have a Google account set up on the phone yet so that didn't help.
Since Nokia refused to help I am forced to turn to you guys for any help/ideas? In the meantime I continue to try various button combinations in desperation.
This is my first, and my last, Nokia. It's also my first new phone in a long time, is this type of factory reset prevention common among manufacturers? I ask as I consider my replacement for this phone if I can't ever manage to reset it.
Click to expand...
Click to collapse
I've done the same thing but I'm still stuck on the < waiting for device > thing