So here's what happened
I got a bootloop in yu yureka, i tried to enter recovery
But I didn't had a recovery (i used boot recovery to root)
So I tried many times to install recovery using the command
fastboot -i 0x1ebf flash recovery recovery.img
But i wasn't able to boot into recovery.
So I googled up and found this site
www.thetechnotriad.com/393/how-to-unbrick-yu-yureka/
Did the same and now my phone shows this type of screen
{
"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'm not even able to access fastboot)
Please Help me. (Sorry for bad English)
Update
Update:
I am now able to use fastboot (I reinstalled drivers)
But still the screen shows the same thing (those lines)
And the output of fastboot -i 0x1ebf oem device-info shows nothing in front of display panel.
Vertical lines on my yureka too!!!!!
romeovictor said:
Update:
I am now able to use fastboot (I reinstalled drivers)
But still the screen shows the same thing (those lines)
And the output of fastboot -i 0x1ebf oem device-info shows nothing in front of display panel.
Click to expand...
Click to collapse
VERTICAL LINES ON MY YUREKA TOO!!!!! Hi please FORUM MEMBERS CAn any1 suggest some help over here? Thanks!!!1
Hi
I dint face any such problem bt still i used jay kapoor's 'Yu Yureka/Yureka+ How to Root in Cm12 Lollipop Without Bricking!' video in youtube to root and install TWRP recovery , just check once.. Even check his channel for a tutorial video on unbricking yureka.. Hope it'll help you.. If not, m really sorry.
Thank you
jsakil14 said:
VERTICAL LINES ON MY YUREKA TOO!!!!! Hi please FORUM MEMBERS CAn any1 suggest some help over here? Thanks!!!1
Click to expand...
Click to collapse
Did you fix it yet ?
Same thing happened to me too!! Please help. Is it bricked permanently ?
Fix for Verticle line issue
Requirements
1. A nightly or Snapshot ROM that works on your Device.
2. THE SAME FILES THAT CAUSED THIS ISSUE(flash tool) (sry cant post links a new user here. if some can pls add the link.)
3. USB cable & Your yureka device.
STEPS
1. Extract all the contents of the flash tool & the ROM to a folder (1st the flash tool and then replace its contents with the ROM).
2. Boot your phone into FASTBOOT (volume up + plug in usb cable).
TIP: if done correctly your phone will not vibrate while turning on.
3. now run flash-all.bat
THIS WILL FIX THE ISSEUE
DID this on my YU YUREKA PLUS.(worked for me)
Long but worked in my yureka+
If u are getting blue line while booting..means u have bricked ur Yureka/Yureka+
I had the same problem in my yureka+ and none of the solutions on internet worked for me.
I made a solution of my own after a long trial and error method.
I even rebricked it and unbricked again by this method.
It is long but it works.
Requirements:
1)Flash-tools : https://github.com/YUPlayGod/factory-image-flash-tools
2)A nightly cyanogen build
(I used cm13.0 nightly of 2-nov-2016 : https://mirror.cyanogenmod.org/jenkins/185536/cm-13.0-20161101-NIGHTLY-tomato-recovery.img)
3)cm12.1 yureka/yureka+ fastboot zip
https://doc-04-78-docs.googleuserco...472/*/0B_aCRdb2PZn7ajl1N25WZjV5LTg?e=download
4)pdanet+
http://pdanet.co/a/
5)adb drivers
http://redirect.viglink.com/?format...drive.google.com/file/d/0B1S...ew?usp=sharing
Method:
Don't delete any of above zip files untill ur phone starts..
1)U have blue lines while turning on ur phone
2)Extract flashtools and cm13 nighlty in a same folder
3)Connect ur phone in fastboot mode..there are lines too but fastboot is working
4)Run flash-all.bat
Now maybe u will see that lines have disappeared but phone keeps vibrating at yu logo.
5)Now in a new folder extract cm12.1 fastboot build
6)Connect ur phone in fastboot..now next steps are most important..
1-Run flash.bat as administrator...in cmd there will be many fails and errors..just keep pressing any key when asked..when u boot ur phone..vibration will be gone but stuck at yu logo
2-Run flash.bat again as administrator..there will little less errors in cmd..but still after booting..yu logo stuck
3-Now run flash.bat without administrative privilages..no any errors in cmd..everything flashed..and phone will boot in cm12.1 yog4pas3jm
I tried this in windows 10 pc but it didn't work.
This worked in win 7 64-bit.
I made this method only by a long trial and error flashing beacuse there are many solutions on internet and i tried many of them but they didn't work.
This worked in yureka+.
Same probelom on Micromax Canvas Xpress 2 E313
Parth Gandha said:
If u are getting blue line while booting..means u have bricked ur Yureka/Yureka+
I had the same problem in my yureka+ and none of the solutions on internet worked for me.
I made a solution of my own after a long trial and error method.
I even rebricked it and unbricked again by this method.
It is long but it works.
Requirements:
1)Flash-tools : https://github.com/YUPlayGod/factory-image-flash-tools
2)A nightly cyanogen build
(I used cm13.0 nightly of 2-nov-2016 : https://mirror.cyanogenmod.org/jenkins/185536/cm-13.0-20161101-NIGHTLY-tomato-recovery.img)
3)cm12.1 yureka/yureka+ fastboot zip
https://doc-04-78-docs.googleuserco...472/*/0B_aCRdb2PZn7ajl1N25WZjV5LTg?e=download
4)pdanet+
http://pdanet.co/a/
5)adb drivers
http://redirect.viglink.com/?format...drive.google.com/file/d/0B1S...ew?usp=sharing
Method:
Don't delete any of above zip files untill ur phone starts..
1)U have blue lines while turning on ur phone
2)Extract flashtools and cm13 nighlty in a same folder
3)Connect ur phone in fastboot mode..there are lines too but fastboot is working
4)Run flash-all.bat
Now maybe u will see that lines have disappeared but phone keeps vibrating at yu logo.
5)Now in a new folder extract cm12.1 fastboot build
6)Connect ur phone in fastboot..now next steps are most important..
1-Run flash.bat as administrator...in cmd there will be many fails and errors..just keep pressing any key when asked..when u boot ur phone..vibration will be gone but stuck at yu logo
2-Run flash.bat again as administrator..there will little less errors in cmd..but still after booting..yu logo stuck
3-Now run flash.bat without administrative privilages..no any errors in cmd..everything flashed..and phone will boot in cm12.1 yog4pas3jm
I tried this in windows 10 pc but it didn't work.
This worked in win 7 64-bit.
I made this method only by a long trial and error flashing beacuse there are many solutions on internet and i tried many of them but they didn't work.
This worked in yureka+.
Click to expand...
Click to collapse
I am getting same issue as you got in yureka but I am unable to enter in fastbootmod, please help
Switch off your phone
Then connect your phone with cable
Then turn on your phone using power on button & volume + button
U may not see fastboot logo but if there are little different kind of lines and phone is on..then u are on fastboot mode
Parth Gandha said:
Switch off your phone
Then connect your phone with cable
Then turn on your phone using power on button & volume + button
U may not see fastboot logo but if there are little different kind of lines and phone is on..then u are on fastboot mode
Click to expand...
Click to collapse
I tried but not working when phone is switched on I press swith off long time then it is not switching off, does it mean that switch off button is not working and that's why I am unable to enter in fastboot mode ?
Phone won't switch off by key
U have to remove the battery from back
Then try switching on with power & volume plus..with usb cable connected
Parth Gandha said:
If u are getting blue line while booting..means u have bricked ur Yureka/Yureka+
I had the same problem in my yureka+ and none of the solutions on internet worked for me.
I made a solution of my own after a long trial and error method.
I even rebricked it and unbricked again by this method.
It is long but it works.
Requirements:
1)Flash-tools : https://github.com/YUPlayGod/factory-image-flash-tools
2)A nightly cyanogen build
(I used cm13.0 nightly of 2-nov-2016 : https://mirror.cyanogenmod.org/jenkins/185536/cm-13.0-20161101-NIGHTLY-tomato-recovery.img)
3)cm12.1 yureka/yureka+ fastboot zip
https://doc-04-78-docs.googleuserco...472/*/0B_aCRdb2PZn7ajl1N25WZjV5LTg?e=download
4)pdanet+
http://pdanet.co/a/
5)adb drivers
http://redirect.viglink.com/?format...drive.google.com/file/d/0B1S...ew?usp=sharing
Method:
Don't delete any of above zip files untill ur phone starts..
1)U have blue lines while turning on ur phone
2)Extract flashtools and cm13 nighlty in a same folder
3)Connect ur phone in fastboot mode..there are lines too but fastboot is working
4)Run flash-all.bat
Now maybe u will see that lines have disappeared but phone keeps vibrating at yu logo.
5)Now in a new folder extract cm12.1 fastboot build
6)Connect ur phone in fastboot..now next steps are most important..
1-Run flash.bat as administrator...in cmd there will be many fails and errors..just keep pressing any key when asked..when u boot ur phone..vibration will be gone but stuck at yu logo
2-Run flash.bat again as administrator..there will little less errors in cmd..but still after booting..yu logo stuck
3-Now run flash.bat without administrative privilages..no any errors in cmd..everything flashed..and phone will boot in cm12.1 yog4pas3jm
I tried this in windows 10 pc but it didn't work.
This worked in win 7 64-bit.
I made this method only by a long trial and error flashing beacuse there are many solutions on internet and i tried many of them but they didn't work.
This worked in yureka+.
Click to expand...
Click to collapse
when i run flash-all.bat file for flashing cm13.1 it gives me below error.
------[Flashing modem and bootloader]
target reported max download size of 268435456 bytes
error: cannot load 'emmc_appsboot.mbn': No error
target reported max download size of 268435456 bytes
error: cannot load 'NON-HLOS.bin': No error
target reported max download size of 268435456 bytes
error: cannot load 'rpm.mbn': No error
target reported max download size of 268435456 bytes
error: cannot load 'sbl1.mbn': No error
target reported max download size of 268435456 bytes
error: cannot load 'tz.mbn': No error
target reported max download size of 268435456 bytes
error: cannot load 'hyp.mbn': No error
-----[Flashing kernel]---
target reported max download size of 268435456 bytes
sending 'boot' (16904).....
okay [ 0.578s]
writing 'boot'...
OKay [ 0.469s]
finished. total time: 1.047s
----[Flashing recovery]--
target reported max download size of 268435456 bytes
error: connot load 'recovery.img': no error
and same for rest flash and then again two vertical lines appeares. what to do ?
i am not able to connect my yureka to pc while fastboot mode...any help...!
kapiljagtap said:
i am not able to connect my yureka to pc while fastboot mode...any help...!
Click to expand...
Click to collapse
Driver issue, probably.
What's the error?
Related
Dear developers and other users!
I have been looking for same issues but I was unable to find answer for my problem.
About a year ago I unlocked and rooted my nexus 7 tablet to use special apps on it.
Today I tried to unroot and lock my device. On my laptop the program(Nexus Root Toolkit) said it was successful so I just needed to reboot the tablet.
After rebooting it stopped on the Google screen with a "Booting failed" text on the top left corner like that:
{
"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 think I have uninstalled android from the device but I can't Intsall a new one because recovery mode doesn't work and Android is not going to boot.
I can only use Bootloader. Bootloader looks like that:
Once I started my tablet it started in bootloader mode but every other startup fails on Google screen.
Please help me to use my tablet as before without root.
What should I do and how should I do that to get it work again?
Any help would be highly appreciated
Download a factory image from here https://developers.google.com/android/nexus/images and follow this guide to flash it http://forum.xda-developers.com/showthread.php?t=1907796
[GUIDE] Flashing a Factory Image with fastboot / return to stock
Sent from my GT-I8190 using Tapatalk
Carlyle_f said:
Download a factory image from here https://developers.google.com/android/nexus/images and follow this guide to flash it http://forum.xda-developers.com/showthread.php?t=1907796
[GUIDE] Flashing a Factory Image with fastboot / return to stock
Sent from my GT-I8190 using Tapatalk
Click to expand...
Click to collapse
Thank you but I have one big problem... I wouldn't have any trouble if I could run the android os on my tablet BUT after starting up it fails to boot so I can't enable usb debugging which I need for pusshong the new firmware. I wouldn't have any problem if II could be able to access my android setting :/
But I will give a chance for everything.( I need to make my device work befora july 2 because I want to use it on my holiday )
Eurioin said:
Thank you but I have one big problem... I wouldn't have any trouble if I could run the android os on my tablet BUT after starting up it fails to boot so I can't enable usb debugging which I need for pusshong the new firmware. I wouldn't have any problem if II could be able to access my android setting :/
But I will give a chance for everything.( I need to make my device work befora july 2 because I want to use it on my holiday )
Click to expand...
Click to collapse
You don't use USB debugging or adb in fastboot to flash the factory image. Follow the link and read the instructions carefully.
#stayparanoid
Pirateghost said:
You don't use USB debugging or adb in fastboot to flash the factory image. Follow the link and read the instructions carefully.
#stayparanoid
Click to expand...
Click to collapse
Thank you It is still not working :/ in cmd after each command it writes waiting for device
Eurioin said:
Thank you It is still not working :/ in cmd after each command it writes waiting for device
Click to expand...
Click to collapse
Fix your drivers then. Fastboot is the surefire way to fix your issue.
#stayparanoid
Eurioin said:
Thank you It is still not working :/ in cmd after each command it writes waiting for device
Click to expand...
Click to collapse
Its much easier on a Linux machine. All you need to do is open terminal and type "sudo apt-get install android-tools-adb android-tools-fastboot" and hit enter. Then extract the .tar file and double click "flash-all.sh" and choose run in terminal. Absolutely no driver headaches.
If you have access to a Linux machine (mint/ubuntu) or if you can dualboot Linux, this will really help
Sent from my GT-I8190 using Tapatalk
I too have this same issue...
Exception is my Nexus is locked... everytime I try to unlock it, it tries to reboot and never comes back on...
What am I doing wrong?
Thanks for everyone I successfully made my tablet work by flashing a stock android 4.4.2
The solution:
1. I connected to my father's laptop (with Win7 on it and mine had Win8.1 so you MUSN'T try fixing on Win8.1 because of the drivers) because my laptop detected the device as undefined USB component and my father's laptop showed the tablet as Nexus 7.
2. I found a working adb&fastboot here
3. After the download is done unip the file and run RUN ME.bat and type fastboot for help
*If needed after running the RUN ME.bat file type
fastboot oem unlock
Click to expand...
Click to collapse
(this will unlock your bootloader which is necessarry
for the following steps)
4. After reconnecting my device and booting to bootloader mode and downloaded the new firmware (unzipped into the fastboot folder) type fastboot
fastboot update image-nakasi-kot49h (this was the firmware that I needed to "update")
Click to expand...
Click to collapse
5. After the fastboot started working and flashing the new OS (it takes about 5 or 10 minuntes) the tablet will restart and starts optimizing all te apps that you had before (that happened in my case).
6. If you want you can lock your bootloader by giving the fastboot this command:
fastboot oem lock
Click to expand...
Click to collapse
And now I am using Android 4.4.4 on my nexus 7 tablet
Eurioin said:
Thanks for everyone I successfully made my tablet work by flashing a stock android 4.4.2
The solution:
1. I connected to my father's laptop (with Win7 on it and mine had Win8.1 so you MUSN'T try fixing on Win8.1 because of the drivers) because my laptop detected the device as undefined USB component and my father's laptop showed the tablet as Nexus 7.
2. I found a working adb&fastboot here
3. After the download is done unip the file and run RUN ME.bat and type fastboot for help
*If needed after running the RUN ME.bat file type (this will unlock your bootloader which is necessarry
for the following steps)
4. After reconnecting my device and booting to bootloader mode and downloaded the new firmware (unzipped into the fastboot folder) type fastboot
5. After the fastboot started working and flashing the new OS (it takes about 5 or 10 minuntes) the tablet will restart and starts optimizing all te apps that you had before (that happened in my case).
6. If you want you can lock your bootloader by giving the fastboot this command:
And now I am using Android 4.4.4 on my nexus 7 tablet
Click to expand...
Click to collapse
I was hopeful that this would work for me.... I am using a win 8.1 machine and the downloaded fastboot and adb seemed to work fine.
I go to do a fastboot unlock and I get the following:
(bootloader) erasing userdata...
(bootloader) erasing userdata done...
(bootloader) erasing cache...
(bootloader) erasing cache done...
(bootloader) unlocking....
FAILED (remote: (Unknown error code))
finshed. total time: 7.902s
So..... Anyone ? The tablet does ask if I want to Unlock the Bootloader... I select yes and hit the power button to select... yet the tablet goes back to the android screen... The top of the screen says Unlocking now...... yet it doesn't...
Please help...
Hi all!!!
I'm screwed!! :crying::crying::crying:
I think I bricked the phone!
Please help!!
Backups files I already have
A-WRP is correctly installed and I made a full nandroid backup.
B-I have a full partitions backups made with Partitions Backup and Restore App (Root access required). I backup all the partitions, all of them in raw mode. All the files are *.img ready to flash with fastboot.
C-I have a full B132 ALE-L21 stock ROM that was working perfectly before.
The problem
1-adb is not recognizing the device
2-fastboot is not recognizing the device
3-I cannot enter TWRP
4-Huawei EMUI 3 buttons (volume up + volume down + on/off button) function doesn't start neither (I'm trying to force the update to B132 ROM)
5-The phone enters directly to Rescue Mode and says:
error! Func NO : 8 (hifi image) Error NO : 1 (Security verify faild!)
{
"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"
}
So the phone is still working and I got this RESCUE MODE screen but I can't do anything when this screen is displayed.
Any idea? What can I try?
Please, I really need your help, anything you can imagine to try please, let me know!!!
Thanks in advance!!!
Update:
Finally I was able to enter in FASTBOOT & RESCUE MODE following this procedure:
1-Turn off the phone
2-Connect USB cable to computer but NOT to the phone
3-Press the volume down button and hold It
4-Connect the USB cable to the phone
5-Ready, the phone will turn on automatically in this mode (DO NOT press the power button)
So, now I have fastboot but I CANNOT flash the f.....ing HIFI partition
I tried:
-fastboot flash hifi hifi.img --> command not allowed
-fastboot flash radio hifi.img --> command not allowed
-fastboot flashing unlock --> command not allowed
-I tried to enter recovery mode. I have TWRP installed, I can also flash It again with fastboot, everything good but can't access It after that!!!!
-ADB is not working
-I flash a B052 ROM, then put B132 Update.app file in SD Card root\dload and try to force update by pressing volume up + volume down + power, nothing
-I flash the B132 ROM again , then put B170 Update.zip file in SD Card root\dload and try to force update by pressing volume up + volume down + power, nothing
-I try fastboot update update.zip but It says no android-info.txt nor android-product.txt
-I try to create a flashable .zip file for fastboot but It requires .sig files for the boot, recovery and system partitions
-HiSuite open ups automatically on the computer but can't connect to phone, the phone is not recognize by HiSuite but in windows says Marshall London Bootloader Interface. I can change that to Huwaei HDB Interface, Android ADB Interface, etc. etc. in device manager. A couple of times in the phone screen refreshes saying "Rescue mode enter.." but no way, HiSuite can't connect.
I tried lastest HiSuite version v2.3.55.1 and v1.8.2.206, nothing.
So, I have fastboot, what else can I do? Can somebody help me build a .zip file flashable with fastboot?
Is there any other fastboot or tool (I tried mfastboot too) that may allow me to flash HIFI partition?
With the phone like this, which USB device shows up? (HardwareID)
Try to put phone in manual download mode.
Alferboy said:
With the phone like this, which USB device shows up? (HardwareID)
Try to put phone in manual download mode.
Click to expand...
Click to collapse
Trying to do that I get FASTBOOT & RESCUE MODE but I can't do anything. How I may enter to download mode?
loredata said:
Trying to do that I get FASTBOOT & RESCUE MODE but I can't do anything. How I may enter to download mode?
Click to expand...
Click to collapse
Fastboot should be enough.
Alferboy said:
Fastboot should be enough.
Click to expand...
Click to collapse
No way, can't flash HIFI partition.
Device is detected as Android Sooner Single ADB Interface.
I tried:
fastboot flash HIFI HIFI.img
fastboot flash hifi HIFI.img
fastboot flash HIFI hifi.img
Always the same error: FAILED <remote: command not allowed>
1.Download b052 unzip/unRAR it
2.Extract from unzipped update.app through huawei update extractor :
boot, cust, recovery, system, userdata
to the folder where u have adb
3.Start cmd in that ADB folder
4.Flash via fastboot those 5 img files
5.After flashing those files use command fastboot reboot
6. Boot phone
7. Update to latest ROM version via ota
Wysłane z mojego ALE-L21 przy użyciu Tapatalka
I have the same problem and it doesnt work... Some many line is failed in the command...
iznogoud69 said:
I have the same problem and it doesnt work... Some many line is failed in the command...
Click to expand...
Click to collapse
Try these commands:
chdir C:\adb
fastboot flash cust cust.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
fastboot reboot
PD: What the f**ck is HIFI?
Had the same problem and solved it. What I did:
1) Disconnect and power off.
2) Put a stock rom (UPDATE.APP) on SD card in folder dload and put it in the phone.
3) Connect as described above to enter FASTBOOT & RESCUE MODE
4) fastboot flash cust cust.img
5) fastboot flash recovery recovery.img
6) fastboot flash boot boot.img
7) Disconnect and power off.
8) Hold down Volume+ AND Volume- AND Power until the phone enters EMUI system update mode and stars update from the SD card.
After a few minutes: Up and running.
I cant fix my phone
Geladk said:
Had the same problem and solved it. What I did:
1) Disconnect and power off.
2) Put a stock rom (UPDATE.APP) on SD card in folder dload and put it in the phone.
3) Connect as described above to enter FASTBOOT & RESCUE MODE
4) fastboot flash cust cust.img
5) fastboot flash recovery recovery.img
6) fastboot flash boot boot.img
7) Disconnect and power off.
8) Hold down Volume+ AND Volume- AND Power until the phone enters EMUI system update mode and stars update from the SD card.
After a few minutes: Up and running.
Click to expand...
Click to collapse
I follow your steps and i cant fix my phone, at the moment of enter in EMUI system update with de 3 keys, It can't update... I only see the screen of Rescue mode
loredata said:
Hi all!!!
I'm screwed!! :crying::crying::crying:
I think I bricked the phone!
Please help!!
Click to expand...
Click to collapse
Did you solved the problem?
Geladk said:
Had the same problem and solved it. What I did:
1) Disconnect and power off.
2) Put a stock rom (UPDATE.APP) on SD card in folder dload and put it in the phone.
3) Connect as described above to enter FASTBOOT & RESCUE MODE
4) fastboot flash cust cust.img
5) fastboot flash recovery recovery.img
6) fastboot flash boot boot.img
7) Disconnect and power off.
8) Hold down Volume+ AND Volume- AND Power until the phone enters EMUI system update mode and stars update from the SD card.
After a few minutes: Up and running.
Click to expand...
Click to collapse
I have the exactly same problem.
I got 'remote: Command not allowed' when I flash the 3 .img files.
But it says that PHONE unlocked.
Could you let me know how to fix it?
sbihero said:
I have the exactly same problem.
I got 'remote: Command not allowed' when I flash the 3 .img files.
But it says that PHONE unlocked.
Could you let me know how to fix it?
Click to expand...
Click to collapse
You can try this method via HiSuite
greatslon said:
You can try this method via HiSuite
Click to expand...
Click to collapse
seriously? chinese?
I HAVE THE SAME PROBLEM AND ICAN NOT SOLVE IT
IHAVE ROOTED MY PHONE BEFORE THAT IS THE guarantee IS STEEL WORKING ?
guarantee
Use this tutorial is in spanish but it worked for me
http://www.htcmania.com/showthread.php?t=1112055
Need to have unlocked bootloader.
Put your phone in fastboot mode.
Use the unziped file you just downloaded.
Run it, it does all for you, instructions are in spanish, but you can figure it out.
Regards
Unlock bootloader
HUSSENISAM said:
I HAVE THE SAME PROBLEM AND ICAN NOT SOLVE IT
IHAVE ROOTED MY PHONE BEFORE THAT IS THE guarantee IS STEEL WORKING ?
guarantee
Click to expand...
Click to collapse
rubentkato77 said:
Use this tutorial is in spanish but it worked for me
http://www.htcmania.com/showthread.php?t=1112055
Need to have unlocked bootloader.
Put your phone in fastboot mode.
Use the unziped file you just downloaded.
Run it, it does all for you, instructions are in spanish, but you can figure it out.
Regards
Click to expand...
Click to collapse
Hi,
Do as rubentkato77 told, unlock bootloader eve if it tells you that is already unlocked. Be sure you have it unlocked by you, then follow the procedure as rubentkato77 told you. It is working like a charm. I have done this already for quiet some time.
Cheers.
My Huawei P8 GRA-UL00 Stuck in RESCUE MODE screen, please HELP ME!!
CristiMCI said:
Hi,
Do as rubentkato77 told, unlock bootloader eve if it tells you that is already unlocked. Be sure you have it unlocked by you, then follow the procedure as rubentkato77 told you. It is working like a charm. I have done this already for quiet some time.
Cheers.
Click to expand...
Click to collapse
awais awais said:
Click to expand...
Click to collapse
awais awais said:
Click to expand...
Click to collapse
First and foremost, this is P8 Lite section of the forum.
Did you followed unlocking bootloader procedure for P8? Be sure you have unlocked bootloader, otherwise do it again and retry to flash those 4 files extracted with "Huawei Update Extractor" from FULL APP ROM image specific for your P8 GRA-UL00.
BTW, I have used Fedora Linux v23 to make all the Android moves, never Windows because it fails big time. +1 for Linux :good:
Sorry mate, I don't own a P8, but a P8 Lite. Cheers.
I have the same error How can i fix it?
You may be have got attracted to those new roms out there on the internet and would have probably bricked your device.Or maybe did some modding and in worst case somehow your phone bootlooped.
so please follow the guide for unbricking or solving bootloop issues:
CAUTION:
[1] FIRST OF ALL, I AM NOT RESPONSIBLE FOR ANY DAMAGE TO YOUR DEVICE.
[2] NEVER UNPLUG THE USB CABLE WHILE FLASHING IS IN PROGRESS.IT MIGHT PERMANENTLY BRICK UR DEVICE..
ONLY FOR ZENFONE 5,A501CG/00CG
download the required files:
[1] kitkat firmware: for zenfone5(a501cg/00cg only other zf5 users download appropriate firmware from asus support page): http://dlcdnet.asus.com/pub/ASUS/ZenFone/A500CG/UL-ASUS_T00F-WW-2.21.40.44-user.zip
[2] adb/fastboot files: from here
[3] device drivers:if you do not have device drivers download and install pc link on pc from asus website,it will automatically install device drivers on your pc.(download from: http://liveupdate01.asus.com/pub/ASUS/LiveUpdate/Release/ZenFone/APP/LinkRim/PCLinkSetup.exe)
IF U R BRICKED PROCEED FROM STEP 2 ELSE FOR BOOTLOOP START FROM STEP 1:
step 1] try booting into recovery and perform a factory rest and wipe cache if this solves the bootloop(in most cases it should).if it still bootloops then follow the following tutorial
step 2]extract the fastboot files on the desktop and paste the firmware(it will be in .zip)in the fastboot folder
step 3]after copying the firmware also extract and copy the recovery.img and fastboot.img file from the firmware into the fastboot folder. (don't remove original firmware zip)
now your fastbootfolder should contain fastboot files+recovery.img+fastboot.img+firmware you dowloaded(compressed in .zip)
step4]boot into the fastboot by switching off the phone and powering it on by power+vol up key until asus logo comes up
if u r returning from some other rom u need to relock the bootloader so scroll some below to see how to relockbootloader.
step5]once you booted to fastboot ,open command promt in fastboot folder (downloaded earlier) by pressing right click+shift in any blank space on folder screen and selecting open command promt here.
in cmd write:
step6]
Code:
fastboot flash fastboot fastboot.img
step7] fastboot reboot-bootloader
wait until reboot is complete then write
step8]
Code:
fastboot flash recovery recovery.img
fastboot reboot-bootloader
step9] now we will be erasing data and cache for a clean flashing
Code:
fastboot clear data
fastboot clear cache
both of them take time and screen may turn off to save power so don't panic
next use volume keys to navigate to recovery and select it using power key .once your phone boots up showing android with belly open symbol press and hold volume up+volume down until recovery menu appears.if that does not open recovery try this:
hold volume down button, click and release vol up button,,,then finally release vol down button.
i admit it brothers,,it is sometimes really difficult to boot into recovery...but keep trying,,it is a bit difficult but is fruitful
if it doesnt appears it may be due to unssucceful flashing, unplug usb cable,force switch off phone by holding power button for few seconds.now again boot in bootloader by power button and vol up key and repeat from :step[8]
once in recovery select apply update from adb
step10] write on cmd
Code:
adb sideload <downloaded firmware name>.zip
for convenience you can rename firmware to kk.zip or any thing you like so command will be adb sideload kk.zip(it may take 15 to 20 mins)
step 11]once thats done select wipe data and cache in recovery and at last select reboot from recovery menu(dont skip this else you may face freezing on welcome screen itself)
hopefully you will boot into homescreen and be patient first bootup may take upto 20 mins.
[UPDATE] HOW TO RELOCK BOOTLOADER{only for zenfone 5 other device users pls google the procedure}
(USE THIS ONLY IF U R RETURNING FROM ANY CUSTOM ROM ITS NOT NEEDED FOR BOOTLOOPING PROBLEM)
hi guys i know u will be needing to relock the bootloader while returning to stock rom..
so what u have do is use the following steps before flashing fastboot.img that is before STEP [5] mentioned above
[1] download this file (its a zip file extract it using password zenfone-five.blogspot.com)...(link=https://drive.google.com/file/d/0B0o7qWuG7vvVRE9CV0hJWGRJS2c/view?usp=sharing)
[2]follow the on screen instructions
after the bootloader is locked carry on the steps from step[5]
PLEASE NOTE---THE UNLOCKING/LOCKING TOOL PROVIDED ABOVE IS NIETHER WRITTEN NOR OWNED BY ME...ALL CREDIT GOES TO ITS RESPECTIVE DEVELOPERS
this method can be used for:
1]unbricking
2]returning to stock rom
3]bootloop issues
IF YOU ARE NOT ABLE TO BOOT INTO FASTBOOT(maybe stuck on usb logo)--see this: http://www.asus.com/zentalk/forum.php?mod=viewthread&tid=33800 it is written by asus guys and will help you
thanks
if you face any issue please ask in comments...........
sources and credits===== www.windroidica.in
SCREENSHOTS DISCRIPTION:
pic 1] sideloading in progress
pic 2] the screen you will get when u will perform step [10] ( ignore the error "can't open /tmp/update-script.log")
pic 3]sideloading in progress (ignore the error: "please upgrade to newest 4.3 first")
pic 4] sideloading complete
NOT HITTING THANKS WILL LEAD TO A ZOMBIE APOCLYPSE(JUST KIDDING) ........dont forget to hit thanks!!!!
{
"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"
}
Kitkat link isn't working. Can I download it from another site? (Yes, it is a beginner problem )
DogeLordTR said:
Kitkat link isn't working. Can I download it from another site? (Yes, it is a beginner problem )
Click to expand...
Click to collapse
I wonder why it isn't working..... Yes u can download it from other sources. I will update the link as soon as possible...
update= download link working now...i omitted a "/" symbol and that gave the error
reserved----
AWESOME
Thanks for solution dude! You rock!
DogeLordTR said:
Thanks for solution dude! You rock!
Click to expand...
Click to collapse
Thanks bro... Ask for help anytime
hi, i have follow all the step, but until adb sideload <filename>.zip, it say at command prompt "error: device not found"
Now the phone stuck at asus logo.. :crying::cryinglease help......
zldjian said:
hi, i have follow all the step, but until adb sideload <filename>.zip, it say at command prompt "error: device not found"
Now the phone stuck at asus logo.. :crying::cryinglease help......
Click to expand...
Click to collapse
already solved the problem by using the method on this thread..
http://forum.xda-developers.com/zenfone-5/help/config-factory-partition-backup-t3316469
zldjian said:
already solved the problem by using the method on this thread..
http://forum.xda-developers.com/zenfone-5/help/config-factory-partition-backup-t3316469
Click to expand...
Click to collapse
great you have your problem solved,the error you were facing due to wrong drivers.
Cant boot recovery mode..
I am not able to boot into recovery mode..
rsunilkumar92 said:
I am not able to boot into recovery mode..
Click to expand...
Click to collapse
provide me more details. is it after flashing recovery.img? what is opening instead of recovery?
[email protected] said:
provide me more details. is it after flashing recovery.img? what is opening instead of recovery?
Click to expand...
Click to collapse
when i select recovery in bootloader, device will restart and stuck with the very frst logo.... "ASUS & Android Logo"
rsunilkumar92 said:
when i select recovery in bootloader, device will restart and stuck with the very frst logo.... "ASUS & Android Logo"
Click to expand...
Click to collapse
whats the current installed recovery?
[email protected] said:
whats the current installed recovery?
Click to expand...
Click to collapse
i tried TWRP ond also stock recovery
rsunilkumar92 said:
i tried TWRP ond also stock recovery
Click to expand...
Click to collapse
then try a guide on the forums by the name "de-brick with ruined partitions" i dont remember correctly but you'll find it easily
After trying to flash the latest 7.1.1 cm 14 ropms many people ended up in bootloop where your phone switch on ,shows mi logo and rebbot again. Many where not able to enter recovey mode also.. Now i come up with a perfect soluton for you all on how to fix these issues in your phone..Lets Get started..
If anything goes wrong iam not responsible.Do it At your Own Risk.
Requirements
------------------
1. Enter edl .rar (attached below)
2.Miui Stock Rom (FastBoot). Download it from(only use this version) here
3.Phone Must have Charge of 50% or more.
4.Unlock Boot loader.zip (Attched Below)
6.MIPhone Tools and install it .Get it from here
6.Extract all the file
7. PDA Net.(Optional,but installing will be useful). Get it from here
Once you have all of the file we can move on
Steps
------
1. Put Your Phone into fastboot mode by pressing Vol Down and power button at same time.
2.Connect your Phone With Your PC
3.Run EDL Mode.exe from the zip Enter edl.. Now your phone must be in edl mode. You can see a light blinking at the top of your phone.
4. From the Unlock Boot Loader folder copy "emmc_appsboot.mbn" to the rom folder ie)
kenzo_global_images_V7.1.8.0.LHOMICL_20160129.0000.14_5.1_global--> images--> paste it there (replace/overwrite if existing)
5. Once the above step is done, Open MIFlash tool as administrator. Browse the folder
kenzo_global_images_V7.1.8.0.LHOMICL_20160129.0000.14_5.1_global and select it..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
6.From the drop Down Menu Select Advanced.
7.Set Fastboot Script As Flash_ALL.Bat.
8.Set Flash Programmer As prog_emmc_firehose_8976_ddr.mbn from images folder.
9. Set RAW Xml File as rawprogram*.xml from images folder
10. Set Patch XML File as patch*.xml from images folder.
11. Video Help HERE.... Watch from 2.40 (Ignore the other portion,We dont need that Part)
Special [email protected] for the video.. I didn't made that video..
12. Once The Above step is done. Click REFRESH OPTION,and you will see Phone detected By The Name COMXX.(XX will be a number)
13.Click Flash and Wait for some time and allow the phone to reboot.
14.Once all the step is done your phone will be good to use..:fingers-crossed: :fingers-crossed:
UNLOCKING BOOT LOADER AND INSTALLING TWRP AGAIN
-------------------------------------------------------------------------
1.Once Your Phone Reboots successfully enable USB Debugginf From Developer Option.
2.Connect Your phone to your PC and Open CMD as administrator.
3.Type in "adb devices".
4. Cmd will show a random number and Device (Everyone will be knowing this,but for info only iam writing it here)
5.Type "adb reboot bootloader". Now your phone will boot into fastboot mode.
6.Type "fastboot oem device-info" to get device status.
7.Type "fastboot oem unlock-go" to unlock bootloader.
8.Again type "fastboot oem device-info" to check to find if device is unlocked.(Do not reboot YET)
9. Now Downlaod TWRP from HERE
10. Now Got to the folder containig TWRP . By holding the Shift Key Of key Board ,right click the mouse and select OPEN COMMAND WINDOW HERE.
11. Type "fastboot flash recovery recovery_filename.img"
12.Type "fastboot reboot".
You Phone will be good to go. If anything goes wrong or you have any doubt Comment Below do not pm me..i will not reply..
If this thread helpef you thumbs up and do comment and shre this post
So i do not need to unlock the boot loader before using MiTool to flash phone via EDL
ahh988 said:
So i do not need to unlock the boot loader before using MiTool to flash phone via EDL
Click to expand...
Click to collapse
Nope if phone is bricked enter fastboot mode and run enter edl.exe to enter edl,flash ROM using mi flash tool
adithyan25 said:
Nope if phone is bricked enter fastboot mode and run enter edl.exe to enter edl,flash ROM using mi flash tool
Click to expand...
Click to collapse
I did that but phone is still stuck . I'm getting infinite boot animation ?
ahh988 said:
I did that but phone is still stuck . I'm getting infinite boot animation ?
Click to expand...
Click to collapse
Boot animation or simply mi logo and then vibrating and again rebooting???
If mi flash tool shows successfully done without any errors then
Try this
Roeboot to fast boot and type
fastboot oem unlock-go
I guess it will be fixed
adithyan25 said:
Boot animation or simply mi logo and then vibrating and again rebooting???
If mi flash tool shows successfully done without any errors then
Try this
Roeboot to fast boot and type
fastboot oem unlock-go
I guess it will be fixed
Click to expand...
Click to collapse
I am stuck at boot animation with the three white dots spinning for ever ? will try to do as you said
I tried fastboot oem unlock-go but i get response: token verification failed and device still stuck on bootanimation
well, i think this caused by relocking bootloader after we flash a new firmware. if that happens, just go in fastboot mode by hold power button + volume down, then unlock it again using mi unlock. reboot it..your twrp is back.
no need to enter edl mode & install twrp again, btw thanks..this is helpful
nitephoenix said:
well, i think this caused by relocking bootloader after we flash a new firmware. if that happens, just go in fastboot mode by hold power button + volume down, then unlock it again using mi unlock. reboot it..your twrp is back.
no need to enter edl mode & install twrp again, btw thanks..this is helpful
Click to expand...
Click to collapse
always my pleasure
For some mi unlock stucks at 50%.. I was one of them...every time I try fails...so I found this was the only way for those who can't access it using mi unlock
tips to avoid relocking bootloader, when u want to flash a new firmware..just delete emmc apsbot.mbn file inside the firmware using winrar or etc, or u can use psy-man firmware because the emmc file has been deleted
nitephoenix said:
tips to avoid relocking bootloader, when u want to flash a new firmware..just delete emmc apsbot.mbn file inside the firmware using winrar or etc, or u can use psy-man firmware because the emmc file has been deleted
Click to expand...
Click to collapse
Yeah...I know that...but it does not support volte. .only abhisheks fw sprt volte
nitephoenix said:
tips to avoid relocking bootloader, when u want to flash a new firmware..just delete emmc apsbot.mbn file inside the firmware using winrar or etc, or u can use psy-man firmware because the emmc file has been deleted
Click to expand...
Click to collapse
@nitephoenix
Can we then flash update marshmallow global firmware this way? (Just delete emmc apsbot.mbn file inside the firmware). Thanks
Pleroma said:
@nitephoenix
Can we then flash update marshmallow global firmware this way? (Just delete emmc apsbot.mbn file inside the firmware). Thanks
Click to expand...
Click to collapse
don't flash official miui from twrp (you better do it in edl mode), but yes you can flash custom miui like miui eu, miuipro, multirom, epic miui etc from twrp. and..after u delete the emmc file inside the firmware which is included on every miui rom, your bootloader will be safe
nitephoenix said:
don't flash official miui from twrp (you better do it in edl mode), but yes you can flash custom miui like miui eu, miuipro, multirom, epic miui etc from twrp. and..after u delete the emmc file inside the firmware which is included on every miui rom, your bootloader will be safe
Click to expand...
Click to collapse
I used to flash it via twrp ..(by deleting bootllader file) followed by flashing lazyflasher...I didn't faced any prblm yet
Mine behaves different
I tried restoring the backup it started to back up and completed sucessfully but when i reboot there comes Mi logo and again it boots to TWRP Recovery .... Same case with any ROM ... Kindly tell me what to do.
ZCX recovery i have.
sarabeshsab said:
I tried restoring the backup it started to back up and completed sucessfully but when i reboot there comes Mi logo and again it boots to TWRP Recovery .... Same case with any ROM ... Kindly tell me what to do.
ZCX recovery i have.
Click to expand...
Click to collapse
Probably the problem with bootloader file
not a whole lot of talk anywhere else so i'll try here. i just got my kenzo few days ago, jumped the gun and started trying to get twrp on it. i'm assuming the bootloader was locked. As of right now it wont boot up, its in edl mode maybe... red led flashes and i can upgrade driver to 9008. sometimes its recognized by miflash and when it is and i try to flash stock fastboot it gives me an error. i know thats a lot to take in but i'm trying to cover all my bases. the phone came from overseas so sending it back isnt really an option. any help is appreciated.
Jjleininger said:
not a whole lot of talk anywhere else so i'll try here. i just got my kenzo few days ago, jumped the gun and started trying to get twrp on it. i'm assuming the bootloader was locked. As of right now it wont boot up, its in edl mode maybe... red led flashes and i can upgrade driver to 9008. sometimes its recognized by miflash and when it is and i try to flash stock fastboot it gives me an error. i know thats a lot to take in but i'm trying to cover all my bases. the phone came from overseas so sending it back isnt really an option. any help is appreciated.
Click to expand...
Click to collapse
Download eiter China based ROM or ROM from post.
Mi flash tool have many prolems.
Some tips:-
Make sure driver enforcement is disabled in PC.
All drivers including PDA net is installed.
Copy paste the unlocked bootloade file inside images folder and replace original one. Even after tryig this method it fails try my other method unbrick viafasrboot
uhm, this does not work for some reason...
i did everything as you said but in the end it just says cathasrophic error and something
After flashing i get Mi logo, vibration and reboot, please help
I've been following this guide with the aim of installing lineageos on a 6T I just bought: https://lineageosroms.com/fajita/#installation.
I downloaded the following files in advance:
copy-partitions-20200903_1329.zip
lineage-18.1-20211230-nightly-fajita-signed.zip
lineage-18.1-20211230-recovery-fajita.img
I have followed all the steps up to and including steps 6 of part 'Temporarily booting a custom recovery using fastboot'. The last part that appeared to run successfully was step 5 e.g.: fastboot flash boot lineage-18.1-20211230-recovery-fajita.img
Here is the output of the commands run on the host (serial number redacted):
adb reboot bootloader
➜ fastboot devices
******* fastboot
➜ fastboot oem unlock
OKAY [ 0.036s]
Finished. Total time: 0.036s
➜ adb reboot bootloader
➜ fastboot devices
******** fastboot
➜ fastboot flash lineage-18.1-20211230-recovery-fajita.img
unknown partition 'lineage-18.1-20211230-recovery-fajita.img'
fastboot: error: cannot determine image filename for 'lineage-18.1-20211230-recovery-fajita.img'
➜ fastboot flash boot lineage-18.1-20211230-recovery-fajita.img
Sending 'boot_a' (65536 KB) OKAY [ 1.543s]
Writing 'boot_a' OKAY [ 0.332s]
Finished. Total time: 1.973s
➜ fastboot devices
******** fastboot. ### This is where I just see the message about the OEM being unlocked and integrity.
➜ adb sideload copy-partitions-20200903_1329.zip ## I ran this even though I just saw the integrity message in the hope it would then enable me to select 'Apply Update'.
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
➜ fastboot devices
******** fastboot
NB I once accidentally wrote fastboot flash lineage-18.1-20211230-recovery-fajita.img instead of fastboot flash boot lineage-18.1-20211230-recovery-fajita.img (i.e. I missed off the 'boot'). However, as I got the immediate error "fastboot: error: cannot determine image filename for 'lineage-18.1-20211230-recovery-fajita.img'" I suppose it was a no-op and hopefully didn't do any harm.
The problem is that when I then booted into the phone with volume down and power (step 6) I just got a screen with a message about the OEM being unlocked and phone integrity.
I powered the phone off after waiting a while with volume up and power. Then powered on. Same message. Since then I've tried powering off and on with both volume up and volume down and power. I get into a mode where I can select start, restart boot loader, recovery mode and power off.
{
"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 I understood I'm trying to get into 'recovery mode' I selected that, but that just restarts the phone. I think that just took me back to the integrity message and at that point I ran the command adb sideload copy-partitions-20200903_1329.zip in the hope it would bring up the option to apply the update. However, now whenever I restart the phone I don't see the integrity message, just the 'options' menu (please see 'start' option above). I don't see the OEM unlocked/integrity message any more regardless of how I start the phone.
I have now tried basically all the options including restart the bootloader. All lead back to the same screen. When I have the phone connected to my mac via usb, I can still at least see it with fastboot devices:
fastboot devices
******** fastboot
As the guide I'm following doesn't show what you ought to see at each step I'm not sure what should have happened on step 6 when booting into recovery mode (this is my first flash) but as the guide says
'On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.' I'm guessing it should at least have booted into a UI different to the one I'm seeing.
Is there anything I can do now? Should I try flashing another recovery image? Re running anything? Is it 'bricked'?
Really appreciate any guidance.
PS one thing I've noticed is that the instructions of 6T (https://lineageosroms.com/fajita/#installation) say we should run
fastboot flash boot <recovery_filename>.img
whereas the instructions for earlier and later models of the one plus (and other brands) say to run
fastboot flash recovery <recovery_filename>.img
Of course this might be correct, but does anyone know if this is a mistake in the instructions - i.e. should it have been 'recovery' not 'boot' for the 6/6T?
---- EDIT -----
Having looked up some documentation on fastboot (which say the structure of the command is basically fastboot flash <partition> <filename>) and then read around a bit on partitions on Android phones, I'm getting the impression android phones pretty much always have a recovery partition, which would make me think that the 'boot' command is indeed wrong. That said, I've got next to no experience with this so it's hard to be sure that the command isn't correct for some reason I'm not aware of, that only pertains to a few generations of phones.
Anyone?
--- EDIT 2 ----
The maintainers of the wiki.lineageos.org have confirmed to me that the line fastboot flash boot <recovery_filename>.img is written as intended. So still at square one.
Any ideas, anyone?
FWIW I got there. In case it helps anyone to know any of the sordid details, first I flashed back the stock ROM using this thread. Worked pretty much as described albeit I had to unzip the images folder and move the bat file into it so it found the images (first had to get hold of a windows machine).
Once I had it installed again I took an android update on the device. I think it highly likely that this was the cause of the original issue reported above - following the lineageOS wiki would probably have worked from that point, but I never found out as I decided I wanted TWRP anyway and used that as my custom recovery instead. That said, I now realise I could just as well have only installed TWRP after flashing lineage, as flashing LineageOS wiped TWRP.
BTW, I really can't fathom why I either didn't clock or ignored the message about making sure you're on the latest 11 firmware (in a red box!) at the top of the lineageOS install wiki. I don't remember seeing it but perhaps I just thought it would be fine as it was a 'fresh' phone (that had probably lying in a box for a year or so). Anyway, lesson learned.
Had to scramble over some other issues, involving booting a temp 'test' TWRP from crdroid first before flashing the official one, described around this page. I also had an odd 'no system' message in TWRP after wiping the existing system (following these instructions to check which bits to wipe when using TWRP before flashing a custom ROM). Anyone reading might want to check those instructions by asking on a lineageos forum if it makes sense to wipe 'system' on TWRP before flashing the lineage ROM - as I got a message after flashing lineage (in TWRP, before rebooting) that there was no 'system'. However it rebooted (with an error re corrupt user data that I was able to fix just by allowing lineage to wipe the user data again), so it's hard to see how that report of there being no system can have been strictly accurate.
But. I. got. there.
PS now I remember why I didn't see the warning to update the firmware. I was (unknowingly) viewing a repost (on lineageosroms) rather than the original wiki (on wiki.lineageos.org). Beware
i have the same thing but on a newer phone, my pc cant see it so im stuck here for now