Lost my root - Galaxy S II Q&A, Help & Troubleshooting

i recently decided to install a new LP rom on my galaxy s2. i was previously running the unofficial cm12. but before wiping the whole phonei decided to do a little internal sd cleanup, which led me to deleting most files (some that were important). i then successfully installed the new rom without any problems. Once the phone booted up and i tried to run titanium backup to restore my data it didn't detect root on my phone. so i have lost root and need help getting it back. any ideas?
Previous rom: [ROM][5.0.2][I9100] CyanogenMod 12 by Lysergic Acid
Current rom: Resurrection Remix by varund7726
PS: i know i am a giant noob at this so save the instults pls
thank you

nukerdude50 said:
i recently decided to install a new LP rom on my galaxy s2. i was previously running the unofficial cm12. but before wiping the whole phonei decided to do a little internal sd cleanup, which led me to deleting most files (some that were important). i then successfully installed the new rom without any problems. Once the phone booted up and i tried to run titanium backup to restore my data it didn't detect root on my phone. so i have lost root and need help getting it back. any ideas?
Previous rom: [ROM][5.0.2][I9100] CyanogenMod 12 by Lysergic Acid
Current rom: Resurrection Remix by varund7726
PS: i know i am a giant noob at this so save the instults pls
thank you
Click to expand...
Click to collapse
You didn't loose root, you just haven't activated it. You can do so by going to developer options and enable root access for apps and adb.

acydwarp said:
You didn't loose root, you just haven't activated it. You can do so by going to developer options and enable root access for apps and adb.
Click to expand...
Click to collapse
thanks for the reply but u see the problem now is that i flashed the official firmware using odin and now that i try to root and flash a new rom, i get an error (attached) and it get stuck here for like 5 mins and finally displays "installation aborted"
{
"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"
}

nukerdude50 said:
thanks for the reply but u see the problem now is that i flashed the official firmware using odin and now that i try to root and flash a new rom, i get an error (attached) and it get stuck here for like 5 mins and finally displays "installation aborted" View attachment 3141573View attachment 3141577
Click to expand...
Click to collapse
Your recovery version is too old. You need recovery version 6.0.4.7 and higher. Download newer CWM version here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/i9100/

Related

[Q] GAPPS not working on CM 12.1

Hi,
First of all apologies if I am not in the right thread to post this question. I am running CM 12.1 (Nightly CM12.1-20150430) on Nexus 5.
The issue is, I flashed the GAPPS as well for CM 12.1 (i.e. for Android 5.1) But after flashing GAPPS, I am constantly getting the message "Unfortunately the process com.google.process.gapps has stopped"
This is so frustrating because before when I was running CM 12 at that time as well these processes stopped. I somehow managed to reduce the frequency of getting such message by clearing app cache (for message "Unfortunately play store services has stopped" I used to clear cache for Play Store app from Settings--> Apps--> All Apps. And same for other apps as well.)
Its irritating to get such messages even after flashing the appropriate GAPPS for CM 12.1. Is there any way or updated GAPPS which could help me in this situation.
Any help is appreciated.
Thanks.
Hi all,
I have the very same error with the latest CM nightly (20150503) and the official CM GAPPS.
I use the Samsung Galaxy S4.
Thanks
TheEmperor69 said:
Hi all,
I have the very same error with the latest CM nightly (20150503) and the official CM GAPPS.
I use the Samsung Galaxy S4.
Thanks
Click to expand...
Click to collapse
Hi,
I somehow escaped from the issue All you have to do is reflash the latest nightly build along with compatible GAPPS (if you are flashing CM12.1 flash Gapps 5.1) Before doing so, you have to format your phone (Clean flash)
Thats what I did. Erased everything from my phone (after taking backup from Titanium Backup) and then flashed the latest nightly build with the GAPPS for android 5.1 and now I can run every google app without any issue
Hope it will work for you as well :good:
If you have same issue then.......
Guyzzzz after trying the method that is written above if you fail then try this method it work 1000% yes it works
Just follow these steps
1. just go to apps
2. Disable all apps that look like 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"
}
3. Keep them disabled for 1 day
4. After a day just enable them n use aaaalllllllllllllllll gapps
Note:---- It will remain till the reboot after reboot follow the steps again
N this time u need them disabled for 1 hour yes 1 hour. Good bye stay blessed brozzz
N if it works just pray for me........
Replace TWRP with ClockWorkmod
I've had the same issue. What solved it for me was replacing TWRP with ClockWork recovery tool. From there it was a breeze. Hope it helps.

First time root - few questions

It's finally time for me to do what every XDA user done already - root my phone and use another ROM. I haven't ever before done this that's why I'm very excited.
I'm trying to follow this noob-friendly guide http://forum.xda-developers.com/showthread.php?t=2213910 . I read it like ten times already, but I still have some questions.
1. I want to have a CM rom. Should I get Lloir's CM 12.1 or the official CM 11? The thing is, I won't be able to get another rom for almost a year and I want a quite stable rom.
2. I guess I should install the latest TWRP 2.8 recovery from this forums, am I right? But then, why on the official CM download page there is a separate "Cyanogen Recovery" file?
3. According to the tutorial, I should install SuperSu, is this the right version?
https://download.chainfire.eu/696/SuperSU/
4. The thing I'm worried about mostly - my digitizer is damaged and I sometimes get "phantom touches", I can't tap anything on screen, the only solution is screen off & on. What if phantom touches appear when I'm in recovery? From what I read most things are controlled by physical buttons (which work), but not all, some requires to swipe. What then? Can I turn the screen off or abort the process and start again?
Thanks in advance for every reply.
If you need a stable rom you should stay on stock.
1. I use CM12.1 and used CM11 before. I prefer 12.1. They all have some more or less annoying bugs -> read the threads and make your own decision
2. Use the TWRP version which is linked in the rom thread. Cyanogen recovery has less functions and is not public released for x+ afaik
3. CyanogenMod is shipped with it's own su-management app. So no need to install SuperSU
4. you can turn screen on and off in recovery
Thank you very much!
An hour ago I installed CM12.1, I may say successfully, because it booted and now Play Store is downloading GBs of apps., so I can't in fact do anything .
Maybe just one lat thing. If I'd like to install a CM12.1 update in the future, do I have to wipe everything? Or just flash the boot.img and rom and that's it?
CM says you don't need to wipe, but Lloir sometimes wants us to wipe x)
In CM12 root must be enabled in developer options btw.
crusader727 said:
but Lloir sometimes wants us to wipe x)
Click to expand...
Click to collapse
{
"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"
}

Opx twrp fail

Hello everyone.
I have problem with my OnePlus X. It's rooted and a week ago starts roll out new Oxygen 2.2. I get OTA update, but I can't install it. I understand, it's because of root, but I downloaded zip file and trying to install it via TWRP and it always say's FAIL. Even on FACTORY RESET. I read a lot of stuff but it's always the same. Flash custom recovery and install ROM via TWRP or CMW.
Can you help me?
Thanks
what are you flashing? the full ROM or the OTA? which TWRP are you using and what is the error message?
I was trying to flash OTA Oxygen 2.2 but it doens't work. So I tried full ROM (oxygen and Cyanogenmode) and it doesn't work too. I have TWRP v2.8.7.0 .
{
"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"
}
OTA can't work it's normal.
Full zip should but if not, you have to install Bluspark recovery.
twrp-2.8.7.0-onyx_f2fs_v12.img
Okey thanks a lot. I'll try it.
maxillam said:
Okey thanks a lot. I'll try it.
Click to expand...
Click to collapse
Just to be sure, You followed well the unlock bootloader / recovery install and root instructions? You didn't just do the oneclick root approach?
Not one click. Full root.
It' should work with the recovery I told you, as it worked with others....
I hope it will. Thanks a lot man.
Do one thing,
Flash blu spark recovery, Then choose the 2.1.3-X zip n in the next step "add zips" add 2.2 (latest one) patch which is about 40mb n flash both at once.. it will do it n u will b on Oos 2.2
YES! Got it. I downloaded full ROM 2.2 Oxygen and I did new recovery (blue spark) and it all works Thanks guys )

Been a long time, think I've messed my Poco up - HELP!

Hi All,
I've not really kept in the loop of custom ROM's for a while now. I got a OnePlus Nord and felt like I didn't need to root or flash it so I left it stock. Anyway, I went to change the software on my POCO F1, but I think I've messed myself up here. I was running Pixel Experience, dont think it was the latest build, it was probably like 3+ months old build. And I am using TWRP 3.5.1_10-0. Now I think I messed up by not removing my lockscreen before doing a wipe in TWRP.
This is what I see when I mount MTP through TWRP (after the 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"
}
So I did a wipe, and now I cant access the ZIP's I put on the storage for flashing. And there is no OS installed. And it doesnt seem to let me copy files onto the internal storage.
Anyone got any ideas or tips for how to bring this back? I have TWRP and thats it it seems.
EDIT: After a few reboots and wipes, managed to remove the encryption and I can install a new ROM. I wasn't fussed about losing the data. Updated TWRP to 3.6 official, and installing Lineage OS 18.1, lets see how that goes
Thanks,
donk165
donk165 said:
Hi All,
I've not really kept in the loop of custom ROM's for a while now. I got a OnePlus Nord and felt like I didn't need to root or flash it so I left it stock. Anyway, I went to change the software on my POCO F1, but I think I've messed myself up here. I was running Pixel Experience, dont think it was the latest build, it was probably like 3+ months old build. And I am using TWRP 3.5.1_10-0. Now I think I messed up by not removing my lockscreen before doing a wipe in TWRP.
This is what I see when I mount MTP through TWRP (after the wipe):
View attachment 5489665
So I did a wipe, and now I cant access the ZIP's I put on the storage for flashing. And there is no OS installed. And it doesnt seem to let me copy files onto the internal storage.
Anyone got any ideas or tips for how to bring this back? I have TWRP and thats it it seems.
EDIT: After a few reboots and wipes, managed to remove the encryption and I can install a new ROM. I wasn't fussed about losing the data. Updated TWRP to 3.6 official, and installing Lineage OS 18.1, lets see how that goes
Thanks,
donk165
Click to expand...
Click to collapse
You can find everything you need at my POCO F1 Ultimate Collection & Guides. Just in case you need any other help take a look there.

Almost bricked phone

I installed TWRP on my N960N and it worked soon as i flashed any ROM it got some kind of issue
On AOSP based ROMs like
-PixelOS - boots keeps crashing on setup screen, and bootloops teeling "Bluetooth Keeps Stopping"
-PE+ - just bootloops
-ArrowOS - same as PixelOS
-Lineage - won't even flash using adb sideload
On OneUI based ROMs
-DEODEX | QQ ONE UI 2.5
-NobleROM2.6 - both of them just bootloops.
any idea?
​
If nothing helps, try installing latest stock rom using odin (find the steps on xda). Then go to developer options, turn on oem unlock (if its off) and install twrp again.
Before installing anything- go to wipe/advanced wipe (this will delete internal storage too so back it up first)/ select change file system and select ext 2 and swipe. After its done select ext 4 and swipe again. Reboot to twrp.
Try installing any rom- i sugest you to go with noble 2.6/one ui 4.1, follow the steps in the thread.
{
"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"
}
QasimHamdani said:
View attachment 5765635
Click to expand...
Click to collapse
Ever since I downloaded a custom ROM after that the problem happened note 960f model Let me know in the comments if you find any issues
googleguy420 said:
I installed TWRP on my N960N and it worked soon as i flashed any ROM it got some kind of issue
On AOSP based ROMs like
-PixelOS - boots keeps crashing on setup screen, and bootloops teeling "Bluetooth Keeps Stopping"
-PE+ - just bootloops
-ArrowOS - same as PixelOS
-Lineage - won't even flash using adb sideload
On OneUI based ROMs
-DEODEX | QQ ONE UI 2.5
-NobleROM2.6 - both of them just bootloops.
any idea?
​
Click to expand...
Click to collapse
Try to follow
After failing multiple times with a few of the same ROMs you mentioned, I used the video to guide me and installed the latest NobleROM, all good.
I was on another ROM (iodeOS), switched back to Samsung official ROM and then simply followed the steps.
I used the PDF instructions from sammobile to get back to factory image first.
Good luck and cheers.

Categories

Resources