Related
Greetings everyone!
Few weeks ago, I gave my device to a friend of mine to manually update it. Something went wrong so he decided not to go any further. Yday i tried to "Factory reset", after reset some error pop'd in the left upper corner of the phone.It says:
[LGE_SECURITY] ERROR: boot image signature
Critical failure: Unable to start kernel.
Unrecoverable bootloader error (0x00000002).
Anyone had any similiar or even the same problem as i am facing right now? Thanks in advance.
best regards, Milan
Guy didn't know what he was doing apparently. Your handset is still locked and he apparently tried installing a 3rd party ROM, lemme guess, you wanted a newer version of Android than 4.1., which is a reasonable enough thing. Problem is that out of the box you can't do that because it only boots images signed by LG and they abandoned development after releasing 4.1 and a couple of minor point releases. You aren't totally screwed but if you were having somebody else do it for you, you might need to get some help. You can find the details elsewhere here, or more likely point a more skilled friend at it, but here it is in a nutshell.
You need to get LG's official updating software (from the LG website) and you need to fiddle with it a bit until you get it to do a rescue because it expects to have already paired up with the phone while it was still working. If you already had it installed, great because it will make it easier. Anyway, you will probably have to manually pick your model and input the IMEI since it won't already know those things and it will go out and fetch the most recent image. You will push VOL Down and insert the USB cable from a powered down state, it will then do the rest. Good chance you will even retain your data unless that 'factory reset' you mention actually succeeded.
Of course that will only get you back to stock 4.1. Read around for the official way and several un-official ways to unlock your boot loader. Once that is done you can install a better recovery and then a newer version of Android. But the first step is to restore the stock software since you have to have a running phone to be able to unlock it.
And no, nobody has ever been able to explain WHY they lock them, but every single manufacturer seems determined to do it, chipmakers put a lot of work and ad copy into how extensive and unbreakable the locks on their newest chip is, etc. And then they either bow to customer demand and add an unlock feature or we here at xda do it for them... as a courtesy of course. Truly we do live in the asylum. Wonko the Sane was onto something.
Hi - apologies first of all if this is covered elsewhere in the forums.
I purchased a brand new Nexus 6 directly from Motorola this week as they had slashed the price down to just £309 for the 64gb. It arrived Monday. I turned it on, signed into my network etc. it starting updating apps. Then it said that Android 5.1.1. was available so I downloaded it and proceeded to install. About halfway through the installation it crashed. My phone is now stuck on continually booting up and saying 'optimising xxx apps'. After a bit of research, I found that this was a common problem as 5.1.1. was trying to update and some apps were incompatible. So I read many forums and booted into Recovery mode, wiped the cache, wiped data and did a factory reset, but it still won't work.
I called Motorola who told me that they have had many of their Nexus 6s do this and all they could do was to refund me the phone as they now are out of stock.
Further research led me to read about 'flashing' the phone so I downloaded Wugfresh but I cannot get into the phone to enable me to debug. After many hours today I have come to the conclusion that I am never going to be able to use my new phone which I am gutted about.
My question is, is there anyway to flash the phone without enabling debugging because I cannot get into the main menu because all if does is just keep optimizing apps?
Many thanks for reading and any assistance would be greatly appreciated.
bacon_roll said:
Hi - apologies first of all if this is covered elsewhere in the forums.
I purchased a brand new Nexus 6 directly from Motorola this week as they had slashed the price down to just £309 for the 64gb. It arrived Monday. I turned it on, signed into my network etc. it starting updating apps. Then it said that Android 5.1.1. was available so I downloaded it and proceeded to install. About halfway through the installation it crashed. My phone is now stuck on continually booting up and saying 'optimising xxx apps'. After a bit of research, I found that this was a common problem as 5.1.1. was trying to update and some apps were incompatible. So I read many forums and booted into Recovery mode, wiped the cache, wiped data and did a factory reset, but it still won't work.
I called Motorola who told me that they have had many of their Nexus 6s do this and all they could do was to refund me the phone as they now are out of stock.
Further research led me to read about 'flashing' the phone so I downloaded Wugfresh but I cannot get into the phone to enable me to debug. After many hours today I have come to the conclusion that I am never going to be able to use my new phone which I am gutted about.
My question is, is there anyway to flash the phone without enabling debugging because I cannot get into the main menu because all if does is just keep optimizing apps?
Many thanks for reading and any assistance would be greatly appreciated.
Click to expand...
Click to collapse
You could try and flash a flash a factory image via fastboot...
draa2711 said:
You could try and flash a flash a factory image via fastboot...
Click to expand...
Click to collapse
No, he can't try, he has his bootloader locked.
OP, this thread is a classic case of why the first thing anyone should do with this device, even if not planning to root or otherwise modify it, is to enable developer options in settings and enable both USB Debugging and OEM Unlocking. Without both enabled there's no way to resolve your problem, and unfortunately you'll need to contact Motorola and arrange a return, since they are out of stock.
Once you get your money back, look on Swappa for a used device. You may be able to get a device that way at a lower price than what Motorola offers.
Strephon Alkhalikoi said:
OP, this thread is a classic case of why the first thing anyone should do with this device, even if not planning to root or otherwise modify it, is to enable developer options in settings and enable both USB Debugging and OEM Unlocking. Without both enabled there's no way to resolve your problem, and unfortunately you'll need to contact Motorola and arrange a return, since they are out of stock.
Once you get your money back, look on Swappa for a used device. You may be able to get a device that way at a lower price than what Motorola offers.
Click to expand...
Click to collapse
Thanks for your advice, but I had no idea, probably like so many others who aren't as clued up on Android that USB Debugging even existed. I just bought a phone that I wanted that now is no good to me having never been able to use it because of a bug in 5.1.1. I am returning to Motorola for refund.
Without wanting to raise false hopes, there is a thread in this forum where the OP says he recovered his device even though the bootloader was locked (he was certain of it, he said...), other people replying that this was impossible, and yet they eventually seemed to accept that it might be. My bootloader has been unlocked since day one, and I don't remember if there was an "Allow OEM unlock" option in Settings - the same thread had discussion about Marshmallow not having it. I suppose this N6 is still on Lollipop, so maybe a red herring...
I'll see if I can find the thread for reference, but in the meantime does anyone recognise the thread I mean?
bacon_roll, since I'm vegetarian I shouldn't be helping you but have you tried Wugfresh's option of "Phone is bricked/bootlooping"? I think all it does is to reboot the device into bootloader anyway, but I think this might be worth a go if you haven't already tried it. You did mention that you've booted into recovery, but you don't mention bootloader mode.
draa2711 said:
You could try and flash a flash a factory image via fastboot...
Click to expand...
Click to collapse
Thanks. As per my post, I can't because the phone is locked.
dahawthorne said:
My bootloader has been unlocked since day one, and I don't remember if there was an "Allow OEM unlock" option in Settings - the same thread had discussion about Marshmallow not having it. I suppose this N6 is still on Lollipop, so maybe a red herring...
Click to expand...
Click to collapse
You could check in the About Phone menu to see what version you're on.
Both Android 5.x and Android 6.x have an OEM Unlocking toggle in Development Options. I know because I followed my own advice given above in my previous post in order to flash the latest Android 6.0.1 ROM to the device, and then checked Developer Options afterward.
dahawthorne said:
Without wanting to raise false hopes, there is a thread in this forum where the OP says he recovered his device even though the bootloader was locked (he was certain of it, he said...), other people replying that this was impossible, and yet they eventually seemed to accept that it might be. My bootloader has been unlocked since day one, and I don't remember if there was an "Allow OEM unlock" option in Settings - the same thread had discussion about Marshmallow not having it. I suppose this N6 is still on Lollipop, so maybe a red herring...
I'll see if I can find the thread for reference, but in the meantime does anyone recognise the thread I mean?
bacon_roll, since I'm vegetarian I shouldn't be helping you but have you tried Wugfresh's option of "Phone is bricked/bootlooping"? I think all it does is to reboot the device into bootloader anyway, but I think this might be worth a go if you haven't already tried it. You did mention that you've booted into recovery, but you don't mention bootloader mode.
Click to expand...
Click to collapse
Hi - please get my hopes up, I really want to keep this phone if I can
Without sounding like a complete nerd, what is the difference between recovery and bootloader mode?
When I scroll through the options with both arrows pressed and power button, I have START, RESTART BOOTLOADER, RECOVERY MODE, POWER OFF, FACTORY, BARCODES, BP TOOLS, QCOM & BOOTLOADER LOGS
I have done factory wipe/cache/restart bootloader etc.
How do I boot into bootloader mode please.
Thank you.
Overly simplistic reply here, but it should be enough to answer the question.
The bootloader prepares the system for booting. Once it's done its work it hands off control of the system to Android's kernel. Recovery is a mini operating system used to initiate low level functions such as wiping the on-board storage. The screen you describe I believe is the bootloader interface, hence why you have a "Restart Bootloader" option instead of "Start Bootloader".
You can probably save some serious money by returning and buying off swappa really. I just broke my N6 and couldn't find one in stock but, used swappa to find one around $260 that was only used for 2 weeks.
If you already have Wugfresh's Nexus Root Toolkit installed, use the "Install & test drivers" button to make sure that you have all your drivers installed properly. If all is ok, although I know this won't be popular advice, then start with the "My device is soft-bricked", then try the "Unlock" button and then "Flash stock" button. If the phone is already a paperweight then I don't believe it can possibly do any more harm, and you might even hit it lucky...
If none of this works, grab Motorola's refund offer with both hands...
Strephon Alkhalikoi said:
Overly simplistic reply here, but it should be enough to answer the question.
The bootloader prepares the system for booting. Once it's done its work it hands off control of the system to Android's kernel. Recovery is a mini operating system used to initiate low level functions such as wiping the on-board storage. The screen you describe I believe is the bootloader interface, hence why you have a "Restart Bootloader" option instead of "Start Bootloader".
Click to expand...
Click to collapse
Ok thank you.
I downloaded and installed Wugfresh, followed all the instructions. It won't work once it goes to flash because it can't see my phone connected. My PC recognises it as Nexus 6 but on the 'bootloader' screen at the bottom, it says Connect USB Data Cable, even though the phone says Battery OK (Charging). I tried to install latest USB drivers but apparently the latest are installed.
I am giving up now as I don't believe I can try anything else. Just strange that Wugfresh won't see the phone, yet my PC does.
Thanks.
Oh well...
You did try the Wugfresh "Test drivers"? It has a really helpful walkthrough on deleting and installing drivers. I'd give it a go before you give up.
dahawthorne said:
Oh well...
You did try the Wugfresh "Test drivers"? It has a really helpful walkthrough on deleting and installing drivers. I'd give it a go before you give up.
Click to expand...
Click to collapse
Ok I don't often use this phrase because I think it's very over rated but O M G - IT WORKED!!
I followed the driver guide in Wugfresh as you suggested, downloaded the CORRECT drivers, flashed it, unlocked bootloader, enabled usb debugging (just in case ) and then restored it then finally relocked the bootloader. It worked flawlessly and after setting up it is now 6.0.1 with the 1 Jan 2016 security patch applied - OTA.
I can't think you enough for your suggestion and advice, I really appreciate it and glad that I persevered with it.
Have a great weekend.
Thanks.
Bacon_Roll (vegetarian version)
That is absolutely fantastic news. I'm almost as pleased as you are. Remote assistance across the ether - you can't beat it with a big stick...
But as your attorney I advise you to go back into bootloader, check the connection (fastboot devices) and unlock again (fastboot oem unlock). This will wipe your device, but I reckon in the last 25 minutes you won't have been able to install much.
There are so many threads on this forum where people have been told "You're stuffed" because they have a problem and have a locked bootloader. Just this afternoon in another thread I read, literally in capital letters "DON'T RELOCK YOUR BOOTLOADER" for this very reason - without it you don't have recourse to the recovery tools you may one day need.
(P.S. Another person whose thread I followed also managed to get a result with NRT after all else had failed. I suggested to him that he might like to thank the developer, Doug Cohen/Wugfresh, more tangibly by donating a few dollars, which you can do through Paypal on his website. After all, he just saved your £300 phone... ).
@dahawthorne: I'll have to look into Wugfresh's utility. Not that I need it for anything, but it would be good to have in the unlikely event something goes wrong over here. Meanwhile, bacon_roll should take your advice to heart, because it will save him a lot of trouble in the future.
dahawthorne said:
That is absolutely fantastic news. I'm almost as pleased as you are. Remote assistance across the ether - you can't beat it with a big stick...
But as your attorney I advise you to go back into bootloader, check the connection (fastboot devices) and unlock again (fastboot oem unlock). This will wipe your device, but I reckon in the last 25 minutes you won't have been able to install much.
There are so many threads on this forum where people have been told "You're stuffed" because they have a problem and have a locked bootloader. Just this afternoon in another thread I read, literally in capital letters "DON'T RELOCK YOUR BOOTLOADER" for this very reason - without it you don't have recourse to the recovery tools you may one day need.
(P.S. Another person whose thread I followed also managed to get a result with NRT after all else had failed. I suggested to him that he might like to thank the developer, Doug Cohen/Wugfresh, more tangibly by donating a few dollars, which you can do through Paypal on his website. After all, he just saved your £300 phone... ).
Click to expand...
Click to collapse
Understood! I will take your advice on both counts but I was going to donate anyway as it really is a fantastic tool.
Thanks again
Strephon Alkhalikoi said:
@dahawthorne: I'll have to look into Wugfresh's utility. Not that I need it for anything, but it would be good to have in the unlikely event something goes wrong over here. Meanwhile, bacon_roll should take your advice to heart, because it will save him a lot of trouble in the future.
Click to expand...
Click to collapse
Thanks for your help over the thread Strephon - much appreciated.
Strephon Alkhalikoi said:
@dahawthorne: I'll have to look into Wugfresh's utility. Not that I need it for anything, but it would be good to have in the unlikely event something goes wrong over here. Meanwhile, bacon_roll should take your advice to heart, because it will save him a lot of trouble in the future.
Click to expand...
Click to collapse
FFS, it's not a magic wand, people! It can't do anything that fastboot and adb can't. Don't start a religion here instead teaching people to do stuff with their phones, Christ!
Some people were lucky enogh that their phones came with 5.0, and some early 5.0s didn't check yet for the Enable OEM Unlocking switch. You could have typed fastboot OEM unlock and achieved the same.
Hi Guys,
I think I have no lucky these days...
I was testing a new ROM and when a returned the backup with TWRP android asked me a patteren for unlock.
The patter I usauly use dont work.
I found a help that say to erase some files in /data/system but it doenst work...
I had a idea to block the cell with my google account and set a new PIN for unnlock... It doenst work
Now I have the cell blocked by google and its impossible to access the internal memory with TWRP...
I need help... I dont know what to do...
Please !!!!
Sounds like your only way back is to format/delete all your data and start from scratch. You can use fastboot to do this.
I think this is the way... but I never did this before...
Do you know a step by step to do this !?
If I understand rightly you have a Google locked phone. I have not tried this on the OP3T but if you are able to reach the boot up screen where Google asks you for the password/pattern lock, you can try inserting an OTG drive of any capacity into your device. The phone will ask for changing storage. After clicking 'OK' you will be taken to the storage section. Go to 'Apps' and from there to 'Setting'. If you are able to reach this far, do a complete reset from that 'Settings' section and you would be able to recover your phone. I repeat, I have not tried this on the OP3T but have successfully tried this on some other phones. Best of luck and hope you get back your toy.
Let me also add that you won't be able to recover a Google blocked phone by factory resetting from recovery. The only way to do this is to reset it from the settings section of the OS itself after you have booted up.
shantanil said:
If I understand rightly you have a Google locked phone. I have not tried this on the OP3T but if you are able to reach the boot up screen where Google asks you for the password/pattern lock, you can try inserting an OTG drive of any capacity into your device. The phone will ask for changing storage. After clicking 'OK' you will be taken to the storage section. Go to 'Apps' and from there to 'Setting'. If you are able to reach this far, do a complete reset from that 'Settings' section and you would be able to recover your phone. I repeat, I have not tried this on the OP3T but have successfully tried this on some other phones. Best of luck and hope you get back your toy.
Let me also add that you won't be able to recover a Google blocked phone by factory resetting from recovery. The only way to do this is to reset it from the settings section of the OS itself after you have booted up.
Click to expand...
Click to collapse
Perfect!
I did exactly this and now I recovery the cell...
Thanks a lot!
You save my day!
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.
So I bought this phone from eBay, like many before it. But this time it came with a twist: when I booted the phone, initial setup ran and all wend fine until I got to the register Google account screen.
There, the phone says: "This phone was reset. To continue, sign in with a Google Account that was previously synced on this device".
No matter what account I use, I always get a Toast message saying "Unable to sign in to device due to a unknown error. Please try another account or try to sign in again after 24 hours.".
I'm guessing this is some kind of theft protection where entering a previously synced account "proves" that you're the legit owner. The authorised service here told me that I need some kind of proof that I'm the legit owner and surely enough the eBay seller has issued no invoice containing the phone's IMEI (or any similar document).
Anyway, here I am with this gorgeous phone on my hands which is little more than a brick due to this.
Is there any way I could get it to work again? Returning it will just generate more costs for me and I'd like to avoid that.
I've seen guides on youtube where they managed to bypass this security measure, but both methods I've seen failed for me. I guess the version running on my phone is just too recent and plugged all the holes.
Do I have any way of downgrading the software at least? Note that this is a fully locked phone and I can't even start TWRP from fastboot.
Anything else?
Edit: Now that I'm re-reading this post, it occurred to me that there's very little chance that this phone wouldn't be a stolen one. Had it not been, the seller would easily issue me an invoice.
Leaving this post only because my searching hasn't turned up anything on XDA. Probably also reporting the guy on eBay.
velis74 said:
So I bought this phone from eBay, like many before it. But this time it came with a twist: when I booted the phone, initial setup ran and all wend fine until I got to the register Google account screen.
There, the phone says: "This phone was reset. To continue, sign in with a Google Account that was previously synced on this device".
No matter what account I use, I always get a Toast message saying "Unable to sign in to device due to a unknown error. Please try another account or try to sign in again after 24 hours.".
I'm guessing this is some kind of theft protection where entering a previously synced account "proves" that you're the legit owner. The authorised service here told me that I need some kind of proof that I'm the legit owner and surely enough the eBay seller has issued no invoice containing the phone's IMEI (or any similar document).
Anyway, here I am with this gorgeous phone on my hands which is little more than a brick due to this.
Is there any way I could get it to work again? Returning it will just generate more costs for me and I'd like to avoid that.
I've seen guides on youtube where they managed to bypass this security measure, but both methods I've seen failed for me. I guess the version running on my phone is just too recent and plugged all the holes.
Do I have any way of downgrading the software at least? Note that this is a fully locked phone and I can't even start TWRP from fastboot.
Anything else?
Edit: Now that I'm re-reading this post, it occurred to me that there's very little chance that this phone wouldn't be a stolen one. Had it not been, the seller would easily issue me an invoice.
Leaving this post only because my searching hasn't turned up anything on XDA. Probably also reporting the guy on eBay.
Click to expand...
Click to collapse
From the Settings / About, what is exact (full) build name/number?
Generally, if you are on Nougat then IMO, rolling back to MM should completely reset your phone.
You cannot flash TWRP without unlocking Bootloader. But that will not help much for resetting Google protection.
Btw, enable Developer's menu, does it allow you to unlock FRP/OEM Unlocking - in that case you will be able to reset all from EMUI recovery.
zgfg said:
From the Settings / About, what is exact (full) build name/number?
Generally, if you are on Nougat then IMO, rolling back to MM should completely reset your phone.
You cannot flash TWRP without unlocking Bootloader. But that will not help much for resetting Google protection.
Btw, enable Developer's menu, does it allow you to unlock FRP/OEM Unlocking - in that case you will be able to reset all from EMUI recovery.
Click to expand...
Click to collapse
He can't get passed the setup screen
Twisted Prime said:
He can't get passed the setup screen
Click to expand...
Click to collapse
- Boot to Recovery (switch off, press and keep pressing Vol+ and Pow). Does it boot to stock Recovery and does it allow there to Factory reset (it should but if FRP was unlocked)
- Boot to Fastboot (switch off, connect by USB to PC, press Vol- and Pow), do you see Phone (Bootloader) and FRP locked or unlocked?
zgfg said:
- Boot to Recovery (switch off, press and keep pressing Vol+ and Pow). Does it boot to stock Recovery and does it allow there to Factory reset (it should but if FRP was unlocked)
- Boot to Fastboot (switch off, connect by USB to PC, press Vol- and Pow), do you see Phone (Bootloader) and FRP locked or unlocked?
Click to expand...
Click to collapse
It is stock recovery. I don't recall the option for factory reset. In fact there's no options at all, save for reboots.
Fastboot says everything is locked as it should be.
Don't know how to downgrade to MM.
velis74 said:
It is stock recovery. I don't recall the option for factory reset. In fact there's no options at all, save for reboots.
Fastboot says everything is locked as it should be.
Don't know how to downgrade to MM.
Click to expand...
Click to collapse
Rollback instructions are here
https://forum.xda-developers.com/showpost.php?p=72153575&postcount=2
But not sure would it allow you to setup.
That is Factory Reset Protection (FRP/OEM Unlocking) - if it was unlocked you would be allowed to reset from recovery.
You can ask seller - maybe he can login to his Google account and remotely remove Google account from the sold phone.
Or you can try DC Unlocker, not sure would it work
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
Well, DC unlocker ultimately worked, but not before buying a wrong package, having to ask tech support, etc, etc. Not to mention the guy really has no patience for people who don't have his level of understanding of the subject. Why does he do it then if he hates the whole thing so much?
velis74 said:
Well, DC unlocker ultimately worked, but not before buying a wrong package, having to ask tech support, etc, etc. Not to mention the guy really has no patience for people who don't have his level of understanding of the subject. Why does he do it then if he hates the whole thing so much?
Click to expand...
Click to collapse
So did you use DC Unlocker to unlock Bootloader or DC Phoenix to reinstall the phone?
zgfg said:
So did you use DC Unlocker to unlock Bootloader or DC Phoenix to reinstall the phone?
Click to expand...
Click to collapse
DC unlocker. I wanted minimal impact on the OS as the phone is for my daughter and she doesn't do custom ROMs et al
velis74 said:
DC unlocker. I wanted minimal impact on the OS as the phone is for my daughter and she doesn't do custom ROMs et al
Click to expand...
Click to collapse
Sorry for bothering but I'm interested now - when Bootloader was unlocked (and FRP too), were you just able to pass setup or you needed to do Factory reset from Recovery or how did you get the stock ROM working for you
Final resolution: the seller sent me an invoice. I guess that means that the phone wasn't stolen after all since they can only expect that this will be entered into Huawei databases.
zgfg said:
Sorry for bothering but I'm interested now - when Bootloader was unlocked (and FRP too), were you just able to pass setup or you needed to do Factory reset from Recovery or how did you get the stock ROM working for you
Click to expand...
Click to collapse
The procedure was thus:
1. unlocker unlocked the FRP
2. phone rebooted into a factory reset (low level) mode - it specifically said "low level"
3. phone booted into normal Android where the FRP protection was no longer active. On screen where it previously demanded a previous Google account it now only demanded A (any) Google account as I'm used to from all the other phones I ever bought.
Sorry old post