yashsingh1/xdaforums huggingface dataset:
[Eee Pad Transformer General] darkstknight1523:
Rayman, thanks for the help, but maybe I'm just not grasping it.

I downloaded the Asus firmware (US_epad-user-9.2.1.24.zip) and extracted the files to the Wheelie directory; (1 folder called META-INF and a file called blob).

I then opened my cmd window and unpacked the blob file with blobunpack

blobunpack blob

that created (4) files called blob.APP, blob.EBT, blob.LNX, and blob.SOS.

I downloaded your files and extracted them both into the wheelie directory.

I ran wheelie (at least I think I am running wheelie) by using

wheelie -2 -o 0x300d8011 --bl bootloader.bin -c transformer.bct

I then I ran the commands you instructed and it appeared everything went fine, unfortunately, I am still with nothing. Maybe you can dissect what I'm doing wrong through the log:

c:\ASUS\wheelie>blobunpack blob
Header size: 60
4 partitions starting at offset 0x3C
Blob version: 65536
Partition 0
Name: EBT
Offset: 124 (0x7C)
Size: 1454712 (0x163278)
Writing file blob.EBT (1454712 bytes)
Partition 1
Name: SOS
Offset: 1454836 (0x1632F4)
Size: 4284416 (0x416000)
Writing file blob.SOS (4284416 bytes)
Partition 2
Name: LNX
Offset: 5739252 (0x5792F4)
Size: 4151296 (0x3F5800)
Writing file blob.LNX (4151296 bytes)
Partition 3
Name: APP
Offset: 9890548 (0x96EAF4)
Size: 536870912 (0x20000000)
Writing file blob.APP (536870912 bytes)

c:\ASUS\wheelie>wheelie -2 -o 0x300d8011 --bl bootloader.bin -c transformer.bct
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================

Using SBK type 2.
Using bootloader: 'bootloader.bin'.
Using BCT: 'transformer.bct'.
----------------------------------------

[=] Chip UID: 0x251199401146529303
[=] RCM Version: 0x20001

[=] CPU Model: Tegra 2
[=] Secure Boot Key Set: Yes
[+] Sending BCT
Sending file: 100 %
[+] Sending ODMData 0x300D8011
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash

c:\ASUS\wheelie>nvflash -r --download 6 kernelblob.LNX
Nvflash started
[resume mode]
sending file: kernelblob.LNX
/ 4173824/4173824 bytes sent
kernelblob.LNX sent successfully

c:\ASUS\wheelie>nvflash -r --download 5 recoveryblob.SOS
Nvflash started
[resume mode]
sending file: recoveryblob.SOS
| 4907008/4907008 bytes sent
recoveryblob.SOS sent successfully

c:\ASUS\wheelie>nvflash -r --go
Nvflash started
[resume mode]

I am so very frustrated but hope you can see what I'm doing wrong.
[Eee Pad Transformer General] darkstknight1523:
thanks baseballfanz, but this isn't working for me either, I connect the TF to the PC and it recognizes it as an APX device. I then try to run the .bat and it doesn't see my device.
[Eee Pad Transformer General] darkstknight1523:
I am wondering if it is a hardware problem at this point. I've been noticing that even though I power off the tablet, it automagically reconnects to the PC as an APX device without me trying to turn the tablet back on.

Any thoughts on this being the culprit or am I just a fool who can't get this right?
[Eee Pad Transformer General] RaymanFX:
It still can't boot, because no rom is installed. But I see my files where flashed succesfully, so please try to get into recovery by holding Power+volume down, then volume up... from there, you can install any flashable zip..
[Eee Pad Transformer General] darkstknight1523:
I tried to get into recovery by holding Power+volume down, but nothing happens. Should be doing this while it is connected to the PC? When I attempt to power down while connected to the PC, I hear the notification that it has been disconnected, I immediately release the button, but then hear it reconnect as an APX device. I have had experience flashing ROMs to my other tablets and phones, but I've never had the problem of not being able to get into recovery before.

Are there any other files I should have in my wheelie folder other than these:

Directory of c:\ASUS\wheelie

07/13/2012 10:14 PM <DIR> .
07/13/2012 10:14 PM <DIR> ..
07/13/2012 10:12 PM 546,761,460 blob
07/13/2012 10:20 PM 536,870,912 blob.APP
07/13/2012 10:20 PM 1,454,712 blob.EBT
07/13/2012 10:20 PM 4,151,296 blob.LNX
07/13/2012 10:20 PM 4,284,416 blob.SOS
05/31/2012 04:58 PM 58,880 blobunpack.exe
06/05/2011 04:43 PM 943,193 bootloader.bin
05/31/2012 05:02 PM 3,172 flash.cfg
07/13/2012 09:04 PM 4,173,824 kernelblob.LNX
05/31/2012 04:48 PM 18,944 libnv3p.dll
05/31/2012 04:48 PM 12,288 libnvaes_ref.dll
05/31/2012 04:48 PM 80,384 libnvapputil.dll
05/31/2012 04:48 PM 9,728 libnvboothost.dll
05/31/2012 04:48 PM 45,056 libnvdioconverter.dll
05/31/2012 04:48 PM 23,040 libnvflash.dll
05/31/2012 04:48 PM 28,160 libnvos.dll
05/31/2012 04:48 PM 10,752 libnvusbhost.dll
07/13/2012 10:10 PM <DIR> META-INF
05/31/2012 04:48 PM 135,168 nvflash.exe
07/13/2012 09:05 PM 4,907,008 recoveryblob.SOS
05/31/2012 04:49 PM 218 reflash_sbkv1.bat
05/31/2012 04:53 PM 218 reflash_sbkv2.bat
06/05/2011 04:43 PM 4,080 transformer.bct
05/31/2012 05:21 PM 196,608 wheelie.exe
23 File(s) 1,104,173,517 bytes
3 Dir(s) 43,178,803,200 bytes free

c:\ASUS\wheelie>

Am I following the steps correctly?
[Eee Pad Transformer General] darkstknight1523:
thinking of throwing in the towel

I am considering just bringing the tablet back to Best Buy and hopefully exchange it for a replacement. I can't seem to get things in order and back up and running. Each time I think I'm close, I get the same result and frustrates me. If anyone else has a suggestion, I'd love to hear it.
[G2 and Desire Z Q&A, Help & Troubleshooting] Ndpking209:
For some reason the sound switches from my external speaker to the speaker used when you're talking on the phone. This is only an issue when I'm running CM9 or Andromadus. Can anyone help:confused::confused::confused:
[G2 and Desire Z Q&A, Help & Troubleshooting] Whoareyou:
I had the same issue, flash rc2 and the unofficial kernel fixed it for me ;)
[G2 and Desire Z Q&A, Help & Troubleshooting] Ndpking209:
Thanks

Thank you I will try that immediately!
[Galaxy S II Android Development] hacker812c:
[Recovery] Galaxy SII ClockWorkMod Touch 5.8.4.5 Black Edition

The base used in this Recovery is the Samsung Galaxy S3 CWM Touch

This recovery is being recommend testing only for experienced users in recovery and backups of your firmware in hand.

The buttons and volume vol - and vol + this buttons are working perfectly

The buttons search and back on touch screen are working perfectly

The file system of this recovery is edited and tested [recovery.fstab]

[Credits]

Hansheck - By working hard to correct the Boot

nitroglycerine33 - At work with Bootstrap Original

Hacker812c - Modification of scripts / exploits internal

Hacker812c - Amendment of recovery Internal / application testing

ClockworkMod is considered by many the best recovery system in place for android.

ClockworkMod Touch is an advanced recovery feature that incorporates the touch screen.

With CWM you can quickly recover your rom, reinstall updates, etc ...

[Setup]

1. Make the root of the device

2. Install the apk

3. Open the application that you installed and click to install the recovery

4. Now you have the best recovery system CWM ClockworkMod

5. Click "Reboot Touch CWM" and restart the device to go into recovery

6. Click on "Backup and restore" and "backup" to create your backup android

7. Now you can install the new Custom roms with CWM Touch 5.8.4.5

Now we have CWM 5.8.4.5 Touch

This recovery is based on the latest system rom manager clockworkmod.com

This recovery is the latest version of the latest technology CWM Touch

[Download CWM Touch 5.8.4.5] The Black Edition build 0.0.5

Re-uploading please wait...

Re-uploading please wait...

[BUSYBOX PRO]

http://www.mediafire.com/?0ctrjgmh17f5ei4

http://www.mediafire.com/?ifzvab33ro4u1lf

[JELLY BEAN BOOTANIMATION]

http://www.mediafire.com/download.php?lj95xcnost0523g

[THANKS]

If you have a little time press the THANKS, thanks.

[RESULTS]

This release is based on Samsung Galaxy S3 Recovery [Clockworkmod.com]

This recovery includes the latest tecnology of CWN Touch and this is the latest version of CWM Touch

Compiled the apk and modified the recovery procedure...

The base used is the Recovery of the Samsung Galaxy S3

If you do download and install please share your experiences

Jesus is the secret of my success!
[Galaxy S II Android Development] hacker812c:
Compiled the apk and modified the recovery procedure...

The base used is the Recovery of the Samsung Galaxy S3

If you do download and install please share your experiences
[Galaxy S II Android Development] vertrag:
I followed the installation procedure but nothing happen my bootloader still CMW Touch 5504 from siyahh..

when i boot to recovery using the apk that just installed the recovery was skipped

hope that helps :D
[Galaxy S II Android Development] tuilalnvinh:
Me too, installed, rebooted, nothing happen. I'm on SpeedMod kernel
[Galaxy S II Android Development] nedooo:
Same with Dorimanx Kernel, nothing happens, recovery wannabe :D

You can ask mods to delete this thread...
[Galaxy S II Android Development] cdaarif:
nothing happened 2 me rooted stock LQ5:crying:, i faound this http://www.clockworkmod.com/rommanager/ recovery-clockwork-touch-5.8.1.5-galaxys2, but dont know how to install it.
[Galaxy S II Android Development] reinbeau:
Thread closed

There is a high probability that this will cause an unrecoverable brick, as reported to me:

I know this is true as touch recovery has already caused bricks on other devices, the Note, for example. Let's not share dangerous methods like this where people who don't know any better might suffer the consequences.
[Sprint HTC EVO 4G LTE] jacobb23:
So apparently the update broke my camera..tried multiple resets, haven't yet tried a factory reset...but I open the camera app and it's just a black screen. Anybody else experienced this?
[Sprint HTC EVO 4G LTE] tazarman79:
4g lte camera broken

Same here. Anyone have a fix?
[Sprint HTC EVO 4G LTE] leo72793:
I did Xhausx update through twrp. Camera works great
[Sprint HTC EVO 4G LTE] NewZJ:
If you are rooted, flash the previous software to see if the problems reappear. If you are not then you should try factory reset. If you don't want to root to continue troubleshooting then take it back under warranty if the factory reset didn't work.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] vma:
Hi,

Is it just me being an idiot, or is it indeed not possible to do a simple voice dial using JUST the bluetooth headset?

I am used to just double click on the headset's button to get a lady asking me what to do and I then just used to say "call xyz".

I did so using Windows Mobile and on the iPhone.

Strangly I can't find a similar option on the Note! Also, the preinstalled voice recognition just sends the wave file to a server for analysis. I don't like that, because I have limited Internet traffic on my plan and don't want to waste it this way. Also, I drive a lot in a different country, where mobile Internet is just not available.

Any help appreciated.

Cheers,

vma
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] dr.ketan:
You can find voice speed dial on market, need not to have net for application, you need to record tag.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] vma:
well, at least I am not plain stupid for not finding the relevant option.

Having to record tags for voice dial is not state of the art and I would not rely on third party software for that.

To me, this is probably the #1 feature I am missing and I can't understand how this phone does not provide voice dial.

Thanks for your reply, though.

Cheers,

vma
[Android Q&A, Help & Troubleshooting] tallesairan:
Hello you can put the LG Optimus CyanogenMod In L3 or is there a version compatible? mod or other without the Cyanogen
[Android Q&A, Help & Troubleshooting] ronilton:
maybe still are doing

still have not found anywhere Maybe they're building a machine because it is released shortly
[Android Q&A, Help & Troubleshooting] tallesairan:
friend took the phone and very good it just need to get better

friend took the phone and very good it just need to get better
[Android Q&A, Help & Troubleshooting] ealita313:
i'm using CM9(cyanogenmod 9) on my L3 ... i found some bugs there, but during these drawbacks do not bother me ...

over of all, it's a cool rom ^_^v
[Samsung Epic 4G Touch] dbldown768:
I have a panasonic th12 home phone base that normally my phone connects to when I am at home over bluetooth. This allows me to use regular handsets while in the house to make / receive phone calls. I just updated to the FF18 from sfhub's odin and now my device no longer will connect the home phone base. It pairs but it will not stay connected or allow me to check the box for phone calls as well. Any ideas? is this a bluetooth bug?
[Samsung Epic 4G Touch] someguyatx:
Every time I flash I have to pair my phone with car again. I typically delete device profile from phone, delete phone profile from device, change bluetooth name of phone, pair phone with device under new name. Finally after paired wait for message to pop up on phone asking if device has permission to access your stuff and check box for always allow.
[Samsung Epic 4G Touch] dbldown768:
Maybe someone can even point me in the right direction as to how to debug this situation? I have a development environment up for apps, but havent ever explored the base source code. If anyone has any thoughts it would truly be appreciated.

Its really makes me made because I had a similar problem with my last phone, the HTC hero. It got to the point you wait for all of these updates and then I had to limit my phone to like andorid 1.5 otherwise my phone would not connect. Its should be a bigger issue only because users who are not on xda would be screwed and could not rollback to a previous Android release. At lease this community exists so that I can go back if needed. As of right now I'm liking the new ics on this phone and will be very disappointed if I have to to back to GB just for this.
[HTC Desire S] sunand777:
Hi

I am now using

ICE_DS -v.4.0 ICS 4.0.4 Sense 3.6 Official Stock RUU 4.10.405.1 rom

but i can't update or download apps from google play store via "INTERNET PASS THROUGH" feature on my desire s

it shows WAITING FOR NETWORK.
[HTC Desire S] sunand777:
sorry...its working

? ?
[HTC Desire S] brat81:
open Terminal

Type

su

killall drmserver

start downloads again

eh just read the thread not sure maybe try the above
[Galaxy Note GT-N7000 General] wpghtc:
Has anyone else got this crappy wake lock with 4.0.4?

Sent from my GT-N7000
[Galaxy Note GT-N7000 General] dannycanrock:
Me 2

Sent from my GT-N7000
[Galaxy Note GT-N7000 General] hyperken:
One day usage with no wake lock.
[Galaxy Note GT-N7000 General] Doodle:
My wakelock disappeared with the installation of 4.0.4. Even if i disconnect from charger without turning the note on first.
[Galaxy Note GT-N7000 General] rowee270:
How did you install 4.0.4? Did you do a clean install? My wakelock issues seemed to have gone since the update - maybe there is a rouge app?
[Galaxy Note GT-N7000 General] aussiebum:
the l2_hsic depends partially on kernel apparently. Goku's kernel supposedly uses SGS3 modem code to try fix the l2_hsic issue. Not sure if the 4.0.4 stock kernel is fixed or not.

I haven't had a l2_hsic wakelock so far since flashing over DDLPA (using Goku 1.3b1 kernel + older LA4 modem).
[Galaxy Note GT-N7000 General] Doodle:
stock kernal for me on 4.0.3 ===> Wakelock

stock kernal for me on 4.0.4 ===> No wakelock
[Galaxy Note GT-N7000 General] _yupa_:
I still have the wakelock in both 4.0.3 and 4.0.4.
[Galaxy Note GT-N7000 General] or8it:
I'm convinced it's certain apps causing L2_hsic. Since I've uninstalled Dolphin Browser I've not not had it reappear, 3 days and counting.
[Galaxy Note GT-N7000 General] palmy999:
Longest record for L2_HSIC not appearing: 14 days without reboot.
[Galaxy Note GT-N7000 General] carlitos66:
I still have it. All stock, official updates via Kies, German software updates.

No wakelock on my S2 with official GB ICS software. All run exactly the same apps and settings.
[Galaxy Note GT-N7000 General] dhruvmalik:
Having drastic Wakelocks due to Exchange and Mail.
[Galaxy Note GT-N7000 General] LowDef:
I heard that screen waked from sleep by some app's notifications especially stock sms & s-planner triggers the lock you said somehow no matter what ROM version you're on or when it would happen.

Solution (as alternatives): Use Handcent sms and freeze the stock sms. Then turn off all screen wake notifications in Handcent and S-planner. You absolutely loss this functionalities. It's just painfully trading off.
[Galaxy Note GT-N7000 General] Braxos:
http://xdaforums.com/showthread.php?t=1656705

There you go, even it is till now for 4.0.3 wakelock reports as no one except you has l2_hsic wakelocks on 4.0.4.
[Galaxy Note GT-N7000 General] nikki2325:
Here is the solution for excessive battery drain and wakelocks

Install cpu spy. Turn your device display off for about 10 min and check if your device is going into deep sleep state. If not, its the problem with your kernel.

Do factory data reset( make sure to backup. Data will be erased) and follow the same procedure.Now you can see your phone goes into deep sleep...

If you are rooted and stil factory data reset doesn't work for you...try those kernel cleaning scripts out there and flash a good recommended kernel.

Hope it works
[Xoom General] R1150GSA:
Up until this point I've been using the EOS Stable Release 2, more because I liked the idea of "stability" over bells & whistles. On a whim last night I installed the EOS Nightly 117 build and I can't believe how fast it is. Screamin' fast! Plus it seems very stable.

How often do you nightly folks update? Every day? Every few days? When a new feature is installed? So far I'd say it's worth the time to update every day. I'm sold.
[Xoom General] adelancker:
I usually only update when I am really bored or when I see a feature I really want! :)

I also updated to JB and it is -like you said- crazy fast! I absolutely love it. Now let's hope the addition of extra features doesn't slow down the performance ;)
[Xoom General] Rone1986:
Its wicked fast and super stable. Loving it. Having no problems except the usual android apps toothing problems, not playing nicely with jb, but only encountered 2 so far.
[Xoom General] djpry:
holly crap :D
[Xoom General] Chaosgod27:
Yep that's Jelly Bean for you =)

The nightlies are generally very stable, it's once in awhile you will encounter issues, but so far I haven't been getting any issues at all. On another note I believe when TeamEOS implement Linaro optimisations on JB, the XOOM will be blazing fast.
[Xoom General] griffin337:
Unless there is major change or fix in the nightlies i dont flash..

But do have a question with 117. I cant seem to get Video chat in google talk to work. It just goes black screen and closes. The normal IM'ing works.. just cant video. Both from and rear camera seem to work with the camera app.

Any Ideas?

Thanks!
[Xoom General] okantomi:
Re: nightlies...I flash them as soon as they come out...works for me.

You see a big change, in part because you're now on a whole new operating system (Jellybean) that has a number of fundamental improvements. TeamEOS will be applying all of their own improvements from here on in, so it's really worthwhile to stay on the bleeding edge with these nightly builds.

Also, flash #118 and the newest eos gapps for Jellybean: 7/13. Your issues should be resolved. If not, there may be something in the Moto propriatary binaries that will be released when the OTA comes out that can fix video chat.
[Xoom General] glock20c:
Sweeeeeet jelly bean
[Xoom General] Asphyx:
The speed increase your seing in Nightly 117 is due to what Google calls "Project Butter" which is a key new feature of jelly Bean and increases performance and screen draws significantly.

As to how often do I flash a new nightly, I usually skip about 10-20 nightlies unless one comes out that is reported to have very few issues and good enough for a release candidate.

Other times I will go off that if a particular bug I have been having is showed to be fixed but it really makes little to no sense for anyone but someone acting as a beta tester (and even then) to flash every nightly that comes down the pipe.

First off if you want to help squash bugs you need to use the device a lot and put it through it's paces which you can'y do if most of your day is spent flashing the newest.

And remember you bought the device to use it not flash it (although some would say otherwise LOL)

If you follow the project it's pretty easy to find the happy medium and know when to flash.

Anyone on the 1.0, 2.0 or pre 117 Nightly should really consider updating and getting all that Jelly Bean and Buttery goodness!

Not to mention Google Now which is pretty damn cool!

And just a warning to anyone on V2.0 or pre-Nightly 96 you will need to flash a new radio as well. Read the direction carefully as on;y Rogue Touch recovery can flash the radio and you need to flash that first before the rom. There is also a new Gapps for jelly Bean as well so read the instruction carefully.

But I'm running the jelly bean now and it is far superior to the older stuff and they haven't even started tweaking it yet they are just creating their base!
[HTC Vivid, Raider, Velocity] Kraizk:
Links removed

***DISCLAIMER: THE OP POST IN THIS THREAD IN NO WAY SHAPE OR FORM SLANDERS OR TRASHES XDA AS ADDRESSED BEHIND THE SCENES. THEREFOR IT IS IN NO WAY A VIOLATION OF ANY OF THE EULA AGREED TO UPON SIGNING UP FOR XDA. I AM NOT TELLING OTHER USERS TO PARTICIPATE IN OTHER SITES ONLY THAT IT MAY BE OBTAINED THERE. ADDITIONALLY THIS THREAD IS DESIGNED TO LINK USERS TO AN ENHANCED EXPERIENCE AS ALL USERS OF XDA AIM TO PROVIDE. THE AUTHOR OF THIS PROJECT NO LONGER CHOOSES TO PARTICIPATE ON XDA. THAT SAID ALL USERS ARE URGED TO READ THE INITIAL LINK OF THIS POST WITH REGARDS TO WHAT HAS OCCURRED AND WHAT XDA ALLOWS IN THEIR REALM. IF ANY XDA ADMINS WISH TO PROTEST THIS POST IT WOULD BE GREATLY APPRECIATED IF THEY WOULD HAVE THE COMMON DECENCY TO PM ME BEFORE DELETING MY POST.

Mod edit: You already received a few PMs about this issue from me last night. Your links direct traffic to another site. Please don't use XDA to direct traffic to another site. In turn, you wouldn't be allowed to direct traffic from that site to our site. Yes, that site has the same rule. Trust me.

Since you're his spokeperson, please tell him if he wants to have his users go this other site, he needs to find a way to contact them about it which doesn't involve XDA.

Here's the rule again:

11. Don’t post with the intention of selling something.

Don’t use XDA to advertise your product or service. Proprietors of for-pay products or services, may use XDA to get feedback, provide beta access, or a free version of their product for XDA users and offer support, but not to post with the intention of selling. This includes promoting sites similar/substantially similar to XDA-Developers.com.

Do not post press releases, announcements, links to trial software, or commercial services. unless you’re posting an exclusive release for XDA-Developers.com.

Encouraging members to participate in forum activities on other phone related sites is prohibited.

Off-site downloads are permitted if the site is non-commercial and does not require registration.

Off-site downloads from sites requiring registration are NOT encouraged but may be permitted if the following conditions are met:

A) the site belongs to a member of XDA-Developers with at least 1500 posts and 2 years membership who actively maintains XDA-Developers' support thread(s) / posts, related to the download,

B) the site is a relatively small personal website without commercial advertising/links (i.e. not a competitor forum-based site with purposes and aims similar to those of XDA-Developers.com.)
[HTC Vivid, Raider, Velocity] shogunmark:
You were previously warned. You know why this is not allowed, you are redirecting the traffic to a banned user. Not redirecting to a user that does not wish to participate.. It's obvious that you all can not follow the rules.

And yes, i am leaving this here so you all can quit acting like victims... Stop being little trolls