Database Develop

Clockworkmod Recovery Galaxy s3 problems

Well guys this is my first time on the forums. My phone is rendered near useless right now. A few days ago, i rooted my phone via towelroot. as a friend reccomended, i installed ROM manager and flashed clockworkmod recovery. I backed up my stock, perfect ROM with CWM and decided to try installing cyanogenmod 10.3.1......... it wouldn't install. I even tried other apps like ROM installer. Then i came across the handy dandy Cyanogenmod Installer. This seemed great, i didn't have to do anything except click a few buttons on my PC. as i was ready to enjoy a new custom ROM, the following message popped up, "Root access possibly lost. Fix?". I was given the options of "No" and "Yes - Fix root (/system/xbin/su)". i chose the second one, and waited for my device to boot. when it did, it was stock Touchwiz Android version 4.4.2, just like i had initially. what's more is my imei and bandwidth version were both "unknown" and i my sim card was undetected. I decided that technology had gotten the better of my and i tried to flash my old stock ROM back on. i found the file in recovery mode but it kept saying "no files found" whenever i clicked on it. I tried the cyanogenmod installer again, this time choosing "No", resulting in exactly the same scenario. At this point, I would be fine having the stock ROM since i have had such bad luck with the "developer's world" of Android.......... PLEASE HELP!!!!!

Another note:
ROM manager now is telling me that CWM is not installed, yet it is present in recovery mode......

EddyTeddy01 said:
Another note:
ROM manager now is telling me that CWM is not installed, yet it is present in recovery mode......
Click to expand...
Click to collapse
Have you tried installing some other recovery, like TWRP? You won't be able to install CM from it, but you should be able to install other roms.

touchbattle.mika said:
Have you tried installing some other recovery, like TWRP? You won't be able to install CM from it, but you should be able to install other roms.
Click to expand...
Click to collapse
How do I replace CWM with twrp? If I flash twrp, wouldnt CWM stay on my phone as default recovery?

EddyTeddy01 said:
How do I replace CWM with twrp? If I flash twrp, wouldnt CWM stay on my phone as default recovery?
Click to expand...
Click to collapse
follow the guide and replace your recovery easily. after flashing, what recovery you have flashed will be default recovery, i recommend philz, they are all downloadable in the guide

MaHo_66 said:
follow the guide and replace your recovery easily. after flashing, what recovery you have flashed will be default recovery, i recommend philz, they are all downloadable in the guide
Click to expand...
Click to collapse
Would I have to uninstall CWM? I'm just wondering if the file for CWM will still be on my phone. I'll check out the link.

EddyTeddy01 said:
Would I have to uninstall CWM? I'm just wondering if the file for CWM will still be on my phone. I'll check out the link.
Click to expand...
Click to collapse
it´s the best if you also do a format of internal sd in recovery before changing the recovery, because sometimes there are some folders left of it in interrnal memory and you cant delete it, do that if this will be the case. but i think Philz and CWM use same folder, so if you flash philz it will be okay if im correct otherwise you can always format internal sd afterwards
Edit: dont use rom manager for recovery actions, use recovery itself, much more reliable

MaHo_66 said:
follow the guide and replace your recovery easily. after flashing, what recovery you have flashed will be default recovery, i recommend philz, they are all downloadable in the guide
Click to expand...
Click to collapse
That guide made it possible for me to install all custom roms. Witz the recovery installed first it did not work. Thx

[Q] XT1060 4.4.4 OTA Boot Loop

TWRP Recovery
Rooted
Xposed framework installed
Been getting bugged for the 4.4.4 update, and I wanted to open and look at the ZIP out of curiosity, so I hit install now, thinking it still needed to download... but turns out it didn't, and rebooted right away.
So now I'm stuck in a boot loop of sorts.... it boots, and loads up Android, and I can use the phone, but after about 20-30 seconds it reboots into recovery.
Is there an easy way out of this without wiping everything? Preferably a modded OTA that I can install for the 4.4.4 update.

Check out the thread under general tab to use RSD Flasher or House of Moto to install the 4.4.4 FXZ
DB's Moto X

coreno said:
TWRP Recovery
Rooted
Xposed framework installed
Been getting bugged for the 4.4.4 update, and I wanted to open and look at the ZIP out of curiosity, so I hit install now, thinking it still needed to download... but turns out it didn't, and rebooted right away.
So now I'm stuck in a boot loop of sorts.... it boots, and loads up Android, and I can use the phone, but after about 20-30 seconds it reboots into recovery.
Is there an easy way out of this without wiping everything? Preferably a modded OTA that I can install for the 4.4.4 update.
Click to expand...
Click to collapse
The above post is good advice. If you use House of Moto with the full 4.4.4 FXZ, you can choose to "KEEP DATA".
You will need to flash TWRP back on and re-root afterwards AND re-install Xposed, but all of your apps and settings will remain intact.
The reason this happened is because you have TWRP installed - taking OTAs *always* requires you to have STOCK recovery - not custom.
Good Luck :good:

samwathegreat said:
The above post is good advice. If you use House of Moto with the full 4.4.4 FXZ, you can choose to "KEEP DATA".
You will need to flash TWRP back on and re-root afterwards AND re-install Xposed, but all of your apps and settings will remain intact.
The reason this happened is because you have TWRP installed - taking OTAs *always* requires you to have STOCK recovery - not custom.
Good Luck :good:
Click to expand...
Click to collapse
Thanks for the replies. Thanks for the reply... the phone eventually decided the update failed and gave up. Apparently clearing the cache would've also probably worked.
But, now I've reflashed stock recovery, removed xposed, and unrooted. I should be safe to just take the OTA now, right?
I would've done the FXZ earlier, but didn't realize there was a keep data option.

coreno said:
Thanks for the replies. Thanks for the reply... the phone eventually decided the update failed and gave up. Apparently clearing the cache would've also probably worked.
But, now I've reflashed stock recovery, removed xposed, and unrooted. I should be safe to just take the OTA now, right?
I would've done the FXZ earlier, but didn't realize there was a keep data option.
Click to expand...
Click to collapse
You can try, and it will probably work....but if it were me, I'd still use the FXZ and keep data option. It's cleaner and no chance of something going wrong. Afterwards, just do like I said -- re-flash TWRP, re-root, then reinstall Xposed.

samwathegreat said:
You can try, and it will probably work....but if it were me, I'd still use the FXZ and keep data option. It's cleaner and no chance of something going wrong. Afterwards, just do like I said -- re-flash TWRP, re-root, then reinstall Xposed.
Click to expand...
Click to collapse
Thanks for you help! I am all upgraded and got everything back going to the way it was!

coreno said:
Thanks for you help! I am all upgraded and got everything back going to the way it was!
Click to expand...
Click to collapse
Great!! Glad to hear everything worked out. I sent you a Private message - check your PMs

Just to add my experience: I too tried to apply the update (rooted, 4.4.2, xposed, stock recovery, locked boot loader).
Got the boot loop you mentioned.
Only remedy was for me to quickly go into root explorer and rename the 3c.ota.apk and 3c.ota.odex files. Now I no longer get the notifications (unless I reboot my phone).

jco23 said:
Just to add my experience: I too tried to apply the update (rooted, 4.4.2, xposed, stock recovery, locked boot loader).
Got the boot loop you mentioned.
Only remedy was for me to quickly go into root explorer and rename the 3c.ota.apk and 3c.ota.odex files. Now I no longer get the notifications (unless I reboot my phone).
Click to expand...
Click to collapse
And in your case, it was Xposed.
There are several threads (and posts) discussing conditions for taking an OTA. You need stock recovery, have to disable Xposed, and you need to be close enough to stock so the pre-flash verification will pass. Otherwise, the OTA will fail, and/or you'll get stuck in a boot loop.
There is a little more to it as well, but I'll ask you to see the other threads.

Thought I disabled xposed. But perhaps not. I've read other threads. From my understanding, I won't be able to root (or even the quasi-root) on 4.4.4 with a locked boot loader.
Thx for the reply.

[Q] No WiFi at all after Lollipop 5.0.2 update! [RESOLVED]

Well, not a singlle answer after so many views for days, but thank God it doesn't matter anymore, I was able to force the solution for th issue anyways! Issue resolved, if you have updated to 5.0.2 and have rooted your device before or after causing it to lose WiFi, please check out my solution for this issue here, it may very well prove to be your definitive solution. Thanks!
http://forum.xda-developers.com/showpost.php?p=58367424&postcount=96

Here's the direct quoted message:
ajape said:
Installing the 5.0.2 OTA while rooted completely and utterly broke my WiFi. No matter what I tried, I couldn't get Wifi to work again. In the end I gave up, and just did a full factory reset from recovery. My recovery version btw is TWRP 2.8.3, and after installing the ZIP ROM update from the first post of this thread TWRP stayed, I didn't have to install it again. So anyways, I let it boot up and then rebooted back to recovery to root on recovery exit, which caused bootloops for a little while until I used Power+VolDown to go back into recovery and installed the SuperSU 2.45 zip from there. NO MORE PROBLEMS! It's just, PERFECT!!! Finally, no more long waits while booting looking at the logo, no more bootloops, and most importantly: by only using the recovery zips to root and never trying to root from the system or allowing it try to update SuperSU from the Play Store, NO WIFI ISSUES, from the very start all is just perfectly functioning, soooo smooth and really fast! FINALLY!!!!!! Really happy here, so remember, for XT1064 TWRP 2.8.3.0, and SuperSU 2.45 should really do the trick. Good Luck!
Click to expand...
Click to collapse
And here's the link to the actual thread that has the appropriate 5.0.2 Stock ROM flashable ZIP file:
http://forum.xda-developers.com/moto-g-2014/development/rom-stock-rom-t2970427

Problem from uninstalling xposed (SOS)

Hi. i'm on Galaxy S6 6.0.1 marshmallow (STOCK ROM) that recently rooted and installed Xposed custom build by wanam.
I regret after finding out that i was unable to use barclays banking app and snapchat;
Unsure if my phone is soft bricked due to my history of actions:
First, i have installed normal xposed that caused bootloop and then proceed to replace it with the custom build version by wanam upon researching in the forums.
Upon finding out that i was unable to use the apps mentioned above after booting,
I unrooted my phone believing it was due to the root without removing xposed. It still didn't work so I rerooted it back just to remove xposed.
After flashing the uninstaller.zip, it went on bootloop again. I tried flashing several uninstaller including the one provided by wanam and it all didn't work.
The only solution i found in the internet was to deleting the file on data/data/de.****xposed via TWRP file manager. That didn't work as well and I panicked when the reboot button in TWRP weren't working anymore so i manually rebooted and proceeded to wipe my data heavy-heartedly which also didn't bypass the bootloop.
Now, i am left with no option and only able to use my newly wiped phone after reinstalling Xposed again.

dleeyx said:
Hi. i'm on Galaxy S6 6.0.1 marshmallow (STOCK ROM) that recently rooted and installed Xposed custom build by wanam.
I regret after finding out that i was unable to use barclays banking app and snapchat;
Unsure if my phone is soft bricked due to my history of actions:
First, i have installed normal xposed that caused bootloop and then proceed to replace it with the custom build version by wanam upon researching in the forums.
Upon finding out that i was unable to use the apps mentioned above after booting,
I unrooted my phone believing it was due to the root without removing xposed. It still didn't work so I rerooted it back just to remove xposed.
After flashing the uninstaller.zip, it went on bootloop again. I tried flashing several uninstaller including the one provided by wanam and it all didn't work.
The only solution i found in the internet was to deleting the file on data/data/de.****xposed via TWRP file manager. That didn't work as well and I panicked when the reboot button in TWRP weren't working anymore so i manually rebooted and proceeded to wipe my data heavy-heartedly which also didn't bypass the bootloop.
Now, i am left with no option and only able to use my newly wiped phone after reinstalling Xposed again.
Click to expand...
Click to collapse
Did you wipe dalvik&cache after flashing the uninstaller?

Portgas D. Ace said:
Did you wipe dalvik&cache after flashing the uninstaller?
Click to expand...
Click to collapse
Yes, although i need to manually reboot it as TWRP doesn't reboot automatically for me.
Would you think that might be the problem?

dleeyx said:
Yes, although i need to manually reboot it as TWRP doesn't reboot automatically for me.
Would you think that might be the problem?
Click to expand...
Click to collapse
I don't think so. I would suggest that you ask for help in wanam's Xposed thread as this is the version you installed.

Help needed - Samsung J5-sm10fn (touchwiz) stuck booting into TWRP recovery

So I tried installing Xposed Framework by flashing it's ROM, but after I did it, I rebooted my phone, but every time I do it, it always boots into TWRP recovery. I tried fixing it by looking in the setting and I used a backup I made before doing all this crap and I restored, but my phone still boots only into TWRP recovery mode. I would really appreciate it if anyone could help me. Thanks.
PS. My phone is rooted and it has TWRP

TribalPaint said:
So I tried installing Xposed Framework by flashing it's ROM, but after I did it, I rebooted my phone, but every time I do it, it always boots into TWRP recovery. I tried fixing it by looking in the setting and I used a backup I made before doing all this crap and I restored, but my phone still boots only into TWRP recovery mode. I would really appreciate it if anyone could help me. Thanks.
PS. My phone is rooted and it has TWRP
Click to expand...
Click to collapse
Is it possible that you used the wrong Xposed for your device or SDK version? I can't imagine that restoring a backup didn't fix it. Did you try wiping system in TWRP first?
Things you can try:
- Flash the "Xposed Uninstaller" zip file in TWRP, which should always be on your device when you are flashing new versions of Xposed.
- Reflash TWRP in Odin. This should fix a recovery loop.
- Wipe system, data, dalvik, cache in TWRP, then try restoring your backup.
- As a last resort, you can download the latest stock firmware for your device from the sammobile site, flash it in Odin, let it boot once, reflash TWRP, wipe in TWRP and restore your backup (if you were running a custom rom you liked or something), then flash the correct Xposed for your device & android version.
Hope this helps!
Sent from my SM-N920T using Tapatalk

bogarty said:
Is it possible that you used the wrong Xposed for your device or SDK version? I can't imagine that restoring a backup didn't fix it. Did you try wiping system in TWRP first?
Things you can try:
- Flash the "Xposed Uninstaller" zip file in TWRP, which should always be on your device when you are flashing new versions of Xposed.
- Reflash TWRP in Odin. This should fix a recovery loop.
- Wipe system, data, dalvik, cache in TWRP, then try restoring your backup.
- As a last resort, you can download the latest stock firmware for your device from the sammobile site, flash it in Odin, let it boot once, reflash TWRP, wipe in TWRP and restore your backup (if you were running a custom rom you liked or something), then flash the correct Xposed for your device & android version.
Hope this helps!
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
Hello. I already tried zipping the uninstaller for xposed but it did nothing, I also tried wiping dalvik cache and all, but no luck. I also think that my backups are just not functional. Now I'm left to just reflashing TWRP and if that doesn't work I'll have to flash the original stock firmware for my phone. I have spent already 2 days with constant searching for ways to fix my phone and not being able to do other things because this has been taking up my time and my patience, so I really appreciate every bit of fixing my phone that I get. Since I am new to all this I would be very grateful if you could send me the links to the correct files for my device and also give me a tutorial on what to do. As I appreciate any support, so I'm thankful for you helping me But until then my device is still not able to boot regulary but rather boots to TWRP

TribalPaint said:
Hello. I already tried zipping the uninstaller for xposed but it did nothing, I also tried wiping dalvik cache and all, but no luck. I also think that my backups are just not functional. Now I'm left to just reflashing TWRP and if that doesn't work I'll have to flash the original stock firmware for my phone. I have spent already 2 days with constant searching for ways to fix my phone and not being able to do other things because this has been taking up my time and my patience, so I really appreciate every bit of fixing my phone that I get. Since I am new to all this I would be very grateful if you could send me the links to the correct files for my device and also give me a tutorial on what to do. As I appreciate any support, so I'm thankful for you helping me But until then my device is still not able to boot regulary but rather boots to TWRP
Click to expand...
Click to collapse
Also, if I try to reflash TWRP, do I have to reflash the original firmware first, or I can just go straight ahead and just reflash TWRP?

TribalPaint said:
Also, if I try to reflash TWRP, do I have to reflash the original firmware first, or I can just go straight ahead and just reflash TWRP?
Click to expand...
Click to collapse
Update:
I fixed my phone, and here's what I did, so if anyone is new here with the same issue I had, I hope this can help you. So first of all as I said I kept booting to TWRP, later I tried reflashing TWRP, but I remembered that I missed something in ODIN, so I just pulled the cord and my screen after rebooting just said something along the lines of "An unexpected error occurred while updating software, please recover using Samsung Smart Switch." after that, I tried Samsung Smart Switch, but it was no luck for me, so then I used the last resort. I went on sammobile.com, I searched stock firmware for the exact model I had and then I checked the stock firmware that was available. Since I'm from Latvia, I picked the Baltic region, then I downloaded the latest stock firmware. After a long time, I downloaded the file, and I checked the instructions on how to flash it, I flashed the stock firmware, and then my problem was fixed, my phone was working again and now I have Android 7.1.1 as I used to have Android 6.0.1 and I had ZERO file loss However as you flash the stock firmware, TWRP get "flashed" out and same with root if you have it, and in that case if you want TWRP and root again, I highly suggest Meziani's YoutTube channel, because he gives simple and working tutorials on how to do it I'm glad if this helped anyone.