Related
This guide is show you how to install second OS in SDCard, so you can have two complete separate OS (each have their own /system, /data and /cache), this will be useful if you want to try out a new ROM or a new version, like CM or latest Stock build etc. I have pre-build 2 ROMs in this guide. and list the instructions of how to do it in post #2.
The whole method is just an implementation of @SHM (Modding.MyMind) guide that inside the post here, so all the credit goes to him:
http://forum.xda-developers.com/showpost.php?p=62460895&postcount=325
Highlight of the steps:
1. Partition a SDCard (32GB or bigger) to have 3 ext4 partitions after regular FAT32 partition
2. Flash two customized flashable zip in twrp so that:
boot image flashed to /dev/block/mmcblk0p18 (regular boot partition)
system image flashed to /dev/block/mmcblk1p2 (sdcard)
The boot image contains the fstab file, it has been updated to use partitions on sdcard as the /system, /data and /cache for the 2nd OS.
And of course, the flashable zip has updater script changed so that, it will flash they system image to correct partition on SDCard.
Note / Limitation:
1) After boot to 2nd OS on the SDCard, theoretically, while you are in Android OS, everything should work. The speed/performance may differ depends on the SDCard read/write speed.
2) TWRP, except flash the zip to install the customized system image to SDCard, all other function will not work for the 2nd OS, The backup/restore function is still working on the primary OS /system, /data etc.
3) Boot partition (/dev/block/mmcblk0p18), this partition will decide which OS it will boot, and the boot image should corresponded to your OS system partition. So if you flashed above boot image for 2nd OS, it will find /system on SDCard and boot it. And if you flashed (or restore) your primary OS boot image, then it will boot to your primary OS /system.
Things you need before you start:
1. MT2L03 with Lollipop installed, TWRP installed, and have a backup of your primary OS (at least /system, and /boot partitions)
2. An empty SDCard that is 32GB or bigger, strongly recommend class 10 or faster. (16GB will work, then you don't have much external space left)
Steps to install 2nd OS to sdcard:
(Note, I will call the empty SDCard as sdcard#2, and your current sdcard in the phone as sdcard#1.)
1. Make a backup of your current OS using twrp, include at least /system and /boot, to your sdcard#1.
2. Install the PartitionWizard (files location below) on windows, and put the empty SDCard#2 to computer sdcard reader.
3. Launch Partition Wizard, and carefully re-partition your SDCard#2 to following:
(pls refer to xda wiki about the usage: http://forum.xda-developers.com/wiki/SD_card_partitioning )
1st Partition: FAT32 primary size: (Total size minus 15000MB), for example, for 64GB(60000MB) card, choose 45000MB
2nd: ext4 primary size: 1800MB (/system for 2nd OS)
3rd: ext4 primary size: 12500MB (/data for 2nd OS)
4rd: ext4 primary size: rest space, should be great than 200MB (/cache for 2nd OS)
Since partition 2/3/4 total size is 14320MB, thus the 1st partition size is (Total size minus 15000MB)
4. Apply the change, this will take some time (like 20 to 30min).
5. Once sdcard#2 is re-partitioned and formatted, unplug and re-plug sdcard#2 to windows again. Right click the sdcard drive letter, and click "Open" to open the FAT32 partition. ( I found double click the drive letter will give error if the FAT32 is bigger than 32GB, but right click and open works)
Copy two flashable zip (file location below) to the sdcard#2.
6. Reject the sdcard#2, and remove it from windows machine.
7. In Mate2 phone, go to settings, storage, and un-mount your current SDCard#1, after it is unmounted, take out the sdcard#1 and put it to a save place. Do not mess the two sdcards!!
8. Put in the sdcard#2 to the phone, and reboot to TWRP.
9. Install the two zip you download in step 5 from sdcard#2. Reboot.
How to go back to your primary OS:
a. Put in sdcard#1 to the phone, boot into TWRP, restore your /boot partition from the backup you took in above step 1. then reboot.
How to switch to the 2nd OS on the sdcard again:
a. Put in sdcard#2 to the phone, boot into TWRP, flash the "MT2L03_xxx_BootOnly.zip" you downloaded in step 5.
Files to download:
PartitionWizard in above step 2:
http://tinyurl.com/q62m68x
location: under Lollipop/SD_Partition_Tools
FileName: pwfree91.exe
This tools is mentioned in XDA wiki: http://forum.xda-developers.com/wiki/SD_card_partitioning
You can use any tool you know to do the re-partition, above tools is what I used and it works.
Customized flashable in zip in above step 5:
http://tinyurl.com/q62m68x
location: under Lollipop/OS_on_SDCards
FileName:
If you want install B309 as 2nd OS, please download "MT2L03_B309_DBoot_BootOnly.zip" and "MT2L03_B309_DBoot_SystemWithRoot.zip"
If you want install CM12 as 2nd OS, please download "MT2L03_CM12_0820_DBoot_BootOnly.zip" and "MT2L03_CM12_0820_DBoot_SystemWithRoot.zip". (Please note the GApp is already included in the zip)
Attached two screenshot of the partition tool, one for 32GB, one for 64GB. Please note though the pic showing in GB, but when config the size, please use MB to make sure the partition size is accurate and big enough.
//reserved
I am not sure how many people is interested in dual boot, so for now, I have pre-built B309 and CM12 only.
In order to build a customize ROM for installing in SDCard, as detailed in SHM original post, two steps are required:
1) For Mate2, after split the original boot image, and unpack the ramdisk, only need following cmd to update the fstab:
cd ramdisk
sed -i 's/platform\/msm_sdcc.1\/by-name\/system/mmcblk1p2/g' fstab.qcom
sed -i 's/platform\/msm_sdcc.1\/by-name\/userdata/mmcblk1p3/g' fstab.qcom
sed -i 's/platform\/msm_sdcc.1\/by-name\/cache/mmcblk1p4/g' fstab.qcom
Then repack it back to boot2.img. Please note the un/repack boot image tool need support DTB section.
2) Then in the updater script of /META-INF/com/google/android/updater-script, install system.img to /dev/block/mmcblk1p2, and still install the new boot2.img to /dev/block/mmcblk0p18.
@SHM, Unfortunately, many tools mentioned in original post, the Aparted tool, and the android binary mkbootimg etc all have problem running under Lollipop, so for now, I am doing all the ROM modification under linux.
Lol. You just had to do it. Lol awesome work. And you picked up on that fast. Thanks Xordos.
Our divices supposedly only support up to a 64 gb SD card. I wonder if since we would partition the SD if it would accept a 128GB card and see it as two x 64GB's
MikeyLee said:
Our divices supposedly only support up to a 64 gb SD card. I wonder if since we would partition the SD if it would accept a 128GB card and see it as two x 64GB's
Click to expand...
Click to collapse
I think if huawei mention 64gb probably because they didn't have 128gb to test when they release the phone. 128gb has nothing special compare with 64gb card. But I could be wrong since I don't have 128gb.
For general use, no need to partition 128gb card unless you want to do something like this thread.
@xordos, no worries. Many things were broken because of Lollipop using a new linker file that checks if the binary is PIE or not. If it is not PIE or if it's not Statically compiled then it won't work on Lollipop. The linker file can be modified though to ignore this check and thus allow them to work regardless. This too could also resolve some issues with other apps not wanting to work on Lollipop . Modifying the linker file is relatively simple but this is off topic so I shall end it here.
Great work. Knew you would be able to get it done. Cheers!
Sent from my C525c using Tapatalk
SHM said:
@xordos, no worries. Many things were broken because of Lollipop using a new linker file that checks if the binary is PIE or not. If it is not PIE or if it's not Statically compiled then it won't work on Lollipop. The linker file can be modified though to ignore this check and thus allow them to work regardless. This too could also resolve some issues with other apps not wanting to work on Lollipop . Modifying the linker file is relatively simple but this is off topic so I shall end it here.
Great work. Knew you would be able to get it done. Cheers!
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
yup, exactly PIE problem.
So this is pretty cool that no need to worry about /data mixed up by different rom. but open the back cover is a little bit pain and my main sdcard is almost full so I am thinking to use otg cable. So i am wondering if we have grub-like boot image to have boot menu, or, the root is not ramdisk, but a file system, so we can modify the fstab after mount it. I know, maybe I ask too much, android is not design like linux.
xordos said:
yup, exactly PIE problem.
So this is pretty cool that no need to worry about /data mixed up by different rom. but open the back cover is a little bit pain and my main sdcard is almost full so I am thinking to use otg cable. So i am wondering if we have grub-like boot image to have boot menu, or, the root is not ramdisk, but a file system, so we can modify the fstab after mount it. I know, maybe I ask too much, android is not design like linux.
Click to expand...
Click to collapse
Yea, it's pretty nice. You can even modify the TWRP recovery for use with making backups and restoring to each Rom specific to their partition. Look at TWRP Unified and check out it's script inside the ramdisk. Modify the script to check some stuff and tell it which fstab to use . This way when you jump back and forth between roms just by the boot.img you flash TWRP will automatically recognize the change upon it booting up and target the partitions properly when you make a backup/restore. Put some thought into all of this and I am sure you could take this thread a bit further.
There are projects out there that are designed for multibooting on android devices but you would need to port one of them.
Sent from my C525c using Tapatalk
Just an update that the AParted app works for Lollipop now. Tested it out on my external sd tonight by resizing my fat partition without losing any of my contents and adding additional partitions with multiple filesystem's such as f2fs and ext4. Quick and effective .
Sent from my Ascend Mate 2 using Tapatalk
I have a HUGE GIFT that I am about to share for all you mate2 fans out there. Dual Booting just got taken to another level. Think of it as Multi Booting . Here are two screenshots to share as teasers. I have it working for our device and its a beast!
Sent from my Ascend Mate 2 using Tapatalk
SHM said:
I have a HUGE GIFT that I am about to share for all you mate2 fans out there. Dual Booting just got taken to another level. Think of it as Multi Booting . Here are two screenshots to share as teasers. I have it working for our device and its a beast!
Sent from my Ascend Mate 2 using Tapatalk
Click to expand...
Click to collapse
Can't waiting.
MT2-User said:
Can't waiting.
Click to expand...
Click to collapse
More teasers. These pics show that its possible to install roms without the need for TWRP. Will be sharing this very soon. I'm running CM, PAC, and Carbon right now.
Sent from my Ascend Mate 2 using Tapatalk
SHM said:
More teasers. These pics show that its possible to install roms without the need for TWRP. Will be sharing this very soon. I'm running CM, PAC, and Carbon right now.
Sent from my Ascend Mate 2 using Tapatalk
Click to expand...
Click to collapse
You run all three (or four including stock one)?
MT2-User said:
You run all three (or four including stock one)?
Click to expand...
Click to collapse
Yes. I can install the roms using either the system, data, and/or cache partition however I don't recommend cache because it's size is way too small for our device. Can even choose to install them on your external sd. I can install and run as many roms as I like as long as I have space for the new ROM. The app even makes it possible to install new builds to the proper ROM without touching your primary ROM or any other ROM other than what its told to target. More info will be shared when I open a thread on it. In short, you just download the ROM, then patch the ROM.zip using the app. You then flash that patched zip which in turns will modify the boot.img to give it dualboot support. You can patch zips for SuperSU, gapps and so forth so you may install them to a specific ROM. Its legit bro.
Sent from my Ascend Mate 2 using Tapatalk
SHM said:
Yes. I can install the roms using either the system, data, and/or cache partition however I don't recommend cache because it's size is way too small for our device. Can even choose to install them on your external sd. I can install and run as many roms as I like as long as I have space for the new ROM. The app even makes it possible to install new builds to the proper ROM without touching your primary ROM or any other ROM other than what its told to target. More info will be shared when I open a thread on it. In short, you just download the ROM, then patch the ROM.zip using the app. You then flash that patched zip which in turns will modify the boot.img to give it dualboot support. You can patch zips for SuperSU, gapps and so forth so you may install them to a specific ROM. Its legit bro.
Sent from my Ascend Mate 2 using Tapatalk
Click to expand...
Click to collapse
Could they or some of them share Data?
MT2-User said:
Could they or some of them share Data?
Click to expand...
Click to collapse
Not at the moment. You would have to reinstall your user apps again. You can backup your apps on your primary rom using something like Titanium backup and then restore them on the other ROM.
Sent from my Ascend Mate 2 using Tapatalk
SHM said:
Not at the moment. You would have to reinstall your user apps again. You can backup your apps on your primary rom using something like Titanium backup and then restore them on the other ROM.
Sent from my Ascend Mate 2 using Tapatalk
Click to expand...
Click to collapse
oh ic
MT2-User said:
oh ic
Click to expand...
Click to collapse
The app implements this feature but I'm working it out if that makes you feel better lol.
Sent from my Ascend Mate 2 using Tapatalk
Damn nice work SHM.. Congrats. And thanks!
Moody66 said:
Damn nice work SHM.. Congrats. And thanks!
Click to expand...
Click to collapse
I have it working %100 now. Its 3:35 am where I am at so time for bed. Sharing apps works as well between roms.
Sent from my Ascend Mate 2 using Tapatalk
Moto E Wi-Fi Won't Turn On after update CM 13.0 official nightly on today with latest open gapps. My Mac address automatically change with 02:00:00:00:00:00
What can i do? Help me
ansariziya said:
Moto E Wi-Fi Won't Turn On after update CM 13.0 official nightly on today with latest open gapps. My Mac address automatically change with 02:00:00:00:00:00
What can i do? Help me
Click to expand...
Click to collapse
Same here. It also corrupted my 32GB mem card, though I didn't select the external as internal option...... :crying: Now crying over my dead mem card!
ansariziya said:
Moto E Wi-Fi Won't Turn On after update CM 13.0 official nightly on today with latest open gapps. My Mac address automatically change with 02:00:00:00:00:00
What can i do? Help me
Click to expand...
Click to collapse
So after lots of flashing of different roms on my Moto E 1st gen
(XT1022) I ended up unable to turn WIFI on in any rom, including
stock!
Thing is, after days of breaking my head with this, I figured out I was
missing the WCNSS_qcom_wlan_factory_nv.bin file from the /Persist
folder.
How did that file go missing and why it was not restored when
restoring to stock or flashing roms? Dam good question, I don't have
an answer to that yet, BUT, I have a fix.
Simply download the attached .rar, unzip it, and manually put the
WCNSS_qcom_wlan_factory_nv.bin file in your /Persist folder using
any root explorer / file manager on your device and reboot!
Such a simple little thing gave me so much trouble, hope this will help
future users who might face the same problem, as I already saw
around that other people are also having the same issue.
Happy surfing on your now working WIFI!:fingers-crossed:
Download Link
dl-1.va.us.xda-developers.com/3/1/2/3/7/7/6/WCNSS_qcom_wlan_factory_nv.rar?key=7MqiX7xPQucqnzDa6IO7Yw&ts=1459273984
Thank you for reply but Download link not work. Can you send me e-mail this file me on [email protected]
Thanks in advance
================
Deepak5310 said:
So after lots of flashing of different roms on my Moto E 1st gen
(XT1022) I ended up unable to turn WIFI on in any rom, including
stock!
Thing is, after days of breaking my head with this, I figured out I was
missing the WCNSS_qcom_wlan_factory_nv.bin file from the /Persist
folder.
How did that file go missing and why it was not restored when
restoring to stock or flashing roms? Dam good question, I don't have
an answer to that yet, BUT, I have a fix.
Simply download the attached .rar, unzip it, and manually put the
WCNSS_qcom_wlan_factory_nv.bin file in your /Persist folder using
any root explorer / file manager on your device and reboot!
Such a simple little thing gave me so much trouble, hope this will help
future users who might face the same problem, as I already saw
around that other people are also having the same issue.
Happy surfing on your now working WIFI!:fingers-crossed:
Download Link
dl-1.va.us.xda-developers.com/3/1/2/3/7/7/6/WCNSS_qcom_wlan_factory_nv.rar?key=7MqiX7xPQucqnzDa6IO7Yw&ts=1459273984
Click to expand...
Click to collapse
PoseidonKing said:
Same here. It also corrupted my 32GB mem card, though I didn't select the external as internal option...... :crying: Now crying over my dead mem card!
Click to expand...
Click to collapse
Did you tried plugging to a pc and repartition it?
-z3r0- said:
Did you tried plugging to a pc and repartition it?
Click to expand...
Click to collapse
No, I didn't. Explain please.....
Did, you flashed a custom kernel on the Rom ?
Try, not to flash the kernel and Reflash the Rom after wiping all the data,system etc.
It might be helpful.
PoseidonKing said:
No, I didn't. Explain please.....
Click to expand...
Click to collapse
Plug ur mem card into a card reader and.
Try this:
1. Open cmd (run as administrator)
2. Type DISKPART, a new window will open.
3. Type list disk/drive ( i dnt remember, but it's either of them )
4. Select end 32gigs partition by:
Code:
select drive 1
(Whichever drive shows size of 32 gigs)
5. Type CLEAN
6. then again
Code:
select drive 1
(Whichever drive shows size of 32 gigs)
And type,
Code:
create partition primary
And then,
Code:
select partition 1
7.Type
format fs=fat32
It'll take some time.. But yea, will surely work and save your tears..
Do let me know..
Hit the thinks botton if it helped..
Or Use Mini Tool Partition Wizard
I flashed the Unofficial CM13 on my Moto E 2015 using TWRP and since then my wifi is gone. I am also facing same issue wherein the wifi would immediately turn off after turning it on. I tried the solution mentioned about putting that file in the /persist folder (I downloaded the file from another thread since the link in this thread is broken) but using ES Explorer, it is not allowing me to copy and keeps saying "Copy Failed". I am not sure how to change permissions using ESexplorer.
What can I do to fix this ?
PoseidonKing said:
No, I didn't. Explain please.....
Click to expand...
Click to collapse
So, did it work?
Link not working, kindly share the file to [email protected]
Deepak5310 said:
So after lots of flashing of different roms on my Moto E 1st gen
(XT1022) I ended up unable to turn WIFI on in any rom, including
stock!
Thing is, after days of breaking my head with this, I figured out I was
missing the WCNSS_qcom_wlan_factory_nv.bin file from the /Persist
folder.
How did that file go missing and why it was not restored when
restoring to stock or flashing roms? Dam good question, I don't have
an answer to that yet, BUT, I have a fix.
Simply download the attached .rar, unzip it, and manually put the
WCNSS_qcom_wlan_factory_nv.bin file in your /Persist folder using
any root explorer / file manager on your device and reboot!
Such a simple little thing gave me so much trouble, hope this will help
future users who might face the same problem, as I already saw
around that other people are also having the same issue.
Happy surfing on your now working WIFI!:fingers-crossed:
Download Link
dl-1.va.us.xda-developers.com/3/1/2/3/7/7/6/WCNSS_qcom_wlan_factory_nv.rar?key=7MqiX7xPQucqnzDa6IO7Yw&ts=1459273984
Click to expand...
Click to collapse
Please share me the file - [email protected]
http://forums.androidcentral.com/go...-wifi-won-t-turn-mac-address-unavailable.html
The solution by Huong Cao seems to work for me.
Sorry if i interpreted some things wrongly
hey guys hope u are doing fine , so lately there being this way to hide the system folder of a rom zip so u can't access the system/app or syste/priv-app so i really need to edit a rom like RN or lineageOS before flashing it , is there a way u can show me please ?
The /system folder is inside system.imgin the zip
Use 7zip to extract just that, mount the IMG with some kind of special program (windows doesn't recognise ext4 partitions) edit it, then put the IMG back in the same zip.
BTW, I came across a good tutorial on what you are trying to do some time ago. I don't remember if it was here, on XDA. Have you tried googling it?
Vagelis1608 said:
The /system folder is inside system.imgin the zip
Use 7zip to extract just that, mount the IMG with some kind of special program (windows doesn't recognise ext4 partitions) edit it, then put the IMG back in the same zip.
BTW, I came across a good tutorial on what you are trying to do some time ago. I don't remember if it was here, on XDA. Have you tried googling it?
Click to expand...
Click to collapse
yeah thnx i tried googlin but all i found was obsolete like posted in 2012 back then the editin was simple and the system file wasn't hidden , and what kind of special programs i can use to mount the image ? m already usin 7zip
berraffarouk15 said:
yeah thnx i tried googlin but all i found was obsolete like posted in 2012 back then the editin was simple and the system file wasn't hidden , and what kind of special programs i can use to mount the image ? m already usin 7zip
Click to expand...
Click to collapse
i guess i found it this is it
https://forum.xda-developers.com/android/help/extract-dat-marshmallow-lollipop-easily-t3334117
berraffarouk15 said:
i guess i found it this is it
https://forum.xda-developers.com/android/help/extract-dat-marshmallow-lollipop-easily-t3334117
Click to expand...
Click to collapse
That is not the one I had found, but it should work.
Try it. Let me know.
Vagelis1608 said:
That is not the one I had found, but it should work.
Try it. Let me know.
Click to expand...
Click to collapse
hey , works fine for marshmallow and lollipop but unfortunately doesn't work for nougat 7.1.2 ,he said he tested it for 7.1.1 but no luck here , so what i'm tryin to do is delete the aosp keyboard cause when i try to install the gapps and install the gboard the package got mixed and when ever i try access the options in gboard it got force close (i tried manually uninstalling the aosp and clean all it data and remaining folders but o luck all ways the same problem it says the package conflicts and even if i success to manually install it it force close when ever i want to personalize the keyboard like shotin down the auto correction or ,,,, so any help here ?
berraffarouk15 said:
hey , works fine for marshmallow and lollipop but unfortunately doesn't work for nougat 7.1.2 ,he said he tested it for 7.1.1 but no luck here , so what i'm tryin to do is delete the aosp keyboard cause when i try to install the gapps and install the gboard the package got mixed and when ever i try access the options in gboard it got force close (i tried manually uninstalling the aosp and clean all it data and remaining folders but o luck all ways the same problem it says the package conflicts and even if i success to manually install it it force close when ever i want to personalize the keyboard like shotin down the auto correction or ,,,, so any help here ?
Click to expand...
Click to collapse
Flash the ROM, mount /system and use recovery's built-in file manager to delete whatever you want.
Vagelis1608 said:
Flash the ROM, mount /system and use recovery's built-in file manager to delete whatever you want.
Click to expand...
Click to collapse
yeah i know i got tired of that methode so i wanted something more efficent
berraffarouk15 said:
yeah i know i got tired of that methode so i wanted something more efficent
Click to expand...
Click to collapse
Well, the way I see it, it's more work to modify the IMG than to use the recovery's file manager.
Also, an idea I had while typing the above, you can write a small script to automate the process. You can the run that script from the recovery's built-in shell.
I can help you with this.
So my friend got an update to the huawei XT. He was already at b160. The new update is labeled as b170 which i think it could gain some hope this phone will get nougat sometime (most likely not). The update only has a device security patch. The security is from june 5 which is pretty old but i guess it's better. If someone else received the update post it here
got the notice for update at noon today - but alas, I have mine rooted so it tried to update, and then reset and is back at 160.
and yes, was really hoping beyond hope for some Nougat...
We need someone then to unroot the phone and update to b170 or at least check how to update to b170
See this post and links in it for how we updated before if the phone was already rooted (and for stock phones that can't OTA due to non-AT&T SIM) :
https://forum.xda-developers.com/showpost.php?p=73488912&postcount=1818
ensol52 said:
So my friend got an update to the huawei XT. He was already at b160. The new update is labeled as b170 which i think it could gain some hope this phone will get nougat sometime (most likely not). The update only has a device security patch. The security is from june 5 which is pretty old but i guess it's better. If someone else received the update post it here
Click to expand...
Click to collapse
Paisley Pirate said:
got the notice for update at noon today - but alas, I have mine rooted so it tried to update, and then reset and is back at 160.
and yes, was really hoping beyond hope for some Nougat...
Click to expand...
Click to collapse
divineBliss said:
See this post and links in it for how we updated before if the phone was already rooted (and for stock phones that can't OTA due to non-AT&T SIM) :
https://forum.xda-developers.com/showpost.php?p=73488912&postcount=1818
Click to expand...
Click to collapse
If anyone is able to capture the B170 update and upload it somewhere I'll try and make a TWRP flashable update
My phone doesn't see any updates yet
Could you briefly describe how to do this please? Can it be done from a phone with a locked bootloader or must the bootloader be unlocked?
clsA said:
If anyone is able to capture the B170 update and upload it somewhere I'll try and make a TWRP flashable update
My phone doesn't see any updates yet
Click to expand...
Click to collapse
divineBliss said:
Could you briefly describe how to do this please? Can it be done from a phone with a locked bootloader or must the bootloader be unlocked?
Click to expand...
Click to collapse
you would need Root and a Root explorer - file manager
you would go to settings / Software update / download the update
choose to install it later
then with the root explorer search your phone for an update.zip
I'm not sure where it's stored I'm looking for that information now
after you find the update.zip file copy it to your phones storage and upload it to your google drive (or anywhere I can download it from)
if you know the exact location the update.zip is stored you could possibly adb pull the file without having root
Update should be in /cache/fotapkg/update.zip
clsA said:
you would need Root and a Root explorer - file manager
you would go to settings / Software update / download the update
choose to install it later
then with the root explorer search your phone for an update.zip
I'm not sure where it's stored I'm looking for that information now
after you find the update.zip file copy it to your phones storage and upload it to your google drive (or anywhere I can download it from)
if you know the exact location the update.zip is stored you could possibly adb pull the file without having root
Update should be in /cache/fotapkg/update.zip
Click to expand...
Click to collapse
iirc, on huawei, it's in a folder on internal storage. shouldn't need root to grab it.
redbeard1083 said:
iirc, on huawei, it's in a folder on internal storage. shouldn't need root to grab it.
Click to expand...
Click to collapse
HwOUC/****** (numbers)
redbeard1083 said:
iirc, on huawei, it's in a folder on internal storage. shouldn't need root to grab it.
Click to expand...
Click to collapse
MT2-User said:
HwOUC/****** (numbers)
Click to expand...
Click to collapse
Thanks seems AT&T likes to put them in the path I described though
I'm pretty sure we can edit the updater script to install this from TWRP if someone captures it
clsA said:
you would need Root and a Root explorer - file manager
you would go to settings / Software update / download the update
choose to install it later
then with the root explorer search your phone for an update.zip
I'm not sure where it's stored I'm looking for that information now
after you find the update.zip file copy it to your phones storage and upload it to your google drive (or anywhere I can download it from)
if you know the exact location the update.zip is stored you could possibly adb pull the file without having root
Update should be in /cache/fotapkg/update.zip
Click to expand...
Click to collapse
working on grabbing it now.
Tried grabbing it - and messed up and got past the waiting part - it tried to update and (of course) failed. I'll give it another shot shortly.
Paisley Pirate said:
working on grabbing it now.
Tried grabbing it - and messed up and got past the waiting part - it tried to update and (of course) failed. I'll give it another shot shortly.
Click to expand...
Click to collapse
Good deal .. what was the name and path to the update file ?
you could possibly grab it with the TWRP file manager also
clsA said:
Good deal .. what was the name and path to the update file ?
you could possibly grab it with the TWRP file manager also
Click to expand...
Click to collapse
When I get it I'll get all that as well.
The ATT update note calls it B160_B170_SMR_100 , I hit continue when I tried to hit "remind me later" - but it redownloaded.
Ghost Commander shows nothing in the /cache - odd - so I don't know where it's actually sticking it. I'm searching for it both under that name above and also as update.zip and anything else I can think of (by date, since it just re-downloaded)
I'll grab and document all the info on what I got where.
File is in /cache/fotapkg/ but is named package_temp.zip
I have it out, xda won't accept the file that large, trying to figure out how to link that file only to my onedrive so you can get it without access to all my other junk (sorry)
clsA said:
Good deal .. what was the name and path to the update file ?
you could possibly grab it with the TWRP file manager also
Click to expand...
Click to collapse
https://1drv.ms/u/s!AkvKyEBneZGLjuQ44wo1pwjtdbgOCA
OneDrive link to file package_temp.zip should be 102 mb in size.
Got it using Total Commander. It seems to be better at grabbing root files than Ghost was.
Also, one other note - I modified the permissions from root root to everyone so that may need to get changed back (or not - you tell me) to be able to get it to move.
Paisley Pirate said:
https://1drv.ms/u/s!AkvKyEBneZGLjuQ44wo1pwjtdbgOCA
OneDrive link to file package_temp.zip should be 102 mb in size.
Got it using Total Commander. It seems to be better at grabbing root files than Ghost was.
Also, one other note - I modified the permissions from root root to everyone so that may need to get changed back (or not - you tell me) to be able to get it to move.
Click to expand...
Click to collapse
ok my phone doesn't see the file as an update ..where was it located ?
that is the file sent down from ATT to the phone. I have unzipped it and looked at it as well -it's 209MB unzipped. Contains the following files and drawers:
cust.new
cust.patch
cust.transfer
system.new
system.patch
system.transfer
UPDATE.APP
(drawer) META-INF
(drawer) com
(drawer) android
otacert
(drawer) google
(drawer) android
update-binary
update-script
blacklist.conf
CERT.RSA
CERT.SF
MANIFEST.MF
If you can't get the .zip to open, let me know and I'll stick it on one drive unzipped.
Paisley Pirate said:
that is the file sent down from ATT to the phone. I have unzipped it and looked at it as well -it's 209MB unzipped. Contains the following files and drawers:
If you can't get the .zip to open, let me know and I'll stick it on one drive unzipped.
Click to expand...
Click to collapse
file opens fine ..where was it located on the phone
clsA said:
file opens fine ..where was it located on the phone
Click to expand...
Click to collapse
as I said earlier - /cache/fotapkg/
Paisley Pirate said:
as I said earlier - /cache/fotapkg/
Click to expand...
Click to collapse
Well I'm sorry to report so far I have had no luck installing this thing
I have tried the dload/update.app using the dialer method and the update flashes but you have no wifi afterwords
and the phone still shows you on B160 (cust not updated / system files not patched)
I also tried with Flashify and Stock recovery and used an edited updater script in TWRP and all fail for one reason or another
Sooo the only way we will get this is if someone that has done the update
uses TWRP and creates a system.img and cust.img and uploads it somewhere for me
So I can build the B170_Full_Update.zip
Any idea how the phone installs this OTA zip file?
Is the updater-script failing because of assert statements for cust and system?
Have you had success patching cust and system using the OTA updater-script/OTA zips for the Huawei Ascend XT before? How did you end up getting the cust and system for your B160 Update zip? Probably from a TWRP of someone's updated B160, which is what we need to do for B170 now, I'm guessing?
Thanks for your efforts on this and answering my questions.
clsA said:
Well I'm sorry to report so far I have had no luck installing this thing
I have tried the dload/update.app using the dialer method and the update flashes but you have no wifi afterwords
and the phone still shows you on B160 (cust not updated / system files not patched)
I also tried with Flashify and Stock recovery and used an edited updater script in TWRP and all fail for one reason or another
Sooo the only way we will get this is if someone that has done the update
uses TWRP and creates a system.img and cust.img and uploads it somewhere for me
So I can build the B170_Full_Update.zip
Click to expand...
Click to collapse
This will be basically the copy of this thread:
https://forum.xda-developers.com/p10-plus/development/downgrade-p10-plus-oreo-to-nougat-t3724382
But it seems to me that I am not the only one who didn't find it first, so I post it here
I am not responsible if you brick your device, or just damage it!
And all credit goes to @mankindtw and @NoMercyWWE
Always make a backup of your important data, and if you rollback, you need to make a factory reset!
I only tested it with L09, but should work with L29 as well
First of all, you need a P10
2. It only works with oreo firmwares
3. Download the three zip files that are required for update, these are:
update.zip
update_data_public.zip
update_all_hw.zip
Click to expand...
Click to collapse
3/b. You can download them with Firmware Finder, or just search on xda. If you want to make a rollback to Nougat, you need rollback firmwares!
3/c. update_data_public and update_all_hw comes with a slightly different name, but rename both files to these names, otherwise the update will fail!
4. Download HWOTA8 from this topic
5. Put the three update files in HWOTA8 dir
5/b. If you want to rollback, but your files in the repack folder, and run repack.bat
6. Create a new folder on your EXTERNAL sd, named HWOTA8
7. Put your three files in it, plus copy MHA_RECOVERY8_NoCheck.img, and hwota8_update.zip
8. Now install P10 Plus twrp_oreo.img, if you havent't yet:
fastboot flash recovery_ramdisk twrp_oreo.img
Click to expand...
Click to collapse
credit to @OldDroid
9. Reboot into recovery, install hwota8_update.zip it replaces your recovery with the Mate 9 one, reboots and updates
10. Done! If you downgraded, or just encounter any problems, go back in recovery, and make a factory reset!
Can I do this without an sdcard?
dmmercado23 said:
Can I do this without an sdcard?
Click to expand...
Click to collapse
I think it is possible, but you need to rewrite hwota8_update.zip, since the links there are pointing to the external sd. But I dont know what you need to write there instead
Not sure if I did this right but now my phone shows---> Build number System 8.0.0.046(02ZP)
I had showing before---> Build number System 8.0.0.046(01BN)
I don't seem to have it right still
I also have somethong like System 8.0.0.046(02BQ) but .321(C10) installed. And there were some visible updates from the C900log Oreo, eg auto shazam disappeared from the status bar.
It's frustrating lol...my old Nexus 5 was so easy compared to this device...I know I updated with something cuz I also see January 1st security patch and other little differences...everything seems to work ok but still got no themes though...how do we get it right?
Droiduser67 said:
It's frustrating lol...my old Nexus 5 was so easy compared to this device...I know I updated with something cuz I also see January 1st security patch and other little differences...everything seems to work ok but still got no themes though...how do we get it right?
Click to expand...
Click to collapse
Here he says that you need to install su, and rename three directories, but for me themes are working even without this. As soon as I try it, these steps will be added to the tutorial though.
EDIT: I followed the steps and renamed the directories, but there was no change anywhere.
Yes just tried it myself too and no change...still no themes...had an extra folder in there on mine named "optus"...not sure but the twrp and rooting work awesome but wasn't able to make a nandroid backup to my external storage...it failed
Good day,
with what firmware (please complete naimeninie) you rolled back and what was installed by this method?
---------- Post added at 12:54 AM ---------- Previous post was at 12:51 AM ----------
dmmercado23 said:
Can I do this without an sdcard?
Click to expand...
Click to collapse
Without a SD card it is impossible, with firmware via TWRP, internal memory can be reset and then the firmware will not go to the end. Therefore, the programs are located on the SD.
urn said:
Good day,
with what firmware (please complete naimeninie) you rolled back and what was installed by this method?
Click to expand...
Click to collapse
If this question is for me, I did not test the rollback (I am fine with Oreo), but I would use C432B180. You can check the description of an update in FF to see if it's a rollback one.
Here's the solution : https://youtu.be/WYSVq1TE2kI
OREO
Can anyone help me android oreo on my Huawei P10
to install?
- OS = Ubuntu 17.10
- Huawei P10 (VTR-L09)
- Bootloader unlocked
- Device rooted
Nakedchef said:
Can anyone help me android oreo on my Huawei P10
to install?
- OS = Ubuntu 17.10
- Huawei P10 (VTR-L09)
- Bootloader unlocked
- Device rooted
Click to expand...
Click to collapse
Hey, there are many ways of doing it i would recommend https://forum.xda-developers.com/showthread.php?t=3691013
[GUIDE] Huawei P10 Debrand/Rebrand/Update for Nougat&Oreo it works great. Go for the hwota rebrand way, it work like charm for me.
Sent from my [device_name] using XDA-Developers Legacy app
Perfect! I applied the update as described in the OP, then did a factory reset and relocked the bootloader (which did another factory reset). Now, at least I can't tell anymore that the phone has been unlocked and rooted...
Hello, I have a problem in the rocovery that I flash wota8_update.zip I have E: unknown command [errno]
Updater process ended with ERROR: 9
Error installing zip file '/external_sd/HWOTA8/update.zip
dukenuken said:
Hello, I have a problem in the rocovery that I flash wota8_update.zip I have E: unknown command [errno]
Updater process ended with ERROR: 9
Error installing zip file '/external_sd/HWOTA8/update.zip
Click to expand...
Click to collapse
Which TWRP are you using?