I can't seem to get TWRP to work. Every time I try to boot into recovery, it loads the TWRP splash screen, and then proceeds to do nothing. I have to hard-reset the phone to get anything to work.
Unlocked with FreeGee and I've booted into recovery many times before, but it seems to be a problem now. I tried running FreeGee once more in an effort to re-install TWRP or CWM, but it refuses to run, referencing an error with creating backups. Any idea what's wrong?
100% Stock
Maybe try pushing the clockwork touch recovery through adb? I think there's a tutorial somewhere...
That was my next step. Thank you for your input. The original freegee thread by thecubed has the tutorial in it, I believe. I'll have to take a look tomorrow when I'm not so tired.
Try TWRP from the goomanager app if you haven't already. I've been using it fine since it was released.
Sent from my Galaxy Nexus using Tapatalk 2
Related
Ok, I'll try to be short about this.
I did the RegawMOD method and was able to install Liquid Smooth on the phone. (1.45)
When I was going to install an update for that things when odd. (I always back up, reset and wipe before hand)
The update didn't take however I was able to the home screen. As it was weird I went back to restore and the Trwp did not back up correctly. The file was bad.
I was able to get back to the home screen and then setup my phone. I decided to wait for a while until the roms grew up a bit.
Now I was going to install Mean 1.4 today so I downloaded as the post said and installed the radio. Downloaded the rom. When into recovery backup, reset and wiped. When I tried to flash the rom TWRP just started rebooting.
I have tried it several times and also tried to recover and TWRP keeps rebooting. Now I am stuck on the HTC screen.
What do I do now? I feel the recovery is bad.
Any help greatly appreciated.
Maybe a bad recovery flash or corupt download.. Try reflashing recovery through fastboot, download the ROM again, do a FULL wipe and reflash the ROM.
Sent from my ELTE using Tapatalk 2
Thankfully I was able to install an earlier backup so at least I am running now. I have tried using Goo Manger to reinstall twrp 2.2. Just stays stuck at the download.
I haven't used the fastboot method before so I'll have to look that up. I want to get to mean 1.4 as included the OTA fixes because I have the wifi issue. Guess I'll have to wait until I have more time.
Thanks for the help.
Ok so I got goo manager to reflash the recovery.
Now I am on mean 1.4 and very happy. No more WiFi issues either!
Finally as useable as my OG EVO and dandy like this phone was ment to be.
Thanks for the help and thanks developers.
Very cool.
Sent from my EVO using xda app-developers app
My thunderbolt got stuck in boot loop about a week later after flashing Liquid ICS MR3V1. If I attempt to reboot the phone numerous times it will eventually boot up and work fine. The phone will not allow me to get into recovery - it will just go into boot loop once recovery is selected. I did manage to get the phone to go into recovery one time and I wiped everything and installed an infected eternity rom that I have been running for a long time without any issues. I thought I was okay once I flashed this rom but when I restarted the phone it went into the boot loop sequence again. Currently after 15+ attempts at starting the phone I got it to boot up without the SD card. I rooted my thunderbolt through revolutionary...if it matters?
From reading other threads it appears I need to install an RUU? Can I just install a RUU that will not un root my phone or do I need to change my modded Hboot, go back to s on and unroot? I flashed roms numerous times without issues and I always wipe multiple times and I am not sure what happened here. Unfortunately I do not have any backups to revert back to -- since I read flashing an RUU without the proper steps can brick my phone I wanted to seek advice to make sure I do it properly.
ys RUU can help you . just my own thought.
good luck to you :laugh:
xcmtnbiker82 said:
My thunderbolt got stuck in boot loop about a week later after flashing Liquid ICS MR3V1. If I attempt to reboot the phone numerous times it will eventually boot up and work fine. The phone will not allow me to get into recovery - it will just go into boot loop once recovery is selected. I did manage to get the phone to go into recovery one time and I wiped everything and installed an infected eternity rom that I have been running for a long time without any issues. I thought I was okay once I flashed this rom but when I restarted the phone it went into the boot loop sequence again. Currently after 15+ attempts at starting the phone I got it to boot up without the SD card. I rooted my thunderbolt through revolutionary...if it matters?
From reading other threads it appears I need to install an RUU? Can I just install a RUU that will not un root my phone or do I need to change my modded Hboot, go back to s on and unroot? I flashed roms numerous times without issues and I always wipe multiple times and I am not sure what happened here. Unfortunately I do not have any backups to revert back to -- since I read flashing an RUU without the proper steps can brick my phone I wanted to seek advice to make sure I do it properly.
Click to expand...
Click to collapse
Sounds like something is just wrong with you recovery. Try flashing another recovery. Also, IF you're using the boot manager app, it may be acting up. If the boot manager app is on your phone, I'd recommend removing it.
Sent from my ADR6400L using xda premium
RBarnett09 said:
Sounds like something is just wrong with you recovery. Try flashing another recovery. Also, IF you're using the boot manager app, it may be acting up. If the boot manager app is on your phone, I'd recommend removing it.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
Do you mean try re installing cwm? I currently can't get into cwm because it goes into the boot loop sequence. I will try this later tonight and see if it helps. I do not have a boot manager app, I believe when I rooted through revolutionary it modifies hboot? (I have been rooted for over a year now withoutproblems)
xcmtnbiker82 said:
Do you mean try re installing cwm? I currently can't get into cwm because it goes into the boot loop sequence. I will try this later tonight and see if it helps. I do not have a boot manager app, I believe when I rooted through revolutionary it modifies hboot? (I have been rooted for over a year now withoutproblems)
Click to expand...
Click to collapse
No, boot manager is just an application from the play store.
Yes, try downloading cwm recovery again.
Sent from my ADR6400L using xda premium
RBarnett09 said:
No, boot manager is just an application from the play store.
Yes, try downloading cwm recovery again.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
Update - I reinstalled CWM and got the phone into recovery, and did a reset, wiped everything and got stuck in boot loop. I eventually got the phone to boot up and I deleted a couple roms, etc in my download folder. After this was done I power cycled the phone twice without any issues.
So I was pretty determined to get Cm 10.1 running on my Galaxy Note 2 for Verizon. Before hand, I was using TWRP to do all my ROM flashings but when I tried to use CM 10.1, I was told I must use CWM for it to work properly.
Here's my issue, I tried using CWM but it kept on giving me an error and after searching for awhile, it said its because I'm trying to use TWRP instead of CWM. So I flashed CWM and it gave me the same error. Tried both Touch and regular, downgraded and upgraded to the latest CWM but still same error. So I said **** it and installed the lastest TWRP. Then all the ROMs that were giving me issues started to install flawlessly. Then I went to CWM and it gave me the same error.
Am I doing something wrong when I flash CWM? I tried both Odin and APP Update way and both with same results. After using TWRP for awhile, I actually am starting to like the CWM Touch a lot better and I want to switch but not if its going to be giving me problems every flash.
Any insight would be helpful,
and as always to everyone on this forum, thanks
Just make sure you are using the latest version of TWRP 2.5 and you will be fine. You also may need to re-download your ROM file.
Well I am, in a way, stuck using the TWRP right now but I would like to know if I can actually change it to CWM. And if so, how would I go about doing that? because flashing the CWM alone isn't doing anything for me.
wythyntime said:
Well I am, in a way, stuck using the TWRP right now but I would like to know if I can actually change it to CWM. And if so, how would I go about doing that? because flashing the CWM alone isn't doing anything for me.
Click to expand...
Click to collapse
That is the way I have always gone about getting CWM on my phone back when I wanted it. I would just flash over TWRP in TWRP and then reboot system and then reboot back into recovery and it would always be CWM. If it doesnt work for you that way then see if they have a Odin tar and if so follow the instructions to flash it in Odin. They may not have an Odin flashable though, its been a long time since I have used it and on a different phone so....
Sent from my SCH-I605 using XDA Premium HD app
Let me actually rephrase this. (My bad for any confusion)
So if I try to flash a rom using TWRP, it goes through without any issues, even the CM rom. But when I flash CWM and try flashing, it gives me the getdevice-"(t0vzwte)"-not exact".. When researching, I was kept on told its because it is running TWRP. I tell them its CWM and they told me to update my CWM. I actually like CWM a bit better, idk why. but I was just trying to get my phone 100% the way I want it.
I have a TF201 and I have it rooted and unlocked. I tried installing CWM Recovery using some method I found online using fastboot. It seemed to work but whenever I tried to boot into recovery it would just say "Booting recovery kernel image" and stay there. So I restarted the device and went to the playstore and downloaded CWM and flashed it from there. Same thing happened. So I installed TWRP via fastboot and yet again I couldn't boot into recovery. Take in mind I'm a noob so I probably did something wrong. I then went to wipe the data to retry and of course it said the same message. I waited awhile then restarted the device. Now I'm stuck on the Asus splash screen and if I turn it off it just restarts again. Please help me! I clearly did something stupid, I didn't think it would be this much trouble to load a ROM. Thanks!
So can you access fastboot?
Sent from my Galaxy Nexus using xda premium
Makrilli said:
So can you access fastboot?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Nope. No matter what I do I go back to that screen. I let it die and turned it back on, same thing. Upon further research I've come to the conclusion that it's hard bricked so I guess I'll be sending it in. But for future reference, what steps should I take to root, unlock, and install CM10 on it? Because there's so many guides that approach these things in so many ways which is what caused me to mess up. I learned my lesson at least.
So I have been trying to upgrade my LiquidSmooth to the most recent release (the 4.3 release), and I everything seems to flash correctly because I am able to boot initially and set up the phone, however when I reboot the phone it just stays on the "Samsung custom" screen and it does not boot. At first I thought it had something to do with my recovery, so I updated it (TWRP 2.6.3) and then I retried it. No dice. So then did some research and I found somewhere that updating the binaries might fix it. So when I flashed the ROM again I tried updating the binaries, but when it goes into recovery mode it starts updating them, but then stops in the middle and then goes back to the Samsung custom screen and then stays there.
Any ideas? Any at all would be awesome!
Also sorry if this has been answered already, I couldn't find anything on it when I searched for it.
Thanks.
Sorry, I'm not on that Rom, but, I've had pretty much the same problems as you. Twrp just wasn't getting it done. I also have goo manager (which uses twrp), so I went into recovery/twrp using goo manager. It worked. You might try installing goo manager from the play store and going into recovery from it and see if that works for you.
I read this suggestion in another post on here.
Sent from my SCH-I545 using Tapatalk 4
gimpy1 said:
Sorry, I'm not on that Rom, but, I've had pretty much the same problems as you. Twrp just wasn't getting it done. I also have goo manager (which uses twrp), so I went into recovery/twrp using goo manager. It worked. You might try installing goo manager from the play store and going into recovery from it and see if that works for you.
I read this suggestion in another post on here.
Sent from my SCH-I545 using Tapatalk 4
Click to expand...
Click to collapse
So you're saying I should use goo to go into my recovery and then flash the rom? Instead of going straight into TWRP by shutting off my phone and booting recovery? Or do you want me to flash the rom, boot it, and then update the binaries by using goomanager? Thanks!
Long story short. I soft bricked my phone the other day. Did the manual recovery with the buttons and installed a Nan droid backup. I later had trouble installing new/updates roms via twrp manager. I read about the problems with using twrp at times. One solution that was suggested was using goo manager, which I did. And, it did work for me the last couple of times.
Try it and see if it helps you out.
Sent from my SCH-I545 using Tapatalk 4