Hi.
I've unlocked my bootloader last night successfully, and went on to flash a custom boot.img.
First I did "fastboot.exe flash boot boot.img", it went through no problems. However after that, my phone boots up to Sony Ericsson logo, it goes away and screen remains black.
I've tried to flash generic global ROM ( "fastboot flash system boot.img" ) to see if I can at least restore my phone to default ROM, it still acts the same..
Anyone mind helping ?
fastboot flash boot boot.img - flash kernel
fastboot boot boot.img -hotboot kernel
what file you flash for rom?.ftf or img?if .ftf you need flashtool,but for .img just use fastboot
Sent from my LT18i using xda premium
I've used "fastboot flash boot boot.img" as my first step.
The file was .img, obviously.
Flash it back to stock with FlashTool and try it again.
Sent from my iPad 2 using Tapatalk
Heh, I haven't realised that .ftf files flash the entire thing INCLUDING kernel to the phone. Oh well, we learn every day
Thanks guys !
Related
Hi everyone...
I recently installed the latest cm9 on my ARC.
I want to install cm7.2 again, but I can't get it to work.
This is what I do:
1) fastboot the image file (fastboot.exe boot boot.img)
2) Install the zip
3) Clear data/cache
But it just hangs at the CM 7.2 logo.
If I install CM9 again, everything work fine.
Any ideas?
fastboot flash boot boot.img
from the ARC
rashid.fairus said:
fastboot flash boot boot.img
from the ARC
Click to expand...
Click to collapse
Exactly!
With fastboot boot command, you simply make the kernel boot once.
Fastboot flash boot will do it for you!
iR¡[email protected]!*™ via Tapatalk Pro
Thanks guys... I suspected it had something to do with the flashboot command. I'll try it out ASAP.
EDIT: It's working now, thank you
Hey guys, I think i screwed up big time. I have just received my Htc one M8 from rogers (with no bloatware on it .. weird lol ) And i wanted to root it in order to use titanium back up.
So i followed a guide to root the phone everything went well execpt that now my phone boots straight into philz custom recovery....
When i was entering the fastboot commands to flash the recovery to the phone i made a mistake i wrote :
fastboot flash boot recovery.img
instead of
fastboot flash boot recovery recovery.img
....
So my guess is that i have overwritten the boot.img of the phone with the custom recovery which is bad... now i can't use the phone...
Is there a way to flash the stock boot image back? of to restore the phone like it was brand new?
Thanks for you help
Reflash the both with the correct commands !!!
Fastboot flash recovery recovery.img
and
Fastboot flash boot boot.img
Mr Hofs said:
Reflash the both with the correct commands !!!
Fastboot flash recovery recovery.img
and
Fastboot flash boot boot.img
Click to expand...
Click to collapse
Yeah this is what i wanted to do but i couldn't find a boot.img. I did find it eventually. here it is in case anyone needs it
Straight, just saying.
The boot.img is always in the rom....Most roms contain the stock boot.img. or check my backup collection and download the stock rom. It has the stock boot.img inside
Thanks a lot.
Hi,
My phone is rooted and the DPI was customized. I tried to manually flash the OTA but the installation got stuck so I cannot boot into Android anymore. I tried those restore tutorials but when I try to flash using fastboot I get a "FAILED (remote: Permission denied). I tried to clear the cache in the recovery and then it got also stuck and now I can't access recovery.
This is what I can read in the bootloader
---------------------------
FASTBOOT MODE
PRODUCT_NAME - Z00A
VARIANT - ASUS_Z00A
HW_VERSION -
BOOTLOADER VERSION - unknown
IFWI - 0094.0177
SERIAL NUMBER - Xxxxx....
SIGNING - ?
SECURE_BOOT - ?
continue fastboot process
-----------------------------
I just been successful in installing TWRP recovery using the toolkit.
Edit: I installed the latest CM 13 build and it can't boot to Android. It goes straight to TWRP recovery no matter how I turn on the phone. My bootloader still looks the same.
Edit: I tried flashing a prerooted .img and stock recovery and I can go back to recovery but I still can't boot into Android or factory reset or nothing.... I'm desperate!
manlord said:
I just been successful in installing TWRP recovery using the toolkit.
Edit: I installed the latest CM 13 build and it can't boot to Android. It goes straight to TWRP recovery no matter how I turn on the phone. My bootloader still looks the same.
Edit: I tried flashing a prerooted .img and stock recovery and I can go back to recovery but I still can't boot into Android or factory reset or nothing.... I'm desperate!
Click to expand...
Click to collapse
You may need to flash boot.img and droidboot.img for the same version of rom you flashed, ie. if you flashed 139 then you must flash the recovery, boot and droidboot images for 139...
As you found the pre-root rom files, download the whole file and flash these image files too making sure you use the right commands or you will brick your phone...
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash fastboot droidboot.img
fastboot flash system system.img
Just remember, flashing these partitions can, potentially, brick your phone. You do this at your own risk...
Happy flashing....
ultramag69 said:
You may need to flash boot.img and droidboot.img for the same version of rom you flashed, ie. if you flashed 139 then you must flash the recovery, boot and droidboot images for 139...
As you found the pre-root rom files, download the whole file and flash these image files too making sure you use the right commands or you will brick your phone...
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash fastboot droidboot.img
fastboot flash system system.img
Just remember, flashing these partitions can, potentially, brick your phone. You do this at your own risk...
Happy flashing....
Click to expand...
Click to collapse
Thanks for your help. I did that earlier with the latest pre-rooted OTA and now it gets stuck on the splashscreen. I tried going to recovery (stock now) and doing a factory reset after flashing system.img and it still the splashscreen after I reboot. I know the 1st boot after flahing a ROM can be long, but now it's been an hour and I'm still on the splash screen...
The only other thing I can recommend is to flash a RAW rom image. As I have never needed to do this I can't say how this works but if you do a search you should find out the procedure...
This may relock your bootloader so just be aware....
So I just switched to a Pixel 3 XL yesterday from an OG Pixel XL and I've having some issues with the kernel.
I build my own kernel with a couple of patches and I don't know how to flash it through fastboot on this device. On my OG XL I could just do "fastboot flash kernel" with the image I had built, but on my 3 XL that command returns "Not allowed to flash (kernel)" when I run it. Do I really have to make a flashable zip now?
Secondly, when I just try to boot the kernel, it takes quite a while to boot and then my touch screen doesn't work once it boots. The buttons all work so the device isn't frozen, but I can't unlock it or touch anything. I thought it might be one of my patches (even though they have nothing to do with the touchscreen) so I completely removed the kernel source from my PC, re-downloaded and rebuilt it (as per this page: https://source.android.com/setup/build/building-kernels) and even with the resulting bone stock kernel, my touch screen does not accept inputs when I boot the kernel through fastboot.
I suggest you use FK manager from Playstore to flash the kernel you made. It can flash any zip file. I would flash stock back and then try your kernel once you are in full stock. just to make sure it's not problem left over from your a possiblly corrupt installation of other thing.
Sent from my Pixel 3 XL
Eudeferrer said:
I suggest you use FK manager from Playstore to flash the kernel you made. It can flash any zip file. I would flash stock back and then try your kernel once you are in full stock. just to make sure it's not problem left over from your a possiblly corrupt installation of other thing.
Sent from my Pixel 3 XL
Click to expand...
Click to collapse
Not really an answer to my question. The OG Pixels can flash the way I want to do it and I want to know if this has changed for the Pixel 3 and whether or not I can make fastboot allow it. The whole point is to avoid the step of making a flashable zip, since I never had to before.
If you've unlocked the bootloader and used the correct command to flash the boot image to the active slot or both slots, then all should be well!
Good luck.
I think the command you're looking for is "fastboot flash boot boot.img" where boot.img will be the name of your kernel
JeromeLeung said:
I think the command you're looking for is "fastboot flash boot boot.img" where boot.img will be the name of your kernel
Click to expand...
Click to collapse
I think the command for flashing a kernel is fastboot flash kernel (name of kernel).img. fastboot flash boot boot.img flashes the boot.img to the active slot. fastboot flash boot boot.img --slot all flashes the boot.img to slots A and B.
Homeboy76 said:
I think the command for flashing a kernel is fastboot flash kernel (name of kernel).img. fastboot flash boot boot.img flashes the boot.img to the active slot. fastboot flash boot boot.img --slot all flashes the boot.img to slots A and B.
Click to expand...
Click to collapse
This is bad advice.
mitchdickson said:
This is bad advice.
Click to expand...
Click to collapse
Please explain.
I think since the Pixel 2 the kernel has been included in the boot.img. Correct me if I'm wrong though
homeboy76 said:
I think the command for flashing a kernel is fastboot flash kernel (name of kernel).img. fastboot flash boot boot.img flashes the boot.img to the active slot. fastboot flash boot boot.img --slot all flashes the boot.img to slots A and B.
Click to expand...
Click to collapse
JeromeLeung said:
I think since the Pixel 2 the kernel has been included in the boot.img. Correct me if I'm wrong though
Click to expand...
Click to collapse
You are correct to flash the stock kernel you flash the boot.img to both slots: fastboot flash boot boot img --slot all
Homeboy76 said:
You are correct to flash the stock kernel you flash the boot.img to both slots: fastboot flash boot boot img --slot all
Click to expand...
Click to collapse
Ok, but I'm not flashing a complete boot image. I want to just flash the kernel by itself, which you could do on the original Pixels by typing "fastboot flash kernel" and I'm pretty sure the kernel was part of the boot image on those phones too.
So my phone has been lagging a whole lot using the stock rom and I have decided that I'll try a custom rom to see if that changes anything. So I came here and saw this forum:
"https://forum.xda-developers.com/xa1/development/half-gsi-oreo-8-1-t3902259"
I thought I'll try and so I unlocked my bootloader, only to have my phone be reset (not a problem, everything was backed up). It also boots with a warning "Device unlocked and can't be trusted".
Then I went on to download TWRP using this link in that post: "https://mega.nz/#!FQFXCYSY!DgxQRkaY1Eqq3B0fZLEQBNzUs0Zj80L6IzSHxdorQ3A" which is the TWRP 3.3.0.0 V2 IS FOR ALL USERS.
I didn't want to flash in the event it was the wrong recovery so I tried booting into it, fastboot boot recovery.img
It flashed, everything was ok and now the phone doesn't boot. It stayed in a boot loop. I went ahead and flashed recovery this time, no luck. Downloaded a recovery.img from another website and it didn't allow me to boot to android or recovery.
Is there a way to save my phone, I can't get another phone until August due to contract. It can still boot to fastboot and gets stuck when trying to boot to android. It being able to boot to fastboot makes me think theres a chance to flash a stock rom or any custom recovery and rom to get the phone working again. Any help? Thanks!
Darth343 said:
So my phone has been lagging a whole lot using the stock rom and I have decided that I'll try a custom rom to see if that changes anything. So I came here and saw this forum:
"https://forum.xda-developers.com/xa1/development/half-gsi-oreo-8-1-t3902259"
I thought I'll try and so I unlocked my bootloader, only to have my phone be reset (not a problem, everything was backed up). It also boots with a warning "Device unlocked and can't be trusted".
Then I went on to download TWRP using this link in that post: "https://mega.nz/#!FQFXCYSY!DgxQRkaY1Eqq3B0fZLEQBNzUs0Zj80L6IzSHxdorQ3A" which is the TWRP 3.3.0.0 V2 IS FOR ALL USERS.
I didn't want to flash in the event it was the wrong recovery so I tried booting into it, fastboot boot recovery.img
It flashed, everything was ok and now the phone doesn't boot. It stayed in a boot loop. I went ahead and flashed recovery this time, no luck. Downloaded a recovery.img from another website and it didn't allow me to boot to android or recovery.
Is there a way to save my phone, I can't get another phone until August due to contract. It can still boot to fastboot and gets stuck when trying to boot to android. It being able to boot to fastboot makes me think theres a chance to flash a stock rom or any custom recovery and rom to get the phone working again. Any help? Thanks!
Click to expand...
Click to collapse
OK use the boot.img and recovery.img made by @janjan HERE. Under the heading ¨Downloads¨ see ¨Xperia XA1¨ and download the KERNEL + RECOVERY the boot.img and recovery.img are compatible with the G3121-G3112-G3125-G3116-G3123 devices on the applicable firmware.
Flash BOTH using fastboot. The boot.img is patched to allow TWRP to boot which it will never do using the stock boot.
If you wish to go back to stock then simply use FlashTool to flash the stock fotakernel.sin and boot.sin contained in the firmware for your device.
Does it works becouse I boot my g3116 from flashtool camand was
Fastboot boot boot.img and then also it's stuck into bootloader