Develop Bugs

Samsung Logo Keeps Flashing, wont boot HELP

Never thought I'd be the one to create a thread like this..
After I flashed the OKV4 ROM, strange things started to happen (this was after a full wipe). Apps kept force closing, etc. Later that day, when I picked up my phone, I saw the samsung logo flashing over and over. Making me unable to enter recovery.
Download mode still worked though and I proceeded to flash a stock firmware via ODIN. This did not help. Oh, and the Odin flash succeeded, without rebooting my phone though...
So, I'm still stuck with my phone which can't seem to get out of this strange loop.
HELP :C

I remember reading somewhere here that if you have flashed a diff FW now and then a possibility the last recent kernel is still in the system folder etc....this is maybe the cause of the bootloop.
Since you had confirmed going to download mode is possible..this may work logically... Why not do the following :
Get your phone rooted via Recovery (there is a thread here by The-E)..Once done flash arco68's CWM Recovery....Boot to recovery n do this :
Factory Format....Wipe n Clear including Delvik...Then go to Mount n Storage wipe every single folder...System...Data...Etc (this will wipe every single data left behind but I assure you the CWM will not be wiped) once done reboot n put the device into DL mode and use Odin to flash back to the stock FW.
From this moment the recovery will be replaced by stock version and the stock FW will be restored....once it boot up..Walla as I had done this over two times :
Best of Luck !!
Sent from my GT-I8150 using xda premium

I think you misunderstood me :/
This isn't the ordinary bootloop where the boot animation plays. It resets literally 2 seconds after starting. This makes me unable to enter the recovery at all. Thanks for the effort tho.
Tl;dr:I can not enter recovery mode.

treUse said:
I think you misunderstood me :/
This isn't the ordinary bootloop where the boot animation plays. It resets literally 2 seconds after starting. This makes me unable to enter the recovery at all. Thanks for the effort tho.
Tl;dr:I can not enter recovery mode.
Click to expand...
Click to collapse
Hi Bro...
I already discuss it in this Tread couple a days a go
You not alone bro
I ask The-E to mention all Wonder user to get safety flashing
Until this time we didn't get way to fix it yet

Please help. R800x boots into a weird screen?

(Just expaining how i got to the screen...in a lot of detail) Okay so yesterday i unlocked my bootloader through sonys website and everything was fine. Then i decided to try to put CM9 on it from a tutorial i found, didnt work. I then flashed back to verizons 2.3.3 through flashtool and everything was fine...but then i decided i wanted to go back to ZeuscNXTLite rom, i was lazy and used the recoveryPLAY.img to go to CWM. I forgot to clear the cache, data, etc. and i thought it was in a hard-brick because i could hold the power button all it would do is vibrate and i could still put it into flash boot(or whatever the green light means) but the screen always stayed black. I left it on my charger all night hoping it would magically come back i guess...today i got home to find the green light on it flashing faintly and quickly. I decided maybe its working now if i flash the .ftf so i did. Nothing happened so i thought maybe it was the bootloader so i tried using a bootloader relocker .ftf file but that just made my computer inable to recognize my phone. It would flash red a few times now when i plugged it into flashboot then go to flash mode and i could use flashtool. I tried adding the 2.3.3 .ftf back to my phone but it failed halfway through. So about 4 mins after doing this i look at my phone and see the Sony Ericsson screen but after that screen i see a triangle with an exclamation point inside of it and a phone under it. It keeps booting to this screen then shutting off over and over again. Now my question...does anyone know how to fix this? I dont really think its still in a brick since it goes to this weird screen.
Sorry for the extensive explanation. Also sorry if this was a repeat i tried searching but honestly have no clue what to search or even call this.

If you can still use flashtool follow this great guide http://forum.xda-developers.com/showthread.php?t=2054512 so you can fastboot a kernal and get into cwm then you can flash a new rom after wiping everything. :fingers-crossed:

The yellow triangle means you're in download mode, but I don't know what to do since I never had it on the Play.
Flashing the ftf will fail sometimes, you can keep re trying, its finicky so you have to make sure to use a good cable, preferably on a USB port that is not 3.0, and have few other USB devices connected at the sametime as possible.
The reason why CM9 didn't work because sometimes the kernel included does not boot. The boot.img from the FXP152's CM9 rom is one of the working one, you can separately flash it using fastboot.

I flashed a bootloader lock ftf file so wouldnt installing a kernel brick my phone again? Also could flashing the stock ftf file again while my phone is in download mode brick my phone? I'm just being extra careful now...dont want a hard bricked phone.

bandoncontortion said:
I flashed a bootloader lock ftf file so wouldnt installing a kernel brick my phone again? Also could flashing the stock ftf file again while my phone is in download mode brick my phone? I'm just being extra careful now...dont want a hard bricked phone.
Click to expand...
Click to collapse
Did flashing the bootloader lock ftf file work? you need to find out if your bootloader is locked or unlocked.If you have phone off, and hold on to search and you plug in USB to computer and get blue light your bootloader is unlocked (flashboot mode)If its unlocked just flash a kernel wipe and install a custom rom
If it is locked and you can use flashtool you can flash a stock ftf. Kernal is included in stock rom which you can find on forum

Ok i just put the stock ftf on it through flashtool. I tried to turn it on and it shows the Sony Ericsson screen and then the Android screen the turns off. Any help? It's at least showing the charging screen right now...
Also bootloader is locked. Just checked with the fastboot.exe

bandoncontortion said:
Ok i just put the stock ftf on it through flashtool. I tried to turn it on and it shows the Sony Ericsson screen and then the Android screen the turns off. Any help? It's at least showing the charging screen right now...
Also bootloader is locked. Just checked with the fastboot.exe
Click to expand...
Click to collapse
That good :good: Not bricked did you wipe data & cache in flashtool when you flashed ftf?

Yes i wiped cache, app log, and data. Im also using an older version of flashtool...maybe upgrading will help? Gonna check

HELP ME PLEASE ! Bricked but Fastboot mode and flash mode working.

Hello everyone here, im a noob around these parts but hope that this beautiful community might help me.
So heres the deal, my gf got an xperia m, that outta the blue started acting out, what i mean for this is, rebooting, outta nowhere and eventually a couple of days later it died.
Making my investigations to get to the problem and therefore the solution, she stated that putting it on the SUS or SONY Pc Companion didn't help at all, plus keep getting error 0x0000067 or 0x000007d5 on PC Companion.
After seeing this, she says tried to unlock the bootloader to install a CWM 6.0 for the 15.4.A.1.9 software, wich it had running, didnt got through since the moment she enter the command through fastboot to check the bootloader status throgh the command fastboot flashing get_unlock_ability but no response just stuck on three dots.
Also tried to flash through FLASHTOOL installing the drivers and everything as ive done with other decives checking everything is okay, which they are, since ive succefully recovered an brick C1904 using CWM with a previous Backup, but the tool gets stuck on flashing loader and wont give a percentage.
Tried Flashing remotely the CWM.img to the boot, but it wont flash, always failed, as for specifics about the code, If really needed ill post them on the next reply.
Hope Someone can Help me,
Regards Jmaquilon

Which error are you getting while flashing the recovery? is it something like remote command not allowed ? If it is then try to flash the recovery in the boot partition (I have done the same many time cuz there are some problem s with my current kernel)and what happens is instead of system the recovery boots up ..
If this doesnt works then try xperiafirm it may bring your phone back to life!
Hope it helps!

Just flash stock rom using flashtool software. Download the Stock Sony Xperia M Rom here http://forum.xda-developers.com/showthread.php?t=2699085 and flash it using flash mode in flashtool. Good Luck

xperia play bricked? pls help

hi all im hoping u can help me i have an xperia play which i tryed to root using cynogen mod 12 but it fails on install it will then reboot and show the blue cynogen logo but sit thier untill battery pull. i can access cyonogen recovery but thats all. ive tried installing other roms such as 9, 10 and 11 but all do the same thing (although 11 does seam to install/unpack).
i unlocked the bootloader and rooted the phone successfully. i also used flashtool to flash the boot.img.
i have heard i could fix the problem by sideloading another better recovery tool but i dont know how to do that. as off now im stuck in cynogen recovery.
any advice you could give would be greatfully appreciated, at this point im completely out of ideas and if you need anymore info i would be happy to provide it
thanks in advance

Hi,
It would be nice if you linked the exact ROM you tried to flash on you phone. It sounds like the boot.img is incorrect.
You can try flashing this kernel forum.xda-developers.com/showthread.php?t=1804003 . This one is for ICs roms(4.0.x).
Or this one - for Jelly Bean versions(4.1-4.2) - forum.xda-developers.com/showthread.php?t=1861970 .
All you have to do, is boot into fasboot mode and flash the given .img file as boot.img. (The difference between 480p and 720p kernels, are that 480 can't capture 720p videos, but sometimes 720p kernel doesn't work with all roms).

hi tnx for the help the rom i tried to install was cm-12-20150314-UNOFFICIAL-LegacyXperia-zeus
i think your idea would work but im unable to boot into fastboot mode as i used flashtool before and it doesnt recognise my phone anymore ( i dont know if i can use ADB as that option is available on my boot loader)
if you could provide me with a link to how to flash a new .img/rom using another way other than flash tools that would be really helpful. im sry to be such a noob, i have rooted every phone i had and never encountered this problem before and am completely stuck.
tnx again for your help

ok ignore my last msg i managed to flash the .img in fastboot no problem but now it wont let me into recovery mode so i think im stuck in some infinate boot loop no matter how many times i click volume down it just reboots after about 2 mins, anything i can do about that or am i now really bricked?
tnx again for your help

rob17zero1 said:
ok ignore my last msg i managed to flash the .img in fastboot no problem but now it wont let me into recovery mode so i think im stuck in some infinate boot loop no matter how many times i click volume down it just reboots after about 2 mins, anything i can do about that or am i now really bricked?
tnx again for your help
Click to expand...
Click to collapse
Well you could try to return to point zero by flashing your phone to stock rom and try to begin from there.
You can do that by using flashtool and downloading stock ROM from these forums.
BTW, you can enter flash mode by inserting usb cable and holding search button(i think, you can try other buttons). Your LED has to turn green, blue is fast boot.
Also if your flashtool give you errors, download earlier version (see some other threads about flashtool, there are links to older version). Maybe it doesn't recognize your phone, because of the new version, i've had problems with it too, but i had to download old version and everything started to work as expected.

Interrupted flashing during "VolumeUp + Power" mode

I have updated my Nexus 5x to 7.1.1 beta and after a day it powered off and I got the infamous red led during charging. I was not able to turn the phone on even after leaving the charger on for some days. I thought it is bricked and left it alone connected to my computer.
However today, out of nowhere Google logo popped up. It was bootlooping, but I was able to enter bootloader and original recovery. I wanted to flash it from bootloader, but was unable, because it was still oem locked. And I was not able to oem unlock, because I did not do the required part in the Developer Tools menu. I tried to adb sideload OTA in the original recovery, but sideloading stopped after uploading ~48% every time.
So I opted for the "VolumeUp + Power" mode flashing. Phone was recognized and I started flashing the appropriate TOT file. However at 33% on phone and 28% on the PC, progress stopped. And after a minute or so phone turned off. Currently it has no signs of life at all. Have I completely bricked it now? Is there a way to recover from interrupted "VolumeUp + Power" flashing mode?
EDIT: at first I though maybe the battery died during flashing. But interruption was not abrupt. First the progress slowed down to halt. And then after some time phone turned off.

It seems not all is lost. Have a blinking red light again after leaving it connected to computer for a day. Back to square one, but at least it is alive.

Your motherboard is dead.
And it is not your fault, mine also died while using beta 7.1 and I sent it RMA. They replaced for a new one.
But in my case i had unlocked bootloader, I flashed back 7.0 and it gave no results, still bootloop that's why I sent

Thanks for the info.
After leaving my phone with a clamp on a power button throughout the night (so the red light would flash continuously), I got it booting into "VolumeUp + Power" mode and this time I have successfully flashed the same TOT file via LGUp software. It was still bootlooping after flashing. Now I was able to enter into bootloader and recovery and this time sideloading the same previous file actually works. However it still bootloops.
Anyway, I tried to RMA it and after giving my IMEI to the Google rep, they said that they could not find it in their system after checking US and UK store records. Also tried calling LG warranty, but they do not know of my IMEI either. I got this phone from Swappa, so I left wondering where did the original owner of this phone got it from. He claimed that he got it as a present...

BlinK_ said:
Thanks for the info.
After leaving my phone with a clamp on a power button throughout the night (so the red light would flash continuously), I got it booting into "VolumeUp + Power" mode and this time I have successfully flashed the same TOT file via LGUp software. It was still bootlooping after flashing. Now I was able to enter into bootloader and recovery and this time sideloading the same previous file actually works. However it still bootloops.
Click to expand...
Click to collapse
out of curiosity, have you ever tried to flash custom recovery through the bootloader ? If you can, you might also wanna try to make a EFS backup, wipe all partition, then flash custom rom or near-stock rom like this one, just for the sake of testing.

anazhd said:
out of curiosity, have you ever tried to flash custom recovery through the bootloader ? If you can, you might also wanna try to make a EFS backup, wipe all partition, then flash custom rom or near-stock rom like this one, just for the sake of testing.
Click to expand...
Click to collapse
I wanted to flash custom recovery but was unable to do so, because device is still OEM locked. And I am unable to unlock it, because I did not do the confirmation in the Developer Options before device started to bootloop. Is there a way to flash custom recovery without this step in Developer Options?

BlinK_ said:
I wanted to flash custom recovery but was unable to do so, because device is still OEM locked. And I am unable to unlock it, because I did not do the confirmation in the Developer Options before device started to bootloop. Is there a way to flash custom recovery without this step in Developer Options?
Click to expand...
Click to collapse
For now, no way that I can think of. You could try to oem unlock it until it work, just cross your finger I guess?

I have some progress here. Since I was able to sideload various OTA images, I started doing that one by one and seeing if some of them would not bootloop. And after flashing 7.0.0 (NRD91N) from here (https://developers.google.com/android/ota) phone booted successfully and now is working. Will report if I get any problems.