yashsingh1/xdaforums huggingface dataset:
[Barnes & Noble Nook Tablet] Pain12345:
yea copied the files like you said and it still doesnt work. The nook does start and instantly boots "nook reader" not cwm. I really dont know what mroe i should do, i might record a movie if im home.

While booting the nook i have connected the usb cable

Thats how my partitions look like:

first partition with the cwm files on it: 50MB - Primary - FAT 32 - boot and lba flag

second partition: nothing on it - 2000MB - Primary - EXT4 - no flags

third partition: nothing on it - 2000MB - Primary - EXT4 - no flags

Edit2:

i didnt fill the sdcard with zeros, should i do this b4 partitioning?

Also my Nook is rooted, does this matter?
[Barnes & Noble Nook Tablet] Valkyrie77:
Indirect's APK?

I couldn't get the SD card method to work either and then I found Indirect's APK and that worked perfectly, just a thought... It's in the development section.
[Barnes & Noble Nook Tablet] Land Master:
Really trying to help you here. Honestly I have never used the method in the actual CWM thread but I have successfully on two occasions created bootable SD cards. It is my understanding that it is the way the card is partitioned that tells and allows the system to "boot" from it. That said I have copied the instructions from the CM7 Rom thread below which use the Linux GParted partitioning method. Not having the SD card setup properly is the only thing I can think of to help at this point besides perhaps that you have a bad card. Try the below (which it sounds like you already have) just to be 100% sure the card is setup properly.

Delete all partitions on your SD card first using GParted and use the following

------------Thanks CelticWebSolutions--------------------

Open GParted select your SDcard in the top right hand side of the window.

Select create partition table form the device menu select the empty space on the newly wiped SD card and click the paeg icon with a green plus on it, a window will appear with some boxes to fill in, change the box that says New Size (Mib) to 50, Change file system to Fat32 and write boot in the label., then click add.

Again click on the unallocated space and add another partition as around 2000(MiB) as EXT4 and label it as system (LandMaster Note: Not needed for CWM only)

Add a 3rd partition in unallocated space again of about 2000(MiB) EXT4 and label it as data. (LandMaster Note: Not needed for CWM only)

now you have three partitions waiting to be created click the green tick to apply your changes

Once changes have applied right click on boot and select the menu item 'Manage Flags', tick boot and lba and close the window, your SDCard is now ready to get it's data for it to work

-------------------------------------------------------

You DONT even need the 2nd (system) and 3rd (data) partition as outlined above if all you want is a bootable CWM. Just one (I used 74MB) MS-DOS (FAT32), Active Partition with "boot" and LBA" flags set.

Lastly, since you are rooted you could always flash the internal recovery partition with CWM using the method in This Thread and get into CWM by clicking reboot recovery from within the app.

I never did ask .... What is your ultimate goal?
[Barnes & Noble Nook Tablet] Pain12345:
I spend a few more hours to it and it still doesnt work. Via the app i can run cwm but only via the app. The goal is that i have a working recovery sd card if i brick my nook..

I installed ubuntu on my computer and i did exactly the same steps like you have posted but it wont work. Ive also tried multiple other sd card but that didnt change anything

Maybe any development settings on the nook that i should change?

As i live in germany would maybe anyone of u sell me a working sd card with cwm on it so i can test?
[Barnes & Noble Nook Tablet] Land Master:
Thats what I thought and it is a good plan. Unfortunately I'm stumped.

Albert Wertz is in the SD Card "business". Check with him to see about getting one.

FYI, now that you have CWM "written" to the internal recovery partition you should be able to enter recovery even if you can't boot the tablet to android.

N+Pwr from off condition should do the trick.
[Barnes & Noble Nook Tablet] tonyp22:
Pain, sorry, I just saw this thread. I made a small update to the instructions. I left out something which I thought was obvious. This was a fault on my part. Did you label each partition correctly? It should be BOOT, system, and data.

I used this method (don't forget the ext4fsd part) and it does work. But if you're still having trouble the CD-boot version of Ubuntu will work just fine too.
[Barnes & Noble Nook Tablet] Pain12345:
i allready have ubuntu running on a cd, in the past i labeld it "boot" (case sensitiv - all small letters) so this could be the fault?

Edit:

i can see that cwm work, it pops up 4 a half second or even less if i start the nook but than it instantly disappears
[Barnes & Noble Nook Tablet] Rafael863:
after installing cwm on my NT after that (my B&N store has been disabled and it doesn't let search, download, or view anything on the store..... has anyone a solution to this issue
[HTC Sensation] hasan69:
Hello

My problem is the Touch Mobile

Some time lag makes touch

Touch buttons not working means nothing nothing

I was doing after updating firmware

I've tested several different

Touch my recovery version 8

When I installed the full wipes

2.3.7 Android Android ROM 4 and tried

For example, when I want to write anything does not work sometimes

And should close by the power button once

Again open I the power button

Please help
[HTC Sensation] jaaystott:
I'm not too sure what you mean because of bad English ( no offence intended) however I will try and help you.

It sounds like you MAY be experiencing the grounding issue that many people have had with their Sensations, there is a small pin on the inside of your case that may not be working properly, hence the screen not working. There is an entire thread on this on the 'Sensation General' section.
[HTC Sensation] hasan69:
Sorry I can not speak good English

Please put a link to this thread

What phone do the cover?
[Galaxy S II Q&A, Help & Troubleshooting] Taurinbtz:
Hallo dudes,

i have a big problem... i flashed my mobile and put a rom on it.

than i tryed to make my phone like i buy it.

Now i cannot update anymore??

I want to go the normal way, but now my phone wont update..

It is possible to get my phone, as i bought it? that i can update it with normal thinks and that kies accept my phone?

sry for my bad english. i really hope somebody helps me :/ ;) iam a newbie
[Galaxy S II Q&A, Help & Troubleshooting] Hollow.Droid:
You have to restore to a stock official ROM. Have a good read at this thread. It should have all the info you need.
[Galaxy S II Q&A, Help & Troubleshooting] Taurinbtz:
but, which file ive to choose? :/
[Galaxy S II Q&A, Help & Troubleshooting] Hollow.Droid:
Find your country and choose the most recent one. For example if you're from China/HK then ZSKF1 would be your best bet. It's pretty self-explanatory :)
[Galaxy S II Q&A, Help & Troubleshooting] Taurinbtz:
Iam from germany :)

so ive to flash the german newest file on my phone? and than kies accept my phone, so it will automaticly update my phone? for example on ics if it comes.

Thank you for your help :)
[Galaxy S II Q&A, Help & Troubleshooting] Hollow.Droid:
Yes, however as you'll be flashing the latest release it could take several weeks if not a couple of months for the ICS update to hit kies. Although March 1st has been rumoured to be the release date.
[Xperia Play Android Development] paxChristos:
R800x Users, I have just compiled a kernel based of the 3.0.1.E.0.88 Sources.

I need a few testers, Big update, read the update section for v.2 (2012 Feb 12)

Pax

Update 01: 2012 February 08 1500 CST:

Working:
Stock kernel (no overclocking yet)
Boots
No random reboots (yet)
Autobrightness is disabled (as it was in 2.3.3 update)

Not Working:
Wifi (came from DooMLoRD's Kernel, need to check coming from stock update: need to flash Doom's stock wifi)
Recovery (need to look into this, in the meanwhile, use market link below)
Will be added Later:
Governers
I/O Schedulers
Overclocking
Auto-rooting

Note: This kernel's ramdisk is ro.secure = 0, which means it can be rooted, you'll just have to do the work.

Update 2012 February 08 -- 1900

Attached boot.img

Update: 2012 February 12 -- 2020

Big update to the kernel
I switched from my ramdisk, which ended up being a headache to DooMLoRD's v10 ramdisk
That means:
Wifi Works
Autoroot (should) work (I haven't tested it yet)
Recovery Works
New Splash on boot (thanks [URL="http://xdaforums.com/showthread.php?t=1494076"]KeiranFTW[/URL] )
What I've added:
Overclocking is possible up to 2.0ghz (be warned, I have not had a chance to completely test it out, and my device only works up to 1.6ghz) (Freqs are from DooM v10)
Governors added:
brazillianwax
smoothass
smartassv2
savagedzen
interactivex
lagfree
Scary
smartass
Original governers

UPDATE: 2012 Feb 12 1055

Noticed that when I switched to DooMLoRD's ramdisk, autobrightness got re-enabled. Fixed that. Uploaded new kernel.

UPDATE: 2012 Feb 13 1335

Changed version from .2 to 1.0

Added IO Schedulers:

Anticipatroy

CFQ

V(R)

SIO

UPDATE: 2012 Feb 13 -- 1400

Realized last update unintentionally removed governors, as soon as I get a stable internet connection, i'll upload completely working kernel.

UPDATE: 2012 Feb 13 -- 1525

Uploaded fixed kernel.

Note: I am not to be held responsible if your device fails you. By flashing this, you are taking your device's ability to work into your own hands. ESPECIALLY WITH OVERCLOCK. TEST BEFORE YOU DECIDE TO SET ON BOOT. IF YOUR PHONES FAILS YOU, IT IS YOUR RESPONSIBILITY

Follow these instructions from Doom if you don't know what to do

download the boot.img

save the boot.img in the folder with fastboot binaries (fastboot.exe files)

power down device

start device in fastboot mode

use the following command to flash the boot.img

fastboot -i 0x0fce flash boot boot.img

reboot phone and enjoy the kernel

What's Left to be added:

What do people want?

To get into recovery, use the exact same key as you would on DooM's

Sources for code:

Github -- Ramdisk (From ftf, if you really want to mess with this, have fun, but it's not worth the time.): https://github.com/paxchristos/R800x-Ramdisk

Github -- Kernel Source: https://github.com/paxchristos/R800x-2.3.3-Kernel

Big thanks to Keiran/Doom for the help in getting this to work.
[Xperia Play Android Development] paxChristos:
Reserved for future use
[Xperia Play Android Development] CrimsonKnight13:
Any modifications regarding I/O schedulers & CPU governors? Any additional kernel modules?
[Xperia Play Android Development] paxChristos:
There well be, as of right now, this is pretty much an alpha release. I'm in class for a little bit, then I'm going to actually flash it (

I just did a fastboot boot) and start bug checking ...
[Xperia Play Android Development] ozzmanj1:
I'm game for trying it out.
[Xperia Play Android Development] Cl8rs:
With this kernel we can overclock? Like with SetCPU? :D
[Xperia Play Android Development] DubleJayJ:
I'll try this later when some other stuff is fixed. But nice job.
[Xperia Play Android Development] PariahLantern:
Is this a kernel for 2.3.3?

What's to prevent you from grabbing sources from a later version and doing this?
[Xperia Play Android Development] nickholtus:
i think this kernel is for unlocked bootloaders???

Because locked can't flash kernels
[Xperia Play Android Development] Selim873:
There can be kernels that can be flashed with CWM Recovery.

I'm SOOO ready to test! Hit me with your best shot! :D

EDIT: Do you think this kernel will eventually evolve into a kernel that will be able to boot Cyanogenmod and/or MIUI? I'm assuming that's what you're aiming for. lol
[Xperia Play Android Development] nickholtus:
Nope we can't flash kernels with cwm on SEMC devices
[Xperia Play Android Development] paxChristos:
I have a R800x (the Verizon Xperia Play) and I play to focus development on sources exclusively for the R800x. If the R800x gets new sources, I will update code based on that, not sources for GSM.

You are correct sir, I was updating between classes and posted the wrong info *fixed*

Sorry, only for unlocked boot loaders, my bad

Eventually I might get into other development. First I wanna get this working, perfectly.

Yupp, the /boot partition is locked so we can't flash kernels that way

(hint: if you do (from terminal emulator as root) cat /proc/mtd and you see /boot, you can use CWM to flash kernels.)
[Xperia Play Android Development] paxChristos:
Kernel v.1 is uploaded and attached to post 1
[Xperia Play Android Development] DubleJayJ:
Probably. We are gonna end up finding another exploit.
[Xperia Play Android Development] DooMLoRD:
nope u cant see /boot and it cant be flashed to using CWM (on xperia devices)
[Xperia Play Android Development] KeiranFTW:
Couldn't we not "find" the boot partition values and then mount the boot partition? Would require a little kernel editing but would be well worth it.
[Xperia Play Android Development] Selim873:
I didn't think about that! I would love to try to get at it, but I'm only a user and know nothing of development... I'm sure that'll get cracked eventually. ;)
[Xperia Play Android Development] paxChristos:
The only problem (that I can see) with what Keiran is suggesting is that the you'd need a custom kernel to affect the /boot partition, which once again, makes it useless for anybody with a locked bootloader...
[Xperia Play Android Development] Selim873:
I understand that, but since it was based off the stock kernel, would the values be the same for everybody with a locked bootloader? I know that you meant when you said that, but what I was thinking was that someone could dig around the kernel to find those values and what trigger the /boot partition in the first place, then use the correct adb shell command, whatever it is, to make that show up on locked devices. Whether the device is on it's recovery mode (Back+Power) or fastboot (Search+Power) state. Like I said, I don't know anything about developing, and I might just be walking off a cliff at the moment, but it's just a thought.

EDIT: As in looking and thinking on the modified "stock" kernel, and applying on the locked devices. Trial and Error.
[Xperia Play Android Development] paxChristos:
Just a quick update,

I'm trying to get the overclocking working, but right now it's being a stone cold b*tch with compiling

As soon as I get it working, i'll upload a new kernel version
[Xperia Play Android Development] DooMLoRD:
we already have those values... but it doesnt work..

currently we have no other way to flash kernel to main boot partition other than FASTBOOT!
[Xperia Play Android Development] KeiranFTW:
Fair enough?

How about putting zImage and ramdisk into kernel.sin then signing it and flashing via Flashtool, would work on LOCKED bootloaders?
[Xperia Play Android Development] paxChristos:
Signing it involves Sony's key (if I remember right) ... I'm pretty sure the encryption for that hasn't been broken... Ever...
[Xperia Play Android Development] KeiranFTW:
I think it has :)

Because, there are kernels floating around for the X10 that can be installed if bootloader is locked, correct me if I am wrong.
[Xperia Play Android Development] paxChristos:
BIG UPDATE, check the changelog in the OP. Kernel attached to op.

Pax
[Xperia Play Android Development] paxChristos:
Fixed Autobrightness turning back on with using DooMLoRD's ramdisk

@Keiran & Doom

In the ramdisk I have for 2.3.3, init.semc.rc has a line

(63) chown system system /sys/class/leds/lcd-backlight/als/enable

I noticed that when this is applied to DooM's ramdisk, it disables the als ... I'll try to pull apart the 2.3.3 source and see where it leads, but i'm curious if this works on the other devices
[Xperia Play Android Development] paxChristos:
Another update: IO Schedulers added. See op.

Anybody want anything else added into this kernel?
[Xperia Play Android Development] KeiranFTW:
You can also use "echo 0 > /sys/class/leds/lcd-backlight/als/enable", I put it in a script in init.d folder when I was using CM7, you could probably put it in one of the scripts in the ramdisk :)
[Xperia Play Android Development] ozzmanj1:
I am on a R800x rooted with unlocked bootloader (obviously) and I flashed the kernel from today, wiped my cache, and flashed the kernel. My phone bootlooped a couple times. I pulled the battery, then tried again. Booted fine but when it was fully loaded up the screen would go dark and then not respond to any buttons presses. It was just a black screen. I was able to get it to stay lit up once but the touchscreen was all unresponsive, not sure why its getting all bug-eyed. Any ideas?
[Xperia Play Android Development] paxChristos:
Right now I'm looking into an issue with gapps crashing, where the screen turns off and after a short time period you can turn it back on... If you get it to happen again, could you logcat it for me?

(abd logcat -v long > crash.txt)

you can email that txt file to nielson.peter@gmail.com and I'll look into it.

Note: you'll have to press ctrl + c to stop the log.
[Xperia Play Android Development] KeiranFTW:
Did you get my PM?
[Xperia Play Android Development] paxChristos:
Do you have V6 installed? So far that's the only way I've managed to get boot loops...
[Xperia Play Android Development] Schwabie64:
This is great man, haven't ran into any problems yet. Keep up the good work.
[Xperia Play Android Development] zektor:
Couple of Q's:

What is the "-i 0x0fce" fastboot switch for? Normally I flash using "fastboot flash boot boot.img"

After kernel installation, is it necessary to install wifi modules? Right now I am using Doomkernel v01 and v01 wifi modules. Do stock modules have to be reinstalled after kernel installation?

Thanks btw for a CDMA kernel for 2.3.3. Not many in existence ;)
[Xperia Play Android Development] paxChristos:
The -i 0x0fce is the vendorID for Sony (Ericsson) Mobile, on linux it's necessary (not sure about windows, I don't use it too often.)

If you're coming from Doom's you need to use the stock wifi modules he included in his first post.
[Xperia Play Android Development] zektor:
Just tested. Bootloops with Darkforest 3.0.5 CDMA rom.
[Xperia Play Android Development] paxChristos:
Yupp, that's because it's meant for .88 firmware (only.) DF 3.0.5 is based off .145.

Sent from my phone, please excuse any Swypos.
[Xperia Play Android Development] zektor:
Aha! Thanks!
[Xperia Play Android Development] lightningdude:
I'm running Ubuntu 10.04 and I've never used -i 0x0fce. Everything seems to be working fine for me.
[Xperia Play Android Development] KeiranFTW:
You have udev rules set up and a different version of fast boot. Some versions have the -i vendor option, some don't.

I also have udev setup, but I used to have to use the -i option
[Xperia Play Android Development] zektor:
Do you know of any custom roms based off .88? Or is there only 2.3.3 .88 stock available out there?
[Xperia Play Android Development] paxChristos:
Gbtweaked, Cola & IT-ROM & I think one more...

Sent from my phone, please excuse any Swypos.
[Xperia Play Android Development] savage24x:
Why should I use this instead of DooM's?
[Xperia Play Android Development] paxChristos:
At the time it was filling a void left by Doom & Keiran, both of them were using .145 sources (iirc) and that (atleast for me) caused the back button to fire multiple times, as well as autobrightness was on in their kernels (in mine it gives the user the choice under display -> brightness)

The downside is that it only works with stock (.88) based Roms, so Darkforest CDMA & UKCDMA doesn't work (because iirc, they're based off .145 sources)

Pax
[Xperia Play Android Development] zektor:
I see the big benefit here (unless I am wrong?) in:

1. Can run stock Verizon rom with this kernel and have root and recovery

2. Brightness option available

3. Overclock with stock rom

I am sure there are more, but I am happy for those. I will try this tonight with stock verizon 2.3.3
[Xperia Play Android Development] zektor:
Not sure what I am doing wrong here. I used the FTF and went right back to stock Verizon .88 rom. That went through without a hitch and I was back to stock. I have unlocked bootloader of course, and was able to enter fastboot afterward and flash your kernel. Reboot and it still bootloops on your splash image. Funny thing is that when I hooked up up USB and left flashtool open, flashtool connected to it after your splash image and installed busybox, superuser, and then it went forward to android logo and into the phone.

I checked the setting and I was indeed on your kernel. I reboot...same loop deal. Only way to actually boot into the phone is to connect to USB and have flashtool open ;)

I also could not access recovery using the same key as Doom (search key) either. This is all on a CDMA r800x. Any ideas??
[Xperia Play Android Development] paxChristos:
Honestly I have no clue, so far I've had two people telling me it bootloops, but every time I've used it, it works (mind you, I haven't touched the kernel since I've been running CM9 :p)

Sent from my phone, please excuse any Swypos.
[Xperia Play Android Development] savage24x:
I see. What about touch recovery? When I turn off Auto-Brightness, it actually turns off for me. I don't see why it doesn't work for anyone else... I literally do not have any problems with it not shutting off. No matter the kernel. Even stock it works fine.
[Xperia Play Android Development] zektor:
Yep, I tried with stock rom, IT rom, Cola rom...just to rule out a rom issue. It simply bootloops. I CAN however get it to go all the way in provided I am connected USB and Flashtool is open....heh.
[Xperia Play Android Development] netizenmt:
Fyi, it would only bootloop for me as well.
[Xperia Play Android Development] chery2k:
Does anybody how to get past the bootloop?
[Xperia Play Android Development] Firehead:
Would like to know as well, for future reference. Managed to get past the bootloop somehow. Dunno what I did.:confused:
[Xperia Play Android Development] Radon_22:
I'd be inclined to agree. As far as I know, the only other CDMA GB kernel is DoomLord's? DL's kernel seemed flakey when it came to wifi, so some of the new r800x owners are probably going to be grasping at straws a bit.
[Xperia Play Android Development] chery2k:
FYI: I didnt get past the bootloop, sold the r800x a long time ago.
[Xperia Play Android Development] abdel12345:
Search more there's a stock 2.3.3 kernel with overclock that works. It was the first kernel I used

Sent from my Xperia Play (r800x)
[Xperia Play Android Development] darkharbinger81:
This kernel works for me except wifi says error :(
[Samsung Galaxy Nexus] kronusx12:
Is there any way I can send messages to google talk users from go sms pro? I really like go sms and find it annoying tip use 2 different apps to send texts. Thanks for any help or thoughts
[HTC Sensation] aygul12345:
Best dear Xda members,

I was wondering how to put S-ON if you rooting your phone (s-off)

I know about the Desire you have a tool '' Unrevoked -forever S-on ''

With that you can put the S-onn if you have your phone rooted,

But wil it also works on sensation? and if not how to put S-on?
[HTC Sensation] Snake_skw:
you have to carefully follow step 5 in this thread

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

there's a possibility of bricking your phone if you dont exactly follow those instructions
[HTC Sensation] aygul12345:
Thanks buddy, for your quick reply ;),

Can you copy and paste the steps on this post please?
[HTC Sensation] Snake_skw:
Here you go,but i highly recommend that you read the entire first post and familiarize yourself with certain expressions and terms used here,it will be easier :)
[HTC Sensation] aygul12345:
Thanks again mate! :D,

Can you explain it a little easer to me...

Because it says in the steps ... that if you on a CUSTOM rom...

But what if you on the Officeel HTc sensation rom 2.3.4 example

Because the steps are not very clear...