Hey guys. Hope the new year will find you jolly!
So, here is my problem. My OneplusX which runs with SultanXDA's Cyanogenmod 13 with TWRP (Sultan-TWRP-onyx-3.0.2-3_2016-10-23).
I cannot make it boot since whenever I press the button to start, it shows the screen (check below) for approximately half a second, it vibrates for a tiny moment and then shuts dows and starts again and does the same thing in a loop.
The only way for me to stop this loop is unplug the battery from the phone's motherboard.
I cannot boot into TWRP and all I can do is boot into fastboot mode. I get the device recognised with fastboot devices, but that doesn't work, too, since it reports that the phone is locked.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
64875585 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.487s]
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.490s
Ultimately, if it's not possible to make it work again, I would like to manage to pull some files from there, like images etc if that would be possible.
{
"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"
}
Thanks in advance for your help!
dimxr said:
Hey guys. Hope the new year will find you jolly!
So, here is my problem. My OneplusX which runs with SultanXDA's Cyanogenmod 13 with TWRP (Sultan-TWRP-onyx-3.0.2-3_2016-10-23).
I cannot make it boot since whenever I press the button to start, it shows the screen (check below) for approximately half a second, it vibrates for a tiny moment and then shuts dows and starts again and does the same thing in a loop.
The only way for me to stop this loop is unplug the battery from the phone's motherboard.
I cannot boot into TWRP and all I can do is boot into fastboot mode. I get the device recognised with fastboot devices, but that doesn't work, too, since it reports that the phone is locked.
Ultimately, if it's not possible to make it work again, I would like to manage to pull some files from there, like images etc if that would be possible.
Thanks in advance for your help!
Click to expand...
Click to collapse
I had same problem once all I could do was reboot fastboot but since the bootloader was locked but luckily I found this thread https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-x.417648/ on oneplus forums this really helped hope this will help you
So, I will not try to use the Mega Unbrick guide yet since it deletes every user data and I will keep that as a backup solution.
I tried using the Skipsoft Android Toolkit in order to unlock bootloader etc, but so far nothing has worked.
The weird thing is that it reports the bootloader locked (even though it shouldn't be since there was already TWRP on it), but by the time that I try to unlock it, it says it's unlocked, tries automatically to get back to normal boot and at that time, we start bootlooping again.
Here's the Skipsoft Android Toolkit report:
Are you ready to start? Type y[yes] or n[no]:y
Device mode detected: Fastboot Mode
Device Serial Number: 64875585
Checking bootloader state..
Device bootloader state is: Locked
Do you want to unlock the bootloader? Type y[yes] or n[no]:y
When prompted, Press the Volume Up/Down button to select Yes on the screen, then
press the Power button to Unlock the Bootloader. If it is already unlocked this
will just be skipped and your device will not be wiped.
Sending oem unlock command to device..
Device bootloader is already unlocked so no data will be wiped
Rebooting back to Android..
rebooting...
finished. total time: 0.002s
Click to expand...
Click to collapse
dimxr said:
So, I will not try to use the Mega Unbrick guide yet since it deletes every user data and I will keep that as a backup solution.
I tried using the Skipsoft Android Toolkit in order to unlock bootloader etc, but so far nothing has worked.
The weird thing is that it reports the bootloader locked (even though it shouldn't be since there was already TWRP on it), but by the time that I try to unlock it, it says it's unlocked, tries automatically to get back to normal boot and at that time, we start bootlooping again.
Here's the Skipsoft Android Toolkit report:
Click to expand...
Click to collapse
Being in the same situation right now. Did you manage to come out of it?
You can try to reflash a TWRP on it. And then boot on it.
Or Mega unbrick guide
Kéno40 said:
You can try to reflash a TWRP on it. And then boot on it.
Or Mega unbrick guide
Click to expand...
Click to collapse
Both not possible so far, since fastboot tells me with
fastboot devices
52541fca fastboot
a) FAILED (remote: Device not unlocked cannot flash or erase)
b) "oem unlock" and "flashing unlock" gives FAILED (status read failed (No such device))
MrEasy666 said:
Both not possible so far, since fastboot tells me with
fastboot devices
52541fca fastboot
a) FAILED (remote: Device not unlocked cannot flash or erase)
b) "oem unlock" and "flashing unlock" gives FAILED (status read failed (No such device))
Click to expand...
Click to collapse
Mega Unbrick Guide doesn't start by flashing via Fastboot.
You need a recovery tool on your computer.
https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-x.417648/
Kéno40 said:
Mega Unbrick Guide doesn't start by flashing via Fastboot.
You need a recovery tool on your computer.
https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-x.417648/
Click to expand...
Click to collapse
Yep, did that, all executed fine and situation changed from boot-loop into stuck at boot. Still only possibility is to get into fastboot.
Edit: Managed to get into recovery and sideload the original ROM there. Back on track
MrEasy666 said:
Yep, did that, all executed fine and situation changed from boot-loop into stuck at boot. Still only possibility is to get into fastboot.
Edit: Managed to get into recovery and sideload the original ROM there. Back on track
Click to expand...
Click to collapse
Lucky you. There was no way for me to get to recovery. Something was wrong there.
The only thing that really worked in the end was the Mega Unbrick Guide. I've got my phone back on track and working.
Glad you managed.
Related
This tutorial is based on the Lenovo Z5 Pro(L78031 - NO-GT version) tutorial By BadCluster
.Pre-Requirements
ADB means Android Debug Bridge, and it is software that you should always do have installed on your PC.
Pre-Requisite 1
Make sure that you have the drivers for your phone installed on your PC.
If not, you can download and install them from here https://devsjournal.com/usb-drivers-for-all-android-devices.html
Pre-Requisite 2
You must also install: Minimal ADB & Fastboot, you can download the software
from here https://devsjournal.com/download-minimal-adb-fastboot-tool.html
Scrolling through the page you will have 2 options: Download or Portable
(choose the one that you prefer)
Pre-Requisite 3
Make sure you have enabled 'USB Debugging' and OEM Unlocking on your device (read all tutorial before do it, because it will be wiped all data from the phone)
Settings -> Advanced settings -> Developer Options
Settings -> Advanced settings -> Developer Options
PAY ATTENTION: If you do not see the Developer Options menu you need to do this:
Settings -> Device Info -> tap 6 or 7 times on the 'ZUI version' entry
A pop-up should appear, telling you 'now you are a developer'
IMPORTANT NOTE: Before doing this, know that this operation completely reset your device and after rebooting, you will find the phone as if he had just left out of the box. So you'll need to configure your phone again and reinstall all apps.
.Unlock Bootloader
1) Go to: http://developer.zuk.com/bootloader_2
2) Get unlock_bootloader.img:
{
"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"
}
3) Go to your email download file:
4) After getting the unlock file put it in the same ADB folder
5) Now start the phone in bootlader by doing this:
Connect the phone to the PC
Start the Minimal ADB & Fastboot program from the PC
On the PC screen, type:
adb reboot bootloader
(A request may appear on the phone screen with permission of USB debugging, accept it)
The phone will now restart in Bootloader mode.
6) Now that you are in bootloader mode, from the PC, from the screen
Minimal ADB and Fastboot type:
fastboot flash unlock unlock_bootloader.img
sending 'unlock' (0 KB)...
OKAY [ 0.004s]
writing 'unlock'...
OKAY [ 0.019s]
7)Then type:
fastboot oem unlock-go
OKAY [ 0.019s]
8) This is very important: Ready now your bootloader is UNLOCKED however your smartphone will have BootLoop and to arrange you need to do this tutorial: HERE
Done !
----------------------------------------------------------
.How to Lock bootloader again:
IMPORTANT NOTE: Before doing this, know that this operation completely reset your device and after rebooting, you will find the phone as if he had just left out of the box. So you'll need to configure your phone again and reinstall all apps.
1) Now start the phone in bootlader by doing this:
Connect the phone to the PC
Start the Minimal ADB & Fastboot program from the PC
On the PC screen, type:
adb reboot bootloader
(A request may appear on the phone screen with permission of USB debugging, accept it)
The phone will now restart in Bootloader mode.
2) Now that you are in bootloader mode, from the PC, from the screen
Minimal ADB and Fastboot type:
fastboot flashing lock
OKAY [ 0.019s]
6) This is very important: Ready now your bootloader is LOCKED however your smartphone will have BootLoop and to arrange you need to do this tutorial: HERE
Done !
Hi,
I followed the instructions and got "FAILED (remote: Serial number not matched)"
I checked and the SN in Device Info matches the one I've used to generate the file on their site.
Any help is appreciated, thanks.
Adr215 said:
Hi,
I followed the instructions and got "FAILED (remote: Serial number not matched)"
I checked and the SN in Device Info matches the one I've used to generate the file on their site.
Any help is appreciated, thanks.
Click to expand...
Click to collapse
I updated the post, try again now
Hello
My mobile phone has only 7 digits of serial number
Do you know what to do?
yuzu1222 said:
Hello
My mobile phone has only 7 digits of serial number
Do you know what to do?
Click to expand...
Click to collapse
Thanks!
I could do it because of you tought me how to do it.
how to lock lenovo z6 pro again ?
I do not receive a mail. Tried many times with different addresses.
BlueIce84 said:
I do not receive a mail. Tried many times with different addresses.
Click to expand...
Click to collapse
same here
So you can use https://www.zui.com/iunlock instead because "http://developer.zuk.com/bootloader_2" is not working.
1IMEI wont get accepted
0z4ck said:
So you can use https://www.zui.com/iunlock instead because "http://developer.zuk.com/bootloader_2" is not working.
Click to expand...
Click to collapse
I tried the link above and when I input my 1IMEI, is say please put the right 1IMEI.. tried it a couple of times but it wont work.
Before this, my phone have a global rom and rooted.. so what I did is flashed the CN rom, relocked the booteloader to get the update, updated it to latest version then tried to unlock again the bootloader. And btw, I got the phone with unlock bootloader already..
hristcroixqwerty said:
I tried the link above and when I input my 1IMEI, is say please put the right 1IMEI.. tried it a couple of times but it wont work.
Before this, my phone have a global rom and rooted.. so what I did is flashed the CN rom, relocked the booteloader to get the update, updated it to latest version then tried to unlock again the bootloader. And btw, I got the phone with unlock bootloader already..
Click to expand...
Click to collapse
You need to insert a sim card into Sim(Slot1) and connect to the internet and wait a couple of hours. (I waited arround 6 hours)
0z4ck said:
You need to insert a sim card into Sim(Slot1) and connect to the internet and wait a couple of hours. (I waited arround 6 hours)
Click to expand...
Click to collapse
Anyone tried it? I've sold my Z5, because of no root and no custom recovery.
If there is a way to use twrp and root that works 100% I want to buy a new one
After two years I need to replace my Motorola Z2 Force...
How long will i wait for the SN.img be sent to my email.thanks.
Charlemagne Palma said:
How long will i wait for the SN.img be sent to my email.thanks.
Click to expand...
Click to collapse
edited...used gmail and it was sent instantly
i've locked the bootloader, now i'm on a bootloop with oem off, somenone can HELP PLEASE
I used you guide to lock bootlader of my Lenovo Z5 GT Pro.
As written, after bootloaderlock, I had bootloop problem, which I solved using the linked guide.
ALL perfectly working: THANK YOU!
Hi guys,
I received my Z5 with the bootloader already unlocked, but I can't lock it again. I tried the post's method, but it didn't work. When i set the command at the cmd, no message shows in the smartphone. Can someone help me?
Thanks
delete
Hello everyone,
I've been googling this for the past couple days it's been driving me crazy. Stock 7 (I think), should have been unlocked but is showing locked.
1. My friend gave me the Nexus 9 which turned off one day, then wouldn't turn on again.
2. I plugged it in, and it turned on fine. Assumed bad usb port, he said keep it. I enabled developer options, then did "OEM [bootloader?] unlock" and "USB Debugging" toggles on (from memory, may not be right phrasing)
3. While trying to back up his data on it by ADB Pull, it would randomly stop. Using it, it would reboot unexpectedly.
4. So I went to Software Update.. bad idea in retrospect probably it rebooted during or something? It was fully charged and on AC power but I wasn't watching it.
5. I come back and it keeps bootlooping. Went into recovery, says "Device Locked" - Tried clearing cache, no difference. Tried sending bootloader unlock command with fastboot, says I have to delete all data to unlock.
The only lead that I have is that it might be possible to image TWRP to recovery, then boot into it so that I can get files off it (With OTG Flash drive or USB?) - I wanted to ask for help here first.
I did my best to search for this prior, but I've been out of the ROM game since 2012 cyanogenmod days.. Hope that it's possible to save my friend's data, and then also to flash a new ROM which will solve the reboot issue.. Thanks!
Boot to recover, then when you get the Android mascot with the belly open, press ( I think vol up plus power) to get to a functional recovery with ADB support.
gk1984 said:
Boot to recover, then when you get the Android mascot with the belly open, press ( I think vol up plus power) to get to a functional recovery with ADB support.
Click to expand...
Click to collapse
Thanks GK,
After going into recovery mode, there's the android mascot with the belly open as you describe. Then, I do (VolUp+Pwr) and it produces this screen below, which I'm guessing people call "fastboot". When I'm there, my Win10 PC makes the "USB item attached" noise, and I can use fastboot commands, but adb devices won't show anything. Do you have any ideas?
{
"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 thought I could use the fastboot access I have to flash twrp, but I get the following error. I switched the "OEM Unlock" toggle, but i'm guessing that doesn't mean anything until I unlock the bootloader in recovery (which necessitates deleting all the files). I followed the directions on the twrp website which claim that root isn't needed, but I guess unlock is.
Code:
PS C:\Users\User Profile\Downloads\platform-tools_r30.0.1-windows\platform-tools> .\fastboot flash recovery twrp.img
Sending 'recovery' (13254 KB) OKAY [ 0.838s]
Writing 'recovery' (bootloader) Device State : Locked
FAILED (remote: 'Can not flash any images while device state is locked!')
fastboot: error: Command failed
Thanks again,
luciant
luciant said:
Thanks GK,
After going into recovery mode, there's the android mascot with the belly open as you describe. Then, I do (VolUp+Pwr) and it produces this screen below, which I'm guessing people call "fastboot". When I'm there, my Win10 PC makes the "USB item attached" noise, and I can use fastboot commands, but adb devices won't show anything. Do you have any ideas?
I thought I could use the fastboot access I have to flash twrp, but I get the following error. I switched the "OEM Unlock" toggle, but i'm guessing that doesn't mean anything until I unlock the bootloader in recovery (which necessitates deleting all the files). I followed the directions on the twrp website which claim that root isn't needed, but I guess unlock is.
Thanks again,
luciant
Click to expand...
Click to collapse
You need to be in recovery for adb to work. The Android with belly open is recovery but you need to unlock it with a button combo. Fastboot won't work unless you unlocked the bootloader.
I may have the steps a little off for getting to recovery but I'm sure searching how to boot to recover for the Nexus 9 will find you the right steps. It's been a long time since I've used the stock recovery on this tablet.
For future bootloopers: Well in the end, I wasn't able to figure out how to pull files using the stock HTC Nexus 9 recovery. Since it was locked, I wasn't able to install or execute TWRP .img , and unlocking it meant losing the files. It was weirdly looping even in Recovery & Fastboot. I tried every mode, and different drivers in the device manager, but ADB couldn't connect. Maybe it's not meant to for security purposes.
If you're bootlooping even in recovery, try the following:
I gave up on trying to recover the data, and decided to just unlock the bootloader. booted to Fastboot (Pwr+Vol Down on start up, select Recovery, Pwr+Vol Up, should say "Fastboot") Then I used fastboot oem unlock, which unlocked the bootloader and Deleted ALL DATA. Then, I could flash TWRP, using fastboot flash recovery twrp.img. Once I flashed TWRP, I booted to twrp recovery using Pwr+Vol Up at boot, wiped all partitions. Then I went to TWRP Advanced -> ADB sideload. Issued adb sideload ota.zip, and this gave me a clean stock install.
Thanks gk for your advice.
I have searched everywhere and have found nothing does a anyone know of a root method for the T-Mobile REVVL 4 model number 5062z
Texasblazed said:
I have searched everywhere and have found nothing does a anyone know of a root method for the T-Mobile REVVL 4 model number 5062z
Click to expand...
Click to collapse
Because phone is based on Mediatek MT6761 Helio A22 chipset you can use either MTK Easy SU or MTK-SU tool
jwoegerbauer said:
Because phone is based on Mediatek MT6761 Helio A22 chipset you can use either MTK Easy SU or MTK-SU tool
Click to expand...
Click to collapse
wrong, its a qualcomm
So can this device be rooted or not? Correct replies only would be great.
I am actively working towards it. The phone is def TCL....a lot of the package-names give that away. I installed a new Linux distro yesterday in hopes of getting to the bootloader. There might be an added advantage to loading a DSU in Developer Opyions...will update ASAP.
{
"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"
}
like this?
krayzieiyian23 said:
View attachment 5351809like this?
Click to expand...
Click to collapse
I can't get the DSU loader to work on mine. It downlaods and says it's ready so I tap on the PROCEED button or whatever and it just reboots back to my Android 11 Stock over and over.
(
I know little about Android development but I have the device it's not my daily driver so I can test stuff on it and if it goes south it's no big deal. Btw the revvl 4+ is the Qualcomm model, the 4 is the mediatek soc.
clintongsan said:
I am actively working towards it. The phone is def TCL....a lot of the package-names give that away. I installed a new Linux distro yesterday in hopes of getting to the bootloader. There might be an added advantage to loading a DSU in Developer Opyions...will update ASAP.
Click to expand...
Click to collapse
Have you had any luck on this yet???
I selected the first DSu , let it install and now the bootloader is corrupt. ( which im pretty sure means its inoperable) so the verity is definitly disabled. I can load into fastboot and baout to test the fastboot oem unlock.
clintongsan said:
I can't get the DSU loader to work on mine. It downlaods and says it's ready so I tap on the PROCEED button or whatever and it just reboots back to my Android 11 Stock over and over.
Click to expand...
Click to collapse
I was bale to let it install. You gotta downgrade to the first firmware it came with and let the DSU install. My dm-verity is corrupted which is, Im pretty sure disabled, and im able to boot into fastboot
Official Bootloader Unlock for T-Mobile REVVL 4G (TMRVL4G)
Unlock DeVops by selecting build number 5 or 6 times. get usb debugging and fastboot oem unlock. if it is not there go to about phone and select the first DSU. itll reboot and say your dm-verity is corrupted. Was then able to boot fastboot by adb reboot fastboot getting the Android with an exclamation coming out of his chest, held power vol + then pressing vol - fastbootd prompted. once your in fastbootd select reboot recovery and then youll get a recovery, fastboot and reboot selection. select fastboot and then you will be able to fastboot devices. once you get an indication your device is there then I used tiny adb with the command: fastboot flashing unlock_critical. An, are you sure? prompt in adb and press y then enter. it'll unlock the bootloader. and boot Orange_state and tell you your device is unlocked.
Anyone found a stock firmware for this yet?
sketchscarz said:
Official Bootloader Unlock for T-Mobile REVVL 4G (TMRVL4G)
Unlock DeVops by selecting build number 5 or 6 times. get usb debugging and fastboot oem unlock. if it is not there go to about phone and select the first DSU. itll reboot and say your dm-verity is corrupted. Was then able to boot fastboot by adb reboot fastboot getting the Android with an exclamation coming out of his chest, held power vol + then pressing vol - fastbootd prompted. once your in fastbootd select reboot recovery and then youll get a recovery, fastboot and reboot selection. select fastboot and then you will be able to fastboot devices. once you get an indication your device is there then I used tiny adb with the command: fastboot flashing unlock_critical. An, are you sure? prompt in adb and press y then enter. it'll unlock the bootloader. and boot Orange_state and tell you your device is unlocked.
Click to expand...
Click to collapse
I tried this with no luck.
OEM unlock and usb debugging is on.
adb reboot fastboot
This brings me to fastbootd which seems to be the only place for running fastboot commands. I tried going to recovery but theres no option to go to fastboot. I think mine is running anewer version.
fastboot oem unlock gives this error:
FAILED (remote: Command not supported in default implementation)
fastboot flashing unlock and unlock_critical gives this error:
FAILED (remote: Unrecognized command flashing unlock_critical)
Any thoughts or ideas?
mfoster978 said:
I tried this with no luck.
OEM unlock and usb debugging is on.
adb reboot fastboot
This brings me to fastbootd which seems to be the only place for running fastboot commands. I tried going to recovery but theres no option to go to fastboot. I think mine is running anewer version.
fastboot oem unlock gives this error:
FAILED (remote: Command not supported in default implementation)
fastboot flashing unlock and unlock_critical gives this error:
FAILED (remote: Unrecognized command flashing unlock_critical)
Any thoughts or ideas?
Click to expand...
Click to collapse
when yourein fastboot d, in adb type fastboot reboot bootloader
sketchscarz said:
when yourein fastboot d, in adb type fastboot reboot bootloader
Click to expand...
Click to collapse
hmm this justs boots the phone back into the android os
then select reboot to bootloader when in fastbootd
or you can hold the volume up while plugging into your computer until you get fastboot mode at the bottom of the screen, you gotta select the dsu at least once to be able to enable orange state on tmobile boot screen
let it sit there forlike 20 minutes itll say android annd ot boot for a long time.... i let it sit there for about 15-20 minutes
im trying to figure out how to make a twrp for this device ow that the bootloader is unlocked
disclaimer - sorry i really have no idea what i am doing and my goal is to just go back to my normal phone
my phone is poco f1 and now i can only access fastboot and this "powered by android" screen. fastboot into twrp doesnt work because of "boot command is not allowed in lock state" error
hello all so i tried rooting my phone and then realized that its going really badly (i have a more details about it down) so i decided to flash stock rom using techno treatment's tutorial on it but along the way i have faced a couple of problems - when trying to install drivers, program crashes, and others below
first time i flashed i got an error (timeout error in logs) , so i tried to flash again but this time i left it open for some time (at around 500 seconds i pressed flash again, in logs it shows that flashing already started) and when i came back it was at 12000 seconds still flashing so i closed miflash and am flashing once again but with a shorter folder path (desktop\xiaomi\firmware).
after this i deleted 2 lines in flash_all.bat because i kept getting stuck on echo mismatching image and device. after this everytime i try to flash i get this error - error:Erasing 'boot' FAILED (remote: 'Erase is not allowed in Lock State')
and also error:Erasing 'boot' FAILED (remote: 'Erase is not allowed in Lock State') in the other log file
and after this i tried to go into fastboot but noticed that the fastboot logo is different, it was a bunny with a hat repairing android robot but now it is android robot repairing itself
{
"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"
}
(this is what it looks now)
what i did before flashing stock - sorry my memory isnt the best this is all in a span of around 5 hours and my phone is pocophone f1. so at first i followed munchys tutorial on how to root, i succesfully enabled bootloader then in twrp i flashed recovery with some errors like failed to mount /system and 3 others like this but i ignored and continued then i installed magisk and after that in the video he goes into his phone no problem but i had "no os" and i think i just clicked around like backing up, restoring and wiping. then i thought i need a rom because its an os right? so i installed lineage and that was the last time when i could put files into my phone through usb. then i flashed the zip and after that rebooted and got "cant load android system, your data may be corrupt" so i pressed format something like that and did it a few times (i think this is when i couldnt put my files) until eventually saw that its no use so i went back to twrp and again clicked around until eventually wiping everything now i have no os and i cant transfer anything through usb.
Hi @medioqre
Seems like you are in locked bootloader state. You can not flash any ROM with locked bootloader unless you are enter EDL mode. See youtube tutorial to access edl mode for Beryllium
khusika said:
Hi @medioqre
Seems like you are in locked bootloader state. You can not flash any ROM with locked bootloader unless you are enter EDL mode. See youtube tutorial to access edl mode for Beryllium
Click to expand...
Click to collapse
Hi, to confirm - entering edl mode requires me to open up my phone right? how would i do that and how would i close it up after?
Thank you!
medioqre said:
Hi, to confirm - entering edl mode requires me to open up my phone right? how would i do that and how would i close it up after?
Thank you!
Click to expand...
Click to collapse
That's right, but i recommend go to the service center if you aren't able to do it.
khusika said:
That's right, but i recommend go to the service center if you aren't able to do it.
Click to expand...
Click to collapse
Hi again, its been 10 days.
so i have not went to a service center yet, because my city is too small for that. But i have a question. i didnt do anything else with my phone but today i decided i could do something and i booted it and i found out i can access fastboot mode and recovery mode, and in here i can see -
main menu, mi-recovery 3.0
and this one option
"connect with miassistant" which just gives me a picture of a phone if its plugged or unplugged with usb and under theres is a link to this website pcsuite.mi.com which doesnt work.
does this change my situation?
medioqre said:
Hi again, its been 10 days.
so i have not went to a service center yet, because my city is too small for that. But i have a question. i didnt do anything else with my phone but today i decided i could do something and i booted it and i found out i can access fastboot mode and recovery mode, and in here i can see -
main menu, mi-recovery 3.0
and this one option
"connect with miassistant" which just gives me a picture of a phone if its plugged or unplugged with usb and under theres is a link to this website pcsuite.mi.com which doesnt work.
does this change my situation?
Click to expand...
Click to collapse
If you are still in locked bootloader, you can't write firmware through fastboot or recovery
Why don't you try unlocking the bootloader officially?
For the last few days, I've wanted to install lineage on my phone, because the stock OS is very bad and uses 90% of the ram on idle, and it is full of bloatware and stupid issues. and the UI is not very good.
This whole post is long explaing about my failed efforts, you should read it all to avoid telling me stuff that i tried already.
What i tried?I tried using the basic way, for any android device. I got adb, and fastboot, and did the required steps. When i get into fastmode (after a whole day of fixing why my device is not detected by fastboot by the way), i tried many commands, they all DO NOT WORK in a confusing way, they are not recognized by the phone.
The following are the commands i tried, the response is always the same.
Bash:
fastboot oem unlock
fastboot flashing unlock
fastboot unlock
fastboot flashing unlock_critical
fastboot flashing get_unlock_ability
fastboot oem device-info # Yes! even this doesn't work...
And all of them give me the EXACT same response
Bash:
FAILED (remote: unknown command)
finished. total time: 0.002s # The time changes obviously
Ok then i got accross this post. According to the post, i had to use their fastboot. Which.. did not work, because it was stuck at < waiting for device >.
But i did not give up and i looked a bit through github, and i found this repository. I tried it and hopefully it detected my phone. However, the commands mentioned by the post, also gave me the same output of the previous commands, so it was not helpful.
Attempts #2So after this massive and confusing failure, i decided to try again, my friend told me i can use mediatek flash tool (stuff that i can barely understand currently) to flash TWRP, and use it to flash lineage. (Note: The Processor is MT6768)
So. i did a bit of research and i tried a few tools, for example TFTUnlock, SP Flash Tool. We managed to get the scatter file, and it should have worked... but it never did
So the problem with them is when i tried the fastboot method in TFTUnlock, it would try but also get unknown command, even the get device info button had the same problem. I tried the BROM Unlock which did not end up working, because the phone is probably not detected, when i plug it in (even while holding VOL+ and VOL-) i just hear window's sounds about device connection (actually multiple) then it continues charging, as if nothing happened. the application was still waiting for device. (and yes i got the drivers installed, and i had testmode on with driver enforcement disabled).
Wait but only one app did something different. The Smart Phone flash Tool had a special error when i connected usb (even if i do not hold VOL+ and VOL-) i had a special error, instead of just stuck at waiting. here's the error:
{
"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"
}
Other Notes
I tried both Windows 10 and Windows 11
I tried Fedora (fastboot method) and i got the same results
Flashing with fastboot will end up in error Verify State Locked
fastboot getvar command actually gives an output which includes some information, in which says that the bootloader is locked.
I did not forget to enable OEM Unlocking, in case this is on your mind
I had kaspersky on my phone which gave me a weird warning about a firmware change (although i did not success in anything). Here's the screenshot
Thanks in advance for the absolute masters who will help me get this done!
To unlock this phone's bootloader this command is the correct one
Code:
fastboot bbk unlock_vivo
If you get a confirmation message on your screen, reply in affirmative (‘Yes’, ‘I agree’, Unlock the Bootloader’, etc).
jwoegerbauer said:
To unlock this phone's bootloader this command is the correct one
Code:
fastboot bbk unlock_vivo
If you get a confirmation message on your screen, reply in affirmative (‘Yes’, ‘I agree’, Unlock the Bootloader’, etc).
Click to expand...
Click to collapse
I tried that, it says unknown command, as i mentioned already
If Fastboot returns
FAILED (remote: unknown command)
Click to expand...
Click to collapse
then the Fastboot driver you use is a wrong one, means not suitable to phone. Point.
jwoegerbauer said:
If Fastboot returns
then the Fastboot driver you use is a wrong one, means not suitable to phone. Point.
Click to expand...
Click to collapse
Sorry I've been struggling for DAYS about drivers, could you send me the right drivers for my phone?
To be on the safe side request it directly from Vivo.
vivo Support - User Guides, FAQs, Service Center, System Update | vivo Global
Home of official the vivo support services. Here you can check the service center, IMEI, query spare parts prices, system updates, FAQs, and more.
www.vivo.com
jwoegerbauer said:
Request it directly from Vivo.
vivo Support - User Guides, FAQs, Service Center, System Update | vivo Global
Home of official the vivo support services. Here you can check the service center, IMEI, query spare parts prices, system updates, FAQs, and more.
www.vivo.com
Click to expand...
Click to collapse
Interesting, but why would they provide me that? I mean, I'm not a technician or a shop I'm just a user trying to improve my personal phone
jwoegerbauer said:
To be on the safe side request it directly from Vivo.
vivo Support - User Guides, FAQs, Service Center, System Update | vivo Global
Home of official the vivo support services. Here you can check the service center, IMEI, query spare parts prices, system updates, FAQs, and more.
www.vivo.com
Click to expand...
Click to collapse
I tried using the driver but same results