Related
Hi,
i have a problem with my Folio100. After update to Custom ROM, folio goes to black screen and freeze. Device is ROOTed, have CWM-based Recovery v5.5.0.4.
i try this ROM:
CM-9.0.0-RC0-folio100-KANG
CM-7.1.0-ToshibaFOLIO
Folio3xv03a
Folio3xv04
All of this ROMs cannot works. Second problem is, the device cannot mount external SDcard (only internal sdcard) and now, i am not able to copy another ROMs to try it...
ps:sorry for my english...
Try this:
http://forum.xda-developers.com/showpost.php?p=21955732&postcount=2
thanks but i already have cwm-recovery-5.5.0.4 and owner of post warms...
"!!! WARNING !!! Don't reflash this update if your are already on 5.5.0.4"
and the owner also write:
!!! WARNING !!! Don't flash another rom update with this recovery
With your cwm 5.5.0.4 you only can install this rom
[DEV][WIP] ICS / CM9 (4.0.3) Alpha 1 - 2.6.39 kernel - Last update 29/01/2012
But I think there is something defect on your filesystem!
Have you ever make a restore to factory-reset?
My Opinion is to make the following commands with fastboot:
fastboot erase recovery
fastboot erase linux
fastboot erase system
fastboot -w fastboot
flash recovery recovery.img (copy the recovery.img in the fastboot directory)
fastboot reboot
Hey guys, I can't seem to flash a kernel via fastboot.
Here's my info
Phone : Xperia Mini Pro
Root : Rooted
Bootloader : Unlocked
Android Version : 2.3.4 (but have tried with 4.0.4 too)
USB debugging on
MSC mode activated
Unknown souces : checked
LOG :
17/012/2012 14:12:13 - INFO - FASTBOOT Output:
sending 'boot' (4926 KB)...
FAILED (remote: Unrecognized command, bork!)
finished. total time: 0.000s
I'm trying to install CM9, I extracted boot.img
fastboot detects device but fails when trying to flash
Any ideas please?
(if you need more info, more than welcome)
Try to redownload the kernel,Maybe that will work Or try to use Flashtool to flash the kernel
Sent from my Xperia Mini using XDA Premium
Singgih4050 said:
Try to redownload the kernel,Maybe that will work Or try to use Flashtool to flash the kernel
Sent from my Xperia Mini using XDA Premium
Click to expand...
Click to collapse
I've tried several different kernels and I've tried with flashtool and Command Prompt
Mikeboss71 said:
I've tried several different kernels and I've tried with flashtool and Command Prompt
Click to expand...
Click to collapse
Do you have tried to install other kernel?
Sent from my Xperia Mini using XDA Premium
Singgih4050 said:
Do you have tried to install other kernel?
Sent from my Xperia Mini using XDA Premium
Click to expand...
Click to collapse
yeah i've tried to flash different kernels but still the same problem :/
which method you are using?
Try with my tool' in my signature
Sent from my WT19a using xda app-developers app
Did you unlock your bootloader via sony or via testpoint method?
Have you checked *#*#7378423#*#* and then Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, it's another problem...
To all the ppl who replied before - Did you even read the log?
Mikeboss71 said:
17/012/2012 14:12:13 - INFO - FASTBOOT Output:
sending 'boot' (4926 KB)...
FAILED (remote: Unrecognized command, bork!)
finished. total time: 0.000s
Click to expand...
Click to collapse
"Unrecognized command"
You need to use the following command:
Code:
fastboot flash boot boot.img
or
Code:
fastboot -i 0x0fce flash boot boot.img
Someguyfromhell said:
To all the ppl who replied before - Did you even read the log?
"Unrecognized command"
You need to use the following command:
Code:
fastboot flash boot boot.img
or
Code:
fastboot -i 0x0fce flash boot boot.img
Click to expand...
Click to collapse
But normally it should have worked, cause with flashtool it should work. Doesn't flashtool do same command like
Code:
fastboot flash boot boot.img
?
Mikeboss71 said:
Hey guys, I can't seem to flash a kernel via fastboot.
Here's my info
Phone : Xperia Mini Pro
Root : Rooted
Bootloader : Unlocked
Android Version : 2.3.4 (but have tried with 4.0.4 too)
USB debugging on
MSC mode activated
Unknown souces : checked
LOG :
17/012/2012 14:12:13 - INFO - FASTBOOT Output:
sending 'boot' (4926 KB)...
FAILED (remote: Unrecognized command, bork!)
finished. total time: 0.000s
I'm trying to install CM9, I extracted boot.img
fastboot detects device but fails when trying to flash
Any ideas please?
(if you need more info, more than welcome)
Click to expand...
Click to collapse
I believe it is a problem with your controller manager kernel. This can occur because of a problem with the remote connections with the driver files. Try flashing your ROM STOCK then do root and then try to apply the kernel
Sorry guys I've been away for a while so I've kinda had to put this on the back burner. but I'm back now
@daydu19
I've tried both methods, Flashtool and through Command Prompt using
Code:
fastboot flash boot boot.img
&
Code:
fastboot -i 0x0fce flash boot boot.img
but no joy
EDIT: I can't unlock my phone with testpoint because of the new securities, my phone is "12W27" :/
@mihahn
I'm not quite sure how I unlocked it I tried several ways, testpoint & sony, the weird thing is that I didn't think that either of them worked but I'm able to flash FTF files with flashtool and also Flashtool says that my bootloader is already unlocked...
Code:
Loader : S1_Loader_Root_773f - Version : R4A066 / Bootloader status : ROOTED
And lastly
Have you checked *#*#7378423#*#* and then Service info > Configuration > Rooting Status. If Bootloader unlock allowed says Yes, it's another problem...
Click to expand...
Click to collapse
It says that it is allowed
@xdevilium
Thanks, I'll try this out and let you know if that helps
EDIT: Nope, doesn't work either
@eltonpestana
I've flashed my device multiple times back to stock to 2.3.4 and 4.0.4, they're FTF files that I found on here but that was the only way I managed to get my phone to work again, When I tried flashing the kernels through fastboot, it came up the errors I mentioned and by so Bricked my phone...
The one thing I haven't tried yet is to use Sony PC companion to "reset" my phone (mainly due to my painfully slow internet connection) but I'm not sure that will do much good seeing as it will restore it to 4.0.4 making it impossible to root and I'll end up having to flash the other FTF again.. no?
is it possible to download a custom kernel as a FTF file and then flash it rather than going through fastboot?
because I can flash the stock kernels (that are in the FTF files) that I got
Worst case scenario are there any good ICS ROMS that will work with the stock kernel?
Try flashing stock ftf and then it should get work done.
Sent from my WT19i using xda app-developers app
---------- Post added at 05:58 PM ---------- Previous post was at 05:51 PM ----------
Apparently not . But cm 7.2 works with stock kernel.
Sent from my WT19i using xda app-developers app
I've already tried :/
thanks, CM 7.2 is gingerbread though, ICS is nicer
anyone?
Heres the new log
C:\Users\Mike\Desktop\fastboot>fastboot devices
YT9001KGWM&ZLP fastboot
C:\Users\Mike\Desktop\fastboot>fastboot -i 0xfce flash boot boot.img
sending 'boot' (4926 KB)...
FAILED (remote: Unrecognized command, bork!)
finished. total time: 0.001s
C:\Users\Mike\Desktop\fastboot>fastboot -i 0xfce flash boot boot.img
sending 'boot' (4926 KB)...
(bootloader) USB download speed was 2505kB/s
OKAY [ 2.030s]
writing 'boot'...
FAILED (remote: Unrecognized command, bork!)
finished. total time: 2.032s
C:\Users\Mike\Desktop\fastboot>fastboot -i 0xfce flash boot boot.img
sending 'boot' (4926 KB)...
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x00000280-0x000002e3
(bootloader) Erase operation complete, 0 bad blocks encountered
(bootloader) Flashing...
(bootloader) Flash operation complete
FAILED (unknown status code)
finished. total time: 1.005s
mihahn said:
But normally it should have worked, cause with flashtool it should work. Doesn't flashtool do same command like
Code:
fastboot flash boot boot.img
?
Click to expand...
Click to collapse
I wonder can anyone help me with this? I recently unlocked my bootloader (with wotanserver.com - test point method) and have since been trying out new kernels.
Unfortunately, I've had some problems with Sirkay's Advanced Stock .587 Kernel when I flash it. http://forum.xda-developers.com/showthread.php?t=1544513
I followed his flashing with flashtool instructions (standard procedure). My phone appears to boot up as normal at first, (the kernel's preinstalled CWM recovery works too) but after the initial boot logo & brightening screen that indicates CWM is present - the screen then just goes black with white LED on (with screen backlight v. slightly on) and nothing else happens, i.e. the phone is well and truly stuck.
The end result is that I have to flash back to the kernel I was previously using. There's nothing in the Flashtool log to suggest any problem with the flashing either, and there's been no problem flashing any .img or .sin files until now - so I assume I have all the correct drivers etc.
Am I overlooking something obvious here? Would be very glad to someone's opinion, this is driving me nuts!
Device: ST18i (unlocked bootloader)
ROM version: Iced Bean 2.1 [.587] - Can be used with any kernel (according to the author)
Baseband version: .77
Hello guys.
I have problem to flash boot.img kernel from custom rom (cm11 and others)
The flashtool keep saying "failed , no rooted device found" but my devise is rooted and has cwm recovery.
i have install succefully the flashtools drivers on my 8.1 windows.
i still have the stock rom ics on my xperia u so guys
please help me, i dont know what else to do to put new rom on my xperia u.
thank you.
use Android SDK and type:
fastboot devices (to check if your device is detected)
fastboot flash boot boot.img (to flash your kernel)
Hello,
After having flash KERNEL_B360a_TOUCH_FIX.img to solve a problem of mount with TWRP on my Honor 9 stf-l09, here I am completely blocked,
When i access TWRP, the screen hangs on teamwin, so I restart the laptop, I waited on "your device has been unlocked and can not be trusted", I do POWER to boot normally and I stumble upon Huawei eRecovery
He offers me: Download latest version and recovery, reboot and shutdown, when I go to Download latest version and recovery it connects to my wifi but still it marks that it does not work ..
I followed this tutorial https://forum.xda-developers.com/honor- ... k-t3696892
I took the last link STF-L09 C432B130 Belgium Germany France Netherlands Portugal Switzerland Spain Italy Austria Bosnia and Herzegovina Poland Denmark Finland Czech Lithuania Romania Serbia Slovenia Hungary Android 7.0 EMUI 5.1
I did as agreed, create the dload folder at the root of my sdcard with inside UPDATE.APP
I did Vol + and - + POWER to install and it marks: Software install failed!
What can I do ? Thank you
What firmware version were you on before flashing KERNEL_B360a_TOUCH_FIX.img ?
Nougat service repair firmware won't work over oreo.
You pasted wrong your link.
Hello,
I used this link https://forum.xda-developers.com/honor-9/development/firmware-huawei-honor-9-stf-l09-stock-t3696892
Yeah, won't work if you were already on oreo.
For the firmware I think it's Android Oreo on Honor 9 (EMUI 8.0) so I have to redo the manipulation with this version ?
I' m guessing you flashed B360 kernel over a B362 kernel partition.
But you could have done something else wrong.
Would you have a link? What should I install?
Don't rush.
When you access TWRP, the screen hangs on teamwin, so you restart. Could you WAIT more when you fell it hangs ? and what twrp version are you using ?
About your kernel flashing ; could you post here the command you used ?
version twrp: stf-twrp-zxz-0.3.img
I waited 10 minutes but nothing.
For the kernel i used fastboot flash kernel KERNEL_B360a_TOUCH_FIX.img
So assuming you flashed B360 kernel over a B362 kernel partition ;
Just flash this stock B362 kernel over your kernel partition to solve your booting problems :
https://mega.nz/#!bdEgiIAJ!sfkzPeBBKVeDzB2ifsczFxJHrKF8JWY1WP1a8PH9fFg
with :
' fastboot flash kernel Stock_KERNEL_STF-L09C432B362.img '
How to fastboot adb on my computer because normally I had to authorize the connection with my honor 9?
Connect your phone to computer via USB.
Hold Volume.down and keep holding it.
Power off phone, then power on while still keeping Vol.down held until you're in bootloader mode aka fzstboot mode.
This should boot you into fastboot mode where you can issue these commands :
fastboot devices
fastboot flash kernel Stock_KERNEL_STF-L09C432B362.img
My phone is USB connected to the PC, I'm in fastboot & rescue mode: Phone unlocked and unlock
On my computer, when I do adb devices it does not detect my phone but when I do fastboot flash kernel .. it marks
target reported download size of 471859200 bytes
sending 'kernel' (24576 KB) ...
OKAY [0.526s]
writing 'kernel' ...
OKAY [0.263s]
finished. total time: 0.792s
Then I did fastboot reboot and it did not solve the problem.
http://prntscr.com/jarq6a
Deadfightmc said:
My phone is USB connected to the PC, I'm in fastboot & rescue mode: Phone unlocked and unlock
On my computer, when I do adb devices it does not detect my phone
Click to expand...
Click to collapse
fastboot is not adb.
adb is not fastboot.
Deadfightmc said:
but when I do fastboot flash kernel .. it marks
target reported download size of 471859200 bytes
sending 'kernel' (24576 KB) ...
OKAY [0.526s]
writing 'kernel' ...
OKAY [0.263s]
finished. total time: 0.792s
Then I did fastboot reboot and it did not solve the problem.
http://prntscr.com/jarq6a
Click to expand...
Click to collapse
So you successfully flashed via fastboot a C432B362 stock kernel over C432B360 kernel fix and it's still bootlooping...
Do you think your region cust may have been something else than European C432 ? Maybe : Japanese C635 ? Russian C10 ?
Download again stf-twrp-zxz-0.3.img and try to flash your non-working twrp with :
fastboot flash recovery_ramdisk stf-twrp-zxz-0.3.img
I downloaded and flash again stf-twrp-zxz-0.3.img but it still hangs on "teamwin" Should I test all possible kernels?
If your bootloops really appeared because you flashed B360kernelfix, flashing the stock kernel of your actual version will solve your issue.
But, before that, does twrp was working ? What do you call 'a problem of mount with twrp' ?
-I'll say user problem- [emoji14]
I wanted to install SuperSU with twrp so I put it on my sdcard, I installed it with twrp but there was an error so I looked at this link https://forum.xda-developers.com/honor-9/development/oreo-t3754483
problems:
Mount system rw
Custom kernel required because of Huawei MMC protection (check second post)
And there he said Download kernel http://www.mediafire.com/file/6n1wfb..._TOUCH_FIX.img
Flash with fastboot.exe kernel flash KERNEL_B360a_TOUCH_FIX.img
So:
1. system and twrp 0.3 were working.
2. you flashed a 'random' supersu via twrp and it gave you errors
3. you flashed B360kernelfix
Am I right ?
Yes that's it
So first we'll try to fix what you did when you flashed a bad supersu (which one ?) by flashing a stock B360 boot image :
fastboot flash ramdisk STF-L09_ramdisk.img
https://forum.xda-developers.com/attachment.php?attachmentid=4420592&d=1518680458
I'm trying to boot an image without flashing it to my Xiaomi:
fastboot boot Image
creating boot image...
creating boot image - 35883008 bytes
Sending 'boot.img' (35042 KB) OKAY [ 0.829s]
Booting FAILED (remote: 'unknown command')
fastboot: error: Command failed
Isn't there a way to do it? It's a Poco M3
Poco M3 has separate recovery partition and TWRP is available too. Why don't you flash it?
You mean flashing the kernel to the recovery partition? How would this work? Flash boot.img to recovery, then do adb reboot recovery, and test the kernel,without rewriting the original kernel?
aIecxs said:
Poco M3 has separate recovery partition and TWRP is available too. Why don't you flash it?
Click to expand...
Click to collapse
You mean flashing the kernel to the recovery partition? How would this work? Flash boot.img to recovery, then do adb reboot recovery, and test the kernel,without rewriting the original kernel?
no I mean flash boot.img to boot and twrp to recovery as usual. I am using this TWRP - encryption only worked on very first boot (don't ask me why) but that was good enough to backup userdata and everything