Okay, so I was trying to install CM 10.2.1, but I got a missing md5 file error, so it didn't work out. I am using TWRP as my recovery, and naturally I wiped everything before flashing, so I then went into some of the recoveries on my sd card to try to restore from those, unfortunately all attempts at restoring have failed,. My next attempt was trying to use the adb sideload feature of TWRP to try to put a new ROM zip file into it, and try to flash that, but TWRP just hangs at "Starting sideload feature" and never really starts it so I am unable to do that. Any ideas on how to get things working? Also why is TWRP unable to do anything correctly? (TWRP v2.6.31)
Phone_BrickerT_T said:
Okay, so I was trying to install CM 10.2.1, but I got a missing md5 file error, so it didn't work out. I am using TWRP as my recovery, and naturally I wiped everything before flashing, so I then went into some of the recoveries on my sd card to try to restore from those, unfortunately all attempts at restoring have failed,. My next attempt was trying to use the adb sideload feature of TWRP to try to put a new ROM zip file into it, and try to flash that, but TWRP just hangs at "Starting sideload feature" and never really starts it so I am unable to do that. Any ideas on how to get things working? Also why is TWRP unable to do anything correctly? (TWRP v2.6.31)
Click to expand...
Click to collapse
Why don't you just take the SD card out of your phone and then put it into your computer and move the ROM file and gapps file to it that way?? Unless you don't have the SD card adapter.
I was having random problems with TWRP myself and got Philz Touch and now I'm good. Just a thought.
Sent from my SCH-I545 using XDA Premium 4 mobile app
TWRP 2.5.0.2 is supposedly the most stable loki recovery for our phone. I would try "downgrading" to that first, If you still have problems with 2.5.0.2 then I would switch to Philz Touch. I had to switch to Philz because TWRP just doesn't like my S4 for some reason. It sucks though, TWRP has a way better UI than CWM.
joshm.1219 said:
TWRP 2.5.0.2 is supposedly the most stable loki recovery for our phone. I would try "downgrading" to that first, If you still have problems with 2.5.0.2 then I would switch to Philz Touch. I had to switch to Philz because TWRP just doesn't like my S4 for some reason. It sucks though, TWRP has a way better UI than CWM.
Click to expand...
Click to collapse
I agree with you there I rather TWRP. Philz takes some getting used to but m actually really liking it now.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Mistertac said:
I agree with you there I rather TWRP. Philz takes some getting used to but m actually really liking it now.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It's just the little things like there's no real graphic interface, it's just a throwback Windows menu, or the fact that dalvik cache needs to be wiped separately, etc.
Related
OK so Im on AOKP milestone 6 with the devil kernel and i went in to recovery to wipe cache and dalvik cache and when i pressed reboot system it goes back to recovery!!!! please help as I really don't want to reflash everything!!! Thanks.
I had this same problem until I flashed TWRP. When I rebooted, it instead loaded the OS, but it still had Devil Recovery. WTF?
Have you tried re-flashing the rom without wiping data?
Sent from my SCH-I500 using xda premium
I can't flash anything because i can't put anything on the sd card because i cant get out of recovery!
ThePlasticBling said:
I can't flash anything because i can't put anything on the sd card because i cant get out of recovery!
Click to expand...
Click to collapse
i have the same problem i cant get out of recovery, cause the rom i flashed is all screwed up
android_noob01 said:
i have the same problem i cant get out of recovery, cause the rom i flashed is all screwed up
Click to expand...
Click to collapse
Try flashing CWM recovery again using Heimdall or Odin. Once it boots into recovery, flash TWRP or another recovery of your choice, then reboot and hopefully you will see your boot animation. That's what I did to get AOKP build 40 to boot again (though strangely enough, it's stuck with Devil recovery even after flashing TWRP). Hope this helps you guys out. And be sure to make backups!
UndeadSquirrel said:
Try flashing CWM recovery again using Heimdall or Odin. Once it boots into recovery, flash TWRP or another recovery of your choice, then reboot and hopefully you will see your boot animation. That's what I did to get AOKP build 40 to boot again (though strangely enough, it's stuck with Devil recovery even after flashing TWRP). Hope this helps you guys out. And be sure to make backups!
Click to expand...
Click to collapse
Again, how can i put twrp on my sd card if i'm stuck in recovery? Is there a link for an odin version of twrp
You should be able to mount your SD card in recovery anyway. If not, take it out and insert it into an adapter to plug into your computer. I don't know if there's an Odin version of TWRP, I flashed it in CWM recovery.
I would read droid styles guide first if you have not yet as it has all the answers you will need. You just need to read through it and following the directions.
Sent from my SCH-R530U
how do i mount my sd card and open it on my pc in recovery?
If you're using CWM, it's under Advanced or Mounts and Storage. Plug in the USB cable like you normally would.
UndeadSquirrel said:
If you're using CWM, it's under Advanced or Mounts and Storage. Plug in the USB cable like you normally would.
Click to expand...
Click to collapse
I try to install twrp but it says installation aborted. I'm really starting to get sick of this phone and its stability issues.
You got the zip, right? It's in the Fascinate development section of the forums.
There is nothing wrong with the phone. I don't understand why you can't just Odin back to stock and start over. With the amount of time you have been stuck in recovery you could have fixed it by now. It you could follow droid styles guide to get out of the recovery loop without going back to stock. Something tells me you really just want a new phone...am I close???
Sent from my SCH-R530U
shelby04861 said:
There is nothing wrong with the phone. I don't understand why you can't just Odin back to stock and start over. With the amount of time you have been stuck in recovery you could have fixed it by now. It you could follow droid styles guide to get out of the recovery loop without going back to stock. Something tells me you really just want a new phone...am I close???
Sent from my SCH-R530U
Click to expand...
Click to collapse
Sent from my SCH-R530U
Don't you belong in a different section?
Anyway, sorry for getting snippy, I was just really tired and frustrated. I did use the .zip from the forums.
If you've already tried Heimdall-flashing CWM again, and that didn't work, then I suggest you Odin back to stock as shelby suggested. If you haven't made a nandroid already, do so, then revert back to stock and start from scratch. You can try restoring your nandroid once you're no longer stuck in recovery.
ThePlasticBling said:
Sent from my SCH-R530U
Don't you belong in a different section?
Anyway, sorry for getting snippy, I was just really tired and frustrated. I did use the .zip from the forums.
Click to expand...
Click to collapse
I have a mez and I just got the sgs3 a little while ago. You need to check out section 8 or 9 I think of the guide. It tells you exactly how to get out of your situation.
Sent from my SCH-I500 using Tapatalk 2
There's also a topic about the "three-finger recovery boot loop" fix. You could try that.
I flashed a half-assed version of twrp from goo manager and it doesn't work right. It's not seeing the right partitions or something. But anyways I need to re flash the correct one anyone know how? Also I'm running Linux not windows.
I did the same thing the other day on my S3. I went and downloaded CWM and then used the messed up TWRP to flash CWM. Everything turned out fine with my S3 so you might try that. Something is really screwed up with Goo cause after I installed TWRP with it it was showing folders I had deleted before I even downloaded TWRP.
Also something else that may be safer, couldn't you just use Casual to re flash TWRP and then download the latest flashable TWRP version and flash it?
Sent from my SCH-I605 using XDA Premium HD app
I am on Beans Build 12 right now and everytime I try to install ANYTHING through TWRP it fails.
Weird enough, the only thing that won't fail is if i reinstall Beans Build 12. When I first installed it I chose the SD Card swap option, if that makes any difference to those who may know what the problem is.
I've had this happen a couple times.
After it fails, try using the reboot to recovery option and try installing again after it reboots to twrp.
Also, you could try moving the file to internal sd and see if it installs from there.
Which version of twrp do you have?
I had the wrong version at first. Goomanager helped a lot.
Sent from my SCH-I605 using xda app-developers app
Or you can try CWM, although flashing that might fail in TWRP as well. I've had issues with TWRP over the course of time, but never with CWM.
Sent From My Beans Powered Note2
Sloopdawgg said:
I am on Beans Build 12 right now and everytime I try to install ANYTHING through TWRP it fails.
Weird enough, the only thing that won't fail is if i reinstall Beans Build 12. When I first installed it I chose the SD Card swap option, if that makes any difference to those who may know what the problem is.
Click to expand...
Click to collapse
Use goo manager to update twrp.
bigtoysrock said:
Use goo manager to update twrp.
Click to expand...
Click to collapse
How do you update TWRP through goo manager? Sorry fairly new to this , I got the fail also when trying to install the beans 12 build.
GooManager => settings => install openRecoveryScript
Alright I have been having some problems with my Note 2 that would be for instance I used to use TWRP but know I use ClockWorkMod Recovery and I don't want to anymore but I try to switch back and it said it did but when I go into recovery mode it just goes into ClockWorkMod Recovery. Also another problem I am having would be I am trying to flash over a new rom (Jedix17) but when I put it on my sd card it says its on there on my computer but when I go into CWMR it nots even in there.
Anyways or ideas that you guys can think of to fix this would be greatly appreciated.
How are you installing TWRP? I would say ODIN or adb it. Also CWM is not seeing which SD, internal or external? Put TWRP on internal and try that if you have not already.
Just download goo manager and install the TWRP recovery through that.
Sent from my SCH-I605 using xda app-developers app
05Warrior said:
Just download goo manager and install the TWRP recovery through that.
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
Thought it was pulled from goo cause of having to have the correct boot loader? I know it said my device was not compatible or couldn't find it for my device. Pretty sure that it said that on the twrp page.
I'm running CM 11 nightlies, usually the latest.. I've been running CWM 6.0.4.4 for as long as I can remember after initially rooting/loki patching my phone.
Last week, Rom manager notified me that there was an update to CWM, 6.0.4.7. I thought "cool" - and I flashed it via Rom manager, which reported this was a success.
However, whenever I rebooted into recovery, I still had CWM 6.0.4.4. I tried again, fail. Decided to clean flash my next nightly and try again. Same thing. Could not get Rom manager to update.
I flashed over to Twrp using goo manager which worked fine. I used Twrp to flash over to Philz touch which worked fine.. anytime I use Rom manager now though, it seemingly does nothing even though it reports a success. For example, if I am on TWRP and use rom manager to flash the latest CWM, I'll be met with a success but a reboot into recovery leaves me still with TWRP and no CWM.
I guess I'm just wondering if anyone can help me figure out what's going on -- I know I've seen others at least in the CM forum post about Rom manager acting similarly, but I also hear reports that it works fine for others. Ultimately I just ended up making a 6.0.4.7 flashable zip of my own to upgrade but I'd rather get things figured out vs make a new flashable zip anytime an updated version of CWM comes out.
vanberge said:
I'm running CM 11 nightlies, usually the latest.. I've been running CWM 6.0.4.4 for as long as I can remember after initially rooting/loki patching my phone.
Last week, Rom manager notified me that there was an update to CWM, 6.0.4.7. I thought "cool" - and I flashed it via Rom manager, which reported this was a success.
However, whenever I rebooted into recovery, I still had CWM 6.0.4.4. I tried again, fail. Decided to clean flash my next nightly and try again. Same thing. Could not get Rom manager to update.
I flashed over to Twrp using goo manager which worked fine. I used Twrp to flash over to Philz touch which worked fine.. anytime I use Rom manager now though, it seemingly does nothing even though it reports a success. For example, if I am on TWRP and use rom manager to flash the latest CWM, I'll be met with a success but a reboot into recovery leaves me still with TWRP and no CWM.
I guess I'm just wondering if anyone can help me figure out what's going on -- I know I've seen others at least in the CM forum post about Rom manager acting similarly, but I also hear reports that it works fine for others. Ultimately I just ended up making a 6.0.4.7 flashable zip of my own to upgrade but I'd rather get things figured out vs make a new flashable zip anytime an updated version of CWM comes out.
Click to expand...
Click to collapse
get the latest cwm 6.4.7 zip and flash through philz recovery make sure to apply auto loki patching (i think thats already checked never hurts to make sure though) hit power options and reboot recovery. thats my thought and u should have on screen cwm 6.4.7
FordNate said:
get the latest cwm 6.4.7 zip and flash through philz recovery make sure to apply auto loki patching (i think thats already checked never hurts to make sure though) hit power options and reboot recovery. thats my thought and u should have on screen cwm 6.4.7
Click to expand...
Click to collapse
Where do you get the 6.0.4.7 zip? I've only been able to find the .img file on the rom manager/cwm website...
Going back to my htc days n adb using it was fastboot flash flash {recovery name}.img. maybe using something like flashimgui or flashify.. just thoughts of course other than that u would need to convert to a zip file
FordNate said:
Going back to my htc days n adb using it was fastboot flash flash {recovery name}.img. maybe using something like flashimgui or flashify.. just thoughts of course other than that u would need to convert to a zip file
Click to expand...
Click to collapse
Nice! Flashify does it beautifully. CWM touch even. I cannot believe I'm just now trying this app!
What's been improved between 6.0.4.4 & 6.04.7?
Sent from my HTC6600LVW using XDA Premium 4 mobile app
joshm.1219 said:
What's been improved between 6.0.4.4 & 6.04.7?
Sent from my HTC6600LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Nothing immediately apparent, I'm just OCD about running the latest/greatest.