Related
A few people have had issues with the EFS getting corrupt or wiped on their OPO before they had a working backup. This guide has so far worked for 4 people to restore their EFS allowing them to access mobile data and bluetooth again.
Note: I really don't know why this works, I have contacted the dev of this rom to ask if he has any ideas but still waiting on a response.
1. Flash official TWRP
2. Flash this ColorOS rom using TWRP - http://forum.xda-developers.com/showthread.php?t=2772627 (you can skip all the account setups if you want)
3. Factory reset
4. Boot and setup ColorOS (you should see a network connect now with your sim card inserted, you will need to toggle mobile data on to test that)
5. If you have data in ColorOS you are good to flash back to CM11S anyway you want (you will need to factor reset after flashing back)
6. Save yourself the headache in the future and backup your EFS
Please post if this fix works for you.:victory:
Edit: I've went ahead and downloaded the ROM and I will hold on to it incase the original mirrors go down for some reason. Please PM me if they do.
One of the ones who can confirm this works. Will post in the official thread.
Worked for me also.
Wholy moly ... I have a mobile data network !!
Still on ColorOS, but this is VERY promising !!!
IMEI is correct, it's the one on the box !
Still no WiFi nor Bluetooh mac addresses, though...
Will keep you posted, but this is a HUGE step forward !
Thanx a lot for sharing this !
BTW, serial number is still unchanged and correct.
JP.
EDIT:
Unfortunately it didn't fix my issue, back to CM11S I am greeted by an AudioFX FC... Device pretty much unusable, the FC pops up the milisecond you click OK ...
Will try a different ROM...
EDIT 2:
SlimKat, CM11 Nightly both boot to the welcome screen, then reboot about 1 second later.
Only ColorOS seems to actually run ?!
A bit disgusted right now
tw1tch175 said:
A few people have had issues with the EFS getting corrupt or wiped on their OPO before they had a working backup. This guide has so far worked for 3 people to restore their EFS allowing them to access mobile data and bluetooth again.
Note: I really don't know why this works, I have contacted the dev of this rom to ask if he has any ideas but still waiting on a response.
1. Flash official TWRP
2. Flash this ColorOS rom using TWRP - http://forum.xda-developers.com/showthread.php?t=2772627 (you can skip all the account setups if you want)
3. Factory reset
4. Boot and setup ColorOS (you should see a network connect now with your sim card inserted, you will need to toggle mobile data on to test that)
5. If you have data in ColorOS you are good to flash back to CM11S anyway you want (you will need to factor reset after flashing back)
6. Save yourself the headache in the future and backup your EFS
Please post if this fix works for you.:victory:
Click to expand...
Click to collapse
Hi, i failed and i wiped EVERYTHING of my phone, i only had the fasboot mode, i installed CWM and the cyanogemod rom, now everything works, and i have the imei in the box, however, i dont have the possibility of EFS backup anymore.... any ideas..?
Gambalajillo said:
Hi, i failed and i wiped EVERYTHING of my phone, i only had the fasboot mode, i installed CWM and the cyanogemod rom, now everything works, and i have the imei in the box, however, i dont have the possibility of EFS backup anymore.... any ideas..?
Click to expand...
Click to collapse
Official TWRP doesn't have EFS backup in it, you have the get the unofficial one http://forum.xda-developers.com/oneplus-one/development/recovery-unofficial-twrp-2-7-1-0-t2815247
Yank555 said:
Wholy moly ... I have a mobile data network !!
Still on ColorOS, but this is VERY promising !!!
IMEI is correct, it's the one on the box !
Still no WiFi nor Bluetooh mac addresses, though...
Will keep you posted, but this is a HUGE step forward !
Thanx a lot for sharing this !
BTW, serial number is still unchanged and correct.
JP.
EDIT:
Unfortunately it didn't fix my issue, back to CM11S I am greeted by an AudioFX FC... Device pretty much unusable, the FC pops up the milisecond you click OK ...
Will try a different ROM...
EDIT 2:
SlimKat, CM11 Nightly both boot to the welcome screen, then reboot about 1 second later.
Only ColorOS seems to actually run ?!
A bit disgusted right now
Click to expand...
Click to collapse
Odd, maybe you could try using TWRP to delete everything again including system, then sideload and boot ColorOS.
tw1tch175 said:
Official TWRP doesn't have EFS backup in it, you have the get the unofficial one http://forum.xda-developers.com/oneplus-one/development/recovery-unofficial-twrp-2-7-1-0-t2815247
Click to expand...
Click to collapse
To add to that you can just boot the unofficial recovery using "fastboot boot recovery.img" to do your efs backup if you would prefer to keep the official TWRP installed. That way it only boots that recovery to allow you to do the backup of your EFS partition and doesn't erase your current recovery. That's how I did it.
sabbotage said:
To add to that you can just boot the unofficial recovery using "fastboot boot recovery.img" to do your efs backup if you would prefer to keep the official TWRP installed. That way it only boots that recovery to allow you to do the backup of your EFS partition and doesn't erase your current recovery. That's how I did it.
Click to expand...
Click to collapse
WOW thanks, i do it and and i tell you how did it go in a few minutes.
I see that the OP has been thanked and this thread has a few success stories so I am giving it a bump for others to view in case of the same issue.
I just flashed the factory image... I never had the problem again
Yank555 said:
Wholy moly ... I have a mobile data network !!
Still on ColorOS, but this is VERY promising !!!
IMEI is correct, it's the one on the box !
Still no WiFi nor Bluetooh mac addresses, though...
Will keep you posted, but this is a HUGE step forward !
Thanx a lot for sharing this !
BTW, serial number is still unchanged and correct.
JP.
EDIT:
Unfortunately it didn't fix my issue, back to CM11S I am greeted by an AudioFX FC... Device pretty much unusable, the FC pops up the milisecond you click OK ...
Will try a different ROM...
EDIT 2:
SlimKat, CM11 Nightly both boot to the welcome screen, then reboot about 1 second later.
Only ColorOS seems to actually run ?!
A bit disgusted right now
Click to expand...
Click to collapse
Im having the same problem as you have Yank555. It started with the AudioFX FCs rendering the device useless.
Next i tried to reflash the standard CM11s 25R rom back to get my phone normal again, it didnt work.
Then i remember i have a nandroid from a few days ago. Not thinking to read up on known issues with the OPO EFS i tried a restore.
My EFS is gone and the phone will not work unless im on ColourOs120. Wifi doesnt work, just basic phone functions.
Still waiting for a miracle for this problem.
Any suggestion guys?
jwai85 said:
Im having the same problem as you have Yank555. It started with the AudioFX FCs rendering the device useless.
Next i tried to reflash the standard CM11s 25R rom back to get my phone normal again, it didnt work.
Then i remember i have a nandroid from a few days ago. Not thinking to read up on known issues with the OPO EFS i tried a restore.
My EFS is gone and the phone will not work unless im on ColourOs120. Wifi doesnt work, just basic phone functions.
Still waiting for a miracle for this problem.
Any suggestion guys?
Click to expand...
Click to collapse
Did you open a service request ? Any response ? So far all I got 5 days later was a "please fastboot flash factory images, case closed." which quite obviously did not help, so case reopened, but again nothing from them in 4 days, now.
But I wonder if my first thought is still correct, flawed emmc as flashing seems to work ... might be a radio hardware issue ? Just don't quite get what the AudioFX has to do with that... cause simply rooting the device and installing apps and making a few nandroid backups is no way to brick anything.
But anyway, tbh, OnePlus is mostly dead to me as a company, worst invest ever so far, nice if your device works, but service is not even close to bad, it's pretty much non-existing ... and for a supposedly "best service ever" it's quite, let's say, "impressing"
JP.
Nope, i have not tried opening a ticket, mine is a grey import from China.
There is something terribly wrong somewhere hardware wise. The audiofx problem only happens if i flash the CM11s. After ColourOS i have tried flashing the CM11 M8.
Im also wondering if i should try to use this OPO made rom to see if it can help.
https://forums.oneplus.net/threads/rom-official-4-4-4-oneplus-aosp.65482/
jwai85 said:
Nope, i have not tried opening a ticket, mine is a grey import from China.
There is something terribly wrong somewhere hardware wise. The audiofx problem only happens if i flash the CM11s. After ColourOS i have tried flashing the CM11 M8.
Im also wondering if i should try to use this OPO made rom to see if it can help.
https://forums.oneplus.net/threads/rom-official-4-4-4-oneplus-aosp.65482/
Click to expand...
Click to collapse
Give it a go, not much to lose. Didn't work for me, though.
JP.
Sent from my Nexus 5 running stock rooted AOSP on Yank555.lu v1.0-alpha5 kernel.
This worked for me! I'm back in business! Thanks guys for getting this figured out, I thought my phone was done.
I hate to bring this back up.
I have a Nandroid of my stock CM11S on my phone. I used it for the update to 300 to get firmware, then made a backup of it and went back to the custom Rom I had been on.
Today, I went and restored the backup of CM11S to sideload the newest update. Weirdly, after restoring I have an unknown baseband. But if I go back to the custom Rom backup I still have a baseband.
I wonder if TWRP just didn't backup the correct partitions? I am on the offficial TWRP. But I do have a backup that contains my EFS backup from the other TWRP that has that option.
I think I know what corrupted my efs....I used the official twrp 2.7.1.1 which for some reason saves modemst1. I remember restoring st1 when I corrupted it the first time with the official 2.7.1.1. Well I did it again trying to restore a nandroid with the official twrp 2.7.1.1. Do not restore the saved modemst1 from the official twrp 2.7.1.1. You will encounter problems.
So, this same thing happened to me...i happily using 30O and not really any issues and getting good battery life~17 hrs w/moderate use. And no other bugs.
Found the 33R update here on the forums and downloaded it and flashed through TWRP.
Thats when trouble found me, lost network and wifi stuck trying to turn on but never finds wifi. Then reading through xda someone suggested to check IMEI and it was gone. I had NOT done any prior back ups other than Nandroid prior to flashing update.
Restore still didn't fix it.
I tried this (flash ColorOS and CM11) but still didnt fix it. I was bummed as my OPO is very new and I had been happy with it.
CM11 or by restore, windows will not detect it even with drivers loaded. Flashing colorOS would allow windows XP to recognize internal and allow me to send files so i tried custom ROMs and CM stock and Mahdi but none worked. Luckily my TWRP still works and i am able to boot and get into fasboot.
I finally got mine fixed with rooted stock 33R from here on xda!
Now my OPO is back in business!!!
Save st1 and st2 with vonnegut's method http://forum.xda-developers.com/showthread.php?p=54623075.. Put it in a safe place for later. I uploaded them to google drive and onedrive . It saved me today.
For those of you that were able to recover, did you lose your entire EFS folder? Mine is completely gone and I don't think this ColorOS trick works either. I've tried it all last night and I fell asleep at my desk
Hey All,
Having an odd issues with Nougat and my proximity sensor. Was curious is anyone else has experienced this.
So, it seems like when I run Nougat ROMs my proximity sensor doesn't work. When I get a call and place the phone up to my ear, the screen turns off. However, when I pull the phone away from my head the screen doesn't turn back on. Even when I hit the power button the screen still stays blank and does so until after the call is ended (by the other person).
So I did some flashing of different things and this is what I found...
I flashed a couple Nougat ROMs (DigitalHigh and WETA, I think) and had the same blank screen issue. I then tried flashing the stock Nougat image (NBD90X) from Google and that also had the same issue. From there, I flashed back to Google's stock Marshmallow image (MTC20L) and the issue went away. I then upgraded to Nougat from stock MTC20L and I didn't have the issue. Everything worked fine after that upgrade.
Anyone have any ideas as to why the upgrade worked fine but the stock Nougat images and other Nougat ROMs don't?
Also, for the record, I don't have a screen protector on the phone.
TheRectified said:
Hey All,
Having an odd issues with Nougat and my proximity sensor. Was curious is anyone else has experienced this.
So, it seems like when I run Nougat ROMs my proximity sensor doesn't work. When I get a call and place the phone up to my ear, the screen turns off. However, when I pull the phone away from my head the screen doesn't turn back on. Even when I hit the power button the screen still stays blank and does so until after the call is ended (by the other person).
So I did some flashing of different things and this is what I found...
I flashed a couple Nougat ROMs (DigitalHigh and WETA, I think) and had the same blank screen issue. I then tried flashing the stock Nougat image (NBD90X) from Google and that also had the same issue. From there, I flashed back to Google's stock Marshmallow image (MTC20L) and the issue went away. I then upgraded to Nougat from stock MTC20L and I didn't have the issue. Everything worked fine after that upgrade.
Anyone have any ideas as to why the upgrade worked fine but the stock Nougat images and other Nougat ROMs don't?
Also, for the record, I don't have a screen protector on the phone.
Click to expand...
Click to collapse
It is peculiar. I have flashed about every factory image clean when they come out and my proximity has always worked. There was an issue where certain devices had locked up sensors about a year ago but that was on MM and I think it was just a hardware problem. Maybe it's early symptoms of that specific problem.
TheRectified said:
Hey All,
Having an odd issues with Nougat and my proximity sensor. Was curious is anyone else has experienced this.
So, it seems like when I run Nougat ROMs my proximity sensor doesn't work. When I get a call and place the phone up to my ear, the screen turns off. However, when I pull the phone away from my head the screen doesn't turn back on. Even when I hit the power button the screen still stays blank and does so until after the call is ended (by the other person).
So I did some flashing of different things and this is what I found...
I flashed a couple Nougat ROMs (DigitalHigh and WETA, I think) and had the same blank screen issue. I then tried flashing the stock Nougat image (NBD90X) from Google and that also had the same issue. From there, I flashed back to Google's stock Marshmallow image (MTC20L) and the issue went away. I then upgraded to Nougat from stock MTC20L and I didn't have the issue. Everything worked fine after that upgrade.
Anyone have any ideas as to why the upgrade worked fine but the stock Nougat images and other Nougat ROMs don't?
Also, for the record, I don't have a screen protector on the phone.
Click to expand...
Click to collapse
I am having this same exact issue ever since I got Nougat. I am not rooted and am running the OTA upgrade. I've been hesitant to reset to factory settings but I may try that later tonight.
abenco said:
I am having this same exact issue ever since I got Nougat. I am not rooted and am running the OTA upgrade. I've been hesitant to reset to factory settings but I may try that later tonight.
Click to expand...
Click to collapse
Oddly enough, the OTA update is the only thing that worked on mine.
Gizmoe said:
It is peculiar. I have flashed about every factory image clean when they come out and my proximity has always worked. There was an issue where certain devices had locked up sensors about a year ago but that was on MM and I think it was just a hardware problem. Maybe it's early symptoms of that specific problem.
Click to expand...
Click to collapse
It really is weird. I'm back on MM now and its working fine. I guess I stay here until the next build comes up and then I'll see what happens.
Same issue here. stock rom, received OTA and now I have the excess battery use, and thanks to the post boss above, the same proximity sensor issue. Phone goes black in middle of call with no way to get back to the screen to hang up, change to speakerphone, etc. It stays black sometimes, even after the other party hangs up, requiring me to reboot. PITA.
Resetting the phone did nothing to fix the problem. The only way to revert back to MM is to root the phone first, correct?
abenco said:
Resetting the phone did nothing to fix the problem. The only way to revert back to MM is to root the phone first, correct?
Click to expand...
Click to collapse
You have to unlock the bootloader but thats pretty much it. After you flash you can relock it if you want.
I could fix that problem by removing the screen protector.
abenco said:
Resetting the phone did nothing to fix the problem. The only way to revert back to MM is to root the phone first, correct?
Click to expand...
Click to collapse
No not rooting. You have to unlock the bootloader and then fastboot flash a factory image. It's best to leave the bootloader unlocked too, unless you are going to leave it stock and never tinker with it again. But if you ever need to flash an image again or use twrp or anything fastboot related you will need an unlocked bootloader.
I have the same problem with my phone. Android 7.1 seems to fix this.
Enviado de meu Nexus 6P usando Tapatalk
I had the same problem, but fixed it by installing a sensor reset app from Play Store, then uninstalled the app.
Just talked to Huawei tech support. My 6P wasn't rotating the screen and whenever I was in a call, wouldn't dim the screen. Such a small feature but we all take it for granted. Anyway, she told me to enter recovery (Power+Volume Up) and "Wipe Cache Partition" rebooted and running like a champ. ?
Hello guys !
I was rocking OOS 4.5.3 with TWRP and root all fine, and I tried some dualboot stuff that I saw here on XDA (plot twist, don't try it) and then I ran into issues
I managed to reinstall the rom fine, but at the reboot, my fingerprint sensor wasn't picking up my fingers
I found out that when I try to register a fingerprint, it works fine, untill the last step where it stop picking my finger (not even vibrates)
I also noticed that it's impossible to delete a stored fingerprint
Any ideas ?
GMX1PT said:
Hello guys !
I was rocking OOS 4.5.3 with TWRP and root all fine, and I tried some dualboot stuff that I saw here on XDA (plot twist, don't try it) and then I ran into issues
I managed to reinstall the rom fine, but at the reboot, my fingerprint sensor wasn't picking up my fingers
I found out that when I try to register a fingerprint, it works fine, untill the last step where it stop picking my finger (not even vibrates)
I also noticed that it's impossible to delete a stored fingerprint
Any ideas ?
Click to expand...
Click to collapse
On man I'm in totally the same situation with you! I tried that dualboot too and stuck in boot screen, so i flashed the original rom zip and managed to boot well but the fingerprint isn't working any more......:crying:waiting for solutions
Okay, now that I woke up I will try to do a data wipe, I'll tell you about it, please do tell me if you find something
I'm also unable to activate wifi
Sounds like a good question for the dual boot thread.
If I remember right from previous threads about dual boot on other devices is, you should delete your original fingerprint or set it up as no lock before doing all the stuff with dual boot. I might be wrong.
ab7casper said:
Sounds like a good question for the dual boot thread.
If I remember right from previous threads about dual boot on other devices is, you should delete your original fingerprint or set it up as no lock before doing all the stuff with dual boot. I might be wrong.
Click to expand...
Click to collapse
Well, can't see where it is listed in the instructions, but thankfully this issue is nothing a full wipe can't fix
GMX1PT said:
Well, can't see where it is listed in the instructions, but thankfully this issue is nothing a full wipe can't fix
Click to expand...
Click to collapse
It's not, it was just a user having that issue on a Nexus 6P. Reset should fix. Set it up without a lock on it, then you should be able to set up fingerprints for each rom.
Thinking about. It, that sounds like a lot of hassle if you just want to try out different roms quickly.
GMX1PT said:
I'm also unable to activate wifi
Click to expand...
Click to collapse
I did not do this dual boot but I ran into WiFi not activating (endless searching for a WiFi access point), but I was able to fix it. Your probably uninterested in how I got into the situation but I fixed it with a previous nandroid backup done with one of the earlier versions of TWRP. Here are the steps that recovered WiFi:
Using TWRP, advance wipe Dalvik & Cache
Restore from a nandroid backup (OOS v4.5.2 in this case) ONLY system & /System
Reboot into the system and ignore TWRP's no OS warning
Using TWRP, advance wipe Dalvik & Cache
Reboot back into TWRP recovery and flash the Full v4.5.5 OTA file (~1.6GB) AND flash root (e.g. SuperSU)
Clear Dalvik&Cache and reboot into the system
After I did that everything return back to normal including the WiFI issue. The fingerprint scanner is working normally and I never lost any data what so ever.
Could someone help me fix my OnePlus5?
Simply from one day to the other the Touch screen stopped working, I can not select any option, being possible only by physical button.
I can not enter Recovery Mode because when I first connected the device I have already entered a password, so I can not type the password because the touch does not work.
I do not know what else to do!!!
I have the OTG cable from OnePlus and even putting Mouse or Keyboard, both do not work.
Would anyone have other suggestions?
Follow the compressed video showing the recovery mode locked by password, touch does not work.
And photo from FastBoot Mode Screen.
Any updates on how you fixed this or what the problem was?
I had to RMA, motherboard was replaced.
I have the same problem
My screen stoped working and the recovery mode is protected with password like the video sent, i live in Brazil and here i dont have the RMA option, can someone help me?
_-^SORCERER^-_ said:
Could someone help me fix my OnePlus5?
Simply from one day to the other the Touch screen stopped working, I can not select any option, being possible only by physical button.
I can not enter Recovery Mode because when I first connected the device I have already entered a password, so I can not type the password because the touch does not work.
I do not know what else to do!!!
I have the OTG cable from OnePlus and even putting Mouse or Keyboard, both do not work.
Would anyone have other suggestions?
Click to expand...
Click to collapse
i was facing this and fixed it.
just use unbrick tool
after the phone boot up and touchscreens still doesn't work, just do a reboot
Tks @Apayah, Will try this procedure, and return with status.
@Apayah, theoretically OnePlus 5 returned works, I will wait a few days to see if the problem continues.
Thank you so much.
edujmjr said:
My screen stoped working and the recovery mode is protected with password like the video sent, i live in Brazil and here i dont have the RMA option, can someone help me?[/QUOTE @edujmjr I used the unbrick process and now works.
Try this process.
Enviado de meu ONEPLUS A5000 usando Tapatalk
Click to expand...
Click to collapse
_-^SORCERER^-_ said:
@Apayah, theoretically OnePlus 5 returned works, I will wait a few days to see if the problem continues.
Thank you so much.
Click to expand...
Click to collapse
Np, all good now?
Apayah said:
Np, all good now?
Click to expand...
Click to collapse
At this moments, yes, I will wait more days.
Thanks for your support in this problem.
_-^SORCERER^-_ said:
At this moments, yes, I will wait more days.
Thanks for your support in this problem.
Click to expand...
Click to collapse
no problem
Apayah said:
i was facing this and fixed it.
just use unbrick tool
after the phone boot up and touchscreens still doesn't work, just do a reboot
Click to expand...
Click to collapse
I'm facing the same issue . My phone was working perfectly fine one minute and then the next, the screen stopped responding including the two capacitive buttons. I rebooted it thinking it mgiht fix it, but now i"m stuck on the lockscreen.
Could you point me to the unbrick tool? Is it this one:
https://forum.xda-developers.com/oneplus-5/how-to/unbrick-tool-oneplus-5-t3648169
Does it do a factory reset or would it fix the unresponsive touchscreen issue without any loss of data?
CoCoGirl886 said:
I'm facing the same issue . My phone was working perfectly fine one minute and then the next, the screen stopped responding including the two capacitive buttons. I rebooted it thinking it mgiht fix it, but now i"m stuck on the lockscreen.
Could you point me to the unbrick tool? Is it this one:
https://forum.xda-developers.com/oneplus-5/how-to/unbrick-tool-oneplus-5-t3648169
Does it do a factory reset or would it fix the unresponsive touchscreen issue without any loss of data?
Click to expand...
Click to collapse
your bootloader unlocked ?, if you're on twrp, then do a back up via mtp.
yes i was use that one, well i was do factory data reset and still touchscreen was didn't work, i was still on twrp so i backing up all my data before i mess with it.
I've also had this issue already had the MB replaced but I had my new MB lost touch for about 5min today so i'll see if it gets worse like it did last time.
Apayah said:
your bootloader unlocked ?, if you're on twrp, then do a back up via mtp.
yes i was use that one, well i was do factory data reset and still touchscreen was didn't work, i was still on twrp so i backing up all my data before i mess with it.
Click to expand...
Click to collapse
I got an usb-c to OTG cable and was able to use the mouse in trwp. I followed a guide online to get past the lockscreen by deleting the lockscreen key files. After I did that, my screen just magically started working again. But now when I boot into the phone, it swipes to unlock but I can't access anything. It looks like it may be encrypted or something? I tried to set a new password to a pin/pattern but it won't save.
When I boot into trwp, it asks me to enter a password but I never had one? I tried using "default_password" and also using the numbers to represent the pattern but still doesn't work. Any idea how I can access my files or get my phone to boot up fully? I'm trying to avoid a factory reset, :crying:
CoCoGirl886 said:
I got an usb-c to OTG cable and was able to use the mouse in trwp. I followed a guide online to get past the lockscreen by deleting the lockscreen key files. After I did that, my screen just magically started working again. But now when I boot into the phone, it swipes to unlock but I can't access anything. It looks like it may be encrypted or something? I tried to set a new password to a pin/pattern but it won't save.
When I boot into trwp, it asks me to enter a password but I never had one? I tried using "default_password" and also using the numbers to represent the pattern but still doesn't work. Any idea how I can access my files or get my phone to boot up fully? I'm trying to avoid a factory reset, :crying:
Click to expand...
Click to collapse
Ahh i never facing like that, try using multirom twrp ? At least at this moment you need to backup you're data.
You mean lockscreen thingy on data/system? There's a 3 files i guess and if you delete that, yes you can pass your screen.
I have no idea if twrp asked for a password, before this happened you're decrypted or encrypted? Password on twrp only for encrypted i think
Apayah said:
Ahh i never facing like that, try using multirom twrp ? At least at this moment you need to backup you're data.
You mean lockscreen thingy on data/system? There's a 3 files i guess and if you delete that, yes you can pass your screen.
I have no idea if twrp asked for a password, before this happened you're decrypted or encrypted? Password on twrp only for encrypted i think
Click to expand...
Click to collapse
I deleted the 5 files in data/system and passed the lockscreen. But it doesn't let me see any information . I think I was probably encrypted since I don't believe I decrypted anything. I can't backup my data in twrp because without entering the password my files have a lot of folders that look like "WDAbwwoefdFZZfde." Before I deleted the keys, twrp asks me to enter my password which is a pattern, same one as when i start my phone. After I deleted the lockscreen keys, trwp asks me to type a password from letters or numbers.
Do you think if I were to dirty flash my rom again without wiping, that it will recreate the lock keys and decrypt my data? Without having to use multirom twrp?
CoCoGirl886 said:
I deleted the 5 files in data/system and passed the lockscreen. But it doesn't let me see any information . I think I was probably encrypted since I don't believe I decrypted anything. I can't backup my data in twrp because without entering the password my files have a lot of folders that look like "WDAbwwoefdFZZfde." Before I deleted the keys, twrp asks me to enter my password which is a pattern, same one as when i start my phone. After I deleted the lockscreen keys, trwp asks me to type a password from letters or numbers.
Do you think if I were to dirty flash my rom again without wiping, that it will recreate the lock keys and decrypt my data? Without having to use multirom twrp?
Click to expand...
Click to collapse
Right seems encrypted problems, did you try multirom twrp yet? Should be on GZR xda thread
My OnePlus 5 stop Work again.
Enviado do meu iPhone usando Tapatalk
Hi all
So i installed AICP 14, all worked fine, wanted Dt2W so put Fk r77 kernel on and within an hour i got a reboot while talking on the phone, then a strange error with my keyboard not working (not sure if both problems were kernel related but never had them before).
I had done a twrp backup before installing the kernel so i thought i can live without Dt2W i restored from the backup, BUT this i when i realised i had fkd up because i hadn't taken off my pattern lock before doing the backup.....so the restore didnt work(got an error at end of running the restore and phone hung on google screen)
So luckily i still had my Oreo back up, restored that and that works fine.
But now when i try a fresh install of any Pie rom (Tried AICP and RR) the sim card isnt detected? Did i quick google yesterday and ran some #*#*4636*#*# service code which reported there was no IEMI number?
So is it a EFS partition problem?
Tia.
r3k0 said:
Hi all
So i installed AICP 14, all worked fine, wanted Dt2W so put Fk r77 kernel on and within an hour i got a reboot while talking on the phone, then a strange error with my keyboard not working (not sure if both problems were kernel related but never had them before).
I had done a twrp backup before installing the kernel so i thought i can live without Dt2W i restored from the backup, BUT this i when i realised i had fkd up because i hadn't taken off my pattern lock before doing the backup.....so the restore didnt work(got an error at end of running the restore and phone hung on google screen)
So luckily i still had my Oreo back up, restored that and that works fine.
But now when i try a fresh install of any Pie rom (Tried AICP and RR) the sim card isnt detected? Did i quick google yesterday and ran some #*#*4636*#*# service code which reported there was no IEMI number?
So is it a EFS partition problem?
Tia.
Click to expand...
Click to collapse
Very likely corrupt radio. Try reflash stock rom before trying top flash a pie rom
ok, downloaded the last stock from google, twrp gave an error when trying to install it? wrong kind of zip ?
r3k0 said:
ok, downloaded the last stock from google, twrp gave an error when trying to install it? wrong kind of zip ?
Click to expand...
Click to collapse
Late Reply...Just Read it today
Stock factory files can be flashed through fastboot don't you know that?
And your problem got solved or not?