Database Users

x8 e15i lights up and reboots no SE logo

Hi. I have e15i witch is dead its starts to the moment when screen lights up for 3s then lights go little lower for 4sec and reboots over and over again. when i start it in flash mode by plugging to the computer with "Back button" it is detected and i can flash it, witch i did to the newest available version but nothing changed still reboots. Is it possible that the bootloader is broken and cant load normal kernel and works properly in flash mode only ?, is there a possibility to reflash bootloader please help.
I'm suspecting that the screen is broken because there is no SE logo at any moment.
some questions that answering would help me very much:
is it possible to boot the phone without the screen? if not that would explain the problems
from where in process of booting the SE logo is generated
-semcboot?
-the loader.sin that loads kernel?
-kernel it self

doublegpl said:
from where in process of booting the SE logo is generated
-semcboot?
-the loader.sin that loads kernel?
-kernel it self
Click to expand...
Click to collapse
The semcboot is the very low-level initialization stuff; you actually shouldn't have access to the semcboot area - only the boot loader unlock tool is able to get in there.
The loader.sin is the boot loader (as in "the file that gets replaced upon unlocking the boot loader so you can load custom kernels) which then also kick-starts the kernel(.sin)
Once the kernel is fully loaded and initialized the framebuffer is being initialized along the way and the "boot splash" (the white Sony Ericsson logo) is being displayed while the kernel continues to boot-strap the ROM.
That's, in brief, what happens at power on.
doublegpl said:
is it possible to boot the phone without the screen? if not that would explain the problems
Click to expand...
Click to collapse
This is a untested scenario. I know of no one who took the phone apart to disconnect the Touchscreen in the attempt to see if the phone will boot (or fail boot due to the display being disconnected therefore unable to init the framebuffer).
doublegpl said:
Hi. I have e15i witch is dead its starts to the moment when screen lights up for 3s then lights go little lower for 4sec and reboots over and over again. when i start it in flash mode by plugging to the computer with "Back button" it is detected and i can flash it, witch i did to the newest available version but nothing changed still reboots. Is it possible that the bootloader is broken and cant load normal kernel and works properly in flash mode only ?, is there a possibility to reflash bootloader please help.
Click to expand...
Click to collapse
Well, this actually depends on what you did...
If you unlocked the boot loader to flash a custom kernel then all you need to do is to either grab the Stock Kernel FTF (loader and kernel) or the Stock baseband FTF (GSM/2G/3G Radio parts plus loader and kernel), connect it in Flash Mode and flash the Kernel or Baseband with Flashtool - and also restore to Stock ROM in case you have a custom ROM not compatible with Stock Kernel flashed.
If you never touched the boot loader it's still locked - in this case you can't flash the loader/kernel with Flashtool as you can't gain access due to the boot loader being locked. However, in this case it is also _very_ unlikely that the boot loader, or kernel, is "damaged".

thank you very much B.Jay for you reply
i don't know about the past of the phone a got it broken
but things i know is:
built date 11w01
dos not have sim lock
semcboot is not unlocked
loader R4A045
the things that you wrote about when the phone display SE logo
confirm my suspect that LCD is broken because its lights up when good working phone displays logo as i seen on some youtube video because i don't have another phone to check it out.
Il buy LCD and check it out fingers cross

You got it broken? Not good if you don't know what went wrong...
Anyway, by timing the boot process ... Once the backlight of the screen lights up the ~3s until the SONY ERICSSON logo is being displayed would be about right.
A reboot at this stage (while you actually see the logo on the screen) would mean that there was a severe problem boot-strapping the ROM (i.e. bad flash or messed up /system partition). A Flashtool restore to Stock would actually solve the problem.
As another test...
If you turn off the phone and connect it to the USB charger or a USB port of your computer ... do you actually see the short "Charging" animation?

Its charging battery but no information is displayed
when i push any button screen lights up.

doublegpl said:
Its charging battery but no information is displayed
when i push any button screen lights up.
Click to expand...
Click to collapse
If you don't see the short "Battery" animation then you can safely assume there's something wrong. The question just is ...
- Is the LCD controller dead?
- Is the Arduino GFX chip dead? (i.e. damage due to too hefty overclock)
- Is the display connection cable damaged or improperly inserted?
While you can buy the Touchscreen (LCD + Touchscreen + Frontpanel of the case as one part) it would be a somewhat costly adventure to find out that the chip is dead.
As the backlight works we can only be sure that it gets power.
Anyway, if you are adventurous - click the link in my Signature and hop into the "Service Manuals" folder. Grab the Service Manuals, have a look and maybe try to crack down on the root of the problem.

Hi.
I want to inform that my story has a happy ending
yes, only LCD screen whose broken the digitizer is good function
I've check all pins on broken screen and all whose fine no broken connection so it whose the LCD controller on glass,
and the glass it self did not look broken.
so the lesson from this is x8 will not start without LCD screen functioning properly
but I can say it will start without digitizer.
thanks for your help B.Jay.

No, thank you for working out that the X8 refuses to boot with a broken / defective LCD - that's a welcome and appreciated information.

Nexus 7 not working. Stuck on Google Screen, No recovery. Any Fix?

Just bought this thing, when i try to boot it up, it gets the google screen, then a black screen then a google screen again. It's been hours and it shows no sign of working.
I can't get into recovery or the OS or anything but the fastboot screen (which doesn't work when it's plugged into the computer, the buttons don't work)
When on the fastboot screen it says:
product name - grouper
Variant - not defined yet
hw version - er3
Bootloader Version - 3.34
baseband version - n/a
Serial Number- ( my serial number)
Signing - not defined yet
Lock State - LOCKED (in red)
I haven't done anything to it but charge it, its brand new too.
Any way to get this to work?

lienlion said:
Just bought this thing, when i try to boot it up, it gets the google screen, then a black screen then a google screen again. It's been hours and it shows no sign of working.
I can't get into recovery or the OS or anything but the fastboot screen (which doesn't work when it's plugged into the computer, the buttons don't work)
When on the fastboot screen it says:
product name - grouper
Variant - not defined yet
hw version - er3
Bootloader Version - 3.34
baseband version - n/a
Serial Number- ( my serial number)
Signing - not defined yet
Lock State - LOCKED (in red)
I haven't done anything to it but charge it, its brand new too.
Any way to get this to work?
Click to expand...
Click to collapse
long press the power button(10-15 seconds), force reboot it. see if itll boot. sometimes that helps. you might want to unlock it via fastboot, flash a custom recoveey, then flash a custom rom in recovery if nothing else will boot it. youll also want to update tbw bootloader, the bug where no buttons work in the bootloader has been fixed with the new bootloader.
,

Download the wugsfresh toolkit and go into bootloader it doesn't matter the buttons don't work and then click flash back to stock with the won't boot option checked yes

Thanks for offering help you guys, but i somehow got it working... i don't really know how but i did

i'm success with this trick..
from tablet off, plug your N7 to your computer with USB, then try to enter recovery as usual (push POWER BUTTON together with -VOL)

[Q] A500 Stuck At Silver Android Screen

I got in an A500 that had a weird yellow icon in the upper left. I wish I would have paid more attention to exactly what it said, but it was a small yellow icon, squareish and, to the best of my recollection, it said something like "NO FILE SYSTEM" or something like that.
Anyways, I followed a thread that I started where Moscow Desire helped me a LOT..
http://forum.xda-developers.com/showthread.php?t=2131327
And was able to obtain my UID and SBK (thanx MD!! ) and went about trying to resurrect this A500..
I was able to get a bootloader installed... A black screen pops up at boot with
SKRILAX_CZ's bootloader v8
Booting Primary kernel image
But then it just sits there at the silver ANDROID screen. The ANDROID will blink a couple times and it shimmers, meaning it is not frozen. But I have left it at that screen for 10-20 mins with no change..
I have tried putting on various update.zip files but it either immediately pukes with a dead ANDROID or it just boots to the same silver ANDROID and sits there..
I have been able to boot into recovery once, did a wipe and reset and then it just went back to the silver ANDROID screen...
Any suggestions for what I can try next??
Thanx

Update info on this...
I have a working A500 so I loaded up PUB RECOVERY and did a back up of that A500 onto an SD card thinking I can simply RESTORE it to this one that is puking at boot...
I got an error message saying it couldn't format or restore /data.. I did an ADVANCED RESTORE and did each section one by one, /flexrom etc etc.. Everything copied over except /data...
Does this mean the partitioning is frak'ed???

Success!!!
I guess I was doing the right thing, but just needed the right combination of tools..
I used Black Thund3rs' APX Flash Tool and downloaded Bundle #11 from his "Bundles" Library..
Everything installed and, upon rebooting, it booted up fine..
So, woot!! Good to go!
Michale

[Q] Flashed Radio and Stuck at Black and White Google Splash Page

Background:
Device: Tilapia
Came from 4.18 / 1205 and a 4.2 ROM (PA)
Flashed PA (latest)
--- No problems at this point ---
Flashed the files found at http://forum.xda-developers.com/showthread.php?t=2175086
Everything went fine until step 16. I was not able to reboot to recovery. What I had instead was this black and white Google splash page.
I did the usual button combinations, was able to get in and out of APX but I am always stopped at the splash page. The device boots but up until the Google splash page only. I need to get to recovery. How do I break from this loop? Thanks in advance.

Looking for solutions I've discovered that the instructions found at http://forum.xda-developers.com/showthread.php?t=2175086 killed a handful of devices following the same procedure.
On the one hand, it's my fault that I did not read through http://forum.xda-developers.com/showthread.php?t=2175086 to see that there was a very big risk of hardbricking your device but on the other hand, there should have been a warning on the first post saying that there have been numerous users who got their devices hardbricked as can be found in http://forum.xda-developers.com/showthread.php?t=2175086 and http://forum.xda-developers.com/showthread.php?t=2385695

Bumping.
Again:
Just APX
Boots up to Google b/w image only.

nexus 4 stuck at loading screen

Hey there,
I'm stuck with the nexus 4 at the "X" loading screen. I've been trying all things I can to fix it: flash an older OS (back to 4.2.2), and just now I did the guide described here to so call "unbrick" the phone.
During the last guide everything went succesfully - however I still am stuck at the "X". There are two remarkable things though:
-During the guide you flash a developer image (that you can't use as you don't have the password)
-Just when the batteries drop dead (and it shows "powering off") I actually see the correct screen (welcome, first time settings etc).
How can I fix it? LG doesn't want to do anything as it is now "rooted" apparently..