[Q] xperia L install kernal error - General Questions and Answers

i have a xperia L laying around that i want to install android 4.4.2 on
ive already rooted it and unlocked its bootloader, but i cant flash a kernel onto it
the kernel im trying to flash is a IMG file, and im using flashtool to flash the kernel onto it, but everytime i try, i get this error:
Code:
13/009/2014 17:09:50 - INFO - Selected kernel (boot.img or kernel.sin): C:\Users\noise\Desktop\phone fix\kernal\boot.img
13/009/2014 17:09:50 - INFO - Flashing selected kernel
13/009/2014 17:09:51 - INFO - sending 'boot' (13920 KB)...
13/009/2014 17:09:51 - INFO - OKAY [ 0.440s]
13/009/2014 17:09:51 - INFO - writing 'boot'...
13/009/2014 17:09:51 - INFO - FAILED (remote: Command not allowed)
13/009/2014 17:09:51 - INFO - finished. total time: 0.441s
13/009/2014 17:09:51 - INFO - FASTBOOT Output:
sending 'boot' (13920 KB)...
OKAY [ 0.440s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.441s
i dont know whats wrong, ive tried multiple times, but it does not seem to work
also, i cant do the "*#*#7378423#*#*" command anymore after unlocking the bootloader
please help

Related

WiFi issues

So I downloaded this Archive.zip from http://forum.xda-developers.com/showthread.php?t=2064868
and I boot my device to fastboot...
now on my pc when i type:
fastboot flash recovery adsp.img
I get:
sending 'recovery' (6345 KB)...
OKAY [ 0.950s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 0.998s
--------------------------------------------------------
or if i try:
>fastboot flash adsp adsp.img
sending 'adsp' (6345 KB)...
OKAY [ 0.949s]
writing 'adsp'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.485s
What am I doing wrong? I have HBOOT-1.13 and viperones rom on my HTC One S
Im pretty sure you cant flash it through fastboot.
You need hboot 1.09 or lower and flash through recovery.

nexus 5 (LG-D820) stuck in CWM recovery

hello,
i've got this lg-D820 stuck in CWM Recovery v6.0.4.5 screen
i want to flash it back to recovery and downloaded 5.1.1 factory image from google developers site
but i always get error while flashing bootloader,something like this-
Code:
sending 'bootloader' (3119 KB)...
OKAY [ 0.334s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 43.583s
rebooting into bootloader...
OKAY [ 0.076s]
finished. total time: 0.080s
< waiting for device >
i need help to fix this set

[Completed] FAILED(remote: Command not allowed) sony xperia z1s c6916

05/052/2017 17:52:19 - INFO - (FastBootToolBoxJob.java:185) - Selected kernel (boot.img or kernel.sin): C:\Users\Admin\Downloads\boot-2015-04-18.img
05/052/2017 17:52:19 - INFO - (FastBootToolBoxJob.java:186) - Flashing selected kernel
05/052/2017 17:52:19 - INFO - (ProcessBuilderWrapper.java:90) - sending 'boot' (15370 KB)...
05/052/2017 17:52:19 - INFO - (ProcessBuilderWrapper.java:90) - OKAY [ 0.507s]
05/052/2017 17:52:19 - INFO - (ProcessBuilderWrapper.java:90) - writing 'boot'...
05/052/2017 17:52:19 - INFO - (ProcessBuilderWrapper.java:90) - FAILED (remote: Command not allowed)
05/052/2017 17:52:19 - INFO - (ProcessBuilderWrapper.java:90) - finished. total time: 0.510s
05/052/2017 17:52:19 - INFO - (FastBootToolBoxJob.java:189) - FASTBOOT Output:
sending 'boot' (15370 KB)...
OKAY [ 0.507s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.510s
I have sony Xperia Z1s C6916 and just unlocked bootloader using flashtool, but still it says Command not allowed while trying to install kernel.
Pls help, i'm beginner here. (also i'm using kingroot and can this be the problem?(
Hi there and welcome to assist,
You have a lot of tutorials:
[25NOV][FLASHTOOL GUIDE] HOW TO for n00bies - G-FACE GUIDE
[Tutorial] Xperia Z1 Bootloader Unlocking/Relocking
Root, Backup TA, Unlock bootloader and more! The ultimate Xperia Z1 guide
You'll have to create an account to post in the main forums if you have any other questions.
> Sony Xperia Z1 > Xperia Z1 Q&A, Help & Troubleshooting
Good luck

Z3 bricked, no recovery

Hi all,
somehow my sons' D6603 messed up and didn't boot anymore. Had an old CarbonROM installed before, but that failed for no reason I can pinpoint.
OK, to recover I tried to reflash the ROM - but boot process got stuck in boot animation for hours (until battery ran out).
OK, so I fired up flashtool and tried to install an FTF - but all FTFs I tried to retrieve failed to unpack.
OK - one more try - got me a stock ROM that was supposed to be flashed through recovery.
Now I get Sony splashscreen, then display turns black and stays like that forever. Only sign of something happening is that the notification LED blinks occasionally.
I tried to enter recovery - wouldn't work at all: never saw any change in boot process.
I can put the phone into flash mode and into fastboot - so I tried to flash a new TWRP:
Code:
[email protected] ~/temp/TWRP-z3 $ fastboot flash FOTAKernel recovery.img
target didn't report max-download-size
sending 'FOTAKernel' (15904 KB)...
OKAY [ 0.502s]
writing 'FOTAKernel'...
OKAY [ 1.056s]
finished. total time: 1.558s
[email protected] ~/temp/TWRP-z3 $ fastboot flash recovery recovery.img
target didn't report max-download-size
sending 'recovery' (15904 KB)...
OKAY [ 0.501s]
writing 'recovery'...
OKAY [ 1.055s]
finished. total time: 1.556s
But still the mobile won't boot into recovery
OK, there's a different TWRP available - but I can't flash it to FOTAkernel:
Code:
[email protected] ~/Downloads $ fastboot flash FOTAkernel twrp_z3_2018-03-28.img
target didn't report max-download-size
sending 'FOTAkernel' (10808 KB)...
OKAY [ 0.342s]
writing 'FOTAkernel'...
FAILED (remote: Command not allowed)
finished. total time: 0.345s
[email protected] ~/Downloads $ fastboot flash recovery twrp_z3_2018-03-28.img
target didn't report max-download-size
sending 'recovery' (10808 KB)...
OKAY [ 0.342s]
writing 'recovery'...
OKAY [ 0.721s]
finished. total time: 1.063s
Can anyone help me to get stuff working again? I'm lost for options right now - TWRP won't come up, and I can't get an FTF via flashtool to my harddrive. Any other ways to unbrick the phone?
Got a recent LinuxMint 19.x here as my machine right now. Getting a Windows up and running would be an obstacle (although I might get a hand to one).

now my device(mi a2 lite) is stuck in a boot loop and the device is locked after android 10 update

using cmd
when trying to unlock oem; giving:
FAILED (remote: OEM unlock is not allowed)
finished. total time: 0.011s
-----------------------------------------------------------------
when trying to flash boot or recovery; giving:
boot:
sending 'boot' (29069 KB)...
OKAY [ 0.765s]
writing 'boot'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.787s
recovery:
sending 'recovery' (42204 KB)...
OKAY [ 1.103s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 1.121s
-----------------------------------------------------------------
when trying to change the partition giving:
C:\Users\Rfastboot --set-active=b
fastboot: unknown option -- set-active=b
-----------------------------------------------------------------
please help!!!
FkReMy said:
using cmd
when trying to unlock oem; giving:
FAILED (remote: OEM unlock is not allowed)
finished. total time: 0.011s
-----------------------------------------------------------------
when trying to flash boot or recovery; giving:
boot:
sending 'boot' (29069 KB)...
OKAY [ 0.765s]
writing 'boot'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.787s
recovery:
sending 'recovery' (42204 KB)...
OKAY [ 1.103s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 1.121s
-----------------------------------------------------------------
when trying to change the partition giving:
C:\Users\Rfastboot --set-active=b
fastboot: unknown option -- set-active=b
-----------------------------------------------------------------
please help!!!
Click to expand...
Click to collapse
From what I found on the internet, I guess you didn't turn on the setting `oem allow unlock' in developer settings.
But isn't there `rescue party' (a subsystem of androids recovery which shows two options: 1) Try again 2) Factory data reset)?
If it is, just press that Try again button, wait until it boots into rescue party again and then press the Try again button again. Do that 5-7 times in a row (depending on the phone). Your phone should detect that your current slot is unbootable and should boot into the unupdated slot.
You could also try to find the stock image (or whatever image you have currently installed) and flash it within recovery (there should be a button labeled like `update...' or `sideload...' or something). That should also work.
If nothing helps, you could also factory data reset and hope that it works now...
If that also doesn't work, you could research abit about edl (emergency donwload mode) and how to use it to reflash your device.

Categories

Resources