yashsingh1/xdaforums huggingface dataset:
[Desire Q&A, Help & Troubleshooting] waynestir:
sorry for delayed responce. I'm sure you had already found a solution by now but in the off chance you didn't.

you have to load fastboot not hboot.

from a power off state hold back button and power on phone. this will load fastboot and ruu will find device when run.
[Desire Q&A, Help & Troubleshooting] expza:
Fastboot will only work in Fastboot. ADB will only work when phone is booted and USB Debugging is on.

I don't know that as fact, I only know it from personal experience.

Use Fastboot to flash a new ROM, or at least a new recovery image. If you can get into Fastboot, you 'should' be able to fix your phone.
[Desire Q&A, Help & Troubleshooting] status_six:
+1 There is a good guide to fastboot commands on the android wiki:

http://android-dls.com/wiki/index.php?title=Fastboot

Should be a case of wiping system, data, cache, then flashing recovery image. Then boot into that and restore a backup or flash a rom.
[Desire Q&A, Help & Troubleshooting] jgm092:
can u plz help me frm with post u solved ur probs....i m stuck too
[Desire Q&A, Help & Troubleshooting] awayra:
1st Post, got my htc desire this morning and after researching for a long time already knew i wanted to root my device.I followed the instructions on this site.[HOWTO] Root Your Desire In 1 Click With UnrEVOked! *UPDATED 20/7* - xda-developers I used unrevoked3, and rooted the device. no trouble Ive backed up the device with titanium backup. Placed cyanogen onto the 4gb sd card which came with the phone.Power off the device. Rebooted whilst holding the volume down button. Got the options up. Navigated to recovery and selected it with the power button. The screen goes blank. The o2 screen comes up saying welcome and thats it, it freezes. I have to pull the battery out of the back in order to reset the device and then it starts up perfectly normal. Tried accessing recovery mode using the clockworkmod but i get the same result.All of the points on the link above were followed. Im pretty much right at the bottom! still researching the net for the answer but im now in need of additional
[Desire Q&A, Help & Troubleshooting] HTCPetter:
Does your phone get hot and overheated during the htc logo? It did so to me and it turned out to that my CPU had melted and overheated. Take it to your retailer and they will fix it for free because it's not your fault, it's the phone that overheated.
[Desire Q&A, Help & Troubleshooting] nhrsak:
Try this:

-download this with ur pc and rename it a PB99IMG.zip (not PB99IMG.zip.zip ok?)

-then put it on the root of ur sdcard (not in some folder) through an sd card reader

-ensure the battery is charged much than 30%..better more

-with the phone off (remove battery and put again) press and HOLD the volume down key and press (still holding the volume down key) and hold the power button..hold both and wait to enter in the hboot

-there wait a bit, and it will ask to u if u want apply the update, select yes with the volume keys and confirm with power button
[Desire Q&A, Help & Troubleshooting] bortak:
Just go to my troubleshooting guide, you'll probably find an answer there.
[Desire Q&A, Help & Troubleshooting] pwraggcan:
Send it back for warranty repair.

Sent from my Motorola Startac running Atari 2600 software!
[Desire Q&A, Help & Troubleshooting] alxkid:
@nhrsak - you save me, thanks very much!!
[Desire Q&A, Help & Troubleshooting] abaaaabbbb63:
Did you try getting s-off with Revolutionary?

I had problems when i was s-on, but when i s-offed, everything went fine.
[Desire Q&A, Help & Troubleshooting] allenfoxtc:
Have you tried flashing recovery.img via AndroidFlasher(from XDA)?
[T-Mobile LG G2x] adrieono:
Anyone know where the bootanimation sound is located?
[T-Mobile LG G2x] c_brown93:
system/media/audio.
[T-Mobile LG G2x] wewoapsiak:
/poweron/PowerOn.ogg

CM7 doesn't support bootanimation sounds, so that folder won't be there if you're using CM. I've found "fixes" for this, but haven't go them to work on the G2x.
[T-Mobile LG G2x] c19932:
thank you, now i can delete the annoying sound
[Nook Color Q&A, Help & Troubleshooting] jhnstn00:
I have been on CM7 for several months and now Nookie Froyo for a few days but wifi keeps going out and I have a difficult time restoring it.

I don't even remember if the stock Eclair had stable wifi.

What Nook ROM has a fully functional wifi?

Edit:

cm7 nightly 87 was good for me but I only stayed on that rom for 24 hours due to other issues.

Phiremod 6.2 has been great for couple days.
[Nook Color Q&A, Help & Troubleshooting] I Am Marino:
Try a stable version of CM7.

Still rocking the Incredible with the XDA Premium App.
[Nook Color Q&A, Help & Troubleshooting] jhnstn00:
I have. Used all 3 stable. Maybe should try 7.0 again.
[Nook Color Q&A, Help & Troubleshooting] GMKcz:
latest nightlies are based on .32 and most of people have their wifi issues solved
[Nook Color Q&A, Help & Troubleshooting] jhnstn00:
Nice. Will head that way and try it out. Cross my fingers ...
[Nook Color Q&A, Help & Troubleshooting] jared_c:
Stock was rock solid, but wouldn't connect to, or even see, ad hoc networks.
[Nook Color Q&A, Help & Troubleshooting] jhnstn00:
I don't use ad hoc but what is that?
[Nook Color Q&A, Help & Troubleshooting] dsf3g:
I've been rocking Phiremod 6.2, which is built on CM7.02, for a couple of weeks now. Never had any WiFi issues, either with my home router (Verizon supplied) or free networks at Panera and Barnes & Noble.
[Nook Color Q&A, Help & Troubleshooting] delosh:
I haven't had a single issue with wifi drops while running CM7 stables or nightlies for a couple of months now. I see posts where other people are having problems using the exact same versions I've been using (a variety of nightlies for several weeks, then stable 7.0.3 for a couple of weeks, now most recently n86). Have no idea why some people have been having problems, while I (and many others) have not. Rather odd.
[Nook Color Q&A, Help & Troubleshooting] I Am Marino:
I'm on N87 right now and I'm having zero issues as we speak.
[Nook Color Q&A, Help & Troubleshooting] phenol312:
I'm on N87 and I have noticed that the display icon will turn white sometimes but ill still be connected to the network...but I've been with the nightlies since day one and never had an issue when I couldnt connect to a network.
[Nook Color Q&A, Help & Troubleshooting] jhnstn00:
Thanks for everyones responses. I am now on N87 with no problems overnight. I had it charging with wifi to never turn off on and it remained connected this am. Will continue to monitor.
[Nook Color Q&A, Help & Troubleshooting] jhnstn00:
Yes it is crazy why that is.
[Nook Color Q&A, Help & Troubleshooting] linyongzheng:
Running n87, don't have trouble with infrastructure wifi but now I notice my joikuspot doesn't work anymore. It was working 2 weeks ago with whatever nightly/beta I was on at the time. Weird...
[EVO 4G Android Development] amot:
http://911sniper.blog.163.com/blog/static/142900881201131503456893/

SuperSonic_GB_Sprint_WWE_4.12.651.1_Radio_2.15.00.04.08_NV_208_release_183986.zip

2011-04-14 09:34

Is this a stock EVO GB release? If so has anyone worked on this and released a Stock GB ROM?
[EVO 4G Android Development] Slatter39:
Where have you been? Check these out,

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

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

DO YOU MIND SEARCHING FIRST?
[EVO 4G Android Development] RileyGrant:
Hahaha dude I see you on here all the time, where you been? Practically all of the new gingersense roms out today are completely dependent on that leak. Without that you wouldnt have any of the new roms, plus, some of the roms out right now are based on that, like Calks new Evio rom.
[EVO 4G Android Development] Joey_UFC:
i love those roms but i wish they were smaller files. i have never partitioned my sd before
[EVO 4G Android Development] amot:
My apologies, I guess these stock ROMS are not so popular...
[EVO 4G Android Development] amot:
Sorry guys, I was just looking for a Stock GB, possibly with Sense 2.1 but I will look harder for sure. Thanks again!
[EVO 4G Android Development] Slatter39:
No problem at all. By the way nice picture
[EVO 4G Android Development] ItsDon:
Check out Mik's .51 Rom. Stock Gingerbread with Sense 2.1, works great!
[EVO 4G Android Development] androidsupra:
Only "stock" gb with sense 2.1 would be a shift port. The evo will not be getting 2.1, not from HTC anyways
[EVO 4G Android Development] nugzo:
I am really liking Avas gingerbread with 2.1. Tried the others, Avas is my favorite. Throw the sense 3 lockscreen on it and your good to go. Hopefully the sense 3.0 ports will stabilize as much as the 2.1s have. 3.0 is tha ****!
[EVO 4G Android Development] scottspa74:
Im kinda glad amot posted this cuz I been curious. I thought I remembered this with the 4.12 radio leak, but if there's an official evo GB, why all the ports and semi-functional roms (no offense to ANYBODY)?

Is it just cuz of the effort to get the newer sense? Im on xda every day. But it seemed like this leak came and went. Unless I missed something.
[EVO 4G Android Development] androidsupra:
We got the (incomplete) kernel, and library files out of this leak that have made every gb sense Rom possible. It is entirely useless other than that because it had nothing other than some files of and interstate to anyone. The better sense versions are why we use ports anyways. I'm sure that once we do actually get an official version, with everything working, these ports will get better.

Also sense 3.0 will never be complete, or 100% stable on the evo for a few reasons, but that's what search is for.
[Xperia Play Android Development] thephawx:
Obviously it hasn't launched on Verizon yet, but when it does anyone have any plans to move it over to Sprint?

Seen a few links on what's required and shouldn't be that big of a problem. Seems like the hardest part will be adding the ESN.
[Xperia Play Android Development] timinator94:
I agree. I'm going to wait because I have heard rumors of an Xperia 4g coming to sprint
[Xperia Play Android Development] thorpe24:
Meh. That just means worse battery life. Just bought mine at cost 410 no contract woot. Been messing with it all day. Runs games faster than my TF
[Thunderbolt Q&A, Help & Troubleshooting] vypurr:
I used Rom Manager to apply an update to my DasBamf 2.0-beta5, and the phone reset but did not into Clockwork. Instead it got stuck in a boot loop.

I thought nothing of it, held down the volume button and went into the bootloader. Turns out I left a radio update on the root of my SD Card, so no biggie, I plugged the SD Card into my pc, removed the radio update file. I put the card back into my phone and now I cannot get into Clockwork!

Every time I get to bootloader, click recovery, then it goes into clockwork for a second, says:

E: Can't Mount /cache/recovery/command

E: Can't Mount /cache/recovery/log

E: Can't Open /cache/recovery/log

E: Can't Mount /cache/recovery/last_log

E: Can't Open /cache/recovery/last_log

What should I do? I do not have any idea what the issue is here!
[Thunderbolt Q&A, Help & Troubleshooting] superchilpil:
Uhhhh flash a new rom... It appears clockworkmod is still partially useable
[Thunderbolt Q&A, Help & Troubleshooting] vypurr:
I wish it were that simple. Clockwork is unusable. After the error message appears, the phone reboots into a boot loop with the White HTC Logo.
[Thunderbolt Q&A, Help & Troubleshooting] Spencer_Moore:
Load the stock rooted ruu through the bootloader than reflash can in the stock ruu than reupdate to gb
[Thunderbolt Q&A, Help & Troubleshooting] barcodelinux:
Can you boot into your ROM?

If so, the just reflash CWR via Rom Manager.

If not, grab a root stock RUU and flash that via HBOOT. Then download Rom Manager from the market, then reflash CWR.

Only bad thing about the second option is that you will loose /data.

I *think* there is a way to flash CWR via adb, but I'd have to look it up.
[Thunderbolt Q&A, Help & Troubleshooting] vypurr:
I feel really stupid because I thought I had a grasp on this whole thing...I got rooted without any trouble!!!

BUt I am not sure what is up at this point. I took the advice of those above, and loaded the stock rooted RUU through HBOOT (http://forum.androidcentral.com/thu...8597-ruu-return-rooted-stock-leaked-ruus.html).

- Put zip on SD-root folder

- Rename to PG05IMG.zip

- Boot into HBOOT

- Press Vol Up To start update

- Reboot phone

- Boot loop (never goes past the white HTC screen before resetting)

But afterwards I still am stuck in a boot loop! When I boot to recovery I get into CWR, and can move through the menus, but the phone reboots after a second or two (not enough to restore a backup).

Am I doing something wrong?
[Thunderbolt Q&A, Help & Troubleshooting] barcodelinux:
Sounds to me like the RUU didn't take when flashed via HBOOT. Is S-ON?

Try reflashing that RUU again.

If that doesn't work, try downloading and flashing another RUU. If all else fails, get the unrooted stock RUU. You might have to reroot but you will have a function device.
[Thunderbolt Q&A, Help & Troubleshooting] vypurr:
Damn. I really only trust stuff posted by Jcase, but all of his links are broken!!!

http://xdaforums.com/showthread.php?p=13921164

http://xdaforums.com/showthread.php?t=1082114
[Thunderbolt Q&A, Help & Troubleshooting] superchilpil:
I have an idea what it is, my phone did this before after I walked in and out of a walk in freezer... Blah blah

Go into hboot and find the selection that says system info.or something along those lines and if it says touch panel - fail or something along those lines then it will.never boot up
[Thunderbolt Q&A, Help & Troubleshooting] vypurr:
I think thats ok!

TOUCH PANEL-ATMELC12_20aaT

OS Ver.-1.12.605.6
[Thunderbolt Q&A, Help & Troubleshooting] superchilpil:
Dang :P well we know it's not a hardware failure

I would just try to.boot it.up after flashing a ruu and don't touch it for awhile and see if its just taking forever to boot
[Thunderbolt Q&A, Help & Troubleshooting] vypurr:
Well multiupload is back up! I will try some other RUUs
[Thunderbolt Q&A, Help & Troubleshooting] vypurr:
Any tips to charge the battery again though? I am fearful that I may have depleted it too far at this point, and plugging it in sends it into a boot loop!
[Thunderbolt Q&A, Help & Troubleshooting] superchilpil:
The best thing is to do a battery pull and plug it in right after you put the battery in

It shouldn't boot up... But who knows I could be wrong

>--The Game--<
[Thunderbolt Q&A, Help & Troubleshooting] vypurr:
I have loaded multiple RUUs in an attempt to fix this...no luck

I followed the Jcase to return to stock for rooted users - I am now stuck with S-ON, but it does not boot still. Just the same old White HTC Screen.
[Thunderbolt Q&A, Help & Troubleshooting] barcodelinux:
It could be that it wasn't a CWR problem to begin with since you have loaded the stock RUU, replacing CWR with the stock recovery, and it still won't boot.

Try taking the battery out and pressing the power button for about 10 seconds. Then put the battery back in. Do not press the power button. Now plug in the wall (AC) charger. Let the battery fully charge, no bump charging required. then unplug the charger. Now press Vol - and the Power button. The phone should boot into the bootloader (If it doesn't, then its bricked). Select RECOVERY. Now let the stock recovery program run and reboot.

I hope that fixes it, but if it doesn't...

Well, it comes down to a question that you need to ask your self...

Do you continue down the path of trying to fix this device?

Or

Do you take it in to a vzw store (or call warranty dept.) since its still under warranty and get a replacement?

If you want to press on with trying to fix it (keep in mind that all your data is already gone) in the hope that this process will help someone later who might run into the same problem and is out of warranty, I can try to help. But outside of flashing the unroot stock RUU, there isn't a bunch more that I can think of.

Let us know what you want to do.
[Thunderbolt Q&A, Help & Troubleshooting] vypurr:
I agree. I kind of think that Rom Manager corrupted the file that it tried to install.

I will try this tonight. I think that my battery is dead at this point. I can get it to reset to HBOOT (S-ON). I can click recovery. The stock recovery opens, and then within 5 seconds the phone resets. From this point (until I pull the battery), it will boot loop to factory recovery. Is this due to a dead battery? Every time I plug in my phone to my wall AC Adapter, the phone actually turns on and boot loops. Because of this I have not been able recharge it.

I have a replacement in the mail at this point, but I am willing to experiment in the meantime so that anyone in the future can avoid my problems!
[Thunderbolt Q&A, Help & Troubleshooting] barcodelinux:
You are not the first one to say that. While using a GUI front end to CWR is handy, it doesn't have a great track record.

I have gotten away from using Rom Manager for anything except flashing CWR.

But then again, I make it a habit to wipe /system, /data, and /cache before flashing a new ROM. You can't do that from Rom Manager.

Anyways, back to the topic...

The battery being in a low charge state wouldn't make the phone reboot (I wouldn't think). In the past when my battery has died, the phone never rebooted...it just turned off. However, I have never had the phone boot when I plugged up my wall charger either. (My old OG Droid used to do that and it pissed me off)

Has anyone else had this happen? If not, that might suggest a hardware malfunction of some sort too.

Was this phone dropped or does it have any kind of water damage?

At this point, I think it is a hardware failure of some sort. And chasing a hardware failure with a software fix is kind of a fruitless endeavor.
[Thunderbolt Q&A, Help & Troubleshooting] vypurr:
I know the phone has been babied its entire life (except for many many roms).

I remember that the phone used to turn on when CWR was first put onto the TB, but it should not do that stock, and it was cleared up with recent CWR updates.

I am just going to cut my losses and get the replacement that Verizon has offered me. Maybe I can have a couple more break and just get the Galaxy S2 when it lands!
[Thunderbolt Q&A, Help & Troubleshooting] vypurr:
Well I am not alone!!!

http://www.droid-life.com/2011/05/2...ght-want-to-consider-reverting-back-to-froyo/
[Thunderbolt Q&A, Help & Troubleshooting] rocko73:
These are the anti-root/rom measures they implemented. Stinks.
[Thunderbolt Q&A, Help & Troubleshooting] vypurr:
This is not anti-root/rom. This is a leaked alpha build radio bricking a phone that should not have been running it.
[Thunderbolt Q&A, Help & Troubleshooting] rocko73:
Exactly. v
[Thunderbolt Q&A, Help & Troubleshooting] barcodelinux:
Interesting...Did you try the fix at the end of the article?
[Thunderbolt Q&A, Help & Troubleshooting] vypurr:
Yup ... :(
[Thunderbolt Q&A, Help & Troubleshooting] brenick:
Recommendation to revert from Gingerbread

Here's a little more info on reverting using adb.

http://xdaforums.com/showthread.php?p=14137013
[Thunderbolt Q&A, Help & Troubleshooting] satseaker:
it is defective hardware,my original tbolt did all that and more on froyo and did not got into the brick reboot until it loaded the ota,never had gb on the phone,so how can it be that radio when my tbolt did with the froyo radio,atleast was able to get it back to stock and s on befor it went totally nuts
[Eee Pad Transformer Q&A, Help & Troubleshooting] MisterEdF:
I have ADB installed and functioning for my (now sold) Nook Color. I have a Transformer coming in tomorrow.

Do I need to uninstall and reinstall ADB specifically for the ASUS or is it "one ADB for all?"

Thanks
[Eee Pad Transformer Q&A, Help & Troubleshooting] ppirate:
One adb for all. No need to install anything extra.
[Vibrant General] superDel:
N#10 NO audio No audiooooooooooooooooooooo
[Vibrant General] geoffcorey:
Seriously, you had to post something like this OUTSIDE of the thread where this belongs (which isactually already known, and yes, nth nightly 9 and 10 suffered from this).

Op, you're not special, and it's unstable software, (hence the still nightly classification). There is no reason for this thread other than attention and someone's sense of entitlement.
[Vibrant General] oka1:
***Geoffcorey........... there you go stompin' on his puppy...... excellent stompin.........:p
[Vibrant General] movieaddict:
Lol
[Nexus S Android Development] -viperboy-:
Hey everyone, welcome to viperMOD for the EVO, Incredible, Nexus One, Desire GSM, Thunderbolt, Nexus S, Nexus S 4G, Desire HD, and Inspire 4G. Many people are having great success with this mod and I hope you enjoy my work :)

I would like to turn this into an app! If someone would like to help out that has Java knowledge, please contact me!

What does this do?

Kernel developers make their kernels to be "universal". By universal, they want the kernel to work on as many phones as possible so they may only mildly undervolt. However, some phones can handle a more aggressive undervolt. Some can't. viperMOD allows you to undervolt to your choosing for better battery life or allow you to overvolt to make your phone more stable.

How do I run this?

Once you flash the .zip go into your Terminal app (I use Android Terminal Emulator set to 10pt font) and type:

su

vipermod

I really only use Terminal for my mod and there is something really cool you can do with Android Terminal Emulator (and maybe others). Menu > Preferences > Initial Command > Press Enter and type su > Press Enter again and type vipermod

Every time you start Terminal now, it will open right into viperMOD. You can quickly exit by pressing Enter if you need to use Terminal for something else :)

UPDATE 6/14

viperMOD v3 beta RC2.4 is live!

Fixed some coding that was giving errors on certain ROMs and phones. Everyone please update to this!

Please see the updated FAQ and changelog for more information!

UPDATE 5/31

viperMOD v3 beta RC2.3 is live!

MUCH better support for NS/NS4G Netarchy kernels and other enhancements!

Please see the updated FAQ and changelog for more information!

UPDATE 5/29

viperMOD v3 beta RC2.2 is live!

Initial support for Desire HD/Inspire 4G and more!

Please see the updated FAQ and changelog for more information!

Please see viperboy.tiamat-dev.com for downloads, more information, changelog, and FAQ!

You can find the answers to all of your questions there!​

Feel free to support this mod with a userbar in your sig :)

Credit to:

- snq_ for the VDD support

- Cayniarb for his awesome Tiamat kernel, hosting, and website!

- Netarchy for his amazing guidance and patience!

- My IRC friends ekarelis, bigrushdog, and morph3k for all their help!

- Ziggy for the adjustable sysfs interface

- Anyone who has done testing for me or helped me at all

- Everyone who contributes to Android development

- Let me know if I left anyone out!
[Nexus S Android Development] brokentoaster24:
I was hoping to port this over when I had free time, beat me to it! :p

Search over in netatch's thread and you'll see there's a few discussions about uv'ing. There's also app over in themes and apps for uv :)

Sent from my Nexus S 4G
[Nexus S Android Development] -viperboy-:
I will take a look at both of those things, thanks!
[Nexus S Android Development] brokentoaster24:
It should be pretty easy. We don't have havs so you only need to echo one value for each clock speed and the voltages should be in sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table

Sent from my Nexus S 4G
[Nexus S Android Development] 651stp:
nice looking foward to it.
[Nexus S Android Development] -viperboy-:
Yeah, I read that in netarchy's thread. It's neat how you guys can go in increments of 5mv, usually it's 25mv. I'm going to try to get 2 ways of undervolting done tonight. I will definitly be able to code in lowering by increments, but it might take a little bit longer before I can code it to allow users to input the values they want. It's also a little bit more challenging when you don't have the device ;)
[Nexus S Android Development] raiderep:
This looks very very interesting, looking forward to see where this goes :)