I noticed that Flash is in system so I'm sure you guys have checked it out before but I thought I would bring it up just in case, have you guys looked into Flash for a possible root attempt? If it has been looked into than please feel free to delete this.
Thanks for your work guys,
Josh
AFAIK, that isn't even a possibility.
I can confirm that the new flash 0day exploit affects flash lite.
what 0day are you talking about, and how can you confirm this? have you tried it? I belive flash lite does not run as root so any exploit would be not be of any help.
If you are referring to CVE-2010-1297 it does not effect any versions of Flash Lite.
Edit: If you are referring to the more recent APSB10-14 (that's Adobe's tag, there are too many CVEs to list here), posted on the 10th of this month, I don't find evidence that any version of Flash Lite is involved (feel free to prove me wrong though, I'd welcome it). Also as binny has stated, this would most likely just put you in userland.
Related
I realize I could probably find the answer to this question by digging around but just really quickly can someone tell me... if I have rooted my atrix and am running on ginngerblur... am I able to just download the update and install it with no consequences(besides losing root which sux ass)... because I am seeing all this RSD lite and soft bricking stuff which I am not familiar with at all.. so with a simple yes or no can someone please tell me if it is safe to just download the update thank you.. VERY much in advance...
yes it is safe to update, but it can/will be unsafe if in the future you try to downgrade. This is just the way the new update works is you go for the official update you will lose the ability to downgrade. If that does not bother you then go for it.
I think gingerblur adds mods for the hdmi mirror and webtop with out a dock. So I dont think it will update. It will probably fail to install. Could be wrong though because new update include webtop etc...
Sent from my MB860 using Tapatalk
I think I read that the over the air method won't work..
Yes, if you have a PC just go this link and follow intructions... Only downfall after update to the GB is YOU WILL NOT ABLE to DOWNGRADE by any MOTO standard (RSD/MSU) but if you unlock the bootloader you can do what ever you want go back and foward....
"http://direct.motorola.com/hellomoto/motosupport/source/SoftwareUpdateSummary.asp?country=USA&language=ENS&web_page_name=SUPPORT&strCarrierId=ATT&strPhone=Motorola%20ATRIX%28TM%29%204G&strCable=Micro%20USB%20Data%20Cable&strURL=https://rsddownload.motorola.com/download5/SoftwareUpdateforATTATRIX4Gversion.4.5.91.pdf"
You need a clean 4.1.83 to ensure being trouble free with the OTA.
ANY mods can cause the upgrade to fail. Motorola has said this over and over.
As stated above, I would do the hard wire update. I created a thread with a link here"
http://forum.xda-developers.com/showthread.php?t=1185322
Thanks a lot for the answers guys....that's why I love this community .... and j think I will wait a bit to upgrade... I have gingerblur it is great for now... I don't think I'm really missing anything....tho
Hey,
I've looked through the forum and I'm a bit puzzled how is it with the bootloader "lock" on newly purchased models as I was thinking a bit of buying A500.
I read that the bootloader only checks for checksums when booting kernel / recovery (unless set to generate them), so you can put there custom kernel (get rid of Java Android) when you root it, which I read is not a problem even with 3.2.1 .
The thing I'm puzzled about is that I read there was a BL update and some say the BL is locked since that update and others not - so if I decide to buy A500 and there will be 3.2 with the BL update on it, is it locked and requiring signed kernel image or is it still the checksum only thing?
Skrilax_CZ said:
Hey,
I've looked through the forum and I'm a bit puzzled how is it with the bootloader "lock" on newly purchased models as I was thinking a bit of buying A500.
I read that the bootloader only checks for checksums when booting kernel / recovery (unless set to generate them), so you can put there custom kernel (get rid of Java Android) when you root it, which I read is not a problem even with 3.2.1 .
The thing I'm puzzled about is that I read there was a BL update and some say the BL is locked since that update and others not - so if I decide to buy A500 and there will be 3.2 with the BL update on it, is it locked and requiring signed kernel image or is it still the checksum only thing?
Click to expand...
Click to collapse
No problem. I'll try to put it in "laymans" terms.
Manufacturers don't want you mucking with things. It causes more tech support for them, and also a bad image reputation when stupid people screw things up.
So what they do, is change bootloaders, the part that tells the tab, that the os they are loading, is 100% Acer. If it's not, it's just going to give you a silly face.
So we, here in the Acer community, try to find a way around the bootloader. And invent ways to install a operating system other than Acer.
It's an ongoing battle it seems. We find a way around it, Acer changes the rules, so we have to find another way.
The thing is, our dev's are smarter than their devs. Even HTC gave up, and just offer bootloader unlocks. Besides, they take our innovations, and incorporate them into their newer releases.
So the point is, if you buy a 500, or a 501, XDA community will give the means to unlock it. Root, so we say. And people will help you get it running right.
Here at XDA, we have many roms, from plain rooted stock roms, to cooked roms with OC kernels.
Ah, oops, placed the question incorrectly, I know how the things work around bootloaders and have designed some workarounds. I was rather asking whether new a model of A500 can run custom kernel (don't mean modifications with modules now) or not - but summarizing what you've said: every A500 can run custom kernel, right? Thanks for answering in any case.
Currently on a new A500 with root and kernel. Manufactured in December 11. whole process took an hour. Hope this helps.
Skrilax_CZ said:
Ah, oops, placed the question incorrectly, I know how the things work around bootloaders and have designed some workarounds. I was rather asking whether new a model of A500 can run custom kernel (don't mean modifications with modules now) or not - but summarizing what you've said: every A500 can run custom kernel, right? Thanks for answering in any case.
Click to expand...
Click to collapse
IIRC, only 3.2.1 locked the bootloader, so even if your a500 comes with 3.2 you're safe.
That said, even with 3.2.1 and a locked bootloader, there is a downgrade trick that allows you to go from 3.2.1 (or 3.2, or 3.1) to 3.0 and run an app called iconiaroot and acer recovery installer. Iconiaroot is like z4root, VISIONary, gingerbreak, etc and recovery installer installs CWM recovery from within android. After doing all this you can flash any rom or kernel you want.
Skrilax_CZ said:
Ah, oops, placed the question incorrectly, I know how the things work around bootloaders and have designed some workarounds. I was rather asking whether new a model of A500 can run custom kernel (don't mean modifications with modules now) or not - but summarizing what you've said: every A500 can run custom kernel, right? Thanks for answering in any case.
Click to expand...
Click to collapse
YES if your a500 has Stock android 3.2 or above.. you will have to fallow the downgrade rom flashing.Then you can flash any rom of your choice . there are several threads on this forum explaining how to do this..
Do a search for the thread by Timmy Dean.. his method i think has been called the easiest. It flashes your tablet to a rooted 3.21 stock rom thru adb . from your windows computer..
Acer has yet to plug this hole. So i would not take ANY OTA UPDATES. Im looking for ics if ever releases to plug such holes in the boot loader and stop its magic .
Happy Flashing just please understand everything before proceeding.. there are enough help i bricked my iconia threads.. Boohoo i hate to see anyone do that to such a expensive device..
Thanks. Ordered a piece
So basically I need to store UID, first x bytes in mmcblk0 (for the mmcblk0_start) from sc2k thread (http://forum.xda-developers.com/showthread.php?t=1129873) and I'm pretty much brick safe (should I screw both kernel & recovery).
Happy Flashing
That in theory will give you the resources to recover . BUT BY NO MEANS A Get of of trouble free pass..
do not flash nothing you don't trust and Fallow all instructions Carefully.. You sound well on your way to Making the best of your tablet...
Enjoy your time on xda Iconia forum. There are some awesome people on here. NO im not including myself in that .. Im just a bored thread reading chic. that repeats what i have read... nothing i know is my own work..
Happy Flashing..
erica_renee said:
Im just a bored thread reading chic. that repeats what i have read... nothing i know is my own work..
Happy Flashing..
Click to expand...
Click to collapse
Aren't we all..... Not necessarily a chic though...
Allright, all went smooth (was 3.2 preinstalled). Thanks all.
you are very welcome..
Its simple easy with just a bit of reading up front..
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
So if you have stopped by the dev forum on this site, you'll notice every other thread is offering some root/recovery method for the N7, and each one is acting like theirs is the official method.
So can anyone actually link me to whichever thread TRULY is current? I dont want to end up bricking my device because someone named their thread "latest official root for N7" only to find out it WASNT the latest official root.
RunNgun42 said:
So if you have stopped by the dev forum on this site, you'll notice every other thread is offering some root/recovery method for the N7, and each one is acting like theirs is the official method.
So can anyone actually link me to whichever thread TRULY is current? I dont want to end up bricking my device because someone named their thread "latest official root for N7" only to find out it WASNT the latest official root.
Click to expand...
Click to collapse
There is no 'official' method to root a Nexus 7. There is one click root tools, there is the good ol' ADB method as well that works on all Nexus devices. Pick whichever one you feel comfortable with and root away!
there is NO OFFICIAL method - there a lot of alternative methods - do yourself a favor and read up on these various methods and see what sort of problems users encounter and what solutions are made available to resolve those issues. I found WugFresh's Nexus Root Toolkit to be the easiest one for me http://forum.xda-developers.com/showthread.php?t=1766475
however there are other simpler/more complicated methods out there
one of the most common problems people encounter when rooting is getting their PC to recognize the device properly - installing the proper drivers is very important to get right
RunNgun42 said:
So if you have stopped by the dev forum on this site, you'll notice every other thread is offering some root/recovery method for the N7, and each one is acting like theirs is the official method.
So can anyone actually link me to whichever thread TRULY is current? I dont want to end up bricking my device because someone named their thread "latest official root for N7" only to find out it WASNT the latest official root.
Click to expand...
Click to collapse
RunNgun42 said:
So if you have stopped by the dev forum on this site, you'll notice every other thread is offering some root/recovery method for the N7, and each one is acting like theirs is the official method.
So can anyone actually link me to whichever thread TRULY is current? I dont want to end up bricking my device because someone named their thread "latest official root for N7" only to find out it WASNT the latest official root.
Click to expand...
Click to collapse
Good question, I'm having the same dilemma. Although I sort of figured the answer would be there isn't one before I opened the thread.
Still if there is one that is held in high esteem by a large amount of people & is from a known & respected dev, I'd be happy with that.
As they said, no official method. The one clicks I'm sure work fine, but I prefer to work with adb and go step by step. This is the method I used and the only problem I had was that I needed to find the .94 Super User to flash (the one linked in the thread didn't work for me, it may for you).
Hi Just A quick ltitle qeustion, is it possible to flash a different bootloader on oe1? I want to flash the od5 bootloader on my oe1 updated s5 so I can downgrade back to kitkat and install a miui rom, but someone told me it would just brick my phone.
chaos10299 said:
Hi Just A quick ltitle qeustion, is it possible to flash a different bootloader on oe1? I want to flash the od5 bootloader on my oe1 updated s5 so I can downgrade back to kitkat and install a miui rom, but someone told me it would just brick my phone.
Click to expand...
Click to collapse
Search before you post. And repost, and repost, and repost.
ldeveraux said:
Search before you post. And repost, and repost, and repost.
Click to expand...
Click to collapse
I did nothing about flashing a different bootloader comes up
chaos10299 said:
I did nothing about flashing a different bootloader comes up
Click to expand...
Click to collapse
You're essentially asking if you can downgrade from oe1. If you searched for what you're actually trying to do, you'd know...
ldeveraux said:
You're essentially asking if you can downgrade from oe1. If you searched for what you're actually trying to do, you'd know...
Click to expand...
Click to collapse
Look all I found was that oe1 will not let you downgrade with the mega locked bootloader verizon added so I was wondering if I can flash the od5 bootloader by instelf which would allow me to downgrade to kitkat to root. I do not have root so I can't use the how to update to oe1 and keep root me think but in the method it says to flash the od5 bootloader but I don't know if I have to already be rooted or not.
No, because if you could do what you're suggesting, then you would be able to downgrade from oe1, which you can't.
chaos10299 said:
Look all I found was that oe1 will not let you downgrade with the mega locked bootloader verizon added so I was wondering if I can flash the od5 bootloader by instelf which would allow me to downgrade to kitkat to root. I do not have root so I can't use the how to update to oe1 and keep root me think but in the method it says to flash the od5 bootloader but I don't know if I have to already be rooted or not.
Click to expand...
Click to collapse
You may be onto something with your approach here. Here's a novel idea I think you should try. Start yet ANOTHER thread asking the exact same question. Maybe this time you will get a different answer.
Oh and by the way, your idea in the OP of this thread is completely flawed to begin with. From the day of release, this phone had been unable to run miui or any AOSP based ROM.
landshark68 said:
You may be onto something with your approach here. Here's a novel idea I think you should try. Start yet ANOTHER thread asking the exact same question. Maybe this time you will get a different answer.
Oh and by the way, your idea in the OP of this thread is completely flawed to begin with. From the day of release, this phone had been unable to run miui or any AOSP based ROM.
Click to expand...
Click to collapse
You can run this rom http://forum.xda-developers.com/galaxy-s5/development/rom-miui-v5-g900f-ry09iu-4-8-11-t2946540 verizon with a kitkat kernel I've already had it once.
chaos10299 said:
You can run this rom http://forum.xda-developers.com/galaxy-s5/development/rom-miui-v5-g900f-ry09iu-4-8-11-t2946540 verizon with a kitkat kernel I've already had it once.
Click to expand...
Click to collapse
Hahaha, no you can't. I read the last 10 pages or so of the thread you linked, and your phone froze up after install. Running a ROM on a phone means after install and set up the phone actually works, functions like it should, and you can use it. The bootloader on our phone is locked down which means no miui or any other AOSP ROMs because we can't flash a traditional recovery. The dev himself in that thread said he didn't think his miui ROM worked on Verizon phones. Keep trying to flash not only an AOSP ROM, but one meant for the international version, and I look forward to reading your post where you write that you now have a $600 paper weight.
landshark68 said:
Hahaha, no you can't. I read the last 10 pages or so of the thread you linked, and your phone froze up after install. Running a ROM on a phone means after install and set up the phone actually works, functions like it should, and you can use it. The bootloader on our phone is locked down which means no miui or any other AOSP ROMs because we can't flash a traditional recovery. The dev himself in that thread said he didn't think his miui ROM worked on Verizon phones. Keep trying to flash not only an AOSP ROM, but one meant for the international version, and I look forward to reading your post where you write that you now have a $600 paper weight.
Click to expand...
Click to collapse
Ok and I have the money for it. And it didnt work because i was on lollipop dummy the rom is based off of kitkat and the dev told me i could try it on lollipop, he said he doesn't know if it'll work on lollipop. I don't know why you have to be rude about it. It was a simple question that I asked for a simple answer. But thanks goodbye.