Hello,
I'm new here. And I think I've learn a lot of things reading through all the useful posts.
I have a moto g 3rd gen. XT1541 2GB reteu ( really its my wife's phone), currently running its original stock 5.1.1.
I want to try some custom ROM based on 7.1, but my wife wants to be able to go back to the actual state, in case she don't like the new OS (worst battery life, mainly). So I think about 2 options:
Option 1:
- Factory reset
- Unlock bootloader
- Boot twrp with fastboot (not install at this time)
- Perform a complete nandroid backup of the system to SD.
- Install twrp.
- Then install Lineage OS 14.1
So in this case: Could be possible to restore the nandroid backup later? Will it be safe? remember its a nandroid backup of LP 5.1.1
Option 2:
- Factory reset
- Install twrp with fastboot
- install Lineage OS 14.1
In case of need... Could I go back to 5.1.1 by installing a factory image with fastboot? Any risk?
Thank you in advance.
angel6700 said:
Hello,
I'm new here. And I think I've learn a lot of things reading through all the useful posts.
I have a moto g 3rd gen. XT1541 2GB reteu ( really its my wife's phone), currently running its original stock 5.1.1.
I want to try some custom ROM based on 7.1, but my wife wants to be able to go back to the actual state, in case she don't like the new OS (worst battery life, mainly). So I think about 2 options:
Option 1:
- Factory reset
- Unlock bootloader
- Boot twrp with fastboot (not install at this time)
- Perform a complete nandroid backup of the system to SD.
- Install twrp.
- Then install Lineage OS 14.1
So in this case: Could be possible to restore the nandroid backup later? Will it be safe? remember its a nandroid backup of LP 5.1.1
Option 2:
- Factory reset
- Install twrp with fastboot
- install Lineage OS 14.1
In case of need... Could I go back to 5.1.1 by installing a factory image with fastboot? Any risk?
Thank you in advance.
Click to expand...
Click to collapse
Hi,
Both the options you mentioned should work without any problems.
For Option 1)
I'd really recommend this option. Its the safe way to go. Also you should have no problem restoring LP 5.1.1 backup after installing any ROM.
For Option 2)
Yes it will work without any problems too, but installing factory image via fastboot is a tedious process.
So just to make things easier go with option 1.
Thank-you for your help.
So I'll say with option 1, and keep the backup in a safe place, just in case...
Anyway, first thing is to manually copy all important data, before unlocking the bootloader. I think the process deletes everything.
Now, is time to play
Thanks again.
To be on the safe side when you do the backup in twrp select also the system image option. It makes a bigger backup but for stock rom backup I always do it. For custom rom it's not needed. Just my humble opinion.
Cheers!
Related
MIUI 8 GLOBAL BETA 6.8.11 reported for DOOGEE DG700
Requirements:
Stock 4.4 KK firmware installed on the phone
Custom recovery
A working brain ... and some patience!
Credits:
All credits go to team ARGN for crossporting MTK6592 to MTK6582 and updating their ported rom here
Me for porting from Gionee M2 to DG700
Feautures:
Cross ported from the latest MIUI8 xiaomi.eu release for Redmi Note. (credits go to team ARGN)
DG700 rom uses as base TEAM ARGN crossports from MTK6592 to MTK6582.
Working: dual sim 3g (using dual sim control apk), wifi, bluetooth, gps, camara, sdcard, and everything else.
No chiness apps
All gapps preinstalled as system apps.
Enhanced camera pics quality (must be enabled in camera settings).
Repartitioned internal storage to 6G, custom carliv touch recovery (using stock kk firmware in the downloads at the end of the post).
Xposed and xposed modules working.
Many more ...
Known bugs:
Theme apk SOMETIMES FC's, but themes are working.
NVRAMWARNING wifi bug, easilly fixable (search xda or google for fix), wifi works just ok even with the NVRAMWARINING bug.
Battery capacity will be shown only at 3100mah, even so battery life is far more superior than the actual R25 lollipop firmware for DG700. (I get about 3 days with wifi / data on, moderate usage of the phone on the current MIUI8 based on kk rom)
Custom recovery CTR touch NOT WORKING. USE HARDWARE KEYS!
Installing
Download DG700_MIUI8_beta_global_6.8.11.zip (link at the end of the post), copy it on the sd card.
Download Stock R14 firmware linked at the end of the post (the attached build INCLUDES CTR custom recovery and repartitioned internal storage to 6G), unzip the archive and flash it with sp flash tools.
After flashing R14 go directly to recovery, DO NOT BOOT into android.
Once in recovery take the following steps:
1. Wipe and Format Options > Clean to Install a new rom ... wait for the recovery to wipe system, data, go back to the main menu
2. Install zip > Choose zip from storage/sdcard1 > browse for DG700_MIUI8_beta_global_6.8.11.zip and select it, install and wait for the installer to finish, go back to the main menu
3. Reboot system now, when asked to install su / root phone, select NO! (if you want to root the phone later you can install Chainfire SU binaries from the recovery, and than SU app from the market)
Wait for the rom to load, for the first time it will take some time ... be patient.
If you are not on stock KK THIS WILL NOT WORK! After flashing R14 firmware you will loose the IMEI's. Follow the guide frome here to restore the IMEI's:IMEI REPAIR / RESTORE /BACKUP
Customizing ... well ... the sky is the limit ... I use Plak to remove titles from the hotseat / launcher icons (as you cans see in the attached screenshots) and MIUI Tweaks for status bar (notification bar) customization ...
IF ALL GOES WELL or IF YOU ENCOUNTER ANY PROBELMS PLEASE POST BACK!
If this post helped you hit the Thanks button!
ENJOY!
Downloads:
DG700 R14 Stock KK with CTR and repartitioned internal memory: DOWNLOAD LINK
DG700 MIUI8 xiaomi.eu global beta v6.8.11: DOWNLOAD LINK
so if my doogee is currently on lolipop, i need to first get it to stock KitKat before i can follow the instructions on your post?
so how do i do that? could you please send a link? thnks!
simchaleh said:
so if my doogee is currently on lolipop, i need to first get it to stock KitKat before i can follow the instructions on your post?
so how do i do that? could you please send a link? thnks!
Click to expand...
Click to collapse
You will need to use spflash tool and the stock rom attached in my first post in order to install (flash) kitkat. Search google or xda for a tutorial on how to use spflash tool.
Have in mind that this is an advanced process and many things might go wrong if you don't have experience with flashing the whole android on your phone.
I think that at some point even doogee had a tutorial at their site showing how to upgrade from kitkat to lollipop (see here: http://www.doogee.cc/download.php?ProId=41). It is the same process only you need to format the whole phone before flashing and instead of flashing lp use kk images and scatter attached by me. If you're not sure what you are doing do some research first ... there are lots of great tutorials on the net for spflashtools and mtk6582 phone. Also have in mind that for some newer DG700 models it is impossible to flash kitkat because of some drivers issues ... or so it was stated on the 4pda.ru dg700 thread.
Hey @tvladan,
thanks a lot for this thread!!!
My experience and feedback:
All went smooth until I booted with the Miui installed. Because the IMEI problem I was not able to log into android (use than play store) nor Miui and the system would not let me go any further until I could by magic.
IMEI
I could not log in (system need unique phone ID such IMEI) so I needed to get the apks and move/save on the sdcard to be installed.
I could not restore the IMEI with MTK which was suggesting a reset in order to fix it and I had no clue how to reset (not reboot).
Mobile uncle. I made a IMEI backup but even if the app was restoring without problem, it really did not do anything also after rebooting
Chameleon: the only app that did something although not permanent. I'm working to fix it
Nvram error: fixed with no issue as on this thread
MIUI: it is definitively a nice designed UI although the one I personally do not prefer. It is flexible if you want to do things as developers allow you which is on my opinion sometime to strick if we consider we all are looking for a rooted phone and than we are bond by the UI. For sure there are some features that are useful as were some I really appreciate from the stock ROM. One example: I agree that moving app to the SD card might slow down the system and use more battery but now that I've achieved a 6GB rom I'm using all of it for the app and just marginal cache/data will be saved on the SD....
@tvladan: If I'd like to try only the KK rom without the MIUI and avoid the IMEI problem, are the following steps correct:
1) restore LP with TWRP
2) install stock R14 KK
3) install your KK with 6gb partition
If this is correct, in all this writing and overwriting, is there any chance I'll flash the recovery TWRP?
In case it will happen, can I use the one as by this thread by @NaturalBornCamper
thanks and enjoy your DG700
ciao
gipsea said:
Hey @tvladan,
thanks a lot for this thread!!!
If I'd like to try only the KK rom without the MIUI and avoid the IMEI problem, are the following steps correct:
1) restore LP with TWRP
2) install stock R14 KK
3) install your KK with 6gb partition
If this is correct, in all this writing and overwriting, is there any chance I'll flash the recovery TWRP?
In case it will happen, can I use the one as by this thread by @NaturalBornCamper
thanks and enjoy your DG700
ciao
Click to expand...
Click to collapse
Yes you can install stock kk but not using the steps you posted. You can not restore it via twrp, you must flash it with spflash tools (using format mode, kk or lp, as you please) BUT you will still loose imei's. This happens because of the format method used by spflash tools, in most MTK phones, that erases all the internal partitions of the phone.
Regarding LP, there is a latest firmware (official) by dooge - R25 that has the internal memory repartitioned to 5.5Gb. I would recommand installing that and than rooting (if needed) via twrp using chainfire binaries. You can download the R25 from here: https://docs.google.com/uc?id=0B_UWiyCZx5s1Z2xxZTRYTE9OcGc&export=download. The thread by NaturalBornCamper is old, deprecated and useless now. That was in the beggining when we did not have a custom recovery or the knowledge on how to root / repartition the DG700 phone.
Regarding lost IMEIS i RECOMMAND the MAUI 3G METHOD to restore them for our phone presented here: http://forum.xda-developers.com/unite-2/general/guide-repair-imei-invalid-micromax-t3048984 It needs a little more work, but once the correct drivers are installed it should work no matter what! (It also has a video tutorial, with some patience and little knowledge you should succeed in properly restoring the IMEI's). In your situation, whatever rom / firmware you will flash now using spflsh tools it will NOT restore the imei's because the nvram was formated.
Good Luck!
LE: To sum it up, to have the latest LP, repartitioned and rooted you will have to follow these steps (and have some knowledge on how to use spflash tools)
1. Flash R25 using spflashtools in format mode.
2. Start up the phone, wait to boot into android (just wait, it will take a while because it will encrypt the data partition). Setup the phone, fix imei's using maui 3g tool methond posted above. At this point you should have a "re-partitioned", unrooted, on stock recovery phone with the proper IMEI's
3. Download the latest chainfire su binaries from here: https://download.chainfire.eu/696/supersu/ and copy the zip to sd card. (UPDATE-supersu-v...... link)
4. Flash TWRP using spflashtools in download mode.
5. DO NOT START ANDROID, Reboot the phone in recovery mode witch should be now twrp that you just flashed before. If you start up android it is possible and very likely that it will restore the stock recovery, but if restarting in twrp first it will override the restoring of the stock recovery forever.
6. Flash the update-supersu-file via twrp
7. Reboot the phone in andorid (if asked by twrp to root, select NO), go to the market, instal chainfire supersu apk, and voila you are now on the latest LP (witch is repartitioned), custom twrp recovery and rooted.
if you need the link to twrp only pls post back I'll upload it somewhere for you!
ciao @tvladan,
thanks for your reply.
Quick question: as I did back up the LP with TWRP including NVRAM, if I restore it will it be permanent? I read the thread you suggested about IMEI/NVRAM but if this work it is a straight shot
I'd like to try the R25 LP and KK. Did you tried both? KK apparently was better compared to the LP up to R24.
Thanks
gipsea said:
ciao @tvladan,
thanks for your reply.
Quick question: as I did back up the LP with TWRP including NVRAM, if I restore it will it be permanent? I read the thread you suggested about IMEI/NVRAM but if this work it is a straight shot
I'd like to try the R25 LP and KK. Did you tried both? KK apparently was better compared to the LP up to R24.
Thanks
Click to expand...
Click to collapse
LP moves a little slower than kk. Nothing to worry about. Regarding battery life there is a 12 -24 hours difference from lp to kk, kk lasting longer. If you install xposed framework on lp it will move a LOT slower. If you do not need xposed I recommend R25 LP. Also I have no knowledge of TWRP being able to backup nvarm. I might be wrong. All you can do is try different methods until you succeed. It is a devious and annoying process but when you get it right you'll be satisfied. Also after lots of hours fking around with this phone I really stand by the steps posted in my previous post as to how to repartition / root / repair imeis the fastest way!
simchaleh said:
so if my doogee is currently on lolipop, i need to first get it to stock KitKat before i can follow the instructions on your post?
so how do i do that? could you please send a link? thnks!
Click to expand...
Click to collapse
tvladan said:
Yes you can install stock kk but not using the steps you posted. You can not restore it via twrp, you must flash it with spflash tools (using format mode, kk or lp, as you please) BUT you will still loose imei's. This happens because of the format method used by spflash tools, in most MTK phones, that erases all the internal partitions of the phone.
Regarding LP, there is a latest firmware (official) by dooge - R25 that has the internal memory repartitioned to 5.5Gb. I would recommand installing that and than rooting (if needed) via twrp using chainfire binaries. You can download the R25 from here: https://docs.google.com/uc?id=0B_UWiyCZx5s1Z2xxZTRYTE9OcGc&export=download. The thread by NaturalBornCamper is old, deprecated and useless now. That was in the beggining when we did not have a custom recovery or the knowledge on how to root / repartition the DG700 phone.
Regarding lost IMEIS i RECOMMAND the MAUI 3G METHOD to restore them for our phone presented here: http://forum.xda-developers.com/unite-2/general/guide-repair-imei-invalid-micromax-t3048984 It needs a little more work, but once the correct drivers are installed it should work no matter what! (It also has a video tutorial, with some patience and little knowledge you should succeed in properly restoring the IMEI's). In your situation, whatever rom / firmware you will flash now using spflsh tools it will NOT restore the imei's because the nvram was formated.
Good Luck!
LE: To sum it up, to have the latest LP, repartitioned and rooted you will have to follow these steps (and have some knowledge on how to use spflash tools)
1. Flash R25 using spflashtools in format mode.
2. Start up the phone, wait to boot into android (just wait, it will take a while because it will encrypt the data partition). Setup the phone, fix imei's using maui 3g tool methond posted above. At this point you should have a "re-partitioned", unrooted, on stock recovery phone with the proper IMEI's
3. Download the latest chainfire su binaries from here: https://download.chainfire.eu/696/supersu/ and copy the zip to sd card. (UPDATE-supersu-v...... link)
4. Flash TWRP using spflashtools in download mode.
5. DO NOT START ANDROID, Reboot the phone in recovery mode witch should be now twrp that you just flashed before. If you start up android it is possible and very likely that it will restore the stock recovery, but if restarting in twrp first it will override the restoring of the stock recovery forever.
6. Flash the update-supersu-file via twrp
7. Reboot the phone in andorid (if asked by twrp to root, select NO), go to the market, instal chainfire supersu apk, and voila you are now on the latest LP (witch is repartitioned), custom twrp recovery and rooted.
if you need the link to twrp only pls post back I'll upload it somewhere for you!
Click to expand...
Click to collapse
About #4), flash TWRP. I have used the one posted by @NaturalBornCamper on his thread on step 11
If the TWRP for KK is different please post
I'm working on R25
Next fun step, R14
Thanks
It is the same twrp, works on kk and lp. You have the right one. For r25 it does not matter on what you are now, the spflashtool needs to format all the phone in order to install r25.
Thanks and good to know.
Now I'm getting curious about NVRAM/IMEI and TWRP...
TWRP can make backup of NVRAM and I did before installing the KK with MIUI8.
If I understood correctly IMEI information is stored in the NVRAM so, theoretically, if I restore the first back up of the NVRAM I should restore also the IMEI?!?!?!
how can I check the difference between a temporary IMEI installation like with chamelephone from a permanent solution?
ciao
gipsea said:
Thanks and good to know.
Now I'm getting curious about NVRAM/IMEI and TWRP...
TWRP can make backup of NVRAM and I did before installing the KK with MIUI8.
If I understood correctly IMEI information is stored in the NVRAM so, theoretically, if I restore the first back up of the NVRAM I should restore also the IMEI?!?!?!
how can I check the difference between a temporary IMEI installation like with chamelephone from a permanent solution?
ciao
Click to expand...
Click to collapse
All you can do is try to restore via twrp ... temp imei restore should be erased at reboot.
Thank you for this very Good rom. it's better than the stock KitKat
Do you have any resurrection remix for this device or any marshmallow based on KitKat kernel..please
Unfortunately no, i moved to a mi5 last year and placed my old doogee in a drawer for safe keeping. This is the last port i made.
tvladan said:
Unfortunately no, i moved to a mi5 last year and placed my old doogee in a drawer for safe keeping. This is the last port i made.
Click to expand...
Click to collapse
Sorry for bothering you again . I just wanted to know if it is possible to restore lollipopTWRP backup without flashing stock lollipop with flashing tool . When I'm on KitKat..is it possible to just flash The kernel .
Thank you
zidane01 said:
Sorry for bothering you again . I just wanted to know if it is possible to restore lollipopTWRP backup without flashing stock lollipop with flashing tool . When I'm on KitKat..is it possible to just flash The kernel .
Thank you
Click to expand...
Click to collapse
Unfortunately it is not possible to restore lolipop over kitkat or opposite because of the big differences in partition tables used by each of them. So the only way to restore a nandroid image is to flash stock with spflash tools with format, install the custom recovery and than restore the recovery backup.
tvladan said:
Unfortunately it is not possible to restore lolipop over kitkat or opposite because of the big differences in partition tables used by each of them. So the only way to restore a nandroid image is to flash stock with spflash tools with format, install the custom recovery and than restore the recovery backup.
Click to expand...
Click to collapse
Ok thank you...then I better stick with kitkat even do some applications stopped supporting it.
You can move to doogee s60, it's on sale on gearbest and it is way better than titans s2. Also comes with android n from factory.
tvladan said:
You can move to doogee s60, it's on sale on gearbest and it is way better than titans s2. Also comes with android n from factory.
Click to expand...
Click to collapse
Thank you for the tip but I will stick with my beloved dg700 until it dies or I die.. Lol
Hi guys,
I bought the "new" Moto X Style last week for 250€(new, white, 32gb) and updated it to the highest Android 6.0 version from Motorola. After that, i flash the OTA-file from:
https://forum.xda-developers.com/moto-x-style/general/ota-moto-x-style-android-7-0-nougat-t3630248
After that, i unlock the bootloader, flash TRWP, clean the data and create a System backup:
https://xda.bioharz.xyz/2017-07-15--06-20-47_NPH25.200-15.7z
This is unmodified! and unrootedI actually have no time to create a System image, but this should also work for you.
I hope this can help you.
Thanks,
One question, this backup work in XT1572 CID12?
Necrodaemon said:
Thanks,
One question, this backup work in XT1572 CID12?
Click to expand...
Click to collapse
nope, only for the EU model
Netflix not working after installing
anth0nymDROID said:
Netflix not working after installing
Click to expand...
Click to collapse
Probably failing SafetyNet API check but what is the error?
Nougat will fail if the bootloader is unlocked and you don't have the Magisk module to stop SafetyNet. In Nougat an unlocked bootloader is enough to get it to fail even if otherwise 100% stock.
Netflix could also be confused as to your region if you restored the backup in this thread.
acejavelin said:
Probably failing SafetyNet API check but what is the error?
Nougat will fail if the bootloader is unlocked and you don't have the Magisk module to stop SafetyNet. In Nougat an unlocked bootloader is enough to get it to fail even if otherwise 100% stock.
Netflix could also be confused as to your region if you restored the backup in this thread.
Click to expand...
Click to collapse
Im reteu fr in Germany but if that's the case well no mobile Netflix I can still live my life without it.
anth0nymDROID said:
Im reteu fr in Germany but if that's the case well no mobile Netflix I can still live my life without it.
Click to expand...
Click to collapse
Magisk 13.3 can help with the safety net test. Here is how to install at stock: post #4
https://forum.xda-developers.com/moto-x-style/general/guide-flashing-stock-firmware-t3637235
dzidexx said:
Magisk 13.3 can help with the safety net test. Here is how to install at stock: post #4
https://forum.xda-developers.com/moto-x-style/general/guide-flashing-stock-firmware-t3637235
Click to expand...
Click to collapse
That's good advice!! Thanks I'll try it later and see how it goes
What is the proper way to flash this backup using TWRP? I did a adb push to /sdcard with al files from the extracted .7z file but TWRP can't ze the backup.
What am I doing wrong?
xabr3 said:
What is the proper way to flash this backup using TWRP? I did a adb push to /sdcard with al files from the extracted .7z file but TWRP can't ze the backup.
What am I doing wrong?
Click to expand...
Click to collapse
Extract the backup zip file. Copy the last folder (containing the boot and system images) to your phone's TWRP Backup folder. Now you will see it in TWRP. Now perform a full backup. Then restore the copied-over nougat backup. Now you can pick on of the following two options.
1. f you have time, you do not need to delete your data before rebooting. You can always uninstall and reinstall any problem apps that show up after rebooting. That is what I did.
2. Of course, if you are in a hurry, you can delete your data and then reboot. That would be called a "clean install" and I don't do that very often.
Hope this helps.
@bioharz
Cheers for this. I was contemplating what method might be easiest for upgrading my rooted Moto X Style (EU) from MM 6.01 to Nougat 7.0. Ideally, this would have been a TWRP flashable ZIP, however, you have provided the second best option, which is a TWRP backup.
My method was as follows:
1) Make full TWRP backup of existing MM installation to extSD
2) Backup my Nova settings to extSD
3) Download, unzip and copy your backup to the TWRP location on extSD
4) Boot into TWRP and wipe Dalvik/ART, Cache, System and Data partitions via Advanced Wipe menu
5) Flash System and Boot partitions from your Nougat backup, BUT NOT EFS partition !!!
6) Reboot, log onto previous Google Account and restore all apps.
7) Restore Nova settings
8) Root with SuperSU (systemless) and SuHide
Worked a treat :good:
Are you sure - you need nougat with old radios?
You could reflash stock MM, update to Nougat, root, restore all you want. @Yemble
Will it work on moto x style Indian variant?
dzidexx said:
Are you sure - you need nougat with old radios?
You could reflash stock MM, update to Nougat, root, restore all you want. @Yemble
Click to expand...
Click to collapse
I am certain that I do not wish to screw up my phone with someone elses IMEI. Besides, what exactly is wrong with the MM radios? They are working perfectly on my phone.
Actually, given that I am now in a good position to experiment further, I have flashed the Nougat EFS partition on its own to my phone. Thankfully, it did not affect the IMEI or any network connectivity (SIM or WiFi). However, it has not changed the base band version either, so it may, in fact, be identical to the MM EFS anyway!
coolncoolest said:
Will it work on moto x style Indian variant?
Click to expand...
Click to collapse
Take a TWRP backup first, then give it a go. What have you got to lose?
I suggest that you try it without the EFS partition first. If that works, take another TWRP backup and then try flashing EFS on its own.
@coolncoolest @Yemble
Don't flash/restore EFS from another phone - you can lose your IMEI.
India - RetAsia version has the same baseband as RetEu - cid7.
Dual sim probably will not work.
dzidexx said:
@coolncoolest @Yemble
Don't flash/restore EFS from another phone - you can lose your IMEI.
India - RetAsia version has the same baseband as RetEu - cid7.
Dual sim probably will not work.
Click to expand...
Click to collapse
Clearly you are wrong about this (on this particular phone model), as I have already tried it and it proved that it did not break, or change, anything! I am aware that flashing EFS can be dangerous on older Samsung phones, hence my cautious approach that you appeared to be dissing in your previous post
I believe in hard facts, rather then hearsay. I have now upgraded three XT1572 (EU) phones from the posted TWRP image using the method that I outlined previously, together with the later flashing of the EFS partition. All three phones work perfectly and all three pass SafetyNet.
Someone else may be less fortunate than you and there is no reason to flash/restore efs.
Not only Samsung can lost imei in this way - Lenovo(+tablets), other Moto series, all Mtk devices(there is easy way to restore imei).
For Moto I don't know any restoring procedure. Sorry - one - mainboard replacement. @Yemble
dzidexx said:
Someone else may be less fortunate than you and there is no reason to flash/restore efs.
@Yemble
Click to expand...
Click to collapse
Really, then what was the point of your post at the top of this page?
Yemble said:
Really, then what was the point of your post at the top of this page?
Click to expand...
Click to collapse
Do you mean:
Nougat with old radios?
I meant:
Flash stock 6.0.1 24...58-5 with fastboot and get ota update.
Somewhere I uploaded my backup(6.0.1 EU) - without efs.
Hello community!
Hope you are doing awesome, I am trying to install specifically the update from the 18 th of May (latest while doing this post) so when I downloaded it I go to TWRP and this is what I done
1)Place my pin and decrypt the device
2) Perform a format Data > Yes
3) Wipe cache, dalvik, internal
4) Restart to Recovery
5) Install the update all seems to be fine and reboot to system
The Phone boots to Poco screen and then vibrates and then gets me back to TWRP. I manage one time to get it worked and got in the config page from the customer rom a UI unresponsive message and is unable to connect to my Wifi so I have to use the Data 4G to make it work and I rolledback to April version of Arrow OS that seems to be the one working now.
The Miui stock that I am using to install the customer Rom is surya_global_images_V12.0.8.0.QJGMIXM_20210222.0000.00_10.0_global
Could you please provide some hints and tips what I am doing wrong so I can get this updates up to date? Because I love the Arrow OS Rom and I want to keep the firmware updated correclty on my side.
Thank you!
I am very interested, too. Got the same problem. After latest OTA-Update I'm stuck in a recovery bootloop as well.
Sadly even the attempt to flash back an older version or a MIUI Stock rom is failing for me now. Always recovery bootloop, even after a successfull flash without errors (and format data of course) .
Is the stock rom or an older arrow os version working for you, after the 18th May update?
@koelbche I was able to make a stock based on the stock fw shown on my post. then I installed old version of arrow OS April update and it was restarting bootloop.
I had to delete data, factory reset and select de wipe options so super clean flash and manage to boot it up.
I am waiting for any updates from others that manage to install the updates because I was not able to do it.
Flash ArrowOS custom recovery for ota update to work. After update you can flash recovery back to TWRP for root and backup, your choice.
I was able to make it worked in another post.
All I have to do was to update the version of the stock with Oss vendor (I think) and then all worked like a charm!.
Thanks for the replies though
Hello! I've been rooting and installing custom ROMs for years but it's been a long while since I last did it, I got a oneplus 8 global (IN2015) late last year, unlocked the bootloader as soon as I got it out of the box since I knew eventually I would want to flash some stuff. but I have kept it stock this long. Running latest Oxygen 11 android 11
Since I want to start flashing some kernels or roms I wanted to ask about making a backup since I've never had a phone without sd card slot where I would usually store backups.
Can I still use titanium backup to keep all of my apps/data/photos/videos and the state they are in, store it in my pc , then go about flashing a custom Rom and then bring my titanium backup back into the phone and restore everything?
since I'll be installing custom roms based on android 11 I believe it will be fine with no conflicts? or does it matter that my apps were installed in Oxygen OS?
that's what I used to do with older phones anyway. is there a way to flash a rom while having the titanium backup still in storage since most roms require full whipe when clean installing them?
Recently twrp added official support for OP8 and when I open the official app it recognizes my phone as instant noodle but when I click search for phone it says it can't connect to the server? should I flash official twrp from the app or via fastboot? which I'm also quite rusty with.
any tips for a step by step would be appreciated
Hello, I was in the same boat as you since I came to the OP 8 from a Galaxy S4. Titanium backup should work for what you want to do, as long as the custom rom is also based on A11 (disclaimer: I haven't tried it; I'm running rooted stock OOS 11 with a custom kernel). If the rom you want to install requires a data partition format, you can't keep the backups there during the flashing process. If it only needs a data wipe / factory reset, everything in the sdcard directory (also known as /data/media) should be preserved.
I'd say just flash TWRP in fastboot. Flash it to both recovery slots, and read up on how flashing works with A/B slot devices if you aren't familiar, since you'll need to know about it when flashing roms also. It's a big difference from what I was used to with older devices.
Thanks for the reply, yeah I was thinking of just going with a custom kernel since I have so much stuff going on the phone I find it really a chore to backup, but still might want to try it.
What kernel are you using and how are you liking it ?
Since oneplus 6 nas no security updates i decide to install custom ROM LineageOS 19.1 the newest build from official website.
Before installing this ROM i do all steps gently from Funky Wizard guide.
I have ADB drivers, unlock bootloader, installed magisk (rootet phone) backup my OOS and EFS, and installed twrp.
All basic stuff. Now i was ready to go to installed lineageOS.
I install lineage and i do all steps by their official website but with twrp. ( only what i dont flash copy partition zip file i wasnt sure if that will be work with twrp ).
After restart to recovery i must install gapps. Unfortunely the recovery was replaced i was assumed istead of twrp.
I installed gapps with their recovery and all work fine until i want to replace to twrp.
Now when i boot temporarly from img to install it perm. I have weird folder names wihtout any possibility to add ZIP file.
With some research i guess that folders are somehow encrypted.
Could you help me to install twrp with lineageOS when i have still access to this files? I need it for ex. recovery to stock if something in future goes wrong.
And i am currently on android 12 for sure.
Thank you from feedback!
first of all, you'd be better of if you posted this in the right area ==> https://forum.xda-developers.com/t/rom-official-enchilada-12-lineageos-19.4437321/ ==> more chance to get help related to LOS 19 questions (it's pure chance I saw your post here)
second: make sure to follow the instructions given at the LOS instructions pages ==> https://wiki.lineageos.org/devices/enchilada/
Mostly it is important that you have latest OOS 11 firmware installed in both slots before you start with LOS.
For the first steps never mind which recovery you have, just follow the instructions using LOS recovery. Reason is that TWRP is having problems wiping data / performing factory reset, at least it never worked for me. Then later on you can switch to TWRP
Back in May this year I wrote an instruction set here: https://forum.xda-developers.com/t/rom-official-enchilada-12-lineageos-19.4437321/post-86879331
Interesting for you right now is everything below 1.x
2.x is a separate instructiopn set for OTA updates coming later on
Good luck!
Thank you for response. You have right its better to install it directly from dedicated recovery (lineage) and than replace with twrp. Also i fill missing steps (install recovery again and flash parition integration file) and also wipe all data as instruction says. Now after reinstall lineageos and then install twrp i have all normal structure files as before. Thanks again