Unlocking and rooting

[zonyl]

Is anyone aware of any exploit for temp root on Android 4.2.3? I'm waiting as well to get debian on this ASAP.

Sent from my K00C using Tapatalk

 

[HaPe000]

It will be hard to root this device without unlocking bootloader.

 

[KGarloff]

Cydia Fails

Is anyone aware of any exploit for temp root on Android 4.2.3? I'm waiting as well to get debian on this ASAP.

Cydia Impactor fails -- both signature verification bugs are fixed (which SRT AppScanner also confirms).

 

[gregpilot]

So I would say: Think twice before unlocking the bootloader on the TF701, when custom-recovery even comes out for it.
Personally, with my TF701 that I ordered on newgg today, I am going to leave the bootloader locked for awhile. I can live with the stock ROM, hopefully with root access. Maybe after a few months I'll unlock the bootloader. It would be nice to do it in a way that didn't void the warranty.

Has anyone decompiled the unlock .apk and tried substituting blank or other characters for the "Device is unlocked" which gets displayed on bootup? Then run the utility? Or is there some kind of check which is run to determine if the unlock utility has been tampered with?

Then the tf701 would not display any obvious signs that it was unlocked, it would appear, at first glance, to be locked. If you re-loaded a stock ROM I doubt asus would know it was unlocked if you sent it in for warranty. I agree unlocking has nothing to do with hardware issues, that's pretty poor serivce. But I suppose asus can adopt whatever policy they want for warranty service. The people here modding their devices are probably insignificant in number for asus to make any changes to their policy.

 

[lpdunwell]

we have root on 47

hi guys,
this is what i have done, and what worked for me:

- installed the ww update
- do this --> http://forum.xda-developers.com/nvidia-shield#root
- watch closely, there will not be penguins, but smeared graphics. at that point wait a minute or two
- hard reset transformer
- profit

- no warranty, i did it, you may try too

good luck,
luke

 

[lpdunwell]

details

I figured out the shield and the tf701 are similar enough to be able to use the same minimal dtb. We have ways to unlock it, so i tried and succeeded.

 

[gregpilot]

- installed the ww update
- do this --> http://forum.xda-developers.com/nvidia-shield#root
- watch closely, there will not be penguins, but smeared graphics. at that point wait a minute or two
- hard reset transformer
- profit


luke

Did you have the ww sku or us sku or ? before you installed the ww update to .47? Did your tablet boot normally if you cross-flashed?

Before you ran "fastboot oem" unlock" was your bootloader stock (locked)? Or had you ran Asus unlock tool?

I am asking because I was under the impression you can't run "fastboot oem unlock" on a locked b/l?

Thanks and nice job!

 

[lpdunwell]

Did you have the ww sku or us sku or ? before you installed the ww update to .47? Did your tablet boot normally if you cross-flashed?

Before you ran "fastboot oem" unlock" was your bootloader stock (locked)? Or had you ran Asus unlock tool?

I am asking because I was under the impression you can't run "fastboot oem unlock" on a locked b/l?

Thanks and nice job!

it was the ww sku, as i bought mine in switzerland. i don't see why this would not work on the us, if adapted.
complete process (the first two steps can be swapped, that's what i did anyway):

- update with correct sku zip file
- use asus unlocker (my transformer made some extra reboots there, but it worked)
- fastboot oem unlock
- proceed with nvidia shield root instructions
- when graphics blur, wait 2 mins to be on the safe side
- hard reset
- it will tell you it's optimising apps on the next boot
- check root

i just debloated my tf701 using titanium backup (yeah i know, backup normally comes first). i also prepared a build environment for cyanogenmod today, so i'm going to have a look at compiling a recovery.

written on my rooted tf701, yeah

 

[Tiger62651]

it was the ww sku, as i bought mine in switzerland. i don't see why this would not work on the us, if adapted.
complete process (the first two steps can be swapped, that's what i did anyway):

- update with correct sku zip file
- use asus unlocker (my transformer made some extra reboots there, but it worked)
- fastboot oem unlock
- proceed with nvidia shield root instructions
- when graphics blur, wait 2 mins to be on the safe side
- hard reset
- it will tell you it's optimising apps on the next boot
- check root

i just debloated my tf701 using titanium backup (yeah i know, backup normally comes first). i also prepared a build environment for cyanogenmod today, so i'm going to have a look at compiling a recovery.

written on my rooted tf701, yeah

well i can confirm you cant install ww on us sku table. so our problem still stands cant unlock bootloader since asus has screwed up on their servers. i waiting for reply from them to fix my ids in their database.

 

[Alta1r]

well i can confirm you cant install ww on us sku table. so our problem still stands cant unlock bootloader since asus has screwed up on their servers. i waiting for reply from them to fix my ids in their database.

Make sur your battery is over 90% when tying to unlock. I unlocked this evening and it wouldn't unlock either with the battery at 65% (eventhough battery was charging). Tried again with battery at 97% and worked like a charm.

Going to try to root it tomorrow.

Sent from my GT-N7100 using XDA Premium 4 mobile app

 

[Tiger62651]

Make sur your battery is over 90% when tying to unlock. I unlocked this evening and it wouldn't unlock either with the battery at 65% (eventhough battery was charging). Tried again with battery at 97% and worked like a charm.

Going to try to root it tomorrow.

Sent from my GT-N7100 using XDA Premium 4 mobile app

i try first thing in morning with battery 100% and throughout the day and no luck. waiting to hear back from asus tw.

 

[menollo]

Root

Thanks Ipdunwell, i managed to root my devices with the SHIELD method.

The unlock part wasn't working in the beginning, but suddenly it was (so most probably when the battery was full after a while).

After unlocking (from the .47 release), boot device to fastboot (hold volume down during power on).
And execute this line with the files from here https://github.com/linux-shield/shield-root:

fastboot boot zImage_dtb ramfs.img.gz

after a while with the graphical mesh, press the power button once (don't need a hard reset).
Now, the device is booting with the su app installed

 

[Tiger62651]

Well decided to do dramatic thing and reset my tablet and still no luck. even used my other account I have for my kids and still no go. Both tablets I have are 98-100% battery and both doesn't work. One has update 45(this is one I tried the WW and it didn't work) and other update 47. Now after lots of research today I came across a post in the TF700 forum. Explains this:
http://forum.xda-developers.com/showpost.php?p=29886680&postcount=44

Funny though it says in order for the unlock tool to work you have to be able to get the OTA updates and my 45 tablet still says up to date so there is something wrong on Asus side of the devices since 47 is out.

 

[lpdunwell]

Well decided to do dramatic thing and reset my tablet and still no luck. even used my other account I have for my kids and still no go. Both tablets I have are 98-100% battery and both doesn't work. One has update 45(this is one I tried the WW and it didn't work) and other update 47. Now after lots of research today I came across a post in the TF700 forum. Explains this:
http://forum.xda-developers.com/showpost.php?p=29886680&postcount=44

Funny though it says in order for the unlock tool to work you have to be able to get the OTA updates and my 45 tablet still says up to date so there is something wrong on Asus side of the devices since 47 is out.

@Tiger62651: can you provide some extra detail how it doesn't work? error messages, screenshots...
@gregpilot: i guess the unlocked message might just as well be somewhere else, and only gets enabled by the unlocker. i'm going to have a look at this...

seems slightly weird...
i had trouble with the ota, anyway. it simply didn't work. even after resetting the two apps somehow linked to ota (there's a post in a master guide somewhere here)
what worked for me, was to first unlock, then manual update.
the zip you get for manual update is close to 1GB, and it needs to be unpacked once, and then saved to the root of a real micro sd card.
plug it into a running tablet will show a message, plug it in and then boot should work, too.

however, asus chewed up their servers globally in the last couple of hours. i cannot find the required files anymore.
this is only an elevated guess, but i'd say you can use my method to root a 45 anyway, but you will probably lose root on later update.

the unlock tool should be the same for all tf701 sku. i don't know for sure if i'm allowed to upload the unlocker here, so try this: http://www.datafilehost.com/d/df096ded

 

[Yezariael]

Thanks Ipdunwell, i managed to root my devices with the SHIELD method.

Great news! :victory:

Could you please make a Thread with exact instructions and working links (you link does not work...) in Dev. Section? I guess would be best, so people can find it and post their experiences

Thanks!

 

[Alta1r]

Great news! :victory:

Could you please make a Thread with exact instructions and working links (you link does not work...) in Dev. Section? I guess would be best, so people can find it and post their experiences

Thanks!

You have to remove the ':' at the end of his link:

https://github.com/linux-shield/shield-root

---------- Post added at 10:23 AM ---------- Previous post was at 10:20 AM ----------

Well decided to do dramatic thing and reset my tablet and still no luck. even used my other account I have for my kids and still no go. Both tablets I have are 98-100% battery and both doesn't work. One has update 45(this is one I tried the WW and it didn't work) and other update 47. Now after lots of research today I came across a post in the TF700 forum. Explains this:
http://forum.xda-developers.com/showpost.php?p=29886680&postcount=44

Funny though it says in order for the unlock tool to work you have to be able to get the OTA updates and my 45 tablet still says up to date so there is something wrong on Asus side of the devices since 47 is out.

What worked for me to .47 update OTA before was to first clear data and force close CMClient and DMClient found under Settings/Apps/All.
First my tablet wouldn't find an update, after doing this it was able to find the update.

 

[lpdunwell]

http://forum.xda-developers.com/showthread.php?t=2516215

 

[Tiger62651]

@Tiger62651: can you provide some extra detail how it doesn't work? error messages, screenshots...

@gregpilot: i guess the unlocked message might just as well be somewhere else, and only gets enabled by the unlocker. i'm going to have a look at this...

seems slightly weird...
i had trouble with the ota, anyway. it simply didn't work. even after resetting the two apps somehow linked to ota (there's a post in a master guide somewhere here)
what worked for me, was to first unlock, then manual update.
the zip you get for manual update is close to 1GB, and it needs to be unpacked once, and then saved to the root of a real micro sd card.
plug it into a running tablet will show a message, plug it in and then boot should work, too.

however, asus chewed up their servers globally in the last couple of hours. i cannot find the required files anymore.
this is only an elevated guess, but i'd say you can use my method to root a 45 anyway, but you will probably lose root on later update.

the unlock tool should be the same for all tf701 sku. i don't know for sure if i'm allowed to upload the unlocker here, so try this: http://www.datafilehost.com/d/df096ded

Whats there to provide. Only error message I get is the "unknown error has occurred, may be network problem, try again later" on the unlock tool. As for the OTA it just says my tablet (45) is up to date. Which I know for fact it is not.

You have to remove the ':' at the end of his link:

https://github.com/linux-shield/shield-root

---------- Post added at 10:23 AM ---------- Previous post was at 10:20 AM ----------



What worked for me to .47 update OTA before was to first clear data and force close CMClient and DMClient found under Settings/Apps/All.
First my tablet wouldn't find an update, after doing this it was able to find the update.

Yeah tried this and no luck, still says up to date I am going to try the google services linked to the OTA.

 

[lpdunwell]

Whats there to provide. Only error message I get is the "unknown error has occurred, may be network problem, try again later" on the unlock tool. As for the OTA it just says my tablet (45) is up to date. Which I know for fact it is not.



Yeah tried this and no luck, still says up to date I am going to try the google services linked to the OTA.

Do you use one time passwords/two step auth or anything like this for your google account? this will mess things up for sure.

 

[Alta1r]

Whats there to provide. Only error message I get is the "unknown error has occurred, may be network problem, try again later" on the unlock tool. As for the OTA it just says my tablet (45) is up to date. Which I know for fact it is not.

I had the exact same error last night when trying to unlock the first time. I must have tried about 4-5 times every time with the same message.
After an hour or 2 i tried again and then it worked immediately. Might have been lucky that the servers were working at that time and maybe had nothing to do with the battery...
Don't know if it can help, but the first time i tried it must have been around 8pm GMT, second time it was 10pm GMT.