Related
So I was looking through the topics in this part of the forum today, and I saw "[Q] What is causing "Communication Failed" error?" (It won't let me post the link to it?) I followed the link in that topic and did what that guy said would help, and after doing that I restarted my phone. It did all of the startup animations correctly, I can still access the recovery menu out of it, but when I get past the startup animations, I'm just greeted with a black screen. The buttons on the bottom of the phone are lit up, but the screen gives no response. I can't turn it off without taking out the battery, and that doesn't help. If possible I'd like to try to fix this without sending my phone in, or without deleting the user data. Any fixes for this?
I would try re-downloading the ROM you want to use and then re-install it. But maybe there's a better fix, that's just what I've done whenever I encounter something strange.
sschrupp said:
I would try re-downloading the ROM you want to use and then re-install it. But maybe there's a better fix, that's just what I've done whenever I encounter something strange.
Click to expand...
Click to collapse
I can't exactly put anything onto my phone with this problem. I can't access the screen at all past the startup animations. It's just black.
Not Bricked!
You have a few options as it seems your phone is "on" and should be recognized by your computer still.
What was it you were doing to the phone before it started doing this behavior.. wasn't quite clear on that....
If it was a mod to change your framework-res.apk. You can find the "stock" one in the ROM you originally downloaded and revert back to stock by doing an ADB Push to your /system/media folder.
Or... you will need to flash your phone back to stock - which means you will need to go here and download Odin and run it.
Always helps to have that "plan b". Bottom line though - your phone isn't bricked and you should be able to restore it and continue on. But... please note that ODIN will wipe your phone and anything you had on it will go bye bye.
androidforums.com/captivate-support-troubleshooting/217905-cant-connect-t-server-updates.html
I followed the advice on how to fix that problem in the second post in that topic. When I restarted my phone the screen just ended up going black. I'm going to try that Odin thing, I hope it works.
e. It's kinda annoying how I can't post links.
Ok Edit again, I've tried the Odin thing, and it just isn't working. Now whenever I try to put my Simcard back in, It doesn't even do the startup things, it just goes to that Phone Caution symbol PC picture thing. I'm worried that I'd have to go get a replacement.
Can you please provide us with a list of everything you have done to your phone and how you tried to use Odin? That will help us help you. Please be specific, this will get you the help you need. I read the link, did you use ADB or the first method in that thread? Sounds like you messed up while trying to fix your device manager. I am not sure how it is you tried to use Odin, try using a rear usb port, Odin can be a pain, make sure you have the drivers installed.
Ok, Here's a list of what I've done to my phone over the past few days.
1. I rooted it.
2. I kinda sorta half-assed the process of allowing me to put on Non-Market apps onto my phone, I made it so that the settings.db file had the permissions all set up, but I never replaced the first settings.db file. (It's just sitting on my phone's interal SD card.)
3. I tried to do that Non-ADB method listed in that topic I linked to. After that I started having these problems.
4. I accidently ended up clearing the Data cache through the recovery menu thing. Just an accidental moving of the buttons. It didn't seem to effect anything.
5. I booted the phone into recovery mode and tried the Odin thing. It got stuck at File Analysis, and I tried again. It still got stuck, and I let it continue trying it while I was eating dinner. After I got back it was still on that, so I took out the USB cord and phone battery and put the Sim card back in. When I try to boot it up it goes to that PC error phone thing. (I can't exactly get an image of it, I hope you know what I'm talking about.)
And that's all I've done to it. I'd try a different USB port, but I don't have any more. I'd try my other computer, but that's a Linux machine, and Odin is a Windows/DOS executable file. I'm pretty sure the drivers are installed correctly, as I had been doing stuff with the phone via USB just yesterday.
I hope that's enough detail to help figure out something.
I'd hate to doulbe post, but I really really do need the help with this. If any of you have any advice for it all, please, feel free to contribute. If there is no fix for this, and my phone is actually bricked, just let me know so I can go get a replacement.
Did you make sure you had odin started up BEFORE you put your phone in download mode? Odin is very touchy and you have to do things exactly right or it won't work.
Yes, I've made sure to follow all of the steps right to the last peroid. I'm probably just going to have to go get a replacement anyway.
I've tried many different things in alot of the threads I've read on this forum and nothing is working. I tried using the One-Click root on my Droid and it didn't work, come to find out, it was an outdated method for the Droid 3. It messed up my phone. My apps constantly crash. My texts disappear, then sometimes reappear switching the place of the texts randomly. When I reset from settings, it restarts phone, but nothing is reset. It won't let me check my e-mails(G-mail). I can hardly do anything. I've tried flashing back using the AP Fastboot method from psouza(spelling?). On my phone it says Battery OK/Program OK/USB Connected. So I run the "CLICK HERE - Flash Verizon DROID 3 OTA 5.6.890 to phone.bat". It failed.
Then I tried ovelayers method. Everything seems to go good. And I was happy! But when it rebooted, it took me to the android triangle screen. SO I selcected reboot. And absolutely nothing changed. Am I Missing a step? I also tried doing it again, but after it went to traingle android screen, I selected the update from the SD card, installed it, rebooted, and STILL nothing. Nothing changes. Ever. Nothing is working. Please help. I tried being as descriptive as possible so that it answers most potential questions.
*Edit* I've also tried the RDS Lite method. Crashes on step 3.
Phone specs: Version: 5.7.906.XT862.Verizon.en.US
Kernel: 2.6.35.7-g5fa4155
Android 2.3.4
download full system file
http://dev-host.org/uEA
put it on your sdcard, and if you are on "android triangle screen" go to menu
pickup update, select the downloaded file and install it.
After will all done push reboot from menu
thats all
Make sure you use the sbf for. 906 and not the one for. 890
http://d-h.st/mvX
niko99 said:
download full system file
put it on your sdcard, and if you are on "android triangle screen" go to menu
pickup update, select the downloaded file and install it.
After will all done push reboot from menu
thats all
Click to expand...
Click to collapse
I have the full system file already. That's what I tried using to update. The problem doesn't lie there though. The problem is that no matter what I do, the phone never resets. It's on right now. If I uninstall apps right now and restart my phone, they'll still be there. Likewise with installing them. If I text anyone, when I restart my phone, that conversation will be gone. Likewise with call logs and everything else. The phone literally after every restart goes back to the same position it was when I badly rooted the first time. No resets, recoveries, hard resets, flashes, etc have worked thus far. I've used ALL the one click SBF versions also, just to be thorough. The phone literally will not change. What I need is something similar to a computer. I need to completely wipe it. Then I need to completely reinstall it from scratch. Just like reformatting your hard drive. I've heard that there has really been no case of an unbrickable phone, that there is always a way to fix it; but this far, I haven't found anybody that hasn't had their phone fixed. Even those that have had similar issues fixed it, and I've tried the methods they've provided to no avail.
xJolly said:
I have the full system file already. That's what I tried using to update. The problem doesn't lie there though. The problem is that no matter what I do, the phone never resets. It's on right now. If I uninstall apps right now and restart my phone, they'll still be there. Likewise with installing them. If I text anyone, when I restart my phone, that conversation will be gone. Likewise with call logs and everything else. The phone literally after every restart goes back to the same position it was when I badly rooted the first time. No resets, recoveries, hard resets, flashes, etc have worked thus far. I've used ALL the one click SBF versions also, just to be thorough. The phone literally will not change. What I need is something similar to a computer. I need to completely wipe it. Then I need to completely reinstall it from scratch. Just like reformatting your hard drive. I've heard that there has really been no case of an unbrickable phone, that there is always a way to fix it; but this far, I haven't found anybody that hasn't had their phone fixed. Even those that have had similar issues fixed it, and I've tried the methods they've provided to no avail.
Click to expand...
Click to collapse
Can you install bootstrap? That way you can wipe data, and there should be no way it boots back like nothing has changed
http://db.tt/pi5c484a
Edit: or, boot into recovery with x+power (or m+power i always forget) and wipe/factory from there
DoubleYouPee said:
Can you install bootstrap? That way you can wipe data, and there should be no way it boots back like nothing has changed.
Edit: or, boot into recovery with x+power (or m+power i always forget) and wipe/factory from there
Click to expand...
Click to collapse
I will attempt that now. How is it used? I can build pc's and am rather intelligent in the IT of macs and pc's. But haven't had to do much with Androids till now. Lol. I've tried the wipe/factory method already. I understand that .apk is the file extension for Google Play apps, and I can install it via the SD card, but what do I do from then?
*EDIT* It's installed, it has bootstrap recovery and reboot recovery. Reboot does nothing. Bootstrap says there's an error running a command. Looks like a directory about files and hashcodes. "Working Directory: null/Environment: null".
xJolly said:
I will attempt that now. How is it used? I can build pc's and am rather intelligent in the IT of macs and pc's. But haven't had to do much with Androids till now. Lol. I've tried the wipe/factory method already. I understand that .apk is the file extension for Google Play apps, and I can install it via the SD card, but what do I do from then?
*EDIT* It's installed, it has bootstrap recovery and reboot recovery. Reboot does nothing. Bootstrap says there's an error running a command. Looks like a directory about files and hashcodes. "Working Directory: null/Environment: null".
Click to expand...
Click to collapse
First you need root access. Use Motofail if you haven't:
https://www.dropbox.com/s/wpl88mwm6eilhe6/motofail.exe
Open bootstrap, press bootstrap recovery, afterwards press reboot recovery.
If it doesn't work, shutdown your phone, hold X and press power and do it from there
DoubleYouPee said:
First you need root access. Use Motofail if you haven't:
Open bootstrap, press bootstrap recovery, afterwards press reboot recovery.
If it doesn't work, shutdown your phone, hold X and press power and do it from there
Click to expand...
Click to collapse
Figured. My phone won't root. Like I said, nothing will change about it.
xJolly said:
Figured. My phone won't root. Like I said, nothing will change about it.
Click to expand...
Click to collapse
Ok so what about x+power?
DoubleYouPee said:
Ok so what about x+power?
Click to expand...
Click to collapse
No. It doesn't work. I've tried that.
xJolly said:
No. It doesn't work. I've tried that.
Click to expand...
Click to collapse
So you did wipe/factory reset from recovery and it still boots like nothing happened? I'm not sure how thats possible.. stock recovery shouldnt have anything to do with what you messed up in your rom. Maybe for some reason your phone is unable to write data anymore
DoubleYouPee said:
So you did wipe/factory reset from recovery and it still boots like nothing happened? I'm not sure how thats possible.. stock recovery shouldnt have anything to do with what you messed up in your rom. Maybe for some reason your phone is unable to write data anymore
Click to expand...
Click to collapse
I'm going to record a video. And show you the multiple things that happens. I'll have to PM it to you though, and anyone who wants to see it.
I remember someone else having a similar issue on their device. Since I'm home sick today I'll see if I can find the thread and if it ever got solved
Sent from my XT860 using xda premium
Just saw your vid and its exactly as you say. I don't know whats going wrong..
Writing yo your internal might not be the same as writing to your data partition.. I don't see why else wiping from recovery would fail since that part should be unaffected.
You said sbf says its succesful however on your screenshot i see errors.
DoubleYouPee said:
Just saw your vid and its exactly as you say. I don't know whats going wrong..
Writing yo your internal might not be the same as writing to your data partition.. I don't see why else wiping from recovery would fail since that part should be unaffected.
You said sbf says its succesful however on your screenshot i see errors.
Click to expand...
Click to collapse
There's only errors for the click here to flash method, however, the ovelayer method screenshot says there are no errors, unless I am missing something there.
xJolly said:
There's only errors for the click here to flash method, however, the ovelayer method screenshot says there are no errors, unless I am missing something there.
Click to expand...
Click to collapse
You're right. No way you can send it back for replacement? Your phone seems stock
DoubleYouPee said:
You're right. No way you can send it back for replacement? Your phone seems stock
Click to expand...
Click to collapse
Well, I don't have insurance on it, as I had gotten it from a friend. So, no. Not without paying an arm and a leg, at which point I'd pay for a new phone instead. I just really wish this could be fixed. I've heard no phone was unbrickable. AM I THE PRODIGY?!
Phone: Samsung Captivate I-896, with AT&T stock Android 2.2 flashed to it. Rooted and unlocked.
Action: Deleted some *.odex files from Root/Data/App, following a guide to get around the "out of space" message while trying to install software. Cleared Delviks cache directory.
Problem: First restart after above actions(which didn't resolve the out of space message issue), phone shows start-up animations, gets stuck with black screen. Left like this overnight, nothing happens. Vibrates every 50 seconds or so. Respons to hardware Vol+ press with the home/back/menu backlight. Otherwise, no response to anything, black screen(backlight on). Does not receive phone calls. I do not know for sure if the action listed above is the one that caused this situation, but I assume so since it was the last action taken before the issue appeared.
Solutions attempted: Tried every possible permutation/combination of buttons/usb cable/etc/ restarts etc. listed here: http://forum.xda-developers.com/showthread.php?t=858765&page=1, except Jig. The phone would not go into recovery or DL mode.
Question.
Am I correct in assuming that forcing the phone into recovery mode and reflashing a new system(or reflashing the old one) is the only way to get the phone to work again?
There is no way to "soft-reset" the phone, with all settings reverted back to stock, if it does not boot up completely?
Titerepayaso said:
Phone: Samsung Captivate I-896, with AT&T stock Android 2.2 flashed to it. Rooted and unlocked.
Action: Deleted some *.odex files from Root/Data/App, following a guide to get around the "out of space" message while trying to install software. Cleared Delviks cache directory.
Problem: First restart after above actions(which didn't resolve the out of space message issue), phone shows start-up animations, gets stuck with black screen. Left like this overnight, nothing happens. Vibrates every 50 seconds or so. Respons to hardware Vol+ press with the home/back/menu backlight. Otherwise, no response to anything, black screen(backlight on). Does not receive phone calls. I do not know for sure if the action listed above is the one that caused this situation, but I assume so since it was the last action taken before the issue appeared.
Solutions attempted: Tried every possible permutation/combination of buttons/usb cable/etc/ restarts etc. listed here: http://forum.xda-developers.com/showthread.php?t=858765&page=1, except Jig. The phone would not go into recovery or DL mode.
Question.
Am I correct in assuming that forcing the phone into recovery mode and reflashing a new system(or reflashing the old one) is the only way to get the phone to work again?
There is no way to "soft-reset" the phone, with all settings reverted back to stock, if it does not boot up completely?
Click to expand...
Click to collapse
Sounds pretty accurate. You'll have to get a jig to get in download mode, flash stock Odin KK4 to fix w/e happened during your testing.
Thanks Bwolf. I just tried ADB console on a different computer and it connects to the device just fine in spite of black screen. I guess I had one thing right, USB DEBUGGING enabled before this whole deal.
Question: is there any way I can restore the phone using the console without wiping everything?
Titerepayaso said:
Thanks Bwolf. I just tried ADB console on a different computer and it connects to the device just fine in spite of black screen. I guess I had one thing right, USB DEBUGGING enabled before this whole deal.
Question: is there any way I can restore the phone using the console without wiping everything?
Click to expand...
Click to collapse
Make a backup with ADB.
Once that's done, push download mode with it and get Odin KK4 (without bootloaders). You'll have to start from there to fix w/e went wrong.
You don't have to wipe your sd doing so but you will lose your apps and such. If you backed up your phone with your Play Store account, it will re-download your apps as you're done booting up.
To get back up where you were, grab Corn Kernel, flash it with Odin 1.87 and then follow the full instructions of the ROM you wanna use.
I have a droid bionic that I acquired used that had some major stability issues when I got it. It appeared to be on stock ICS when I got it, so I tried to reflash through rsdlite. The flash just stuck on step 1 of the flash. I've tried HOB method, and every other method I've come across, but all writes to the phone just hang indefinitely. All of the erase steps complete though, and when I've unplugged the USB cable after hanging and plug back in, it will move on to the next erase, copy, write step and hang on the write. So now I have a phone that appears to have every thin wiped during the deletes, and no system of any kind. From day one, when entering recovery I would get several lines about not being able to mount cache etc. The only thing that flashed successfully was a radio flash.
I appreciate any help, but please don't direct me to any more guides unless it is relevant to the can't mount... errors I'm getting. I need to find the reason why no write operations complete and just hang. That's where my problem really lies.
Genaugmen said:
I have a droid bionic that I acquired used that had some major stability issues when I got it. It appeared to be on stock ICS when I got it, so I tried to reflash through rsdlite. The flash just stuck on step 1 of the flash. I've tried HOB method, and every other method I've come across, but all writes to the phone just hang indefinitely. All of the erase steps complete though, and when I've unplugged the USB cable after hanging and plug back in, it will move on to the next erase, copy, write step and hang on the write. So now I have a phone that appears to have every thin wiped during the deletes, and no system of any kind. From day one, when entering recovery I would get several lines about not being able to mount cache etc. The only thing that flashed successfully was a radio flash.
I appreciate any help, but please don't direct me to any more guides unless it is relevant to the can't mount... errors I'm getting. I need to find the reason why no write operations complete and just hang. That's where my problem really lies.
Click to expand...
Click to collapse
i recently had issues with rsdlite but eventually got it working with jb4.1.2.
i am using 5.7 and erased a couple things from the xml file to get it working. if you dont care of root install 4.1.2
podagee said:
i recently had issues with rsdlite but eventually got it working with jb4.1.2.
i am using 5.7 and erased a couple things from the xml file to get it working. if you dont care of root install 4.1.2
Click to expand...
Click to collapse
I've tried to flash individual parts of the the fxz but it still hangs on every write operation no matter what method I try. I'm becoming convinced it's a hardware fault. I've tried several versions of rsdlite. I can't get one package to complete a write operation. I've seen others with similar problems, but none that couldn't get make at least some progress with a flash, even if they had trouble getting it fully flashed. Unfortunately, the erase commands for the different methods I tried did complete without issue, so now I have no system at all it seems.
i'm in desperate need for guide please,
so i first off i had some questions (excuse my stupidity but i really couldn't find any answers around)
1) can an never-rooted android device's build number change or is it always the same? like with stock/official updates only?
2) my recovery mode (stock/system recovery) aborts every single installation file (official rom from the Asus website) without even opening the package, it's like i press 'install update from sd card' then as i press the zip file, it immediately says 'installation aborted' without even typing any other significations/steps, and the same happened for the kernals zip files too. so does that mean my recovery mode is corrupted or something is wrong with it?
3) i noticed some slight changes in my recovery since the last bootloop i had and had to use it back then, for example the dead android screen appearing after choosing the recovery mode, at first it used to say 'no command' under the dead android, but this time it doesn't say anything, just the dead android image only until i press power button and volume up to get the recovery options. so does that mean my firmware version changes since last time or my recovery is corrupted or it just means nothing?
4) is there aNYWAY to know my build number of a phone in bootloop (not rooted but bootloader unlocked)
so my initial problem is; i had my asus zenfone go zc500tg on march 2016. it was working so fine actually (using it like a default user not actually knowing anything about roms/flashing/recovery etc) until july of 2017 when i noticed my phone was a bit slow (out of the ordinary) and it used to get SO hot while using it normally and battery drained pretty faster than before, but i didn't know what to do tbh so i just kind of ignored something was off. but not long after these symptoms, the booting of my phone got slower and slower, until it reached its max by staying more than three hours just doing the 'optimizing apps' on the booting screen until it booted, so i thought it was a virus that would go away after a factory reset, and after the reset, it got worse, until it stopped booting and got into a bootloop. I panicked then because i didn't have the slightest idea what was happening until some internet searching guided me into the world of bootloops and custom roms and recovery. so i eventually managed to fix the bootloop and it worked fine for several months until it started to lag again and boot slowly and got the second bootloop, and that i fixed like the first one by installing the rom from the asus website then putting it on the sd card sand flashing it through recovery,
the third bootloop was quite the same, except that i did something additional in recovery mode, i pressed "backup user data" and that did a nandroid backup then i restored it smoothly after flashing the rom.
the fourth bootloop was a bit different, i as always downloaded the same firmware as the times before and flashed it and backed up user data too, but the odd thing that happened was me getting a message box that won't go away that said "unfortunately, the process com.android.phone has stopped" the phone worked but the sim cards weren't recognized and the message box was coming and going every second, so i noticed that the message box went away (nearly) when i got my sd card out, but still the phone app and the sim cards were corrupted,i thought the issue was from my sd card at first but i eventually, (coincidentally tbh) managed to fix it by doing the OTA update that was due, (that bootloop was fixed on the date of January 13th 2018)
then my phone was working so fine and everything was alright.
then shortly after (january 20th 2018) i was on whatsapp normally then suddenly ALL the things on my phone came crashing in front of me : TONS of endless message boxes saying things like "unfortunately, the process com.(any app on my phone) has stopped"
that i literally panicked and tears welled up in my eyes, so i rebooted the phone and while rebooting it did a (relatively quick) "optimizing apps" but as it booted everything was the dreaded same, all the apps crashing, then with the second rebooting was the current bootloop. i thought it was the same as before and just downloaded the usual zip file i use everytime but while flashing it (it did the same as mentioned in question 2 above) but it aborted instantly so i went and downloaded every rom there but it was the same so i went and tried the kernal zips too but always the same (i can't read my build number through the system recovery because it is like not fitting well in the screen si half the number isn't there that's why i asked question number 4)
so can anyone help me please? i'm in desperate need for help, i'm literally crying while typing this because i can't afford another phone and i'm so scared.
also is there a way to install custom recovery to not rooted device while in bootloop?
or if the system recovery was actually corrupted what do i do? :crying: