Related
Hi Guys,
I updated my Vodafone Ireland HTC One to Android 4.4.2 OTA version (4.19.161.10) a couple of weeks ago. I have serious problems with the phone since then, it's not much of use anymore. I get the following error messages on homepage when the phone starts: "shoebox engine has stopped", "com.android.phone has stopped" , and I constantly get "google play services has stopped" error message. Worst thing is that the phone restarts itself a few times a day and when it restarts, it goes back to the state it was on the day I updated it. Anything I saved on my phone since the update gets removed (contacts, pics, sms, whatsapp messages, progress in games).
I tried a factory reset, but it doesn't work. Phone restarts to do the reset and shows me a triangle with an exclamation mark in it for a minute or so, and then just restarts normally, no reset done. HTC phone support couldn't offer any solution.
So, I would like to wipe all the data off my phone and go back to official Android 4.3. I never rooted the phone and it's still "Locked" with S-On. I'm not really interested in rooting, I just want to have the device working properly. Do I still have to relock the bootloader and turn S-Off before I flash official 4.3 version, or should I just skip those steps? HBoot version is 1.56, would it cause any problems?
Any additional feedback is welcome, appreciate your help! Thanks
I never rooted the phone and it's still "Locked" with S-On.
Click to expand...
Click to collapse
Do I still have to relock the bootloader and turn S-Off before I flash official 4.3 version, or should I just skip those steps?
Click to expand...
Click to collapse
Is the bootloader unlocked or not? my guess is you meant to say unlock?
You should be able to flash RUU without doing anything else
JPS7 said:
Hi Guys,
I updated my Vodafone Ireland HTC One to Android 4.4.2 OTA version (4.19.161.10) a couple of weeks ago. I have serious problems with the phone since then, it's not much of use anymore. I get the following error messages on homepage when the phone starts: "shoebox engine has stopped", "com.android.phone has stopped" , and I constantly get "google play services has stopped" error message. Worst thing is that the phone restarts itself a few times a day and when it restarts, it goes back to the state it was on the day I updated it. Anything I saved on my phone since the update gets removed (contacts, pics, sms, whatsapp messages, progress in games).
I tried a factory reset, but it doesn't work. Phone restarts to do the reset and shows me a triangle with an exclamation mark in it for a minute or so, and then just restarts normally, no reset done. HTC phone support couldn't offer any solution.
So, I would like to wipe all the data off my phone and go back to official Android 4.3. I never rooted the phone and it's still "Locked" with S-On. I'm not really interested in rooting, I just want to have the device working properly. Do I still have to relock the bootloader and turn S-Off before I flash official 4.3 version, or should I just skip those steps? HBoot version is 1.56, would it cause any problems?
Any additional feedback is welcome, appreciate your help! Thanks
Click to expand...
Click to collapse
I don't think you will be able to downgrade to 4.3 without s-off, You sure you don't have an app that kitkat doesn't like. Since you want to wipe all data, why not backup all apps and then uninstall everything you downloaded and installed, reset the phone gain and see what happens.
Or perhaps try a custom rom
Backup the SD card/any data you want and factory reset the phone and set up 4.4.2 again from scratch. Sometimes and OTA doesn't 'take' properly the first time from my experience
I think a factory reset would solve a lot of problems, but the phone doesn't want to do it. When I try to factory reset, it first shows Red triangle with exclamation mark and then just restarts with nothing removed. Tried both through the menu and with hardware buttons.
I read on several guides that "Fastboot" needs to be switched off before a factory reset. Maybe that's the problem. Because if I disable "Fastboot" in "Settings -> Power", the phone will not have this setting saved when it restarts. As I wrote in the original post, when the phone restarts, all of the settings and data in the phone go back to the state they were on the day I updated it to 4.4.2. My e-mails, messages, pictures, songs, app settings, even the temperature on the weather app :silly:
Bootloader is currently "Locked" and it was never unlocked before. I upgraded only OTA versions so far. Thanks for the opinions. I just don't want to do anything wrong while trying to make it better. Still don't know if I should skip s-off or not. Would it harm the phone if I just try with s-on?
JPS7 said:
I think a factory reset would solve a lot of problems, but the phone doesn't want to do it. When I try to factory reset, it first shows Red triangle with exclamation mark and then just restarts with nothing removed. Tried both through the menu and with hardware buttons.
I read on several guides that "Fastboot" needs to be switched off before a factory reset. Maybe that's the problem. Because if I disable "Fastboot" in "Settings -> Power", the phone will not have this setting saved when it restarts. As I wrote in the original post, when the phone restarts, all of the settings and data in the phone go back to the state they were on the day I updated it to 4.4.2. My e-mails, messages, pictures, songs, app settings, even the temperature on the weather app :silly:
Bootloader is currently "Locked" and it was never unlocked before. I upgraded only OTA versions so far. Thanks for the opinions. I just don't want to do anything wrong while trying to make it better. Still don't know if I should skip s-off or not. Would it harm the phone if I just try with s-on?
Click to expand...
Click to collapse
Wow!!!! UNLOCK BOOTLOADER!!!!!!! Install twrp. In recovery wipe data only that's a factory reset. If you read the s-off threads fully you will have no problems,so go forth and profit. The fastboot setting in power settings is for a quick power on only. It has nothing to do with anything else.
[email protected] said:
Wow!!!! UNLOCK BOOTLOADER!!!!!!! Install twrp. In recovery wipe data only that's a factory reset. If you read the s-off threads fully you will have no problems,so go forth and profit. The fastboot setting in power settings is for a quick power on only. It has nothing to do with anything else.
Click to expand...
Click to collapse
It's a pain. I can't even unlock the bootloader. I followed the steps correctly and got to the screen on my phone where it gives all the information about warranty and asks "Unlock the bootloader?". I volume up and pick "Yes". Device restarts and nothing happened. Again back to the day I installed 4.4.2 and the bootloader is still locked
You will somehow have to unlock. Have you tried from command line to use the unlock.bin file, or have you tried it via AIO to see if there are different results when it asks? To downgrade you will need to get that done, S-Off, downgrade HBoot, and run the RUU if there is one for your device. If not, grab one of the stock 4.3's from the forums, and do it manually. Personally I would change CID if needed and RUU the dev edition, but that's just me.
Question/issues solved - thread done!
Picture of M7 screen with information: http://imgur.com/a/l6hIg
Basically, last year I traded this phone for my current phone at the time with a T-Mobile employee.
Got home and reset everything, setup everything to my liking, etc.
I then tried to go through the rooting process and all that but it didn't work (sadly, this was a while ago and I don't remember the exact issue...).
I tried everything I could but nothing worked and so I gave up since the phone was working fine other than it not being 'rootable'.
Fast forward to a couple days ago and I found a great deal on the M8 and have been using it to make sure it is everything the seller said it would be.
Then my friend said he wants to buy my M7 and I said sure but I need some time to backup my stuff and clear/reset the phone.
So the real details/interesting part of the situation is this:
Between when I got the M7 and a couple days ago the performance of the M7 has degraded and by this I mean that I have to restart the phone to get mobile data working (even though the symbol shows 4g/LTE), some apps have randomly crashed (namely Maps but it seems updates have fixed that). When I did try to root and all that, I installed TitaniumBackUp Pro and Root Explorer (here comes the interesting part) - sometimes TPUP has root access and sometimes it doesn't have root access; however, Root Explorer has always worked for what I needed (looking for downloaded files).
So is it possible to somehow properly root the phone and then unroot to make sure everything is good to go for my friend or do I need to just unroot the phone? Or do I simply need to do a factory reset (I am fine with this since I have all my contacts on the M8 already)? I haven't touched any software/rooting stuff since my 1 and only attempt to root the phone.
Sorry for the wall of text and I did try searching for similar posts/threads but couldn't (maybe I searched the wrong words?) and please feel free to ask questions for clarification and I will do my best to respond ASAP! Thank you in advance for your help.
CTR01 said:
Picture of M7 screen with information: http://imgur.com/a/l6hIg
Basically, last year I traded this phone for my current phone at the time with a T-Mobile employee.
Got home and reset everything, setup everything to my liking, etc.
I then tried to go through the rooting process and all that but it didn't work (sadly, this was a while ago and I don't remember the exact issue...).
I tried everything I could but nothing worked and so I gave up since the phone was working fine other than it not being 'rootable'.
Fast forward to a couple days ago and I found a great deal on the M8 and have been using it to make sure it is everything the seller said it would be.
Then my friend said he wants to buy my M7 and I said sure but I need some time to backup my stuff and clear/reset the phone.
So the real details/interesting part of the situation is this:
Between when I got the M7 and a couple days ago the performance of the M7 has degraded and by this I mean that I have to restart the phone to get mobile data working (even though the symbol shows 4g/LTE), some apps have randomly crashed (namely Maps but it seems updates have fixed that). When I did try to root and all that, I installed TitaniumBackUp Pro and Root Explorer (here comes the interesting part) - sometimes TPUP has root access and sometimes it doesn't have root access; however, Root Explorer has always worked for what I needed (looking for downloaded files).
So is it possible to somehow properly root the phone and then unroot to make sure everything is good to go for my friend or do I need to just unroot the phone? Or do I simply need to do a factory reset (I am fine with this since I have all my contacts on the M8 already)? I haven't touched any software/rooting stuff since my 1 and only attempt to root the phone.
Sorry for the wall of text and I did try searching for similar posts/threads but couldn't (maybe I searched the wrong words?) and please feel free to ask questions for clarification and I will do my best to respond ASAP! Thank you in advance for your help.
Click to expand...
Click to collapse
probably a better idea to reset the phone back to stock. can you post the output of "fastboot getvar all" except imei/serialno?
alray said:
probably a better idea to reset the phone back to stock. can you post the output of "fastboot getvar all" except imei/serialno?
Click to expand...
Click to collapse
@alray:
Thanks for the quick reply. I will gladly just reset to stock if that's the easiest/best method.
I currently don't have ADB setup on either computer since I haven't been in the rooting game for a long while now.
As of now I'm on my MacBook Pro 13" with Retina display and Mac OSX 10.9.4 and internet connection.
My home Windows desktop currently doesn't have internet due to some issues at home...
So I'm guessing the first thing is to setup ADB on the Mac (if possible?), though I haven't done it before on a Mac.
Thanks.
CTR01 said:
@alray:
Thanks for the quick reply. I will gladly just reset to stock if that's the easiest/best method.
I currently don't have ADB setup on either computer since I haven't been in the rooting game for a long while now.
As of now I'm on my MacBook bla bla bla.
My home Windows desktop currently doesn't have internet due to some issues at home...
So I'm guessing the first thing is to setup ADB on the Mac (if possible?), though I haven't done it before on a Mac.
Thanks.
Click to expand...
Click to collapse
yes its also possible to have adb and fastboot on mac, just make a quick google search and you'll find a great thread how to setup fastboot/adb on mac.
alray said:
yes its also possible to have adb and fastboot on mac, just make a quick google search and you'll find a great thread how to setup fastboot/adb on mac.
Click to expand...
Click to collapse
@alray:
Great, thanks for that and I will be sure to update here as soon as it is all setup.
@alray:
I found this link from a Google search that showed me how to install adb/fastboot on Mac in less than 5 minutes and my M7 is showing up in the adb devices list.
Screen shot with all the info is attached.
Sorry for the delayed reply, had to eat dinner.
CTR01 said:
@alray:
I found this link from a Google search that showed me how to install adb/fastboot on Mac in less than 5 minutes and my M7 is showing up in the adb devices list.
Screen shot with all the info is attached.
Sorry for the delayed reply, had to eat dinner.
Click to expand...
Click to collapse
So you have probably unlocked the bootloader in your attempt to root the phone. When you unlock the bootloader, it wipe users data but it also wipe some preloaded app by HTC in /data/preload. Problem is your friend will not be able to install ota updates with those missing files.
Good news is that there is a ruu for your phone version you could use to reset the phone back to stock and it will also wipe all your personal data at the same time, like if the phone was new (no need to factory reset). The ruu is a .exe file so you'll need a windows computer and because of the hboot version on the phone (1.44) you can't use windows 8.1 to flash the ruu, you'll need windows 7. Because your phone is S-ON, you'll also need to relock the bootloader before flashing the RUU. After flashing it, the phone will be wiped from any user data and ready to take ota updates.
so
relock bootloader:
Code:
fastboot oem relock
download the 1.27.531.11 ruu.exe from here
with the phone booted in bootloader mode or booted in the OS and connected to the windows 7 pc, lauch the ruu.exe and follow simple instructions so the ruu.exe will flash the phone automatically.
sell the phone to your friend
alray said:
So you have probably unlocked the bootloader in your attempt to root the phone. When you unlock the bootloader, it wipe users data but it also wipe some preloaded app by HTC in /data/preload. Problem is your friend will not be able to install ota updates with those missing files.
Good news is that there is a ruu for your phone version you could use to reset the phone back to stock and it will also wipe all your personal data at the same time, like if the phone was new (no need to factory reset). The ruu is a .exe file so you'll need a windows computer and because of the hboot version on the phone (1.44) you can't use windows 8.1 to flash the ruu, you'll need windows 7. Because your phone is S-ON, you'll also need to relock the bootloader before flashing the RUU. After flashing it, the phone will be wiped from any user data and ready to take ota updates.
so
relock bootloader:
Code:
fastboot oem relock
download the 1.27.531.11 ruu.exe from here
with the phone booted in bootloader mode or booted in the OS and connected to the windows 7 pc, lauch the ruu.exe and follow simple instructions so the ruu.exe will flash the phone automatically.
sell the phone to your friend
Click to expand...
Click to collapse
@alray:
My first post has a link to a picture of what the current status is of my phone, if you missed it before.
I will look at this part in more detail after I'm done with work
I'll post asap when I get a chance. Thanks!
@alray:
So I tried the bootlock command but then got the following error/problem (see screen shot).
I was either in the wrong mode or did stuff in the wrong order...
What I did:
1) open Terminal app
2) move to the adb/fastboot folder on Mac
3) type in the fastboot oem relock command
4) then received the attached screen shot error/problem.
I have a feeling the problem is going to be a bit tougher to solve than anticipated...
EDIT:
I have managed to screw up my device by doing factory reset and getting rid of the OS
EDIT 2:
I have managed to solve the above issue of no OS by getting CM 10 installed and working.
Now I need to get things back to stock to sell to my friend.
Thanks!
CTR01 said:
@alray:
So I tried the bootlock command but then got the following error/problem (see screen shot).
I was either in the wrong mode or did stuff in the wrong order...
What I did:
1) open Terminal app
2) move to the adb/fastboot folder on Mac
3) type in the fastboot oem relock command
4) then received the attached screen shot error/problem.
I have a feeling the problem is going to be a bit tougher to solve than anticipated...
EDIT:
I have managed to screw up my device by doing factory reset and getting rid of the OS
EDIT 2:
I have managed to solve the above issue of no OS by getting CM 10 installed and working.
Now I need to get things back to stock to sell to my friend.
Thanks!
Click to expand...
Click to collapse
sorry mate, my bad! The correct command is "fastboot oem lock" not "fastboot oem relock"
alray said:
sorry mate, my bad! The correct command is "fastboot oem lock" not "fastboot oem relock"
Click to expand...
Click to collapse
@alray:
No worries, I'll try that and get back to you.
Thanks.
Sent from my HTC One_M8
@alray:
So quick recap:
1) use the fastboot oem lock command
2) install the RUU.exe that you linked to me (I have it downloaded) on a Windows 7 computer (which I have)
3) then everything should be good to go and I can sell to my friend
Question:
Do I need to have HTC Sync Manager and/or USB drivers installed on the Windows 7 computer for the above process to work?
CTR01 said:
@alray:
So quick recap:
1) use the fastboot oem lock command
2) install the RUU.exe that you linked to me (I have it downloaded) on a Windows 7 computer (which I have)
3) then everything should be good to go and I can sell to my friend
Question:
Do I need to have HTC Sync Manager and/or USB drivers installed on the Windows 7 computer for the above process to work?
Click to expand...
Click to collapse
yes you need the drivers, but better to have htc sync uninstalled
alray said:
yes you need the drivers, but better to have htc sync uninstalled
Click to expand...
Click to collapse
Great, thanks for that clarification. I'll update you when I get a chance to run through the steps!
@alray:
I don't think that the M7 is communicating with the computer/adb based on the screen shot attached and that after typing in the command to lock the bootloader, it keeps waiting for device.
Thoughts?
Sent from my HTC One_M8
CTR01 said:
@alray:
I don't think that the M7 is communicating with the computer/adb based on the screen shot attached and that after typing in the command to lock the bootloader, it keeps waiting for device.
Thoughts?
Sent from my HTC One_M8
Click to expand...
Click to collapse
driver installed incorrectly? Is the phone listed in windows device manager when booted in bootloader?
alray said:
driver installed incorrectly? Is the phone listed in windows device manager when booted in bootloader?
Click to expand...
Click to collapse
@alray:
Yeah, the drivers installed just fine.
However, I actually just showed my friend the phone with CM10 on it and told him the pros/cons and he was just fine with everything since he just wanted a phone that would work and not freeze/lag like his current phone does.
So thank you for your help and the situation has been solved!
So gentleman its about time i asked for help. I am not a dev but very android savvy, have rooted, recovered, de-bricked 100+ devices and only two hard bricks so far.
So here goes. i got a m8 hk edition brand new, proceeded with custom recovery, unlocked boot-loader, firewater s-off blah blah and next i try to sim unlock. while in programming screen i looked away and my baby boy hit a the screen and chose an unknown option, my phone rebooted, upon boot I was greeted by a phone lock screen please enter password. I never set one. I cannot call but only 911 sometimes can *2 but only for a second. cannot reset after 10 attempts, lock is persistent after flash of new rom and now i really messed up s back on and relocked bootloader. i can unlock bootloader again but since flashed new rom and reset device adb isnt on. have tried everything google got and searched for almost a year to no avail for a solution. PLEASE HELP. I AM NO NOOB. also have tryed the encryption bug fix too and nothing.....REWARD......
Have you tried a RUU? Hit the second link in my sig and read the RUU section. Then go to the thread in the link below and grab the RUU for software version 3.31.654.2 and run it from your computer.
http://forum.xda-developers.com/showthread.php?t=2729173
ruu
I have tried several ruus not sure of versions with fail if i remember right error was something about security or permissions.. also cid was changed at some point, havent worked on phone in a month downloading your link now. I appreciate any and all input on this and would like to hear of any others with this problem. as soon as i get device booted with recovery i will post more information about device specs
jamesdeanwest said:
I have tried several ruus not sure of versions with fail if i remember right error was something about security or permissions.. also cid was changed at some point, havent worked on phone in a month downloading your link now. I appreciate any and all input on this and would like to hear of any others with this problem. as soon as i get device booted with recovery i will post more information about device specs
Click to expand...
Click to collapse
If you changed your CID then you're S-off and there is no need to relock your bootloader. You may need to change your CID back to stock (SPCS_004 in your case) if you continue to get errors while trying to run the RUU, however, I don't believe that will be necessary.
If you're wanting to go back totally stock & S-on, locked bootloader and all, check out the guide in the link below.
http://forum.xda-developers.com/showthread.php?t=2826343
Ruu's flash successfully but device still boots locked. I was s off but returned device back to s on at some point. I can still re-lock and unlock bootloader, but i cannot return to s off because the Device has yet to enable ADB . Since every flash clears all settings after boot the developer settings are not even enabled because im locked out at first boot EVERY time I factory reset or flash a new Rom or ruu.
Please tell me something I havent tried yet. Something im missing? Im thinking about offering a reward to anyone who can help me solve this problem.
In the picture is something I haven't been able to find on than any other Harman Kardon m8. What password? Could it have possibly been a password set with my root anti-theft app AVAST?
If you select emergency call from the screen in the picture, does it bring up the dialer or just call 911?
If the dialer comes up, can you enter any ## or *# whatever type commands? Maybe reset it from there. ##72786# or ##786#
fgr said:
If you select emergency call fe, does it bring up the dialer or just call 911?
If the dialer comes up, can you enter any ## or *# whatever type commands? Maybe reset it from there. ##72786# or ##786#[/QUO
Dialer comes up but the only code it will take is *2
activation menu but only for a second. 25 $ bounty on this issue if anyone has some insight on how to resolve this issue. ANYONE HAVE A JTAG? ILL SEND.MY DEVIVE TO U AND.PAY YOUR FEE?
Click to expand...
Click to collapse
no dialer codes
fgr said:
If you select emergency call fe, does it bring up the dialer or just call 911?
If the dialer comes up, can you enter any ## or *# whatever type commands? Maybe reset it from there. ##72786# or ##786#[/QUO
Dialer comes up but the only code it will take is *2
activation menu but only for a second. 25 $ bounty on this issue if anyone has some insight on how to resolve this issue. ANYONE HAVE A JTAG? ILL SEND my device
TO U AND.PAY YOUR FEE?
Click to expand...
Click to collapse
Have you contacted Sprint?
Hi,
So I wanted to prepare my unlocked Nexus 6 on T-mobile for my brother by completely un-rooting and then relocking to setup stock firmware. With the help of “Nexus Root Toolkit” it was a quick update. I simply picked up the latest firmware for t-mobile, then relocked - and off you go.
The Phone was ok for couple of days, but then google pushed new update – which would render my phone useless. After update Initially the phone went through the boot almost to the end, and then exception happened. Something about system UI crashing and then screen was unavailable. So I could not do anything on the phone.
I tried fixing with “Nexus Root Toolkit” (unlocking, rooting etc.), but at this point the phone is stock on booting (few colored dots signifying loading), but the phone never actually boots. Going to Factory reset or Recovery does nothing.
Is there anything else I can try please?
Thanks,
-Mariusz
keinam.ty said:
Hi,
So I wanted to prepare my unlocked Nexus 6 on T-mobile for my brother by completely un-rooting and then relocking to setup stock firmware. With the help of “Nexus Root Toolkit” it was a quick update. I simply picked up the latest firmware for t-mobile, then relocked - and off you go.
The Phone was ok for couple of days, but then google pushed new update – which would render my phone useless. After update Initially the phone went through the boot almost to the end, and then exception happened. Something about system UI crashing and then screen was unavailable. So I could not do anything on the phone.
I tried fixing with “Nexus Root Toolkit” (unlocking, rooting etc.), but at this point the phone is stock on booting (few colored dots signifying loading), but the phone never actually boots. Going to Factory reset or Recovery does nothing.
Is there anything else I can try please?
Thanks,
-Mariusz
Click to expand...
Click to collapse
There's not much you can do here. If you don't have TWRP or unlocked bootloader, you should just RMA the device direct through Motorola.
You could try to sideload the update you had received that caused this.
Other than that, RMA.
I was hoping not to hear RMA - but thanks for the reply.
I recently had to replace the motherboard on my Nexus 6. I could only find refurbished ones, and bought one on AliExpress, with item description clearly specifying as unlock. I installed it, and it appears it is actually locked status 2. Looks like demo version used in T-Mobile retail network. Some settings inaccessible u such as developer mode or Apps. Trying to get refund but both AliExpress and the vendor are in denial mode.
I have 7.0, NBD92G installed. Very hard to unlock as I cannot access developer mode to allow usb debug. Pressing build nr several times won't help. I get message "you're already a developer" but actually usb debug does not work.
Anybody can help?
Go download factory image from Google and flash it manually by using the command prompt.
@ShernDog: He can't as his bootloader is locked. He can however download an OTA and sideload it.
Strephon Alkhalikoi said:
@ShernDog: He can't as his bootloader is locked. He can however download an OTA and sideload it.
Click to expand...
Click to collapse
Thanks. You are right, bootloader is locked too. Would there be any instructions somewhere on your proposed solution (sorry I am rather inexperienced user).
FYBRU said:
Thanks. You are right, bootloader is locked too. Would there be any instructions somewhere on your proposed solution (sorry I am rather inexperienced user).
Click to expand...
Click to collapse
I think I figured out how to do this but the other question is whether I won't be stuck afterwards being requested to enter the only registered user's login which I do not have (I cannot register a second user, as this setting screen is locked too). Do I need to sideload the OTA corresponding to current version / build or can I sideload an older one?
Download the oldest OTA available, as long as it is a full system OTA (easily detectable by size). You're going to have to bypass Factory Reset Protection to be able to resolve this, and the older the OTA, the better.
If this doesn't work, you're going to have to fight with the place you got the motherboard from, and file a chargeback with your credit card company if need be.
Ultimately I can go for the refund, but there is no place where I can find 64 GB MBs outside China, which means I'll have to wait again for something like 3 weeks with poor backup device, and with no certainty I don't receive again a locked MB.
I tried with 6.0 OTAs (page with instructions I followed: https://developers.google.com/android/ota#shamu) and even with just older versions of 7.0, I got every time abortion after about 45% installation, with the msg that I cannot update with older versions.
I am a bit confused now, I just tried to install same build as what I had installed (https://dl.google.com/dl/android/aosp/shamu-ota-nbd92g-2b65257b.zip), it worked but it looks like absolutely nothing has changed on my phone. I thought it would have erased pretty much everything. Am I missing something?
OTA updates don't wipe system. That's why nothing changed.
Ultimately, I think you're going to have to go for the refund and take the risk that the next motherboard you get is going to be locked. Unless the version of Android you're on can have its FRP bypassed - and I don't think it can - you're stuck.
Thanks, bad news. Would it be worth trying wipe data / factory reset accessible from the recovery mode + power/volume up menu ?
You can try it, but it won't help. Doing a factory reset will cause Factory Reset Protection to kick in, meaning you'd need to know the original owner's account information.
Surprisingly it worked. I could log in with the google account I used before the reset. Everything works, but indeed I was expecting some more difficulties
@FYBRU: This is one of those times where I'm pleased to be wrong. LOL.
Glad you got it resolved.