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
Related
Hello,
My Extended ROM (which I access through an UnlockExtRom tool) has been corrupted somehow. Now I cannot read or write or edit the ExtROM. It only shows junk files with unreadable characters.
How can I clean this mess and load a clean Extended ROM package for future hard-reset needs without reinstalling a whole new AKU?
Thanks
xtrips said:
Hello,
My Extended ROM (which I access through an UnlockExtRom tool) has been corrupted somehow. Now I cannot read or write or edit the ExtROM. It only shows junk files with unreadable characters.
How can I clean this mess and load a clean Extended ROM package for future hard-reset needs without reinstalling a whole new AKU?
Thanks
Click to expand...
Click to collapse
Hi I had the same issue when unlocking the ext rom and trying to write on it.
I did not find any solution except by reflashing with an original aku.
Sorry if the answer to this is somewhere, but I just cant find an answer.
Will flashing my ROM reset everything, and will I loose all my installed software / email / contacts.
Thabks guys ...
yes you will lose everything , think of it like re-installing an operating system on a pc from scratch, you can of course, make a back-up of stuff before
hjlow said:
yes you will lose everything , think of it like re-installing an operating system on a pc from scratch, you can of course, make a back-up of stuff before
Click to expand...
Click to collapse
Thanks hjlow ...
ratzz said:
Thanks hjlow ...
Click to expand...
Click to collapse
If you flash a UC ROM you can re-install programs and configure settings automatically after flashing.
See here for more: http://forum.xda-developers.com/showthread.php?t=366337
And you can use PIM backup to backup anything you dont Active Sync (although WM6.1 SMS's can be buggy).
Ta
Dave
I will add this info to the wiki & New Guy/Gal Sticky Sticky.
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...
I know that this topic has been probably discussed, but searching for few things do not give me a good result
1. I have panel1 type and all recent nbh are for panel3. I read somewhere that there is a converter, but I cannot find the thread.
2 Is it possible to flash back a winmo rom? I guess yes, by putting the nbh in the sim card and going to bootloader, but are there fellow forum guys that did that with good success?
4. Is it possible to restore my current img files? By modifying existing l1q1d's install-seq.sh and mounting my system and data img and copying them to newly formatted system and data partitions.. or use some other backup tool? Does it worth the hassle?
5. What is the battery life when using mostly 3G for synchronization every 10 minutes and occasionally WiFi for app download. Will it last two days?
Thanks in advance
OK.. I found the editor.. silly me
Answer for 4 (i'm sorry the other are too stupid,take a look in the forum)
You can use bsb in this way:
renaming data partition as backupdisk
select restore data in bsg
select format data on nand
place install-seq.sh o andboot
reboot
wait
cheers
Can anyone shed some light on this question?
Is it possible to flash back a winmo rom? What are the steps? Could'nt find it on the forums.
Like hard resetting the device or something?
Thanks
edit: got it.
Hi, first of all, thank you for reading me.
I think i messed up big time.
I had Havoc OS 4.1 installed since more than a year and it was kinda messy e.g. the sim card card wasnt recognized anymore so wasnt able to make calls because i played to much in the settings.
Having some stupid but incredibly addictive games on this smartphone i decided to keep it like this and since i'm a complete n00bs and being afraid of security risk of rooting my device i never rooted it.
Big mistake.
So, recently, one games needed an update (like they all do at least once a week) and since i'm anti-google/f***book (no comment please) i nvever saved my progress in the cloud and "that" game required absolutely an update.
I installed the update from an alternative apk source and , (applause if you want and laugh), it screwed up the game.
Now the nightmare begin.
Since the device isnt rooted i made a backup of /data partition. Gone crazy and before i might explode in an uncontrollable fury and madness i used LMSA to rescue the phone. And myself, lol.
Now i have stock android and i am googled to the bone. My butt hurts. My head too.
THE (first) simple question is : how can i restore this backup because i have the error 255?
Notes and observations; logically i would say because the device is back with stock rom and doesnt have the same os/rom installed and/or the partition and whatever is not the same wich may explain the error 255.
SECOND QUESTION: can i extract/uncompress this backup and take the precious data wich is my games progresses and restore it somehow?
I know i have to give as much information possible but i dont what else to give. If you need logs, or everything else just say it nicely and i will give it to you with immense pleasure.
Oh yeah, model : XT2113-2 5g Kiev RETCA 128gb a/b type and maybe was crypted before because twrp asked me the password to make backup or else.
Thank you in advance and i really hope somebody would help, if not i just loosed 1.5 years of stupid gaming because i messed up like an idiot. (A lesson well learned, the hard way...)
Thank you so much for not answering this simple question.
Kerplunk83 said:
Thank you so much for not answering this simple question.
Click to expand...
Click to collapse
The problem is it's a Motorola with a Qualcomm chip.
If you find a solution I would love to see it.
Finally a sign of life from someone here.
Thank you sd_shadow
sd_shadow said:
The problem is it's a Motorola with a Qualcomm chip.
If you find a solution I would love to see it.
Click to expand...
Click to collapse
These precious brief and concise 2 lines of a simple answer is immensely welcomed.
Wich point me to reply that to my knowledge i interpret it as a security chip with big chances that its in relation to the knox technology.
It also point me to ask WHY, if i cant back up because of that, why/how is it possible to install a custom rom or gsi (sorry i still dont make the difference because i dont understand it) on this very protected smartphone?
That must explain why i had problems trying to root it and fail each time.
Finally i think that i should use another device for android gaming since i dont want to depend on f***book and google.
Thanks again sd_shadow. Even if it was a very simple answer it enlightens me alot.
Note: sorry for my bad english.
Kerplunk83 said:
how can i restore this backup because i have the error 255?
Click to expand...
Click to collapse
This error code means that at some point your backup of /data could not be extracted further. But for more detailed infos you must provide a recovery.log which will be generated when doing a backup of e.g. /boot.
>>> Please DO NOT copy+paste it here!! <<<​Rename it (recovery.log > recovery.log.txt) to be able to upload it within "Attach files".
Kerplunk83 said:
can i extract/uncompress this backup and take the precious data wich is my games progresses and restore it somehow?
Click to expand...
Click to collapse
Yes, use Titanium Backup (TB). Although it's very outdated it still features a restore of single apps out of a TWRP backup. Here's how you do it:
1. IMPORTANT: TB will only search for TWRP backup files on internal storage!! Use the default path created by TWRP, e.g.: /sdcard/TWRP/BACKUPS/ZY322V8K28/2023-04-08--06-53-20/
2. Install and open Titanium Backup.
3. In the upper right corner tap
MENU > scroll down to "Extract from Nandroid backup" > choose your backup folder
##############
Notes:
- Usually a TWRP backup of /data consists of several parts (data.ext4.win000, ~win001, ~win002 etc). TB requires all of them (or at least those ones with the /data/data/ path inside).
- If you are facing this error message:
Could not find any data in this TWRP backup
then your TWRP backup is compressed with gzip. To decompress it you must rename the file
data.ext4.win001 > data.ext4.win001.gz
and extract it with any archiver tool, e.g.:
- ZArchiver (Android)
- 7zip (Windows)
- Problems finding any TWRP backup data with Titanium Backup? Then please check your path!! (see above section)
Good luck!!
Thank you very much WoKoschekk i'll do it as soon i'll have the time for since i'm working today.
Thank you so much again, i'll keep you posted with logs and such.
I'm sorry i didnt gave news since, i'm not doing very well.
there's those 2 question i still have in my head;
1-With all the instructions you gave me is it worthy to continue because when i did the backup i wasnt rooted?
2- i'm sure i read many time to use Titanium Backup (wich is a paid app?) i have to be rooted or have root access.
Ultimately, how can i be rooted if there's a chip preventing me to do so?
I'll keep you posted when i'll be of better health, thank you.
Kerplunk83 said:
-With all the instructions you gave me is it worthy to continue because when i did the backup i wasnt rooted?
Click to expand...
Click to collapse
TWRP backup = *.tar archive
TB unpacks the needed app's data and nothing else. You must be rooted to have access on /data for restoring your apps. But for the backup process it doesn't matter if you were rooted. Root is part of your boot.img.
Kerplunk83 said:
2- i'm sure i read many time to use Titanium Backup (wich is a paid app?) i have to be rooted or have root access.
Click to expand...
Click to collapse
TB is for free. But a paid version unlocks additional features (not related to the TWRP restoring feature).
And yes... root is mandatory for TB. As I said before you must have r/w access on /data/*.
Kerplunk83 said:
if there's a chip preventing me to do so?
Click to expand...
Click to collapse
Which chip?? You already have root access via TWRP. Magisk is only needed in system and just a patched boot.img (custom kernel).
Get well soon!
WoKoschekk thank you for this insanely fast reply.
All those answers and infos have now a gigantic value for me, if only i knew that before.
To describe a bit more my situation i slept only few hours since 5 days, vomiting, heavy coughs and fever.
I'm sure i'm not supposed to but i will anyway, i engage myself and promise to reward you (in particular) and others for the help you're bringing me. It wont be much but very important to me.
I'll go try to get (again) some rest. Just before i go, why was there a mention about my device;
"
The problem is it's a Motorola with a Qualcomm chip.
If you find a solution I would love to see it.
"
I dont ask you (WoKoschekk) or other to explain in the most explicit and endless details of what is exactly this "chip" and all the history that goes with it cause i dont want to be a pain but just why it was mentionned. Only, why?, it has ben mentionned.
I cant wait to get better since i finally see possibilities to get back those files.
Have a nice week-end and thanks again.
@Kerplunk83 To reveal the mystery behind "the chip": Motorola released two variants (Snapdragon/Mediatek CPU) of this model. Since the CPU largely determines the system structure, building a functional TWRP for both of them is very challenging. It seems that TWRP for the SD's variant got some bugs while the MT's variant runs more smooth. Due to this fact the error 255 is caused by something that you weren't be able to fix.
Regarding your problem: To restore an app and its specific app data you need the proper permissions to write in /data/data and /data/app. For this permissions you either need TWRP or Magisk installed. TWRP seems to be unable to write in that specific directory. On the other hand you don't want to install Magisk. I'm sorry but with this setup your problem can't be fixed.
Just out of curiosity, could you provide me a recovery.log showing error 255 during the restore process?
Please DO NOT copy/paste the whole log and post it here!! Instead of this you should rename the file (recovery.log => recovery.txt) because a file called *.log isn't allowed for upload. But a *.txt file is.
Options to create a recovery.log:
1. adb pull /tmp/recovery.log
=> copies a recovery.log into your ADB/fastboot folder
2. Do a backup of sth. like "boot" because the backup process will create a recovery.log by default
3. TWRP mainscreen > advanced > create log (kernel log isn't needed here)
=> log is stored on the default storage (internal or external) that you have choosen for backups etc.