Database Info

"Converting data partition..." Problem

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

Black screen & no recovery!!!!

Hi all !!! Sorry for my English but I need your help
I commented what is happening with my phone N5 (which for good and evil is always stock without root or anything, with corresponding OTA updates.)
1- Yesterday afternoon at lunchtime while reading a book in playbooks, I notice that suddenly disappears one line and then appeared intermittently. I close the app and noticed the same thing happening on the screen menu. I shut down the cell and turn on again and I thought it must be an application be kidding. But still does.
2 Also yesterday I happened to change the security on the phone screen. After a while of normal operation, try to turn it on the screen with the button, nothing, the screen goes "black", with light and retrolight turned on but no picture no nothing .
Called the cell to see if it works or is turned off and the phone rings but the screen nothing. Try turning it off and on again by holding the on / off / lock button and the phone restarts, but the screen nothing. In one such attempt to do the above it is seen that managed to turn it off. And I get it on and do a normal boot, except that the picture of my screen is changed to the original. Change the lock screen which was previously using (slip). And it seemed that out or some conflict with the lock. In one of those again pressed the ON / OFF / lock as would normally and it starts all over again.
After I magically back to life, I want to make a full wipe as I think it should be an app that is doing some conflict or something. BUT ....
3I turn off the phone and then press the keys VOLUME UP / DOWN and ON / OFF is normally off, squeezed the first screen with the options but options RECOVERY / BOOTLOADER appears in red I choose RECOVERY give the ok with the key and .... andriod robot appears with the legend below that says something (I do not remember well) without or without controls options appears. So its seems thatI dont have recovery.
After that keep pressing the key ON / OFF and the phone turns off and / or reboot normally. All this I did it again to see if the error reappears and looks that I do not have recovery.
The failure of the screen is increasing. I dont know if they are separate problems or is it all the same problem.
Sorry if I was too long but I need the help of you.
UPDATE Now it seems that the screen died, since I do not achieve to turn it on as before, the light and the retrolight its ok. The phone receives calls and notifications but the screen stills black.
Thanks all.
Matias M 73

the android laying on its back IS the atock recovery.

simms22 said:
the android laying on its back IS the atock recovery.
Click to expand...
Click to collapse
thank you simms22 but I need to fix or understand what happend with the screen first.
:good::good:

Matias M 73 said:
thank you simms22 but I need to fix or understand what happend with the screen first.
:good::good:
Click to expand...
Click to collapse
sometimes things just "derp". itll happen more often if you dont reboot your phone often. also, your phone will be a little bit more responsive if it gets reboot once a day or two.

RMA or fastboot it back to stock, if the screen doesnt turn on afterwards then it looks like a hardware issue, open device and reconnect the display.

republicano said:
RMA or fastboot it back to stock, if the screen doesnt turn on afterwards then it looks like a hardware issue, open device and reconnect the display.
Click to expand...
Click to collapse
Thank you Republicano!!
I think too that its a hardware issue. I already see on you tube problems like mine.
Thanks again!!

Can't boot, restarts constantly

Bought a Nexus 5 about 6 months ago USED. It has been amazing. I got the latest OTA a week ago or so, not sure if that has anything to do with current issues.
About 2 days ago started randomly restarting. Today, it shut down and has been in continuous loop restarting. I see "Google" and maybe even the boot dots loading, then it is off. Three seconds later, starts again and repeats. Never makes it all the way into Android system. I let it sit for a while and when I pick it up, without touching any buttons, it repeats all of this. I suppose it is probably dead in general, but I don't know. Do you guys have any ideas? Again, I bought it used and from a ma/pap store who said they buy 100 in bulk, which made me skeptical, but they also had a 60 day guarantee and it was amazing the first 60 days and even after. It has been error free for 6 months, so I don't know if this is just a random issue or if the previous owner dropped it in a lake and I got lucky, or what. FWIW the damn thing has been in a case and never dropped, so it isn't anything that I have done I don't think. Thanks for any help.
edit: never rooted, never messed with, always been stock

Another user reported some instability since the last OTA update.
Flashing the full factory images did the trick.

a friend of mine gave me his nexus 5 to repair and its doing something similar. He had ir rooted and on latest 5.1.1 (i think). Either way, he said it was randomly locking up and rebooting. When i got it it had the red blinking light when plugged so i got a new battery. That got fixed but then the constant bootloop showed itself. I flashed TWRP (many versions, 2.6.3.1; 2.7.1.1; 2.8.7.1; the one that worked best was 2.7.1.1). So, once in twrp wiped, pushed cm 12 snapshot, flashed it, pushed gapps, falshed, pushe supersu flashed. Started the system. That precise order of things (ie: pushing flashing, then pushing something new and flashing it) was what gave me best results to actually boot up at least once. Once booted up and logging in and everything to cm i had some sort of stability (even rebooting and powering off) but i think that everything went wrong when i plugged the phone to the computer and it was back to bootloops and not even getting to the recovery. Flashed everything again. Didnt work. Had to leave the phone sit for a while (without the back casing) before trying again, in order, before getting any success. Im starting to think of ovrheating but it doesnt even get that hot...
Dunno if you guys have any ideas on this. Or if i can give you mor details to help us out.
Regards!

Looks like I'm having a similar problem to what is described here, as well as http://forum.xda-developers.com/google-nexus-5/help/bootlooped-dont-how-to-enable-debugging-t3215951
I've had one of my Nexus 5 phones running OmniROM 5.1.1 for some time now, very stably. After trying out the Marshmallow preview and going back to that ROM, I started having spontaneous hard reboots and hard crashes. The phone would often boot loop before even getting to the OmniROM boot animation. It was also very recalcitrant about entering and staying in the boot loader, rebooting spontaneously shortly after rendering the boot loader screen. I was occasionally able to "grab" control long enough to get it to boot into TWRP, from which a boot to Android seemed to usually get it out of the loop and into running Android.
I've flashed back the boot loader and baseband from factory-stock 5.1.1 LMY48M (HHZ12h and 2.0.50.2.26) using the flash-base.sh script from a freshly downloaded and extracted hammerhead-lmy48m. Things appeared to be OK last evening and this morning, but things got worse today.
Now the phone is in a state where it is not responsive to the power button when unplugged. I can hold it down for 30 seconds with no response.
If I plug in USB, it spontaneously starts rebooting, not showing more than about two seconds of the Google boot loader screen. If I hold the down-volume button, I can get the boot-loader screen, but no matter how fast I try to be, I can't select anything more than "Restart bootloader" (or "Power off") option before it spontaneously reboots (to boot loader).
As far as I know, the battery had a significant charge before this started happening.
I see the same behavior if the phone is connected to a USB charging source, rather than a USB port.
I've tried pulling the SIM, but that doesn't change the behavior.
adb wait-for-device never returns, so poking it over adb doesn't seem to be an option.
fastboot devices also doesn't see the phone, for the brief time the boot loader is running.
Any suggestions on how to get this into the boot loader so I can at least re-flash it?
Nexus 5 D820(E) 32 GB
Edit:
WaxLarry said:
In my opinion your problems seems power button's related.
Click to expand...
Click to collapse
Trying to see how I can "clean" or "clear" the power button now.
Edit:
Paul22000 said:
This morning my Nexus 5 was turned off all of a sudden after not having used it for 20-30 minutes. I held the power button and nothing. I plugged it into power and the "Google" screen appeared. It then went into a reboot loop on and off, on and off, on and off. I held the Volume Buttons and it went into fastboot, but then boot looped out again and again. Searching on Google yielded that this was indeed a common problem. [...]
Click to expand...
Click to collapse
Edit: Repeatedly pressing the power button seems to have temporarily allowed a boot to Android.
In retrospect, I had noticed over the last few days that the phone didn't seem to respond properly to the power button, either "ignoring" it, or when a second press got things started, it would unexpectedly come up with the long-press-volume menu.
One link on how to replace the power switch yourself is http://protyposis.net/blog/replacing-the-nexus-5-power-button/

Ok @jeffsf keep going on this thread. I had the same damn experience, that ended with RMA. LG said that the problem is related to some tension change in the power button. After the RMA I used the phone totally stock and never had a problem. Two months ago I switched to blu_spark kernel and some weeks after i noticed some problem. When I pressed the button to lock the screen, phone locked itself and then screen turned on, sometimes showing the shutdown option. So i understood that something was happening to the power button. I tried to overvolt with a +5mV on general offset and since then i never had problem. If you can enter recovery or bootloader i suggest you to flash some kernel with volt change support and then overvolt the general offset... and keep finger crossed

jeffsf said:
Looks like I'm having a similar problem to what is described here, as well as http://forum.xda-developers.com/google-nexus-5/help/bootlooped-dont-how-to-enable-debugging-t3215951
I've had one of my Nexus 5 phones running OmniROM 5.1.1 for some time now, very stably. After trying out the Marshmallow preview and going back to that ROM, I started having spontaneous hard reboots and hard crashes. The phone would often boot loop before even getting to the OmniROM boot animation. It was also very recalcitrant about entering and staying in the boot loader, rebooting spontaneously shortly after rendering the boot loader screen. I was occasionally able to "grab" control long enough to get it to boot into TWRP, from which a boot to Android seemed to usually get it out of the loop and into running Android.
I've flashed back the boot loader and baseband from factory-stock 5.1.1 LMY48M (HHZ12h and 2.0.50.2.26) using the flash-base.sh script from a freshly downloaded and extracted hammerhead-lmy48m. Things appeared to be OK last evening and this morning, but things got worse today.
Now the phone is in a state where it is not responsive to the power button when unplugged. I can hold it down for 30 seconds with no response.
If I plug in USB, it spontaneously starts rebooting, not showing more than about two seconds of the Google boot loader screen. If I hold the down-volume button, I can get the boot-loader screen, but no matter how fast I try to be, I can't select anything more than "Restart bootloader" (or "Power off") option before it spontaneously reboots (to boot loader).
As far as I know, the battery had a significant charge before this started happening.
I see the same behavior if the phone is connected to a USB charging source, rather than a USB port.
I've tried pulling the SIM, but that doesn't change the behavior.
adb wait-for-device never returns, so poking it over adb doesn't seem to be an option.
fastboot devices also doesn't see the phone, for the brief time the boot loader is running.
Any suggestions on how to get this into the boot loader so I can at least re-flash it?
Nexus 5 D820(E) 32 GB
Edit:
Trying to see how I can "clean" or "clear" the power button now.
Edit:
Edit: Repeatedly pressing the power button seems to have temporarily allowed a boot to Android.
In retrospect, I had noticed over the last few days that the phone didn't seem to respond properly to the power button, either "ignoring" it, or when a second press got things started, it would unexpectedly come up with the long-press-volume menu.
One link on how to replace the power switch yourself is http://protyposis.net/blog/replacing-the-nexus-5-power-button/
Click to expand...
Click to collapse
I got a notification for this post since you quoted me. I'm not sure if you're having the same problem but I'll tell you what happened to me, just in case. I called T-Mobile and they referred me to the nearest 3rd party phone repair shop. I went there and after an evaluation, the repairman told me the power button on my phone was indeed broken. They replaced it for $55.
The story doesn't end there though. I took my phone home and a few hours later I tried to use bluetooth and it didn't work. I took it back and found out that unfortunately, when the guy replaced the power button, he inadvertently broke the bluetooth. There's no way to fix bluetooth without replacing the motherboard entirely, which would cost $200. I'd rather buy a new phone at that point since my Nexus 5 was getting old. He refunded me, which was nice. At least the power button worked so I could use my phone. Bluetooth isn't as valuable as being able to you know, turn on the phone, so at least it was a net gain.
After that, I purchased a Nexus 6 and rooted it so I could use double-tap-to-wake (along with the automatic screen on when you pick up the Nexus 6). I also use the following app in order to turn off the screen by swiping up from the home button (I don't care about losing the shortcut to Google Now): Screen Off and Lock
I can now literally go weeks without using the power button on my Nexus 6. (I literally only use it when tap to wake sometimes becomes unresponsive which is rare.)
Bottom line: I will never buy another phone without tap to wake functionality! :good:

A local repair shop here indicated that one sometimes does changing the power switch resolve the issue. They have seen situations where the issue appears to be one of the power-management ICs. Just something to be aware of when examining the potential cost of a repair and who you would have do the work.

Question Z flip 3 bootloop

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.

Motorola XT1542 Weird brick, (Please help)

Due to some finantial plot twists in my life I've been forced to dust out my old Motorola G 3rd gen and use it as my main phone. A couple of days ago I followed a guide in how to unlock the bootloader and installed Lineage OS, everything was decently smooth, except by the fact that it didn't recognize my SIM card.
So as a troubleshooting step (And since I still didn't had anything important on my phone) I decided to reload a recovery image I had made with the original ROM.
And here is where the troube started. TWRP finished the restoration of the image and I told it to reboot the phone, now it has been stuck on the "Warning Bootloader Unlocked" Warning screen for the past hour or two. When I try to turn it off I hold the power button and 10 second later the screen goes off, but a few seconds later it turns back on and goes back into the warning screen.
When I plug it into my computer it isn't recognized and for some reason it doesn't allow me to enter the Bootloader (It might be worth noting that the volume down button hasn't worked very well for some years.)
So, it's not completely unresponsive, I have a screen and it recognizes button presses to some extent, but I can't do anything with it...
Is there any way I could fix it? I'll appreciate any help. (I don't care if I have to format the phone, I just need to fix it)

martiagosantinez said:
Due to some finantial plot twists in my life I've been forced to dust out my old Motorola G 3rd gen and use it as my main phone. A couple of days ago I followed a guide in how to unlock the bootloader and installed Lineage OS, everything was decently smooth, except by the fact that it didn't recognize my SIM card.
So as a troubleshooting step (And since I still didn't had anything important on my phone) I decided to reload a recovery image I had made with the original ROM.
And here is where the troube started. TWRP finished the restoration of the image and I told it to reboot the phone, now it has been stuck on the "Warning Bootloader Unlocked" Warning screen for the past hour or two. When I try to turn it off I hold the power button and 10 second later the screen goes off, but a few seconds later it turns back on and goes back into the warning screen.
When I plug it into my computer it isn't recognized and for some reason it doesn't allow me to enter the Bootloader (It might be worth noting that the volume down button hasn't worked very well for some years.)
So, it's not completely unresponsive, I have a screen and it recognizes button presses to some extent, but I can't do anything with it...
Is there any way I could fix it? I'll appreciate any help. (I don't care if I have to format the phone, I just need to fix it)
Click to expand...
Click to collapse
So I don't know if this is helpful in anyway, but I'll wait for it to run out of battery and then I'll try to plug it into the computer again, maybe that helps in any way?

I found this reddit thread
https://www.reddit.com/r/MotoG/comments/5iz8fz
Someone had the same issue (Or a very similar one) I had, but I don't know if OP figured out a way to fix it, or if he was able to get into the bootloader.

Update, the phone ran out of battery and it's shows the low battery screen when I try to turn it on, or when I try to enter Bootloader, it's still not recognized by my PC