Database Users

Very Weird Startup Error - BLAC100 32M / SPL-1.14.0000 Serial

I've had this come up three days in a row now.
All the time it has happenned presumably overnight as when I attempt to wake the phone up from standby it shows me this.
I also suspect a battery problem as it was full overnight and I have been recharging it and it's only up to half-way. If the problem occurs again tomorrow morning, I'll check how much battery is left upon successful startup.
Any ideas?

This is bootloader mode!
SingaporeAirlines said:
I've had this come up three days in a row now.
All the time it has happenned presumably overnight as when I attempt to wake the phone up from standby it shows me this.
I also suspect a battery problem as it was full overnight and I have been recharging it and it's only up to half-way. If the problem occurs again tomorrow morning, I'll check how much battery is left upon successful startup.
Any ideas?
Click to expand...
Click to collapse
It looks like the phone is being rebooted at some point and going into bootloader mode. This can only be achieved by holding down the lower volume button while powering up.
Have you scheduled a nightly reboot and if so is it in a tight fitting case that might be inadvertently pressing the lower vol button?
G

SingaporeAirlines said:
I've had this come up three days in a row now.
All the time it has happenned presumably overnight as when I attempt to wake the phone up from standby it shows me this.
I also suspect a battery problem as it was full overnight and I have been recharging it and it's only up to half-way. If the problem occurs again tomorrow morning, I'll check how much battery is left upon successful startup.
Any ideas?
Click to expand...
Click to collapse
it may be a dirty or broken lower Volumekey that is hanging. Try to open your case and clean it

Gisbourne said:
is it in a tight fitting case that might be inadvertently pressing the lower vol button?
Click to expand...
Click to collapse
Matthes42 said:
it may be a dirty or broken lower Volumekey that is hanging. Try to open your case and clean it
Click to expand...
Click to collapse
My volume rocker has been causing problems for about two weeks now. It sometimes goes up but a lot of the times it tries to lower the volume. I have opened up the case but can't find anything that looks out of shape or out of the ordinary.
I'll have a look at it again tonight and see if anything else is jamming it.
Thanks guys.

Still strange though 'cos it would also need a reboot too for it to put you in bootloader

Maybe a night backup schedule or a rom with the reset manager active?

May be some app (set up deliberately to reset) or some other app unintentionally crashing can cause this in presnce of a stuck vol down button.
ROM with reset manager unlikely as his book loader shows factory SPL
sstolk said:
Maybe a night backup schedule or a rom with the reset manager active?
Click to expand...
Click to collapse

It didn't happen this morning or during the rest of today.
However, the volume button was stuck.
I also notice that the battery depleted substantially to the [ ]! mark.
I posit that the volume rocker is stuck at random times and when the screen is not switched off it obviously drains the battery leading to a reset.
Any tips on unblocking that volume rocker? I've tried to press out the button but it's not really working. There doesn't seem to be much I can do

I get the same error when i try to install an updated radio. Here's what i did:
- Used _HTC Touch HD_RUU_BlackStone_HTC_WWE-AFK_Radio_52.69.25.37_1.17.25.09_Only.exe
- versions: official dutch rom 1.56.404.1 (43972) NLD with radio 1.13.25.24, protocol 52.62.25.34W
- Put the NBH file on a formatted 6gb sdhc card
- Rebooted: long press power, short press power with volume_down pressed.
- I get the same screen with "Serial" on the bottom and no prompt.
I've read http://forum.xda-developers.com/showthread.php?t=508717 and http://forum.xda-developers.com/showthread.php?p=3438549&highlight=serial#post3438549. But, I haven't got any Xp machine (except virtual machines in Win7, which i don't trust for this matter), so using softspl is not an option either.
Can anyone help me? Should i buy a 2gb sd (non-hc) card perhaps?

Vega Won't turn on at all. Not even backlight

Just bought my Advent Vega today and was all running fine. Charged it too 100% then turned off and booted into the stock recovery. I then waited for it to show up on the computer as i have already got the drivers installed as i have jjust today flashed someone elses vega on the computer. mine didnt show up and then unplugged it and now it wont turn on at all. Tried charging it and then try booting. Unplug charger nothing. The thing is that the charging light still shows.
Any Help would be great. Dont want to have to send it back for repair. it may take weeks.
Thanks
Alex

Hmmm.... it could be a faulty unit, but my guess would be that you need to try at least 10x to try to turn it on.
I know some people complained that the buttons are very poorly designed and sometimes don't even work.
It's the same for my tablet, the "power/home" button doesn't always work like it should.
Once, I had to retry five times in order to power on the device.
If it's not that it could be some other minor issue, try holding the power button for a long time (8 sec), or try to go into recovery again, or something like that.

a sighn its trying to boot is the blue led under the camera tilt the vega away from you and look at the edge of the LCD it will glow when powering on

have you tried push back button, hold it, then press power button 2 second, the release the power button while still pressing the back button? it should be recognized and can be flashed

pramanta said:
have you tried push back button, hold it, then press power button 2 second, the release the power button while still pressing the back button? it should be recognized and can be flashed
Click to expand...
Click to collapse
Some times this can take several attempts.. and i mean several!
I actually had Audi running and had it connected to the pc so could tell if it had worked or not... not the correct way i know but it worked for me.

Interested to know if you ever got this sorted alcurtis93? I'm having the same issue with a vega where it won't even bring up the backlight. No life in it whatsoever.

A bit of a late reply, but try to wipe your device and maybe even flash a newer custom rom

Possibly Hard-bricked?

Got this phone from a friend. She already upgraded to iPhone so this is like a trash or free phone (I will take maximum risk to fix it). There was some moisture under the LCD glass. Put it in a bag of rice for 4 days while the new battery was on its way. That seemed to fix the moisture under the glass, so I'm assuming it fixed any other moisture.
I can get to bootloader (30.04) and the SBF using RSDLite (tried 5.3 and 5.5) appears to go through just fine. Have tried 602.sbf, VRZ_MB810_2.3.32_1FF_01.sbf, and VRZ_MB810_2.3.34_1FF_01.sbf.
Stuck on red M logo. Have tried different ways to get into recovery like holding down Home key or holding down camera key. Nothing I do can get it into recovery so I can wipe and get past this red M.
Should I try some other method I've heard of with Ubuntu and some SBF-flash application?

Hold power and home key until it goes to bootloader, do a wipe data/cache of factory restore.

FluffyMittens said:
Hold power and home key until it goes to bootloader, do a wipe data/cache of factory restore.
Click to expand...
Click to collapse
I think you've got your terminology mixed up. Bootloader is the mode that comes up by pressing both volume keys while powering on. This is where you flash stuff through RSDLite or use adb server to push and do hacker stuff.
Recovery is the phase where you can do factory wipes and data formatting. I can't get into recovery.
When you flash an SBF, it should be flashing a new recovery. I think the phone is hosed.

If wiping data doesn't help, do an SBF
Sent from my DROIDX using XDA App

infazzdar said:
If wiping data doesn't help, do an SBF
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
You've got to be ****ing kidding me.

Haha, I'm sorry, my kid was crawling all over me when I was writing that. What have you done so far?
Edit: Possibly try this, same thing just through ADB.
adb shell
su
format SYSTEM
format DATA
format CACHE
Click to expand...
Click to collapse

FluffyMittens said:
Haha, I'm sorry, my kid was crawling all over me when I was writing that. What have you done so far?
Edit: Possibly try this, same thing just through ADB.
adb shell
su
format SYSTEM
format DATA
format CACHE
Click to expand...
Click to collapse
ADB isn't working. I don't think ADB works in bootloader.
You ask me what I have done so far, but I already put all that information in the OP. That is why I was so frustrated with that second guy. If you guys would take time and not skim over my post that I actually thought out and typed ****, you wouldn't have to waste your time asking me what I have done.
I appreciate the ADB suggestion.

Just trying to collect some information. I'm someone that doesn't let a phone just be deemed as bricked. How charged is the battery?
-Edit: Just checked, ADB doesn't work in bootloader. Confirmed by having RSD open and making sure it sees it, and then tried adb devices. Also as a supporting confirmation for the fun of it, ran the one click root.
-Edit: Further thinking about it, was this phone submerged in water or just had moisture in there? There could just be some minerals formed up on the board that a toothbrush would get rid of. I've fixed phones a dozen times. Some phones will turn on and get stuck. Some wont turn on. Some the backlight comes on but no video signal.

Deoxit
My guess is that the buttons aren't working. There's no way to test that since you can only get to the bootloader, but if you can successfully SBF the phone the odds of any of the solid state gear being bad are pretty low. It does seem odd though that you can't make it to the boot animation and get stuck at the boot logo.
I would suggest getting some deoxit (tv tuner cleaner) and spraying it in around the hardkeys on the bottom of the phone. You don't need too much (especially since it might end up behind the screen). Spray that in there and then work the buttons a few dozen times. That should loosen up any corrosion on the switches and let them close the circuit again. If that doesn't do it, I'm out of ideas, but at least you'll have some deoxit lying around (stuff is great for static-y radio/stereo volume control knobs, etc).

The battery is pretty well charged. When I got it in the mail, there was no charge. I cut a USB cable and hooked it up to power. After about 2 minutes, I tried it. It got to bootloader but said battery was too low. I used the cut USB cable and hooked it around the battery pins in the phone and put the battery in, so it charged it at the same time it was tricking the phone into thinking the battery was full.
Also, if you go into Bootloader and then power off the phone, the green LED comes on. I'm assuming that means it's charging? I was skeptical since all we hear is that you're ****ed if your battery runs out at this stage of the game. It was off this morning and had been plugged in with the green LED all night (no USB cable hack).
As for trying adb while RSDLite is open, no go. adb devices shows blank. Motorola OneClick root didn't work either. It just sat there waiting for my phone. I didn't have the balls to plug in my Bionic to see if Motorola OneClick would work (and therefore the problem is with the Droid X).
As for the water damage, who knows. The lady I got it from was surprised when I told her there was moisture under the screen. I'm not her mommy so she didn't have any reason to withhold information from me. I just thought a bag of rice, a $12 battery off Newegg (free shipping, too), might just get me a sellable Droid X out of the deal.
As for the hardware buttons - they feel like they're clicking, but I know that obviously isn't the 100% test whether they're functioning properly or not. The volume buttons and power button obviously do function, since I can use those to get into BL.
Another brain jog idea: Is there an SBF out there that wipes the data and cache, along with all the other **** it puts on? This probably won't work because I still should be able to get into Recovery - something is FUBAR.
Please give up if you feel like giving up. Bricks exist. This may very well be one of them.
P.S. The girl that gave me this dropped her new iPhone 3 days into ownership. It only cracked the back glass, but the point still remains: she may not be the most graceful phone owner on the planet. Who knows what this DX has been through.
Thanks for all your help, guys.

I would try cracking that thing open and seeing if there are any mineral deposits and cleaning them. This means those weird clips and stuff too, just take a toothbrush to the whole thing and see where that gets you.
As with giving up, I'm a pretty bored guy and finding something to do is better then sitting around and watching Star Trek.
I haven't lost a phone once
Edit: Except for this [email protected]*% of an ACN voip phone that I buffer overflowed in attempt to gain root.. That ended badly.

Same problem
I had the same problem with my dx trying to sbf to .602 I ended up flashing the stock stock froyo sbf and upgrading to gingerbread by rooting and flashing CM7 or any other gingerbread rom. You didn't specify whether or not you tried froyo sbf. No idea if this will work for you but its worth a shot if you haven't already tried it. I also had to use RSD lite 4.9 or 4.8 to get the sbf file to work right.

I'd like to toss my problem into this thread if it's alright. The OP is the closest description to my situation I've read. A co-worker brought his phone to me and it would only get to the round red logo and stop there. No bootloop just a freeze at the red logo.
I tried different ways to get to recovery but was only able to get it to the white bootloader screen. (30.04) So I flashed .340 using RSD and it completes and tells me to manually start the phone. But the phone is already at a white logo (not a red one). I do a battery pull to restart the phone and I still can't get the phone to a recovery by holding down home or any other key while powering on. Battery charge is near full.
The owners explanation of how the phone got this way is that he woke up one morning and there was a 'protection mode' transparency on the screen so he rebooted and had the red logo from then on.
So, I can RSD flash just fine but the phone won't get past the black screen with the white and black M logo.
I would try flashing other files or even the Linux CD option but I can't find anything downloadable since mega got shut down.
Any advice would be appreciated.

Flash the latest rom (Gingerbread, .605) and the red logo will appear. Then, assuming it gets to the droid x loading eye, battery pull and enter recovery.
You can enter recovery by holding power and home, then, once the red/white M shows up, release the power button. Once the triangle appears, press the vol. up and down buttons simultaneously. If that doesn't work, press a bunch of random buttons until the recovery screen comes up. I'm not kidding, it works.
From this menu, scroll with the volume keys, and select with the power button. Wipe data/factory reset, then wipe cache partition. Reboot, and you should be good to go.

NType3 said:
Flash the latest rom (Gingerbread, .605) and the red logo will appear. Then, assuming it gets to the droid x loading eye, battery pull and enter recovery.
You can enter recovery by holding power and home, then, once the red/white M shows up, release the power button. Once the triangle appears, press the vol. up and down together gets buttons simultaneously. If that doesn't work, press a bunch of random buttons until the recovery screen comes up. I'm not kidding, it works.
From this menu, scroll with the volume keys, and select with the power button. Wipe data/factory reset, then wipe cache partition. Reboot, and you should be good to go.
Click to expand...
Click to collapse
1. Would be happy to try .602. Do you know of a working link?
2. It never gets to the eye.
Edit... I found a 602 iso to make a CD boot disk from and used that. The install went perfect but the phone still just boots to a red M logo and freezes there. It doesn't get to the red eye and no button press combo can get it to the recovery screen. I can only get it to the bootloader or let it go to the red logo. The buttons don't feel sticky or anything and the batt is fully charged.

The Fix
Skyroket said:
Got this phone from a friend. She already upgraded to iPhone so this is like a trash or free phone (I will take maximum risk to fix it). There was some moisture under the LCD glass. Put it in a bag of rice for 4 days while the new battery was on its way. That seemed to fix the moisture under the glass, so I'm assuming it fixed any other moisture.
I can get to bootloader (30.04) and the SBF using RSDLite (tried 5.3 and 5.5) appears to go through just fine. Have tried 602.sbf, VRZ_MB810_2.3.32_1FF_01.sbf, and VRZ_MB810_2.3.34_1FF_01.sbf.
Stuck on red M logo. Have tried different ways to get into recovery like holding down Home key or holding down camera key. Nothing I do can get it into recovery so I can wipe and get past this red M.
Should I try some other method I've heard of with Ubuntu and some SBF-flash application?
Click to expand...
Click to collapse
This will have all sbf working files and linux operating systems along with everything you will need try to sbf one of those preff linux. If this doesn't work and your still stuck! Go to this web page you will need.
Motorola Droid X Motherboard Flex Cable Replacement
Motorola Droid X Keypad Flex Cable Replacement
http://www.repairsuniverse.com/motorola-droid-x-replacement-screens-repair-parts.html
Finally here is how you take it apart with out damaging it.
http://www.youtube.com/watch?v=wo7dXyJhL1U
GL to you enjoy your droid x once ya get it working!

I always have to sbf my dx twice, I always boot loop the first time.

Just fyi, if you bootloop after an sbf, you can pull the battery, boot into stock recovery with the usual key combo format data and you'll be all set: no more bootlooping (or double sbfing!)

Press & Hold for 15 seconds to power up?

My wife's N7 sometimes starts normally, but very often you have to press and hold the power button for at least 15 seconds before you get the boot screen google logo.
I have searched but not found a thread dealing with this issue. I do not have the powering off/battery status issues, the tablet ALWAYS boots up, just that it seems very odd you have to press and hold the power button for so long sometimes. EDIT... HERE is a similar thread.
Any ideas if there is some fix for this?
The tablet is on Kitkat OTA update.
tx
Mark.

+1 having same issue and have been for some time ever since jelly bean 4.3 ? Nexus 7 2012 UK 16GB WiFi variant
Sent from my Nexus 7 using xda app-developers app

Your device is not shutting down properly. For me if i load a bad kernel or do some thing nasty in kernel settings then device some times goes into sleep of death. It is on but not responsive. You are just pressing power button for 15 sec to reboot it. Plz update your kernel if u have custom kernel or check settings if u have changed any. And if u haven't done any thing then start paying attention to apps after which these problems start to happen.
Factory reset would also fix the issue.
P.s: do not undervolt if you are and if custom kernel then try increasing lowest cpu state frequency to 200+. Just a thought. Not every device can handle all kernels.
Sent from my Nexus 7 using xda app-developers app

xateeq said:
Your device is not shutting down properly. For me if i load a bad kernel or do some thing nasty in kernel settings then device some times goes into sleep of death. It is on but not responsive. You are just pressing power button for 15 sec to reboot it. Plz update your kernel if u have custom kernel or check settings if u have changed any.
Click to expand...
Click to collapse
Hi
Thanks, I had thought that not shutting down properly is the cause, but now I have updated to stock kitkat, wouldnt that have come with stock kernel? Yet the issue persists...
Tx
Mark

Some app is causing sleep of death or ur tablet is faulty. Please do a through checkup and try to find out what situation is likely the be the reason to cause the problem.
Please ignore my spelling mistakes, English is not my native language and i hate on screen touch keyboards.

xateeq said:
Some app is causing sleep of death or ur tablet is faulty. Please do a through checkup and try to find out what situation is likely the be the reason to cause the problem.
Click to expand...
Click to collapse
I wonder if there is an app for tracking/logging that...
I am not going to uninstall every app just to find this out.
Perhaps someone else with the problem has already found out some apps that cause this, anyone?
tx
Mark.

well i have the same problem myself, even if i shutdown the device normal.
Sometimes i need to press the power button a few times for like a few seconds. Even after a factory reset.

BL4CK_92 said:
well i have the same problem myself, even if i shutdown the device normal.
Sometimes i need to press the power button a few times for like a few seconds. Even after a factory reset.
Click to expand...
Click to collapse
Ok, thanks BL4CK...
So that seems to point at HARDWARE being the problem... since after Factory Reset it cannot be software, and since I have STOCK kernel STOCK firmware, it cant be the ROM...
ah well... just have to live with it, it seems... though it does behave as though it is not shutting down properly.
cheers
Mark.

Same here...device is untouched, no root, no custom rom etc.
At first after unboxing i thought the nexus was doa, untill i realised that you have to keep pushing power button for 13 seconds!
What i hate even more: it's still on 4.3 because OTA updated doesn't work!
-update notification appears
-downloading update
-confirming "restart and install update"
-nexus turns off
I would really really appriciate some help!
PS: i do NOT want to update via usb to computer connection

Here is a thread with some good fixes for the hard start problem (hardware problem):
http://forum.xda-developers.com/showthread.php?t=2090826
If an app was causing SOD when shutting down, a factory reset would resolve it.
Should also check bootloader to be v4.23
Start the device by pressing n holding PWR + VOL DWN until you enter the bootloader.
The info should be somewhere along the left-bottom side of the screen.
Once u get the version number, use vol up/down buttons to navigate until u reach power off.
Press power button to confirm power off.
Start normally/whichever way currently works for u.
Used to have this hard start problem alongside touchscreen problems.
Under the nexus's back cover are actually some antenna pins along with some grounding pins.
Sometimes these pins corrode or have poor contact, then it causes some electrical abnormalities.
Try to clean these pins with an cotton earbud and some metal cleaning solution. Stuff like carb sprays for example. Nothing oil based. Wet the bud a little with your solution and clean gently. Then use a dry bud and gently wipe dry the pins and all residues. Repeat a few times if needed.
Also try to push the pins outward so it will have more contact with the back cover.
!!Be very gentle and use minimal pressure, these pins break easily and if they do you will need a new board.
Other than that, check the battery connector too. Unplug and replug. Or other suggestions/solution in the thread above.
Good luck!

Word of advice be extra careful when messing with bootloader. I have seen many loss their devices because of simple yet stupid mistake.
Please ignore my spelling mistakes, English is not my native language and i hate on screen touch keyboards.

Stock Mi A1 locked on Fastboot screen

Ok, here's as much info as I can give as my phone is locked up:
Stock Mi A1 with 1st Oreo update: December patch level
I have not tried to load anything custom on it, nor have I even loaded the apps to do so.
I took my phone out of my pocket and it is locked on on a screen that says Fastboot.
Power button does not work. Long press power button does not work. Power+UP volume button does not work. Power+UP+DOWN volume buttons do not work.
Plugging the phone into the computer via USB port does nothing.
The battery is non-removable, so I can't pull it to reset.
I am at a complete loss as to what happened, why it happened, and how to resolve it. The phone was working fine this morning. I took it out of my pocket to use it and then discovered the issue. I live in Thailand, and there are no local service centers for Xiaomi, so hopefully someone will have an idea of how to fix the issue.
Any help, ideas or suggestions would be MOST appreciated!
Regards,
KB
UPDATE: I tried to restart the phone via the power button while it was plugged into the computer via USB. Holding the power button down for 10 seconds (guesstimate) did force a restart. This was NOT the case when not plugged in. In any event, if anyone has an idea of what happened and why, I would really like to know! I am wondering if there was some sort of long press key combo or something that happened while it was in my pocket.

Sorry for replying to my own post, but I am totally confused by this issue. I did a lot of searching and reading on Fastboot, and they ALL said that to get there, you had to enable Developer Tools on your phone, download a program for your computer, and then connect the phone via USB.
Here's the thing: I have a photo of the screen, so this is not some hallucination!
1) I DID NOT have Developer Tools enabled on the device. (I do now as I enabled it to see if it was already enabled...it wasn't)
2) I DID NOT download and install an ADB program for the computer.
3) I DID NOT (before the issue) connect the phone to the computer via USB.
So my question is how the h*ll did I get into Fastboot?????
This is really concerning as maybe Xiaomi has an issue similar to the root issue One Plus had and I happened to pocket dial the right combo???? In any event, it does not give me a warm fuzzy about what is going on behind the scenes here!
Any thoughts or info appreciated.
--KB

To get phone into fastboot mode you have to hold power off + volume down button. Might have happened in tight pocket.

_mysiak_ said:
To get phone into fastboot mode you have to hold power off + volume down button. Might have happened in tight pocket.
Click to expand...
Click to collapse
Thanks mysiak...in all my reading, nowhere was that mentioned! And yeah, it was in a pocket pressed up against a seat, so could easily have pocket dialed that combo.
Also, it is not easy to find the solution when it is locked there. I THOUGHT I had held the power off button long enough when trying to get out of Fastboot, but maybe missed it by a second or two. My solution was just to hold down the power button until the phone turned off. Whether that is the correct solution, I don't know as I still have not found anything about getting into and out of Fastboot without a computer.
Regards,
--KB

KB_Thailand said:
Thanks mysiak...in all my reading, nowhere was that mentioned! And yeah, it was in a pocket pressed up against a seat, so could easily have pocket dialed that combo.
Also, it is not easy to find the solution when it is locked there. I THOUGHT I had held the power off button long enough when trying to get out of Fastboot, but maybe missed it by a second or two. My solution was just to hold down the power button until the phone turned off. Whether that is the correct solution, I don't know as I still have not found anything about getting into and out of Fastboot without a computer.
Regards,
--KB
Click to expand...
Click to collapse
Power+volume down button is the usual way how to get into fastboot mode. From a PC you can type "adb reboot bootloader", but many prefer just using phone buttons combo (myself including). If you want to get out of fastboot, you either hold power off button until phone vibrates shortly - this works in whatever mode, even if powered on, basically it's "emergency shutdown" as we don't have removable battery. Or if you are connected to a PC, type "fastboot reboot".
Long story short, you did it right
Btw. if you will hold power+volume up combo long enough, you'll end in stock recovery mode with "no command" on the screen. Don't panic, just hold power off button and then start phone normally

I had the same problem and plugged into the computer via USB and holding the power button down for 10 seconds did force a restart. and the phone is OK since then!!! Thank you you saved my time!!!

Thank you.
Picked up my Mi A1 this morning and it had the beautiful FASTBOOT icon on the screen. The phone has been lying on my desk for several weeks without a SIM. When I could not clear the FASTBOOT message I Googled for a solution and this thread was the result. I just wanted to record my grateful thanks. I plugged the phone into a computer USB socket and held the power button until the error message disappeared, as recommended by KB_Thailand..
XDA doing what it aims to do.:good:

It is always nice to find solutions instead of even more questions. Glad that it helped!
After the initial glitches, the A1 has been pretty dang dependable.
I still am using my A1. The A2 and A3 (someone needs to be fired over that monstrosity) left me flat. I am hoping against hope that the A4 will be 'the one', otherwise I am going to have to look for something other than Xiaomi.