Related
Recently I made a backup before installing a ROM on my oneplus 2. When I was doing it I selected the Boot, System, Data partitions. Then after I restored it everything was working fine except when I was trying to type in my password(not SIM password) it seemed to just restart the UI, but the strange thing was that the Finger print sensor was working I could unlock it that way. So I tried to go in to security setting after that and that also made my UI restart and just threw me back to the home screen. So my question is what mistake did I make when making the backup and how not to make it again?
Perhaps your persistant-partition (where fingerprint data and other security stuff is stored) is damaged. There's an persistant.img which you can flash in fastboot to restore it somewhere here on the op2 forum which you can find if you search.
Best regards
Peter
pitrus- said:
Perhaps your persistant-partition (where fingerprint data and other security stuff is stored) is damaged. There's an persistant.img which you can flash in fastboot to restore it somewhere here on the op2 forum which you can find if you search.
Best regards
Peter
Click to expand...
Click to collapse
But when I install oxygen OS image it works, it just doesn't work when I restore it from a backup.
winVIP said:
Recently I made a backup before installing a ROM on my oneplus 2. When I was doing it I selected the Boot, System, Data partitions. Then after I restored it everything was working fine except when I was trying to type in my password(not SIM password) it seemed to just restart the UI, but the strange thing was that the Finger print sensor was working I could unlock it that way. So I tried to go in to security setting after that and that also made my UI restart and just threw me back to the home screen. So my question is what mistake did I make when making the backup and how not to make it again?
Click to expand...
Click to collapse
Were you on CM13 and installed the H2OS MM firmware? If so, I ran into a similiar thing. You'll may need to flash the Revert2Lollipop to fix.
unremarked said:
Were you on CM13 and installed the H2OS MM firmware? If so, I ran into a similiar thing. You'll may need to flash the Revert2Lollipop to fix.
Click to expand...
Click to collapse
No, I was making a backup of oxygen OS 2.2.1 before installing Resurrection Remix.
https://download.mokeedev.com/?device=zoom
Does someone try this rom? If u ever on this rom, can u give a feedback about the rom..? I would like to know your opinion..
X10MINISTER said:
Does someone try this rom? If u ever on this rom, can u give a feedback about the rom..? I would like to know your opinion..
Click to expand...
Click to collapse
Rom works but it wasn't maintained. No new bug correction from february.
stuccamelo said:
Rom works but it wasn't maintained. No new bug correction from february.
Click to expand...
Click to collapse
Thanks for sharing ur opinion/experiences on this rom.. Im running on latest build of this mokee rom, i think it is suitable for daily driver..but I got some problem with hotspot(maybe it is because of mod that i've installed).. Maybe u got some solution on this
X10MINISTER said:
Thanks for sharing ur opinion/experiences on this rom.. Im running on latest build of this mokee rom, i think it is suitable for daily driver..but I got some problem with hotspot(maybe it is because of mod that i've installed).. Maybe u got some solution on this
Click to expand...
Click to collapse
Sorry no solution I have big problem with gmaps doesn't recalculate path after initial path and play store give "not compatible device" error in some apps.
Good thing battery drain is very very good
stuccamelo said:
Sorry no solution I have big problem with gmaps doesn't recalculate path after initial path and play store give "not compatible device" error in some apps.
Good thing battery drain is very very good
Click to expand...
Click to collapse
So, it mean that u also facing the hotspot problem.?
Can u change/install fonts in mokee roms? Cause I have an issue with changing font style using iFont apps..its say installed but after reboot font style doesnt change. Any solution?
linux shall eternally bloat all search engines with expired ?=
as it is stated in the title: the internet is full of long expired conversations about issues which are gone, along with hardware.
back in the beginning i recall only one distro Dev, SimplyMepis, who always, promptly warned, that most if not all information online about Linux is outdated or incorrect.
now on mokee, has anyone tested mokee naugat on vibe shot as recent as September/October 2017? The reason I ask is because there are no reviews or any useful feedback on mokee download/changelog page. I used it in August and each time the phone disconnect from WiFi it would reboot with an ugly, annoying double beep.
Apart from this issue everything would work pefectly well, including both sim loaded.
Thanks for taking time to respond.
Dr Tungsten said:
as it is stated in the title: the internet is full of long expired conversations about issues which are gone, along with hardware.
back in the beginning i recall only one distro Dev, SimplyMepis, who always, promptly warned, that most if not all information online about Linux is outdated or incorrect.
now on mokee, has anyone tested mokee naugat on vibe shot as recent as September/October 2017? The reason I ask is because there are no reviews or any useful feedback on mokee download/changelog page. I used it in August and each time the phone disconnect from WiFi it would reboot with an ugly, annoying double beep.
Apart from this issue everything would work pefectly well, including both sim loaded.
Thanks for taking time to respond.
Click to expand...
Click to collapse
There are a lot of recent updates for this rom. I flashed the most recent (2017-11-21 date). I didn't make a lot of testing but the problem you refered has been solved and the performance and stability seems good.
The only issue I noticed so far is that the phone does not start automatically from the shutdown state when an alarm is set.
@piccolo2k2 Was your device flagged as certified? When I flushed the rom I wasn't able to pass the SafetyNet test and I would appear as uncertified in play store, meaning I couldn't download most apps like Messenger or Facebook. I installed a third party app store which worked fine, but YouTube wouldn't play any video, because it couldn't load any ads... I even tried Magisk with no luck..
GeorgeTsak said:
@piccolo2k2 Was your device flagged as certified? When I flushed the rom I wasn't able to pass the SafetyNet test and I would appear as uncertified in play store, meaning I couldn't download most apps like Messenger or Facebook. I installed a third party app store which worked fine, but YouTube wouldn't play any video, because it couldn't load any ads... I even tried Magisk with no luck..
Click to expand...
Click to collapse
This is not my main phone right now so I spend very limited time using or testing it but you are right, I have just checked that with this ROM the device is unable to pass the SafeNet test so far. On the other hand I have not problems at all playing videos with youtube app or rooting the device. I'm using supersu v2.82 and TRWP-3.0.2-0 for lenovo 6.0 by wzsx150 (didn't try Magisk)
has anyone managed to install this ROM?
i tried to install it but failed.
I unlocked the bootloader using the method described here, and installed TWRP recovery as described here
when i try to install it - the flashing is stopped by a long vibration and the device went off, i tried to debug the flashing process, it seems that the step of mounting "\system" fails, i tried to replace the mount/unmount calls from updater_script with respective run_program(busybox) commands, but had no success with that. when i'm using the TWRP build in funcitonlity to wipe the system partition, TWRP claims the operation was successful, but checking the system partition details shows that the partition still contains data.
ohh, and also - the device model seems strange, the script checked that the model is zoom_tdd (or something like that) but the device (the bootloader?) return Z90a40... (i also updated the script to check for Z90a40)
the current state is that the device won't boot, but i can get into recovery.
Anyone have an idea how to proceed?
Thanks.
mrtowel said:
i tried to install it but failed.
I unlocked the bootloader using the method described here, and installed TWRP recovery as described here
when i try to install it - the flashing is stopped by a long vibration and the device went off, i tried to debug the flashing process, it seems that the step of mounting "\system" fails, i tried to replace the mount/unmount calls from updater_script with respective run_program(busybox) commands, but had no success with that. when i'm using the TWRP build in funcitonlity to wipe the system partition, TWRP claims the operation was successful, but checking the system partition details shows that the partition still contains data.
ohh, and also - the device model seems strange, the script checked that the model is zoom_tdd (or something like that) but the device (the bootloader?) return Z90a40... (i also updated the script to check for Z90a40)
the current state is that the device won't boot, but i can get into recovery.
Anyone have an idea how to proceed?
Thanks.
Click to expand...
Click to collapse
I think you need a different TWRP version. Try this one:
https://drive.google.com/file/d/0B1Sms71Oe6FIQnl4STlhSk96b0E/view?usp=sharing
Help me!
I'm new to these things. Installing roms and ****s. Can someone help me with the step by step procedure of installing this room on my Lenovo vibe shot. Thanks in advance.
The same probvlem with TWRP
piccolo2k2 said:
I think you need a different TWRP version. Try this one:
Click to expand...
Click to collapse
I have exactly the same problem.
Did you resolved it? Tried also mentioned "Twrp by rahul.rar", but the same problem - unable to mount /system partition.
Thanks for reply,
st
bug fix?
does anybody tested it?
is it still any bug on release version MK71.2-zoom-180914-RELEASE?
hhaekal said:
does anybody tested it?
is it still any bug on release version MK71.2-zoom-180914-RELEASE?
Click to expand...
Click to collapse
Im using it right now.. Im still have the problem with:
-hotspot tethering,bluetooth tethering
-usb mtp
-suddenly shutdown when on wifi
Have someone had the problem with delay in receiving whatsapp messages?
Hello,
has anyone tested the MK71.2-zoom-181107-RELEASE version? Is the bug with the WiFi still there?
Alex_135 said:
Hello,
has anyone tested the MK71.2-zoom-181107-RELEASE version? Is the bug with the WiFi still there?
Click to expand...
Click to collapse
Hi,
I'm using the release and there is no bug with WIFI.
Linaxx said:
Hi,
I'm using the release and there is no bug with WIFI.
Click to expand...
Click to collapse
How about wifi tethering problem? Does it remain error when wifi tethering are enabled?
https://youtu.be/xQdkQqAMdj0
New video mac 02:00:00:00:00:00
Solutions?
4Bismuth said:
https://youtu.be/xQdkQqAMdj0
New video mac 02:00:00:00:00:00
Solutions?
Click to expand...
Click to collapse
thats just what the custom rom shows. thats how it is for my on lineage. the system and apps know and use the real mac.
you can use change my mac to spoof a new one if it bothers you. but you shouldnt have any problems.
all my wifi and bluetooth connections work without problems.
4Bismuth said:
https://youtu.be/xQdkQqAMdj0
New video mac 02:00:00:00:00:00
Solutions?
Click to expand...
Click to collapse
Try resetting your network or just wipe your device and do a clean install. I have used every rom available for the Leeco Pro 3 and have never encountered this issue.
Kennii said:
thats just what the custom rom shows. thats how it is for my on lineage. the system and apps know and use the real mac.
you can use change my mac to spoof a new one if it bothers you. but you shouldnt have any problems.
all my wifi and bluetooth connections work without problems.
Click to expand...
Click to collapse
Ok, So the 02:00:00:00:00:00 mac is not a problem?
tsongming said:
Try resetting your network or just wipe your device and do a clean install. I have used every rom available for the Leeco Pro 3 and have never encountered this issue.
Click to expand...
Click to collapse
I already made all the wipes, factory reset, network reset ...
I think it's a problem with the internal folders as I restore the folders'
4Bismuth said:
Ok, So the 02:00:00:00:00:00 mac is not a problem?
I already made all the wipes, factory reset, network reset ...
I think it's a problem with the internal folders as I restore the folders'
Click to expand...
Click to collapse
What internal folders? If you do the full wipe, including formatting storage there aren't any internal folders that would have access to that would cause this kind of problem. Beware, do not format your internal storage unless you have a permanent Twrp Recovery partition. As long as you have the recovery partition there is no danger with formatting your storage.
What you are describing is related to your device ID. Are you also experiencing sim card, or bluetooth issues?
Have you flashed various basebands, chinese roms etc?
It sounds as if your EFS is possibly corrupted. If that is in fact the case you should take a look at this guide: https://forum.xda-developers.com/le-pro3/how-to/guide-how-to-downgrade-jui-restore-bands-t3622639
Another possible scenario is the issue stems from a corrupted installation of adb, Mac spoofing, or local network issues due to an improper static ip configuration, which can definitely result in duplicate MAC addresses on your network.
Source: https://android.izzysoft.de/articles/named/identifiers-1?lang=en
MAC: The MAC-Address identifies the corresponding network interface. Hence it is globally unique (aside maybe from some „Fakes“ and „NoName replicas“). WiFi and Bluetooth have each their own MAC address. Starting with Android-6, only system apps have access to it, all other apps just receive the default value "02:00:00:00:00:00"2; on older Android versions the permission ACCESS_NETWORK_STATE, ACCESS_WIFI_STATE resp. BLUETOOTH is required to access it (requested by ca. 70%, 30% resp. 10% of all apps).3
Click to expand...
Click to collapse
Follow any of the steps mentioned above, at your own discretion.
tsongming said:
What internal folders? If you do the full wipe, including formatting storage there aren't any internal folders that would have access to that would cause this kind of problem. Beware, do not format your internal storage unless you have a permanent Twrp Recovery partition. As long as you have the recovery partition there is no danger with formatting your storage.
What you are describing is related to your device ID. Are you also experiencing sim card, or bluetooth issues?
Have you flashed various basebands, chinese roms etc?
It sounds as if your EFS is possibly corrupted. If that is in fact the case you should take a look at this guide: https://forum.xda-developers.com/le-pro3/how-to/guide-how-to-downgrade-jui-restore-bands-t3622639
Another possible scenario is the issue stems from a corrupted installation of adb, Mac spoofing, or local network issues due to an improper static ip configuration, which can definitely result in duplicate MAC addresses on your network.
Source: https://android.izzysoft.de/articles/named/identifiers-1?lang=en
Follow any of the steps mentioned above, at your own discretion.
Click to expand...
Click to collapse
Ty, I will try it, if I have problems with the bluetooth as you can see in the video.
Gracias mi amigo
"Push The rom with mtp and install it."
how to push the rom with mtp?
I pass it by normal USB to the phone and already or it does not work?
-What you are describing is related to your device ID. Are you also experiencing sim card, or bluetooth issues?
Only wifi and bluetooth issues.
Have you flashed various basebands, chinese roms etc?
Only i flashed is TWRP and AICP 8.1 and nothing more.
It sounds as if your EFS is possibly corrupted. If that is in fact the case you should take a look at this guide:
I dont have EFS partition, i cant found this partition with root explorer.
4Bismuth said:
-What you are describing is related to your device ID. Are you also experiencing sim card, or bluetooth issues?
Only wifi and bluetooth issues.
Have you flashed various basebands, chinese roms etc?
Only i flashed is TWRP and AICP 8.1 and nothing more.
It sounds as if your EFS is possibly corrupted. If that is in fact the case you should take a look at this guide:
I dont have EFS partition, i cant found this partition with root explorer.
Click to expand...
Click to collapse
Your EFS partition is hidden, you would not see it with root explorer. I will not be able to check back to see you answer until later tonight.
(approximately 7 to 8 hours from now)
You have an X720?
So you were on stock EUI and then went straight to a custom rom?
You have flashed, AICP, and Twrp and Gapps right? Which version of Twrp?
How long have you owned the phone?
Have you tried simply resetting the phone?
I can suggest a few things, So lets start with the basics, in my experience it's usually something simple that causes a big issue.
Potential Solution
Go here and download file: http://www.teamsuperluminal.org/wp-content/uploads/2016/12/le_zl1_x720_mod.zip
Boot into Twrp and flash reboot,
Let me know if this resolves the issue.
tsongming said:
Your EFS partition is hidden, you would not see it with root explorer. I will not be able to check back to see you answer until later tonight.
(approximately 7 to 8 hours from now)
You have an X720?
So you were on stock EUI and then went straight to a custom rom?
You have flashed, AICP, and Twrp and Gapps right? Which version of Twrp?
How long have you owned the phone?
Have you tried simply resetting the phone?
I can suggest a few things, So lets start with the basics, in my experience it's usually something simple that causes a big issue.
Potential Solution
Go here and download file: http://www.teamsuperluminal.org/wp-content/uploads/2016/12/le_zl1_x720_mod.zip
Boot into Twrp and flash reboot,
Let me know if this resolves the issue.
Click to expand...
Click to collapse
You have an X720?
Yes, with 23s stock bought in Banggood.
So you were on stock EUI and then went straight to a custom rom?
First the WiFi stopped working and the phone restarted. And he fixed it by restarting the phone. Then I tried to reset the factory and the phone was fixed but then it failed again and finally I changed the ROM, it lasted a day and it failed again. And now I'm like the video without bluetooth or wifi.
You have flashed, AICP, and Twrp and Gapps right? Which version of Twrp?
This TWRP 3.0.2-v4 para LePro3 X720 unofficial de YDDS
What version of TWRP is the better?
How long have you owned the phone?
Like 4-5 month
Have you tried simply resetting the phone?
Yes, factory reset, all wipes, format data, reseting network, apps etc.
My phone is creating logs....
[1922:F :HDD] hdd_driver_init: WLAN Driver Initialization failed
<3>[ 45.130417][01-03_01:30:44 UTC] [WiFi-0x2304]wlan: driver load failure
<36>[ 48.758557
this is repeating in the log file...
4Bismuth said:
You have an X720?
Yes, with 23s stock bought in Banggood.
So you were on stock EUI and then went straight to a custom rom?
First the WiFi stopped working and the phone restarted. And he fixed it by restarting the phone. Then I tried to reset the factory and the phone was fixed but then it failed again and finally I changed the ROM, it lasted a day and it failed again. And now I'm like the video without bluetooth or wifi.
You have flashed, AICP, and Twrp and Gapps right? Which version of Twrp?
This TWRP 3.0.2-v4 para LePro3 X720 unofficial de YDDS
What version of TWRP is the better?
How long have you owned the phone?
Like 4-5 month
Have you tried simply resetting the phone?
Yes, factory reset, all wipes, format data, reseting network, apps etc.
My phone is creating logs....
[1922:F :HDD] hdd_driver_init: WLAN Driver Initialization failed
<3>[ 45.130417][01-03_01:30:44 UTC] [WiFi-0x2304]wlan: driver load failure
<36>[ 48.758557
this is repeating in the log file...
Click to expand...
Click to collapse
There truly is no reason why that files shouldn't load, try it again and immediately afterwards create a log report and upload it. I would bet you have a permissions issue., or a possible hardware issue> more likely permissions.
First, you need this version of Twrp:
PHP:
https://twrp.me/leeco/leecolepro3.html
" Download Links"
You can update Twrp with in twrp - choose to instal from image if you downloaded an .img file or as you know Zip its .zip
Have you reflashed Magisk?
You should do that first, to ensure that your issue is not permissions related?
Next, reflash the file from the last post, if it fails get the log file.
Do you have a recent full backup? If not try to create a full backup.
With your issue, Titanium backup would be great, this way if the issue persists, you will have a way to restore your apps and cloud based data.
Ideally, you need to do a full wipe. With the correct newest version of Twrp, ( linked above)
Newest official Gapps: 8.1 arm64 is now available:
PHP:
http://opengapps.org/
Newest version Rom of choice ( Lineage, AICP, Pixel, AOSIP)
As of Mar 1, 8:20 pm EST :Lineage is the most up to date. But all of the recent versions of 8.1 are great.
Hopefully this helps. If not, it's definitely a hardware or EFS issue.
EFS issues can sometimes repaired with Qfil. Personally, I save myself the hassle of uncertainty and contact Bangood for a warranty repair or replacement.
tsongming said:
There truly is no reason why that files shouldn't load, try it again and immediately afterwards create a log report and upload it. I would bet you have a permissions issue., or a possible hardware issue> more likely permissions.
First, you need this version of Twrp:
PHP:
https://twrp.me/leeco/leecolepro3.html
" Download Links"
You can update Twrp with in twrp - choose to instal from image if you downloaded an .img file or as you know Zip its .zip
Have you reflashed Magisk?
You should do that first, to ensure that your issue is not permissions related?
Next, reflash the file from the last post, if it fails get the log file.
Do you have a recent full backup? If not try to create a full backup.
With your issue, Titanium backup would be great, this way if the issue persists, you will have a way to restore your apps and cloud based data.
Ideally, you need to do a full wipe. With the correct newest version of Twrp, ( linked above)
Newest official Gapps: 8.1 arm64 is now available:
PHP:
http://opengapps.org/
Newest version Rom of choice ( Lineage, AICP, Pixel, AOSIP)
As of Mar 1, 8:20 pm EST :Lineage is the most up to date. But all of the recent versions of 8.1 are great.
Hopefully this helps. If not, it's definitely a hardware or EFS issue.
EFS issues can sometimes repaired with Qfil. Personally, I save myself the hassle of uncertainty and contact Bangood for a warranty repair or replacement.
Click to expand...
Click to collapse
Hi, I have already installed the new version of twrp, I have also made all the wipes, new rom of AICP, etc. I just deleted superSu and I installed magisk.
I have made a log with twrp and I get several errors.
4Bismuth said:
Hi, I have already installed the new version of twrp, I have also made all the wipes, new rom of AICP, etc. I just deleted superSu and I installed magisk.
I have made a log with twrp and I get several errors.
Click to expand...
Click to collapse
I just reviewed your post history and I see alot of good advice was given.
I assume you followed all advice.
I was not aware that you started having this issue originally on the stock rom???
The problem persist after stock reset and resetting your home network.
Before seeing your history, I was going to suggest that you attempt to return to stock. But, it seems that you have already tried that as well as attempted using Qfil.
The only other thing that I see from your logs that shows that the SELinux protection turned off, and that you are getting few kernel errors.
The answer is simple return the phone to Bangood for a replacement under warranty the phone has a hardware that it was likely caused by a faulty charger or usb cable.
tsongming said:
I just reviewed your post history and I see alot of good advice was given.
I assume you followed all advice.
I was not aware that you started having this issue originally on the stock rom???
The problem persist after stock reset and resetting your home network.
Before seeing your history, I was going to suggest that you attempt to return to stock. But, it seems that you have already tried that as well as attempted using Qfil.
The only other thing that I see from your logs that shows that the SELinux protection turned off, and that you are getting few kernel errors.
The answer is simple return the phone to Bangood for a replacement under warranty the phone has a hardware that it was likely caused by a faulty charger or usb cable.
Click to expand...
Click to collapse
I was not aware that you started having this issue originally on the stock rom???
Yes
The problem persist after stock reset and resetting your home network.
yes
Before seeing your history, I was going to suggest that you attempt to return to stock. But, it seems that you have already tried that as well as attempted using Qfil.
I'm going to try this, link?
The only other thing that I see from your logs that shows that the SELinux protection turned off, and that you are getting few kernel errors.
:/ i have another log with the wifi errors
tsongming said:
I just reviewed your post history and I see alot of good advice was given.
I assume you followed all advice.
I was not aware that you started having this issue originally on the stock rom???
The problem persist after stock reset and resetting your home network.
Before seeing your history, I was going to suggest that you attempt to return to stock. But, it seems that you have already tried that as well as attempted using Qfil.
The only other thing that I see from your logs that shows that the SELinux protection turned off, and that you are getting few kernel errors.
The answer is simple return the phone to Bangood for a replacement under warranty the phone has a hardware that it was likely caused by a faulty charger or usb cable.
Click to expand...
Click to collapse
Hi, I've tried using Qfil.
And when I use the phone, I get the red frames.
And my mac and bluetooth adress is unavaible :/
4Bismuth said:
Hi, I've tried using Qfil.
And when I use the phone, I get the red frames.
And my mac and bluetooth adress is unavaible :/
Click to expand...
Click to collapse
Other than what we have discussed. It seems to me that you have a hardware issue which if is the case you need to return it under warranty. Perhaps a component was not soldered well and it needs repair.
If you have owned the device for less than a year you should still be under warranty. If not maybe find a shop in your local area.
Worst case, the people at this link had some crazy ideas to resolve the same issue on another phone. If you are bold and desperate go take a look : https://forum.xda-developers.com/general/help/qa-wifi-stuck-mac-020000000000-g2-g3-g4-t3452133
If I had better advice I would certainly give it to you.
tsongming said:
Other than what we have discussed. It seems to me that you have a hardware issue which if is the case you need to return it under warranty. Perhaps a component was not soldered well and it needs repair.
If you have owned the device for less than a year you should still be under warranty. If not maybe find a shop in your local area.
Worst case, the people at this link had some crazy ideas to resolve the same issue on another phone. If you are bold and desperate go take a look : https://forum.xda-developers.com/general/help/qa-wifi-stuck-mac-020000000000-g2-g3-g4-t3452133
If I had better advice I would certainly give it to you.
Click to expand...
Click to collapse
How I return everything in stock as if it were banggood came with version 23s
There is through return to stock instructions here on XDA.
tsongming said:
Source: https://android.izzysoft.de/articles/named/identifiers-1?lang=en
Follow any of the steps mentioned above, at your own discretion.
Click to expand...
Click to collapse
How and where to access/modify this "access_wifistate" permissions ? In apks, or etc / permissions ?
Yogesh1969 said:
How and where to access/modify this "access_wifistate" permissions ? In apks, or etc / permissions ?
Click to expand...
Click to collapse
The last time that I answered a question on this thread was over a year ago, and I rarely use a Le Pro 3, since buying another phone. So first you may want to describe your issue so I don't have to guess.
Since you are on this thread I assume that you have a baseband issue and likely have a corrupted EFS partition.
There are ways to delete and reload your modems.
However I don't recommend it and I will not describe it, the partition is encrypted and it should only be repaired from fastboot, recovery or EDL. Otherwise you risk unrecoverable damage.
The best thing to do, is to restore your full Nandroid backup
Hopefully made before you began flashing roms on this phone. So if you have one , do that.
The next options
Restoring the phone to factory stock with a fastboot rom. NOT A MODDED EUI, STOCK ONLY
Keep in mind that this may relock your bootloader.
Depending on which rom you use and this step is a little more dangerous if you have an X722.
If you have a X720 or X727
Try using my posted recovery, its includes the full efs.
If that doesn't work, you should find and download EUI 26s fastboot rom
If you have a X720 then unpack the 26S rom on your desktop, the 2GB file will unpack a 4GB version of the file, unpack it as well and you will now see a folder with all disk images. Look for the flashall.bat file and double click it. The flashboot.bat is a batch file that restores every partition one at a time, when the process is finished stock will be restore and the phone will automatically boot. Set the phone up, go to developer options and prepare the phone for a custom rom all over again.
If you have a X727, same steps but use EUI 21s fastboot instead of 26S
At this point the issue should be resolved, there is one other option of using QPST, with the stock QFil, but you will need to find a QCN file specifc to whichever device you own, it would be much easier to use flashall.bat or a Full Recovery.
Good Luck,
Also, I don't get paid to spend 20 minutes typing instructions, so click thanks or donate a beer. Cheers.
Hi everyone,
To flash the last rom (nightly ) of LineageOS ( in Oreo,from the 2 february), i had to put the firmware 5.1.7. After flash this firmware i was able to flash the ROM but it makes my phone extremely slow and with screen issues (i can still use the tactile but the screen doesnt follow).
I restored but the problem stills then i put le last stable ROM from Oneplus on android pie (9.0.3). It is a bit better (still really slow) and after a moment i get now like a white noise (same as on TV but with color moreover) by wink ( was more and more often on Google Maps), I had to reboot cause i couldnt use more my phone.
Thanks you in advance !
Ps : I've got TWRP from siankatabg and i'm not rooted , if you want me to send log tell me how pls.
Up :good:
When you were flashing did you used this instructions?
https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-4-5-2-7-1-1-ota-t3627003
Flash codework's TWRP for Pie. After that reboot into recovery, wipe everything down and use clean flash instructions for your OTA. It should be able to fix any issue you were having. If not let me know.
Yes i followed the clean flash way (it didn't resolve my issue) but my issue occured before i flash pie, when i flashed lineageOS 15.1 with the firmware 5.1.7 required (which i flashed too). A restoration didnt change that issue.
I tried with the TWRP from codework but it doesnt recognise my internal stockage.
Thanks of your time.
Raidenne said:
Yes i followed the clean flash way (it didn't resolve my issue) but my issue occured before i flash pie, when i flashed lineageOS 15.1 with the firmware 5.1.7 required (which i flashed too). A restoration didnt change that issue.
I tried with the TWRP from codework but it doesnt recognise my internal stockage.
Thanks of your time.
Click to expand...
Click to collapse
Hi, try wiping everything down with the new TWRP, after that reboot into recovery once more. Install last normal working OOS to see if that helps you. If not maybe it is hardware issue? Let me know once you wiped and installed the last working OOS on it.
I have installed multiple roms and firmware updates on my device with codework's TWRP and never had big issue like this. In my opinion best option for you to trace your steps back to the last working version of your os and try learning what might have gone wrong.
Ebeninyo said:
Hi, try wiping everything down with the new TWRP, after that reboot into recovery once more. Install last normal working OOS to see if that helps you. If not maybe it is hardware issue? Let me know once you wiped and installed the last working OOS on it.
I have installed multiple roms and firmware updates on my device with codework's TWRP and never had big issue like this. In my opinion best option for you to trace your steps back to the last working version of your os and try learning what might have gone wrong.
Click to expand...
Click to collapse
My issues seem gone since few weeks with the last OTA (it very rarely happens now). I don't know what caused that even if i use my backup.
Thanks for your support !
Greetings.
Due to events beyond my control, I had to give up my Pixel 3 XL (packing it as I type this)
Until funds become available, I decided to bring the Nexus 6P - with pre-mature battery shutdown issue - back to duty. I have new battery, lens cover, etc. waiting in the wings so it may become my primary whip after all. That is "if" I can undo whatever mistake I made tonight (knocking on wood).
The 6P was unlocked already before being retired (Idon't know if it matters or not). Stock image (I think it was 8.1) with security update from December 2018 I think.
Here's what I think I did tonight that lead to the current situation:
1. installed TWRP 3.3.1
2. along the way wiped one too many partitions - my stupidity
3. thanks to TWRP for warning me that there was no OS so went back, found USB-A to USB-C adapter, copied "PixelExperience_angler-10.0-20191113-2124-OFFICIAL," and used TWRP's "Install" option
First problem is that I noticed in the text log within TWRP that the vendor image was missing
Second problem, or perhaps because of above, after restarting the 6P it never gets out of the welcome screen of Android 10
Third problem, again may be related to #2 in the things I did tonight, when I reboot into TWRP recovery, first thing it does ask is "Mount, Decrypt Data" and "Enter Password" to which I don't know the password. If I select "Cancel" I get to TWRP main menu but I can see that "Internal Storage" is now at 0MB.
I know I did wrong here but is there any way to recover? Since it doesn't boot into Android 10 (just stuck at welcome screen, I guess using ADB on laptop, if it helps, is out of question? Can I fix this through TWRP?
Thank you for any help/advice.
UPDATE: Reading some more threads on XDA & decided to try Lineage. At one point seems to have things working following the directions but the SIM card was not recognized.
Thinking of trying again with Lineage but maybe with Lineage16 instead of 17. But what is the best stable ROM that is plain Android but perhaps based with up-to-date security patching?
Thank you!
ur2punk said:
UPDATE: Reading some more threads on XDA & decided to try Lineage. At one point seems to have things working following the directions but the SIM card was not recognized.
Thinking of trying again with Lineage but maybe with Lineage16 instead of 17. But what is the best stable ROM that is plain Android but perhaps based with up-to-date security patching?
Thank you!
Click to expand...
Click to collapse
I've been running aicp for the past few months, which is 9.0 they still put out weeklies with security updates. Not sure how long they plan on supporting 9.0 though
Lawlrus said:
I've been running aicp for the past few months, which is 9.0 they still put out weeklies with security updates. Not sure how long they plan on supporting 9.0 though
Click to expand...
Click to collapse
Thank you. Because the SIM was not recognized, I was going to restore to the last Android. I may just try the aicp ROM first.
ur2punk said:
Thank you. Because the SIM was not recognized, I was going to restore to the last Android. I may just try the aicp ROM first.
Click to expand...
Click to collapse
Yeah I haven't noticed any issues with Sim with this device. You said you had it on a shelf for a while though, if it was before the last update the device got, DEC of 2018 did you DL the ota a d make sure the radio was up to date ?
ur2punk said:
Thank you. Because the SIM was not recognized, I was going to restore to the last Android. I may just try the aicp ROM first.
Click to expand...
Click to collapse
I had this SIM card issue when I was trying to flash RR, tried twice with same results. Came across a post once about a bug and it said to remove all screen locks, low and behold it worked... weird
redshirt110 said:
I had this SIM card issue when I was trying to flash RR, tried twice with same results. Came across a post once about a bug and it said to remove all screen locks, low and behold it worked... weird
Click to expand...
Click to collapse
Ah yeah, I've seen that before no idea why people have to do that. I've never had my Sim stop working because of a screen lock. I never looked onto why it happens. I always chaulked it up to a not a US problem because most of the people that posted about it seemed to be from a different country lol.
Update!
I thought it would be a good idea for me to try this routine of wipe & install the Android 8.1 again to get myself comfortable with the process. Long story short, I did exactly that:
(- Bootloader was already unlocked)
- TWRP
- flashed/installed Dec 2018 OTA images/zip
- Installed Magisk
Everything seemed to be working fine when I found out ,while on road, that Google Maps don't work after 5 seconds or so (the navigation part). Read up & they suggested safe mode so I did that. Happy to report that it works so it is not the GPS antenna as some had reported. Whew.
Is there any particular image I need to reflash to see if that was the problem? Or should I just reinstall again? At least I'm getting more comfortable with the various commands - LOL.
Thank you!