Database Users

[Dev] Desire HD Dual Boot

Why isn't there any Dual Boot Development on the Forum?
It would be great to run 2 ROMs, and it would be very useful for Developers.
Because you can run a Stable ROM and at the same time a beta test ROM without
wiping you Device again and again and make any Nandroid backup..
It's already possible on the HTC Droid Eris
The best option would be to run a ROM from your SD Card, is this an option?
And how difficult, do you guys think, is it to create a Dual Boot option during startup/recovery?
Check also this project, major update coming soon!
unCoRrUpTeD Dual Boot V1 (RELEASE DATE: TBA...)
http://forum.xda-developers.com/showthread.php?t=847423
[RECOVERY-BETA] Eris Multiboot recovery hack
http://forum.xda-developers.com/showthread.php?t=779274
This hack will boot a rom from SDCard. It expects to see system.img and data.img on the sdcard as well as init.rc.
System.img needs to be a disk image of a filesystem that the kernel can read(I've been using ext3) around 170MB(Thats the Eris's NAND size for system)
data.img needs to be a disk image of a filesystem that the kernel can read(I've been using ext3) as big as you'd like your data partition to be(This holds your apps etc, so a couple hundred megs is good)
init.rc needs to be the init.rc of your rom with two changes
You need to remove the lines where it mounts /system and /data.
Once you have those three files on your sdcard, and have flashed this recovery you're ready to try your first boot.
Reboot into recovery, you'll see the normal usual recovery menu(I'll add an item eventually)
connect to the recovery console with adb
run 'adb shell /bootfromsd'
It will APPEAR to have done nothing for a bit, this is normal. Its booting your rom now. Once it gets to the place in the rom where it would display the splash screen, you'll get a splash as usual. You can watch it with logcat if you like.
I've personally booted the following roms from SD.
KaosFroyo
KaosLegendary
CELBFroyo
MR4
PlainJane
Click to expand...
Click to collapse
Kendon at the VillainROM forums
i have managed to have two different android flashes on the hero, tested using VillainROM5.5.0 and SlideVillain1.1.0. it is designed to work with every rom you throw at it. it uses the /system partition for the first rom, the /data partition for the second rom, and two ext partitions for the userdata of each rom. apps2sd support is completely removed during the process, it is obvious that two roms using the same apps2sd partition would create a mess. the process is completely reversible (except for the wiping, so backup!). i have written a bash script that does the necessary steps for you, which are:
- modify the boot.imgs of the roms
- partition your sdcard
- flash the roms
- move the second rom to the /data partition
- move the two roms’ userdata to the sdcard’s ext partitions
Click to expand...
Click to collapse

love to see that

patiently waiting for this feature. keep it posting

I was just looking for something like this. Going to be keeping an eye out on the top Post to see if anything comes. Although i imagine it'll be a while before we see anything final !

alguna informacion adicional sobre este tema, gracias.
Mod edit: any additional information about this topic...thanks!

+1 woulod save time for flashmaniacs like myself

This would be great for testing purposes. I would definitely beta test this if needed.

Aye, I hope someone figures this out
Sent from my Desire HD using XDA App

Quote from iOO
[ROM] REAL SENSE - i00 ROM 5.2 - UPDATED 16/05/2011 - Android:2.3.3
THE FIRST "SYSTEM PARTITION" TRUE SENSE 3.0 ROM!
So what does this all mean?
System partition - this means that i00 ROM does not install any ROM component on your data partition; this has two advantages: it saves precious space on your data partition - so you can maximize the amount of apps you can have installed, and it allows you to factory reset the phone without having to re-install the ROM!
Click to expand...
Click to collapse
Does this mean that you can also Flash a ROM to your Data partition? This means you should only have an option in recovery to choose which ROM you want to start?!?!?!

avisador said:
alguna informacion adicional sobre este tema, gracias.
Click to expand...
Click to collapse
Please use the English language, as stated in the xda posting rules.

Thekn said:
Quote from iOO
[ROM] REAL SENSE - i00 ROM 5.2 - UPDATED 16/05/2011 - Android:2.3.3
Does this mean that you can also Flash a ROM to your Data partition? This means you should only have an option in recovery to choose which ROM you want to start?!?!?!
Click to expand...
Click to collapse
i00 answer
It is possible to dual boot android phones (some at least) with two different versions of android... not sure about doing it on the DHD...
The advantages from flashing this are as stated: to save space on the data/"internal memory" for more applications, and so you can factory reset and have your phone still work without having to re-flash the ROM.
Click to expand...
Click to collapse

Thekn said:
i00 answer
Click to expand...
Click to collapse
By "this" in my quote (in the post above) i mean "my ROM" ... just to avoid confusion...
Kris

i00 said:
By "this" in my quote (in the post above) i mean "my ROM" ... just to avoid confusion...
Click to expand...
Click to collapse
Sorry! Thanks for the explanation! Do you think you can make a Dual Boot for DHD?

Also check this out...
Kris

Also ... it isn't a user friendly process...
From what i gather:
Has only been done on the hero .. and basically involves flashing a ROM then editing another ROM to flash "purely" to the data partition...
create two update packages that each contain a mod'ed boot.img file
... one boot.img points to boot from system partition ... and one points to data partition
... then u have to flash the update file with the corresponding boot.img each time u want 2 change os'es
... only issue would be if you have, for example, sense 2.1 and sense 3.0... the /data/data/? for rosie (etc) (that holds your settings for the apk) conflict between 2.1 and 3.0... and thus would cause issues when switching between the ROMs (FC's in this case hence why you cannot upgrade to 5.0 from previous versions of my ROM).
Kris

i00 said:
Also check this out...
Kris
Click to expand...
Click to collapse
yeah i already found that link, but the link is broken and also the site is blank, couldn't find another source..

Also check this out if you are interested in editing the boot image...
Doesn't seem worth it though to me ... exp if you dont have a way to quickly jump between one OS and the other
Kris

Maybe Ubuntu
Maybe not another android rom but a real linux distro?

humbi83 said:
Maybe not another android rom but a real linux distro?
Click to expand...
Click to collapse
That's also a possibility!

i'm actually more interested in running winmo7 on my phone for a change

★★★★[INFO]ANDROID ROM & How they Work★★★★

★★★★[INFO]ANDROID ROM & How they Work★★★★
Parts of a ROM
i. The kernel.
Android (like many other Smartphone operating systems) runs on the Linux kernel. The Linux kernel was created in the early 1990’s by a gentleman named Linus Torvalds in Helsinki, Finland. It’s incredibly stable, incredibly friendly, and incredibly difficult for the layman to understand and modify. Thankfully it’s also very popular so it has been ported on to a multitude of hardware, including our Android devices.
Think of the kernel as an interface layer between the hardware and software on your device. The kernel decides when things happen, such as the LED indicator gets lit or when the soft button's LED gets lit. An application sends a request to the operating system to blink the LED. The operating system then sends the request to the kernel, which makes the light flash for the amount of time requested by the OS.
What sounds like a round-about way to get things done is also what makes the system so scalable and robust. Application developers only have to code in a way the operating system understands and the kernel makes it work on the hardware. This also keeps the application running in it’s own user-space and separate from the kernel. That means when you run the latest uber-cool app that wasn’t designed for your particular OS version, or is still very beta and it crashes, the kernel gives you the option to Force Close the application and the kernel can run untouched.
In a standard Android ROM (we will leave developer images and the like for another discussion) the kernel is bundled along with a set of instructions that tell the device how to load the kernel and the OS during boot. This is the boot.img that you see inside a zipped ROM that your not able to easily open. The device knows to extract this image to internal memory (the ramdisk) and follow a series of scripts (init scripts) to load the kernel and then the other portions of the OS. That’s what’s happening while you’re watching the boot animation. Interestingly enough this is done the same way for a PC, your smartphone, an Android tablet, or even a smart Linux powered toaster. If you’re feeling exceptionally geeky, plug your Android phone into the USB port on your PC and let the PC boot from the USB device. No, it doesn’t actually load, but you can watch the animation while it tries to match up the hardware support with what’s inside your PC. As I said, Linux is amazingly scalable and as a result so is Android.
What is a kernel? If you spend any time reading Android forums, blogs, how-to posts or online discussion you'll soon hear people talking about the kernel. A kernel isn't something unique to Android -- iOS and MacOS have one, Windows has one, BlackBerry's QNX has one, in fact all high level operating systems have one. The one we're interested in is Linux, as it's the one Android uses. Let's try to break down what it is and what it does.
Android devices use the Linux kernel, but it's not the exact same kernel other Linux-based operating systems use. There's a lot of Android specific code built in, and Google's Android kernel maintainers have their work cut out for them. OEMs have to contribute as well, because they need to develop hardware drivers for the parts they're using for the kernel version they're using. This is why it takes a while for independent Android developers and hackers to port new versions to older devices and get everything working. Drivers written to work with the Gingerbread kernel on a phone won't necessarily work with the Ice Cream Sandwich kernel. And that's important, because one of the kernel's main functions is to control the hardware. It's a whole lot of source code, with more options while building it than you can imagine, but in the end it's just the intermediary between the hardware and the software.
When software needs the hardware to do anything, it sends a request to the kernel. And when we say anything, we mean anything. From the brightness of the screen, to the volume level, to initiating a call through the radio, even what's drawn on the display is ultimately controlled by the kernel. For example -- when you tap the search button on your phone, you tell the software to open the search application. What happens is that you touched a certain point on the digitizer, which tells the software that you've touched the screen at those coordinates. The software knows that when that particular spot is touched, the search dialog is supposed to open. The kernel is what tells the digitizer to look (or listen, events are "listened" for) for touches, helps figure out where you touched, and tells the system you touched it. In turn, when the system receives a touch event at a specific point from the kernel (through the driver) it knows what to draw on your screen. Both the hardware and the software communicate both ways with the kernel, and that's how your phone knows when to do something. Input from one side is sent as output to the other, whether it's you playing Angry Birds, or connecting to your car's Bluetooth.
It sounds complicated, and it is. But it's also pretty standard computer logic -- there's an action of some sort generated for every event. Without the kernel to accept and send information, developers would have to write code for every single event for every single piece of hardware in your device. With the kernel, all they have to do is communicate with it through the Android system API's, and hardware developers only have to make the device hardware communicate with the kernel. The good thing is that you don't need to know exactly how or why the kernel does what it does, just understanding that it's the go-between from software to hardware gives you a pretty good grasp of what's happening under the glass. Sort of gives a whole new outlook towards those fellows who stay up all night to work on kernels for your phone, doesn't it?
Click to expand...
Click to collapse
ii. The operating system.
Once the kernel is loaded, the init scripts tell the Operating System to load. Android is the user interface for a custom built Java virtual machine called Dalvik. Dalvik was written by Dan Bornstein, who named it after the fishing village of Dalvik in Iceland, where his family originated from. The debate of which Java VM is superior is best left for another discussion, so I’ll simply say that DalvikVM is a register-based machine versus true JavaVMs which are stack based.
The Dalvik machine creates executable files (.dex files) which can be interpreted by the OS and run by the end user. These .dex files are OS version dependant. That simply means that applications and core functions built to work with one version of Android may or may not work well with other versions. Google provides the tools through it’s Software Development Kit (SDK) for applications to communicate with the OS.
Click to expand...
Click to collapse
iii. Core functions.
No smartphone would be complete without a set of functions that allow the device to be used as intended. Things like the phone and dialer interface, the calendar, the messaging system are core functions of the Operating System. In Android, these are run on top of the kernel as separate applications. The merits (or lack of) of providing these needed functions as separate applications is once again best left for another discussion, but this is what allows developers like HTC or Motorola to replace the standard functions with alternatives that provide a different look and feel from stock. HTC’s onscreen keyboard or Motorola’s MotoBlur contact list are great examples of this. The “little guy” isn’t left out of the mix either. Handcent SMS or Chomp SMS can integrate into the OS very well, as most of us already know.
An additional set of Core Functions are provided by Google. Popularly called GoogleBits, things like Gmail, sync, Gtalk and the Android Market are applications written by Google that give an extra set of useful functions to the OS. You’ll find these on all smartphones, as well as many other Android devices.
Click to expand...
Click to collapse
iv. Optional applications.
These are applications provided by the manufacturer to give the device even more usability. Things like the Amazon MP3 store, PDF readers, Corporate Calendar etc. allow you to do even more with your device. Remember - Droid Does
Click to expand...
Click to collapse
B. How is a ROM packaged?
In most cases a ROM will come packaged in a .zip file. The recovery image’s kernel (yes, it has one too!) has the ability to unzip and copy the contents into the correct place. Inside this zip file is a folder (META-INF\com\google\android\) that contains a script prepared by the ROM “cooker” (another of those techie terms - it means the person(s) who developed the ROM) that tells the system what to format, what to copy and where, and any file operations that need to be done. Each device does things a bit differently, but this script is where it all gets done. More on this folder later.
You’ll also see a /system folder. This is the meat of the ROM. It has the necessary OS files, the Core functions, and any optional applications the cooker decided to include. The folder is structured the same way it is on your device - /system/app, /system/framework, etc. The whole tree is usually copied over and the existing /system folder is overwritten. The cooker uses the script to tell the kernel to erase the existing system folder, copy the new folder over, and set the file permissions.
Sometimes you will also see a data folder. This usually is space set up for optional applications, including optional system tools like busybox or SuperUser white list. These applications could be placed in the /system folder, but placing them in the data folder makes it easier for the end user (you and I) to remove or update them as needed.
You’ll also notice a META-INF folder. This contains the update script we talked about earlier, as well as secure keys that need to be provided so the device knows the update can be trusted. A special note needs made here. Trusted means that the update is trusted to be in the correct form to load the device. It in no way means the ROM is safe from malicious code. Anyone is able to use a set of test keys and create a ROM that will flash and run your device - even those people with bad intentions. Flashing and running a custom 3rd party ROM is putting faith in the cooker that he or she not only knows what they are doing, but are honest as well. Also, some Motorola custom ROMs will have a small update.zip stored inside this folder to be run on first boot of the device.
Finally we are left with the boot.img file. This is the kernel and ramdisk image we discussed earlier. Your phone copies this over to be decompressed and run when the device boots.
Click to expand...
Click to collapse
2. How do I install a ROM?
In this section we’re discussing how to install a custom 3rd party ROM. ROMs from the manufacturer usually have a utility that runs on your PC to flash and load the new image.
A. Got Root???
Yes ?:good:!!!
Custom ROM’s simply will not load on devices that aren’t rooted. In theory, it may be possible to sign a 3rd party ROM with the keys that the stock recovery image will flash, but for the most part you need to have flashed a custom recovery image before you can change your device’s ROM. Instructions and tutorials on how to root your device are all over the internet. Some are good, some are bad. The hacking forum is a great place to go and learn more about rooting and how to successfully get it done on your device.
Click to expand...
Click to collapse
B. Recovery
Most Android devices have had a custom recovery image written for them. This will overwrite the stock recovery image, allowing you to flash 3rd party ROMs as well as giving extra functionality. Help with finding and flashing the custom recovery image for your device can also be found in the hacking forum. The installation of a custom recovery image also allows for a very important function. Backup and restore.
Click to expand...
Click to collapse
.C. Nandroid
Nandroid is a set of bash scripts and code written by that copies the state of your system and stores it in a folder on your SD card. You can then use the restore function of Nandroid to restore to this point at any time. This is a priceless feature and reason enough to root your phone. It’s included by default in most custom recovery images, and the code is freely available to use if you’re inclined to write your own recovery image.
Click to expand...
Click to collapse
In most situations, using Nandroid to back everything up is easy:
1. Verify you have a memory card with enough free space (~300MB to backup, ~500MB to restore).
2. Reboot your device into recovery. It’s slightly different for each device, once again hacking forum FTW!
3. Navigate through the menu and select the Nandroid Backup function.
4. Apply your choice and wait for the device to tell you it’s finished.
It’s always good practice to copy the entire nandroid folder from your SD card to a safe place. You can then copy it back to the SD card if the card is ever damaged, lost or erased.
D. Copy and Flash
You’re rooted, have downloaded a custom ROM, have your system backed up and are now ready to flash your device. This is not nearly as scary as it sounds.
1. Mount your SD card to your PC, and copy the .zip file to the root folder of the card. Don’t unzip the file, and don’t look for a folder called root. The root folder in this case means the base folder, what you will see when you mount your card to a PC or the device.
2. Reboot your phone into recovery.
3. Navigate through the recovery menu and select the flash update option. Depending on your recovery image, the file may need to be named update.zip, or you may be able to select any zip file on your card as long as it’s the correct format. The cooker knows this as well and if the ROM needs to be named update.zip it will be.
4. Apply your choice and wait for your device to tell you it’s finished.
5. Reboot.
Click to expand...
Click to collapse
It’s worth noting that many times a new ROM will require that you wipe and factory reset your devices data. While inconvenient, it’s often necessary to get rid of the old data as it may be incompatible. As long as you’re using the cloud for calendar and contacts, they will be re- downloaded and stored back on your device automatically.
Dirty flash and Clean flash
A dirty flash is only wiping cache and davlik then flashing your ROM....
a Clean flash is at LEAST factory reset/data wipe + wiping davlik(factory wipe takes care of /cache also)... Maybe doing a format /system also.
***Odin***
Odin is the ROM Flashing Tool for SAMSUNG smartphones. ROM files flashable with Odin come with .tar extension.
Most of the ROMs you are going to flash with Odin are the official stock Samsung ROMs (or leaked stock ROMs). Custom ROMs are rerely flashable by Odin because they come with .zip extension that Odin does not recognize (it recognizes .tar files).
Custom kernels, however, are sometimes provided in .tar format by their developers (e.g. CF-Root kernels), so that they can be flashed by Odin. When your phone is new and running official firmware you most often cannot flash a custom ROM to it because a Samsung phone often requires a custom recovery and root rights that are included in a custom kernel to be able to flash custom ROMs. That's why Odin often comes in handy in rooting and flashing a custom firmware to your phone because you (often) can flash a custom kernel with it that already includes root and custom recovery and enables you to flash custom firmware (custom ROMs). I use the word "often" very frequently in the previous sentence because every Samsung smartphone is different and requires various procedures for rooting it and flashing custom ROMs (see the section about using Odin below).
If it comes to stock ROMs, the best source of stock (official) Samsung ROM files is located at this excellent website: SamMobile.com/firmwares (link). It requires registration (it's free) and I encourage you to set up an account there because you will most likely use this site several times during your stay at XDA. You will most likely come across 1 .tar or 3 .tar file ROMs there, flashable by Odin. Refer to the Odin flashing guide below for more info.
Click to expand...
Click to collapse
****Heimdall****
What is Heimdall?
Heimdall is a cross-platform open-source tool suite used to flash ROMs onto Samsung Galaxy S devices.
How does it work?
Heimdall uses the same protocol as Odin to interact with a device in download mode. USB communication in Heimdall is handled by the popular open-source USB library, libusb-1.0.
Why “Heimdall”?
The flashing software Odin is named after the king of gods in Norse mythology. Loke, the software component on the Galaxy S that provides functionality to flash, may also to be named after an important character in Norse mythology, often translated as Loki. As such I have named my flashing software Heimdall, after the Norse god, and guardian of the Bifrost Bridge.
What platforms does Heimdall run on?
Linux, OS X and Windows (XP, Vista, 7 etc.)
Why use Heimdall when we can use Odin?
Odin is generally unreliable and only runs on Windows systems. Furthermore, Odin is leaked Samsung software that is not freely available or well understood by the community.
Is Heimdall safe?
No matter what method you chose, flashing firmware onto your phone has a lot of potential for disaster. We have tested Heimdall with a variety of phones flashing several different firmware versions resulting in a 100% success rate. As such we believe that Heimdall is generally reliable. However keep in mind, just like any flashing software, Heimdall has the potential to brick your phone if not used correctly.
How do Galaxy S phones get bricked when flashing?
Besides the inherent risks like power outs, accidental removal of the USB cable etc. The Galaxy S appears to be running extremely unreliable USB control software.
A failure to flash does not automatically equate to a bricked phone. However if you're extremely unlucky and the flash fails whilst transferring the primary boot-loader, secondary boot-loader or params.lfs (all quite small) than you've got yourself a paper weight that you're hoping Samsung will replace.
Please be extremely careful mixing files from different firmware releases. Don't do so unless you're certain it will work!
What Galaxy S variants has Heimdall been tested with?
We’ve tested Heimdall with a Galaxy S GT-I9000 (8 GB) from the United Kingdom and Galaxy S GT-I9000 (16 GB) from Australia. We don’t personally have access to any other devices to test with, however users have confirmed Heimdall functions correctly with the AT&T Captivate, Bell Vibrant, Telstra GT-I9000T, Epic 4G and the Galaxy Tab.
Click to expand...
Click to collapse
^

CWM Errors and Solutions
ERRORS encountered in CWM Recovery
.
What is CWM Recovery ?
ClockworkMod Recovery is a custom recovery for many Android devices. It is considered to be the most popular recovery for Android due to its easily-ported nature, and integration with ClockworkMod ROM Manager by Koush(Koushik Dutta). The easiest way to recognize it is by the printed name when it first starts, and the background logo of a gear and hat.
Click to expand...
Click to collapse
ERROR STATUS 6
This is usually caused by CR/LF EOL(Windows style End Of Line) in updater-script. Change it to LF EOL(Unix Style EOL) using Linux command: dos2unix updater-script, then re-signing the ZIP, will usually fix this error.
Click to expand...
Click to collapse
ERROR STATUS 7
This is usually caused by a corrupt download, or bad file signature. Re-downloading (or re-signing) the ZIP will usually fix this.
Click to expand...
Click to collapse
We have been consistently seen and heard people facing error “Status 7″ error while trying to flash or install
custom ROMs or firmware packages on their Android smart phones or tablets with ClockworkMod Recovery. Many
of the users are nowadays facing this problem with CWM Recovery while flashing .zip files of modded or custom
Ice Cream Sandwich (ICS) or Jelly Bean (JB) ROMs on their devices. So, you have also downloaded a custom ROM,
placed its .zip file in your phone’s or tablet’s SD card, booted into ClockworkMod Recovery, selected – “install zip
from sdcard” and then chosen the .zip file of the ROM to get it installed on your device. But instead of getting
flashed successfully, if you are facing the issue mentioned below, then just keep reading this article to find out
what’s wrong and fix up the problem :
Finding update package…
Opening update package…
Installing update…
Error in /sdcard/custom-jelly-bean-rom.zip (Status 7)
Installation aborted
Click to expand...
Click to collapse
or the following error right after CWM recovery shows –
Installing update…
assert failed: getprop(“ro.product.device”) == “I9103″ || getprop(“ro.build.product”) == “I9103″ || getprop
(“ro.product.board”) == “I9103″
Error in /sdcard/android-4-1-1-ics-rom-latest.zip (status 7)
Click to expand...
Click to collapse
So, if you are facing any of these errors while trying to install the desired custom ROM package on your Android
phone or tab, then you may try a various things or steps which may turn out to be the workaround of this
problem. Here are a few tips to get this “Status 7” error fixed in ClockworkMod Recovery and flash the ROM
successfully on your device :
(1) First of all, make sure your device’s bootloader is unlocked. If it is already unlocked but you are still
not able to flash the ROM, then just extract the .zip file of the ROM into a new folder, find the boot.img file from
that directory and flash it up on your phone or tablet via fastboot on your PC.
(2) Make sure that you are having the appropriate Radio or Baseband version installed on your device which is
supported by the custom ROM you are trying to flash. Most of the ROMs requires the latest version of Baseband, so
just update or upgrade your device to the latest Baseband version and then try to install the ROM once again.
(3) Update your device to the supported / latest build of official firmware before trying to install the ROM. You can
do it from – Settings > About Phone / Device > Software Update.
(4) Make sure you are having the supported or required kernel installed on your phone or tab. If it’s not, then flash
a new kernel right away and try to install your custom ROM once again.
(5) Is the ROM which you are trying to flash really works ? Find out whether it is working for other users or not.
Click to expand...
Click to collapse
Error Status 0
Well sometimes while flashing some ROMs especially the cooked ones we get Error status 0 in the CWM Recovery
this error is an indicator of Wrong Update Binary.This is usually caused by an incompatible update-binary in edify ZIPs. Replacing it with a compatible one, then re-signing the ZIP, will usually fix this error.
Click to expand...
Click to collapse

Partitions
Now it's time for the partitions :good:
Let’s start with a list of standard internal memory partitions on Android phones and tablets. These are:
/boot
/system
/recovery
/data
/cache
/misc
In addition, there are the SD card partitions.
/sdcard
/sd-ext
Note that only /sdcard is found in all Android devices and the rest are present only in select devices. Let’s now take a look at the purpose and contents of each of these partitions.
/boot
This is the partition that enables the phone to boot, as the name suggests. It includes the kernel and the ramdisk. Without this partition, the device will simply not be able to boot. Wiping this partition from recovery should only be done if absolutely required and once done, the device must NOT be rebooted before installing a new one, which can be done by installing a ROM that includes a /boot partition.
/system
This partition basically contains the entire operating system, other than the kernel and the ramdisk. This includes the Android user interface as well as all the system applications that come pre-installed on the device. Wiping this partition will remove Android from the device without rendering it unbootable, and you will still be able to put the phone into recovery or bootloader mode to install a new ROM.
/recovery
The recovery partition can be considered as an alternative boot partition that lets you boot the device into a recovery console for performing advanced recovery and maintenance operations on it. To learn more about this partition and its contents, see the ‘About Android Recovery’ section of our guide to ClockworkMod recovery.
/data
Also called userdata, the data partition contains the user’s data – this is where your contacts, messages, settings and apps that you have installed go. Wiping this partition essentially performs a factory reset on your device, restoring it to the way it was when you first booted it, or the way it was after the last official or custom ROM installation. When you perform a wipe data/factory reset from recovery, it is this partition that you are wiping.
/cache
This is the partition where Android stores frequently accessed data and app components. Wiping the cache doesn’t effect your personal data but simply gets rid of the existing data there, which gets automatically rebuilt as you continue using the device.
/misc
This partition contains miscellaneous system settings in form of on/off switches. These settings may include CID (Carrier or Region ID), USB configuration and certain hardware settings etc. This is an important partition and if it is corrupt or missing, several of the device’s features will will not function normally.
/sdcard
This is not a partition on the internal memory of the device but rather the SD card. In terms of usage, this is your storage space to use as you see fit, to store your media, documents, ROMs etc. on it. Wiping it is perfectly safe as long as you backup all the data you require from it, to your computer first. Though several user-installed apps save their data and settings on the SD card and wiping this partition will make you lose all that data.
On devices with both an internal and an external SD card – devices like the Samsung Galaxy S and several tablets – the /sdcard partition is always used to refer to the internal SD card. For the external SD card – if present – an alternative partition is used, which differs from device to device. In case of Samsung Galaxy S series devices, it is /sdcard/sd while in many other devices, it is /sdcard2. Unlike /sdcard, no system or app data whatsoever is stored automatically on this external SD card and everything present on it has been added there by the user. You can safely wipe it after backing up any data from it that you need to save.
/sd-ext
This is not a standard Android partition, but has become popular in the custom ROM scene. It is basically an additional partition on your SD card that acts as the /data partition when used with certain ROMs that have special features called APP2SD+ or data2ext enabled. It is especially useful on devices with little internal memory allotted to the /data partition. Thus, users who want to install more programs than the internal memory allows can make this partition and use it with a custom ROM that supports this feature, to get additional storage for installing their apps. Wiping this partition is essentially the same as wiping the /data partition – you lose your contacts, SMS, market apps and settings.
With this, we conclude our tour of Android partitions. Now whenever you install a ROM or mod that requires you to wipe certain partitions before the installation, you should be in a better position to know what you’re losing and what not and thus, you’ll know what to backup and what not.

You should at least post the source of such a large copy paste post.
Sent from my GT-N7100 using Tapatalk 2

Source? How do you post a source for an article which is compiled from 10+ sites? Plus my own addition?
Started from the bottom

Good job man, this saves me the time to do all this researches.
Keep it up
Best regards
Sifou
Using a Samsung N7100

sos_sifou said:
Good job man, this saves me the time to do all this researches.
Keep it up
Best regards
Sifou
Using a Samsung N7100
Click to expand...
Click to collapse
DO tell me if you have some suggestions for the thread.
"Thanks button is just to avoid "THANKS" posts in threads. Nothing more than that. Don't ask in signature or post for it and defeat the purpose why it was introduced"

I think that this is a pretty good summary of the basics. I even converted it to epub and stocked it on my e-reader for reference
You can get to the details if you want? Adding some info about flashing softwares like odin and the Linux based one (i don't remember it name)
The different recoveries available and their advantages vs désavantages
How to protect yourself from malicious applications, starting from knowing what are permissions...
Keep it up mate
Best regards
Sifou
Using a Samsung N7100

sos_sifou said:
I think that this is a pretty good summary of the basics. I even converted it to epub and stocked it on my e-reader for reference
You can get to the details if you want? Adding some info about flashing softwares like odin and the Linux based one (i don't remember it name)
The different recoveries available and their advantages vs désavantages
How to protect yourself from malicious applications, starting from knowing what are permissions...
Keep it up mate
Best regards
Sifou
Using a Samsung N7100
Click to expand...
Click to collapse
Heimdall?
"Thanks button is just to avoid "THANKS" posts in threads. Nothing more than that. Don't ask in signature or post for it and defeat the purpose why it was introduced"

Tha TechnoCrat said:
Source? How do you post a source for an article which is compiled from 10+ sites? Plus my own addition?
Started from the bottom
Click to expand...
Click to collapse
I guess you have a point, it's just the scientist in me with source-referral-ocd.
Sent from my GT-N7100 using Tapatalk 2

adytum said:
I guess you have a point, it's just the scientist in me with source-referral-ocd.
Sent from my GT-N7100 using Tapatalk 2
Click to expand...
Click to collapse
DO tell me if you have any problems or if you want something to be added.
"Thanks button is just to avoid "THANKS" posts in threads. Nothing more than that. Don't ask in signature or post for it and defeat the purpose why it was introduced"

Thread updated with Odin and Heimdall information.
"Thanks button is just to avoid "THANKS" posts in threads. Nothing more than that. Don't ask in signature or post for it and defeat the purpose why it was introduced"

Tha TechnoCrat said:
Source? How do you post a source for an article which is compiled from 10+ sites? Plus my own addition?
Started from the bottom
Click to expand...
Click to collapse
By listing ALL the different sources? And obviously crediting yourself with bits you've added.
Sent from my GT-N7100 using xda premium

You should make the title of the thread more presentable though.

Simone said:
You should make the title of the thread more presentable though.
Click to expand...
Click to collapse
Would like some suggestions.
"Thanks button is just to avoid "THANKS" posts in threads. Nothing more than that. Don't ask in signature or post for it and defeat the purpose why it was introduced"

Tha TechnoCrat said:
Would like some suggestions.
"Thanks button is just to avoid "THANKS" posts in threads. Nothing more than that. Don't ask in signature or post for it and defeat the purpose why it was introduced"
Click to expand...
Click to collapse
You should think of your own. That would be the best
Make it more professional looking, though.
Everything else is good.

Guys I have got my Note 2 finally. Will compile some guides for it too.
Sent from my GT-N7100 using xda app-developers app

You bought a note 2? Congrats mate !
Best regards
Sifou
Using a Samsung N7100

sos_sifou said:
You bought a note 2? Congrats mate !
Best regards
Sifou
Using a Samsung N7100
Click to expand...
Click to collapse
Thanks buddy. Get ready for more guides
Sent from my GT-N7100 using xda app-developers app

[RECOVERY] ClockworkMod 6.0.3.7 for Xiaomi Mi3 tegra4 (pisces)

This is a modified ClockworkMod recovery for the Xiaomi Mi3 tegra4 (pisces). It includes some changes from M1cha's CWM for Mi2 to support the dual-system design of the Mi2 (same thing on Mi3), while leaving out "true dualboot" feature for now. I think TDB is useless as long as there is only MIUI available for this device. See source for details.
Working so far:
adbd in recovery
nandroid backup/restore, including system1, boot1
running any update.zip (including AROMA)
choose system to install update to
set active system
Anything else untested.
Installing:
(1) Flash using fastboot:
adb reboot-bootloader
{wait for fastboot screen}
fastboot flash recovery cwm-*-pisces-*.img
(2) Boot new recovery:
Type fastboot reboot and press enter while holding Vol+ key should take you directly to CWM.
(3) Let CWM disable recovery flashing (offered automatically when selecting reboot)
I didn't test this method so far (feedback welcome) -- in case it doesn't work, try this instead:
Alternative installation method:
(1) Disable automatic recovery reflashing (while running MIUI, requires busybox installed and a root shell, eg "adb root; adb shell")
Code:
mount -o remount,rw /system
chmod 444 /system/etc/install-recovery.sh
mount -o remount,ro /system
(2) Flash using fastboot
Code:
adb reboot-recovery
{wait for fastboot}
fastboot flash recovery cwm-*-pisces-*.img
Use at your own risk, right now this is largely untested
Download: cwm-6.0.3.7-pisces-a20131110a.img
Older Releases: cwm-pisces
Source:
Device tree (stub)
Recovery
Note: As there's no kernel source available yet, the kernel is left out of device tree. For building yourself, extract stock kernel from your boot image and place it in the device tree (filename "kernel")
History:
a20131110a:
Integrated all fixes by M1cha that are not related to TDB -- backup/restore of boot1 now working
Set default storage to /sdcard/0, nandroid backups now accessible via MTP
a20131110:
Integrated boot-system selection and recovery-check for both systems
Used biggest font for readability on fullHD display
a20131109a: Integrated the first dualsystem support modification by M1cha
a20131109: Unmodified CyanogenMod source, no dualsystem support at all

This is my future phone.. So thanks

Thanks, but keep in mind this phone comes with 2 different SoCs, Tegra4 and Snapdragon800 -- this here is for Tegra4, which is found in TD-SCMA version... maybe I should update OP to explicitly state that.
Btw, it's not complete yet, it doesn't flash original ROM updates correctly, I think thats because named partition nodes are missing ... I'll add support for these soon
Gesendet von meinem MI 3 mit Tapatalk

No third-party ROM MI3 brothers now seems less useful but thank you
I did a card brush pack Share
Attachment Download：
recovery-clockwork-cwm-6.0.3.7-pisces-a20131110a.zip
http://115.com/lb/5lbdstd81pd#
recovery-clockwork-cwm-6....3.7-pisces-a20131110a.zip
115 network disk packs code：5lbdstd81pd

yao85930101 said:
No third-party ROM MI3 brothers now seems less useful but thank you
Click to expand...
Click to collapse
Well, I need some time to improve it, because there's two possible uses with stock ROM:
- nandroid
- re-flashing mods after upgrade
I'm especially interested in the second, because I want some apps to reside in /system/app permanently. Unfortunately, it doesn't work yet, as it doesn't flash official upgrades (right now need updater app for this) -- as I said, probably the named device nodes for partitions, need time to work on this.
For 3rd-party ROM ... There COULD be. I assume stock kernel is somehow based on this:
http://nv-tegra.nvidia.com/gitweb/?p=linux-2.6.git;a=tree;hb=refs/heads/linux-tegra-nv-3.4
(seems to contain platform drivers for tegra pluto board, has android drivers and it's even exactly the same linux version)
So, it COULD be possible to build a working kernel from these sources. Well, I didn't even get anything to boot far enough for giving useful error info to me But if you want to "waste" hours and days, please try yourself A custom kernel would be an excellent start.
yao85930101 said:
I did a card brush pack Share
Attachment Download：
recovery-clockwork-cwm-6.0.3.7-pisces-a20131110a.zip
http://pan.baidu.com/s/1Dwmj9
Click to expand...
Click to collapse
Nice! :good: Is this installable from stock recovery, too?
A little remark: I'd prefer not to modify /system automatically from the installer but better boot directly into CWM and then let the user decide. Of course thist would require rebooting to recovery from updater-script. I didn't do edify script for quite some time -- is this possible? If not, maybe we could throw together a little arm7 binary for the boot to CWM for some kind of "final" release. I'd consider thios CWM version "final" as soon as it can flash official updates (from xiaomi)

Oh look forward to updating you again Come on you are the best

However, a day to focus on the brothers really no way to track it?

Hello, I don't have time for this right now. I'll get back to the project probably after christmas.
But, as I said, it's probably the missing partition names -- so this SHOULD be fixable in the device tree, adding init scripts to the recovery (no need to modify CWM itself further). Feel free to clone the repo (AND you need an original kernel image extracted from the phone)

Any reason this wouldn't work on Tegra Note 7?

e8hffff said:
Any reason this wouldn't work on Tegra Note 7?
Click to expand...
Click to collapse
At least two.
1. The kernel. It's taken from an original Mi3 tegra phone, unfortunately, there are no sources yet from Xiaomi. Although it's the same platform, the chances this kernel would boot on any other device are low.
2. "Dual-system". I don't know much about the Tegra Note 7, but I doubt it has 2 system and boot partitions. Most android devices don't -- the Xiaomi phones are the only ones I'm aware of. CWM code in this zip is modified/extended to handle this (mostly taken from modifications done by M1cha for the Mi2). It won't work on a normal single-system device. In fact, there's no need to modify CWM source for a standard single-system device, a device-tree would be enough for building a working CWM recovery.

Zirias said:
At least two.
Click to expand...
Click to collapse
Ok thanks for the reply.

any progress on this work? is this CWM fully working now?

Don't Copy Others Work
If u Copy some ones Post Then Plzzz........... Mention
http://forum.xda-developers.com/showthread.php?t=2521125

new cwm but in chinese dor tegra 4
i have find these two but i think it is in chinese
http://4pda.ru/forum/index.php?showtopic=541742&st=5360#entry32916655
http://www.miui.com/thread-2069908-1-1.html
if any one could help and translate them to english we can have true dual boot and try the new custom roms for tegra 4 xiaomi
Android - 5.0 Lollipop for tegra 4 xiaomi but this must be in chinese too
http://www.miui.com/thread-2111749-1-1.html

TWRP 3.2.3-0 and older versions for Redmi Note 2

TWRP3.2.30-Universal version uploaded
https://drive.google.com/open?id=16BueY8230PzL-5ngkMiNZGxpIYBoK4EL
TWRP3.2.20-Universal version uploaded
https://drive.google.com/open?id=1Qr35EfIy76c6lkQZaKBzRS_PuBhUfjMX
TWRP3.2.10-Universal version uploaded
Rebased on TWRP3.2.1-0
https://drive.google.com/open?id=1Tcc5pk-7MOz5IRwqgH-zfKj-t7pnSMi5
TWRP3.2.0-0-Universal version uploaded
Changelog:
Backup / Restore every possible partition
Supports both Android 5.x and 6.0+ partitioning schemes
Oreo ready..........
https://drive.google.com/open?id=1uJAc84Qgw4k1NW3W3BjcVtwc37y--xz8
TWRP3.1.1-0-Universal version uploaded
Changelog:
Uses 7.5.11 Android 5.02 kernel
Backup / Restore every possible partition
Supports both Android 5.x and 6.0+ partitioning schemes
https://drive.google.com/open?id=0BwdRTuyj12_yVWZqUnd6MEN0QVk
Note: This version saves to a folder named as the serial number of the device which is different to the previous version. Old backups will not work unless they are copied into the new folder.
TWRP3.0.2-2 has had a makeover also:
Rebased on 7.3.16 Kernel
Removed F2FS support to prevent "mishaps"
Added ability to backup & restore Preloader partition
https://drive.google.com/open?id=0BwdRTuyj12_yU19qQWNra1o3alk

Hi, great work. Can you make twrp 3.0 for our beloved xrmn2? It's has been released: http://www.xda-developers.com/twrp-3-0-0-has-arrived/

If you don't like the extensive partition listings in the original, I have altered the fstab files and repacked so you see only the necessary partitions for each function. Other than that, it is the same.
Now only one version with all the partitions you need and none that will get you into trouble

Thank you for sharing!

jajk said:
TWRP3.0 is here. All credit to Jeminni.
Unpacked, examined and tested to be fully functional and free from malware by me. This is totally unaltered - just mirrored here for convenience.
Click to expand...
Click to collapse
Hi, great work...thanks alot, just keep peaking !
Can we get informed by you what kind of malware plant in this, does it method by flashing any zip using it or by restore/backup process?
Anyway, u're whispering somethin' th
at we cant wait ur MM builds desperately...

@Adam Hui Maybe you misunderstood, I checked that there is no malware in the original by unpacking it and looking at the code. I also tested every function does not break the phone and works correctly. I am assuring other users that maybe cannot examine the contents that it is clean.
My modified version only rationalizes how partitions are presented in Recovery. Try the original and you will understand the need to alter the partitions displayed.
MIUI based on MM is in beta testing for ReNo2 already (I am not one of the beta testers)
Be careful what you wish for as MM brings everyone one step closer to a closed platform like Apple. I would be happy on 5.1.1

jajk said:
[MENTION=4666525]
Be careful what you wish for as MM brings everyone one step closer to a closed platform like Apple. I would be happy on 5.1.1
Click to expand...
Click to collapse
Hey man, pls washout that greyed info.
Do u mean there'll be a locked bootloader in miui MM ?
U should inform us if u knew it at first time !

Hi, Is there a MultiROM / dualboot feature included in this release?
Thank you to jemimi for the dev work and thank you in advance for any reply.

@MiSteven No dualboot in this one and I haven't seen one for our phone (not that I have been looking)

New version 3.0.0-3

jajk said:
New version 3.0.0-3
Click to expand...
Click to collapse
Is this update of jemmini's TWRP_3_ReNo2.zip from 4pda.ru?

@sanceliken2000 No it is original.

jajk said:
@sanceliken2000 No it is original.
Click to expand...
Click to collapse
Thanks for the answer. Could you please tell me if i could flash it directly with twrp 3 jemminis' in order not to do the procedure with fastboot?

@sanceliken2000 Just flash it in your existing TWRP (it is a flashable zip)

Interface look good, old backups need to be re-backup! Thx~

addro said:
Interface look good, old backups need to be re-backup! Thx~
Click to expand...
Click to collapse
If you have backup made by jemmini's TWRP3 it is not necessary to re-back. The new one understands that backup.

@faorekh It surely is. I look for compatible donors since we have no official build for our device.
The only thing that changes from previous TWRP backups is the folder name where it is stored. If needed, rename the old folder to /TWRP/BACKUPS/Redmi_Note_2 and TWRP will see it or just move the old backups into the new folder when it is created on first new backup.

There is the signature "Lenovo/full_aio_otfp/aio_otfp" inside recovery. Is this recovery port from recovery-twrp-3.0.0-3-k3.img of Lenovo K3 Note?

This version works great for my rmn2 prime.
Sent from my 2014817 using Tapatalk

I flashed this recovery yesterday through my twrp 2.8.7.
After updating to TWRP 3.0.0-3 I got messages like this:
Code:
This package is for "hermes" devices; this is a "".
[COLOR="Red"]Updater process ended with ERROR: 7
Error installing zip file '/external_sd/!Flash/twrp287.zip'[/COLOR]
After that I used the fix in this thread to make my old recovery flashable again. Now everything works fine again, but you may want to look into that, so others won't have to get similar headaches as me.
Little note: I spent 3 hours trying to make this work under OSX El Capitan, but it seems like OSX can't create flashable zips. I used a windows partition to zip the files and everything worked fine.

Update H815 to v29a (with backup of v20g)

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