Related
Ive seen many questions in the Q & A forum about this CWM and figured the best way is to get developers and other main contributors to look at the issues some of the "little people" have about using it. DAF was convenient and easy for all because it was one click for the people who could get that far, and since CWM, there where the 3 versions and this one has yet to really be well touched upon as a full tutorial with the copy to SD not being needed any more. I feel as do many others that a main "sticky" thread be made for it with a few FAQ on this section of the forum so they do not have to search too far away from the main thread they are using and get completely confused.
1. Will doing a backup and changing ROMs using CWM with different partition delete my backup?
2. Will doing a backup KEEP my partition?
3. Is it possible to do a partition from CWM or is the partition need to be carried on a computer?
(this to me seemed to defeat the purpose of CWM with some DEVs making their own partition layouts and not using the main ones that were originally laid out for use, no aim towards DEVs because I know they work hard)
4. If I put multiple ROMs on my SD card do I need to change the partition every time if I want to change them?
5. Is there a way to know which backups are from which ROMs I had used?
(I guess this is asking if they can change the name?)
6. How do I know when to "Wipe Cache Partition"?
I know there is *THIS* thread, however there are surely some differences between the copy of those files and not needing to copy amongst other things to which the "new" people do not understand.
If this is just a bother and hindrance to you all, I understand the deletion of this thread, however it did take quite a while to plan out what to write, and what not to should you choose to do so and I would give the answers, however even I do not know all of them and so I leave this to you all for debate. NO PUBLIC BASHING PLEASE
Dude, this forum is for posting dev projects. Why on earth do you think its ok to post a questions topic in here when we have a dedicated questions forum?!?!
TheATHEiST said:
Dude, this forum is for posting dev projects. Why on earth do you think its ok to post a questions topic in here when we have a dedicated questions forum?!?!
Click to expand...
Click to collapse
I said it could be moved or deleted just the questions are not very well maintained in that DEDICATED (? HA) forum there are multiple posts of the same and I felt that since there is a sticky thread here that could answer the forum issue of the DEVELOPED CWM program this should be brought to the attention and as such is a DEV related issue. It can and most likely will be moved, do you have an answer to any of the issues the people asked?
TheATHEiST said:
Dude, this forum is for posting dev projects. Why on earth do you think its ok to post a questions topic in here when we have a dedicated questions forum?!?!
Click to expand...
Click to collapse
now that it's been moved, nobody will discuss the answers and it's a pointless post.
harrystone33 said:
1. Will doing a backup and changing ROMs using CWM with different partition delete my backup?
Click to expand...
Click to collapse
No this will not delete your back up as it is saved on yor SD card when you do the back up.
harrystone33 said:
2. Will doing a backup KEEP my partition?
Click to expand...
Click to collapse
This I am not really sure of as I am not a dev but I think it does as the backup is just a backup of your settings, personal information, your gmail account associated with your Android, boot data, and any cache data that you have built up.
harrystone33 said:
3. Is it possible to do a partition from CWM or is the partition need to be carried on a computer?
(this to me seemed to defeat the purpose of CWM with some DEVs making their own partition layouts and not using the main ones that were originally laid out for use, no aim towards DEVs because I know they work hard)
Click to expand...
Click to collapse
You can partition your SD card with CWM but I do not think you can do a system portion as CWM is what creats the system portion when you flash it. It creates a partition in the CWM.
harrystone33 said:
4. If I put multiple ROMs on my SD card do I need to change the partition every time if I want to change them?
Click to expand...
Click to collapse
Once again I am not a dev (yet) and I am not 100% sure of this. But I would say if the ROMs you have stored on SD card need different portition sizes then yes you will need to change the partition size when you change ROMs. If they require the same partition size then no you do not need to change the partition size.
harrystone33 said:
5. Is there a way to know which backups are from which ROMs I had used?
(I guess this is asking if they can change the name?)
Click to expand...
Click to collapse
You should be able to manually go into your SD card with a computer and change the name on the backup file, but I do not know if this will interfer with CWM being able to detect the backup file. So you might want to write down the original full name of the file befor you change it.
harrystone33 said:
6. How do I know when to "Wipe Cache Partition"?
Click to expand...
Click to collapse
As a rule of thumb I would not delete my cache unless I was about to flash a new ROM.
Also check out my guide I wrote in linked in my sig, you might find it useful.
Hope this helps you out some.
This is the general discussion/Q&A/"wtf is this?"/"what good does this do me?" thread. Below is a general description of The Nullifier and the Q&A for it. This being the general thread for the AIO wipe tool, general questions about it are welcome.
Link to thread: Vision AIO Wipe Tool
The Nullifier.
This uses a special command in combination with a special file to overwrite the internal partitions with 0's, hence "Null" for 0 and "-ifier" for the fact that it does the action of the root word to something else. It also formats all the partitions afterward and checks for, and repairs any errors on them, as it can.
Q&A Section
Nullifier Q and A:
Q: Why not just format everything?
A: Because a format isn't intended to erase data, though, to a degree, does so. This script is intended to and will wipe out the data and leave a clean set of partitions for a ROM to be installed to.
Q: (Submitted by Cargohook) Would it be idiotic or fruitless to run this and then restore a nandroid backup? I mean, would that defeat the purpose?
A: I highly doubt it would be a waste of your time. On an educated hunch, when you restore a nandroid all CWM does is format the partitions then load the data from the nandroid to those partitions; back to square 1 with old data being left behind. The only thing to say is that if there is something such as bugged settings, or file corruption, those things will be present in the nandroid itself.
Q: Why don't I get a message about formatting /boot?
A: Because it doesn't format /boot. Why? In testing I found that it doesn't need it. It's all a matter of how Android uses boot.img and how it's copied.
Q: Does this wipe internal or external SD? (added because it keeps getting asked)
A: In a word, no.
Q: Will using this cause nand-failure or make my phone unusable if used too much?
A: I first developed this in March, I have used it many many times and I have no problems. Some people want to get up on a soap box and declare that it will. Overground was kind enough to step in and offer an unbiased opinon here: http://forum.xda-developers.com/showpost.php?p=25257903&postcount=327
(More to come as need be)
Reserved
Reserved, just in case.
quick question, might be stupid to ask but would i have to use the nullifier AND system format option, or just use the nullifier?
Your question is answered above in the section entitled "The Nullifier".
Sent from my LG-P999 using xda premium
oh haha, sorry.
Drink more vodka.
Sent from my LG-P999 using xda premium
Hi guys.
Yesterday I got a used HTC HD2. It is installed with android nand and the DFT (Dark Forces Team) rom, I think taken from the DESIRE (according to the information on the 'About').
The main problem in the device is that it has really bit memory! After installing few apps, I cant download a thing :/
So I searched for the problem and I've realized that I need to make a partition on the SD-CARD. However I saw that in the market there are apps that allow moving the application that can only sit in the internal memory to the external memory.
I then found out that the phone doesn't have root access too. (Although it came with SUPERUSER app as default).
I can't find the main thread of the rom in order to ask there how to root the device.
Which software / app, will I need recovery installed (althogh I don't think it requires) and ETC.
Please can someone direct me or just give me names of apps/softwares/guides/anything :crying:
I guess GOOGLE could be my assitstant from there.
I'm afraid to follow guides that I don't sure will work properly with my phone's software.
Thank you.
pelegm28 said:
Hi guys.
Yesterday I got a used HTC HD2. It is installed with android nand and the DFT (Dark Forces Team) rom, I think taken from the DESIRE (according to the information on the 'About').
The main problem in the device is that it has really bit memory! After installing few apps, I cant download a thing :/
So I searched for the problem and I've realized that I need to make a partition on the SD-CARD. However I saw that in the market there are apps that allow moving the application that can only sit in the internal memory to the external memory.
I then found out that the phone doesn't have root access too. (Although it came with SUPERUSER app as default).
I can't find the main thread of the rom in order to ask there how to root the device.
Which software / app, will I need recovery installed (althogh I don't think it requires) and ETC.
Please can someone direct me or just give me names of apps/softwares/guides/anything :crying:
I guess GOOGLE could be my assitstant from there.
I'm afraid to follow guides that I don't sure will work properly with my phone's software.
Thank you.
Click to expand...
Click to collapse
look for guides in this forum...about nativSD and dataonEXT...very helpful (that's how i learned what i need to know about the device)...also i recommend to change the rom to a better or newer version of android...you will also find guides about changing the rom...
eliaskammas said:
look for guides in this forum...about nativSD and dataonEXT...very helpful (that's how i learned what i need to know about the device)...also i recommend to change the rom to a better or newer version of android...you will also find guides about changing the rom...
Click to expand...
Click to collapse
Hi,
Thank you for your kindly help.
Which Android version do you suggest to change to ?
ICS ? Or maybe GingerBread ?
And BTW I entered before to the MAGDLR menu, chosed the " AD Recovery " option and it said something like " no boot source ".
Does that mean that I don't have a recovery installed ?
And if so, will I need to install it first and then change the rom ?
Again, Thank you for your help.
Peleg.
yes you will need recovery...fast roms are mostly GB but ICS are as good as well...GB need less space on rom memory so if you don't install alot of craps as most of us do the remaining space will be fine for your data...ICS have hwa, apps work faster and games play better..I recommend ICS by tytung to be honest(very fast and stable)...when you download the recovery you will see a "flash.cfg" file...on the rom thread the developer will state the partitions needed for his rom and so you change the numbers on that file accordingly before flashing the recovery...but always make system space little bigger than needed just in case(and to avoid other problems that i will have a finger cramp if i write them down.! )
eliaskammas said:
yes you will need recovery...fast roms are mostly GB but ICS are as good as well...GB need less space on rom memory so if you don't install alot of craps as most of us do the remaining space will be fine for your data...ICS have hwa, apps work faster and games play better..I recommend ICS by tytung to be honest(very fast and stable)...when you download the recovery you will see a "flash.cfg" file...on the rom thread the developer will state the partitions needed for his rom and so you change the numbers on that file accordingly before flashing the recovery...but always make system space little bigger than needed just in case(and to avoid other problems that i will have a finger cramp if i write them down.! )
Click to expand...
Click to collapse
Thank you.
I will first install the recovery, but I guess I'll have to read a lot before:
http://forum.xda-developers.com/showthread.php?t=1021837
Then I will search for a guide for installing recovery-
CWM will be great right ?
Thank you very much !!! :laugh:
The guide you linked is very useful and makes everything clear. I strongly recommend reading it thoroughly before doing anything. Once you're slightly more comfortable with the terms, you can follow the guide in my sig to flash CWM and a ROM. You already have HSPL, a compatible Radio version and MAGLDR installed so don't worry about any of those. If you happen to come across guides which say 'task29' just ignore that step, Task29ing is completely useless.
As for recommending a ROM, it depends on your usage. Eliaskammas' post sums it up nicely, but you should note that (IMO) ICS and JB will give you worse day to day performance and stability than GB but will be better for intensive activities e.g. gaming, web browsing, using content-heavy apps etc. I've also found battery drain to be marginally more on ICS and JB ROMs.
Nigeldg said:
The guide you linked is very useful and makes everything clear. I strongly recommend reading it thoroughly before doing anything. Once you're slightly more comfortable with the terms, you can follow the guide in my sig to flash CWM and a ROM. You already have HSPL, a compatible Radio version and MAGLDR installed so don't worry about any of those. If you happen to come across guides which say 'task29' just ignore that step, Task29ing is completely useless.
As for recommending a ROM, it depends on your usage. Eliaskammas' post sums it up nicely, but you should note that (IMO) ICS and JB will give you worse day to day performance and stability than GB but will be better for intensive activities e.g. gaming, web browsing, using content-heavy apps etc. I've also found battery drain to be marginally more on ICS and JB ROMs.
Click to expand...
Click to collapse
Hi.
Thank you for your advices and technical help.
I will read it as soon as possible and then try to install the CWM Recovery and a better Rom.
According to what I saw, I think I will go on the "Energy rom" (Sense 3.5).
I will probably update my progresses here.
Thank you a lot.
BTW, a deodexed rom is needed for languages that are written from right to left ?
Or that I have to find a rom supports RTL ?
Beacuse for example, I've searched the thread of the Energy rom for "Hebrew" and found out that it doesn't supports RTL :/
Thank you.
I don't want to confuse you but I personally have always found Sense based ROMs to be slow and I think you should really stick to CM or MIUI. Anyway, that's really just my opinion.
Unfortunately, I think that you may have to find a ROM which supports RTL. I haven't looked into it but there may well be an app which somehow makes it work. If you're desperate for Android with Sense and RTL support then you could consider some of the SD ROMs from boxmax, he made good SD ROMs (at least when I used it), but I don't know which NAND ROMs will work for you.
Nigeldg said:
I don't want to confuse you but I personally have always found Sense based ROMs to be slow and I think you should really stick to CM or MIUI. Anyway, that's really just my opinion.
Unfortunately, I think that you may have to find a ROM which supports RTL. I haven't looked into it but there may well be an app which somehow makes it work. If you're desperate for Android with Sense and RTL support then you could consider some of the SD ROMs from boxmax, he made good SD ROMs (at least when I used it), but I don't know which NAND ROMs will work for you.
Click to expand...
Click to collapse
Hi Nigeldg.
I took your advice and I think I will go on this rom:
http://forum.xda-developers.com/showthread.php?t=1639932
It supports rtl and data2ext.
But do I need to change my HD2's kernel ? To Dorimanx 's kernel ?
And from the guide that you've recommended on before, do I need to start from this part:
http://forum.xda-developers.com/showpost.php?p=12656427&postcount=3
And to skip the other parts ?
I've read the hole guide and it is very helpful.
Everything is really clearer.
There's no need to change the kernel after flashing, but you can if you want to. I think the dorimanx krrnel is included in that rom anyway so i don't see why you'd want to flash it again. Follow the new way method and everything should be fine. You can use the NAND toolkit to select the appropriate partition size.
Nigeldg said:
There's no need to change the kernel after flashing, but you can if you want to. I think the dorimanx krrnel is included in that rom anyway so i don't see why you'd want to flash it again. Follow the new way method and everything should be fine. You can use the NAND toolkit to select the appropriate partition size.
Click to expand...
Click to collapse
Hi Nigeldg.
I now want to install the CWM (long time hh)..
In this rom:
http://forum.xda-developers.com/showthread.php?t=1639932
It says to install CWM with this partition size:
" Flash the Latest CWR (Clockwork Recovery) with the appropriate partition sizes by using the "Repartition" button inside the HD2ToolKit: System: 200MB | Cache: 5MB "
In the thread of CWM: http://forum.xda-developers.com/showthread.php?t=898913
Can I change the partition sizes used for CWM
A. You can by editing the flash.cfg but this is not recommended, CWM is designed to make it easier for switching roms, by flashing a custom partition size you may stop other roms working and require reflashing a new partition size when you want to change roms.
Q. I dont know which partition size to download
A. Depending on what type of roms you plan on using, you should choose the partition size based on the following.
150MB Partition - For bare roms including CyanogenMod, AOSP, and MiUI
250MB Partition - For Standard sense roms including Desire and EVo based ROMs, can also be used for some squashed HD builds
400MB Partition - For Larger roms including unsquashed Desire HD and Z roms, ROMs REQUIRE data2sd for EU HD2 with 512MB NAND
And in the thread in your sig it is possible to download 3 version of the CWM. (150, 250, 400).
How do I need to install the CWM ?
To download the 250MB version, and using the HD2ToolKit to change the partition size and install with System: 200MB | Cache: 5MB (as the rom developer suggested) ?
Thank you!
The thread you've linked to is the old CWM thread. I don't see why it says that you shouldn't change the partition sizes because that's simply not true, pretty much all ROMs use custom sizes. Ignore that advice, it's wrong. In my opinion the easiest thing to do is to download the HD2 NAND Toolkit, click 'MAGLDR repartition', choose 200 and you're done.
Nigeldg said:
The thread you've linked to is the old CWM thread. I don't see why it says that you shouldn't change the partition sizes because that's simply not true, pretty much all ROMs use custom sizes. Ignore that advice, it's wrong. In my opinion the easiest thing to do is to download the HD2 NAND Toolkit, click 'MAGLDR repartition', choose 200 and you're done.
Click to expand...
Click to collapse
Ok.
So I've downloaded the HD2 ToolKit.
Actually what I need to do is this:
1. To choose the 200MB and 5 Cache and then press repartition. (In what way does the phone need to be ? MAGDLR Menu, or other option ? )
2. Then to install the CWM by going to MAGDLR - USB Flasher, connect to the computer, and run the
DAF.exe.
Right ?
1. Open the toolkit
2. Click the MAGLDR repartition tab and select 200 and change the cache size to 5
3. Click 'repartition' (bottom left of the toolkit)
4. Follow the instructions it gives you (boot your phone into USB flasher mode then connect it to your PC) and let it flash.
Nigeldg said:
1. Open the toolkit
2. Click the MAGLDR repartition tab and select 200 and change the cache size to 5
3. Click 'repartition' (bottom left of the toolkit)
4. Follow the instructions it gives you (boot your phone into USB flasher mode then connect it to your PC) and let it flash.
Click to expand...
Click to collapse
And once I've finished this, I need to install the CWM.
To donwload the 250MB version ?
pelegm28 said:
And once I've finished this, I need to install the CWM.
To donwload the 250MB version ?
Click to expand...
Click to collapse
I don't think you understand, THIS IS INSTALLING CWM :') After you've done this, just flash the .zip ROM and you'll be done
Nigeldg said:
I don't think you understand, THIS IS INSTALLING CWM :') After you've done this, just flash the .zip ROM and you'll be done
Click to expand...
Click to collapse
If I've already did it, just do this thing again and it will work ?
because now my phone cant load to the rom, it says NAND Kernel something and boots up to MAGDLR.
Is it OK ?
EDIT:
I've did it and chosed the "AD Recovery" option.
Now I can see that I have CWM Recovery!!
I thought that I had to choose somehow to install the CWM, and that's why I didn't understand.
Now,
Do you recommend to do wipe data/factory reset and wipe cache ?
And after that to install from CWM the ROM that I've transferd to the Root of the SD right ?
Thank you very much !!!
You don't need to wipe anything, that already happened when you flashed CWM. Yes you should just have to flash the ROM now, as said in the guide in my sig. You may want to create an EXT partition but for your particular ROM it's not a necessary step so you can skip that. Glad I could help
Nigeldg said:
You don't need to wipe anything, that already happened when you flashed CWM. Yes you should just have to flash the ROM now, as said in the guide in my sig. You may want to create an EXT partition but for your particular ROM it's not a necessary step so you can skip that. Glad I could help
Click to expand...
Click to collapse
It isn't necessary because it automaticly transfer the data to the SD ?
During the installation a message showed up saying that the rom identified that I don't have an EXT-partition installed.
Can I make a partition using the CWM/ADVANCED/PARTITION-SD ?
Thank you so much for your help!!
You saved me, and becuase of you I didn't sell the phone.
Thank you!!
It isn't necessary because the ROM itself is quite light, so all of it can be fit on to the NAND memory. It would help to create one because you may need it in the future, so I personally would if I were you. The way you described would work fine
Introduction
This is a collection of Tools and Resources for Flashing Mi2(s)(c).
MiFlash4Linux
https://github.com/M1cha/aries-image-builder
Core Recovery Package for MiFlash
This is a small package to Recovery MI2 from any bricked state. It has the following advantages over the official ones from Xiaomi:
They don't flash any ROM, just the core system(bootloaders, modem and recovery)
They are small which means both Download and Installation are faster
It directly installs custom Bootloader and TWRP. That means you easily get your device back to a modded status.
Please follow the official MiFlash guidelines for installation with the following differences:
the DLOAD config is called rawprogram_core.xml
the fastboot script is called flash_core.bat(or flash_core.sh for linux)
there's a script called flash_partition_table_and_core which is a alternative to flash_core.bat/sh.
It can be used to change the partition table.
USE THIS WITH THE CUSTOM BOOTLOADER INSTALLED BY ONE OF THE CORE PACKAGES ONLY. Xiaomi's bootloader will format your whole MMC device. THIS WOULD ERASE YOUR EFS AND YOU CAN'T MAKE CALLS ANYMORE
Changing the partition table
There are multiple packages available:
separated: Xiaomi's original layout with a virtual internal sdcard
separated_single: same as separated but without Dualsystem and bigger system partitions
unified: Xiaomi's new layout with /data/media support
unified_single: same as unified but without Dualsystem and bigger system partitions
unified_single_xiaomi: Xiaomi's version of unified_single
SkiFire13 said:
aries_core_unified_single.zip -> only MIUI > 5.4.x or M1cha's CM12.1 or latest AOSP5 works (only they can see Internal Storage, that now is a virtual sd-card in /data/media/0)
aries_separated_single.zip -> other roms
Click to expand...
Click to collapse
Installation:
Backup all your data(including internal sdcard, and EFS just to be safe)
if you don't use the custom Bootloader yet, flash this package using flash_core.bat/sh first. See the big red warning above for more information
flash the package using flash_partition_table_and_core.bat/sh
boot into recovery(which is TWRP now), recreate the filesystems for all partitions(system,data,cache,sdcard to ext4) in the wipe menu and reinstall your ROM.
Version Information
Bootloader: https://github.com/M1cha/mi2_lk/commits/LA.AF.1.1-02810-8064.0
TWRP: v2.8.7.0
core partitions: aries_images_5.7.16_20150626.0000.4_5.0_cn_a63cddccfa.tgz
Download links for Mobile users:
aries_core_unified_single_xiaomi.zip
aries_core_unified_single.zip
aries_core_unified.zip
aries_core_separated_single.zip
aries_core_separated.zip
XDA:DevDB Information
Flashtools, Tool/Utility for the Xiaomi Mi 2
Contributors
m11kkaa
Source Code: https://github.com/M1cha/aries-image-builder
Version Information
Status: Stable
Created 2015-02-21
Last Updated 2015-07-27
First (as always)
Sent from my A0001
the singleboot packages causes the latest version of CM12 to fail booting because of SELinux enforcing. I'll upload a fixed package asap.
everything has been fixed and is up again.
Pls download everything again(especially MiFlash4Linux if u use that).
i think i will wait util the release of GRUB4Android....
acastrocab said:
i think i will wait util the release of GRUB4Android....
Click to expand...
Click to collapse
the purpose of this thread is not G4A
G4A doesn't allow u to change the partition table. I may publish a simple tool for it though.(so u don't need a computer).
m11kkaa said:
the purpose of this thread is not G4A
G4A doesn't allow u to change the partition table. I may publish a simple tool for it though.(so u don't need a computer).
Click to expand...
Click to collapse
Hey m11kkaa, I'm sorry for the noob question, but where can I download the files for windows? And how should I use them? I can't understand from the OP. Thanks in advantage for your help
MyNameIsKappa said:
Hey m11kkaa, I'm sorry for the noob question, but where can I download the files for windows? And how should I use them? I can't understand from the OP. Thanks in advantage for your help
Click to expand...
Click to collapse
On the top of the page just followed by the title, there is a "Download" tab, you could find the miracle at there ;p
MyNameIsKappa said:
Hey m11kkaa, I'm sorry for the noob question, but where can I download the files for windows? And how should I use them? I can't understand from the OP. Thanks in advantage for your help
Click to expand...
Click to collapse
I can't find the links too, but i saw this link in another thread... http://forum.xda-developers.com/devdb/project/?id=8360#downloads
ancics said:
I can't find the links too, but i saw this link in another thread... http://forum.xda-developers.com/devdb/project/?id=8360#downloads
Click to expand...
Click to collapse
You can see this with a computer only.(Tapatalk doesn't work)
http://puu.sh/gamlY/dd7e4904f9.png
Hey M1cha, thank you! Great job!
I have some issues about the procedure:
1. I am not sure if already had a custom bootloader, so first i'll flash the package flash_core.bat :
- turn on mi2s in fastboot mode
- plug usb, device should appear in miflash(the program should be configured as the photo?)
- and click flash
- reboot phone, enter in fastboot mode again and do the same procedure with flash_partition_table_and_core.bat
Is that right?
It's easy to recreate the ext4 filesystem in TWRP? always used CWM....
m11kkaa said:
You can see this with a computer only.(Tapatalk doesn't work)
http://puu.sh/gamlY/dd7e4904f9.png
Click to expand...
Click to collapse
Oh that's why, I'll download it from a computer, thanks!
Sent from my MI 2S using XDA Free mobile app
@m11kkaa: thnx for the linux tools/scripts, it made my migration from CWM to single-system partition + new bootloader + TWRP easier.
BTW, I just wanted to migrate and keep my current CM11 for the time being. I had to fight a bit with restore from backup because I was not aware of the incompatibility between CWM and TWRP, luckily enough it eventually was sufficient to:
reformat system, data and cache in TWRP
flash the old CWM temporarily and restore boot, system and data
flash TWRP again and make new backups.
Proposal:
It would be good if you can change the heading style of "Installation" in the OP to be the same as e.g "Introduction", because now it looks like part of "Singleboot Partition Layout" section only. It is confusing IMHO.
In my case (i.e. flashing both flash_core.sh and then flash_partition_table_and_core.sh), I had to recreate ext4 FS not only on the system partition in TWRP, but also on the data partition (it could not be mounted and TWRP announced 0 MB size) and eventually also on the cache partition. This seems to contradict the info in OP, part "Singleboot Partition Layout", which mentions that data will be preserved.
@cogano thx for your feedback
it's weird that u had to recreate the filesystems because the positions of these partitions still are the same. I resized system1, modem1 and boot1 to 2KB and system, modem and boot to 2*oldsize-2KB. I checked the offsets and they still are the same.
I have another phone and plan to do the same some time in the next week.
I'll try to avoid the trial&error approach and keep notes between the steps.
P. S. I am quite proficient with Linux administration. However I have to admit that upgrading android devices is usually a risky thing: I would have to read lot of guides - often unclear and confusing - or just give it a go and resolve the problems as they appear. The latter one eventually seems to be faster
cogano said:
I have another phone and plan to do the same some time in the next week.
I'll try to avoid the trial&error approach and keep notes between the steps.
P. S. I am quite proficient with Linux administration. However I have to admit that upgrading android devices is usually a risky thing: I would have to read lot of guides - often unclear and confusing - or just give it a go and resolve the problems as they appear. The latter one eventually seems to be faster
Click to expand...
Click to collapse
thx "parted /dev/block/mmcblk0 p" will help to debug these things.
If you don't have a ROM/Recovery with parted you can reboot to dload from the bootloader which will provide ur whole MMC as a usb drive to your computer.
i didn't see the download tab at first, so i downloaded the whole zip from the github and excuted the ./build.sh in Cygwin. Anyway, it works!
m11kkaa said:
you can reboot to dload from the bootloader which will provide ur whole MMC as a usb drive to your computer.
Click to expand...
Click to collapse
What a great feature!
superiyezi said:
i didn't see the download tab at first, so i downloaded the whole zip from the github and excuted the ./build.sh in Cygwin. Anyway, it works!
Click to expand...
Click to collapse
There's a Download "card" on top.
What are the partitions sizes after flashing the singleboot partition layout?
The following is the latest version of TWRP compiled for the T-mobile V10 Model H901.
https://androidfilehost.com/?fid=818070582850501883
MD5SUM: b89d341cd61da31a5348d8f6b3c75c97
The heavy lifting was done by the twrpbuilder project who were generous enough to compile TWRP for our device. They also provide their services to see TWRP is available for devices that don't yet have it. I've personally used this version to do a backup and restore but can't guarantee there won't be issues. If there are while you are still in twrp you should go to the advanced section and copy the log to your external sd card. This log will help them diagnose any issues.
The project is located at: https://twrpbuilder.github.io
Their XDA thread is located here: https://forum.xda-developers.com/android/apps-games/twrpbuilder-t3744253
If you already have TWRP installed installation is as follows: Click Install, choose Image file, navigate to where the TWRP img file is located on your external sdcard and flash that img to the recovery partition. Back out to the root dir and you can select reboot then recovery...it should bounce you right back into recovery and you should see the new version loaded. If you have root in the rom and run into issues the app "flashify" can reflash TWRP 3.0 so make sure you also have it's img available.
This is pretty much only for folks who already have twrp to update to the latest. If you are on nougat you are still stuck until an exploit is released that works for nougat the way dirtycow did for marshmallow and below. *update* an exploit to give root to nougat users is now available thanks to @runningnak3d here: https://forum.xda-developers.com/tmobile-lg-v10/general/root-h901-nougat-t3773942
Reserved Post #1
Reserved Post #2
famewolf said:
The following is the latest version of TWRP compiled for the T-mobile V10 Model H901.
https://www.androidfilehost.com/?fid=8180705828505018
MD5SUM: b89d341cd61da31a5348d8f6b3c75c97
Click to expand...
Click to collapse
Looks to me like that URL should read
https://androidfilehost.com/?fid=818070582850501883
[ EDIT ] Yup, confirmed.. The URL I listed works fine.
Thanks for the file!
:laugh::silly:
NYLimited said:
Looks to me like that URL should read
https://androidfilehost.com/?fid=818070582850501883
[ EDIT ] Yup, confirmed.. The URL I listed works fine.
Thanks for the file!
:laugh::silly:
Click to expand...
Click to collapse
You are correct. For some reason a few characters got truncated. I've corrected the url in post #1.
famewolf said:
The following is the latest version of TWRP compiled for the T-mobile V10 Model H901.
https://androidfilehost.com/?fid=818070582850501883
MD5SUM: b89d341cd61da31a5348d8f6b3c75c97
The heavy lifting was done by the twrpbuilder project who were generous enough to compile TWRP for our device. They also provide their services to see TWRP is available for devices that don't yet have it.
Click to expand...
Click to collapse
Just as an aside, this version seems to correct (mostly) the date issue of previous TWRP versions for the V10. Versions before this one used to generate a default date (folder name) for the backup dating back to the 1970s as I recall.
This one has the correct month and day and time and the year is only 1 off - it showed 2017 on my very quick attempt to play with it.
One additional note to those installing it via TWRP itself - after selecting image flash , MAKE SURE you specify RECOVERY partition, not BOOT! Specifying BOOT will most likely have some less than desirable results.. :laugh:
NYLimited said:
Just as an aside, this version seems to correct (mostly) the date issue of previous TWRP versions for the V10. Versions before this one used to generate a default date (folder name) for the backup dating back to the 1970s as I recall.
This one has the correct month and day and time and the year is only 1 off - it showed 2017 on my very quick attempt to play with it.
One additional note to those installing it via TWRP itself - after selecting image flash , MAKE SURE you specify RECOVERY partition, not BOOT! Specifying BOOT will most likely have some less than desirable results.. :laugh:
Click to expand...
Click to collapse
I've passed on the date issue. Uncertain if he'll generate another build though.
famewolf said:
I've passed on the date issue. Uncertain if he'll generate another build though.
Click to expand...
Click to collapse
Seems that either nobody is using this version or nobody knows about it or they just have nothing to say..
Anyway, as you know, I have spent a fair amount of time recently working with this and installing it. A couple of observations that may be worth noting..
I double checked and I did set a screen timeout on TWRP. Previous versions would first, dim the screen, followed by turning it off completely. If you had the device near you on a desk while backing up the screen lighting up again when TWRP completed was a sure signal that it was finished.
This version of TWRP dims the screen but the screen is never turned off completely. A minor annoyance I suppose but something is different from previous versions.
During the /data partition backup I noted a (to me) new display in yellow: "Backups of data do not include any files in internal storage such as pictures or downloads"
Seriously? Is this something new? Certainly the display is but I always kinda relied on all that being backed up with /data and having the ability to restore them. This is a more serious issue for me which may make me consider going backward..
Thoughts?
NYLimited said:
Seems that either nobody is using this version or nobody knows about it or they just have nothing to say..
Anyway, as you know, I have spent a fair amount of time recently working with this and installing it. A couple of observations that may be worth noting..
I double checked and I did set a screen timeout on TWRP. Previous versions would first, dim the screen, followed by turning it off completely. If you had the device near you on a desk while backing up the screen lighting up again when TWRP completed was a sure signal that it was finished.
This version of TWRP dims the screen but the screen is never turned off completely. A minor annoyance I suppose but something is different from previous versions.
During the /data partition backup I noted a (to me) new display in yellow: "Backups of data do not include any files in internal storage such as pictures or downloads"
Seriously? Is this something new? Certainly the display is but I always kinda relied on all that being backed up with /data and having the ability to restore them. This is a more serious issue for me which may make me consider going backward..
Thoughts?
Click to expand...
Click to collapse
I use my v10 as my backup phone now. On my HTC U11 life when I make a nandroid it shows that it is not backing up files on internal storage. I think this is normal now on the latest version of twrp.
NYLimited said:
Seems that either nobody is using this version or nobody knows about it or they just have nothing to say..
Anyway, as you know, I have spent a fair amount of time recently working with this and installing it. A couple of observations that may be worth noting..
I double checked and I did set a screen timeout on TWRP. Previous versions would first, dim the screen, followed by turning it off completely. If you had the device near you on a desk while backing up the screen lighting up again when TWRP completed was a sure signal that it was finished.
This version of TWRP dims the screen but the screen is never turned off completely. A minor annoyance I suppose but something is different from previous versions.
During the /data partition backup I noted a (to me) new display in yellow: "Backups of data do not include any files in internal storage such as pictures or downloads"
Seriously? Is this something new? Certainly the display is but I always kinda relied on all that being backed up with /data and having the ability to restore them. This is a more serious issue for me which may make me consider going backward..
Thoughts?
Click to expand...
Click to collapse
On your last issue this is business as usual...twrp has NEVER backed up the internal SDCARD unless you selected the sdcard entry in the list of sections to be backed up. DCIM (pictures) and the Downloads folder/dir have never been included.
As to the dimming, you can check in settings to see if something can be configured however each person compiling twrp can set their own options as to how they want it to function. There is no guarantee or expectation that Person B is going to use the same options as Person A. You are of course free to compile your own copy configured the way you would prefer it to behave but the process was enough of a pain in the butt I just requested twrpbuilder to generate one as I kept getting errors. The process to compile it also appears poorly documented.
sabresfan said:
I use my v10 as my backup phone now. On my HTC U11 life when I make a nandroid it shows that it is not backing up files on internal storage. I think this is normal now on the latest version of twrp.
Click to expand...
Click to collapse
I kinda suspected that but that is, at best, a questionable choice since I don't even have the option to check or uncheck a selection for it. Not happy..
famewolf said:
On your last issue this is business as usual...twrp has NEVER backed up the internal SDCARD unless you selected the sdcard entry in the list of sections to be backed up. DCIM (pictures) and the Downloads folder/dir have never been included.
Click to expand...
Click to collapse
Not quite. INTERNAL is not the SD Card. Internal is emulated sd on /0. In TWRP if you tap select storage, for example, you can pick "internal" or "SD" for backup destination, as one example.
I keep a fair number of things in /Download - things I grab in my travels, things I save there for later use.. whatever. I'll have to device a Tasker module or something for copying all those to the actual SD card...
NYLimited said:
I kinda suspected that but that is, at best, a questionable choice since I don't even have the option to check or uncheck a selection for it. Not happy..
Not quite. INTERNAL is not the SD Card. Internal is emulated sd on /0. In TWRP if you tap select storage, for example, you can pick "internal" or "SD" for backup destination, as one example.
I keep a fair number of things in /Download - things I grab in my travels, things I save there for later use.. whatever. I'll have to device a Tasker module or something for copying all those to the actual SD card...
Click to expand...
Click to collapse
A fairly recent app/utility created by @kdrag0n called Tipatch brings a long-needed resolution to the table regarding "full backups" of Data using TWRP. In a nutshell, Tipatch installs to your Android device as a basic APK. Within the simple GUI, once root permissions are granted (In-Place Patching) Tipatch will decompile, patch, recompile and flash the patched TWRP to /recovery, effectively patching your TWRP build to backup the contents of Internal Storage (emulated SD card) as part of Data itself, so that backups will now include those Internal Storage contents such as downloads, photos, videos, game data, and other various files. I've tried it on this particular build of TWRP and it works without any issues. There are options to patch TWRP without root permissions as well. There are Windows, Mac & Linux versions available too. If you are patching TWRP on a device with an A/B partitioning scheme, the patched TWRP can be installed on both A & B using a one-click option. Of course, one insurmountable caveat to patching TWRP with Tipatch is that wiping Data now will also wipe Internal Storage (emulated SD card). In short, the utility works on pretty well all device types and chipset platforms (Exynos, Kirin, Snapdragon, MediaTek, etc.). The latest Tipatch update, v1.6, includes support for TWRP builds that use LZMA compression, and removes the now-misleading notification previously listed when backing up Data -- that Internal Storage (/data/media/ path / emulated SD card) contents are not backed up. Anyway guys, here is a link to the Tipatch Discussion & Support thread: https://forum.xda-developers.com/android/apps-games/app-twrp-tipatch-backup-internal-t3831217
The latest Tipatch v1.6 app is also available on the Play Store and many other app & apk repos for Android. Versions for Windows, Mac and Linux can be downloaded using the above link.