Hello everyone !
I updated my tablet to android 9, during the update an error occured and now my tablet can't boot (it's stuck on LENOVO screen forever).
My tablet is Lenovo TB-X605F.
I tried:
- Wipe/data (recovery mode)
- Wipe/cache (recovery mode)
- Fastboot (my bootloader is locked so I can do nothing)
Note: I don't have TWRP or custom recovery, I have the default one .
I don't know what can i do please help me !
XX_MRBEAN_XX said:
Hello everyone !
I updated my tablet to android 9, during the update an error occured and now my tablet can't boot (it's stuck on LENOVO screen forever).
My tablet is Lenovo TB-X605F.
I tried:
- Wipe/data (recovery mode)
- Wipe/cache (recovery mode)
- Fastboot (my bootloader is locked so I can do nothing mSpy reviews)
Note: I don't have TWRP or custom recovery, I have the default one .
I don't know what can i do please help me !
Click to expand...
Click to collapse
I am sorry to say that but I guess nothing could be done to fix your tablet. I would be happy to proven wrong and see some solutions in this thread.
@XX_MRBEAN_XX
The mostly overlooked command
Code:
adb sideload <ROM / MOD>
may help: Get device's Stock ROM and flash it this way.
jwoegerbauer said:
@XX_MRBEAN_XX
The mostly overlooked command
Code:
adb sideload <ROM / MOD>
may help: Get device's Stock ROM and flash it this way.
Click to expand...
Click to collapse
Windows detect my tablet only when It's in fastboot. I don't know why
When I do recovery --> apply update from adb it's say "E: failed to open driver control: Permission denied"
And in my pc, ADB don't recognize my tablet (only fastboot recognize)
Btw, i downloaded my stock tablet rom
XX_MRBEAN_XX said:
Windows detect my tablet only when It's in fastboot. I don't know why
When I do recovery --> apply update from adb it's say "E: failed to open driver control: Permission denied"
And in my pc, ADB don't recognize my tablet (only fastboot recognize)
Btw, i downloaded my stock tablet rom
Click to expand...
Click to collapse
1. Looks to me that the ADB-driver you use isn't suitable: Download and install the correct driver for your Lenovo. tab:
https://devsjournal.com/download-lenovo-usb-drivers-adb.html
2. Wondering why then you didn't flash this Stock ROM by means of Fastboot ?
Code:
fastboot devices
fastboot erase boot
fastboot erase system
fastboot erase cache
fastboot erase userdata
fastboot flashall <STOCK-ROM-IMG>
fastboot reboot
jwoegerbauer said:
1. Looks to me that the ADB-driver you use isn't suitable: Download and install the correct driver for your Lenovo. tab:
2. Wondering why then you didn't flash this Stock ROM by means of Fastboot ?
Code:
fastboot devices
fastboot erase boot
fastboot erase system
fastboot erase cache
fastboot erase userdata
fastboot flashall <STOCK-ROM-IMG>
fastboot reboot
Click to expand...
Click to collapse
Well, i think i am ****ed because when i do these fastboot command, it's saying "FAILED (remote: 'device is locked. Cannot erase.')
And adb still don't recognize my system.
Thank you for your help
XX_MRBEAN_XX said:
Well, i think i am ****ed because when i do these fastboot command, it's saying "FAILED (remote: 'device is locked. Cannot erase.')
Click to expand...
Click to collapse
Oh man
become familiar with Fastboot-driver and its subcommands available!!!
Anyway, unlock tab's boot-loader by means of Fastboot before you carry out the commands previously shown
Code:
fastboot devices
fastboot OEM unlock
FYI: I no longer participate with this thread.
jwoegerbauer said:
Oh man
become familiar with Fastboot-driver and its subcommands available!!!
Anyway, unlock tab's boot-loader by means of Fastboot before you carry out the commands previously shown
Code:
fastboot devices
fastboot OEM unlock
FYI: I no longer participate with this thread.
Click to expand...
Click to collapse
I tried fastboot oem unlock
It's say "unknow commands"
Anyway thank you for your help !
I think we can't do something for this tablet.
Thank you very much
XX_MRBEAN_XX said:
Hello everyone !
I updated my tablet to android 9, during the update an error occured and now my tablet can't boot (it's stuck on LENOVO screen forever).
My tablet is Lenovo TB-X605F.
I tried:
- Wipe/data (recovery mode)
- Wipe/cache (recovery mode)
- Fastboot (my bootloader is locked so I can do nothing)
Note: I don't have TWRP or custom recovery, I have the default one .
I don't know what can i do please help me !
Click to expand...
Click to collapse
To rescue a bricked Lenovo device, download their LMSA tool to a Windows PC. Use the Rescue option.
Have a look on the TWRP thread for the unlock commands. They will only work if you had already enabled Developer Options and OEM unlocking before the device bricked.
Yahoo Mike said:
To rescue a bricked Lenovo device, download their LMSA tool to a Windows PC. Use the Rescue option.
Have a look on the TWRP thread for the unlock commands. They will only work if you had already enabled Developer Options and OEM unlocking before the device bricked.
Click to expand...
Click to collapse
Holy crap. My hero! Can I buy you a beer dude?
Related
Asus TF201 stuck on Asus Logo screen + "this device is unlocked" -- Newbie here!
Hi guys,
First off- I have to clarify that I don't know squat about Android..
I got this TF201 tablet from a technology-ill friend who asked if I can do something about it.
I've encountered many posts of people with this issue:
* Powering On the tablet get it stuck on the Asus Logo screen, with the "this device is unlocked" writing on the top left corner (and the nVidia Logo on the bottom right).
* Trying to power off the tablet only causes a power cycle, and it gets stuck in the same screen all over again.
* Trying to boot into fastrecovery (I think that's how it's called? - pressing the down volume button+power button) gets to the same stuck on screen as mentioned.
* Only way I got it to power off (I think) is by pressing the up volume button+power button and then first releasing the power button after the screen is blank (and only after the volume button).
* Connecting the tablet to the computer doesn't seem to work - it won't recognize the USB device (I do see "APX" under the list of Other Devices on the Device Manager) - can't seem to find (working) drivers.
I've read that there's a way to solve this using NVFlash -- don't think I have that..
Found other workarounds, but as I mentioned - I don't know how to get around much in this territory.
Anyone who's patient enough to help me out (if such thing is even remotely possible) ?
It will be much appreciated !
help?
I tryed install the v30, and later v26 version, but do not work.
When powering On the tablet get it stuck on the Asus Logo screen, with the "this device is unlocked" writing on the top left corner and the nVidia Logo on the bottom right.
Trying start with power mode, but boot do not start, only RCK mod recovery/fastboot started.
I think, that device is not unlocked. How to check/verify the device really unlocked? Or any idea? Please help me. Thanks.
Have one pf you @msarg77 or @skew01 got the tablet working again?
I am stuck with a tf201 which has TWRP 2.8 but after installing Katkiss 6 it won't boot; keeps rebooting...
deltabet, Can you get into the TWRP console?
NP
I'am sorry Nektopoli that i did not answer you any sooner.
The original fault was that i had formatted the tab with the wrong file system; it should have been f2fs.
After that is was Murphy, i run into other problems ending up with no fastboot, no adb, no TWRP only APX mode.
Luckily i had made the NvFlash backup of my tab with the important tab id files...
But i managed to get my tablet working with Android 6, but had to reinstall the original Asus firmware with the nvflash backup i had made.
An other problem i run into was that my tablet had an older bootloader 10.4.2.15 and this should have been 10.4.2.18.
With the reinstall of the latest Asus firmware (from support site Asus) i received the correct bootloader.
Anyhow, I am glad the tab is working again. And i have learned a lot about installing a rom on an Android tab.
Good to hear, but you should try be on BootLoader: 10.6.1.27.1 if you want to use one of the newer KANG-TWRP
NP
Check out this link for info on the bootloader;
https://forum.xda-developers.com/transformer-prime/help/bootloader-questions-tf201-t3104884
Same Problem... Different Day...
Nektopoli said:
Good to hear, but you should try be on BootLoader: 10.6.1.27.1 if you want to use one of the newer KANG-TWRP
NP
Check out this link for info on the bootloader;
https://forum.xda-developers.com/transformer-prime/help/bootloader-questions-tf201-t3104884
Click to expand...
Click to collapse
Hya Gang... I seem to have the same problem.....
The good news here is that I am able to get into the bootloader, and I do have BootLoader: 10.6.1.27.1 and I am able to fastboot into my windows computer... I have tried fastboot flashing both the flatline TWRP and the latest TWRP but here is my problem..
It will start into the TWRP recovery screen for a few seconds... then goes black. This computer was working fine running KatKiss a few weeks ago, then one night just crashed, went into the above described bootloop and got me stuck in this situation...
Unidave199, you might have to do a full wipe (via a laptop or computer), flash KANG's TWRP [found here: https://basketbuild.com/devs/Captain_Throwback/TF201T/TWRP ].
Boot into the new TWRP and then flash the ROM, GAAPs and SuperSU. I was able to send these commands to my TF201 to up-brick it;
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
Then flash the TWRP and reboot
fastboot -i 0x0B05 flash recovery c:\your\DIRECTORY\path\BLOB.FILE <TWRP zip file
fastboot -i 0x0B05 reboot
Good Luck
NP
Nektopoli said:
Unidave199, you might have to do a full wipe (via a laptop or computer), flash KANG's TWRP [found here: https://basketbuild.com/devs/Captain_Throwback/TF201T/TWRP ].
Boot into the new TWRP and then flash the ROM, GAAPs and SuperSU. I was able to send these commands to my TF201 to up-brick it;
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
Then flash the TWRP and reboot
fastboot -i 0x0B05 flash system c:\your\DIRECORY\path\HERE
fastboot -i 0x0B05 reboot
Good Luck
NP
Click to expand...
Click to collapse
Regarding this line:
fastboot -i 0x0B05 flash system c:\your\DIRECORY\path\HERE
Is this a directory of the TWRP .img file that you've included in your post?
Luckily i had made the NvFlash backup of my tab with the important tab id files...
But i managed to get my tablet working with Android 6 said:
what did you use to restore your id files?
Click to expand...
Click to collapse
Krysiul said:
Regarding this line:
fastboot -i 0x0B05 flash recovery c:\your\DIRECTORY\path\HERE
Is this a directory of the TWRP .img file that you've included in your post?
Click to expand...
Click to collapse
Yes, but I made a mistake, it needs to be flashed to the recovery partition NOT system
NP
asus tf201 stucked on "the device is unblocked"
I seem to have the same problem with my asus tf201
Have you solved this problem?
shehada said:
I seem to have the same problem with my asus tf201
Have you solved this problem?
Click to expand...
Click to collapse
You need a computer or laptop (windows 7 or XP is preferred) with;
Universal_Naked_Driver_0.72: https://forum.xda-developers.com/attachment.php?attachmentid=1489873&d=1353190173
and
Minimal ADB and Fastboot: https://forum.xda-developers.com/showthread.php?t=2317790
Then you can plug the TF201 into the computer and see if you can receive fastboot commands like: adb reboot
NP
I am having trouble rooting my Galaxy J7 Prime sm-j727t
Every Odin version I use with every TWRP tar file I try to use doesn't work. They either Fail or Odin stops responding when I try to load the tar file into the AP.
I've tried just using the CF Auto Root and those fail as well.
Any ideas what the issue is? I've been trying for two days with no success
Is your bootloader unlocked?
Emir Çetin said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
I thought Samsung phones come with bootloader unlocked already??
BramaKnox said:
I thought Samsung phones come with bootloader unlocked already??
Click to expand...
Click to collapse
You can check bootloader with dialer (search it).
Of phone has fastboot mode you can check bootloader with fastboot commands (search it too)
Emir Çetin said:
You can check bootloader with dialer (search it).
Of phone has fastboot mode you can check bootloader with fastboot commands (search it too)
Click to expand...
Click to collapse
When I put the phone in FastBoot mode I have the following options
Reboot System Now
Reboot to Bootloader
Apply update from ADB
Apply Update from SD card
Wide data/factory reset
Wipe Cashe partition
Mount /system
View recovery logs
Run graphics test
Power off
Lacking storage booting
1-Install your phones drivers on your PC.
2-Install adb and fastboot tools. https://www.addictivetips.com/android/download-adb-and-fastboot/
3-Reboot to fastboot.
4-Connect your phone with USB cable.
5-Open command prompt in adb and fastboot folder
6-Type fastboot devices (If you don't see your device there is a problem in drivers or fastboot)
7-Type fastboot oem device-info
You can check your bootloader status in that screen.
Emir Çetin said:
1-Install your phones drivers on your PC.
2-Install adb and fastboot tools. https://www.addictivetips.com/android/download-adb-and-fastboot/
3-Reboot to fastboot.
4-Connect your phone with USB cable.
5-Open command prompt in adb and fastboot folder
6-Type fastboot devices (If you don't see your device there is a problem in drivers or fastboot)
7-Type fastboot oem device-info
You can check your bootloader status in that screen.
Click to expand...
Click to collapse
Am I doing something wrong here ? see attached for screnshot
Emir Çetin said:
1-Install your phones drivers on your PC.
2-Install adb and fastboot tools. https://www.addictivetips.com/android/download-adb-and-fastboot/
3-Reboot to fastboot.
4-Connect your phone with USB cable.
5-Open command prompt in adb and fastboot folder
6-Type fastboot devices (If you don't see your device there is a problem in drivers or fastboot)
7-Type fastboot oem device-info
You can check your bootloader status in that screen.
Click to expand...
Click to collapse
I tried a some other steps. Tried using the video on youtube on a tut. When I get to the oem unlock I just get stuck with a msg sayng "waiting for any device" my device is plugged in, from what I know I have updated the samsung drivers (from previous attempt of other methods) the adb bootloader cmd did put my phone into fastboot mode
(White box, blue arrow point down with a straight line under the point)
(Blue screen with Downloading...)
do not turn off target
What am I missing here?
I tried rooting TWRP 3.2.3. with Odin on the phone again and it still failed
Does anyone else have any more insight to a possible solution?
Have you checked bootloader with dialer?
BramaKnox said:
I am having trouble rooting my Galaxy J7 Prime sm-j727t
Every Odin version I use with every TWRP tar file I try to use doesn't work. They either Fail or Odin stops responding when I try to load the tar file into the AP.
I've tried just using the CF Auto Root and those fail as well.
Any ideas what the issue is? I've been trying for two days with no success
Click to expand...
Click to collapse
Witch android you are?
Hello I have a xiaomi mi mix 3 5g that I never removed the bootloader on, as it had the stock EU firmware on. It has recently been updated to to MIUI12. however the battery went low and went all weird and now constantly reboots.
I can get to fastboot by holding down the power and volume down, I have also tried a wipe device by holding down the power and up. From what I have read I i cant re-install fastboot firmware without and unlocked bootloader. (can someone confirm that this is correct) as its not clear.
***I have now confirmed this I have tried to install firmware using xiaomi flash tool and fails with the following
"Error: erasing boot Failed remote erase is not allowed in locked state. so this confirms it.
Also I cant unlock the bootloader as it wont boot. Does any body have any idea of what I can do with this phone? any help would be apprciated
thanks
The error I get when trying the mi unlock tool
Couldn't Unlock
Please add your account in MIUI;s Settings > Developer options > Mi Unlock Status
Seems the update miserably failed, Android OS got corrupted. My suggestion: Re-flash phone's Stock ROM ( phone's battery should be fully charged ! ).
To keep you updated:
FASTBOOT is a program used to manipulate ( list, install, erase ) the non-volatile memory such as flash filesystem partitions on devices that adhere to the fastboot protocol, via a USB connection from a host computer. It requires that the device be started in a boot loader mode ( AKA fastboot mode ) with the fastboot protocol enabled.
Take note that fastboot ( the fastboot daemon ) is integral part of phone's bootloader.
jwoegerbauer said:
Seems the update miserably failed, Android OS got corrupted. My suggestion: Re-flash phone's Stock ROM ( phone's battery should be fully charged ! ).
To keep you updated:
FASTBOOT is a program used to manipulate ( list, install, erase ) the non-volatile memory such as flash filesystem partitions on devices that adhere to the fastboot protocol, via a USB connection from a host computer. It requires that the device be started in a boot loader mode ( AKA fastboot mode ) with the fastboot protocol enabled.
Take note that fastboot ( the fastboot daemon ) is integral part of phone's bootloader.
Click to expand...
Click to collapse
How do I re-flash stock rom when the bootlloader is not unlocked.
I have already tried Xiaomi's flash tool and it when flashing the stock ROM and get the following error
"Error: erasing boot Failed remote erase is not allowed in locked state"
Are there any methods of flashing a stock rom with a locked bootloader ?
sivhead said:
How do I re-flash stock rom when the bootlloader is not unlocked.
I have already tried Xiaomi's flash tool and it when flashing the stock ROM and get the following error
"Error: erasing boot Failed remote erase is not allowed in locked state"
Are there any methods of flashing a stock rom with a locked bootloader ?
Click to expand...
Click to collapse
How to flash firmware to any Xiaomi smartphone is described here.
jwoegerbauer said:
How to flash firmware to any Xiaomi smartphone is described ["]here[/url].
Click to expand...
Click to collapse
I have already tried that method When I flash using the flash tool I get the error "Error: erasing boot Failed remote erase is not allowed in locked state" My bootloader is not unlocked is this method supposed to be work with a locked bootloader. Bit of chicken and egg situation. I cant unlock the bootloader as I cant boot the device and I cant reflash software as I don't have an unlocked bootloader.
AFAIK you always are allowed to flash an original firmware image without unlocking the phone's bootloader.
If you can access the device by means of ADB try to flash the Stock ROM via ADB:
Code:
adb devices
adb reboot sideload
adb sideload <LOCATION_OF_STOCK_ROM_ZIP_FILE_HERE>
C:\adb>adb devices
List of devices attached
f625af1 sideload
C:\adb>adb sideload miui_ANDROMEDAEEAGlobal_V12.0.1.0.PEMEUXM_9e4961bf09_9.0.zip
loading: 'miui_ANDROMEDAEEAGlobal_V12.0.1.0.PEMEUXM_9e4961bf09_9.0.zip'
* cannot read 'miui_ANDROMEDAEEAGlobal_V12.0.1.0.PEMEUXM_9e4961bf09_9.0.zip' *
@sivhead
Try this:
Rename the file to rom.zip and then start "adb sideload rom.zip"
jwoegerbauer said:
@sivhead
Try this:
Rename the file to rom.zip and then start "adb sideload rom.zip"
Click to expand...
Click to collapse
tried that same error cannot read rom.zip
sivhead said:
tried that same error cannot read rom.zip
Click to expand...
Click to collapse
C:\adb>adb sideload c:\Users\Administrator\Downloads\andromeda_eea_global_images_V12.0.1.0.PEMEUXM_20200823.0000.00_9.0_eea_70004ce050.zip
loading: 'c:\Users\Administrator\Downloads\andromeda_eea_global_images_V12.0.1.0.PEMEUXM_20200823.0000.00_9.0_eea_70004ce050.zip'* failed to read command: No error
I also thought its worth mentioning that I have never registered the device with mi connect
Also enable usb debugging is not enabled.
aqnd THe bootloader is locked .
Man I wish I would have unlocked the bootloader when I got it and put a custom rom on. then I wouldnt be in this situation. how ironic that I wanted to keep it stock
so I am at a loose end
I want to unlock the bootloader on my ZTE Blade v9 but i can only boot normal in recovery mode and in ftm (Factory Test Mode). In Ftm i can use adb but not with root and without fastboot. If i type in adb "adb reboot bootloader" , its just an normal reboot. When i select reboot to bootloader in the recovery mode too. I can go in Edl on my phone too when i press both volume buttons. So is there a way to go in fastboot? Sorry for my bad english i am german.
Fastboot commands basicallly only work if device's bootloader is unlocked. You do this via enabling in Android Settings -> Developer options -> "OEM unlock", restart device, and run commands
Code:
fastboot devices
fastboot flashing unlock
and again restart device.
The thing is I can't boot into fastboot.
The thing is i can't boot into fastboot.
Kiwilikecookies said:
The thing is i can't boot into fastboot.
Click to expand...
Click to collapse
What do you want to express with this? Do you mean you can't boot into device's bootloader mode?
Code:
adb devices
adb reboot fastboot
What error message do you get when doing what?
Please clarify.
Kiwilikecookies said:
I want to unlock the bootloader on my ZTE Blade v9 but i can only boot normal in recovery mode and in ftm (Factory Test Mode). In Ftm i can use adb but not with root and without fastboot. If i type in adb "adb reboot bootloader" , its just an normal reboot. When i select reboot to bootloader in the recovery mode too. I can go in Edl on my phone too when i press both volume buttons. So is there a way to go in fastboot? Sorry for my bad english i am german.
Click to expand...
Click to collapse
At 4pda is instructions, using service firmware's aboot
ZTE Blade V9 - Обсуждение - 4PDA
ZTE Blade V9 - Обсуждение, Смартфон, 5.7"
4pda.ru
Mentioned here: https://romprovider.com/zte-blade-v9-twrp/
jwoegerbauer said:
What do you want to express with this? Do you mean you can't boot into device's bootloader mode?
Code:
adb devices
adb reboot fastboot
What error message do you get when doing what?
Please clarify.
Click to expand...
Click to collapse
It's only a normal reboot
CXZa said:
At 4pda is instructions, using service firmware's aboot
ZTE Blade V9 - Обсуждение - 4PDA
ZTE Blade V9 - Обсуждение, Смартфон, 5.7"
4pda.ru
Mentioned here: https://romprovider.com/zte-blade-v9-twrp/
Click to expand...
Click to collapse
Thanks i am going to check it out now
Kiwilikecookies said:
Thanks i am going to check it out now
Click to expand...
Click to collapse
I am not able to download the tools.zip file. So what can i do then?
Kiwilikecookies said:
It's only a normal reboot
Click to expand...
Click to collapse
Have you ever tried this?
jwoegerbauer said:
Have you ever tried this?
Click to expand...
Click to collapse
I saw that so often there is not physical camera button or home button. Only a normal camera and with Android a navigation bar. and with Volume + i get in recovery mode and with Volume - i get in Ftm.
Kiwilikecookies said:
I am not able to download the tools.zip file. So what can i do then?
Click to expand...
Click to collapse
Good luck! (and remember to make a backup first.)
Thanks
CXZa said:
Good luck! (and remember to make a backup first.)
Click to expand...
Click to collapse
I cannot speak russian so I use a translator but i don't understand it clearly. Did someone the guide and explain me how to do it.
If I have understood correctly, OP has a problem with Fastboot Mode (Bootloader Mode) and not with Recovery Mode. Wonder why OP should install a CR ( TWRP ) to solve his problem?
@Kiwilikecookies
A CR replaces device's Stock Recovery, what can't be undone. Do you really want this?
jwoegerbauer said:
If I have understood correctly, OP has a problem with Fastboot Mode (Bootloader Mode) and not with Recovery Mode. Wonder why OP should install a CR ( TWRP ) to solve his problem?
@Kiwilikecookies
A CR replaces device's Stock Recovery, what can't be undone. Do you really want this?
Click to expand...
Click to collapse
I want to unlock the bootloader to install Cr or Twrp with EDL and when i can backup it i do(wich is not importent for me), root my device and install a custom rom because there are no more official updates.
How Fastboot is implemented on a mobile device if at all ( Note: The fastboot mode is available on a lot of devices but not on all the devices out there ) varies from OEM to OEM. It's on you to find out this.
I know that from my old broken phone where i had a bootloop and had to reinstall android but i want to unlock the bootloader and my phone hasn't fastboot. So i have only recovery, ftm and EDL wich i can boot into it. I only want to unlock the bootloader i know then how to flash twrp (with edl).
Hello, i bricked my V9 . Cant communicate via ADB anymore. It shows me DFU5 COM5 under Windows and when i use ZTE Terminal i can change it it to QDLoader 9008 COM6 but still no communication via ADB possible. The only thing that works is Recovery Mode but can't install update.zip (OEM unlock not enabled, Bootloader is unlocked) and Sideload also not working (adb: sideload connection failed: no devices/emulators found). And it's not a USB, Drivers or ADB problem. Another phone works. Qfil can't communicate with COM6 and in COM5 Mode it says "Switch to EDL Fail". What i can do now?
XTA4235 said:
Hello, i bricked my V9 . Cant communicate via ADB anymore. It shows me DFU5 COM5 under Windows and when i use ZTE Terminal i can change it it to QDLoader 9008 COM6 but still no communication via ADB possible. The only thing that works is Recovery Mode but can't install update.zip (OEM unlock not enabled, Bootloader is unlocked) and Sideload also not working (adb: sideload connection failed: no devices/emulators found). And it's not a USB, Drivers or ADB problem. Another phone works. Qfil can't communicate with COM6 and in COM5 Mode it says "Switch to EDL Fail". What i can do now?
Click to expand...
Click to collapse
check params.cmd
Hi guys I am having an interested issue,
I want to install custom rom in my phone
I have downloaded in depth test and applied for un depth test
my mobile do connect to computer when it prompt to select mod I do select file transfer and my mobile do connect to laptop
and it shows in "adb devices" but when it goes into bootloader mod my mobile gets disconnected I have done everything I could
I have install every possible driver i got from articles but non worked is it the issue with my windows 10 ? or driver issue I have spent my whole night on this but couldn't find the way
fastboot devices
0purple said:
fastboot devices
Click to expand...
Click to collapse
what does it mean ?
when i connect my phone it prompt me with this and usb debugging is on
i tried adb devices but it didn't showed anything but when i chose transfer file it do connect to the laptop and shows in adb devices
najam489 said:
what does it mean ?
Click to expand...
Click to collapse
Try it once you are in fastboot
wow its showing
najam489 said:
wow its showing
Click to expand...
Click to collapse
0purple said:
Try it once you are in fastboot
Click to expand...
Click to collapse
i have another problem now my device is showing with fastboot devices but my devices status is locked when i tried this command "fastboot flash recovery recovery.img" it didnt work i am follwing this article https://www.guidetoroot.com/root-realme-3-pro/
thank you for your help my bootloader wasn't unlock it is now thanks a lot
It appears your device's bootloader is locked. Try:
fastboot oem unlock
fastboot flashing unlock
If that doesn't help, search for a guide on how to unlock bootloader for your specific brand.
It also looks like don't really know what you are doing. Make sure you are following trusted guide. If no, I'll be happy to help.
0purple said:
It appears your device's bootloader is locked. Try:
fastboot oem unlock
fastboot flashing unlock
If that doesn't help, search for a guide on how to unlock bootloader for your specific brand.
It also looks like don't really know what you are doing. Make sure you are following trusted guide. If no, I'll be happy to help.
Click to expand...
Click to collapse
well i did installed custom roms few time but i dont know much, i did unlock bootloader now the problem is i do install custom recovery twrp and it do installed and rom manager shows that custom recovery is installed but pressing volume down + power button just shows fastboot logo and it restart my phone, and with command "
adb reboot bootloader" i am able to boot into fastboot mood and when i go to recovery from their it open stock recovery instead of twrp
Stolen from my guide:
7. Go into fastboot mode
8. fastboot flash recovery recovery.img
9. fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
10. fastboot reboot recovery
12. Sometimes recovery doesn't want to stick as a permanent one. To test it, hold the power button and select "Reboot to recovery". If you reboot to TWRP, you can move on, but if you reboot to stock one, flash recovery using fastboot again and from recovery flash recovery again (sounds crazy, right?). I won't give you instructions on this, research it yourself. Make sure guide you will find is for your device and your recovery.