Related
hi all,
I need to dump a rom from a mda III to a SD.
Who knows the right procedure? Is it the same of the himalaya?
thanks mates..
boobee
boobee said:
hi all,
I need to dump a rom from a mda III to a SD.
Who knows the right procedure? Is it the same of the himalaya?
thanks mates..
boobee
Click to expand...
Click to collapse
Go in bootloader mode, (yes, the device will factory reset, so backup before) by pressing all at the same time: power, record and the reset button.
Cradle the device, kill the processes wcesmgr.exe and wcescomm.exe if they are active.
Connect to the device with a terminal program that supports USB serial connections.
http://www.xda-italia.com/modules.php?name=News&file=article&sid=93
Ensure to take the whole device, so use the three lines.
“d2s 80000000 02000000“
“d2s 60000000 00300000 sd a“
“d2s 70000000 01080000 sd a“
Please be carefull not to interrupt the dump process, your dump will still work and checksum OK but the resulting SD card will not result in a working device after loading from it.....
I did it with success a couple of times, and scr$$ed up once because I had an error during the dumping of the image and still tried to load that image on another device.
Good luck.
Willem.
thank you Willem for your kind reply..
seen also how to restore it on the link you provided.
thanks again
boobee
Well for your info, it is working to save the ROM on the SD, but if you try to restore it, it won't work
SD Download
Sections = 3
Not Allow Update!
My Qetk is stuck in Bootloader and ask a friend of mine to do this trick, (same model) and it do not work
I think some addresses are not correct
In the saved dump of GSM module there were no any ST commands found. So i think XDA3 MDA3 memory map is not same.
Max
Anonymous said:
Well for your info, it is working to save the ROM on the SD, but if you try to restore it, it won't work
SD Download
Sections = 3
Not Allow Update!
My Qetk is stuck in Bootloader and ask a friend of mine to do this trick, (same model) and it do not work
Click to expand...
Click to collapse
YYMV..... Tried it again this morning, works fine as per the previous post. My bootloader is a 2.06, do you have the same bootloader version ?
Regards,
Willem
Anonymous said:
Well for your info, it is working to save the ROM on the SD, but if you try to restore it, it won't work
SD Download
Sections = 3
Not Allow Update!
My Qetk is stuck in Bootloader and ask a friend of mine to do this trick, (same model) and it do not work
Click to expand...
Click to collapse
YYMV..... Tried it again this morning, works fine as per the previous post. My bootloader is a 2.06, do you have the same bootloader version ?
Regards,
Willem
Check here:
http://forum.xda-developers.com/viewtopic.php?t=12298
wmeter said:
“d2s 80000000 02000000“
“d2s 60000000 00300000 sd a“
“d2s 70000000 01080000 sd a“
Click to expand...
Click to collapse
is RIGHT.
SD Download
Sections = 3
Not Allow Update!
Click to expand...
Click to collapse
If you are getting the error above, that means, that the SD image was done on different device than yours. If you want to avoid it, you have to have SD image done on your device, and you have to copy it's header out of it and then paste it over your friend's SD image header.
buzz
buzz_lightyear said:
Check here:
http://forum.xda-developers.com/viewtopic.php?t=12298
wmeter said:
“d2s 80000000 02000000“
“d2s 60000000 00300000 sd a“
“d2s 70000000 01080000 sd a“
Click to expand...
Click to collapse
is RIGHT.
SD Download
Sections = 3
Not Allow Update!
Click to expand...
Click to collapse
If you are getting the error above, that means, that the SD image was done on different device than yours. If you want to avoid it, you have to have SD image done on your device, and you have to copy it's header out of it and then paste it over your friend's SD image header.
buzz
Click to expand...
Click to collapse
I think that should be rewritten as "same bootloader version" since I restored the image on another device w/a problem. Works fine. Guess that the dumps are differently done per bootloader version.
I'm not quite sure. That header is some kind of checksum...
In wiki it says that the checksum depends on the SD card... however, it could depend on the bootloader version.
But then, I have 1.06 and i took the chinese 696 SD ROM image, which has 1.06 BL as well, but I was getting "Not allow update" till i changed the header from my SD card...
buzz
buzz_lightyear said:
SD Download
Sections = 3
Not Allow Update!
Click to expand...
Click to collapse
If you are getting the error above, that means, that the SD image was done on different device than yours. If you want to avoid it, you have to have SD image done on your device, and you have to copy it's header out of it and then paste it over your friend's SD image header.
buzz
Click to expand...
Click to collapse
how can I do this ?
Indeed the rom is coming from another Qetk but both were french...
wmeter said:
Anonymous said:
Well for your info, it is working to save the ROM on the SD, but if you try to restore it, it won't work
SD Download
Sections = 3
Not Allow Update!
My Qetk is stuck in Bootloader and ask a friend of mine to do this trick, (same model) and it do not work
Click to expand...
Click to collapse
YYMV..... Tried it again this morning, works fine as per the previous post. My bootloader is a 2.06, do you have the same bootloader version ?
Regards,
Yes bootloader 2.06, but the SD has been made on another Qetk, both in French and no operators
Willem
Click to expand...
Click to collapse
Hi Daimaou,
You need to change/overwrite the header of the SD card data. Please
see the posts from buzz_lightyear for this.
Willem
wmeter said:
Hi Daimaou,
You need to change/overwrite the header of the SD card data. Please
see the posts from buzz_lightyear for this.
Willem
Click to expand...
Click to collapse
thanks I am trying to find it now, but could you be more specific :x coz ouch there are some post to read before I can find it !
@daimaou
hi,
do you have a working device or is it dead?
i mean, can you boot it?
buzz
Hi !
my device is stuck in bootloader
V 2.06, I ask a friend of mine in france to dump its rom on a SD, while I am trying to put it on my Qetk I got Section 3 not allowd
So it seems that my friends SD is OK, but cannot use it, any idea?
I need my Qetk working soon since I will fly to China and US
Daimaou said:
Hi !
my device is stuck in bootloader
V 2.06, I ask a friend of mine in france to dump its rom on a SD, while I am trying to put it on my Qetk I got Section 3 not allowd
So it seems that my friends SD is OK, but cannot use it, any idea?
I need my Qetk working soon since I will fly to China and US
Click to expand...
Click to collapse
that's not that bad at all. keep your friends SDimage for now.
did you try to rerun the official ROM package for your device?
just give it a try... cradle it and run it...
don't use any USB hub, jUst straight USB connection to your PC...
let me know then...
buzz
buzz_lightyear said:
Daimaou said:
Hi !
my device is stuck in bootloader
V 2.06, I ask a friend of mine in france to dump its rom on a SD, while I am trying to put it on my Qetk I got Section 3 not allowd
So it seems that my friends SD is OK, but cannot use it, any idea?
I need my Qetk working soon since I will fly to China and US
Click to expand...
Click to collapse
that's not that bad at all. keep your friends SDimage for now.
did you try to rerun the official ROM package for your device?
just give it a try... cradle it and run it...
don't use any USB hub, jUst straight USB connection to your PC...
let me know then...
buzz
Click to expand...
Click to collapse
Yes I did, but the PB that so far no Official ROM image in French exist, I tried the UK (WWE one) but always Country ID Error, whatever I am doing (used the xda3nbftool.exe)
this is how to do it on xda2, but you can give it a try:
Download upgrade/downgrade package from your favourite provider
Unpack it into some directory (use WinZip or WinRAR)
Delete "GetDeviceData.exe" and "enterBL.exe" (don't edit .nbf files)
Restart your device in bootloader mode and cradle it (OPTIONAL)
Run "BAUpgradeUt.exe"
i typed those .exe names just from my head (sitting in the car right now), so maybe they are slightly different...
buzz
Doesn't work
error 120, country ID, 11-11-12-12-12
:x
I don't want to be rude but it is 1:17 AM in Tokyo now, and need to wake up early tomorrow, so cannot continue now, but please don't let me down I don't want to send my Qetk back to France and wait a month to have it back...
if you need my email address please send anything there
gagayjp[at]gmail.com
Cheers
My hp 6515 won't work sound and camera. After I made hard reset it work for some times after that it won't work again. Please help what it happening to my one.
I found the solution.
The problem comes with two files from my device/windows/
BtCoreIf.dll
BtSdkCE30.dll
I use total commander to rename them:
BtCoreIf.dll.old
BtSdkCE30.dll.old
And then, do a soft reset.
Its ok for both sound and camera.
neonaing said:
I found the solution.
The problem comes with two files from my device/windows/
BtCoreIf.dll
BtSdkCE30.dll
I use total commander to rename them:
BtCoreIf.dll.old
BtSdkCE30.dll.old
And then, do a soft reset.
Its ok for both sound and camera.
Click to expand...
Click to collapse
hi,
i have same problem with my hw6515 but i can't change the name of BtCoreIf.dll/BtSdkCE30.dll as the system won't let me do by using the total commander.
can you explain how to rename ?
thanks.
tangwd898 said:
hi,
i have same problem with my hw6515 but i can't change the name of BtCoreIf.dll/BtSdkCE30.dll as the system won't let me do by using the total commander.
can you explain how to rename ?
thanks.
Click to expand...
Click to collapse
Use Activesync to change it from your comp or mac. If the systen ask change, say yes.
tangwd898 said:
hi,
i have same problem with my hw6515 but i can't change the name of BtCoreIf.dll/BtSdkCE30.dll as the system won't let me do by using the total commander.
can you explain how to rename ?
thanks.
Click to expand...
Click to collapse
Use Activesync to change it. If the system ask to change, say yes. And make soft reset.
neonaing said:
Use Activesync to change it. If the system ask to change, say yes. And make soft reset.
Click to expand...
Click to collapse
Can't do it at all?
tangwd898 said:
Can't do it at all?
Click to expand...
Click to collapse
Arr,
If so use third party software (like Unlocker, its free version)to change the file name.
neonaing said:
Arr,
If so use third party software (like Unlocker, its free version)to change the file name.
Click to expand...
Click to collapse
just wonder if you really did that success by yourself? - did you try it?
Hi,
That doesn't work for me, I have rename them but nothing work.
I try delete too, but doesn't work.
Thanks for your help.
Takodz
takodz said:
Hi,
That doesn't work for me, I have rename them but nothing work.
I try delete too, but doesn't work.
Thanks for your help.
Takodz
Click to expand...
Click to collapse
hi, did you mean you can rename or delete the files?
Hi,
I rename the files, try with no result , then delete the files and no result too.
Takodz
takodz said:
Hi,
I rename the files, try with no result , then delete the files and no result too.
Takodz
Click to expand...
Click to collapse
hi, how can you rename the files?
Sound problem Hw6515D
This problem come from Tomtom 6
Tomtom6 must be installed without Bluetooth module,
Try install this one.
or make yours.
Sound problem Hw6515D
This problem come from Tomtom 6
Tomtom6 must be installed without Bluetooth module,
I guess HW6515D have already Tomtom5 and that's why Tomtom6 gives sound crash.
for the solution...
I can't the links give here but users can make their installs without bluetooth support
and a CECab editor needed.
I hope this solution solves the problem.
Regards.
i think that everything i do correct .... and maybe not.... when start the instalation says after log of ''D'' pad says that fail to extract install, not have space in device... what does it mean? and how i can solve this....
thanks for your time
wankel29 said:
i think that everything i do correct .... and maybe not.... when start the instalation says after log of ''D'' pad says that fail to extract install, not have space in device... what does it mean? and how i can solve this....
thanks for your time
Click to expand...
Click to collapse
Moved to General.
wankel29 said:
i think that everything i do correct .... and maybe not.... when start the instalation says after log of ''D'' pad says that fail to extract install, not have space in device... what does it mean? and how i can solve this....
thanks for your time
Click to expand...
Click to collapse
If you are trying to install android from HaRET for the first time you need to have a compatible sd card that can run HaRET .
I installed a cyanogen mod 11 custom rom on sony xperia sp c5302. The installation was successful but when i checked my device's credentials that is when i checked my about device section i saw that my model number was changed to c5303. Please help me I am unable to use my SIM card and moreover my IMEI is also not changed.
abhishekverma590 said:
Please help me I am unable to use my SIM card and moreover my IMEI is also not changed.
Click to expand...
Click to collapse
The IMEI is not supossed to change, is your phone's UINIQUE number. Try editing the build.prop for model number and see if it works for you.
Thank you so much for an early reply. I am a noob when it comes to flashing roms and changing the builds. I will be very grateful to you if you can provide me with a link which tells how to change the build.
abhishekverma590 said:
Thank you so much for an early reply. I am a noob when it comes to flashing roms and changing the builds. I will be very grateful to you if you can provide me with a link which tells how to change the build.
Click to expand...
Click to collapse
Download root explorer from play store-->grant root access-->open system folder-->mount it as r/w--> search for build.prop-->long press and then select "open in text editor"
Sent from My XSP
Pulsa said:
Download root explorer from play store-->grant root access-->open system folder-->mount it as r/w--> search for build.prop-->long press and then select "open in text editor"
Sent from My XSP
Click to expand...
Click to collapse
I tried your method but when i save it, explorer says cant save the file.
Is there any other rom or any other method which can help me or can I flash the stock rom back again??
abhishekverma590 said:
I tried your method but when i save it, explorer says cant save the file.
Is there any other rom or any other method which can help me or can I flash the stock rom back again??
Click to expand...
Click to collapse
Try this
Take the build.prop from the system folder and copy it in your internal storage
Now in pc open buil.prop from internal storage
Do the required editing in notepad or notepad ++
Save it
Now using root explorer copy the edited buil.prop to system folder with permissions rw-r-r
dipesh1502 said:
Try this
Take the build.prop from the system folder and copy it in your internal storage
Now in pc open buil.prop from internal storage
Do the required editing in notepad or notepad ++
Save it
Now using root explorer copy the edited buil.prop to system folder with permissions rw-r-r
Click to expand...
Click to collapse
I tried your method it is not working. Any suggestions??
abhishekverma590 said:
I tried your method it is not working. Any suggestions??
Click to expand...
Click to collapse
Not working??means?where u got stuck?actually it shud get edited thru root explorer only.
abhishekverma590 said:
I tried your method but when i save it, explorer says cant save the file.
Is there any other rom or any other method which can help me or can I flash the stock rom back again??
Click to expand...
Click to collapse
Do you remount to r/w?
Sent from My XSP
dipesh1502 said:
Not working??means?where u got stuck?actually it shud get edited thru root explorer only.
Click to expand...
Click to collapse
I have now installed the stock rom and still the same problem
Plus I tried the root explorer changing the build it didn't work.
abhishekverma590 said:
I have now installed the stock rom and still the same problem
Plus I tried the root explorer changing the build it didn't work.
Click to expand...
Click to collapse
You sure you have c5302?
Confirm it again by opening the backcover
dipesh1502 said:
You sure you have c5302?
Confirm it again by opening the backcover
Click to expand...
Click to collapse
I can understand your doubt. I am attaching the photo of my box it says c5302.
Please try to help me if you can. I am helpless here since I have unlocked the bootloader and the sony customer care people won't consider it under warranty.
abhishekverma590 said:
I can understand your doubt. I am attaching the photo of my box it says c5302.
Please try to help me if you can. I am helpless here since I have unlocked the bootloader and the sony customer care people won't consider it under warranty.
Click to expand...
Click to collapse
Bro i had the same problem as you
I. Have c5302 but when i flashed existenz it changed to c5303...it doesnt harm anything why to bother
And i just editd build.prop it worked for me...
dipesh1502 said:
Bro i had the same problem as you
I. Have c5302 but when i flashed existenz it changed to c5303...it doesnt harm anything why to bother
And i just editd build.prop it worked for me...
Click to expand...
Click to collapse
Ok but the SIM card is supposed to work, right??
In my case the rom is working but not the sim card.:crying:
abhishekverma590 said:
Ok but the SIM card is supposed to work, right??
In my case the rom is working but not the sim card.:crying:
Click to expand...
Click to collapse
Everything working for me
Can someone upload a copy of this file?
I try to install ota and failed in this point because stickmount modified this file at install them.
Need this from someone have 5.0 without stickmount installed.
Thanks in advance and sorry for my english.
dacbes said:
Can someone upload a copy of this file?
I try to install ota and failed in this point because stickmount modified this file at install them.
Need this from someone have 5.0 without stickmount installed.
Thanks in advance and sorry for my english.
Click to expand...
Click to collapse
Just flash the new factory image (without wiping data).
How, can you explain this with detail, please?
Solved install factory image without wipes.
Thanks