[Q] Rooted and installed new rom but can't flash new kernel - Xperia Arc Q&A, Help & Troubleshooting

Alright, so I've rooted my Sony Xperia Arc S (Lt8i) and installed the latest JJHybrid 3.1 ROM. I wanna install the Trinity ICS kernel.
So from what I know I need to have an unlocked bootloader. I unlocked my bootloader the first time using the fastboot cmd method. It showed that it worked. However, trying a few times to flash the new kernel, I keep getting the error that my phone is not rooted when it is! So I thought the bootloader was not locked and tried to unlock it again... This was what I got.
C:\Android Rooting\unlock xperia arc bootloaders\fastboot_with_Android_USB_file\
fastboot_with_Android_USB_file\fastboot> fastboot.exe -i 0x0fce getvar version
version: 0.3
finished. total time: 0.001s
C:\Android Rooting\unlock xperia arc bootloaders\fastboot_with_Android_USB_file\
fastboot_with_Android_USB_file\fastboot>fastboot.exe -i 0x0fce oem unlock 0x!36D
24885F3ADF806
...
(bootloader) Unlock phone requested
FAILED (remote: oem unlock 0xFFFFFFFFFFFFFFFF)
finished. total time: 0.002s
Click to expand...
Click to collapse
Using Flashtools to install the kernel fails too... I get the following
01/016/2012 03:16:14 - INFO - <- This level is successfully initialized
01/016/2012 03:16:15 - INFO - Flashtool Version 0.6.9.1 built on 2012-04-09 19:22:19
01/016/2012 03:16:15 - INFO - You can drag and drop ftf files here to start flashing them
01/016/2012 03:16:16 - INFO - Device connected in fastboot mode
01/016/2012 03:16:21 - INFO - Launching Fastboot Toolbox 1.0 by DooMLoRD
01/016/2012 03:16:21 - INFO - Device Status: FASTBOOT mode
01/016/2012 03:16:56 - INFO - Selected kernel (boot.img or kernel.sin): C:\Flashtool\firmwares\kernelboot.img
01/016/2012 03:16:56 - INFO - Flashing selected kernel
01/016/2012 03:16:56 - INFO - sending 'boot' (8366 KB)...
01/016/2012 03:16:56 - INFO - FAILED (remote: The Device must be rooted first)
01/016/2012 03:16:56 - INFO - finished. total time: 0.001s
01/016/2012 03:16:56 - INFO - FASTBOOT Output:
sending 'boot' (8366 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.001s
01/016/2012 03:16:56 - INFO - Please check the log before rebooting into system
01/017/2012 03:17:03 - INFO - Finished Fastboot Toolbox
Click to expand...
Click to collapse
I'- very sure that I have root access... I have CWM installed.
I tried using the fastboot cmd dialouge to install the kernel but I get this message
C:\Android Rooting\unlock xperia arc bootloaders\fastboot_with_Android_USB_file\
fastboot_with_Android_USB_file\fastboot>fastboot flash boot kernelboot.img
sending 'boot' (8366 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.001s
C:\Android Rooting\unlock xperia arc bootloaders\fastboot_with_Android_USB_file\
fastboot_with_Android_USB_file\fastboot>
Click to expand...
Click to collapse
Can someone tell me what is going on? What should I do? %r9:

C:\Android Rooting\unlock xperia arc bootloaders\fastboot_with_Android_USB_file\
fastboot_with_Android_USB_file\fastboot> fastboot.exe -i 0x0fce getvar version
version: 0.3
finished. total time: 0.001s
C:\Android Rooting\unlock xperia arc bootloaders\fastboot_with_Android_USB_file\
fastboot_with_Android_USB_file\fastboot>fastboot.e xe -i 0x0fce oem unlock 0x!36D
24885F3ADF806
...
(bootloader) Unlock phone requested
FAILED (remote: oem unlock 0xFFFFFFFFFFFFFFFF)
finished. total time: 0.002s
Click to expand...
Click to collapse
on your 1st Quote it clearly states that the (bootloader) Unlock phone requested
FAILED....your bootloader still may b locked...

Yeah your bootloader is locked go unlock it, mate.
Sent from my LT18i using xda app-developers app

Thanks for the replies...
Here's the weird thing. The first time I tried unlocking my bootloader, it said the unlocking was successful. Since it was successful, I didn't save a log of it. Subsequent attempts at trying to unlock my bootloader again was totally unsuccessful and resulted in the error.
I've tried alot of guides around the forums but strangely none works. Could anyone of you suggest any method which you tried before that worked for you? In the meanwhile, I'll try to unlock my bootloader again

OrionyX said:
Thanks for the replies...
Here's the weird thing. The first time I tried unlocking my bootloader, it said the unlocking was successful. Since it was successful, I didn't save a log of it. Subsequent attempts at trying to unlock my bootloader again was totally unsuccessful and resulted in the error.
I've tried alot of guides around the forums but strangely none works. Could anyone of you suggest any method which you tried before that worked for you? In the meanwhile, I'll try to unlock my bootloader again
Click to expand...
Click to collapse
There's the problem
You only need to unlock it once...

BL unlocking is very much easy.
Follow the instructions again carefully mate
.
Sent from my LT15i using Tapatalk 2

OrionyX said:
Thanks for the replies...
Here's the weird thing. The first time I tried unlocking my bootloader, it said the unlocking was successful. Since it was successful, I didn't save a log of it. Subsequent attempts at trying to unlock my bootloader again was totally unsuccessful and resulted in the error.
I've tried alot of guides around the forums but strangely none works. Could anyone of you suggest any method which you tried before that worked for you? In the meanwhile, I'll try to unlock my bootloader again
Click to expand...
Click to collapse
BL only need to be unlocked once.
Sent from my LT18i using xda app-developers app

Related

[Q] Can't flash doomkernel, waiting for device

Hey all,
Just nuked my phone set up so I could install the latest doomkernel (first time wanted to try it out) on my GSM play running latest SE software, but it refuses to flash the boot.img file to the device.
I unlocked (after a re-lock a while ago) the boot loader and can access fastboot (blue LED on phone, "fastboot.exe -i 0x0fce getvar version" brings a version 0.3)
fastboot.exe flash boot boot.img ---> stuck on "< waiting for device >" message
I tried with the latest flashtool and I got this from the log:
Code:
05/046/2012 00:46:31 - INFO - Device connected in fastboot mode
05/046/2012 00:46:42 - INFO - Selected kernel (boot.img or kernel.sin): C:\boot.img
05/046/2012 00:46:42 - INFO - Flashing selected kernel
05/046/2012 00:46:43 - INFO - FASTBOOT Output:
sending 'boot' (7330 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.001s
I then rooted the phone using zergrush and it's rooted properly, but I can't for the life of me figure out why I can't push the kernel, since I know the fastboot process is working because I used it to unlock the boot loader
Code:
C:\Users\Access\Downloads>fastboot.exe -i 0x0fce oem unlock 0x
< waiting for device >
... INFOUnlock phone requested
INFOErasing block 0x00000d00
INFOErasing block 0x00000e00
INFOErasing block 0x00000f00
Is there something I'm missing or will I never be able to have a custom kernel?
Any ideas and suggestions appreciated thanks
I have the exact same problem with my Arc S, can`t figure out why is getting stuck on "< waiting for device >"
Try fastboot -i 0x0fce flash boot boot.img
Michealtbh said:
Try fastboot -i 0x0fce flash boot boot.img
Click to expand...
Click to collapse
Thx alot man, it worked like a charm !
Code:
C:\Android>fastboot.exe -i 0x0fce getvar version
version: 0.3
finished. total time: 0.001s
C:\Android>fastboot -i 0x0fce flash boot boot.img
sending 'boot' (7922 KB)... INFOUSB download speed was 9187kB/s
OKAY [ 0.892s]
writing 'boot'... INFODownload buffer format: boot IMG
INFOFlash of partition 'boot' requested
INFOS1 partID 0x00000003, block 0x00000280-0x000002e3
INFOErase operation complete, 0 bad blocks encountered
INFOFlashing...
INFOFlash operation complete
OKAY [ 1.532s]
finished. total time: 2.424s

[Q] Xperia S JB

When someone will release the FTF file for JB?
Is anyone here got the JB update?
ygil1234 said:
When someone will release the FTF file for JB?
Is anyone here got the JB update?
Click to expand...
Click to collapse
I love a new and refreshing post about JB. :thumbup:
Sometimes i wonder why people buy a smartphone if they are blind or can't read. :screwy:
From the planet Nexus 7
ygil1234 said:
When someone will release the FTF file for JB?
Is anyone here got the JB update?
Click to expand...
Click to collapse
I think the update haven't roll out,he just said the first build etc...some said will roll out on first week of June...
Sent from my Sony Xperia™ sola using XDA Premium App
There is one
Bin4ry has released a JB ftf file but its not to safe to flash it
Envious_Data said:
Bin4ry has released a JB ftf file but its not to safe to flash it
Click to expand...
Click to collapse
And here's the link of that thread
http://forum.xda-developers.com/showthread.php?t=2295033
Sent from my Sony Xperia™ sola using XDA Premium App
http://forum.xda-developers.com/showthread.php?t=2252940
Doomlord posted that version of Sony Jelly Bean, I installed it a month from now, and it's clean and there are not so much bugs, you can try it !
But Sony France announced yesterday that they were releasing Jelly Bean for Xperia S !
now, now, patience is a virtue
Until now there is no JB ftf.......
khaled222 said:
Until now there is no JB ftf.......
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2295033
Please read it carefully
MaxPayne3004 said:
http://forum.xda-developers.com/showthread.php?t=2295033
Please read it carefully
Click to expand...
Click to collapse
hai guys, beg ur pardon if iam asking a noobish question, but i am tired of waitting for Offical JB update from sony
i would like to install "LT26i_DooMLoRD_leak-JB-197.zip" and iam stuck in between now will u guys help me get out of this mess
My phone is LT26i and in configuration it says "Bootloader unlock allowed :Yes" .
and my build is 6.1.A.2.55.
i Rooted my phone with " ERoot-1.0.14.exe.7z "
and when i flash the kernel with " S-DooMLoRD-JB_leak_68-AdvStk_v1.elf " i get the error like this
27/006/2013 12:06:22 - INFO - Device connected in fastboot mode
27/006/2013 12:06:29 - INFO - Launching Fastboot Toolbox 1.0 by DooMLoRD
27/006/2013 12:06:29 - INFO - Device Status: FASTBOOT mode
27/006/2013 12:06:40 - INFO - Selected kernel (boot.img or kernel.sin): C:\Flashtool\kernal\S-DooMLoRD-JB_leak_68-AdvStk_v1.elf
27/006/2013 12:06:40 - INFO - Flashing selected kernel
27/006/2013 12:06:40 - INFO - sending 'boot' (8855 KB)...
27/006/2013 12:06:40 - INFO - FAILED (remote: The Device must be rooted first)
27/006/2013 12:06:40 - INFO - finished. total time: 0.016s
27/006/2013 12:06:40 - INFO - FASTBOOT Output:
sending 'boot' (8855 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.016s
what should i do now ? plz help !!
epicsha said:
hai guys, beg ur pardon if iam asking a noobish question, but i am tired of waitting for Offical JB update from sony
i would like to install "LT26i_DooMLoRD_leak-JB-197.zip" and iam stuck in between now will u guys help me get out of this mess
My phone is LT26i and in configuration it says "Bootloader unlock allowed :Yes" .
and my build is 6.1.A.2.55.
i Rooted my phone with " ERoot-1.0.14.exe.7z "
and when i flash the kernel with " S-DooMLoRD-JB_leak_68-AdvStk_v1.elf " i get the error like this
27/006/2013 12:06:22 - INFO - Device connected in fastboot mode
27/006/2013 12:06:29 - INFO - Launching Fastboot Toolbox 1.0 by DooMLoRD
27/006/2013 12:06:29 - INFO - Device Status: FASTBOOT mode
27/006/2013 12:06:40 - INFO - Selected kernel (boot.img or kernel.sin): C:\Flashtool\kernal\S-DooMLoRD-JB_leak_68-AdvStk_v1.elf
27/006/2013 12:06:40 - INFO - Flashing selected kernel
27/006/2013 12:06:40 - INFO - sending 'boot' (8855 KB)...
27/006/2013 12:06:40 - INFO - FAILED (remote: The Device must be rooted first)
27/006/2013 12:06:40 - INFO - finished. total time: 0.016s
27/006/2013 12:06:40 - INFO - FASTBOOT Output:
sending 'boot' (8855 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.016s
what should i do now ? plz help !!
Click to expand...
Click to collapse
I think you can unlock your bootloader, but you had not do and / or you failed root
Sony Mobile Germany says XPERIA S Jelly Bean Rollout Has Not Started...
The announcement of our french colleagues was a mistake...
Sent from my Sony Xperia™ sola using XDA Premium App
epicsha said:
hai guys, beg ur pardon if iam asking a noobish question, but i am tired of waitting for Offical JB update from sony
i would like to install "LT26i_DooMLoRD_leak-JB-197.zip" and iam stuck in between now will u guys help me get out of this mess
My phone is LT26i and in configuration it says "Bootloader unlock allowed :Yes" .
and my build is 6.1.A.2.55.
i Rooted my phone with " ERoot-1.0.14.exe.7z "
and when i flash the kernel with " S-DooMLoRD-JB_leak_68-AdvStk_v1.elf " i get the error like this
27/006/2013 12:06:22 - INFO - Device connected in fastboot mode
27/006/2013 12:06:29 - INFO - Launching Fastboot Toolbox 1.0 by DooMLoRD
27/006/2013 12:06:29 - INFO - Device Status: FASTBOOT mode
27/006/2013 12:06:40 - INFO - Selected kernel (boot.img or kernel.sin): C:\Flashtool\kernal\S-DooMLoRD-JB_leak_68-AdvStk_v1.elf
27/006/2013 12:06:40 - INFO - Flashing selected kernel
27/006/2013 12:06:40 - INFO - sending 'boot' (8855 KB)...
27/006/2013 12:06:40 - INFO - FAILED (remote: The Device must be rooted first)
27/006/2013 12:06:40 - INFO - finished. total time: 0.016s
27/006/2013 12:06:40 - INFO - FASTBOOT Output:
sending 'boot' (8855 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.016s
what should i do now ? plz help !!
Click to expand...
Click to collapse
You can not properly flash .efl files using Flashtools.
Follow The @DooMLoRD's for custom elf flashing.
Link here ----> http://forum.xda-developers.com/showthread.php?p=23181182#post23181182
If this helps you please press thanks before leaving! Thank You!
Personally I Think The Bootloader is not Unlocked.

plz help noobs like me !

hai guys, beg ur pardon if iam asking a noobish question, but i am tired of waitting for Offical JB update from sony
i would like to install "LT26i_DooMLoRD_leak-JB-197.zip" and iam stuck in between now will u guys help me get out of this mess
My phone is LT26i and in configuration it says "Bootloader unlock allowed :Yes" .
and my build is 6.1.A.2.55.
i Rooted my phone with " ERoot-1.0.14.exe.7z "
and when i flash the kernel with " S-DooMLoRD-JB_leak_68-AdvStk_v1.elf " i get the error like this
27/006/2013 12:06:22 - INFO - Device connected in fastboot mode
27/006/2013 12:06:29 - INFO - Launching Fastboot Toolbox 1.0 by DooMLoRD
27/006/2013 12:06:29 - INFO - Device Status: FASTBOOT mode
27/006/2013 12:06:40 - INFO - Selected kernel (boot.img or kernel.sin): C:\Flashtool\kernal\S-DooMLoRD-JB_leak_68-AdvStk_v1.elf
27/006/2013 12:06:40 - INFO - Flashing selected kernel
27/006/2013 12:06:40 - INFO - sending 'boot' (8855 KB)...
27/006/2013 12:06:40 - INFO - FAILED (remote: The Device must be rooted first)
27/006/2013 12:06:40 - INFO - finished. total time: 0.016s
27/006/2013 12:06:40 - INFO - FASTBOOT Output:
sending 'boot' (8855 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.016s
what should i do now ? plz help !!
You have not unlocked your bootloader. Just follow Sony's official guide to unlock your boot loader. After you unlock your boot loader, the status in your service menu should say - "Boot loader unlocked:yes"
Then you will be able to flash the custom kernel.
Sent from my LT26i using xda app-developers app
abcdjdj said:
You have not unlocked your bootloader. Just follow Sony's official guide to unlock your boot loader. After you unlock your boot loader, the status in your service menu should say - "Boot loader unlocked:yes"
Then you will be able to flash the custom kernel.
Sent from my LT26i using xda app-developers app
Click to expand...
Click to collapse
But mate my Bootloader is already on yes
epicsha said:
But mate my Bootloader is already on yes
Click to expand...
Click to collapse
Yes means it is unlockable...just unlock then try
sent from Lt28at loaded with Lt28i fw ics
smartboy0668 said:
Yes means it is unlockable...just unlock then try
sent from Lt28at loaded with Lt28i fw ics
Click to expand...
Click to collapse
oh, TY both of u i got it now. i will try it .
Another question is if i unlock the bootloader will EMMA detect the phone ?
epicsha said:
oh, TY both of u i got it now. i will try it .
Another question is if i unlock the bootloader will EMMA detect the phone ?
Click to expand...
Click to collapse
Nope,forget to update the official way
Sent from my Xperia SL using xda premium
epicsha said:
hai guys, beg ur pardon if iam asking a noobish question, but i am tired of waitting for Offical JB update from sony
i would like to install "LT26i_DooMLoRD_leak-JB-197.zip" and iam stuck in between now will u guys help me get out of this mess
My phone is LT26i and in configuration it says "Bootloader unlock allowed :Yes" .
and my build is 6.1.A.2.55.
i Rooted my phone with " ERoot-1.0.14.exe.7z "
and when i flash the kernel with " S-DooMLoRD-JB_leak_68-AdvStk_v1.elf " i get the error like this
27/006/2013 12:06:22 - INFO - Device connected in fastboot mode
27/006/2013 12:06:29 - INFO - Launching Fastboot Toolbox 1.0 by DooMLoRD
27/006/2013 12:06:29 - INFO - Device Status: FASTBOOT mode
27/006/2013 12:06:40 - INFO - Selected kernel (boot.img or kernel.sin): C:\Flashtool\kernal\S-DooMLoRD-JB_leak_68-AdvStk_v1.elf
27/006/2013 12:06:40 - INFO - Flashing selected kernel
27/006/2013 12:06:40 - INFO - sending 'boot' (8855 KB)...
27/006/2013 12:06:40 - INFO - FAILED (remote: The Device must be rooted first)
27/006/2013 12:06:40 - INFO - finished. total time: 0.016s
27/006/2013 12:06:40 - INFO - FASTBOOT Output:
sending 'boot' (8855 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: 0.016s
what should i do now ? plz help !!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=41894424&postcount=11
Please don't post anywhere
epicsha said:
oh, TY both of u i got it now. i will try it .
Another question is if i unlock the bootloader will EMMA detect the phone ?
Click to expand...
Click to collapse
Yes.
Rishi Raj Is Right!
Finally I have done it! Yt? Guys for the help
Yea if the bootlooder is unlocked EMMA will not detect and well prompt "unauthorized modification detected "
But if we relock the bootlooder then no one will understand that it was unlocked
I have already tested it §§§§§
Sent from my C6602 using xda app-developers app
EMMA is meant only for unlocked bootloader. After unlocking your bootloader, you won't be able to update using Sony Update Service or PC Companion. EMMA is officially provided by Sony so you can still update

[Q] Help with fastboot a kernel pls!!

hello guys i got the xperia arc s lt18i and im trying to change kernel with flashtool,fastboot the kernel is named boot.img and when i select it the follow commands appear and fastboot fails....anyone has the solution? i installed the drivers and my device is rooted and unlocked...
18/042/2014 15:42:58 - INFO - Device connected in fastboot mode
18/043/2014 15:43:06 - INFO - Device Status: FASTBOOT mode
18/043/2014 15:43:23 - INFO - Selected kernel (boot.img or kernel.sin): C:\Flashtool\drivers\boot.img
18/043/2014 15:43:23 - INFO - Flashing selected kernel
18/043/2014 15:43:23 - INFO - sending 'boot' (3470 KB)...
18/043/2014 15:43:23 - INFO - FAILED (remote: The Device must be rooted first)
18/043/2014 15:43:23 - INFO - finished. total time: -0.000s
18/043/2014 15:43:23 - INFO - FASTBOOT Output:
sending 'boot' (3470 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: -0.000s
pantazis1 said:
hello guys i got the xperia arc s lt18i and im trying to change kernel with flashtool,fastboot the kernel is named boot.img and when i select it the follow commands appear and fastboot fails....anyone has the solution? i installed the drivers and my device is rooted and unlocked...
18/042/2014 15:42:58 - INFO - Device connected in fastboot mode
18/043/2014 15:43:06 - INFO - Device Status: FASTBOOT mode
18/043/2014 15:43:23 - INFO - Selected kernel (boot.img or kernel.sin): C:\Flashtool\drivers\boot.img
18/043/2014 15:43:23 - INFO - Flashing selected kernel
18/043/2014 15:43:23 - INFO - sending 'boot' (3470 KB)...
18/043/2014 15:43:23 - INFO - FAILED (remote: The Device must be rooted first)
18/043/2014 15:43:23 - INFO - finished. total time: -0.000s
18/043/2014 15:43:23 - INFO - FASTBOOT Output:
sending 'boot' (3470 KB)...
FAILED (remote: The Device must be rooted first)
finished. total time: -0.000s
Click to expand...
Click to collapse
it says you have no root....
also did you tried ''cmd fastboot'' (over android sdk)??? i dont like kernel flashing over fashool
bejunk said:
it says you have no root....
also did you tried ''cmd fastboot'' (over android sdk)??? i dont like kernel flashing over fashool
Click to expand...
Click to collapse
can you send me a tutorial ? i ve never heard of that
pantazis1 said:
can you send me a tutorial ? i ve never heard of that
Click to expand...
Click to collapse
1 install android sdk from here (just leave all the stuff like it is & press on install packages): http://developer.android.com/sdk/index.html
2 go to: [install location of android sdk]\sdk\platform-tools put kernel (boot.img) here
3 click in some empty space in this folder, then HOLD [SHIFT] while right click in this folder & choose ''open command prompt here''
4 power off phone. hold the menu-button while connecting to pc. the blue led will lit which means the device is in fastboot mode:good:
5 now in the command prompt enter ''fastboot flash boot boot.img'' it will flash kernel & tell u all is okay.
6 done
i get same fail that device must be rooted first oO its kinda wird because my device is rooted i use SU daily im 100% sure :/ maybe fastboot can't get permission for root but i don't know how to do that :/
pantazis1 said:
i get same fail that device must be rooted first oO its kinda wird because my device is rooted i use SU daily im 100% sure :/ maybe fastboot can't get permission for root but i don't know how to do that :/
Click to expand...
Click to collapse
okay some guesses.
1. you use win 8/81 ? --> there some driver problems there is a solution here in xda just google. need install these
2 you need install fastboot driver from flashtool in its install dir in driver folder
3 can try this to see if device connected (from sony site):
Enter fastboot.exe -i 0x0fce getvar version, and verify that you get a response back (for example "0.3"). This means your device is connected properly.
Click to expand...
Click to collapse
good luck
No root here means your bootloader is locked...
Sent from my Xperia Z1 Compact using Tapatalk 2

FAILED (remote: Command not allowed)

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.

Categories

Resources