So I have installed the 6.0 CWRecovery in my Note 3 (hlr) in order to install the newest CWM12(7.8), I managed to install the CWRecovery touch 6.0 using the app known as Flashfy, it worked fine and so I managed to install CM mod 12 (I have some problem with the stock Music app, which crashes all the time). I saw a new update (8.1) and I wanted to update it again, but the boot does not load the recovery mod and thus, it just keep on a recovery boot loop. The only way to get out of such loop is to load the download mode, and then it boots the CW12. I have tried reinstalling the recovery mode using the flashfy and rom manager, but it does not work at all, even when using the said programs to flash the ROM itself. What should I do? Thanks!
Leminur said:
So I have installed the 6.0 CWRecovery in my Note 3 (hlr) in order to install the newest CWM12(7.8), I managed to install the CWRecovery touch 6.0 using the app known as Flashfy, it worked fine and so I managed to install CM mod 12 (I have some problem with the stock Music app, which crashes all the time). I saw a new update (8.1) and I wanted to update it again, but the boot does not load the recovery mod and thus, it just keep on a recovery boot loop. The only way to get out of such loop is to load the download mode, and then it boots the CW12. I have tried reinstalling the recovery mode using the flashfy and rom manager, but it does not work at all, even when using the said programs to flash the ROM itself. What should I do? Thanks!
Click to expand...
Click to collapse
Try downloading the TWRP...tar file for your phone (http://teamw.in/project/twrp2 - click top right for your phone) and flash it using Odin - it will give you TWRP Recovery.
Also go to Chainfire's site and get SuperSU.zip (http://download.chainfire.eu/695/SuperSU/UPDATE-SuperSU-v2.45.zip) so you can flash it in Recovery.
I flash the ROM, then GApps (I use PA version) then SuperSU in one flash session, then I Restore my Data partition from my nandroid backup and always good to go after that.
http://forum.xda-developers.com/showthread.php?t=3060970
Sent from my SM-N900 using XDA Free mobile app
Related
Hello,
my phone was working like a charm with cm 7.1 , Siyah Kernel, clockworkmod recovery mod 5.0.2.
I decided to upgrade my Siyah Kernel from 2.0 beta 8 to v2.
I used the QR code from Xda forum. Phone downloaded kernel, then once download finished, opened Rom Manager app, then invite me to install the new .zip file.
I usually do it manually, in rebooting in recovery and installing the .zip file in recovery mod, but I wanted to try this way.
Now my phone doesn't boot, hanf on on Samsung logo. No recovery mod available, only download mod.
Tried to reinstall ClockworkMode recovery 5 with Odin, but nothing happens. The yelow box stays yellow, and message hans on at Setup connection.
I alos tried to flash P-SBL.tar with odin, but it failed.
So, what can I do??
EDIT : Issue solved. Retried with Odin and ClockworkMod. This time I booted in recovery, phone booted in it and installed new kernel, and the booted in cm 7.1. I do think this issue came from Rom Manager.
So far as i know, using rom manager with the S2 is a mistake.
The S2 dosnt like rom manager much, and it can end up in a lot of problems up to a semi bricked phone.
Glad you solved it , but i recommend to avoid rom manager for now
Hi,
I'm currently running CyanogenMod KitKat version with ClockWorkMod. Since the rom has several bugs and for the past few months they haven't published any updates to my Galaxy s4 I9505, I've decided to switch to WanamLite.
There I found out I need TWRP recovery so I went ahead and downloaded GooManager which installed an outdated version, as I've found out.
I tried wiping my internal storage as recommended but the recovery couldn't mount any of my partitions.
So now CyanogenMod won't boot. I know this issue is fixed in the updated version of TWRP but I'm not sure how to update it without the phone booting (Odin perhaps? It doesn't recognize it currently... Should I move to download mode for it to be detected?)
Anyways, I'm kind of stuck as of now. Any help would be very much appreciated!
Btw I have a question, what's the difference between using Odin 1.85 and 3.09? Why do people still use the old version?
Thanks in advance!!
Neta
Edit:
Alright, now I can't get into recovery either. When I try, I can see the Samsung logo and there's "recovery" written in the top left but then it just restarts again into the same logo without "recovery". I'm starting to lose my cool now. Anyone have any ideas?
Try flashing latest stock through download mode and see if it boots.
Sent from my GT-I9506 using Tapatalk
Flash this recovery through odin. It's TWRP 2.6.3.1. Worked alwys for me.:fingers-crossed:
https://db.tt/SwLvOrZl
Uncheck auto-reboot in Odin.
Thank guys
I got freaked out and just did everything I could to make the phone working again.
I found a thread on XDA explaining how to return your phone to stock version, so I followed it, rooted with auto root, (btw Odin didn't recognize my phone because I used the front usb... how annoying!), then flashed the latest TWRP (2.7.0.1, not 2.6.x.x as GooManager downloaded for me), then booted to recovery and flashed WanamLite.
Everything is working now!
Except one thing - I'm still not able to access recovery mode through physical buttons, only using boot apps. Is this a kernel issue?
Could be some incompatibility since CyanogenMod uses it's own kernel and CWM recovery.
The recovery itself is working fine, but when I try to access it using buttons it shows the Samsung logo with the recovery on the top left, and then reboots again to normal boot.
What do you think?
Thanks!
Hello,
I've rooted my own note 3 and flashed Temaseks unofficial cm 12 rom. Everything works perfect so I decided to do the same thing for my father. It all went well, first I rooted his phone, then I flashed CWM and flashed cm 12 by temasek. The rom works fine but I forget to install the Gapps. So I tried to install Gapps but I got an error "Failure Status 6". I googled on that error and someone told it has to do something with CWM. I tried to flash a different version of CWM but now I can't reboot into recovery mode anymore. So I can't flash anything.
I flashed another version of CWM but this one also doesn't work. Whenever I try to boot the phone into recovery mode, the blue line shows up. Rebooting into recovery mode, but after a few secs, the phone just boots the normal way. Is there anyone that can help me to get CWM back to work? In the mean time I'll try to flash TWRP by Odin.
Thanks in advance!
So I flashed latest version of CWM: Buildversion; 6.13.0, CWM Base Version V6.0.4.7. I can reboot into recovery now but still can't install Google Apps due to failure status 6. On my own Phone I run a different version of CWM, but when I try to flash it, the phone won't boot into recovery mode anymore. It only boots into recovery when I flash this V6.0.4.7 . How can I get rid of this version and flash an older version of CWM?
You'll probably have to Odin back to stock and start over...
Morningstar said:
You'll probably have to Odin back to stock and start over...
Click to expand...
Click to collapse
You mean If there is no other way to get the Google Apps on the phone, I have to go back to stock. I did make a backup with CWM on the while it was running custom firmware. Now I have 4 files on my comuter, 3.tar and 1.md5 . If I recover them, I will still have this not working CWM version on my phone right? Isn't there a easier way to delete CWM, can I flash TWRP over CWM and see if it will install these Gapps?
Yeah, you should be able to flash TWRP over it. TWRP is much better anyway, in my opinion. Once you get the recovery issue sorted, I really wouldn't't recommend trying to flash just the gapps. It would probably work, but it's also quite likely to cause some weird issues. It's always best to flash gapps immediately after flashing a ROM, without leaving recovery.
I would flash TWRP, wipe everything but your internal SD, re-flash the ROM, flash the gapps, and everything should be cherry.
Edit: here is the link to download TWRP.
Morningstar said:
Yeah, you should be able to flash TWRP over it. TWRP is much better anyway, in my opinion. Once you get the recovery issue sorted, I really wouldn't't recommend trying to flash just the gapps. It would probably work, but it's also quite likely to cause some weird issues. It's always best to flash gapps immediately after flashing a ROM, without leaving recovery.
I would flash TWRP, wipe everything but your internal SD, re-flash the ROM, flash the gapps, and everything should be cherry.
Edit: here is the link to download TWRP.
Click to expand...
Click to collapse
I appreciate your effort, thank you. The recovery issue is solved. I flashed Chainfires Root script and that installed the stock recovery. However, when I tried to install and older CWM version I got back in the recovery reboot cycle. But once I installed the latest CWM it booted in recovery. So I flashed Chainfires Root once again and had the stock recovery back. From there on I tried to install TWRP but got the recovery boot cycle again. My phone is now running android 5.0.2 and I think that's the problem.... :S I'll try again to flash Chainfires Root script to get the stock recovery back. From there on I will try to flash the link you gave to me with Odin and hope that will fix it. Do you have any ideas on what I'm doing wrong?
Your version of TWRP works so far. It reboots into RecoveryMode. Now I'll wipe and try to install Temaseks Cm 12 followed by Gapps! Thanks so far!
Okay, it's solved. Can't thank you enough for you help. Bless you!!
No problem. Glad you got it figured out!
[emoji106]
I'm running Optimized CyanogenMod 12.1 rom from the Jflte DevConnection Team.
After trying to flash the last OTA update for the rom my TWRP recovery has become unresponsive, stuck on its boot screen (TWRP logo).
What happen was that I downloaded the update via the OTA app and then pressed the Install button to reboot the device and flash the update.
But after the device booted into the recovery TWRP never opened up a process window or its menu but just stayed on the boot screen appearing to do nothing. It did not respond to any commands (buttons or touch). I waited half an hour before forcing a shot down.
But at this point I was in a manual boot loop, the device would boot into recovery instead of the Rom and I was unable to use the phone.
I managed to flash TWRP again using Heimdall which allowed me to boot again into the Rom, but if I tried manually going into recovery it was still unresponsive.
I tried flashing older version of TWRP using Flashy app, I clicked on a option in the app to reboot into recovery. This cost the origin boot loop problem again.
I than flashed CyanogenMod Recovery and was able to boot into that.
Tried once more to flash TWRP but the problem persists.
Anybody that could know what is going on or how to fix this issue. I'm hoping not to have to format the phone to Stock to fix this.
I had same issue with TWRP in the past and never found a solution, to run into the ROM directly and escape the loop thing try
Power Button and volume -
Then continue and it will boot up normally.
I had to change to Clockwork-mod recovery after this.
einsiol said:
I'm running Optimized CyanogenMod 12.1 rom from the Jflte DevConnection Team.
After trying to flash the last OTA update for the rom my TWRP recovery has become unresponsive, stuck on its boot screen (TWRP logo).
What happen was that I downloaded the update via the OTA app and then pressed the Install button to reboot the device and flash the update.
But after the device booted into the recovery TWRP never opened up a process window or its menu but just stayed on the boot screen appearing to do nothing. It did not respond to any commands (buttons or touch). I waited half an hour before forcing a shot down.
But at this point I was in a manual boot loop, the device would boot into recovery instead of the Rom and I was unable to use the phone.
I managed to flash TWRP again using Heimdall which allowed me to boot again into the Rom, but if I tried manually going into recovery it was still unresponsive.
I tried flashing older version of TWRP using Flashy app, I clicked on a option in the app to reboot into recovery. This cost the origin boot loop problem again.
I than flashed CyanogenMod Recovery and was able to boot into that.
Tried once more to flash TWRP but the problem persists.
Anybody that could know what is going on or how to fix this issue. I'm hoping not to have to format the phone to Stock to fix this.
Click to expand...
Click to collapse
look at the twrp thread... i posted a fixed twrp there (look at last 2 pages)
try that one
Sent from my Xperia T using XDA Free mobile app
SdtBarbarossa said:
look at the twrp thread... i posted a fixed twrp there (look at last 2 pages)
try that one
Sent from my Xperia T using XDA Free mobile app
Click to expand...
Click to collapse
All I could find was recovery for I9305, is that one you ment? I tried it out but was not able to reboot into that.
But I tried now using the dd to flashed version 2.8.4 and got it to work finally.
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p21
Found this option on the TWRP page for I9505
einsiol said:
All I could find was recovery for I9305, is that one you ment? I tried it out but was not able to reboot into that.
But I tried now using the dd to flashed version 2.8.4 and got it to work finally.
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p21
Found this option on the TWRP page for I9505
Click to expand...
Click to collapse
i meaned the one i posted in s4 twrp page :-O NOT i9305 (wich is s3lte not s4)
Sent from my Xperia T using XDA Free mobile app
Helped a friend recently to install custom recover (TWRP v. 2.8.7.1) so she could install a Kit Kat rom, as she doesn't like Lolipop at all.
Anyways, since we did this, TWRP keeps auto booting. Is there any way to disable that and instead boot straight into the system?
your phone its now without os .... so you will get TWRP Auto boot.. try install stock rom then install twrp via odin
We still can boot into the os trough TWRP.
It's just autobooting instead of going straight to the os.
DarkShadeX said:
We still can boot into the os trough TWRP.
It's just autobooting instead of going straight to the os.
Click to expand...
Click to collapse
ok, reinstall stock rom then install twrp via odin