I had initially flashed JellyBomb Domination, but it ran worse then I had it setup prior to flashing it. So when I reverted to a Nandroid backup, I noticed that I have some...skewed charging animation still in place. It has the menu keys like TWRP, but a blue icon reminiscent of JBD...
Did a factory reset in TWRP, and reverted to my backup. Still present. Deleted the JBD 2.0.1 .Zip, and still present.
How did this happen? why is it still present?
See photo.
What what what???
Bump.
Sent from my SM-N900P using xda app-developers app
Related
I was flashing a circular battery icon for the notification bar and when I reset the phone in clockwork it won't move past the load screen. I've removed the battery and tried to reset into hboot (holding volume down and power button when turned off). Did I brick my phone?
Did you make a backup? If so restore it. Otherwise you may have to go a factory reset from clockwork.
Sent from my cm7 Aria using XDA App
Yeah thanks man. I couldn't even get clockwork to load up, but I finally did. Luckily I did a nandroid backup!
drblack2013 said:
Yeah thanks man. I couldn't even get clockwork to load up, but I finally did. Luckily I did a nandroid backup!
Click to expand...
Click to collapse
Lol good thing.
I've been doing weekly backups and saving them on my external hdd
Sent from my Liberty using Tapatalk
Decided I better ask for help before digging a deeper hole...
I had rooted my Vibrant around September 2010 and tried some ROM at the time, don't remember which one. I didn't keep it for very long...I accepted one or two stock OTA updates thereafter, ending up with 2.1-update1/KA6.
Fast forward to yesterday, when I decided to try to go to Gingerbread so as to be able to install an app I wanted. I chose CM7.2. I presumed I wasn't rooted anymore after the OTA's, so used CWM to run the update.zip that I still had on the SD card from 2010. I did a Titanium backup. I started following the abbreviated directions, then went to the full directions here:http://wiki.cyanogenmod.com/wiki/Samsung_Vibrant:_Full_Update_Guide
So I actually made two nandroid backups as a result of switching between the two sets of directions and getting distracted after I made the first one.
All went well, except after CM7.2 was booted and everything restored from Titanium, I had the following issues:
1. Messaging was broken
2. Most contacts were missing
3. GPS wouldn't lock
I poked around for fixes and tried some, but it was not looking promising. I decided I didn't really need that new app after all, and today tried to revert to stock. I supposed it would be a simple matter of a nandroid restore followed by a Titanium restore. Unfortunately the nandroid restore failed.
Research revealed this is a known issue with "different hboots".
I then compounded the issue by accidentally pressing the power button while in Recovery. The phone rebooted but stuck on the "Vibrant" splash screen, because of the corrupted restore attempt. No amount of 3-button resets got me back to Recovery. The phone is now connected to my laptop in Download mode.
I think what I now need to do is odin, per http://forum.xda-developers.com/showthread.php?p=13132341#post13132341
I will then be able to do a nandroid restore and Titanium restore and be back where I started? Any additional hints, warnings, etc?
Thanks in advance.
Be careful about what you backup with Titanium on stock and then restore on CM. Did you backup your Messaging app or any system data? If you restored system apps or data from a TI backup onto CM from stock, that could cause issues.
And about the contacts, where did you store them before? On Google, SIM, or in memory?
I may have clicked, in Titanium, "restore app and data" rather than just "data" for the messaging app. Thinking that may have been the case, I thought that reinstalling the ROM or Google apps zip files might fix it. It didn't. (this was before I soft-bricked)
Since I needed a working phone this afternoon, I went ahead and did the Odin thing. That went well. I am back to JFD and my contacts are back.
If I do a nandroid restore now, followed by a Titanium restore, it should get me back to where I was before starting the move to CM7.2, right? Except I would still have a JFD radio? (because nandroid does not touch that, as I recall)
In that case, finding a KA6 to install with odin would be best? And would there be any point to the nandroid restore if I did that?
GPS took a very long time to lock after going back to JFD, too. I think perhaps I need to try the antenna fix.
Maybe I will give CM7.2 another go...
m3rb said:
I may have clicked, in Titanium, "restore app and data" rather than just "data" for the messaging app. Thinking that may have been the case, I thought that reinstalling the ROM or Google apps zip files might fix it. It didn't. (this was before I soft-bricked)
Since I needed a working phone this afternoon, I went ahead and did the Odin thing. That went well. I am back to JFD and my contacts are back.
If I do a nandroid restore now, followed by a Titanium restore, it should get me back to where I was before starting the move to CM7.2, right? Except I would still have a JFD radio? (because nandroid does not touch that, as I recall)
In that case, finding a KA6 to install with odin would be best? And would there be any point to the nandroid restore if I did that?
GPS took a very long time to lock after going back to JFD, too. I think perhaps I need to try the antenna fix.
Maybe I will give CM7.2 another go...
Click to expand...
Click to collapse
If you do a nandroid restore you don't need to do a TI restore as nandroid will restore all your apps and data. (Even down to which wallpaper you're using and Wifi networks)
If the KA6 modem works best for you then go for it.
Where you rooted before you flashed the CWM update.zip? I didn't see that you were...
Sent from my SGH-T959 using xda app-developers app
whatiznt said:
Where you rooted before you flashed the CWM update.zip? I didn't see that you were...
Sent from my SGH-T959 using xda app-developers app
Click to expand...
Click to collapse
You don't need to be rooted, you just need a way to install. For example when you install from stock, you don't need to root it, only flash the custom kernel that has CWM, and then flash, since root is a state of the ROM.
Sent from my SGH-T959 using xda premium
Huh. Always thought you needed root to flash CWM.
Sent from my SGH-T959 using xda app-developers app
whatiznt said:
Huh. Always thought you needed root to flash CWM.
Sent from my SGH-T959 using xda app-developers app
Click to expand...
Click to collapse
Well, in our case we can use download mode + heimdall to flash a kernel that has the CWM recovery included.
Sent from my SGH-T959 using xda premium
...and now my phone works except the screen never turns on.
I remember exactly what I changed, I backed up /system/bin/samsungani and tried replacing it (stupid, I know, I didn't think I'd get a pseudo softbrick).
It's fully operational except I can't see anything.
Are there no options besides reflashing a rom?
If you did a nandroid backup then you can just restore back.
But incase you cant see the screen in recovery then your only option is to reflash through odin.
Sent from my GT-I9300 using xda premium
I tried flashing the Droid DNA Cubed Kernel 2.4.2, but forgot to flash the modules before rebooting. When the phone loaded up, all I got was a black screen with a title bar that would restart when I tried to unlock. I then restarted, flashed the modules, and I continued to get the same black screen. I even tried flashing back to the stock kernel with no luck. The only thing that fixed it was doing a factory reset. I had rooted stock with an unlocked bootloader. I didn't see mention of a required factory reset, so what went wrong? Thanks.
I'm not sure what went wrong, and factory reset is not required.
How did you flash the kernel?
I flashed the boot.img from fastboot, then installed the modules in TWRP after the blackscreen.
StormChaser46 said:
I flashed the boot.img from fastboot, then installed the modules in TWRP after the blackscreen.
Click to expand...
Click to collapse
That's normally what I do but I flash the modules before booting, which is how it should be done.
Exact same thing happened to me. I did the factory reset and started from the beginning again. It really scared me but now I have actual root access with superSU having no issues. So much happier now.
Anyways, the point is. If you mess that step up, just factory restore and do it again... The right way lol
Sent from my HTC6435LVW using xda app-developers app
Just flashed back to stock kernel from Flash Image GUI because I kept getting crashes/restarts on cubed, and no black screen this time. Not sure what the problem was, just hope it doesn't happen again lol.
StormChaser46 said:
Just flashed back to stock kernel from Flash Image GUI because I kept getting crashes/restarts on cubed, and no black screen this time. Not sure what the problem was, just hope it doesn't happen again lol.
Click to expand...
Click to collapse
So you did a factory reset and tried cubed again but still didn't work?
It did work after a factory reset, but I got crashes/reboots out of nowhere. I saw other people were also reporting occasional crashing, so I'll stick with stock til it's a little more stable.
Understandable, I get a random hangups every other day or so and it restarts... But the pro's outweigh the cons imo. But I agree with you as well .
Coming from a DX, I got used to random reboots here and there after rooting hahah
Sent from my HTC6435LVW using xda app-developers app
Hey All-
I cracked my N4 screen for the 3rd time and am using a buddy's Atrix 4g with firmware 4.15(ish) as a loaner... Here's my deal- I used the auto rooter/CWM-installer (I think it installed CWM 4.0.0.2. Everything went fine- it was rooted and fully functional. I should have updated the recovery, but anyway....
I made a backup in CWM recovery and I decided to flash epinter's CM10.1 zip file. I don't know if there is something I missed, but I wiped everything and installed... But it 'installed' wayyyy too fast- it looks like the CWM version I have installed the zip as an update or something, and of course, when I rebooted the phone, nothing happened for about 5 seconds- it just stayed on the unlock/dual core logo screen. But then the screen sort of zoomed in and distorted/it looks like there is a reflection of the dual-core/unlocked logo.. Kind of hard to explain. But it's frozen in place. Nothing happens.
So I reinstalled my backup- it takes a while to install as it should, but when I reboot, the same thing happens- it looks like it's going to boot, and then the screen just distorts and stays that way.... What on earth would make my backup not work??
All that said, I can still access CWM recovery.
Any thoughts on where I should go from here?
Zac
Update your recovery to cwm 5.0.2.x
Sent from my MB860 using xda app-developers app
What would be the best way to do that?
Download img, flash via fastboot. Done.