I don't know anything about the scripts in the clockworkmods but isn't the backup and restore supposed to make an exact image and then be able to put it back the same way? So if your phone is able to boot fine through power cycles, reboots, whatever, then it should also be able to boot when that same setup is restored through clockwork.
I am asking this here so as not to get flamed in the CM9 thread. But it seems something as simple as adding a theme to CM9 stock causes the backup and restore process to fail when restoring a this setup ending in boot loops. I have never had this problem with CWM 5.0.2.7 MTD so was wondering if there is something different in the scripts between the 2 CWM versions.
Can a DEV please help me to understand what is going on? Is it something being looked at? I know there are more important things on the plate but was hoping that it is at least known and somewhere on the agenda list.
Thanks for all the awesome work on CM9 and all the CWM versions to the DEV team.
Kenny, it might have to do with a boot sequence loop problem. Meaning, it might need some extra code in the boot sequence
Sent from my SPH-D700 using xda premium
I was trying to back up data and wipe the cache and I keep ferrying this message. Can anyone help?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my EPIC 4G running ICS CM9 MTD using Tapatalk
Cartmanz, your question was answered in your thread. Don't use ROM Manager without setting it up properly.
As to the original question, the CM9 team got back to me and said I had to pull a logcat during the boot sequence. I googled that and it has to be done with adb while it is bootlooping. I will attempt this today. The CM9 team is awesome. We both agreed this is a low priority but something to be looked at down the road.
Related
...and it's saying that I need to flash CWM first before I can do anything, but already have CWM 3.0.0.6 running. If I select flash CWM within Rom Manager, will it adversely affect anything? Will I need to flash a rom again after flashing CWM (again) in order to use my phone?
ROM manager doesnt work properly with Epic right now. You'll cause yourself a lot of headaches if you try to use it
Dubar said:
ROM manager doesnt work properly with Epic right now. You'll cause yourself a lot of headaches if you try to use it
Click to expand...
Click to collapse
ahh...thank you for the advice
Just reading the title and you know this can get bad fast
I use ROM MANAGER on the Epic, I haven't had any major problems with it, except it doesn't like to quick boot on a few roms without a little extra push. Any way, it isn't really a necessity unless you get the paid app, you can do everything easier (and on the epic, sometimes quicker) in CWM.
kennyglass123 said:
Just reading the title and you know this can get bad fast
Click to expand...
Click to collapse
Exactly.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have never used rom manager. Everything I do is through odin or clockwork
Sent from my SPH-D700 using XDA Premium App
Rom Manager doesn't help me in any way that CWM can't, plus it generally wants to install its own problematic version of CWM... If you make multiple Nandroid backups with clockwork, then you can rename their directories to whatever you choose, just make sure there's no space in the name (i.e. try something like Nandroid_Backup-1).
hey guys i just recently switched from fresh to myn's warm and am liking it much better anyways, through all of the customization you can do, ive hit a bump. most people have had this same problem, as ive read, but ive only come up with temporary solutions and not something permanent. it seems like when i try to manually flash something via clockwork, a specific file such as the circle battery in the notification bar linked on myn's page, the phone gets stuck on the warm loading screen after a reboot saying "please wait while strting up.." or something like that. I KNOW HOW TO FIX IT SO PLEASE DONT POST AND TELL ME TO REFLASH. i just want to know which files specifically i need to avoid from flashing so this doesnt happen again, and why it does this with some and not others. theres a reason i just cant find it :/. help?
Before you flash anything... You always have to wipe. Even if your flashing a mod for a custom rom , always WIPE!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
you have to do a factory reset for a simple flip clock?
Always wipe dalvik and cache before mods.
I would flash any mod from recovery and wipe cache and dalvik cache first . Also I would switch to ra Amon recovery I had all kind of problems with cwm and I've never had one with ra just my opinion though.
Sent from my PC36100 using XDA App
I had a lot of weird things happen before i switched to AmonRA.
im actually in the process of switching over to amon ra and trying that out. like u said...to many problems with cwm. also when i try to flash some mods it aborts and gives me a script error because of clockwork. yet another reason why im gonna switch.
Hello Everybody, I pretty sure you will sugess me something ... this community all peoples very smart! I bout recently EVO 4G sprint looks like it was used with Cricket. First day when I've receive it I just decide to reset it to factory default and probably it was my mistake .... this is how I did it
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
it look like it was restoring original google files and after restore it become like this
now I dont know what to do ... how do I restore it ....
please help me!
i see that community peoples are very useful I just google it and restore Sandwich 4.0.4, look very good! but animation pretty slow performance ...
First off, thanks for giving us more than an hour to respond. If you want speedy service, go to McDonald's.
Second, you did it all wrong. You should have just run an RUU. Restoring a Google profile in recovery should never be used, as it never works correctly.
No need to be brash. But next time give us some time to check threads. Sometimes I have to wait days.
System reset only wipes data. The original ROM is still in tact. You would have to flash a different ROM after you perform a system reset and wiping everything but stats, sd card, and rotation settings.
Sent from my PC36100 using xda premium
sitlet said:
First off, thanks for giving us more than an hour to respond. If you want speedy service, go to McDonald's.
Second, you did it all wrong. You should have just run an RUU. Restoring a Google profile in recovery should never be used, as it never works correctly.
Click to expand...
Click to collapse
I think he means the proprietary files? And if I remember right a RUU removes root?
Sent from my PC36100 using xda premium
Hello folks. So yesterday I was tinkering around with my phone in an attempt to load the jelly bean ROM. I am new to the world of ROM's and things, so I made sure I did my research before going into the new ROM. I got everything backed up (so I thought), and flashed the jelly bean ROM. The screen just sat there doing nothing until I got rid of it and restored my backup from CWM.
Now every time I boot, I get a screen that says "Unfortunately, Factory Test has stopped" and it cancels out wifi and I have no lock screen/power off menu. I found a solution on XDA that said to look in the EFS file for a certain folder, but when I went into my /efs folder, this is what I saw.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So there is nothing in my EFS file unless I'm reading this wrong. And I was stupid enough to save my original absolutely clean version from EFS Pro on the internal memory which I wiped. I have another backup which I think might also be corrupted on my computer from the Galaxy s3 toolkit.
The strange thing is that from what I've read, EFS corruption leads to the phone being useless with no functionality. Mine is almost totally functional, minus the Factory Test coming up.
Help please?!!
Bump. Any help would be GREATLY appreciated. Any ideas to shoot around at all.
bump. Im having the same issue
psychojv said:
bump. Im having the same issue
Click to expand...
Click to collapse
If your /efs folder is missing/empty try this:
Get back to stock
Open Dialer
type ##72786#
Follow prompts
recovery: TWRP 2.5.0
ROM: aokp_primoc_unofficial_Jan-19-13
kernel: the one that came with the aokp rom .zip found in this page
anyway I try to do a factory reset in TWRP and it failed (sd - ext wouldnt wipe for some reason) so I just wipe everything else (system, cache, davlek, and android_secure). I install AOKP and reboot.
so AOKP's colorful unicorn bootloader comes up and I'm greeted by the new interface. It asks for the default launcher and I decide to go with nova launcher. About 30 seconds later the thing reboots and I go through the same process over and over again.
I tried a different kernel as well, lean kernel, and it never got past the "this is for development purposes only" screen. this >
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I tried getting back to stock, but even when I recover the back up I made in TWRP before I changed ROMs it gives me the "this is for development purposes only" screen again and never continues.
Things I've tried
Running an RUU program. always fails.
getting the RUU rom file from the temp folder, renaming it, PK76DIAG, and putting in my sd card. says hboot version is old.
flashing a different ROM. gives me a black screen
reformatting sd card, still can't wipe sd - ext
Scrolling through the internet I can see that a lot of people have trouble with the One V and boot looping, but none of their solutions help me,
I'm really at my wits end so if anyone has had this trouble before I'd love the help
Is this even in the right section?