Database Users

[Q] Root for US OTA 2.0

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

[Q] noob first post looking for a wee bit of help

hi all i have been looking around the site to see how to root my galaxy tab 10.1 with 4.0.4 firmware on it i have seen a lot of good post's for what
i want to do but the problem is i dont know what firmware it was on when i unboxed it when i switched it on it wanted to update so is there any
way to see what firmw are it was on before the update and is it possible to root it any help will be appreciated thank you .

billy2464 said:
hi all i have been looking around the site to see how to root my galaxy tab 10.1 with 4.0.4 firmware on it i have seen a lot of good post's for what
i want to do but the problem is i dont know what firmware it was on when i unboxed it when i switched it on it wanted to update so is there any
way to see what firmw are it was on before the update and is it possible to root it any help will be appreciated thank you .
Click to expand...
Click to collapse
Odds are you were on 3.1 when you unboxed but it doesn't matter. The easiest way to root the tab is to use ODIN to flash ClockworkMod Recovery, put the root .zip on the SD card and then flash the root .zip form CWM. Feel free to let me know if you need help!

The standard GT10.1 root zip installs an old version of Superuser that doesn't jive well with ICS. The solution is using Superuser 3.1.3-ARM from the Superuser site, but I have seen so many people struggle with this that I think I might take it upon myself to take the current flashable zip and just create a new one specifically for ICS by replacing the apk. I don't think anyone would mind, would they? There's no rule against doing so as far as I know.
I think I will ask a couple of q's about it and then put that together for everyone if it's cool.

djmatt604 said:
The standard GT10.1 root zip installs an old version of Superuser that doesn't jive well with ICS. The solution is using Superuser 3.1.3-ARM from the Superuser site, but I have seen so many people struggle with this that I think I might take it upon myself to take the current flashable zip and just create a new one specifically for ICS by replacing the apk. I don't think anyone would mind, would they? There's no rule against doing so as far as I know.
I think I will ask a couple of q's about it and then put that together for everyone if it's cool.
Click to expand...
Click to collapse
Supercool. I've tried a lot of ways to root Stock ROM ICS, and most methods just make it worse (scrolling recovery, scrolling wake-up screen, etc.), so if you have a fail-safe method, via Odin, or noob-friendly Odin-free (my pref), be my guest, and I will misuse a secondary one for testing that (my wife's, if I survive the wrath)...
You've got my support!

Just_Another_N00b said:
Supercool. I've tried a lot of ways to root Stock ROM ICS, and most methods just make it worse (scrolling recovery, scrolling wake-up screen, etc.), so if you have a fail-safe method, via Odin, or noob-friendly Odin-free (my pref), be my guest, and I will misuse a secondary one for testing that (my wife's, if I survive the wrath)...
You've got my support!
Click to expand...
Click to collapse
I agree, rolling anything sucks. But I'm...just another noob. *snicker*
What I'm offering is to take that Galaxy_Tab_Root.zip and repackage the flashable zip with the newer Superuser apk...it won't fix the rolling recovery or rolling wakeup of an ICS rom - there's lots of content on this forum that teaches folks how to get around that. I do agree it would be helpful to newcomers to be pointed in the direction of the right solutions so that is something I'd do.
Speaking of the wife's device - I feel you there too.....took me almost 2 months to convince the lady to let me touch it and I just rooted it when she wasn't looking.

You could try this for rooting http://www.xda-developers.com/andro...gn=Feed:+xda-developers/ShsH+(xda-developers)
Swyped from my finger to your face, on my Samsung Galaxy Note.

RavenY2K3 said:
You could try this for rooting http://www.xda-developers.com/andro...gn=Feed:+xda-developers/ShsH+(xda-developers)
Swyped from my finger to your face, on my Samsung Galaxy Note.
Click to expand...
Click to collapse
The OP says it's confirmed working on the GT-P7510, but it was just in a response to a thanks post by someone using a 7510. They never said whether it worked or not. I tried it and it failed on my GT-P7510. I didn't try but once though. YMMV
BTW-It did not do any harm at all trying. It just didn't work.

OK guys, here you go:
ICS Root Zip
Here's what I did
1) Cracked open the Superuser flashable zip and the old root zip
2) Swapped in the new update-binary from the Superuser flashable zip and merged updater-scripts so newer su binary file and Superuser.apk are installed - really not that much different from the Superuser flashable honestly
3) zipped it all back up
All of the credits in the original update script and proper credits for su binary/Superuser.apk added to script - I take credit for nothing other than swapping updated files into the old zip package.
NOTE: This particular package is NOT TESTED!!! I am at work and already have a rooted tab so haven't got the environment to test it right now. However, in all honesty, the changes are pretty minor so it should work just fine. If any of you are on stock firmware, give it a go if you choose but don't flame me if it doesn't work. TAKE A BACKUP WITH YOUR RECOVERY FIRST! THAT IS ALREADY A RULE!
Hope this works and saves folks a step trying to root ICS.
EDIT: If someone can confirm that this works I'll probably just add the same link to the existing HOWTO thread for rooting this device. People are already looking there first for direction so we'll make it nice and easy to find.

help please
9xnine said:
Odds are you were on 3.1 when you unboxed but it doesn't matter. The easiest way to root the tab is to use ODIN to flash ClockworkMod Recovery, put the root .zip on the SD card and then flash the root .zip form CWM. Feel free to let me know if you need help!
Click to expand...
Click to collapse
thank you for your response and offeing to help i would'nt mind if your way works as i dont want to brick it as its only a week old so if you can point me in the right direction to get the files i need and maybe a guide to follow that would be appreciaped thanks .

Head into the Android Development section and check the stickies at the top of the forum. There are wonderful guides there that will point you to the correct recovery.
Make sure you save this ZIP file I re-packaged to the root of your tablet before you start...saves you some time when you actually start the process. You can simply reboot into your newly flashed recovery and then flash the zip file. Let me know if it works for you!! Again, I didn't really change it at all, just tiny changes to the updater script and updated files.

Hi billy...How did things go? Were you able to get rooted?

Any devs wanna help

Are there any devs that would be interested in a new challenge? The electrify m for us cellular is the sister to the RAZR m but with an unlocked boot loader. Its a great phone just need somebody to kick start the development on it. If you are interested here is the thread for the factory software image. I'm not begging just hoping somebody will.
http://teamuscellular.com/Forum/top...trify-m-stock-firmware-unlockable/#entry44454
Sent from my XT901 using xda premium

I am also hoping someone can assist us USC users with this. Our version is no longer rootable using the methods found here for the Razr m.
TIA!
Sent from my XT901 using Tapatalk 2

Meeeee toooooo!!!!
I'm not a developer, but I'm looking into a few things in regards to getting something going with this model. The biggest hurdle right now for me is figuring out how the partitions work on this thing and when they get mounted. Seems like they don't even exist until the damn thing is halfway booted up, so flashing from fastboot is a challenge. Once I figure out the right things to put into an updater script I think she'll be something we can work on. Again, I'm no developer, but I'm hoping I can gather enough peices of info that someone with more skills can take off with it.
In the meantime I'm cramming through the android sdk docs and java for dummies, smali stuff and xml. Hopefully I'll get to where I can start doing something before the phone is an antique.

dtrud0h said:
I'm not a developer, but I'm looking into a few things in regards to getting something going with this model. The biggest hurdle right now for me is figuring out how the partitions work on this thing and when they get mounted. Seems like they don't even exist until the damn thing is halfway booted up, so flashing from fastboot is a challenge. Once I figure out the right things to put into an updater script I think she'll be something we can work on. Again, I'm no developer, but I'm hoping I can gather enough peices of info that someone with more skills can take off with it.
In the meantime I'm cramming through the android sdk docs and java for dummies, smali stuff and xml. Hopefully I'll get to where I can start doing something before the phone is an antique.
Click to expand...
Click to collapse
Well as it is now, we can root using ADB commands with fastboot. You can either use CWM or TWRP, however CWM is a little more involved, so most people are just using TWRP.
Once rooted, CM10 can be flashed onto the M, but NFC and Wifi Direct don't work, which generally isn't a deal breaker for anyone on the Electrify M. However, it's a careful process since anyone flashing to CM10 will need to restore the APN settings.
Personally, I just kept it stock JB, but rooted. CM10 was too much of a headache to bother with after I screwed up the first time and had to flash stock in an emergency when on vacation. haha!
This is all being discussed on another website, and since I don't know the rules about posting external links, I'm not going to =)

[LOKI] Bootloader hack official FAQ thread

I just released Loki, a set of tools for developers and users to flash custom kernels and recoveries on the AT&T and Verizon branded Samsung Galaxy S4.
The tool is available at:
https://github.com/djrbliss/loki
The technical details on how the exploit works are described at:
http://blog.azimuthsecurity.com/2013/05/exploiting-samsung-galaxy-s4-secure-boot.html
This is a support thread that I will check regularly until I decide to hand over support to the community. Feel free to ask any questions, and I may add the answers to this post. As a guideline, if it's a question that's already been answered in this thread or in the README for Loki, I will ignore it.
Does this make any permanent changes to the device?
No permanent changes are made to your device when using loki_flash. The bootloader itself is untouched. By restoring the original system, boot, and recovery images (via Odin or otherwise), the device will be in a stock state.
Can this be patched?
Absolutely. Any update that includes a new aboot will almost definitely cause your custom kernel or recovery to fail to boot without running it through loki_patch again, and if the update contains a fix for the vulnerability Loki exploits, it may permanently prevent using the tool. It's possible for Samsung to ship an update that prevents downgrading aboot to a vulnerable version, so I recommend avoiding installing any OTA updates without confirmation that it's safe.
What about the bounty?
As usual, I encourage anyone looking to donate (as part of the bounty or otherwise) to give their money to a reputable charity organization instead. If you insist on donating to me, I'm sure you can find my Paypal account somehow.
This all seems complicated. What about a step-by-step guide?
These tools are primarily intended for developers, who will be able to use them and provide ordinary users with easy ways to flash custom ROMs. Be patient, I'm sure your favorite ROM developer will come up with something for you.
I've installed a Loki-patched recovery. Can I just install regular custom ROMs now?
Any ROMs that include a replacement boot.img must be modified to include a Loki-patched boot.lok file instead. Otherwise, your phone will fail to boot until you restore a Samsung-signed boot.img or a custom boot.lok image via your custom recovery, or flash a stock image via Odin.
So this is just like kexec?
This is similar to kexec in that it works around a locked bootloader, but this approach is much more flexible and robust. Kernel and recovery developers can build their projects just as they would for an unlocked device, run the final result through Loki, and then it's ready to be flashed. No hackery and brokenness required.

Thanks!!
Sent from my SAMSUNG-SGH-I337 using xda premium

is this similar to htc dev which doesn't truly unlock "s-off" the device? i assume your method just circumvents the locked bootloader? the way i read what your tool accomplishes is for us to flash a recovery and kernels but doesn't actually touch the locked bootloader status?
thanks for your work. also let the games begin!

Thank you very much!!!!
Sent from my SAMSUNG-SGH-I337 using Tapatalk 2

Very much appreciated!

By the time I get back from work, I'm pretty sure there'll be at least two recoveries and three roms prepared

Wooooot!!! Thanks man.

Awesome! Finally devs can start releasing some ROMs!

hopefully someone can make a toolkit and make this a one-click unlock/root

Thanks so much! :good:

thanks dude.

RawisTheGameHhH said:
hopefully someone can make a toolkit and make this a one-click unlock/root
Click to expand...
Click to collapse
This or a step by step guide.

Theres already recovery available...
But thank you Dan, now all this bootloader madness can finally stop!

so we can flash a recovery and kernels with this tool but what about radios? can those be flashed with a locked bootloader? i swore they couldn't.

You are the MAN. A charity will be finding my donation per your recommendation.
Thanks again for all the great work.

Oh man, I'm dying here. I don't get off work for another ~6 hours! And I don't have admin access on my work computer, so no adb.
So, we have a patched recovery now, but custom kernels also have to be patched, correct? So it would be a bad idea to adb the recovery and then immediately try to use it to flash one of the roms that are already out there?

mattdm said:
Oh man, I'm dying here. I don't get off work for another ~6 hours!
So, we have a patched recovery now, but custom kernels also have to be patched, correct? So it would be a bad idea to adb the recovery and then immediately try to use it to flash one of the roms that are already out there?
Click to expand...
Click to collapse
i wouldn't try flashing any roms yet.

YES!YES!YES!
Dan, You are The Man!!! Thank you so much. May your thanks meter need a fire extinguisher before the day is done....lol.:good::good::good::highfive::highfive::highfive:

did a nadroid backup, and it is doing multiple archives, is there a setting I missed?
nevermind, I stand correct, nice, very nice, thanks goes out to everyone involved.

Solid.
Sent from my ASUS Transformer Pad TF700T using XDA Premium HD app

[Q] Challenge: I've messed up my new RAZR

Hey XDA! Just picked up new Droid RAZR M (XT907) and immediately messed it up on the first day. So here's the deal:
- I'm an idiot.
- Got it with 98.30.1 FW, so I used this method to root it: http://www.droidviews.com/root-verizon-droid-razr-m-razr-hd-maxx-hd-latest-firmware/
- Forgot to unlock the bootloader
- Installed ROM Manager and flashed CWM recovery
And this must have messed up something, because now I'm not able to:
- Unlock my bootloader
- Get into recovery, it returns this error: "failed to hab check for recovery 0x56"
I'm clueless now, since I have not much knowledge in this stuff...
I'd be so thankful if anyone could help me
Thanks!
Edit: Will this help me? http://www.phonearena.com/news/How-...-M-back-to-stock-ICS-from-the-JB-leak_id35580
Edit 2: Okay, so that didn't help, but I used "DROID RAZR M Utility 1.20" from mattlgroff and I was successful with bringing OG recovery back. However, I found out that the bootloader on my build just can't be unlocked. I also tried to install Safestrap and install CM on another slot, but it failed with status 6. Why is that? Or is there just any other way how to install any ROM?

krYshuT said:
Hey XDA! Just picked up new Droid RAZR M (XT907) and immediately messed it up on the first day. So here's the deal:
- I'm an idiot.
- Got it with 98.30.1 FW, so I used this method to root it: http://www.droidviews.com/root-verizon-droid-razr-m-razr-hd-maxx-hd-latest-firmware/
- Forgot to unlock the bootloader
- Installed ROM Manager and flashed CWM recovery
And this must have messed up something, because now I'm not able to:
- Unlock my bootloader
- Get into recovery, it returns this error: "failed to hab check for recovery 0x56"
I'm clueless now, since I have not much knowledge in this stuff...
I'd be so thankful if anyone could help me
Thanks!
Edit: Will this help me? http://www.phonearena.com/news/How-...-M-back-to-stock-ICS-from-the-JB-leak_id35580
Edit 2: Okay, so that didn't help, but I used "DROID RAZR M Utility 1.20" from mattlgroff and I was successful with bringing OG recovery back. However, I found out that the bootloader on my build just can't be unlocked. I also tried to install Safestrap and install CM on another slot, but it failed with status 6. Why is that? Or is there just any other way how to install any ROM?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=45548210&postcount=3

Thanks, but I don't need that. I just expected a simple answer. So I'll just answer myself, sum up what I needed to know. Correct me if I'm wrong:
- There's no way I'm going to unlock my BL, I'm stuck with locked BL on my build
- There's no way I'm going to install CM (not even using SS)
- I can only wait on official Motorola KitKat update (coming in months???)
- I can also install some stock-based ROMs with SS
Yeah, I don't wanna Safestrap with custom stock-based ROMs if it can't be official CM. I'll rather keep my internal storage space with stock, disable bloat and wait for official 4.4.2 update...

krYshuT said:
Thanks, but I don't need that. I just expected a simple answer. So I'll just answer myself, sum up what I needed to know. Correct me if I'm wrong:
- There's no way I'm going to unlock my BL, I'm stuck with locked BL on my build
- There's no way I'm going to install CM (not even using SS)
- I can only wait on official Motorola KitKat update (coming in months???)
- I can also install some stock-based ROMs with SS
Yeah, IFon't wanna Safestrap with custom stock-based ROMs if it can't be official CM. I'll rather keep my internal storage space with stock, disable bloat and wait for official 4.4.2 update...
Click to expand...
Click to collapse
Simple answer.
Do you know how many times it has been summed up! For you to find if you just searched! Or just browsed the thread titles in the general forum!
That page is all YOU need.
We need it sticked.
There is an old ss cm btw. See dev section.

aviwdoowks said:
Simple answer.
That page is all YOU need.
We need it sticked.
There is an old ss cm btw. See dev section.
Click to expand...
Click to collapse
Yeah, that page is also A LOT of stuff I DO NOT need.
You didn't get that. Simple answer is something else than you may think and also best answer is something really distant.
I just wanted a direct response or confirmation of what I said, not this negativism. Yeah, but what could I expect, typical XDA attitude...

krYshuT said:
Yeah, that page is also A LOT of stuff I DO NOT need.
You didn't get that. Simple answer is something else than you may think and also best answer is something really distant.
I just wanted a direct response or confirmation of what I said, not this negativism. Yeah, but what could I expect, typical XDA attitude...
Click to expand...
Click to collapse
I wanted...
We do not need the likes of you!

krYshuT said:
Yeah, that page is also A LOT of stuff I DO NOT need.
You didn't get that. Simple answer is something else than you may think and also best answer is something really distant.
I just wanted a direct response or confirmation of what I said, not this negativism. Yeah, but what could I expect, typical XDA attitude...
Click to expand...
Click to collapse
I do apologize you fell this way about the members here at xda... Here at xda we help a lot of people, take time from our day away from our loved ones to assist those in need... Avi helps a lot members a lot of members... You have to understand that your issue your question has been answered and resolved several times prior to this post... I'm sure just scrolling through the topics reading the titles you would have found the answer/s to your question/s (probably answered by Avi)... I understand the search feature of xda may not result in what you are looking for but google will... We do get very tired of answering the same questions over and over again... So i apologize for the "negativism" but Why help those who won't help them selves... knowledge is power and reading is the key...
Sent from my XT907 using xda app-developers app

krYshuT said:
Thanks, but I don't need that. I just expected a simple answer. So I'll just answer myself, sum up what I needed to know. Correct me if I'm wrong:
- There's no way I'm going to unlock my BL, I'm stuck with locked BL on my build
- There's no way I'm going to install CM (not even using SS)
- I can only wait on official Motorola KitKat update (coming in months???)
- I can also install some stock-based ROMs with SS
Yeah, I don't wanna Safestrap with custom stock-based ROMs if it can't be official CM. I'll rather keep my internal storage space with stock, disable bloat and wait for official 4.4.2 update...
Click to expand...
Click to collapse
To answer your question, yes to all. And before you jump so quick as to label this typical xda attitude, keep in mind I can label you typical self entitled noob expects everything on a silver platter. People get tired of answering the same question a hundred times over... Guess your number in line. Anytime you're dealing with a locked BL it's a good idea to learn all the intricacies of your phone, which is precisely where you were referred to.... And precisely where I had to start too. That said, politeness and gratitude will get you farther in getting noob answers quicker, which none of your posts contained.

Thanks! I'm sorry if it sounded rude, I'm really grateful for any type of help. I've spent like 5h in all kinds of threads, but most of the time I just get "half-answers" from just reading and reading and reading. I'm not expecting any type of extremely thorough answer, just a direct answer with confirming of what I said. Sending me another link (which I already read) just makes me even more confused. I just found out for example, that Koush's Helium doesn't work on Motorola devices. Does that apply for root method, too? If so, are there any other alternatives to backup & restore on my RAZR M (without and with root)?