Related
Hello,
I have a big problem with my H815.
My H815 bootloader is been unlocked.
II try to install TWRP, but without success:
Code:
C:\Users\~\Downloads\G4\platform-tools>adb reboot bootloader
C:\Users\~\Downloads\G4\platform-tools>fastboot flash recovery twrp-2.8.7.0-h
815.img
target reported max download size of 536870912 bytes
sending 'recovery' (32064 KB)...
OKAY [ 1.197s]
writing 'recovery'...
OKAY [ 0.317s]
finished. total time: 1.520s
C:\Users\~\Downloads\G4\platform-tools>fastboot boot twrp-2.8.7.0-h815.img
downloading 'boot.img'...
OKAY [ 1.189s]
booting...
OKAY [ 0.036s]
finished. total time: 1.230s
For me, it's ok, but after that, my G4 reboot directly to the system (Android 6.0 : V20A).
And when I run the command "adb reboot recovery" I get to a screen where there is only an Android slept with a red triangle and "No command."
Any idea please?
Kind regrards,
~~
Sylar
I have exactly the same problem. Then I just can take out the battery and put the phone in download mode and then to flash via LG UP the kdz marshmallow file again. it seems I cannot install TWRP or root. The bootloader is unlocked of course.
nfsolutions said:
I have exactly the same problem. Then I just can take out the battery and put the phone in download mode and then to flash via LG UP the kdz marshmallow file again. it seems I cannot install TWRP or root. The bootloader is unlocked of course.
Click to expand...
Click to collapse
This way:
adb reboot bootloader
and if bootloader prompt on the g4:
fastboot boot twrp-xxxx.img
Also this steps are required:
http://forum.xda-developers.com/showpost.php?p=64148898&postcount=287
hannsheinz said:
This way:
adb reboot bootloader
and if bootloader prompt on the g4:
fastboot boot twrp-xxxx.img
Also this steps are required:
http://forum.xda-developers.com/showpost.php?p=64148898&postcount=287
Click to expand...
Click to collapse
This does not work for me. :'(
After this command : fastboot boot twrp-2.8.7.0-h815.img
My G4 boot imediatly to the System... :s
hannsheinz said:
This way:
adb reboot bootloader
and if bootloader prompt on the g4:
fastboot boot twrp-xxxx.img
Also this steps are required:
http://forum.xda-developers.com/showpost.php?p=64148898&postcount=287
Click to expand...
Click to collapse
thanks, now it works. My mistake was that I installed directly a supersu (not this from twrp) and this messed up the boot.
After installing twrp permanently, I used this method to get root:
http://forum.xda-developers.com/g4/general/guide-root-lg-marshmallow-rom-repacked-t3265497
now I have root and twrp
Can someone help me please ?
I tried to flash the KDZ 2 times but still nothing I parobleme always the same.
hannsheinz said:
This way:
adb reboot bootloader
and if bootloader prompt on the g4:
fastboot boot twrp-xxxx.img
Also this steps are required:
http://forum.xda-developers.com/showpost.php?p=64148898&postcount=287
Click to expand...
Click to collapse
Thank you Sir!
Got the same problem, installed TWRP but got bugdroid dead once booting recovery. Idk why TWRP isn't written.
Nothing to do I'm trying every way I could imagine. The result is always the same.
I can't find solution on any forum. Please, I need help. :'(
Kind Regards
Hmm...have you already had root before flashing TWRP?
I think you can use Flashify.apk
rjboy11223 said:
Hmm...have you already had root before flashing TWRP?
I think you can use Flashify.apk
Click to expand...
Click to collapse
No i'm not rooted atm. That why i wanna install a custom recovery ^.^
Try fastboot boot twrpblabla.img
then inside twrp just flash twrp.zip (or as img..)
bender_007 said:
Try fastboot boot twrpblabla.img
then inside twrp just flash twrp.zip (or as img..)
Click to expand...
Click to collapse
Thank you, but after that... :
Code:
C:\Users\~\Downloads\G4\platform-tools>fastboot boot twrp-2.8.7.0-h815.img
downloading 'boot.img'...
OKAY [ 1.189s]
booting...
OKAY [ 0.036s]
finished. total time: 1.230s
...my G4 reboot directly to the system (Android 6.0 : V20A).
And when I run the command "adb reboot recovery" I get to a screen where there is only an Android slept with a red triangle and "No command."
Got exactly the same problem
adb reboot bootloader
fastboot boot <nameoftheTWRPimage>.img
then flash the SuperSU zip in order to get root
install TWRP Manager app
launch the app and accept to give su rights
choose your G4 model and the latest recovery version
install and validate reboot
:good:
bel57 said:
Got exactly the same problem
adb reboot bootloader
fastboot boot <nameoftheTWRPimage>.img
then flash the SuperSU zip in order to get root
install TWRP Manager app
launch the app and accept to give su rights
choose your G4 model and the latest recovery version
install and validate reboot
:good:
Click to expand...
Click to collapse
Thank you, but same problème i can't boot to TWRP after the comand "fastboot boot twrp-2.8.7.0-h815.img" my G4 reboot directly to the system.
Might be stupid, but is your bootloader unlocked?
Android 6.0 V20A stock?
bel57 said:
Might be stupid, but is your bootloader unlocked?
Android 6.0 V20A stock?
Click to expand...
Click to collapse
Yes, my G4 is unlocked. And and it's Android 6.0 stock beacause I did the update by LG Bridge.
Ur phone is weird lol
Sylar37 said:
Yes, my G4 is unlocked. And and it's Android 6.0 stock beacause I did the update by LG Bridge.
Click to expand...
Click to collapse
try first fastboot erase recovery, then fastboot flash recovery twrp....img
then fastboot reboot recovery
I downloaded the v20b kdz and flashed via LGUP.. I don't know what's wrong mate, sorry. :silly:
Hey guys !
So since i messed up with the recovery mode, i'm stucked in the fastboot with no Download mode (recovery doesnt work neither).
So after searching 3 days in the internet i found the acces to fast through adb by puting a new laf.img in order to restore the download mode and flash a stock firmware !
My problem is that when i try to enter the command on the cmd, i get severals errors, take a look :
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
error: device not found
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase laf
erasing 'laf'...
FAILED (remote: failed to erase partition
)
finished. total time: 5.034s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash laf laf.img
target reported max download size of 2147483648 bytes
sending 'laf' (18432 KB)...
OKAY [ 0.581s]
writing 'laf'...
FAILED (remote: flash write failure)
finished. total time: 5.615s
Also command : "fastboot boot laf.img" result to "Failed(remote: dtb not found) instead of flash write failure..
Of course i have my G3 855 32GB in download mode (but it goes into fastmode), so when i try a command, lines are added in the screen etc..
Does that mean that my laf.img don't work? I assumed that so i try several, but does it have to be the exact same one as the one who was in my phone before( v20a if i record correctly ) or could it be from any 855 32GB version ?
I also thought it could be a recognition problem as when i type "adb devices" or "adb shell" nothing is found..
If someone has any clue or a link to some guide i'll be more than joyful, thanks in advance !
Try adb fastboot when writing command hope it helps
Anik49 said:
Try adb fastboot when writing command hope it helps
Click to expand...
Click to collapse
Hey thank you so much for answering !
What do you mean by that, i already download the adb/fastboot driver and launch a cmd in the directory they are at, writing "adb fastboot" has no result neither, can you be more specific please ?
cm13 recently messed up my phone in exactly the same way, no recovery and download mode would jump straght to fastboot. I followed this guide to the letter and am now back running again: http://open-freax.fr/guide-unbrick-your-lg-g3/
BigsyBiggins said:
cm13 recently messed up my phone in exactly the same way, no recovery and download mode would jump straght to fastboot. I followed this guide to the letter and am now back running again:
Click to expand...
Click to collapse
Well i hope my problem can be solved in a safer way, i dont like much to go on the hardware part, so I'll use it as my last hope, but thanks
Altought i think my device is recognized by fastboot in someway because it responds when i type commands in fastboot, and also when i reboot it.
But i'm getting this error :
Code:
error : command never completed
error : auto CMD12 error
error : command completed with errors
error : command timeout error
failed to send stop command
failed writing block @ 1
in the screen of my phone. Does that stand for Cyanogen mode which i was trying to put on my phone ?
I mean when you enter command in cmd use adb before any command also use cmd which one available on android sdk folder....also you can use this method if adb not workinhg properly http://forum.xda-developers.com/lg-g...-9008-t3072091
BigsyBiggins said:
cm13 recently messed up my phone in exactly the same way, no recovery and download mode would jump straght to fastboot. I followed this guide to the letter and am now back running again: http://open-freax.fr/guide-unbrick-your-lg-g3/
Click to expand...
Click to collapse
Like @BigsyBiggins said, this is the guide which could fix your phone. HW Part is not too hard!
Anik49 said:
I mean when you enter command in cmd use adb before any command also use cmd which one available on android sdk folder....also you can use this method if adb not workinhg properly
Click to expand...
Click to collapse
Oh ok ! Also your link is not working :s
I understand that the method can work but I think that the method i'm trying to use is really close to succeed, over my search on the internet, i saw lots of people who manage to succeed with it.
But i guess i must do something wrong. I downloaded the kdz file according to my IMEI.
Then I extracted the .dz file with LG Firmware Extract. Then I extracted the file named laf_393216.bin from the dz file. Changed his name into laf.img , put it into the fastboot directory.
Then i typed
Code:
fastboot format cache
fastboot erase laf
fastboot flash laf laf.img
in a cmd from the directory.
It all seemed to work, but then when i remove the battery and restart into download mode, it goes into fastboot after the download mode charging animation..
Also when i try to boot with fastboot boot laf.img i get the error (remote: dtb not found) on the cmd.
And ERROR: Unable to find suitable device tree for device(194/0x0001001/112/0) ERROR: getting device tree adress failed DTB offset is incorrect, kernel image does not have appended DTB)
Am I doing something wrong, should I changed more file than just laf ?
SisGG said:
Oh ok ! Also your link is not working :s
I understand that the method can work but I think that the method i'm trying to use is really close to succeed, over my search on the internet, i saw lots of people who manage to succeed with it.
But i guess i must do something wrong. I downloaded the kdz file according to my IMEI.
Then I extracted the .dz file with LG Firmware Extract. Then I extracted the file named laf_393216.bin from the dz file. Changed his name into laf.img , put it into the fastboot directory.
Then i typed
Code:
fastboot format cache
fastboot erase laf
fastboot flash laf laf.img
in a cmd from the directory.
It all seemed to work, but then when i remove the battery and restart into download mode, it goes into fastboot after the download mode charging animation..
Also when i try to boot with fastboot boot laf.img i get the error (remote: dtb not found) on the cmd.
And ERROR: Unable to find suitable device tree for device(194/0x0001001/112/0) ERROR: getting device tree adress failed DTB offset is incorrect, kernel image does not have appended DTB)
Am I doing something wrong, should I changed more file than just laf ?
Click to expand...
Click to collapse
I don´t know what exactly is the problem, maybe something with your win-driver, some crashed or drifted partitions or some broken files...
I just can repeat my advice: I was in the same situation with my phone after a failed cm13 update and i was trying and reading about 2 days how to solve it - after the above mentioned method, your phone would get out of this "coma".
Maybe somebody else here in this forum could help you with your mentioned method, sorry.
Ernesto0023 said:
I don´t know what exactly is the problem, maybe something with your win-driver, some crashed or drifted partitions or some broken files...
I just can repeat my advice: I was in the same situation with my phone after a failed cm13 update and i was trying and reading about 2 days how to solve it - after the above mentioned method, your phone would get out of this "coma".
Maybe somebody else here in this forum could help you with your mentioned method, sorry.
Click to expand...
Click to collapse
Well I think i'm still under warranty, so i dont wanna touch to much on the hardware.
So do you think, if i send it back without touching anything, saying i put it on charge one night and the next morning it was like this, the warranty could work?
If they found it's rooted or they understand you did something with your software your warrenty is void ?
SisGG said:
Well i hope my problem can be solved in a safer way, i dont like much to go on the hardware part, so I'll use it as my last hope, but thanks
Altought i think my device is recognized by fastboot in someway because it responds when i type commands in fastboot, and also when i reboot it.
But i'm getting this error :
Code:
error : command never completed
error : auto CMD12 error
error : command completed with errors
error : command timeout error
failed to send stop command
failed writing block @ 1
in the screen of my phone. Does that stand for Cyanogen mode which i was trying to put on my phone ?
Click to expand...
Click to collapse
Remove the battery, put it, press the volume + and connect to PC USB, if like entering download, what happens to us not to go, will leave the ****ing LoGo, Well, hold down the volume + and not let go, I think it is less for 2 minutes more. After a while, the computer tells us that something was connected, the phone will tell you who is in fastboot as I said before, if not let me fastboot flash boot files and the LAF, recovery ect, nothing happens, there is still a magic command.
fastboot boot laf.img
Keep it in the ****ing heart
miguexneox said:
Remove the battery, put it, press the volume + and connect to PC USB, if like entering download, what happens to us not to go, will leave the ****ing LoGo, Well, hold down the volume + and not let go, I think it is less for 2 minutes more. After a while, the computer tells us that something was connected, the phone will tell you who is in fastboot as I said before, if not let me fastboot flash boot files and the LAF, recovery ect, nothing happens, there is still a magic command.
fastboot boot laf.img
Keep it in the ****ing heart
Click to expand...
Click to collapse
I dont quite understand what u meant there :s
I already have acces on the fastboot, actually now, my phone goes instantly on fastboot whatever i do.. Though i cannot boot a laf.img downloaded and flashed .. :'(
SisGG said:
I dont quite understand what u meant there :s
I already have acces on the fastboot, actually now, my phone goes instantly on fastboot whatever i do.. Though i cannot boot a laf.img downloaded and flashed .. :'(
Click to expand...
Click to collapse
were u able to resolve this issue. I am in your shoes at the moment.
I have tried the qualcomm. The drivers doesnt seem to work for my phone .
I can't flash or the laf.img . the fastboot commands doesnt seem to work.
and I'm stuck in fastboot .
What can be done
datrmon said:
were u able to resolve this issue. I am in your shoes at the moment.
I have tried the qualcomm. The drivers doesnt seem to work for my phone .
I can't flash or the laf.img . the fastboot commands doesnt seem to work.
and I'm stuck in fastboot .
What can be done
Click to expand...
Click to collapse
You have several options:
- find your phone firmware, extract recovery.img and flash it back through fastboot(do exactly the same for the LAF partition to restore download mode)
- flash a custom recovery for your phone model, if it doesn't work try an older version of TWRP, also it can be that your phone is not d855 but d850 model, so try to flash a d850 custom recovery and see if it works(that was exactly my problem and why i got stuck in fastboot mode, because my phone is d850 model and in settings it says d855, so I flashed wrong TWRP)
Ghikya said:
You have several options:
- find your phone firmware, extract recovery.img and flash it back through fastboot(do exactly the same for the LAF partition to restore download mode)
- flash a custom recovery for your phone model, if it doesn't work try an older version of TWRP, also it can be that your phone is not d855 but d850 model, so try to flash a d850 custom recovery and see if it works(that was exactly my problem and why i got stuck in fastboot mode, because my phone is d850 model and in settings it says d855, so I flashed wrong TWRP)
Click to expand...
Click to collapse
Thanks for the response .
I am unable to flash files at all.
This is the error
D:\mfastboot-v2>fastboot flash laf laf.img
target max-download-size: 2048MB
sending 'laf' (18432 KB)...
OKAY [ 0.646s]
writing 'laf'...
FAILED (remote: flash write failure)
finished. total time: 5.726s
D:\mfastboot-v2>
datrmon said:
Thanks for the response .
I am unable to flash files at all.
This is the error
D:\mfastboot-v2>fastboot flash laf laf.img
target max-download-size: 2048MB
sending 'laf' (18432 KB)...
OKAY [ 0.646s]
writing 'laf'...
FAILED (remote: flash write failure)
finished. total time: 5.726s
D:\mfastboot-v2>
Click to expand...
Click to collapse
It seems that your phone's bootloader is locked, you can try to execute this command: "fastboot oem unlock", and then check state with "fastboot oem device-info". But some people says that it does nothing, so you can try and check for yourself.
You can also try to boot directly an image from fastboot for eaxmple:
Code:
fastboot boot laf.img
or
Code:
fastboot boot twrp.img
So if you could successfully boot a laf image you would be able to access download mode, and if you could boot a custom recowery then you could access ADB and to try to flash other partitions, or even flash a custom rom...
Hi, I am trying to install twrp twrp-3.1.1-0-odin.img so I can get RR rom on my C6502
first of all, I'm well aware of steps, and I personally have this rom installed in my xperia m, so it won't be hard for me to understand and it's quite easy as 123 over there
the problem I'm facing is, this xperia ZL c6502 l35h device seems to have something in different I'm not able to flash twrp here
I used repair feature in sony pc companion, done successfully, start device, wait for first boot time, configure, enable unknown source, enable usb debugging, connect cable to pc and allow RSA pc's code
power off and connect with voldown, used flash tool to unlock bootloader (yes the blootloader status unlock is yes in *#*#7378042#*#* code confi thing)
bootloader unlocked successfully, device tried to be in bootloop for three times, then it started, like first boot took somewhere 15 min to start up, and everything is fine, except I cannot increase brightness anymore but nvm
I again enable unknown source, and usb debugging, and allow my pc's RSA key > always allow
poweroff, connect in fastboot, flash kernel > select the just downloaded twrp from official source 3.1.1.0 I think
I flash receive an error says remote: command not allowed
22/002/2017 07:02:33 - INFO - Device connected in fastboot mode
22/002/2017 07:02:39 - INFO - Selected kernel (boot.img or kernel.sin): D:\IDM\General\twrp-3.1.0-0-odin.img
22/002/2017 07:02:39 - INFO - Flashing selected kernel
22/002/2017 07:02:40 - INFO - sending 'boot' (11406 KB)...
22/002/2017 07:02:40 - INFO - OKAY [ 0.361s]
22/002/2017 07:02:40 - INFO - writing 'boot'...
22/002/2017 07:02:40 - INFO - FAILED (remote: Command not allowed)
22/002/2017 07:02:40 - INFO - finished. total time: 0.363s
22/002/2017 07:02:40 - INFO - FASTBOOT Output:
sending 'boot' (11406 KB)...
OKAY [ 0.361s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.363s
tried to used minimal adb and fast boot
here's the log
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target didn't report max-download-size
sending 'recovery' (11474 KB)...
OKAY [ 0.364s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.368s
So, I have my bootloader unlocked, I can confirm that because after booting up post unlock, there's change in system, I cannot increase brightness, and in that code *#*#7378... I see more Bands available before unlock
and device booted after like 3 bootloops automatically, what am I doing wrong, and what should I do? how are people able to get this rom in their device?
btw, I'm dealing with firmware 10.7.A.0.222 India version, all latest as per pc companion repair feature and today it will be offc latest one
and the version of my flashtool is 0.9.18.6
in minimal adb and fastboot, I tried this
fastboot.exe -i 0x0fce getvar version
result is 0.5
fastboot.exe -i 0x0fce oem unlock 0x[my key in caps]
first time it fails and second time it does, and output is successfull
then I proceed to flash twrp
fastboot flash recovery twrp.img
I receive failed command not allowed
then I try
fastboot flash boot boot.img
successful, but phone bricked
I reflash 10.7.A.0.222 and device working again, but how do I flash twrp?
what am I doing wrong?
Godlydevils said:
Hi, I am trying to install twrp twrp-3.1.1-0-odin.img so I can get RR rom on my C6502
first of all, I'm well aware of steps, and I personally have this rom installed in my xperia m, so it won't be hard for me to understand and it's quite easy as 123 over there
the problem I'm facing is, this xperia ZL c6502 l35h device seems to have something in different I'm not able to flash twrp here
I used repair feature in sony pc companion, done successfully, start device, wait for first boot time, configure, enable unknown source, enable usb debugging, connect cable to pc and allow RSA pc's code
power off and connect with voldown, used flash tool to unlock bootloader (yes the blootloader status unlock is yes in *#*#7378042#*#* code confi thing)
bootloader unlocked successfully, device tried to be in bootloop for three times, then it started, like first boot took somewhere 15 min to start up, and everything is fine, except I cannot increase brightness anymore but nvm
I again enable unknown source, and usb debugging, and allow my pc's RSA key > always allow
poweroff, connect in fastboot, flash kernel > select the just downloaded twrp from official source 3.1.1.0 I think
I flash receive an error says remote: command not allowed
22/002/2017 07:02:33 - INFO - Device connected in fastboot mode
22/002/2017 07:02:39 - INFO - Selected kernel (boot.img or kernel.sin): D:\IDM\General\twrp-3.1.0-0-odin.img
22/002/2017 07:02:39 - INFO - Flashing selected kernel
22/002/2017 07:02:40 - INFO - sending 'boot' (11406 KB)...
22/002/2017 07:02:40 - INFO - OKAY [ 0.361s]
22/002/2017 07:02:40 - INFO - writing 'boot'...
22/002/2017 07:02:40 - INFO - FAILED (remote: Command not allowed)
22/002/2017 07:02:40 - INFO - finished. total time: 0.363s
22/002/2017 07:02:40 - INFO - FASTBOOT Output:
sending 'boot' (11406 KB)...
OKAY [ 0.361s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.363s
tried to used minimal adb and fast boot
here's the log
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target didn't report max-download-size
sending 'recovery' (11474 KB)...
OKAY [ 0.364s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.368s
So, I have my bootloader unlocked, I can confirm that because after booting up post unlock, there's change in system, I cannot increase brightness, and in that code *#*#7378... I see more Bands available before unlock
and device booted after like 3 bootloops automatically, what am I doing wrong, and what should I do? how are people able to get this rom in their device?
btw, I'm dealing with firmware 10.7.A.0.222 India version, all latest as per pc companion repair feature and today it will be offc latest one
and the version of my flashtool is 0.9.18.6
in minimal adb and fastboot, I tried this
fastboot.exe -i 0x0fce getvar version
result is 0.5
fastboot.exe -i 0x0fce oem unlock 0x[my key in caps]
first time it fails and second time it does, and output is successfull
then I proceed to flash twrp
fastboot flash recovery twrp.img
I receive failed command not allowed
then I try
fastboot flash boot boot.img
successful, but phone bricked
I reflash 10.7.A.0.222 and device working again, but how do I flash twrp?
what am I doing wrong?
Click to expand...
Click to collapse
Just to confirm that you did change your downloaded recovery name to boot.img and placed it inside c drive adb folder, right?
hhjadeja007 said:
Just to confirm that you did change your downloaded recovery name to boot.img and placed it inside c drive adb folder, right?
Click to expand...
Click to collapse
yes, I renamed to boot.img after googling and learning,
and as I had minimal adb and fastboot installed in
C:\Program Files (x86)\Minimal ADB and Fastboot
I placed in that directory
is that correct?
Godlydevils said:
yes, I renamed to boot.img after googling and learning,
and as I had minimal adb and fastboot installed in
C:\Program Files (x86)\Minimal ADB and Fastboot
I placed in that directory
is that correct?
Click to expand...
Click to collapse
Yeah that's correct.
hhjadeja007 said:
Yeah that's correct.
Click to expand...
Click to collapse
Hi, I just managed to get it done, but another problem arise
I flash anew 10.7.A.0.222
after that, I ticked unknown source, and enable debugging, and as people mentioned that it means bootloader is not unlocked
I fired this command five times
fastboot.exe -i 0x0fce oem unlock 0xDB29CBBEFBAB4A64
and after that I fired
fastboot flash boot boot.img
output was
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target didn't report max-download-size
sending 'boot' (11474 KB)...
OKAY [ 0.364s]
writing 'boot'...
OKAY [ 0.548s]
finished. total time: 0.915s
means it worked, but when I hold power button, it vibrates, if I press and hold again, it would vibrate, and never start up
if I connect it for charging red LED would blink
Godlydevils said:
Hi, I just managed to get it done, but another problem arise
I flash anew 10.7.A.0.222
after that, I ticked unknown source, and enable debugging, and as people mentioned that it means bootloader is not unlocked
I fired this command five times
fastboot.exe -i 0x0fce oem unlock 0xDB29CBBEFBAB4A64
and after that I fired
fastboot flash boot boot.img
output was
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot boot.img
target didn't report max-download-size
sending 'boot' (11474 KB)...
OKAY [ 0.364s]
writing 'boot'...
OKAY [ 0.548s]
finished. total time: 0.915s
means it worked, but when I hold power button, it vibrates, if I press and hold again, it would vibrate, and never start up
if I connect it for charging red LED would blink
Click to expand...
Click to collapse
Well, it's strange.
hhjadeja007 said:
Well, it's strange.
Click to expand...
Click to collapse
that's the one I'm trying
downloaded from
https://dl.twrp.me/odin/twrp-3.1.1-0-odin.img
okay, I just flashed again .222 I will now unlock bootloader, then restart and post result
Godlydevils said:
that's the one I'm trying
downloaded from
https://dl.twrp.me/odin/twrp-3.1.1-0-odin.img
okay, I just flashed again .222 I will now unlock bootloader, then restart and post result
Click to expand...
Click to collapse
Maybe try pressing vol + button just like Xperia m after mobile vibrates
hhjadeja007 said:
Maybe try pressing vol + button just like Xperia m after mobile vibrates
Click to expand...
Click to collapse
Here's something more I learned
If you unlock boot loader, and restart, > tick unknown + usb debugging, and boot to bootloader, it won't let you flash boot.img
but if you immediately unlock bootloader, and without restart, you flash boot.img, it will go success
but after that, your device won't start
it's not starting, it vibrates, but no display, no matter how many times you press and hold power button to start it, it will vibrate, and won't start
I tried each and every combination of vol +/- and power button, but it's not starting that way
EDIT:
but I can still press and hold vol up and connect cable to get in fastboot mode, after which if I try flashing twrp, i again get command not allowed, except if I try fastboot.exe -i 0x0fce oem unlock 0xDB29CBBEFBAB4A64 and then fastboot flash boot boot.img
after which I will get success flashing that recovery, but device won't start
Godlydevils said:
Here's something more I learned
If you unlock boot loader, and restart, > tick unknown + usb debugging, and boot to bootloader, it won't let you flash boot.img
but if you immediately unlock bootloader, and without restart, you flash boot.img, it will go success
but after that, your device won't start
it's not starting, it vibrates, but no display, no matter how many times you press and hold power button to start it, it will vibrate, and won't start
I tried each and every combination of vol +/- and power button, but it's not starting that way
EDIT:
but I can still press and hold vol up and connect cable to get in fastboot mode, after which if I try flashing twrp, i again get command not allowed, except if I try fastboot.exe -i 0x0fce oem unlock 0xDB29CBBEFBAB4A64 and then fastboot flash boot boot.img
after which I will get success flashing that recovery, but device won't start
Click to expand...
Click to collapse
For me, i think if you're recently to unlock your bootloader. Have you try to confirmed that your bootloader really unlocked from stock firmware? (*#*#7378423#*#*) and see about bootloader info?
If bootloader already unlocked, then you're safe to flash, And have you read any requirement to flash recovery for your device? i think it's like only work for custom rom or only work for specified version of firmware?
If device won't start, then it should from kernel problem. Try to check your custom recovery compatibility before flashing, and tell us what happen next
Nicklas Van Dam said:
For me, i think if you're recently to unlock your bootloader. Have you try to confirmed that your bootloader really unlocked from stock firmware? (*#*#7378423#*#*) and see about bootloader info?
If bootloader already unlocked, then you're safe to flash, And have you read any requirement to flash recovery for your device? i think it's like only work for custom rom or only work for specified version of firmware?
If device won't start, then it should from kernel problem. Try to check your custom recovery compatibility before flashing, and tell us what happen next
Click to expand...
Click to collapse
okay,
so few points worth mentioning
1) my bootloader is unlockable, and is unlocked, I mean in 7378423 it's written yes in root status bl unlock
2) I have received code from sony, and I can unlock it
3) the only recovery that works is https://forum.xda-developers.com/showthread.php?t=2288118 that too only after using kingroot, which gives me old philz and 2.8.7.0 twrp which are not helpful, also I tried to flash RR 7.1.2 based, phone basically gets bricked
4) I can only flash twrp or any recovery if I unlock bootloader, and without restarting I flash boot.img, if I do so, phone gets bricked
Here's the ss of BL status
{
"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"
}
There's nothing written about requirements of twrp to flash, or rom, they just don't have, but as I have latest firmware, it should work, even nothing is written in linageos thread
I found basically few members of the community faced this problem
https://forum.xda-developers.com/xperia-zl/help/related-problems-flashing-stock-t3274520/
Godlydevils said:
okay,
so few points worth mentioning
1) my bootloader is unlockable, and is unlocked, I mean in 7378423 it's written yes in root status bl unlock
2) I have received code from sony, and I can unlock it
3) the only recovery that works is https://forum.xda-developers.com/showthread.php?t=2288118 that too only after using kingroot, which gives me old philz and 2.8.7.0 twrp which are not helpful, also I tried to flash RR 7.1.2 based, phone basically gets bricked
4) I can only flash twrp or any recovery if I unlock bootloader, and without restarting I flash boot.img, if I do so, phone gets bricked
Here's the ss of BL status
There's nothing written about requirements of twrp to flash, or rom, they just don't have, but as I have latest firmware, it should work, even nothing is written in linageos thread
Click to expand...
Click to collapse
Man Your bootloader is locked. It can be clearly seen from screen shot
hhjadeja007 said:
Man Your bootloader is locked. It can be clearly seen from screen shot
Click to expand...
Click to collapse
can you explain?
hhjadeja007 said:
Man Your bootloader is locked. It can be clearly seen from screen shot
Click to expand...
Click to collapse
Better?
Godlydevils said:
Better?
Click to expand...
Click to collapse
Yeah now you are good to go
hhjadeja007 said:
Yeah now you are good to go
Click to expand...
Click to collapse
so far, I am able to flash twrp, and I just flashed RR with gapps and mod, just got into settings wizard, will update/comment if I face any problem other than music has stopped working :/
Godlydevils said:
so far, I am able to flash twrp, and I just flashed RR with gapps and mod, just got into settings wizard, will update/comment if I face any problem other than music has stopped working :/
Click to expand...
Click to collapse
Okay, that's good. Now my questions , that is recovery based on FOTA or only normal recovery based on Boot.IMG?
Sent from my nicki using XDA Labs
Nicklas Van Dam said:
Okay, that's good. Now my questions , that is recovery based on FOTA or only normal recovery based on Boot.IMG?
Sent from my nicki using XDA Labs
Click to expand...
Click to collapse
boot.img
The problem was with the lolipop rom
Had to flash Kitkat, and unlock bootloader, no probs
Hello
my name is modou sow.in fact i have a problem with my huawei p9 lite.je wanted to put on my my phone and i did a wrong handling and because it could not walk any more.auauf mode wipe / data which ended in failure. Then I tried to install the recovery, boot, system ... but at any time I have the results:
*FAILED (remote: Command not allowed);
please help me;
I apologize for the bad English because I am Senegalese.
Hi all,
unfortunatelly I can't get my pixel c working again. I'm stuck in bootloader and only fastboot commands work but with no success.
fastboot flash recovery twrp.img
target reported max download size of 268435456 bytes
erasing 'recovery'...
FAILED (remote: unsupported command)
Click to expand...
Click to collapse
fastboot boot twrp.img
creating boot image...
creating boot image - 13133824 bytes
downloading 'boot.img'...
OKAY [ 0.442s]
booting...
FAILED (remote: image verification failed)
Click to expand...
Click to collapse
All drivers (ADB, Fastboot, Google etc.) are installed and are up-to-date. Bootloader is unlocked and it seems BL reacts the same way like BL is locked.
System is not booting and recovery won't boot too. Is there any way to get an adb shell in another way?
Bolemichel said:
Hi all,
unfortunatelly I can't get my pixel c working again. I'm stuck in bootloader and only fastboot commands work but with no success.
fastboot flash recovery twrp.img
fastboot boot twrp.img
All drivers (ADB, Fastboot, Google etc.) are installed and are up-to-date. Bootloader is unlocked and it seems BL reacts the same way like BL is locked.
System is not booting and recovery won't boot too. Is there any way to get an adb shell in another way?
Click to expand...
Click to collapse
Have you tried flashing stock?
Bolemichel said:
Hi all,
unfortunatelly I can't get my pixel c working again. I'm stuck in bootloader and only fastboot commands work but with no success.
fastboot flash recovery twrp.img
fastboot boot twrp.img
All drivers (ADB, Fastboot, Google etc.) are installed and are up-to-date. Bootloader is unlocked and it seems BL reacts the same way like BL is locked.
System is not booting and recovery won't boot too. Is there any way to get an adb shell in another way?
Click to expand...
Click to collapse
Were you able to solve that?
FWIW, the state you're describing is not unheard of and requires to use the fwtool (reference, for example, here). But that, in turn, requires you can have TWRP installed... because with the bootloader in this limbo state, it also refuses to load TWRP on the fly using "fastboot boot ..."
xrad said:
Were you able to solve that?
FWIW, the state you're describing is not unheard of and requires to use the fwtool (reference, for example, here). But that, in turn, requires you can have TWRP installed... because with the bootloader in this limbo state, it also refuses to load TWRP on the fly using "fastboot boot ..."
Click to expand...
Click to collapse
No, meanwhile I returned it to google and got a new one. But thank you for help!
I did local upgrade of Beta 2 from stable firmware, but I am stuck on boot screen, If i choose reboot option it is rebooting to the same menu.
It is showing this:
Boot Reason: fs_mgr_mount_all
Unablt to parse kernel log. For more informaton,
adb pull /mnt/vendor/op2/rbr_log
or pull op2.img
Please help if you know the solution
I would say some firmware mismatch.
Try switch to other slot and boot, then reinstall update.
Lossyx said:
I would say some firmware mismatch.
Try switch to other slot and boot, then reinstall update.
Click to expand...
Click to collapse
I somehow managed to reboot it to the version from which I Flashed the update file. (all data as it is)
but now I'm afraid to flash it again as I may lose my data...
How I rebooted:
Menu showed me three options : Fastboot, Recovery, Exit
I went in to the fastboot mode couple of times and then I booted into recovery mode, then I rebooted the device and it got flashed to normal firmware with data
Khushil kanani said:
I did local upgrade of Beta 2 from stable firmware, but I am stuck on boot screen, If i choose reboot option it is rebooting to the same menu.
It is showing this:
Boot Reason: fs_mgr_mount_all
Unablt to parse kernel log. For more informaton,
adb pull /mnt/vendor/op2/rbr_log
or pull op2.img
Please help if you know the solution
Click to expand...
Click to collapse
The problem is with the update package, Using the computer, install fastboot driver then restart phone in fastboot mode then open command prompt and type "fastboot --set-active=b" or "fastboot --set-active=b" type without quotes and then reboot. Just type one command and restart if the first one does not work then type second. Below is the result of the command.
Code:
C:\Users\>fastboot --set-active=b
Setting current slot to 'b' OKAY [ 0.047s]
Finished. Total time: 0.062s