|
Welcome to the GSM-Forum forums. You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. Only registered members may post questions, contact other members or search our database of over 8 million posts. Registration is fast, simple and absolutely free so please - Click to REGISTER! If you have any problems with the registration process or your account login, please contact contact us . |
|
Register | FAQ | Donate | Forum Rules | Root any Device | ★iPhone Unlock★ | ★ Direct Codes ★ | Direct Unlock Source |
| LinkBack | Thread Tools | Display Modes |
04-26-2019, 23:02 | #1 (permalink) |
Junior Member Join Date: Jun 2009
Posts: 3
Member: 1063405 Status: Offline Thanks Meter: 0 | Honor 8 EMUI 8.0.0 It's currently on a partial build of EMUI 8.0.0 without any system apps, Unable to use the projectMenu *#*#2846579#*# FastBoot Shows Phone Locked FRP Lock Code: Looking for a device in upgrade mode No devices detected in upgrade mode Device found: 73QDU16818008273 25/04/2019 00:01:23 Starting to write device in FASTBOOT mode... Looking for a device in fastboot mode Device found: REDACTED Getting IMEI... Getting build number... Getting model ... Getting battery state... Getting backdoor info... Getting lock state info... Getting lock boot info... SN:REDACTED IMEI:REDACTED IMEI1:REDACTED Build number: :System 8.0.0.046(0JSQ) Model: FRD-L09 Battery state: 4683mv OEM lock state info: FB LockState: LOCKED USER LockState: LOCKED OEM get bootinfo: locked Device with unsupported security patch User accepted to update device with unsupported security patch Writing XLOADER partition XLOADER partition UPDATE :FAIL Command not allowed Device with unsupported security patch 25/04/2019 23:07:46 Writing device finished - INCOMPLETE I'd really like this phone to work again. Thanks |
04-29-2019, 09:25 | #2 (permalink) |
Product Supporter Join Date: Sep 2013 Location: Lithuania, Kaunas
Posts: 4,690
Member: 2023196 Status: Offline Thanks Meter: 1,893 | You are flashing same version of android right? It's hard to see the problem without really knowing what are you trying exactly to do for device and with what files. Usually problem lies there as people tend to try to downgrade or upgrade using incorrect version security patches that do not match current one in device which demands to use different files. |
The Following User Says Thank You to Namelocked For This Useful Post: |
04-29-2019, 21:14 | #3 (permalink) |
Junior Member Join Date: Jun 2009
Posts: 3
Member: 1063405 Status: Offline Thanks Meter: 0 | Thanks Namelocked, Yes, I was trying to restore the latest Oreo build to my device. I was on Oreo before switching to a custom ROM, switching back has caused my bootloader to lock and grey out the OEM Lock setting in the developer menu. I tried flashing a number of different builds and they all failed. Any help would be greatly appreciated to restore my device to a useable state. My phone now shows as having 8.0.0.046(0EE2) which isn't even a build I can find online. I was trying to revert to 8.0.0.562. Last edited by linkazoid; 04-29-2019 at 21:21. |
05-01-2019, 21:06 | #5 (permalink) | |
Junior Member Join Date: Jun 2009
Posts: 3
Member: 1063405 Status: Offline Thanks Meter: 0 | Quote:
Can I use testpoints to revive? It's usable to make calls, but no system apps and can't sideload all google apps either to make it fully useful either. | |
05-02-2019, 08:12 | #6 (permalink) |
Product Supporter Join Date: Sep 2013 Location: Lithuania, Kaunas
Posts: 4,690
Member: 2023196 Status: Offline Thanks Meter: 1,893 | You see, we do not have solutions for specific problems... So asking here will not help. To revive a mobile means to to bring it back from bricked state - does not boot at all. |
Bookmarks |
| |
|