Related
I've looked all over for the answer to this, and I've tried multiple things but nothing seems to be working. Last night my phone froze (for no apparent reason) so I pulled the battery. The first boot screen came and went but the 2nd doesn't show...it stays blank and then eventually I hear the noise my phone makes when it's fully started up, but the screen is still blank. I have to push menu and the home and call keys a couple of times to get the screen to turn on, and then I can see everything seems to be up in the background, but when I go to unlock my phone it doesn't recognize me pressing the buttons (to unlock the SIM) so I can't get any further. When I do home+power combination, the screen with the triangle and exclamation point comes up, but it won't recognize any of my button presses. I tried to use fastboot to bring it back, and it says everything went through but when it starts back up the same thing happens, it won't recognize me pressing the screen to unlock the phone. It will take maybe the first 2 keys I press..and it will lag while it takes them...but after that it doesn't take anything else. I don't know what to do so if anyone can help or might know what could have happened. Like I said, I was just on the browser last night looking around and it froze so I pulled the battery. Oh and I'm running JF 1.50 if that matters. Thanks guys.
Did you install hardSPL?
If not, maybe you can create a goldcard (search in this forum) and flash the basic system on it again!
I have the SPL for Sapphire ported to Dream.
I might have to take it in to T-Mobile because it boots up and just automatically freezes at the main screen.
The only thing I'm worried about is that I changed the first boot screen so if I do end up having to get a new phone I'm going to have to pay for it
wipe wipe wipe
no need to take it to t mob just wipe take the sd card put it in a sd card reader load up the root/hack rom and go from there no need to take it back cause t mob will tell hell no when they try ro boot it up
I don't know how to wipe it without going through the bootloader and that won't load up.
I also don't know how to flash an update without going through bootloader so I'm stuck.
try this
pull the battery hold down power + home put battery in without taking your fingers off thoses buttons wait till bootloader loads. it happent to me an endless loop everytime i pulled the battery it would power up without touching the battery so thats what i did
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
So heres the story....wife has had lg g2 since it came out with 0 issues. About 3 days ago the phone starts doing some crazy ****, flipping through screens by itself, opening and closing apps, deleting things, rebooting, changing system settings. This was after earlier in the day she had downloaded some random games for my son to play (not sure if this was the cause/is at all relevant, just trying to be as detailed as possible).
My first though was that one of the games may have had some virus/malware **** going on, so did a factory reset. The reset was successful, however the issues continued. Next though was to root/unlock/install custom rom. (I have done this to all my phones, with minimal issues, so i felt fairly confident in doing so) So i rooted, installed twrp 2.7.0.0, and flashed this rom - ATT-stock-rooted-D80020K.zip - and all seemed well. Phone booted and behaved normally for the rest of the day (12 hours or so). Plugged in charger, went to sleep.
Next morning, wake up, grab phone, and its showing the LG logo (like when you first power it on). Restart (power button long press) and it boots into TWRP, and i go looking for the rom file to reflash, and its gone. All files are gone. In the file explorer in TWRP, i can see the files,(data, system, boot, and so on) but when i click on them there in nothing in any folder. All downloads gone. Everything.
But i can still get into TWRP, so i thought ok, ill just plug into pc, mount the phone, copy appropriate files, reflash rom, and all will be good. WRONG. I cannot get TWRP to mount the phone, and at this point ive got a pretty expensive paperweight.
All my unlock/flash/root experience has been on HTC devices up to this point, and i have never had an issue like this.
If anybody can advise what to do next, Im listening. Ive exhausted my knowledge on the subject at this point and NEED HELP PLEASE.
Thanks in advance.
Hello all,
Today my Verizon S6 (on CleanRom 1.5) started to keep rebooting. After it boots, I can use the phone for less than a minute until it reboots again.
Here's how it began to happen today, if it helps.
- I didn't plug my phone to a charger last night, and when I woke up the phone had like 0%~1% battery. The phone died soon after I picked up the phone.
- At the same time I turned on the phone, I connected it to the stock charger.
- I used it for like 1-2 minutes, and the phone seemed to get confused whether it should die again or not (at 0% battery level)
- Then the phone decided to die again, and keeps rebooting itself.
My guess is something related to booting, initializing, or battery might have gone wrong. Also the soft button lights get never turn on.
Now I cannot use the phone really, as it dies like 30 seconds after I swipe the lockscreen.
- I tried to boot into safe mode, it didn't help.
- I wiped cache partition, it didn't help either.
The last thing I would like to try is to odin CleanRom again (or factory reset) but I would like to try other things first because I cannot even backup the data as it keeps rebooting. Odin will wipe all the data in my phone.
Any help or suggestions guys?
mtshure said:
Hello all,
Today my Verizon S6 (on CleanRom 1.5) started to keep rebooting. After it boots, I can use the phone for less than a minute until it reboots again.
Here's how it began to happen today, if it helps.
- I didn't plug my phone to a charger last night, and when I woke up the phone had like 0%~1% battery. The phone died soon after I picked up the phone.
- At the same time I turned on the phone, I connected it to the stock charger.
- I used it for like 1-2 minutes, and the phone seemed to get confused whether it should die again or not (at 0% battery level)
- Then the phone decided to die again, and keeps rebooting itself.
My guess is something related to booting, initializing, or battery might have gone wrong. Also the soft button lights get never turn on.
Now I cannot use the phone really, as it dies like 30 seconds after I swipe the lockscreen.
- I tried to boot into safe mode, it didn't help.
- I wiped cache partition, it didn't help either.
The last thing I would like to try is to odin CleanRom again (or factory reset) but I would like to try other things first because I cannot even backup the data as it keeps rebooting. Odin will wipe all the data in my phone.
Any help or suggestions guys?
Click to expand...
Click to collapse
The OE2 tar file shouldn't wipe your phone as it is not a full wipe tar. I don't know if your phone would do it with it's reboot problem but a dirty flash of clean rom shouldn't wipe your phone either. However, a reboot during the middle of either of those would not be good. Flashfire does seem to be able to keep a phone from rebooting once it gets going or at least it has for me when I have been caught in a bad way before.
Problem Solved!!!
Thank you Tulsadiver for your suggestions. But is it okay to do odin without wiping anything?
I almost gave up after struggling several hours and thought about doing a factory reset, but the problem is solved now.
I found it weird that the soft key lights never turn on, so I thought that there might have been something wrong with the power management. So I turned the ultra power saving mode on (fortunately the phone didn't reboot before I did that), and it didn't reboot itself. I turned it back off then now the problem is gone!
I am happy with it now, and this might be one of the things to try if you experience a random reboot.
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.