yashsingh1/xdaforums huggingface dataset:
[Transformer TF300T Android Development] rayman:
it's easily possible to write boot and recovery. They are not encrypted in any way.

However, they are cryptographically signed, which means the device will fail to boot if you overwrite them. (We did test this ;))
[Transformer TF300T Android Development] afazel:
/boot is signed as well?

What about kexec? Would that be a viable option for those of us who want to use a custom ROM, but not void our warranty by using the ASUS method?
[Transformer TF300T Android Development] chenxiaolong:
That depends on whether or not CONFIG_KEXEC is enabled in the stock kernel. If so, that would make it very easy to do: https://wiki.archlinux.org/index.php/Kexec. The initramfs could be modified to load the filesystem/ROM from SD card/network/USB/etc. The Arch wiki has plenty of examples doing this :)
[Transformer TF300T Android Development] afazel:
Obviously we aren't going to crack the RSA encrypted key the boot loader is signed with, but what if we looked at it from a different angle? What if we were able to trick the tablet into booting even if the images in /recovery and /boot aren't signed with the encrypted key? Bypass the signature check.

How did the REVOlutionary guys crack the Evo 3D and the OG Evo to get them S-OFF? Obviously that boot loader wasn't signed with an encrypted key, but I believe they flashed something to the baseband that caused the signature check to be bypassed during boot.

Need someone smarter than I to fill in the holes, but at 3:45am it sounds like the right path.
[Transformer TF300T Android Development] adamo3957:
Why not take a look over in the defy forums about 2nd init, we pushed as far as we can in the last couple of years and we can run custom roms, and a recovery (we even have multiboot) however we can't get access to change recovery
[Transformer TF300T Android Development] afazel:
I remember when the OG Evo first came out we were running recovery from SD card
[Transformer TF300T Android Development] surferpr:
Don't let the thread die :( This means a lot to the people stuck with the stupid network error on the unlock app
[Transformer TF300T Android Development] peterperfect:
I think theres nothing that could be done anymore..at least for now...
[Transformer TF300T Android Development] EndlessDissent:
If you're referring to the workaround used on Motorola phones, I guess it could happen, so yeah, this thread should stay open. If you're talking about the method that involves cracking the encrypted bootloader, you can forget it unless you have a top-of-the-line supercomputer handy. I looked into RSA-2048 encryption. Turns out, it would take more than a quadrillion years for a modern top-of-the-line desktop system to crack that encryption. Yes, quadrillion. No joke. Ask Google.

So, unless you're interested in the Motorola method or you're very good at factoring prime numbers, this thread doesn't need to live. It was a good run, though. I applaud all the parties involved in the attempt, and I was hopeful for a while there that you guys would be able to do it.
[Transformer TF300T Android Development] mikaole:
even if you could relock. What does it matter. On unlocking the tool send your Serial to Asus, so they know that you were unloked anyway.
[Transformer TF300T Android Development] EndlessDissent:
This thread's not about relocking the bootloader. It's about unlocking the bootloader without the Asus app, to avoid sending the serial number in the first place, which would then make relocking the bootloader a possibility.
[Transformer TF300T Android Development] peterperfect:
In fact I'm not even worried about relocking. I just wanna unlock. :(
[Transformer TF300T Android Development] surferpr:
Yes I know we can't crack RSA. What I mean is this thread is the closest one we have to an effort to unlock the bootloader without the app. Since so many people (me included) cant use the app because of the serial number/network error bug. I have been looking for one for quite a while but honestly this goes way over my head.
[Transformer TF300T Android Development] Rawahi:
Hello,

Just after discussing with the Asus vip site about our problem, here is the result:

Hello,

referring to case **************** , Just to inform you that I've done what

you suggested, the problem still persist (used the UnLock_Device_App_V7.apk,

installed it and done all the methods).

I've searched the form about the matter, it appears that I'm not alone in this case

following these models (C3OKCT and C4OKCT) on this thread on your site:

http://vip.asus.com/forum/view.aspx?

id=20120526021230787&board_id=12&model=PadFone&page=1&SLanguage=en-

us

Could this be a database issue when we try to unlock our devices? My Device model

range is: C6OKCT******

Should we wait until the unlocking software works on our models? because i believe

it's a connection to database issue or the model serials are not updated.

Thank you.

A reply from them came after days:

Dear valued customer

Thank you for contacting ASUS Technical Service

Now we are try our best to, and at this time we are unable to set a date for its release. Please stay tuned for more news on it.

If you need, you can try to contact our local service center for help.

The following is the contact information:

http://support.asus.com/hotlines.aspx?SLanguage=en

Have a nice day!

For more information feel free to refer to our self-help pages by clicking

the links below:

Troubleshooting -

http://support.asus.com/troubleshooting/troubleshooting.aspx?SLanguage=en-us

FAQ - http://support.asus.com/faq/faq.aspx?SLanguage=en-us

Live Support - http://livesupport.asus.com

Best Regards

Myra Xu

ASUS Service Center

It means they are working on a new version of the unlocker.

Hope they done it on time :X

---------- Post added at 03:48 PM ---------- Previous post was at 03:45 PM ----------

As long as rooting and unrooting is easy with locked bootloader, all you need is to wait for Asus to release their new unlocker.
[Transformer TF300T Android Development] beepea206:
Sorry, I'm a bit late to the convo... Which model does that affect? If we try to unlock and it fails, do we get and reoccurring error or anything adverse? I thought I saw someone mention issues after a failed unlock.
[Transformer TF300T Android Development] peterperfect:
Affects some range of serials of the TF300T. The provided tool doesnt even starts the unlock process due to a network error. No side effects.
[Transformer TF300T Android Development] didda:
I can verify SN# CCAH12**** will not unlock. No adverse effects otherwise.
[Transformer TF300T Android Development] beepea206:
Grrr... Unlock check failed. What's odd is I can take ota, but I thought that was a way to see if the unlock would fail?
[Transformer TF300T Android Development] sad96:
Have you tried this: http://xdaforums.com/showthread.php?t=1669328?
[Transformer TF300T Android Development] beepea206:
Downgrade to 17 and unlock, eh? Hadn't thought of that.... I'm on 30, so it's worth a try. I'll report back with results.
[Transformer TF300T Android Development] Rawahi:
:crying:

I tried this method, but still no OTA update and ERROR can't connect to server when unlocking, my serial series is C6OKCT******

I really want to backup OS easily with CWM, without recovery it's PAIN when reseting defaults and recovering from TB....

this is really master piece model, but why the heck is all that lateness from ASUS to update their unlocker?....
[Transformer TF300T Android Development] surferpr:
I'll tell you why. Asus has the absolute worst customer support I have seen in a company (btw used to be an AT&T subscriber so ya, even worse) I have an outstanding issue with them and I have opened several support tickets. The last one a customer rep told me he was going to send me an RMA # but he hasn't. That was two weeks ago, I have contacted them several more times but now they wont even reply. It would not surprise me at all if they never fix this issue seeing as they already have our $.
[Transformer TF300T Android Development] beepea206:
I did the downgrade method and it *think* it worked. I flashed twrp and it didn't hang up at the 'failed' message, so I assume it all worked. This tablet is new to me, so I'm still trying to figure out how to reboot into recovery from stock... Rom Toolbox isn't doing it, like it does with cwm.
[Transformer TF300T Android Development] Buster99:
if you are unlocked you will see it in the top left corner when you boot - there is a message that tells you you are unlocked at every boot - as for getting into recovery etc - use "quickboot" from the market - best tool there and its free (but consider getting the payd version)

cheers
[Transformer TF300T Android Development] beepea206:
Yeah it looks like it didn't take or I did something, because I did it again and I see the unlocked message now.
[Transformer TF300T Android Development] dsp4774:
I don't think we can reboot to recovery. We can reboot, and hold the vol-down button until the message appears and then press the vol-up button, but I haven't seen an app (quickboot included) that can get us to our recovery directory.
[Transformer TF300T Android Development] kindrudekid:
budddy same here i feels ya bro
[Transformer TF300T Android Development] kindrudekid:
I hope this gets attention and they fix it for us
[Transformer TF300T Android Development] surferpr:
I wouldn't count on it. The moment it started getting attention Asus deleted the comments supporting your comment mine included. Thing is I wasn't harsh or anything. I just stated the obvious. They just don't care.
[Transformer TF300T Android Development] kindrudekid:
ahhhh those assholes...

yeah all big company tend to do this....

we should probably make a video and send it to all major android websites, BAD PR is a nightmare for Asus
[Transformer TF300T Android Development] beepea206:
Downgrading to 17 worked for me for unlocking.
[Transformer TF300T Android Development] kindrudekid:
do u know where can i find the .17 zip to downgrade?

m free this week till college starts, might as well go balls deep and see if this will work!
[Transformer TF300T Android Development] surferpr:
Guys something Awesome just happened. I followed this guy's tutorial http://xdaforums.com/showthread.php?t=1840825 To update to JB kept root and everything intact. Thing is the unlocker worked for me this time. I had done everything to get it working and nothing helped. Update to .30 downgrade to .17 and all. but for some reason it worked now. I was one of the ppl affected by the serial bug (C30KCT) so no OTA or Device Tracker. Check it out see what happens.
[Transformer TF300T Android Development] peterperfect:
Gentleman, im proud to say that asus fixed the serial issue. Just try to unlock now. Just go and try. No need of upgrading or downgrading.
[Transformer TF300T Android Development] kindrudekid:
OMG Fcuking Awesome!!!!

yes it asked me if i want to unlock!!

PS: will i still be able to get JB update after unlocking ?

from the zip that pops up on Asus Page!??/
[Transformer TF300T Android Development] peterperfect:
Hahaha! Im so happy to! Lets go

Yes you can have JB....Asus official or better: you can have CM10 on it!
[Transformer TF300T Android Development] das7771:
Still not working for me. Maybe they are slowly fixing the serial numbers in groups. At least I can hope
[Transformer TF300T Android Development] peterperfect:
Whats tour serial range?
[Transformer TF300T Android Development] das7771:
C30KCT
[Transformer TF300T Android Development] prototype7:
C4OKCT here, still no luck. Will try upgrading to JB.
[Transformer TF300T Android Development] DarkSorcerer:
Hi,

So, basically, what has been said in this thread is:

1 - you can't unlock bootloader unless you use ASUS's own tool

2 - you can't "fool" the tool

So, no hope to unlock bootloader without them knowing. Am I correct?

Regards,
[Transformer TF300T Android Development] Reilly1812:
IMHO - you are correct.

Still Charged Up
[Transformer TF300T Android Development] DarkSorcerer:
Hi,

That can be a deal breaker for me, as I'm /was thinking of buying TF300TL here in Portugal.

Thank you
[Transformer TF300T Android Development] ostar2:
Deobfsucated sources decompiled with fern flower

Hi, I thought I would add on to this by posting fully deobfuscated version of the source. I have decompiled and fully deobfsucated the code. It has been decompiled with fern flower meaning that it is not byte code, but fully readable java code.I hope this helps both "OP" and the community. :) :)
[Transformer TF300T Android Development] purist:
Would it be possible to recompile this to recompile without the 'call home' function? Whenever I try to unlock I get a 'network error, try later' message. It seems a few others are starting to have problems with this as well.

Thanks.
[Transformer TF300T Android Development] funnel71:
It would most likely depend on a specific response to work. Asus isn't dumb :) :)
[Transformer TF300T Android Development] untermensch:
no you cannot recompile this, it is not de-obfuscated if you look through the code all the good stuff did not decompile and is replaced

with "could not decompile" comment. IIRC it works be sending the device CPU serial number to Asus and Asus signs it and sends it

back it is then written to a partition on the device and when the device reboots the bootloader finds the signed CPU serial number and

verifies it and then unlocks the device. If it doesn't call home then it doesn't work.
[Transformer TF300T Android Development] harpik3d:
I want to share what I've learned examining the padfone 2 unlock tool (which seems to use the same process to unlock)

- the unlock process itself seems to be made during the boot process

- the unlock is called when the raw text "boot-unlock" is written to the first few bytes of mmcblk0p3 partition, the string "recovery\lf" (\lf is the line feed character) is also written starting at byte 64, and another set of data (which may be the processor ID signed by Asus) is written to mmcblk0p4.

- in the init.rc (from my padfone) there is a comment:

#+++ ASUS_BSP : add for unlock function

chown root system /dev/block/mmcblk0p13

chmod 660 /dev/block/mmcblk0p13

#--- ASUS_BSP : add for unlock function

and looking to /dev/block/platform/msm_sdcc.1/by-name it looks juicy:

lrwxrwxrwx root root 1970-01-15 17:19 asuskey -> /dev/block/mmcblk0p13

so it could be possible to change the mmcblk0p13 partition and fake an asus code to unlock the device

what do you think?
[Transformer TF300T Android Development] tjy8tim:
bump. any progress?
[Transformer TF300T Android Development] jammysunny:
Hi @All

does an unlock do a hardreset/ factory reset?
[Transformer TF300T Android Development] funnel71:
No
[Transformer TF300T Android Development] nuno407:
realy interesting!

I'd like to help but I have no knowledge for that :/
[Transformer TF300T Android Development] crunchthem:
Did you read the posts before? :D the serial is rsa encrypted. So there's no way to decrypt it.
[Transformer TF300T Android Development] UtCollector@gmail.com:
Sow any progres unlocking Asus bootloader..?
[Transformer TF300T Android Development] cmendonc2:
Haha major necro.

Thanks to some well placed encryption, Asus's secrets with their bootloader remain safe unfortunately.
[Transformer TF300T Android Development] UtCollector@gmail.com:
Well maybe a Snowden guy will leak it sometime.

I did try this commands:

fastboot oem unlock61646 Works but does not fully unlock the device.

fastboot oem unlockD696E Not working. Telling: remote: oem admmunlock not requested

fastboot oem unlock Works but does not fully unlock the device.

When i do fastboot oem device-info

Its tells the boadloader is still locked.

Do you know any other commands?
[Transformer TF300T Android Development] das chaos:
Boy, you revived a thread from the stoneages. Inn the meantime unlocking the bootloader is a two-click effort. Why bothering with reingeneering?
[Transformer TF300T Android Development] UtCollector@gmail.com:
Stonages:o Well its just time past. Tell me how its a 2 click effort..? Maybe for the FT300 I need a Asus Memo pad 10 -me102a bootloader. I hoped a expert here would have a sugestion how to unlock it.:D
[Transformer TF300T Android Development] t3chwizard:
If you can accomplish this, would it be possible to generate a generic NVflash blob that we could use to flash a bricked tf300t back to a usable state or flashing it some other way? My tablet boots up and shows the logo but will not let me enter recovery or fastboot or anything. It just boot loops. It can enter APX mode. If you can figure out how to allow us to flash back to usable state in APX mode using a generic blob many people would be very grateful.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] roltzje:
Please delete. Fixed this
[Sony Ericsson Xperia Neo, Pro] mpiekp:
Just found this build ;-)

Thanks on the original thread here

http://xdaforums.com/showthread.php?p=22969714

Tested and fully working on gb, there is an ICS build there too
[Verizon Droid Charge] xdadevnube:
I currently have my Charge set up as a WiFi only device for the time-being.

I am on Tweaked 2.0 with PBJ kernel.

I noticed that cell-standby is consuming a sizable chunk battery.

I have CDMA set in network selection. I have data toggled off as well.

I'm trying to devise a way to disable cellular connectivity completely. In TSM parts I can set HDR1X selection to the following options:

Hybrid Mode

CDMA Only Mode

EVDO Only Mode

EHRPD 1X Mode

EHRPD Only Mode

There is also Rev A mode that forces EVDO to use Rev 0 or Rev A when on EVDO, which I don't think is going to help me.

For now, I just set System Selection in Network Options to CDMA, toggled off Data, and set HDR1X Selection to EVDO Only Mode. I guess we'll see how it goes. When I didn't need the phone line and still had service a while ago, I just set the thing to EVDO Only mode since I don't have 4G yet. In this way I couldn't make calls, and my data connection seemed more reliable since it wasn't using (I think) eHRPD to authenticate to the network, which seemed buggy at the time. Data seemed to drop less.
[Verizon Droid Charge] xdadevnube:
Hm, I didn't realize you could toggle on GPS, WiFi, and BT with airplane mode still enabled.

I'll give that a shot.

*EDIT* Oops, forgot to edit the OP, not make another post...
[Verizon Droid Charge] JihadSquad:
You can also remove the sim card.

Sent from my handheld Linux computer using electromagnetic radiation.
[Verizon Droid Charge] xdadevnube:
I don't want to try it, but I assume 911 calls work with the SIM card removed as well as when the phone is in airplane mode?
[Verizon Droid Charge] imnuts:
911 should work with the SIM removed, but not when in airplane mode. You'll have to come out of airplane mode to make any calls.
[Verizon Droid Charge] BleedsOrangeandBlue:
Take a look at this

http://rootzwiki.com/topic/25016-modany-phone-any-rom-wi-fi-only-mode-disable-cell-radio/
[Verizon Droid Charge] xdadevnube:
That's nifty, but I decided to just use airplane mode all the time. Wifi, GPS, and Bluetooth still work fine and I think they all keep their settings after a reboot. Battery life is now rather good.

I would probably use the method in your link, but I like the ability to just pop in my SIM card if I get in a bind without worrying about the lost functionality of the removed system apps.
[Galaxy S II Q&A, Help & Troubleshooting] wanewon:
I have two galaxy s2s. one is i9100 and the other one is i777 on at&t.

SoD happened once on each phone. The i777 was running stock gingerbread and the i9100 was running resurrection remix 1.9.1 with the siyan kernal I believe.

The screen just wouldn't turn on so I just pulled the battery out (is it safe for the phone?)

This doesn't happen often,well just once each on each phone as stated before, but it does bug me as it makes me think there's something wrong with my phones, and pulling the battery out doesn't seem like it's good for the phone.

I searched around the forum a bit and saw other people are having this issue as well. And not just the galaxy s2, but other phones too.
[Galaxy S II Q&A, Help & Troubleshooting] atifsh:
only sleep of death in almost 10 months of use is when i tried xwlp9.

so no its not common
[Galaxy S II Q&A, Help & Troubleshooting] shazui:
It's fairly common yes, a lot of people running non-stock ROMs get this. I had this ~25 times on numerous Resurrection Remix ROMs, but since v1.9 I haven't had this issue fortunately. If it's causing you a big problem, try fixing permissions from CWM recovery, that seemed to make a big difference when I was having the problem.
[Galaxy S II Q&A, Help & Troubleshooting] UpInTheAir:
SOD usually occurs when the kernel UV the CPU or GPU a little to much. Not every device is the same and not handle same kernels, UV values etc
[Galaxy S II Q&A, Help & Troubleshooting] wanewon:
From the sound of it, it seems to be a software problem.

I got it on the i777 which wasn't running a custom rom. But I think it could be caused by that battery management app that I installed.

anyway, my main concern is that if there's anything wrong physically with the hardware. ( having the SoD caused by software problem is much easier to swallow as to it being caused by hardware problem, as I can just reflash the kernal, roms, factory reset, etc. )

and did removing the battery while in SoD mode damage the phone?
[Galaxy S II Q&A, Help & Troubleshooting] MistahBungle:
It's normally a firmware issue, or a conflict between an app & the firmware. You'd find it's pretty rare for an 'untouched' (I.E not modded) phone running stock firmware to have SOD's. And obviously if you're flashing custom firmware that's constantly evolving/changing, then sometimes you're going to get SOD's, tho with most well crafted firmware these are fairly rare.

I reckon I've probably had <10 in the 8 mths I've had my phone & I've been running non-stock firmware the whole time save for the week I got my phone, which is nothing when stacked up against all the mucking around I've with my phone.

Edit to add - One way you can test to see if SOD's you're having are possibly hardware related is to do a completely clean install of stock firmware & see if they still happen. If they don't, then it's obviously whatever firmware you were running. If they do, then it might be hardware-related. Re: your question about pulling the battery after a SOD, normally this shouldn't cause you any problems (it's sometimes the only way you can successfully reboot the phone).
[Galaxy S II Q&A, Help & Troubleshooting] victorator:
The only known SOD issues on I9100 are the old 2.3.3 (don't remember which one) and the XWLP9 kernel.

Custom roms... well. No need to elaborate I guess.

Most of them have undervolted settings as default.
[Galaxy S II Q&A, Help & Troubleshooting] Ray_Grey:
Im pretty sure i rooted my phone on the we with LP9 kernel. Since Sunday, I've had about 10 sods and never had one before... no doubt here as to what's causing it. I plan to change the kernel on the we and hopefully no more sod.
[Galaxy S II Q&A, Help & Troubleshooting] victorator:
Or just flash the newer build. No SOD there.
[Galaxy S II Q&A, Help & Troubleshooting] wanewon:
How about this?
[Galaxy S II Q&A, Help & Troubleshooting] MistahBungle:
I answered your question. Read the edit I made to my post.
[Galaxy S II Q&A, Help & Troubleshooting] wanewon:
Thank you for the answer.

Since it's kinda hard to recreate the SOD. I'll reflash the rom and kernal and do a wipe and see if the SOD still happen
[Galaxy S II Q&A, Help & Troubleshooting] Ray_Grey:
Victorator, forgive my ignorance, but are you saying i should just flash the latest build, XWLPD, onto my fone rather than re-rooting it using a different kernel (i.e. CF-Root-SGS2_DX_SIN_LP9-v5.4-CWM5.zip) in order to stop the SOD?
[Galaxy S II Q&A, Help & Troubleshooting] tariq2kn:
Never faced such issues ever.