yashsingh1/xdaforums huggingface dataset:
[Droid Eris Q&A, Help & Troubleshooting] bftb0:
When you say "...letting the boot loader install all the contents...", it sort of implies that either you used the toastcfh battery-pull trick, or the other components of the package failed to install when you used the HBOOT installation of the Root-ROM.

Which one of those scenarios was it?

When you performed the flash of the recovery partition, e.g.

fastboot flash recovery recovery-RA-Eris-v162.img

did you get any unusual (error) messages?

There have been one or two cases where applying the Root ROM to a phone that was in trouble have actually killed the phone off. Not trying to scare you, because there is no reason to believe your phone is in the same state - but just letting you know that you are in dangerous/uncharted territory.

I would proceed pretty methodically - and very slowly - at this point.

Some things you could try which are short of just flashing the full Root ROM:

1) Try using fastboot to "live boot" a recovery without flashing anything at all:

fastboot boot recovery-RA-Eris-v162.img

This might give you some more wiggle room - I'll explain later. Let me know if this works (and if it does work, obviously you should immediately attempt a Nandroid backup.)

2) Try using fastboot to erase the recovery partition first, and then re-flash it, e.g.

fastboot erase recovery
fastboot flash recovery recovery-RA-Eris-v162.img

and see if that changes anything.

bftb0

PS I am AFK for a couple hours, but will be back to have a look.
[Droid Eris Q&A, Help & Troubleshooting] the_aether:
This thing really doesn't want to boot :mad:

I installed the bootloader using the battery-pull trick as CCCP4ever suggested.

$ fastboot boot recovery-RA-eris-v1.6.2.img
downloading 'boot.img'... OKAY [ 0.823s]
booting... OKAY [ 0.001s]
finished. total time: 0.824s

When I do a "live boot" the phone goes back to the droids on boards screen and stalls. This seems odd to me... why does it go back to the normal bootloader screen? From what I understand it should really go straight into recovery as the bootloader has already run.

$ fastboot erase recovery
erasing 'recovery'... OKAY [ 0.080s]
finished. total time: 0.080s

$ fastboot flash recovery recovery-RA-eris-v1.6.2.img
sending 'recovery' (3834 KB)... OKAY [ 0.832s]
writing 'recovery'... OKAY [ 1.328s]
finished. total time: 2.160s

Erasing recovery before flashing had no effect.

Probably going to attempt flashing the full PB00IMG.ZIP via the bootloader if I don't figure something else by the end of the night... not having a phone is not fun.
[Droid Eris Q&A, Help & Troubleshooting] bftb0:
You will always see the skating droids at the beginning of the recovery boot.

That splash screen usually lasts for 10 or 15 seconds before it proceeds to the recovery menu.

Do you get a different result if you eject the sd card first?
[Droid Eris Q&A, Help & Troubleshooting] the_aether:
Alright, I think I'm starting to go insane.

I took out my MicroSD card. The first time I tried to boot straight into recovery (by holding VOL UP while turning on) it started into recovery. However it didn't look like amon_ra recovery (at least as I remember it)-it had the HTC logo in the background and I'm pretty sure the menu options weren't the same as usual. IIRC it looked like the stock recovery. It stayed up for literally 2 seconds they my phone went black. :mad::mad::mad: Many explicatives were yelled. I'm pretty sure that it wasn't the battery that died since it's been on the charger most of the day.

I haven't gotten it to boot back into recovery again yet (haven't been counting, but I've probably tried over 10 times now). Every single time I try to boot into recovery it goes to the droids on boards screen, stays on for about 2 or 3 seconds, goes black, vibrates/turns on again, then is stuck at the droids on boards screen. At this point I'm about ready to try flashing the full update and/or throw my phone against the wall.
[Droid Eris Q&A, Help & Troubleshooting] bftb0:
Only your patience will rescue your phone - remember that.

When Amon_RA's recovery first loads, the kernel is awake and doing things after about 2 seconds. It then spends a fair bit of time bringing up individual pieces of hardware - the USB bus is one of them, and this happens fairly early. The SD card happens somewhat later (that's why I asked about the SD card - slight chance the kernel was hanging initializing the SD card slot). The reason I mention this is that there is a small possibility that the kernel is alive far enough along that ADB is alive - when you boot the recovery and it sits there hanging at the splash screen (wait for ~20 secs), does

adb devices

report anything alive?

One more question (unrelated):

Does the phone show evidence that it is charging when turned off but plugged in? (For instance, amber LED goes to green after a couple of hours)

(Note what I pointed out above about the battery discharging even when plugged in when the phone is in HBOOT, FASTBOOT, or RUU mode - don't leave it sit that way for long period of times. HBOOT in particular can drain a 100% charge in less than 90 minutes - even though the phone is plugged in to a computer)

bftb0
[Droid Eris Q&A, Help & Troubleshooting] the_aether:
The phone does not show up on ADB. The LED is amber while charging and turns to green as usual once it is completely charged.
[Droid Eris Q&A, Help & Troubleshooting] Conap:
I'm throwing out an idea to bftb0(he is really the best person to walk you through this) so don't go trying anything like this yet but when flashing the recovery.img does it format that partition? If it doesn't can't you format/erase the recovery partition and then reflash the recovery in case something in recovery partition is corrupted. Also you could try fastbooting a rom boot.img and you can actually flash the a whole rom through fastboot. This really isn't my strong area but just throwing out some ideas....
[Droid Eris Q&A, Help & Troubleshooting] bftb0:
Hi Conap

The boot and recovery partitions are "raw" - they have no format, just a binary blob of data (of course, that blob does have a very specific Android header, but it's not a file system like /system, /data, or /cache).

He tried fastboot erase followed by reflashing, and also live-booting via fastboot Amon_RA - neither seemed to work.

Hey the_aether - that reminds me : what is the MD5 sig of the recovery-RA-Eris-v1.6.2.img file you are flashing? The original (from Amon_RA) has a value of

$ md5sum recovery-RA-eris-v1.6.2.img
e3932991f097993602af3c7a4b61a4f8 *recovery-RA-eris-v1.6.2.img

everything but the system partition - unfortunately, fastboot reports that it runs out of room when you try to write system.img. I don't know why that is, but it is what I have observed (many times, I'm pretty sure it's not a fluke).
[Droid Eris Q&A, Help & Troubleshooting] the_aether:
In a sudden twist of events, when I accidentally turned on my phone in normal mode (not holding anything) it booted into Android... :confused::mad::confused::mad:

I'm currently running TiBackup for obvious reasons, but I'm honestly a bit afraid to turn it off again. Now that I can actually run things on my phone, what should I do to fix the problem while I have complete access to it?

Your suggestion about the BCB makes sense to me. I was actually going to suggest that this looked like a bootloader problem to me as sometimes it would go into that stock recovery and sometimes it would just stay there. I've had similar problems at work with alpha bootloaders. I guess I can try the fastboot stuff after TiBackup runs if you think it's a good idea to turn it off.

Oh, and please don't feel the need to apologize for asking for information and not giving suggestions in every single post... I understand that you need more info on the problem to know what's going on and you've helped a ton already. I appreciate it! :)
[Droid Eris Q&A, Help & Troubleshooting] bftb0:
Well that's a relief... sort of... maybe :(

Computers are supposed to behave deterministically, though - not "this way" sometimes and "that way" other times. When they start behaving erratically, it's usually time to suspect a hardware problem.

The thing is, without being an HTC engineer with intimate knowledge of the bootloader's behavior, it is hard to know whether or not the behavior you observe is truly random - or if every time you cycle the bootloader it is actually changing the system state slightly (for instance writing stuff to flash memory someplace), and that's why you see different behaviors in boot cycles afterwards.

Obviously, you should back up everything first, and then you may as well back up the entire SD card too, so that if the phone goes "offline" you have access to everything without requiring a microSD card reader.

Did you double-check the MD5 of the Amon_RA image?

You can re-flash the recovery again from within the booted OS if you want - sort of the "old fashioned way" of installing a custom recovery (putting recovery-RA-Eris-v1.6.2.img on your SD card and then using the "flash_image" tool). Given the symptoms you described, I don't know why that would change anything, though.

There really isn't a good way to make bit-for-bit backups of your /system and /data partitions without being offline - they need to be unmounted to get bit-for-bit accuracy (certainly that is true for /data - probably you would get a "pretty good" dump of /system if it is mounted read-only).

If the ROM you are using has shutdown options available, when you finally get enough confidence to shut your phone off - try to reboot directly to recovery - that definitely re-writes the BCB.

If it were my phone, I honestly don't know what I would do - let sleeping dogs lie, or try to make sure I captured a current Nandroid backup and then go for the Root-ROM full flash, followed by re-installation of a custom recovery, and then restoration of the Nandroid backup. The one thing that happens with the PB00IMG.ZIP-style ROM installs is that there is this mysterious "nvram" object which gets flashed - if that area is the source of the trouble, then maybe the ROM flash could help.

good luck

bftb0
[Droid Eris Q&A, Help & Troubleshooting] the_aether:
Alright, my phone is definitely still not OK. It was just sitting on the desk next to me and it rebooted and is currently in the same state it was before. Oh, and while it was on I couldn't text or call any phones--it gave me a message about Verizon not being able to authenticate my phone, and had me call a number where they told me to use *228 to reprogram it. I was able to call and text after that.

Anyways, here is my output of fastboot oem boot. Definitely the same... (edit: I'm an idiot, didn't see the FAILED at the end of yours)

$ fastboot oem boot
... INFOsetup_tag addr=0xA0000100 cmdline add=0x8F066FD0
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 32
INFOTAG:hwid 0x0
INFOTAG:skuid 0x21E01
INFOTAG:hero panel = 0x4
INFOTAG:engineerid = 0x0
INFOHYNIX_512MB_FLASH_256MB_RAM_DUAL_DIE_ID
INFOHYNIX_512MB_FLASH_256MB_RAM_DUAL_DIE_ID
INFOTAG:mono-die = 0x0
INFODevice CID is not super CID
INFOCID is VZW__001
INFOsetting.cid::VZW__001
INFOserial number: HT03SHG00272
INFOcommandline from head: no_console_suspend=1 console=null
INFOcommand line length =407
INFOactive commandline: board_desirec.disable_uart3=0 board_desi
INFOrec.usb_h2w_sw=0 board_desirec.disable_sdcard=0 diag.enabled
INFO=0 board_desirec.debug_uart=0 smisize=32 androidboot.baseba
INFOnd=2.42.01.04.27 androidboot.cid=VZW__001 androidboot.carrie
INFOr=COMMON androidboot.mid=PB0010000 androidboot.keycaps=qwert
INFOy androidboot.mode=normal androidboot.serialno=HT03SHG00272
INFOandroidboot.bootloader=1.49.2000 no_console_suspend=1 consol
INFOe=null
INFOaARM_Partion[0].name=misc
INFOaARM_Partion[1].name=recovery
INFOaARM_Partion[2].name=boot
INFOaARM_Partion[3].name=system
INFOaARM_Partion[4].name=cache
INFOaARM_Partion[5].name=userdata
INFOpartition number=6
INFOValid partition num=6
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
INFO0
FAILED (status read failed (Too many links))
finished. total time: 0.755s

fastboot oem rebootRUU does work and displays the HTC logo on my phone. Don't know if it was meant to display a menu or anything.

Anyways, the fact that my phone rebooted for no reason while just sitting there almost makes me want to say that this is a hardware problem. What do you guys think?
[Droid Eris Q&A, Help & Troubleshooting] tazzpatriot:
Y don't u call Verizon and get a replacement?
[Droid Eris Q&A, Help & Troubleshooting] the_aether:
Phone was bought on eBay used, so I'm pretty sure it doesn't have a warranty.
[Droid Eris Q&A, Help & Troubleshooting] tazzpatriot:
Sorry I musts missed it..did u get insurance? If u had it on ur account it follows ur phones.. I got one from ebay. And when I activated, the phone it was covered _
[Droid Eris Q&A, Help & Troubleshooting] bftb0:
Probably. Assuming you've got everything backed up, it looks like there's little to lose by flashing the root Rom and then rerooting the phone, and flashing a ROM - you will see the same sort of behaviors popping up if there are hardware problems.

If that happens, you can get a little money back from eBay - selling it "for parts".

If it gets bricked, same outcome.

bftb0
[Droid Eris Q&A, Help & Troubleshooting] the_aether:
Unfortunately I don't have insurance...

Flashed the full zip, no changes. Any other ideas, or should I just give up at this point?
[Droid Eris Q&A, Help & Troubleshooting] bftb0:
I am out of ideas that would be likely to change the behavior of your phone.

Some very low probability of success (but low risk) activities would be:

- Erase the cache partition using fastboot

- Flash the misc partition using fastboot with the misc.img file from jcase's "Flash any RUU" thread

A high-risk activity that you could perform prior to selling the phone for parts would be:

- Experiment with the fastboot OEM commands, and carefully document the results you get.

You can get a list of the OEM commands with "fastboot oem ?" (with the phone plugged in and in fastboot mode, obviously)

You would be doing the Eris community a service here, rather than being likely to fix your phone. As a matter of fact, several of the commands look downright fatal, judging from their names. We don't know much, if anything about use of these commands - because of the risks involved.

Someone in your position though - with a phone to be sold for parts, but a partly functioning fastboot mode - is in a unique position to experiment.

bftb0
[Droid Eris Q&A, Help & Troubleshooting] the_aether:
First of all, I just want to say thanks to bftb0 and all the other people who replied. Your efforts are greatly appreciated! :)

I played around the the fastboot oem options earlier but there were none that particularly caught my eye. Are there any specific ones that you'd like me to try? Otherwise I'll just start playing around, but I figure I should refine what I'm trying before I possibly (accidentally) kill it for good.
[Droid Eris Q&A, Help & Troubleshooting] bftb0:
Before you get too far along, does

fastboot oem imgcrc

report that your hboot CRC is good?

I've tried all these - so I know they won't kill your phone (you can skip them if you want)

ram_test
sdtest
readconfig
readsku
erasesd (un-formats SD card)
readserialno
gotofastboot
readmbserialno
listpartition
saveprt2sd
savemem2sd
boot
powerdown
rebootRUU
readbcid
keytest (needed a battery pull to get out of it)
imgcrc
heap
heaptable

For the balance of the commands, I suppose I would avoid anything that says "Set", "reset", "erase" or "clear" in it, I would save those for last.

Many of the commands require parameters, and some of the commands will offer brief syntax hints if you run them without parameters; if you get one of those hints, and the new information looks dangerous to you - save the information presented on the screen and fool with them later, according to your judgement.

(You might want to put all of your findings into a new thread, BTW)

The following are in no particular order - they didn't look obviously dangerous to me, but that's because I don't know what they do - any one of them might be hiding a "nuke your phone" functionality.

mb
mh
mw
ew
eh
eb
mmu
jump
test
rflash
tflash
block_test
btrouter
tick
emapi
emapiTest
emapiCountryID
emapiWlanMac
emapiReadCal
lr
battcheck
usbtestmode
powertest
fmrouter
bdaddress
rMfgTp
lnb
gpiow
gpior
mddiw
mddir
clock
i2cr (I-squared-C bus "r" ... "read" ? Play with touchscreen?)
i2cw
ulpi
bma150
reset
enableqxdm
rtask
task

Here's the ones that "look" particularly dangerous - I put them in the order that I would try them (least harmful to most harmful)

erasebcid (backup CID - probably harmless)
writebcid "
writeserialno
writemid (might affect activation status)
wMfgTp
changeCid (Carrier ID - might affect network access via CDMA)
emapiSetDefCal
resetuP
resetautoimage
resetRUUflag
eraseconfig (Possibly harmless - "readconfig" reports 10 values of 0x0)
writeconfig
erase (I am wondering this allows individual partition erasure)
writesku
eraseWifiFlash

Good Luck
[Droid Eris Q&A, Help & Troubleshooting] roirraW "edor" ehT:
I'd be interested in finding which of all these codes hides the "Predator" self-destruct personal-size nuke countdown.
[G Tablet General] Falco01:
Maybe I am dumb, but I can't find the answer anywhere. I downloaded and installed launcher pro. When I hit the home button, I accidentally chose the regular launcher as default. Now, even when i go into home switcher and choose launcher pro as default, when I bit the home button it defaults to stock. How can I change that? Thanks.
[G Tablet General] Sprdtyf350:
Have seen the same thing before. Simplest thing is don't use home switcher. I don't think it works very well. One way to fix it is to uninstall launcherpro and then reinstall. Then hit the home button and check the little box at the bottom before you pick launcherpro.
[G Tablet General] Falco01:
Thanks man. I ended up downloading Home Switcher for Froyo and it did the trick. I noticed that in the default home switcher, there is a check box to enable the ad blocker. I never seen that before.
[G Tablet General] smakcc:
Change from launcher proback to default launcher:

Go settings > applications > downloaded applications. Select launcher pro and clear default settings(last option). When you hit home again show ask which launcher. Select default then click the one you want.

Change from default to launcher pro:

Go to system applications, look for "launcher" and clear defaults if this is the current launcher.
[G Tablet General] aver2one:
if that ever happens again you can go to settings>applications >manage applications >launcher(or launcher pro depending on which one you want to take off)>clear defaults
[G Tablet General] aver2one:
lol great minds think alike!
[Desire Q&A, Help & Troubleshooting] tahosa:
I recently unbricked my Desire and upgraded to Froyo, but now whenever I try to install some apps my device reboots when it gets to the "Installing" phase. I have figured out that this is due to the fact that the SDK requires apps which need access to system resources to be installed on the device rather than on the SD card which is the Froyo default.

It seems this is a problem with rooted Droid X variants as well, but it is solved by installing a new ROM. Is that the easiest way to fix this, and can anyone point me to a stable Sense ROM which has the WiFi hotspot capability?

Thanks
[Desire Q&A, Help & Troubleshooting] TheGhost1233:
Every sense rom has hotspot, there is a nice sticky in development with all the roms listed. Look for yourself what you like.
[G2 and Desire Z Q&A, Help & Troubleshooting] jburnette87:
ive downloaded adb and android sdk but when i open adb to start rooting it briefly opens and then closes. Thoughts?
[G2 and Desire Z Q&A, Help & Troubleshooting] Buck Shot:
this may be a dumb question, but I just got the wife a G2 from Best Buy for Xmas ( awaiting it to be shipped ) and she now has a Cliq. I just got a new Cliq 1 month ago due to insurance replacement and I plan on giving my grandma her Cliq. lol yes my grandma....she has a BB and FB...lol anywho, I know she doesnt have a data plan but my question is

if she is on wifi can she access the web and android market without charge and if so, if she downloads apps, when she is not on wifi will she be charged for using the apps such as hancent for text and things of that nature?
[G2 and Desire Z Q&A, Help & Troubleshooting] gantou:
Wifi works just fine without a data plan, that's what I do as I'm still on a prepaid plan. No charges for wifi data as your not using their network. Standard SMS fees even while using Handcent will apply. If you want free SMS sign her up for google voice, but of course you won't be able to utilize it off of wifi if you have no data.
[G2 and Desire Z Q&A, Help & Troubleshooting] Buck Shot:
she has a reg plan, just not an android web plan, just minutes and text/pics. Its good to know she can download apps without a prob then. but...... will it be considered data through android web if she uses the apps not on wifi. she has a text plan i think
[G2 and Desire Z Q&A, Help & Troubleshooting] Sleef:
I believe that apps that require internet access to function simply won't if she's not on WiFi.

I don't think you can simply start accessing T-Mo's data connection without a plan so she should be fine. Just know that getting away from the WiFi signal may cause some apps to not work.
[G2 and Desire Z Q&A, Help & Troubleshooting] Buck Shot:
k, thanks guys....ill be back when my wife lets me root her g2...lol
[G2 and Desire Z Q&A, Help & Troubleshooting] bongd:
I'd kill the APN settings on that sucka except for the MMS settings. Make sure the data is dead because in a lot of cases they can remove the actual plan, but not the data feature all together. This can result in even more expensive data charges ironically.

Make sure to call in and review this with a CSR so they note it on file in the event of an overage. I worked for an outsourced call center that did work for T-Mobile yeeeeaaars ago. They've always had liberal billing policies from what I remember so it shouldn't be a problem. I actually with they were in Canada because the providers here SUCK!
[G2 and Desire Z Q&A, Help & Troubleshooting] ddotpatel:
Excellent advice there!
[EVO 4G Q&A, Help & Troubleshooting] stkiswr:
Couldn't really find the answer I was looking for. I have a stock evo. installed swype beta and would like a sweet keyboard theme. I seen one a while back...black and green I think with htc over the space bar. Looked clean. Anyone know? thanks
[EVO 4G Q&A, Help & Troubleshooting] lopezpm:
http://xdaforums.com/showthread.php?t=793471

Look under Other Optional Downloads

Then look at 3rd post for installation instructions
[EVO 4G Q&A, Help & Troubleshooting] stkiswr:
Thanks very much!

Sent from Epic 4g
[Captivate General] kamesen:
There is an app MarketAccess that allows you to change your phones market id (its a 6 digit number) which allows you to access the different versions of android Market. att may limit what you can see in the market...

the verizon id is 310410

t-mobile id is 310260

what is the att number? its set in the phone as default (so all you need is the app to look at it) but i dont have it. or if anyone knows what it is that would be great.

thanks
[Captivate General] visitador02:
Since I tend to log whatever I do.

The AT&T code is 310410
[Captivate General] BL4zD:
Then what is Verizon's code?
[Captivate General] polarbee:
Verizon's code: 310004
[Captivate General] kamesen:
thanks folks
[Touch CDMA General] Earl123676:
Hi I have a htc touch celluer south and i ran the unlock.

it has slp-0.41 coKe then i ran a custom firmware ant it will never start up.

I tryed anything i could whent to htc web got it from there and it wouls freeze up at 11% need help sorry im a new with this stuff.

did a custom firmware for the 5th time now it says no radio and wont start up.