Develop Bugs

[Q] Problems after restoring in Clockworkmod

Hello, this is kind of a long story but.......I was in clockworkmod recovery looking to restore back to a backed up rom. I saw a backup titled, 2000-01-01.00.00.16/. I didn't remember a backup that had that named and it said it was from the year 2000. Out of curiosity I decided to backup to it. Then It got stuck or what appeared to be stuck on "checking md5 sum". After ten minutes I pulled the battery thinking it hadn't even started restoring. When I put the battery back in I got the charging battery icon with a cloud and a thermometer, assuming this meant that the phone was to hot I felt the back and it wasn't hot at all. I tried to power the phone off but each time I turned it back on I got the same icon. Finally I tried plugging it in. Then the icon went away and the booted into clockworkmod. So then I restored to the Unnamed rom and the led notification light wouldn't go off. Then every time I turn the phone off I get the thermometer icon and have to plug it in. On top of that my computer won't recognize the phone. I want to use Odin to go back to stock but since the computer won't recognize it I'm stuck with a phone full of problems. Any suggestion?

First backups can't contains signs /&%*+# etc...
Second.. can you get to recovery?
Sent from my SPH-D710 using XDA Premium App

omg .. i THINK YOU BRICKED YOUR PHONE!!
But not to worry, most likely it's an easy fix. Reboot phone a couple times, MAKE SURE DRIVERS & EVERYTHING are INSTALLED FIRST, open ODIN with proper .TAR file, .PIT NOT needed. Only Auto Reboot box should be checked, then plug in to pc. Wait for phone to connect and hit start. BE PATIENT. If it doesn't work try booting into CMW, holding POWER and VOL UP buttons. Hope this helps!

Thanks everyone for the help. I ended up downloading mobile odin from the market, and then flashing the stock unrooted EK02.tar file. I still had the same problems and figured it was a hardware problem. So I took it into my local sprint store and they took one look and it and ordered me knew for free, no questions asked!

[Q] I need immediate help!

Hi, well I learned about rooting about 4 months ago. Last week I rooted my phone, everything was ok.
So, last night I was bored and saw a video about illusion rom, so I went to the thread (on this page) and downloaded it. I opened clockwork mod recovery app and it said something about flashing and installing the mod. It said it was going to reboot. Well, it rebooted and it got installed. But when I rebooted my phone again like a triangle non-stop aurora just keep going, not even the normal 'samsung' would appear so, I took out the battery and plugged my charger then I noticed something. Instead of the old battery indicator I had the new one, (black and grey) so I thought I managed to do it. Then I unplugged my phone and it won't boot. Well, it only did once it just went to the Samsung logo and turned off. Can you tell me how to fix this?
Oh yeah, I cleared cache,data, Davlik (something like that) and wiped all the data from the phone.
(I can go to download mode too) what i do wrong, can I fix it? Thanks.

You need to fully wipe the phone factory reset/data then install rom > then gapps > then reboot let it sit for 5 minutes at least. To boot into recovery hold volume UP & home & power. Search a little more next time dude, would have saved you the headache probably. I have a pretty basic easy to fallow install guide in my q&a http://forum.xda-developers.com/showthread.php?t=2106546 for that rom specifically and there is this http://forum.xda-developers.com/showthread.php?t=1946701
Also your battery sounds low, just let it charge for 20 minutes unplug the phone and then power on if that happens again.

Phone model? Can you boot into recovery (CWM)?
|When Emotion Goes Up, Logic Goes Down|

mt3g said:
You need to fully wipe the phone factory reset/data then install rom > then gapps > then reboot let it sit for 5 minutes at least. To boot into recovery hold volume UP & home & power. Search a little more next time dude, would have saved you the headache probably. I have a pretty basic easy to fallow install guide in my q&a http://forum.xda-developers.com/showthread.php?t=2106546 for that rom specifically and there is this http://forum.xda-developers.com/showthread.php?t=1946701
Also your battery sounds low, just let it charge for 20 minutes unplug the phone and then power on if that happens again.
Click to expand...
Click to collapse
I'm going to try it tomorrow morning. I already factory reseted like 2 hours ago. Do I do it again (? Thanks for the help

read the links I posted. Either or will do fine.

I hope he did backup

[Q] Restored backup from TWRP locks up, reboots

I had Android 4.1.1 installed on a rooted Sprint Galaxy S3 with ClockworkMod. Someone recommended TWRP, so I installed it and used the backup feature, thinking I was completely covered if my foray into ROM flashing on the SGS3 went awry.
So I booted to TWRP, did a "Wipe Data/Factory Reset", and installed the "Blazer" ROM; didn't like it. So I TWRP'ed again, wiped it and flashed CyanogenMod 10.1. Didn't like it either. So I went back into TWRP, did the "Wipe Data/Factory Reset" again, and restored my backup.
When it finished rebooting, it was good for like 20 seconds. I left it on the "lock" screen, and the date reverted back to Dec 24th at some ungodly hour (4 am?). It wouldn't unlock. After less than a minute, it reboots. It kept doing this.
I had a hard time getting back *into* TWRP. I kept getting this weird picture of the battery (?) and the phone kept buzzing every 10 seconds or so. The battery had at least 30% charge. Eventually, by taking the battery out, I was able to get back into TWRP.
Tried it again 2 or 3 more times with the same result. This last time, I immediately got off the lock screen and let it "sit". It has been stable for 10 hours now.
Any idea what's going on?
(If I'm leaving out important information, I apologize. Please let me know and I'll add it.)

Something wrong happened in the restore process. Just make sure that you have at least 80% battery next time.
Sent from my SPH-L710

Thanks.
If I keep restoring it over and over again, is there a chance it will "take" one of these times?

Ok so, check the size of your backups and make sure that they are consistent (for the same ROM types)
I've seen an issue where someones recovery got corrupted, and all restores made with the corrupted recovery were unnaturally small and would bootloop once done restoring
Reflashing your recovery (i recommend through ODIN from a PC) should fix it if this is the issue

[Q] JellyTime gets stuck on bootanimation

Hi, I have been running JellyTime 4.2 R11 for few weeks now on my S-OFF Desire HD.
Today, I noticed that the light was blinking and battery was low 6%, so I decided to put it into charger, and somehow when I connected it soon I accidently disconnected the charger, and when I put it back, the phone probably crashed or something, since it went black and the white screen with HTC logo appeared and it started to boot again. Now, JellyTime tries to boot, the bootanimation goes fine for sometime but then it gets stuck after "playing" the bootanimation for a while, nothing happens, even if I wait 5 minutes, it's stuck, bootanimation is frozen, no matter do I have the charger connected or not.
So, is there anything I could do, or is reflashing the only solution? I did full wipe when I flashed the ROM.
If you need more information, sure, just ask.

You could try dirty flashing, but if that doesn't work you'll have to reflash.

bananagranola said:
You could try dirty flashing, but if that doesn't work you'll have to reflash.
Click to expand...
Click to collapse
Thanks for the tip, but it didn't help, gets stuck still on bootanimation.
Time to full wipe and flash it again then. Wipe&FlashTime

Happened to me a few times. I suggest a battery pull before anything else. Seems stupid. But it can work in some cases
- Sent from Guy's Super Duper S3

GuyInTheCorner said:
Happened to me a few times. I suggest a battery pull before anything else. Seems stupid. But it can work in some cases
- Sent from Guy's Super Duper S3
Click to expand...
Click to collapse
I did battery pull several times considering that the phone refused to shutdown even when holding the power button for 10 secs, so battery pull was needed every time.
Anyway, it's now running fine when I reflashed.

910263 said:
Hi, I have been running JellyTime 4.2 R11 for few weeks now on my S-OFF Desire HD.
Today, I noticed that the light was blinking and battery was low 6%, so I decided to put it into charger, and somehow when I connected it soon I accidently disconnected the charger, and when I put it back, the phone probably crashed or something, since it went black and the white screen with HTC logo appeared and it started to boot again. Now, JellyTime tries to boot, the bootanimation goes fine for sometime but then it gets stuck after "playing" the bootanimation for a while, nothing happens, even if I wait 5 minutes, it's stuck, bootanimation is frozen, no matter do I have the charger connected or not.
So, is there anything I could do, or is reflashing the only solution? I did full wipe when I flashed the ROM.
If you need more information, sure, just ask.
Click to expand...
Click to collapse
I have the same problem since a crash on opening the outlook-email App (JellyTime 4.2 R9).
I found, that the "data" partition causes the trouble when booting. Formating the "data" partition with "4ext recovery" fixes boot-freezing. But this is not an option for me as my last (working) backup is a couple of months ago (yes, I know - should backup more frequently...).
I was able to backup the up-to-date "data" partition (with 4ext recovery) but when restoring it (even on an fully wiped and updated system) boot sequence freezes again.
Any ideas???
Many thanks!

Solved the problem with the data-backup. Instead of restoring complete partition the APP "AppExtractor" works fine for restoring data of the partition backuped.
For now, system runs perfectly.
Conclusion:
If system hangs in Boot-Animation use Recovery for backup of up-to-date system. Full wipe system and install ROM of your choise. After that restore SMS, contacts, etc. with "AppExtractor". Apps should be installed from PlayStore as far as possible. "AppExtractor" allows restoring of app, data+app, data.

Replaced LCD Display... Now Phone Will Only Boot Loop... Help!

A few months ago, the display broke on my Moto Z Play. It took me awhile, but I finally got a replacement display.
During the time I was not using it (starting immediately after it broke) it would make the sounds for my calendar notifications as they would come up, and continued to do so until the battery died.
While the battery was dead, I carefully took off the remnants of the old broken LCD.
About two weeks before I got the new display, I plugged it into my computer to see if I could pull any of my information off of it. Unfortunately, I was unable to get it to show up as a drive on my computer so I couldn't pull anything off of it.
Since it had power, it once again made sounds for my calendar notifications until the battery died.
I got my new display in the mail a couple days ago. I set about installing it and after I was done, I charged the battery to 96%. The charging screen appeared perfectly normal. I had no indication that there was going to be any problem when I went to use it until I powered it on at 96%. It looked like it was going to boot up just fine and made it three screens (not counting the triangle screen) into the boot up process and restarted the process.
The last time the phone was fully functional (as well as while it was on with a broken LCD) it was running OmniROM and it has TWRP 3.2.1-0 recovery on it.
First I tried clearing the cache and dalvik cache. That didn't help. Then, as I keep a copy of the zip for that ROM on my SD card, I decided to reflash OmniROM and 8.1 gapps. That didn't help. So, I decided to do a nandroid backup. It got part of the way through the back up and failed at system image. So, I decided to try to backup my data so that I can at least hopefully restore some of it at a later date on my computer or something. Thankfully, I was able to successfully backup my data partition.
After the backup finished, I decided to attempt to dirty flash CosmicOS.
However, I experienced the same boot loop.
I then did a full wipe and did a clean flash of OmniROM.
Still: the triangle screen, 3 seconds of the boot process and then it starts over again.
I am lost as to what to do now.
Help!

Hello?...