Related
okay guys, I tried to figure this out without bothering yall, but my newb knowledge is limited and I'm confused as hell. I was planning on rooting my phone today after reading about all the information I've been collecting from you guys, but now that I have updated my phone, will Toast's method using those files still allow me to root? Or do I need new files in order to root my phone? I see some files on developer page on new root but I'm confused if those are for phones already rooted or not...ahhhh
so I guess I'm asking is..if you have stock phone with new update applied, how do I go about rooting my evo?
We don't know yet. You should not have updated.
Quick and straight to the point, thanks for your reply. I guess I'm a motherfreakin idiot with the worst timing in the world for things like this. FML
TheBiles said:
We don't know yet. You should not have updated.
Click to expand...
Click to collapse
quick question; if i root with Toast's method, then install the rooted updated rom that's in the dev section (by Calkulin), that should be fine, right?
jblazea50 said:
quick question; if i root with Toast's method, then install the rooted updated rom that's in the dev section (by Calkulin), that should be fine, right?
Click to expand...
Click to collapse
yes
-----------------------
So in order to fully root and nand unlock stock evo with new update, all I have to do is follow Toast's step 1&2 then apply the new rooted update on developer site? just wanna get things crystal clear so I don't risk bricking my evo..
I don't know or think it has been confirmed to work with the new update yet.
Toast step 1 will root the phone
Toast step 2 will unlock nand
Installing the new rooted update will flash the stock sprint rom without breaking your root.
mizerab1e said:
So in order to fully root and nand unlock stock evo with new update, all I have to do is follow Toast's step 1&2 then apply the new rooted update on developer site? just wanna get things crystal clear so I don't risk bricking my evo..
Click to expand...
Click to collapse
No. We don't even know if you can use Toast's method to root it. You can be the guinea pig and post results, though!
initial said:
yup.
Toast step 1 will root the phone
Toast step 2 will unlock nand
Installing the new rooted update will flash the stock sprint rom without breaking your root.
Click to expand...
Click to collapse
There is some info going around in dev forum saying Toast's method will not work if you have the new OTA update applied on stock EVO saying you will get error messages and stuff although it will not brick your phone which is adding to more confusion..
has anyone successfully rooted their stock evo with new OTA update applied? or do I need to wait until devs come up with new files needed to root the evo?
mizerab1e said:
There is some info going around in dev forum saying Toast's method will not work if you have the new OTA update applied on stock EVO saying you will get error messages and stuff although it will not brick your phone which is adding to more confusion..
has anyone successfully rooted their stock evo with new OTA update applied? or do I need to wait until devs come up with new files needed to root the evo?
Click to expand...
Click to collapse
All you have to do is place a file in the root of your SD card and reboot the phone. Try it out and post your results!
mizerab1e said:
Quick and straight to the point, thanks for your reply. I guess I'm a motherfreakin idiot with the worst timing in the world for things like this. FML
Click to expand...
Click to collapse
You and me both my friend, you and me both. Sat there as the update came up and thought, I bet this is going to prevent me from rooting today ...
Yeah, ALL root is broken if you install the OTA.
Okay so I've been digging around and asking questions in dev forum, seems like there is no way for Stock EVO with OTA update to root their EVO yet. What bothers me is that I haven't seen a single post from a dev announcing that they are working on new root methods for Stock EVO with new OTA update.. they seem to be more concerned about fixing the issue around previously rooted EVOs, and I'm afraid we are getting left out... I hope this isn't the case, and hopefully one of our brilliant devs will give the new stock evo with OTA update owners some attention to this matter.
mizerab1e said:
Okay so I've been digging around and asking questions in dev forum, seems like there is no way for Stock EVO with OTA update to root their EVO yet. What bothers me is that I haven't seen a single post from a dev announcing that they are working on new root methods for Stock EVO with new OTA update.. they seem to be more concerned about fixing the issue around previously rooted EVOs, and I'm afraid we are getting left out... I hope this isn't the case, and hopefully one of our brilliant devs will give the new stock evo with OTA update owners some attention to this matter.
Click to expand...
Click to collapse
They're busy working on the kernel. Everybody was warned not to accept the OTA and those of us that chose to do it have to lie in our beds until the developers get around to it.
EtherealRemnant said:
They're busy working on the kernel. Everybody was warned not to accept the OTA and those of us that chose to do it have to lie in our beds until the developers get around to it.
Click to expand...
Click to collapse
Seems like that is the case, someone from dev forum suggested that downgrading the OTA to previous one then rooting might wield some fruit, If I can figure out how to do that I'll be more than happy to be a guinea pig for you guys.
TheBiles said:
All you have to do is place a file in the root of your SD card and reboot the phone. Try it out and post your results!
Click to expand...
Click to collapse
I'm not quite sure which file you're talking about, could you elaborate some more?
mizerab1e said:
Okay so I've been digging around and asking questions in dev forum, seems like there is no way for Stock EVO with OTA update to root their EVO yet. What bothers me is that I haven't seen a single post from a dev announcing that they are working on new root methods for Stock EVO with new OTA update.. they seem to be more concerned about fixing the issue around previously rooted EVOs, and I'm afraid we are getting left out... I hope this isn't the case, and hopefully one of our brilliant devs will give the new stock evo with OTA update owners some attention to this matter.
Click to expand...
Click to collapse
They busted their asses to get root the first time, and, as of right now, every EVO that you buy is capable of being rooted. Only people who update without heeding the warnings are affected, so it is kind of hard to convince a dev to throw down all of their current work to go back and try to solve this AGAIN. It should be a general rule of thumb that you NEVER install manufacturer's updates on any piece of electronics that you are interested in hacking/modifying/changing in any way. 99% of the time they provide some kind of security fixes that are not announced.
mizerab1e said:
Seems like that is the case, someone from dev forum suggested that downgrading the OTA to previous one then rooting might wield some fruit, If I can figure out how to do that I'll be more than happy to be a guinea pig for you guys.
Click to expand...
Click to collapse
It doesn't work. I've already tried it. The bootloader is locked.
TheBiles said:
They busted their asses to get root the first time, and, as of right now, every EVO that you buy is capable of being rooted. Only people who update without heeding the warnings are affected, so it is kind of hard to convince a dev to throw down all of their current work to go back and try to solve this AGAIN. It should be a general rule of thumb that you NEVER install manufacturer's updates on any piece of electronics that you are interested in hacking/modifying/changing in any way. 99% of the time they provide some kind of security fixes that are not announced.
Click to expand...
Click to collapse
I have no doubt in my mind the devs are doing everything they can to provide us with their brilliant work, I have no one but myself to blame for updating the OTA without heeding their warnings. I'm sure once the devs iron out all the issues with previously rooted system, they will get around to us as they always have. I just wish there was any way I can contribute to putting some light onto this matter for those who made the mistake of updating their OTA..
Yeah, was kicking myself as I knew it was a mistake.
Am willing to try out some ish too, that is if an extra Guinea is needed.
Figured I'd start a thread for all of us suckers that went with Unrevoked and want to back down or switch methods.
Has anyone that did the Unrevoked 2 / ClockWorkMod method of root successfully backed down to stock and / or converted to Toast?
What method did you use.
Thanks
Smac61 said:
Figured I'd start a thread for all of us suckers that went with Unrevoked and want to back down or switch methods.
Has anyone that did the Unrevoked 2 / ClockWorkMod method of root successfully backed down to stock and / or converted to Toast?
What method did you use.
Thanks
Click to expand...
Click to collapse
*raises hand*
4G still hosed. I was on Unrevoked v1 which hosed my 4G.
Did the dummy's guide to rooting found on this forum.
Still no 4G, but my MAC is now correct.
If you still have partial root try this
http://forum.xda-developers.com/showthread.php?t=715915
Might not fit your situation but might help somebody out
just use Toasts ruu to get back to stock then reroot using his guide.
p.s. whats wrong with unrevoked2, does 4g not work with it or something?
Im in a no 4g zone so.................
ifly4vamerica said:
If you still have partial root try this
http://forum.xda-developers.com/showthread.php?t=715915
Might not fit your situation but might help somebody out
Click to expand...
Click to collapse
Just did that. No go.
I have tried a lot of things to restore my 4g. I reset my MAC to original using:
http://forum.xda-developers.com/showthread.php?t=715525
I have converted to Damage Control: Still no working 4g.
I have tried basically everything I can think of including going back to stock.
At this point I think I am going to flash the original hardware and do the OTA update....then take it in and show that my 4g isn't working.
This has been bugging me for a while, and this seems like the right thread to ask this question in. If a lot of roms require Toast's root method, and Unrevoked has given issues, is there a reason that people are still using Unrevoked's root method over Toast's? Not to hate on the Unrevoked guys, but this has been bugging me.
i have tried everything, i dont know what to do!!
jonathaflores said:
i have tried everything, i dont know what to do!!
Click to expand...
Click to collapse
What EXACTLY are you trying to do?
restore 4G after using the Unrevoked 1 to update to the new firmware, but it just busted my 4g i have gonne back to stock, i am bout to take it to sprint and act dumb!!
jonathaflores said:
restore 4G after using the Unrevoked 1 to update to the new firmware, but it just busted my 4g i have gonne back to stock, i am bout to take it to sprint and act dumb!!
Click to expand...
Click to collapse
This may be the only option. I have the same issue.
As far as using unrevoked over toast, it was just the first one I used to get root when I got the phone. I went with it because it was easy. I have since used toast to install other items in an attempt to restore 4g. I will use toast in the future now that I am familiar with it.
okay, so i used unrevoked.apk to root then used unrevoked2 to flash recovery. are you saying that 4g is now completely gone from my phone?
yep sir, Unrevoked its busting 4g!!
I was using unrevoked.apk at first, as I didn't want to wipe my EVO. I had to wipe it anyway to move from the I/O account to my personal one, so I though "might as well root now." I like having ENG SPLs, and unrevoked2 wasn't out yet, so it wasn't a difficult decision.
I was terribly disappointed in every custom ROM I tried. They would run hot, the battery sucked, and they'd randomly reboot when I wasn't even touching them. I finally had enough and went back to a stock system.img with unrevoked.apk installed, and everything worked fine. I only use root to have full access in adb anyway - I don't really mess with task killers or the like. I'm not interested in a custom ROM until FroYo AOSP.
I applied the unrevoked version of the latest OTA patch last night. Let's see how that goes…
im confused. why is this just now being brought up. unrevoked has been around for awhile. I haven't heard anyone complain until now. Is it something Unrevoked has done recently, or are we just now realizing the issue?
It is a known issue. Unrevoked released a response to the OTA for users to update without breaking root. The initial release broke 4g for almost everyone who applied it (maybe everyone). They pulled the release and a day later put up a new one that works (as far as i know). Those who used the first release still have no 4g. To the best of my knowledge, no one has been able to fix the 4g issues caused by the initial unrevoked2
Edit:
Read the second bullet under FAQs: http://unrevoked.com/rootwiki/doku.php/public/evo_ota_2_patch
Why the f*** is there ANOTHER thread on this...
There's already 3 threads relating to this, one of which I made that goes into detail and another which talks about changing MAC and it still doesn't work.
There is no solution, stop making new threads hoping to find one.
If you want a solution, wait for unrevoked to announce one.
bandagraph said:
It is a known issue. Unrevoked released a response to the OTA for users to update without breaking root. The initial release broke 4g for almost everyone who applied it (maybe everyone). They pulled the release and a day later put up a new one that works (as far as i know). Those who used the first release still have no 4g. To the best of my knowledge, no one has been able to fix the 4g issues caused by the initial unrevoked2
Edit:
Read the second bullet under FAQs: http://unrevoked.com/rootwiki/doku.php/public/evo_ota_2_patch
Click to expand...
Click to collapse
ok, so this just pertains to the OTA?
cause I haven't dont the OTA.
it doesnt matter, we jut got screw, taking my phone to sprint on monday, two days to find a solution, or i am taking my phone back to sprint!!
jonathaflores said:
it doesnt matter, we jut got screw, taking my phone to sprint on monday, two days to find a solution, or i am taking my phone back to sprint!!
Click to expand...
Click to collapse
LMAO - you really think the people at your "local sprint" store are smarter than these guys at XDA?
-= User Error =-
psneuter & rageagainstthecage only work for Froyo and below.
gingerbreak only works for 2.3.2 and below.
Sprint update EF17 is 2.3.4
That means none of those exploits will work. That means you can't just boot up SuperOneClick and expect it to root the new ROM.
With that in mind, could everyone please stop posting about their failed one-click rooting attempts.
I know, it's well intentioned, but it's not helping.
Now, there is no known exploit readily available, so there are two options:
1) Compile & flash a ROM already patched with root/superuser.apk
2) Build an update.zip file that that does the patching and run it from recovery.
Both of these have been done plenty of times in the past on other phones, and there is nothing to stop them from working. Expect to see one or the other from someone who knows how (not me) in the near future.
Till then, don't even bother with the one-clicks.
Good Post! I, myself, read all the information regarding the upgrade, and realized from the awesome Devs that root would not work until they get a chance to have it in hand, and see if there is an available exploit.
If people would just relax a little, and give some of these Guys/Gals a chance to take a look at the code, and see what they can do, it would make the forums a wee bit happier..
that's right, i personally went through all the existing methods but no luck
this makes me wanna go into android system dev. now im staying on android app dev but it seems that it is not enough. hopefully i can have more time to learn system tweaking after i finish my current project.
until then, it's all on you guys good luck. for all the devs out there, thank you for your great works, saving us from this unrooted system BS
to hopefully decrease the number of posts from members in the coming days about the new OTA that Sprint/HTC released today (but will not officially "push" to devices until January 24,) I would like to point out some things to new members as well as veterans, as we see this happen every time a new OTA is pushed.
latests news/updates in bold.
flashing lights reminder: IF YOU ARE ROOTED, DO NOT UNROOT TO GET THIS OTA UPDATE FROM SPRINT. YOU WILL LOSE THE ABILITY TO RE ROOT AS REVOLUTIONARY DOES NOT WORK YET WITH THE NEW HBOOT 2.18
1. Number one rule, and i will cap this DO NOT ACCEPT A OTA UPDATE IF YOU ARE ROOTED. it has been said many many times here, and members with rooted phones do it anyways. why risk it???? we all saw the gingerbread debacle last year.
2. New HBoot. it seems the new ota update has a new h-boot, 2.18, and from what it seems and this may remain to be seen 100% it is not unlockable with revolutionary. i can not confirm this personally. EDIT: seems the new 2.18 hboot is preparing the evo4g to be added to the unlock bootloader list at htcdev. we await word on when this might be official from htc. UPDATE: seems Captain_Throwback has a way to get your hboot down to 2.10 to use unrevoked. the process is long but it does work, as I have tested it myself.
http://themikmik.com/showthread.php...18-HBOOT-with-HTCDev-com-No-More-Watermark!-"
4. Why the update? The big part of this update was to remove CIQ from the evo's. yay. There were small improvements to Peep (the htc twitter client) and other various fixes. report of battery life being worse than 4.54 have been reported.
5. So when will my favorite rom be updated to the OTA base? well, we already have a stock rom based on the ota (actually 2!) , it is located here:
http://forum.xda-developers.com/showthread.php?t=1455340
so this is a start. your favorite rom will be updated by it's developer when the dev has time, last update we had (4.54) we saw a rapid update of roms.
6. Great, so has sense changed at all? No we are still at sense 1.0 sigh.
7. so how about the new kernel? it is now based on htc 2.6.35.10 dated december 21, 20011. Captain_Throwback has extracted the kernel standalone: http://forum.xda-developers.com/showpost.php?p=21654186&postcount=3214
7a. What "hacks" work with the the new stock rom you posted? look here: http://forum.xda-developers.com/showthread.php?t=1459982
8. i have a question!! well use the search function and see if it has been answered, look here, the Q&A threads, or the dev threads. I hope this will clear down some of the clutter that comes up during this wonderful thing called an OTA update.
I'm far from a sense person, and more seasoned veteran, but good post, and has some good info that people should read. I'd like to believe it'd cut down on threads, but you can't say you didn't try.
teh roxxorz said:
I'm far from a sense person, and more seasoned veteran, but good post, and has some good info that people should read. I'd like to believe it'd cut down on threads, but you can't say you didn't try. :_
Click to expand...
Click to collapse
i just want the new members to realize 2/3 their questions can be answered by reading for ten minutes, and may save them major headaches, but your right. we shall get some doozies. lol
brad560 said:
i just want the new members to realize 2/3 their questions can be answered by reading for ten minutes, and may save them major headaches, but your right. we shall get some doozies. lol
Click to expand...
Click to collapse
They need to set up like a new user pen where they can only post there for the like 2 days and learn those things. Also, glad you're rom is doing well, know you had a semi uphill battle at the start.
Also, I can't WAIT to see all the 'I just updated, and now I wana root" threads.
interesting
Sent from my ICS Evo4g using XDA App
Awesome post bro.. thank you.
^ great info, thanks brad, no doubt this will help some!
Sent from my PC36100 using XDA App
Thanks Brad I flashed your rom. I'm waiting along with everyone else for the new Radios. I cant wait.
teh roxxorz said:
They need to set up like a new user pen where they can only post there for the like 2 days and learn those things. Also, glad you're rom is doing well, know you had a semi uphill battle at the start.
Also, I can't WAIT to see all the 'I just updated, and now I wana root" threads.
Click to expand...
Click to collapse
OMG! I just had nightmare flashbacks of "Root the *****!"
Thanks Brad for the update,its good to know whats going on with our EVO.Looks like sprint has a hardon for stopping developement,but as smart as you guys are,you'll get the HBoot unlocked before long.
HipKat said:
OMG! I just had nightmare flashbacks of "Root the *****!"
Click to expand...
Click to collapse
That was a nightmare that needs to just stay a memory. D:
will try to update this with relevant info as it comes along.
Great thread and maybe some of the noobs will read it before thinking the ota update is the next greatest thing.
It will be once the devs get ahold of it and move along updating their great roms.
Thank Brad for the new info,
Long live the Evo 4g.
Seems your rom file host is struggling this morning. I can not dl either version of your ROM, Brad.
Has it been confirmed that it cannot get S-Off with Revolutionary and SuperTool?
Oh how I hope it can be unlocked... If it cannot, then a deluge of root threads will open and I might be driven to insanity.
Sent from my PC36100 using xda premium
tropicalbrit said:
Has it been confirmed that it cannot be rooted with Revolutionary and SuperTool?
Oh how I hope it can be rooted... If it cannot be rooted, then a deluge of threads will open and I might be driven to insanity.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
Cannot since revolutionary doesn't support the hboot with the new ota
Sent from my PC36100 using XDA App
I feel I must chime in here and make some further clarifications.
Tools like unrevoked and Revolutionary do NOT give you root. This is a very common misconception. What these tools DO give you is NAND access (S-OFF).
In order to obtain root, a custom recovery is required to flash a rooted ROM. In order to flash a custom recovery, you must have NAND access (S-OFF).
If your phone has S-OFF, you can run rooted and non-rooted ROMS just the same. It all depends on what ROM you flash. What gives a ROM root access is having superuser permissions. This is achieved with ChainDD's Superuser app which grants a ROM with SU permissions. If a ROM has the Superuser app cooked in, it has root access.
So it goes a little something like this:
unrevoked/revolutionary --> S-OFF
S-OFF --> allows flashing custom recovery
custom recovery --> allows flashing custom ROMs
custom ROMs with SU permissions cooked in --> gives you root
S-OFF and Root are only indirectly related.
If you have S-OFF, you will ALWAYS have the ability to flash ROMs, even the latest newest releases.
Here's a further example, my own personal experience:
I obtained S-OFF over a year ago using unrevoked3, which permanently granted S-OFF. Since then I have applied every radio, hboot, etc as they have been released. Never lost S-OFF.
Now regarding this latest OTA release, #12 (4.67.651.3), here is what I did. I flashed a stock unrooted/unmodified 4.54 rom. I then went into settings->system updates and checked for the new ota. I downloaded the OTA, and APPLIED the OTA. Applying the update flashed the new hboot, the stock recovery, and the new radios, as well as the new stock 4.67.651.3 ROM.
After it fully completed it's process I reflashed the custom recovery. From there I am free to flash any ROM I wish. What I did was took the new rom into the developer kitchen and rooted it. Then flashed it. Viola, I am on rooted 4.67.651.3 with full access. In actuality I'm running my barebones build currently, linked in my sig.
Once you run unrevoked or revolutionary you should never have to again. They give you permanent S-OFF. You'll always have the ability to flash a custom recovery, even if you accept an OTA update, and flash ANY custom ROM.
I hope this post helps people better understand the whole root and NAND security process.
bman3333 said:
Seems your rom file host is struggling this morning. I can not dl either version of your ROM, Brad.
Click to expand...
Click to collapse
strange, no problems here, i use dev-host for now, seems it is easier to download there for people in work, etc.
thanks misery for your post. newbies would get confused by all of that, but i still will say to the day i die, lol. do not accept a OTA from sprint if you are rooted. things could go wrong..
brad560 said:
thanks misery for your post. newbies would get confused by all of that, but i still will say to the day i die, lol. do not accept a OTA from sprint if you are rooted. things could go wrong..
Click to expand...
Click to collapse
Accepting an OTA does indeed cause you to lose root acces. No arguement there. But it's a simple matter of reflashing a custom recovery and flashing a rooted ROM through recovery and bam back to being rooted.
So I'm going to go out on a limb and say that there is no solution to root a TP that's already applied the 2.0 update?
I've tried the root methods already obtainable on here and they don't work. I'm guessing (more hoping) that someone is working on finding a solution.
Makes me sad. A co-worker updated it for me because "it said it needed to update it so I did it for you"... *sigh*
OTA2 removed the exploit unless you were already rooted and used Voodoo Rootkeeper to maintain root during the update. I haven't heard the outcome with regards to 2.5. I don't want to risk root so won't be updating unless it's safe.
2.5 is out ? which your version of tablet ?
16gb us. Was delivered last week.
Yeah, I didn't have it rooted before so yeah.
Either people like us find a way to downgrade or wait until a new exploit is found. The former seems easier but my knowledge of these things isn't very high...
Yeah, I'm not sure how to either. I'm good at following directions but when a "friend" upgrades your device for you...
As for downgrading, I don't think that'll be an option until someone finds a Lenovo rom flash utility.
byersbw said:
16gb us. Was delivered last week.
Yeah, I didn't have it rooted before so yeah.
Click to expand...
Click to collapse
2. 5 was not available to US last week. How did you get it? Supposedly it's still going through certification. 0086_US is 2.0. What version are you?
Oh hell.... I've been reading too many posts on the Lenovo forums. My apologies, I am running OTA 2.0 NOT 2.5. I will correct my first post and title.
I'm running ThinkPadTablet_A310_02_0039_0086_US.
Okay. Thanks. No worries, but was scratching my head, looking puzzled.
Haha! I can understand. I have that look a lot sadly. I appreciate you telling me as I had no clue as to what exactly I was saying.
Now, if anyone knows someone on the inside at Lenovo that could get the flash utility...
LOL If only.
And now we wait. Did NOT expect CM9 to come out so fast and be working so didn't care much for root otherwise. Oh well, that was my fault and I knew I'd lose root for the time being. Now I wait patiently, since the primary work of the developers now is making CM9 to work properly so w/e.
Why isn't there a way to downgrade the rom to 075? The tab has a recovery boot. If it could be downgraded, it could then be rooted , then updated.
No way to downgrade, unless you know something the rest of us are unaware of. There's a bunch of folks that either can't root at all, or took OTA2 before getting root/without preserving root. We've been told that there's nothing to be done for the time being.
I don't know how to do it, but I know that's how other tabs got around the problem. I only say it in case someone does.
AFAIK, the problem is the recovery's signature check.. if it recognizes that the update.zip to flash is older than the build actually installed, it won't install the new ROM.
Thanks. Noob enough that I couldn't explain it, just knew it doesn't work.
YassinTP said:
AFAIK, the problem is the recovery's signature check.. if it recognizes that the update.zip to flash is older than the build actually installed, it won't install the new ROM.
Click to expand...
Click to collapse
I wonder what it takes to defeat the check? There must be an update script that performs that check. Editing elements of the update script has been the key to other "can't be done" situations.
http://forum.xda-developers.com/showthread.php?p=22918839[WIP][4.0.3]ICS CM9 ThinkPad Tablet PORT
I'm going to keep putting forth suggestions instead of claiming something can't be done. Afterall, the point of this entire forum is to work togther to overcome obstacles.
While I don't know a lot about these things, if it could be done, it would have been. This forum is overflowing with posts from owners of all kinds devices asking how to downgrade their respective device so they can take root. It's not an uncommon request, and one that I have researched for another device, only to find the same answer. Hey if you find out how to do it, you'll make a fortune.
Two other tablets, the Flyer and the View downgrade to gingerbread, then unlock bootloader, then root, then update to honeycomb, then custom roms are applied. They got the idea from another tab, the Iconia, who got it from the Transformer . . .
I'm just trying to push good and bad ideas to someone with the skills. It's about not taking 'no' as an answer.
Here's the thread for Flyer/View:
http://forum.xda-developers.com/showthread.php?p=21028879[Procedure]No HTC unlock downgrade HC-GB for official OTA