[Q] Issues after switching to cwm from twrp - Verizon Samsung Galaxy Note II

Been using twrp since rooting note II. I wanted to try out 4.4 PA but they said to only use cwm. It was late so I decided to be lazy and since I used to use rom manager all the time I installed it to flash cwm recovery then booted into recovery to install touch version. It wasn't showing the touch version so selected to restart to check to see where I saved it to it would not boot past the first "note II" splash screen. Battery pull then back into recovery and went ahead and flashed PA 4.4 and now it will get past the splash screen then shows boot animation but then starts all over.
Is this a rom manager issue?
can I flash twrp from within cwm recovery?
will I have to basically reroot it?
Any suggestions on how to get back to twrp and to a usable phone?
thanks

If you download a .zip of twrp and flash it you will have twrp for your recovery.
As long as you flash a rooted rom, you will be rooted.
Not sure what happened with the boot loop, did you by chance wipe the system without flashing another before booting?
Sent from my SCH-I605 using Tapatalk

cadavjo said:
If you download a .zip of twrp and flash it you will have twrp for your recovery.
As long as you flash a rooted rom, you will be rooted.
Not sure what happened with the boot loop, did you by chance wipe the system without flashing another before booting?
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
Nope did my standard wipe cache, wipe dalvik, and factory reset then flashed rom then gapps. Going to go back to twrp and wait for 4.4 to be more stable before I try it out again and maybe then I can use twrp to flash it.
thanks for the help

cadavjo said:
If you download a .zip of twrp and flash it you will have twrp for your recovery.
As long as you flash a rooted rom, you will be rooted.
Not sure what happened with the boot loop, did you by chance wipe the system without flashing another before booting?
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
that didn't work. flashed newest twrp then rebooted into it and tried to flash tweaked and sticks at the splash screen again

jdpeck said:
that didn't work. flashed newest twrp then rebooted into it and tried to flash tweaked and sticks at the splash screen again
Click to expand...
Click to collapse
Have you wiped data at all? You need to wipe data / factory reset when switching roms, and it sounds like you havent.

fallingup said:
Have you wiped data at all? You need to wipe data / factory reset when switching roms, and it sounds like you havent.
Click to expand...
Click to collapse
As stated above, on both cwm and twrp I wiped caches and did factory reset and still having the issues. Once back on twrp I even formatted internal memory thinking maybe rom manager messed something up on it and still can't get passed the splash screen.

jdpeck said:
As stated above, on both cwm and twrp I wiped caches and did factory reset and still having the issues. Once back on twrp I even formatted internal memory thinking maybe rom manager messed something up on it and still can't get passed the splash screen.
Click to expand...
Click to collapse
Copy a ROM to your SD card (external not internal)
Install cwm and format data (actually full format, where /data/media gets wiped) and system
Install rom
Reboot
TWRP has some issues randomly with corrupting /data, that's why I no longer use it.

fallingup said:
Copy a ROM to your SD card (external not internal)
Install cwm and format data (actually full format, where /data/media gets wiped) and system
Install rom
Reboot
TWRP has some issues randomly with corrupting /data, that's why I no longer use it.
Click to expand...
Click to collapse
Finally got it. Thought using odin to flash back to root 66 and start fresh would work but after that it was still going to the splash screen then black and a battery pull had to be done. TWRP back ups would fail when trying to restore, so I reverted back to an older version of twrp and it finally let a back up be installed and it booted up just fine!!
thanks for all the suggestions

Im having a similar problem to yours, I am using twrp and flashed PA 3.99 the phone works great, but if my battery dies or i restart the phone or shut it down it automatically wont get passed the samsung logo, or sometimes the PA logo, the only work arounds ive seen to it is to wipe the cache and dalvik to boot, but when that fails i have to install the whole rom over again. any ideas?

Related

[Q] Stuck at Boot screen, how to recover?

Just bought a used phone off Swappa. It has TWRP and had Cyanogenmod installed.
I wanted to try a TouchWiz ROM so I downloaded one. Booted into recovery, made a backup to external SD Card and then flashed the ROM. It said it flashed
successfully but when rebooted, it just stayed at the Samsung Galaxy S4 Boot
screen.
I tried restoring the backup, but it failed!
I thought I might have had a bad download so I downloaded Cyanogenmod nightly and LiquidSmooth on my laptop, transfered to the SD card, popped it into the S4, boot into recovery, and tried flashing each, and both just boot to the boot screen and freeze.
What are my best options now? I saw some guides for flashing back to stock via Odin, but requires that I know if I am on VRUAME7 or VRUAMDK and I don't know. Could I have been on ME7 and running Cyanogenmod? Doesn't seem possible, no?
Me7 ota doesnt have the ability to flash custom recovery or rom, so no you werent on that beforehand. Whenever you flash a rom you need to do a wipe/factory reset and wipe caches, unless op states you can dirty flash. Doing some reading will only help you out, generally every post outlines the installation process. Boot to recovery do your wipes then try booting again. If your still in a bootloop then you will need to flash mdk via odin then start the rooting and romming process over.
Sent from my SCH-I545 using Tapatalk 2
Man, I thought I did everything right.
First, did a backup.
Then full wipe with TWRP full wipe, including cache.
Then flash ROM
I'll have to get familiar with Odin and find the MDK images.
Sometimes that happens. Could have been a bad download then it happens more often then you would think. If theres an md5 hash posted its a good idea to verify the download is good. In the dev section theres no wipe mdk images posted so you wont lose your already installed apps and data.
Sent from my SCH-I545 using Tapatalk 2
So I downloaded the factory image and flashed via Odin, but accidentally flashed via bootloader rather than PDA. It wouldn't start - still hung at the boot screen, so I re-flashed via PDA and it is still hanging at the boot screen.
Now I don't know if it is just the same problem as before, or if I messed something up with flashing through bootloader. Can I reflash something via the bootloader section of Odin to restore it?
What version of twrp? And try to go back into recovery and wipe cache and dalvik.
That worked for me on the buggy version of twrp when it wouldn't booy
Sent from my SCH-I545 using Tapatalk 2
twiz0r said:
What version of twrp? And try to go back into recovery and wipe cache and dalvik.
That worked for me on the buggy version of twrp when it wouldn't booy
Sent from my SCH-I545 using Tapatalk 2
Click to expand...
Click to collapse
Not sure what version it was because it's now back to factory recovery. I did go back into it and did a factory wipe and it booted!

TWRP or CWM

Hey guys,
I was just wondering what the general consensus is on which recovery is the most preferred.
I was using TWRP 2.6, but that gave me problems (being stuck on samsung logo everytime my phone rebooted). Reverted back to 2.5.0.2 and it seems to work fine so far. I did try CWM in the past but for some reason my boot loader would get locked and I would have to ODIN back to stock.
So what's your preferred recovery and why?
Thanks.
Exodus885 said:
Hey guys,
I was just wondering what the general consensus is on which recovery is the most preferred.
I was using TWRP 2.6, but that gave me problems (being stuck on samsung logo everytime my phone rebooted). Reverted back to 2.5.0.2 and it seems to work fine so far. I did try CWM in the past but for some reason my boot loader would get locked and I would have to ODIN back to stock.
So what's your preferred recovery and why?
Thanks.
Click to expand...
Click to collapse
I like TWRP. It works well with the new phone and Roms that are coming out plus it is so easy to use. Never liked CWM very much. You did right by reverting to an older version of TWRP I had to do that once.
TWRP... i don't even consider anything else.
Do you guys know why my phone gets stuck on the samsung logo everytime i restart my phone?
Doesn't matter what ROM i use it always happens....
Did you do a factory reset, system wipe, preload wipe, cache wipe, and dalvik wipe? Or try fix permissions from recovery?
If not, go do all of those.
If that doesn't work, something is missing from the system partition that is keeping it from booting. Which means you deleted it. :good:
Dubbsy said:
Did you do a factory reset, system wipe, preload wipe, cache wipe, and dalvik wipe? Or try fix permissions from recovery?
If not, go do all of those.
If that doesn't work, something is missing from the system partition that is keeping it from booting. Which means you deleted it. :good:
Click to expand...
Click to collapse
I did ALL of those, still have the problem.
So.... I just ODIN-ed back to stock and going to root and basically re-do everything -_-

[Q] Boot Loot -- Help!

Here's my situation--I had been running MeanBean for a while and decided to try Kush's KK build (http://forum.xda-developers.com/showthread.php?t=2518211&highlight=loop). I flashed the recovery he linked to, then installed the rom and gapps he linked to. TWRP said everything went successfully. But, when I reboot, the phone just hung at the HTC splash screen. I tried flashing again, downloading fresh and flashing again, wiping the cache, etc. Nothing worked.
So, I decided to go back to my last nandroid of MeanBean. But, after TWRP "successfully" recovered to the latest nandroid, I got stuck in a boot loop. The phone gets through the first part of the boot animation, then freezes and reboots. I tried installing a fresh version of MeanBean, flashing back to TWRP 2.6.3, but nothing has eliminated the boot loop.
I'm s-off and I've never gotten stuck like this before. Anyone have any thoughts?
Reboot to the bootloader and run the command "fastboot erase cache" from a command prompt, then try a fresh install. Are you sure you're S-off?
Sent from my HTC EVO 4G LTE
Thanks for the suggestion. I erased the cache from fastboot and did a fresh install of MeanBean. No luck--still in the same boot loop.
tbhtjd said:
Thanks for the suggestion. I erased the cache from fastboot and did a fresh install of MeanBean. No luck--still in the same boot loop.
Click to expand...
Click to collapse
Have you tried fastboot flashing the boot image from the rom? You shouldn't need to if you're s-off but couldn't hurt if you're still getting boot loops.
Sent from my EVO LTE
Thanks, Fin. I tried fastboot flashing to boot.img separately (which shouldn't be necessary with s-off) after a fresh install, and I'm still in the boot loop. Any other ideas?
Go to recovery, do a full system wipe (data, system, Dalvik & cache) and re-flash the ROM after a fresh download. Really, though, you shouldn't have to wipe cache, since it's under /data.
Sent from my HTC EVO 4G LTE
Okay, did a full wipe, got a fresh download and installed. Still in the same boot loop. I also tried flashing TWRP fresh again. Any other ideas or am I bricked?
tbhtjd said:
Okay, did a full wipe, got a fresh download and installed. Still in the same boot loop. I also tried flashing TWRP fresh again. Any other ideas or am I bricked?
Click to expand...
Click to collapse
What ROM are you trying to flash at this point, and also, which recovery are you using, the one posted in Deck's OP, or one from the TWRP website? If you're trying to flash a 4.4 ROM, use the recovery posted in Deck's OP. If you're trying to flash a different ROM, use the regular TWRP recovery.
Sent from my HTC EVO 4G LTE
FinZ28 said:
What ROM are you trying to flash at this point, and also, which recovery are you using, the one posted in Deck's OP, or one from the TWRP website? If you're trying to flash a 4.4 ROM, use the recovery posted in Deck's OP. If you're trying to flash a different ROM, use the regular TWRP recovery.
Sent from my HTC EVO 4G LTE
Click to expand...
Click to collapse
Trying to flash MeanBean, which is what I've been using previously. I flashed the regular 2.6.3 Jewel TWRP.
It sounds to me like you have the same problem I did. When in recovery and you wipe caches does it say failed? Look into your internal sdcard and if it is empty then it has been erased and corrupted. If so remove your sd card and plug your phone into your pc and mount usb. If it says the card needs to re-format then that is your problem. Re-format your internal sdcard and replace your external sd-card. Flash meanbean and reboot.
fredgar75 said:
It sounds to me like you have the same problem I did. When in recovery and you wipe caches does it say failed? Look into your internal sdcard and if it is empty then it has been erased and corrupted. If so remove your sd card and plug your phone into your pc and mount usb. If it says the card needs to re-format then that is your problem. Re-format your internal sdcard and replace your external sd-card. Flash meanbean and reboot.
Click to expand...
Click to collapse
Hmm, don't think that's it. I've been able to mount internal storage and wipe the cache, etc. just fine.
I'm at a loss at this point as to what the problem might be. If you shoot me a PM I have one last option for you.
Sent from my HTC EVO 4G LTE

PLease help with softbricked S4

Hello all,
I rooted my s4 a while a go and installed TWRP and today I decided to flash a rom so I downloaded it and flashed it but my phone would no longer boot past the first splash screen apparently the rom files were corrupted so I went back into recovery and wiped the phone then restored my backup and now I am stuck on the boot animation which I left for a good 15 min and I also tried pulling the batteries out and still no luck.
Could you please help me fix this??
joeandro said:
Hello all,
I rooted my s4 a while a go and installed TWRP and today I decided to flash a rom so I downloaded it and flashed it but my phone would no longer boot past the first splash screen apparently the rom files were corrupted so I went back into recovery and wiped the phone then restored my backup and now I am stuck on the boot animation which I left for a good 15 min and I also tried pulling the batteries out and still no luck.
Could you please help me fix this??
Click to expand...
Click to collapse
Reboot to TWRP and wipe your System, Data, Dalvik and Cache... Then Boot to Download mode and flash your phone's proper firmware using Odin.. Make sure you have a backup of your installed Apps and their Data..
Hope this helps you
Sami Kabir said:
Reboot to TWRP and wipe your System, Data, Dalvik and Cache... Then Boot to Download mode and flash your phone's proper firmware using Odin.. Make sure you have a backup of your installed Apps and their Data..
Hope this helps you
Click to expand...
Click to collapse
Thanks alot man!! I flashed stock as you said and everything went back to normal. Good thing I had 3 different types of backup so I didn't lose any data.

Stuck in bootloop

Hello guys, so previously I was on nameless rom 4.4, and i wanted to change my recovery from cwm recovery to twrp recovery. So I used this app from the playstore to do it TWRP Manager app. Anyways this app seemed pretty buggy to me, and it was requesting me to install busybox, so i just followed the instructions. Anyways, after it had finished installing twrp, I wanted to test it out. So, when i tried to reboot in recovery, the phone is now stuck on the samsung logo. Cant even boot normally. What should i do now?
lopiop said:
Hello guys, so previously I was on nameless rom 4.4, and i wanted to change my recovery from cwm recovery to twrp recovery. So I used this app from the playstore to do it TWRP Manager app. Anyways this app seemed pretty buggy to me, and it was requesting me to install busybox, so i just followed the instructions. Anyways, after it had finished installing twrp, I wanted to test it out. So, when i tried to reboot in recovery, the phone is now stuck on the samsung logo. Cant even boot normally. What should i do now?
Click to expand...
Click to collapse
Try and reboot into recovery holding up power and home keys then wait galaxy s3 to be displayed then the phone should boot into recovery. From there do a wipe data factory reset, wipe cache and wipe dalvik cache. I would recommended using the latest Clockworkmod recovery as it seems reliable. You can install it using Rom Manager from Play Store, as long as you have root follow the necessary instructions to flash the recovery.
tail.adam said:
Try and reboot into recovery holding up power and home keys then wait galaxy s3 to be displayed then the phone should boot into recovery. From there do a wipe data factory reset, wipe cache and wipe dalvik cache. I would recommended using the latest Clockworkmod recovery as it seems reliable. You can install it using Rom Manager from Play Store, as long as you have root follow the necessary instructions to flash the recovery.
Click to expand...
Click to collapse
i tried to manually reboot into recovery, but it wont enter.
can you use adb sideload if you cannot enter recovery?
lopiop said:
i tried to manually reboot into recovery, but it wont enter.
Click to expand...
Click to collapse
You may need to flash back to stock using Odin then re rooting again.
so i should flash the latest stock rom (4.3) for my region using odin? like this guide http://forum.xda-developers.com/galaxy-s3/general/restore-to-stock-rom-galaxy-s3-i9300-t2187081
fixed using odin, though rather sad that my internal sd got wiped as well
lopiop said:
fixed using odin, though rather sad that my internal sd got wiped as well
Click to expand...
Click to collapse
Glad it's fixed I would recommend not to use apps from playstore to flash recoveries or roms seen nothing but trouble from them.Either use Odin or custom recovery to flash to avoid trouble in the future.

Categories

Resources