[Q] Clockworkmod V2.6.0.1 is gone! - EVO 4G Q&A, Help & Troubleshooting

Does anyone know if there was a change made to ROM Manager/Clockworkmod Recovery yesterday?? I had V2.6.0.1 installed and yesterday afternoon I got a notice that Clockworkmod Recovery had been upgrade and to download the new release. It was 3.0.0.5 (RomManager Version 3.0.0.7) so I updated my recovery.
This morning I tried to install a ROM that I have installed dozens of times before using v2.6.0.1 but this time it wouldn't run because of the scripting issues within V3. I tried to find & reload V2.6.0.1 but RomManager does not list it as an alternate install at the bottom of RomManager's setting page.
Anyone else receive the update notice?

I got the update message yesterday too! I chose not to update because I knew about the issues you talked about. You can flash RA recovery, flash ROM, then go back if you need to. Or I can get you the zip if clockwork that does both versions of scripting..... Wait can't do that from the xda app....okay ill post it up when I get to my work computer...unless someone else throws it up before I do.
Sent from my PC36100 using XDA App

gzibell said:
I got the update message yesterday too! I chose not to update because I knew about the issues you talked about. You can flash RA recovery, flash ROM, then go back if you need to. Or I can get you the zip if clockwork that does both versions of scripting..... Wait can't do that from the xda app....okay ill post it up when I get to my work computer...unless someone else throws it up before I do.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Thanks. I couldn't find a .zip version of 2.6.0.1 on XDA. only the _img version.

ChadH42 said:
Thanks. I couldn't find a .zip version of 2.6.0.1 on XDA. only the _img version.
Click to expand...
Click to collapse
Just great!..I should have never upgraded!

http://mirror1.kanged.net/recoveries/

Guess I got beat to it but here is the zip file anyways.

CM still has an option to go to 2.5.0.7
I did not know this Sh%^t and could not restore any nands and was forced to unroot and start over. Seemed easier (for me) than pushing a recovery. I was not able to boot into anything to make the change... one would think that clockwork would play nice with older clockworks

apfrost said:
http://mirror1.kanged.net/recoveries/
Click to expand...
Click to collapse
gzibell said:
Guess I got beat to it but here is the zip file anyways.
Click to expand...
Click to collapse
thanks!! I'm keeping this so if It happens again...

How do I install the .zip file? Installing via recovery is only temporary. Next reboot it's back to 3.0.0.5
Sent from my PC36100 using Tapatalk

I only use it as a temp. I think to actually install you have to use a .img file....???? Not sure on that one. Someone has the answer.
Sent from my PC36100 using XDA App

gzibell said:
I only use it as a temp. I think to actually install you have to use a .img file....???? Not sure on that one. Someone has the answer.
Click to expand...
Click to collapse
gzibell, I know this is an old thread, and I don't even have an Evo (I have a lowly Sprint Hero), I was just looking for an earlier version of clockwork than the 3.0.0.5 I'm currently using and I ran across this thread, and your post made me aware that I could flash 2.5.0.7 strictly as a temp, without losing the embedded 3.0.0.5 that I'm currently using...what an awesome idea!
So I tried it, and it works great!
Just want to say thanks for that post, friend!

Related

[Q] Updating CWM Recovery

I rooted my phone using Unrevoked3. Of course by doing this, an outdated version of CWM Recovery was flashed to my phone. Can I flash a newer version of CWM Recovery from CWM or will that mess up my phone?
VisualPerfection said:
I rooted my phone using Unrevoked3. Of course by doing this, an outdated version of CWM Recovery was flashed to my phone. Can I flash a newer version of CWM Recovery from CWM or will that mess up my phone?
Click to expand...
Click to collapse
Flashing a new version won't hurt a thing. An easy way is to install ROM manager from market, open ROM manager and select the first option to flash cwm. After that you can uninstall ROM manager if you wish. Or you can dl the version you want and install it from your SD card.
Sent from my ADR6350 using xda premium
CondemnedSoul said:
Flashing a new version won't hurt a thing. An easy way is to install ROM manager from market, open ROM manager and select the first option to flash cwm. After that you can uninstall ROM manager if you wish. Or you can dl the version you want and install it from your SD card.
Sent from my ADR6350 using xda premium
Click to expand...
Click to collapse
Thanks, that's what I was thinking... Just wanted to be sure! And hey, I gotta also say thanks for helping me bring life to my dad's Eris. I flashed your ROM on it and he's really noticed a difference. Ha ha, it's actually usable now!
VisualPerfection said:
Thanks, that's what I was thinking... Just wanted to be sure! And hey, I gotta also say thanks for helping me bring life to my dad's Eris. I flashed your ROM on it and he's really noticed a difference. Ha ha, it's actually usable now!
Click to expand...
Click to collapse
Any time glad people are still enjoying it. I'll be updating the Eris ROM with the R.I.P. release soon. Working on getting cm fully synced back up now for that, updating my inc cm ROM and starting the condemned cm series for inc2. Also have a new inc ROM in testing now. Just have a few things to work out with it yet.
Sent from my ADR6350 using xda premium

how do I rollback to the old recovery

Hello,
I am having issues with the new recovery mode 6.0.14, how do I roll back to the recovery mode before this?
I updated my recovery using rom manager, it does not give me the option to roll back
thanks
Which one you want? I have 6.0.1.3 by sk8r and its touch. I can upload it but other than that you gotta download the one you want and flash it in recovery..
I used ROM manager and went back to 5.xxx
noodles2224 said:
Which one you want? I have 6.0.1.3 by sk8r and its touch. I can upload it but other than that you gotta download the one you want and flash it in recovery..
Click to expand...
Click to collapse
I can not remember what exactly was the version# it was before it got updated, I know it was version# 5 something.
I haven't been able to do any nandroid backup ever since it was updated to version 6.0.1.4
I want to stay away from touch, I haven't had any good luck with it
tomasitoc said:
I can not remember what exactly was the version# it was before it got updated, I know it was version# 5 something.
I haven't been able to do any nandroid backup ever since it was updated to version 6.0.1.4
I want to stay away from touch, I haven't had any good luck with it
Click to expand...
Click to collapse
TWRP FTW!! 2.22 has no issues what so ever!!
Sent from my SGH-T989 using xda premium
tomasitoc said:
I can not remember what exactly was the version# it was before it got updated, I know it was version# 5 something.
I haven't been able to do any nandroid backup ever since it was updated to version 6.0.1.4
I want to stay away from touch, I haven't had any good luck with it
Click to expand...
Click to collapse
I had the same issue, this is what i did...
open ROM manager, scroll to the bottom you will see a option that says something about all recoveries, click that it shows 5.0.2.6 and 5.0.2.7, the .7 is the one you want, hit that and it will install that for you..
worked for me
Hit thanks if i helped you!
Thank you

[Q] Cannot flash rom!! Installation Aborted, help!

Just got my gs3 today and decided to root using this method http://forum.xda-developers.com/showthread.php?t=1746682
Not really so tech-savy with this yet and after the whole root process of odin3 i reboot into recovery, wipe/cache/dalvik then flash the new miui 2.10.19 http://miuiandroid.com/community/threads/2-10-19.18540/ one i hit flash it says installation failed blah blah blah (status 7) getprop. Yeah all that junk, so i searched up on the forums and the only solution i find is to update cwm and i have, to 6.0.1.4 and still same thing!! installation error, aborted. Can someone please help me out :crying: I'm sorry if im a noob, just trying to flash a rom here
Update CWM via ROM Manager.
Download again
Sent from my SGH-T999 using xda app-developers app
use twrp
theexel said:
Update CWM via ROM Manager.
Click to expand...
Click to collapse
i did, still no luck
mt3g said:
use twrp
Click to expand...
Click to collapse
and this was my last thing i tried before bed last night and still didnt work! should i just unroot then re-root all over again?
How did you update to 6.0.1.4 when 6.0.1.2 is the latest version? And no, you don't need to re root. You don't need root to flash firmware.
Aerowinder said:
How did you update to 6.0.1.4 when 6.0.1.2 is the latest version? And no, you don't need to re root. You don't need root to flash firmware.
Click to expand...
Click to collapse
Looking on the forums someone posted a link to download an updated 6.0.1.4 so I tried that since 6.0.1.2 wasnt working. There's gotta be something simple to fix that I dont know about, ive flashed and rooted my htc sensation and mytouch4g easy and never had installation failure when flashing. Can someone walk me through what exactly I need to be fully rooted and flash a rom!?
How could cwm not be working if its updated to latest version? I dont think im downloading the wrong rom and its not a bad link. Even tried dragging it onto my internal sd wirh debugging off. Btw I have the 32 gb s3 with does not have an external sd.
The way I fix that was I rerootes my phone into latest clockwork recovery. I didn't remove the root I just rerootee it. Look for cwr 6 I think.
Sent from my SGH-T999 using xda app-developers app
From watching the video given for the toolkit, when in odin and have to open up pda then go to the toolkit files and then root all my files are in winRAR type and his are in tar archive type. Does that matter at all? And also when clicking on the pda then root you chose the file /boot-insecure-tmo-t99uvalem-cwm but when in odin and clicking this file on the little winrar icon to the left of the file name its the only one with a little like key lock, doesnt know if thats an issue or anything just something i noticed because when accessing the toolkit files on my c drive and going to the root folder, the key icon is no longer there.. Any ideas??
Reading about people flashing a kernal in recovery then flashing the rom and working but when you flash a rom isnt it flashing the kernal it comes with also? Or is this the problem
Well, I re ran the toolkit, re did the root and odin process same as i did the first time, downloaded rom straight from my phone flashed again still getting status 7 error/ installation aborted -______- ugh...
Brad4891 said:
Looking on the forums someone posted a link to download an updated 6.0.1.4 so I tried that since 6.0.1.2 wasnt working. There's gotta be something simple to fix that I dont know about, ive flashed and rooted my htc sensation and mytouch4g easy and never had installation failure when flashing. Can someone walk me through what exactly I need to be fully rooted and flash a rom!?
Click to expand...
Click to collapse
Look at my signature for the proper CWM. I don't know where you saw 6.0.1.4 for our device, but the main thread and the developers website show no sign of it. And download CM10 from get.cm, d2tmo. If you that doesn't work, you don't have a SGH-T999.
I can't believe I didn't see this before....what is the exact file name of the rom you are flashing?
I looked and did not see our phone listed in the op. Looks like the international one is there (codename m0?). But no d2tmo, d2att, etc.
Unless I just missed it there, you do not want to even try flashing that anymore! If I'm right you just got very lucky dude!
Sent from my SGH-T999 using xda app-developers app
Aerowinder said:
Look at my signature for the proper CWM. I don't know where you saw 6.0.1.4 for our device, but the main thread and the developers website show no sign of it. And download CM10 from get.cm, d2tmo. If you that doesn't work, you don't have a SGH-T999.
Click to expand...
Click to collapse
Okay, so i just followed and installed everything you had in your signature and it finally is flashing hellfire!! Hours of frustration i think i finally got it! Thank you so much
Brad4891 said:
Okay, so i just followed and installed everything you had in your signature and it finally is flashing hellfire!! Hours of frustration i think i finally got it! Thank you so much
Click to expand...
Click to collapse
I thought you were trying to flash miui...
Glad you got it sorted out.
Just for the future though, never flash anything not built for the TMobile SGH-T999 (codename d2tmo). If you do flash an international GS3 rom it will brick your device. I think this woulda happened had the miui rom from the link in op actually flashed.
Sent from my SGH-T999 using xda app-developers app
Aerowinder said:
Look at my signature for the proper CWM. I don't know where you saw 6.0.1.4 for our device, but the main thread and the developers website show no sign of it. And download CM10 from get.cm, d2tmo. If you that doesn't work, you don't have a SGH-T999.
Click to expand...
Click to collapse
DocHoliday77 said:
I thought you were trying to flash miui...
Glad you got it sorted out.
Just for the future though, never flash anything not built for the TMobile SGH-T999 (codename d2tmo). If you do flash an international GS3 rom it will brick your device. I think this woulda happened had the miui rom from the link in op actually flashed.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
I was at first but then changed my mind, both werent working before hand though when i was getting the errors.
And im using hellfire and the rom is super smooth like butter. I have one problem though, its notifications. Whenever receiving texts i dont get a vibration or light pulse. Sometimes randomly i get a vibration. Anyone know how to fix?

At a loss with cwm

Hello,
So I've been rooted for a while now, i was going to install a custom rom but decided not to a few months ago. Tonight, i decided to install aokp, however my phone would not go into cwm, only stock recover. I could have sworn it was installed, but fine, so i installed it once again with auto reboot in odin checked, and it still wouldnt enter cwm. I then tried to install it again with auto reboot checked off so i could see if i could enter it without the reboot. I ended up getting into it, but then when i was taking a NANDROID, it just froze on one of the first steps. Fine, reboot, try to enter cwm again. Nope, just stock android recovery. I am sure im installing it correctly and pressing the right button combos. I am at a total loss for what is stopping me from being able to enter cwm. I hope you guys know/help me find whats going on.
Thanks!!!
Zay
maybe you didn't actually "root" your phone to begin with lol
are you sure you have "superuser" or "superSU" app?
anyways to get CWM or TWRP recovery you need
find a up-to-date CWM or TWRP (if i spell teamwin recovery correctly)
download it
put your phone in ODIN Mode (download mode) by power + vol down + home
flash the recovery
i personally think twrp is better
they just released a new version which support ExFat
and all you need is just use terminal on your phone to install it.
pcshano said:
maybe you didn't actually "root" your phone to begin with lol
are you sure you have "superuser" or "superSU" app?
anyways to get CWM or TWRP recovery you need
find a up-to-date CWM or TWRP (if i spell teamwin recovery correctly)
download it
put your phone in ODIN Mode (download mode) by power + vol down + home
flash the recovery
i personally think twrp is better
they just released a new version which support ExFat
and all you need is just use terminal on your phone to install it.
Click to expand...
Click to collapse
Yes my phones rooted.
If you actually read my post, you'd know that that is EXACTLY what I am doing.
Thanks anyways though..
Zay48 said:
If you actually read my post, you'd know that that is EXACTLY what I am doing.
Thanks anyways though..
Click to expand...
Click to collapse
i have no idea how i missed that odin part on your part... i read everything but somehow i just missed that part alone 0_0
anyways
try install twrp recovery instead then
by using terminal emulator
can get it here https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
latest twrp can be found here http://forum.xda-developers.com/showthread.php?t=2074951
pcshano said:
i have no idea how i missed that odin part on your part... i read everything but somehow i just missed that part alone 0_0
anyways
try install twrp recovery instead then
by using terminal emulator
can get it here https://play.google.com/store/apps/details?id=jackpal.androidterm&hl=en
latest twrp can be found here http://forum.xda-developers.com/showthread.php?t=2074951
Click to expand...
Click to collapse
Aha its alright
I'd like to stick with cwm though, its what im familiar with. If nobody else has an answer i'll try it tomorrow though.
Thanks
Zay48 said:
Aha its alright
I'd like to stick with cwm though, its what im familiar with. If nobody else has an answer i'll try it tomorrow though.
Thanks
Click to expand...
Click to collapse
if you still want cwm then i guess you can try flash stock rom and root it again and see
since you're going to flash a custom rom which will delete all your data anyways
Zay48 said:
Aha its alright
I'd like to stick with cwm though, its what im familiar with. If nobody else has an answer i'll try it tomorrow though.
Thanks
Click to expand...
Click to collapse
Stock ROM has a built in script that reloads standard android recovery when it boots. The only way to keep it is to keep Odin auto reboot unchecked, boot directly in and make your nandroid/flash custom. Once you are on a custom ROM CWM will stick.
On a side note TWRP is a very nice recovery and many people find it much easier to use. If you insist on CWM, make sure you have the latest version. You might need to flash CWM again if you had a bad flash. It shouldn't freeze up on a nandroid.
Many people never experienced this because they flashed during early ICS when the device was released. The change was an update just before JB was released which caused this little annoying script to appear.
Sent from my SGH-I747 using xda app-developers app
RPelham said:
Stock ROM has a built in script that reloads standard android recovery when it boots. The only way to keep it is to keep Odin auto reboot unchecked, boot directly in and make your nandroid/flash custom. Once you are on a custom ROM CWM will stick.
On a side note TWRP is a very nice recovery and many people find it much easier to use. If you insist on CWM, make sure you have the latest version. You might need to flash CWM again if you had a bad flash. It shouldn't freeze up on a nandroid.
Many people never experienced this because they flashed during early ICS when the device was released. The change was an update just before JB was released which caused this little annoying script to appear.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thankyou!! That makes sense ;p. When I did get to start making a nandroid last night but it froze, right before it froze it said the free space on my sdcard was 1612 mb (or something like that) This is wrong, I have the 16gb i747 so I have 11.95 gb of usable storage for apps and such, after deleting some big apps I have 4.93 gb available, my sdcard is a 16 gb sdcard which has 12.06 gb available. Do the math and I have enough room on my sdcard for a nandroid, so what could be causing cwm to freeze and report false information?
Zay48 said:
Thankyou!! That makes sense ;p. When I did get to start making a nandroid last night but it froze, right before it froze it said the free space on my sdcard was 1612 mb (or something like that) This is wrong, I have the 16gb i747 so I have 11.95 gb of usable storage for apps and such, after deleting some big apps I have 4.93 gb available, my sdcard is a 16 gb sdcard which has 12.06 gb available. Do the math and I have enough room on my sdcard for a nandroid, so what could be causing cwm to freeze and report false information?
Click to expand...
Click to collapse
Bump
what version of CWM are you currently running?
you could always try to download GooManager or ROM Manager from the Play Store.
then from one of those, install the custom recovery, GooManager for TWRP or ROM Manager for CWM.
xBeerdroiDx said:
what version of CWM are you currently running?
Click to expand...
Click to collapse
3.0.7
Zay48 said:
3.0.7
Click to expand...
Click to collapse
That is a very out dated version as they are now up to version 6.0.2.3. I would try getting an updated CWM. that could very well fix your freezing/reporting problems...
Sent from my SGH-I747 using xda app-developers app
CWM is very very funny and one of the reasons I switched to TWRP was for stability
In my experience errors come up on restoring images when 1) you don't use the same version you backed up the image with 2) you don't get to CWM through the same method you used while making the image (ie through ROM manager with your phone on).
zetsui said:
CWM is very very funny and one of the reasons I switched to TWRP was for stability
In my experience errors come up on restoring images when 1) you don't use the same version you backed up the image with 2) you don't get to CWM through the same method you used while making the image (ie through ROM manager with your phone on).
Click to expand...
Click to collapse
He's not having a problem restoring images, he's having a problem making his first nandroid.
Sent from my SGH-I747 using xda app-developers app
Zay48 said:
3.0.7
Click to expand...
Click to collapse
Holy hell! CWM 3.0 is still around? Like RP said, you're recovery is severely outdated.
RPelham said:
That is a very out dated version as they are now up to version 6.0.2.3. I would try getting an updated CWM. that could very well fix your freezing/reporting problems...
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
This.
Also, I was a long time CWM touch user on my old NS. After using TWRP on this phone, I will never look back at CWM. TWRP is much more user friendly. Give it a shot OP unless you're adamant in using CWM. Again, update your recovery.
Download rom manager and update your cwm and then try making a nandroid again.
Sent from my SGH-I747 using xda app-developers app
CrackerTeg said:
Holy hell! CWM 3.0 is still around? Like RP said, you're recovery is severely outdated.
This.
Also, I was a long time CWM touch user on my old NS. After using TWRP on this phone, I will never look back at CWM. TWRP is much more user friendly. Give it a shot OP unless you're adamant in using CWM. Again, update your recovery.
Click to expand...
Click to collapse
I was also a CWM user, but after I got my s3 and my first flash of CWM on the s3 hard bricked my phone, I decided to use TWRP. Little did I know I was missing out on what TWRP had to offer. I won't ever turn back to CWM again lol.
That said... If you insist in CWM, this is the guide I followed to get a successful CWM flash. (This was the CWM I was running successfully for the brief time TWRP disbanded.)
http://wiki.cyanogenmod.org/w/Install_CM_for_d2att
The above is for the ATT variant only. If you have a different variant and can't find the link, post back and I'll find it for you
Sent from my SGH-I747 using xda app-developers app
CrackerTeg said:
Holy hell! CWM 3.0 is still around? Like RP said, you're recovery is severely outdated.
This.
Also, I was a long time CWM touch user on my old NS. After using TWRP on this phone, I will never look back at CWM. TWRP is much more user friendly. Give it a shot OP unless you're adamant in using CWM. Again, update your recovery.
Click to expand...
Click to collapse
apparently it's still around because new android users who want to root use those guides with outdated files
RPelham said:
I was also a CWM user, but after I got my s3 and my first flash of CWM on the s3 hard bricked my phone, I decided to use TWRP. Little did I know I was missing out on what TWRP had to offer. I won't ever turn back to CWM again lol.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Preach brother!

Root issues (moved from Virgin rom as requested) Help

I am trying to upgrade my Virgin ROM to the 9.12 build but get a fail upon trying to flash it. The background.... I'm using TWRP recovery and have tried the chainfire root method. Here are the results:
As you can see you can see some conflicting information... all shots were taken in sequence. I'm thinking the fail in twrp is coming from the system not having root but the info is telling me otherwise....
Bump... Anybody???
Sent from my GT-I9505G using xda app-developers app
th3h0ff said:
Bump... Anybody???
Sent from my GT-I9505G using xda app-developers app
Click to expand...
Click to collapse
Do you have the latest SuperSU version?
I'm a little lost at what you are saying.
You flashed a rom, and it said fail, and you think it has to do with Root?
If you have TWRP installed it doesn't matter if you are rooted or not. It's going to over right the system partition regardless if you have root or not.
So it's either a bad download or bad transfer for it to fail.
Sent from my SGH-M919 using Tapatalk 4
I do have the latest SU version by chain fire. And maybe I'm doing something wrong the because I am running the virgin gpe ROM now and that flashed in twrp with no issues. Now when I go to install (after wiping) and select the 9.12 update that I downloaded it hangs on trying to open the zip and fails... I haven't changed any twrp settings but in the write options of twrp what boxes should be checked because system is not by default... Thanks for the replies!
Sent from my GT-I9505G using xda app-developers app
I previously only used cwm so I'm not sure if I should just try that or what... And I've checked the download and md5 for verification
Sent from my GT-I9505G using xda app-developers app
th3h0ff said:
I previously only used cwm so I'm not sure if I should just try that or what... And I've checked the download and md5 for verification
Sent from my GT-I9505G using xda app-developers app
Click to expand...
Click to collapse
You can give CWM a try, I've been using it for a while without any issues. Out of curiosity what version if TWRP you are using? I think most people recommend TWRP 2.5.0.2. I'm using the latest version of CWM.
Sent from my GT-I9505G using xda app-developers app
If all else fails, just start from scratch, get stock UVUAMDL tar, flash it with Odin, make sure to do a factory wipe after you flash it, sometimes bootloops occur if you don't. You don't even have to go past the first screen where you pick the language. Just shut it down from there and boot into download mode and root with Chainfire with Odin, then shut down and boot up again into download mode again and flash custom recovery tar of ur choice with Odin. Then download whatever custom rom zip and install it via custom recovery.
norml said:
If all else fails, just start from scratch, get stock UVUAMDL tar, flash it with Odin, make sure to do a factory wipe after you flash it, sometimes bootloops occur if you don't. You don't even have to go past the first screen where you pick the language. Just shut it down from there and boot into download mode and root with Chainfire with Odin, then shut down and boot up again into download mode again and flash custom recovery tar of ur choice with Odin. Then download whatever custom rom zip and install it via custom recovery.
Click to expand...
Click to collapse
Thanks again to everyone... not going to have time to mess with it tonight but I'll update tomorrow. Thanks again
th3h0ff said:
Thanks again to everyone... not going to have time to mess with it tonight but I'll update tomorrow. Thanks again
Click to expand...
Click to collapse
heyyy saw your reply in my thread.
just as @byron1985 suggested there, it sounds like you got a bad download. the flashing scripts are essentially exactly the same from previous version. the flashing process has absolutely zero to do with SuperSU.
edit: re-read. so you've verified the download. if you had success with CWM previously, i would go back to that. i do not use TWRP.
mrvirginia said:
heyyy saw your reply in my thread.
just as @byron1985 suggested there, it sounds like you got a bad download. the flashing scripts are essentially exactly the same from previous version. the flashing process has absolutely zero to do with SuperSU.
edit: re-read. so you've verified the download. if you had success with CWM previously, i would go back to that. i do not use TWRP.
Click to expand...
Click to collapse
Im going to give the twrp 2.5.2 a try as it seems most of my troubles keep happening on the 2.6.3 build. Hopefully that works either way its back to CWM for me as well. Thanks again for taking the time to help out and again sorry about hijacking the thread for a page... Your ROM is absolutely perfect so I appreciate the efforts and time!,
Andrew
SOLVED... tried 2.5 version of TWRP and all went well... odd but apparently my device doesnt like 2.6 versions of TWRP! Thanks to everyone who helped me out and gave me suggestions and thank you to the dev for taking some of his time to assist! It was a great help to me!
th3h0ff said:
SOLVED... tried 2.5 version of TWRP and all went well... odd but apparently my device doesnt like 2.6 versions of TWRP! Thanks to everyone who helped me out and gave me suggestions and thank you to the dev for taking some of his time to assist! It was a great help to me!
Click to expand...
Click to collapse
Good to know you are out of trouble
Sent from my Nexus 10 using xda app-developers app
See you shoulda said you were running 2.6.3 lol
word of advice (and to all who run twrp)
DO NOT RUN ANYTHING GREATER THAN 2.5.2!!!!!!!!!!!!!!

Categories

Resources