As the title indicates I am currently in the process of rooting my LG V60 Verizon Variant. However, I am running into a issue when using QFIL.
I am following the V60 Bootloader Unlock and Magisk Root by crimsonrommer: https://forum.xda-developers.com/t/v60-bootloader-unlock-and-magisk-root.4358785/
Here is steps 1-5 from the guide:
If you already have it unhidden go to Developer Options under Settings -> System and enable OEM Unlock as well as USB Debugging. If you don't see Developer Options go to Settings => System => About Phone => Software Information and tap Build Number until it either asks you for your password or says you are a developer at the bottom. Verizon Users: You will not see the oem unlock option, we will fix this later in this guide.
Get it into 9008 Mode: (This may take several tries)
Make sure you are connected to your computer via USB.
Hold Volume Down and Power until it shuts off
Now here's the tricky part, as soon as the screen turns off, immediately start tapping volume up quickly, but do not let go of volume down and power, if you did it successfully you will see your screen is off but it appears either in Device Manager or Windows plays the Device Connected sound.
Open and Configure QFIL as shown below:
{
"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"
}
4. After that click Browse and select the Firehose you downloaded earlier
5. Next go to the Tools menu at the top then select Partition Manager (If this errors please reboot back into edl using the steps mentioned above!)
All of the previous steps have been followed to my knowledge. Below is a video link showing what happens when I try to access the partition manager:
2023-05-30 23-18-39.mkv
drive.google.com
Any help is greatly appreciated as I am willing to provide any information needed.
reinstall qdil and drivers
change usb cable or usb port
7henoble1 said:
As the title indicates I am currently in the process of rooting my LG V60 Verizon Variant. However, I am running into a issue when using QFIL.
I am following the V60 Bootloader Unlock and Magisk Root by crimsonrommer: https://forum.xda-developers.com/t/v60-bootloader-unlock-and-magisk-root.4358785/
Here is steps 1-5 from the guide:
If you already have it unhidden go to Developer Options under Settings -> System and enable OEM Unlock as well as USB Debugging. If you don't see Developer Options go to Settings => System => About Phone => Software Information and tap Build Number until it either asks you for your password or says you are a developer at the bottom. Verizon Users: You will not see the oem unlock option, we will fix this later in this guide.
Get it into 9008 Mode: (This may take several tries)
Make sure you are connected to your computer via USB.
Hold Volume Down and Power until it shuts off
Now here's the tricky part, as soon as the screen turns off, immediately start tapping volume up quickly, but do not let go of volume down and power, if you did it successfully you will see your screen is off but it appears either in Device Manager or Windows plays the Device Connected sound.
Open and Configure QFIL as shown below:
4. After that click Browse and select the Firehose you downloaded earlier
5. Next go to the Tools menu at the top then select Partition Manager (If this errors please reboot back into edl using the steps mentioned above!)
All of the previous steps have been followed to my knowledge. Below is a video link showing what happens when I try to access the partition manager:
2023-05-30 23-18-39.mkv
drive.google.com
Any help is greatly appreciated as I am willing to provide any information needed.
Click to expand...
Click to collapse
Uncheck use Verbose and use this firehose!
JigsawMobile said:
reinstall qdil and drivers
change usb cable or usb port
Click to expand...
Click to collapse
It's the firehose some are using jigsaw for some reason.I have sent mine to a few already...lol...
Surgemanxx said:
It's the firehose some are using jigsaw for some reason.I have sent mine to a few already...lol...
Click to expand...
Click to collapse
we have two varsions firehouse ?
JigsawMobile said:
we have two varsions firehouse ?
Click to expand...
Click to collapse
Brother,I have seen 3 different ones.I haven't scaled through the different ones I have,but some will work fine with certain variants and some won't.The one I posted works with just about all variants with no issues.I do have another one,and it fails the handshake everytime with my U.S. variants.
Related
Hello,
I would like to root my Z5C, but I can't load the phone in fastboot mode.
I tried the following :
adb reboot bootloader (with my phone one, with usb debug)
the phone shut down completely, but nothing is displayed on the screen
power up + volume up (from my phone shutdowned)
there are three vibrations, and sometimes the logo Xperia appears for a few second, but then the screen show the charging icon
power down + plug usb (from my phone shutdowned)
nothing appends
each time, I tried the following command to check if the phone was indeed in fastboot mode :
fastboot devices
but I get nothing (empty list).
Could you help me please?
thanks in advance.
As far as I know, only the led will light up. The display stays black. Have you looked in the device manager if your device is recognized there. Maybe as an unknown device etc?
then I probably don't have the correct driver. I installed this one
developer.sonymobile.com/downloads/drivers/xperia-z5-compact-driver
Do you know where I can find the correct driver?
In device manager, I see a new item when I plug my phone :
USB mass storage device
I tried to update the driver with the one mentioned before, but it says that it is already up to date.
Noneangel said:
Hello,
I would like to root my Z5C, but I can't load the phone in fastboot mode.
I tried the following :
adb reboot bootloader (with my phone one, with usb debug)
the phone shut down completely, but nothing is displayed on the screen
power up + volume up (from my phone shutdowned)
there are three vibrations, and sometimes the logo Xperia appears for a few second, but then the screen show the charging icon
power down + plug usb (from my phone shutdowned)
nothing appends
each time, I tried the following command to check if the phone was indeed in fastboot mode :
fastboot devices
but I get nothing (empty list).
Could you help me please?
thanks in advance.
Click to expand...
Click to collapse
You've got some commands wrong. Volume up plus power is hard reset. You get 3 vibrations then phone is off.
To get into fastboot mode or flash mode you do not use power button and phone needs to be off. Simply hold volume up and plug in USB for fastboot mode, or hold volume down plus plug in USB for flash mode. Blue LED for fastboot and green LED for flash mode.
This is the best option for install and drivers: http://forum.xda-developers.com/showthread.php?p=48915118
I became a lot more understandable, thanks you.
I tried to install android driver from the topic you suggested (I know I should post in this topic, but I have not enough privileges to do so), but I have the following issue :
after the installation of the drivers, I followed the howto_driver.zip (the device is not recognized), and in step 5, I don't see the "android device" driver.
As suggested by
If you have problem with driver enumeration in Windows 8.1 install update KB2917929
Click to expand...
Click to collapse
I tried to install KB2917929 but during the installation I got
The update is not applicable for this computererror. After a bit of googleing, I found this
answers.microsoft.com/en-us/windows/forum/windows_8-update/instalation-failure-for-kb2917929/9ebb0567-8923-4f13-8840-61dbe54212e5
Hi ,
The Best Thing To Install KB2917929 Is To Remove The KB2919355 Update
To remove the update, follow these methods:
Press Windows Key + X.
Click on Programs and Features.
Click on View installed updates on the left hand side.
Find the update KB2919355, right click on it and Uninstall.
After That Re Install The KB2917929 Update And It Will Be Installed
Click to expand...
Click to collapse
But when I tried to uninstal KB2919355 I got this error :
An error has occurred. Not all of the updates were successfully uninstalledI gave up and tried to install the usb driver from a folder. I downloaded the following driver : developer.android.com/studio/run/win-usb.html
but when I tried to update the driver, I get a message error saying
windows could not find driver software for your device.I run out of option (I might try this with linux, but I have no machine running under linux right now).
try forcing install of the driver by selecting the unknow device/detected phone and update/install driver by "find software driver in pc" then "choose manually driver from a driver list" then "driver disk" button on the right, "explore" and go the folder and select the downloaded driver. Be sure to install the correct driver described in the guides.
I get the following after selecting the "driver disk" :
{
"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 suppose that by explore you mean Have disk.
I tried to select the usb driver directory, and I get the following error :
The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systemThe folder I selected is the unzip of the driver from developer.android.com/studio/run/win-usb.html
I'm not much help with Windows, I'm still running XP lol
civicsr2cool said:
I'm not much help with Windows, I'm still running XP lol
Click to expand...
Click to collapse
LOL kinda old school these days :cyclops:
I can not be held responsible if you do not follow the instructions and your phone explodes in your face, you get wings and fly, your microsd smoke etc. EVERY PROCEDURE YOU MAKE ON YOUR PHONE IS ONLY YOUR RESPONSIBILITY.
{
"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"
}
As you notice, this process also enables fastboot commands.
This is a step-by-step tutorial to get the Brick phone
I leave a video as a reference that I recorded in addition to the files and drivers you need.
Either because of bad flashing, you were wrong with bootstacks or ROM.
1.- See that the phone is off
2.- Press Volume + and Volume - and the Power key at the same time until the LED turns on and off in Red, that means that you are already in EDL Emergency mode.
3.- Connect the phone and Install the Drivers
4.- When you see that Qualcomm HS-USB QDLoader 9008 and a COM port have been installed
5. Open MiFlash and copy the address of the unpacked A2017U_B19-NOUGAT_TWRP_EDL package into the address bar.
click on Refresh and when the COM port of your phone comes out click on Flash.
If everything goes well you will see that the process begins and at the end it will say Ready, then you have to disconnect the phone and press power about 10 seconds later and press power again until it turns on. You should be able to enter TWRP to restore your backup or flash a new ROM.
Even it is very likely that the rom you had installed start.
https://www.youtube.com/watch?v=dHB61cMurG4&t=10s
Link MiFlash: http://www.mediafire.com/file/25fu9boj245wynz/MiFlash20161222.zip
LinkB19 EDL TWRP: https://build.nethunter.com/misc/axon7/A2017U_B19-NOUGAT_TWRP_EDL.zip
Link Drivers Qualcomm: https://androidfilehost.com/?fid=745425885120754986
Link Drivers ZTE: http://phoneusbdrivers.com/zte-axon-7-usb-driver/
Update: All Links in 1 uploaded by me: https://drive.google.com/file/d/16Szwb4paI-aBH-v8gxbuVi0xMf-NdxLp/view?usp=sharing
TheDarkKnightSM said:
I can not be held responsible if you do not follow the instructions and your phone explodes in your face, you get wings and fly, your microsd smoke etc. EVERY PROCEDURE YOU MAKE ON YOUR PHONE IS ONLY YOUR RESPONSIBILITY.
As you notice, this process also enables fastboot commands.
This is a step-by-step tutorial to get the Brick phone
I leave a video as a reference that I recorded in addition to the files and drivers you need.
Either because of bad flashing, you were wrong with bootstacks or ROM.
1.- See that the phone is off
2.- Press Volume + and Volume - and the Power key at the same time until the LED turns on and off in Red, that means that you are already in EDL Emergency mode.
3.- Connect the phone and Install the Drivers
4.- When you see that Qualcomm HS-USB QDLoader 9008 and a COM port have been installed
5. Open MiFlash and copy the address of the unpacked A2017U_B19-NOUGAT_TWRP_EDL package into the address bar.
click on Refresh and when the COM port of your phone comes out click on Flash.
If everything goes well you will see that the process begins and at the end it will say Ready, then you have to disconnect the phone and press power about 10 seconds later and press power again until it turns on. You should be able to enter TWRP to restore your backup or flash a new ROM.
Even it is very likely that the rom you had installed start.
&t=10s
Link MiFlash: http://www.mediafire.com/file/25fu9boj245wynz/MiFlash20161222.zip
LinkB19 EDL TWRP: https://build.nethunter.com/misc/axon7/A2017U_B19-NOUGAT_TWRP_EDL.zip
Link Drivers Qualcomm: https://androidfilehost.com/?fid=745425885120754986
Link Drivers ZTE: http://phoneusbdrivers.com/zte-axon-7-usb-driver/
Update: All Links in 1 uploaded by me: https://drive.google.com/file/d/16Szwb4paI-aBH-v8gxbuVi0xMf-NdxLp/view?usp=sharing
Click to expand...
Click to collapse
Crap forget what I said, it was right on the title...
Would be much better if you:
a) made it for all 3 models with a link to WesTD's EDL package thread
b) said something about DFU (if you make it for the other models) and how this will not work on them if the driver is the dfu one (zte handset diagnostic interface)
Add somewhere on the guide that it is only for the U just in case.
Choose an username... said:
Crap forget what I said, it was right on the title...
Would be much better if you:
a) made it for all 3 models with a link to WesTD's EDL package thread
b) said something about DFU (if you make it for the other models) and how this will not work on them if the driver is the dfu one (zte handset diagnostic interface)
Add somewhere on the guide that it is only for the U just in case.
Click to expand...
Click to collapse
both in the title and in the guide in the mention of the package, it is said that it is only for A2017U, even though I will have a clarification in red and great, if any. Thank you.
Sent from my ZTE Axon 7 using XDA Labs
Details of phone
{
"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"
}
Currently I have 2 issues. Number 1 is that I cannot find stock firmware for my phone on Frija. No matter what CSC code I enter it is unable to find it. However, this is not a major problem at the moment as I plan to use this random firmware if things go wrong as it resembles my firmware.
~Main Issue~
My main issue is that even though I have enabled OEM unlock and USB debugging in developer settings I am unable to unlock my bootloader.
I am currently using this method:
Code:
1-Turn off the device.
2-press Volume Down + Volume UP + Connect the USB cable.
3-You will see a warning and under it three options (Volume up: Continue / Volume up long press: Device unlock mode / Volume down: Cancel restart phone.
4-Will choose Volume up long press: Device unlock mode.
5-Unlock bootloader page will appear, Under it are two options (Volume up: Yes / Volume down: No).
6-Press the volume up key.
The device will reboot and a message will appear telling you that the boot loader has been unlocked, Then press the power switch to continue.
7-Then press the power switch to continue.
8-The bootloader is unlocked, Done.
At step 5 the screen either only displays on the lower eighth of the device and shuts down or it shows the "bootloader page" but will not accept a volume up input press and powers down. Any advice on how to resolve this issue?
Update: I attemped to do a factory reset on the phone but the phone won't even boot into recovery mode! Holding PWR+VOLUP on boot does nothing!
what goes wrong?
Linusrg1 said:
what goes wrong?
Click to expand...
Click to collapse
When I reboot to unlock the bootloader, the confirmation screen does not accept the volume up input
Tattered said:
When I reboot to unlock the bootloader, the confirmation screen does not accept the volume up input
Click to expand...
Click to collapse
i have the same phone
with the same issue, i get pass the long press vol up, another menu confirm i want to unlock the bootloader i press vol up for yes . A quick blue screen and boots into recovery.
ro.oem_unlock_supported]: [1]
[sys.oem_unlock_allowed]: [1]
[ro.boot.vbmeta.device_state]: [locked]
And I have had the recovery issue as well. I have been using adb to boot into recovery when needed
first download and install the vcom drivers
https://forum.xda-developers.com/galaxy-a10/how-to/guide-how-to-root-a107m-device-a10s-9-10-t4115919
read this too
https://forum.xda-developers.com/galaxy-a10/how-to/discussion-galaxy-a10s-successfully-t4051189
finally got mine unlocked
first i did a factory reset from the settings not the recovery
i went through the setup without signing in,
activated developer settings , usb debugging . Make sure oem boot loader is selected
.. turned off the phone and pressed up and down as i plugged the usb into the phone
Then long pressed up until the menu changed press up again and it unlocked.
it will factory set again . go through the setup without signing in
activated developer settings , usb debugging .
now sure oem boot loader should be grayed out.
now if your intalling magisk follow the instructions
I was able to flash magisk and it went great for about 10 minutes. my bootloader relocked
if it happens to you just odin the full stock firmware and do the process again
---------- Post added at 10:41 PM ---------- Previous post was at 10:19 PM ----------
firmware
i would use frija the speeds are faster
theres also
https://samfrew.com/download/Galaxy__A10s__/Ow46/TPA/A107MUBU5BTJ3/A107MOWO5BTJ2/
Hi there! I need some help, I am trying to root my device and need a boot.img, but I cannot find a Rom for the x9 anywhere online.
This is my first time doing this, I got this phone just to mess around with rooting. But maybe I bought a bad phone for it.
If there are no Flash Roms online, what are the next steps? Can I use a Rom for the e9 which released alongside this phone? Sounds like it wouldnt work.. but IDK.
Looking for help from the experts ^^
Any help is appreciated.
Finally found one! Took over 2 hours to download a 2gb file O,O but it's finally done.
Now I am having problems getting into bootloader mode.
In developer mode with both OEM unlocking and USB debugging enabled.
Used the correct cmd prompt (adb reboot bootloader) but the phone just restarts.
I've tried restarting while holding the volume buttons.
VOL Down = Factory Test Mode, nothing works as expected there.
VOL UP = A boot menu letting me select from ~10 options, one of them is Boot to Bootloader. Selecting that simply boots normal, nothing special.
I have followed three guides:
How TO Root Vodafone Smart X9 Magisk without TWRP Recovery
If your Smart X9 is rooted using Magisk without TWRP Recovery. You can control a lot of features such as you can remove unwanted software.
www.getdroidpro.com
Vodafone Smart E9 Unlock Bootloader with Fastboot Method
How to unlock bootloader on your Vodafone with Fastboot Method. You can install custom ROM, custom recovery, kernel, flash all data
www.mobilewithdrivers.com
All seem logical enough, many similarities between them. I just cannot get into fastboot mode.
I've seen LOADS of threads with this same problem on this forum. And none of them have any solutions. So I think this is the end of the road. If nobody has figured it out .. then I am just out of luck I guess?
HalpNeeded said:
Forget, your phone have only 3 buttons
Click to expand...
Click to collapse
Hi @joke19 !
I havnt seen any of the guides mentioning needing a certain amount of buttons :O
How does that factor in - does that mean it cannot be rooted for some reason?
Still having this problem, and I have followed a lot of guides to the letter. I cant see what I am doing wrong. Here's where I am:
Phone is visible on device manager and the drivers are up-to-date.
{
"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"
}
PC is fully up to date on Windows 10.
I've got the lastest up-to-date version of platform-tools.
I'm using USB2.0 with the correct wires.
The phone is in developer mode with USB Debugging and OEM unlocking enabled.
I'm using the correct command lines. adb devices & adb reboot bootloader work as expected.
But none of these will work: fastboot devices, fastboot flashing unlock, fastboot oem unlock.
I just get < waiting for any device >
Can anyone help figure this out? I must be doing sooomething wrong. Everything online says its a driver issue, but then again, all the guides on how to fix that driver issue have been followed and completed. The first bullet with the image should also sort of verify that.
Praying some wizard out there has the knowledge I need to get this working! ^^
HalpNeeded said:
Still having this problem, and I have followed a lot of guides to the letter. I cant see what I am doing wrong. Here's where I am:
Phone is visible on device manager and the drivers are up-to-date.
View attachment 5671635
PC is fully up to date on Windows 10.
I've got the lastest up-to-date version of platform-tools.
I'm using USB2.0 with the correct wires.
The phone is in developer mode with USB Debugging and OEM unlocking enabled.
I'm using the correct command lines. adb devices & adb reboot bootloader work as expected.
But none of these will work: fastboot devices, fastboot flashing unlock, fastboot oem unlock.
I just get < waiting for any device >
Can anyone help figure this out? I must be doing sooomething wrong. Everything online says its a driver issue, but then again, all the guides on how to fix that driver issue have been followed and completed. The first bullet with the image should also sort of verify that.
Praying some wizard out there has the knowledge I need to get this working! ^^
Click to expand...
Click to collapse
did you manage to get this working?
After I updated pixel 6 to android 13,phone doesn't work became bricked and I can't fix it because when I plug it into my computer and see the device manager in windows,but it is not detected by `adb devices` or `fastboot devices`.I see it detected in seconds and disappear by watching device manager as a " USB serial port device (COM 3)" in windows 11
{
"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"
}
in windows 7 & ubuntu detected as pixel CDC- ACM (Pixel ROM Recovery )device because devices manager in win7 can't find any driver compatible so it detected as itself in "Other devices"
in VM box :
while I hold down the power button so I can't fix it,how to restore my phone and flash it in this mode I think this mode is EDLI tried to boot in bootloader by pressing press power + volume down and power + volume up and all together but nothing work , the phone is deadI have tried to fix by this post but unfortunately it doesn't work https://forum.xda-developers.com/t/guide-unbrick-pixel-6-oriele-or-pixel-6-pro-raven.4441245/I have escalated this issue in google tracker since 2 months but i got NO ANSWER and NO HELP https://issuetracker.google.com/issues/243636259
is anyone have any idea to fix my ? i will appreciate any try PLZ help me
Very likely you can't.
From your description, when you flashed it, A13 was updated only on one slot with the new bootloader, while the second slot is still stuck with the previous bootloader. During the flashing (how did you flash?), something went wrong, so the Pixel wanted to boot from the second slot with the "old" bootloader and the "Anti-Roll-Back" kicked in.
RMA and hopefully get an exchange
Cheers
Follow this steps and let us know if it worked for you
1. Unplug the cable from your phone
2. Press and hold for at least 15 seconds the power button then release
3. Connect a cable from your pc to your phone but you need to press volume up and hold it until you connect the cable, once connected release the button your phone shall turn on fastboot mode, it it worked just proceeded and flash a13 again, just download it from it's official source
14. Profit
tom1807 said:
Very likely you can't.
From your description, when you flashed it, A13 was updated only on one slot with the new bootloader, while the second slot is still stuck with the previous bootloader. During the flashing (how did you flash?), something went wrong, so the Pixel wanted to boot from the second slot with the "old" bootloader and the "Anti-Roll-Back" kicked in.
RMA and hopefully get an exchange
Cheers
Click to expand...
Click to collapse
i have flashed using fastboot commands and that was on both-solts
Do you have idea how manufacturing put the Rom on devices? OR about
cdc-acm connection?
J0nhy said:
Follow this steps and let us know if it worked for you
1. Unplug the cable from your phone
2. Press and hold for at least 15 seconds the power button then release
3. Connect a cable from your pc to your phone but you need to press volume up and hold it until you connect the cable, once connected release the button your phone shall turn on fastboot mode, it it worked just proceeded and flash a13 again, just download it from it's official source
14. Profit
Click to expand...
Click to collapse
i have tried but nothing work