The topic says it all...
i believe this is what you're after:
http://www.spritesoftware.com/products/sprite_clone.html
I doubt that.
you would need to accesss bootldr, and read / write files, otherwise all you will be doing is backing up data and applications and not the actual ROM
rgds
jim
I made a bad change in shellres.dll.0409.mui and my device (Herald) cannot boot normally. It is frozen on the Windows welcome page (WM6.0).
So, Activesync cannot detect the device.
I would like to copy the good file from my computer to the device, or to copy the good file which is still installed on my device in \Temp, to \windows.
Is it possible to do that with mtty, with the bootloader mode, or with another tool ?
I'm afraid that a hard reset is not useful because shellres.dll.0409.mui is a "ROM file" (ROM property checked, is it considered as the ROM component ?).
And I don't want to flash ou upgrade the ROM. It is Ok except shellres.
Thanks for your help !
You don't need to flash again the rom. I had this problem a lot of times and with a hard reset solved. This file makes the translation for the main wm applications, so if its wrong the applications fail to start, and for this you cannot achive an activesync connection. But with a hard reset the device returns to factory settins and all windows files replaced with the defaults, so you can boot it again normally.
Possible without a hard reset ?
... because I didn't have a backup. So, I would prefer another solution.
Other question : when a file is marked as "ROM" in the properties, does that mean this is a real part of the ROM ? Or is the ROM stored elsewhere ?
Rom is "read only image like a cd rom. you can't change one file on the cd rom without rewriting the entire cd. When you flash a rom you are rewriting that cd.
In other words the actual "rom" is stored elsewhere and reloaded when you hardreset.
Would WM5torage be of any use?
no his phone won't load so therefore he can't install anything.
plus i don't think wm5torage is compatible with 6 or 6.1 (it may have been that it was just 6.1 ....i've seen people complaining about it, i may be wrong)
I made the hard reset but I have to do again everything...
... and I can't change the read-only property of shellres.dll.0409.mui.
I'm creating a new question...
Is there a way to turn a backup file into an OEM package that is automatically set up as part of the ROM?
For example, say I cook my own ROM that has nothing at all. I then install all my apps, enter all my serials and registration info into all the apps, get my WiFi set up with all my WEP keys, all my favorites, all that kind of stuff. Then I make a backup using some backup program.
Can I then take that backup file and cook it into the naked ROM so that all of my serials, settings, etc are all set up after every hard reset?
I know I could just put it on the storage card and restore after every hard reset, but I would rather have it cooked right into the ROM if this is possible.
If this is possible, what would be a good backup program to make the backup file with?
i was thinking that when the device is doing the customization or whatever you call it after the hard reset, it could be restoring from the backup file.
Has anyone done anything like this yet?
Even I am wishing that there is such a way.... You put in words what many of us noobs wish for.
I'm sure there is a way to do it. Hopefully someone will help us out.
I am by no means an expert, but I would guess you need to somehow cook the backup file into the ROM, and then edit the autoexec.bat file to run that backup file.
So what we really need to know is, which backup program makes the best backups, that restore without any user input. Something that all you do is tap it and it does the rest from there. And it would need to restore all installed apps, all settings, all internet favorites, all registration info for all the apps, all calendar, contacts, and tasks, and any registry tweaks.
If we can locate the backup program that does this with minimal user input we have passed step one. Step 2 would be to cook the self executing backup file into the ROM, and step 3 would be making the ROM run the self executing backup after hard reboot, during the automated customizations. And if you soft reset the device before it runs customizations, I would want it to start running the customizations immediately after the reboot (like the newer stock ROMs do).
That way if my phone gets stolen I can use Sprite Terminator to locate it, and whoever steals it will have to flash a new ROM to get rid of Sprite Terminator.
I would not want this backup file listed anywhere on the device either. For example, if you look in "Programs" (or anywhere else) you don't see it. That may or may not be the hardest part- I don't have any idea if it's even possible. But it's not an issue until we get the other steps done.
life would be much easier...I hope someone can make this real
Any UC compliant ROM can do that for you. They are meant to autorun any file which you users want to run after ROM upgrade. Good luck, check sleuths thread for more info.
A while back i decided to downgrade my stock 4.3 to 4.1.1 in order to try to unlock it from carrier... the thing is i lost my IMEI and Serial Number
The good news is i have a backup of my EFS folder (only copy-paste with "root explorer" app though... no ".img" file sadly), but I understood that the most important file is "nv_data.bin"
So... my problem seems to be like this: http://forum.xda-developers.com/galaxy-s3/help/successful-imei-repair-i9300-backup-t2544109
but only the last step (put back the nv_data.bin, delete backups of bad nv_data.bin, reboot and magic)
The sad part: it doesn't resolve anything because everytime I reboot the phone it recreates the "nv_data.bin" even if I restore the original one (the one i had before downgrading)
Can anyone help me please :angel: ?
I have also tried as seen in other posts to change it's owner into radio:1001, unfortunately it still recreates the file after reboot.
I am currently trying to go back on 4.3 to try to restore the nv_data.bin on that verison (but i don't think it has anything to do with the android version)
Anyone encountered this problem or knows a solution ? Thank you !
Hi,
I see you've already asked about this in the appropriate section for your device. Xda Assist is here to help navigate the site, not for support.... And you found your way already. ?
Thread closed.
My device
(IPRO SENSEI FI)
(OS : KITKAT)
(ROOTED"Using kingoroot but I change to supersu") (ORIGINAL ROM NO CUSTOM)
(STOCK RECOVERY)
(NO HAVE ORIGINAL BACKUP OR Etc. T_T )
If you need more information Ask me.
My problem is Bootloop "Or you have another name, because I do not understand", just stop on logo but it still can go into recovery mode.
The story before the events bootloop or whatever name this problem, So as I recall before this incident I edit files and install Tweaks build.prop with applications My pimp and try other features, it works, but when I restart my device. You know what happened. when just stopped in my logo I does not do anything just to wait so that I fell asleep and when I woke up I realized this a bootloop Or what ? I do not know his name.
At that time I was just doing the usual way way., list.
(Wipe data / Factory reset)
(Wipe cache partition)
(reboot system now)
but no change
(Restore user data)
(backup user data)
(Reboot again)
Still same
(Apply update from ADB - I do not have a pc)
(Apply update from sdcard - No have ORIGINAL ROM, BACKUP ROM, CUSTOM ROM Etc.)
(Apply update from cache - I do not understand what this)
Just information There is writing on my recovery mode "Android System Recovery <3e> ALPS.KK1.MP7.V1" I do not know what this is but I show in case you need it.
Just info :
"I have submitted my problem is on the web and social media owned IPRO but no response, I also have to ask in the thread "is concerned about this issue but no response. I do not know if I really make this thread in the forum Q & A if any anyone please notifications where should I post this thread, I hope anyone can help me here, if no input on how to make this a better thread again please write your comment"
I think your reading if this type of problem?
Is it still could be improved?
Installing custom rom whether other devices can fix this? What is this due to file damage build.prop?
How to fix it?
Can you tell tutorial to solve this problem?
If you told me to look for tutorials on the internet what keywords for this problem?
What is correct I asked here or I OOT?
What do I need to make this thread or just my neighbor asking questions like this course in every thread that said key bootloop?
You do not have to answer all of them just answer that you know or your own statement to me, I am newbie please guidance, Sorry in advance, and thanks afterward
Nano.nano said:
My device
(IPRO SENSEI FI)
(OS : KITKAT)
(ROOTED"Using kingoroot but I change to supersu") (ORIGINAL ROM NO CUSTOM)
(STOCK RECOVERY)
(NO HAVE ORIGINAL BACKUP OR Etc. T_T )
If you need more information Ask me.
My problem is Bootloop "Or you have another name, because I do not understand", just stop on logo but it still can go into recovery mode.
The story before the events bootloop or whatever name this problem, So as I recall before this incident I edit files and install Tweaks build.prop with applications My pimp and try other features, it works, but when I restart my device. You know what happened. when just stopped in my logo I does not do anything just to wait so that I fell asleep and when I woke up I realized this a bootloop Or what ? I do not know his name.
At that time I was just doing the usual way way., list.
(Wipe data / Factory reset)
(Wipe cache partition)
(reboot system now)
but no change
(Restore user data)
(backup user data)
(Reboot again)
Still same
(Apply update from ADB - I do not have a pc)
(Apply update from sdcard - No have ORIGINAL ROM, BACKUP ROM, CUSTOM ROM Etc.)
(Apply update from cache - I do not understand what this)
Just information There is writing on my recovery mode "Android System Recovery <3e> ALPS.KK1.MP7.V1" I do not know what this is but I show in case you need it.
Just info :
"I have submitted my problem is on the web and social media owned IPRO but no response, I also have to ask in the thread "is concerned about this issue but no response. I do not know if I really make this thread in the forum Q & A if any anyone please notifications where should I post this thread, I hope anyone can help me here, if no input on how to make this a better thread again please write your comment"
I think your reading if this type of problem?
Is it still could be improved?
Installing custom rom whether other devices can fix this? What is this due to file damage build.prop?
How to fix it?
Can you tell tutorial to solve this problem?
If you told me to look for tutorials on the internet what keywords for this problem?
What is correct I asked here or I OOT?
What do I need to make this thread or just my neighbor asking questions like this course in every thread that said key bootloop?
You do not have to answer all of them just answer that you know or your own statement to me, I am newbie please guidance, Sorry in advance, and thanks afterward
Click to expand...
Click to collapse
I edit files and install Tweaks build.prop
Click to expand...
Click to collapse
more than likely, it is not booting because you made some bad edits to the build prop. i see this happen a lot.
you will need to find a stock firmware for your device and install it back to fix the problem.
use search terms like "(your device name) return to stock" to try and locate the files.
bweN diorD said:
more than likely, it is not booting because you made some bad edits to the build prop. i see this happen a lot.
you will need to find a stock firmware for your device and install it back to fix the problem.
use search terms like "(your device name) return to stock" to try and locate the files.
Click to expand...
Click to collapse
Thanks for your suggestions and answers, Before I made this thread I have searched from internet Stock firmware or stockrom for my device but I never found it, Is there any other way than to install stock rom or firmware to fix my device, or install a custom rom firmware or install other devices can be made in alternative
Nano.nano said:
Thanks for your suggestions and answers, Before I made this thread I have searched from internet Stock firmware or stockrom for my device but I never found it, Is there any other way than to install stock rom or firmware to fix my device, or install a custom rom firmware or install other devices can be made in alternative
Click to expand...
Click to collapse
you can try searching for a custom rom, that should fix it.
other than that, with no stock firmware, i dont see any way you could fix it.
no, you cant use files from another device, unless it specifically says its ok for your device (very rare, but happens occasionally)
bweN diorD said:
you can try searching for a custom rom, that should fix it.
other than that, with no stock firmware, i dont see any way you could fix it.
no, you cant use files from another device, unless it specifically says its ok for your device (very rare, but happens occasionally)
Click to expand...
Click to collapse
Thank you for your prompt response.
Similarity such as what should I look for when taking custom rom or files from other devices?
Nano.nano said:
Thank you for your prompt response.
Similarity such as what should I look for when taking custom rom or files from other devices?
Click to expand...
Click to collapse
look for it to say directly, it can be used on your device. thats the only way.
bweN diorD said:
because you made some bad edits to the build prop.
Click to expand...
Click to collapse
So there will be plenty of experiments,
CMIIW.
If this error in build.prop can I fix it with this way?:
-Take the backup file build.prop.bak with ADB
-Then Edit it by removing the code that previously I input
-And I input back into the system folder in my device with ADB
-And delete files that are in init.d
What a way as it could to improve my device, because I think if it's just damage build.prop file.
And if I use a custom rom whether he would change the system information such as kernel, android version, and whether he will change the code in the file build.prop and What it will also transform the tweaks in the init.d folder or even add to the pile? I think if a custom rom working to add code or tweaks both in build.prop or init.d I think it will worsen, CMIIW, because I think if true custom rom works like that then it is not a good solution
Nano.nano said:
So there will be plenty of experiments,
CMIIW.
If this error in build.prop can I fix it with this way?:
-Take the backup file build.prop.bak with ADB
-Then Edit it by removing the code that previously I input
-And I input back into the system folder in my device with ADB
-And delete files that are in init.d
What a way as it could to improve my device, because I think if it's just damage build.prop file.
And if I use a custom rom whether he would change the system information such as kernel, android version, and whether he will change the code in the file build.prop and What it will also transform the tweaks in the init.d folder or even add to the pile? I think if a custom rom working to add code or tweaks both in build.prop or init.d I think it will worsen, CMIIW, because I think if true custom rom works like that then it is not a good solution
Click to expand...
Click to collapse
1. i have no idea what CMIIW means
2. yes, if you have an original copy of the build prop or can remove edits from the current one, and can replace with adb, that would be good.
3. i would try fixing one thing at a time to see what actually caused the issue. init may or may not need to be fixed.
4. custom rom would clean and replace the entire system including kernel, so it should fix the issue. however, this is your choice, its not a bad option, just a different one.
bweN diorD said:
1. i have no idea what CMIIW means
2. yes, if you have an original copy of the build prop or can remove edits from the current one, and can replace with adb, that would be good.
3. i would try fixing one thing at a time to see what actually caused the issue. init may or may not need to be fixed.
4. custom rom would clean and replace the entire system including kernel, so it should fix the issue. however, this is your choice, its not a bad option, just a different one.
Click to expand...
Click to collapse
CMIIW is Correct Me If I'm Wrong.
Finally, I have two ways for the try, the title and content of this thread may be changed if it is successful.
Thank you for helping me
Thank you for patiently explained
Now I know what to do,
thank you for your participation
thank you very much :good:
no problem