Related
Hi,
One year ago, I successfully installed Windows 8 Consumer Preview. Since its asked me for license, I've bought Win8 Pro but the problem is that it won't let me keep my files in the installation. The only option Win8 install shows is the clean install as "nothing".
How to install Win8 Pro with keeping my desktop, files... ?
Thx in advance !
Are you are trying to upgrade from a beta copy of Windows 8 to the final retail version? I don't think that will be an option. You'll need to back up your files to a USB drive or something and do a fresh install.
Yes indeed. Why wont that be possible ?
The consumer preview is an unfinished version of Windows, it's possible issues with that could carry over with an upgrade to the retail version and cause head aches for Microsoft or anyone else that has to troubleshoot any problems that might occur.
I would expect that "keep my files (but not my programs)" would be a valid option, though... very odd if it is not. That's basically still a clean install, it just moves everything from the old OS (except your personal libraries) to a "Windows.old" folder.
kinder771 said:
Yes indeed. Why wont that be possible ?
Click to expand...
Click to collapse
From what I've read, you will have to do a clean install. Microsoft wants to make sure none of the preview stuff is mixed in with the official release files.
Sent from my IdeaTabA2109A using xda premium
GoodDayToDie said:
I would expect that "keep my files (but not my programs)" would be a valid option, though... very odd if it is not. That's basically still a clean install, it just moves everything from the old OS (except your personal libraries) to a "Windows.old" folder.
Click to expand...
Click to collapse
Yeah that's true, however I'd like to keep evrything... The only solution is to do the clean install...
Thx everyone !
kinder771 said:
The only option Win8 install shows is the clean install as "nothing".
How to install Win8 Pro with keeping my desktop, files... ?
Thx in advance !
Click to expand...
Click to collapse
It is not an option - either clean install or nothing.
Sorry
Yeah I finally did the clean install...
I have recentally purchaed the Mojo Mad Catz Device. I have successfully root the device. But i am not comfortable with the rooting. There is lot of apps crashing. I want to re-install the original firmware and un root my device. I have download the firmware. Can some one tell me how do i re-install this software on the Mojo. I have already apply the factory reset. But it did not work. I want to re-install factory software through the memory card or the usb. Thanks for helping me. If someone has solve my problem. I want install the mojo signed ota firmware.
robotics909 said:
I have recentally purchaed the Mojo Mad Catz Device. I have successfully root the device. But i am not comfortable with the rooting. There is lot of apps crashing. I want to re-install the original firmware and un root my device. I have download the firmware. Can some one tell me how do i re-install this software on the Mojo. I have already apply the factory reset. But it did not work. I want to re-install factory software through the memory card or the usb. Thanks for helping me. If someone has solve my problem. I want install the mojo signed ota firmware.
Click to expand...
Click to collapse
I assume you have only rooted it, if so, you can use the 'update app', put the zip file on a USB/SDcard and load it, it will unroot the mojo.
I doubt unrooting it will help with crashing apps though.
If you have installed lollypop firmware, then you should have made a backup using the new recovery, I don't think you can revert back to original using only the firmware file
Firmware Re-Installation.
gwaldo said:
I assume you have only rooted it, if so, you can use the 'update app', put the zip file on a USB/SDcard and load it, it will unroot the mojo.
I doubt unrooting it will help with crashing apps though.
If you have installed lollypop firmware, then you should have made a backup using the new recovery, I don't think you can revert back to original using only the firmware file
Click to expand...
Click to collapse
I have only root the devise from the instruction on the Mojo page. After doing this my mojo is as new as this devise comes from the mojo company
Firmware Installation.
gwaldo said:
I assume you have only rooted it, if so, you can use the 'update app', put the zip file on a USB/SDcard and load it, it will unroot the mojo.
I doubt unrooting it will help with crashing apps though.
If you have installed lollypop firmware, then you should have made a backup using the new recovery, I don't think you can revert back to original using only the firmware file
Click to expand...
Click to collapse
Have you check it or test it.
robotics909 said:
Have you check it or test it.
Click to expand...
Click to collapse
Yes, many times, it removes root, I prefer mojo-signed-ota-MO0202-WW.zip from ftp://86.54.116.234/pub/software/mojo/firmware/
Firmware Re-Installation.
gwaldo said:
Yes, many times, it removes root, I prefer mojo-signed-ota-MO0202-WW.zip from
My Mojo comes with MO205. Its mean i can install the old version of MO202. Do you mean that MO0202 is better then MO205.
Click to expand...
Click to collapse
robotics909 said:
gwaldo said:
Yes, many times, it removes root, I prefer mojo-signed-ota-MO0202-WW.zip from
My Mojo comes with MO205. Its mean i can install the old version of MO202. Do you mean that MO0202 is better then MO205.
Click to expand...
Click to collapse
Yes, I've reverted from 205, to 202.
MO205 has 4k support and ouya, 202 does not.
I don't use 4k nor ouya.
MO205 has the multitask (semi long press of madcatz on button) not working 100% of the time, which to me, is more a important feature.
Click to expand...
Click to collapse
Firmware Re-Installation.
gwaldo said:
robotics909 said:
Yes, I've reverted from 205, to 202.
MO205 has 4k support and ouya, 202 does not.
I don't use 4k nor ouya.
MO205 has the multitask (semi long press of madcatz on button) not working 100% of the time, which to me, is more a important feature.
Click to expand...
Click to collapse
You are great. I think Mad Catz should hire you as a consultant. Do you know they gave me this solution for the unroot. They gave me two solution. And these are very non professional method. I am new user and i cant do that. but you are the best.
First Solution
Once the device is rooted there usually is not a way of un-rooting.
You can possibly try the follwoing, but it has not been tested yet.
1) you device you need to go back to the folder where you droidxroot files normally
for me this was c:\droidxroot_v2
then do follow some steps from the root process
Run "adb push exploid /sqlite_stmt_journals/exploid"
Run "adb shell"
Run "cd sqlite_stmt_journals"
Run "chmod 755 exploid"
On your phone, navigate to a screen where you can switch wifi/bluetooth on/off easily (settings, or a home screen with a widget)
IMMEDIATELY after executing the next step, toggle wifi or bluetooth off and back on
Run "./exploid" and follow directions on screen. Once this completes you'll be back at a shell prompt.
Run "rootshell". You'll be prompted for a password.
Type in password "secretlol" and press Enter then you are root! (You'll know because your prompt will now be a "#" instead of "$")
now this is were things change instead of copying the files we will remove them
rm /system/app/Superuser.apk
rm /system/bin/su
rm /system/bin/busybox
finally remove the rootshell
rm /system/bin/rootshell
reboot
If this does not work you will need to replace your device.
2nd Solution :-
Greetings from Mad Catz,
I apologize for the delayed response and for the issues you are experiencing. We greatly appreciate you as a customer and a supporter. If you could provide an attached picture of a proof of purchase I can warranty the unit for you. You have a two year warranty with an approved proof of purchase. A proof of purchase constitutes as a physical receipt, email conformation, a screen shot of a purchase history via a website where the product was purchased from, packing slip, debit/credit statements, or an order number only if purchased via gameshark.com.
We can swap your rooted mojo for one that is not rooted.
Click to expand...
Click to collapse
robotics909 said:
gwaldo said:
You are great. I think Mad Catz should hire you as a consultant. Do you know they gave me this solution for the unroot. They gave me two solution. And these are very non professional method. I am new user and i cant do that. but you are the best.
First Solution
Once the device is rooted there usually is not a way of un-rooting.
You can possibly try the follwoing, but it has not been tested yet.
1) you device you need to go back to the folder where you droidxroot files normally
for me this was c:\droidxroot_v2
then do follow some steps from the root process
Run "adb push exploid /sqlite_stmt_journals/exploid"
Run "adb shell"
Run "cd sqlite_stmt_journals"
Run "chmod 755 exploid"
On your phone, navigate to a screen where you can switch wifi/bluetooth on/off easily (settings, or a home screen with a widget)
IMMEDIATELY after executing the next step, toggle wifi or bluetooth off and back on
Run "./exploid" and follow directions on screen. Once this completes you'll be back at a shell prompt.
Run "rootshell". You'll be prompted for a password.
Type in password "secretlol" and press Enter then you are root! (You'll know because your prompt will now be a "#" instead of "$")
now this is were things change instead of copying the files we will remove them
rm /system/app/Superuser.apk
rm /system/bin/su
rm /system/bin/busybox
finally remove the rootshell
rm /system/bin/rootshell
reboot
If this does not work you will need to replace your device.
2nd Solution :-
Greetings from Mad Catz,
I apologize for the delayed response and for the issues you are experiencing. We greatly appreciate you as a customer and a supporter. If you could provide an attached picture of a proof of purchase I can warranty the unit for you. You have a two year warranty with an approved proof of purchase. A proof of purchase constitutes as a physical receipt, email conformation, a screen shot of a purchase history via a website where the product was purchased from, packing slip, debit/credit statements, or an order number only if purchased via gameshark.com.
We can swap your rooted mojo for one that is not rooted.
Click to expand...
Click to collapse
ahh, wow, that's pretty complicated stuff.. it took me a while to setup adb and I use linux daily.
"secretlol" lol, I don't know what that instruction really does, if enabled root on a command console, you could just remove the rootshell
rm /system/bin/rootshell
Click to expand...
Click to collapse
I'm no android expert.
Anyway.. I'm now doubting myself :/
As I said I tried 205, rooted it (oh another reason, root didn't unlock as many apps like it does in 202 BTW).
When I reverted to 202, I'm *sure* I had to reroot it.. I might have been for play store, it was over 8 months ago now, so don't thank me yet.
But like I said, I don't think root would cause apps to crash
Click to expand...
Click to collapse
Firmware Re-Installation.
gwaldo said:
robotics909 said:
ahh, wow, that's pretty complicated stuff.. it took me a while to setup adb and I use linux daily.
"secretlol" lol, I don't know what that instruction really does, if enabled root on a command console, you could just remove the rootshell
I'm no android expert.
Anyway.. I'm now doubting myself :/
As I said I tried 205, rooted it (oh another reason, root didn't unlock as many apps like it does in 202 BTW).
When I reverted to 202, I'm *sure* I had to reroot it.. I might have been for play store, it was over 8 months ago now, so don't thank me yet.
But like I said, I don't think root would cause apps to crash
Click to expand...
Click to collapse
I have downloaded the firmware 202. Tomorrow I will try to upload it into my mojo. Their is any instruction for that. Or i just put it zip file and upload it from the mojo software uploader. I have already on the 205 with the rooted. When I installed firmware 202. Do i need to root this also or it works fine without rooting. Wifi is very unstable int his device. Do you also solution for this also.
Regards,
Click to expand...
Click to collapse
robotics909 said:
gwaldo said:
I have downloaded the firmware 202. Tomorrow I will try to upload it into my mojo. Their is any instruction for that. Or i just put it zip file and upload it from the mojo software uploader. I have already on the 205 with the rooted. When I installed firmware 202. Do i need to root this also or it works fine without rooting. Wifi is very unstable int his device. Do you also solution for this also.
Regards,
Click to expand...
Click to collapse
no instructions, just select the zip file, it will reboot boot, stay off for awhile then start (best to leave it for a few minutes).
it works fine with or without root, I like root tho.
Wifi, is typical android.. and not the best but it's stable for me, maybe play with position of the mojo, ie put it in line of sight and not obstructed.
202 does have ethernet issues (freezes on large downloads) I think 205 fix that issue, (I don't use ethernet).
Good luck.
Click to expand...
Click to collapse
robotics909 said:
gwaldo said:
I have downloaded the firmware 202. Tomorrow I will try to upload it into my mojo. Their is any instruction for that. Or i just put it zip file and upload it from the mojo software uploader. I have already on the 205 with the rooted. When I installed firmware 202. Do i need to root this also or it works fine without rooting. Wifi is very unstable int his device. Do you also solution for this also.
Regards,
Click to expand...
Click to collapse
For me I just fastboot boot twrp recovery. Downloaded the SuperSu zip from chainfire. Once in recovery I flashed stock rom and flashed super su zip and everything was fine. After that I created a backup.
Click to expand...
Click to collapse
console mojo brique suite a une mauvaise manipulation une idée
gwaldo said:
Yes, many times, it removes root, I prefer mojo-signed-ota-MO0202-WW.zip from ftp://86.54.116.234/pub/software/mojo/firmware/
Click to expand...
Click to collapse
05f2b97a69d9b3489ba0b5b5822b8cb3d2e1c58f
robotics909 said:
gwaldo said:
Yes, many times, it removes root, I prefer mojo-signed-ota-MO0202-WW.zip from
My Mojo comes with MO205. Its mean i can install the old version of MO202. Do you mean that MO0202 is better then MO205.
Click to expand...
Click to collapse
Sent from my LGE LM-X210APM using XDA Labs
---------- Post added at 08:06 PM ---------- Previous post was at 08:00 PM ----------
gwaldo said:
Yes, many times, it removes root, I prefer mojo-signed-ota-MO0202-WW.zip from ftp://86.54.116.234/pub/software/mojo/firmware/
Click to expand...
Click to collapse
05f2b97a69d9b3489ba0b5b5822b8cb3d2e1c58f
robotics909 said:
gwaldo said:
Yes, many times, it removes root, I prefer mojo-signed-ota-MO0202-WW.zip from
My Mojo comes with MO205. Its mean i can install the old version of MO202. Do you mean that MO0202 is better then MO205.
Click to expand...
Click to collapse
Sent from my LGE LM-X210APM using XDA Labs
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I have a WinBook TW800 from Micro Center. I wanted to load Windows 10 on it, has anyone on here done this? Maybe you can give me tips\pointers on how to go about doing this; is the update method better or would a clean install be the ideal way? Thanks for your help in advanced.
Well I got my answer today while trying to do it via the update way. I got an error that my tablet wasn't able to upgrade because the OS is compressed something about Boot WIM. SMH.
sinister1 said:
Well I got my answer today while trying to do it via the update way. I got an error that my tablet wasn't able to upgrade because the OS is compressed something about Boot WIM. SMH.
Click to expand...
Click to collapse
I can help you install it, in fact, I can make a guide. I have the TW801 and everything is working properly.
TravisAntonio said:
I can help you install it, in fact, I can make a guide. I have the TW801 and everything is working properly.
Click to expand...
Click to collapse
Cool, I will appreciate it. Thanks.
Any luck on getting a guide posted
Sorry for taking ages, I totally forgot about this.
http://forum.xda-developers.com/windows-10/general/guide-install-windows-10-tw800-801-t3069958
is it for free?
Issues
I'm having issues too. I don't think the 800 has enough space to do the install. The 801 seems like a better option due to the 16gb of storage, vs the 8gb on the 800.
TravisAntonio said:
Sorry for taking ages, I totally forgot about this.
http://forum.xda-developers.com/windows-10/general/guide-install-windows-10-tw800-801-t3069958
Click to expand...
Click to collapse
I will try it this some time this week. Thanks.
No luck
Apparently I can't because the memory is full so I basically can't do anything with this POS. I can't back it up or restore it or add anything to it, it actually runs out of disk space when uninstalling stuff.
I successfully installed Windows 10 on my TW-801 I first installed internally (internal installation failed) and then installed again via the sdcard (so you have to burn the win image to the sdcard for the second install in addition to doing the download for the first install). The second time Windows 10 was activated. I am also running Ubuntu with VMWare on a virtual machine on this tablet. Windows 10 is alot better than 8.1 on this tablet. I think even though the internal installation fails it saves the Windows 10 activation code and the second install works because it is not a download and is directly from the cd or in this case the sd. Also, during the first download (that fails) two files are created on the c drive that I copied to the sdcard that I had already burned the win image on it - I don't know if that did anything or not.
Hey guys, a new version of Phoenix OS (v2.0.7) is out and I have created rooted images for you guys to use.
Instructions:
Download the correct system rooted.7z file provided in the Download section and extract it
Install Phoenix OS and restart your computer.
Boot into Phoenix OS and finish the system initialization wizard. Restart the computer and boot into your main OS.
Go to C:\Phoenix OS (or wherever your Phoenix OS installation is) and replace the system.img file that's already there with the one you just downloaded
Reboot your computer now and boot into Phoenix OS.
Install the latest version of SuperSU. Sign in to Play Store using your Google account and update SuperSU that way. If you for some reason cannot use the Play Store, you can find SuperSU on the official thread. Download the flashable zip, extract Superuser.apk from the common folder, and install it in Phoenix OS by opening the .apk file with the default file manager that comes with the OS.
Update the binary by choosing Normal and your Phoenix OS should now be fully rooted
Download:
Phoenix OS x86 v2.0.7 (13 June) Rooted Image + original system.img + PhoenixOSInstaller_v2.0.7.151.32bit.exe
https://drive.google.com/drive/folders/0B_UTWXKFnZoNVGpBZmxQS0dhRjg
Phoenix OS x64 v2.0.7 (13 June) Rooted Image + original system.img + PhoenixOSInstaller_v2.0.7.150.64bit.exe
https://drive.google.com/drive/folders/0B_UTWXKFnZoNclN5SGdFUGlTRGs
Download Phoenix OS v2.0.7 here (original thread):
http://bbs.phoenixstudio.org/en/showthread.php?tid=6186
History:
Uploaded v2.0.7 system images
Oooh... now I can test this to see if it fixes my G+ compatibility issue
The Wrath of Kahn said:
Oooh... now I can test this to see if it fixes my G+ compatibility issue
Click to expand...
Click to collapse
Sure! Let us know if it works out well for you
meanhacker said:
Sure! Let us know if it works out well for you
Click to expand...
Click to collapse
Sadly, no. It is rooted successfully and everything else seems fine, but "device not compatible" again. Unfortunately this is a deal killer for me =/
The Wrath of Kahn said:
Sadly, no. It is rooted successfully and everything else seems fine, but "device not compatible" again. Unfortunately this is a deal killer for me =/
Click to expand...
Click to collapse
Did you try both, the 32 and 64 bit versions? I will try it on my Surface Pro 3 sometime and will let you know my results. Meanwhile, you can post it on their official forum and let them know that G+ isn't working
meanhacker said:
Did you try both, the 32 and 64 bit versions? I will try it on my Surface Pro 3 sometime and will let you know my results. Meanwhile, you can post it on their official forum and let them know that G+ isn't working
Click to expand...
Click to collapse
Only tried 64 bit... guess I could give 32 bit a shot. Tomorrow then...
The Wrath of Kahn said:
Only tried 64 bit... guess I could give 32 bit a shot. Tomorrow then...
Click to expand...
Click to collapse
I tried opening G+ on the v2.0.6 and got the same error as you. Perhaps you can use the browser to browse G+ for now until a solution is available? Also, look into spoofing your deice model into a model of an actual tablet. Maybe that will work if you edit the build.prop file.
If anyone get's "grub minimal bash like line editing issue" when trying to boot
Hi I just tried phoenix OS. yesterday on my unbranded baytrail tablet (ub15ms10) I was stuck with this issue for a while and I finally came up with the fix using the grub prompt! (I used "rufus" to create the boot usb drive)
First, list your drives with ls ls Mine came up with hd0 and some others, but since I was booting from a usb drive, that's all that matters at the moment. hd0 will be the drive that you need so set it as the target and below is basically what you need to type to try it out without installing.
set root=(hd0,1)
linux /kernel root=/dev/ram0
initrd /initrd.img
boot
You should then be able to boot Pheonix OS 2.0.7 32bit. I did not try the 64bit version since there's no point because tablet has less then 4GB of RAM. What works: It makes good use of the tablet's GPU, it didn't lag in anyway for games such as clash royal. Browsing is good, playstore works..The performance is nice, It runs well on a 2GB ram tablet with a 1.3Ghz Intel Atom Z3735F. GPS works, bluetooth works.
What doesn't work: No audio, no brightness control. I didn't bother testing anything else since I lost interest as soon as audio didn't work. I'd probably be able to fix it myself by messing around with the kernel parameters but it's a PITA.
meanhacker said:
I tried opening G+ on the v2.0.6 and got the same error as you. Perhaps you can use the browser to browse G+ for now until a solution is available? Also, look into spoofing your deice model into a model of an actual tablet. Maybe that will work if you edit the build.prop file.
Click to expand...
Click to collapse
I tried editing the build.prop before with no luck, but I'm not experienced in doing it so I may have missed the fields that I needed.
irex102 said:
Hi I just tried phoenix OS. yesterday on my unbranded baytrail tablet (ub15ms10) I was stuck with this issue for a while and I finally came up with the fix using the grub prompt! (I used "rufus" to create the boot usb drive)
First, list your drives with ls ls Mine came up with hd0 and some others, but since I was booting from a usb drive, that's all that matters at the moment. hd0 will be the drive that you need so set it as the target and below is basically what you need to type to try it out without installing.
set root=(hd0,1)
linux /kernel root=/dev/ram0
initrd /initrd.img
boot
You should then be able to boot Pheonix OS 2.0.7 32bit. I did not try the 64bit version since there's no point because tablet has less then 4GB of RAM. What works: It makes good use of the tablet's GPU, it didn't lag in anyway for games such as clash royal. Browsing is good, playstore works..The performance is nice, It runs well on a 2GB ram tablet with a 1.3Ghz Intel Atom Z3735F. GPS works, bluetooth works.
What doesn't work: No audio, no brightness control. I didn't bother testing anything else since I lost interest as soon as audio didn't work. I'd probably be able to fix it myself by messing around with the kernel parameters but it's a PITA.
Click to expand...
Click to collapse
For the audio and other issues for baytrail/cherrytrail devices, someone made a kernel that apparently fixes these issues in debian/ubuntu which can be found here: https://yadi.sk/d/pW1Fbl-VyVPoR/Linux 4.12/Linux 4.12rc5. If someone else could use these kernels sources to apply a patch for android x86 that would be awesome.
irex102 said:
For the audio and other issues for baytrail/cherrytrail devices, someone made a kernel that apparently fixes these issues in debian/ubuntu which can be found here: https://yadi.sk/d/pW1Fbl-VyVPoR/Linux 4.12/Linux 4.12rc5. If someone else could use these kernels sources to apply a patch for android x86 that would be awesome.
Click to expand...
Click to collapse
Hey I found some readied kernels that fixes all the issues on baytrail tablets for android x86 7.1: https://drive.google.com/drive/folders/0B1HDhURlGNctY045UWFhalo5MW8 All that's left is to patch a rom for these devices. More info found here: https://github.com/burzumishi/linux-baytrail-flexx10/issues/12#issuecomment-309275211
#Quest
i'm already install phoenix os latest version, can i replace old system.img with system.img rooted without uninstall my latest phoenix os already installed on my pc?
Nicojoy said:
i'm already install phoenix os latest version, can i replace old system.img with system.img rooted without uninstall my latest phoenix os already installed on my pc?
Click to expand...
Click to collapse
What version of Phoenix OS do you have installed? If you have v2.0.7, you're in the right thread, so go ahead and download either a 32 or 64-bit version of the rooted image and replace it with your current system.img.
This will work on a Nexus 9 or it only works in pc's?
when i update su binary like you say it says to me installation failed
edit: ifound soulition its to update super su to the latest version with play store or aptoide or arc market or app vn and the install the binary data its soooo easyyyyyyy
Waiting for rooted system.img for Phoenix OS 2.1.0
SU Binary busy?
So I followed the instructions (although the step 6 is kind of confusing, English is not my native language so...) booted with the rooted sys image, installed superSU from the Play Store and when I open it it says "SU binary busy" and send me to a FAQ where it says that
"The SU files are already occupied by other software, such as Kingroot."
So I need to install the binary somehow? or something went wrong?
Oh BTW, used Root checker and it says it's not propely installed
Thanks for the image, buddy
MrSlenderman said:
"The SU files are already occupied by other software, such as Kingroot."
Click to expand...
Click to collapse
I also ran into this problem using the newest version from the play store, I could avoid this though by installing version 2.79 through an apk.
But now it won't let me update the binary, since everytime I select "Normal" the installation fails after a minute or so.
Any ideas?
Guys, when to expect a rooted image for V 2.1.0 x86
thank you, but i bit confused about when i update the os,
so when i update the os, the rooted image will gone ? and i need to wait for another rooted image ?
After considering the pros and cons of upgrading (mainly I would like to see if it fixes issues that I am experiencing with custom roms), I have decided that I would like to upgrade the firmware on my G4 to v29a. However, I would like to make a backup of my current firmware (I believe booloader and modem are the parts that cannot be backed up with TWRP), and I was wondering how I would back those up.
Also, should I need to restore these backups, how would I do it?
Thanks
ThePiGuy said:
After considering the pros and cons of upgrading (mainly I would like to see if it fixes issues that I am experiencing with custom roms), I have decided that I would like to upgrade the firmware on my G4 to v29a. However, I would like to make a backup of my current firmware (I believe booloader and modem are the parts that cannot be backed up with TWRP), and I was wondering how I would back those up.
Also, should I need to restore these backups, how would I do it?
Thanks
Click to expand...
Click to collapse
Latest unofficial TWRP backups bootloader and firmware (if you select it)
Nevertheless I ALWAYS recommend to do a backup with SALT at least once as this backups really EVERYTHING ( full mode can even backup your full internal storage which can NOT be done with TWRP) . A SALT backup is just a double protection as a full TWRP backup is usually all you need.
Restore in TWRP your TWRP backup and for SALT backup files you would use TWRP plus the dd command in an adb shell if needed (e.g. dd if=/sdcard/cust.image of=/dev/block/bootdevice/by-name/cust).
But again: restoring SALT backup files is for the worst case only.. But for that case it's good to have them..
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Latest unofficial TWRP backups bootloader and firmware (if you select it)
Click to expand...
Click to collapse
Would you recommend latest Marshmallow or Nougat unofficial TWRP (I'm backing up Marshmallow but I would be restoring it from Nougat or Oreo)?
ThePiGuy said:
Would you recommend latest Marshmallow or Nougat unofficial TWRP (I'm backing up Marshmallow but I would be restoring it from Nougat or Oreo)?
Click to expand...
Click to collapse
If you do not encrypt just choose latest N one. Regardless of which ROM you currently use or will use in the future.
Sent from my LG-H815 using XDA Labs
steadfasterX said:
If you do not encrypt just choose latest N one. Regardless of which ROM you currently use or will use in the future.
Click to expand...
Click to collapse
Ok thanks. I just booted into it and had a look at the backup - I can see bootloader, and I can also see Carrier. Is the Carrier option the modem that is referred to in the v29a update?
ThePiGuy said:
Ok thanks. I just booted into it and had a look at the backup - I can see bootloader, and I can also see Carrier. Is the Carrier option the modem that is referred to in the v29a update?
Click to expand...
Click to collapse
Nope. Firmware = Modem
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Nevertheless I ALWAYS recommend to do a backup with SALT at least once as this backups really EVERYTHING ( full mode can even backup your full internal storage which can NOT be done with TWRP) . A SALT backup is just a double protection as a full TWRP backup is usually all you need.
Restore in TWRP your TWRP backup and for SALT backup files you would use TWRP plus the dd command in an adb shell if needed (e.g. dd if=/sdcard/cust.image of=/dev/block/bootdevice/by-name/cust).
But again: restoring SALT backup files is for the worst case only.. But for that case it's good to have them.
Click to expand...
Click to collapse
I have just tried to do a backup with SALT, and it was working really well and then it froze on the System backup. Looking in the log, it appears there has been a timeout error. Could this have been because my Ubuntu VM locked whilst the backup was happening?
ThePiGuy said:
I have just tried to do a backup with SALT, and it was working really well and then it froze on the System backup. Looking in the log, it appears there has been a timeout error. Could this have been because my Ubuntu VM locked whilst the backup was happening?
Click to expand...
Click to collapse
Well there is one open issue in SALT atm: it does not warn you about too less disk space. The result is it freezes on backup if you have not 32 GB disk space available and choosen the full backup.
In VirtualBox you can setup shared folders which then can be auto mounted on FWUL (choose persistent folder and to auto mount in vbox settings)
Choose a folder with at least 32 GB free space and choose that one in SALT.
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Well there is one open issue in SALT atm: it does not warn you about too less disk space. The result is it freezes on backup if you have not 32 GB disk space available and choosen the full backup.
In VirtualBox you can setup shared folders which then can be auto mounted on FWUL (choose persistent folder and to auto mount in vbox settings)
Choose a folder with at least 32 GB free space and choose that one in SALT.
Click to expand...
Click to collapse
My VM has 58GB free space at the moment. The python error in the log was a usb timeout error
ThePiGuy said:
My VM has 58GB free space at the moment. The python error in the log was a usb timeout error
Click to expand...
Click to collapse
What FWUL version? Persistent or forgetful? If forgetful the disk size is defined by the RAM. If persistent the max avail is 30 GB. So out of the box none of them can handle a full backup atm without modifications..
...or do you have mounted a 58 GB disk in vbox and store the backup there?
Some devices / firmwares got a timeout issue like you describe in big partitions. I adjusted the timeouts already and fixed it for the most ppl. If that happens go to advanced menu and grab the log. Use a pastebin service like hastebin or pastebin and share the link
Sent from my LG-H815 using XDA Labs
steadfasterX said:
What FWUL version? Persistent or forgetful? If forgetful the disk size is defined by the RAM. If persistent the max avail is 30 GB. So out of the box none of them can handle a full backup atm without modifications..
...or do you have mounted a 58 GB disk in vbox and store the backup there?
Some devices / firmwares got a timeout issue like you describe in big partitions. I adjusted the timeouts already and fixed it for the most ppl. If that happens go to advanced menu and grab the log. Use a pastebin service like hastebin or pastebin and share the link
Click to expand...
Click to collapse
I wasn't running it in FWUL - I already had a Ubuntu 16.04.3 LTS VM set up so I was backing up in there, and the allocated disk space for the VM had 58GB free. It only had 4GB RAM allocated though, so maybe this caused an issue. I can try again on a true Ubuntu machine to see if the VM was the issue
ThePiGuy said:
I wasn't running it in FWUL - I already had a Ubuntu 16.04.3 LTS VM set up so I was backing up in there, and the allocated disk space for the VM had 58GB free. It only had 4GB RAM allocated though, so maybe this caused an issue. I can try again on a true Ubuntu machine to see if the VM was the issue
Click to expand...
Click to collapse
Just use your Ubuntu one is fine!
The RAM is just interesting when we talk about FWUL forgetful.
So just do it again and when it happens again grab the log as mentioned above.
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Just use your Ubuntu one is fine!
The RAM is just interesting when we talk about FWUL forgetful.
So just do it again and when it happens again grab the log as mentioned above.
Click to expand...
Click to collapse
I just ran it on a native Ubuntu machine and it worked perfectly - I think the USB timeout must have been my VM.
Just out of interest, looking at the files, I can see a modem file (and also modemst1 and modemst2 - If I use the modem backup, do I need to flash these as well?), but I can't see a bootloader file. Is it under a different name?
Finally, now that I have a backup, where would you recommend getting the v29a files and how would you recommend flashing them?
Thanks for all your help
ThePiGuy said:
I just ran it on a native Ubuntu machine and it worked perfectly - I think the USB timeout must have been my VM.
Click to expand...
Click to collapse
Having said that, I just got an md5 mismatch error on my userdata.bin. Is there any way to backup just that partition rather than the entire thing again?
ThePiGuy said:
I just ran it on a native Ubuntu machine and it worked perfectly - I think the USB timeout must have been my VM.
Just out of interest, looking at the files, I can see a modem file (and also modemst1 and modemst2 - If I use the modem backup, do I need to flash these as well?), but I can't see a bootloader file. Is it under a different name?
Finally, now that I have a backup, where would you recommend getting the v29a files and how would you recommend flashing them?
Thanks for all your help
Click to expand...
Click to collapse
Nope modemst1 and 2 are when you have issues with your imei. Nothing which you need to restore usually. Those are also get backuped by TWRP when you choose EFS.
Regarding the way to go to N? Well when you're unlocked and you have TWRP: flash the zip from @kessaras . If you flash the full ROM ensure that it does not contain the recovery image as it would overwrite TWRP. I would also remove the laf file from there to ensure SALT will continue to work (some ppl have issues on N laf).
ThePiGuy said:
Having said that, I just got an md5 mismatch error on my userdata.bin. Is there any way to backup just that partition rather than the entire thing again?
Click to expand...
Click to collapse
Was it really a mismatch so ERROR or a warning?
Yes but not in the GUI (yet):
Open a terminal
sudo -s
cd /root/programs/lglafng
sudo python3 partitions.py --dump YOURBACKUPFOLDER/userdata.bin userdata
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Nope modemst1 and 2 are when you have issues with your imei. Nothing which you need to restore usually. Those are also get backuped by TWRP when you choose EFS.
Regarding the way to go to N? Well when you're unlocked and you have TWRP: flash the zip from @kessaras . If you flash the full ROM ensure that it does not contain the recovery image as it would overwrite TWRP. I would also remove the laf file from there to ensure SALT will continue to work (some ppl have issues on N laf).
Click to expand...
Click to collapse
Ok thanks - I'll get going
steadfasterX said:
Was it really a mismatch so ERROR or a warning?
Click to expand...
Click to collapse
Unfortunately it was definitely an error. I reran the entire backup and I got the same error - "These files are corrupt (md5 mismatch): userdata.bin" under the errors tab after md5 verification
ThePiGuy said:
Ok thanks - I'll get going
Unfortunately it was definitely an error. I reran the entire backup and I got the same error - "These files are corrupt (md5 mismatch): userdata.bin" under the errors tab after md5 verification
Click to expand...
Click to collapse
Share the log
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Share the log
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
I would but I made the mistake of closing and reopening SALT and it all got deleted. Would you like me to run a third backup to get the log again?
ThePiGuy said:
I would but I made the mistake of closing and reopening SALT and it all got deleted. Would you like me to run a third backup to get the log again?
Click to expand...
Click to collapse
If you don't mind.. Maybe it's an issue I can fix. Up to you.
Sent from my LG-H815 using XDA Labs
steadfasterX said:
If you don't mind.. Maybe it's an issue I can fix. Up to you.
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
I'll get it going