I have tried to install smartdroid in my s3 using TWRP as recovery manager. Since I previously backed up my stock rom I was able to back from a flashing problem I had "some changes failed". As I saw this can be overcame using Philz I changed the recovery. Then I tried to install, again, the smartdroid. This time it finishes but never booted up correctly.
Now, I am not able to reload my backed up rom (as it was made with TWRP and now I have Philz) nor installing smartdroid. So well, I want to install TWRP but I haven't seen the zip file to install it from Philz recovery What can I do?. Can I use odin from Philz?
Thanks
I didn't remember the download mode!, This post saved my day http://forum.xda-developers.com/galaxy-s3/help/twrp-flashing-tar-t2680354
Related
Hello,
I have just successfully rooted my S3 using "Heimdall Frontend" following the tutorial here:
However I found initially when leaving "No Reboot" unchecked I was unable to boot into CWM until I checked no Reboot then once the flash was complete I manually went into CWM by holding the recovery keys.
I then installed the SuperSu zip file on my SD card and rebooted my phone into it's newly rooted state.
HOWEVER.. I went to boot my S3 into CWM Recovery to flash a custom ROM and I'm only able to boot into the standard android recovery.. It says on the tutorial that versions 4.1.2+ need to tick "No reboot" otherwise the newer firmware simply wipes over CWM recovery every reboot..
I was under the impression that CWM was there as a safety net in case my phone ever played up and needed to be unrooted?
read this http://forum.xda-developers.com/showthread.php?t=1911726
UPDATE: After using ROM Manager to boot into CWM to create a backup, it gave the option to "Fix reflashing to original recovery after reboot"
Is it a good idea to have CWM permanently flashed as my recovery? How would I revert back to the stock recovery should I want to unroot the device?
Thanks
iamtherealmungo said:
UPDATE: After using ROM Manager to boot into CWM to create a backup, it gave the option to "Fix reflashing to original recovery after reboot"
Is it a good idea to have CWM permanently flashed as my recovery? How would I revert back to the stock recovery should I want to unroot the device?
Thanks
Click to expand...
Click to collapse
You need to read the faqs and guides its all posted and has been asked multiple times .
Hi all, I'm looking forward to your help. Current state of my phone is a bootloop straight into TWRP with failed installs of Kitkat/gapps and failed restore of my backup. Here's a step by step of what I've done.
1. Opened Goomanager, updated TWRP using the button (current version 2.6.3.0)
2. Downloaded AOKP kitkat nightly and pa gapps - download completes and MD5 hashes check out
3. Used goomanager "flash zips" interface to attempt flash, with factory reset option and backup option selected
4. Came back to find my phone stuck at TWRP with failed flash
5. Tried to flash again manually, using the standard TWRP flashing page
6. Failed again.
7. Decided to cut my losses and restore the backup created when I first attempted to flash via Goomanager
8. Restore fails.
9. Phone fails to load system, reverts into TWRP when it fails.
10. So now I can't restore my old android system and I can't flash a fresh one.
Where do I go from here? Is my version of TWRP dodgy and giving bad flashes? Should I downgrade it via adb? My phone was fine until an hour ago, so I don't think it's a hardware issue. Many thanks for your help. Tom
Did you try to flash a stock rom via Odin (in case you can get to dl mode) or via recovery (you need to get a flashable stock rom for that). I have not experience with twrp though, maybe you could also try philz recovery (I think I read somewhere that kitkat had problems with twrp).
Sent from my GT-I9300 using xda app-developers app
Twrp let me recover my backup after I pulled the battery rather than just use twrps reboot option. So at least I have a functioning phone now. Odin was always my last resort, but I have a mac so finding someone's pc to use is a bit annoying/embarrassing. I'm going to try re-downloading the kitkat rom and see if that fixes it, but it seems unlikely considering it passed an MD5 check after download. Thanks for taking the time to reply.
reading through other KitKat threads, people had reported all kind of strange behavior with TWRP.
Philz recovery (last version, or 6.00.8) didn't have any issues with KitKat (using it atm.)
Tom-Tom07 said:
reading through other KitKat threads, people had reported all kind of strange behavior with TWRP.
Philz recovery (last version, or 6.00.8) didn't have any issues with KitKat (using it atm.)
Click to expand...
Click to collapse
thats what I read as well. the Slim team for instance recommends Philz and not TWRP if I am not wrong
I have a rooted MDK Verizon S4 with SuperSU installed. I had been trying to use Rom Manager to install clockworkmod recovery and every time, it comes back with the message that it has been successfully installed. When I try to boot into recovery, it wouldn't work. I finally installed GooManager and went ahead and installed TWRP. Now I am able to boot into TWRP with no issues, but when I try to overwrite and install clockworkmod recovery from within Rom Manager, it again comes back with the message that it has been successfully installed, but it still boots into TWRP.
I understand that I can use TWRP to switch over to a different rom, but I am just befuddled as to why I am not able to install clockworkmod. Can you guys please help me understand what I am doing wrong?
the_jaguar said:
I have a rooted MDK Verizon S4 with SuperSU installed. I had been trying to use Rom Manager to install clockworkmod recovery and every time, it comes back with the message that it has been successfully installed. When I try to boot into recovery, it wouldn't work. I finally installed GooManager and went ahead and installed TWRP. Now I am able to boot into TWRP with no issues, but when I try to overwrite and install clockworkmod recovery from within Rom Manager, it again comes back with the message that it has been successfully installed, but it still boots into TWRP.
I understand that I can use TWRP to switch over to a different rom, but I am just befuddled as to why I am not able to install clockworkmod. Can you guys please help me understand what I am doing wrong?
Click to expand...
Click to collapse
You can either ODIN the CWM edition you want (for example Philz Touch Recovery - http://goo.im/devs/philz_touch/CWM_Advanced_Edition/jfltevzw) - get the md5 file of course for ODIN. You can also try to flash the zip file of Philz Touch Recovery from your SDCard (same site - http://goo.im/devs/philz_touch/CWM_Advanced_Edition/jfltevzw) through TWRP. Reboot into recovery and see what happens.
Skeetch79 said:
You can either ODIN the CWM edition you want (for example Philz Touch Recovery - http://goo.im/devs/philz_touch/CWM_Advanced_Edition/jfltevzw) - get the md5 file of course for ODIN. You can also try to flash the zip file of Philz Touch Recovery from your SDCard (same site - http://goo.im/devs/philz_touch/CWM_Advanced_Edition/jfltevzw) through TWRP. Reboot into recovery and see what happens.
Click to expand...
Click to collapse
Thanks. When I was trying to install CWM within Rom Manger, I ended up paying for the touch upgrade, hence my desire to try and install CWM form within Rom Manager... It's just a bit frustrating that I can't figure out what's going on..
Hello I was having problems in backing up data in nandroid using cwm recovery. Some nice guy suggested me to change my recovery so I did.
Now i have messed up real bad, i flashed a philz recovery which I had used in a stock based rom and the backup was successful but then the phone couldn't boot up. So i restored the boot patrition from a previously made backup. This way i successfully booted up my phone and got previous recovery. So far so good. Now i knew that the problem is in recovery. I also had a raw kernel file which I had used to flash the cm11 rom so i flashed that kernel. But then i restated device to find out that i have now lost root access. I tried flashing super su via raw kernels twrp recovery but I saw no effect despite it being flashed. I cannot flash the recovery because the curreny twrp recovery crashes when i try to flash that.
Current situation is that I am getting constant unlimited, system process is crashed, errors and I can see no signal from mobile operator. Wifi is working fine.
Please help me, my phone is almost unusable with this error but I have access to all the apps, functions etc. in case you can suggest me to use it.
UPDATE:
Tried to flash a latest version of cm11 and now booted up correctly. root checker says I am rooted.
got latest cwm as well
Now I need to take backup to see if the initial problem is there or not.
As the issue highlighted in this thread is solved, I will mark this as solved and will reply to future problems (related to not being able to backup /data) in the following thread:
http://forum.xda-developers.com/android/help/cwms-nandroid-backup-fails-to-backup-t2899038
Hey Guys,
I'm having a bit of an issue. Currently I was running STOCK Android 4.3 JB, have been for a while, it started to get a bit slow & I was wanting to fresh install, but also try out a 5.0 lollipop ROM. I've rooted my phone in the past and installed custom ROMs before without a problem (Revolution Remix + Cyanogenmod 11), however, I decided to try Liquidsmooth 5.0 lollipop. i followed this video,
https://www.youtube.com/watch?v=QquFDFEEKlI
http://forum.xda-developers.com/galaxy-s3/development/rom-liquidsmooth-lollipop-4-0-b1-t2980477
I downloaded both files and copied them onto my MicroSD card.
I backed up my data (contacts, images, files etc..)
Booted into "Recovery Mode", wiping Cache & factory Reset
When to install from SD, located file and it started reading/installing (sorry can't remember exactly what it did), but during process it failed. I went back into Android (had to setup again), Went and made sure Developer Mode and USB Debugging was on, still didn't work.
Went to make sure CWM was installed/update, which it said it was (possibly from previous custom installs?), tried updating, failed. It said
Went and installed 'SuperSU' from Play store, but got this error.
Decided to try re-install STOCk 4.3 JB, I
made sure USB Debugging was on
loaded Odin 3.07 (or was it 3.09) and loaded 4.3 Firmware under PDA (left everything else as is)
Started and let it do its thing. It finished/PASSED and phone restarted.
i went back into the phone, installed ROM manager & SuperSU again to give it another shot... but same problem again, getting the error above.
I'm not sure what's happened and I'm not sure what "solutions" to search for... anyone have any suggestions?
At this stage I'm thinking of just going back to STOCK 4.3, then maybe try again (either with Liquidsmooth lollipop, or, Slimkat 4.4)
Thanks guys, any help would be super appreciated,
Regards,
~ Dave
Le Widget said:
Hey Guys,
I'm having a bit of an issue. Currently I was running STOCK Android 4.3 JB, have been for a while, it started to get a bit slow & I was wanting to fresh install, but also try out a 5.0 lollipop ROM. I've rooted my phone in the past and installed custom ROMs before without a problem (Revolution Remix + Cyanogenmod 11), however, I decided to try Liquidsmooth 5.0 lollipop. i followed this video,
https://www.youtube.com/watch?v=QquFDFEEKlI
http://forum.xda-developers.com/galaxy-s3/development/rom-liquidsmooth-lollipop-4-0-b1-t2980477
I downloaded both files and copied them onto my MicroSD card.
I backed up my data (contacts, images, files etc..)
Booted into "Recovery Mode", wiping Cache & factory Reset
When to install from SD, located file and it started reading/installing (sorry can't remember exactly what it did), but during process it failed. I went back into Android (had to setup again), Went and made sure Developer Mode and USB Debugging was on, still didn't work.
Went to make sure CWM was installed/update, which it said it was (possibly from previous custom installs?), tried updating, failed. It said
Went and installed 'SuperSU' from Play store, but got this error.
Decided to try re-install STOCk 4.3 JB, I
made sure USB Debugging was on
loaded Odin 3.07 (or was it 3.09) and loaded 4.3 Firmware under PDA (left everything else as is)
Started and let it do its thing. It finished/PASSED and phone restarted.
i went back into the phone, installed ROM manager & SuperSU again to give it another shot... but same problem again, getting the error above.
I'm not sure what's happened and I'm not sure what "solutions" to search for... anyone have any suggestions?
At this stage I'm thinking of just going back to STOCK 4.3, then maybe try again (either with Liquidsmooth lollipop, or, Slimkat 4.4)
Thanks guys, any help would be super appreciated,
Regards,
~ Dave
Click to expand...
Click to collapse
First of all and most important don't use rom manager! it causes more problems than anything else.The best way to install custom roms is to use Cwm,PhilZ or Twrp to install anything!
Flash superSU zip in recovery from here >> http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1 << SuperSU forum here >> http://forum.xda-developers.com/showthread.php?t=1538053 << Technically you should not need to flash SuperSU because nearly all custom roms come with root built in so you could flash a custom recovery then wipe and flash your rom (but I can see you have been having problems doing that)
What you should do is
(1) Flash a custom recovery with Odin (Recommend PhilZ)
(2) Reboot to custom recovery
(3) Wipe phone
(4) Install custom rom (which is already rooted) from Ext SD card
(5) Reboot (If you get bootloop factory reset/ wipe cache
Also to note PhilZ recovery (which I think is better as more options and is based on Cwm) as a option to fix root in settings.
tallman43 said:
First of all and most important don't use rom manager! it causes more problems than anything else.The best way to install custom roms is to use Cwm,PhilZ or Twrp to install anything!
Flash superSU zip in recovery from here >> http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1 << SuperSU forum here >> http://forum.xda-developers.com/showthread.php?t=1538053 << Technically you should not need to flash SuperSU because nearly all custom roms come with root built in so you could flash a custom recovery then wipe and flash your rom (but I can see you have been having problems doing that)
What you should do is
(1) Flash a custom recovery with Odin (Recommend PhilZ)
(2) Reboot to custom recovery
(3) Wipe phone
(4) Install custom rom (which is already rooted) from Ext SD card
(5) Reboot (If you get bootloop factory reset/ wipe cache
Also to note PhilZ recovery (which I think is better as more options and is based on Cwm) as a option to fix root in settings.
Click to expand...
Click to collapse
hi tallman, much appreciated for the reply
For some reason I couldnt get Philz Custom Recovery to work with odin, kept getting an error :/ . So I ended up trying TWRP, which worked, I booted into it then installed Liquidsmooth + gapps, all installed ok, but all up it was the same process you mentioned, which I greatly appreciate.
So running Liquidsmooth 5 now with TWRP recovery, though will likely give Philz recovery a shot down the track
Le Widget said:
hi tallman, much appreciated for the reply
For some reason I couldnt get Philz Custom Recovery to work with odin, kept getting an error :/ . So I ended up trying TWRP, which worked, I booted into it then installed Liquidsmooth + gapps, all installed ok, but all up it was the same process you mentioned, which I greatly appreciate.
So running Liquidsmooth 5 now with TWRP recovery, though will likely give Philz recovery a shot down the track
Click to expand...
Click to collapse
Good to hear it's working Yes it's worth persevering with PhilZ it's a good recovery although Twrp is not bad either:good: