Hi guys,
I flashed stock back to my phone and relocked the bootloader by "fastboot oem lock".
I been stuck with this for the last 2 days searching for solution on how to get my phone unlocked and rooted again.
This is what I have tried so far:
1. Rumrunner 1.10.605.10 and 1.10.605.15 firmware (flashed 1.10.605.10 and updated to 15) - Run just fine, but it does not change anything on the phone. Still shows RELOCKED S-off and NO Root.
2. Firewater (temp-root method) - Temproot: Root acquired. Firewater: "there really isn't a helluva lot to do here. bye bye"
3. Flashing CM recovery - failed remote not allowed
Could someone please help me to get back Root access and UNLOCK my phone?
Thank you in advance.
If your s-off, all you have to do is fastboot flash a custom recovery.
Code:
fastboot flash recovery name_of_recovery_file.img
Then flash superuser zip thru recovery. Then you will be rooted. Also it is a myth that you need to relock the bootloader to do an ruu, so that wasnt really needed. Not sure exactly how to unlock the bootloader again.
cmlusco said:
If your s-off, all you have to do is fastboot flash a custom recovery.
Code:
fastboot flash recovery name_of_recovery_file.img
Then flash superuser zip thru recovery. Then you will be rooted. Also it is a myth that you need to relock the bootloader to do an ruu, so that wasnt really needed. Not sure exactly how to unlock the bootloader again.
Click to expand...
Click to collapse
Thank you for your reply.
I have tried to flash recovery several times, and both TWRP and CWM gives the same error: FAILED remote not allowed
Code:
sending 'recovery' (8784 KB)...
OKAY [ 1.097s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.134s
I tried the following recoveries:
openrecovery-twrp-2.6.3.3-m7vzw
recovery-clockwork-6.0.4.4-m7vzw
recovery-clockwork-6.0.4.7-m7vzw
recovery-clockwork-touch-6.0.4.5-m7vzw
recovery-clockwork-touch-6.0.4.7-m7vzw
NELORAO said:
Thank you for your reply.
I have tried to flash recovery several times, and both TWRP and CWM gives the same error: FAILED remote not allowed
Code:
sending 'recovery' (8784 KB)...
OKAY [ 1.097s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.134s
I tried the following recoveries:
openrecovery-twrp-2.6.3.3-m7vzw
recovery-clockwork-6.0.4.4-m7vzw
recovery-clockwork-6.0.4.7-m7vzw
recovery-clockwork-touch-6.0.4.5-m7vzw
recovery-clockwork-touch-6.0.4.7-m7vzw
Click to expand...
Click to collapse
Ok try this then.
1. Download this file http://vzw1files.dyndns.org/RECOVERIES/twrp/Twrp_2.6.3.4_RUU_Mode.zip, and place it on your pc in the same folder as fastboot.exe and adb.exe. Rename it to recovery.zip
2. Connect the phone to the pc and open a cmd prompt to where the files are, and type the following.
Code:
adb reboot bootloader
Wait for hboot.
Code:
fastboot oem rebootRUU
Wait for grey HTC logo.
Code:
fastboot flash zip recovery.zip
Wait for cmd window to say it has finished.
Code:
fastboot reboot-bootloader
3. Hit power button to select bootloader, and then use the power button again to select recovery.
If all is well you should boot to TWRP 2.6.3.4. Then flash Superuser http://vzw1files.dyndns.org/Superuser/superuser.zip and you will be rooted.
.
NELORAO said:
Hi guys,
I flashed stock back to my phone and relocked the bootloader by "fastboot oem lock".
I been stuck with this for the last 2 days searching for solution on how to get my phone unlocked and rooted again.
This is what I have tried so far:
1. Rumrunner 1.10.605.10 and 1.10.605.15 firmware (flashed 1.10.605.10 and updated to 15) - Run just fine, but it does not change anything on the phone. Still shows RELOCKED S-off and NO Root.
2. Firewater (temp-root method) - Temproot: Root acquired. Firewater: "there really isn't a helluva lot to do here. bye bye"
3. Flashing CM recovery - failed remote not allowed
Could someone please help me to get back Root access and UNLOCK my phone?
Thank you in advance.
Click to expand...
Click to collapse
Enable USB Debugging in Settings.
To do so, go to build information and tap it 7 times.
This will enable the Developer options in settings.
In there, check the box for Usb Debugging.
You should then be able to fastboot flash the recovery as per usual.
Good luck! :good:
cmlusco said:
Ok try this then.
1. Download this file http://vzw1files.dyndns.org/RECOVERIES/twrp/Twrp_2.6.3.4_RUU_Mode.zip, and place it on your pc in the same folder as fastboot.exe and adb.exe. Rename it to recovery.zip
2. Connect the phone to the pc and open a cmd prompt to where the files are, and type the following.
Code:
adb reboot bootloader
Wait for hboot.
Code:
fastboot oem rebootRUU
Wait for grey HTC logo.
Code:
fastboot flash zip recovery.zip
Wait for cmd window to say it has finished.
Code:
fastboot reboot-bootloader
3. Hit power button to select bootloader, and then use the power button again to select recovery.
If all is well you should boot to TWRP 2.6.3.4. Then flash Superuser http://vzw1files.dyndns.org/Superuser/superuser.zip and you will be rooted.
.
Click to expand...
Click to collapse
Dude, there just aren't enough words to say thank you.
Again, thank you so much, everything works like a charm now.
santod040 said:
Enable USB Debugging in Settings.
To do so, go to build information and tap it 7 times.
This will enable the Developer options in settings.
In there, check the box for Usb Debugging.
You should then be able to fastboot flash the recovery as per usual.
Good luck! :good:
Click to expand...
Click to collapse
Thank you, I was finally able to flash your KitKat Rom that I have been dreaming for the last 3 days. :laugh:
Again, thank you so much.
cmlusco said:
Ok try this then.
1. Download this file, and place it on your pc in the same folder as fastboot.exe and adb.exe. Rename it to recovery.zip
2. Connect the phone to the pc and open a cmd prompt to where the files are, and type the following.
Code:
adb reboot bootloader
Wait for hboot.
Code:
fastboot oem rebootRUU
Wait for grey HTC logo.
Code:
fastboot flash zip recovery.zip
Wait for cmd window to say it has finished.
Code:
fastboot reboot-bootloader
3. Hit power button to select bootloader, and then use the power button again to select recovery.
If all is well you should boot to TWRP 2.6.3.4. Then flash Superuser and you will be rooted.
.
Click to expand...
Click to collapse
Holy crap dude. I thought my phone was bricked. Thank you so much for that!
Hi all,
I installed CM14 on my OP3 but now after 5days somthing has happen.
The phone doesn't start I can see the logo and after that I see some check that it does.
cache : failed
boot: failed
boot-aging: failed
system: failed
Tried to do "technobuzz net / unbrick-oneplus-3"
But it doesn't work.
In fastboot under
Fastboot mode
PRODUCT_NAME - msm8996
VARIANT - MTP UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - ********
SECURE BOOT - enabled
Device state - locked
So I can't flash any thing and the recovery menu is not there.
I can only start the phone in Fastboot menu but no more.
Can anyone help my?
Can I boot some bootimage and login to CM14?
thefuse said:
Hi all,
I installed CM14 on my OP3 but now after 5days somthing has happen.
The phone doesn't start I can see the logo and after that I see some check that it does.
cache : failed
boot: failed
boot-aging: failed
system: failed
Tried to do "technobuzz net / unbrick-oneplus-3"
But it doesn't work.
In fastboot under
Fastboot mode
PRODUCT_NAME - msm8996
VARIANT - MTP UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - ********
SECURE BOOT - enabled
Device state - locked
So I can't flash any thing and the recovery menu is not there.
I can only start the phone in Fastboot menu but no more.
Can anyone help my?
Click to expand...
Click to collapse
same here
Is there any way to get the device state -locked to unlocked without having the OS?
C:\adb>fastboot oem device-info
...
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) Have console: false
(bootloader) Selinux type: <none>
(bootloader) Boot_mode: normal
(bootloader) Kmemleak_detect: false
OKAY [ 0.094s]
finished. total time: 0.095s
C:\adb>
I got it back from the repair yesterday, and they replaced my motherboard because of faulty motherboard.
install mod-twrp via fastboot
http://forum.xda-developers.com/devdb/project/dl/?id=21835 and install OxygenOS 3.2.6/3.2.8
You simply plug it into a pc and type fastboot oem unlock to unlock the device, then flash TWRP and reflash the OS
cache : failed
modem : failed
boot: failed
boot-aging: failed
system: failed
md5checksum: failed
I have same problem, i was on OOS b9
I flashed TWRP but can not restart to recovery, and also I flashed stock recovery but same problem ,
Any suggestion
Regards
almuhajir said:
cache : failed
modem : failed
boot: failed
boot-aging: failed
system: failed
md5checksum: failed
I have same problem, i was on OOS b9
I flashed TWRP but can not restart to recovery, and also I flashed stock recovery but same problem ,
Any suggestion
Regards
Click to expand...
Click to collapse
Unbrick guide, you will have to flaah these files manually.
Puddi_Puddin said:
Unbrick guide, you will have to flaah these files manually.
Click to expand...
Click to collapse
I got this problem after using (guide mega unbrick guide hard bricked)
http://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
Yes. Boot into fastboot and see of windows device manager shows Kedacom. If it does boot into https://www.google.nl/amp/www.howto...signed-drivers/amp/?client=ms-android-oneplus then install http://www.technobuzz.net/download-oneplus-3-usb-drivers/ now go to device manager it still shows kedacom. (Im not fully sure) but there should be a option if you right click it to change it to Oneplus drivers. Try to play yourself with thid method. I had it aswell and fixed it. I cant give you a fully guide since im not homeless yet..
Puddi_Puddin said:
Yes. Boot into fastboot and see of windows device manager shows Kedacom. If it does boot into https://www.google.nl/amp/www.howto...signed-drivers/amp/?client=ms-android-oneplus then install http://www.technobuzz.net/download-oneplus-3-usb-drivers/ now go to device manager it still shows kedacom. (Im not fully sure) but there should be a option if you right click it to change it to Oneplus drivers. Try to play yourself with thid method. I had it aswell and fixed it. I cant give you a fully guide since im not homeless yet..
Click to expand...
Click to collapse
Dear,
its not show Kedacom with me
What does it show then? Otherwise try to manually flash these files.
Puddi_Puddin said:
What does it show then? Otherwise try to manually flash these files.
Click to expand...
Click to collapse
I'll try to flashed manually, i'll give you feedback
almuhajir said:
I'll try to flashed manually, i'll give you feedback
Click to expand...
Click to collapse
Otherwise well go back to the basics
1. Boot into fastboot type "Fastboot devices" does it show up? No? > Device Manager try to see if it shows something with Kedacomm.
2. Fastboot devices shows up? > Go to the unbrick program it has a file with all partitions. Flash the missing ones that you get on your screen manually, i assume that you know how fastboot works.
3. System boots yay! But no wifi Reflash OOS but dont boot! Go to Fastboot and type this
"fastboot erase modemst1"
"fastboot erase modemst2"
If you still didn't manage to fix it try to explain as clearly ss you can with what you are doing and what you have tried.
Puddi_Puddin said:
Otherwise well go back to the basics
1. Boot into fastboot type "Fastboot devices" does it show up? No? > Device Manager try to see if it shows something with Kedacomm.
2. Fastboot devices shows up? > Go to the unbrick program it has a file with all partitions. Flash the missing ones that you get on your screen manually, i assume that you know how fastboot works.
3. System boots yay! But no wifi Reflash OOS but dont boot! Go to Fastboot and type this
"fastboot erase modemst1"
"fastboot erase modemst2"
If you still didn't manage to fix it try to explain as clearly ss you can with what you are doing and what you have tried.
Click to expand...
Click to collapse
Thanx dear,
the problem now still in
cache : failed (dont have it)
modem : ok flash it via fastboot
boot: failed try but not show ok
boot-aging: failed (dont have it)
system: failed (dont have it)
md5checksum: failed (dont have it)
almuhajir said:
Thanx dear,
the problem now still in
cache : failed (dont have it)
modem : ok flash it via fastboot
boot: failed try but not show ok
boot-aging: failed (dont have it)
system: failed (dont have it)
md5checksum: failed (dont have it)
Click to expand...
Click to collapse
Either Method 1 or Method 2 has these files. Try to navigate the folders. Then manually flash them. If you really cant find them ill send you them later this day or tomorrow since im not home. To be exact your device does showup under fastboot devices.
Puddi_Puddin said:
Either Method 1 or Method 2 has these files. Try to navigate the folders. Then manually flash them. If you really cant find them ill send you them later this day or tomorrow since im not home. To be exact your device does showup under fastboot devices.
Click to expand...
Click to collapse
Many thanx dear,
now i download Method 2, i hope to get repair,
Thanx
almuhajir said:
Many thanx dear,
now i download Method 2, i hope to get repair,
Thanx
Click to expand...
Click to collapse
It will, it is software based.. If your device shows up under Fastboot then there is no problem If you have no wifi on boot make sure to post what i said before, keep in mind your device will be at 3.2.1 OOS.
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.