Dear all,
I am trying to bring to life an old WM2003SE pocket pc by flashing it. However, I am unable to bypass the "version error" warning. Please have a look at the attached image from a hex editor locating the "version error" text. I would be grateful if someone can tell me how to bypass this warning by editing the bootloader file eboot.nb0 (attached).
Cheers,
Jay
PS: let me know if more info is required.
Related
when I updated my Dopod(CHT) to Qtek( UNI_QTEK_WWE_13077_130176_10900_WWE_Ship.exe),I clicked ROMUpgradeUt.exe . First ,It showed Error Country ID Error, I added [CHECKCEID_TYPE]=1 to RUU.conf, and i clicked ROMUpgradeUt.exe again ,the error code disappeared, but when I clicked UpDate , the activesync was broken, it can't connect to PDA, and then it showed CONNECT ERROR. Anybody could help me ! very urgently!!!!!!!
try to use "Maupgradeut_noid" tool . hope it will help on your problem.
help
I have used "Maupgradeut_noid.exe". it alse showed this error.
From your description above, you did NOT use the Ma_upgrade No ID Tool. Read my instructions here: http://forum.xda-developers.com/viewtopic.php?t=54071
help
Where is the Maupgradeut_noid.exe for QTek? I can't find it.
I have used "ROMUpgradeUt.exe" to upgrade.
I think i may have come up with a way to CID unlock the G4 version of HTC Prophet, but i need help to complete some gaps.
As far as i can tell (and please correct me if i'm wrong) the only reason why the "downgrade&unlockcid" procedure doesn't work is because "pdocwrite.exe" can't write back the unlocked file. So, if we could find a way to write that information the problem should be solved...
I think that by performing the following steps one could do the unlocking:
- create an ActiveSync connection;
- run "unlockcid.bat" to get the "acidunlocked.bin" file;
- get the checksum of the "acidunlocked.bin" file;
- restart Prophet in bootloader mode;
- run "Rom Update Utility" and cancel after a successful "Verifying information..." window;
- use a TTY program to connect to the PDA and issue the following commands:
>ruustart
>ruuformat ???? 10000
>wdata ???? 10000
>HTCS
>"acidunlocked.bin content"
>"4-byte acidunlocked.bin checksum"
>HTCE
>ruuflashdoc ???? 10000 "4-byte acidunlocked.bin checksum"
>ruurun 0
>ResetDevice
The knowledge i lack is the exact memory address to place the information.
Also, is the data retrieved by "pdocread" in a "raw" format? And can it be directly written to the DOC by this method?
I think i'm very close, but i really help with these few things before taking the last step... i don't want to end up with an expensive brick.
PS.: i would like to thank all the people in the xda-developers, modaco and spv-developers forums, and all the other guys who have been "burning their brains out" to find solutions, and without whom i could never have gone this far (if one can call THIS "far"... )
we poor guys trying to upgrade our HP IPAQ hx2000 series with AKU 3.5
There is a solution available in a Russian Websites, but we couldn't understand,
we we try to download the ROM and install it gives an error saying "Digital Sign Mismatch"
I see some comments on "Digital Sign Mismatch" again I couldn't understand,
can any one from this site can help us?
here is the forum
http://4pda.ru/forum/index.php?showtopic=35871&st=330
I appreciate all of your response
try to translate with google language tools:
http://translate.google.com/transla...&hl=en&ie=UTF-8&oe=UTF-8&prev=/language_tools
helps that you can read at least - but translation is awful
your handset must be set to bootloader mode first.
hi,
How do I get the boot loader mode?
press button #2, button #4 and "reset" simultaneously.
Hi,
I got the boot loader, I see a message called "USB is connected" in the iPAQ, but when I run hpruu.exe I got error "ERROR: 503" saying active sync is not connected
Any idea?
Find the right way!
Please push "calender" after you enter the boot loader mode.
anavas said:
Hi,
I got the boot loader, I see a message called "USB is connected" in the iPAQ, but when I run hpruu.exe I got error "ERROR: 503" saying active sync is not connected
Any idea?
Click to expand...
Click to collapse
Dear Anavas,
Please try
http://forum.xda-developers.com/showthread.php?t=326214&page=2
I already place step by step procedure. Good luck
hi edcom,
I appreciate your reply
thank you
Every time I try a Firmware upgrade my P320 I get the "No GSMFFS" error and the installation stops.
Can someone help me understand what GSMFFS is???
Also is there a way to fix this error??? I am getting the Bootloader prompt. It is even finding the image files. But then it says " No GSMFFS. 3 images found" and stops executing.
On a related topic. There seems to be an option to Upgrade the firmware using USB... Has anyone successfully done that???
Please advice!
Joe!
Someone Anyone???
Hey,
I've been researching the OP3 bootloader and the bootloader warning and I've found a possible method to hide it.
There is a file "emmc_appsboot.mbn" which contains information and strings (see content below). I'm not sure if modifying the file causes booting problems. I've examined the file and found something about verifying various files and blocking the boot process. I'm looking for someone who could help me and explain things. What do you think? If it's going to brick, would it be unbrickable?
Strings:
"Start >"
"< More options"
"Your device has been unlocker and cann't be trusted"
"To learn more, visit: g.co/placeholder"
"If no key pressed:
Your device will boot in 5 seconds"
Something about blocking the boot:
This phone has been flashed with unauthorized software & is locked. Call your mobile operator for additional support.Please note that repair/return for this issue may have additional cost.
boot_verifier: keystore length is invalid
I'm thinking about replacing all these texts with spaces to make the screen look blank. That's the way to "hide" the text, but there's still going to be the 5 seconds delay.
Download link to the file: http://d-h.st/SQID (Uploading attachments wasn't working when I posted this)
EDIT: Feel free to examine the file with a hex editor. Search for those strings to find the position.
There're already two threads dealing with the bootloader warning:
http://forum.xda-developers.com/oneplus-3/how-to/help-how-to-remove-device-unlocked-t3425028/page7
http://forum.xda-developers.com/oneplus-3/help/request-remove-bootloader-unlocked-t3405485
meiser said:
There're already two threads dealing with the bootloader warning:
http://forum.xda-developers.com/oneplus-3/how-to/help-how-to-remove-device-unlocked-t3425028/page7
http://forum.xda-developers.com/oneplus-3/help/request-remove-bootloader-unlocked-t3405485
Click to expand...
Click to collapse
I know, but neither one is dealing with this exact file/method. There is of course the "logo.bin", but I don't think it includes the warning message as I've found it from the file I discovered.
santeri3700 said:
I know, but neither one is dealing with this exact file/method. There is of course the "logo.bin", but I don't think it includes the warning message as I've found it from the file I discovered.
Click to expand...
Click to collapse
the "warning" message is inside the aboot....at the moment there's no way to modify this file....but....we will see.
lance2010 said:
the "warning" message is inside the aboot....at the moment there's no way to modify this file....but....we will see.
Click to expand...
Click to collapse
Isn't it possible to modify the hex codes? Or is it the verification that is the problem in this case?
Edit: I've seen that people edit this file with success.
santeri3700 said:
Isn't it possible to modify the hex codes? Or is it the verification that is the problem in this case?
Edit: I've seen that people edit this file with success.
Click to expand...
Click to collapse
where did you see it running?
editing is not the problem, flashing it back is not the problem...but the phone won't start, even if you change a single bit !
there's an checksum active even if you set your phone to unlock_critical...
lance2010 said:
where did you see it running?
editing is not the problem, flashing it back is not the problem...but the phone won't start, even if you change a single bit !
there's an checksum active even if you set your phone to unlock_critical...
Click to expand...
Click to collapse
It was a Samsung and a Xiaomi device (partition and bl unlocking stuff, so not exactly related to this). The checksum is what I'm after.
Unfortunately I don't have enough experience and I don't know if it's even possible to do this.
I'm wonder what exactly happens if I edited the code to have only "spaces" or "NBSP".
Would I get any response from the device? Would I see any error codes on the screen?
I'm too unsure to risk my device. But thanks for the answer!
if you not know how to use the OP3 unbrick tool, let it be..in result you got an unbootable device if you change anything inside the bootloader.
It can't be changed.