Thanks for the info!! Didn't know thatDalvik cache is rebuilt when android boots. That's why a boot after wiping it takes longer.
Sent from my EVO using Tapatalk 2
Thanks for the info!! Didn't know thatDalvik cache is rebuilt when android boots. That's why a boot after wiping it takes longer.
What exactly is that mysterious checkbox? I tried looking back a lot of pages, and haven't seen it explained, or I missed it somehow. Just curious, as it does seem to have an effect on if restores are successful or not. Thankseyeballer...Can we have the checkbox with no description in the Restore section, unchecked by default?
Sent from my EVO using Tapatalk 2
Shouldn't this say "You need to be HTC unlocked OR S-off" before flashing a custom recovery?TeamWin is proud to present TWRP 2.1.x for the EVO 4G LTE!
*YOU NEED TO BE HTC UNLOCKED TO FLASH A CUSTOM RECOVERY!!!!!!*
If you are ONLY HTC unlocked you will need to follow the fastboot method to install, if you are HTC unlocked AND rooted, you can use the goo manager method.
Updates:
v2.1.8: usb mount + sdcard path fixes: http://forum.xda-developers.com/showthread.php?p=26856447#post26856447 (download mirror: http://techerrata.com/file/twrp2/openrecovery-twrp-2.1.8-jewel.img )
v2.1.7: adb working
v2.1.6: Fix corruption issue with /misc partition
Do you not see the big red print?Shouldn't this say "You need to be HTC unlocked OR S-off" before flashing a custom recovery?
The op was created long before s-off was achievable.Shouldn't this say "You need to be HTC unlocked OR S-off" before flashing a custom recovery?
Plus the big red print that says you need to be unlocked to flash a custom recovery. LOLThe op was created long before s-off was achievable.
Could someone please elaborate the above issue? How exactly does this usually manifest? I'm trying to get an AROMA-based ROM to install, but the installer keeps hard freezing, requiring an adb reboot to clear.Zip files that install more data than free space is available will crash or hang recovery (AOSP issue)
Sounds like a bad dl.Could someone please elaborate the above issue? How exactly does this usually manifest? I'm trying to get an AROMA-based ROM to install, but the installer keeps hard freezing, requiring an adb reboot to clear.
Fredgar, you fredgared again. Lol.Sounds like a bad dl.
Sent from my Transformer Prime TF201 using Tapatalk 2
That's not how I read it. Seems like he got a bad dl and when he installs it it freezes. He's talking about the aroma installer no?Fredgar, you fredgared again. Lol.
Grayn0de was trying to flash his rom, using aroma and recovery froze.
Sent from my lair.
The issue is how the recovery interacts with the AROMA installer. I noticed this same behavior on my OG EVO when using TWRP. I don't think it's a matter of a bad download; it's more of coding between AROMA and TWRP.That's not how I read it. Seems like he got a bad dl and when he installs it it freezes. He's talking about the aroma installer no?
Sent from my EVO using Tapatalk 2
Gotcha. I kind of figured as much, though I never used twrp on the OG Evo. Guess I'll just have to put this ROM project on hold until either CWM is ready for primetime or TWRP & AROMA can play nice.The issue is how the recovery interacts with the AROMA installer. I noticed this same behavior on my OG EVO when using TWRP. I don't think it's a matter of a bad download; it's more of coding between AROMA and TWRP.
I don't have an issue with aroma and twrp. I use them both on my prime and my 4g LTE. Which is why I said a bad dl. But captain throwback would know a lot more than I. Thanks captain.Gotcha. I kind of figured as much, though I never used twrp on the OG Evo. Guess I'll just have to put this ROM project on hold until either CWM is ready for primetime or TWRP & AROMA can play nice.
Sent from my EVO using xda premium
That's interesting. I didn't realize there were any LTE ROMs that used the AROMA installer. I guess I'll have to look through the threads and test it myself. If anything, it seems to work inconsistently. Can you try it again and confirm it works?I don't have an issue with aroma and twrp. I use them both on my prime and my 4g LTE. Which is why I said a bad dl. But captain throwback would know a lot more than I. Thanks captain.
Sent from my EVO using Tapatalk 2
Well I forgot which Rom it was and now I can't find one with it. I know there is one but I'm on some painkillers cause I wrecked my motorcycle yesterday and can't remember which one it was. I'll keep looking.That's interesting. I didn't realize there were any LTE ROMs that used the AROMA installer. I guess I'll have to look through the threads and test it myself. If anything, it seems to work inconsistently. Can you try it again and confirm it works?
If it were not my ROM that I was attempting to flash, I'd think the same, but I'm copying it via USB. I actually did a round of rezip/resign and verified my checksums. I'm wondering if it may have something to do with the amount of code being loaded into the memory buffers, as I was able to successfully flash a very small (few options) AROMA-based test ROM. My current ROM has over 1200 lines of code between the aroma-config and updater-script, though. LOL.I don't have an issue with aroma and twrp. I use them both on my prime and my 4g LTE. Which is why I said a bad dl. But captain throwback would know a lot more than I. Thanks captain.
Sent from my EVO using Tapatalk 2
That's interesting. I didn't realize there were any LTE ROMs that used the AROMA installer. I guess I'll have to look through the threads and test it myself. If anything, it seems to work inconsistently. Can you try it again and confirm it works?
As far as I'm aware, ViperROM is not yet using AROMA, but I've not really been following the progress of any other devs too well, being lost in my own code.Seen this http://forum.xda-developers.com/showthread.php?p=28521956
~Freshly acquired LTEvo; ViperRom'ed in under 2hrs...
They're not using Aroma in their current ROM, that's correct.If it were not my ROM that I was attempting to flash, I'd think the same, but I'm copying it via USB. I actually did a round of rezip/resign and verified my checksums. I'm wondering if it may have something to do with the amount of code being loaded into the memory buffers, as I was able to successfully flash a very small (few options) AROMA-based test ROM. My current ROM has over 1200 lines of code between the aroma-config and updater-script, though. LOL.
As far as I'm aware, ViperROM is not yet using AROMA, but I've not really been following the progress of any other devs too well, being lost in my own code.
Post was about him tryin to get aroma working bro....If it were not my ROM that I was attempting to flash, I'd think the same, but I'm copying it via USB. I actually did a round of rezip/resign and verified my checksums. I'm wondering if it may have something to do with the amount of code being loaded into the memory buffers, as I was able to successfully flash a very small (few options) AROMA-based test ROM. My current ROM has over 1200 lines of code between the aroma-config and updater-script, though. LOL.
As far as I'm aware, ViperROM is not yet using AROMA, but I've not really been following the progress of any other devs too well, being lost in my own code.