I am on stock C456B385 and seem Smart key funtion not work. I set it on and assign Press in Flasflight then check nut it not turn on. Current I am on stock with unlocked bootloader. Anyone can explain?
I don't know what causes it but, try activating swipe on the fingerprint scanner for notification panel (as I've seen in a reddit thread)
PalakMi said:
I don't know what causes it but, try activating swipe on the fingerprint scanner for notification panel (as I've seen in a reddit thread)
Click to expand...
Click to collapse
Swipe for notifications work fine.Only smart key not work
blackbuffalo said:
Swipe for notifications work fine.Only smart key not work
Click to expand...
Click to collapse
I don't know how to help now
I did it before post o question here, no luck
Rommco05 said:
I sure before unlocked bootloader work Smart key? Try relock bootoader and reinstall rom, don't know why Smart wont work, never see before
Click to expand...
Click to collapse
Never try when bootloader is locked, cause I bought it, update to latest build then unlock and flash customer rom
Rommco05 said:
You are on custom rom? I maybe this rom just not support smart key
Click to expand...
Click to collapse
I mean when I am on stock. Not say about on Customer rom, I known this feature not available on AOSP rom
PS: You on stock and it work? Your device rooted or not? Bootloader status?
How about reflashing the firmware
PalakMi said:
How about reflashing the firmware
Click to expand...
Click to collapse
I tested on fresh flash. I back to B360 then OTA to B385 (without relock bootloader)and did a factory reset. And test smart key but not luck
blackbuffalo said:
I tested on fresh flash. I back to B360 then OTA to B385 (without relock bootloader)and did a factory reset. And test smart key but not luck
Click to expand...
Click to collapse
I think you should send it to repair
PalakMi said:
I think you should send it to repair
Click to expand...
Click to collapse
It not sold in my country. I bought via swappa. And I thinks software think. Because, my finger print still work fine
blackbuffalo said:
It not sold in my country. I bought via swappa. And I thinks software think. Because, my finger print still work fine
Click to expand...
Click to collapse
That's good news that fp is working! Maybe you're right. However it's a sensor/hardware button, so maybe the button doesn't function while the sensor is working.
I hope it is software issue
All the best, buddy.
Rommco05 said:
That's look like this firmware not support Smart key
Click to expand...
Click to collapse
No, every official firmware support smart key
There's something (which we don't know) that keeps it not working.
blackbuffalo said:
It not sold in my country. I bought via swappa. And I thinks software think. Because, my finger print still work fine
Click to expand...
Click to collapse
have you tried clearing the data and cache for Smart Key app? perhaps better to Force Stop the app, clean its data and cache then restart the phone.
He tried factory reset, which means data of smart key app have been cleared.
It's so hard to figure out what causes it
I doubt that, I didn't face this issue no matter what I've done.
I guess this leads to the possibility of hardware issue
Perhaps the final test would be to do a rollback to marshmallow rom, just in case. If that didn't work, service center it is then.
That's a great suggestions, I hope it turns out a software issue.
Rommco05 said:
This can be issue if is used some theme, I using AOSP N theme and here missing setting for auto screen on notification
Click to expand...
Click to collapse
Hey I just realized this option is missing for me as well and I'm running a theme. When u remove the theme does the option come back? I had set it as on but I can't see it anymore.
Sent from my Honor 8 using XDA Labs
[/COLOR]
blackbuffalo said:
I am on stock C456B385 and seem Smart key funtion not work. I set it on and assign Press in Flasflight then check nut it not turn on. Current I am on stock with unlocked bootloader. Anyone can explain?
Click to expand...
Click to collapse
Strange. Are you actually pressing the button and not simply laying your finger on top?
Related
Hi, so I was using my opo with stock CM11S without a hitch and when I took the phone out and hit the power button to show the lock screen it didn't respond. I had to switch the phone off and on by long pressing power button and every time the phone goes to sleep I have to do this all over. How do I stop this?
lockscreen
Bridge Ric said:
Hi, so I was using my opo with stock CM11S without a hitch and when I took the phone out and hit the power button to show the lock screen it didn't respond. I had to switch the phone off and on by long pressing power button and every time the phone goes to sleep I have to do this all over. How do I stop this?
Click to expand...
Click to collapse
Go into Settings->Security->Screen lock and try a different screen lock setting. Reboot the phone. Set it back to original. Reboot. Cross your fingers.
You can try toggling the double-tap to wake gesture, too.
Didnt work mate
proximity sensor?
Bridge Ric said:
Didnt work mate
Click to expand...
Click to collapse
Google "power button doesn't unlock oneplus":
https://forums.oneplus.net/threads/power-button-doesnt-unlock-neither-double-tap.292269/
Among other google-y things.
P.S.--glad you tried.
pbergonzi said:
Google "power button doesn't unlock oneplus":
https://forums.oneplus.net/threads/power-button-doesnt-unlock-neither-double-tap.292269/
Among other google-y things.
P.S.--glad you tried.
Click to expand...
Click to collapse
I disabled Prevent Accidental WAkeup blah and it worked!
great
Bridge Ric said:
I disabled Prevent Accidental WAkeup blah and it worked!
Click to expand...
Click to collapse
Nice move--glad you fixed it, and thanks for reporting back--that'll be the first thing I say next time someone asks.
Well you know..., either that or "use google."
Bridge Ric said:
I disabled Prevent Accidental WAkeup blah and it worked!
Click to expand...
Click to collapse
This hasn't actually fixed the problem. I'm guessing you recently went from a Lollipop ROM back to KitKat on CM11S, right? Did you flash the KitKat modem first?
Transmitted via Bacon
timmaaa said:
This hasn't actually fixed the problem. I'm guessing you recently went from a Lollipop ROM back to KitKat on CM11S, right? Did you flash the KitKat modem first?
Transmitted via Bacon
Click to expand...
Click to collapse
I did. I read about how not flashing the modems can do stuff like screen going dead on calls and stuff but I can't be bothered to flash it as we're so close to CM12S anyway so when I update to that the issues will go away anyway
Bridge Ric said:
I did. I read about how not flashing the modems can do stuff like screen going dead on calls and stuff but I can't be bothered to flash it as we're so close to CM12S anyway so when I update to that the issues will go away anyway
Click to expand...
Click to collapse
You can't be bothered? It's a simple zip flash in TWRP, takes 15 seconds.
Transmitted via Bacon
Hello
I'm a703l stock user. I recently upgraded to b211 and it's my worst android experience, here's why
Very unstable, alot " stop responding" toasts
Android wear doesn't work
Can't create homescreen shortcuts
Lots of apps doesn't support
Every app needs manual permission adjustment in order to work.
It's like revert back to dos, you need to do everything!
What should I do to change to a good 5.1 rooted stable Rom?
Thanks
Chen
have you made after a factory reset?
for me works better the B211 with a Factory Reset comes from B112
Hi, thanks for replying, I tried to do factory reset twice, and still.
My main problem at the moment is that android wear doesnt connect, I tried three different versions of wear and theres a bug. I hit connect and nothing happend
I am on B201 from 702L,works fine,but i can not say,if works with Android Wear.
I tried to install twtp but when im at fastboot,.after I commanded to burn the recovery image I'm receiving a " operation failed - access not allowed)
I have a unlocked bootloader.
Any one may know the problem?
letschky said:
have you made after a factory reset?
for me works better the B211 with a Factory Reset comes from B112
Click to expand...
Click to collapse
Does Multi-screen work for you after a factory reset on B211? A couple of us have noticed it does not work on B211 but I did not do a factory reset, not sure if it helps with this issue.
I don't have a multi screen adapter do I can't tell.
Can you please give me a link to a twrp installation guide that you used?
I tried several at Google and I receiving a error when I tried to burn the recovery
E--Man said:
Does Multi-screen work for you after a factory reset on B211? A couple of us have noticed it does not work on B211 but I did not do a factory reset, not sure if it helps with this issue.
Click to expand...
Click to collapse
I think factory reset help not with this issue,i am not on B211,i am on B201 from 702L
---------- Post added at 04:16 PM ---------- Previous post was at 04:10 PM ----------
chsiboni said:
I don't have a multi screen adapter do I can't tell.
Can you please give me a link to a twrp installation guide that you used?
I tried several at Google and I receiving a error when I tried to burn the recovery
Click to expand...
Click to collapse
http://forum.xda-developers.com/mediapad-x2/development/recovery-twrp-gem-703l-t3215815
Thank you, ill try tomorrow and update
youre tip did helped, but it seem like i did a mistake, i flashed a twrp 6 version and installed a 5.1.1 rom. i now stuck at bootloop where i see " honor powered by android" and nothing happend.
i flashed a 5.1.1 twrp and reintalled the rom but the problem seem to continue
can you please help me or give a usfel link?
by the way fastboot and recovery still working so i assume that i good yes?
E--Man said:
Does Multi-screen work for you after a factory reset on B211? A couple of us have noticed it does not work on B211 but I did not do a factory reset, not sure if it helps with this issue.
Click to expand...
Click to collapse
Multi screen is working fine after OTA update to 6.0.1
But I didn't do any factory reset.
hagba said:
Multi screen is working fine after OTA update to 6.0.1
But I didn't do any factory reset.
Click to expand...
Click to collapse
Ota 6.0.1?
Which Versionsnumber?
letschky said:
Ota 6.0.1?
Which Versionsnumber?
Click to expand...
Click to collapse
Sorry That should have been 6.0,mixed up with S7E.
hagba said:
Sorry That should have been 6.0,mixed up with S7E.
Click to expand...
Click to collapse
Hagop, are you on the B211 OTA stock non-rooted update? We on the B211 have not been able to get Multi-screen to work on this update.
Maybe you can post a screenshot? In the Notifications, if you click on "Multi-screen" icon, do you see any other devices expect besides "Me"? Thanks.
hagba said:
Sorry That should have been 6.0,mixed up with S7E.
Click to expand...
Click to collapse
Ok,no Problem,thanks
E--Man said:
Hagop, are you on the B211 OTA stock non-rooted update? We on the B211 have not been able to get Multi-screen to work on this update.
Maybe you can post a screenshot? In the Notifications, if you click on "Multi-screen" icon, do you see any other devices expect besides "Me"? Thanks.
Click to expand...
Click to collapse
Here you go:
Two TVs one in the siting room the other in the bedroom, and yes mine is stock and unrooted.
E--Man said:
Hagop, are you on the B211 OTA stock non-rooted update? We on the B211 have not been able to get Multi-screen to work on this update.
Maybe you can post a screenshot? In the Notifications, if you click on "Multi-screen" icon, do you see any other devices expect besides "Me"? Thanks.
Click to expand...
Click to collapse
Did you try with the TV's Mirroring Settings?On the TV go to the settings,Mirroring,Registered devices,and click on GEM-703L and see what happens.
hagba said:
Did you try with the TV's Mirroring Settings?On the TV go to the settings,Mirroring,Registered devices,and click on GEM-703L and see what happens.
Click to expand...
Click to collapse
Wait, are you using a third party app to cast your device to the TV, or, are you using the built-in way using one of the methods in the screenshots below?
E--Man said:
Wait, are you using a third party app to cast your device to the TV, or, are you using the built-in way using one of the methods in the screenshots below?
View attachment 3803412
View attachment 3803413
Click to expand...
Click to collapse
You can see from my post #16 that I'm using the built in application, NO third party app whatsoever.
However I think that you should try to Factory Restore your TV, yes the TV and not the device.
hagba said:
You can see from my post #16 that I'm using the built in application, NO third party app whatsoever.
However I think that you should try to Factory Restore your TV, yes the TV and not the device.
Click to expand...
Click to collapse
Hi Hagop,
Sorry you are correct, your screenshot in post #16 was not displaying for me when I posted earlier. I will definitely try to reset one of my receiving devices to see if it makes a difference but all of my displaying devices are K0di and not a TV. It looks like it's a DLNA issue with device detection since it had no issue detecting your Sony Bravia TV!
Have you used any other non-TV devices successfully?
I was able to flash the rooted boot.img, but it seems to have caused a problem with the fingerprint sensor. It works a little after a fresh reboot, but then it stops working completely. Anyone have an idea as to why and maybe how I can fix it?
i have the same problem, you fix it?
Probably, incompatible Boot
Try flash stock Boot back and check Fingerprint
5[Strogino] said:
Probably, incompatible Boot
Try flash stock Boot back and check Fingerprint
Click to expand...
Click to collapse
yeah, but we dont have the stock boot, we have tha us version c567 and its not online yet
Same problem
Abumarf said:
I was able to flash the rooted boot.img, but it seems to have caused a problem with the fingerprint sensor. It works a little after a fresh reboot, but then it stops working completely. Anyone have an idea as to why and maybe how I can fix it?
Click to expand...
Click to collapse
Hi Abumarf and depooltrd,
I have the same symptoms. I've flashed boot.img from C432 (rooted now) to my C567. It was the only way to unbrick it.
What region is rooted boot.img you flashed from. Do you think it is a software problem, not a hardware one?
Also, could anyone who has rooted MHA-L29C567B138 confirm that the fingerprint sensor works fine?
night_wind said:
Hi Abumarf and depooltrd,
I have the same symptoms. I've flashed boot.img from C432 (rooted now) to my C567. It was the only way to unbrick it.
What region is rooted boot.img you flashed from. Do you think it is a software problem, not a hardware one?
Also, could anyone who has rooted MHA-L29C567B138 confirm that the fingerprint sensor works fine?
Click to expand...
Click to collapse
I'm not sure as to what region I flashed but I can guarantee you it's a software problem. After checking the System/Bin/ it was clear that the fingerprintID folder and a few others were missing. This is most likely what causes the Fingerprint sensor to no longer work. All we can do is wait for Huawei to release the complete C567 update so we can revert to complete stock.
Abumarf said:
I can guarantee you it's a software problem. After checking the System/Bin/ it was clear that the fingerprintID folder and a few others were missing.
Click to expand...
Click to collapse
That is promising. So did you notice these problems right after you had flashed the boot.img?
BTW, it could work for hours after a fresh restart for me. What about yours?
night_wind said:
That is promising. So did you notice these problems right after you had flashed the boot.img?
BTW, it could work for hours after a fresh restart for me. What about yours?
Click to expand...
Click to collapse
Yes, as soon as I flashed both boot images that I had. One with root and the other with stock. I asked around and a dev buddy of mine told me that the KangVIP root isn't always interchangeable with the non-KangVIP roms. It was the same case for the Mate 8. Mine works for a few minutes at most, but I did flash an unknown stock boot image though it did nothing. It's a pain to live without a fingerprint sensor
Abumarf said:
Yes, as soon as I flashed both boot images that I had. One with root and the other with stock. I asked around and a dev buddy of mine told me that the KangVIP root isn't always interchangeable with the non-KangVIP roms. It was the same case for the Mate 8. Mine works for a few minutes at most, but I did flash an unknown stock boot image though it did nothing. It's a pain to live without a fingerprint sensor
Click to expand...
Click to collapse
I've just ran into this same issue, you think someone could just upload the missing files?
posydon1 said:
I've just ran into this same issue, you think someone could just upload the missing files?
Click to expand...
Click to collapse
I don't think so but I think there may be some hope. Ajsmsg78 released a full root and encryption guide (https://forum.xda-developers.com/mate-9/development/root-root-mate-9-t3556590) which I'm going to try from the complete beginning later to see if it'll restore functionality.
Abumarf said:
I don't think so but I think there may be some hope. Ajsmsg78 released a full root and encryption guide (https://forum.xda-developers.com/mate-9/development/root-root-mate-9-t3556590) which I'm going to try from the complete beginning later to see if it'll restore functionality.
Click to expand...
Click to collapse
That's exactly how I ended up here lol. His method works great but some file are still missing.
posydon1 said:
That's exactly how I ended up here lol. His method works great but some file are still missing.
Click to expand...
Click to collapse
Then we may be stuck until Huawei releases the C567 update. It's pretty disappointing that we seem to be the only version without an update even after almost a month and a half from release. :crying:
Abumarf said:
Then we may be stuck until Huawei releases the C567 update. It's pretty disappointing that we seem to be the only version without an update even after almost a month and a half from release. :crying:
Click to expand...
Click to collapse
Hey Abumarf,
Looks like Huawei released the new MHA-L29C567B167 and also decrypted-boot-MHA-L29C567B138.img has appeared as well. Did you try to flash any of them? Did it fix the fingerprint sensor?
night_wind said:
Hey Abumarf,
Looks like Huawei released the new MHA-L29C567B167 and also decrypted-boot-MHA-L29C567B138.img has appeared as well. Did you try to flash any of them? Did it fix the fingerprint sensor?
Click to expand...
Click to collapse
No I haven't as of yet. I've been trying to download the C567B167 OTA through Firmware Finder but it wasn't working for me. I also haven't had much time to look into it. If you or anyone else do end up trying either of the solutions, please let me know.
Abumarf said:
No I haven't as of yet. I've been trying to download the C567B167 OTA through Firmware Finder but it wasn't working for me. I also haven't had much time to look into it. If you or anyone else do end up trying either of the solutions, please let me know.
Click to expand...
Click to collapse
I tried decrypted-boot-MHA-L29C567B138.img and it fixed the fingerprint sensor, but I didn't manage to restore data partitions and the ROM wasn't full. Finally, I updated through FunkyHuawei and everything works fine now.
night_wind said:
I tried decrypted-boot-MHA-L29C567B138.img and it fixed the fingerprint sensor, but I didn't manage to restore data partitions and the ROM wasn't full. Finally, I updated through FunkyHuawei and everything works fine now.
Click to expand...
Click to collapse
I also did just that but just fixed the problem with the Huawei apps and system update by changing a few file names. Works like a charm now. Will wait till Monday and attempt to flash the B167 update. But as of now, I'm fully root, decrypted, and enjoying life!
Im using Huawei Honor 4c running OS v4.4.2. Now I want to update my device OS with v6.0 EMUI 4. I found one on official website but with different build number. My device build number is V100R001C185B130 but firmware on website has build number C185B503. Will there be any issue if I upgrade firmware?
Also do I have need to first upgrade from Kitkat to Lollipop and then Marshmallow, or I can directly upgrade from Kitkat to Marshmallow?
I'm wishing to upgrade official firmware availabe on Huawei website.
If the firmware is wrong the update will fail and device will stay in previous state.
Trying to go straight to Marshmallow won't cause any issues, update will fail before starting if it doesn't work.
keikari said:
If the firmware is wrong the update will fail and device will stay in previous state.
Trying to go straight to Marshmallow won't cause any issues, update will fail before starting if it doesn't work.
Click to expand...
Click to collapse
Okay, thanks for your reply. I will report you after flashing.
And can I upgrade it putting in device storage, but not in external sd card?
asdkazmi said:
Okay, thanks for your reply. I will report you after flashing.
And can I upgrade it putting in device storage, but not in external sd card?
Click to expand...
Click to collapse
No idea. But trying it won't cause problems.
I tied to upgrade firmware both normally and force upgrade but it gives me error
"Version check fail"
keikari said:
No idea. But trying it won't cause problems.
Click to expand...
Click to collapse
first I tried with Marshmallow but it gives me error "Version check failed". Then I tried to upgrade it into Lollipop, at start in upgrade it work fine but at the end of updating, it stucks, I can't update. It always stuck to end of updating.
asdkazmi said:
first I tried with Marshmallow but it gives me error "Version check failed". Then I tried to upgrade it into Lollipop, at start in upgrade it work fine but at the end of updating, it stucks, I can't update. It always stuck to end of updating.
Click to expand...
Click to collapse
Does it give some error and how long did you waited after it got stuck.
keikari said:
Does it give some error and how long did you waited after it got stuck.
Click to expand...
Click to collapse
After some wait it has successfully upgraded to lollipop but now nothing is working, touch panel and volume up/down buttons are not working. Only power button is working. Also I haven't any backup of previous android.
asdkazmi said:
After some wait it has successfully upgraded to lollipop but now nothing is working, touch panel and volume up/down buttons are not working. Only power button is working. Also I haven't any backup of previous android.
Click to expand...
Click to collapse
Try factory reset, I have never heard that anyone else has had any problems like that with normal update.
keikari said:
Try factory reset, I have never heard that anyone else has had any problems like that with normal update.
Click to expand...
Click to collapse
I tried factory reset and then volume button was working but touch panel was not working again. Now I'm upgrading it to Marshmallow and will tell you after successfully upgrade.
keikari said:
Try factory reset, I have never heard that anyone else has had any problems like that with normal update.
Click to expand...
Click to collapse
Upgraded to marshmallow but still touch is not working.... please help me
asdkazmi said:
Upgraded to marshmallow but still touch is not working.... please help me
Click to expand...
Click to collapse
This sounds dump but give it a try. Open screen and wait for it to automatically turn off. Then try again.
keikari said:
This sounds dump but give it a try. Open screen and wait for it to automatically turn off. Then try again.
Click to expand...
Click to collapse
Tried but nothing happened.
asdkazmi said:
Tried but nothing happened.
Click to expand...
Click to collapse
And touch screen works in recovery screen?
keikari said:
And touch screen works in recovery screen?
Click to expand...
Click to collapse
No, recovery works with volume and power buttons.
asdkazmi said:
No, recovery works with volume and power buttons.
Click to expand...
Click to collapse
Then it's most likely hardware issue. If you think it's software issue, you can either try to find rollback updates or install TWRP custom recovery and see if some custom rom will give your screen some life.
My wifi/BT was completely broken once and I thought it was hardware issue(factory reset and re-install didn't fixed it), but after I wiped all basic partitions in TWRP and then did stock force update, it started working.
So, what now I need to do is TWRP recovery flash?
asdkazmi said:
So, what now I need to do is TWRP recovery flash?
Click to expand...
Click to collapse
Depending on your question, the answer is either "You need to unlock bootloader." or "Yes".
keikari said:
Depending on your question, the answer is either "You need to unlock bootloader." or "Yes".
Click to expand...
Click to collapse
I just have given my device for hardware check and will tell you tomorrow.
keikari said:
Depending on your question, the answer is either "You need to unlock bootloader." or "Yes".
Click to expand...
Click to collapse
Thanks for your support. Finally, I have repaired my device and that was hardware problem.
OnePlus 7 stuck in "Your device is corrupt it can't be trusted" after locking the boo
Help. I've made a big mistake. I can only access the Bootloader. Recovery mode is not accessible.
As with the 7 Pro, I didn't like the standard 7 and decided to return it. Thought it would be a good idea to lock the bootloader before doing so.
OnePlus support won't help me and they are telling me that I can't return the device anymore. "Repair is the only option now" even though I'm in the 30 days return window.
GoToNap said:
Help. I've made a big mistake. I can only access the Bootloader. Recovery mode is not accessible.
As with the 7 Pro, I didn't like the standard 7 and decided to return it. Thought it would be a good idea to lock the bootloader before doing so.
OnePlus support won't help me and they are telling me that I can't return the device anymore. "Repair is the only option now" even though I'm in the 30 days return window.
Click to expand...
Click to collapse
Try this one.
https://forum.xda-developers.com/oneplus-7/how-to/rom-stock-fastboot-roms-oneplus-7-t3937478
If thats not working because of locked bootloader, you can try the MSMTool.
https://forum.xda-developers.com/oneplus-7/how-to/unbrick-tool-oneplus-7-msmtool-hydrogen-t3953240
Note: Never lock the bootloader if system isn't Stock!
Kollachi said:
Try this one.
https://forum.xda-developers.com/oneplus-7/how-to/rom-stock-fastboot-roms-oneplus-7-t3937478
If thats not working because of locked bootloader, you can try the MSMTool.
https://forum.xda-developers.com/oneplus-7/how-to/unbrick-tool-oneplus-7-msmtool-hydrogen-t3953240
Note: Never lock the bootloader if system isn't Stock!
Click to expand...
Click to collapse
I keep trying the MSMTool method but nothing happens when I keep both volume buttons pressed...
GoToNap said:
I keep trying the MSMTool method but nothing happens when I keep both volume buttons pressed...
Click to expand...
Click to collapse
Be sure device is off and try to hold the buttons while connecting phone to your computer.
Kollachi said:
Be sure device is off and try to hold the buttons while connecting phone to your computer.
Click to expand...
Click to collapse
OMG it worked. Thank you so much. You saved my life man!
GoToNap said:
OMG it worked. Thank you so much. You saved my life man!
Click to expand...
Click to collapse
Np dude. Good to know if I could help you.
Kollachi said:
Np dude. Good to know if I could help you.
Click to expand...
Click to collapse
Sorry to be a pain in the ass, but I can't really figure out how to get back to OxygenOS now. Everything is in Chinese...
Also, will this procedure mess with anything on my device?
GoToNap said:
Sorry to be a pain in the ass, but I can't really figure out how to get back to OxygenOS now. Everything is in Chinese...
Also, will this procedure mess with anything on my device?
Click to expand...
Click to collapse
Read the unbrick thread. There is all you need.:good:
Kollachi said:
Read the unbrick thread. There is all you need.:good:
Click to expand...
Click to collapse
I've looked through it but couldn't find anything. Sorry, I am extremely stressed out as tomorrow I am supposed to return this phone and I want to make sure that it passes inspection.
So, I did the following:
- Used the unbrick tool which lead me to HydrogenOS
- Installed the latest OxygenOS version on top of it
- Did a factory reset, and so far everything looks to be in working order.
Am I missing anything here? Are there any possible changes done to the device so that it won't pass inspection?
Sorry again for being so annoying...
GoToNap said:
I've looked through it but couldn't find anything. Sorry, I am extremely stressed out as tomorrow I am supposed to return this phone and I want to make sure that it passes inspection.
So, I did the following:
- Used the unbrick tool which lead me to HydrogenOS
- Installed the latest OxygenOS version on top of it
- Did a factory reset, and so far everything looks to be in working order.
Am I missing anything here? Are there any possible changes done to the device so that it won't pass inspection?
Sorry again for being so annoying...
Click to expand...
Click to collapse
So if OxygenOS works and you also did a factory reset, your device should be fine. Check bootloader status. But it should be locked.
Kollachi said:
So if OxygenOS works and you also did a factory reset, your device should be fine. Check bootloader status. But it should be locked.
Click to expand...
Click to collapse
Yes, I'm on the latest OxygenOS version after a factory reset and the bootloader is locked.
Thank you so much man! You are my hero
GoToNap said:
Yes, I'm on the latest OxygenOS version after a factory reset and the bootloader is locked.
Thank you so much man! You are my hero
Click to expand...
Click to collapse
Great. you could report your experience at the other thread. Maybe it helps other people too.:good: