So I tried to restore my previous ROM after giving another a try and it all fails. I wiped data/delvik/swap and then restored to the latest stored image. Phone starts to boot and then just freezes. I let it sit for about 8-10 minutes (phone usually takes a minute at most to boot) and then just did a hard reset by taking the battery out. I thought maybe the last file was corrupt so I removed the latest image and restored an older one. STILL no go. Freeze right at the second splash screen. Did I do something wrong? I have done this before and it worked fine. Im lost.
Hmmm anyone have an answer to this?
what rom is it and is the phone rooted?
The phone is Rooted and at that time I was on Kings Eris 2.1 sense ROM. Do you need a special ROM?
Related
WHAT I DID:
From stock ROM, albeit rooted -
opened ROM Manager
chose to download CM7rc2, also ticked Google bundle
allowed it to do its thing
Could not log into Google account, same as with CM6 - why does it hate me?
decided to flash back to previous backup
it goes OK, BUT:
"Restoring boot image..."
"Restoring system..."
"Restoring data..."
dalvik-cache
^^^ wtf is that?
it's stuck on "dalvik-cache" forever.
Pulled battery, tried again, same result.
Pulled battery again, tried to reflash older backup. BOOT LOOP.
So now I have a phone that isn't exactly bricked, but is unusable. I suspect there's a way to recover this, but I have no idea how to go about it. Help?
I almost see why no one else is helping. I surely posted in the last thread you had about the same thing. Your list never once mentioned a full wipe before installing CM7 over stock.
Sent from my CM7 powered G2
I've spent close to most a work day now searching for an answer but am stumped.
I'm on MDL.
Downloade and flashed latest version of Goldeneye. Works great. After a bit, went to reboot phone.
Phone stuck @ boot screen ("Samsung" w/ unlocked lock below).
pull battery, same screen.
Wipe/reflash - all is well. Then re-boot, and stuck at same screen.
I have tried restoring multiple Nandroids and loaded 2 differnet roms. All with same result.
Also tried wiping data and restoring ESF backup and restoring my first rooted stock backup.
Same issue. works great till I reboot. Obviously somehting isn't sticking.
Any ideas? I hope I gave enough info
what recovery are you using?
The last few days I had an experience that I want to share. Maybe it helps somebody else.
Last week I upgraded my Defy from Quarx's CM10.2 to CM11 version 20140724.
It ran for about two days. It was stable and the performance looked better than before.
Then, when I was outside, my battery was empty. I always have another battery with me, so I exchanged the battery.
Then, two seconds after I inserted the battery, a black screen with the following white text appeared spontaneously, without pressing a button:
Bootloader
09.10
Code Corrupt
Ready to Program
connect USB
I could not enter recovery, or anything else.
So, I decided to go back and flash the original Motorola Android 2.2 version.
On earlier occasions this worked perfectly when I bricked my phone, but this time, after flashing the SBF with RSDlite, the phone hang while booting with the android logo on the screen. Only after a few hours of trying different SBF systems, the idea popped up, that the problem was not in the SBF, but in the combination of the old Motorola system and the new CM11 data partition. So, I entered recovery and wiped the data partition.
Then the system booted normally and I could proceed with rooting the system, installing custom recovery and restoring the backup.
Everything is back to normal again.
Now, I wonder what could have caused this problem.
I am a bit suspicious about the backup method I used. I create backups with the online nandroid app. The CM11 system installed the TWRP 2.7 recovery. The first time I tried to restore a backup, I noticed that the TWRP recovery had a problem with the old (CM10) and the new (CM11) backups, because they contained files for partitions and-sec and recovery, that it could not handle. In later attempts to restore the backup I unticked these partitions and the restore seemed to work well. I rebooted it several times. Could it be that these attempts damaged the system in such a way, that only when inserting a battery, the corruption was detected?
Or should I assume that there was a hardware glitch when the battery was replaced?
F.Zwarts said:
.
Then, when I was outside, my battery was empty.
Click to expand...
Click to collapse
iirc this was one of the bugs of cm11. if you let the battery runs completely down, it may not boot again. not sure if this has been fixed with the latest cm11.
This is my wifes phone, who has always refused to have her phone altered in any way. Today, it started getting hung on the yellow sprint screen. A couple of times, another reboot would get past it. But now it's stuck for good.
She has some pics and thousands of contacts and SMS messages on it that she doesn't want to loose, so kind of afraid to do a factory reset or odin a fresh ROM. I don't know if she allowed it to take the latest firmware updates, so I don't know for sure what version is on it.
Can I odin CWM or TWRP only so that I can do a nandroid backup?
Once I know all the data is backed up, I can try the factory reset and/or odin rooted stock rom and use titanium backup to restore data.
Thanks
I don't know the answer but in my head I'd think you would have to have a working rom to back up in the first place. Maybe she ran out of memory? Flashing the stock Rom won't delete anything. Just did that a few days ago.
I went ahead and flashed CWM and did a nandroid backup. I used my other phone to look at the backup with Titanium Backup.
It looks like I will be able restore contacts and other apps/data. Not sure which item in the backup is for SMS history. In TB, I see a line that says "Messaging" and "Messaging+" and i don't see "com.adroid.providers.telephone".
I know the SMS's are in the backup, I extracted the tars in linux and see the folder /data/data/com.android.providers.telephony/
Used odin to flash the pre-rooted OD2 lollipop. It stayed on the yellow screen for several minutes, but I did notice that it played the full boot tune, which it hadn't been before. After a few minutes, it finished booting and started the setup wizard!
I upgraded to Nightly 20160107 today through a notification on my S4. After the upgrade, I noticed that the phone was not working right. A number of apps were missing and the camera was not responding, etc. I quickly went to Recovery and chose Restore. But I did not wipe before I pressed on the Restore Button. The process hung and did not advance after 10 MB of 5600 MB. After a fairly longtime, I removed the battery and after I reinserted, the phone hung on the boot screen showing SAMSUNG GALAXY S4. I have tried removing and reinserting the battery several times but got the same result.
Can somebody help me please?
Try to flash stock rom with odin http://www.sammobile.com/
Try a full wipe before restoring.
Normally, when you restore something, it automatically wipes.
But yeah, since the restore didn't complete you messed up the OS. In other words there is no OS to boot in. So I'd suggest flashing a rom. Any rom should do.