Problem: A few people wrote that they are having problems to boot up after flashing a new kernel/rom with fastboot. When the on key is pressed, the phone vibrates but the screen stays black - no boot up screen, nothing.
Solution: Instead of flashing the new kernel via fastboot (fastboot flash boot boot.img), try booting up directly via fastboot (fastboot boot boot.img), keep the phone pluged in, press the on key for 2 seconds, battery loading icon will appear, press again the on button for 2 seconds and the phone will finally boot up.
When battery power runs low making the phone switch off and you have no pc near to boot up via custom kernel, you can still boot up the original Kernel as long as you are on stock Rom (CM7 didn´t work for me, because the kernel is flashed over fastboot).
Worked for me, hope this helps you as well.
Okay that worked..buuuutt it could only be turned on with a computer =='
lofike said:
Okay that worked..buuuutt it could only be turned on with a computer =='
Click to expand...
Click to collapse
You´re right, but if on stock, you can still boot up with the original kernel, when no computer is near. So what i do is not flashing the custom kernel at all, but only booting up. So dont use the "fastboot flash boot boot.img" command, only use the "fastboot boot boot.img" command to boot um and leave the original kernel on the Phone...
1st Post was updated
arihellmichimich said:
You´re right, but if on stock, you can still boot up with the original kernel, when no computer is near. So what i do is not flashing the custom kernel at all, but only booting up. So dont use the "fastboot flash boot boot.img" command, only use the "fastboot boot boot.img" command to boot um and leave the original kernel on the Phone...
1st Post was updated
Click to expand...
Click to collapse
This thread is not a good idea. If you flash a rom and it does not boot up. Thats means something is wrong. Forcing it to boot will cause more problems down the road.
AndroHero said:
This thread is not a good idea. If you flash a rom and it does not boot up. Thats means something is wrong. Forcing it to boot will cause more problems down the road.
Click to expand...
Click to collapse
Okay you're scaring me lol...
I had the same problem as the OP, i thought it was bricked, so i got it replaced by verizon. Sadly i can't unlock my bootloader anymore, so i'm stuck on stock, but at least I'm rooted.
AndroHero said:
This thread is not a good idea. If you flash a rom and it does not boot up. Thats means something is wrong. Forcing it to boot will cause more problems down the road.
Click to expand...
Click to collapse
Its the only way i get my phone to boot a custom kernel and it runs great. No problems at all, overclocking works great, quadrant score of 2600. If battery runs off, Im still able to boot (without custom Kernel), so no need to bother.
Somehow flashing with fastboot doesnt work on my phone. So when I flash with fastboot, im not able to boot anymore until i flash a whole rom with flashtool. If someone knows how to flash only the custom kernel with flashtool id like to know...
Related
Hi
I really appreciate all the help, stuck and dont know whats next.
Shortly i connected xperia Active to X10FlashTool and pressed root and Optimize.
After that phone keeps restarting, only flashing the SE logo and then restart again. I put it to recovery - power, usb, volume +, and now its blank with only blue light burning. Connected via USB device manager showing - Android ADB intreface connected.
If i run fastboot i can see the device and if i type- Fastboot -i 0x0fce flash boot boot.img (http://forum.xda-developers.com/showthread.php?t=1345215) i get must be rooted first.
So basically my question is please explain to stupid noob how i can get my SE back to stock rom or even to boot it normally again!
Thanks!
Please ask if i forgot something!
You dont need to be rooted in order to flash a custom kernel. Basically flashing a custom kernel gives you the ability to root your phone. Try my Kernel that autoroots your phone.
http://forum.xda-developers.com/showthread.php?t=1345215
You can use that kernel with the stock rom. All it does is it gives you root privileges, busybox and CWM. You can boot into CWM by pressing the power button several times as the screen lights up brigter than normal on the Sony Ericsson logo.
dumraden said:
You dont need to be rooted in order to flash a custom kernel. Basically flashing a custom kernel gives you the ability to root your phone. Try my Kernel that autoroots your phone.
http://forum.xda-developers.com/showthread.php?t=1345215
Click to expand...
Click to collapse
How do i get this boot.img in to the phone?
dumraden said:
You can use that kernel with the stock rom. All it does is it gives you root privileges, busybox and CWM. You can boot into CWM by pressing the power button several times as the screen lights up brigter than normal on the Sony Ericsson logo.
Click to expand...
Click to collapse
pressing power button several times does not work, logo shows up as normal and then restart again.
means that the logo does not get brighter at all phone restarts againbefore that...
Lol? You have already posted it dude....
Fastboot -i 0x0fce flash boot boot.img
If that doesnt work, i think you have messed up something with the Flash Tool.
BTW... Have you unlocked the Bootloader?
dumraden said:
Lol? You have already posted it dude....
Fastboot -i 0x0fce flash boot boot.img
If that doesnt work, i think you have messed up something with the Flash Tool.
BTW... Have you unlocked the Bootloader?
Click to expand...
Click to collapse
Ok, yes, but this fastboot command gives me error: you must be rooted first...
What do you mean under unlock bootloader?
Thanks!
/facepalm
http://unlockbootloader.sonyericsson.com/
Hey,
I just unlocked the bootloader of a Xperia Neo MT15 (.69 firmware) using the testpoint method. Everything worked fine, the device identified as 'r...', I can get in fastboot and execute commands. Executing 'fastboot boot recoveryNeo.img' exits normally with download ... okay, booting..., but no new devices (like adb interface) appear, I tried several times.
But, what is worse, I can't boot the phone regularly, the screen is constantly black. After 'fastboot reboot' or removing battery and plugging in USB cable, the green LED goes on and a 'SEMC Flash Device' appears after a few seconds the LED goes off and the device vanishes. Pressing the power button causes the phone to vibrate shortly but nothing else happens.
Any idea how to get the phone working again. Thanks million times in advance for any help.
Regards!
buergi
Flash GB Kernel...such as Alliance kernel,Night-elf Kernel...
megatpanji said:
Flash GB Kernel...such as Alliance kernel,Night-elf Kernel...
Click to expand...
Click to collapse
Thanks megatpanji. Do I have to use a different Kernel? Isn't it possible to use the Stock kernel?
I followed the progress as for example described here for the Xperia Arc but I found similar descriptions for the Neo.
As I understood the progress after unlocking fastboot is open and I can hot-boot a recovery image. From where, in turn, I can push su using adb or install it from zip. Isn't that right? I'd like to understand what exactly went wrong or if I just misunderstood the progress.
why messing so much. use flashtool to flash any custom kernel. then boot into recovery (CWM), place your custom rom zip on sd card, and flash via recovery.
if wanting stock rom, then use flashtool to flash stock ftf file.
rajxelton said:
why messing so much
Click to expand...
Click to collapse
actually I tried messing up as little as possible As I said, at the moment, I'd just like to root the stock rom.
As the .69 firmware is unrootable and I did not mess up anything by downgrading I decided to use the method for unlocked bootloaders, which took me only a few minutes. Everything worked perfectly except the last step. The phone does neither boot normally nor in recovery.
Guess I'll have to begin searching a new kernel.
Nevertheless I would love to understand what went wrong so that I will not make the same error again in the future. Especially why the phone appears as "SEMC Flash Device" and shuts down shortly after it again.
i think, the kernel doesnt support the rom. you were on stock rom, so you must use stock based kernel.
rajxelton said:
i think, the kernel doesnt support the rom. you were on stock rom, so you must use stock based kernel.
Click to expand...
Click to collapse
well but I didn't flash any new kernel, did I? I only executed
Code:
fastboot boot recoveryNeo.img
As I understood this does not flash anything but does only hotboot into the recovery.
recoveryNeo.img is the kernel . this code is used to flash kernels
rajxelton said:
recoveryNeo.img is the kernel . this code is used to flash kernels
Click to expand...
Click to collapse
well and what is than the following for?
Code:
fastboot flash boot boot.img
I thought flashing writes the image to NAND while hot-booting boots from the image without changing the flash memory.
Isn't this the case?
uh :\ m mad ! maybe you are righht. i never used all this. but the boot loops you are getting is related to kernel only. maybe corrupted
So after all I tried flashing the kernel from the 4.0.2.A.0.62 ftf, which did not fix the problem. Then I relocked bootloader and flashed everything (except data wipe) and just as I thought it didn't work neither the phone booted and after some further 5 long minutes of trembling (while the phone refills the wiped cache) the phone turned on as always.
One possible reason for the trouble might be that the battery was almost fully discharged although as I started hacking it was at about 70%. Seems the phone discharged heavily over night. I guess I'll charge the phone now and will try again some other day.
*Fixed*
uppon2 said:
I just go the phone today and I have unlocked it and it all went well. I was looking at installing ViperDNA on to my phone. So I started to follow instructions in the Viper thread
1. I "tried" to install TWRP through the Goo method and after downloading the file it told me that recovery was no installed.
2. I rebooted in to bootloader and hit power button to enter fastboot then I scrolled down to where it says recovery and I hit power again. Phone displayed a message up the top that it was now entering recovery. The phone did not go to recovery it simply rebooted all the way back to my phones home screen.
I then though hmm well maybe I didn't install it properly so I follwed the instructions using Goo again but still nothing happened.
I noticed there was an alternative method to flash recovery by using ADB. I put the file in to the same directory as where my adb/fastbood reside and I booted in to fastboot again and in cmd prompt I entered "flash recovery openrecovery-twrp-2.4.0.0-dlx.img"
It seemed to flash and gave me a response which I can't remember now but it said OK!.
I then proceeded to try and enter recovery again but this time it has sent my phone in to a bootloop. It will not pass the Droid splashscreen. I can however still access bootloader mode.
I also noticed now in my Bootloader above where it says Unlocked it also says Tampered?
Phone doesn't seem to be recognised by ADB anymore neither. adb devices returns with a blank space
I'm a long time Samsung user so usually in this situation I would use Odin and flash a stock firmware but I don't know the process with HTC
I don't have a backup because I hadn't got to this stage yet!
Any advice as to what to do now
Click to expand...
Click to collapse
if you can still get the phone into fastboot mode then you should be fine.. when in fastboot mode the command "adb devices" will not return any entries.. when in fastboot you should use the command
fastboot devices
and see if your phone shows up there.. also the command for flashing a recovery in fastboot is:
fastboot flash recovery "your recovery filename.img" without the quotations though..
so the exact command would be the fastboot flash recovery openrecovery-twrp-2.4.0.0-dlx.img if that is what the recovery file on your computer is named.
then hit enter it should say sending etc...
I always then do the command
fastboot reboot-bootloader then the phone will reboot into the fastboot screen, then manually select recovery and see that it worked that time.
lazarus2297 said:
if you can still get the phone into fastboot mode then you should be fine.. when in fastboot mode the command "adb devices" will not return any entries.. when in fastboot you should use the command
fastboot devices
and see if your phone shows up there.. also the command for flashing a recovery in fastboot is:
fastboot flash recovery "your recovery filename.img" without the quotations though..
so the exact command would be the fastboot flash recovery openrecovery-twrp-2.4.0.0-dlx.img if that is what the recovery file on your computer is named.
then hit enter it should say sending etc...
I always then do the command
fastboot reboot-bootloader then the phone will reboot into the fastboot screen, then manually select recovery and see that it worked that time.
Click to expand...
Click to collapse
After attempting this it hangs here:
C:\Android-adb>fastboot flash recovery openrecovery-twrp-2.4.0.0-dlx.img
< waiting for device >
EDIT* Rookie mistake for it hanging. I was only in bootloader not Fastboot. However, this worked and I love you. I will now flash Viper. Do I still need to flash the Kernel Modules?
uppon2 said:
After attempting this it hangs here:
C:\Android-adb>fastboot flash recovery openrecovery-twrp-2.4.0.0-dlx.img
< waiting for device >
EDIT* Rookie mistake for it hanging. I was only in bootloader not Fastboot. However, this worked and I love you. I will now flash Viper. Do I still need to flash the Kernel Modules?
Click to expand...
Click to collapse
flashing the modules for the kernel is always a good idea just flash that after you flash your ROM..
and you are welcome just glad I could help!!
lazarus2297 said:
flashing the modules for the kernel is always a good idea just flash that after you flash your ROM..
and you are welcome just glad I could help!!
Click to expand...
Click to collapse
lol. Now Aroma is being a pain in the ass. It won't let me click Next to install. haha
EDIT* Maybe because of the smaller TWRP or maybe not but I had to try again and then click next but about 2" higher than where it says it :S
I am not a huge fan of aroma... i had issues when i tried to flash my DNA the first time.. that is something that you just have to keep trying unfortunately it seems... i have seen where people had to aroma freeze on them multiple times before finally completing the flash... some tips i have seen is keep the phone flat... also keep it plugged in.. I can't vouch for any of these being actual fixes but hey "it's only weird if it doesn't work"
Do you know the load time on a ROMs first boot after flash?
The ROM said it was installing and at about 8% the screen went all grey and then rebooted in to the HTC splash screen and hasn't changed for about 15 minutes. Tried it twice
EDIT* Would only flash using CWM
uppon2 said:
Do you know the load time on a ROMs first boot after flash?
The ROM said it was installing and at about 8% the screen went all grey and then rebooted in to the HTC splash screen and hasn't changed for about 15 minutes. Tried it twice
EDIT* Would only flash using CWM
Click to expand...
Click to collapse
glad to hear it sorry for the slow response.. i was away for a bit..
lazarus2297 said:
glad to hear it sorry for the slow response.. i was away for a bit..
Click to expand...
Click to collapse
All good. Thanks for your assistance
I am usually the guy helping other people. It's quite an unusual change going from Samsung to HTC!
Basically using any ROM to start my phone I have to use "fastboot boot boot.img" to start it. I do not want this as I recently did a job for a friend and he is not very good with technology, so this is not a good enough method for him to start his phone.
The guy who made the InsertCoin ROM told me that it seems the boot partition is corrupted, which is what I originally feared. Can I get any help please with this?
TheDreamLord said:
Basically using any ROM to start my phone I have to use "fastboot boot boot.img" to start it. I do not want this as I recently did a job for a friend and he is not very good with technology, so this is not a good enough method for him to start his phone.
The guy who made the InsertCoin ROM told me that it seems the boot partition is corrupted, which is what I originally feared. Can I get any help please with this?
Click to expand...
Click to collapse
So if you try to flash the very same boot.img you're using for starting your phone via above command with fastboot flash boot boot.img you can't start your phone afterwards? Also, have you tried to S-OFF your phone and flashing boot.img via recovery? Or reformatting boot after doing S-OFF?
what did you do get this error in the first place? i flashed kernels via "fastboot flash boot boot.img" a lot of times and never encountered any problems.
havent tested this, dont know if its possible to boot a jellybean-kernel via fastboot if you're still on ics-hboot, but maybe this is the problem?
afair if you're on ics-hboot, the jellybean kernel is too big in size to be flashed in the ics-boot partition, but maybe booting it is possible cause its just temporarily?
so whats your hboot-version and what kernel did you try to flash?
jellybean hboot is 1.25.002 btw, lower one is ics.
Another thing: Try to flash Infinity kernel from Original Development section. It is small enough to fit on ICS hboot boot partition, and you should be able to boot normally.
dansou901 said:
So if you try to flash the very same boot.img you're using for starting your phone via above command with fastboot flash boot boot.img you can't start your phone afterwards? Also, have you tried to S-OFF your phone and flashing boot.img via recovery? Or reformatting boot after doing S-OFF?
Click to expand...
Click to collapse
It just won't flash. It used to but doesn't now.
realCyphox said:
what did you do get this error in the first place? i flashed kernels via "fastboot flash boot boot.img" a lot of times and never encountered any problems.
havent tested this, dont know if its possible to boot a jellybean-kernel via fastboot if you're still on ics-hboot, but maybe this is the problem?
afair if you're on ics-hboot, the jellybean kernel is too big in size to be flashed in the ics-boot partition, but maybe booting it is possible cause its just temporarily?
so whats your hboot-version and what kernel did you try to flash?
jellybean hboot is 1.25.002 btw, lower one is ics.
Click to expand...
Click to collapse
Yeah my hboot is 1.2.4.
dansou901 said:
Another thing: Try to flash Infinity kernel from Original Development section. It is small enough to fit on ICS hboot boot partition, and you should be able to boot normally.
Click to expand...
Click to collapse
Will give i t a shot.
dansou901 said:
Another thing: Try to flash Infinity kernel from Original Development section. It is small enough to fit on ICS hboot boot partition, and you should be able to boot normally.
Click to expand...
Click to collapse
Thank you so much, it worked!
So I have been installing this rom http://forum.xda-developers.com/showthread.php?t=2188931 .
I installed just the rom and not the update and now my phone will not boot it turns onto the htc first screen and vibrates a few times.
I have tried going into recovery mode and starting again but recovery does not now boot the phone restarts and the above happens.
I have installed fast boot on my computer but when I run it, it flashes up for a second then closes.
Thanks in advance for your help.
sodamhall said:
So I have been installing this rom http://forum.xda-developers.com/showthread.php?t=2188931 .
I installed just the rom and not the update and now my phone will not boot it turns onto the htc first screen and vibrates a few times.
I have tried going into recovery mode and starting again but recovery does not now boot the phone restarts and the above happens.
I have installed fast boot on my computer but when I run it, it flashes up for a second then closes.
Thanks in advance for your help.
Click to expand...
Click to collapse
Well, without knowing any details about your phone and what update you were on, which recovery you used, whether or not you are S-On / S-Off, then we're just shooting in the dark trying to help.
If fastboot flashes for a sec and closes, then you are not using fastboot right. You have to run it from the Command Prompt. You don't double click on the fastboot.exe .
Can you still get to the bootloader mode?
And I have to ask, but you're sure you got the right rom from the right forum as there are quite a few different variants of the Desire...?
es0tericcha0s said:
Well, without knowing any details about your phone and what update you were on, which recovery you used, whether or not you are S-On / S-Off, then we're just shooting in the dark trying to help.
If fastboot flashes for a sec and closes, then you are not using fastboot right. You have to run it from the Command Prompt. You don't double click on the fastboot.exe .
Can you still get to the bootloader mode?
And I have to ask, but you're sure you got the right rom from the right forum as there are quite a few different variants of the Desire...?
Click to expand...
Click to collapse
How do I open fastboot from a command prompt I just need to know what to type.
I can still get into bootloader fine on the phone and my pc knows its contected via usb.
I know the phone was running a different recovery mode than standard but I don't know witch one. I think it may have been xloader or something with a x.
Its a standard desire. Regards Wayne
I have manged to load bootloader with command prompt and I want to remove the rom I have installed how do I go about this? Regards again, Wayne
O.K so I have loaded up bootloader and thought -w would be the command I am looking for, all I get from bootload on my computer is: waiting for device. I have attached a screen shot. Regards Wayne
You'll have to find an appropriate recovery.img and use fastboot to install. Make sure the img file is in the fastboot directory and while connected in bootloader/fastboot mode:
fastboot flash recovery recovery.img (where recovery.img is the name of your file - it can be whatever.img and you can rename it to whatever you want as long as you don't change the extension .img)
and see if you can boot to recovery at that point. If not, then you will probably have to use an RUU to return to stock and start over.
If you can get into the custom recovery, then you can reinstall another rom. Keep in mind, if S-On, then you will probably need to use fastboot to install the boot.img like so:
fastboot flash boot boot.img (here boot.img should remain named that)