Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,778,176 Members 51,724 Now Online
XDA Developers Android and Mobile Development Forum

[Q] Phone is stucked at Fastboot mode started, cannot do anything, please help!

Tip us?
 
kennytung
Old
#1  
Senior Member - OP
Thanks Meter 8
Posts: 236
Join Date: Jul 2010
Location: Ho Chi Minh City
Unhappy [Q] Phone is stucked at Fastboot mode started, cannot do anything, please help!

As said, after flashing AEONFLEX rom from PA KitKat, my phone is now stuck at the black screen with text: Fast boot mode started - udc_start(). I tried to hold the power button to turn off but it keep turning on with that same screen, cannot get into any other stage? Can anyone help me? I already searched through the web but no solution for my case.
 
darkobas
Old
#2  
darkobas's Avatar
Senior Member
Thanks Meter 583
Posts: 1,318
Join Date: Jan 2011
Quote:
Originally Posted by kennytung View Post
As said, after flashing AEONFLEX rom from PA KitKat, my phone is now stuck at the black screen with text: Fast boot mode started - udc_start(). I tried to hold the power button to turn off but it keep turning on with that same screen, cannot get into any other stage? Can anyone help me? I already searched through the web but no solution for my case.
go to recovery. try harder. there is lots of guides or videos how to go to recovery.
 
kennytung
Old
#3  
Senior Member - OP
Thanks Meter 8
Posts: 236
Join Date: Jul 2010
Location: Ho Chi Minh City
Quote:
Originally Posted by darkobas View Post
go to recovery. try harder. there is lots of guides or videos how to go to recovery.
Thanks, I can get into recovery and flash another rom, can boot up normally now. Any reason why a specific rom can cause this?

EDIT: turn out it was my fault to forgot flash the patch of the rom also.
 
darkobas
Old
#4  
darkobas's Avatar
Senior Member
Thanks Meter 583
Posts: 1,318
Join Date: Jan 2011
Quote:
Originally Posted by kennytung View Post
Thanks, I can get into recovery and flash another rom, can boot up normally now. Any reason why a specific rom can cause this?

EDIT: turn out it was my fault to forgot flash the patch of the rom also.
yes, probably wrong kernel
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes