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.
Related
I am trying to return to stock in order to update via OTA. I have restored with CWM with stock Nandroid, and everything went fine except for android.secure has failed to restore. Then after trying to return recovery to the stock one (my version is 2.17) I still get to CWM 5.8.4.0, no matter how many times I flash it and erase cache.
Under this circumstances I am unable to update with OTA. Can any one help me with this?
glazzi said:
I am trying to return to stock in order to update via OTA. I have restored with CWM with stock Nandroid, and everything went fine except for android.secure has failed to restore. Then after trying to return recovery to the stock one (my version is 2.17) I still get to CWM 5.8.4.0, no matter how many times I flash it and erase cache.
Under this circumstances I am unable to update with OTA. Can any one help me with this?
Click to expand...
Click to collapse
I get this screen when trying to access Recovery. Is this stock? I just checked here (http://forum.xda-developers.com/showthread.php?t=2067001 ) and it looks similar to the one in HOX+
{
"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"
}
glazzi said:
I get this screen when trying to access Recovery. Is this stock? I just checked here (http://forum.xda-developers.com/showthread.php?t=2067001 ) and it looks similar to the one in HOX+
View attachment 1894661
Click to expand...
Click to collapse
yeha that is stock recovery.
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.
{
"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 there,
I just flashed TWRP 3.0.0.0 recovery using that I installed ResurrectionRemix-M-v5.6.5-20160317-armani, in my Phone.
Everything was fine, My working good.
But I cant boot to recovery mode now wenever i tried to do that recovery starts and stuck on the First screen that comes when we start recovery.
I installed cwm, philz too but the problem is same with thm.
My phone is working but i cant flash anything now using recovery.
I want to upgrade my ROM bt I cant.
KarthikCalling said:
Hi there,
I just flashed TWRP 3.0.0.0 recovery using that I installed ResurrectionRemix-M-v5.6.5-20160317-armani, in my Phone.
Everything was fine, My working good.
But I cant boot to recovery mode now wenever i tried to do that recovery starts and stuck on the First screen that comes when we start recovery.
I installed cwm, philz too but the problem is same with thm.
My phone is working but i cant flash anything now using recovery.
I want to upgrade my ROM bt I cant.
Click to expand...
Click to collapse
Try flashing the latest twrp recovery i.e., 3.0.1 through fastboot. .
same problem here... still try downgrade twrp
Same problem tried 3 version, flashed using fast boot and normal (using app) but no use tried using miui 7,8 and cm ....... please help me
Try installing MIUI offical rom through fastboot boot
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!
This is my first question here.
I have SM-N975F. A couple of days ago I installed 12 version of Android (Official Star Wars, OSW) and got a root access with the help of Magisk 24.1. All is good, but one thing: if it is just stock firmware, then I have 256 Gb on board as expected. But after rooting I have only 32 Gb!
Can anybody explain me what happened? Is it possible to fix that problem?
{
"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'm also on A12 ( ONEUI 4) and rooted using Magisk 24.1 and everything seems good here. May be you'd like to take a closer look on all the steps which u did to root the device!
U haven't did factory reset after flashing. To solve this just flash same stock rom and directly boot into stocl recovery and perform a factory reset and wipe cache partition
LinhBT said:
I'm also on A12 ( ONEUI 4) and rooted using Magisk 24.1 and everything seems good here. May be you'd like to take a closer look on all the steps which u did to root the device!
Click to expand...
Click to collapse
Yes, you are right. I missed some steps.... Thank you!
rc chanu said:
U haven't did factory reset after flashing. To solve this just flash same stock rom and directly boot into stocl recovery and perform a factory reset and wipe cache partition
Click to expand...
Click to collapse
Thats it! I haven't done factory recet. Now all is good, thank you so much!