Search results

this not only fixed the missing auto rotate (which really pi**ed me off) but also the missing temperature and humidity sensor. thanks

TBCH, I'm not sure about the BC1. The recovery is not part of the blob (anymore?). And the exact way an official update flashes it is probably not the best way to go when flashing manually. My advice for the moment probably is: Keep flashing the bootloader to a minimum, and flash recoveries via...

Thanks a lot. Yes root gets wiped on upgrade. I'm not yet up and running 2014, so no real progress so far. But i'm still on it.

Thanks! I believe it's doable. I must admit PCB rework is nothing new to me, and I'm not bad at it, but BGAs never were my favorite. However, even being a 100+ ball package, only a hand full of them need to be soldered for it to work, so using some magical ZephPaste (this stuff rocks) chances...

status I believe I have found a bug in the bootloader, in the staging part. So I have a bricked TF701 here, what lead to me buing a second one. On the first one I desoldered the eMMC, and right now I'm waiting for the test adapter to turn up, so I can verify the bug. Then I'll reflash and...

moar pictures I made a whole series of pictures today, which will be added very soon. there are a lot of awesome close-ups.

fixed: adapted to the new root_shield.img

my findings I completed 3 tests today: scalpel on the tf101: I couldn't get a scratch.scalpel on the galaxy nexus (that had a sh*tload of scratches already): I couldn't scratch itscalpel on the tf701: I couldn't scratch itConclusion: I cannot tell if or which gorilla glass it is, but on the WW...

Will post exact details this evening. also more and detailed pictures for the teardown will follow. I have one bricked and one working device. I'm actually up to more useful stuff than just taking pictures, but that's sort of ot.

it is glass. maybe gorilla glass, but at least it's scratch resistant.

done

From the tegra 4 TRM This is from the Technical Reference Manual at tegrazone. To get this 2663 page document, you need to register. This has been typed by hand, as copy is disabled. 25.1.1 Output Capabilities - 1 or 2 captive panels on two 4-lane DSI channels, operating either independently...

I believe this is a fault of engineering to begin with, and there will be no easy fix...

you missed the part about unpacking it once. reboot is generally futile. Android should see the file anyway. EDIT: wtf I missed the part about "extracted it". sry.

As all we seem to have at the moment is some words about 2013.11 being first fixed batches, but I say "pics or it didn't happen". So for the time being, let's have a look at what the situation in general is. Some things I noticed: I have yet to see the docking being sold seperately, as it was...

You might want to get this fixed, as batterystats.bin is nothing to do with calibration. Source: Dianne Hackborn http://www.xda-developers.com/android/google-engineer-debunks-myth-wiping-battery-stats-does-not-improve-battery-life/ Cheers

lol

go for it, it's sinking... cheers

Here's a teardown of the TF701. Basically it's dead simple. Remove 2 tiny screws. One in each slot for docking.Pry apart plastic front and aluminium back shell. The only thing holding these together are plastic clips around the edge. And black magic. Disconnect two cables from screen. The size...

I'm pretty sure the resolution hack can be improved, but it's all I needed for now... anybody write an app for that?

Here's how bad mine tilts.

well on the bright side, if I need to return the entire thing (they granted warranty, even if unlocked) I might end up with another locked bootloader and as for such another attempt in rooting without unlocking... but that's a SWAG...

because they confused it with the italian user manual ^^

@ AngryDinosaur: so you're still having trouble?

Hi all! yes, this is still beta, I might go back and re-call it experimental. right now we have mount point and property problems. wiping will be something to do with bad mount points. I'm working on it, but any suggestions, error logs or whatever you brave guys can offer is of great value.

yeah, the keymapping crap... I found tons of "unpack this apk, edit soandso..." but I wanted to have it changed on a lower level. the remapping should work on most if not all transformers, and be easily portable to anything that has a hardware keyboard...

Backlight is fixed

backlight fix: please hand me the eye-bleach Original: static int dsi_s_wqxga_10_1_bl_notify(struct device *unused, int brightness) { int cur_sd_brightness = atomic_read(&sd_brightness); /* SD brightness is a percentage */ brightness = (brightness * cur_sd_brightness) / 255; /* Apply any...

Great. I have tried to write this silly value into brightness, but I failed hard. What I've done to make this recovery: get cm-11.0, downloaded the recent kernel sources from this other thread, edited the configs, avoided errors. If anybody cares to talk me through uploading this whole mess to...

exactly^^ the "hold on, the screen's black, let's grab a flashlight..." has been in my mental toolbox for years...

Also, if you can tell me how to get the darned backlight working by default, go on, tell me!

Disclaimer: Not knowing what you're doing is a serious brick risk! Don't dare saying you haven't been warned! Status: beta experimental Requirements: v7 Bootloader Working: Backup, Recovery (?) Bugs/Not working: Wipe, trouble with mount points Comment: The backlight fix is an ugly hack at...

I'd say it's a bad script, because they didn't think of connecting two msds.

test setup: 1 x powered USB 2.0 hub 1 x WD My Passport 2TB 1 x Codemeter license stick 1 x Logitech T650 touchpad description: all but the codemeter stick are connected to the hub, which is connected to the TF701. Then each device including the dock touchpad is tested. Then the codemeter stick...

things that will appear here tomorrow: by name symlinks recovery fstab info unpacked blob contents more detailed bootloader related stuff anything fun I'll find on the way for the next 12 hours that's it...

Yeah. that... All I read about "bad NAND" is more or less centered around one or two "reviews". I have yet to see any proof for anything. The TF701 is a high tech piece of kit, and the hardware is beautiful(not talking about the design, but that's not bad either). There's nothing I could...

Dude, WTF? cool down Also, instead of writing of "other post's" and "NAND problems", share some links!

Hi there! Is it correct to use a cm-11.0 branch and add your projects from git to the roomservice.xml? That's what I tried, but I believe there's something wrong. Also, adding a micro sd card seems to not work. It doesn't mount correctly. I tested exFAT and ext3. Anyone who got this to work...

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

Disclaimer: I try my best to produce valid answers, but if you have no idea what you're doing, don't do it. Terms and Definitions NVflash / APX mode This is the lowest level of software that can talk to an Nvidia Tegra device. Basically this is the Holy Grail of memory modification, which can...

well it's "wait until someone leaks a newer nvflash", or "try sending it back". but I'm pretty sure they're going to charge you a fair amount of cash to fix it, as you voided the warranty (the unlocker app calls home, that's a fact). But I might be wrong. If I were you, I'd wait for a fix. But...

if that's what you did, I can't help you.

so you had root and a running V10.26.1.7 and did this? WARNING: DO NOT FOLLOW THESE STEPS! fastboot flash boot boot.img (of the 10_14_1_47) fastboot flash system blob (of the 10_14_1_47) fastboot flash system WW_epaduser_10_14_1_47_UpdateLauncher.zip fastboot reboot If you did, you bricked it...

what firmware version was it when you rooted? was it WW 47?

so you can't enter the bootloader selection screen? what does your pc detect when connecting it?

flash drgravy's recovery.img, the v47 blob, start recovery, sideload update 47 zip (this works without errors)

That page is fishy. At the place you'd look for the ww v7 update, you'll find the italian user manual. I reported this to ASUS, and they confirmed the error. Last week.

oh alright... well i have unpacked the blob, there's a thread about that already. If only size matters, you can edit the blob contents and repack...

I have found the location of that string, but I hesitate changing it, because a) this will not fix your warranty and b) I have no reliable info if the EBT has a checksum.

I totally missed this thread, sorry. But as you're up and running now, I guess that's ok...