Related
Hello xda community, I'd like to start with saying all the work done on this forum for open-source, freeware, and general android tweaks is awesome! Thank you.
So awesome in fact that I got a little bit ahead of myself with my new "Sprint HTC One". I followed this guide http://forum.xda-developers.com/showthread.php?t=2244060 to Unlock the bootloader, and root my phone. I then went a step further and wanted to flash a custom Rom. I followed this video, but strayed a little bit (whoops!). I went into twrp recovery, and flashed the "Beanstalk" super custom 4.3 (9/24/2013), along with smw6180_superwipe, and 4.3 gapps.
This actually was working for about 4 days, but now it won't connect to the mobile network even when toggling on and off airplane mode (A temp fix for the ROM). I went ahead and looked for solutions, namely to just get back to stock to see if the problem is bigger than just custom ROM. I relocked my bootloader, following http://www.youtube.com/watch?v=0WWNZpaQBh8&list=PLE395F615E026133D&index=11 Thus running into my current issue of Error 140 when trying to flash the RUU.
I'm asking anyone that could help, to offer suggestions on getting my phone back to stock. I would also like a couple suggestions for more stable ROM's (again, i knew what i getting into; ie disclaimers) that offer cool customization!
did you put the stock recovery back on before you locked the bootloader? Also are you super cid?
olorolo said:
did you put the stock recovery back on before you locked the bootloader? Also are you super cid?
Click to expand...
Click to collapse
No i don't believe so, Well now its not even going into twrp recovery. It displays tampered relocked security warning, s-on, hboot 1.44.0000 and This is the only screen i have for fastboot and the bootloader
I've seen this issue before let me take a quick look I think your ok
Sent from my HTCONE using Tapatalk 4
---------- Post added at 06:58 PM ---------- Previous post was at 06:57 PM ----------
You caught me in the middle of flashing the s-off firmware myself
Sent from my HTCONE using Tapatalk 4
Good to hear! Thank you for your time sir
get the newest twrp and rename it to recovery.zip put it in your cmd folder in bootloader type reboot bootloader fastboot flash flash recovery fastboot reboot
---------- Post added at 07:28 PM ---------- Previous post was at 07:18 PM ----------
once you have twrp back flash the s-off firmware http://forum.xda-developers.com/showthread.php?t=2467607 then the 4.3 rom of your choice
olorolo said:
get the newest twrp and rename it to recovery.zip put it in your cmd folder in bootloader type reboot bootloader fastboot flash flash recovery fastboot reboot
Click to expand...
Click to collapse
Either i don't understand fully or its failing. I have fastboot usb selected on my phone connected to usb on pc. I open my folder with cmd in it, and i typed what you said but error is "reboot" is not recognizable.
edit: I also have the trwp 2.6.3 image in the folder along with cmd.
Pug4567 said:
Either i don't understand fully or its failing. I have fastboot usb selected on my phone connected to usb on pc. I open my folder with cmd in it, and i typed what you said but error is "reboot" is not recognizable.
edit: I also have the trwp 2.6.3 image in the folder along with cmd.
Click to expand...
Click to collapse
twrp has to be renamed to recovery.zip try fastboot flash then type flash recovery then the name of the zip which is recovery.zip then fastboot reboot
I did that am getting error:cannot load recovery.
Also tried fastboot flash recovery openrecovery-twrp-2.6.3.0-m7wls.img
that resulted in this
sending 'recovery' (8608 KB)...
OKAY [ 1.120s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.880s
Or should i try http://forum.xda-developers.com/showthread.php?t=2314582
Pug4567 said:
I did that am getting error:cannot load recovery.
Also tried fastboot flash recovery openrecovery-twrp-2.6.3.0-m7wls.img
that resulted in this
sending 'recovery' (8608 KB)...
OKAY [ 1.120s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.880s
Or should i try http://forum.xda-developers.com/showthread.php?t=2314582
Click to expand...
Click to collapse
try hassoons all in one toolbox
I got twrp back by unlocking my phone again. Should i proceed with the 3.04.651.2 firmwre? beanstalk is now hanging on splash screen.
The phone isn't being recognized on my computer it seems, it shows as m7wls under device manager, when in twrp 2.6.3. When in bootloader it shows as One device, but neither is accessible.
Also tried flashing the s-off firmware, but got 'error cannot load firmware.zip'
Any more help would be appreciated, almost thinking of taking it back to sprint, i have a protection plan. But i would like to avoid that, im currently going to buy an otg-usb cable as well.
Hi,
I have following problem, phone is D405N:
If I boot into fastboot and try to flash some file - TWRP recovery for example I always get following error:
c:\adb>fastboot flash recovery L90.img
target reported max download size of 536870912 bytes
sending 'recovery' (13818 KB)...
OKAY [ 0.546s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.546s
Any idea where is a problem and how to fix this it? Using latest adb and drivers also.
same here
Did you tried with driver from @LaDY Vengeance post?
http://forum.xda-developers.com/lg-l90/general/guide-fastboot-l90-d415-t2827825
neverdies said:
Did you tried with driver from @LaDY Vengeance post?
http://forum.xda-developers.com/lg-l90/general/guide-fastboot-l90-d415-t2827825
Click to expand...
Click to collapse
I tried those drivers, and I have no luck. I have the same problem, except that I can't use any command, they all return FAILED (remote: unknown command)
I'm stuck in fastboot, and with this issue I can't flash the backup img's to restore it.
SOMEONE PLS HELP
jmang98 said:
I tried those drivers, and I have no luck. I have the same problem, except that I can't use any command, they all return FAILED (remote: unknown command)
I'm stuck in fastboot, and with this issue I can't flash the backup img's to restore it.
SOMEONE PLS HELP
Click to expand...
Click to collapse
what steps have you done so far?
ie: unlock/root/flash recovery?
itsJohnuno said:
what steps have you done so far?
ie: unlock/root/flash recovery?
Click to expand...
Click to collapse
Same problem....
Did anyone who was having this problem end up finding a fix?
This is a problem I have too, need a fix.
Still need a solution. Is this due to lollipop? Cuz back then I was able to unlock the bootloader. LG L90 D415
BlaMa said:
Hi,
I have following problem, phone is D405N:
If I boot into fastboot and try to flash some file - TWRP recovery for example I always get following error:
c:\adb>fastboot flash recovery L90.img
target reported max download size of 536870912 bytes
sending 'recovery' (13818 KB)...
OKAY [ 0.546s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.546s
Any idea where is a problem and how to fix this it? Using latest adb and drivers also.
Click to expand...
Click to collapse
D405_v20a_patched_aboot??
http://forum.xda-developers.com/lg-l90/development/recovery-twrp2-7-1-0lgl90w7xxshoxx-t2826150
EDIT:
Did you flash D405_v20a_patched_aboot if not, you need to flash D405_v20a_patched_aboot
i also have same poblem d415
me too...same problem D415 tmobile version
Does anyone with this problem have an lg d-415 and android with root? Because I think these commands in a terminal emulator or in an adb shell will fix fastboot:
Code:
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/laf
Or if that doesn't work try this >> https://forum.xda-developers.com/lg...ick-hard-bricked-l90-variants-t3173429/page24
I think this problem is caused by people not unlocking the bootloader.
Same error on LG D415
BlaMa said:
Hi,
I have following problem, phone is D405N:
If I boot into fastboot and try to flash some file - TWRP recovery for example I always get following error:
c:\adb>fastboot flash recovery L90.img
target reported max download size of 536870912 bytes
sending 'recovery' (13818 KB)...
OKAY [ 0.546s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.546s
Any idea where is a problem and how to fix this it? Using latest adb and drivers also.
Click to expand...
Click to collapse
PLEASE HELP. I'm getting the same error on my LG D415. They said on the other thread that this variant comes with the bootloader already unlocked but whenever i try to enter a command (e.g fastboot flash laf laf.img) or pretty much every command I enter (except fastboot getvar all and fastboot devices), I get the same message FAILED (remote: unknown command). My android is now stuck on the T-mobile logo whenever I try to power it up and I can't flash because download mode has been replaced with fastboot.
aixhinnn said:
PLEASE HELP. I'm getting the same error on my LG D415. They said on the other thread that this variant comes with the bootloader already unlocked but whenever i try to enter a command (e.g fastboot flash laf laf.img) or pretty much every command I enter (except fastboot getvar all and fastboot devices), I get the same message FAILED (remote: unknown command). My android is now stuck on the T-mobile logo whenever I try to power it up and I can't flash because download mode has been replaced with fastboot.
Click to expand...
Click to collapse
How did you enable fastboot, what commands did you run?
0000.0000.00 said:
How did you enable fastboot, what commands did you run?
Click to expand...
Click to collapse
i followed this guide
https://forum.xda-developers.com/lg-l90/general/guide-unlock-bootloader-t-mobile-l90-t2836457
but once I was already in fastboot no other commands work.
aixhinnn said:
i followed this guide
https://forum.xda-developers.com/lg-l90/general/guide-unlock-bootloader-t-mobile-l90-t2836457
but once I was already in fastboot no other commands work.
Click to expand...
Click to collapse
Did you try volume down+ power to factory reset and see if that fixes it?
im having this problem too, but on an lg v10 tmobile
17mm said:
im having this problem too, but on an lg v10 tmobile
Click to expand...
Click to collapse
This problem is strange and I'm not sure if it has a solution.
0000.0000.00 said:
This problem is strange and I'm not sure if it has a solution.
Click to expand...
Click to collapse
what i did was get lg bridge and mobile support, let if flash the most current update then used this method to root on the latest 30c update https://forum.xda-developers.com/tm...901-nougat-t3773942/post76711778#post76711778
twrp flashed fine, magisk installed flawlessly, now rooted on latest official update with all kinds of goodies to play with :good:
oh and with magisk you pass safetynet aswell so all good.
Hello all!
So recently I was playing around with my G4, and decided to see if i could boot into fastboot mode. Turned out I could: theandroidsoul.com/lg-g3-fastboot-mode-61660/, but it would remove download mode in the process. It was totally useless. I couldn't run any commands and so I decided to put download mode back. I rebooted my phone, a notification caught my eye, and I completely forgot to put it back.
Fast forward a couple days, and my phone starts to run at 2 miles per hour. So, I factory reset, losing root and recovery in the process. That still didn't fix it, and now the camera, all speakers, and microphone don't work. Now, I can't replace download mode without root, so I cant run the LG Flash Tool. I'm starting to lose my mind over this. Please help!
Can your phone boot to android at all? if yes, then this might help put TWRP back on the phone WITHOUT ROOT. http://forum.xda-developers.com/tmobile-g4/development/tool-one-click-twrp-root-t3172936 thank micromod for making it possible.
MrSteelX said:
Can your phone boot to android at all? if yes, then this might help put TWRP back on the phone WITHOUT ROOT. http://forum.xda-developers.com/tmobile-g4/development/tool-one-click-twrp-root-t3172936 thank micromod for making it possible.
Click to expand...
Click to collapse
I can, but that unfortunately requires download mode, which I removed(oops).
jlynch630 said:
I can, but that unfortunately requires download mode, which I removed(oops).
Click to expand...
Click to collapse
Factory reset should have kept twrp recovery on the phone. With phone off, hold vol down and power together, when you see lg logo just release power button the hold it down again stioll holding vol down. say yes to the next 2 screens and it should boot into recovery.
MrSteelX said:
Factory reset should have kept twrp recovery on the phone. With phone off, hold vol down and power together, when you see lg logo just release power button the hold it down again stioll holding vol down. say yes to the next 2 screens and it should boot into recovery.
Click to expand...
Click to collapse
Hmm... I must have done something then, because it isn't there anymore. It just boots to the android logo and resets my phone.
jlynch630 said:
Hmm... I must have done something then, because it isn't there anymore. It just boots to the android logo and resets my phone.
Click to expand...
Click to collapse
Your only hope is to get fastboot to work then or lg service center
MrSteelX said:
Your only hope is to get fastboot to work then or lg service center
Click to expand...
Click to collapse
Heres what fastboot says:
Code:
[COLOR="Red"]FASTBOOT MODE[/COLOR]
PRODUCT NAME - msm9992_p1_tmo_us
VARIANT - msm9992_p1_tmo_us Toshiba 32GB
HW VERSION - rev-10
BOOTLOADER VERSION - N/A
BASEBAND VERSION - N/A
CARRIER INFO - N/A
SERIAL NUMBER - LGH811********
SIGNING - Production
SECURE_BOOT - disabled
LOCK_STATE - locked
[1280]
[1280] Fastboot mode started
[2780]
I think the lockstate may be why it doesn't work. Any clues to disable it?
jlynch630 said:
Heres what fastboot says:
Code:
[COLOR="Red"]FASTBOOT MODE[/COLOR]
PRODUCT NAME - msm9992_p1_tmo_us
VARIANT - msm9992_p1_tmo_us Toshiba 32GB
HW VERSION - rev-10
BOOTLOADER VERSION - N/A
BASEBAND VERSION - N/A
CARRIER INFO - N/A
SERIAL NUMBER - LGH811********
SIGNING - Production
SECURE_BOOT - disabled
LOCK_STATE - locked
[1280]
[1280] Fastboot mode started
[2780]
I think the lockstate may be why it doesn't work. Any clues to disable it?
Click to expand...
Click to collapse
Have twrp on internal storage then run
fastboot flash recovery twrp.img pray it flashes twrp and go from there.
MrSteelX said:
Have twrp on internal storage then run
fastboot flash recovery twrp.img pray it flashes twrp and go from there.
Click to expand...
Click to collapse
Ohh!! So close! It finishes writing, but then says : Failed(remote: Unknown Command)
jlynch630 said:
Ohh!! So close! It finishes writing, but then says : Failed(remote: Unknown Command)
Click to expand...
Click to collapse
in android, do u have the oem lock checked
also make sure that twrp is named twrp.img
MrSteelX said:
in android, do u have the oem lock checked
also make sure that twrp is named twrp.img
Click to expand...
Click to collapse
I didn't, but I enabled it and tried again, and it still didn't work.
try updating adb from the latest SDK. Also check to make sure your twrp download in not corrupted. then try again.
MrSteelX said:
try updating adb from the latest SDK. Also check to make sure your twrp download in not corrupted. then try again.
Click to expand...
Click to collapse
Updated adb(& fastboot) to no avail
Code:
C:\Users\21JohnL\adb>fastboot oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.016s
C:\Users\21JohnL\adb>fastboot flash recovery twrp-2.8.7.0-h811.img
target reported max download size of 536870912 bytes
sending 'recovery' (32968 KB)...
OKAY [ 0.719s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.750s
jlynch630 said:
Updated adb(& fastboot) to no avail
Code:
C:\Users\21JohnL\adb>fastboot oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.016s
C:\Users\21JohnL\adb>fastboot flash recovery twrp-2.8.7.0-h811.img
target reported max download size of 536870912 bytes
sending 'recovery' (32968 KB)...
OKAY [ 0.719s]
writing 'recovery'...
FAILED (remote: unknown command)
finished. total time: 0.750s
Click to expand...
Click to collapse
Did you make a backup of laf?
Yes, why?
EDIT: Haha! Factory reset got me again! I'll make a comment on that page and see if someone has a copy stored
EDIT 2: I found one for the G3, will that work?
jlynch630 said:
Yes, why?
EDIT: Haha! Factory reset got me again! I'll make a comment on that page and see if someone has a copy stored
EDIT 2: I found one for the G3, will that work?
Click to expand...
Click to collapse
https://www.mediafire.com/?4a8bivbgk4s1d7q this is laf from 10n. flash this in fastboot should put download mode back for you.
MrSteelX said:
https://www.mediafire.com/?4a8bivbgk4s1d7q this is laf from 10n. flash this in fastboot should put download mode back for you.
Click to expand...
Click to collapse
Which partition?
Edit:
Still get error
Code:
C:\Users\21JohnL\Downloads>fastboot flash laf "laf (1).img"
target reported max download size of 536870912 bytes
sending 'laf' (36864 KB)...
OKAY [ 0.821s]
writing 'laf'...
FAILED (remote: unknown command)
finished. total time: 0.844s
jlynch630 said:
Which partition?
Click to expand...
Click to collapse
I am not sure at this time. Still goggling the problem.
edit 1.fastboot flash laf laf.img try this.
edit 2. fastboot erase laf.img
fastboot flash laf laf.img
---------- Post added at 08:37 PM ---------- Previous post was at 08:25 PM ----------
jlynch630 said:
Which partition?
Edit:
Still get error
Code:
C:\Users\21JohnL\Downloads>fastboot flash laf "laf (1).img"
target reported max download size of 536870912 bytes
sending 'laf' (36864 KB)...
OKAY [ 0.821s]
writing 'laf'...
FAILED (remote: unknown command)
finished. total time: 0.844s
Click to expand...
Click to collapse
fastboot erase laf.img
fastboot flash laf laf.img
try that.
MrSteelX said:
I am not sure at this time. Still goggling the problem.
edit 1.fastboot flash laf laf.img try this.
edit 2. fastboot erase laf.img
fastboot flash laf laf.img
---------- Post added at 08:37 PM ---------- Previous post was at 08:25 PM ----------
fastboot erase laf.img
fastboot flash laf laf.img
try that.
Click to expand...
Click to collapse
Both return:
Code:
FAILED: (remote:unknown command)
I think something is blocking fastboot commands from running
jlynch630 said:
Both return:
Code:
FAILED: (remote:unknown command)
I think something is blocking fastboot commands from running
Click to expand...
Click to collapse
At this time, I am unable to help you out. You should get into contact with Jcase or Autoprime. They know a lot more about this and may be able to help fix this laf.
fastboot erase laf
Hello everyone, I'm new in the Android world.
I have been trying to unlock my bootloader with the sticky guide, but it doesnt work for some reason.
In the cmd (after i got into the "Device locked" screen) it gives me an error and i dont know how to fix it.
I would like to see a full working 2k17 guide for how to unlock bootloader for a Huawei P7 running android 5.1.1 with Emui 3.1
Hope someone can help me.
What error do you get?
Does it appear right after entering fastboot mode?
RangerP7 said:
What error do you get?
Does it appear right after entering fastboot mode?
Click to expand...
Click to collapse
Im getting into fastboot without problem, but when i try to unlock it gives me the (Failed to write) error? Maybe its the guide that doesnt work
What guide do you use?
Did you install your driver (HiSuite)
---------- Post added at 02:00 PM ---------- Previous post was at 01:57 PM ----------
Before you are flashing try the command "fastboot devices". Is your devices listed?
RangerP7 said:
What guide do you use?
Did you install your driver (HiSuite)
---------- Post added at 02:00 PM ---------- Previous post was at 01:57 PM ----------
Before you are flashing try the command "fastboot devices". Is your devices listed?
Click to expand...
Click to collapse
I used this guide: https://forum.xda-developers.com/ascend-p7/general/rooted-p7-l10-609-t3003605
I got HiSuite installed and updated.
It is listed as "0123456789ABCDEF fastboot" ?
F:\Overførsler\ADB Flash Tools>fastboot flash boot BOOT_EMUI3.0_619_UNLOCKED.img
target reported max download size of 536870912 bytes
sending 'boot' (8038 KB)...
OKAY [ 0.309s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.309s
So you are trying to flash a KitKat boot image on a lollipop device?
But the guid works, I rooted my device the same way
CalloDK said:
I used this guide: https://forum.xda-developers.com/ascend-p7/general/rooted-p7-l10-609-t3003605
I got HiSuite installed and updated.
It is listed as "0123456789ABCDEF fastboot" ?
F:\Overførsler\ADB Flash Tools>fastboot flash boot BOOT_EMUI3.0_619_UNLOCKED.img
target reported max download size of 536870912 bytes
sending 'boot' (8038 KB)...
OKAY [ 0.309s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.309s
Click to expand...
Click to collapse
if you have emui 3.1 you can't flash a kernel for emui 3.0
a question: is your bootloader unlocked? (in fastmode under the green robot there is written in red letters phone unlocked)
EDIT: in your first post you write that the phone is locked...so you need an unlock code from huawei site in order to unlock bootloader, otherwise you will never be able to flash kernel or recovery
use this guide https://forum.xda-developers.com/ascend-p7/general/guide-root-huawei-p7-t3311424
and at point 8-9-10 use this https://forum.xda-developers.com/ascend-p7/orig-development/recovery-t3314665
usb2 said:
if you have emui 3.1 you can't flash a kernel for emui 3.0
a question: is your bootloader unlocked? (in fastmode under the green robot there is written in red letters phone unlocked)
EDIT: in your first post you write that the phone is locked...so you need an unlock code from huawei site in order to unlock bootloader, otherwise you will never be able to flash kernel or recovery
use this guide https://forum.xda-developers.com/ascend-p7/general/guide-root-huawei-p7-t3311424
and at point 8-9-10 use this https://forum.xda-developers.com/ascend-p7/orig-development/recovery-t3314665
Click to expand...
Click to collapse
I tried to install it on 2 computers, but i dont get any desktop shortcut?
What shortcut do you mean adb/fastboot?
RangerP7 said:
What shortcut do you mean adb/fastboot?
Click to expand...
Click to collapse
It says in the guide that it will create a shortcut on the desktop, otherwise i dont know how to continue
You don't need any shortcut
Just go to the path, you installed it via cmd
How did you get it work in your first post?
RangerP7 said:
You don't need any shortcut
Just go to the path, you installed it via cmd
How did you get it work in your first post?
Click to expand...
Click to collapse
I didnt set a path, it just got installed.
I used another cmd, where i was just going to open it and run it
CalloDK said:
I didnt set a path, it just got installed.
I used another cmd, where i was just going to open it and run it
Click to expand...
Click to collapse
There schoulkd be a folder calld "adb" at C:
So open cmd "cd C:/adb"
RangerP7 said:
There schoulkd be a folder calld "adb" at C:
So open cmd "cd C:/adb"
Click to expand...
Click to collapse
I got a folder called ADB Flash Tool? Can i use that?
Yes of course
RangerP7 said:
Yes of course
Click to expand...
Click to collapse
It worked and now im rooted, thanks. But I cant find the cyanogenmod which works with P7
Because there is no one for Android L.
Or look at the developer channel, there you will find another custom roms
Hello friends!
After i tried to find a way to bypass LeEco login on the install of stock based ROM , i have bricked my phone (not really bricked, but i will tell you). On the first boot i cant complete the setup, because X527 dont detect my sim cards and shows no wifi networks (So i cant go to developer options and can not use a dial code).
After i have read a lot, im sure it was a problem with the efs or nvram (The last working boot shows no serial and no bootloader). But now im on Stock ROM and Stock Recovery and need an option to repair efs/nvram over fastboot or stock recovery, without changing anything in the phone itself.
Hope you guys can help me...
i recommend you to install twrp and flash official stock rom it has stock recovery too so it will came back to original state. we have the original stock rom here so dont afraid to install twrp.
anjel05 said:
i recommend you to install twrp and flash official stock rom it has stock recovery too so it will came back to original state. we have the original stock rom here so dont afraid to install twrp.
Click to expand...
Click to collapse
I can't install TWRP because i have to go to the developer options, but my phone can not start....
quasimodo88 said:
I can't install TWRP because i have to go to the developer options, but my phone can not start....
Click to expand...
Click to collapse
What you need in developers option? Oem unlocking and usb debugging? I thnk in our device theyre already on default
anjel05 said:
What you need in developers option? Oem unlocking and usb debugging? I thnk in our device theyre already on default
Click to expand...
Click to collapse
Yes. If i want to install twrp in fastboot mode i get this error:
PS C:\adb> fastboot flash recovery twrp-3.1.1-1-s2.img
target reported max download size of 536870912 bytes
sending 'recovery' (17244 KB)...
OKAY [ 0.562s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.578s
quasimodo88 said:
Yes. If i want to install twrp in fastboot mode i get this error:
PS C:\adb> fastboot flash recovery twrp-3.1.1-1-s2.img
target reported max download size of 536870912 bytes
sending 'recovery' (17244 KB)...
OKAY [ 0.562s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.578s
Click to expand...
Click to collapse
You have to do
U need to unlock first dude
DarknessKiller said:
You have to do
U need to unlock first dude
Click to expand...
Click to collapse
Yes i know bro. But if i try to unlock i get this message:
PS C:\adb> fastboot oem unlock-go
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.016s
quasimodo88 said:
Yes i know bro. But if i try to unlock i get this message:
PS C:\adb> fastboot oem unlock-go
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.016s
Click to expand...
Click to collapse
Did you install the drivers you need?
anjel05 said:
Did you install the drivers you need?
Click to expand...
Click to collapse
Yes i did. My phone is shown under fastboot devices.
quasimodo88 said:
Yes i know bro. But if i try to unlock i get this message:
PS C:\adb> fastboot oem unlock-go
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.016s
Click to expand...
Click to collapse
I think you are ****ed. Why oh why didn't you enable oem unlocking b4 flashing roms?
You can try
Fastboot erase modemst1
Fastboot erase modemst2
But it probably won't work cus your bootloader is locked
You can also try
Fastboot boot <insert name of your twrp img here>
But again doubt it'll work
---------- Post added at 08:31 PM ---------- Previous post was at 08:29 PM ----------
Try googling for an alternative way to unlock your bootloader
---------- Post added at 08:40 PM ---------- Previous post was at 08:31 PM ----------
Also if you can find a way to transfer files to your phone, try downloading eui 19s rom, edit the update script as needed(especially if you are downgrading), then send it to your phone /sdcard as update.zip and try to flash it through stock recovery.
Dudeonyx said:
I think you are ****ed. Why oh why didn't you enable oem unlocking b4 flashing roms?
You can try
Fastboot erase modemst1
Fastboot erase modemst2
But it probably won't work cus your bootloader is locked
You can also try
Fastboot boot <insert name of your twrp img here>
But again doubt it'll work
---------- Post added at 08:31 PM ---------- Previous post was at 08:29 PM ----------
Try googling for an alternative way to unlock your bootloader
---------- Post added at 08:40 PM ---------- Previous post was at 08:31 PM ----------
Also if you can find a way to transfer files to your phone, try downloading eui 19s rom, edit the update script as needed(especially if you are downgrading), then send it to your phone /sdcard as update.zip and try to flash it through stock recovery.
Click to expand...
Click to collapse
Fastboot erase... and fastboot boot... i have already tried.
Fastboot sideload... i have tried too, but im not sure if i do it right. I think my last chance is to try it over an otg cable, right?
quasimodo88 said:
Fastboot erase... and fastboot boot... i have already tried.
Fastboot sideload... i have tried too, but im not sure if i do it right. I think my last chance is to try it over an otg cable, right?
Click to expand...
Click to collapse
Any luck on googling a way to enable oem unlocking without access to developer options?
Or you can treat your phone as if it was bricked. Try downloading the sparse or Qfil file (not sure which is used for unbricking) for your model. And flashing through flashone or Qfil. Google or search xda for steps on how to unbrick this particular phone or Qualcomm phones in general. I believe it involves a step where you hold vol+, vol- & power key.
Anyway goodluck.
Dudeonyx said:
Any luck on googling a way to enable oem unlocking without access to developer options?
Or you can treat your phone as if it was bricked. Try downloading the sparse or Qfil file (not sure which is used for unbricking) for your model. And flashing through flashone or Qfil. Google or search xda for steps on how to unbrick this particular phone or Qualcomm phones in general. I believe it involves a step where you hold vol+, vol- & power key.
Anyway goodluck.
Click to expand...
Click to collapse
I dont find a way to unlock the bootloader. Flashing the qfil i have already tried, but it doesnt repair the issue. I think efs or nvram is broken.
quasimodo88 said:
I dont find a way to unlock the bootloader. Flashing the qfil i have already tried, but it doesnt repair the issue. I think efs or nvram is broken.
Click to expand...
Click to collapse
What version did you flash with Qfil? 19s usually doesn't ask for leeco login so try that. If you can bypass the leeco login I can walk you through the steps to repair your efs, I even have qcn files for x526 and x522 you can edit to fix it.
Don't know if these three options are possible, because I'm not sure what the qfil files contain but
1. with your current qfil if you can find a way to delete the letvaccount apk from the system image and reflash, that should bypass the login issues. Though dm verify might prevent the phone from booting past the splash screen, so you'll need to replace the kernel(boot) img with any custom one like illusion or overload
2. replace the system, data and kernel(boot) image with ones from miui 9 rom. This will flash miui instead and voila, no login issue
3. Replace Qfil recovery image with renamed twrp
Dudeonyx said:
What version did you flash with Qfil? 19s usually doesn't ask for leeco login so try that. If you can bypass the leeco login I can walk you through the steps to repair your efs, I even have qcn files for x526 and x522 you can edit to fix it.
Don't know if these three options are possible, because I'm not sure what the qfil files contain but
1. with your current qfil if you can find a way to delete the letvaccount apk from the system image and reflash, that should bypass the login issues. Though dm verify might prevent the phone from booting past the splash screen, so you'll need to replace the kernel(boot) img with any custom one like illusion or overload
2. replace the system, data and kernel(boot) image with ones from miui 9 rom. This will flash miui instead and voila, no login issue
3. Replace Qfil recovery image with renamed twrp
Click to expand...
Click to collapse
Thank's dude, that sounds good! I have to bypass the leeco setup, what i have to do? Can you give me an instruction, please? You can find the file on this site:
http://www.gsmhelpful.com/2017/08/how-to-flash-letv-le-2-x526-with-qfil-flash-tool.html
quasimodo88 said:
Thank's dude, that sounds good! I have to bypass the leeco setup, what i have to do? Can you give me an instruction, please? You can find the file on this site:
http://www.gsmhelpful.com/2017/08/how-to-flash-letv-le-2-x526-with-qfil-flash-tool.html
Click to expand...
Click to collapse
Have you flashed this? If so did it remove the leeco login or at least make it skipable?
Send a pic of the login screen
---------- Post added at 03:28 PM ---------- Previous post was at 03:25 PM ----------
Also unzip the sparse file and send me pics of its contents. Because I can't download the file right now
Dudeonyx said:
Have you flashed this? If so did it remove the leeco login or at least make it skipable?
Send a pic of the login screen
---------- Post added at 03:28 PM ---------- Previous post was at 03:25 PM ----------
Also unzip the sparse file and send me pics of its contents. Because I can't download the file right now
Click to expand...
Click to collapse
Yes, i have install it 2 times, but same issue. Can you give me an email address for the pictures, please?
quasimodo88 said:
Yes, i have install it 2 times, but same issue. Can you give me an email address for the pictures, please?
Click to expand...
Click to collapse
I've seen the pics, the system file is in parts so replacing it is very very difficult as I cant be sure how it was split.
But good news, I noticed a file named recovery
So move that file somewhere else.
Then rename your twrp file to recovery and copy it to that folder.
Then try flashing it, if successful this should give you custom recovery and I can work with that
Dudeonyx said:
I've seen the pics, the system file is in parts so replacing it is very very difficult as I cant be sure how it was split.
But good news, I noticed a file named recovery
So move that file somewhere else.
Then rename your twrp file to recovery and copy it to that folder.
Then try flashing it, if successful this should give you custom recovery and I can work with that
Click to expand...
Click to collapse
Ok, i will try it now. Don't run away :fingers-crossed:
quasimodo88 said:
Ok, i will try it now. Don't run away :fingers-crossed:
Click to expand...
Click to collapse
Good luck, also I noticed that your issue isn't leeco account login but rather Google's factory reset protection. So if this fails you can search for ways to bypass google factory reset protection.