yashsingh1/xdaforums huggingface dataset:
[Optimus One, P500, V General] 25x8:
trying to find it too.

anyone please?
[Xoom Q&A, Help & Troubleshooting] jerses:
When i try to download files to my xoom sometimes it just dont download at all. It just stays there , if i get the notification of 100% then the file wont run and sometimes i get the file with the extension .htm i try renaming it to the original extension but cant run it.Sometimes i try to download files higher than 600mb and it disconect my internet. I dont know if its the main browser or do i need other app to make my downloads more easy. I dont have this kind of problem with my SE x10i so im worried . thanks
[Droid Incredible Themes and Apps] snapper915:
I am currently running cm7 7.0.2 and I love everything about this Tom but I can't find a way to mod or change how the battery and signal bars look. Are there any mods out there for this. If so please let me knw.
[Droid Incredible Themes and Apps] masully1984:
Try a different theme
[Droid Incredible Themes and Apps] SynisterWolf:
who's tom? lol ;)

here is a link to find themes that will work with CM7. Just make sure it says theme chooser and the theme should be an apk and not a zip

http://xdaforums.com/forumdisplay.php?f=527
[Droid Incredible Themes and Apps] snapper915:
Awesome thanks alot man.
[Droid Incredible Themes and Apps] michael2572:
Curiosity is getting the better of me too. Who's Tom?
[Droid Incredible Themes and Apps] snapper915:
Lol. I was meaning rom. Lol. I missed and hit the T.
[Droid Incredible Themes and Apps] k_nivesout:
The GB keyboard always auto corrects rom to Tom and roms to Rome. Kinda annoying.
[Droid Incredible Themes and Apps] snapper915:
Yes it is. Lol
[Droid Incredible Themes and Apps] Crans:
Switch to go launcher ex and try the honeycomb theme from the market its pretty cool, nice 3g, WiFi, and batt mod
[EVO 4G Q&A, Help & Troubleshooting] n00barmy:
I'm at my wit's end here. I've tried searching around (I rarely, if ever, post) and I can't find a solution to my problem so I'm gonna try here.

First thing's first, Device Specs (HTC Evo 4G):

SUPERSONIC EVT2-3 ENG S-OFF

HBOOT-0.76.2000 (PC3610000)

MICROP-041f

TOUCH PANEL-ATMELC03-16ac

RADIO-2.15.00.11.19

Mar 30 2010,11:24:04

Rooted with unrevoked3

Second, what I was running:

Cyanogenmod 7.0 happily running for about a week

What I was doing (at time of crash): Getting coffee... I left my phone on top of my computer (installed Go SMS Pro about 10 minutes prior), came back and it was boot looping from htc evo 4g screen to htc evo 4g screen to etc...

I have tried everything to get this thing running. All I have is fastboot and the bootloader, I can flash recovery using fastboot but they will not load up... I have tried the 3.7 RUU annd it will only detect my device while in fastboot, it runs through the update and acts like it was successful but it goes back to boot looping. I have also tried to do a nandroid restore using fastboot and I can flash every partition (system, userdata, recovery, cache) EXCEPT boot, where I get a FAILED (remote: image update error) message.

Also, I have tried using the eng-pc36img.zip file and the normal PC36img.zip file and, something interesting, it will update all of the files , radio v2, bootloader, system etc.. etc.., but when it gets to "boot" it will immediately shut off, boot back into the bootloader, reload the zip file and continue where it left off... Is it supposed to do that?

Anyways, that is my plight. I hope I've been descriptive enough. Please help and thanks you!
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
Well that certainly sounds no good man. It kind of sounds like your boot partition may be corrupted, so it's unable to write to that partition. You have already tried everything I would have suggested (RUU, RUU from fastboot, RUU from PC36IMG, tried reflashing recovery, etc). Your situation sounds identical to what people were experiencing in this thread, http://xdaforums.com/showthread.php?t=1009672, and unfortunately no one ever found a solution, other than replacing the phone. I wish you luck, and hope you're able to recover with one of the available RUU's or PC36IMG.
[EVO 4G Q&A, Help & Troubleshooting] n00barmy:
Oh well...

Well, shucks :(. I really wanted to be able to figure this out. I've tried and tried and tried and nothing seems to work. Oh, well thanks for putting my mind at ease. Sprint is already replacing it tomorrow. I just wanted to see if I could get this fixed now and be able to pass the information on to others who might be in the same situation. At least I was able to figure out how to downgrade from 2.10 to 0.76!

You don't know of any way of zeroing out the phone's partitions do you? Sorry if that is an odd request but I'm just brainstorming.
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
I apologize for the sour news, and wish there was a way for you to recover (maybe there is, but I'm just not aware of it). As far as zeroing out, or erasing all of the partitions, I'm not positive. I know you can do that using fastboot commands ( i beleve), but I don't have a ton of experience with fastboot, other than running an RUU. I'm sure someone else will chime in here and give you the fastboot commands to do that. It would be something like 'fastboot erase recovery', for example if you wanted to erase your recovery partition. I would google up on that a little bit, and see what all you can erase by using fastboot.
[EVO 4G Q&A, Help & Troubleshooting] n00barmy:
It's all good. Like I said, they're replacing it anyways, just more for my curiosity. Thanks for showing me that thread. Out of all the threads I looked at I, somehow, missed that one. I see y'all have been at this for a while and I will certainly be watching it even after I get my replacement. I guess I'll have to pull my battery doing a radio install...
[EVO 4G Q&A, Help & Troubleshooting] cordell12:
Sucks to hear about your phone :( For my curiosity could you please answer a question or two. A lot of people are chalking this up as a "user error" while others are thinking its CM7 (i dont). Then there is the logical one, to much flashing. I see you do not post often, but you know what to do to get out of a jam, most anyway. Did you flash your phone often, like every time a new rom comes out you would try it? Or more of a moderate flasher, stick to a main rom and flash updates, not counting nightlies. Nightlies would be extreme flashing, lol. Thats all, I am just curious on flashing habits, you did say up downgraded Hboot. I am assuming you did this after the bootloops to gain fastboot access, correct? Downgrading Hboot with the new larger partitions will brick a Evo real quick! Personally I am thinking the reason for the new partitions is related to this problem starting to emerge. If there is a way to "erase" everything and write new partitions via fastboot, those of us with older partitions can avoid this sudden death loop, and fix them for those who catch it...

Just a thought :)

Thanks
[EVO 4G Q&A, Help & Troubleshooting] dougjamal:
When did your problem begin? Was it after you downgraded from hboot 2.10? That is a tricky and dangerous feat in and if itself. Can you get to the bootloader screen?

UPDATE: If you can get to the bootloader, try reflashing amon RA v2.3. If you're successful, I would then reflash all of the radios including hboot 2.10 and then a rom...in that order.

posting & replying via the XDA Premium app.
[EVO 4G Q&A, Help & Troubleshooting] n00barmy:
My problem began last friday and no, I only tried the downgrading bit after it started looping. I wanted to be able to use the fastboot commands. Oddly enough, though. I just tried to run the eng-pc36img.zip again and now it did not immediately reset when trying to update "boot" but rather went through the whole thing... It still loops though...
[EVO 4G Q&A, Help & Troubleshooting] n00barmy:
Woah!

Now able to write to boot using fastboot flash boot boot.img...
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
Forward progress is good. So you were able to do that after the last RUU ran? You said it didn't skip over writing the boot.img that time?? However it still loops? Where is it looping at? THe splash screen, correct?
[EVO 4G Q&A, Help & Troubleshooting] n00barmy:
Yes, at the splash screen. It seems I can only manually write this one boot.img in my tools folder. Everything else gets a image update error in fastboot. I was not able to do that after the RUU because it changed my hboot to 2.10 (I think, don't quote me on that).
[EVO 4G Q&A, Help & Troubleshooting] irishgreen:
sucks

Damn im sorry to hear about this..i hope that as mentioned above it isnt from too much flashing!! Cause i am what i would call an extreme flasher..lol i flash just about every new rom that drops to try it out
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
I see. And yes, running the most recent RUU would indeed 'upgrade' your bootloader to 2.10.
[EVO 4G Q&A, Help & Troubleshooting] n00barmy:
I have a little more info. It seems that the only boot.img that flashes successfully through fastboot is the one located in the eng-pc36img.zip file. I cannot flash any from my nandroid backups from rom manager pro. I have not tried any other boot.img files from any other actual pc36img.zip files. I have another but that will set my hboot to 0.97.

Also, I doubt it is from too many writes. I am still fresh to rooting and I am not flash happy by any means...
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
I also doubt it's from writes. That would be a very hard sell on me. I have flashed hundreds of things I'm sure, between roms, kernels, mods, themes, etc. Probably more than hundreds, lol. I just dont see that causing it.

Keep in mind, that whatever hboot you were on when you created a nandroid backup, is the one you'd also need to be on when restoring it. Therefore, if you're using a boot.img from a nandroiid backup, then I'm fairly certain that you'd need to be on the same hboot as when you created the nandroid backup. I discovered this a few weeks ago, lol. Every nandroid backup I had made was created on .93 hboot. I then downgraded to the ENG. 76 hboot, and got careless and tried to restore a backup from when I was on .93 hboot. That did not go well, and resulted in me only being able to get to fastboot. Fortunately I still had recovery, so I had no problem recovering from that.

Anyways, I'm not sure what to suggest next, unfortunately. I will continue trying to come up with suggestions for ya, but for now I think it's pretty much trial and error for ya. I guess if you already have a new phone coming, you don't have much to lose by messing around with that one. I'm just not sure where to take it from there. I've been down that road, and I failed, lol. I just have no idea what prevents the RUU from running successful. Or even if it appears to be successful, it still yields boot loops. So I'm at a loss on what the actual cause of that may be.
[EVO 4G Q&A, Help & Troubleshooting] n00barmy:
Yeah, It's getting replaced so if you have any suggestions, go ahead. I'll try anything, I've got nothing to lose at this point. Maybe we can find a solution before I have to turn it in (hopefully). Thanks for the info on the hboot versions, I didn't know that. It makes sense though. I wonder if I can just switch the hboot from .97 to .76 in that one PC36img file I have and maybe it will run... Don't know but anyways...

Oh, I forgot to mention. I flashed an AmonRA v1.8 recovery earlier and while it didn't load it got farther than ANY other recovery I flashed. After the device shut down it said AmonRA v1.8 at the bottom of the black screen, for a split second, before it would go back into the HTC splash loop. It's not much farther but it worked "better" none the less... Anyways, just some food for thought
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
That is very interesting that you saw the RA recovery 1.8 at the bottom of the screen for a second. What hardware version is your phone? I believe 1.8.0 is only for phones with the older erase block size, which is hardware 002, and some 003. Some of the later 003 models were the new erase block size, which is 0040000. The old size is 0020000. If you're 0040000, 1.8.0 wouldn't work anyways.

As far as changing hboots go, if you're on 2.02 or 2.10 currently, you can't easily downgrade. If you're on something other than those, you should be able to switch hboots easily.
[EVO 4G Q&A, Help & Troubleshooting] erik077:
Same here. Sorry for asking in here but does anyone know is there limit?.... and if yes how many time you can flash it, or may just go randomly?
[EVO 4G Q&A, Help & Troubleshooting] n00barmy:
I'm actually not sure how to check that :o. But, As for the hboots, I have successfully downgraded from 2.10 to .076 three times as of right now. I have a few things I'm going to try in succession and I'll post the results :).
[EVO 4G Q&A, Help & Troubleshooting] k2buckley:
The only way to check that (that I know of) is issuing a command from a shell. it would be something like cat /proc/mtd.

Is this the method you've been using to downgrade hboot?? http://xdaforums.com/showthread.php?t=883548&highlight=downgrade+hboot ? Otherwise, I'm not sure... As far as I always understood, if you had the newer erase block size (some 003 and all 004 hardware) then downgrading from 2.02/2.10 hboot was not even possible (without making a brick). If you had hboot 2.02/2.10 on the older erase block size then you would be able to successfully downgrade. Anyhow, good luck with your efforts and please post your results.
[EVO 4G Q&A, Help & Troubleshooting] n00barmy:
Unfortunately, adb doesn't work because I can't get past the splash screen nor can I boot into recovery; and I am running the pc36img_210-76.zip and then running the eng-pc36img.zip after that. I can't boot into the recovery so that's how I have to do it.

BTW, my phone was useless BEFORE I tried that so don't anyone go about trying to do it that way ;)...
[EVO 4G Q&A, Help & Troubleshooting] n00barmy:
Bah! I tried to run the pc36img_210-76.zip then run eng-pc36img.zip then pc36img.zip and then use the ruu 3.70. Same outcome, oh well. I'm at a loss :(. Any ideas?
[EVO 4G Q&A, Help & Troubleshooting] cordell12:
If he successfully downgraded Hboot he has the small partitions, 20k. Downgrading with the large partitions results in another kind of brick. The reason they made the larger partitions must be related to this death loop issue. Why they become corrupted, who knows. With the larger sizes maybe it leaves space to skip the bad blocks???
[EVO 4G Q&A, Help & Troubleshooting] n00barmy:
No go...

Oh well, I've tried what I can think of. Nothing worked, I hope it really is something hardware related, that way there is no way I could've fixed it :p. I pick up the replacement in a few hours. Good luck to everyone who is having this issue.
[EVO 4G Q&A, Help & Troubleshooting] n00barmy:
Phone has been replaced by Sprint with no hassle. I have rooted it and I am ready to install new ROMs! Thanks for everyone who tried to help :)
[EVO 4G Q&A, Help & Troubleshooting] tguerena:
I think I have figured it out!!! I had a customer that had an evo that would not boot. It would get to the HTC Evo 4g Icon and that's all. Wouldn't boot into recovery, wouldn't boot into anything but HBoot. I have spent 4 hours on this damn phone, and I finally got it to boot. If you guys are interested I can type up a little tutorial of how I did it. I got it booting back up to stock and now I am going to try to root it and flash custom recovery... Here goes!

P.S. he had H-Boot 2.10.00001 S-Off but was acting like s-on

Oh, and I figured out how to get around that fastboot remote failure
[EVO 4G Q&A, Help & Troubleshooting] SwtSexiness:
Hi, I am having same issue. Please tell me how you fixed this. your help is appreciated.
[EVO 4G Q&A, Help & Troubleshooting] el_venga:
Im also interested, post the tutorial please.
[EVO 4G Q&A, Help & Troubleshooting] SwtSexiness:
There is no fix for this. I have searched hi and lo, I can't find anything seems that many people have had this problem, and could not find a fix.
[EVO 4G Q&A, Help & Troubleshooting] tguerena:
It's been a while since I did it now... But I am pretty sure I remember how I had to do it... I was gonna write up a tutorial, but on the 9th my gf left me and it has been a world of chaos.

If I remember right what I had to do, was download the hboot eng zip file, rename it to PC36IMG.ZIP, put it on the root of sd card, boot into bootloader, flash the pc36img, then reboot into hboot again, mount fastboot. Then download the latest rootable rom zip file, extract all the img files, and flash each one individually (Like 8 files).

i.e. fastboot flash recovery recovery.img

i.e fastboot flash userdata userdata.img or whatever.

Then it booted up and I was able to reroot it using unrevoked. Took me about 6 hours total, before I found that this solution worked.

I hope this helps. It's kind of a vague tutorial but it should work.
[EVO 4G Q&A, Help & Troubleshooting] nanstedt:
This same exact thing happened to me. Pretty much word for word with the OP. I am a casual flasher (ha that could be taken two ways). Anyway, I downgraded hboot after the bootlooping began to gain access to fastboot. I have the same curiosity about being able to erase everything and write new partitions. Any devs out there have any ideas?
[JAM, MDA Compact, S100 Software Upgrading] andre_kepy:
XDA II miniku cuman muncul seperti ini setelah aku upgrade

HTCMAG_ROM_WWE_03

by Cotulla

64 RAM

HW Hard Reset

Bad Radio

bagaimana biar XDA ku normal lagi aku upgrade lagi gagal terus katanya device error

trus di bootloader

cuman ada tulisan ini

USB/SERIAL

V 1.00

:(
[JAM, MDA Compact, S100 Software Upgrading] crachel:
Closed. Thread not related to development & does not contain an English translation. Please translate and post in the General section.
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] bnd10706:
So i went with WP7 on the HD2 and love it.

The only issue i seem to have is the fact that the battery is draining pretty fast. It was full this morning and its only been 6 hours and its at what appears to be 30% (its hard to tell without percent icon)

I installed the xmod rom.

Is this normal? is there a fix? I see lots of things when i do search on registry fixes, but i dont know much, if anything about registry editing this rom nor what it means.

Any advice is apreciated.
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] mrventura:
Battery drainage is a common issue. You could try some regediting and see if that helps. Just search around the forum to find out how to do it.
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] bnd10706:
Is this drainage going to screw up the battery? I have a spare, just prefer not to have to waste a good battery
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] argentocruz:
On my phone I've found no difference with battery drainage...
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] Tastenchef:
check this out:

http://xdaforums.com/showthread.php?t=1041912
[HD2 Windows Phone 7 Q&A, Help & Troubleshooting an] mrmomba:
At the first release from DFT, i had a batterylifetime from 6 up to 7 hours as a maximum.

Now i will test a newer ROM, so i would tell ya!
[Xoom Q&A, Help & Troubleshooting] metwally:
Will the xoom be working 3g in egypt under vodafon, i wonder, and heard that there will be a mandatory verizon subscription which in egypt ther is no verizon, and is there any other reason xoom might not work in Egypt,

Thanks,
[Xoom Q&A, Help & Troubleshooting] flyer138:
Verizon xoom will not work in Egypt, wait for GSM version, but make sure it is not carrier locked.

الصبر جميل
[Xoom Q&A, Help & Troubleshooting] willverduzco:
This is not development. Thread moved to Q&A.
[About XDA developers] MarkusPO:
how about a new forum for designers to share resources they've made that would be ok to use in apps? xda is a large community with designers around, and it may bring more people to xda putting their artwork up for use.

a forum for artwork, sounds, etc would be useful to both the design community and developers.
[Vibrant Q&A, Help & Troubleshooting] ZoNoMo:
I used to be a T-Mobile customer with my Samsung Vibrant Galaxy S. I unlocked the phone and went to ATT. Everything worked great except the GPS. So I searched on this forum and downloaded GPSRestore Samsung. When I run it, it gets hung up on trying to find the satellite and fails. But I discovered a workaround by accident. I was trying to Navigate to a place using Maps and it was hung up trying to find the satellite. During that time, I ran GPSRestore, and as usual, it hung up trying to find the Satellite. But the GPS in Maps started working! The next time I tried to run Nav on Maps, it wouldn’t run until I ran GPSRestore again! Can anyone point me to a permanent fix for the GPS? Oh BTW, I upgraded to 2.2 thinking that would fix the GPS but no. :eek: Thanks everyone.
[Vibrant Q&A, Help & Troubleshooting] da_dragon2k3:
Look in general chat for "correct hardware fix" and in development section for Jellet's gps fix. With those powers combined they are captain planet.
[Vibrant Q&A, Help & Troubleshooting] anthonys2r:
I do not think its a hardware problem (not in this case) because the OP did say he went to AT&T and as far as I know, there are different drivers for AT&T and T-Mobile. If anything, try going on the captivate forums and swapping out the GPS files (don't flash a whole captivate rom though!).
[Vibrant Q&A, Help & Troubleshooting] nomadrider123:
Have you used lbstestmode? There are other software fixes out there besides gpsrestore? You could put a PLASTIC piece of a pen top between your back cover and the gps antenna. That would tell you if the hardware fix would work for you. There is a good thread here about all the different gps fixes if you need it I can give it to you when I get home.
[Nook Color General] themitchy:
Anyone know any tricks to getting better sensitivity out of the screen for drawing? I was playing around with Autodesk Sketchbook and you can't even draw a circle without going all wonky. Same app and stylus on my Nexus One are smooth as butter.

-themitchy
[T-Mobile LG G2x] royale192:
When I first received my phone the wiring calling app was horrible. Even with good connection to the router. Seems to be 2.2 Froyo related. My cappy did the same thing. Well I set wifi calling to favor the cell tower more than the wifi. Also set cell the GSM /wcdma auto. Have not had any more concerns. Always switches to wifi when it wakes up hitting the power button. Did not use any freeze programs to stop wifi calling. If anyone wants to try that route with both items I have mention let me know how It works out. If I forgot a setting will edit post.
[Captivate Q&A, Help & Troubleshooting] eyebanez333:
My computer will not recognize my phone if usb debugging is turned ON. The computer recognizes it immediately with usb debugging turned OFF. It started doing it after I flashed Serendipity (REDROM) to it.

I've searched around and found a few threads on it, but it seems like no definitive answer has been given, and I've tried all of the advice in the threads.

-tried every USB port on my computer

-tried a different cable

-tried a different launcher (Launcher Pro).

any help would be greatly appreciated :cool:
[Captivate Q&A, Help & Troubleshooting] TRusselo:
try re-installing the official captivate drivers.

if that doesnt work try the i9000 drivers, some kernel/roms built on i9000 like those drivers.
[Captivate Q&A, Help & Troubleshooting] BWolf56:
Would that be the case after flashing a I9000 theme? I don't really wanna try it but maybe you'll know the answer :p

I've seen this happen alot after people are flashing certain theme and though it could be related? :rolleyes:
[Captivate Q&A, Help & Troubleshooting] viny2cool:
you cannot use I9000 theme on captivate. It has to be properly ported over, means changing the required files....and debugging issue has nothing to do with theme...but it might the case with rom...
[Captivate Q&A, Help & Troubleshooting] BWolf56:
Eh figured but though I'd ask.. Just though it's weird that it stopped after flashing RedRom!?

As for I9000 theme, they can work.. I mean, can't you use a JVB I9000 based theme on a JVB cappy? Just not sure if it would be the case with earlier build.