yashsingh1/xdaforums huggingface dataset:
[Nexus S Q&A, Help & Troubleshooting] AllGamer:
try to download the ROM again

sounds like the zip file is corrupted
[Nexus S Q&A, Help & Troubleshooting] zephiK:
What version Clockwork Recovery are you using? Try reverting back to a older version or something.

Verify the ROM's MD5 Hash using HashTab (Google it)
[Nexus S Q&A, Help & Troubleshooting] hllywd:
I've tried several times with downloads and now the latest clockwork and the version prior.

Samething always aborts, can't verify signature. Tried manual and through rom manager.

When using rom manager is that suppose to do the whole install? Cuz that only gets me to the little droid and the triangle. I have to get myself into bootloader and continue manually from there.

Thanks

I Love The Smell Of Burnt Rubber Anytime
[Nexus S Q&A, Help & Troubleshooting] zephiK:
what's the latest clockwork recovery? ;) did you try 3.0.0.5?
[Nexus S Q&A, Help & Troubleshooting] hllywd:
Ya. The new ver is 3.0.2.4

I Love The Smell Of Burnt Rubber Anytime
[Nexus S Q&A, Help & Troubleshooting] donaldcaps:
Hmm... It sounds like clockwork isn't properly installed. ROM Manager should take you directly to clockwork recovery without you having to do anything.
[Nexus S Q&A, Help & Troubleshooting] deeren:
the problem you are facing is that you are still on stock rom. so even if you flash clockwork recovery and then reboot to recovery, you'll always end up going to the stock recovery. this is a new feature implemented by google.

what you should do is...

1) go to bootloader

2)flash the clockwork recovery using fastboot

3)DO NOT reboot the phone or quit bootloader. immediately after flashing the rec. using fastboot, just enter recovery (through bootloader)

4)flash you new rom

just for u to have an idea. the recovery should be orange in colour.

option 2.

you also have the option of using a file manager with moun/root functions such as root explorer and rename the recovery script in etc folder but i guess step 1 is much easier for now.
[Nexus S Q&A, Help & Troubleshooting] hllywd:
OK I played alot today and this is what happened.

After fixing permissions and flashing the new CWM and wiping data/cache it finally worked. Unfortunately titanium and my backup didnt bring everything over. So I went back and forth between stock and CM7 several times but I just couldnt get all my stuff back in CM7. So I thought Id try the 2.3.3 update but not wiping stuff. That didnt work. Then I tried one more time with CM7 but not wiping. I couldnt get pastthe little CM7 droid on the skateboard. So went back to stock for now. Ill have more time on Sat to give things another try.

At least I can get in it now.

Any ideas/thoughts/

Thanks and sorry for the long post.
[Droid X Themes and Apps] dwjr82:
Can someone make or guide me on how to make s Puerto Rican based theme for gb dx

Droid X deodexed GB 2.3.3
[Desire Q&A, Help & Troubleshooting] dzumagos:
ok since im s-off i thought it would be a good idea to upgrade my radio

just to be super-sure.

i download the radio.img and put it into my AndroidSDK\tools

then go into command prompt and do 'fastboot flash radio radio.img'

and that is it ? same thing when flashing a new recovery ?

and another thing, i dont really get the RIL...

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

if i want to flash this radio (which is supposed to be the newest) is the RIL included ? or do i have to get it from where ? and do i flash RIL after RADIO flash or before ?

oh and last question, do i have to wipe all after radio flash ?
[Desire Q&A, Help & Troubleshooting] ijama:
RIL can be flash via recovery method...
[Desire Q&A, Help & Troubleshooting] dzumagos:
but how do i know if the RIL is included in radio, or do i have to get it from somewhere else
[Desire Q&A, Help & Troubleshooting] Meaple:
RIL is seperate to the radio therefore you get it somewhere else.

Quite a few questions on RIL tonight

Sent from CM7
[Captivate Q&A, Help & Troubleshooting] mirceani:
What is the difference (if any) between :

Froyo Baseband version I897UCKB1

and

Froyo Baseband version I897UCJI6

Thank you:confused:
[Captivate Q&A, Help & Troubleshooting] modest_mandroid:
One is from a buggy and leaked firmware, the other is the final build. Also, post your questions in the QA subforum from now on.
[Captivate Q&A, Help & Troubleshooting] cropythy:
This really belongs in Q&A not Development.
[Captivate Q&A, Help & Troubleshooting] PhillyFlyer:
Honestly, who stops to take the time and say "this really belongs in QA."

Who cares where it is? If it helps someone- then great.
[Captivate Q&A, Help & Troubleshooting] Andrewsc1:
For the sake of organization, and so we don't clog up the development forums with questions.
[Captivate Q&A, Help & Troubleshooting] DanDroidOS:
To not clutter dev section keep it in Q&A, but I agree these wannabe mods(trolls) need to shut there lame mouths and let the real mods handle it!
[Captivate Q&A, Help & Troubleshooting] Mr. Clown:
moved to proper forum.
[Upgrading, Modifying and Unlocking] scott7saunders:
Hey guys,

I am new of this forum and also to the world of Android, not too sure what to make of it yet but its early days.

Right, down to business, what can I do with the handset to perhaps tinker or modify it? purely from a software point of view. Rather taken by the idea of dual booting but I guess this is something that is not possible with this phone yet as the bootloader is probably locked.

Anyone offer a brave soul a few pointers?
[Upgrading, Modifying and Unlocking] jaberwockii:
Try a new ROM

If you want to tinker, try rooting the phone (voiding your warranty) and installing a new ROM. Cyanogen Mod 7 and Miui are amongst the most popular. Be prepared for lots of reading before doing anything, but it can be a rewarding experience.
[Optimus One, P500, V General] vin-ivar:
When I use the volume keys to change the volume, the bar is yellow in color. It's blue on the Xperia and green on the Galaxy Pop. Any idea how I can change it? Running void echo ROM.
[Nook Color General] getllamasfast:
My nook color recently got stuck on the boot screen for CM7 where the blue android text just chills out in the left corner. This happened right after my nook ran out of battery power.

I have gotten it to boot all the way into CM7 occasionally. However, it is not reliable at all, so I've tried to restore it to stock and reflash the whole thing.

I tried to do this by booting into recovery and then flashing the restore to 1.01 stock zip file, but when the nook rebooted it was still stuck on the android text. I have tried flashing everything related to restoring nooks, but to no avail.

I thought that maybe my CWR was broken, so I tried making a CWR sd card but even when I flashed the restore zip, my nook's boot still gets stuck on the android text.

What do you think I should try to do now?
[Nook Color General] cshehan:
You are able to boot into cwr though? If so have you tried downloading the stock image file again? Could be the file is corrupt.
[Nook Color General] getllamasfast:
I just downloaded it again and it still doesn't work.

I don't think that the problem is the zip files. I think that CWR is the problem since I've tried formatting /system and /data and tried repartitioning boot, but nothing happens...
[Nook Color General] getllamasfast:
I just tried to restore my nook to stock through ADB, but it still tried to boot into CM7. I guess that rules out CWR as the problem...

I also made an ext4 compatible CWR SD and tried the restore 1.01 zip again. This time I got past the android text and instead got to the grey android text from the rooted nook boot. However, it just sat there, stuck in a loop.
[Nook Color General] cshehan:
Odd, that even after wiping system and data that you'd have anything to boot into. You aren't leaving a bootable sd card in place are you?
[Nook Color General] getllamasfast:
I make sure to take out the SD card before rebooting.

Is it possible to check to see if CWR/ADB is actually writing to the correct partitions?

EDIT: I do not think that my nook is keeping any changes that I make to it...

I managed to boot into CM7 and I uninstalled a few apps and changed the max clock to 800mhz. Then I rebooted and eventually got back into CM7 and my apps magically came back and my max clock was reset to 1.1ghz. :(
[Nook Color General] cshehan:
okay that is very odd. Unfortunately I've never run into this or even read about it before. Hopefully someone here will be able to give you a tip that will help you fix this.
[Nook Color General] tuxhacker:
I've been having same issue for a week now. I tried everything I was able to find here but nothing is wokring. It seems like my nook became a read-only device. No matter what I do it goes back to previous stage.

I was running CM7 RC4 and system hung so I rebooted and that was it. It displays "Android_" on the bottm for about 10-15 sec and reboot.

I tried

CWR 3.0.0.5

- Repratition to stock nook.

- Getting error when I try to format system and data - I thought it was because CM7 was setting system to ext4.

- ADB and DD boot.img, System.img and copy Factory to mmcblk0p3

- Try to restore from back up I made

- Nothing works but goes back to boot loop

CWR 3.0.0.6 - One I got from CM7 install to emmc thread

- System format works

- Install latest nightly

- Restore from back up

- ADB can't find device - This is odd and couldn't find a way to fix it yet.

- Tried to install Stock zip but going back to CM7 boot loop

CWR 3.0.1.0

- Can't format data/system

- ADB to delete partitions and create them again but it doesn't help

- Tried all zip files to bring it back to stock - no go

- ADB to copy Factory.zip to emmc partition - umount and mount again then file I copied is gone.

- Deleted partitions and reboot but some how I got back to CM7 loop

I see people start to talking about CM7 boot loop issue. I saw this thread and man this is same issue I'm having! Let me know if you some how resolved this issue. I will do the same if I can find one.
[Nook Color General] getllamasfast:
Naw, I haven't resolved it yet... :(

I will post the solution if I do though!

Perhaps it's just a coincidence, but I am also stuck running RC4. Maybe there's some weird glitch in RC4 that makes the file system read only or something...?
[Nook Color General] cshehan:
I went from RC4 to stable with no problem. I did notice that CWR was not mounting the system and data partitions so I did have to do that when updating. Not sure why they aren't mounting automatically.
[Nook Color General] deadbot1:
From the Dummies guide link....Here...

First visit this link:

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

Download either the Rootpack, or the Clockwork Recovery image (1gb).

Next visit this link and download the 1.0.0 or 1.0.1 restore to stock files:

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

From this link you should also download the very last zip on the page. It is titled-flashable boot repartition zip. or something of the like. If you followed all these steps and still nothing, I would recommend flashing this as it can fix a completely screwed boot partition.

I had to use that last file after my hard crash. Seems that te /boot gets corrupted and tis seemed to fix it for me. After this you will probably need to do a full wipe and reinstall.

My order was...

rebuild /boot

reflash to stock

reflash to CM7

not sure why this worked...just did.

edit: just noticed my H key isn't always working...makes me type like a alf drunk brit..:o
[Nook Color General] tuxhacker:
I tried this too but mine didn't come back. :(
[Nook Color General] deadbot1:
Hmm. dunno. Maybe you can get samuelhalff to chime in...he was helping another guy out with something similar. searc in the threads for his name and your problem...wasn't to long ago.

edit---http://xdaforums.com/showthread.php?t=1022941 this was the thread I was talking about...doesn't appear they came up with a solution.
[Nook Color General] getllamasfast:
I tried all the things you suggested guys, but nothing worked...

Although I think I made some kind of progress... I tried to dd stock boot.img and system.img files onto my nook and now CM7 just bootloops instead of hangs!

Hopefully we can get this sorted out soon, or else I may try what one member suggested about microwaving it so that you can get a new one...
[Thunderbolt General] Magicadder:
I don't know if this is just an issue with me or if others are experiencing the same issue.

for some reason my proximity sensor is VERY sensitive... for example if I move my face just 1/2 and inch from the screen my screen turns on and I either press "Mute" or "Speaker" with my cheek OR i hang up on the person I'm calling when I place the phone back against my face.

This happens about 50% of the time... so every other call I make has this issue.

I don't know if I can change the sensitivity or the length of time before the screen turns on.

I'm coming form the Eris/D1/DX/Fascinate and I never had these issues with my older phones.

Any advice or Steps to fix this would be greatly appreciated.

Plz Advise
[Thunderbolt General] brent_strong:
Happens to me too, but I don't manage to hang up or mute the calls normally. I'd love a solution as well!
[Thunderbolt General] m00nshake:
Which kernel / rom are you using? I have heard that some kernels have caused proximity sensor issues but I'm not sure if the issue others have experienced is the same as yours. I'd try a battery pull first, if that doesn't help try a different kernel and see if that fixes it. If the issue still persists, it could be a hardware issue and you might have to get the phone exchanged under the manufacturers warranty.
[Thunderbolt General] Magicadder:
I'm using Stock firmware with bamf 4.3a Kernal

I've reset this thing too many times... installing different roms and such.. but I can verify that this is happening to another phone. My wife's phone does exactly the same thing. we purchased out tbolts on launch day ( if that helps )
[Thunderbolt General] MONKY_1:
The proximity sensor is located were the Verizon V is at

In between the big V is the sensor. Very hard to see go under a light a tilt the like you would if you want to find scratchs on your phone it really is between the V or I'm you can not find it. Make a phone call and get your index or any finger. And again make sure your under light and make the shadow of your finger go on top of the proximity sensor. Mine is very sensitive also.

-Monky_1

-Monky_1
[Thunderbolt General] calbruc:
My proximity sensor seems pretty touchy, as well.

I initially thought it to be a problem with a particular version of Adrynalyne's kernel, but I'm not so sure anymore. Adrynalyne also said that a kernel shouldn't affect the proximity performance -- that HTC puts these setting or whatever in the framework (what that means exactly, I'm not sure).

Anyway, I haven't done any exhaustive testing or anything, but I did notice one thing that seems to help keep my screen off is to have the thing pointed straight down while on the phone. My natural inclination is to have it along my jaw line, with the end pointed at my mouth. But the proximity sensor is to the left-of-center on the phone. Angling it moves the sensor away from your ear a bit. Assuming you've got it up to your right ear, that is.

I'd still welcome any other points folks might have about this.
[Thunderbolt General] Magicadder:
This is exactly what's happening. It's nice to see that I'm not the only one having this issue... even tho I'm sure it's annoying for everybody. Hopefully we'll be able to get some relief from this. :)
[Thunderbolt General] rizzomegav:
http://market.android.com/details?id=i4nc4mp.myLock.phone

This app keeps me from smashing my Droids.

this is not a signature I type it in every time maybe sent from my phone or my computer
[Thunderbolt General] Magicadder:
Would this work even tho the Thunderbolt has no physical Trackball or Camera Button?

Not to discredit this app Kudos to the Dev who wrote it, but it seems like a work around and not an actual Fix.

But I'll try it out and reply back with some feedback
[Thunderbolt General] dzigns:
Here's what I do and it works for me most of the time. When making or receiving a call, once the call is 'connected' I quickly hit the 'home' button so I'm no longer on the 'phone screen' & then the power button which darkens & locks the screen. Even if the proximity sensor allows the screen to light up, the lockscreen is still there and prevents me from muting or hanging up on the other person. It's not a perfect solution since my jaw has managed to unlock the screen & randomly open apps occasionally but it beats hanging up on someone every 5 seconds. ;)
[Thunderbolt General] gatorguy:
I'll just throw my hat in that I am experiencing the same issues of muting/hanging up on people. I don't recall having the issue on the stock ROM, but have really noticed it since I've been on BAMF 1.5 with Adrynalyn's 4.4.2 kernal included with BAMF 1.5.

I was running 4.4.2 with the stock ROM before BAMF 1.5 and don't recall having proximity sensor issues. Who knows?

Edit: Anybody think that screen protectors are causing interference in any way? I have an Invisible Shield that I've had since shortly after launch date.
[Thunderbolt General] g00s3y:
BAMF 1.5 is based on the new leak, which includes a fix for the proximity sensor. If the rom you are running isn't based on the recent leak for our phones, then you don't have the fix, and will most likely have problems with it.
[Thunderbolt General] gatorguy:
Check this thread out at droid forums! It fixed my "problem" with the proximity sensor. Simply blow out the sensor with air. Apparently dust gets in there and jacks it all up. I can confirm big time results with this method.

http://www.droidforums.net/forum/thunderbolt-tech-support/142050-thunderbolt-proximity-sensor-issue.html

Edit: All those kernel switches and setcpu tweaks over pocket lint!!! Damnitman!
[Thunderbolt General] rizzomegav:
Well the fix is only to hold the phone correctly unfortunately. My gf has no problem using either phone (hers or mine) but if I touch them its muted hang up bam.

One of my coworkers has the same problem as me another dosent. Its absolutely user errorish IMO.

It works with my thunder bolt sort of the home key still works. I don't mind it, moreso than buggered calls.

this is not a signature I type it in every time maybe sent from my phone or my computer
[Thunderbolt General] Jessesmith888:
A screen protector was an issues for me. The first one I put on did not fit perfectly, so the top of the protector cut directly threw the center of the sensor and collected dust and gave me some issues. The second one i used was applied from the top down to not obstruct the sensor. Solved my problem.
[Thunderbolt General] SDracis:
My phone sensor will black out when I am on a call and the phone is against my face, but when I pull the phone away the screen won't come back up for some reason..
[Thunderbolt General] electrofreak2k7:
I find that it seems to reflect off the arm of my glasses, which is kinda glossy like. When the IR LED reflects back at it, it seems to assume infinite distance. Same thing happened on my Droid.

There was also a case that lacked the cutout for the proximity sensor on the Droid... screen would never turn off because it reflected the IR.
[Thunderbolt General] c_live_lee:
I'm glad to see I'm not the only one with this problem. It's been happening to me for a few weeks now. I've run the majority of available ROMs and kernels (pre- and post- radio update) in multiple combinations so, I believe its safe to say they are not to blame.

I'm not using a screen protector so, that can't be to blame. And I don't have any scratches on my screen either. I'm curious about this dust theory though. It may be the best one I've heard yet. Has anyone else put the air hose to their Thunderbolt yet? I think I'm gonna give it a go asap. But, in the meantime, I'd love to hear whether anyone else has had positive results. If not, I fear I may have to move on to the glasses theory. I really hope it isn't that one though. I don't want to choose between having my Thunderbolt or my sight! ;)
[Thunderbolt General] mr.fatface:
Mine still does it and I'm using the leak , so I don't think there is a fix in it. If so it doesn't work. Locking the screen seems like a pain but that's the best bet for now.
[Thunderbolt General] Magicadder:
After trying many ways to work around this problem with the proximity sensor I have found that this is actually works the best .... And I can't thank you enough..... I've grown used to this method and so far its flawless.

Thank you again
[Droid Incredible Q&A, Help & Troubleshooting] tjrocks91:
Is there a method of creating an update.zip from a nandroid backup that you have stored onto your sdcard? can you take its contents and put it into an update.zip or something?

thanks!
[Droid Incredible Q&A, Help & Troubleshooting] kzoodroid:
Using the Android Kitchen you can create ROMs from backups. I haven't used it in about a year and only with the Eris but thats the way I did it a number of times. You can also take pretty much any ROM and modify it to your hearts content and create a personalized update.zip of that ROM of your own.

Android Kitchen thread

http://xdaforums.com/showthread.php?t=633246
[Sony Ericsson XPERIA X10 Mini] irontomrackham:
Hi Guys,

I hate to do this (1st post and a stupid question) but I have been searching a couple days now. So here it goes.

I have bought an x10 mini pro a week ago, but the Sony Ericsson flavor of Android is driving me mad (where the heck is the separate volume control for messages?). I would like to root it with a 2.1 Rom that is as close to the original vanilla android as possible. AOSP in other words :)

Other phones do have roms like this, my G1 is rocking with AOSP GB and I am happy with it. Is there such a rom for the X10 Mini Pro.

BTW, its a nifty little phone, but I never had a phone with a LONGER name :)
[Sony Ericsson XPERIA X10 Mini] x-peria-pro:
that would be awesome
[Sony Ericsson XPERIA X10 Mini] Eyama:
for mini pro u got 2 roms that works prfect maided by owain and they are CM6-Froyo, CM7-Gingerbread

sory for bad english
[T-Mobile LG G2x] BLiizz:
will the g2x ever get windows 7 ?
[T-Mobile LG G2x] nate420:
WHY WOULD YOU WANT TO?!?!??!?!

sorry for caps but i yelled that out when i seen this
[T-Mobile LG G2x] davehasninjas:
Haha, agreed!

That and is wp7 even capable of running on a dual core chipset yet?
[T-Mobile LG G2x] nate420:
i never even thought of that.. but like the OS now (2.2/2.3) they wont fully utilize the dual core without modifications...

i really see no benefit to run dual boot android/windows on a android phone

now when i had my HTC HD2 i ran dual boot... (windows/android) but still it was to slow
[T-Mobile LG G2x] BLiizz:
i love winodws 7 its a very fast ui :) and would be beast on a dual core :). well the thing is that i have the htc hd2 but im looking for a windows phone 7 running a dual core and crazy specs you know but i dont know what phone to get :/
[T-Mobile LG G2x] nate420:
yeah i can understand i got to try out the HD7 when it first came out for a few days... (customer loyalty) and it was very fast... now a quick question have you EVER owned a 1ghz andriod phone?

because if you have you will know that andriod is alot faster than windows... (windows phones does have some cool features)

i found this nokia dual core phone but im sure there will be some to come.. if you like windows vs andriod you'll just have to wait =(

http://www.nokiawindows.co.cc/nokia-will-have-in-2012-dual-core-devices/
[T-Mobile LG G2x] pakraider:
with the way things are progressing, we'll see things like VMware for smartphones soon enough, haha.
[T-Mobile LG G2x] BLiizz:
ya i love the facebook for windows phone 7 and plus all the new features coming aka mango update :) well the hd2 has been my only and first phone when i was running android it was pretty fast but i thought windows 7 was faster maybe because it isnt a legacy device :)
[T-Mobile LG G2x] peacekeeper05:
Not. Wp7 has hardware restrictions. They do not support tegra or any other dual core processors yet.