Database Info

[Q] Samsung Fascinate - BRICKED... HELP!!!

okay, so i'm very new to this rooting concept.
i rooted 2 days ago using Z4Root. It seems to have worked, installing SuperUser.
A friend directed me to BlackDroid.net, supposedly to get free apps. I went from my default browser on my Samsung Fascinate and installed a few apps.
One app i installed was Type Fresh. I was messing around with the fonts within the app, trying to understand what was actually changing on the phone. I had rebooted the device around 5 times within an hour after making (what I thought were) font changes.
After changing some fonts, the device began to malfunction:
- Upon reboot, the device will show the Samsung logo while playing the intro music for Galaxy S & Verizon Wireless.
- The device never gets passed this screen.
- After a battery pull, the device showed "downloading - do not turn off target!!!"
- I read in these forums that a battery pull should help. No luck. It still boots up the Samsung logo screen only.
- I've tried a factory reset by holding the volume keys and power button, but the device ONLY boots up into the samsung logo screen.
ANY HELP WOULD BE GREATLY APPRECIATED.

Wish I could help. Do you have a custom recovery??
Sent from my Nexus One using XDA App

i have nothing. i don't even fully understand your question, unfortunately.
(dunno if this is related or not...)
i have a macbook and considering installing a 30-day free trial of vmware to restore the phone. i didnt, but even if i did, i would have no clue what i was doing. im a quick learner with good directions, but some of the verbiage is not familiar to me.

to stop Verizon from forcing update

to stop Verizon from forcing update
Use Titanium to freeze com.smithmico
i lost root because vz forced the update so i reinstalled .5 oem then used revoluton to unlock boot in stall SU installed .9 radio seems to work well rebboted it pop saying .9 would start download in 26 secs i stoped it from installing
i remembered reading about smithmicro and OTA so i froze it so far n more pushed OTA ...
your mielage may vary

Or just delete it completely. Not needed and is in my top 10 list of things to remove via tb.

Could you tell me exactly how you reinstalled .5 after having .9 already on the phone?

http://www.multiupload.com/WES9PABEQF
rename it PG05IMG.zip copy to sd card reboot do power volume restart it should do it itself don't shutdown until it is completley finished.

I did that but it won't downgrade. It says I have the newest version installed so it won't flash the "older .5" version. Any suggestions?

Make you rename it pull battery two button restart and it will load .5 I had no issues
Sent from my ADR6400L using Tapatalk

davwman said:
Or just delete it completely. Not needed and is in my top 10 list of things to remove via tb.
Click to expand...
Click to collapse
Is that uninstall com.smithmicro.DM 1.0.0 ? Is this the right thing to uninstall for no OTA? Thanks
If so, I think I will uninstall this before I flash the new radio. What do ya think?

i don't see that file... on a side note, i updated the radio this morning and still no message to update so not sure if i'm in the clear or not

so what does com.smithmirco actually do? is it just an updater?

My phone seems to be stuck in the process. I can't locate a p50IMG on the SD card and before I can even open Titanium my phone starts to power down and tries to install the update, but fails. Any ideas?
---------- Post added at 01:51 AM ---------- Previous post was at 12:57 AM ----------
Finally think I figured it out for my situation. As soon as home screen loaded I opened up TasKiller, killed everything. Repeated that 4 times so that everything loading up with the phone was killed before it would reboot the phone. Went to app drawer and made a shortcut for Titanium right next to TasKiller. After this I went in and killed all apps again.
Now let's freeze some things via Titanium so it doesn't try to reboot to install an OTA. First I froze com.smithmicro, next I froze HTC DM. After these two I let the phone go while I messed around for a few minutes, after this I turned airplane back off. I checked TasKiller and noticed that an app MCC_OTA had opened, fearing this may be the cause I killed all apps again and went in to Titanium and froze this.
15 minutes later and I've had no issues with cell/data service. I can get into the market, update apps, receiving gmail/email, and Facebook working fine.

Pender1 said:
so what does com.smithmirco actually do? is it just an updater?
Click to expand...
Click to collapse
I am not trying to be an alarmist, but a description from Smithmicro's site sounds strangely similar to the description on the Carrier IQ site. I will let you be the judge.
"Device Management Suite™ (DM Suite) is a standards-based server solution for mobile device management, enabling mobile operators to remotely customize, provision, configure, and diagnose mobile device settings."
http://www.smithmicro.com/products/device-management-suite.aspx

Still running strong, no problems and no force OTA attempts.

Woke up at about 4:00 AM this morning and my phone was sitting at HTC screen. Pulled battery and phone rebooted, quickly showed OTA icon and rebooted.
It got to the android man screen and got stuck there. Again pulled the battery and rebooted in to recover. Wipe Davlik cache and regular cache, rebooted and phone appears to be back to normal.
Rooted running Team Gingerbreaton ROM. This is the second time in the last few months that the forced OTA has tried to run itself.

CenFlo said:
Woke up at about 4:00 AM this morning and my phone was sitting at HTC screen. Pulled battery and phone rebooted, quickly showed OTA icon and rebooted.
Click to expand...
Click to collapse
Happened to me this morning too. Good thing the phone sits next to my bed (use it as an alarm) and woke me up since I would have oversleep without it. Of course, I lost two hours of sleep because of it since I couldn't get it working in my half-sleep state and just stayed up because I didn't want to be late to work.
I need a real alarm clock.

CenFlo said:
Woke up at about 4:00 AM this morning and my phone was sitting at HTC screen. Pulled battery and phone rebooted, quickly showed OTA icon and rebooted.
.
Click to expand...
Click to collapse
Happened to me as well. Up at 4:30 roughly with nothing working. Cleared cache as suggested and phone is now powered up but no longer showing 3g or 4g, simply 1x so something is still wrong. Have to get ready for work at this point and will have to do some more digging.

CenFlo said:
Woke up at about 4:00 AM this morning and my phone was sitting at HTC screen. Pulled battery ... Wipe Davlik cache and regular cache, rebooted and phone appears to be back to normal.
Click to expand...
Click to collapse
Thanks for that. I was losing my mind this morning. Woke up, grabbed phone, and it had the sad Android screen with the Exclamation triangle. Felt like Anakin at the end of Ep. III for a bit. Did a search for "Block update" and came to this thread. Now to flash a non-Verizon ROM so I don't have to go through that again.

Just got another OTA notification this morning, was able to delay it... WTF? I'm rooted running a custom ROM and it's still trying to push this updated.

Just an FYI, if you get the update. Revolutionary root no longer works.

I woke up to my phone stuck on the black screen with the little Android man also. I pulled the battery, powered up and quickly restarted into recovery. Then I factory reset from recovery and after that I re-flashed my shift ROM and all is good so far. *knocks on wood* Anyone think its the new radio I flashed that prompted this or did they push everyone??

zx12dak said:
I woke up to my phone stuck on the black screen with the little Android man also. I pulled the battery, powered up and quickly restarted into recovery. Then I factory reset from recovery and after that I re-flashed my shift ROM and all is good so far. *knocks on wood* Anyone think its the new radio I flashed that prompted this or did they push everyone??
Click to expand...
Click to collapse
I had the same issue -- I received the update even though I had not accepted or checked for it. Took my phone out of my bag at work and saw I was at the Android man and exclamation point screen.
I wiped cache and wiped Dalvik cache, and the update stopped. I did flash the new radios though for the .9 update and have been sitting fine on 4G for the last two hours.

[Completed] Hello everyone my name is Michael. I have an Archos FamilyPad 2 doing a boot loop.

When my Archos FamilyPad 2 first arrived I was so excited. It was a pre-owned one that I got from Amazon. I took it out and the battery was dead. So I plugged it up to charge for about 15 minutes before I turned it on with the charger still intact. Alright. Everything was fine as I saw the previous owners apps and games on the home page. First thing I did was performed a factory reset from the settings menu. I noticed that the developers option had already been turned on. So I was thinking I would have to tap the build number after the factory reset to get the developers option back on. To my surprise it was already cooked into the OS for some reason. So I started tinkering with it while everything was starting to update. The only way I know how to root is through KingRoot. So that's what I always use to root my devices. The root was successful as it is about 75% of the time with KingRoot. Everything checked out with Root Checker and root was properly installed by KingRoot. Then I got superuser access and granted all permissions. Got BusyBox in and xposed framework. I overclocked it to see what it would do. It ran pretty decent for a duo core with 1 GB of RAM. So I began to start messing with the LCD display and density to make the resolution a bit better and sharper. And it worked. Changed the system font with Font Master. And changed the things that needed to be changed for the system to read it as running Android 6.0.1. So then I wanted to cut the boot time in half by turning off the boot animations. Reboot and yes it did work. I then started to wonder how customized boot animations would look. The .IMG boot animation that I wanted to see is the new Android boot up logo. So I restarted the tablet without turning the boot animations back on. So it started doing a boot loop at that point. So I went into Recovery Mode to try to do a hard reset and I rebooted it again. It can never get past the initial Archos logo now. Even after a hard reset. I don't know how to take the battery out. So I let the battery drain. I thought it may be the same as taking the battery out and resetting it. Well it still just shows the first Archos logo and then the screen goes blank and never gets to the lock screen anymore. Does anyone know a solution to this? Or is it over for this Archos FamilyPad?

XDA Visitor said:
When my Archos FamilyPad 2 first arrived I was so excited. It was a pre-owned one that I got from Amazon. I took it out and the battery was dead. So I plugged it up to charge for about 15 minutes before I turned it on with the charger still intact. Alright. Everything was fine as I saw the previous owners apps and games on the home page. First thing I did was performed a factory reset from the settings menu. I noticed that the developers option had already been turned on. So I was thinking I would have to tap the build number after the factory reset to get the developers option back on. To my surprise it was already cooked into the OS for some reason. So I started tinkering with it while everything was starting to update. The only way I know how to root is through KingRoot. So that's what I always use to root my devices. The root was successful as it is about 75% of the time with KingRoot. Everything checked out with Root Checker and root was properly installed by KingRoot. Then I got superuser access and granted all permissions. Got BusyBox in and xposed framework. I overclocked it to see what it would do. It ran pretty decent for a duo core with 1 GB of RAM. So I began to start messing with the LCD display and density to make the resolution a bit better and sharper. And it worked. Changed the system font with Font Master. And changed the things that needed to be changed for the system to read it as running Android 6.0.1. So then I wanted to cut the boot time in half by turning off the boot animations. Reboot and yes it did work. I then started to wonder how customized boot animations would look. The .IMG boot animation that I wanted to see is the new Android boot up logo. So I restarted the tablet without turning the boot animations back on. So it started doing a boot loop at that point. So I went into Recovery Mode to try to do a hard reset and I rebooted it again. It can never get past the initial Archos logo now. Even after a hard reset. I don't know how to take the battery out. So I let the battery drain. I thought it may be the same as taking the battery out and resetting it. Well it still just shows the first Archos logo and then the screen goes blank and never gets to the lock screen anymore. Does anyone know a solution to this? Or is it over for this Archos FamilyPad?
Click to expand...
Click to collapse
Greetings,
Thank you for using XDA Assist.
First, please create an XDA account so you can post in other forums.
After that, please post your question here:
Android Q&A
You'll find expert advice there. Good luck and welcome to XDA!

Why does my Google Pixel randomly reboot?

Hi. My device worked just perfect until 5 days ago. It slowly began to ignore some tasks like opening apps or doing calls.
2 days ago my google pixel with Android 8.0 started to ignore every input i made, like opening apps or trying to reboot. It behaving like this after taking some pictures with the rear cam. After some attepts in opening apps it started to reboot. But instead of a normal reboot it stuck in a booting screen (the one with the Google G and a gray animation bar underneath). It took a while and i waited until it seemed that the OS booted correctly. But after this my device started to reboot randomly after a few minutes. After a while i figured out, that i can hold the power button while the screen with the google G was up to reboot it normally. This worked so that the phone was at least half an hour or more working until it rebooted again out of nowhere.
So far i tried to get it in safe mode and delete some apps like whatts app etc. In safe mode i didnt notice any crashes so far.... but in normal one it does a lot so deleting apps wasnt helpful. Turning on flight mode was not helpful either.
What can I do? What could it be?

marf3 said:
Hi. My device worked just perfect until 5 days ago. It slowly began to ignore some tasks like opening apps or doing calls.
2 days ago my google pixel with Android 8.0 started to ignore every input i made, like opening apps or trying to reboot. It behaving like this after taking some pictures with the rear cam. After some attepts in opening apps it started to reboot. But instead of a normal reboot it stuck in a booting screen (the one with the Google G and a gray animation bar underneath). It took a while and i waited until it seemed that the OS booted correctly. But after this my device started to reboot randomly after a few minutes. After a while i figured out, that i can hold the power button while the screen with the google G was up to reboot it normally. This worked so that the phone was at least half an hour or more working until it rebooted again out of nowhere.
So far i tried to get it in safe mode and delete some apps like whatts app etc. In safe mode i didnt notice any crashes so far.... but in normal one it does a lot so deleting apps wasnt helpful. Turning on flight mode was not helpful either.
What can I do? What could it be?
Click to expand...
Click to collapse
Same thing happens with my Pixel, sometimes the phone is just get stuck on some random screen then I have to press and hold it for 15 seconds to let it reboot again. Lately I have started to see another problem, when it reboots bunch of google apps and services stops working and gives hell lot of notifications. All this started to happen after Android Oreo update

pradctgign said:
Same thing happens with my Pixel, sometimes the phone is just get stuck on some random screen then I have to press and hold it for 15 seconds to let it reboot again. Lately I have started to see another problem, when it reboots bunch of google apps and services stops working and gives hell lot of notifications. All this started to happen after Android Oreo update
Click to expand...
Click to collapse
I noticed problems with my ear speaker as well. And i cant make phone calls. The phone doent respond anymore when i try to.

Same problem after android 8.0 update

If you have installed the latest Google phone/dialer app, that is likely the problem, was for me.
Find the app in settings and uninstall,it will roll back to a previous version and hopefully fix your issues.
Sent from my Pixel using Tapatalk

My pixel does the same thing, ever since I updated to 8.0, have you tried doing a factory reset? I haven't done it yet, I have been uninstalling apps for the last couple of days, when it is in safe mode it works good, but when it's not, it freezes and restarts. I'm going to try uninstalling the latest version on google dialer to see if it helps.

I just want to update everyone in case you are having a problem with the random reboots.
I uninstalled the phone update and it was still randomly rebooting so I backed up the stuff that I needed and just did a factory reset. I have been a full day on my phone without any problems. I did a factory reset twice, just in case, for some crazy reason, the phone still had a problem, I wiped it twice! I think you'll be good with only wiping once.
Anyways to sum it all up, I did a factory reset, restored all of my backed up data from my pixel, I had about 120 apps and the phone has not had a problem since. I hope it helps someone else.

droid4lif3 said:
I just want to update everyone in case you are having a problem with the random reboots.
I uninstalled the phone update and it was still randomly rebooting so I backed up the stuff that I needed and just did a factory reset. I have been a full day on my phone without any problems. I did a factory reset twice, just in case, for some crazy reason, the phone still had a problem, I wiped it twice! I think you'll be good with only wiping once.
Anyways to sum it all up, I did a factory reset, restored all of my backed up data from my pixel, I had about 120 apps and the phone has not had a problem since. I hope it helps someone else.
Click to expand...
Click to collapse
Mate, please report if you're still getting the reboots. Mine disappear for two weeks after I do a factory reset and then come back. Same happens in Safe Mode. Bug report claims it's 'Sense Key : Hardware Error [current]' and Google rep says it's a hardware issue (Toshiba's memory or something). Buganiser thread is here.

wrong place sry

Had this on my pixel xl. I was on the 8.1 beta.
factory reset, rolled back to 8.0
8.1 ota official
haven't had a reboot in over a week now

Murrzeak said:
Mate, please report if you're still getting the reboots. Mine disappear for two weeks after I do a factory reset and then come back. Same happens in Safe Mode. Bug report claims it's 'Sense Key : Hardware Error [current]' and Google rep says it's a hardware issue (Toshiba's memory or something). Buganiser thread is here.
Click to expand...
Click to collapse
Yea, the issue is back, has been for about 2 weeks. This phone is really starting to be a pain in the ass, I can't believe that it happens so often. Did you do a warranty fix?

That's a pity. Yes, I did. Got the device roughly two and a half weeks ago. Flashed 8.0 and then sideloaded 8.1 right away. Knock on wood, all good. But there's still a report every other day in Buganiser of a phone even on 8.1 doing this.

Got mine at release. November 16. Google won't replace it either. I have a one pixel brick

I have the same problem. However, it is not frequent enough on Android P beta. But as soon as I go back to the stable build, it starts to do the same thing. Did you guys have any luck resolving this or should I send it back to the vendor I bought it from. They won't replace the device in Pakistan but may be will fix it in some manner.

Pixel randomly shuts down then says needs to be factory reset to boot..

I Just got my pixel about a week ago I am using it when all of the sudden it just randomly shuts down and then goes to the boot screen for a second then goes to recovery mode and says cannot load operating system needs to be restored.
I have just finished setting everything up on the phone I had no backup for my music and playlists I am beyond fuming right now. Is this a common issue with this phone? I was not rooted in any way, completely stock.

rbtrucking said:
I Just got my pixel about a week ago I am using it when all of the sudden it just randomly shuts down and then goes to the boot screen for a second then goes to recovery mode and says cannot load operating system needs to be restored.
I have just finished setting everything up on the phone I had no backup for my music and playlists I am beyond fuming right now. Is this a common issue with this phone? I was not rooted in any way, completely stock.
Click to expand...
Click to collapse
Follow this guide maybe the firmware got corrupted..https://www.the***********.com/restore-google-pixel-2-stock-firmware/
Sent from my [device_name] using XDA-Developers Legacy app