RealmeGT 5G Root problem ! - Realme GT

Hi there,
Having an issue rooting this phone.
rmx2202_11_A.25
At the moment ive got to a point where ive got it setup with adb and i put in " adb reboot fastboot ". I then boot into the fast boot ( ive seen in places people suggesting putting in " adb reboot bootloader " however in that mode my pc cant see my phone as a fastboot or adb device so ive given up on that atm )
Everythign seems good im in a mode called fastbootd and the phone is listed as a Fastboot device. However when i type in " fastboot flasthing unlocked ( also tried fastboot flashing unlocked critical ( with and without _ between words ) also tried a few other i get the error:
"FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed"
Cant get any further than this. I did wonder if this command is actually wrong and there is a hidden command for this function
ive done adb help which shows this command and a list of other commands however not many of them seem to work for some reason.
additional info
. usb debugging is enabled and the oem unlock setting is on.
. i've installed android studio and im using the adp tools from that.
. ive installed the google usb drivers from the android studios.
. ive also installed specific usb drivers for my phone ( or so i think )
. ive installed the testing app which i used get into the bootloader originally
Ive already tried
. Many but not all the app based ways of rooting. Unfortunately every one i have tried so far ..... the phone has stopped me installing it due to it being a rooting app. I tried installaing an app to clone the app which ive seen online however this didnt seem to wor
. Ive tried kingo root on the Pc but it gets stuck on the part where it says to enable usb debugging.
Any help would be amazing !
Thank you

i had lots of issues trying to do this.
are you
A) in fastbootd - you need to use the deeptest.apk to install twrp
B) did you open up powershell, I was trying to use cmd as that's what i had used before, but wouldn't do it until it was done through powershell.

unparalleled82 said:
i had lots of issues trying to do this.
are you
A) in fastbootd - you need to use the deeptest.apk to install twrp
B) did you open up powershell, I was trying to use cmd as that's what i had used before, but wouldn't do it until it was done through powershell.
Click to expand...
Click to collapse
Hi Unparalleled82,
So i think i was actually using "adb reboot bootloader " instead of the app at times so ive just tried it using the app however it still doesnt come up as a fastboot device. When i put in the command " fastboot flashing unlocked " i just get " waiting for any device " for ever.
Few things im wondering do you have exacly the same phone as me RealmeGT 5G rmx2202_11_A.25. Its good to know you have done it and the way you did it. Because mines not working the same way ( assuming the models are the same ) im thinking now its a driver issue perhaps .
So when im just doing adb sideload or something when the phone is booted into the OS i dont have the yellow triangles however in this fastboot mode i see this...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Which does indicated a driver issue however when i try to manually install the correct drivers windows tells me its already has the best driver. ( im browsing to the folder where ive downloaded the drivers here )
Ive tried installing them through the legacy hardware option which does install them but phone still doesnt show up in fastboot devices.
Ive also installed the driver using android studios ... you can see google usb drivers ticked.
Ive also googled how to stop windows from automatically installing drivers from windows update then uninstalled my device .. plugged it back in ... then installed them. However thinking now perhaps i should uninstall ... then install the drivers before plugging in the phone ? any ideas ?
Some more info this has reminded me of. Ive tried a different usb cable, a different usb port ( both usb 2.0 ) and a different computer already.
As for the powershell I'm certain i'm using it not the cmd line. I'm holding shift in the correct folder then right click, then open the power shell window.
Any more help would be amazing. Im going to have a look more into fastboot driver problems

I know you said you'd changed your cables, but that's another one of the issues i faced.
The phone would show just like yours, but wouldn't show in fastboot. I changed for a different one and then it actually worked. You won't get anywhere until within powershell it shows under the command
adb devices

unparalleled82 said:
I know you said you'd changed your cables, but that's another one of the issues i faced.
The phone would show just like yours, but wouldn't show in fastboot. I changed for a different one and then it actually worked. You won't get anywhere until within powershell it shows under the command
adb devices
Click to expand...
Click to collapse
Ill try another cable now for sure see what happens. About the powershell im confused what you mean sorry. Im definitely in the power shell.... the phone lists as an adb device ... when its not in fastboot mode that is ... its just it wont list as a fastboot device in fastboot mode.

Piefrag said:
Ill try another cable now for sure see what happens. About the powershell im confused what you mean sorry. Im definitely in the power shell.... the phone lists as an adb device ... when its not in fastboot mode that is ... its just it wont list as a fastboot device in fastboot mode.
Click to expand...
Click to collapse
sorry, what i mean is, mine showed in adb but not in fastboot until i changed for a better cable

unparalleled82 said:
sorry, what i mean is, mine showed in adb but not in fastboot until i changed for
Click to expand...
Click to collapse
Ahh got you now. So ive tried the cable sent with the phone and now 2 other cables and all of them have the same issue so im thinking its not the cable atm.
Ive seen on youtube a method for rooting it from anotehr phone.... i have no idea if it works but ive bought a usb c too usb c cable to give it a try at least !
Thinking now i may buy another usb A too usb C cable of good quality too make absolute sure its not the cable messing it up.

Piefrag said:
Hi there,
Having an issue rooting this phone.
rmx2202_11_A.25
At the moment ive got to a point where ive got it setup with adb and i put in " adb reboot fastboot ". I then boot into the fast boot ( ive seen in places people suggesting putting in " adb reboot bootloader " however in that mode my pc cant see my phone as a fastboot or adb device so ive given up on that atm )
Everythign seems good im in a mode called fastbootd and the phone is listed as a Fastboot device. However when i type in " fastboot flasthing unlocked ( also tried fastboot flashing unlocked critical ( with and without _ between words ) also tried a few other i get the error:
"FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed"
Cant get any further than this. I did wonder if this command is actually wrong and there is a hidden command for this function
ive done adb help which shows this command and a list of other commands however not many of them seem to work for some reason.
additional info
. usb debugging is enabled and the oem unlock setting is on.
. i've installed android studio and im using the adp tools from that.
. ive installed the google usb drivers from the android studios.
. ive also installed specific usb drivers for my phone ( or so i think )
. ive installed the testing app which i used get into the bootloader originally
Ive already tried
. Many but not all the app based ways of rooting. Unfortunately every one i have tried so far ..... the phone has stopped me installing it due to it being a rooting app. I tried installaing an app to clone the app which ive seen online however this didnt seem to wor
. Ive tried kingo root on the Pc but it gets stuck on the part where it says to enable usb debugging.
Any help would be amazing !
Thank you
Click to expand...
Click to collapse
did you use deep app and press "start the in-depth test" because i forgot to do and i spent 2 days to understand whats the problem

grown_man said:
did you use deep app and press "start the in-depth test" because i forgot to do and i spent 2 days to understand whats the problem
Click to expand...
Click to collapse
Yes i did but thank you. Ive done that and it boots into the fastboot mode. Problem is my phone doesn't list as a fastboot device when in fastboot mode.

Piefrag said:
Yes i did but thank you. Ive done that and it boots into the fastboot mode. Problem is my phone doesn't list as a fastboot device when in fastboot mode.
Click to expand...
Click to collapse
another solution mighte be to try https://forum.xda-developers.com/t/rmx2202-realme-gt-5g-ui2-0-ui3-0-all-root.4377165/ link - one click root. theres their own usb drivers installation. its in chinese but theres only one place to click for installation of drivers

grown_man said:
another solution mighte be to try https://forum.xda-developers.com/t/rmx2202-realme-gt-5g-ui2-0-ui3-0-all-root.4377165/ link - one click root. theres their own usb drivers installation. its in chinese but theres only one place to click for installation of drivers
Click to expand...
Click to collapse
Thats it ! Thank you so much

Related

{HELP}only fastboot is accessible

(used unofficial way to unlock) .please anyone help only fastboot screen is accessible not edl and nothing other,bricked by flashing 7.2.3 recovery rom through twrp-cofface recovery.
please help as soon as possible not able to access device
when i try to switch on the phone then mi logo blinks fro two times then gets off.
when tried miflash it says device is locked .
in device manager this shows when connected in fastboot modeView attachment 3736364
this shows when connected for chargingView attachment 3736365
and when try to flash with miflash tool this error comes
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
shubham tech said:
please anyone help only fastboot screen is accessible not edl and nothing other,bricked by flashing 7.2.3 recovery rom through twrp-cofface recovery.
please help as soon as possible not able to access device
when i try to switch on the phone then mi logo blinks fro two times then gets off.
when tried miflash it says device is locked .
in device manager this shows when connected in fastboot modeView attachment 3736364
this shows when connected for chargingView attachment 3736365
Click to expand...
Click to collapse
Are you able to access recovery (Power + Vol Up)?
If not:
Marshall London Bootloader Interface gave me some problems before. Try this:
1. Right-click "Marshall London Bootloader Interface" in your Device Manager and click "Update Driver Software..."
2. Select "Browse my computer for driver software"
3. "Let me pick from a list of device drivers on my computer"
4. In the list you should be able to find "Android" (or something like that) and in the sub-menu "ADB" (again, something like that), provided you have adb drivers installed on your computer.
5. Select "ADB" drivers to replace "Marshall London Bootloader Interface"
You should be able to use ADB in a command window to reapply Cofface's TWRP recovery and access it. If it's in Chinese see my comment here.
Hope this helps solve at least some of the problem.
Does your bootloader officially unlocked? If yes, just download a miui fastboot rom, and flash it through miflash
Edit: oops I didn't read the whole post. sorry
shubham tech said:
please anyone help only fastboot screen is accessible not edl and nothing other,bricked by flashing 7.2.3 recovery rom through twrp-cofface recovery.
please help as soon as possible not able to access device
when i try to switch on the phone then mi logo blinks fro two times then gets off.
when tried miflash it says device is locked .
in device manager this shows when connected in fastboot modeView attachment 3736364
this shows when connected for chargingView attachment 3736365
Click to expand...
Click to collapse
Hello..
I too faced such situation...
I tried to root my redmi note 3 pro..(SD)
I followed the unofficial method which I found here in XDA.. Don't know ,where I missed any step...
My phone gets in same situation as yours..
It can boot into fastboot mode ( volume - and power ),
If I turn on it flashes mi logo two times and .. Gets into diagnostic mode ...
Searched a lot.. But.. Can't find my exact situation in any thread..
Somewhere in some forum I found that.. Let the battery be fully drain.. And.. Without turning on.. Charge the phone to at least 30% .. And den enter edl mode by pressing and holding two volume buttons...( + & -).
My mobile is at 97 % of charge when it got bricked .
Which means... A few days to drain it fully..
Omg... I can't wait..
So.. I decided to open the back cover..
Gently opened it.. And.. Removed battery strip.. And.. Placed it again ...
Den..
While connecting to PC through USB cable..
I pressed and hold the two volume buttons..
Connected cable..and.. Pressed both volume buttons as fast as I can after connecting cable.. And holded for two secs..
There. U can enter edl mode...
So that u can flash.. Global stable ROM..via mi flash tool...
If u failed...
Remove the battery connector . and.. Put it again..
Close mi flash.. Open it again.. Try to put the phone in edl again...
I don't know .this can be done in another easy way..
But.. I have done this way...
Tell me if u succeed..
can you execute "adb devices" and "adb reboot edl" in command window when connecting your phone to PC? if so, you might use latest MiFlash (20160330 or 20160401) to flash rom.
MIUI forum has a guide to rescue bricked redmi note 3, you should have a look at it.
The posts are http://en.miui.com/thread-274589-1-1.html and http://en.miui.com/thread-235865-1-1.html
If the vol + and - trick does not work, I was in the same situation and I ended up doing this: http://forum.xda-developers.com/redmi-note-3/how-to/redmi-note-3-pro-snapdragon-650-edition-t3367774
if you unlock official way, just run the unlock tools again
Immortal68 said:
Are you able to access recovery (Power + Vol Up)?
If not:
Marshall London Bootloader Interface gave me some problems before. Try this:
1. Right-click "Marshall London Bootloader Interface" in your Device Manager and click "Update Driver Software..."
2. Select "Browse my computer for driver software"
3. "Let me pick from a list of device drivers on my computer"
4. In the list you should be able to find "Android" (or something like that) and in the sub-menu "ADB" (again, something like that), provided you have adb drivers installed on your computer.
5. Select "ADB" drivers to replace "Marshall London Bootloader Interface"
You should be able to use ADB in a command window to reapply Cofface's TWRP recovery and access it. If it's in Chinese see my comment here.
can you tell about this in some brief from where to select which driver please help?
Hope this helps solve at least some of the problem.
Click to expand...
Click to collapse
can you tell about this in some brief from where to select which driver please help?
shubham tech said:
can you tell about this in some brief from where to select which driver please help?
Click to expand...
Click to collapse
Created a short slide show. Hope this helps.
If you don't see "Android ADB Interface you have to install ADB/fastboot first. Minimal ADB and fastboot drivers
Best of luck. Let me know if anything else is still unclear to you.
Abhi45 said:
Hello..
I too faced such situation...
I tried to root my redmi note 3 pro..(SD)
I followed the unofficial method which I found here in XDA.. Don't know ,where I missed any step...
My phone gets in same situation as yours..
It can boot into fastboot mode ( volume - and power ),
If I turn on it flashes mi logo two times and .. Gets into diagnostic mode ...
Searched a lot.. But.. Can't find my exact situation in any thread..
Somewhere in some forum I found that.. Let the battery be fully drain.. And.. Without turning on.. Charge the phone to at least 30% .. And den enter edl mode by pressing and holding two volume buttons...( + & -).
My mobile is at 97 % of charge when it got bricked .
Which means... A few days to drain it fully..
Omg... I can't wait..
So.. I decided to open the back cover..
Gently opened it.. And.. Removed battery strip.. And.. Placed it again ...
Den..
While connecting to PC through USB cable..
I pressed and hold the two volume buttons..
Connected cable..and.. Pressed both volume buttons as fast as I can after connecting cable.. And holded for two secs..
There. U can enter edl mode...
So that u can flash.. Global stable ROM..via mi flash tool...
If u failed...
Remove the battery connector . and.. Put it again..
Close mi flash.. Open it again.. Try to put the phone in edl again...
I don't know .this can be done in another easy way..
But.. I have done this way...
Tell me if u succeed..
Click to expand...
Click to collapse
thanks for help but didnt succeed.
Immortal68 said:
Created a short slide show. Hope this helps.
If you don't see "Android ADB Interface you have to install ADB/fastboot first. Minimal ADB and fastboot drivers
Best of luck. Let me know if anything else is still unclear to you.
Click to expand...
Click to collapse
thanks for help but none of above worked for me.
adb things will not work if phone just got to fastboot.
you must look on 'ports' section on device manager.
it will detect qcom hs-usb qloader 9008 if you're on edl mode (you can use miflash on this situation).
but on bricked phone it will show qcom hs-usb diagnostic 900e if you try to enter edl. here you can't do anything.
the only working solution known is by disassembling the phone and use test-point method.
but luckily I don't have to do it. mine works just by re-unlock using unlock tool.
just apply the unlock code with your last entered mi account on phone. when you got the sms, go unlock it
aabenroi said:
adb things will not work if phone just got to fastboot.
you must look on 'ports' section on device manager.
it will detect qcom hs-usb qloader 9008 if you're on edl mode (you can use miflash on this situation).
but on bricked phone it will show qcom hs-usb diagnostic 900e if you try to enter edl. here you can't do anything.
the only working solution known is by disassembling the phone and use test-point method.
but luckily I don't have to do it. mine works just by re-unlock using unlock tool.
just apply the unlock code with your last entered mi account on phone. when you got the sms, go unlock it
Click to expand...
Click to collapse
even unlock tool says cant verify device, this is really a xiaomi,dont expect anything better from xiaomi.
shubham tech said:
even unlock tool says cant verify device, this is really a xiaomi,dont expect anything better from xiaomi.
Click to expand...
Click to collapse
If u had not opened ur phone and tried test point method , take it to service center ASAP.
sanjib734 said:
If u had not opened ur phone and tried test point method , take it to service center ASAP.
Click to expand...
Click to collapse
yes i am going to service center on tomorrow .
shubham tech said:
yes i am going to service center on tomorrow .
Click to expand...
Click to collapse
best of luck.
sanjib734 said:
best of luck.
Click to expand...
Click to collapse
got my phone repaired from mi service center.
Immortal68 said:
Are you able to access recovery (Power + Vol Up)?
If not:
Marshall London Bootloader Interface gave me some problems before. Try this:
1. Right-click "Marshall London Bootloader Interface" in your Device Manager and click "Update Driver Software..."
2. Select "Browse my computer for driver software"
3. "Let me pick from a list of device drivers on my computer"
4. In the list you should be able to find "Android" (or something like that) and in the sub-menu "ADB" (again, something like that), provided you have adb drivers installed on your computer.
5. Select "ADB" drivers to replace "Marshall London Bootloader Interface"
You should be able to use ADB in a command window to reapply Cofface's TWRP recovery and access it. If it's in Chinese see my comment here.
Hope this helps solve at least some of the problem.
Click to expand...
Click to collapse
Sorry to chime in (and open up this discussion) months later, but: I have marshall london bootloader interface Here's the thread with my issue http://en.miui.com/thread-362628-1-1.html (if you don't mind). My phone has finally powered off after bootlooping for hours (was able to switch between fastboot mode and mi logo bootloop). Waiting to recharge and try and enter recovery or try this (http://xiaomitips.com/guide/how-to-put-redmi-note-3-into-edl-mode/). Maybe you have some other pointers for me? Please? :laugh: I'm nearing my wits end
Hope this isn't rude and all and hope you have some ideas. Thanks in advance!
shubham tech said:
got my phone repaired from mi service center.
Click to expand...
Click to collapse
how much time they take to repair it
devsc said:
how much time they take to repair it
Click to expand...
Click to collapse
½ an hour
Sent from my Redmi Note 3 using Tapatalk

problems with Xpeira X ADB and Flashtool

Hi,
i have a problem with ADB drivers for the phone. i have downloaded it from Sony (Link:https://developer.sonymobile.com/downloads/drivers/xperia-x-driver/) and install it like they said (by going in to device manager and manually installing it). after booting it to Fastboot, Flashtool says i have to install them from the drivers folder, which however, does not contain the Xperia X driver. Also, when selecting the Flashboot and Flashmode drivers, one installs but the other doesn't which is "Google, Inc, (WinUSB) Android UsbDeviceClass".
While in Fastboot, i tired to delete it, then update it using the download driver from Sony which failed to install. Also, in device manager it say something like S1 fastboot driver with a Waring symbol (it's not recognised), and upon checking in flashtool while in Fastboot, it says there is no ADB drivers installed, just Fastboot.
i have tried booting the phone with USB debugging and it does recognise it, but still doesn't work when booting to Fastboot.
BTW i am on Windows 10
any information would be useful.
Force install adb driver over device manager
max26292 said:
Force install adb driver over device manager
Click to expand...
Click to collapse
thanks, just to confirm, by force install do you mean to download from sony and install within device manager, by 'adding legacy software' ?
if so, i have done that and the driver appears, and shows the following error:
This device cannot start. (Code 10)
The specified request is not a valid operation for the target device.
Also, still and unrecognised 'S1 fastboot ' driver appeared when in Fastboot.
thank you again.
remar786 said:
thanks, just to confirm, by force install do you mean to download from sony and install within device manager, by 'adding legacy software' ?
if so, i have done that and the driver appears, and shows the following error:
This device cannot start. (Code 10)
The specified request is not a valid operation for the target device.
Also, still and unrecognised 'S1 fastboot ' driver appeared when in Fastboot.
thank you again.
Click to expand...
Click to collapse
If you install Jdk you already have driver, you just right click choose update driver> choice option 2 ( I choose driver from my computer > choose from list device > android > adb. Next, it will show a alert message bla bla > yes :3 use flash tools again to see the magic
max26292 said:
If you install Jdk you already have driver, you just right click choose update driver> choice option 2 ( I choose driver from my computer > choose from list device > android > adb. Next, it will show a alert message bla bla > yes :3 use flash tools again to see the magic
Click to expand...
Click to collapse
quick question, what is JDK?
hopefully i will try when i hear back, thanks again .
How to install ADB Xperia x
finally!!!
it's worked. Thanks for your help max26292 (although would have been nice to hear back but a huge thank you!)!
Here's what i did (not in the exact order though)
i used the instruction from Sony - http://support.sonymobile.com/global-en/xperiae3dual/kb/0231018805656b91c0145c620eeaf004cb9/(Not for the Xperia X though but usable) on how to install the Xperia driver, and after restarting the PC, Flashtool still didn't recognise while in Fastboot. Also, in device manage there, was a Waring sign next to it, and gave the error as mentioned previously. image is below of the sign.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I then installed the 15 seconds ADB from https://forum.xda-developers.com/showthread.php?t=2588979 ( i keptpressing Y) after a reboot and putting the phone in Fastboot, still Flashtool had the same messages about drivers, like i said in the first post.
i then tired out max26292's method, which there are images below to show the process. i put the phone in Fastboot, and where the warning sign was, NOT THE SAME PLACE AS THE IMAGE SHOWN ABOVE, rather where it said "S1Boot Fastboot" . using the steps you mentioned (THANKS ALOT BTW!) :
i right clicked on the s1 fastboot> clicked update driver> chose the second option - browse my computer>
the clicked on "let me pick from a list of device drivers on my computer"> then browsed for the driver i'd already installed from Sony - the "Sony sa0114> kept clicking next, and yes to a warning message> restarted computer and BANG! it worked!
i however should mention that i did try to install the flashmode and fastboot driver from flashtool, but one of them failed to install - i have mentioned n my previous post, please refer back. so, you may want to do that, but i think the 15 seconds ADB will do it for you. also, i have not done commands so i can't test it out fully, bu when i do, i will let you know.
again i would like to thank everyone for your help, really appreciate it!
P.S. Please put a F U C K ING updated guide up Sony, T W A T s.
remar786 said:
finally!!!
it's worked. Thanks for your help max26292 (although would have been nice to hear back but a huge thank you!)!
Here's what i did (not in the exact order though)
i used the instruction from Sony - http://support.sonymobile.com/global-en/xperiae3dual/kb/0231018805656b91c0145c620eeaf004cb9/(Not for the Xperia X though but usable) on how to install the Xperia driver, and after restarting the PC, Flashtool still didn't recognise while in Fastboot. Also, in device manage there, was a Waring sign next to it, and gave the error as mentioned previously. image is below of the sign.
I then installed the 15 seconds ADB from https://forum.xda-developers.com/showthread.php?t=2588979 ( i keptpressing Y) after a reboot and putting the phone in Fastboot, still Flashtool had the same messages about drivers, like i said in the first post.
i then tired out max26292's method, which there are images below to show the process. i put the phone in Fastboot, and where the warning sign was, NOT THE SAME PLACE AS THE IMAGE SHOWN ABOVE, rather where it said "S1Boot Fastboot" . using the steps you mentioned (THANKS ALOT BTW!) :
i right clicked on the s1 fastboot> clicked update driver> chose the second option - browse my computer>
the clicked on "let me pick from a list of device drivers on my computer"> then browsed for the driver i'd already installed from Sony - the "Sony sa0114> kept clicking next, and yes to a warning message> restarted computer and BANG! it worked!
i however should mention that i did try to install the flashmode and fastboot driver from flashtool, but one of them failed to install - i have mentioned n my previous post, please refer back. so, you may want to do that, but i think the 15 seconds ADB will do it for you. also, i have not done commands so i can't test it out fully, bu when i do, i will let you know.
again i would like to thank everyone for your help, really appreciate it!
P.S. Please put a F U C K ING updated guide up Sony, T W A T s.
Click to expand...
Click to collapse
Please read carefully =-= I told Android driver not sony =-=
max26292 said:
Please read carefully =-= I told Android driver not sony =-=
Click to expand...
Click to collapse
thank you, but i don't have them. i only have the Sony ones and ADB by Samsung, which the 15 seconds ADB program installed.
when i connected to Fastboot, Flashtool does recognise it, so it should work right?
thanks again
pm me on facebook when you onl I think we should do a private mess and teamview
max26292 said:
pm me on facebook when you onl I think we should do a private mess and teamview
Click to expand...
Click to collapse
Thank you but it's working fine with the way I installed it (by installing the Sony driver from the list)
remar786 said:
Thank you but it's working fine with the way I installed it (by installing the Sony driver from the list)
Click to expand...
Click to collapse
you also use driver pack in flashtool because it include android driver
max26292 said:
you also use driver pack in flashtool because it include android driver
Click to expand...
Click to collapse
yes i did use it, but only one installed. i did before i installed both drives, (Fastboot and ADB) but one installed and one didn't ( i think the ADB driver failed and the other one installed).
remar786 said:
Hi,
i have a problem with ADB drivers for the phone. i have downloaded it from Sony (Link:https://developer.sonymobile.com/downloads/drivers/xperia-x-driver/) and install it like they said (by going in to device manager and manually installing it). after booting it to Fastboot, Flashtool says i have to install them from the drivers folder, which however, does not contain the Xperia X driver. Also, when selecting the Flashboot and Flashmode drivers, one installs but the other doesn't which is "Google, Inc, (WinUSB) Android UsbDeviceClass".
While in Fastboot, i tired to delete it, then update it using the download driver from Sony which failed to install. Also, in device manager it say something like S1 fastboot driver with a Waring symbol (it's not recognised), and upon checking in flashtool while in Fastboot, it says there is no ADB drivers installed, just Fastboot.
i have tried booting the phone with USB debugging and it does recognise it, but still doesn't work when booting to Fastboot.
BTW i am on Windows 10
any information would be useful.
Click to expand...
Click to collapse
1. install XPERIA COMPANION
2. INSTALL FLASHTOOL (www.flashtool.net)
3. after installing flastool goto C:\Flashtool\drivers and you will find "Flashtool-drivers.exe" / run it and install from list "common fastboot drivers", "common flashmod drivers" and xperia z series with Xperia X series motherboard drivers.
windows 10 gives digital signature verification errors so you have to
Use the following steps to disable driver signature enforcement.
Click the Start menu and select Settings.
Click Update and Security.
Click on Recovery.
Click Restart now under Advanced Startup.
Click Troubleshoot.
Click Advanced options.
Click Startup Settings.
Click on Restart.
Click to expand...
Click to collapse
then repeat point "3"
you should be ok
frp locked huawei honor 20 wont connect to laptop
hi mate im trying to connect my huawei honor 20 to my laptop but it doesnt even come up with anything in device manager. its frp locked and i need to access fastboot mode to enter the frp key. can anyone please help me.

Issue with my Moto X Play's Boot Logo

This is the first time it happens to me. I'm not an expert with cellphones, but i think this is a very weird situation.
This is the history. My cousin gave me his Moto X Play as a gift after he went to a local to repair the phone's broken display. It looked good well when i used it at the first time. But, when i tried to root that phone i have noticed a very weird issue....
The phone can't enter to a Fastboot mode when i press the buttons, and when i turn it on, it doesn't seem to have a boot logo. Im not sure about this situation, but im afraid that this phone doesn't have a boot logo, or fastboot menu.
-The phone doesn't seems to be rooted before, or have an another recovery, but i'm not sure about this.
-Everyting in the phone's system seems ok.
-The phone turns on with order (The right time and right boot), there's also the boot animation except that there's no logo.
-I have a little trouble with the phone's speaker, but, thats an another situation.
What can i do about? What do you think this is about? I can't talk with my cousin because his not living in my town, and he doesn't know about this.
Are you sure all the buttons are working ?
Are you saying that the phone manages to boot to the OS (Android)
It also sounds like you've deleted or corrupted some files e.g. the boot logo file (which contains a load of images not just the unlocked one)
Once its booted and you connect via ADB?
Have you rooted the phone, and does ADB have root.
Have you tried installing a replacement boot img file ? (not sure if this is possible from ADB)
RogerClark said:
Are you sure all the buttons are working ?
Are you saying that the phone manages to boot to the OS (Android)
It also sounds like you've deleted or corrupted some files e.g. the boot logo file (which contains a load of images not just the unlocked one)
Once its booted and you connect via ADB?
Have you rooted the phone, and does ADB have root.
Have you tried installing a replacement boot img file ? (not sure if this is possible from ADB)
Click to expand...
Click to collapse
.....
1. Yes! Pretty sure
2. Yes, the OS runs perfectly
3. I'm not sure about that, it may be
4. Nope
5. Not me, maybe another guy, but the phone doesn't seem to be rooted right now
6. Nope
Anny sugest?
Try entering fastboot with no power cable connected (not connected to the PC or charger)
Hold the power and volume down for at least 15 secs (needs longer than you expect)
(I see that on some Motorola G's if it is connected to a PC or power it doesn't seem to enter fastboot)
RogerClark said:
Try entering fastboot with no power cable connected (not connected to the PC or charger)
Hold the power and volume down for at least 15 secs (needs longer than you expect)
(I see that on some Motorola G's if it is connected to a PC or power it doesn't seem to enter fastboot)
Click to expand...
Click to collapse
I tried those before and nothing. Anything else you can think for me?
Have you tied this
https://forum.xda-developers.com/showthread.php?t=1853159
RogerClark said:
Have you tied this
https://forum.xda-developers.com/showthread.php?t=1853159
Click to expand...
Click to collapse
I have tried, but console says my ADB Device is Offline. What can i do? My ADB Tools are up to date
I presume you followed the instructions in the linked thread and enabled the developer options etc
One thing I've noticed about Marshmallow and Nougat is that ADB doesnt seem to work unless you select File Transfer instead of Charging in the "Using USB to " notification popup.
Otherwise if you do
adb devices
there is nothing in the list
RogerClark said:
I presume you followed the instructions in the linked thread and enabled the developer options etc
One thing I've noticed about Marshmallow and Nougat is that ADB doesnt seem to work unless you select File Transfer instead of Charging in the "Using USB to " notification popup.
Otherwise if you do
adb devices
there is nothing in the list
Click to expand...
Click to collapse
I'll keep that in mind, thanks a lot for those sugestions.
RogerClark said:
I presume you followed the instructions in the linked thread and enabled the developer options etc
One thing I've noticed about Marshmallow and Nougat is that ADB doesnt seem to work unless you select File Transfer instead of Charging in the "Using USB to " notification popup.
Otherwise if you do
adb devices
there is nothing in the list
Click to expand...
Click to collapse
UPDATE: It seems i can access to bootloader from the computer, but screen is black when that happens. When i finaly entered to fastboot mode screen was all black and nothing happened. I noticed about this 'cause when i pushed the "+" button phone has restarted with normaly. What do you think about this?
As an extra, these messages apear when i write an ADB comand...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slot:recovery: not found
UPDATE: I've already unlocked the phone's bootloader, but can't flash the TWRP Recovery. When i try it says it was flashed sucessfuly, but, when i enter to recovery mode, it haves the stock recovery.
I've not personally experienced this, but I think you are supposed to make sure you reboot back onto recovery after flashing TWRP because some systems will overwrite TWRP the next time you boot.
If you can get hold of the original ROMs for the phone, (search this forum). I'd recommend perhaps you flash them first, using mfastboot, and get the phone back into a factory configuration.
And make sure you erase the existing files first, on my Moto G I normally erase all of these
mfastboot erase boot
mfastboot erase system
mfastboot erase userdata
mfastboot erase cache
mfastboot erase webtop
mfastboot erase preinstall
But moto X is probably different
RogerClark said:
I've not personally experienced this, but I think you are supposed to make sure you reboot back onto recovery after flashing TWRP because some systems will overwrite TWRP the next time you boot.
If you can get hold of the original ROMs for the phone, (search this forum). I'd recommend perhaps you flash them first, using mfastboot, and get the phone back into a factory configuration.
And make sure you erase the existing files first, on my Moto G I normally erase all of these
mfastboot erase boot
mfastboot erase system
mfastboot erase userdata
mfastboot erase cache
mfastboot erase webtop
mfastboot erase preinstall
But moto X is probably different
Click to expand...
Click to collapse
What do you refer with factory configuration? Actualy the phone are supposed to be on Stock. The phone has never unlocked by bootloader, i'm almost sure of that. So, for that reason i suppose the phone had never another rom.
Maybe i can be wrong, but. Why do you thing there are missing files?

Wileyfox 2 corrupted after update to Android 7.1.2

Updated my phone to Android 7.1.2 today, using the built in updater.
Now when I restart, I get the following on the bootloader: "Your device is corrupt. It can't be trusted and may not work properly"
It still boots normally. But Android Pay doesn't work.
Any suggestions for fixing this?
I can't help, but I can confirm that the same has happened to me so you're not alone...
I had the same problem. I couldn't even start twrp anymore. I fixed it by flashing the full tos118c rom from fastboot. After that I let the ota install. I then reinstalled twrp and flashed magisk to root the phone. Now it boots without dm verity or corrupt message. Even the play store is now certified, so I can install Netflix without problem.
Also you can hide root so you can use Android pay.
WileyFox customer support?
I have the exact same issue.
My device started off by saying:
The dm-verity is not started in enforcing mode and may not work properly
Now after the update, I get the error message saying that the phone is corrupt and will power off if I dont press power within 30 seconds.
I contacted WileyFox when the first issue occurred and was told that I needed to send the phone back. I sent on my details and never heard back.
Ideally I would like to get the phone sorted without flashing a custom rom or recovery.
Has anyone else had issues with their support? Is it just my case they are managing badly, or is it an ongoing thing?
jamesmcd05 said:
I have the exact same issue.
My device started off by saying:
The dm-verity is not started in enforcing mode and may not work properly
Now after the update, I get the error message saying that the phone is corrupt and will power off if I dont press power within 30 seconds.
I contacted WileyFox when the first issue occurred and was told that I needed to send the phone back. I sent on my details and never heard back.
Ideally I would like to get the phone sorted without flashing a custom rom or recovery.
Has anyone else had issues with their support? Is it just my case they are managing badly, or is it an ongoing thing?
Click to expand...
Click to collapse
You can try reflashing using fastboot. That fixed it for me.
Start the phone into fastboot mode.
If you don't have fastboot on your pc download and install this: https://forum.xda-developers.com/showthread.php?t=2317790
Download the fastboot image from https://forum.xda-developers.com/swift-2/how-to/marmite-android-7-1-1-tos118c-fastboot-t3605101
Connect your phone to the pc.
Flash the image using the following command: Fastboot update "path to the update zip"
That fixed the phone for me.
good luck!
RedNas74 said:
You can try reflashing using fastboot. That fixed it for me.
Start the phone into fastboot mode.
If you don't have fastboot on your pc download and install this: https://forum.xda-developers.com/showthread.php?t=2317790
Download the fastboot image from https://forum.xda-developers.com/swift-2/how-to/marmite-android-7-1-1-tos118c-fastboot-t3605101
Connect your phone to the pc.
Flash the image using the following command: Fastboot update "path to the update zip"
That fixed the phone for me.
good luck!
Click to expand...
Click to collapse
Brilliant, thanks.
Didn't realise there were offical wileyFox builds available.
Much appreciated. I will give that a try
:fingers-crossed:
EDIT:
I got an error saying that:
target reported max download size of 535822336 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
Also my phone was OEM locked.
I unlocked the device and tried again, but got the same error.
So I unzipped the contents and manually flashed each img,. which seems to have worked fine
I re-enabled OEM lock and now the phone boots without errors.
Thanks a million
Just wanted to say thank you very much for the thread info.
I also got the error messages, but realised that I was just being a bit hasty. Waiting a further 20 seconds gives a couple of other messages about other .sig files missing, but then the update continues and the flash is completed. The 'corrupted' and 'dm-verity' messages have now gone and the phone appears to be functioning properly.
Hopefully it will now update OTA to the next version and do so without corruption.
Thanks again
David
Wait a minute.
I'm a almost complete newbie but perhaps you guys can help me out.
Like davids-h I also got the errors and after over seven (!) minutes I get:
writing 'boot'...
FAILED (remote: Partition flashing is not allowed)
finished.
What can I do or should I do?
Thanks in advance!
I have the same issue as Razorblattor above - please could someone chime in with any suggestions. Would be appreciated. Thanks
rjl_12345 said:
I have the same issue as Razorblattor above - please could someone chime in with any suggestions. Would be appreciated. Thanks
Click to expand...
Click to collapse
Update: I managed to get the ROM flashed by removing the SD card and SIM. I have no idea why this would have been an issue but it was. I could then flash the ROM. Thanks
I was able to solve this issue with the following steps:
If not installed already install USB drivers (//dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip) and ADB (//dl.google.com/android/repository/platform-tools-latest-windows.zip). Unzip ADB
- enable USB debugging (under Developer options)
- connect phone to Windows machine, open a dos box and type 'adb devices' (you should see your WileyFox)
- enter the command: adb reboot "dm-verity enforcing" (incl. quotes)
Issue solved!
The steps documented by asg1977 have also worked for me.
I had the issue on a Swift2X that was delivered factory standard with a Nougat image. It occured while taking the phone out of its cover, pressing the power button in the process. After that the phone rebooted consistently with the corrupted warning. (Even tough the phone worked fine once past that screen.)
asg1977 said:
I was able to solve this issue with the following steps:
If not installed already install USB drivers (//dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip) and ADB (//dl.google.com/android/repository/platform-tools-latest-windows.zip). Unzip ADB
- enable USB debugging (under Developer options)
- connect phone to Windows machine, open a dos box and type 'adb devices' (you should see your WileyFox)
- enter the command: adb reboot "dm-verity enforcing" (incl. quotes)
Issue solved!
Click to expand...
Click to collapse
Thanks for this, but when I open a command prompt, and type in adb devices, I get a message saying that
'adb' is not recognized as an internal or external command,
operable program or batch file. I have developer options activated and usb mode is switched on and set to mtp devices. I have downloaded the 2 sets of files (USB drivers and ADB, and unzipped them to the desktop. Where am I going wrong?
EDIT - SOLVED IT! The command prompt needs to be opened inside the platform tools folder, whereupon it will find the phone, and the adb reboot "dm-verity enforcing" command will work. Prior to this, I had to revoke usb debugging authorisation between the phone and computer, then reconnect the phone the computer, so the phone could be seen by the computer. Command prompts can be very finicky about how they work, but I got there in the end.
RedNas74 said:
You can try reflashing using fastboot. That fixed it for me.
Start the phone into fastboot mode.
If you don't have fastboot on your pc download and install this: https://forum.xda-developers.com/showthread.php?t=2317790
Download the fastboot image from https://forum.xda-developers.com/swift-2/how-to/marmite-android-7-1-1-tos118c-fastboot-t3605101
Connect your phone to the pc.
Flash the image using the following command: Fastboot update "path to the update zip"
That fixed the phone for me.
good luck!
Click to expand...
Click to collapse
Hi sorry I have the same problem but I am new to all this, could someone send me a link to/write out a step by step instructions on how to do this?
Thanks in advance!
Louise
---------- Post added at 02:33 PM ---------- Previous post was at 02:06 PM ----------
louisew92 said:
Hi sorry I have the same problem but I am new to all this, could someone send me a link to/write out a step by step instructions on how to do this?
Thanks in advance!
Louise
Click to expand...
Click to collapse
Sorted now thanks!
I had the same issue and WF support fixed it for me
I had this issue previously when Wileyfox support was still active and they gave me this PDF file as a solution
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3LzW said:
I had this issue previously when Wileyfox support was still active and they gave me this PDF file as a solution
Click to expand...
Click to collapse
FTFY:
Something weird about posting links makes me fail posting the correct link: https:// imgur.com/a/NHjGV
asg1977 said:
I was able to solve this issue with the following steps:
If not installed already install USB drivers (//dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip) and ADB (//dl.google.com/android/repository/platform-tools-latest-windows.zip). Unzip ADB
- enable USB debugging (under Developer options)
- connect phone to Windows machine, open a dos box and type 'adb devices' (you should see your WileyFox)
- enter the command: adb reboot "dm-verity enforcing" (incl. quotes)
Issue solved!
Click to expand...
Click to collapse
Thanks from Poland, genius! It works
My phone has developed this problem after I flashed TWRP, I've tried to follow instructions so I can enforce the DM verity reboot in a command line interface but if I select fastboot my phone stays on a load up screen and doesn't change. The only other thing I can access is TWRP, will I be able to use the terminal in that to solve this problem?
asg1977 said:
I was able to solve this issue with the following steps:
If not installed already install USB drivers (//dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip) and ADB (//dl.google.com/android/repository/platform-tools-latest-windows.zip). Unzip ADB
- enable USB debugging (under Developer options)
- connect phone to Windows machine, open a dos box and type 'adb devices' (you should see your WileyFox)
- enter the command: adb reboot "dm-verity enforcing" (incl. quotes)
Issue solved!
Click to expand...
Click to collapse
I know this is old.. but just wanted to say I wasn't able to do this from my laptop via adb - but used the terminal via TWRP and it worked.
Thanks a lot from Wales

DID I BRICK MY P20 LITE?!

Hi everyone, I'm in need of some help ASAP. I unlocked my ANE-LX1 phone's bootloader so that I could root it, but things went wrong. My phone is stuck on TWRP logo screen (No TWRP menu, only logo) and my PC doesn't recognize it no matter what. I can only access the fastboot screen but it means nothing when you can't use ADB commands. I really don't know what to do, please help!
@-Alf- Hope that you'd help
soslusos said:
@-Alf- Hope that you'd help
Click to expand...
Click to collapse
Hi, try to explain what exactly happened, step by step.
soslusos said:
when you can't use ADB commands
Click to expand...
Click to collapse
For what reason?
-Alf- said:
Hi, try to explain what exactly happened, step by step.
For what reason?
Click to expand...
Click to collapse
Ok so I unlocked the bootloader, then I tried to root with Magisk by using adb but somehow it didn't work so I decided to install TWRP. I was on 9.1 but TWRP version was 9.0. I installed it and phone started to boot into TWRP only. PC recognized the phone but there were a bunch of folders with weird names. So I pressed on Format Data in TWRP but it didn't progress so I had to force-shut down my phone. Now PC doesn't recognize the phone at all. It's stuck on TWRP logo screen. Since my PC can't read the phone, I'm unable to use adb commands.
soslusos said:
Ok so I unlocked the bootloader, then I tried to root with Magisk by using adb but somehow it didn't work so I decided to install TWRP. I was on 9.1 but TWRP version was 9.0. I installed it and phone started to boot into TWRP only. PC recognized the phone but there were a bunch of folders with weird names. So I pressed on Format Data in TWRP but it didn't progress so I had to force-shut down my phone. Now PC doesn't recognize the phone at all. It's stuck on TWRP logo screen. Since my PC can't read the phone, I'm unable to use adb commands.
Click to expand...
Click to collapse
Format Data in incompatible TWRP? Really not good idea...
Okay, try the following:
- install on PC "Minimal ADB and fastboot" , open it, run command
fastboot devices <enter>
You'll get message 'waiting for any device'.
- Turn off the phone, hold Volume Down and connect to PC. Post the result.
What is region? (Cxxx)
-Alf- said:
Format Data in incompatible TWRP? Really not good idea...
Okay, try the following:
- install on PC "Minimal ADB and fastboot" , open it, run command
fastboot devices <enter>
You'll get message 'waiting for any device'.
- Turn off the phone, hold Volume Down and connect to PC. Post the result.
What is region? (Cxxx)
Click to expand...
Click to collapse
First of all, thank you man. It was suggested by someone on XDA, I shouldn't have done it.
I think the regional code is C121, I bought it in Turkey.
The thing is my phone doesn't turn off. Even when I force it by holding the button, it just turns back on. It stays like that until the battery dies.
I can open the fastboot screen by holding the vol down button and it says:
ap_s_abnormal 64
phone unlocked
frp unlocked
Have you tried connect to PC, then press and hold Power + Vol Down for 10-12 sec?
soslusos said:
It was suggested by someone on XDA
Click to expand...
Click to collapse
I bet I know who it was
Yeah I tried that, it just opens fastboot mode after phone restarts.
soslusos said:
Yeah I tried that, it just opens fastboot mode after phone restarts.
Click to expand...
Click to collapse
Game over . Test point method & board SW or DC-Phenix is your friend (maybe...). Unfortunately, I can't help you with this, I've never done it.
Damn. I don't even know what they are Can customer services do anything with this? I guess I'll have to pay.
soslusos said:
Can customer services do anything with this?
Click to expand...
Click to collapse
I guess so. It's all a matter of money .
Haha yeah but some stuff you do on your phone might be irreversible, that's what I'm afraid of.
So do you actually know what caused my device to boot into TWRP menu only? Is it because TWRP is incompatible with Android 9.1? (Or is it?)
soslusos said:
some stuff you do on your phone might be irreversible
Click to expand...
Click to collapse
Yes, e.g. damaged motherboard...
soslusos said:
So do you actually know what caused my device to boot into TWRP menu only? Is it because TWRP is incompatible with Android 9.1? (
Click to expand...
Click to collapse
Of course I cannot say that for sure. But I can say for sure that doing 'data format' (running stock EMUI) on some TWRP 3.4. and above can brick Kirin 659 device.
@-Alf- Hey, my phone is finally fixed. Do you know what's the latest firmware for 9.1 and where to download it? I'll install that one after rooting my phone.
soslusos said:
what's the latest firmware for 9.1
Click to expand...
Click to collapse
Hi, .401 (for C432 region)
soslusos said:
where to download it?
Click to expand...
Click to collapse
via OTA update
soslusos said:
I'll install that one after rooting my phone.
Click to expand...
Click to collapse
I would suggest updating first and then root
OTA says 9.1.0.208 is the latest version but I highly doubt that, something must be wrong with this ROM because the customer service guy installed it. My phone is C121 by the way.
soslusos said:
OTA says 9.1.0.208 is the latest version but I highly doubt that, something must be wrong with this ROM because the customer service guy installed it. My phone is C121 by the way.
Click to expand...
Click to collapse
Try to update via HiSuite or using option "Download latest version etc." in eRecovery. Maybe .208 is really the latest version for regional variant C121, idk...
-Alf- said:
Try to update via HiSuite or using option "Download latest version etc." in eRecovery. Maybe .208 is really the latest version for regional variant C121, idk...
Click to expand...
Click to collapse
So I was gonna roll back to EMUI 8 to unlock the bootloader but this time there's no "Switch to previous versions" option... In phone settings it says LGRP_OVS 9.1.0.208, is that the cause? How am I gonna unlock the bootloader now? So confused, I don't want to mess things up this time
soslusos said:
LGRP_OVS 9.1.0.208, is that the cause?
Click to expand...
Click to collapse
Yes, it is. Incompatible or incomplete FW .
In fastboot mode run commands :
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
Some might fail, so don't worry about it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Categories

Resources