yashsingh1/xdaforums huggingface dataset:
[T-Mobile myTouch 4G Slide] strapped365:
As long as your s-off just flash the kernel right?

S-on you need to fastboot flash the boot.img so the kernel and modules match up. I use a different zip then whats posted here to flash my kernel. These zips seem like their built funny and it was taking the kernels I've compiled like 9 minutes to boot. I would ask if you wanted to test it out but i not exactly sure if your results would differ, but pm me if your up for it
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] potsykate:
I have been trying to root and install the latest cwm and a custom rom to a galaxy tab wifi only uk version.I rooted and installed 5.0.2.7 cwm and a rom but when i rebooted it there was a password needed which i didnt have.It was a P7500 K11 restock rom if that is of any use.I would like to either go back to unrooted or just flash another rom but without usb mode i cannot copy another rom across to flash via cwm.

What would be the best method going forward for me now?

Thanks
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] BroBot175:
look up a tutorial on how to set up adb

im pretty sure you can trasfer stuff accross to your tab when your in cwm using adb :)
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] Benzoman:
Edit: that password needed is what you see when following the info below but forget the last step of doing the factory restore or reset, whatever it's called. ;)

don't know that you need to go this far but below is my standard reply to posts like yours. hope this helps. :D

It's helped me and I've seen it help many others too.

Goto http://www.teamovercome.net/p7500/?page_id=5

Towards the bottom of the guide There is a section called Restocking yer system.

Follow that on down.

Make sure you use the files for you device (7500 or 7510).

Make sure you triple check that you follow everything as suggested. The most common one I see missed is the last step of doing a factory reset/restore.

Let us know how it goes, as this keeps us trying to help when we know we're successful. ￼

Also if you have any issues come up that you can't figure just ask. ￼
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] potsykate:
Thanks for that,I finally managed to get it back to stock and I'm going to start again.Strangely enough I find this tab harder than my HD2 to mod with WM7 or Android even my new galaxy Nexus gave me less problems than this tab.Lesson learnt tho,,,read then read again !!!

Thanks
[AT&T Samsung Galaxy S II SGH-I777] Jadefalkon:
I've turned into a semi flashing addict trying a different rom each week. Recently I started to use the Seidio 3200mah. Is it safe to do flashing with an aftermarket battery installed, or more specific an extended battery? I read where a guy mentioned he accidentally had one in while flashing a rom and was just wondering is there a danger in doing that.
[AT&T Samsung Galaxy S II SGH-I777] Waddle:
As far as I know there is no dangerous from flashing with a different battery. I do it all the time. There is no reason for anything bad to happen because of a different battery.
[AT&T Samsung Galaxy S II SGH-I777] Jadefalkon:
Thanks, I'm getting ready to try Shostock and it was a pain getting the back cover on perfectly with this battery.
[AT&T Samsung Galaxy S II SGH-I777] R6Blitz:
Went from UnNamed to ICScrewD about a week ago with the same battery as you, no differnce from stock battery.
[AT&T Samsung Galaxy S II SGH-I777] jeffsmith01:
I can also verify that the extended batteries work fine. Have done many flashes and used odin a few times and it all worked flawlessly.

Sent from my Samsung Galaxy S II running ICScrewD.

Via XDA Premium
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] papul:
Hello,

I am pretty much new to Android. Bought my phone a few months ago. Rooted it but haven't unlocked the bootloader yet. ICS seems to have fulfilled most of the shortcomings with the Android OS. And I am willing to install it to my phone. But I am very confused as to which ROM should I choose. ASOP or the FreeXperia FP110 ROM. Which one of them is more stable?

Also I would be very thankful if some one gave me the links guides explaining how to unlock the bootloader and install a custom ROM and also backup everything before installing it.

(since I am a very new member to the forums I couldn't search for previous articles mentioning my very question. So please don't get annoyed if I posted a question that has been already discussed.)

Thanks.
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] zummer22:
I would go with this one http://xdaforums.com/showthread.php?t=1434001

Because it has less bugs and feels more stable. You can PM me if you need some help ;-)
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] urra901109:
Aosp one has less bug.. if want to go and fool around, i would choose the aosp... :p but one thing you might want to know as it is not clearly stated on the "bug list". i think both release plays video, but more like a slideshow rather than a video (im talking about 1fps). :D they're still working on it. that's the only downside that cause me to switch back to GB. sorry, not to discouraged you. even with the bugs, i recommend you to try both if you had free time to spare.

as for unlocking bootloader i would suggest the guide on sony's website. quite straightfroward http://unlockbootloader.sonymobile.com/
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] whalesplaho:
First Update yur Phone to Latest Firmware den install Titanium Backup & use it to Backup yur Rom/Files....

Secondly, Unlock BL & Root yur Mobile..... Unlocking BL-> http://androidflip.com/unlock-xperia-phones-bootloader-without-losing-drm-data-track-id-working/

Lastly, choose a ROM to use... sorry am an SK17i user!
[HTC Sensation] cryptstyling:
How can you see if your phone is bricked???

Is there maybe a way to unbrick it then???

THX 4 helping
[HTC Sensation] dexter93:
Can you build a wall with it? If yes then it is a brick.

How about you searched before opening a new thread?
[HTC Sensation] pdagenius:
We are not clairvoyent - more info please. :confused:
[HTC Sensation] sshede:
1. Does it turn on, at all, no matter what you do? No? Bricked.

2. No, true bricks cannot be fixed. The good news, most bricks aren't bricks, they're "bricks". As in, super easy to fix.
[HTC Sensation] cryptstyling:
The phone turns on. After the HTC logo the screen stays white.

Is stil can get in the bootloader and recovery.

I tried to restore a previous back-up but the screen stays white.
[HTC Sensation] cryptstyling:
Nice comment. took a while to think about that???

Seriously, there is no search button right now so that i can't search for a related thread.

Don't comment if you ain't saying something usefull.
[HTC Sensation] rbeavers:
Sounds like you can flash a rom. Your not bricked.
[HTC Sensation] moshe22:
Just to let you know if you are able to get into bootloader then is not bricked.

Bricks are only if the phone cannot power on. No signs of anything, then it's a bricked.

Yours is not a bricked
[HTC Sensation] cryptstyling:
I flashed a lot of roms so i know how all of this works here.

But when i try to update my cousins phone this happens.

Is the first time that i ever see something of this.

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

After an hour staying on the white screen the phone started all sudenly.

Now everything works like a charme again.

Guess that there was some kind or bug or something.
[HTC Sensation] moshe22:
Place this in your ad card root http://db.tt/ht4BPIS8 that's a cwm recovery.

After that power off your phone, take out the battery and then re insert it.

Once you do that, hold down the down vol key then hold down the power button.

You will get to the bootloader

Select recovery

Restore your Nandroid or flash ROM

Sorry for the un organize post but I'm writing on my phone.

Let me know how that goes
[HTC Sensation] moshe22:
Oh nice
[HTC Sensation] dexter93:
You opened a thread asking for help without explaining what's wrong. Also the sticky threads have all the info you need. There is a thread called "help" for such questions. You are not bricked, you are in a bootloop, flashing a rom will fix it.

I don't see the reason why you should had opened a thread. The same answer has been answered about a hundred times by now. Look at the top of your browsers window.. there is the SEARCH field. Use it next time

Damn. I accidentally thanked that post
[Verizon Droid Incredible 2] Kayak83:
I think the ICS keyboard is a step down from the Sense one. The keys seem smaller and I constantly hit the "v" instead of the space bar. Is there an apk anywhere I can flash or some better mods/app recommendations?
[General Questions and Answers] akkelaro:
I have a 2gb micro sd card 130 mb intern memory and 18,16 sd intern what is tha sd intern? and can not root..
[General Questions and Answers] BioT3rm:
Maybe you should

You wasted an entire post to just say that?
[General Questions and Answers] TeeJay3800:
Bringing up a 5 month old thread just to ask an unnecessary question is even more pointless. Closed.
[Epic 4G Accessories] Jbluna:
I've been thinking about getting myself an Hdmi Mhl Adapter for My Epic for awhile, so I'm currenty on the look out for one at tjhe moment. Has anyone here bought themselves one of these and worked well enought? Also, what dictates the tv compatibility of these things? I've heard only certain ones work with them.
[Epic 4G Accessories] MikeEx:
The Epic is not MHL capable.
[Epic 4G Accessories] irule9000:
STOP!!!!!

DO NOT BUY THE MHL IT IS INCOMPATIBLE we haven not gotten tv out working yet. The dev came back a month or two ago after being gone for a year. He had a terrible accident I believe. I havnt seen him on since. Either way dont buy mhl.
[Epic 4G Accessories] Jbluna:
Well so much for that hope... there any other subsitutions for video out I could possibly use?
[Epic 4G Accessories] thomasskull666:
Nope :-(
[Epic 4G Accessories] TWO515TY:
Just to make sure, you have an Epic 4G and not an Epic 4G Touch right? If you have an Epic 4G, it is not MHL compatible. If you have an Epic 4G Touch, it is MHL compatible, but this is the Epic 4G section.
[Acer Iconia A500] mobilebone:
Hello

I have been having some problems with the main camera on the A500. It has different tints to it. Sometimes the picture seems to be divided in 4 and all 4 squares have a different hue to them. Restoring to factory settings seem to take care of it for a while. Initially I thought it was "skype" that messed it up, but it is not.

I just restarted the tablet and the camera is giving me a yellow tint, with a clear horizontal stripe about 3/4 inch wide through the middle.

The tab has stock 3.2 on it.

I was wondering if anyone has experienced similar problems and if there was a solution to the problem.

Thank you
[Acer Iconia A500] Moscow Desire:
Well, I would think the problem seems to be some app/apps you have installed. Based on when you do a factory reset, it goes away.

I would just do another factory reset. Then verify it went away. Run it for a couple of days WITHOUT installing any apps. This will probably rule out a hardware issue.

Then install apps, 1 at a time. Use the camera, and look for issues.
[Acer Iconia A500] mobilebone:
Thanx. I will give that a try.
[Acer Iconia A500] mobilebone:
I traced it back to Swift Key X keyboard for tablets. How is that even possible?

Also yahoo messenger is another one that ruins the camera. As soon as I install any of those apps and reboot, the camera is back to normal.

Does anyone out there use either of those apps?
[Acer Iconia A500] Moscow Desire:
So, everything is ok?

Rule #1,

Stay away from apps meant for phones.

Yes, they "may" have tested it it on "1" tablet, then gave it a clean bill of health. Maybe.
[Acer Iconia A500] mobilebone:
I thought it would be ok. But after restarting a few times, the camera colors are off. I'm going to root and install a custom 3.2 to make sure it is not the hardware.

Spasiba for all your help :))
[Acer Iconia A500] bullyspud:
any news about this problems.

it seems that my iconia has the same problem- i never noticed it because i dont use the rear camera.

i sold it it today and the guy who bought has described something like what you folks are talking about

the strange thing is that i had done a clean boot before i sold it, and the buyer hasnt installed anything on it yet.

im waiting to hear back from him after he tries another clean boot.

anyone else have any ideas ?
[Acer Iconia A500] danc135:
I'm having the same problem. I don't use it much, but the camera was ok before. When I tried using it this weekend, it showed colored translucent squares on the sides. It is not a config problem, as there are no effects turned on. The front camera works 100%. I will post a sample when I get home.

If I change the "whites" config to Incandescent, it kind of solves the problem. Sometimes, the squares appear, but not for most the time.

I believe this is not a harware issue, unless that whites configuration is made with hardware (highly doubt it). I don't have Swift key, or Yahoo messenger, or any other apps that use the camera (other than Skype, but it was already installed when the camera worked).

Did anybody find a fix to this? It seems it is only a problem on stock 3.2.

Edit: not an exclusive 3.2 stock issue, it appears that custom roms have this problem as well.
[Acer Iconia A500] ale1975br:
I have the same issue after ICS ota upgrade...

Any ideas?
[Acer Iconia A500] danc135:
I haven't had the issue since the ICS upgrade. Only tested once or twice, but it is working properly.

What I did to partially fix it was changing the White Balance to "Incandescent".
[Eee Pad Transformer General] feisty_noodle:
A few days ago Koush published his new CWM recovery v.5.5.0.4 for TF101.

Many (most?) of those who flashed it are experiencing trouble booting normally:

the device goes straight into CWM recovery unless you cold-boot by holding the Vol(-) key at boot time.

This thread is meant to support those who are in this situation.

Also, this thread is to warn others not to flash CWM 5.5.0.4 for the time being.

Also, also, this thread is to gather information that will help devs to fix our problem.

Note:

The previous thread found here got locked (I was told) because of FUD and general lack of clarity.

Please keep it clean and flame-free.

If you are new to Android and TF101, please refer to good guides such as this one:

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

You can save yourself from much trouble by educating yourself a little.

UPDATE:

If you have 5.5.0.4 installed and have not used any apps for booting into recovery you likely don't have the problem described above.

We now have two reports of being able to successfully flash an alternate recovery and escape 5.5.0.4

See posts #3 and #67.

UPDATE2:

See post #3 for continuing contributions from @gee one (thanks!):

http://xdaforums.com/showpost.php?p=23257966&postcount=3

UPDATE3:

There is some progress. More testing to be done ...

Money post: http://xdaforums.com/showpost.php?p=23301594&postcount=105

UPDATE4:

We have a solution courtesy of @gee one and @leetlikeawping and the fearless tester @trtk.

This solution does NOT involve NVFlash or has anything to do with the boodloader, so it should apply to all SBK versions (and SN's).

There are comments from people with B70 and B80 (as well as below) reporting success.

The repair can be done in several ways. I have tested the scenario of when you cannot cold-boot into the system, but have a correctly set-up adb access.

(If you entered the shell, don't forget to exit at the end.)

Now you should "Reboot system".

When rebooting, you will notice the ASUS splash screen with a blue progress line. This indicates that the /staging partition got picked up and is being processed (i.e. your payload is being flashed to the recovery partition).

When you next boot into recovery, you should NOT see the 5.5.0.4 screen.

Continue by flashing your ROM if you need to.

Word of the day: teamwork. Peace!

UPDATE 5: Roach2010 published a fixed version of CWM v5.5.0.4

You may find it here. You still need to clear the boot-recovery flag by following the procedure described above or using the command line, as explained by Roach2010 here.
[Eee Pad Transformer General] feisty_noodle:
My personal observations so far are that, after flashing Koush's CWM 5.5.0.4, I cannot replace it with any other CWM's I've tried (roach, solarnz, using the RecoveryInstaller app).

The available recovery blobs get written to the staging partition (mmvblk0p4) but appear to not be touched on boot.

I have the 9.2.1.11 bootloader on B70 with SBK v.2
[Eee Pad Transformer General] gee one:
I flashed both ways and got stuck not being able to flash using the staging partition, which is the typical way to reflash recovery. So if you flash this, there is no way to unflash it. I think it also uses a different sdcard mount, so it makes it a little tougher to get a fresh zip to flash onto there.

When it's working normally, cwm will flash to the staging partition on reboot. When it's recovery bootlooping, the flash to staging will be skipped, which makes it difficult to flash a new recovery. I looked at the init.rc files and noted that the cwm 5.5.04 version doesn't even touch the staging partition, so it will be ignored completely.

I did have success reflashing a full rom- EBT, LNX, SOS, and APP or bootloader, boot.img, recovery, and system. This might work for others too, although I never had a problem of always booting into recovery. If it boots into recovery after flashing a full rom, then it might not work since we'll be stuck with the same init.rc.

I don't know all the inner workings of what happens at the boot process, so does anyone have any ideas about what is causing this.

Some things I found out:

to mount the internal sdcard so that you can push a new rom- use adb shell

mount /dev/block/mmcblk0p7 /data/

ls /sdcard/

exit

then from your pc, type:

adb push /path/to/your/rom.zip /data/media

There are other ways too- I think cwm will mount data when you try to flash a zip from the sdcard.

Here's the init.rc's

part of 92111 stock recovery init.rc

on early-init
start ueventd

on init
export PATH /sbin
export ANDROID_ROOT /system
export ANDROID_DATA /data
export EXTERNAL_STORAGE /sdcard

symlink /system/etc /etc

mkdir /sdcard
mkdir /staging
mkdir /system
mkdir /data
mkdir /cache
mkdir /btmac
mount /tmp /tmp tmpfs

mount ext4 /dev/block/mmcblk0p1 /system wait
# mount ext4 /dev/block/mmcblk0p1 /system ro remount
mount ext4 /dev/block/mmcblk0p2 /cache wait nosuid nodev
chown system cache /cache
chmod 0770 /cache
mount ext3 /dev/block/mmcblk0p4 /staging wait nosuid nodev
chown system staging /staging
chmod 0770 /staging
mount ext4 /dev/block/mmcblk0p7 /data wait nosuid nodev
chown system system /data
chmod 0771 /data

part of cwm init.rc

on early-init
start ueventd

on init
export PATH /sbin
export ANDROID_ROOT /system
export ANDROID_DATA /data
export EXTERNAL_STORAGE /sdcard

symlink /system/etc /etc

mkdir /sdcard
mkdir /staging
mkdir /system
mkdir /data
mkdir /cache
mount /tmp /tmp tmpfs

mount ext4 /dev/block/mmcblk0p2 /cache wait nosuid nodev
chown system cache /cache
chmod 0770 /cache

---------- Post added at 01:53 PM ---------- Previous post was at 01:18 PM ----------

Does mounting and clearing/formatting cache do anything for anyone stuck in the recovery loop?

I thought this issue popped up before too- are we reinventing fire?
[Eee Pad Transformer General] sandiegopaneraiguy:
Same specs here, installed ROM Manager via market, purchased premium ROM Manager, installed recovery via ROM Manager.

I have attempted to restore to previous ROM using recovery and it restores system but fails data.

I have attempted the restore to stock and unrooted using the methods listed in XDA, and because it will not allow a reboot after flashing the factory unrooted firmware it does not work. I had actually seen mention of a soft brick if unable to reboot and thought that is what had happened. After flashing the factory unrooted firmware I was unable to cold boot.
[Eee Pad Transformer General] gee one:
I used the free version and I don't get the bootloops. Can you check something for me- in /sdcard/clockworkmod/download/ there will be a file there maybe something like -210115432

look around and see if you can find something like this:

{
"name": "Asus Transformer",
"flash_recovery": "dd if=%s of=/dev/block/mmcblk0p4 ;",
"version": "5.5.0.4",
"init": "init.ventana.rc",
"key": "tf101",
"lunch": "cm_tf101-userdebug"
}

These seem to be the parameters that cwm uses to flash the recovery. See if they are any different.
[Eee Pad Transformer General] pooh-bah:
Add me to the forced recovery boot list, but I have a twist to add. I flashed via Rom Manager and I'm running Revolver 4.0 beta 1.2.

Reboot #1 after flashing the new CWM 5.5.0.4 went as usual - no forced recovery

Reboot #2 also worked fine

Reboot #3 - I forced a shutdown, then rebooted fine

Reboot #4 - this time I forced a reboot into recovery, and now I'm stuck in the recovery loop unless I hold down the volume button.

So...until I booted INTO recovery, everything was working fine.
[Eee Pad Transformer General] gee one:
are there any recovery commands in your /cache or /cache/recovery folders?
[Eee Pad Transformer General] pooh-bah:
/cache is empty

/cache/recovery has one file, "last_log" - this appears to be a log of when I first entered the recovery about 30 min ago.

Regarding your question about /sdcard/clockworkmod/download/ - I see the same as you posted above.
[Eee Pad Transformer General] AlcoholicDoc:
I got the same thing as Poo-Bah.

Everything was fine until I booted into recovery, now that's all I can boot into unless I cold boot into android.

I'm on bootloader 9.2.1.11 on a B90.

I was wondering if there are any files that tell the system what to boot into and if those are something we can edit. Sorry, I don't have a lot of experience with android, but I'm willing to help as much as I can.
[Eee Pad Transformer General] gee one:
OK- I have recovery bootloops now. Does any one have them and isn't running on Revolver4? I did not get them with stock or team eos, but those roms don't have a reboot to recovery that works, as far as I could tell. I had to flash to Revolver4 to get them.
[Eee Pad Transformer General] AlcoholicDoc:
I'm running stock rooted.
[Eee Pad Transformer General] gee one:
Do you have any mods that allow you to reboot into recovery from the power menu?
[Eee Pad Transformer General] AlcoholicDoc:
Nothing. With the exception of being rooted and having CWM installed, I'm bone-stock. :(
[Eee Pad Transformer General] gee one:
Thanks, that helps. I had a stock-ish rom and I couldn't get the recovery bootloops. Very curious.
[Eee Pad Transformer General] kxs783kms:
Anyone think NVFlash CWM will work? I have a B50 model that can take NVFlash, I just don't know the exact steps of getting it done. I downloaded the NVFlash CWM. Do I just throw that into the nvflash folder and go from there?
[Eee Pad Transformer General] AlcoholicDoc:
NVFlash should be able to fix this issue. Use one of the tutorials to unbrick to stock with NVFlash. Then re-root. You'll be fine

I wish I had a B50, I'd be done with this crap already. :(
[Eee Pad Transformer General] kxs783kms:
The good news is that there is just the recovery.img nvflash, so I don't have start from stratch with my rom. The bad news is that the link to download the NVFlash folder keeps telling me to check back later. :/
[Eee Pad Transformer General] ShadowZephyr:
I'm in the same predicament and want to try the same thing as you. Could you provide a link to the Recovery only NVFlash thread please? I've tried to search but cannot find the one you are talking about.
[Eee Pad Transformer General] kxs783kms:
Can anyone link me to another NVFlash download for the Transformer, other than the one going through the AndroidRoot.mobi website. That one leads me to a FileFactory link that download it, but it appears to not be working at the moment. Thanks.

---------- Post added at 06:06 PM ---------- Previous post was at 06:04 PM ----------

Here you go buddy, but it's not working for me(the files download link that is.) http://androidroot.mobi/2011/06/13/nvflash-on-asus-transformer/