Database Users

How do I know if the T-Mob MDA stock ROM backup is complete?

How do I know if the T-Mobile stock ROM backup is done?
I'd like to be 100% sure I've backed up the ROM before I go flashing with the latest, greatest builds (e.g. xelencin's).
The completion bar at the bottom of the MDA screen next to "USB" has completely filled (I guess implying its done copying the image?), and last line in TeraTerm says "WriteDataToSDCard() - pusSourceAdd"
There's been no activity for at least 5 minutes on the MDA or the PC.
Can I safely disconnect the USB cable at this time -- is the ROM backed up to the MiniSD now?

I redid the T-Mobile stock ROM backup since I haven't gotten a firm response to my query about what completion of the backup looks like (actually, redid it twice). Both times the results was as below.
You don't actually get any kind of formalized "process is complete" prompt.
Instead, the completion bar next the the "USB" at the bottom of the MDA is full, and on TeraTerm, this is what is looks like:
(bunch of other messages before this)
-WriteDataToSDCard() - pusSourceAddr = 0x8CB00000 , ulSourceLength=0xA00000
Double Check 0 Start=0x80000000, Length=0x800, Checksum=0xDCDA598A
Double Check 1 Start=0x80000800, Length=0xC0000, Checksum=0xD9316F31
Double Check 2 Start=0x800C0800, Length=0x40000, Checksum=0x8AA9A67C
Double Check 3 Start=0x80100800, Length=0x280000, Checksum=0xEA461346
Double Check 4 Start=0x4E3D4C0, Length=0x3900000, Checksum=0x58FE1D88
Double Check 5 Start=0x743D4C0, Length=0xA00000, Checksum=0xDC9C91B8
usTotalBlock = 1 sizeof(SDCARD_SIGNATRUE_TABLE)=512
+WriteHTCSignature,download type = 5
Common Info Checksum=0xE256BE04
-WriteHTCSignature...
Cmd>
I presume since the bar is full and it brought me back to a command prompt, the backup was successfully completed.

[H E L P]HTC Touch have dieeed!

I am trying to flash my HTC TOUCH XL.When the screen changes tocolor white, the PDA remains stop, and later in a few seconds appears me in the RomUpdateUtility program this screens:
http://img206.imageshack.us/my.php?image=dibujo1lb2.jpg
http://img206.imageshack.us/my.php?image=dibujo1lb2.jpg
http://img517.imageshack.us/my.php?image=dibujo2qh3.jpg
http://img255.imageshack.us/my.php?image=dibujo3iq6.jpg
http://img255.imageshack.us/my.php?image=dibujo4vm2.jpg
http://img517.imageshack.us/my.php?image=dibujo5ot0.jpg
The screen continues with white color always,it doesn't anything.Then I have reboot the PDA.Now the screen always stays here:
http://img47.imageshack.us/my.php?image=dibujo6zt0.jpg
Always,when I reboot the PDA,in a few seconds appear two messages:
- Searching for SD card
- Checking SD contents
Omg...which the problem?Can I repair the PDA?
Thxx!

Possible reason for HD2 CoreDroid HD GB 2.3.3 V2 slowness

Seems like having SD card inserted causes high IOWait.
User 1%, System 3%, IOW 95%, IRQ 0%
User 5 + Nice 0 + Sys 10 + Idle 0 + IOW 291 + IRQ 0 + SIRQ 0 = 306
Currently running smsBackup+ that restores sms messages from Gmail (1 message in 4 sec)
This also seems to cause reported installation issues:
(thread http://forum.xda-developers.com/showthread.php?t=926507)
Installed several times myself... waited up to 0.5 hour.. still splash screen.
Several processes (com.android.phone, etc) got "Force" or "Wait" messages.
Only after connecting ADB console was i able to see that android was still initializing.. waited for longer and in the end ~1 - 1.5 hours phone booted up.
Are you affected? .. Try removing SD card.. does HD2 boot up within 10 min.? .. then probably you have the same issue.
(not really usable with no SD card.. settings are lost on each boot)

This is discussed very often in the developing thread that you already mentioned: Dev Thread
The first time it needs a lot of time - in my case it was more then one hour before the splash screen was away - for the FCs just press the "Wait" button and wait - after the first time it will become less and less and the device will work quite fast (just the known bugs are still there).
Some people told that they had to wait for 2 or one even for 4 hours before the splash screen was away. I had very strong problems with installing and it did not disappear after 6 hours.
If you have that try the following:
1.) data wipe
2.) d-cache wipe
3.) starting in MAGLDR
4.) USB flasher / DAF.exe
5.) recovery menu / cwm partition sd card (1024/0M)
6.) mounting and transfering .zip
7.) install .zip
8.) reboot
hope i got you right

[Q] problem with booting htc hd2

I need help guys!!! Here is the thing i was using many roms starting from DFT LEO NAND to latest ICS, and with ICS instalation started with problems. hd2 started to crush while he was working and when i wanted to boot bootloader was loading and keep loading forever (using (Android 4.0.3) (AOSP ICS ROM for HD2) NexusHD2-IceCreamSandwich Beta10).
I used again ROM who was before ICS - NexusHD2-Gingerbread V3.2a (GWK74)(Android 2.3.7)[tytung_r13] and more roms using MALDGR >> all roms i install normaly and boot up and when i reboot they are going on Splash loader and keep it there forever. I tried all methods using task29, radio, magldr (installing again) still nothing and when i wanted to install DFT LEO NAND again i have error on the end of installation :
Error Description: send partition data failed
Info: .\RSPL\RSPL.cpp (802)
Error Description: flash write failed.
Info: .\RSPL\RSPL.cpp (586).
I tried to remove sd card and also did active sync detach still nothing
Any ideas.

Why will you type a whole message in bold?!
Looks like you're volumes keys may be stuck or acting up... I had this happen sometime back, ended up changing the main flex circuit strip.
Sent from my HTC HD2 using XDA

ph03n!x said:
Why will you type a whole message in bold?!
Looks like you're volumes keys may be stuck or acting up... I had this happen sometime back, ended up changing the main flex circuit strip.
Sent from my HTC HD2 using XDA
Click to expand...
Click to collapse
Sorry for my bold writing
i checked mu volume keys and everything is ok. Today i changed my radio and booted ROM everything was fine several time i rebooted and when i go in clockwork mode mode on botom of screen it is written somthing like E:/error/ recovery log etc etc. is it possible that i did something wrong with mu internal partition
here is the thing with DFT LEO NAND on my screen
USB Flasher mode
Wait USB...USB
Lauout...PC=4, ASI=3 OASI=5
Erase...
k = 25-> 23D 25 219, 1000
0: part = 37, part2 = 37
1: total = 1999, extra = 99
2: total = 320, extra = 16
[ASIZE] START: BB0 END: f40 SIZE: 390
PARTITION LAYOUT NEW
0: 0219 023E 50 89
1: 023E 0A70 50 01
2: 0A70 0BB0 50 01
3: 0BB0 0F40 20 01
Erase...
D S: 0 E: 219
D S: 1 E: 23E
D S: 2 E: A70
D S: 3 E: BB0
Save EMBR...
Default OS is AD NAND...
Flashing 0 partition...0 [219-23E] M1 OK 8B21 22C
Flashing 1 partition...1 [23E-A70] M1
and stuck loading on almost 90 %
There i get erroron DFT FLASHER:
Error Description: send partition data failed
Info:.\RSPL\RSPL.cpp (802)
Error Description: flash write failed.
Info: .\RSPL\RSPL.cpp (586)

Unable to use Glowlight

Hi guys, I've got a little problem here. I played with my Nook Simple Touch Glowlight and even rooted it. But I couldn't install apps for some reason, so I decided to restore and root it again with other tool (Glownooter) so I could have Google's App Market. Here comes my first fault. I installed [NST]Touch-Formatter v2 .zip - I didn't notice it is only for the normal NSG - using CWM. Everything worked fine, I registered my Nook and then, using CWM, installed glownooter. But instead of showing me Android homescreen, it rebooted itself. And it got stuck booting (five dots loading) until the battery died. So I charged it and then I tried it again (NST Touch Formatter, Glownooter...). And "surprisingly", I ended up with the same result. I tried that about four or five times and then I gave up for two days. Today, I wanted to read something, so I used only the Touch Formatter, registered it, uploaded the book on it... And held the "n" button to turn the glowlight on. But nothing happened. So I went to settings and there wasn't anything about glowlight. Well then, I had a backup, so I restored from backup. When it booted, it kept me showing the screen "your system is damged" (or something like that) "you must perform a system restart". Tried that 2 times. Didn't help. I did factory reset (holding the two bottom buttons during boot up). After that, I had trouble with connecting to my wifi, so I skipped the registration proccess.
Now, I can use it, but without Glowlight and that was the main reason why I bought Nook and not Kindle. I guess, the Touch Formatter somehow installed the normal NSG software, so the device thinks, it's the old model. And that may also be the reason why Glownooter didn't work. Then again, my opinion has 90% to be wrong - given to what I did with my nook, and that this is my first Android device.
I did the backup with Windows, everything else using Terminal in OS X (if that info helps).
Thanks for any idea that comes up onto your mind.
P.S.: Sorry for mistakes in my text, I'm not a native speaker and I've been learning English for 3 years (plus it's 1 a.m. ).
,

The good thing about that screen that says "You must reboot your Nook" is that it means that your Nook is almost working.
At least in some cases it's caused by not being able to mount partitions.
Here's an example:
Code:
I//system/bin/fsck_msdos( 744): ** /dev/block//vold/179:6
I//system/bin/fsck_msdos( 744): Invalid cluster size: 0
I/logwrapper( 744): /system/bin/fsck_msdos terminated by exit(8)
D/vold ( 744): Filesystem check failed (unknown exit code 8)
E/vold ( 744): vfat filesystem check failed on 179:6 (I/O error)
D/SurfaceFlinger( 811): Frame buffer posted; elapsed time = 34 msecs
D/MountListener( 811): handleEvent volume_checking:/media
D/MountListener( 811): handleEvent volume_damaged:/media
I/ActivityManager( 811): Starting activity: Intent { flg=0x10000000 cmp=android/com.android.interna
l.app.RebootRequiredActivity (has extras) }
I/RebootRequiredActivity( 811): getReason(): received reason [REASON_MEDIA_UNMOUNTABLE [/media]]
The easy solution is to check whether all the partitions mount.
You can do that with noogie and a Linux system or Clockwork Recovery.
If you still can't figure it out, get ADB over USB working on your Nook and get a logcat.