Database Info

[Q] CWM sticking, stock recovery isn't coming back

for some reason my cwm recovery is sticking and its causing my play store to stay on 3.4.7
Any ideas on why the recovery is sticking I didn't even touch the install-recovery.sh
Infact all I did was get the stock 4.0.4 image from google flash that:
Format System, data, cache, sd card, dalvik cache
Reboot into bootloader
flash bootloader, radio, update image
then flash cwm recovery and install superuser
after that my stock recovery just won't come back, any ideas?
I left the recovery on stock and the play store updated immediately, i also tried manually flashing the recovery from the stock image package from google that didn't help either.

The stock recovery has nothing at all to do with the market updating

You just need to run
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
using the recovery image in the update .zip. There's a guide here about halfway down. As albundy said though, it shouldn't have any effect on the Market updating.
Edit: Flashing a new recovery will delete all data and so on (afaik) so backup and what not first.

albundy2010 said:
The stock recovery has nothing at all to do with the market updating
Click to expand...
Click to collapse
i remember when i first started rooting and all that if you don't have the stock recovery you don't receive things like OTA updates also, thats why I wanted the stock recovery.
Also if i leave the recovery as stock the market updates immediately thats whats bothering me but when I root (flash CWM) it won't update even after hours of waiting it stays on 3.4.7
x ZackehSoul x said:
You just need to run using the recovery image in the update .zip. There's a guide here about halfway down. As albundy said though, it shouldn't have any effect on the Market updating.
Edit: Flashing a new recovery will delete all data and so on (afaik) so backup and what not first.
Click to expand...
Click to collapse
i flashed the stock recovery it didn't help, for some reason. Thats why I posted this question, thanks for the suggestion though

clean rom

Looking for some input on clean ROM on the TF300T,
This is my second time trying to install it and both times it was successful, however as soon as the boot image loads up it stays stuck loading... I did download the file again thinking it may have been corrupted.
It has been sitting there loading for 20 minutes now.
I am using cwm the latest version and I did not install a kernel still running stock
Any ideas on what could cause this?

chibra said:
Looking for some input on clean ROM on the TF300T,
This is my second time trying to install it and both times it was successful, however as soon as the boot image loads up it stays stuck loading... I did download the file again thinking it may have been corrupted.
It has been sitting there loading for 20 minutes now.
I am using cwm the latest version and I did not install a kernel still running stock
Any ideas on what could cause this?
Click to expand...
Click to collapse
CWM has issues on this unit. Many, many complaints. I use twrp. If you decide to use twrp be sure to choose JB and tf300t version.

Clean ROM is freaking amazing! Seriously just do it I love the mods I can make for it too! Can't wait till I get my volume long press seek mod done! Love this device!
Sent from my SGH-T999
"So I put my phone into airplane mode and threw it... worst transformer ever. -.-" -My friend

tobdaryl said:
CWM has issues on this unit. Many, many complaints. I use twrp. If you decide to use twrp be sure to choose JB and tf300t version.
Click to expand...
Click to collapse
I initially when i first rooted intalled Twrp however i was not able to flash anything at all with it, it would give me errors.... that is the only reason i went to cwm.... I was able to make backups and restores with but ROMs flashing would just fail

chibra said:
I initially when i first rooted intalled Twrp however i was not able to flash anything at all with it, it would give me errors.... that is the only reason i went to cwm.... I was able to make backups and restores with but ROMs flashing would just fail
Click to expand...
Click to collapse
OK. It was just a suggestion since the problem you are experiencing is usually cleared by using twrp.

oryhight sullivan
tobdaryl said:
OK. It was just a suggestion since the problem you are experiencing is usually cleared by using twrp.
Click to expand...
Click to collapse
i m going to give twrp another shot...

i installed http://tinyw.in/5foT
JB version for the TF300T
This is the Rom i m trying to install
http://forum.xda-developers.com/showthread.php?t=2049322
Kernel is still stock and i ve left it that way through the aroma installer
Everytime i flash and reboot i get a boot loop

chibra said:
i installed http://tinyw.in/5foT
JB version for the TF300T
This is the Rom i m trying to install
http://forum.xda-developers.com/showthread.php?t=2049322
Kernel is still stock and i ve left it that way through the aroma installer
Everytime i flash and reboot i get a boot loop
Click to expand...
Click to collapse
I'm sorry it is hard to tell since you have chosen an older twrp to install. The current is five versions later and was updated as the kernels were updated to account for changes. The rom you are flashing is based on 10.4.4.25.

chibra said:
i installed http://tinyw.in/5foT
JB version for the TF300T
This is the Rom i m trying to install
http://forum.xda-developers.com/showthread.php?t=2049322
Kernel is still stock and i ve left it that way through the aroma installer
Everytime i flash and reboot i get a boot loop
Click to expand...
Click to collapse
Use TWRP 2.4.1.0
You are using a very old version of TWRP that has bugs with AROMA installer. So that is most likely where your issues are.

What ROM are you ccoming from? What boot loader are you on.
Sounds to me like you need to upgrade your boot loader and possibly do a full wipe - make sure you are on latest TWRP first otherwise you could brick if you use an older recovery!

sbdags said:
What ROM are you ccoming from? What boot loader are you on.
Sounds to me like you need to upgrade your boot loader and possibly do a full wipe - make sure you are on latest TWRP first otherwise you could brick if you use an older recovery!
Click to expand...
Click to collapse
Wise words. Nobody likes to listen to me so im glad someone else suggested it!

elesbb said:
Use TWRP 2.4.1.0
You are using a very old version of TWRP that has bugs with AROMA installer. So that is most likely where your issues are.
Click to expand...
Click to collapse
Updated the TWRP to the version you mentioned still stuck in boot loop.

sbdags said:
What ROM are you ccoming from? What boot loader are you on.
Sounds to me like you need to upgrade your boot loader and possibly do a full wipe - make sure you are on latest TWRP first otherwise you could brick if you use an older recovery!
Click to expand...
Click to collapse
The only ROM i was able to flash that was fully functioning is cm10.1,
i have also flashed PA 2.9 but had some bugs i couldn't stand (screen rotation not working, extended desktop with no pie)
as for boot loader it says 1.00e by "US _Epad-10.4.2.20-20121228" A03
I just updated the TWRP as recommended on the other post (v2.4.1.0)
on every flash i wipe dalvik / Cache / Factory reset.
Before attempting to boot into Clean Rom i also followed the steps on screen saying to wipe cache and dalvik.
I m hoping PA releases a 3.0 for this device and/or i m able to get Clean rom running

chibra said:
The only ROM i was able to flash that was fully functioning is cm10.1,
i have also flashed PA 2.9 but had some bugs i couldn't stand (screen rotation not working, extended desktop with no pie)
as for boot loader it says 1.00e by "US _Epad-10.4.2.20-20121228" A03
I just updated the TWRP as recommended on the other post (v2.4.1.0)
on every flash i wipe dalvik / Cache / Factory reset.
Before attempting to boot into Clean Rom i also followed the steps on screen saying to wipe cache and dalvik.
I m hoping PA releases a 3.0 for this device and/or i m able to get Clean rom running
Click to expand...
Click to collapse
If you are coming from cm10.1 you will definitely need to do a full wipe as it is non stock. It does say this in the first post. You only do a dalvik and cache wipe when upgrading from the same ROM or in CROMI's case from stock.
Do a data wipe in recovery, make sure you have a titanium backup or equivalent if you want to restore apps.

Success!!!
It worked perfectly fine after i install the back up i did before i flashed my 1st costume rom,
I rooted made a back up at stock/rooted... It just would not install from a full wipe,
it install fine once i flashed that specific backup and dirty flashed then wiped dalvik and cache before booting.

Trying to get back to CM 10.0 from 10.1

I know the CM 10.1 nightly was experimental.
I flashed it, and it worked decently well enough.
What I failed to realize was that 10.1 flashes a new kernel on the phone, one that is incompatible with CM 10.0. I'm guessing the 4.2 base requires a new kernel.
So Fine, I've tried flashing the stock kernel on my phone, and then installing CM10, but no fish.
Any attempts I've made to change my kernel and then install CM 10 have resulted in my phone being stuck on the CM boot screen (the cyan circle animation)
Flashing CM10.1 nightly from twrp lets my phone boot up, because (i suppose) that rom installation just installs the compatible kernel again.
Can someone please help me figure out what I'm doing wrong with my kernel flashing?

taurius1 said:
I know the CM 10.1 nightly was experimental.
I flashed it, and it worked decently well enough.
What I failed to realize was that 10.1 flashes a new kernel on the phone, one that is incompatible with CM 10.0. I'm guessing the 4.2 base requires a new kernel.
So Fine, I've tried flashing the stock kernel on my phone, and then installing CM10, but no fish.
Any attempts I've made to change my kernel and then install CM 10 have resulted in my phone being stuck on the CM boot screen (the cyan circle animation)
Flashing CM10.1 nightly from twrp ets my phone boot up, because (i suppose) that rom installation just installs the compatible kernel again.
Can someone please help me figure out what I'm doing wrong with my kernel flashing?
Click to expand...
Click to collapse
What hboot r u on? You're full wiping right? And if you're on hboot 1.14 grab the boot.img our of the Rom zip you desire to flash and Fastboot flash it

a box of kittens said:
What hboot r u on? You're full wiping right? And if you're on hboot 1.14 grab the boot.img our of the Rom zip you desire to flash and Fastboot flash it
Click to expand...
Click to collapse
I'm on the 1.09 hboot. I haven't messed with my hboot ever. Should I be upgrading? I'll have to look it up.
I did try what you suggested.
I extracted the boot.img from CM10 stable for evita, flashed it via fastboot.
Then i rebooted into recovery, wiped my system, my cache, my dalvik cache, and did a factory reset.
Then I flashed CM 10.
After all this, still stuck on the cm boot animation. :3 I give it about 10 minutes before I decide its stuck. That is enough time, I think.

taurius1 said:
I'm on the 1.09 hboot. I haven't messed with my hboot ever. Should I be upgrading? I'll have to look it up.
I did try what you suggested.
I extracted the boot.img from CM10 stable for evita, flashed it via fastboot.
Then i rebooted into recovery, wiped my system, my cache, my dalvik cache, and did a factory reset.
Then I flashed CM 10.
After all this, still stuck on the cm boot animation. :3 I give it about 10 minutes before I decide its stuck. That is enough time, I think.
Click to expand...
Click to collapse
Ok no you want to stay on hboot 1.09 and redownload the latest cm10..and do these exact instructions
Wipe factory reset
System
Caches
Install Rom
Install gapps
I'm thinking you just had a bad download

a box of kittens said:
Ok no you want to stay on hboot 1.09 and redownload the latest cm10..and do these exact instructions
Wipe factory reset
System
Caches
Install Rom
Install gapps
I'm thinking you just had a bad download
Click to expand...
Click to collapse
I've done that. But just to be sure, I'm gonna try a fresh download once more. ^_^ Brb 10 minutes.

Curious what happened, as I think I may be having this same issue.

a box of kittens said:
Ok no you want to stay on hboot 1.09 and redownload the latest cm10..and do these exact instructions
Wipe factory reset
System
Caches
Install Rom
Install gapps
I'm thinking you just had a bad download
Click to expand...
Click to collapse
OOh that worked. Thanks a ton! ^_^
Probably was a bad download all three times I tried to download it before. :/ (I should probably buy a lottery ticket now :/ )
Now, Let me try installing my rooted stock rom. :3

Almost Same Problem
I have HTC One XL
-rooted
-unlocked
-bootloader unlocked
-hboot 1.14
-twrp recovery
I was also running the 10.1 expiremental (the first one). It was very buggy, so I tried out the newer experimental to see if the problems were fixed. The newer one was worse, so I decided to switch back to 10.0 nightly. I used fastboot to change the kernel to the one extracted from the 10.0 rom zip. I went to recovery and installed the 10.0 rom, but I DID NOT WIPE ANYTHING THE FIRST TIME. Either it slipped my mind, or I was thinking it wasn't necessary because I was still using a CM rom. The device would not boot, but instead of hanging on the cm animation screen, I'm stuck on the HTC logo screen. I went back to fastboot and did the kernel again and the phone automatically rebooted up correctly, however after a reboot i'm still stuck at the htc logo screen. It reminds me of tethered jailbreaks on iOS, lol. I may have to reflash the kernel every time I reboot. I tried stable, nightly, 10.1 nightly. no dice. any ideas?

lucasjohnsond said:
I have HTC One XL
-rooted
-unlocked
-bootloader unlocked
-hboot 1.14
-twrp recovery
I was also running the 10.1 expiremental (the first one). It was very buggy, so I tried out the newer experimental to see if the problems were fixed. The newer one was worse, so I decided to switch back to 10.0 nightly. I used fastboot to change the kernel to the one extracted from the 10.0 rom zip. I went to recovery and installed the 10.0 rom, but I DID NOT WIPE ANYTHING THE FIRST TIME. Either it slipped my mind, or I was thinking it wasn't necessary because I was still using a CM rom. The device would not boot, but instead of hanging on the cm animation screen, I'm stuck on the HTC logo screen. I went back to fastboot and did the kernel again and the phone automatically rebooted up correctly, however after a reboot i'm still stuck at the htc logo screen. It reminds me of tethered jailbreaks on iOS, lol. I may have to reflash the kernel every time I reboot. I tried stable, nightly, 10.1 nightly. no dice. any ideas?
Click to expand...
Click to collapse
Sounds like the best solution would be what I did, thanks to box of kittens.
Full wipe. (factory reset, system, cache)
Flash a download of CM to make sure you don't have a damaged copy.

taurius1 said:
Sounds like the best solution would be what I did, thanks to box of kittens.
Full wipe. (factory reset, system, cache)
Flash a download of CM to make sure you don't have a damaged copy.
Click to expand...
Click to collapse
Actually, I just remembered. If you're on the new hboot, you should be flashing the boot img through fastboot, and then installing the zip. Since you've been doing all that anyway, perhaps its time to just wipe everything and start over, step by step.
> download cm 10.0
> check md5 to make sure it's proper
> extract boot.img and flash it via fastboot
> reboot into recovery.
> wipe system, cache, dalvik cache, and factory reset
> transfer the rom and flash it via recovery
:/ I'm no expert here, but that's what I'd be doing now.

[Q][Solved] HTC One X AT&T - Boot looping once, defaulting to recovery boot

I just installed the VenomXL 3.2.6 on my HTC One X using TWRP 2.5.0.0. I am not 100% sure that I have S-Off, I rooted my phone right when the exploit for the "impossible" firmware was figured out a number of months ago. HBoot is showing 1.14.
I did factory wipe 3x before starting the installer. Then chose "wipe" in the installer. Everything installed quickly/correctly. After installing, I rebooted into fastboot and flashed the boot.img over with no issues.
Now when I try to boot, it'll boot loop at the initial white HTC-with-red-warning screen and then automatically boot into TWRP.
What can I do to make this ROM work?
Thanks

You can download twrp 2.3.3.1, check md5
flash twrp 2.3.3.1
fastboot erase cache
reboot to recovery, wipe cache, dalvik, system, factory reset.
flash rom, flash boot.img
Working.
Good Luck. By the way, if you were S-OFF, you would know.

exad said:
You can download twrp 2.3.3.1, check md5
flash twrp 2.3.3.1
fastboot erase cache
reboot to recovery, wipe cache, dalvik, system, factory reset.
flash rom, flash boot.img
Working.
Good Luck. By the way, if you were S-OFF, you would know.
Click to expand...
Click to collapse
Thank you for your advice! I've followed it as you listed and, unfortunately, my problem persists. After flashing fastboot flashing the boot.img at the end and restarting, it will hang at the white HTC-with-red-warning-text screen and then reboot into recovery.
Do you have any other suggestions?
I'm still searching that particular ROM thread looking for people with similar issues.
My next step is to try the next most popular ROM, whichever that is.

sappro said:
Thank you for your advice! I've followed it as you listed and, unfortunately, my problem persists. After flashing fastboot flashing the boot.img at the end and restarting, it will hang at the white HTC-with-red-warning-text screen and then reboot into recovery.
Do you have any other suggestions?
I'm still searching that particular ROM thread looking for people with similar issues.
My next step is to try the next most popular ROM, whichever that is.
Click to expand...
Click to collapse
the boot.img you are flashing is extracted from viperxl rom? viper xl should have the option to flash the boot.img for you so you don't even have to.
Otherwise i'd check MD5 of the Rom, either the file is bad or you're doing something wrong.

exad said:
the boot.img you are flashing is extracted from viperxl rom? viper xl should have the option to flash the boot.img for you so you don't even have to.
Otherwise i'd check MD5 of the Rom, either the file is bad or you're doing something wrong.
Click to expand...
Click to collapse
The MD5 on my flash drive of the downloaded ROM is incorrect, even though it was correct before moving to my flash drive. I will redownload and see if that solves the issue.
Thank you!

exad said:
the boot.img you are flashing is extracted from viperxl rom? viper xl should have the option to flash the boot.img for you so you don't even have to.
Otherwise i'd check MD5 of the Rom, either the file is bad or you're doing something wrong.
Click to expand...
Click to collapse
Wow, I've never had an MD5 problem before, but that appeared to have fixed it. Thanks very much for the suggestion!
SOLVED: The ZIP files were somehow subtly corrupted during transfer from computer to flash drive to phone. After checking the MD5 using http://forum.xda-developers.com/showthread.php?t=1939007 I was verify this. Using a different computer/browser, I downloaded the ROMs again and now the MD5 hashes correctly!

Cool glad you are up and going. Personally I like to download roms to phone then install with twrp . Also you probably know this but a nandriod backup is a must .
Sent from my HTC One X using xda premium

Upgrade from Prime! 2.1.1 to a 4.2/4.3 custom ROM

Is there any way to do this without having to do a factory wipe?

It may be possible, however it is HIGHLY recommended to do a factory reset in recovery. If you choose not to, I do not even want to think about what will crash going from Honeycomb to JellyBean 4.2/4.3
Here is what I would do. First, install GooManager from the play store. Update the recovery to TWRP 2.3.2.3. I have seen a LOT of users with issues using CWM on android 4.2 and later. Some swear it works great, but I would not trust it myself. After installing the GooManager, tap the menu button in the top right and choose the Install OpenRecovery Script.
Next, use Titanium Backup to back up your user apps. Do not back up system apps. Restoring these can cause some issues on newer versions of Android, especially since there are no Jelly Bean ROMs based on stock Asus Firmware.
Download your ROM of choice, and any GAPPS or kernels that you want to install.
Boot to recovery.
Backup your current setup as a fail safe.
Next, wipe the following partitions:
Cache
Davlik Cache
System
Data (Factory Reset). This will wipe the /data/ partition without wiping /data/media/ (aka /sdcard/) so your files on the internal storage will still remain. I would HIGHLY recommend doing a FORMAT DATA and fully wiping the /sdcard/ to help your device run faster. The files on /sdcard/ are not backed up by recovery's backup function so if you choose to do this be sure you backed up your entire /sdcard/ to microSD/SD/USB/PC/Cloud storage before formatting it.
Now go to the Install menu and install the ROM. Also install GAPPS and kernel if required.
I always wipe cache & davlik again after flashing then reboot. Set up the new ROM and then install TiBu and restore your apps. Once again, be sure not to restore any system apps or data as it can cause random reboots, SOD and app crashes.

Thanks for such a quick and detailed reply. I do have TB so that is not the problem. My problem is I do not want to lose my custom HUB that I created and am not sure how to back that up. Also I have been fairly happy with this HC rom other than a few browser crashes and the occasional overnight battery drain. Is JB that much better than HC?

thorin33 said:
Thanks for such a quick and detailed reply. I do have TB so that is not the problem. My problem is I do not want to lose my custom HUB that I created and am not sure how to back that up. Also I have been fairly happy with this HC rom other than a few browser crashes and the occasional overnight battery drain. Is JB that much better than HC?
Click to expand...
Click to collapse
It will be night and day.
As far as your HUBS, are you using a custom launcher? If so it should be backed up with the launcher settings. If not, you will have to set it up again....which I know how much time that takes.

frederuco said:
It will be night and day.
As far as your HUBS, are you using a custom launcher? If so it should be backed up with the launcher settings. If not, you will have to set it up again....which I know how much time that takes.
Click to expand...
Click to collapse
Plus 1. I hesitated to upgrade because I was "comfortable" with the ROM I was on (Megatron). I decided to update to KatKiss 4.3 mostly cause I was bored and wanted to flash something. Glad I did as it's a big different.:good:

Thanks again. I am using ADW and saved my configuration. I may just have to bite the bullet and just do it.

That is where I am at. I am very comfortable with this ROM and quite happy with it. Just wondering if the grass is greener.

thorin33 said:
That is where I am at. I am very comfortable with this ROM and quite happy with it. Just wondering if the grass is greener.
Click to expand...
Click to collapse
MUCH greener - Honeycomb is an ancient slow laggy build of Android, Jellybean is a fast smooth build
The user experience using Jellybean is immensely improved
Its the difference between Vista and 8.1, if not more, maybe XP > 8.1
Just make a Nandroid backup with TWRP recovery, then wipe everything, flash KatKiss #226 and Gapps and play around with it
Guarantee you will not want to return to HC
On the off chance you do want to return, just boot back into TWRP and restore your backup, you'll be back to exactly the state you were in when you made the backup, nothing lost

frederuco said:
It will be night and day.
As far as your HUBS, are you using a custom launcher? If so it should be backed up with the launcher settings. If not, you will have to set it up again....which I know how much time that takes.
Click to expand...
Click to collapse
Does anyone happen to know if my HUBS using ADW will look and act the same in JB?

thorin33 said:
Does anyone happen to know if my HUBS using ADW will look and act the same in JB?
Click to expand...
Click to collapse
I don't know anyone using HUBS myself. I am not sure how ADB works with JB. I moved on to APEX myself.
I think the BEST option is to make a backup of PRIME. Install, restore your apps (I would restore ADW last after all widgets and such are restored) and test it out.
If it does not work like you wanted, restore the PRIME backup in recovery and you will be right where you left off.

Well I figured I would give it a go. I installed Goo Manager and tried to install OpenRecovery. I just get the notifiation that it is downloading then a force close of Goo Manager. Not sure what to do now. I have tried to re-install Goo Manager but still get the same thing. I have rebooted, cleared Dalvik.

thorin33 said:
Well I figured I would give it a go. I installed Goo Manager and tried to install OpenRecovery. I just get the notifiation that it is downloading then a force close of Goo Manager. Not sure what to do now. I have tried to re-install Goo Manager but still get the same thing. I have rebooted, cleared Dalvik.
Click to expand...
Click to collapse
Use Easyflasher to flash TWRP, then Goo Manager to update it
http://forum.xda-developers.com/showthread.php?t=1688012
Or if Frederuco would be kind enough to link to his updated version, you can flash the newest TWRP in one shot

thorin33 said:
Well I figured I would give it a go. I installed Goo Manager and tried to install OpenRecovery. I just get the notifiation that it is downloading then a force close of Goo Manager. Not sure what to do now. I have tried to re-install Goo Manager but still get the same thing. I have rebooted, cleared Dalvik.
Click to expand...
Click to collapse
*Detection* said:
Use Easyflasher to flash TWRP, then Goo Manager to update it
http://forum.xda-developers.com/showthread.php?t=1688012
Or if Frederuco would be kind enough to link to his updated version, you can flash the newest TWRP in one shot
Click to expand...
Click to collapse
I was thinking the same thing.
See here:
frederuco said:
Since this tool has not been updated for newer recoveries, I repacked the zip with the two latest versions of TWRP:
EasyFlasher with TWRP 2.3.2.3
EasyFlasher with TWRP 2.5.0.0
EasyFlasher with TWRP 2.6.0.0
EasyFlasher with TWRP 2.6.1.0
EasyFlasher with TWRP 2.6.1.0-b This version has the microSD mounted as /MicroSD/ instead of /sdc/
EasyFlasher with TWRP 2.6.1.0-c This version has the the storage mounted as sdcard0 for internal storage and microSD is mounted as sdcard1
EasyFlasher with TWRP 2.6.3.0 Fixes the SuperSU nag during reboot.
NOTE - It STILL has the TWRP version listed as 2.2.1.1 in the dropdown, but it WILL INSTALL 2.3.2.3, 2.5.0.0 or 2.6.X.X I cannot update the dropdown.
I have tested all of these on my TF101 and all of them worked successfully.
Click to expand...
Click to collapse
You can follow my rooting guide here for detailed instructions on how to use EasyFlasher: http://www.transformerforums.com/fo...nt/31927-frederucos-guide-root-rom-tf101.html

frederuco said:
EasyFlasher with TWRP 2.6.3.0 Fixes the SuperSU nag during reboot.
Click to expand...
Click to collapse
Frederuco - do I have to use the EasyFlasher version with ADB to flash the TWRP 2.6.3.0? Although I updated to TWRP 2.6.3.0-c today and then updated to KatKiss 4.3 v24 and the nag hasn't appeared again (yet)

Theziggy said:
Frederuco - do I have to use the EasyFlasher version with ADB to flash the TWRP 2.6.3.0? Although I updated to TWRP 2.6.3.0-c today and then updated to KatKiss 4.3 v24 and the nag hasn't appeared again (yet)
Click to expand...
Click to collapse
If you have a custom recovery installed, just flash the zip file in sidneyk's TWRP thread to update to a different version.
http://forum.xda-developers.com/showthread.php?t=2434422

frederuco said:
If you have a custom recovery installed, just flash the zip file in sidneyk's TWRP thread to update to a different version.
http://forum.xda-developers.com/showthread.php?t=2434422
Click to expand...
Click to collapse
Oh I know how to flash the zip file Frederuco (as my sig shows - I have recently updated to 2.6.3.0-3 using this method), I was wondering what the advantage of the EasyFlasher version was - or is that for people who are just starting to root their tf101?

Theziggy said:
Oh I know how to flash the zip file Frederuco (as my sig shows - I have recently updated to 2.6.3.0-3 using this method), I was wondering what the advantage of the EasyFlasher version was - or is that for people who are just starting to root their tf101?
Click to expand...
Click to collapse
EasyFlasher is mainly to install a custom recovery when you are still stock so you can root and/or ROM and also to flash the stock firmware if you bricked your tablet and it won't boot to recovery or to a ROM.
It can be used to update to a newer version of TWRP or other recovery, but it is much easier to just flash the zip file in recovery as you do not need to have a PC to make it happen.

That's what I was kinda thinking Frederuco, thanks for clarifying it for me :good: :good: :good:

Finally found some time to do a little bit more on my upgrade path (Having a 5 month old sucks up most of my free time). I was able to just install the zip from sidneyk. Did my nandroid and hopefully will find time to flash Katkiss.
Thanks for all the help so far everyone.

I noticed that when I went to do my backup I got the following message:
Updating partition details
E: Unable to locate ui.xml in zip file
E: An internal error has occured.
It proceeded to backup and said it was successful. Is this normal?
TIA