i have this problem with twrp .i had to factory reset my phone rerooted installed twrp but when i try to install rom from sd card twrp shuts down and starts back up i have i337m and twrp 2.7.0
ron31 said:
i have this problem with twrp .i had to factory reset my phone rerooted installed twrp but when i try to install rom from sd card twrp shuts down and starts back up i have i337m and twrp 2.7.0
Click to expand...
Click to collapse
Best option is to flash an earlier version of twrp, some people are having problems with the latest.
ronnie498 said:
Best option is to flash an earlier version of twrp, some people are having problems with the latest.
Click to expand...
Click to collapse
2.6 works fine on the i337m....that is the version I am running
Gage_Hero said:
2.6 works fine on the i337m....that is the version I am running
Click to expand...
Click to collapse
How do you install twrp 2.6 with goomanager it keeps bringing 2.7
ron31 said:
How do you install twrp 2.6 with goomanager it keeps bringing 2.7
Click to expand...
Click to collapse
Many people have had a lot of success with this. Flash it in your current version of twrp.
http://forum.xda-developers.com/showthread.php?t=2441196
Sent from my Nexus 5
ron31 said:
How do you install twrp 2.6 with goomanager it keeps bringing 2.7
Click to expand...
Click to collapse
You should be able to find an Odin file to flash through Odin, I don't remember if goomanager allows you to search previous versions, just a thought...
Related
Hey all,
Just rooted my Galaxy S4 yesterday on AT&T. Rooted it using tLoki + TWRP + Motochopper CASUAL method. I have TWRP recovery installed and can get to that no problem. I have the following build of Cyanogen flashed:
cm_jflteatt-userdebug 4.3 JLS36G f65925b07a test-keys
CyanogenMod version:
10.2-2013007-NIGHTLY-jflteatt
Baseband: I337UCUAMDL
Phone works flawlessly after the flash, but as soon as I power off or reboot, it just hangs at the Samsung Galaxy S4 screen and doesn't do anything. Only way out is to boot into recovery wipe and re-flash the Cyanogen ROM.
Any thoughts? I don't even know where to start...
a.stalker22 said:
Hey all,
Just rooted my Galaxy S4 yesterday on AT&T. Rooted it using tLoki + TWRP + Motochopper CASUAL method. I have TWRP recovery installed and can get to that no problem. I have the following build of Cyanogen flashed:
cm_jflteatt-userdebug 4.3 JLS36G f65925b07a test-keys
CyanogenMod version:
10.2-2013007-NIGHTLY-jflteatt
Baseband: I337UCUAMDL
Phone works flawlessly after the flash, but as soon as I power off or reboot, it just hangs at the Samsung Galaxy S4 screen and doesn't do anything. Only way out is to boot into recovery wipe and re-flash the Cyanogen ROM.
Any thoughts? I don't even know where to start...
Click to expand...
Click to collapse
Use twrp 2.5.0.2. I'm guessing you're using 2.6
jd1639 said:
Use twrp 2.5.0.2. I'm guessing you're using 2.6
Click to expand...
Click to collapse
No, I am using 2.5.0.2 just verified.
a.stalker22 said:
No, I am using 2.5.0.2 just verified.
Click to expand...
Click to collapse
This has been an issue on other devices. Flashing with cwm seems to have consistently worked. Once you get it up and running you can flash back to twrp for your nandroids. I've had to do this on my i727.
jd1639 said:
This has been an issue on other devices. Flashing with cwm seems to have consistently worked. Once you get it up and running you can flash back to twrp for your nandroids. I've had to do this on my i727.
Click to expand...
Click to collapse
Thought maybe it was a ROM problem, but any I've tried have this same problem.
How do I go about replacing twrp with cwm? I have no idea how to replace the recovery. Any direction would be much appreciated :good:
a.stalker22 said:
Thought maybe it was a ROM problem, but any I've tried have this same problem.
How do I go about replacing twrp with cwm? I have no idea how to replace the recovery. Any direction would be much appreciated :good:
Click to expand...
Click to collapse
This is already a known issue for Cyanogenmod 10.1 and 10.2. Using CWM will help it a little bit, but will still occur. There is no fix.
emckai said:
This is already a known issue for Cyanogenmod 10.1 and 10.2. Using CWM will help it a little bit, but will still occur. There is no fix.
Click to expand...
Click to collapse
But it's not just happening with CM...it's any ROM that I try to use. Boots up fine the first time, but after a reboot...no luck Frozen on the Samsung screen. How do I flash cwm over my current recovery?
a.stalker22 said:
But it's not just happening with CM...it's any ROM that I try to use. Boots up fine the first time, but after a reboot...no luck Frozen on the Samsung screen. How do I flash cwm over my current recovery?
Click to expand...
Click to collapse
Get a cwm zip file and flash it like you would a rom but don't do any wipes. It'll flash on top of twrp and replace it. Do the same thing to go back to twrp.
a.stalker22 said:
But it's not just happening with CM...it's any ROM that I try to use. Boots up fine the first time, but after a reboot...no luck Frozen on the Samsung screen. How do I flash cwm over my current recovery?
Click to expand...
Click to collapse
Just download ROM Manager and flash CWM.
Which ROMs have you tried so far? Are they based off of CM?
Try to clear the delvik cache and the cache. I believe it will boot normal then
Sent from my SAMSUNG-SM-N900A using Tapatalk 5
emckai said:
Just download ROM Manager and flash CWM.
Which ROMs have you tried so far? Are they based off of CM?
Click to expand...
Click to collapse
No, they're not all based off of CWM.
The last few I tried were BeanStalk and Task650 AOKP. The Task650AOKP booted up fine the first time, I did a reboot and then it was permanently stuck at the Samsung Galaxy S4 screen, even after I cleared cache's and factory reset with a re-flash. I tried that several times and still couldn'y get back in, so luckily I had a backup of my original rooted config and that booted up.
I did install rom manger just now and flashed cwm recovery...just afraid to reboot..haha. I wish I knew what the problem could be here...
Hi. How do I removed / uninstall Philz Touch 5 because I want to try TWRP 2.6.3.0. I had installed Goo Manager and installed TWRP but rebooting to Recovery, it will reboot to Philz TOuch's recovery.
Thank you.
flash this twrp 2.5.0.3 zip in recovery and then reboot recovery. see if it sticks. if it does, stay on that version. i've heard it works better than the newer releases. cheers
Just flash TWRP in your recovery
Sent from my SAMSUNG-SM-N900A using Tapatalk 5
I did flash the 2.6.3.0 using Goo Manager but when in rebooted in REcovery it was still the Philz Touch that opened.
Thank you.
agent929 said:
Just flash TWRP in your recovery
Sent from my SAMSUNG-SM-N900A using Tapatalk 5
Click to expand...
Click to collapse
qwer43 said:
I did flash the 2.6.3.0 using Goo Manager but when in rebooted in REcovery it was still the Philz Touch that opened.
Thank you.
Click to expand...
Click to collapse
did the flashable zip work?
qwer43 said:
I did flash the 2.6.3.0 using Goo Manager but when in rebooted in REcovery it was still the Philz Touch that opened.
Thank you.
Click to expand...
Click to collapse
You can't use that to do it. You have to take that zip file that beerdroid posted and save it to your sd card. Save it in the root so it's easy to find. You have to boot into Philz and flash that zip.
I don't ever recommend the Goo Manager. There has been so many people that has had problems with it, especially after flashing a new ROM. It's not because it's a bad program, it's because sometimes when you flash a new ROM the prop changes so it tricks Goo Manager.
Philz Touch
Agent said:
You can't use that to do it. You have to take that zip file that beerdroid posted and save it to your sd card. Save it in the root so it's easy to find. You have to boot into Philz and flash that zip.
I don't ever recommend the Goo Manager. There has been so many people that has had problems with it, especially after flashing a new ROM. It's not because it's a bad program, it's because sometimes when you flash a new ROM the prop changes so it tricks Goo Manager.
Click to expand...
Click to collapse
I'm experiencing the same thing. TWRP wasn't able to load the Cyanogenmod SNAPSHOT, but Philz did and I don't have WiFi just like when I loaded the unstable version so I'm trying to delete Philz and it won't go away. Why did my TWRP disappear? arghhh...... I wish I had a Nexus 5.
qwer43 said:
Hi. How do I removed / uninstall Philz Touch 5 because I want to try TWRP 2.6.3.0. I had installed Goo Manager and installed TWRP but rebooting to Recovery, it will reboot to Philz TOuch's recovery.
Thank you.
Click to expand...
Click to collapse
I downloaded a new firmware and flashed my phone and it worked.
Plz try flashing ur phone with a new firmware '
Kesh421 said:
I downloaded a new firmware and flashed my phone and it worked.
Plz try flashing ur phone with a new firmware '
Click to expand...
Click to collapse
Thanks for the timely information, lol
Sent from my Nexus 9 using XDA Free mobile app
hey guys plizz help me,im using the philz touch recovery on my Micromax a120 for a decent long time,last night i go to the Advanced option then to the GUI preferences,then Change Background option since i never bother to go there before,and in the background change options,im not very sure,but i think it was the Reset Koush Background option that i've selected,and now whenever i go into recovery the screen doesn't show me any option but a complete pink-ish screen,how do i reset my settings now,can anyone give me some suggestions
i'm writing here because no one know how help me:
my s4 boot only 4.2 roms, if i install any 4.3 or 4.4 rom will result in a cm logo bootloop
i have latest cwr, i always wipe all data (clean rom) and cache/dalvik
how can i solve this? please don't close this topic
djsolidsnake86 said:
i'm writing here because no one know how help me:
my s4 boot only 4.2 roms, if i install any 4.3 or 4.4 rom will result in a cm logo bootloop
i have latest cwr, i always wipe all data (clean rom) and cache/dalvik
how can i solve this? please don't close this topic
Click to expand...
Click to collapse
did u tried any official firmware with odin ? flash any official rom with odin and try again . i think something wrong with ur bootloader
ne0__ said:
did u tried any official firmware with odin ? flash any official rom with odin and try again . i think something wrong with ur bootloader
Click to expand...
Click to collapse
not yet, do you suggest me to flash 4.2 or 4.3? where can i find official firmwares?
update your recovery my friend
N10AP said:
update your recovery my friend
Click to expand...
Click to collapse
is already updated!
djsolidsnake86 said:
is already updated!
Click to expand...
Click to collapse
hmmm... Which recovery are you using? Are you clearing cache and dalvik before and after flashing?
N10AP said:
hmmm... Which recovery are you using? Are you clearing cache and dalvik before and after flashing?
Click to expand...
Click to collapse
latest philz touch, yes i clear all but no luck! only cm 4.2 start!
N10AP said:
hmmm... Which recovery are you using? Are you clearing cache and dalvik before and after flashing?
Click to expand...
Click to collapse
if you wont cm11 use latest cwm ,else with google edition or other aosp 4.4 use philz
djsolidsnake86 said:
latest philz touch, yes i clear all but no luck! only cm 4.2 start!
Click to expand...
Click to collapse
install rom manager and download / flash latest CWM for jfltexx (international which I`m assuming is what you have) and try again
so...
1) Install 4.2, get it running
2) Root device if you haven`t rooted it
3) Download Rom manager from play store
4) Flash recovery for jfltexx (it is only listed after you press menu and view all devices / recoveries)
ne0__ said:
did u tried any official firmware with odin ? flash any official rom with odin and try again . i think something wrong with ur bootloader
Click to expand...
Click to collapse
oke first try with phliz recovery if not than flash a official firmware with odin.
for official firmwares Here
if u want new bootloader install lastest MK or ML series
if u want to stay on old bootloader than install your own 4.2
ne0__ said:
oke first try with phliz recovery if not than flash a official firmware with odin.
for official firmwares Here
if u want new bootloader install lastest MK or ML series
if u want to stay on old bootloader than install your own 4.2
Click to expand...
Click to collapse
what are the differences?
DONT ODIN FIRMWARE FLASH 4.3!!! YOU WILL UPGRADE YOUR BOOTLOADER!!! KNOX BAD!!!
Try the official CWM from ROM manager. Trust me.
Go into ODIN mode and if you see knox then you are on new bootloader.
If not, don`t flash a 4.3 image with ODIN. You will not be able to go back to 4.2 easily
N10AP said:
install rom manager and download / flash latest CWM for jfltexx (international which I`m assuming is what you have) and try again
so...
1) Install 4.2, get it running
2) Root device if you haven`t rooted it
3) Download Rom manager from play store
4) Flash recovery for jfltexx (it is only listed after you press menu and view all devices / recoveries)
Click to expand...
Click to collapse
now i'm running miui 4.2, is ok? device is rooted
djsolidsnake86 said:
now i'm running miui 4.2, is ok? device is rooted
Click to expand...
Click to collapse
yes its fine as log as rom manager can get root permissions on your MIUI
N10AP said:
DONT ODIN FIRMWARE FLASH 4.3!!! YOU WILL UPGRADE YOUR BOOTLOADER!!! KNOX BAD!!!
Try the official CWM from ROM manager. Trust me.
Click to expand...
Click to collapse
new bootloader but deodexed roms i was using 4.3 deodexed rom with new bootloader and i was happy with it today i just flashed 4.4 google edition and theres no problem my device is flying )
N10AP said:
yes its fine as log as rom manager can get root permissions on your MIUI
Click to expand...
Click to collapse
yes, ok rom manager installed, now what next?
my recovery installed is 6.0.4.4 by philz touch
djsolidsnake86 said:
yes, ok rom manager installed, now what next?
Click to expand...
Click to collapse
go to recovery setup...
install or update clockword mod recovery
install recommended recovery
flash clockwork mod recovery. should ask for root permissions. success.
reboot to recovery and try again clearing cache and dalvik
N10AP said:
go to recovery setup...
install or update clockword mod recovery
install recommended recovery
flash clockwork mod recovery. should ask for root permissions. success.
reboot to recovery and try again clearing cache and dalvik
Click to expand...
Click to collapse
ok installed cmr, wiped all data anche cache, installed cm11+gapps and (as always) cm bootloop!
djsolidsnake86 said:
ok installed cmr, wiped all data anche cache, installed cm11+gapps and (as always) cm bootloop!
Click to expand...
Click to collapse
ok. might sound strange but check your battery for swelling
So yesterday I flashed TWRP instead of CWM and later on I tried to wipe the cache/dalvik but screwed up and accidentally ran a factory reset. No big deal I have a recovery I can use... well... TWRP can't use CWM recoveries. okay... we'll just flash CWM back on.
That's where the problem comes in no matter how many times or how I flash CWM it always goes into TWRP I've flashed using ODIN 3.07, 3.09 and using ROM manager on my phone.
What do I have to do to force CWM to flash?
aphoticinullity said:
So yesterday I flashed TWRP instead of CWM and later on I tried to wipe the cache/dalvik but screwed up and accidentally ran a factory reset. No big deal I have a recovery I can use... well... TWRP can't use CWM recoveries. okay... we'll just flash CWM back on.
That's where the problem comes in no matter how many times or how I flash CWM it always goes into TWRP I've flashed using ODIN 3.07, 3.09 and using ROM manager on my phone.
What do I have to do to force CWM to flash?
Click to expand...
Click to collapse
You might need to find a flashable zip form of it.
Sent from my SGH-I337 running BlackBox 3.0
DeadlySin9 said:
You might need to find a flashable zip form of it.
Sent from my SGH-I337 running BlackBox 3.0
Click to expand...
Click to collapse
thank you! got it!
for future people, here is what I used
http://forum.xda-developers.com/showthread.php?t=2322682
Hey I have this huge problem with TWRP. I wiped the usual files, and then tried to flash a rom. It said ERROR: failed to update binary zip or something like that. FYI, I installed Multi Boot and have two roms installed. I tried uninstalling the secondary rom and wiped the phone, but still no luck. I even used multiboot cleaner and it still says the samething. Help?
Which version of twrp is on the phone?
Use another recovery
use CWM its way better than TWRP!
wajid iqbal said:
use CWM its way better than TWRP!
Click to expand...
Click to collapse
Thats not true!
TWRP 2.8.7.0 is running perfectly till Android 6 roms and all!! TW-Roms,so use this!You can use Flashify to install.
cheers
audit13 said:
Which version of twrp is on the phone?
Click to expand...
Click to collapse
My Current recovery is TWRP 2.8.6.0
Use 2.8.7 version of twrp. Many ROMs need twrp.
audit13 said:
Use 2.8.7 version of twrp. Many ROMs need twrp.
Click to expand...
Click to collapse
how can i get it?
Wow...
I installed the new TWRP and it still doesn't work. This started to happened when I was creating a backup with my OTG then i canceled it, and did another backup in the internal storage of my phone.
You are using twrp 2.8.7?