Related
Alright, allow me to summerize to you guys the series of screw ups that happened in the day that I've had my captivate.
Basically, it's like this. I got this phone from my brother (it used to be his). Now when I got it, I began basically erasing his contents and setting up mine. The Phone is on the Cognition OS and everything seemed fine.
Now, when I tried to set up my google account, it said I had to do a factory reset, I did that. Then I realized the market place app was no longer there :/
I did another factory reset, still didn't help, and started looking around for info.
I told my buddy this and he said he could fix it. So he get's the update.zip for rooting the phone, sets it up on the SD card, and goes to root the phone normally. Except when he restarts the phone after, it doesn't go to the set up screen, so he just starts it normally and enters the setup screen by holding home+volume up+power.
Then he presses the reinstall packages, and the phone seems to get to work on the update pack...
Now, every time I turn on the phone the voice says "converting data partition to optimize extension four", turns off, then repeats.
I've looked up this problem and it seems to have something to do with voodoo, but the causes in the other cases the causes were different.
Can someone please help me out here? I've also tried doing a hard reset by holding the volume down button and pressing power, but nothing seems to take me to the recovery mode.
HELP.
Did you pull the battery during this our did you let it run? Should let it run.
Does your phone boot up at all?
At&t or rogers?
Do you have a windows pc with usb drivers installed?
What its your build number, located under battery, something like 1008?
Answer these questions and we can get you back up and running
-Well after he did the reinstall thing we let it run for like 15 minutes, then he pulled the battery out.
-The phone only shows the AT&T screen, say's the "converting data partition..." thing, then goes blank and does it again. I've let it run for like 10-15 minutes before having to turn it off because I couldn't have the speech going off.
-I have a windows PC, and but I'm not sure if I have the drivers installed. I have Kies installed and when I plugged the phone in before Kies could recognize the phone (though it wouldn't fully connect, it would just say "connecting" on the kies screen).
-The Model is SGH-I897, that's the only relevant thing I see under the battery, that good enough?
Thanks a lot.
No, your phone has a build, on phone under battery, the word build is not listed. Something between 1006-1012
If we are going to do this you need to be active, I can not wait 20 minutes in between responses
Sorry the internet kinda crapped out actually.
And I see a 1007 between the bar codes, that it?
Yes
Before we get started try this
Take battery, sim, ext sd our of phone
Plug usb into pc but not phone
Put battery back in
Hold volume up and down, while holding plug in usb
Screen should come on with android with shovel
You can pull the battery again
Confirm this happened
Yep, it happened.
It may be easier if we use gtalk, log in on your pc using google id, send me an invite [email protected]. This way we know when each other respond
Just sent u the inv
I am having the same issue.. Chairchair did your problem get resolved?
Can anyone help?
James
liquorsh0tz said:
I am having the same issue.. Chairchair did your problem get resolved?
Can anyone help?
James
Click to expand...
Click to collapse
Have you gone back to stock and then reflashed? Seems like some files are getting corrupted. Because you have a voodoo kernel I would follow these steps. Make sure to back up.
1. Use Odin to flash a non vodoo kernel.
2. Flash stock rom and master clear
3. Reflash rom of choice if it is 2.2
3a. If you want 2.3 follow the tut on it.
4. Breath a sigh of releive lol
Hello, my Photon started acting up really weird. First of all, it was really slow. I thought it's because I had like 150MB left and it was nearly full data-wise. However, I erased most of the data, and left it with 3GB left. Didn't work and it got worse.
I have these stripes around the display (just at sides, not at middle), while phone is turned on. Doesn't matter if in system, or at boot logo. Doesn't matter, because whenever I get to system, I can be in system for like 1 minute, then every application starts crashing (Apex launcher, Google play, whatever you pick) and I basically can't get anywhere. Also if I go to sleep mode, phone is basically dead and it's pure luck when I will turn on phone again. I am trying every few minutes and it's worthless, because any time I get to system anyway, I crash after few seconds.
What to do? I was planing to install custom ROM yesterday, but never got to that, because this all started to act up. So what should I do? Reset system? Any other ideas? Is phone dead?
Sorry for bad english, no bully please.
Thanks in advance
Update - now when I am trying to start up my phone, I have just black screen with white lines in the middle. Then phone shuts down. I will give more info when I will be at home and can get phone on charger
Well definitely try to charge the device up. You might try re-flashing the stock ROM using RSD Lite... Although from your description I fear your issue may be hardware related.
Could turn device on. Apparently that black screen with white lines was just discharged phone. When I put it on charger, I could again boot into system and it was working until I pressed power button to go to sleep mode and phone is again dead. Will try to flash RSD Lite later today and will post what happened
kanek06 said:
Could turn device on. Apparently that black screen with white lines was just discharged phone. When I put it on charger, I could again boot into system and it was working until I pressed power button to go to sleep mode and phone is again dead. Will try to flash RSD Lite later today and will post what happened
Click to expand...
Click to collapse
Charge the device as much as you possibly can before doing anything with RSD. Ideally you should have at least 50% battery in the device when flashing anything.
This is really miserable. I can't really get into bootloader. Because phone after that 'crash' or whatever you want to call it is dead and I can't even see if it's turned on or not. Basically I am randomly waiting when it's gonna restart and then I just get into system. Even if I fully discharge it, it will have black screen with white lines first, it flashes quite couple times and then it will finally boot into system. Also I remember it was ***** in past to get into recovery. Can I do anything from system? Because as soon as I don't turn off my screen by power button, phone is working, though it has those lines on side of LCD (I will try to borrow camera from someone and post it here today).
I set automatic turning screen off for 10 minutes and I am really careful about pressing power button. Sucks there is only option for just 10 minutes, so I have to tap on screen at least for once every 10 minutes or I will not have working phone. **** my life, really.
kanek06 said:
This is really miserable. I can't really get into bootloader. Because phone after that 'crash' or whatever you want to call it is dead and I can't even see if it's turned on or not. Basically I am randomly waiting when it's gonna restart and then I just get into system. Even if I fully discharge it, it will have black screen with white lines first, it flashes quite couple times and then it will finally boot into system. Also I remember it was ***** in past to get into recovery. Can I do anything from system? Because as soon as I don't turn off my screen by power button, phone is working, though it has those lines on side of LCD (I will try to borrow camera from someone and post it here today).
I set automatic turning screen off for 10 minutes and I am really careful about pressing power button. Sucks there is only option for just 10 minutes, so I have to tap on screen at least for once every 10 minutes or I will not have working phone. **** my life, really.
Click to expand...
Click to collapse
Why can't you turn the phone off and charge it while off, or boot to recovery and charge the phone in recovery?
arrrghhh said:
Why can't you turn the phone off and charge it while off, or boot to recovery and charge the phone in recovery?
Click to expand...
Click to collapse
About charging it while turned off - Can't because when I try to turn it on again, it's roulette when I get finally bootloader logo and not black screen with white stripes.
And boot to recovery. Is it possible to like download some command prompt application and boot to bootloader from there? I know when I had my G1 (and when I actually understood android ) you could boot to recovery or bootloader via console. I have astro installed on phone, so downloading some console application and installing it shouldn't be problem.
Btw as we are speaking, I tried to call someone and I basically get same thing like when I am going to sleep mode, I get black screen and now I am just waiting, when phone will eventually want to restart itself.
kanek06 said:
About charging it while turned off - Can't because when I try to turn it on again, it's roulette when I get finally bootloader logo and not black screen with white stripes.
And boot to recovery. Is it possible to like download some command prompt application and boot to bootloader from there? I know when I had my G1 (and when I actually understood android ) you could boot to recovery or bootloader via console. I have astro installed on phone, so downloading some console application and installing it shouldn't be problem.
Btw as we are speaking, I tried to call someone and I basically get same thing like when I am going to sleep mode, I get black screen and now I am just waiting, when phone will eventually want to restart itself.
Click to expand...
Click to collapse
Still sounds like some sort of a hardware issue, is the phone new to you?
You can certainly force bootloader mode, in several ways. When it's off you can hold power + camera and it will give you a choice of what to boot. When it's in Android you can do "adb reboot recovery" or "adb reboot bootloader" depending on where you want to end up. There are various apps which can also do this for you, if you are on the stock ROM but rooted.
arrrghhh said:
Still sounds like some sort of a hardware issue, is the phone new to you?
You can certainly force bootloader mode, in several ways. When it's off you can hold power + camera and it will give you a choice of what to boot. When it's in Android you can do "adb reboot recovery" or "adb reboot bootloader" depending on where you want to end up. There are various apps which can also do this for you, if you are on the stock ROM but rooted.
Click to expand...
Click to collapse
Phone is not new. I bought it used about one year ago.
I am not entirely new to android, but I didn't have android phone for 2 years and then I got this one. So I am really pretty **** with android atm
I will try reboot to bootloader from some console application.
I am rooted, opened bootloader, stock rom
Finally got into recovery, what now?
Also, when I once booted to system, I downloaded some root checking app, and root apparently isn't here. Well cornholio told me it is rooted back when I gave him my phone to perform sim card mod, but whatever. However, I am in recovery, but device is not detected by RSD Lite.
kanek06 said:
Finally got into recovery, what now?
Also, when I once booted to system, I downloaded some root checking app, and root apparently isn't here. Well cornholio told me it is rooted back when I gave him my phone to perform sim card mod, but whatever. However, I am in recovery, but device is not detected by RSD Lite.
Click to expand...
Click to collapse
Well reading back thru this thread, I was suggesting RSD Lite back to stock. I'm not really sure what you want to achieve tho, what your "final" goal is here.
I'm not even sure what kind of recovery you are booted into - stock recovery? CWM?
Either way, if you want to RSD the phone back to stock, you need to boot into fastboot/bootloader mode - not recovery. Just make sure the phone is charged up as much as possible before flashing in RSD.
Oh, sorry - misunderstanding from my side, thought I can switch to fastboot from recovery, oh well.
Also yeah, stock recovery.
To spread more facts - in case somebody would have similiar problems, when I try to just turn phone on, I have zero success what so ever. There's just this blank black page flashing every few seconds. However, when I remove back cover, I somehow force phone to load to bootloader logo, then I finally get chance to force phone to get to recovery. I will try to get to fastboot
kanek06 said:
Oh, sorry - misunderstanding from my side, thought I can switch to fastboot from recovery, oh well.
Also yeah, stock recovery.
To spread more facts - in case somebody would have similiar problems, when I try to just turn phone on, I have zero success what so ever. There's just this blank black page flashing every few seconds. However, when I remove back cover, I somehow force phone to load to bootloader logo, then I finally get chance to force phone to get to recovery. I will try to get to fastboot
Click to expand...
Click to collapse
Not sure if stock recovery has adb enabled, but if you have adb you can 'adb reboot bootloader'.
Otherwise do the power+cam trick I mentioned earlier.
http://i.imgur.com/3XYLngJ.png
kanek06 said:
http://i.imgur.com/3XYLngJ.png
Click to expand...
Click to collapse
Did you remove the getvar lines from the xml file...?
Yes
Weird. I only recall seeing that when people were trying to downgrade... but you are flashing 4.1.2.
The phone is in fastboot mode? What happens when you click "show device"? The "Device Properties" section is eerily empty.
I know it sounds shady, when I am coming back here again in few weeks, just been a bit busy lately, sorry about that.
However, somehow I got phone to flash it. The white graphical lines on sides dissapeared, however I got some new bug - I can't use phone in portrait mode, just in landscape - aka I need to swipe keyboard to have phone working. Also, that thing when phone completely stops working now occurs only when I am in that portrait mode, but I can restart phone this time.
When I finished this, it was midnight so I went to bad, so I tried to set up alarm, if it's gonna randomly shutdown like before and unfortunately, yes it did. I was waken up with this classical white line graphical bug black screen and had to reboot the phone. Oh well, managed to boot to system and it takes 5 minutes to fetch sim card (I have sim card mod from cornholio) and as I said, those white lines on side aka mysterious graphical bug is back.
Unfortunately for me, starts looking like real hardware issue now
Hello everyone! So I've had my phone (HTC One M8) rooted and custom recovery and rom installed for a little while now. The latest rom I've installed was Android Revolution HD 22.1. I also have twrp 2.8.1.0 installed. The other day my phone got wet and started to constantly reboot itself, wouldn't shut off and stay off, would never actually start. I put it in a cup of rice for 2 days, then proceeded to plug it in to charge it. Once charged enough I tried to turn it on. It only made it the HTC One logo screen and would vibrate every 10 seconds or so. I tried rebooting several times and no matter what I did with different button combinations I could not get it to load into bootloader. Eventually with restarting different ways and "mechanically stressing" the phone (short temper lol) I managed to get it to loading into the rom itself. From there I opened hasoons all in one toolkit to reboot directly into recovery and recovered to the stock rom. So the phone will now reboot with no problem into this rom. I haven't tried reflashing the ARHD 22.1 rom again because im afraid it'll break again. However, while in the stock rom everything work fines except for the volume up button which does nothing, except for while the screen is off, if I turn my phone to landscape the camera app will open without me even pressing the volume up button. If I reboot into bootloader via the quickboot app or hasoons toolkit, my volume down button with make the cursor go up, the volume up button does nothing, and the power button does nothing. The only thing I can do in bootloader is to hold power+volume up to get the phone to reboot. I also cannot get bootloader to load by holding volume down+power. So, After all that explaining, my main question would be, do you think that the buttons are shorting in a weird way because of water damage, or do you think my software got corrupted because of all the rebooting it did? Any help is appreciated, thanks!
-Tim
Hi,
You could try a clean flash of the rom.... If you're sure the wonky buttons won't interfere with the flash, because if they do... You'll be left with no OS on the device.
Water can affect many things, especially with power on while it was wet. This will be hard to solve, and could get costly. Usually with water damage, you fix or replace one thing, only to find now that something else doesn't work. Can turn into a real money pit.
You're issue isn't so bad, but my usual advice for worse cases are save your money for a new device, because you may never get your device fully working and spend a lot of money trying to fix it.
Ah, I just saw you already asked for help in your device section. Good. ?
Then this thread can be closed, as we're here to help navigate the site, not support.
Thank you.
The problem I have is with the galaxy z flip 3, it worked just fine inthe morning but after it ran outta juice and I charged it to a certain percentage, it stopped working properly, and got into an infinite boot loop, I tried forcing it to restart by long pressing volume down+power , but it didn't work, then I tried opening the recovery by long pressing on volume up+power and yet it also didn't work (I think that maybe it's because it was trying to boot at the time), so have you guys any solutions , please do help me cuz this phone really is important and with all honestly, isn't even mine XD, I'll be waiting for an answer
Your failsafe options are contact Samsung or do a factory reset (and then potentially contact Samsung).
If you can't boot it to anything, the only real option you have is to flash firmware, which likely won't help without wiping.
Unfortunately, not booting doesn't have a whole lot of options that don't wipe data without being rooted. Even then, you'd need recovery.
I see, then I may consider giving it to samsung, as long as they won't reset it, cuz the only reason why the phone is so important is because of the data, altough, isn't there any other way to acess recovery? Cuz I had this problem with the s10 before and I fixed it somehow (a certain Bixby key combination), but this time it seems there isn't any hidden combination.
Samsung is going to reset it. It's a required first step for them to do any work on it, even if the work has nothing to do with the software. What may help find a way to recover the data is starting with how it got to this point. Did you install anything new, change any important settings, or anything else that could have been a part of the issue? If not and it is an unexplained hardware failure, the data is likely gone already.
If it's something you might have installed or changed, it's possible that putting the phone in safe mode and undoing it may solve the issue and let you boot normally.
Booting into Safe Mode:
Make sure the device is powered off (charging is ok, as long as it is not currently trying to boot)
Hold the side key to power on and continue holding until "SAMSUNG" appears and the device vibrates
Immediately release the side key and begin holding volume down until boot completes
If the device has booted into safe mode, you will see a translucent "Safe Mode" in the bottom left
twistedumbrella said:
Samsung is going to reset it. It's a required first step for them to do any work on it, even if the work has nothing to do with the software. What may help find a way to recover the data is starting with how it got to this point. Did you install anything new, change any important settings, or anything else that could have been a part of the issue? If not and it is an unexplained hardware failure, the data is likely gone already.
If it's something you might have installed or changed, it's possible that putting the phone in safe mode and undoing it may solve the issue and let you boot normally.
Booting into Safe Mode:
Make sure the device is powered off (charging is ok, as long as it is not currently trying to boot)
Hold the side key to power on and continue holding until "SAMSUNG" appears and the device vibrates
Immediately release the side key and begin holding volume down until boot completes
If the device has booted into safe mode, you will see a translucent "Safe Mode" in the bottom left
Click to expand...
Click to collapse
Well I just asked the original owner (my mother), and apparently she doesn't remember downloading anything new into it, and it just went crazy by itself, also something else I wanna note, I tried charging it and it booted into recovery all by itself, I taught it was weird but Still went and wiped the cache and then when I tried restarting it it suddenly ran out of juice once again, also, it's second display shows some weird curruption/bug or glitch-like lines. So based off of this, can you really find the origin of this problem and if there is really any hope of saving it's data XD. Thank you btw, and once again, I'll be waiting for an answer
There are hundreds of reasons it could do that, including a faulty board. Thanks to the removal of physical sdcard support, you'd need to get it to boot into something with at least adb support to pull anything off it. Stock recovery doesn't provide any ways to perform a decent backup, but it sounds like the only option that wouldn't wipe the device didn't work.
I see, alright, thanks a lot, I'll consider resetting it
It may be worth trying to flash firmware first. Go into it knowing it may reset the device or leave you needing to reset it, but it doesn't hurt to try if you run out of safer options.
Same here, same symptoms, happened in front of my wife's and eyes face. We are fairly techy and understand our way around our devices. We also noticed the device crashed then would make it all the way to the home screen launcher and before catching signal the crash would cause a restart at that point I went in and did a cash swipe rebooted right back into recovery by itself then I unplugged the cable and it was acting as if it has a dead battery but when the cable was last plugged in during a couple of crash and then restarts all the way to the home screen I know the battery was at 70 something percent. My next step is going to probably be flashed the current firmware that just released on top of it as a dirty flash and see if I can get it to boot. If not then I'm going to do a hard reset and see if that works. When plugged in it automatically starts exhibiting symptoms as if the buttons are stuck. The devices in the OtterBox and it's fairly brand new I would say mint. Not dirty or any smudges either. all I'm saying is I'm one of those type of technicians that say yeah right when people say it just happened I don't know where but this actually happened I don't know when I was able to witness it. I'll come back and let you guys know what works and what doesn't. (By the way excuse my grammar I was voice typing while driving )
ariveraiv said:
Same here, same symptoms, happened in front of my wife's and eyes face. We are fairly techy and understand our way around our devices. We also noticed the device crashed then would make it all the way to the home screen launcher and before catching signal the crash would cause a restart at that point I went in and did a cash swipe rebooted right back into recovery by itself then I unplugged the cable and it was acting as if it has a dead battery but when the cable was last plugged in during a couple of crash and then restarts all the way to the home screen I know the battery was at 70 something percent. My next step is going to probably be flashed the current firmware that just released on top of it as a dirty flash and see if I can get it to boot. If not then I'm going to do a hard reset and see if that works. When plugged in it automatically starts exhibiting symptoms as if the buttons are stuck. The devices in the OtterBox and it's fairly brand new I would say mint. Not dirty or any smudges either. all I'm saying is I'm one of those type of technicians that say yeah right when people say it just happened I don't know where but this actually happened I don't know when I was able to witness it. I'll come back and let you guys know what works and what doesn't. (By the way excuse my grammar I was voice typing while driving )
Click to expand...
Click to collapse
Hello everyone just a quick update. Once I got home I plugged the device into a Samsung fast charger and Samsung OEM USB type-c cable and realize the device booted all the way to the home screen but register the same battery level as I mentioned above. Device was working as if nothing happened to it. So I updated all the apps on the Galaxy store then updated all the apps left over from the Google Play store, I then proceeded to check for a firmware update because I know the April update just released and installed the update with no issues. Updated the apps that needed to be updated again somehow there's always something and unplug the device from the power cable. Everything was working if no issues about half hour later the device cuts off and does not want to power on. FYI I already had my wife contact T-Mobile and get a warranty replacement we only paid $5.00 so my thoughts and conclusion on what's going on something happened to the battery or it's defective. Btw we only use Samsung OEM cables and equipment at home and in the car while connected through Android auto. it's only working while being plugged in it's not charging all the way even though it's registering it's charge level while the device is on.
Some time ago I wiped all my partitions on Xiaomi Redmi Note 5A, one by one, using adb. It was pretty dumb because I haven't had any experience with ARM or android. I thought it will act as x86 pc. I can remember that last thing I have done with it was flashing Arrow OS rom, the booting process was going that long that I gone sleep. When I woke up, the device was boiling hot. The android booting animation was still playing. I ran fastboot reboot and since that I haven't seen my phone working again.
I have tried already to enter recovery or do anything, but all my phone reacts to is the charging, the led goes bright (since it's a hardware condition, i guess). Except that, my device doesn't give any signs of working. I have also tried to enter the download mode by tooking the battery off (when I displace the back case using maintenance tools for mobiles) and connecting two gold-color pins and holding the power button. It doesn't seem to work. It has no chance, there is no recovery.
What I got now:
- ADB doesn't see my phone since it can't power on
- Fastboot doesn't see my phone since it's unable to enter fastboot mode
- The device doesn't react to anything
If someone could help, I would really appreciate it.
Take phone to authorized service center and let them try to fix it.
xXx yYy said:
Take phone to authorized service center and let them try to fix it.
Click to expand...
Click to collapse
I won't pay any more for this goofy ah phon. Is it impossible to fix it at home?