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.
Related
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 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"
}
Hi everyone!
OK, I'm sick as a dog, so I know I shouldn't have been doing this today, but..
I was trying to update my HTC One M8 with Cyangenmod, (cm-13.0-20160314-NIGHTLY-m8). I had been having problems with TWRP reading my SD card, so I decided to go ahead and wipe my phone and try reinstalling using fastboot. I used TWRP for the wipe, but I used the advanced option, and it seems that I wiped everything, including the OS from my phone. Now, all I get when I boot is this screen:
{
"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 tried holding the power and volume down buttons but I can't get back to the recovery. Both adb and fastboot do not seem to be able to see my phone:
Does anyone have any suggestions one how I can fix this?
Thanks
zog
Can you go to bootloader or only this screen ?
mefistoreyon said:
Can you go to bootloader or only this screen ?
Click to expand...
Click to collapse
Only this screen. My phone won't even power down.
OK, I was just able to get into the bootloader and I can also get into TWRP. I have a micro USB chip that I can put into the phone. Should I copy the files onto the chip and use TWRP to flash? There is also an option for "adb sideload" in TWRP.
Whew!
OK, using sideload, I was able to flash Cyanogenmod back onto my phone!
Every thing should be fine now! (fingers crossed!)
You also can copy files with mounting from twrp.
Sent from my HTC One M8 using Tapatalk
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.
Hello, I tried rooting my phone following this tutorial from a youtuber named Max Lee. since I am a noob. Everything was going fine until I flashed the SuperSU (As shown in the vid). I rebooted it and it got stuck in a bootloop. I tried multiple methods to get out, but I ended up relocking the bootloader and now I can't get into recovery. Since I hit rock bottom (which is why I am making this thread lol), I just need to know if there is anyway I can resolve this issue, or I need to know if my phone is just hard bricked.
{
"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"
}
BarackObama1889 said:
Hello, I tried rooting my phone following this tutorial from a youtuber named Max Lee. since I am a noob. Everything was going fine until I flashed the SuperSU (As shown in the vid). I rebooted it and it got stuck in a bootloop. I tried multiple methods to get out, but I ended up relocking the bootloader and now I can't get into recovery. Since I hit rock bottom (which is why I am making this thread lol), I just need to know if there is anyway I can resolve this issue, or I need to know if my phone is just hard bricked.
Click to expand...
Click to collapse
@zedomax! His tutorials are good. He also has a website for that at htconeroot.com
But here's the problem, that tutorial is over two years old, so the TWRP recovery and SuperSU app linked there are outdated and won't work with the newer firmware.
Here's what to do:
Unlock your bootloader again.
Flash the latest TWRP in fastboot that you can download from here
From there you can either flash a ROM (almost all of them come pre-rooted with SU already installed), or flash the latest stable SuperSU.zip in recovery that you can download from here.
The easiest is to just flash TWRP, then a custom ROM.
Good luck!