I have a Virgin Mobile Galaxy S II (which is just a rebranding of the Sprint Epic Touch 4G).
I'm rooted, running CM 10.2 nightlies (no stable versions available)
New build update came, I downloaded and updated to it, it updated my phone from 4.2.2 to 4.3.1, I was happy, seemed a lot smoother
Couldn't get any data or wifi though, so I rebooted, but my phone wouldn't get past the screen that says Samsung Galaxy S II
Booted into recovery, tried restoring the nandroid backup I made just before installing the new build
Won't restore boot image, I can use advanced restore to restore system, data, cache, etc, but not boot, which is kinda important since I can't turn use my phone without it
Help pls
EDIT: So I just kept trying to reboot it because I had nothing better to do while trying to find a solution, and it randomly worked, so I am back wjere I was before I installed the new nightly build.
BUT, I just made a new nandroid backup since the one I had lacked /boot, but as I was making the new nandroid backup it said this:
06:25:51 /boot not found! Skipping backup of /boot!
06:25:51 Consider installing patch file for your device, for a complete nandroid!
06:25:51 /recovery not found! Skipping backup of /recovery!
So apparently my phone has no /boot right now or /recovery, so I can't turn my phone off until I get a new one. Any advice on how to do that would be appreciated.
Just flash a different ROM or the one you were on before. Make a new nandroid. Restore the data portion if you want.
{
"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"
}
Related
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?
I recently switched from TWRP to CWM because I had trouble flashing CM11 in TWRP. Anyway since I am new to CWM I have these two noob questions:
(1) Does CWM backup EVERYTHING the same way TWRP did? In TWRP, I had the option to check everything (system, data, cache, etc) to backup, and restoring a backup restored absolutely everything. CWM didn't give me any options to check during backup and plus the backup files are much smaller than those in TWRP.
(2) As you can see in the screenshot below, cache.ext4.tar, data.ext4.tar, and system.ext4.tar are all 0 B in size. Is this normal?
{
"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"
}
davelee1054 said:
I recently switched from TWRP to CWM because I had trouble flashing CM11 in TWRP. Anyway since I am new to CWM I have these two noob questions:
(1) Does CWM backup EVERYTHING the same way TWRP did? In TWRP, I had the option to check everything (system, data, cache, etc) to backup, and restoring a backup restored absolutely everything. CWM didn't give me any options to check during backup and plus the backup files are much smaller than those in TWRP.
(2) As you can see in the screenshot below, cache.ext4.tar, data.ext4.tar, and system.ext4.tar are all 0 B in size. Is this normal?
Click to expand...
Click to collapse
If you just wiped data and cache then made the backup then those files would be 0 bytes. But there should be an advanced backup option then you can chose what to backup. I use twrp Abe have no problems but try out philz. It's just like cwm but has more options and is full touch but you can still use hardware buttons.
Search didn't turn up anything related to my issue and it doesn't seem to break the phone, but I'd like to know what's going on. After successfully flashing TWRP 2.8.0.2, then the CyanogenMod 11 M9 snapshot (2014-08-04) and the latest gapps (2014-01-05) last night, this morning I go to make a nandroid and imagine my surprise when TWRP isn't there, but CWM 6.0.5.0 (touch version). WTF? It seems like CWM functions properly, and my phone's working fine, but I never flashed CWM. The only thing semi-related in the CM 11 thread is a post from May 2014 about needing to use CWM 6.0.4.8 for future CM builds, but I succesfully did it with TWRP, soooooooo. I don't know what's going on. Does CM 11 automatically flash CWM for some compatibilty reason? The only other thing that might be useful info is that I did have my phone connected to my PC the whole time last night, since I had just finished unlocking bootloader, copying the CM 11 and gapps zips, etc. and I did have a CWM img in my adb/fastboot directory (since I wasn't yet sure which recovery I was going to flash), but it was the 6.0.4.8 non-touch recovery, which isn't the version that's been mysteriously flashed to my phone, and I never entered any commands to flash that img anyway. Any thoughts?
i think you might have clicked "update CM Recovery" in the developer options. that's the only real explanation i can think of
{
"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"
}
The "update CM recovery" thing sounds the most plausible at this point. Thanks for taking the time to read. Although Rick James might be on to something.
ROM: ResurrectionRemix-M-v5.7.1-20160715-t0lte
SuperSU: https://download.chainfire.eu/969/SuperSU/UPDATE-SuperSU-v2.76-20160630161323.zip?retrieve_file=1
Recovery: ClockWorkMod
So, I probably did something dumb and I'm stuck on the boot animation which loops forever. I can get into Recovery and Bootloader. I previously had a working install of the ROM listed above but I thought I needed to regain root (apparently it is already rooted but that was turned off or something) so I downloaded the SuperSU file to the device and rebooted into Recovery. I installed the SuperSU and rebooted but now I have the problem. Please advice. This is my first time ever using a custom ROM and I had it working fine before I did this to myself...
{
"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 suggest flashing TWRP as CWM has not been updated for a long time. Once TWRP is on the phone, perform a full system wipe and re-install a custom ROM.
audit13 said:
I suggest flashing TWRP as CWM has not been updated for a long time. Once TWRP is on the phone, perform a full system wipe and re-install a custom ROM.
Click to expand...
Click to collapse
Thank you for your reply!
I was unaware that CWM was so out of date; it did work well before I tried to root an already rooted ROM. But I will try TWRP in any case. Still, I was hoping to solve this issue without wiping/reinstalling everything as I have data I want to preserve. If there is no way out of this mess except that, I will use ADB to get what data I can, then reinstall.