[Q] cant open phone after burning kernal - Xperia Arc Q&A, Help & Troubleshooting

arc s
bootloader is unlocked
burnt a kernal
open the device, it showed the logo of the new kernal,
after a few seconds the logo was gone but the phone wasnt open, it stucked on a black screen.
this is the first time changing kernal (and rom aswell, I was doing that in order to change rom).
what happened?
how do I fix it?
thanks for reading! :laugh:
EDIT - So I changed the kernel to stock kernel and my phone is back to normal.
but that doesnt fix my problem because I want to change the rom..
my phone isnt rooted and this kernel was suppose to root it too, so I could go to recovery mode and change the rom, but I cant do nothing cause of this.
how do I fix it?

On the custom kernel, you're supposed to press vol down button when you see the kernel boot image. That will bring you into the recovery...
僕のLT18iから送られてきた

Related

rom flashing issues

my phone aborts when trying to flash some new roms...any idea y
Are you flashing through Amon RA or Clockwork? I would use RA and make sure you do a full wipe.
Is the ROM you are flashing signed? If not it will abort unless you turn off signature verification. Not sure if Clockwork lets you do this (I haven't used it in forever) but RA does. Of course, if a dev can't properly sign their ROM then you probably shouldn't use it anyway.
Sent from my HTC EVO 4G with Tapatalk
Pls i need help
Hi there, phone screen remains black and no visuals after flashing rom, so I canrt see anything on screen or know what to do about it, pls help?
Details -
After flashing ROM from SD card via which seem to go well... ONLY that the screen is blanked out, no lights except the key lights, phone comes on, responds to touch by giving normal sounds like when I use flick the scroll lock and touch the screen etc (just because I know how the phone works) but problem remains that I cant see anything, so I cant even boot into recovery or download mode to flash again since its all black and dimly lit.
I have a B63M running Gingerbread 2.3.5 so I am not sure what model of HTC it falls under in case this question or similar has been asked already.
I was able to initially get into flash recovery using the mobile uncle tool which allowed me get into recovery, something that has been impossible using the stock recovery in b63m.
I backed up the ROM , cleared cache and daikvil cache then went on to flash ROM using an update.zip and then the touble I explained above.
This is a current situation pls I need help getting back up and flashing the right lattest rom for my phone?
SORRY, i didnt realize at first that you dont have an evo, so i dont know if these instructions will help you
turn your phone off, remove and reinsert battery.
hold vol-down then power until HBOOT loads.
use vol keys to navigate and power to select the word "recovery" to boot into recovery.
I suggest you download roms over wifi if you havent as over 3g can cause roms to download wrong and cause issues

Defy stops @ "android" logo

Hello,
I have a great problem with my Motorola. I installed battery icon mod without reading for which phone it's made and used it. Now I can't use my phone, because it's stopping at this logo before system. I had Cyanogenmod 7 (last nightly before RC), but when I destroyed it by this application first thing I did was wipe. After it nothing has changed, so I tried again and I flashed it with normal 2.2 Nordic but - as I "predicted" - nothing has changed again, but this time system was stopping at Android logo, not Cyanogenmod logo. I tried to flash again - nothing. The device can be charged (there appears this battery).
What should I do?
zielonek430 said:
Hello,
I have a great problem with my Motorola. I installed battery icon mod without reading for which phone it's made and used it. Now I can't use my phone, because it's stopping at this logo before system. I had Cyanogenmod 7 (last nightly before RC), but when I destroyed it by this application first thing I did was wipe. After it nothing has changed, so I tried again and I flashed it with normal 2.2 Nordic but - as I "predicted" - nothing has changed again, but this time system was stopping at Android logo, not Cyanogenmod logo. I tried to flash again - nothing. The device can be charged (there appears this battery).
What should I do?
Click to expand...
Click to collapse
Go into the stock recovery and wipe data. Then re-flash the sbf.
I did it already, but I forgot, that I can do wipe after flashing the device I thought about it and did it - everything is working. Sorry for useless thread.
Regards.
I wanted to ask at the same time. What if i can't enter stock recovery. My phone's rooted , slightly overclocked , and i can't download any apps , i can't do factory reset , and even when i'm trying to enter it , the android pic would appear with that "danger - triangle". What should be done?
sLvW said:
I wanted to ask at the same time. What if i can't enter stock recovery. My phone's rooted , slightly overclocked , and i can't download any apps , i can't do factory reset , and even when i'm trying to enter it , the android pic would appear with that "danger - triangle". What should be done?
Click to expand...
Click to collapse
The triangle IS the stock recovery! when you see the triangle with the little android dude, hit both up and down volume at the same time. This will bring up a menu that will allow you to do a factory wipe.
And another question. I've installed custom recovery , and it said that install was succsesful , but when I apply recovery boot , it just reboots my phone , or lefts screen blacked out, at which case i have to turn on my phone by removing and applying battery.
sLvW said:
And another question. I've installed custom recovery , and it said that install was succsesful , but when I apply recovery boot , it just reboots my phone , or lefts screen blacked out, at which case i have to turn on my phone by removing and applying battery.
Click to expand...
Click to collapse
Not sure I understand the questions, but I'll take a stab at it anyway:
Since we have a locked bl, the custom recovery does not overwrite the stock recovery.
As far as I know, the only way to get in to custom recovery, is to push the vol down when the blue light goes on during the boot cycle.
sLvW said:
And another question. I've installed custom recovery , and it said that install was succsesful , but when I apply recovery boot , it just reboots my phone , or lefts screen blacked out, at which case i have to turn on my phone by removing and applying battery.
Click to expand...
Click to collapse
If it was a first reboot after installing Custom Recovery than USB Debbug should be off...

[Q] not booting any sbf ?? help

hi
i have defy , new from box , tried to install CM7.1 , (after root and cwm) on loading , phone froze on google logo.
i couldnt go into recovery for wipe , so i tried reflashing it
i tried some 2.2 nordic sbf phone froze on red moto
i d/l 2.3.3 85 and 112 with fix , same all freez on moto logo
1 time only i got the phone to boot with the 233 /85 version
but after reboot again freez.
any correct way to do it ? any way to fix it ?
thx
(how long should way till boot ?)
trabel said:
hi
i have defy , new from box , tried to install CM7.1 , (after root and cwm) on loading , phone froze on google logo.
i couldnt go into recovery for wipe , so i tried reflashing it
i tried some 2.2 nordic sbf phone froze on red moto
i d/l 2.3.3 85 and 112 with fix , same all freez on moto logo
1 time only i got the phone to boot with the 233 /85 version
but after reboot again freez.
any correct way to do it ? any way to fix it ?
thx
(how long should way till boot ?)
Click to expand...
Click to collapse
1. remove your battery
2. reinsert it
3. go in stock recovery by pressing power and volume down button at the same time.
4. when (!) this sign appears press volume down and up at the same time.
5.choose clear data
6.choose clear cache
7. flash any froyo rom
8. root it
9. install 2nd init (preferably 1.4)
10. reboot twice
11. install cm7.1 by choosing update (CM 7.1) from zip
12. install google apps
13. reboot
14. there you go
15. enjoy....
rishi2100 said:
1. remove your battery
2. reinsert it
3. go in stock recovery by pressing power and volume down button at the same time.
4. when (!) this sign appears press volume down and up at the same time.
5.choose clear data
6.choose clear cache
7. flash any froyo rom
8. root it
9. install 2nd init (preferably 1.4)
10. reboot twice
11. install cm7.1 by choosing update (CM 7.1) from zip
12. install google apps
13. reboot
14. there you go
15. enjoy....
Click to expand...
Click to collapse
o.k
from what i wrote ....
phone not going into stock recovery ...
and it keep freezing on motorola logo.
i reinstall battery , press vol down and power (for how long ?) usely anroid icon should be in 5 - 10 sec ...
anyhow , no metter what rom or fix i flash i cant get the phone back on , or i get logo freez or i get boot loops
cant enter recovery menu in any of the flashes.
i dont want to try 2.3.4 roms as there are no coming back from them
please some ideas
thx
Can you spot a blue led blink at boot?
Sent from Android 2.3.7
ryan8r said:
Can you spot a blue led blink at boot?
Sent from Android 2.3.7
Click to expand...
Click to collapse
I don't think the guy has 2nd-init installed properly. Or the rooting was not done correctly. He must go into the stock recovery to perform the wipe/clear before he can proceed on flashing another sbf. I would suggest the OP to flash any froyo 2.2.2 then.
Rooting and CWM could easily get ruin if one doesn't install it properly. Next time please confirmed root is working by installing apps that required root access before attempting installing CWM. Suggesting 2nd-init v1.9 is good to start with as it fairly stable which also come build-in custom recovery.
he posted that he can not enter stock recovery. This is caused (probably) by a bad sbf flash. I would try flashing the sbf you said that you actually got to boot. A properly flashed sbf will give you stock recovery. Pull battery for 30 seconds re insert it, then hold vol- and power the phone on. Continue to hold vol- for 5 seconds or so. If you insert your battery and the phone automatically starts to boot then it is too late and you should have already been holding down vol- in which case you would want to press and continue to hold vol- prior to inserting the battery.
zyxwvut said:
he posted that he can not enter stock recovery. This is caused (probably) by a bad sbf flash. I would try flashing the sbf you said that you actually got to boot. A properly flashed sbf will give you stock recovery. Pull battery for 30 seconds re insert it, then hold vol- and power the phone on. Continue to hold vol- for 5 seconds or so. If you insert your battery and the phone automatically starts to boot then it is too late and you should have already been holding down vol- in which case you would want to press and continue to hold vol- prior to inserting the battery.
Click to expand...
Click to collapse
o.k
thx for any answer
but
phone not going into stock recovery , maybe root done well or not , now it doesnt metter , as i tried many stock romes
non of them get me to boot , none of them get me to stock recovery.
i tried romes that works for sure , and none of them are working for me
i d/l many of the romes , none of them working
all give me freez boot logo of motorola.
i see many fixes , what the fixes for ?
is there any way to do it all ? as i cant go to recovery and wipe phone
trabel said:
o.k
thx for any answer
but
phone not going into stock recovery , maybe root done well or not , now it doesnt metter , as i tried many stock romes
non of them get me to boot , none of them get me to stock recovery.
i tried romes that works for sure , and none of them are working for me
i d/l many of the romes , none of them working
all give me freez boot logo of motorola.
i see many fixes , what the fixes for ?
is there any way to do it all ? as i cant go to recovery and wipe phone
Click to expand...
Click to collapse
any ideas ppl ??
I have seen in the past, people who report successful sbf flashing with rsd but still no boot or recovery. None that I tried or anyone else tried to help ever got their phones to boot. You are in a bootloop after flashing a sbf because you need to wipe in stock recovery, BUT you don't have stock recovery! There is only so much that you can do without having recovery when you are in bootloop. Not to rain on your parade but I honestly believe it is some sort of hardware issue. If RSD reports that all CG md5 checksum's match after it flashes then you should have stock recovery. But you don't????? I think it is hardware
I'm begining to start thinking your rsdlite might be the root cause here.
You might need to try another PC to flash or trying another rsdlite version.
Were you flashing this in sbf format??
i d/l 2.3.3 85 and 112 with fix , same all freez on moto logo
Click to expand...
Click to collapse
Isn't these Gingerbread files???
farsight73 said:
I'm begining to start thinking your rsdlite might be the root cause here.
You might need to try another PC to flash or trying another rsdlite version.
I thought of this too however his situation isn't the first of its kind and other people with the same problem tried multiple combo's of RSD ver #s and different pc's with no success. Plus I would think if it were RSD problem it wouldn't reports a successful flash and then verify the flashed CG md5's. But I say definitely give it a shot on multiple different computers with multiple OS's! When I was having problems with RSD I started using sbf_flash in linux with GREAT success. Unfortunately this never helped anyone else with this problem! But anything is worth a shot.
Click to expand...
Click to collapse
O.k
Its not seem to be h/w problem, as its a brand new phone from box....
But i took phone home, gonna install new rsd and will try on other pc.
I will post results.
As i read more ppl with same problem.
I will post later details of what i hD in the phone before, maybe someone can identify the original region and sfb phone came with
o.k
i got some progress...
i installed on a reformated laptop , new rsd 5.5
installed drivers , and tested flashing the orange 112 version.
phone is powered up after flash and goes to recovery .
i then wiped all and wait , phone is powered up.
but after about 10-20 secs it reboots.
i then wiped again , and flashed nordic 2.2.2 version.
phone is powered up , also recovery and wipe.
phone kkep rebooting after few secs from full turn on.
i can access menu .
i guess this is better then not booting and no recovery.
what should i try now to fix the reboots ?
o.k
last replay
fixed
flashed this sbf from this post
http://forum.xda-developers.com/showpost.php?p=14762402&postcount=143
thx for all help
hmm. just seems weird that RSD would flash successful, verify CG md5s as "match" after flashing and still be the cause of the problem. I guess stranger things have happened! CRAPPY MOTOROLA SOFTWARE
zyxwvut said:
hmm. just seems weird that RSD would flash successful, verify CG md5s as "match" after flashing and still be the cause of the problem. I guess stranger things have happened! CRAPPY MOTOROLA SOFTWARE
Click to expand...
Click to collapse
well , from old razar motor crapy phones , had weird flashing problems , try flashing newer/older or different from original soft phone will not boot , go back to original soft , all is o.k ...
only flashed 2-3 defy , so i cant say its a weird problem for me , thought rsd did flash the files , and only phone freez after reboot.
but funny is now , after phone is booted and rooted again , installed cm7 again , and lol phone froze on google again (dejavu)
btw ,on recovery (stock) i getting all the time
E:Can't open /cache/recovery/command
????
anyhow , i folowed the guide in first stickly, i'll finish it exactly
How to fix it:
Download this SBF and Flash it
Root your Phone
Download 2nd Init 1.4.2 and Install ClockworkMod Recovery
Download and install this Nandroid Backup
Enter Recovery, Wipe Data/Cache
After wiping, turn off your phone
Turn it on and get immediately into Bootloader mode
Flash this Fixed SBF
Delete Data/Cache again and reboot.
You WONT be able to install full SBFs of any Éclair or Froyo since these Androids have lower CG Versions.
**NOTE*: I just rephrased the original post since it can be a bit confusing, it is linked as source below.
**NOTE2**: If you are using a non-Chinese defy, DO NOT USE THE CAMERA FLASH while on the Chinese rom, it WILL kill your LED.
Source: ((Original post here))
How to Install CM7 after Installing a Full Gingerbread SBF: Ok, first of all do all the steps above on "Installed full Gingerbread SBF and can’t go back to another rom"
Root your Defy (Using SuperOneClick 1.7 and not 1.9).
Install SystemRecovery from GoAPK. If you install 2nd init, you'll just get into a boot loop and have to start over.
Reboot to recovery. Do a factory wipe, then do the cache wipe.
Install CM7 .Zip and then gapps zip file. DO NOT wipe again, you'll just go back to 2.2.2 CEE (if you accidentally do this, you can pick up again from step 3).
profit!
thx
Well, after long play with it.... Something is realy weird!
No metter what rom im trying to flash, orher then the jordan one that worked, both 2.3.3 i try before now give me black screen, the 2.3.4 give me phone restart every 10 secs. And i cant seem to install cwm without hqving boot loops . ...
Ideas?
Delete all drivers and redownload and install then uninstall RSD Lite and reinstall to 4.9 ( Google it) then reboot your pc.. dont connect your defy yet do it later as its says in my little guide
then open RSD Lite and boot your defy to bootloader (Power + vol up) dont Connect defy yet.
choose nordic 2.2.2 in to RSD Lite then connect your Defy and let it install drivers.. then Press Start...
that worked for me wen i got lost and no one told me what to do soo i indprovise

[Q] Always stuck on Splash Screen

I can't find anything about this on the Xperia Play forum so I have to ask now, I just unlocked my bootloader, SO glad I did, but it seems that after playing with some kernels, I can't even get past their splash screens! I've used LuPuS, FXP, and Mjolnir. It'll show the splash screen, vibrate and the led will light up. I've tried holding volume down and leaving it alone. Nothing happens, it just sits there. ADB says no device is plugged in as well so I can't try adb reboot recovery. I'm going to flash the R800X 2.3.3 FTF then reflash the Mjolnir Kernel, flash it's Wifi module, then install Glazed ICS. If anyone knows why it does this, I don't plan on turning my phone off UNTIL I know a solution to the stuck splash screens. Thank you!
EDIT: It starts doing that when I restart into recovery from the phone, I forgot to mention that, I haven't just rebooted the phone's system yet. I'll try that and get back to you once I install Glazed.
EDIT2: I powered off and booted for the second time and it didn't get stuck. I guess for the time being, I'll stay away from Reboot Into Recovery on the phone and just use the recovery-play.img.
Okay, now my phone needs to be reactivated... Can't see the number pad so I have no way of pressing One. Help please???
EDIT: I'm an idiot, I had to activate it while it was on stock gingerbread first.
Generally, after you flash a room, in that rom zip file the kernel is the boot.img, you need to extract and flash that boot.img so the rom would be able to boot.
First install FlashTool, in the flashtool folder there is a driver file to install the ADB drivers for Xperia devices, select all the drivers that apply to the Play to install.
Enter flash mode (hold Search button).
Flash the kernel: fastboot flash boot boot.img
If all fail, you can use Flashtool to flash the stock tft file to restore the phone to factory state.
Selim873 said:
Okay, now my phone needs to be reactivated... Can't see the number pad so I have no way of pressing One. Help please???
EDIT: I'm an idiot, I had to activate it while it was on stock gingerbread first.
Click to expand...
Click to collapse
Had the same problem, dial *228, instead of pressing one (since the dial pad is not yet visible) just stay on the line and they'll activate it. That's how I got mine activated.

Failed to Load! :(

I am currently running Domination CM10 build 6 and was previously using the kernel that came with the rom.
Just updated to latest bricked which first just wouldnt boot (flashed kernel via fastboot and zip via recovery as normal) either normally or load recovery so used viper flasher to do kernel and modules (replaced ones it came with to latest ones from the kernel zip)
Now phone boots fine but after a few seconds it comes up "Failed to Load! " in a box at bottom (similar to boxes when something is given root access, checked and phone still rooted and that side working fine) but the box never seems to fade away so stays stuck over top of everything.
I only have 2 widgets... clock & calendar both of which load up fine, boots into recovery now if I boot normal and then use rom "reboot into recovery" but whenever I try to use it the phone just reboots, if I hold volume down when powering on it just boots as normal and dont load hboot
Any ideas? Know its not major issues and can probably be fixed with a wipe but tbh was lazy and didnt backup before flashing kernel thinking I wouldnt need it so hoping someones had similar and knows a simpler fix which wont involve wiping
ViaraiX said:
I am currently running Domination CM10 build 6 and was previously using the kernel that came with the rom.
Just updated to latest bricked which first just wouldnt boot (flashed kernel via fastboot and zip via recovery as normal) either normally or load recovery so used viper flasher to do kernel and modules (replaced ones it came with to latest ones from the kernel zip)
Now phone boots fine but after a few seconds it comes up "Failed to Load! " in a box at bottom (similar to boxes when something is given root access, checked and phone still rooted and that side working fine) but the box never seems to fade away so stays stuck over top of everything.
I only have 2 widgets... clock & calendar both of which load up fine, boots into recovery now if I boot normal and then use rom "reboot into recovery" but whenever I try to use it the phone just reboots, if I hold volume down when powering on it just boots as normal and dont load hboot
Any ideas? Know its not major issues and can probably be fixed with a wipe but tbh was lazy and didnt backup before flashing kernel thinking I wouldnt need it so hoping someones had similar and knows a simpler fix which wont involve wiping
Click to expand...
Click to collapse
try to reflash stock kernel, maybe it will be ok again, in worst case you'll have to wipe

Categories

Resources