OK so now that Roms are officially being released for our device, even with a RC TWRP. I am wondering how and if I have to flash a bootloader to my non primary partition (B) or if I can install TWRP to main partion A and then install Carbon worried before I do it would prefer to not brick phone, thanks in advance guys
ne0ns4l4m4nder said:
OK so now that Roms are officially being released for our device, even with a RC TWRP. I am wondering how and if I have to flash a bootloader to my non primary partition (B) or if I can install TWRP to main partion A and then install Carbon worried before I do it would prefer to not brick phone, thanks in advance guys
Click to expand...
Click to collapse
When you install TWRP it installs to both partitions. Both partitions should have a bootloader on them already, I would however flash a factory image first them flash twrp, rom etc. The rom will install to the opposite partitions that you are currently on.
Hi all,
Looking for expert guidance on how to flash stock roms using TWRP without full wipe. Let me set the current scenario.
1. Flash stock rom (sammobile) using ODIN with the 4 files BL-AP-CP-CSC.
2. Flash TWRP using ODIN.
3. Format Data in TWRP in order for TWRP communicate with the phone. (TRYING TO AVOID THIS STEP).
4. Flash Kernel (any from XDA).
5. Flash SuperSU
6. Reboot phone -> Clean install phone.
My question is, when the next update stock rom comes out, is there a way to flash it without having to do steps 2-5 again especially step 3? I know with some custom roms I can load onto my SD then use TWRP to flash without full wipe (e.g. OMEGA).
Does anyone have a better method of what I am doing above?
**EDIT** Just looking up Flashfire. Is this something I could use without selecting 'erase data'?
Many thanks in advance.
P
i have the same question
You can't flash stock ROMs with TWRP, you flash stock ROMs with ODIN
CSC will wipe, HOME_CSC will not
But if you're running custom, you're gonna want to wipe anyway or chances are a lot will not work, if it boots
id like to know if it is possible to flash OOS without needing to wipe the internal SD somehow?
i always flash custom roms to another custom rom without needing to wipe internal sd and thats rly cool.
but whenever i flash oos i use those fastboot zips and it wipes my internal SD.
is there some way to get OOS to boot up when i am on a custom rom ?
so question is , can i flash stock OOS while i am on a custom rom without wiping my internal sd.
if yes please guide me how to do it !
edit : So e.g i have this flashable zip of the latest oos "OnePlus6Oxygen_22_OTA_015_all_1808102118_770880.zip" can i somehow flash it within twrp and get it to boot up without wiping my internal sd ?
i had tried it before and i just couldnt get it to boot up.
It is best practise to wipe your data if your coming from another rom Otherwise you will get some error.
leondestiny said:
id like to know if it is possible to flash OOS without needing to wipe the internal SD somehow?
i always flash custom roms to another custom rom without needing to wipe internal sd and thats rly cool.
but whenever i flash oos i use those fastboot zips and it wipes my internal SD.
is there some way to get OOS to boot up when i am on a custom rom ?
so question is , can i flash stock OOS while i am on a custom rom without wiping my internal sd.
if yes please guide me how to do it !
edit : So e.g i have this flashable zip of the latest oos "OnePlus6Oxygen_22_OTA_015_all_1808102118_770880.zip" can i somehow flash it within twrp and get it to boot up without wiping my internal sd ?
i had tried it before and i just couldnt get it to boot up.
Click to expand...
Click to collapse
You can flash the full ROM in TWRP. The full steps are to flash full ROM zip, flash TWRP zip, reboot recovery, flash magisk, reboot. Data stays in tact. SD stays in tact. There is absolutely no reason to wipe sdcard and anyone who tells you is full of crap. The only reason to wipe sdcard is to decrypt your device.
---------- Post added at 03:51 AM ---------- Previous post was at 03:46 AM ----------
leondestiny said:
id like to know if it is possible to flash OOS without needing to wipe the internal SD somehow?
i always flash custom roms to another custom rom without needing to wipe internal sd and thats rly cool.
but whenever i flash oos i use those fastboot zips and it wipes my internal SD.
is there some way to get OOS to boot up when i am on a custom rom ?
so question is , can i flash stock OOS while i am on a custom rom without wiping my internal sd.
if yes please guide me how to do it !
edit : So e.g i have this flashable zip of the latest oos "OnePlus6Oxygen_22_OTA_015_all_1808102118_770880.zip" can i somehow flash it within twrp and get it to boot up without wiping my internal sd ?
i had tried it before and i just couldnt get it to boot up.
Click to expand...
Click to collapse
Also, stop using fastboot ROMs. It will wipe your data. It is meant for an emergency recovey, not for regular flashing.
mikex8593 said:
You can flash the full ROM in TWRP. The full steps are to flash full ROM zip, flash TWRP zip, reboot recovery, flash magisk, reboot. Data stays in tact. SD stays in tact. There is absolutely no reason to wipe sdcard and anyone who tells you is full of crap. The only reason to wipe sdcard is to decrypt your device.
---------- Post added at 03:51 AM ---------- Previous post was at 03:46 AM ----------
Also, stop using fastboot ROMs. It will wipe your data. It is meant for an emergency recovey, not for regular flashing.
Click to expand...
Click to collapse
thank you so much man, i initially had no idea ..
i thought for OOS stock roms id always need to wipe sd as it is a A/B device
thats why i often stayed away from oos.
but hot damn oos pie beta is so snappy and smooth..
same goes for Oreo oos stock what i find lots better is the speed /smoothness it blows custom roms out of the water..
and i even noticed that the FP sensor works a lot faster on oos.. in custom roms fp feels slow to unlock phone.
whereas on oos its instant.
i only wish stock oos had FLING.... the only reason i use custom roms at times is the usage of Fling..
leondestiny said:
thank you so much man, i initially had no idea ..
i thought for OOS stock roms id always need to wipe sd as it is a A/B device
thats why i often stayed away from oos.
but hot damn oos pie beta is so snappy and smooth..
same goes for Oreo oos stock what i find lots better is the speed /smoothness it blows custom roms out of the water..
and i even noticed that the FP sensor works a lot faster on oos.. in custom roms fp feels slow to unlock phone.
whereas on oos its instant.
i only wish stock oos had FLING.... the only reason i use custom roms at times is the usage of Fling..
Click to expand...
Click to collapse
The a/b makes ota updates easier. While booted in system a, an OTA will flash to b while the OS is still running and after a reboot, it will boot to b, and vice versa. The reason for a reboot recovery after flashing stock oos zip and TWRP zip is to get TWRP to flash on the correct slot. You can change it manually in TWRP, but that method requires you to keep track of your slot. A simple reboot of recovery will put it on the correct slot to flash magisk. Without flashing magisk, bootloop will happen.
---------- Post added at 04:04 PM ---------- Previous post was at 03:57 PM ----------
leondestiny said:
thank you so much man, i initially had no idea ..
i thought for OOS stock roms id always need to wipe sd as it is a A/B device
thats why i often stayed away from oos.
but hot damn oos pie beta is so snappy and smooth..
same goes for Oreo oos stock what i find lots better is the speed /smoothness it blows custom roms out of the water..
and i even noticed that the FP sensor works a lot faster on oos.. in custom roms fp feels slow to unlock phone.
whereas on oos its instant.
i only wish stock oos had FLING.... the only reason i use custom roms at times is the usage of Fling..
Click to expand...
Click to collapse
I also forgot! Delete your lock screen before flashing another ROM. That is why your sdcard is inaccessible. If you delete it before going to TWRP, it will automatically decrypt since the password would be technically nothing.
Hello,
I am running PixysOS rom on my Honor 6X (BLN-AL20) since some months and I am actually satisfied of the stability and usability of the Rom.
Actually I can't convince the device to use the installed as card to store pictures, videos etc.
The SD card is recognised and listed under memory but the system is not using it.
Is there any workaround to fix this problem?
Thanks,
Andrea.
Sent from my BLN-AL20 using Tapatalk
Anybody out there?
Sent from my BLN-AL20 using Tapatalk
Sephiroth79 said:
Anybody out there?
Sent from my BLN-AL20 using Tapatalk
Click to expand...
Click to collapse
for me my internal storage is not detected. only sd card is main storage. seems like its a bug and never gonna fixed. there is no perfect android 9 os out there. so better go to emui 8 and use cyclox kernel.
Sephiroth79 said:
Hello,
I am running PixysOS rom on my Honor 6X (BLN-AL20) since some months and I am actually satisfied of the stability and usability of the Rom.
Actually I can't convince the device to use the installed as card to store pictures, videos etc.
The SD card is recognised and listed under memory but the system is not using it.
Is there any workaround to fix this problem?
Thanks,
Andrea.
Click to expand...
Click to collapse
By what I read in the thread of DotOS, that's a bug that should had be fixed in latest builds... Are you using latest version or not?
Anyway every Pie ROM/GSI I tried seems to read microSD, eject it and re-read once again immediately after booting to OS, on every single boot. Then, there are systems that keep reading the microSD (as AEX, Descendant...) and allows modifications, reading files, basically everything you should be able to do with a microSD, and systems that just keep it ejected (like DotOS did on old builds). Saw other users reporting that on the thread. Look for "microSD" in DotOS thread to read latest comments about, there you could find a solution. By how things sound at the moment, my only advice is to move on another system.
Thanks for your reply. Could you suggest me a proper and stable rom?
Sephiroth79 said:
Thanks for your reply. Could you suggest me a proper and stable rom?
Click to expand...
Click to collapse
Nothing hard to do man. We use to thank others with the appropriate button, for next times.
Anyway since that we're not talking 'bout different devices but we share the same phone, i feel to strongly recommend ya the Descendant GSI project by Dil3mm4.. It's a fork of Phh AOSP project but with sone very good extras. I never used a system smooth like this one, really impressive. It has a decent amount of customizations options (not at levels like RROS in example, but too much is too much IMHO), great battery management, fluid transitions and great compatibility with Huawei devices (it's a GSI, but the dev has a P8 Lite at the moment, so he knows how to make things working on Huawei).
Give it a shot, you can always go back to stock with HuRUpdater in just 5 minutes. And in case you'd like to try more, remember to take a look into Treble section here on XDA. Every arm64 a-only GSI is good to be flashed on our device, but before flashing just look if other users owning a Huawei device have already tried it or not. I say this simply because many GSIs are actually not working thanks to our vendor compatibility, so make things without hurry and nothing can go wrong
Used appropriate "thanks button" this time...eheh
Any tutorial on how to install the Descendant GSI rom starting from PixysOs with Askuccio's TWRP?
Sephiroth79 said:
Used appropriate "thanks button" this time...eheh
Any tutorial on how to install the Descendant GSI rom starting from PixysOs with Askuccio's TWRP?
Click to expand...
Click to collapse
Well there isn't a dedicated tutorial for every ROM/GSI you're starting from, overall because a clean flash is strongly recommended (especially when you switch from a ROM to a GSI) - you can dirty flash Descendant updates or other GSIs based on phhusson trees without problems, but in this case you've already modified your device kernel and other stuff with a custom ROM, so it's better to start from scratch in way to avoid useless wastes of time running to repairs with hurry.
The faster and safest way to do this is:
1) restore stock OS with HuRUpdater and let it boot (i saw that you already own Askuccio's TWRP, i always had to use Elemental TWRP from KingOfMezi in way to use HuRU without errors, but apart this Askuccio's TWRP works for flashing everything you'd need);
2) following steps listed in Descendant OP, flash the system image through fastboot or through TWRP, then reboot to TWRP once again and wipe ONLY /cache and /dalvikART partitions;
3) factory reset through stock recovery and let the system boot (yeah, you'll have to reflash stock recovery once again before reflashing TWRP - again.
4) flash all the rest you'd like to flash (GApps, Magisk, ecc.)
By default, /data partition remains encrypted after performing factory reset with stock recovery, and so with TWRP you won't be able to perform full backups, but you can also choose to run with /data decrypted. The method isn't supported by the developer, but works like a charm (personally tested about 3 versions of the GSI ago, worked). You just have to flash "disable dm verity" script during the process, but you can know more by reading about it here.
Happy flashing
RedSkull23 said:
Well there isn't a dedicated tutorial for every ROM/GSI you're starting from, overall because a clean flash is strongly recommended (especially when you switch from a ROM to a GSI) - you can dirty flash Descendant updates or other GSIs based on phhusson trees without problems, but in this case you've already modified your device kernel and other stuff with a custom ROM, so it's better to start from scratch in way to avoid useless wastes of time running to repairs with hurry.
The faster and safest way to do this is:
1) restore stock OS with HuRUpdater and let it boot (i saw that you already own Askuccio's TWRP, i always had to use Elemental TWRP from KingOfMezi in way to use HuRU without errors, but apart this Askuccio's TWRP works for flashing everything you'd need);
2) following steps listed in Descendant OP, flash the system image through fastboot or through TWRP, then reboot to TWRP once again and wipe ONLY /cache and /dalvikART partitions;
3) factory reset through stock recovery and let the system boot (yeah, you'll have to reflash stock recovery once again before reflashing TWRP - again.
4) flash all the rest you'd like to flash (GApps, Magisk, ecc.)
By default, /data partition remains encrypted after performing factory reset with stock recovery, and so with TWRP you won't be able to perform full backups, but you can also choose to run with /data decrypted. The method isn't supported by the developer, but works like a charm (personally tested about 3 versions of the GSI ago, worked). You just have to flash "disable dm verity" script during the process, but you can know more by reading about it here.
Happy flashing
Click to expand...
Click to collapse
Point 1: I have to download stock fw using Huawei firmware finder and I have to use Askuccio's TWRP to flash HuRupdater on the device. Do I have to choose a custom recovery or I have to let HuRupdater flash stock recovery too?
Point 2: you are saying I have to wipe cache/dalviw partitions using TWRP so I have to flash TWRP after flashing and booting stock fw?
Sephiroth79 said:
Point 1: I have to download stock fw using Huawei firmware finder and I have to use Askuccio's TWRP to flash HuRupdater on the device. Do I have to choose a custom recovery or I have to let HuRupdater flash stock recovery too?
Point 2: you are saying I have to wipe cache/dalviw partitions using TWRP so I have to flash TWRP after flashing and booting stock fw?
Click to expand...
Click to collapse
To me flashing HuRU with Askuccio TWRP never worked, as said above, so i'd suggest you to look for ElementalTWRP in way to have a custom recovery that can flash HuRU with no problems. Secondarily, in way to avoid confusion, just start from stock and do a fastboot flash of Descendant, reboot to OS and let it boot. Once set, flash TWRP and flash GApps, then wipe just /cache and /dalvik and reboot one last time. Then you can do anything you want.
RedSkull23 said:
To me flashing HuRU with Askuccio TWRP never worked, as said above, so i'd suggest you to look for ElementalTWRP in way to have a custom recovery that can flash HuRU with no problems. Secondarily, in way to avoid confusion, just start from stock and do a fastboot flash of Descendant, reboot to OS and let it boot. Once set, flash TWRP and flash GApps, then wipe just /cache and /dalvik and reboot one last time. Then you can do anything you want.
Click to expand...
Click to collapse
Ok, I'll put elemental TWRP recovery in the same directory in order to let HuRU flash it together with the stock firmware.
Edit: can't find elemental twrp download link
Sephiroth79 said:
Ok, I'll put elemental TWRP recovery in the same directory in order to let HuRU flash it together with the stock firmware.
Edit: can't find elemental twrp download link
Click to expand...
Click to collapse
Good, i usually do that later just in case the system prompts to factory reset before booting, but it's up to you. Here's the link anyway https://mega.nz/#!a81EDZAR!2-9yPFh3reghkGcfSl3nRIJhHGkP8fqDsgUG66ewjkk
Using fw finder I downloaded the fw named: BLN-AL30C00B541 (8.0.0.541) FULLOTA-MF 2018.12.27
Clicking on download give me some choices:
- update.zip (1.74 GB)
- BLN-Al20_all_cn/update_full_BLN-AL20_all_cn.zip (643 MB)
Already downloaded both of them and can't find any of the files required from HurUpdater to run. Do I have to use an extractor?
EditOne: used Huawei Update Extractor gives an error on the update.app extracted from the update.zip archive and works on the same file extracted from BLN-Al20_all_cn/update_full_BLN-AL20_all_cn.zip
Edit2: just realized I don't need to extract anything but still can't find update_data_public and update_all_hw files
That is because it's Chinese build and as you just noticed some update packages are assembled in a slightly different manner, so some package misses one if not two useful zips. Would you mind to switch to India variant? Nothing changes in performance nor in features, plus if you'd only use the firmware as a base to get to other ROMs/GSIs, it really doesn't matter (but i can offer better assistance since that i'm more experienced with India variant other than China). FYI in this thread https://forum.xda-developers.com/honor-6x/how-to/french-language-t3938592/ i've already guided an user to obtain India variant, but it's really simple:
in TEAM MT site (google for "team mt online firmware database", the first result you get is what you need), look for build "BLN-L22HNC675CUSTC675D1B510" - you'll obtain 4 results. Download the package dated 2018.07.19, it is the better one. From here you just have to follow instructions in HwOTA thread, renaming the three packages as suggested in OP and choosing to debrand during the process to BLN-L22 region/variant (don't remember if it happens anyway since that the firmware is India variant but it's a thing that doesn't give hassles).
I tend to mess things up when flashing new ROMs on my Oneplus6. And I usually end up using the MSMdownloadtool to 'fix my phone' again.
* Does MSMdownloadtool install OOS on both slots?
* What do you advise to do before installing a custom (v10) rom?
* I tried doing a fastboot OOS install by mauronofrio, it didnt work. I got into bootloops after running/finishing the flash all bat file. So I used MSMdownloadtool again. I wondered if the fastboot OOS installer guide by mauronofrio installs OOS on both slots??
* Does the fastboot OOS installer do the same thing as MSMdownloadtool?
* In a lot of guides for clean install custom rom I read as first step: wipe system/data. But then I wonder why do you have to install the correct OOS version first, THEN wipe it, and then install custom ROM. Does an OOS installation leave some hidden (essential) files/partitions behind or something?
* Do you guys switch slots in twrp / or do you reboot to switch slots / or do you use the fastboot --set-active a/b command?
* Why does gapps only have to be installed on 1 slot and not on both?
* Why don't custom ROMS install themselves on both slots straight away, like when you flash the twrp installer zip.. ?
Im currently running carbonROMv8 ROM, its running fine so Im not looking to change yet. But im sure im gonna have to use msmdowndtool again when I wanna try out some other ROM in the future. I dont really feel like im having any control off the flashing process. It either works or it doesnt and when it doesnt I cant explain why..
dumbl3 said:
I tend to mess things up when flashing new ROMs on my Oneplus6. And I usually end up using the MSMdownloadtool to 'fix my phone' again.
* Does MSMdownloadtool install OOS on both slots?
* What do you advise to do before installing a custom (v10) rom?
* I tried doing a fastboot OOS install by mauronofrio, it didnt work. I got into bootloops after running/finishing the flash all bat file. So I used MSMdownloadtool again. I wondered if the fastboot OOS installer guide by mauronofrio installs OOS on both slots??
* Does the fastboot OOS installer do the same thing as MSMdownloadtool?
* In a lot of guides for clean install custom rom I read as first step: wipe system/data. But then I wonder why do you have to install the correct OOS version first, THEN wipe it, and then install custom ROM. Does an OOS installation leave some hidden (essential) files/partitions behind or something?
* Do you guys switch slots in twrp / or do you reboot to switch slots / or do you use the fastboot --set-active a/b command?
* Why does gapps only have to be installed on 1 slot and not on both?
* Why don't custom ROMS install themselves on both slots straight away, like when you flash the twrp installer zip.. ?
Im currently running carbonROMv8 ROM, its running fine so Im not looking to change yet. But im sure im gonna have to use msmdowndtool again when I wanna try out some other ROM in the future. I dont really feel like im having any control off the flashing process. It either works or it doesnt and when it doesnt I cant explain why..
Click to expand...
Click to collapse
Yoo.. So Many Questions. Will try to explain in easiest way..
1. Yes. It Does Flash OOS in Both Slot via Qualcomm Download Mode which is mainly for Manufactures to restore Device..
2. Let me clear that Most people's who face issue in booting custom ROM have their data encrypted by previous or stock ROM.
Here is Link Thread to know how to decrypt your device..
https://forum.xda-developers.com/oneplus-6/how-to/tutorial-decrypt-flash-rom-pie-oreo-roms-t3838643
My own Instructions to Flash Custom ROM (Strictly for Decrypted Device):-
Boot Into Recovery
Wipe Cache, Data & System
Flash Latest Stable/Beta OOS10 & Recovery
Reboot Into Recovery(Ignore No OS Installed Warning)
Flash Latest Stable/Beta OOS10 & Recovery again
Reboot Into Recovery
Now flash Custom ROM + Recovery(If Not Included)
Reboot Into Recovery
Flash Gapps(If not included in ROM), Magisk & No-Verity zip(to keep Device dencrypted)
Reboot & Done
For Installing Update on Same Custom ROM :-
Download the Update
Reboot Into Recovery
Flash Update ZIP & Recovery
Reboot Into Recovery
Flash Gapps(If not included in ROM), Magisk & No-Verity zip(to keep Device dencrypted)
Reboot & Done
3. Fastboot Don't always work if You try to Upgrade/Downgrade Android Version as it won't flash Critical Partitions.. Meanwhile MSMDownload tool Use Download mode which is more powerful.
4. Nope. Both are Different AS both use different mode to flash ROM.
5. Clean install required while flashing new custom ROM because Not All ROM uses Same Base. Some uses Stable OOS or some uses Beta OOS... Now, your answer is in these two build Types...
In my Opinion, Custom ROM have nothing to do with your System partition but it most like to related to Vendor Partition... Both Stable & Beta OOS Have little difference in Vendor partition data..
When any dev Build Any ROM, he uses any one of those Build as base for which he tweak/fix bugs.. That's why always Use Dev specified OOS build for avoid Bootloop/bugs..
6. I prefer last option as it's more reliable..
7. It's like when you clean install any ROM.. When you install Any ZIP, It get installed in an Inactive Slot which make those ZIP data Allowed to use in Active slot..
But when you update ROM for 1st time, You install Gapps as well.. So i don't think you need to Install Gapps on 2nd Update as it already installed in both slots.
1st time when Clean installed & 2nd time when Updated 1st time...
8. It's Because how A/B Partition works... Any zip you flash get installed in inactive slot & this applies to both Stock OOS & Custom ROM...
That's why we have to flash OOS twice before flashing any custom ROM.. Which confirms you will have same Vendor partition regardless to your current slot so when you flash custom ROM it will get booted anyways even after an update..
Hope that's helpful.. Any question or help, you can DM or reply here..
Thanks for your reply. It clears a few things up I think. I got a few follow up questions.
I don't really feel comfortable walking around with a decrypted phone. I have already been pick-pocketed once and also lost two smartphones. I would say the chances are likely that also my OP6 is gonna get lost at some point. Having it decrypted would leave it very vulnerable for people trying to access my files.
* So lets say I decrypt my phone. Is it possible then to encrypt the phone again after I have flashed a new ROM (for example LineageOS 17.1)?
dumbl3 said:
Thanks for your reply. It clears a few things up I think. I got a few follow up questions.
I don't really feel comfortable walking around with a decrypted phone. I have already been pick-pocketed once and also lost two smartphones. I would say the chances are likely that also my OP6 is gonna get lost at some point. Having it decrypted would leave it very vulnerable for people trying to access my files.
* So lets say I decrypt my phone. Is it possible then to encrypt the phone again after I have flashed a new ROM (for example LineageOS 17.1)?
Click to expand...
Click to collapse
Well, In my Opinion Every Device is Vulnerable to Hackers.. Doesn't matter if it's bootloader is Locked or Unlocked...
Your device is more Vulnerable at the time you unlocked bootloader because after that you can execute advanced commands with fastboot.....
If your device have pin/pattern, Thief gone reset your device anyway to reset pass.. Eventually your data get wiped as well....
Well, you can encrypt your data but you might face issue while migrating to other ROM if you face any bug + decrypting your encrypted device again is time taking process if you have alot of data..
I mean there is difference between someone being able to reset/delete my data than someone being able to read my data. As far as I know a thief cannot just read my data after he has stolen my device which is encrypted with unlocked bootloader. Sure, he can connect it to his computer and fastboot delete my sh!t but I don't care I got backups of my most important data anyway, as long as he/she cannot just read my device data its fine by me. But how would I encrypt my device again after I installed, lets say, LineageOS 17.1?
dumbl3 said:
I mean there is difference between someone being able to reset/delete my data than someone being able to read my data. As far as I know a thief cannot just read my data after he has stolen my device which is encrypted with unlocked bootloader. Sure, he can connect it to his computer and fastboot delete my sh!t but I don't care I got backups of my most important data anyway, as long as he/she cannot just read my device data its fine by me. But how would I encrypt my device again after I installed, lets say, LineageOS 17.1?
Click to expand...
Click to collapse
you can.. But do it only if you gone use it for long term....
Not fine to waste your whole day transfer your date from mobile to PC then PC to mobile..