Related
I have rooted and rom'd for a couple of years, first on the moment, then the EVO and now the evo 3d and have never run across this. E: error in tmp/sideload/package.zip I have tried 2 different roms and have gotten the same result. I have searched but have been unable to find an answer. Anyone know how to fix this?
nikiya said:
I have rooted and rom'd for a couple of years, first on the moment, then the EVO and now the evo 3d and have never run across this. E: error in tmp/sideload/package.zip I have tried 2 different roms and have gotten the same result. I have searched but have been unable to find an answer. Anyone know how to fix this?
Click to expand...
Click to collapse
What ROM are you trying to flash? Are any of the options under the flash menu checked or have an"X" beside them?
Have you tried reflashing the recovery? Are you using TWRP 1.01 or 1.0?
I am using twrp 1.0.1 and have been trying to flash gbsense-e3d-deck [0.2] and Chogardjr3D v0.9 - Re-Engineered Sense 3.0, I have tried redownloading, reflashing the recovery, I am doing full wipes before flash attempts. I am really at a loss as to what the issue is.
Did you check reboot after successful flash? I don't know if that's what fixed it for me but I had that problem the first time.
Sent from my E3D.
I know I had it checked when trying to flash Chogardjr3D v0.9 but not the other because I wanted to flash the netarchy kernel
nikiya said:
I know I had it checked when trying to flash Chogardjr3D v0.9 but not the other because I wanted to flash the netarchy kernel
Click to expand...
Click to collapse
Hmmm..I know others have had this problem. It seems perseverance is key. Keep wiping, factory reset, etc. It seems once it works once, your good.
Sent from my E3D.
I can't flash any roms. I am using twrp 1.0.1 downloaded early this am.
Also, I redownloaded twrp, and redid that so recovery is new.........
Just tried the mik rom, I got the same errors.
E:Error in /tmp/sideload/package.zip
and with sig verification on I get
E:signature verification failed
mik's rom is signed as well as synergy............
There have been a few others with this problem, but they seem to get past it. I wipe everything but still get these errors. And when I tried to restore with my nandroid, I get stuck on the htc screen, then I pull the battery, wipe, and restore the nandroid again, and it works, but it always takes me two times. Any one have an idea, never ran into this before............
I have no options checked, still get this error.......
B-Mod said:
I can't flash any roms. I am using twrp 1.0.1 downloaded early this am.
Also, I redownloaded twrp, and redid that so recovery is new.........
Just tried the mik rom, I got the same errors.
E:Error in /tmp/sideload/package.zip
and with sig verification on I get
E:signature verification failed
mik's rom is signed as well as synergy............
There have been a few others with this problem, but they seem to get past it. I wipe everything but still get these errors. And when I tried to restore with my nandroid, I get stuck on the htc screen, then I pull the battery, wipe, and restore the nandroid again, and it works, but it always takes me two times. Any one have an idea, never ran into this before............
I have no options checked, still get this error.......
Click to expand...
Click to collapse
This is exactly what is happening to me as well.
Do a reboot. Your system wont be there so reboot into bootloader and go back into recovery.
I had the restore problem too..had to double up.
Sent from my E3D.
B-mod you are the man! That did it.
Sent from my PG86100 using XDA Premium App
nikiya said:
B-mod you are the man! That did it.
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
tehbeetus, and I both got it, I rebooted and selected factory reset, and it worked, tehbeetus just rebooted and got it to go. Not sure why some of use have to do it twice though. Mine is that way everytime I flash a rom, or nandroid.
On my Verizon GS3.
I was using a stock-rooted ROM, and then today tried to install the latest wanamlite.
Even though it says No Wipe, I did just to be safe in CWM (or so I thought).
When trying to flash the ROM, I got the "assert failed:write_raw_image("/tmp/boot.img","boot")" error , and I remember seeing a (status 7) error
Then I tried to reboot... and then nothing but a black screen.
I've tried the Volume Down + Home + Power button to get into "Download Mode" with no success.
I would appreciate any help towards getting this rom on my device.
PS. I've searched, and read these threads
- http://forum.xda-developers.com/showthread.php?t=1045887
- http://forum.xda-developers.com/showthread.php?t=1767226
- http://forum.xda-developers.com/showthread.php?t=1526599
Can't really seem to figure things out.
AB_ said:
On my Verizon GS3.
I was using a stock-rooted ROM, and then today tried to install Wanalam's latest.
Even though it says No Wipe, I did just to be safe in CWM (or so I thought).
When trying to flash the ROM, I got the "assert failed:write_raw_image("/tmp/boot.img","boot")" error , and I remember seeing a (status 7) error
Then I tried to reboot... and then nothing but a black screen.
I've tried the Volume Down + Home + Power button to get into "Download Mode" with no success.
I would appreciate any help towards getting this rom on my device.
PS. I've searched, and read these threads
- http://forum.xda-developers.com/showthread.php?t=1045887
- http://forum.xda-developers.com/showthread.php?t=1767226
- http://forum.xda-developers.com/showthread.php?t=1526599
Can't really seem to figure things out.
Click to expand...
Click to collapse
The Verizon s3 is different from the international model. You're in the wrong forum.
Sent from my GT-I9300 using xda app-developers app
kofiaa said:
The Verizon s3 is different from the international model. You're in the wrong forum.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Man, I should've been paying attention. I was directed to that rom there from a thread I found in the Verizon section.
Sorry bro, just get a rom from the Verizon forum I'm sure your phone will be just fine after flashing.
Sent from my GT-I9300 using xda app-developers app
AB_ said:
On my Verizon GS3.
I was using a stock-rooted ROM, and then today tried to install the latest wanamlite.
Even though it says No Wipe, I did just to be safe in CWM (or so I thought).
When trying to flash the ROM, I got the "assert failed:write_raw_image("/tmp/boot.img","boot")" error , and I remember seeing a (status 7) error
Then I tried to reboot... and then nothing but a black screen.
I've tried the Volume Down + Home + Power button to get into "Download Mode" with no success.
I would appreciate any help towards getting this rom on my device.
PS. I've searched, and read these threads
- http://forum.xda-developers.com/showthread.php?t=1045887
- http://forum.xda-developers.com/showthread.php?t=1767226
- http://forum.xda-developers.com/showthread.php?t=1526599
Can't really seem to figure things out.
Click to expand...
Click to collapse
Maybe you are in the wrong thread... this is international S3 thread, not verizon, try here: http://forum.xda-developers.com/forumdisplay.php?f=1708
but i cannot help you
Anyone have an idea why every time I install an aosp rom it glitches at the Samsung boot screen then just goes black and I have to pull the battery? I've installed clean, jelly beans and jedi Rom without issue. Any help is appreciated.
Update your twrp then try again. Make sure your doing full wipes and flashing gapps
Sent from my SCH-I605 using Tapatalk 2
hopesrequiem said:
Update your twrp then try again. Make sure your doing full wipes and flashing gapps
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Just updated my TWRP to 2.4 and did what you suggested with the wiping and same problem.
The Samsung Galaxy screen glitches to half way off the screen, then goes off, then comes back on then the whole thing goes black and nothing.
I'm going to try another rom and see if it still does it as well.
dudeicles said:
Just updated my TWRP to 2.4 and did what you suggested with the wiping and same problem.
The Samsung Galaxy screen glitches to half way off the screen, then goes off, then comes back on then the whole thing goes black and nothing.
I'm going to try another rom and see if it still does it as well.
Click to expand...
Click to collapse
Even with another ROM it doesn't seem to want to work. It's really weird, because any Touchwiz ROM works fine, it only does it on AOSP roms..... I'm hoping someone knows what the fix for this is.
dudeicles said:
Even with another ROM it doesn't seem to want to work. It's really weird, because any Touchwiz ROM works fine, it only does it on AOSP roms..... I'm hoping someone knows what the fix for this is.
Click to expand...
Click to collapse
Odin to stock then re unlock and try this all again? I'm not sure what else you can try. I flip between aosp and tw almost daily
Sent from my SCH-I605 using Tapatalk 2
The Note 2 that couldn't...
Sent from my SCH-I605 using Tapatalk 2
1ManWolfePack said:
The Note 2 that couldn't...
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Heh I think I can I think I can...I was thinken are you trying to flash the file that the post links to because thats not the right one you need to get the note 2 lte one tolte..just a though I downloaded the wrong one first but caught it
http://changelog.bbqdroid.org/#t0lte/cm10.1/next
in my experience, you need to do a factory wipe again AFTER you install or you will get a bootloop.
I think CM10.1 mentions that in their install process.
Acery said:
in my experience, you need to do a factory wipe again AFTER you install or you will get a bootloop.
I think CM10.1 mentions that in their install process.
Click to expand...
Click to collapse
Yeah it can't hurt even if they don't say that
Sent from my SCH-I605 using Tapatalk 2
Acery said:
in my experience, you need to do a factory wipe again AFTER you install or you will get a bootloop.
I think CM10.1 mentions that in their install process.
Click to expand...
Click to collapse
Would it help in any way to change to CWM when flashing my AOSP roms?
dudeicles said:
Would it help in any way to change to CWM when flashing my AOSP roms?
Click to expand...
Click to collapse
I would try cwm, I had a gs3 that couodnt flash anything with cwm but could with twrp, my note was the opposite, cwm was awful on it.
Just ran into something very interesting . When I installed Rom Manager and flashed the CWM recovery, I rebooted and my boot screen did the exact same thing it was doing installing AOSP roms. It would seem my problem may just be CWM.
dudeicles said:
Just ran into something very interesting . When I installed Rom Manager and flashed the CWM recovery, I rebooted and my boot screen did the exact same thing it was doing installing AOSP roms. It would seem my problem may just be CWM.
Click to expand...
Click to collapse
I've heard too many issues with cwm to even try it. Twrp has been flawless for me so why switch? If it ain't broke, don't fix it.
Sent from my SCH-I605 using Tapatalk 2
Ok, so update - Odin'd back to stock and re-rooted using the Casual method. I have the most recent TWRP installed and when i install the AOSP rom it does the exact same thing. I'm thinking about videotaping what the boot animation does and maybe someone can look at it and see what the cause may possibly be.
If anyone has any other suggestions i'm all ears. Again, any rom based on STOCK works without issue (Clean Rom, Jelly Beans and Jedi), but only AOSP roms (And CWM) crash the phone at "Samsung Galaxy Note II" screen on startup.
Thanks for the suggestions so far, just weird it's not working. I may have the single note 2 to never run AOSP roms. LOL
so... oddly enough i still have trouble installing AOSP roms. the only AOSP rom i have been able to install so far is Paranoid Droid. I am slowly trying each one just to see which one i can force to work. Am I the only person who can't just flash whichever rom I want whenever?
Anyone with other ideas on this? I was frequently flashing back and forth between TW and AOSP. The other day I tried to flash AOSP again and get a failed message in TWRP. Already using latest version of TWRP. I then restore a backup of TW. Download again, verify md5, get failed message again. And yes, I wiped everything...same thing I do everytime. Now I have tried to DL and flash multiple different AOSP roms and I get failed everytime. Decided to try CWM recovery and that just aborts. I have NO problems flashing TW roms though
Follow the advice to Odin back to stock and start over. Otherwise, get a replacement and tell them it's acting weird and slow haha.
Sent from my SCH-I605 using xda app-developers app
Same here!!
spydersilk said:
Anyone with other ideas on this? I was frequently flashing back and forth between TW and AOSP. The other day I tried to flash AOSP again and get a failed message in TWRP. Already using latest version of TWRP. I then restore a backup of TW. Download again, verify md5, get failed message again. And yes, I wiped everything...same thing I do everytime. Now I have tried to DL and flash multiple different AOSP roms and I get failed everytime. Decided to try CWM recovery and that just aborts. I have NO problems flashing TW roms though
Click to expand...
Click to collapse
I currently have a Tmobile Note 2. And i recently ran into the same issue. I think it started after installing a certain paranoid andrroid rom, which wrote OS folders differently from what i am normally used to seeing. The folders were 0, legacy, and obb. I also notice that it changed my device id to an SGH-i317, which is an ATT Note 2. The rom was a port from an ATT rom of course, but if it was for ATT, it wouldn't work on my device right? I installed GOOmanager, and flashed the OPEN INSTALL SCRIPT. Which it flashed the ATT version. Everything still worked. I flashed back to stock, and updated OTA. Still nothing. I've also noticed that, if i can open the zip file on my pc, it will work on my phone. For some reason, The AOSP files read invalid. While the Touchwiz roms open like a regular zip file.
Any help is appreciated. Hope some of this info helps.
Just realized i posted in the Verizon section. But i think you and I are the only two people with this issue...lol
slinky42 said:
I think it started after installing a certain paranoid andrroid rom, which wrote OS folders differently from what i am normally used to seeing. The folders were 0, legacy, and obb.
Just realized i posted in the Verizon section. But i think you and I are the only two people with this issue...lol
Click to expand...
Click to collapse
This is standard on 4.2.2 ROMs. It is related to the multi-user implementation.
slinky42 said:
I currently have a Tmobile Note 2. And i recently ran into the same issue. I think it started after installing a certain paranoid andrroid rom, which wrote OS folders differently from what i am normally used to seeing. The folders were 0, legacy, and obb. I also notice that it changed my device id to an SGH-i317, which is an ATT Note 2. The rom was a port from an ATT rom of course, but if it was for ATT, it wouldn't work on my device right? I installed GOOmanager, and flashed the OPEN INSTALL SCRIPT. Which it flashed the ATT version. Everything still worked. I flashed back to stock, and updated OTA. Still nothing. I've also noticed that, if i can open the zip file on my pc, it will work on my phone. For some reason, The AOSP files read invalid. While the Touchwiz roms open like a regular zip file.
Any help is appreciated. Hope some of this info helps.
Just realized i posted in the Verizon section. But i think you and I are the only two people with this issue...lol
Click to expand...
Click to collapse
Did you ever get your phone to install the AOSP Roms? Mine worked when l just let the phone sit. Now it works fine all the time.
Sent from my SCH-I605 using xda app-developers app
I flashed CM10. That went smooth, but started giving me issues a few hours in, so I decided to flash back to ICS. I've done this without a hitch 2 times prior.
Now I get, "Error while restoring /system!" when trying to restore a CM9 backup (one that I've used once already, so I know it was a good backup).
I tried a full system restore to factory GB through ODIN, then reflashed CWM recovery in ODIN, then tried to restore the backup. Nothing but that message...repeatedly.
I then tried flashing a stock, rooted, ICS zip, that worked (flashed) okay (while a few other ROM's did not). Then attempted the restore again...nothing new. Same thing.
I tried flashing the CM9 zip I originally used (it was a nightly that worked well for me). CWM would not execute it.
I saw somewhere someone said to modify the "updater-script" by removing the lines:
"assert(getprop("ro.product.device") == "SGH-I717" || getprop("ro.build.product") == "SGH-I717" ||
getprop("ro.product.device") == "quincyatt" || getprop("ro.build.product") == "quincyatt");".
That actually worked and I was able to flash that with no issues.
I tried the restore...again...to no avail.
I guess if I have to "start from scratch" with everything, so be it, but I would REALLY rather not have to if possible.
I have read through a lot here in the forums, as well as done internet searching. I've seen info that is close to what I'm experiencing, but nothing exactly like it.
I'm at a loss right now.
I'd appreciate any new help that anyone can offer.
Thanks everyone.
Did you by chance rename your backup? If so, is there a space in the name? Do you have the latest version of CWM?
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Bubba got it .....thanks brother ...g
Sent from my SAMSUNG-SGH-I717 using XDA Premium HD app
Bubbajoe...thank you.
This morning, while starting to go through system settings and trying to get things close to back to where they were before, I went into ROM Manager (installed by default in CM9) seeing you mention version of the app (and for the record for anyone having the same issue, I left the naming of the backup alone. It was the default that the app gives the file).
While I had tried a couple different CWM versions, the last I was on was v5.8.4.3. There was v5.8.4.8 available. So in a last ditch effort, and keeping in mind that sometimes the solution could either be simplest or the most obviously overlooked one, I updated to that newest version (happens to be the non-touch one), and thought "what the hell...it can't get any worse" and tried the restore one last time. I'm pretty sure I had 5.8.4.8 running when I made the backup, but wasn't thinking that could be the issue.
And it worked! Go figure. That one small version difference did the trick.
Thanks again man!
:thumbup:
Bubbajoe40356 said:
Did you by chance rename your backup? If so, is there a space in the name? Do you have the latest version of CWM?
Click to expand...
Click to collapse
Sent from my Mental 'Note'.
Oh snap. I was helpful. Better write that down. glad it helped man. Have a good one.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Yeah man. Me too.
Sometimes its the smallest things that make a big difference.
Bubbajoe40356 said:
Oh snap. I was helpful. Better write that down. glad it helped man. Have a good one.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
Sent from my Mental 'Note'.
Here are all of the radio images that are currently available for the Note 2. These are packaged for flashing in recovery (CWM/TWRP). I'm posting these here because apparently the other images are all offline or unavailable anymore. I make no promises about these working, improving signal, or doing much of anything, but they're here anyway. If you need to know how to use these, flash your phone to stock and leave it locked, I'm not here to support stupidity. Enjoy.
VRALJB Modem
VRALL4 Modem
VRAMC3 Modem
VRUEMJ9 Modem
Than you!!!!
Sent from my SCH-I605 using Tapatalk
Thanks for putting some updated links Imnuts. I try to keep them perma-saved so I don't have to worry about that problem when I need a modem lol.
Do you know if we're safe mix-matching modems and ROMs? Like could I run VRALL4 with the new 4.3 leak? I'm not liking this MJ9 on my phone atm.
Is the latest radio from today or is it from the leak?
Does this avoid us having to use ODIN to install the modem?
Anyone try the latest yet with official ota?
Sent from my SCH-I605 using xda app-developers app
Skilover said:
Does this avoid us having to use ODIN to install the modem?
Click to expand...
Click to collapse
Is this a trick question? Did you not read the op??? It says pretty clearly that it can be flashed through twrp/cwm....my goodness
Sent from my SCH-I605 using xda app-developers app
npainter7 said:
Is this a trick question? Did you not read the op??? It says pretty clearly that it can be flashed through twrp/cwm....my goodness
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
I got that part. I am so sorry, I didn't ask this correctly. What I'm trying to ask is, does this achieve everything that the ODIN package floating around does, which includes the modem and perhaps other things. I know it takes the phone back to stock as well. I have no idea why that would be necessary to install a radio. I've flashed radios before.
My goal is to be able to install one of the 4.3 TW roms that requires the MJ9 radio for wifi to work. If this achieves that goal, then flashing this file is clearly the way to go!!!
Thanks for this @imnuts !
Sent from my SCH-I605 using Tapatalk
Tried flashing j9 radio and don't seem to work on cm11 nightly
Skilover said:
I got that part. I am so sorry, I didn't ask this correctly. What I'm trying to ask is, does this achieve everything that the ODIN package floating around does, which includes the modem and perhaps other things. I know it takes the phone back to stock as well. I have no idea why that would be necessary to install a radio. I've flashed radios before.
My goal is to be able to install one of the 4.3 TW roms that requires the MJ9 radio for wifi to work. If this achieves that goal, then flashing this file is clearly the way to go!!!
Click to expand...
Click to collapse
I second this question. I am not going to bust out Odin. But if this is the same I will flash this and a new room at my leisure. I have been reading threads for thirty minutes and now I know I am not the only one that is wondering this.
Sent from my SCH-I605
JustusIV said:
I second this question. I am not going to bust out Odin. But if this is the same I will flash this and a new room at my leisure. I have been reading threads for thirty minutes and now I know I am not the only one that is wondering this.
Sent from my SCH-I605
Click to expand...
Click to collapse
Ive been on the leak for 5 days. I flashed modem in recovery with this same type of file from another thread. I had no issues. Just flashed official, this modem in recovery, and then latest devil kernel. I can confirm this works just fine instead of odin. Im wondering if the odin flashing might be causing issues for some. In 5 days i had no fcs and no reboots with leak.
Sent from my SCH-I605 using xda app-developers app
donnyp1 said:
Ive been on the leak for 5 days. I flashed modem in recovery with this same type of file from another thread. I had no issues. Just flashed official, this modem in recovery, and then latest devil kernel. I can confirm this works just fine instead of odin. Im wondering if the odin flashing might be causing issues for some. In 5 days i had no fcs and no reboots with leak.
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
I flashed the official, this modem and left the default kernel. For some reason, it would flash the sammy boot screen twice, then take me right back to recovery. Do you have to use an alternate kernel?
MADDAN18 said:
I flashed the official, this modem and left the default kernel. For some reason, it would flash the sammy boot screen twice, then take me right back to recovery. Do you have to use an alternate kernel?
Click to expand...
Click to collapse
I dont know if you do or not. It runs perfect on devil with great battery just on stock settings.
Sent from my SCH-I605 using xda app-developers app
I flashed the zip, it said successful, installed new rom-and it says modem still is VRALL4.
This doesn't seem right.
Please excuse me if I'm being stupid-tough crowd here!
When I try to flash VRUEMJ9 Modem with twrp 2.3.2.3 it fails on an assert:
asser filed: getprop("ro.product.device") == "t0ltecdm
getprop("ro.product.device") == i605" ||
getprop("ro.product.device") == SCH-II605
Error in /external_sdcard/.../VRUEMJ9_.. (status 7)
(yes I verified the md5sum as 881d4b58aaf...a31b38 using MD5Checker)
I used this same setup to flash the previous radio.
(part of the message is truncated because of bad linewraps)
Skilover said:
I got that part. I am so sorry, I didn't ask this correctly. What I'm trying to ask is, does this achieve everything that the ODIN package floating around does, which includes the modem and perhaps other things. I know it takes the phone back to stock as well. I have no idea why that would be necessary to install a radio. I've flashed radios before.
My goal is to be able to install one of the 4.3 TW roms that requires the MJ9 radio for wifi to work. If this achieves that goal, then flashing this file is clearly the way to go!!!
Click to expand...
Click to collapse
I think that Odin isnt just for the radio but other parameters also. Im not sure but from what ive read thats what it sounds like. There was another zip that was supposed to work but it never did for me anyway so i had to use odin. It will be worth it to have it done right 4.3 is great i run jellywiz
Sent from my SCH-I605 using Tapatalk
jake21 said:
When I try to flash VRUEMJ9 Modem with twrp 2.3.2.3 it fails on an assert:
asser filed: getprop("ro.product.device") == "t0ltecdm
getprop("ro.product.device") == i605" ||
getprop("ro.product.device") == SCH-II605
Error in /external_sdcard/.../VRUEMJ9_.. (status 7)
(yes I verified the md5sum as 881d4b58aaf...a31b38 using MD5Checker)
I used this same setup to flash the previous radio.
(part of the message is truncated because of bad linewraps)
Click to expand...
Click to collapse
You're on a pretty old version of twrp
http://goo.im/devs/OpenRecovery/t0ltevzw//openrecovery-twrp-2.6.3.1-t0ltevzw.zip
Here's the latest....flash in recovery.
Sent from my SCH-I605 using XDA Premium HD app
Yea I know and you can also reference it via google play. My problem is I am a bit of a newbie and it was not obvious to me how to install. You might ask how I got the current version - well that was a side effect of the folks making it really easy to crack the note 2 back in Dec (2012). You just ran this script and it cracked the boot loader and installed twrp (I believe it used odin) so I never really did learn how to update twrp.
This afternoon I tried the version of google play but it wanted to isntall an 'open bootloader" and I wasn't sure why it wanted to do that since my bootloader was already cracked and all I wanted it to do is to update twrp.
=
So I guess this begs the question do I download this zip file and then use twrp 2.6.3.1 to install it like a rom ?
MADDAN18 said:
You're on a pretty old version of twrp
http://goo.im/devs/OpenRecovery/t0ltevzw//openrecovery-twrp-2.6.3.1-t0ltevzw.zip
Here's the latest....flash in recovery.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
jake21 said:
Yea I know and you can also reference it via google play. My problem is I am a bit of a newbie and it was not obvious to me how to install. You might ask how I got the current version - well that was a side effect of the folks making it really easy to crack the note 2 back in Dec (2012). You just ran this script and it cracked the boot loader and installed twrp (I believe it used odin) so I never really did learn how to update twrp.
This afternoon I tried the version of google play but it wanted to isntall an 'open bootloader" and I wasn't sure why it wanted to do that since my bootloader was already cracked and all I wanted it to do is to update twrp.
=
So I guess this begs the question do I download this zip file and then use twrp 2.6.3.1 to install it like a rom ?
Click to expand...
Click to collapse
That is correct. Simply download the zip, copy it to your sd card, boot into recovery, choose the zip and flash (just like you would a ROM. When you reboot, twrp will be updated. You can also download goo manager from the market. And choose "install custom recovery" I just find flashing the zip eliminates several steps ie software down loads etc.
Sent from my SCH-I605 using XDA Premium HD app