hd2 from tmobile.i start up and it is stuck in aMAGLDR screen
when i push volume at restart i get this:
PB81120 SS-B3
SPL-2.08. HSPL 8G XE
0X05
0X50
CotullaHSPL
what can i do to either get to android like i was planning or get back to windows mobile? any help would greatly be appreciated.
if i am in wrong section, please direct me to proper section, thanks!
the volume buttons work and when i try to do flash loader i get the following errors:
An error has occurred
Read below for more information
Error Description: Config load failed.
Info: .\RSPL\RSPL.cpp (725)
Error Description: CONFIG: can't open config file
Info: .\RSPL\RSPL.cpp (304)
i have the same problem!
Related
HI. Please help me! I wasn't able to modify an article on the WIKI (wiki.xda-developers.com).
All the time I press the "Edit" Button, FireFox give me the option to download the php file :?: :?: :shock: WEIRD
The address I was modifying was:
http://wiki.xda-developers.com/index.php?pagename=List of HimaUpgradeUt.exe Error Code
After trying it several times, I could get inside and edit the page, then I saved it, and now is BLANK!!!!
HEEEEELLPPPP
The contets of the page at the time of my edit were:
--------------------------
ERROR 100: MODEL ID ERROR
Definition: ROM image is not design for the device you are upgrading. It happens when you try to use Himalaya's ROM image into other HTC like MAGICIAN, BlueAngel or Alpine
Solution: Use appropriate ROM Upgrade image for your Device, no two device can share the same ROM
ERROR 101: CONNECTION ERROR
ERROR 102: CE IMAGE FILE CHECKSUM ERROR
ERROR 103: ROM IMAGE FILE NOT FOUND
ERROR 104: CANNOT OPEN ROM IMAGE FILE
ERROR 105: OPEN PORT FAILURE
ERROR 106: EXECUTE REMOTE COMMUNICATION PROGRAM FAILURE
WARNING 111: POWER ADAPTER NOT PLUGGED IN
ERROR 112: CE ROM UPDATE ERROR
ERROR 113: EXTENDED ROM UPDATE ERROR
ERROR 114: RADIO ROM UPDATE ERROR
ERROR 115: INVALID VERSION OF ACTIVESYNC
ERROR:116 GENERAL ERROR
ERROR 117: INVALID MODEL ID
ERROR 120: COUNTRY ID ERROR
ERROR 121: LANGUAGE ID ERROR
ERROR 122: EXTENDED IMAGE FILE CHECKSUM ERROR
ERROR 123: RADIO IMAGE FILE CHECKSUM ERROR
ERROR 130: CREATE CE ROM IMAGE ERROR
ERROR 131: ALLOCATE MEMORY ERROR
ERROR 132: WRITE DATA ERROR
ERROR 133: COMMUNICATION ERROR
ERROR 134: READ CE ROM IMAGE ERROR
ERROR 135: COMMUNICATION ERROR
ERROR 136: COMMUNICATION INTERRUPT
ERROR 137: COMMUNICATION ERROR
ERROR 150: ROM UPGRADE UTILITY ERROR
ERROR 200: WRITE EXTENDED ROM FAIL
Error 201: GET DEVICE DATA ERROR
This error is a bit misleading. The BAUpdate tool is trying to switch the phone into bootloader mode, and the phone for some reason is being uncooperative. This happens to me from time to time. The best, and quickest way around this is to force the phone into Bootloader manually. By pressing the record button, while doing a hard reset (Power + Reset) your phone will enter bootloader mode. You can verify this as the screen will say, Serial, and change to USB when you cradle it.
Once you cradle your phone, Windows will detect it as new hardware, and take a minute or two configure the right driver(Microsoft USB Sync). Once this is complete, you can run the BAUpgrade utility again, and this time you should get past error 201.
Error 202: READ IMAGE ERROR
ERROR 210: CREATE EXTENDED ROM IMAGE ERROR
ERROR 211: ALLOCATE MEMORY ERROR
ERROR 212: WRITE DATA ERROR
ERROR 213: COMMUNICATION ERROR
ERROR 214: READ EXTENDED ROM IMAGE ERROR
ERROR 215 COMMUNICATION ERROR
ERROR 216: COMMUNICATION INTERRUPT
ERROR 310: CREATE RADIO ROM IMAGE ERROR
ERROR 311: ALLOCATE MEMORY ERROR
ERROR 312: WRITE DATA ERROR
ERROR 313: COMMUNICATION ERROR
ERROR 314: READ RADIO ROM IMAGE ERROR
ERROR 315: COMMUNICATION ERROR
ERROR 316: COMMUNICATION INTERRUPT
ERROR 317: COMMUNICATION ERROR
Hi,
I tried it too & have simular probs in changing any wiki page @ the moment. IMHO there's something wrong on the serverside cause the text is still present but compilation into a page fails.
Try again later is my suggestion.
Cheers, M
Yup, I thought it was a temporary problem. Moreover, I'm having the same strange behaviour in some wiki links.
For instance:
http://wiki.xda-developers.com/index.php?pagename=BA_Versions
It is the first link on this page:
http://wiki.xda-developers.com/index.php?pagename=BA_FAQ_Upgrade_Radio
Thanks for your answer. I'll try later........
oltp said:
Hi,
I tried it too & have simular probs in changing any wiki page @ the moment. IMHO there's something wrong on the serverside cause the text is still present but compilation into a page fails.
Try again later is my suggestion.
Cheers, M
Click to expand...
Click to collapse
If the problem persists you can always pm 'peter poelman' or another moderator, maybe they can fix it.
The way it is now, we'll have a very empty wiki soon. Luckily the preview shows the same errors & peolpe should be warned by that, so as long as people don't save any changes to a page...
Luckily, I think you can allways get an older version of the page.
Cheers
oltp said:
If the problem persists you can always pm 'peter poelman' or another moderator, maybe they can fix it.
The way it is now, we'll have a very empty wiki soon. Luckily the preview shows the same errors & peolpe should be warned by that, so as long as people don't save any changes to a page...
Click to expand...
Click to collapse
arieltools said:
Luckily, I think you can allways get an older version of the page.
Click to expand...
Click to collapse
Ok learned something again, I didn't know that.
hi
I wan t to unlock HTC touch Pro
so i decided to buy a code for this phone .....
the problem is that the phone doesn t recognize the code i upload a video to Youtube to the seller see that i wasn t cheating.....
now
my question is the phone is locked to 26806 on portugal and i have upgraded to the latest Rom version that i download from htc and try again to put the code that i buy and i get always wrong code.....
is possible that the operator put difrent codes that unlockers cannot calculate????
is possible to unlock by other method ?????
you can find my video if you search on youtube by ----HTC touch pro - code dosen t work-
since i can t pos link s ...
try here;
http://forum.xda-developers.com/showthread.php?t=328221
Long story short-unlock codes don't always work. Don't try to enter it too many times, or you can be locked out of the device. Just run the unlocker, it works every time. Kiss your original 20 bucks good-bye.
unlock dosen t work
tank s for reply but that unlock don t work ...
don t appear nothing ....
it runs normaly and the txt inside the folder open but nothing more apear....
any idea??
i have istutils inside the folder windows on the device ....
i get this on istutils.txt on the device....
ERROR: DeviceIoControl(1, FL_IOCTL_BDK_OPERATION, BDK_INIT_READ, start=0, size=0x40000) - A device attached to the system is not functioning.
ERROR: DeviceIoControl(1, FL_IOCTL_BDK_OPERATION, BDK_INIT_READ, start=0, size=0x40000) - A device attached to the system is not functioning.
ERROR: DeviceIoControl(1, FL_IOCTL_BDK_OPERATION, BDK_INIT_READ, start=0, size=0x40000) - A device attached to the system is not functioning.
ERROR: DeviceIoControl(1, FL_IOCTL_BDK_OPERATION, BDK_INIT_READ, start=0, size=0x40000) - A device attached to the system is not functioning.
ERROR: DeviceIoControl(1, FL_IOCTL_BDK_OPERATION, BDK_INIT_READ, start=0, size=0x40000) - A device attached to the system is not functioning.
ERROR: DeviceIoControl(1, FL_IOCTL_BDK_OPERATION, BDK_INIT_READ, start=0, size=0x40000) - A device attached to the system is not functioning.
The unlocker in the link is for the HTC Touch (Elf) not the Touch Pro.
You will need to use the unlocking service from imei-check.co.uk or Olipros version of this method, both options are not free but will fully unlock your device.
you don t see my first post
since I already bought a code and did not work !!!
i lost money already !!!
what guarantees do I have to turn to buy a code !!!
it will run ,???
Just buy olipro's unlocker, it's guaranteed to work, unless you screw it up.
Mymind said:
you not see my first post
Click to expand...
Click to collapse
Yes, I see your post & read it correctly.
The unlock method by IMEI check & Olipro do not use code as you purchased before, they use a patched radio & software to unlock.
These mothods will work 100% & IMEI check would refund if you fail to unlock.
More on Olipro unlock can be found in the Touch Pro wiki I expect.
Hi all i Encountered following issues while install HD2O_2.00b5_8773 rom on HTC_HD2. on end only this error message appar. pls help me on it.
An error has occurred
Read below for more information
Error Description: send d000ff partition data failed
Info: .\RSPL\RSPL.cpp (1279)
Error Description: block send fail
Info: .\RSPL\RSPL.cpp (962)
Error Description: Block is after end.
Info: .\RSPL\RSPL.cpp (704)
thanks,
Hi all,
I'm quite new in the Android debugging. (please save your thoughts on my screenname. I don't know anything about android development at all)
I have a Samsung Galaxy Tab 2 (model: GT-P5110 w/ cpu: armeabi-v7a and android release: 4.0.3)
This device is Rooted.
It's irritating that out of nowhere my device reboots randomly. (but not often)
I never turn off my device, so every now and then, these reboots appear.
I searched the logs with Log Viewer and aLogcat BUT neither of them show any unusual information of the random reboots.
Digging more on the Internet, I found there are two places to look into for reboots:
1.- Look into /dev/kmsg (which is currently with 0 bytes)
2.- Look for a file called last_kmsg (found on /proc)
So I went into file "last_kmsg" and found parts which got me wondering:
SA_PH_CFG_VBATLOWV = 0x80
PHOENIX_LAST_TURNOFF_STS = 0x3
init_ddi_data: usable ddi data.
MSV already was fused : 0xf000ff00
------------------ERR result : 0x1---------
[ERROR] [SEC_ENTRY] Call to Secure HAL failed!
[ERROR] [FUSE INIT] Failed!
[FUSE INIT] OK!
---------------------
nps status=0x504d4f43
g_nRebootReason = 0x100000
AST_POWERON..
Kernel @ 81808000 (4175668 bytes)
Ramdisk @ 82800000 (412785 bytes)
*** ltn101al03_power_on ***
Autoboot (1 seconds) in progress, press any key to stop .
boot_kernel: debug level low!
checkbit: find RECOVERY
checkbit (60749f8b)
Starting kernel at 0x81808000...
What do they mean?
Unfortunately, I've never done any formal course on Android Development so it's quite bulky to search the web for this.
All I get is code and code, from various people on the Net, and technical answers regarding memory dumps.
But nothing is really an answer.
Please help!. I've had this issue for months and just today I finally found something that could be of use, but my knowledge is too little in this subject.
Note:
I have attached : last_kmsg and my basic device information (from logcat)
Please help
But when used carried the code for opening files I got the following message (( get toueh controller vender fail [fail] ))
The device in position s-on
Device hanging on a company's logo does not enter into the system
Device Type htc htc incredible 2