LeEco Le 2 X620 (MTK 6797) Boot loop recovery - LeEco Le 2 ROMs, Kernels, Recoveries, & Other Deve

I have official 5.9.028s eui rom and i received OTA update (EUI 6)..
When the phone gone to recovery for finish the update proccedure i got an infinite loop to recovery..I cannot turn on my phone,i cannot go into recovery,the only thing that i can do is to go to fastboot but the bootloader is locked and i can't to unlock it to install twrp,because i have stock recovery..I tried to unlock the bootloader but i see this message:
(bootloader)start unlock flow
FAILED (remote: Unlock operation is not allowed)
finished. total time 3.267s
Any suggestions-help-solutions?

Related

[Q] A510: Cant unlock Bootloader

Hello,
first... sorry for my bad English.
Since yesterday my Acer A510 doesnt boot. (I have done Nothing. I used the Stock ROM)
Cannot boot into the Bootloader. The Device only enter into Fastboot.
I want to try flash CWM-Recovery, but i cant unlock the Bootloader.
"
C:\fastboot> fastboot oem unlock
...
FAILED <remote: <Unknown error code >>
finished. total time: 2.166 sec
"
Cant install any Image or update.zip, because the device says "Bootloader is locked"
Can anyone help me?

[Q] My htc one sv will only go to boot loader

so my phone froze today so I took out battery and turned it on and all it does is go to the boot loader.
So I decide to try recovery all this does is flash android logos and then back to same screen,
Next I try factory reset and same flashes to android logos and back to same screen
After reading this forum
I then go through the process of unlocking my boot loader via htc dev the process goes great I receive email etc etc
The final process should bring up a disclaimer on my screen but nothing
So my question is wtf what do I do?
Please help me
Check the guide at HTC side if you have done everything correctly, all is written how it should or copy and paste.
Without unlocked bootloader, there is no chance to rescue your phone.
Any information about your phone model and exactly the step it fails is important, too.
this problem has such a friend, and it does not solve constantly locked bootloader ...
Does anyone solved this problem?The same situation of my phone?Please help!
Hi,
i flash 2.8.4.0twrp, then make backup, after that (whit in recovery options) try to make factory reset, and after that my one sv is messed up like hell...
It is not booting...stuck for a while at htc logo, screen goes black, then loads bootloader, I am able to go to twrp (I have fresh backup of complete phone, did it with twrp above), but not able to flash anything...it fails every time, saying that is unable to mount cache...try advance wipe, but it is not able to mount any thing...
Since my phone was S-off, unlocked bootloader, superCID (it is k2ul), hboot2.0, I tryed with fastboot oem relock (to lock bootloader, and flash stock pl80img.zip) but that fails too, ends up with to many links message...and bootloader stays with tampered and unlocked sign...before flashing 2.8.4.0twrp phone was working great, but after factory reset it is not able to mount anything, and running pl80img.zip gives me all so only fail...fail...fail...
So..now i have latest twrp and totaly messed up phone...
How can U help me, anny advice???
THX in advance!
danrock1984 said:
so my phone froze today so I took out battery and turned it on and all it does is go to the boot loader.
So I decide to try recovery all this does is flash android logos and then back to same screen,
Next I try factory reset and same flashes to android logos and back to same screen
After reading this forum
I then go through the process of unlocking my boot loader via htc dev the process goes great I receive email etc etc
The final process should bring up a disclaimer on my screen but nothing
So my question is wtf what do I do?
Please help me
Click to expand...
Click to collapse
I have the same problem!!
The phone details:
Locked Bootloader
K2_UL XA SHIP S-ON RL
HBOOT 2.00.0000
T-mobile network lock
NO SuperCID
The phone doesn't boot up!
It boot to bootloader fastboot mode always!
The notification led blinks constantly!
When I wanted run the RUU (K2_UL_ICS_EUROPE...etc) the phone doesn't reboot black HTC Screen it goes back to bootloader, and it doesn't working
After I downloaded this:
https://www.androidfilehost.com/?fid=23212708291675772
After I download it rename to PL80IMG.zip and it loading after checking, and goes back to bootloader, no volume up to update option!
After I downloaded OTA_K2_UL_JB_45_S_Voda-Hutch_AU_2.14.862.9-1.17.862.9_release_3136147vue6nb55rwgyw0d.zip
After I extracted the firmware zip from it, edited the android-info.txt CID number to HTC__032 and place it to SD, rename to PL80IMG.zip after I get the same problem!
After these problems are try another method with fastboot!
fastboot flash zip flash firmware zip and I got this:
C:\Users\Erkaft\Desktop\Új mappa>fastboot flash zip firmware.zip
sending 'zip' (33772 KB)...
OKAY [ 2.668s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 5.264s
C:\Users\Erkaft\Desktop\Új mappa>
And when i want to erase all with fastboot I got this:
C:\Users\Erkaft\Desktop\Új mappa>fastboot erase all
erasing 'all'...
FAILED (remote: not allowed)
finished. total time: 0.000s
C:\Users\Erkaft\Desktop\Új mappa>fastboot erase boot
erasing 'boot'...
FAILED (remote: not allowed)
finished. total time: -0.000s
C:\Users\Erkaft\Desktop\Új mappa>fastboot erase system
erasing 'system'...
FAILED (remote: not allowed)
finished. total time: -0.000s
I also tried bootloader unlock but the last message didn't appear on the phone and it stay locked
Any idea to ressurection this phone?
You need ti unlock your phone,otherwise you can't do anything.

Cant boot into recovery, fastboot cant unlock oem

Hello Guys, I am new to the forum. I read a lot of threads, but no one i found had the solution or the exact same problem i have.
I bought a new Xiaomi Redmi 4X and wanted to install the los 14.1 Version I found here in XDA (https://forum.xda-developers.com/android/development/rom-2017-08-07lineage-14-1-t3653016). (I have installed custom roms a few times before and also faced some problems)
I flashed twrp via the fastboot mode using my linux laptop. I installed the los zip file and booted into it, but it was stuck in a boot loop. I wanted to go back into twrp, but it did not work, so i tried it with the fastboot again. Then I saw that oem is locked.
As root user i tried to unlock it with
Code:
# fastboot oem unlock
...
FAILED (remote: Token verification failed, reboot the device)
finished. total time: 0.004s
but it doesnt work.
So I am stuck now without any ROM and Recovery, I can only access to the bootloader.
I am happy for any help.

I bricked my 6x error mode

update 1 : error mode gone and when the phone starts honor logo then eRecovery
bln-l21c432b371
I was on twrp rooted unlocked bootloader so i decided to go back to stock
tried dload method not wroking 5 % failure with b371-372-374
tried with fastboot FAILED (remote: Command not allowed)
tried flashing using twrp succeeded but the phone booted into error mode but I was able to enter fastboot and eRecovery as twrp was gone
so I tried eRecovery to load stock connected to wifi but says after getting package failed
so I tried to relock bootloader to re unlock it to use fastboot without the error and I succeeded to relock it but failed to unlock it again as fastboot FAILED (remote: Command not allowed) and I was stuck in error mode with bootloader locked frp locked
waited until the battery died and I can now access fastboot and eRecovery and dload mode
tried the the 3 ways and still the same errors
and I can't get into anything
any help?????????????
.

Google Pixel bootloop Problem

Hello Everyone, I lost my hope with google pixel.
Let me tell you my problem.
1. Custom Rom installed
2. Oem unlock disabled in developer settings
3. and I accidentally locked the boot loader
4. and top of that not been able to boot into recovery because I lost it when I locked the boot loader I think
so as a result I always get this error
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.051s
I tried
flashing unlock
fastboot oem unlock
fastboot flashing unlock_critical
After 2/3 months of relentless trying I lost hope.If anyone can help please help me.
iqbal.jewel said:
Hello Everyone, I lost my hope with google pixel.
Let me tell you my problem.
1. Custom Rom installed
2. Oem unlock disabled in developer settings
3. and I accidentally locked the boot loader
4. and top of that not been able to boot into recovery because I lost it when I locked the boot loader I think
so as a result I always get this error
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.051s
I tried
flashing unlock
fastboot oem unlock
fastboot flashing unlock_critical
After 2/3 months of relentless trying I lost hope.If anyone can help please help me.
Click to expand...
Click to collapse
You can't fix it. :crying:

Categories

Resources