yashsingh1/xdaforums huggingface dataset:
[Thinkpad Tablet Android Development] gallahad2000:
No dice, the K1 had it's key accidentally released. The TPT is still locked tight. It's kinda cruel for you to have to share the same XDA forum with us but hopefully it'll give you hope that the TPT will eventually get root.
[Thinkpad Tablet Android Development] timmyDean:
If you want to test, then test if the leaked keys work

Not with this. But in theory, you could use this principle. The key would be does the thinkpad recognize the ASUS leaked key? Which is what makes 'time-travel to any OTA possible' (flux capacitor).

Here's my questions:

1. Does the thinkpad have Nvida chipset therefore Nvflash is supported?

2. If yes, then does this command work "./nvflash --sbk 0x0d0a6f49 0x6c577634 0x4d634e55 0x47336d55 --bct flash.bct --setbct --odmdata 0x300c0011 --configfile flash.cfg --bl transformer_bootloader.bin --sync"

Note, this will NOT cause any damage to your tablet. It will just test if we can unlock the boot loader. If this unlocks it, then YES, you can dump off what we need to build tools to flash it. I've attached the transformer files you'll need to test the keys. You just need the Nvflash tool installed. So, give this a try, if it works then we should be able to build a root flash. If not, then we'll need to wait for a set of leaked keys or for someone to find a hole in the OS to exploit to gain root.

TD
[Thinkpad Tablet Android Development] gallahad2000:
Yeah, it has the Tegra 2 just like ours.
[Thinkpad Tablet Android Development] timmyDean:
Ok, so can you load the transformer bootloader ??? Someone will have to test the leak with the transformer boot. These keys probably won't unlock the TPT boot loader but would allow us access to the data. Then we could build a different boot loader, root it, and then flash in TPT boot loader. Sort of like booting to a CD with Linux and then mounting your C: drive and putting an exploit in it. Then booting back to Windows. Anyway, the key is can we get the TPT to recognize another boot loader that we have the keys for?

NOTE: To test this you'll have to put the TPT into APX (flash/fastboot) mode. So, someone will have to say what the key combination is for it.
[Thinkpad Tablet Android Development] timmyDean:
Also, does anyone know if the boot loader for the TPT was every unlocked?

If so, what version, or has it always been locked? I mean way back as anyone can recall. Not what they have. If it was ever unlocked then all we'd have to do is get our hands on the nvida unlocked boot loader. That would be easier than building one.

Also, what version (exact tablet and a link would be helpful) is everyone trying to root? If the boot loader test works, I'll go buy one and root it, so I'll need to know what to get.

Thanks,

TD
[Thinkpad Tablet Android Development] yirsung:
I think it is unlocked.

Here:

http://xdaforums.com/showthread.php?t=1231771

---------- Post added at 01:16 AM ---------- Previous post was at 01:15 AM ----------

I will try it tonite. See what i can get.

Thanks for helping. Let's root this.

---------- Post added at 01:19 AM ---------- Previous post was at 01:16 AM ----------

APX (flash/fastboot) mod?

How do i get in here?

Same as Recovery?I guess not.

I can get into Recovery mod.
[Thinkpad Tablet Android Development] timmyDean:
I do NOT know how to get into APX mode. On the K1 you power off and then hold press and hold the + and - volume keys and press and hold the power button. You will see Windows detect the device and should see the APX driver loaded. But, for the TPT, no idea.

TD
[Thinkpad Tablet Android Development] timmyDean:
Another thing you could try, after testing the keys for the ASUS is can you talk to the device via adb when you are in recovery? I doubt they left the hole open, but when you boot to recovery you are actually loading from the SOS partition another copy of Linux. On some tablets, you force the recovery to boot and of course it crashes with yellow !, which is normal. But at this time you are able to connect to it via adb shell. If you can, you will be root(#) on the SOS partition (there is no security on SOS, or at least there shouldn't be). Then you mount p6 rw put in your su, and reboot. But, I doubt they left that open, but it's worth a try. It would be easier than building boot loaders.

TD
[Thinkpad Tablet Android Development] yirsung:
Ok, I got into APX mode

However, can not find a driver for it.

Is the driver universal?
[Thinkpad Tablet Android Development] gallahad2000:
http://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles/adb_driver_20110720.zip
[Thinkpad Tablet Android Development] yirsung:
Thanks but it is for ADB not APX
[Thinkpad Tablet Android Development] gallahad2000:
here it is:

http://android.modaco.com/topic/335416-nvflash-setup-instructions-drivers-links-active/
[Thinkpad Tablet Android Development] yirsung:
Now I did "nvflash --sync"

It said

Nvflash started

Command send failed <usb write failed>

Damn it
[Thinkpad Tablet Android Development] timmyDean:
You have to use the complete command with the SBK keys and the transformer.bin

which I posted. Write failed means the bootloader is locked.

"./nvflash --sbk 0x0d0a6f49 0x6c577634 0x4d634e55 0x47336d55 --bct flash.bct --setbct --odmdata 0x300c0011 --configfile flash.cfg --bl transformer_bootloader.bin --sync"

This command ONLY mounts the transformer blob. IT WILL NOT destroy anything. I just don't want to waste money on buying one.

Also, try the recovery exploit now that you have the drivers loaded.

ALSO what's the secret key combination to get into APX mode????
[Thinkpad Tablet Android Development] yirsung:
I can do it with "./"

So did nvflash --sbk 0x0d0a6f49 0x6c577634 0x4d634e55 0x47336d55 --bct flash.bct --setbct --odmdata 0x300c0011 --configfile flash.cfg --bl transformer_bootloader.bin --sync

here is what I got

Nvflash started

nvflash configuration file error: file not found

---------- Post added at 08:28 AM ---------- Previous post was at 08:27 AM ----------

I put Nvflash under my SDK files (same folder with ADB)

then I put all files you gave me to the same folder .

any thing wrong?
[Thinkpad Tablet Android Development] timmyDean:
Got the correct files http://xdaforums.com/showpost.php?p=21373483&postcount=4 the files I posted???

It should be only three files and you will need them in your folder, so can you check they're there?
[Thinkpad Tablet Android Development] yirsung:
Yes, that's what I did. I guess the key won't work on TPT
[Thinkpad Tablet Android Development] timmyDean:
Missing file is a filing missing not that the keys don't work? Sounds like the keys work, but it's hard to tell remotely.
[Thinkpad Tablet Android Development] yirsung:
transformer_bootloader.bin

flash.bct

flash.cfg

are in same folder with nvflash

is it right?
[Thinkpad Tablet Android Development] soveryevil:
Hey, I tried this on my TPT and I got the error rcm version 0X4 no matter what NVflash commands I use.

Which as appears to be incorrect key.

Any one have anything else I can try as I have APX and ADB set up just fine.
[Thinkpad Tablet Android Development] yirsung:
Me too.

I did try everything I can.

Still no luck......

When we can root this damn thing!
[Thinkpad Tablet Android Development] timmyDean:
Can you put it into recovery, get the yellow ! and then try to connect to it with adb shell?????
[Thinkpad Tablet Android Development] soveryevil:
Yeah connected it and get

C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
43c7044419fc2d7 recovery

C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
[Thinkpad Tablet Android Development] timmyDean:
Well that sort of stinks. I didn't think they'd leave that hole open. It was worth a try. So, form what I've learned form this, is it doesn't seem like the leaked keys allow you to load the transformer's boot image even though we have the key for it. I'm suspecting the chipset to be different, but then again I don't know, I don't have one (nor do I want one).

Therefore this sort of takes nvflash off the table unless we get leaked keys. Next, all the known hacks seem to be removed from what I've gathered. So, someone will have to find a new one. Has anyone tried the GPS hack? Haven't seen that tested yet, but it works on the locked Toshiba.
[Thinkpad Tablet Android Development] soveryevil:
point me to a link for it and I'll try it
[Thinkpad Tablet Android Development] timmyDean:
The key is ln

can you do this:

adb shell ln -s /data/local.prop /data/gps/gldata.sto

What happens, is GPS runs as root and writes to the gldata.sto file. So if it's not there (it gets purged on factory restores) then you tell the OS to link (ln) to another location. If the link works, then when GPS turns on it writes to this cache file. If it writes, the the file is written to with rw-rw-rw- permissions which means we can not write to it, then you:

adb shell "echo 'ro.kernel.qemu=1' > /data/local.prop"

Reboot and you'll have root. But, they probably patched that too, but it's fairly new and works on some devices.
[Thinkpad Tablet Android Development] soveryevil:
link failed permission denied.

Thanks if there is anything else you can think of I could go onto #thinkpad-android and do some real time commands for you?
[Thinkpad Tablet Android Development] timmyDean:
Nothing off the top of my head, if we can't get to the bootloader than we're at the mercy of someone leaking keys. I'll keep my eyes and ears open. I don't really have a reason to get a TPT. But, I am interested in the challenge.
[Thinkpad Tablet Android Development] yirsung:
I did this 2 days ago. no luck
[Thinkpad Tablet Android Development] timmyDean:
Ok, then I don't have a TPT nor do I care too <lol>. So, I am at a loss now if you've all tried the normal exploits. I did download the OTA from their website and looked at it. Nothing really exciting to share.

You really need some leaked keys I'm suspecting now unless someone comes up with an exploit. Or a leaked certificate so we can sign the OTA update.zip therefore fooling it into thinking it came from Lenovo.

In theory, you could extract the bootloader from an OTA and then run a comparison against it to a known set of unlocked data to get the keys that encrypted it?? Not sure, just thinking (typing out load) here. Way too much coffee this morning and too much work to write really. You know, I think I read about someone hacking certificates, so take their OTA and run one of those programs against it to get the key they're using to sign the OTA. Then we unzip it, add root, re-zip, and sign the update? If someone wants to spend some time researching that, it would be start. Figure out what signing method they're using and then how to get the key. Like I said, it's a standard encryption that I think a few at MIT hacked as a challenge. Anyway, Google and see what you come up with.

Nvflash is really probably what well need to get working unless you can unzip the OTA and re-zip and then fake the Lenovo signature. Once that gets solved, I'd help build the nvfash images. It's really a shame they've locked the bootloader. They should just do what others have done and that's provide a method to unlock it.

Sorry I can't help you guys on the TPT, there's a lot smarter people out there probably already working on it.

Let me know if there's any news on it,

TD
[Thinkpad Tablet Android Development] lx1226:
The thread is getting away from TD's first post.
[Thinkpad Tablet Android Development] gilberthcordova:
If i want to update to K1_A301_13_13_120110_SG and keep the root, what can i do? use the back door? how?

thanks :)
[Thinkpad Tablet Android Development] Dueces99:
If i have APX drivers already on my system for another tablet (GTablet), would I need to remove those drivers first before installing these, or does it not matter?
[Thinkpad Tablet Android Development] twe69:
I have a US Ideapad K1 and noticed a UK OTA with Blob from the website, I am in the UK so wouldn't mind changing it..... K1_A301_03_03_111110_UK.zip

Has anyone tried that? Thanks.
[Thinkpad Tablet Android Development] twe69:
Just trying this out and I get an error saying....

'nvflash' is not recognised as an internal or external command, operable program or batch file.

I am following the guide in the pdf of the tool..... On my Lenovo Ideapad K1.

Any ideas?

Thanks....
[Thinkpad Tablet Android Development] gallahad2000:
I believe all the root methods so far have involved flashing a rooted rom. Titanium Backup requires root so you'll have to reinstall everything.
[Thinkpad Tablet Android Development] rezapatel:
Really upsetting :-(

Which method / rom is suggested?

Sent from my HTC Vision
[Thinkpad Tablet Android Development] rezapatel:
Hello guys - I'm all ready to redownload the OTA's, but now I'm stuck trying to find the best or the working method.

I remember seeing a method, that rooted you directly on version 13_13, so that way i can directly jump on to 14_14 which is the latest.

So, if someone can point me to the best method to permanently root would really be appreciated.

Thanks a million! Would really want to do it over the weekend, else will have to wait for another week :)

Cheers!
[Thinkpad Tablet Android Development] rezapatel:
Any updates / info on this? Anyone, pls? Thanks!

Sent from my HTC Vision
[Thinkpad Tablet Android Development] Twist79:
I got a German Ideapad K1 with UMTS and Wifi

I tried this root + OTA update method with backdoor on.

From the this US version to K1_A301_02_02_111004_GE is no problem.

When I flash K1_A301_11_11_111213_M_GE I loose root and this firmware has bugs

Then I have to use OTA because sdcard\download\update-zip method does not work...the zip just gets deleted and the K1 reboots.

Now I am on K1_A301_12_12_120109_M_GE

No root no fun.

Edit: and no Sound! so this backdoor does something...but superuser does not install....

I tried it 3 times...

Could anyone help me?

BTW: The K1 just got sold cheap in Germany so there will be more users with my firmware and root problems.
[Thinkpad Tablet Android Development] dms92969:
It seems that TimmyDean fell off the face of the earth. It's been a while since we posted about the issues with his rom.

khanning88 has

14_14 Rooted

http://xdaforums.com/showthread.php?t=1564002

14_14 Stock Rom (No Root) with 3rd party apps included

http://xdaforums.com/showthread.php?t=1560441

David.
[Thinkpad Tablet Android Development] Twist79:
Thanks but I got 3G Version....will not work with USA wifi only ROM won't it?
[Thinkpad Tablet Android Development] Supaiku:
Bootloop of death

So I flashed a new OTA (K1_A301_13_13_111209_US.zip) just by dropping it in the Downloads folder and pressing Vol+ and Power, and now I've got terrible bootloops of death.

Has anyone had experience with this? Do you think this tool will do the trick?

I tried nvflash from here but it just gives some lame error:

nvflash -w
Nvflash started
rcm version 0X4
Command send failed (usb write failed)

Does anyone have any information for me? The good news is it's a brand new thing - all I did was put on a screen protector - so it should be covered by the warranty... I hope! That is if I can't get it working on my own first:)

EDIT: And I'm retarted. I was just testing nvflash, and I hadn't put it in the right directory yet. *sigh* All fixed up:)
[Thinkpad Tablet Android Development] hmartinus:
I'm experiencing the same problem...I've got never ending bootloop...I'm trying to flash to K1_A301_03_03_111025_M_SG but it gave me error. I read that you succeeded flashed to SG model...but I've searched in the OTA link, only that rom that has blob in it. Do you have other SG ROM that has blob in it? my device is the 3g model
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] Aandi87:
Hi guys,

today i had bad day. Cotulla released the new HD2 Ultrafruit Rom and i wanted to try it out.

So i followed the flashing steps which worked for me and mostly everone in this forum. Like:

-1st it's recommended to flash an old rom wm 6.5 and let it boot entirely

-Format your SD card too

-Flash magldr 1.13

-Enable 24MB extra memory in Magldr services

-Delete MBR of SDcard in Magldr services

-Flash the rom with DWI & Set a correct time & date.

But somehow my new Transcend SD wont get formated via 6.5 ROM and clearing MBR hasnt made a change to this. I tried serveral times with different approaches and no success.

Another problem was, that when i inserted my 2 old SDs, no matter which one, in my HD2 i could boot just one time. After a reboot, the touchscreen didnt response.

Conclusion for me on this Friday 13. :) : No phone for me.

But finally i've found a way:

I flashed Yuki and Xboxmods Rom which is able to hande cabs WITHOUT a SD inside. So i had some MB left on my phone memory which allowed me to install DEV_STORAGELOCK.cab from Xboxmod.

But as we know just inserting a SD wont let the phone recognize the card. This works just with a reflash or a hardreset from the Info screen of WP7.

I did a hardreset and after that the DEV_STORAGELOCK.cab was still installed and my SD was recognized. So i could execute the storage lock app on the phone and unlock my SD.

After that my Windows 7 PC could see the card when i went to MAGLDR and its Mass Storage Mode. Then i formated the SD with the Panasonic SD Formatter with Options/Format Type = FULL (ERASE) and FORMAT SIZE ADJUSTMENT on.

->Voila i had my 16GB cards back to life.

The absence of a SD Card Reader wasnt helpful too.

Hope this little How to helps others too.
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] mideel:
haha, exactly what happened to me :D I tried many things, but nothing worked. And then I thought "Okay, lets move to the Q&A Forum and look for answers" .. and your topic was the first one ;) great.

worked perfectly.
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] jackrabbit72380:
Sory about your bad experiance!

We dont need a hole srory to explane how this is done if thats why your reading this! it go's like this...

1.Flash magldr 1.13 (or) if your alredy have it services/clear sdmem

2.Enable 24MB extra memory

3.flash xbmod yukixda 7004

4.install DEV_STORAGELOCK.cab

5 use the app & unlock your card then take it out untill your newly flashed rom boots up then put it back in!

I know he just sayed that but I figure i take out the unusefull parts! make it simple!

I know this is a frustrating experiance to have but never the less hears your fix!
[General Questions and Answers] Zeely:
1. There ROOT for XPERIA Pro?

2. Why XPERIA Pro is not listed phones on this board?
[Samsung Galaxy Nexus] jack_d12:
I have noticed white blemishes near the metallic textured area surrounding the galaxy nexus rear camera. It doesn't feel like there is a scratch on it since it has that thin lined texture, but I can't get it off no matter how hard I rub it!

Does anyone else have these blemishes?

Thanks!
[HTC Rezound] JeramyEggs:
Alright, so I am not really new to flashing, and rooting, but I am a newb when it comes to S-on devices. If I made a nandroid with the original kernel, andI then flashed an alternate, will I be able to just flash my nandroid, or do I have to change the kernel too? I know typically, the kernel is saved within the backup. Is it the same on a s-on device? Tried finding an answer on many boards, but came up empty. I should stop playing with things I don't understand. Thanks..... from my ADR6425LVW using Tapatalk

Edit; Also, with the frequencies jumping on a kernel, is this detrimental to the CPU? I get the best battery life on dsb's, but am afraid that the jumping is bad for my phone. I promise this is my last stupid post for the next 30 seconds....
[HTC Rezound] MrSmith317:
It's better to ask questions that just randomly doing things. I believe the answer to this question is you'd have to use a recovery that is capable of flashing the boot partition. I think this is why we have to flash kernels separately, because they can't be flashed via any of the recoveries available. Seems that you would be able to do this with full S-Off, just not with S-On.
[HTC Rezound] JeramyEggs:
So the proper thing to do is to flash the original kernel, then my recovery? I just want to get the correct method before I go flash happy. Thanks Mr.Smith for the quick reply....
[HTC Rezound] MrSmith317:
Flash ROM then Kernel(before you leave recovery). If you're doing a restore, then restore then kernel.
[Samsung Galaxy Nexus] cbkitt:
What’s New?

- Attempt at some ICS optimisations

- Added a check for phones with ICS (takes you to sound settings to enable Volume+ in Meida Effects)

- App starts differently (should be more reliable)

- App should be more ‘persistant’ (see above)

- EQ values completely changed

- Volume levels completely changed

- Higher volumes now available (up to +20)

- Louder volumes should now be attainable

- EQ Band frequencies now shown

http://androidaudiohacks.com/?p=149#more-149
[Samsung Galaxy Nexus] Zargon335:
Is this still uploading? The download link isn't working right now for me.
[Samsung Galaxy Nexus] bryannh:
posting for when link works, i get 404
[Samsung Galaxy Nexus] vibranturk:
fix your link.
[Samsung Galaxy Nexus] zephiK:
Source: http://androidaudiohacks.com/?p=149#more-149

Edit: whoa this new version is AMAZING... huge difference in volume from previous, it can go up to +10 as well
[Samsung Galaxy Nexus] winwiz:
Source: http://androidaudiohacks.com/?p=149#more-149

Edit: whoa this new version is AMAZING... huge difference in volume from previous, it can go up to +10 as well[/QUOTE]

What an amazing difference!!! Wow
[Samsung Galaxy Nexus] Skunk Ape1:
How do you install this? Never mind....
[Samsung Galaxy Nexus] Soulja556:
Wow amazing work! Set mine to +15, its almost too loud! lol
[Samsung Galaxy Nexus] djfrost17:
just installed it...let's try this out...:D

WOW!!! THIS IS A MUST HAVE!!!! so much better!!! i cant wait to try it in my car via bluetooth!!!

thanks!!!
[Samsung Galaxy Nexus] Stigy:
What settings are people using on their Nexus?
[Samsung Galaxy Nexus] georgiapi:
WoW, I was a fan of Equalizer over Volume+ but am defecting over to this new Beta V+ Camp. The Equalizer having no auto start was a pain anyway.

The thing gets loud enough to make the speaker distort and go into cut out if pushed more. It looks like Sammy added a protection circuit. Amazing.

Scared me, I thought I blew her. But after backing out she came back. It cuts out to a super low level and will not respond until you correct or reset.

I adjusted while listening to a known strong .mp3 on my phone. Coolio's Gansta Paradise.

Eq Type = Rock

No Room Effect

Volume Level - +14 (Distorts @ 15 and cuts out @ 16 & Above)

No Base enhance

No Equlaizer. (Move those sliders over too much and she cuts out)

---------- Post added at 05:29 PM ---------- Previous post was at 05:26 PM ----------

I would think the equalizer would apply to headsets. The little speaker on the GN is hardly something to fine tune eh?
[Samsung Galaxy Nexus] aergern:
OK. Maybe I'm just stupid ... or too old because you know .. over 40 your brain just goes but all the sounds, music and whatnot are really loud and I like this BUT one of the things I thought that Volume+ would do is make all sounds louder. I would REALLY like the lock sounds to be as loud as say .. an SMS notification but even with Volume+ they are not ... so light I can barely hear them. Is there a setting for this I am missing? Or is it just the volume the lock sounds are recorded at?
[Samsung Galaxy Nexus] :
Anybody else having problems with the EQ Settings for the speaker? I can't change it to Good Quality - keeps changing to treble boost instead.
[Samsung Galaxy Nexus] zephiK:
Yeah I'm having the same problem. It's a beta, can't wait for the finished product.