I am working with Skyrocket I727R (the rogers phone), and have installed LiquidSmooth 4.1.2 which I must say works very well. I just wanted to try another rom and update to JB 4.2.2.
I thought when I could not flash JellyBeer and Paranoid Android getting error 7 that it was due to the Assert line in the updater-script. But after removing the Assert Line, it still would not flash. I also found out I cannot flash any of the Roms. I am using TWRP 2440. which I had to install through Odin as the TWRP.zip file would not flash properly with CWM recovery. It said it completed successfully but on reboot nothng would happen, so I had to install the TWRP.tar through ODIN. Could it be my SD card, or a problem with recovery? Should I try a different version of TWRP?
Thanks for any help.
The twrp version you're using is very old. New roms won't flash on it. The latest is 2.5.x.x
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
WARRENFRALEIGH said:
I am working with Skyrocket I727R (the rogers phone), and have installed LiquidSmooth 4.1.2 which I must say works very well. I just wanted to try another rom and update to JB 4.2.2.
I thought when I could not flash JellyBeer and Paranoid Android getting error 7 that it was due to the Assert line in the updater-script. But after removing the Assert Line, it still would not flash. I also found out I cannot flash any of the Roms. I am using TWRP 2440. which I had to install through Odin as the TWRP.zip file would not flash properly with CWM recovery. It said it completed successfully but on reboot nothng would happen, so I had to install the TWRP.tar through ODIN. Could it be my SD card, or a problem with recovery? Should I try a different version of TWRP?
Thanks for any help.
Click to expand...
Click to collapse
Use the goo manager app to install twrp. Yours is old as dirt.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 4 Beta
xcrazydx said:
Use the goo manager app to install twrp. Yours is old as dirt.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I updated TWRP using Goo manager as suggested. I tried installing Revolt which does not have an assert line. It failed. Error with updater-binary.
Tried installing Beanstalk (newest version). Also had error with update-binary. Then I edited the updater-script removing the assert line. Eureka, it worked.
WARRENFRALEIGH said:
I updated TWRP using Goo manager as suggested. I tried installing Revolt which does not have an assert line. It failed. Error with updater-binary.
Tried installing Beanstalk (newest version). Also had error with update-binary. Then I edited the updater-script removing the assert line. Eureka, it worked.
Click to expand...
Click to collapse
Sweet!
Sent from my SAMSUNG-SGH-I727 using Tapatalk 4 Beta
Related
Im trying to flash the superlite rom by vincom but every time i try to flash it throws out an error.
assert failed: getprop("ro.product.device") ==
getprop("ro.product.device") == "skyrocket"
E:Error in /tmp/sideload/package.zip
(status 7)
*verifying filesystems...
*verifying partition sizes...
Error flashing zip '/sdcard/superlite_cm10_jb_v
Injecting TWRP into boot image...
TWRP injection complete
It says the flash is successful but the phone doesn't boot after flash. I have checked the md5 of the ROM, wiped everything, basically followed all the instruction in vincoms post to the letter but no dice. I'm on rogers.
Error 7 is assert protection it's seeing your phone model is different from the phone model in the updater script of the rom meaning either A. Turn off assert checks or B. Do you own a skyrocket and not a 989?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Illnevertell said:
Error 7 is assert protection it's seeing your phone model is different from the phone model in the updater script of the rom meaning either A. Turn off assert checks or B. Do you own a skyrocket and not a 989?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
How do I go about turning off assert checks? My phone model is SGH-I727R so yes, skyrocket
Also, could the problem be that I am using twrp 2.1.2? Im not sure how to flash 2.2.0 onto my system, google searches are unreliable and installing via goomanager does not work for me
generelkickass said:
Also, could the problem be that I am using twrp 2.1.2? Im not sure how to flash 2.2.0 onto my system, google searches are unreliable and installing via goomanager does not work for me
Click to expand...
Click to collapse
I have never used TWRP but you should be able to flash the newer version in recovery just as you would to update CWM.
------------------------------------------------
Sent from my Skyrocket i727 running AOKP JB
One does not simply search on XDA
Twrp isn't the issue do a little digging son learn your recovery it's not real hard
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Illnevertell said:
Twrp isn't the issue do a little digging son learn your recovery it's not real hard
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Just so happened I soft bricked my phone, after resetting everything (and installing twrp 2.2.0) the flash worked! Thanks for your time and help, hope you dont hate me for being a noob! Thanks to vincom for the great ROM!
generelkickass said:
Just so happened I soft bricked my phone, after resetting everything (and installing twrp 2.2.0) the flash worked! Thanks for your time and help, hope you dont hate me for being a noob! Thanks to vincom for the great ROM!
Click to expand...
Click to collapse
I have no issue with noobs it's stupid noobs that bother me I will say a quick Google search of the error would have given you an idea of where to start searching is your friend heads up
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Hi – I have a stubborn issue with my Blaze 4G not working on CM roms, I would appreciate any help you guys can provide. Below are the details:
I recently bought a T-Mobile Samsung Galaxy S Blaze 4G, and did the following:
- Rooted it using the following guide (it now has ICS)
- SIM Unlocked it using the following guide (now it works on other networks)
- Updated to CWM 6.0.3.8, since JB roms needs it
- Flashed the T769-UVLH5 modem, since CM support it
And now when I flash CM 10 stable or 10.2 nightly it gets stuck in booting and displaying the CM logo animation screen, after few minutes it reboots and does it all over again.
I remember when I upgraded to CM JB on my SGS3 I needed to flash a JB stock rom on it to get the new boot loaders for JB, but I saw no mention of this on this forum. What else am I missing?
Thanks.
TINGEA said:
Hi – I have a stubborn issue with my Blaze 4G not working on CM roms, I would appreciate any help you guys can provide. Below are the details:
I recently bought a T-Mobile Samsung Galaxy S Blaze 4G, and did the following:
-Rooted it using the following guide (it now has ICS)
-SIM Unlocked it using the following guide (now it works on other networks)
-Updated to CWM 6.0.3.8, since JB roms needs it
-Flashed the T769-UVLH5 modem, since CM support it
And now when I flash CM 10 stable or 10.2 nightly it gets stuck in booting and displaying the CM logo animation screen, after few minutes it reboots and does it all over again.
I remember when I upgraded to CM JB on my SGS3 I needed to flash a JB stock rom on it to get the new boot loaders for JB, but I saw no mention of this on this forum. What else am I missing?
Thanks.
Click to expand...
Click to collapse
You wiped data/cache/system? Reinstall it. Anyways use the new 6.0.4.4 recovery.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Somcom3X said:
You wiped data/cache/system? Reinstall it. Anyways use the new 6.0.4.4 recovery.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Thanks Somcom. I have to admit that I forgot to do the wipes. but even after doing the wipes (data/system/ factory rest/ cach/devalk) and reinstalling the CM nightly, I still have the same issue.
as for recovery, I updated to the latest version using the rom manager, and according to the official site clockworkmod[dot]com[slash]rommanager (can't post links) I have the latest version for Blaze. how do you get the 6.0.4.4 on blaze?
I still feel it's a ICS vs JB bootloaders issue, but not sure how to proceed next.
Thanks!
TINGEA said:
Thanks Somcom. I have to admit that I forgot to do the wipes. but even after doing the wipes (data/system/ factory rest/ cach/devalk) and reinstalling the CM nightly, I still have the same issue.
as for recovery, I updated to the latest version using the rom manager, and according to the official site clockworkmod[dot]com[slash]rommanager (can't post links) I have the latest version for Blaze. how do you get the 6.0.4.4 on blaze?
I still feel it's a ICS vs JB bootloaders issue, but not sure how to proceed next.
Thanks!
Click to expand...
Click to collapse
No boot loaders man. This is before Samsung's complications.
Recovery is here.
http://d-h.st/AFu
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Thanks Somcom3X, but still didn't work. When installing the CM room in recovery 6.0.4.4 I get a bunch of getprop assert failures. This used to work on the previous version (6.0.3.8). Now the Rom won't install.
Also, I'm curious what did you mean by this is before Samsung's complications?
Thanks
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
TINGEA said:
Thanks Somcom3X, but still didn't work. When installing the CM room in recovery 6.0.4.4 I get a bunch of getprop assert failures. This used to work on the previous version (6.0.3.8). Now the Rom won't install.
Also, I'm curious what did you mean by this is before Samsung's complications?
Thanks
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
After 2011 samsung began installing software and counters to try and prevent people from rooting and installing custom firmwares.
knox is an example of this.
These devices don't have any of that complicated security.
You handy with odin? Your recovery is not right. Just to be clear, what is your model number?
If it is T 7 6 9, your good to go to odin. I'd recommend going back to stock, and then install a recovery and you should be good to go.
Somcom3X said:
After 2011 samsung began installing software and counters to try and prevent people from rooting and installing custom firmwares.
knox is an example of this.
These devices don't have any of that complicated security.
You handy with odin? Your recovery is not right. Just to be clear, what is your model number?
If it is T 7 6 9, your good to go to odin. I'd recommend going back to stock, and then install a recovery and you should be good to go.
Click to expand...
Click to collapse
Thanks again, I use the guide here to convert the image into a tar.md5 to flash using odin, but after flashing successfully I still have the same issue when installing the CM zip file in recovery, and yes it is the T-mobile Samsung Galaxy S Blaze 4G T769.
any other possible causes?
BTW - when I was flashing via Odin my upload phone screen was showing that I have a custom rom and the counter was 1.... do I need to fix that?
TINGEA said:
Thanks again, I use the guide here to convert the image into a tar.md5 to flash using odin, but after flashing successfully I still have the same issue when installing the CM zip file in recovery, and yes it is the T-mobile Samsung Galaxy S Blaze 4G T769.
any other possible causes?
Click to expand...
Click to collapse
SOLUTION:
The reason your stock recovery system keeps getting overwritten at Android startup is because of a script that is being run.* All you need to do is either rename this script or simply delete it.
Please keep in mind that if you restore your stock ROM, this script will be restored with it so you will have to rename or delete it again.* Do the following:*
1.
Make sure your device is powered on and running normally,
2.
Make sure you have rooted your device and that you have all of the necessary permissions in order to manipulate system files.*
3.
In the root file system go to \system\etc
4.
Find the file named install-recovery.sh and either rename it or, as I did, delete it.*
That’s all there is to it.*
Please keep in mind that you will need to flash your custom system recovery one more time after modifying the script file.* After that, reboot away and you will always be able to get back into your new system recovery.
Good Luck and Happy Tweaking.
Click to expand...
Click to collapse
Try that.
Found it here http://mark.candleshoreblog.com/201...-factory-stock-roms-at-android-system-reboot/
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Somcom3X said:
Try that.
Found it here http://mark.candleshoreblog.com/201...-factory-stock-roms-at-android-system-reboot/
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Thanks Somcom3X - but I'm not sure this is needed for my case. I read the original blog post and my recovery does not get overwritten. I actually rebooted multiple times into CWM recovery and each time it is the same 6.0.4.4.
I also went into the /system/etc folder and there is no install_recovery.sh file.
to clarify, here is where I'm stuck now:
- when I use CWM 6.0.3.8 CM install completes successfully, but then CM will not boot, and will keep on cycling on the boot logo screen.
- when I use CWM 6.0.4.4 I can't start to install CM as it complained that my phone is not t769.
in all cases I'm using CM 10.2 nightly for T769.
Thanks for the help.
You should delete assert lines at the top of the zip's updater-script and it will let you flash it.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
I removed the assert lines from the updater script, and it was able to complete the install process afterwards, however when I booted the new CM 10.0 system it got stuck on the cyanogenmod boot logo. I made sure I do a system/data rest, cleared cash, and cleared devalk.
I do not think it's an issue with my recovery as I'm getting the same result as I did with the official 6.0.3.8.
Something else is going on.
Any ideas?
Thanks.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
TINGEA said:
I removed the assert lines from the updater script, and it was able to complete the install process afterwards, however when I booted the new CM 10.0 system it got stuck on the cyanogenmod boot logo. I made sure I do a system/data rest, cleared cash, and cleared devalk.
I do not think it's an issue with my recovery as I'm getting the same result as I did with the official 6.0.3.8.
Something else is going on.
Any ideas?
Thanks.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Tar back to stock GB. Upgrade to ICS. Then root and install cwm. Flash away
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Somcom3X said:
You should delete assert lines at the top of the zip's updater-script and it will let you flash it.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Thanks Somcom3X - but this is more trouble than what I wanted to put in - I'll stick with the rooted stock ROM I have. I was hoping the process was a little more straight forward, similar to my SGS3.
thanks for all your help thus far!
Somcom3X said:
Tar back to stock GB. Upgrade to ICS. Then root and install cwm. Flash away
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Ok, my rooted ICS stock is acting up (random shutdowns and such), so I need to give this another try and get this phone to CM.
I tared back to stock GB, skipped the upgrade to ICS (was not able to upgrade via the ROM software update option), flashed CWMR (5.0.4.x) via Odin, upgraded to CWMR 6.0.4.5, installed CM 11 nightly, and then wiped data/factory rest and Dalvik .... and ....
it is still stuck on the boot screen....
I seriously would appreciate a silver bullet right now!
TINGEA said:
Ok, my rooted ICS stock is acting up (random shutdowns and such), so I need to give this another try and get this phone to CM.
I tared back to stock GB, skipped the upgrade to ICS (was not able to upgrade via the ROM software update option), flashed CWMR (5.0.4.x) via Odin, upgraded to CWMR 6.0.4.5, installed CM 11 nightly, and then wiped data/factory rest and Dalvik .... and ....
it is still stuck on the boot screen....
I seriously would appreciate a silver bullet right now!
Click to expand...
Click to collapse
Hmm. Go back to stock ics, flash a 10.2 recovery, then flash whatever you desire.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
What is a10.2 recovery? Is it a certain version of CWMR? And do I need to flash it via Odin? Thanks
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
TINGEA said:
What is a10.2 recovery? Is it a certain version of CWMR? And do I need to flash it via Odin? Thanks
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
It would be cwm 6.0.2.7
You can flash the img through a zip or by terminal on the phone.
Odin needs a tar'd recovery img
Sorry been very busy.
Have you tried this?
http://forum.xda-developers.com/showthread.php?t=2577265
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Thanks Somcom3X - I looked all over this forum and the internet, and could not find a link for a 6.0.2.7 CWM for Blaze - I found it for other phones but not Blaze. can you please point me to a link if you happen to know of one. the official site does not have an archived list of previous versions.
as for the provided link, I did follow it through, and downloaded the recovery Tar (it was CWM 5.5.04) but that yielded the same results after installing CM 10 and 10.2 - stuck at boot screen logo. I'm reasonably confident now that it is not a recovery issue, as I flashed half a dozen different versions and none worked with CM 10, 10.2, or 11.... it has to be something else!
Thanks.
TINGEA said:
Thanks Somcom3X - I looked all over this forum and the internet, and could not find a link for a 6.0.2.7 CWM for Blaze - I found it for other phones but not Blaze. can you please point me to a link if you happen to know of one. the official site does not have an archived list of previous versions.
as for the provided link, I did follow it through, and downloaded the recovery Tar (it was CWM 5.5.04) but that yielded the same results after installing CM 10 and 10.2 - stuck at boot screen logo. I'm reasonably confident now that it is not a recovery issue, as I flashed half a dozen different versions and none worked with CM 10, 10.2, or 11.... it has to be something else!
Thanks.
Click to expand...
Click to collapse
I'm very sorry for the delay. Been very very busy.
https://www.dropbox.com/s/awp1zy4u3x34a2v/CWM-cm-10.2-Recovery-t769.zip
That is my personal 10.2 recovery. Works fine for me.
The author is me, but I was too lazy to change the lines.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
I am trying to use flash paranoid android and flashing this version of gapps along with it: pa_gapps-stock-4.4.2-20140412-signed. When I go to flash the ROM, it succeeds without issue, but when I go to flash gapps it says that it cant open the zip fie of gapps and than in parenthesis it says (bad). and than it says installation aborted. Please help.
maxell505 said:
I am trying to use flash paranoid android and flashing this version of gapps along with it: pa_gapps-stock-4.4.2-20140412-signed. When I go to flash the ROM, it succeeds without issue, but when I go to flash gapps it says that it cant open the zip fie of gapps and than in parenthesis it says (bad). and than it says installation aborted. Please help.
Click to expand...
Click to collapse
Maybe it was a bad download?
Sent from my Nexus 7 using xda app-developers app
Kreateablaze said:
Maybe it was a bad download?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I have downloaded it about 3 times and tried to flash it. Previously I tried to do this with OmniROM but than I just gave up and restored my system back to stock. Now I am trying it with Paranoid Android and the same thing is happening.
maxell505 said:
I have downloaded it about 3 times and tried to flash it. Previously I tried to do this with OmniROM but than I just gave up and restored my system back to stock. Now I am trying it with Paranoid Android and the same thing is happening.
Click to expand...
Click to collapse
Are you checking the md5sum of the download? Do that to make sure it's a good download
Sent from my SAMSUNG-SGH-I727
Yes, I am unlocked and rooted. Running carbon 4/1 nightly atm and using KTK but whenever I try to flash a new kernel I get an error. In TWRP it says "Error flashing update binary" and in CWM I get Status Error 7. Both are latest versions and the kernels are for my version of Android as well and the downloads did download successfully. Just got no clue what is happening.
U can use SU to update ur binary. I also recommend to have the latest twrp (2.6.3.1. I read that 7.0 ppl having trouble with backups) or cwm recovery
Sent from my SCH-I535 using Tapatalk
Updated my SU binary and still getting the same error. "Error executing updater binary"
I guess I can try CWM
Sent from my SCH-I535 using xda app-developers app
Tried it in CWM. Got status error 7.
Sent from my SCH-I535 using xda app-developers app
Do a clean install. Factory reset format. Then flash rom and different kernel
Sent from my SCH-I535 using Tapatalk
DubleJayJ said:
Yes, I am unlocked and rooted. Running carbon 4/1 nightly atm and using KTK but whenever I try to flash a new kernel I get an error. In TWRP it says "Error flashing update binary" and in CWM I get Status Error 7. Both are latest versions and the kernels are for my version of Android as well and the downloads did download successfully. Just got no clue what is happening.
Click to expand...
Click to collapse
Status 7 error indicates you need to update your recovery
Answer should be stickied
ShapesBlue said:
Status 7 error indicates you need to update your recovery
Click to expand...
Click to collapse
Thanks, finally a proper response!!! :good::good::good:
I wanted to try a KitKat ROM so i downloaded a couple on PC and transferred to SD card. I did a backup (which really saved me lol) and then, as instructed , formatted system, data, and cache. Wiped Dalvik and flashed ROM (Paranoid Android 4.0). It started but after the "installing update" message I got a error message " error /location of zip/name of zip (status0)". I thought it meant that the zip was corrupted so i downloaded on PC again. Transferred to SD and tried to install following the same stepsand got the error again. After that I tried to install another ROM(Validus 5.1) and still got the error. Decided to restore and see if i could get help before trying again. Any ideas what is wrong? Thanks in advance for any help
EDIT can dev please move I thought i was posting in troubleshooting section. Sorry
explicitKC said:
I wanted to try a KitKat ROM so i downloaded a couple on PC and transferred to SD card. I did a backup (which really saved me lol) and then, as instructed , formatted system, data, and cache. Wiped Dalvik and flashed ROM (Paranoid Android 4.0). It started but after the "installing update" message I got a error message " error /location of zip/name of zip (status0)". I thought it meant that the zip was corrupted so i downloaded on PC again. Transferred to SD and tried to install following the same stepsand got the error again. After that I tried to install another ROM(Validus 5.1) and still got the error. Decided to restore and see if i could get help before trying again. Any ideas what is wrong? Thanks in advance for any help
EDIT can dev please move I thought i was posting in troubleshooting section. Sorry
Click to expand...
Click to collapse
Are you using the most recent version of TWRP, CWM, or Philz recovery? Are you currently running a custom ROM?
EDIT: Thread reported to mod as "Thread needs moving or maintenance."
Sent from my SGH-T989 using Tapatalk
jrc2 said:
Are you using the most recent version of TWRP, CWM, or Philz recovery? Are you currently running a custom ROM?
EDIT: Thread reported to mod as "Thread needs moving or maintenance."
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
I'm using a custom ROM right now, I don't know if the Philz I have is the most recent. Would that cause errors? How would i know what version I have installed.
explicitKC said:
I'm using a custom ROM right now, I don't know if the Philz I have is the most recent. Would that cause errors? How would i know what version I have installed.
Click to expand...
Click to collapse
If the version of Philz you are using is from JB then that could cause the errors.
Sent from my SGH-T989 using Tapatalk
jrc2 said:
If the version of Philz you are using is from JB then that could cause the errors.
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
ok I installed CWM recovery v6.0.1.2. I tried installing Paranoid Android again and after it got to Installing Update I got a message
set_metadata_recursive: some changes failed
E:Error in /external_sd/zips/pa_p3113-4.3-BETA4-20140513.zip
(Status 7)
Installation aborted.
explicitKC said:
ok I installed CWM recovery v6.0.1.2. I tried installing Paranoid Android again and after it got to Installing Update I got a message
set_metadata_recursive: some changes failed
E:Error in /external_sd/zips/pa_p3113-4.3-BETA4-20140513.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Status 7 means that your recovery is out of date. I am running AOSPA Beta4 on my p3113 and installed it using the latest TWRP from the below thread. The version of cwm in that thread should also work.
Latest recoveries: http://forum.xda-developers.com/showthread.php?t=2548257
Sent from my SGH-T989 using Tapatalk
jrc2 said:
Status 7 means that your recovery is out of date. I am running AOSPA Beta4 on my p3113 and installed it using the latest TWRP from the below thread. The version of cwm in that thread should also work.
Latest recoveries: http://forum.xda-developers.com/showthread.php?t=2548257
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
TY i'll download and try, Is there a recommended recovery? Or is it just personal preference?
explicitKC said:
TY i'll download and try, Is there a recommended recovery? Or is it just personal preference?
Click to expand...
Click to collapse
I am currently using TWRP, but I have used PhilzTouch in the past. They both work pretty well. TWRP has bigger buttons that are spaced out better and has an easier interface to use. PhilzTouch has some other features but isn't as polished. It is just a matter of personal preference. Some Roms will have a recommended recovery listed, though.
Also, to make sure that the zip you download isn't corrupted, check the md5 of the zip you download against the md5 on the download page.
Sent from my SGH-T989 using Tapatalk
Biggest advantage of using Phillz touch is that it can detect OTG cable,so you can flash ROMs from USB device as well;on the other hand, TWRP allows you to flash 10 zips at the same time,it will release the overhead of selecting Zip one after another manually. So choose your options wisely.
Edit:-
One more thing I would like to add,Phillz touch blackhawk supports dual-booting through next kernel
lokesh.3440 said:
Biggest advantage of using Phillz touch is that it can detect OTG cable,so you can flash ROMs from USB device as well;on the other hand, TWRP allows you to flash 10 zips at the same time,it will release the overhead of selecting Zip one after another manually. So choose your options wisely.
Click to expand...
Click to collapse
The version of TWRP I linked to also supports otg.
Sent from my SGH-T989 using Tapatalk
jrc2 said:
The version of TWRP I linked to also supports otg.
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
really,which one are you referring to ? TWRP 2.7.0.3 ?
lokesh.3440 said:
really,which one are you referring to ? TWRP 2.7.0.3 ?
Click to expand...
Click to collapse
I am currently using 2.7.0.1 but 2.7.0.3 also has it. The one that I linked to was compiled by Android-Andi
Sent from my SGH-T989 using XDA mobile app
jrc2 said:
Status 7 means that your recovery is out of date. I am running AOSPA Beta4 on my p3113 and installed it using the latest TWRP from the below thread. The version of cwm in that thread should also work.
Latest recoveries: http://forum.xda-developers.com/showthread.php?t=2548257
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Just wanted to say thanks again to jrc2. I went with TWRP because backup to sd card was not working on CWM and Philz. Backup would start and in the middle of backing up data or system tab would just reboot. But TWRP looks ok and flashed with no problems.