yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer Q&A, Help & Troubleshooting] DatDude123:
This is the only thing that works for me. I have been through the exact same thing that you have. I had to push blobs of some sort. All due to ROM Manager. I still use ROM Manager on my other three devices though. I never learn.

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

D

---------- Post added at 10:09 PM ---------- Previous post was at 10:07 PM ----------

*** EDIT ***

And I only use ARHD and/or Revolver.

---------- Post added at 10:11 PM ---------- Previous post was at 10:09 PM ----------

*** EDIT ***

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

---------- Post added at 10:12 PM ---------- Previous post was at 10:11 PM ----------

*** EDIT ***

http://xdaforums.com/showthread.php?t=1245892
[Eee Pad Transformer Q&A, Help & Troubleshooting] sidneyk:
Did you try this version that was built for the sl101?

https://dl.dropboxusercontent.com/u/47619656/signed_twrp-2.6.3.9_sl101.zip

It's a flashable zip, and if you're not able to do that, you can unzip it and find the twrp.blob inside. The reports I've gotten back is that it works fine for the sl101 and has touch working as expected. As far as ROMs go, I don't know if there any specific for the sl101, other than stock.
[Eee Pad Transformer Q&A, Help & Troubleshooting] Timberwolfhusky:
Sorry to hear that.. I do not know what could be the source of that "assert" error, but if there is something I did NOT find surfing through the internet, was development on the Slider, therefore if you still have a working stock ROM I'd stick to that one since we have a very unstable array of tools.. As far as I can tell CWM will only mean trouble for the SL101. Since I am not an expert developer do not be discouraged by my advice, but I just warn you that I tried a CWM and TWRP combination that totally killed my tablet ..just so you do not end like me.

As for the slowdown issue, all you can do is pray that TF101 devs put a little effort in releasing a kernel allowing overclocking, as not even that I could find..
[Eee Pad Transformer Q&A, Help & Troubleshooting] Timberwolfhusky:
Flashing recovery blob

Hi [MENTION=4342873]sidneyk[/MENTION]

That twrp.blob looks promising, can you elaborate on how to flash it? Do you need adb? If so, never mind:(
[Eee Pad Transformer Q&A, Help & Troubleshooting] sidneyk:
Well, adb is one method, but I was responding to the person who said they were able to swap a blob with peri or something, so I was assuming that person at least had some method that sorta worked. Without adb or apx mode I don't really know a way. Sorry, if I got your hopes up again. Just trying to help. I was looking through nvflash scripts and files earlier to see if I could find a way for you guys, but haven't come up with one yet.

Sent from my TF101 running OmniROM 4.4.2.
[Eee Pad Transformer Q&A, Help & Troubleshooting] Timberwolfhusky:
It's ok, since you mentioned a blob I tought you may have figured NvFlash out, misunderstanding from my part, apologies..

Please let us know if you find out anything new ;)
[Eee Pad Transformer Q&A, Help & Troubleshooting] Fhurzel:
almost same problem as yours.

I have almost the same problem with an SL101. I did have ADB working but after using 1 click installer i ended up with a tablet without adb. APX works but you can't do much with it since it has not been hacked. I wonder if there is any way to get back adb. When I connect the tablet to a pc it now fails to install adb driver. I have tried a whole range of drivers but seems windows will not recognise it.
[Eee Pad Transformer Q&A, Help & Troubleshooting] Timberwolfhusky:
[MENTION=244701]Sydney[/MENTION]k Off topic question here....still haven't figured the tablet yet...

anywho since you send your messages from a Note 3 can you clarify if that model you own (sm n900p) is the model with a quad S800? I am seriously considering in acquiring one but I have to make absolutely sure that it is not the "Exynos" model I'm getting...since I screwed my tablet and this EVO is stone age, I realized I needed an upgrade...

As a side note I won't give up on the SL101 for the sake of finally solving the issue for other usssrs that my also experience my same predicament...

Thanks!
[Eee Pad Transformer Q&A, Help & Troubleshooting] sidneyk:
It's a quad core T-Mo US version and a nice, but expensive piece of hardware. It's a SM-N900T.
[Eee Pad Transformer Q&A, Help & Troubleshooting] searge:
Can't get into TWRP Recovery on SL101

I' am following this thread on my problem with my slider. Coming from CM10 with CWM (Rogue I think) I decided to try the new twrp for the slider tablet. I booted into recovery and flashed the zip-file provided. After that I couldn't get into recovery menue anymore. I am still able to cold-boot android, but I didn't find a way to fix recovery. Neither a rollback on stock rom (EP101_SDUPDATE.zip) does work for me nor any 1-clicktool (PERI) because unfortunatly I am already on JB-Rom and these tools require ICS-Roms.

Well the good thing is, that I am still able to use CM10 ( a little bit complicated in booting) but TWRP always ends up in ASUS Logo...

I can't use ADB while system is hanging on ASUS Logo. ADB works for me on android level.

With root explorer I can see that paths to mmcblk0p3 or mmcblk0p4 are different (i.e. /dev/block/platform/sdhci-tegra.3/ ... a little bit confusing as I know that my tablet uses tegra 2 cpu ... maybe a good hint for devs)

Any help is welcome, especially now that there is a testing round for katkiss for asus slider I would like to join ... but without twrp this door will kept close.:crying:

Any help is appreciated.

Regards,

searge
[Eee Pad Transformer Q&A, Help & Troubleshooting] Timberwolfhusky:
Im sorry to hear that you have a similarly severe issue..I myself haven't progressed at all, I think this ASUS devices are unnecessarily complex, andcall that file system encryption and that you mention of the dev blocks just makes development even more difficult...

I've hit rock bottom with my slider, if there is any hope left is on you guys..

I'll stick around..
[Eee Pad Transformer Q&A, Help & Troubleshooting] Trancebear:
I also have the SL101 Slider. I just bought it and it was stock and I wanted to root it. I have tons of modding experience with all my Samsung devices but never an Asus tablet, what a nightmare with the Asus.

I found what I thought was an easy root method and I used it. It is called OneclickrecoveryV0.4.2 or PERI found here http://xdaforums.com/showthread.php?t=1681155

I used this root method quite easily and after all was done my recovery could not recognize my SD Card to update the recovery to install KatKiss ROM.

I needed to update my recovery for my tablet could see my SD Card. I Found the latest touch recovery named "signed_twrp-2.6.3.9_sl101".

I took the blob file from the latest TWRP recovery for our SL101 and renamed it recoveryblob and replaced it in the folder for the PERI root method. Now you can do an easy root method and get the latest TWRP all in one process. I am going to host this on my SkyDrive account until they pull it down. It is too large to upload here (12.3mb).

You can get the file here, I hope. http://1drv.ms/1nqsHAS
[Eee Pad Transformer Q&A, Help & Troubleshooting] Timberwolfhusky:
I wish I figured that in the beginning, PERI requires a working debugging bridge (ADB) and I have no way of accessing it :( for my sl101 won't boot far enough to get adb, not to mention the recovery, which does not even boot at all.

Good luck and don't go tampering to too much with these tablets ;) they don't like for what I have experienced.
[Eee Pad Transformer Q&A, Help & Troubleshooting] Trancebear:
I hope this helps for JGarrido. He/she seemed to have my same issue. Sorry you still haven't got it worked out. I think being late to this game helped me.
[Eee Pad Transformer Q&A, Help & Troubleshooting] JGarrido:
I was somehow finally able to get things going, though it's been a couple weeks/months, so I don't recall the exact sequence I took; but it was definitely in no small part due to some tips and tools suggested by others here, so I'm grateful for that.

I'm currently running Revolver 4.2.1, and although it's essentially stock with tweaks, it does seem to be snappier than stock, so I'm happy enough with it. I'll occasionally have issue with certain applications that are programmed not to work on a rooted ROM, but I found something called Voodoo OTA RootKeeper that seems to do the trick to work around that.
[Eee Pad Transformer Q&A, Help & Troubleshooting] FinlStrm:
hey sidneyk, thanks so much for posting this howto. I myself made the mistake of loading CWM via RomManager (and yes, I knew better, just lazy on updating my CWM). After Loading CWM I just got a boot loop into recovery. Also could not get to Cold Boot menu at all. However.. still had ADB access via recovery..... YES!!!! used your method below (wanted TWRP anyway, so much better than CWM) and boom.... back up and running with TWRP Recovery installed.... now on to Nandroid and install CM 10......
[Eee Pad Transformer Q&A, Help & Troubleshooting] Timberwolfhusky:
It was a life saver that you did have access to ADB somehow :)

I wasn't so lucky and now im stuck with a really cool paperweight :(

Heck, I even took my slider completely apart to disconnect all power sources hoping that would help somehow. ..didn't...

My only hope was nVflash but it is not compatible with my model due to the lack of available Secure Boot Keys required to gain access to the flash...

Unless some miracle happens and someone fixes nvflash for the slider, I'm sure it will en up as my windows mobile devices..in the development oblivion.
[Eee Pad Transformer Q&A, Help & Troubleshooting] FinlStrm:
Lucky is right.... one wrong move... and game over. I fancy tinkering inside of products, but I don't think I would ever tear apart my Slider with the inentions of actually using it agan. But is not a bad idea to disconnect power from the board. I tried that on my (dating myself here) Palm Tungsten E2, back in the day, but also did not come back on.

Hopefully someone can figure out that NVFlash for you to get that Slider back up and running, if there are any Devs still around that want to look at the SL101, these really are some great devices. I wish they took off a bit more in popularity. I guess they were a bit before their time however.

If all else fails.... Maybe the connectors on the display are standard (LVDS for the display and USB for the digitizer), you could have yourself a nifty second touchscreen display.
[Eee Pad Transformer Q&A, Help & Troubleshooting] Timberwolfhusky:
Luckily I have myself been taking stuff apart since I was six, and taking advice on how to put it all back together of course ;) My slider was still the same after putting it back together didn't get any worse nor better :/

interesting what you said about the possibility of using the slider display as a secondary touchscreen, have you tried this before? Can you elaborate a little further on that?

Cheers :)
[Eee Pad Transformer Q&A, Help & Troubleshooting] FinlStrm:
Simply guessing here. But assuming ASUS used a standard connection for the display itself, (which would be LVDS, same as laptop screens), then all that would be needed is a controller board to drive it, using a normal VGA or DVI connection. I have taken old laptop screens and done this. I used to have one as a Systems Monitor on the wall until the actual display died.

As far as the touchscreen, taking a extreme wild guess that they simply used USB for the connection. Its the same way Laptop Mfgr's do interal parts (i.e. Bluetooth and Webcams) but with proprietary connectors. However no matter what they use to interface with the touchscreen, finding drivers are going to be a -redacted-.

Then again, if they used all non-standard connections, one could always reverse engineer it. Not impossible but way out of my expertise (haven't used a O-Scope or Logic Probe in about a decade).
[Eee Pad Transformer Q&A, Help & Troubleshooting] Orshi:
Trying to root my slider.

Hi everyone!

I just tried to root my Slider. Nothing works for now. I manage to install TWRP, booting in recovery, but just the menu is shown, not operational. If I am pressing the shut down button will show up a "Slide to unlock" icon with a lock above and that's it. I have to restart the tablet to get rid of it. Almost all the newer links are dead. I can not really find anything. I would like to install 4.4.4.... I still do not see how:) Anyone help in this regards?

It is true that I am a newbie in android rooting, flashing, a.s.o., but I have to try rooting it, since the 4.0.3 it became very slow. Until I am opening something on it I can have lunch....

Firstly I need a rooting tool. Secondly some sort of help on the steps. I know they are something like this:

1. Root,

2. boot in recovery;

3. choose wipe (would be necessary)

4. Install/flash .zip.

But I am stuck at root, it does not happens, but I managed to run from the cmd twrd. It can be the problem that I am playing from a windows 8 machine? Should I move and try on a win7 machine, before I will kill my slider? :silly:

Thank you for your help and\or ideas:D
[Eee Pad Transformer Q&A, Help & Troubleshooting] Timberwolfhusky:
So it ends....

Just thought I post my last fiddling with my long dead SL101.. I have tried it all fruitlessly.. even tearing the WHOLE thing apart, I just noticed a little switch on the MOBO, wondering if anyone would know what it is for, as I flipped it back and forth and nothing happened......AN OVERCLOCKING SWITCH like those found on high end nVidia cards??!! lol JK... As it turns out, The system works (no boot still) with only the MOBO attached, I scrapped everything else (I/O ports, GPS, Ambient Light Sensors etc..)

All bad jokes aside I took some pics of the carnage for your enjoyment...
[Eee Pad Transformer Q&A, Help & Troubleshooting] cheyennemtn:
Been so long I can't remember how I even bricked my SL101 Slider. I've tried numerous times using Peri, OneClickRecovery, Easy Flasher to try and push either the ABD or naked drivers. The APX shows up in my Devices and Printers folder after I boot up into APX mode and Device manager says the drivers are installed but there is no communication when I try to flash using EasyFlasher and get stuck on the NVflash Mode command prompt screen. I've uninstalled the drivers dozens of times. This pad is so damn old now but it's just sitting around and hoping I could bring it back from the dead in time.
[Eee Pad Transformer Q&A, Help & Troubleshooting] Timberwolfhusky:
I get you. I was on the same predicament and tried just about as much as you did.. I additionally tried to do something by taking the whole thing apart to no apparent avail. I was hoping to find a JTAG interface or something of the sort but I do not even have the equipment nor the knowledge to work that anyway..

I now use only the display as a "diagnostic" panel since the connector is the same as in most laptops and has worked every time I've tried it in the same interface..

Rest in pieces SL101
[Eee Pad Transformer Q&A, Help & Troubleshooting] cheyennemtn:
Thanks for the reply Timberwolfhusky. Didn't really even think there were any of us left in this old EEE Slider SL101 ghost town. It's too bad because I have everything right there ready to flash a new recovery and the factory ROM but no matter how many times I tried to get the APX drivers to communicate, it just wouldn't happen. Hahaha. I could boot into the same CWM Recovery 6.0.1.3 but like you said I couldn't access anything without the ABD drivers, kept getting the error E: unable to mount /sdcard. I actually spent the entire day yesterday messing with it and I thought I almost had it a couple times on the flash but it would just freeze up on the NVFlash Mode in command prompt - Just no communication with the driver that apparently was installed. Just about drives you up a FN'g wall. :)... I wish there was another program that would push that driver to be recognized in APX mode so we could flash the damn paperweight. Maybe they're be collectors items someday in a museum. They were ahead of their time with the the pull out physical keyboard. Might have been the first tablet that had that. Again, thanks for the reply. I appreciate it.
[Eee Pad Transformer Q&A, Help & Troubleshooting] Timberwolfhusky:
Always here in the android scene however ancient ;)

I believe the issue with out sliders resides in the nvFlash binaries, which were never updated to contain the SBK for our particular serial numbers (B90 / 80 if memory serves) The flashing program can in theory communicate but it does not have the security cipher to allow secureboot to run.. and since we're talking about encryption here, it's not just a matter of a driver hack or a stunt of such description :(

So at the point we cocked up out boot/staging partitions we were pretty much SOL...I also thought I almost had it. .I was at it for over two weeks and I pretty much just gave up :/

Such is life.
[Xperia SP Q&A, Help & Troubleshooting] maxify:
Hi all. I'm quite desperate about rooting my device as I couldn't get it working in two days.

My firmware version is 12.0.A.2.254.

I followed this tutorial: http://xdaforums.com/showthread.php?t=2440375

On Windows 8.1, Flashtool does not detect the device in Flash mode. The notification light goes green, but nothing happens with Flashtool.

On Windows 8, the result was just like above.

Later I read about driver signature enforcement in Windows 8 and I admit that it was not enabled, so maybe that was the problem.

On Windows XP, Flashtool says the following:

PC Companion and the drivers that came with Flashtool were installed in both cases.

Please share any thoughts - or, if you were able to root your device with the same firmware version, say how and on which OS! Thanks!
[Xperia SP Q&A, Help & Troubleshooting] Robin>Hood:
Hey,

Just read DoomLords tutorial, the whole thread, I believe there are many people with the same question and it's answered.

Are you sure you installed the flash tool drivers on the XP machine? (I would use XP or win7, not win8 for this).

Also try this:

Connect your Xperia SP via USB. (Don't forget to enable USB Debugging)

Then run the Software (http://adbdriver.com/downloads/) and choose your phone, which should be listed in the list.
[Xperia SP Q&A, Help & Troubleshooting] maxify:
Ok, I did it all over again on Windows 7 and... I'm excited to have my device rooted now.

There were two attempts, the first time Flashtool again threw an error, but at the same time Windows installed some driver itself and then everything went all right.

Thanks, Robin>Hood!
[Xperia SP Q&A, Help & Troubleshooting] noahvt:
Yeah windows 8 and 8.1 gives massive problems you can do it eventually but it will take longer then just installing windows 7 on your computer!
[Xperia SP Q&A, Help & Troubleshooting] Robin>Hood:
Glad it worked out for you! Enjoy your rooted phone and the many options of the Xposed Framework!

Or you could give Cyanogenmod a try, I use CM10.1 29.10.2013 build as it is super stable for me :)

Next time, don't forget to use the search option, typing the right key words will help you a lot on these fora! Enjoy :D
[Nexus 5 Q&A, Help & Troubleshooting] gil80:
Hi,

I'm unlocked & rooted using stock ROM 4.4.2 and kernel with Xposed framework installed.

When selecting ART in developer options the phone reboots and then is up again in 10 seconds.

I know that this should take up to 20 minutes.

Can someone please help me out?
[Nexus 5 Q&A, Help & Troubleshooting] PhilipTD:
I think xposed and art are incompatible.

Sent from my Nexus 5
[Nexus 5 Q&A, Help & Troubleshooting] ldubs:
Correct. It is bouncing your device right back to dalvik.

sent from my hammerhead
[Nexus 5 Q&A, Help & Troubleshooting] x8hsu:
http://xdaforums.com/showpost.php?p=24267823&postcount=2

search "ART" then you would see~

:silly:
[Nexus 5 Q&A, Help & Troubleshooting] g01851:
Sneaky sneaky... I installed Xposed and didn't notice it switched me back to Dalvik!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] yapoyo:
Hey guys,

I'm running the latest carbonrom 11/17 nightly. I was thinking about using koush's superuser app, to use it, do i just have to install it from the play store? ore is there something more I have to do?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] daroco:
you can download it from the play store, or alternatively you can use his flashable zip from the link on the play store page in the description field. Play store would be the easiest way.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] yapoyo:
That's it? Do I have to delete the old superuser app?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fresti:
Are u mind is change superuser old to new superuser?? I ever do that... but are you mind like that ??

Sory my english so bad

Sent from my PICOpadGCE
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] daroco:
The installation process will remove the old one.
[Acer Iconia A500] iNT0XiC8D:
Heya, I have an engineering sample A500 with 2.2 froyo installed and am trying to update it. Putting a decrypted update.zip on an sd card and booting into recovery doesn't work. It shows a progress bar for a few secs and then nothing else. Can someone with the Application.apk send it my way or post it here? I can't find it anywhere and 2.2 doesn't have the Play store. I'm also unable to install it to another device as they are unsupported devices. I'm hoping this will allow me to upgrade to something usable and then go from there. Thanks for the help.

Android Build	: Acer_Picasso_0.008.01_EMEA_GEN1_DEMO

Bootloader	: 0.03.01-HC

-iNT0XiC8D
[Acer Iconia A500] iNT0XiC8D:
Well after a couple days of trying everything I enabled USB mounting with windows and it said the volume needed formatted. Let it format and then had an 8GB volume. After coping some apk's to try I rebooted and now it seems Android 2.2 is gone and there is a blank screen after the acer boot logo. :( Any ideas? Can I nvflash a full rom directly as a block device or something? JTAG/ISP, SPI, I2C, ect?
[Acer Iconia A500] uglyjohny:
I dnt understand smthing ... 5 hrs ago u asked for apk and 1 hr ago u had your tab formated and thres nutting?

sent from sgs3 -stock 4.3 open europe rom

---------- Post added at 07:46 AM ---------- Previous post was at 07:42 AM ----------

Imo you shoud download EUU package and try to unbrick your tab.

sent from sgs3 -stock 4.3 open europe rom
[Acer Iconia A500] iNT0XiC8D:
They'll be nutting after I get this thing fixed. :p I don't understand that there are 127 views and no one can share an apk from their tablet. :confused: That apk probably wouldn't have helped anyway. Am I supposed to wait around for it to magically fix/hack itself or keep trying things? I tend to keep trying things and I thought I explained in enough detail what I was doing. Never would have thought that enabling usb sharing would have caused it to wipe out the OS too.
[Acer Iconia A500] uglyjohny:
In two posts you stated two diferent things. If you cnt boot up your tab no apk will help you. If you can boot download aptoide apk and install playstore and google services and ill send you enhecment apk. If you cnt boot up as your internal memory was wiped out as stated by you than try EUU package.

sent from sgs3 -stock 4.3 open europe rom
[Acer Iconia A500] iNT0XiC8D:
Yes I thought updating the original thread was better than starting a new one.

EUU and nvflash got me in the right direction. Flashing EUU didn't unbrick (still at Acer logo). I was able to find a procedure that worked though and can create a guide if anyone is interested. Engineering samples seem to be different than retail units. CPUID and SBK are completely unneeded and will cause current (retail) utils to fail.

Nvflash started

rcm version 0X20001

System Information:

chip name: t20

chip id: 0x20 major: 1 minor: 3

chip sku: 0x8

chip uid: 0x0XXXXXXXXXXXXX (masked my info)(this was the same ID AfterOTA captured from 2.2 froyo)

macrovision: disabled

hdcp: enabled

sbk burned: false

dk burned: false

boot device: emmc

operating mode: 3

device config strap: 0

device config fuse: 0

sdram config strap: 1

-iNT0XiC8D