Database Info

Unable to Boot error, but device works!

Greetings people!
Yesterday I got this message while booting up my TP (latest official ROM):
"The device is unable to boot because either you have turned off the device incorrectly or tried to install an application from untrusted source. Press END to reset your device or press any other button to cancel. This operation will delete all your personal data and restore the device to its factory default settings"
However apart from that message, phone works flawlessly without any noticable change in speed or stability! The only apparent problem is that it takes a while longer (about 10 seconds) to boot up because of that message. I tried a couple of backups, problem was solved at first, but returned later...
I do take daily backups, but since I hardly monitor my phone when I reset it, this problem could have been caused by an app or reg entry a while ago... and searching for the appropriate backup will be a pain in the ass.
Since there's no change in speed or stability, do you think it would be wise to keep using the phone as is, or is it possible this would cause further problems down the road?
Any other way to troubleshoot it (at least to find the program that's causing this) other than a hard reset?
Edit: couldn't wait so I reverted to a week-old backup, installed back most of my applications, and it seems to be fixed (for now)

Update! I just tried a new SD to try XDAndroid, and guess what, the error disappeared!
So there must be a program I had installed in the storage card, possibly trying to start a service or something on every reset... and failing.
Is there a way to troubleshoot this? Maybe through SKTools or anything similar? I have a ton of apps installed into storage card and it will be a pain in the back cover to try by trial-and-error.
Thank you in advance
edit: inserted my old storage card again, error did not appear, problem solved! At least for now
Still if anyone knows how to troubleshoot this, please let me know

Update: Seems this error occurs every time I use SPB backup.
Yesterday, after a scheduled backup, the error came back. To troubleshoot this, I removed the SD card, did a soft reset, the error was gone! I took another manual backup, and again, the error came back.
So there must be something happening with SPB Backup and my SD card. Probably messing with files on the SD, or the driver or whatever (no idea there, I'm a total noob when it comes to software).
Moved the issue to the SPB forum

I have this message to, but I have never used SPB Backup

Well, in my case, it was obviously something tampering with the SD card (even if not SPB backup, something else)
Have you tried rebooting your phone with the SD card taken off? I just wait till it boots normally, and then insert it back. Works for me every time.
If that still happens, that probably means whatever is causing the problem is in your main memory.

akpidis said:
Well, in my case, it was obviously something tampering with the SD card (even if not SPB backup, something else)
Have you tried rebooting your phone with the SD card taken off? I just wait till it boots normally, and then insert it back. Works for me every time.
If that still happens, that probably means whatever is causing the problem is in your main memory.
Click to expand...
Click to collapse
Well I tried that just to see what would happen and I did not get the error message. So it is something on the SD card, but booting without it is not an option for me as I have several boot-start apps that are housed on it.

Perhaps one of those apps is broken?
As far as my case goes, I kept on using it for three months after the error appeared, without noticing any lag or issues at all. The only downside was that it took me three minutes to boot up, something I got used to.
If that's no big deal for you, I'd suggest you just leave it as it is for now, and check for lagging or specific applications failing (maybe one of them will be the app that's causing the problem?). If nothing happens down the road I think it could be safe to leave it as it is.
Now, if you can't stand this, I guess the only practical solution would be a hard reset. You can always play around with removing/reinstalling those apps you mention (or even better, installing them in the phone's memory) to check if and which one is broken, but I can understand that this not only will be a huge burden, but you may come to the conclusion that no specific app is causing this and something went south in the OS.
Personally the only apps which include a boot-up service I have installed into my SD are Football Monitor and PocketWeather. I tried removing both of them them back when I first had that issue, it didn't work...
Sorry I couldn't help more :/

Ahhhhndroid!

I've got a rooted (Super User) LG C800 that I was having problems with. To be specific, I installed some apps on to the system. Some of these apps would be Titanium Backup for root, Avast Mobile Security, ROM Tool Box, Super SU, and a couple others. From day one they seem to be kicked right back to my S.D. card, but not all at the same time, and some would stay on the system. I read where I should move the apps back to my S.D. card and try to re-install them on the system minus the data. When I did, the phone went nuts. Now it stays in a restart mode but never fully boots up. Can I salvage it, and if so, please tell me how?! I have tried the hard reset/recovery boot where you hold down the power button, volume, and a few other keys, but it did not work. I'm a broke college student and can't really afford to buy a new phone. I used this one for everything including tethering it to get my assignments done at home in on time. Please help! I'm open to suggestions.......

Did you do a Nandroid backup? If not, I would try reinstalling whatever ROM your running, see if that helps.
Why did you want to move the apps in the first place? Did they not install/run properly? I'm not certain but I believe that some apps prefer/require running from system, others from the SDcard. I don't think you can just assume that all apps should be moved to your card. Normally, wherever they install to, is where they are supposed to remain.

I can't even........
My phone will be completely off. When I plug it into my computer, via U.S.B., it automatically turns it on whether I want it to be on or not. Then it starts into that "boot loop" all over again but never fully boots up before going back to the beginning of that "boot loop" yet again. I can't even get it to register on my laptop as being plugged in. The reason I took the apps I placed on the system off was because sometimes when I'd re-boot the system the apps would be on the system and sometimes back on my S.D. card without my involvement of any kind other than rebooting my phone. Is completing a Nandroid recovery or re-installation of my ROM even possible with my computer no longer recognizing it as even being plugged in?
Rooted myTouch Q 4G, a.k.a. LG C800
I believe it had a what the exact numbers were but I want to say it was 2.3.4 GRJ22-perf, and then something like 2.6.35.7? I can't remember off the top of my head, and I can't pull it up on my phone anymore or else I'd double check.

[Q] Über-crash = reformat? What to do? thx

Hey gang -
Yesterday at home I pulled my phone out of my pocket and it was at the "touch the Android to begin" (!) screen. But it was still connected to my WiFi... And I was confused.
Rather than do that, I reset the phone, wiped Davlik cache and Fixed Permissions (took a long time!), then rebooted.
That sort of worked, but a LOT of my apps are crashing on start, and others are missing altogether. Even when I re-download them and re-install them, they don't work.
What's the way-ahead here? Am I stuck doing a factory reset? Or even formatting the SD card?
Thanks in advance.

When things get that fouled up, a clean install over a freshly formatted microSD is probably the best thing to do. You might be able to get away with restoring from a "nandroid" backup from before things started going bad, but "Your mileage may vary."

jeffsf said:
When things get that fouled up, a clean install over a freshly formatted microSD is probably the best thing to do. You might be able to get away with restoring from a "nandroid" backup from before things started going bad, but "Your mileage may vary."
Click to expand...
Click to collapse
Okay, thanks!
Anything else on the SD card I should back up besides DCIM / Media-> Ringtones/MP3s / "ui" / TitaniumBackup?
(Got about an hour while this stuff goes off to my HD...)

Hoo! Thought I effed myself for a sec - from CWM I was wiping all partitions... including /sdcard.
Then I realized... $#¡+... my ROM is on there!
Fortunately CWM has the "mount USB storage" option.
*whew!*

I was going to add format the sdcard from the phone. But you did that. Typically when what happened to you would happen to me it would be from some app updating and for whatever reason got corrupted during install and fouled the phone up. If you use TiB I highly suggest setting a automated task to back up your TiB backups to drop box, google drive or box.net. Then in these situations you have a recent TiB to fall back on.

JaimeZX said:
Hey gang -
Yesterday at home I pulled my phone out of my pocket and it was at the "touch the Android to begin" (!) screen. But it was still connected to my WiFi... And I was confused.[...]...a LOT of my apps are crashing on start, and others are missing altogether. Even when I re-download them and re-install them, they don't work.
Click to expand...
Click to collapse
Hi JaimeZX,
I am curious if you have recently rooted, flashed to stock, or installed the VB or Basic w/a twist kernel? I am running the exact same setup as you list (minus the modem) and this *exact* same scenario happened to me on the exact same day. March 12th, at about 10pm.
Detail as much information as you can, I've had many problems since flashing back to stock, formatting the SD, wiping everything multiple times, and re-installing Valhalla Black, Basic w/a Twist and all fresh apps d/l'd from the market. I'm on multiple attempts to stabilize the device and have questioned whether or not there is some issue with either the Rom or the Kernel. Perhaps there is an issue with the stock packages, or the USB driver ghosts (I've deleted all USB assigns at all ports and reinstalled for device detection in Heimdall). Hopefully we can get a good list of information to help us fix an issue that is apparently quite catastrophic (in that /data seems to corrupt) and save others from a future headache.
I have searched the dev threads to no avail, and as a general rule it seems that if problems are brought up they are usually met with "try flashing back to stock," "gremlins," "no one else is having problem 'X'," etc. even in cases of users with multiple complaints of the same issue. Both the DSP Sound force close upon EQ preset select and the issue that some had with the Messages, Phone Dialer, Search, Call Logs closing to homescreen are issues that I've seen this with. I believe this is a real issue, and I need to get it fixed without wasting time on messaging replies to anyone advising "try this," "Try that," etc.
My hope is that between the two of us we can address any of the common responses from developers before taking the issue to them and reporting it. I personally cannot today get my phone to boot without freezing (after boot cycle completes - not bootlooping or freezing during the bootleader seq) and am currently attempting to get into d'l mode without much luck.
When this happened to me on Tuesday night I was able to reboot to recovery, reflash the final-fixed.zip first without wiping data (which failed-/data is corrupted somehow here) and then *with* wipe/data and it booted, ran fine, so I then re-flashed BasicWithaTwist Kernel and was fine until late last night again.
I had been using the phone for some fairly constant web searching and the screen went black, appeared to soft reboot, and then froze. I pulled the battery, waited a few mins, reinstalled battery, once again, Freeze after boot.
No indication that an app crashes, phone just completely freezes, remains screen on, capkeys lit, power button does not respond, nor do softkeys or touchscreen. Makes it though the scan device and scan SD processes *sometimes* and other times freezes before it completes them.
I pulled the both the SD and the SIM and booted up, same issue, though it makes it through the scan device processes everytime since it's not scanning 18gb of data on an SD. This tells me it is not SD or SIM related, and is most likely software related, either ROM or Kernel. I've also ruled out the possibility of an old app/data package by reformatting the SD (long format - wipe all containers to "o,") let Android rebuild menu structure on SD, redownloaded a short list of commonly used apps and installed fresh - *NO* TiBackup apps were restored and the actual backup folder was not replaced to the SD after flashing.
I've tried both the Odin (Fb KJ6 back to stock) and the one click (lumin's tutorial) back to stock. Checked the download of Final-Fixed, MD5 checksum is correct. Cannot find MD5 on the sms-T959V-KJ6-antsvx.v1.1.3.zip file. Doesn't seem to be listed on Anton's github site, perhaps I don't know how to find it there. That is the only puzzle piece I haven't double checked.
All for now, looking forward to yours or anyone's replies or suggestions for anything I may be overlooking. Thanks.
0
---------- Post added at 11:19 AM ---------- Previous post was at 11:12 AM ----------
devlinandersen said:
Hi JaimeZX,
... I've had many problems since flashing back to stock, formatting the SD, wiping everything multiple times, and re-installing Valhalla Black, Basic w/a Twist and all fresh apps d/l'd from the market. I'm on multiple attempts to stabilize the device and have questioned whether or not there is some issue with either the Rom or the Kernel....
0
Click to expand...
Click to collapse
I should add that I have been on Valhalla Black Edition since it was in beta and have been quite happy with it. I only did a back to stock flash to try to (one more time) see if I could get a cooperative DSP sound manager. No such luck, and now a few headaches, and this issue on Tuesday coupled with yours in the exact same timeframe...I'm just thinking there is a problem somewhere in the chain of attack and hope to find it with the help of others.
Also, phone freezes after boot, needless to say, I'm not able to run a logcat.

devlinandersen said:
No indication that an app crashes
[...]
Also, phone freezes after boot, needless to say, I'm not able to run a logcat.
Click to expand...
Click to collapse
Try running logcat > /sdcard/some_file and cat /proc/kmsg > /sdcard/some_other_file so you have a capture of both the Android logs as well as the kernel logs. If you're not comfortable with command-line work, aLogrec should be able to at least help with the Android logs.
Given the number of people successfully running stock and custom ROMs on this device with stability, it either is going to be a hardware problem with your phone, corruption of a file system, or some app or combination of apps you are running, not a "dev" issue. Without logs, it is going to be nearly impossible to differentiate between the causes.

jeffsf said:
Try running logcat > /sdcard/some_file and cat /proc/kmsg > /sdcard/some_other_file so you have a capture of both the Android logs as well as the kernel logs. If you're not comfortable with command-line work, aLogrec should be able to at least help with the Android logs.
Click to expand...
Click to collapse
I will try in a bit, collecting files for another fresh install, different ROM.
jeffsf said:
Given the number of people successfully running stock and custom ROMs on this device with stability, it either is going to be a hardware problem with your phone, corruption of a file system, or some app or combination of apps you are running, not a "dev" issue. Without logs, it is going to be nearly impossible to differentiate between the causes.
Click to expand...
Click to collapse
This is false logic and is just what I was trying to avoid. I will attempt to explain to hopefully help build a stronger environment that is conducive to problem solving. It still very well could be a dev issue if say, a certain ROM or Kernel begins to wrestle with an app that has recently updated. Is it the apps or the rom's fault? Maybe it is a seldom used feature of an app that just missed all the users testing until now, it's well within the realm of possibilities and would just like to see helpful comments (such as the first portion directly above) to help solve issues. Truth is, I don't know *what* is wrong and neither do you, so a focus on constructive commentary would just help everyone out.

Logs or it didn't happen.

Update...
After a factory reset/data wipe, wipe cache, wipe dalvik cache I had to let the battery charge for a bit. Came back and decided to just try to boot phone, still freezes after boot sequence. I decide that I will flash a different kernel and a different ROM in order to see if I can make a difference. Before flashing Blastoff v2.5 Kernel I decided to factory wipe/data wipe, wipe cache and dalvik again...I am not sure if this is news, but when doing the Dalvik cache wipe in CWM it returned no result, perhaps because I had previously performed and is empty, but I thought it strange that there was *no* communication that it was already empty/wiped, etc.
Installed Blastoff v2.5 and was able to boot without freezing. Something else was damaged with the Rom as well, would not load home screen, only had pulldown menu. Rebooted to Recovery and flashed Unnamed RC-2.zip and have been charging the battery, talking on the phone and reinstalling apps from market.
Same error happened twice to me and once with Jaime. Both of us on VB and Basic+Twist. After installing new kernel i'd point towards kernel. Also uninstalled DSP and installed voodoo sound on VB, but had that on previous version as well. If I had to start somewhere, I'd start right around there.
Hope this helps, will provide logs from SD backup I made before reflash of new kernel/rom. Gotta run. Adios...
-devil.

I had to get my phone going today, it appears to be working without freezing, though on this new app the phone dialer/phone caller force closes on outgoing calls (I am only mentioning here, I will visit the Q&A for the ROM if I need assistance). Unfortunately I was unable to replicate the problem without flashing back to my previous nandroid. I have it saved and given some time I will do my due diligence and get a logcat **if** Jaime doesn't do it before me...because I kinda have a feeling that something was updated in the market on Tuesday evening that is now fighting with the kernel somehow. But again...I didn't run a logcat so it's not even happening...yet...
...to be continued...

Devlin - sorry for the delayed reply.
I did notice that I'd had more and more apps FCing on me in the week leading up to the Über-crash. Unfortunately I don't have any more "background" to add than that.
I backed up everything I wanted on the SD card and then formatted that, plus /data, /system /everythingelsethatwasanoptioninCWM. Then did my installs.
FORTUNATELY (knock on wood) I have not had any recurrence of the major issue.

Softbricked, basic usage no rooting.

Gday everyone.
I just got this phone and since it was first powered on I've had issues. I will likely be going back to the carrier tomorrow and asking for a replacement, but wanted to put my experience down here. Ive looked at a lot of other threads, but all of them involve unlocking of bootloader, flashing etc - I havent done ANY of this (yet). Its fresh out of the box.
Location: Australia
Carrier: Optus
Model: MHA-L09 (cant access extended model number)
So first up, had issues connecting to the carriers in-store wifi, which uses a captive portal.
When I finally got it going I was presented with a Chinese site - id accept this usually considering it is Huawei.
This phone is a replacement for my dead Note4 and as such I wanted to restore apps, as I had no internet, I skipped the process.
Got back to my office and connected to my wifi fine, so decided to factory reset to get a fresh start.
Noticed that after reset the initial process was in a different order. Restored from Google and all apps downloaded, happy days for a couple of hours, just waiting for my service to port over.
2 hours later, I decide to restart the phone, it gets hung up on the Optus logo which is displayed before the reboot starts.
Hard reboot.
System loads, I figure I may as well see about a firmware update. Get 'Package installer isn't responding' errors. Try again, works, no updates available.
Go to google photos, get 'Package installer isn't responding' error.
At this point I think, f**k - what is going on here.
So I reboot into recovery to wipe the cache. This processes fine, but then the option to reboot the phone doesn't work.
Hard reboot.
Boots into recovery without me touching it.
Hard reboot. - happens again.
So then I think, fine ok, I've upset the balance, lets do a factory reset.
Factory reset hangs on 99% for over 30 minutes.
Against better judgement - hard reboot.
Now I have the EMUI logo with a nice round 0% under it... and that's where its staying.
Thoughts?
I have to fly interstate on the weekend and cant really afford unreliable comms. Should I ditch the Huawei?
Thanks all.

So - it seems that nowhere did i find a mention of the fact that if i plug it into my PC and goto the recovery mode, it loads eRecovery. Whilst this didnt actually work (I believe it only works for CN firmware) It did give me a shutdown option. I shut it down and started it again and im back into a fresh install.
Lets see how I go now...

Never restore backups from other phone.

Wow, helpful.
I didn't restore the backup from another phone, just apps, ie google downloaded the apps I selected.
The device is still performing poorly, even a standard reboot does not succeed, instead it hangs on the carrier logo before actually rebooting.
Ill take it back to the store tomorrow and ask for another one, im hoping Ive just gotten a dud.

Any chances of data recovery? (Galaxy S7)

Hi guys, I'm new to the community here.
I've been using a Samsung Galaxy S7 (SM-G930W8) for the past four years that I bought second hand. It had this issue where it would get stuck and force reboot while playing videos. I tried looking up the issue, but there seemed to be no one else having this issue so in the moment I just kind of gave up and learned to live with it. However, for the past week or so, the problem got really bad. It had started freezing up while doing even regular stuff like browsing the settings app or tapping on a notification. If I left it, it would either force restart itself, or I'd do it myself by pressing Volume Down + Power Button.
I had planned on making a backup on Sunday Night, but just my luck, the phone just sorta gave up and died in the evening. It crashed during a video call, and it just kept rebooting, getting stuck on lock screen, and rebooting again. It did this a few times before going completely unresponsive. No power button, no Power + Volume up + Home, no Power + Volume Down, nothing would work. After a few hours, I tried connecting it to my Laptop, and at first it wouldn't even respond there, so I left it.
In the morning, I tried plugging it in to the laptop one last time and lo and behold, as soon as I connect, the Samsung Galaxy S7 logo shows up. However, the phone keeps going to "Installing System Update" Screen, end up at "No Command", and shutting down. The only thing I can do at this point is take it into download mode, and exit download mode. Nothing else seems to be working.
I got most of the data off of my SD Card, but when I took it to the local electronics store, they told me the only thing they could do was Flash the software and reset the whole thing, and even that was not a guarantee that it would turn back on, and that my data would be lost. They said if I wanted to access my data, I'd have to go to a professional data recovery service and pay several hundred euros.
I've been doing some research online and it seems that it is very much possible to flash new firmware onto the device without deleting all the data on it. I just need the phone to turn on once to the point where I can unlock the screen so I can copy the data off of it. Does anyone know if this would be possible, or if trying to flash it would work? I'd really appreciate any guidance and help. As a student, I cannot afford to drop 5-600 euros on data recovery on top of buying a new phone. If there's any way to access and copy the data into a PC without turning on the phone, that would work absolutely fine as well. Like I said, I do not need the phone anymore, but I would really really like to be able to get the data still on it.

I will ask my cousin he is an android pro engineer.

Huilopanich said:
I will ask my cousin he is an android pro engineer.
Click to expand...
Click to collapse
Thank you!

Hi booyakiller01, phone is recognized when connected to PC in Download mode ?

OP, sorry to hear that.
Data loss it something that happens to everyone, eventually.
Use the SD card as your data drive; put or backup all critical data here except for the Downloads folder (to create a security buffer).
Use ApkExport to backup up all your loaded apps and updates for a faster reload.
Backup any apps that allow it as well.

djibe89 said:
Hi booyakiller01, phone is recognized when connected to PC in Download mode ?
Click to expand...
Click to collapse
Hi @djibe89
The PC recognizes that there is a device connected but is unable to access the data or anything on the device. I tried flashing a new ROM, but I think I didn't have USB debugging enabled before it crashed, which is why that didn't work.
blackhawk said:
OP, sorry to hear that.
Data loss it something that happens to everyone, eventually.
Use the SD card as your data drive; put or backup all critical data here except for the Downloads folder (to create a security buffer).
Use ApkExport to backup up all your loaded apps and updates for a faster reload.
Backup any apps that allow it as well.
Click to expand...
Click to collapse
Hi @blackhawk
I'm a little confused, were you offering me advice for the future, or trying to suggest it as something I could try at the moment? In case I wasn't clear, the device is not able to boot into anything other than download mode, so I can't really do any of that. And my current replacement doesn't have an SD card slot so

The future. Now you know why I always have a SD card slot ie data drive.
Even adding a data drive to my Dell e6400.
They have saved me a lot of time and trouble more than once.
Hopefully someone here will figure out a way to help you recover your data

Hi @booyakiller01, by download mode I mean, what happens when you power on phone by holding Home + Power + Volume- and release buttons when screen is on ?

djibe89 said:
Hi @booyakiller01, by download mode I mean, what happens when you power on phone by holding Home + Power + Volume- and release buttons when screen is on ?
Click to expand...
Click to collapse
Yeah play with it.
My 10+ got into a boot loop twice by a badly coded launcher. When around in circle a couple times but finally got it to load in safe mode. Recovered some stuff and reloaded.
You may be able to get it to boot into safe mode...

booyakiller01 said:
Hi @djibe89
The PC recognizes that there is a device connected but is unable to access the data or anything on the device. I tried flashing a new ROM, but I think I didn't have USB debugging enabled before it crashed, which is why that didn't work.
Hi @blackhawk
I'm a little confused, were you offering me advice for the future, or trying to suggest it as something I could try at the moment? In case I wasn't clear, the device is not able to boot into anything other than download mode, so I can't really do any of that. And my current replacement doesn't have an SD card slot so
Click to expand...
Click to collapse
if its stuck on DL mode you can reflash the FW in Odin using the HOME_CSC which wont wipe your data. If it still refuses to boot and debugging isnt on, then its beyond my knowledge level of how to approach. also, sd to usb readers are stupid cheap

Youdoofus said:
if its stuck on DL mode you can reflash the FW in Odin using the HOME_CSC which wont wipe your data. If it still refuses to boot and debugging isnt on, then its beyond my knowledge level of how to approach. also, sd to usb readers are stupid cheap
Click to expand...
Click to collapse
thanks a lot! i was just silently reading and hoping @booyakiller01 would get a solution. had similar problem. i got lucky. i hope he could save his data too!