Related
Hi all,
I'm new to this, so please be gentle (ie I'm a bit slow)
After getting completely frustrated at the lenght of time to get the UK Honeycomb update from Motorola I've decided to take the plunge and flash the US version.
I've floowed all the instructions on downloading SDK, the USB drivers, the US images and I've successfully unlocked my Xoom.
However, when I type the instruction 'fastboot flash boot boot.img' I get the following error message - "error: cannot load boot.img"
The i got the US HWI69 files from Moto and saved them in the SDK\..Platform-Tools folder. That's also the same folder the file path in System Properties' points to - so I can't understand why its not recognising the file?
Can anyone out there help? As I say I'm pretty new to this, so may need a bit of coaching...
The steps I'm following are:
adb reboot bootloader
fastboot oem unlock
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot reboot
As I say, I've performed the unlock, just unable to go any further. If I connect to my pc and type adb devices, it finds the xoom ok..
I have read someithng about opening command prompt in the platforms-tools folder, but I'm unclear how to do this or if this is the problem?
dhawkes said:
The steps I'm following are:
adb reboot bootloader
fastboot oem unlock
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot reboot
As I say, I've performed the unlock, just unable to go any further. If I connect to my pc and type adb devices, it finds the xoom ok..
I have read someithng about opening command prompt in the platforms-tools folder, but I'm unclear how to do this or if this is the problem?
Click to expand...
Click to collapse
to open the command window in a folder, shift and right click in the folder and click on open command window here... (windows 7)
ed.dark said:
to open the command window in a folder, shift and right click in the folder and click on open command window here... (windows 7)
Click to expand...
Click to collapse
could be
or try redownloading the US images as they might be a bit corrupt?
ed.dark said:
to open the command window in a folder, shift and right click in the folder and click on open command window here... (windows 7)
Click to expand...
Click to collapse
Sorry if I'm being a tool, but holding down shift and right clicking in the folder does not give me an option to open a command window? In fact holding shift down doesn't seem to have an effect - just the usual right click menu?
I'm using XP Media Center version, service pack 3 if that helps?
Am i missing something really obvious? (Probably )
I'll try downloading the images again..
Its only for windows 7. download xp power toys for the addon for xp
http://go.microsoft.com/fwlink/?LinkId=211471
Hey, ed.dark (and Lothaen) Thanks for taking the time to read and answer my query. I'm delighted to say once the power toys were installed it was all plain sailing.
3.1 has just been picked up and is installing and I'm over the moon.
Thanks guys!
I have flashed a new rom on my lg540gt and after that the android logo stays forever.
When I tryed to reflash another rom,the LG logo stays.
Tryed to go to fastboot but the phone will not comunnicate with the computer.
Thx for any help
restart you pc and try fastboot again
Tryed but it didn't work,I have tryed it on another PC and without success
darac32 said:
I have flashed a new rom on my lg540gt and after that the android logo stays forever.
When I tryed to reflash another rom,the LG logo stays.
Tryed to go to fastboot but the phone will not comunnicate with the computer.
Thx for any help
Click to expand...
Click to collapse
bro this question was answered heaps of times..
search before posting..
Also this is supposed to be in the general section not
development..
Anyways go into clockworkmod if you can't connect to
pc and wipe everything and reflash with Recovery.
there was a post of how to make fastboot recognizr your device
but i forgot because fastboot works fine on linux
maybe if you find
cccb010 said:
there was a post of how to make fastboot recognizr your device
but i forgot because fastboot works fine on linux
maybe if you find
Click to expand...
Click to collapse
yeah i think i saw it as well..
forgot though..
Try the recovery, i had this problem as well!!
uninstall all drivers and reinstall them..
After that go to fastboot and type
fastboot -w
fastboot reboot
Press Power+Volume key to access download mode. Computer will now recognize your GT540.
Reflash .kdz
*fastboot enabled
After that is done, when phone automatically reboot, press Power+Camera till phone stays on black screen.
Open up CMD and run with administrator's rights>*make sure USB is connected
Type in;
cd c:/<location>
Fastboot -w
No more boot loops afterwards
MrAndroid12 said:
Press Power+Volume key to access download mode. Computer will now recognize your GT540.
Reflash .kdz
*fastboot enabled
After that is done, when phone automatically reboot, press Power+Camera till phone stays on black screen.
Open up CMD and run with administrator's rights>*make sure USB is connected
Type in;
cd c:/<location>
Fastboot -w
No more boot loops afterwards
Click to expand...
Click to collapse
I have made this,but the phone gives me a blue screen with "fastboot" ...
Tryed to reflash with original,and fastboot rom but the effect is the same ...
and i have the fasboot in command prompt ...
I can not get to recovery ...
I have win ,and on another xp ...
thx for any help
flash another recovery via fastboot
darac32 said:
I have made this,but the phone gives me a blue screen with "fastboot" ...
Tryed to reflash with original,and fastboot rom but the effect is the same ...
and i have the fasboot in command prompt ...
I can not get to recovery ...
I have win ,and on another xp ...
thx for any help
Click to expand...
Click to collapse
Hold the HOME button along with the POWER button while turning on your phone. You should encounter recovery at some point. If not, flash a recovery rom by typing:
Code:
fastboot flash recovery <image_name>
Replace <image_name>, with the recovery image and remove the brackets.
So for example:
Code:
fastboot flash recovery recovery.img
jhonnyx1000 said:
Hold the HOME button along with the POWER button while turning on your phone. You should encounter recovery at some point. If not, flash a recovery rom by typing:
Code:
fastboot flash recovery <image_name>
Replace <image_name>, with the recovery image and remove the brackets.
So for example:
Code:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
THe command prompt says <waiting for device> and stands here
btw. the screen is blue when i press home +power or camera + power and it says
"Display initialized
USB init ept @ 0x6b000
fatstboot_init()
udc_start() "
darac32 said:
THe command prompt says <waiting for device> and stands here
btw. the screen is blue when i press home +power or camera + power and it says
"Display initialized
USB init ept @ 0x6b000
fatstboot_init()
udc_start() "
Click to expand...
Click to collapse
The 'display initialize' thing is a part of fastboot. Do the commands when you're in fastboot.
Sent from my GT540 using XDA App
er dudes remember that the blue screen and white text is only there if you use mur4ik's bootloaders and not the one you get from the kdz
If you have blue screen its not dead
sudo ./fastboot -w
sudo ./fastboot flash boot boot.img
sudo ./fastboot flash system system.img
sudo ./fastboot flash recovery recovery.img
Maybe its your adb server cant remember the exact command but its something like
sudo ./adb kill-server
sudo ./adb server
Or something along those lines look it up on google its the command to restart the adb server if you use more than one device or do alot of work with adb sometimes it will show it cant connect to the phone when really it can it just needs to be rest because something has screwed up on the system and or phone.
Hope this helps and good luck if you still have problems give us a few more details and what happend where but your gt540 is nowhere near broke trust me.
Sent from my tf101 using xda premium 1.54Ghz
Danzano said:
If you have blue screen its not dead
sudo ./fastboot -w
sudo ./fastboot flash boot boot.img
sudo ./fastboot flash system system.img
sudo ./fastboot flash recovery recovery.img
Maybe its your adb server cant remember the exact command but its something like
sudo ./adb kill-server
sudo ./adb server
Or something along those lines look it up on google its the command to restart the adb server if you use more than one device or do alot of work with adb sometimes it will show it cant connect to the phone when really it can it just needs to be rest because something has screwed up on the system and or phone.
Hope this helps and good luck if you still have problems give us a few more details and what happend where but your gt540 is nowhere near broke trust me.
Sent from my tf101 using xda premium 1.54Ghz
Click to expand...
Click to collapse
You think that I should reinstal the adb server (or the complete adb with sdk)
Killed the server,and startet it again,but with no response from phone ...
I have reflashed the phone with V20D,and now it stucks on android logo ...
The fastboot is still not working
darac32 said:
You think that I should reinstal the adb server (or the complete adb with sdk)
Killed the server,and startet it again,but with no response from phone ...
I have reflashed the phone with V20D,and now it stucks on android logo ...
The fastboot is still not working
Click to expand...
Click to collapse
reinstall LG drivers or whatever drivers needed for our phone and try fastboot again .
Fast boot drivers are missing from your computer, Vernica's pinned post with lots of guides will point you in the correct direction.
Sent from my GT-I9100 using XDA Premium
airbus360 said:
Fast boot drivers are missing from your computer, Vernica's pinned post with lots of guides will point you in the correct direction.
Sent from my GT-I9100 using XDA Premium
Click to expand...
Click to collapse
From what you just said airbus is right
do you use windows or linux because windows uses drivers but linux you will have to set rules for the phone
Sent from my tf101 using xda premium 1.54Ghz
Danzano said:
From what you just said airbus is right
do you use windows or linux because windows uses drivers but linux you will have to set rules for the phone
Sent from my tf101 using xda premium 1.54Ghz
Click to expand...
Click to collapse
I use Windows 7,but windows xp is no problem
mircea89fzr said:
reinstall LG drivers or whatever drivers needed for our phone and try fastboot again .
Click to expand...
Click to collapse
Tryed that but no response from phone,that is what makes my troubles ...
Everything rechecked twice ... but maybe somthing I miss but I don't think I did
hi,
trying to flash the breadcrust recovery using my linux pc, but the Z1 doesn't appear in the list of devices when running adb devices. Image attached. Normally I would get a request to accept the RSA key for a trusted pc when enabling usb debug. But I don't get this option.
- Adb tools are loaded and working on my linux laptop
- My nexus 7 responds to ADB devices and shows up ok
- tried on wifes windows laptop with adb/sdk tools loaded and no joy there too
- i have developer USB debug options enabled, i've tripple checked this
could it be the cable? I'm using the one which came with the phone, so that should be ok?!!
cheers
SOLUTION - I ran this One Plus Two script modified with the Z1 device ID and now I can see my device in adb devices and interact with it. I get the SHA screen to allow access and can run commands from linux terminal. YAY!
See the attachments for script.
I think it´s a driver fault. Did u install them in windows?
im using linux, i dont get any rsa pop up confirmation either!
EggZenBeanz said:
im using linux, i dont get any rsa pop up confirmation either!
Click to expand...
Click to collapse
and that was the reason, why i installed windows last night. as long you dont get rsa pop up, the device will not listed (i think so)
EggZenBeanz said:
im using linux, i dont get any rsa pop up confirmation either!
Click to expand...
Click to collapse
But u said, that u tried ur wifes Windows notebook. Did u install the drivers there?
ADB doesn't work for me, too. I work around this problem by booting into recovery (simultaneously press Vol+ and Vol- and Power until phone vibrates) and choose "Boot to bootloader" from there. After rooting I installed "Power Toggles" from Play Store and use the toggle to reboot to recovery or bootloader.
By the way, when I boot into recovery, I'm able to ADB sideload. So I don't think there's a driver issue.
MKKLR21 said:
ADB doesn't work for me, too. I work around this problem by booting into recovery (simultaneously press Vol+ and Vol- and Power until phone vibrates) and choose "Boot to bootloader" from there. After rooting I installed "Power Toggles" from Play Store and use the toggle to reboot to recovery or bootloader.
By the way, when I boot into recovery, I'm able to ADB sideload. So I don't think there's a driver issue.
Click to expand...
Click to collapse
Good tip - I'll give it a go.
My nexus 7 works as expected on all PCs and laptops Linux/windows so it must be the phone
Sent from my Nexus 7 using Tapatalk
Maybe sudo or check this:
http://1.bp.blogspot.com/-rDdBnJTh870/U-hxVzxMf3I/AAAAAAAAKwQ/WrZkaMjaReo/s1600/Unlock-Bootloader-linux-terminal-xperia-z.png[img/]
Source: [url]http://linuxwelt.blogspot.de/2014/08/cyanogenmod-unter-linux-installieren.html[/url]
ok some progress.....
got the trusted device RSA screen to appear on my wifes windows pc. i could then run adb devices and see the device.
I could run adb reboot bootloader, but the device doesn't boot into fastboot, just reboots as normal!
I could also hold down up/down volume buttons and get into the bootloader, but again the device isn't picked by any fastboot oem checks for unlocking!!
arrrgh!!!
You'll have to add -i switch followed by the device ID to your fastboot command. I don't have it at hand, so just read the TWRP thread.
ok! Some progress...ish.
running "adb reboot bootloader"command in windows worked when I switched Cyanogen recovery updates off in developer options. The Z1 reboots into bootloader.
Running "fastboot -i 0x2b4c oem get-device-info" returns nothing just "....."
So I tried "fastboot -i 0x2b4c oem unlock" an error returns cannot unlock use command "fastboot -i 0x2b4c oem unlock-go" which works. The phone wipes data and reboots back into OS.
I re-enable the developer options and adb debug. and reboot into bootloader
Run "fastboot -i 0x2b4c flash recovery z1.twrp.2.8.7.0.By.Breadcrust-UPDATE3.img" - some time stats are retunred and OKAY message. But when I boot into recovery it's still the cyanogen stock recovery. not TWRP.
weird!
Your commands are simply wrong, thats why they don´t work.
It is:
fastboot -i 0x2b4c oem device-info
fastboot -i 0x2b4c oem unlock-go
Run "fastboot -i 0x2b4c flash recovery z1.twrp.2.8.7.0.By.Breadcrust-UPDATE3.img" - some time stats are retunred and OKAY message. But when I boot into recovery it's still the cyanogen stock recovery. not TWRP.
Click to expand...
Click to collapse
Flashing does NOT work on the international version, you have to boot into it directly from fastboot.
fastboot -i 0x2b4c boot z1.twrp.2.8.7.0.By.Breadcrust-UPDATE3.img
Should be correct instead of the flash command.
EggZenBeanz said:
ok some progress.....
got the trusted device RSA screen to appear on my wifes windows pc. i could then run adb devices and see the device.
I could run adb reboot bootloader...
...
Click to expand...
Click to collapse
What made the change? I was able to see the RSA screen only once, but after device restored to defaults I can't get it back. same drivers installed, and it appears in the device manager.
I honestly don't know, it just worked after many attempts. I read somewhere about USB 3 ports with Linux so might be the same for windows?
Sent from my Z1 using Tapatalk
It's an USB 3.0 issue. Plug the phone into an USB 2.0 port, or an USB 2.0 hub plugged into an USB 3.0 port and it will magically start working. God knows why this is the case...
Ironically, fastboot works fine even on USB 3.0...
For to be able to boot (not flash) the TWRP recovery you shouldn't need to unlock bootloader. Am I right?
Planet X said:
For to be able to boot (not flash) the TWRP recovery you shouldn't need to unlock bootloader. Am I right?
Click to expand...
Click to collapse
Booting should work.
At least it worked fine on other fastboot capable devices I've had in the past.
MrColdbird said:
Booting should work.
At least it worked fine on other fastboot capable devices I've had in the past.
Click to expand...
Click to collapse
Okay, I have found out that it is impossible to boot from TWRP as log as the bootloader is locked. It just took me 2 hours to setup my phone again after unlock.
Have a look at this thread, I am going to give it a try later.
http://forum.xda-developers.com/showthread.php?t=2408802
This did the trick on Linux (Ubuntu):
- run on terminal "sudo gedit ~/.android/adb_usb.ini"
- put "0x2b4c" in
- run on terminal "adb kill-server" and "adb start-server"
And run the fastboot commands with "sudo".
I restarted my phone this evening, and when it booted up I got a "decryption unsuccessful" message. When that happens it appears my only option is to flash a factory image. So I download the most recent image, and when I get into the bootloader I see no option for fastboot.
When I'm in TWRP (3.0.2-0) I can see my phone listed in recovery or sideload when I run "adb devices" from my computer, but no devices are listed when the command is run while on the main bootloader screen.
Not sure if it matters at this point, but I had the 20160821 Pure Nexus build installed when this happened.
How do I get my phone into fastboot mode so I can flash the factory image?
Thanks so much for your help.
It sounds like you may not have the latest drivers for the Android SDK or ADB toolkit.
RonaldusMagnus said:
I restarted my phone this evening, and when it booted up I got a "decryption unsuccessful" message. When that happens it appears my only option is to flash a factory image. So I download the most recent image, and when I get into the bootloader I see no option for fastboot.
When I'm in TWRP (3.0.2-0) I can see my phone listed in recovery or sideload when I run "adb devices" from my computer, but no devices are listed when the command is run while on the main bootloader screen.
Not sure if it matters at this point, but I had the 20160821 Pure Nexus build installed when this happened.
How do I get my phone into fastboot mode so I can flash the factory image?
Thanks so much for your help.
Click to expand...
Click to collapse
When you are in bootloader, you can use fastboot commands.
RonaldusMagnus said:
I restarted my phone this evening, and when it booted up I got a "decryption unsuccessful" message. When that happens it appears my only option is to flash a factory image. So I download the most recent image, and when I get into the bootloader I see no option for fastboot.
When I'm in TWRP (3.0.2-0) I can see my phone listed in recovery or sideload when I run "adb devices" from my computer, but no devices are listed when the command is run while on the main bootloader screen.
Not sure if it matters at this point, but I had the 20160821 Pure Nexus build installed when this happened.
How do I get my phone into fastboot mode so I can flash the factory image?
Thanks so much for your help.
Click to expand...
Click to collapse
Not sure what you're talking about. Turn the phone off. Hold vol down + power, to boot into the bootloader / fastboot.
Run the fastboot devices command, and you should see your device. That's where you can flash your system images.
JustPlayingHard said:
When you are in bootloader, you can use fastboot commands.
Click to expand...
Click to collapse
So, if I'm at the bootloader's main screen, I should be able to see my device when I run the command "adb fastboot devices", right? Cuz that's not happening. Also, when I use the volume rocker to see the available options fastboot isn't listed.
When I go into recovery from the bootloader and run the command "adb devices" I see my device listed with "recovery" next to it. When I launch ADB sideload from TWRP, I also see my device listed with "sideload" next to it.
So, I can run fastboot commands when I'm in the bootloader even if "adb fastboot devices" returns nothing?
RonaldusMagnus said:
So, if I'm at the bootloader's main screen, I should be able to see my device when I run the command "adb fastboot devices", right? Cuz that's not happening. Also, when I use the volume rocker to see the available options fastboot isn't listed.
When I go into recovery from the bootloader and run the command "adb devices" I see my device listed with "recovery" next to it. When I launch ADB sideload from TWRP, I also see my device listed with "sideload" next to it.
So, I can run fastboot commands when I'm in the bootloader even if "adb fastboot devices" returns nothing?
Click to expand...
Click to collapse
It's not adb fastboot.. It's just fastboot.
teh roxxorz said:
Not sure what you're talking about. Turn the phone off. Hold vol down + power, to boot into the bootloader / fastboot.
Run the fastboot devices command, and you should see your device. That's where you can flash your system images.
Click to expand...
Click to collapse
The problem I have is that when I'm in the bootloader (at the screen with the android robot on its back) and use the volume rocker to see the available options, fastboot isn't listed as an option to select.
Sent from my FIND7 using XDA-Developers mobile app
RonaldusMagnus said:
The problem I have is that when I'm in the bootloader (at the screen with the android robot on its back) and use the volume rocker to see the available options, fastboot isn't listed as an option to select.
Sent from my FIND7 using XDA-Developers mobile app
Click to expand...
Click to collapse
It's literally, stay in bootloader
type: "fastboot devices" and you should see your device.
JustPlayingHard said:
It's literally, stay in bootloader
type: "fastboot devices" and you should see your device.
Click to expand...
Click to collapse
Thanks. I'll do as you said and report back. Maybe what I'm doing wrong is recalling the bootloader unlock procedures where "adb" precedes some of the commands when executing them from the Windows command prompt.
Just to be ridiculously clear it's:
1. While unplugged, Power + Volume Down to enter the bootloader.
2. Once in the bootloader connect USB cable.
3. Navigate to the SDK platform-tools folder, and from the Windows command prompt execute "fastboot devices". Then I should see my device listed.
Sorry if I'm being dense.
RonaldusMagnus said:
Thanks. I'll do as you said and report back. Maybe what I'm doing wrong is recalling the bootloader unlock procedures where "adb" precedes some of the commands when executing them from the Windows command prompt.
Just to be ridiculously clear it's:
1. While unplugged, Power + Volume Down to enter the bootloader.
2. Once in the bootloader connect USB cable.
3. Navigate to the SDK platform-tools folder, and from the Windows command prompt execute "fastboot devices". Then I should see my device listed.
Sorry if I'm being dense.
Click to expand...
Click to collapse
No worries, it's probably me that's being dense.
That should work fine
RonaldusMagnus said:
Thanks. I'll do as you said and report back. Maybe what I'm doing wrong is recalling the bootloader unlock procedures where "adb" precedes some of the commands when executing them from the Windows command prompt.
Just to be ridiculously clear it's:
1. While unplugged, Power + Volume Down to enter the bootloader.
2. Once in the bootloader connect USB cable.
3. Navigate to the SDK platform-tools folder, and from the Windows command prompt execute "fastboot devices". Then I should see my device listed.
Sorry if I'm being dense.
Click to expand...
Click to collapse
or plug your phone in (while its booted normally, into its OS)
type: adb reboot bootloader
once phone reboots to bootloader, type: fastboot devices
He must have came from a HTC bc he's looking for the option Fastboot in Bootloader.
Sent from my Nexus 6P using Tapatalk
Thanks for your help everyone. I'm back up and running now. My problems stemmed from a misunderstanding that once in the bootloader I'm already able to execute fastboot commands and didn't need to select a fastboot option from the bootloader. And I had a misunderstood how to execute the fastboot commands from the command prompt.
Many thanks to everyone setting me straight!
Hello, I was curious if anyone could help me with unbricking my phone, my phone has no custom recovery installed, the bootloader is apparently unlocked (OEM unlocking is disabled), FRP lock is enabled, I cannot flash anything (Command not allowed), relock bootloader (Root type is at risk), Unlock bootloader (Command not allowed), any help would be appreciated.
Edit: I also cannot boot a from a recovery img locally using fastboot (Command not allowed)
EDIT: Fixed it using DC Pheonix and flashing VNS-L22C636B140 OEMINFO and flashing B160
Hi, try my way. https://forum.xda-developers.com/showpost.php?p=77307223&postcount=30 Just pick CxxxBxxx that suits your model. Try to unlock bootloader again via SRKTool, I think FRP must be unlocked too...
Check this also: https://forum.xda-developers.com/huawei-p9lite/help/p9-lite-bricked-please-help-t3415275
4uvak91 said:
Hi, try my way. https://forum.xda-developers.com/showpost.php?p=77307223&postcount=30 Just pick CxxxBxxx that suits your model. Try to unlock bootloader again via SRKTool, I think FRP must be unlocked too...
Check this also: https://forum.xda-developers.com/huawei-p9lite/help/p9-lite-bricked-please-help-t3415275
Click to expand...
Click to collapse
I cannot flash anything, so any of these do not help, thanks for trying I guess
wheellzzz said:
I cannot flash anything, so any of these do not help, thanks for trying I guess
Click to expand...
Click to collapse
Are you sure you run from inside the folder where adb.exe and fastboot.exe is? Boot to bootloader and use terminal pointed to fastboot.exe. Shift+right click -> open command line here. Make sure your devices is listed: adb devices. If device is shown: adb reboot bootloader, to reboot to bootloader. If not, install adb drivers / huawei drivers.
4uvak91 said:
Are you sure you run from inside the folder where adb.exe and fastboot.exe is? Boot to bootloader and use terminal pointed to fastboot.exe. Shift+right click -> open command line here. Make sure your devices is listed: adb devices. If device is shown: adb reboot bootloader, to reboot to bootloader. If not, install adb drivers / huawei drivers.
Click to expand...
Click to collapse
Yes I am sure, also, I have no way to access ADB since there is no recovery on the phone.
Only thing I can do is boot to that eRecovery screen with the option to download, reboot or shutdown. (Automatticly goes to here), or boot to bootloader
wheellzzz said:
Yes I am sure, also, I have no way to access ADB since there is no recovery on the phone.
Only thing I can do is boot to that eRecovery screen with the option to download, reboot or shutdown. (Automatticly goes to here), or boot to bootloader
Click to expand...
Click to collapse
Well if you can access to bootloader then you able to use fastboot commands. ADB is not related to recovery anyhow, you use windows command prompt to use adb and fastboot. IF FRP is locked, unlock bootloader again. I quiet don't understand how the command are not allowed or so. You are definitely doing something wrong.
4uvak91 said:
Well if you can access to bootloader then you able to use fastboot commands. ADB is not related to recovery anyhow, you use windows command prompt to use adb and fastboot. IF FRP is locked, unlock bootloader again. I quiet don't understand how the command are not allowed or so. You are definitely doing something wrong.
Click to expand...
Click to collapse
The problem is I cannot unlock bootloader again, flash anything or boot into any image in fastboot mode, I always get "ERROR: (Command not allowed)", attempting to relock the bootloader shows "ERROR: (Root type is at risk)"
EDIT: I have done some research for the dload method, If I want to dload to hopefully fix it, I'll need VNS-L22C636B381, but the official link from the hicloud is dead, if anyone could help me with that, that'd be great.
Last EDIT: Ended up scratching the above idea as it didn't work, gritted my teeth as I bought DC Phoenix and will update if it works out with the .APP from the latest package I found on firmware finder.