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
I bought a Nextbook Ares 8 whose stock rom is:
Model : NXA8QC116
Android Version : 5.1.1
Build # : V2.0.3
Kernel version : 3.10.62-x86_64_byt
As with all of my Android devices, I always have to have a custom recovery and device must be rooted.
And upon googling around, there's not much discussions/forums in installing custom recovery and root for this device.
I came across @vampirefo's Root Nextbook Ares 8, TWRP Recovery, Disable encryption
His thread is specifically for the Nextbook Ares 8 with stock Android 5.0. But, despite his warning, as I really needed TWRP and root, I went ahead and did his steps. I was successful in installing TWRP. But, unfortunately, his modified boot.img did not work with my Ares 8 5.1.1 stock rom. My tablet was stuck in the Nextbook logo.
Good thing is I made a TWRP backup of my stock 5.1 rom, including the original boot.img. Unfortunately too, the stock boot.img won't work with unlocked bootloader. Still bootloop.
So I edited the original 5.1 boot.img so it works on unlocked bootloader/custom recovery. I also modified it to remove the force encryption.
I flashed my modified boot.img and my Ares 8 booted normally. So i am happy with TWRP installed and a rooted Stock Ares 8 5.1.1 rom.
I am posting here the modified boot.img (with encryption removed) and a TWRP backup of the Rooted and Unencrypted Stock 5.1 rom so others may try (at their own risk).
DISCLAIMER:
As much as this worked for my device doesn't necessarily mean it will work for you. It's totally your choice if you did what I did and use the files I posted on this thread. I will not be held responsible if you f#@ked up your device. It's totally your responsibility.
Click to expand...
Click to collapse
Requirements:
1) Nextbook Ares 8 with 5.1.1 stock rom. NOTE: The modified boot.img attached is for the stock 5.1.1 It won't work properly with other roms. If you are using a custom rom at the moment, go back to your TWRP backup of stock 5.1.1. If you don't have a backup, you could try the TWRP 5.1.1 backup posted below.
2) TWRP installed (using @vampirefo's method)
IMPORTANT NOTE: Make a backup of all your important data. Unencrypting your device will wipe your data partition.
Steps:
1) Read disclaimer above. If you're ok with that, go to step 2. Else, leave this thread, and go elsewhere.
2) Head over to @vampirefo's thread to install TWRP. Root Nextbook Ares 8, TWRP Recovery, Disable encryption
3) Don't reboot your device as the unmodified stock boot.img wouldn't work with unlocked bootloader and @vampirefo's modified boot.img will not work with our stock 5.1.1 rom.
4) Boot to TWRP. Making a system backup is highly recommended (but not necessary).
5) Download, place on your sd card and install via TWRP the attached file Ares8_5.1_modified_boot.img.by.greatbal.zip (just like a normal zip file flashable via TWRP)
6) Reboot your device after successful installation.
7) Enjoy.
Suggestion:
Install SuperSU via TWRP for a better Android experience.
==================
TWRP Backup of Stock 5.1.1 Rom
This is the TWRP backup of the stock Ares 8 5.1.1 rom. It's pre-rooted and removed force encryption. It's working on my device. You could try it on your Ares 8 version.
DISCLAIMER:
As always, TRY AT YOUR OWN RISK. Make sure you have a backup plan if anything goes wrong. Don't blame me if you mess up your device and you forgot to make a backup of your working rom.
Click to expand...
Click to collapse
Steps:
1) Download Ares8_Stock_5.1_rooted_unencrypted.2016-11-08--TWRPbackup.zip
2) Extract the zip file.
3) Transfer the Ares8_Stock_5.1_rooted_unencrypted.2016-11-08--TWRPbackup folder you extracted to your sd card. Place it inside the TWRP/Backups/[Your Device] folder. Mine it's TWRP/BACKUPS/NXA8QC116/ folder.
4) Boot to TWRP.
5) In TWRP: Wipe>Advanced Wipe. Wipe dalvik-cache, cache, data, system.
6) In TWRP: Restore>Choose "Ares8_Stock_5.1_rooted_unencrypted.2016-11-08--TWRPbackup"
7) Reboot after successful restoration.
NOTE: the TWRP backup already has the modified boot.img, so you don't have to install the Ares8_5.1_modified_boot.img.by.greatbal.zip
You may also be interested with Remix OS 2.0 ported for the Ares 8. Please visit this link.
Click to expand...
Click to collapse
===================
Credit goes to @vampirefo for his work in bringing TWRP and root to Nextbook Ares 8.
Thx, 101% percent working on my Nextbook Ares 8 running on Android 5.1.1 out of the box. and now i'm very happy, after trying a lot of modified roms of vampirefo this stock 5.1 rom is still the best for our Ares 8 tab.
Sent from my ASUS_Z00ED using Tapatalk
Tuzuriro said:
Thx, 101% percent working on my Nextbook Ares 8 running on Android 5.1.1 out of the box. and now i'm very happy, after trying a lot of modified roms of vampirefo this stock 5.1 rom is still the best for our Ares 8 tab.
Sent from my ASUS_Z00ED using Tapatalk
Click to expand...
Click to collapse
Good to hear it worked for you. IMO, I also think this 5.1.1 is the best rom for Ares 8, compared to the other roms I've tried. Much better by a mile!
For one thing, the speaker volume is a lot louder than the other roms.
I have a question I just got a nextbook ares 11a with 5.1 and wanted to root it I read that ares 8 is the same to root it
stickman1981 said:
I have a question I just got a nextbook ares 11a with 5.1 and wanted to root it I read that ares 8 is the same to root it
Click to expand...
Click to collapse
There is a thread re Ares 11 rooting and installing TWRP. I've read that it is very similar to Ares 8 rooting. maybe you could visit their thread so they can help you better.
I still get the boot IMG signature verification failed upon reboot but everything else is working great. Like you I started with stock 5.1.1 and downgraded to vampires 5.0. how do I remove this annoying Sig. verification failed message?
OT. If anyone is interested, I ported Remix OS 2.0 to Nextbook Ares 8.
Im sorry but may I ask what OT is and would you mind helping me understand how to fix this. I really appreciate your twrp backup and all your time and effort in creating the working 5.1.1 backup. Thanks to vampirefos as well for all of your work as well.
After trying a lot of different rom. I was successful thanks to your guidance. Thanks a lot :good:
roy.garlington said:
I still get the boot IMG signature verification failed upon reboot but everything else is working great. Like you I started with stock 5.1.1 and downgraded to vampires 5.0. how do I remove this annoying Sig. verification failed message?
Click to expand...
Click to collapse
Yes, that's the downside of unlocking bootloader and installing a custom recovery. You are always reminded upon reboot. It's an issue on other devices as well when you unlock the bootloader unofficially. Examples are Motorola, HTC, Nexus, Oppo, etc...
It's a small price to pay for being able to install a custom recovery, rooting and being able to play around with custom roms, IMO.
roy.garlington said:
Im sorry but may I ask what OT is and would you mind helping me understand how to fix this. I really appreciate your twrp backup and all your time and effort in creating the working 5.1.1 backup. Thanks to vampirefos as well for all of your work as well.
Click to expand...
Click to collapse
OT = Off Topic. hehe. Off topic because I posted a link to a port of Remix OS 2.0 I made for Ares 8, whixh has nothing to do with this thread. Just in case somebody is interested to try and want something to play around with.
As of now, there is no way of getting rid of that nag screen reminding you that your bootloader has been unlocked or custom recovery has been installed. We have to live with that nag screen and press Volume Up everytime we reboot our devices. This is an issue with some other devices as well when bootloader is unlocked unofficially.
nguoiduatin196 said:
After trying a lot of different rom. I was successful thanks to your guidance. Thanks a lot :good:
Click to expand...
Click to collapse
good to here I was able to help you go back to Stock 5.1.1
BTW, since you are into changing and trying out roms, you may also want to try Remix OS 2.0 for Nextbook Ares 8 NXA8QC116 just something to play around with.
greatbal said:
good to here I was able to help you go back to Stock 5.1.1
BTW, since you are into changing and trying out roms, you may also want to try Remix OS 2.0 for Nextbook Ares 8 NXA8QC116 just something to play around with.
Click to expand...
Click to collapse
I do not want this change. But I will save your links ^^. I believe that after this I will need to it: P
Thanks man :highfive:
nguoiduatin196 said:
I do not want this change. But I will save your links ^^. I believe that after this I will need to it: P
Thanks man :highfive:
Click to expand...
Click to collapse
Ok.
Works perfectly. Thank you.
NeuralMonk said:
Works perfectly. Thank you.
Click to expand...
Click to collapse
good to here I was able to help you go back to Stock 5.1.1
BTW, if you're up to it, you may also want to try Remix OS 2.0 for Nextbook Ares 8 NXA8QC116 just something to play around with.
I spoke to early. No sound on the device either through the speaker or earphone jack. I have not tried attaching a bluetooth yet. If I plug the earphone in, I hear the "pop" of the electric on the jack, but no sound.
NeuralMonk said:
I spoke to early. No sound on the device either through the speaker or earphone jack. I have not tried attaching a bluetooth yet. If I plug the earphone in, I hear the "pop" of the electric on the jack, but no sound.
Click to expand...
Click to collapse
What's the model number of your Ares 8? What was the original Android version it had? If the model number and the original android version matches mine, you shouldn't have that problem. I didn't touch the rom in any way. it is the stock rom.
BTW, did you flash just the modified boot image? Or did you flashed the TWRP backup?
FYI, you cannot use the modified boot image posted above with other roms. You should use the stock 5.1.1 your device had originally. If you are using other custom roms, it won't work properly. you could try to flash the complete TWRP backup of the stock 5.1.1 posted on the original post.
Requirements:
1) Nextbook Ares 8 with 5.1.1 stock rom. NOTE: The modified boot.img attached is for the stock 5.1.1 It won't work properly with other roms. If you are using a custom rom at the moment, go back to your TWRP backup of stock 5.1.1. If you don't have a backup, you could try the TWRP 5.1.1 backup posted..
Click to expand...
Click to collapse
greatbal said:
What's the model number of your Ares 8? What was the original Android version it had? If the model number and the original android version matches mine, you shouldn't have that problem. I didn't touch the rom in any way. it is the stock rom.
Click to expand...
Click to collapse
Model: NXA8QC116
Android Version: 5.1.1
Should be the same. I am wondering if I removed something from the cache that is missing. I need to look at this in more detail. Maybe this weekend.
greatbal said:
BTW, did you flash just the modified boot image? Or did you flashed the TWRP backup?
Click to expand...
Click to collapse
TWRP is in the recovery slot.
Modified boot image is the last flash via TWRP zip file install.
Thanks for your help.
NeuralMonk said:
Model: NXA8QC116
Android Version: 5.1.1
Should be the same. I am wondering if I removed something from the cache that is missing. I need to look at this in more detail. Maybe this weekend.
TWRP is in the recovery slot.
Modified boot image is the last flash via TWRP zip file install.
Thanks for your help.
Click to expand...
Click to collapse
Ok. If you're coming from another custom rom like I708Q or Batville Rom, do a fresh install of the TWRP Backup. Wipe>Advanced Wipe. Wipe dalvik-cache, cache, data, system, and then restore the TWRP backup (System+Boot). You don't even have to install the modified boot image as it is already included in the TWRP backup.
Good luck. I hope you will be successful as this 5.1.1 rom is really the best for our Ares 8, based on experience. Specially the louder speaker volume. Other custom roms, very soft speaker volume.
The Remix OS 2.0 rom is also nice. Loud speaker volume and quite stable. That is, if you're into the "Windows-style UI" and willing to learn the ins-and-outs of Remix OS.
deleted.
Reserved
Hi, I got a BLU Studio J1. I am sorry for the newbie question. I am looking to root this device. No intention on installing any custom ROM, I only need root. Can you point me out which files (if available) would I need to do so? Thank you!
BobAt1080p said:
Hi, I got a BLU Studio J1. I am sorry for the newbie question. I am looking to root this device. No intention on installing any custom ROM, I only need root. Can you point me out which files (if available) would I need to do so? Thank you!
Click to expand...
Click to collapse
You have the BLU Studio J1 - S050Q - MT6570 - Android 6.0 Marshmallow - 512RAM - 8GB ROM.
So my question can be funny. But need.
You searched any custom recovery for your device before asking here?
If yes: So you have 2 ways. 1) Got to link and the guys create one to you => TWRP Builder
Read all thread!!
2) send me 3 files from stock ROM (same build version ROM of your device): recovery.img - boot.img - scatter....txt
If you don't have stock ROM, so I can't help!!
You need know about tool process to flash files.
READ this!!
About TWRP question:
1- is need anyone with experience (or courage to do) to flash stock files with SPFT.
IYou can able to do a backup stock ROM with SPFT if build version ROM is different from firmware. Then you will be able to flash the test file.
2- is need know if need unlock bootloader or not.
The first moment NO UNLOCK! If the file test not boot so is need Unlock to know if work file test.
3- I not need phone in my hands. But is very easy and fast solving issues when have its.
Because is more easy to repair phone if anything wrong happens. So the risk and responsability is of the user!!
lopestom said:
You have the BLU Studio J1 - S050Q - MT6570 - Android 6.0 Marshmallow - 512RAM - 8GB ROM.
So my question can be funny. But need.
You searched any custom recovery for your device before asking here?
Click to expand...
Click to collapse
Okay. Lets go by part. I have not looked/found any custom recovery for this device yet. If I am correct, getting a custom recovery for my device/build would allow me to initiate or start the process or rooting the phone? right?
lopestom said:
If yes: So you have 2 ways.
1) Got to link and the guys create one to you => TWRP Builder
Read all thread!!
Click to expand...
Click to collapse
I suppose I can work on this. I am just confused on this part.
"Get any working recovery.img for your device (from stock ROM or old working TWRP)"
Do I have to get it somewhere or, I can get it from that App of that thread?
lopestom said:
2) send me 3 files from stock ROM (same build version ROM of your device): recovery.img - boot.img - scatter....txt
If you don't have stock ROM, so I can't help!!
Click to expand...
Click to collapse
I ALSO can do this option instead. But how can I extract those files from my phone? or extract the stock ROM?
lopestom said:
You need know about tool process to flash files.
READ this!!
About TWRP question:
1- is need anyone with experience (or courage to do) to flash stock files with SPFT.
IYou can able to do a backup stock ROM with SPFT if build version ROM is different from firmware. Then you will be able to flash the test file.
2- is need know if need unlock bootloader or not.
The first moment NO UNLOCK! If the file test not boot so is need Unlock to know if work file test.
3- I not need phone in my hands. But is very easy and fast solving issues when have its.
Because is more easy to repair phone if anything wrong happens. So the risk and responsability is of the user!!
Click to expand...
Click to collapse
I have some experience with flashing devices, and I am aware of some of its basic principles and what It means. I am willing do it myself and take the risk, given I wont need get or purchase extra hardware for it. I assume with SPFT is some sort of tool that I can use to extract my current ROM build and flash?
BobAt1080p said:
If I am correct, getting a custom recovery for my device/build would allow me to initiate or start the process or rooting the phone? right?
I suppose I can work on this. I am just confused on this part.
"Get any working recovery.img for your device (from stock ROM or old working TWRP)"
Do I have to get it somewhere or, I can get it from that App of that thread?
I ALSO can do this option instead. But how can I extract those files from my phone? or extract the stock ROM?
I have some experience with flashing devices, and I am aware of some of its basic principles and what It means. I am willing do it myself and take the risk, given I wont need get or purchase extra hardware for it. I assume with SPFT is some sort of tool that I can use to extract my current ROM build and flash?
Click to expand...
Click to collapse
With Custom recovery you can flash SuperSu or Magisk to have Root. Marshmallow ROM has the part that no good to Root with apps (in first released. But can have modified.).
So You can try some apps or software to have Root like kingroot (I don't like that but...). Search in xda!
Stock ROM: click in the link first post have Source Code going to thread with firmware and SEARCH if exist.
On that can have recovery.img file.
If not: send me PM and I show for you.
Your MT6570 can have difficulty or easy. All depend of your knowledge, courage and attempts!
Obviously, with security is better!!
Sent from my BLUBOO Xtouch using XDA Labs
lopestom said:
With Custom recovery you can flash SuperSu or Magisk to have Root. Marshmallow ROM has the part that no good to Root with apps (in first released. But can have modified.).
So You can try some apps or software to have Root like kingroot (I don't like that but...). Search in xda!
Click to expand...
Click to collapse
I will give that a try.
lopestom said:
Stock ROM: click in the link first post have Source Code going to thread with firmware and SEARCH if exist.
On that can have recovery.img file.
Click to expand...
Click to collapse
Studio J1 S050Q
http://www.mediafire.com/folder/5oyd...o%20J1%20S050Q
I previously had found this on your BLU Stock firmware thread, but was not sure if that was it. So I don't need to extract the ROM from my phone? Can I get the files/information I need for the TWRP Builder with this stock ROM?
BobAt1080p said:
I will give that a try.
Studio J1 S050Q
http://www.mediafire.com/folder/5oyd...o J1 S050Q
I previously had found this on your BLU Stock firmware thread, but was not sure if that was it. So I don't need to extract the ROM from my phone? Can I get the files/information I need for the TWRP Builder with this stock ROM?
Click to expand...
Click to collapse
I think you not reading first post.
The V6.0.03.01 stock ROM file is same version from your phone?
Setting - about phone - build version
If yes: unzip file, look recovery.img and following instructions by twrp builder.
Sent from my BLUBOO Xtouch using XDA Labs
i Have a Blu S1 (Blu R1 HD 2018) rooted with magisk and i did a working TWPR ported from Doogee Y6, but my problem is that when i boot in TWPR it ask for a patron to decrypt data. I draw the patron but it fail to decrypt (can use normaly) and internal storage shows 0MB.
Recovery shows a partition called /System Image" with 2650Mb and /Data with around 12Gb
Any way to fix this issue?
Edit: I did a factory reset. Now the internal storage is fixed and TWPR dont ask for decryp data. But the Wipe Data delete the files in internal storage
Rvrjei said:
i Have a Blu S1 (Blu R1 HD 2018) rooted with magisk and i did a working TWPR ported from Doogee Y6, but my problem is that when i boot in TWPR it ask for a patron to decrypt data. I draw the patron but it fail to decrypt (can use normaly) and internal storage shows 0MB.
Recovery shows a partition called /System Image" with 2650Mb and /Data with around 12Gb
Any way to fix this issue?
Edit: I did a factory reset. Now the internal storage is fixed and TWPR dont ask for decryp data. But the Wipe Data delete the files in internal storage
Click to expand...
Click to collapse
You have the BLU S1 - S0320WW - MT6750 - Android 7.0 Nougat - 2 GB RAM - 16GB ROM.
For TWRP 3.2.x (either the kernel with Marshmallow or Nougat) it is necessary to perform a data reset (WIPE - FORMAT DATA) part so that the TWRP recognizes the data structure in the phone. This is required for TWRP to also see internal storage.
For people who do not know, there is currently a patch.zip called disable_encryption (forceencrypt=> encryptable). But it should be done particularly for an MT6750 with Android 7 or someone else making one for /or you do yourself.
With the option made in FORMAT DATA the device will start the ROM as factory.
That's why I always write something that people should know about like the attacked image.
Obviously, after installing TWRP you could use a MicroSD to back up your data. But, since you have already reset ....
Regarding partitions do you need to know, compare and confirm if the TWRP coming from the donor has the same partitioning structure as your phone.
If everything works out well, congratulations and good luck! :fingers-crossed:
@lopestom intentionally i reset factory to remove the data encryption and it worked. TWRP shows all the partitions with the available space.
What I want is to be able to do in the future, to clean Data without removing files from internal storage (music, pics)
Could that be possible?
I compared the partition table of both and they are the same.
The difference between the devices more than everything, is in ram and storage.
Hace the same mt6750
Rvrjei said:
@lopestom intentionally i reset factory to remove the data encryption and it worked. TWRP shows all the partitions with the available space.
What I want is to be able to do in the future, to clean Data without removing files from internal storage (music, pics)
Could that be possible?
I compared the partition table of both and they are the same.
The difference between the devices more than everything, is in ram and storage.
Hace the same mt6750
Click to expand...
Click to collapse
Well. If you or other user installing TWRP in first time so yes, need FORMAT Data. But installing universal disable encrypt patch and Root so I think the users no lost internal storage. Obviously if TWRP look internal storage after install that files....
If no, so need FORMAT Data. In this case that's need only in first install TWRP. After that no need same process....
Two ways for no lost files: 1) put files in the Microsd. 2) in each period you can copy files to your PC or host/server like google photos, drive, etc...
Sent from my BLUBOO Xtouch using XDA Labs
Hello, I have a BLU STUDIO C 5+5 D890U, there is the phone but no recovery file A little help please, i wish to install a recovery and then a custom ROM
Raen! said:
Hello, I have a BLU STUDIO C 5+5 D890U, there is the phone but no recovery file A little help please, i wish to install a recovery and then a custom ROM
Click to expand...
Click to collapse
I sent PM to you.........
READ FAQ in first page too!!
:cyclops:
i have the files to install twrp and root BLU VIVO 5 MINI
I don't know how to root a blu studio j8
arxii said:
I don't know how to root a blu studio j8
Click to expand...
Click to collapse
You can try the KingRoot option from here. It worked on my Blu Studio One Plus. It says 2018 but its updated 2019 in the actual post. But in reality, nothing probably changed from the previous year to this year
https://www.xda-developers.com/best-one-click-root-2018/
---------- Post added 12th November 2019 at 12:02 AM ---------- Previous post was 11th November 2019 at 11:53 PM ----------
Hello lopestom, thank you for the TWRP for the Blu Studio One Plus. I tried getting the file from Android File Host but it kept telling me that access was denied to me there. Luckily I found it here.
I am hoping you can help me as I now want to use TWRP and magisk to root my device instead of the kingroot that I used previously.
Can you upload the stock boot.img for the Blu Studio One Plus? I'm trying to flash the stock firmware once more onto the device so It can hopefully fix some problems I'm having. After removing kingroot, it's being pesky and not letting me fully remove root and is at times stuck in a bootloop or not wanting to boot properly at all.
I'm able to access factory mode, standard recovery mode, and go into fastboot. But I'm afraid to create my own boot.img from it's current state, fearing the current problems will persist. The latest firmware I have is BLU_S0130UU_V14_GENERIC
Thank you for any help you can provide.
...............................
Hello again!
I found the TWRP from your downloads link in you= first post and then with even more searching I found a stock image here on XDA for the phone. Thank you for your help!
I have a nitro 5p, I'm looking for a way to root so I can get some type of custom rom. The stock one is lost unuseable
shatheone said:
I have a nitro 5p, I'm looking for a way to root so I can get some type of custom rom. The stock one is lost unuseable
Click to expand...
Click to collapse
I can help! Please Pm me, I just rooted and installed twrp. However I still haven't learned how to build custom rom yet.
timba123 said:
Did you figure it out
Click to expand...
Click to collapse
yea
wait that wasn't a question for me...lol
TWRP is not required in order to root the MaxWest Nitro 5P. In fact, you could not root it using TWRP even if you wanted to. This device ships with Android 9 Pie Go Edition and is fully Project Treble supported. Also, like many devices of its kind with a System-as-Root (SAR) configuration, this phone has no boot-ramdisk. The only workaround to attain root is to patch the ramdisk in the recovery image and flash the patched image to /recovery versus the typical /boot partition. This effectively enables Magisk to hijack the recovery partition. Thus, the tricky part. In order for root to be properly installed, the phone must manually be booted to recovery mode during each and every reboot. However, it won't actually boot into recovery mode due to Magisk hijacking the /recovery partition. It will boot into the Android OS with Magisk systemless root installed. If you choose to boot the phone normal, it will still boot into Android, but without Magisk installed. This is rather unorthodox and inconvenient but it remains the only solution for these devices with no boot-ramdisk. For more info on Magisk running in recovery, see the official GitHub documentation here: https://topjohnwu.github.io/Magisk/install.html
TWRP is not compatible with this type of install and will cause a bricked device. Simply unlock the bootloader, patch the stock recovery image with Magisk, and flash the patched image to the recovery partition via fastboot. Boot to recovery mode during the next and every subsequent reboot. I am presently drafting a rooting guide on this device and I will post my link here when finished, for anybody needing instructions.
The OP of this thread originally requested info on root for purposes of possibly installing a custom ROM. Indeed, there are a few Treble GSI ROMs compatible with the Nitro 5P (ARM, A-Only). However, you do not need to have a rooted OS in order to install GSI custom ROMs, but only an unlocked bootloader. I will compile some resources for compatible GSI Treble ROMs and list this info in my rooting guide coming soon. TWRP isn't needed for GSI installation. Everything can be done in AP Fastboot Mode. I am not certain if MaxWest Telecom has released the kernel source code for the Nitro 5P. I will research this. This code will be required for the compiling of custom ROMs such as LineageOS & Pixel Experience. It is likewise needed for TWRP to be built from source.
No problem. I'm certainly not saying that TWRP cannot be booted or even installed on the Nitro 5P. I'm only stating that under no circumstances can the Nitro 5P (in its stock configuration, at least) be rooted using TWRP. The only root solution -- due to the boot image being devoid of a ramdisk -- is the method I outlined above. Now, if someone compiled a custom boot image with integrated ramdisk, this would certainly change matters. Out of curiosity, have you tried flashing TWRP to the /recovery partition using fastboot flash recovery twrp.img? Or, in the alternative, you can replace the stock recovery image with TWRP by decompiling the .pac firmware package, repack the .pac archive, and flash TWRP using the Spreadtrum Flash Tool. I'm just curious as to whether anybody has tried that.
timba123 said:
I finally got a decent laptop. Windows 10. I'd love to root this nitro 5p. IDC if it's superuser or magisk root. I could take or leave twrp.
Click to expand...
Click to collapse
Magisk is the only supported root solution for this devices
Installation
The Magic Mask for Android
topjohnwu.github.io
Scroll down until you reach the installation heading titled "Magisk in Recovery." Follow those steps and you will attain root on your Nitro 5p. In a nutshell, you will be patching a stock recovery image versus a stock boot image. Magisk will be able to hijack the /recovery partition and enable systemless root on the Android OS.
hellofriendlymanveriosns said:
I can help! Please Pm me, I just rooted and installed twrp. However I still haven't learned how to build custom rom yet.
Click to expand...
Click to collapse
Why would you want somebody to PM you in order to get help? This is a custom Android development community. Provide your input openly on the thread so it can benefit all others who need help as well.
hellofriendlymanveriosns said:
I can help! Please Pm me, I just rooted and installed twrp. However I still haven't learned how to build custom rom yet.
Click to expand...
Click to collapse
Keep in mind that you rarely ever need to be rooted in order to install a custom ROM. However, you will need a custom recovery and the custom ROM itself. To the best of my knowledge, no custom ROMs have been ported to, or compiled for, the Maxwest Nitro 5p. However, the Nitro 5p is Project Treble supported, meaning you can boot and install a Generic System Image (GSI). There are a nunber of custom GSI ROMs available here on XDA, which have been build by various developers. This is a link to several GSI ROMs built from some of the more popular custom ROMs, i.e. HavocOS, LineageOS, ArrowOS, PixelExperience and others. These are available both with and without GApps, in both 32-bit and 64-bit architectures.
[SUMMARY][PIE GSI] BEST PIE-GSI ROMS to TRY (to this moment)
As we(in the TG group) have tested a bunch of Pie9.0 (s)GSI Roms on the XDA forum (https://forum.xda-developers.com/project-treble/trebleenabled-device-development) I was asked to make a guide/summary of what there was already been tested and in...
forum.xda-developers.com
Also, this is the official Project Treble forum here on XDA. This includes numerous GSI ROMs in various versions, instructional guides, device-specific resources and a ton of general info on Project Treble.
Project Treble
The Android 8.0 release includes Project Treble, a major re-architect of the Android OS framework designed to make it easier, faster, and less costly for manufacturers to update devices to a new version of Android. Treble is for all new devices launching with Android 8.0 and beyond.
forum.xda-developers.com
shatheone said:
I have a nitro 5p, I'm looking for a way to root so I can get some type of custom rom. The stock one is lost unuseable
Click to expand...
Click to collapse
I've tried unlocking the bootloader with no success.
For members having difficulties unlocking the Nitro 5P bootloader, you need to use the Token Identifier method typical to Unisoc (Spreadtrum) devices. There is a comprehensive YouTube guide on the process.
You will need a modified fastboot tools build, A Linux PC (or Windows PC running Ubuntu Live), and ADB Debugging/OEM Unlocking enabled in Developer Options. Links for the files you will need can be found here https://forum.hovatek.com/thread-32287.html
To the best of my knowledge, this is the only viable method for unlocking the bootloader on the Nitro 5p.
timba123 said:
I had trouble originally but a fellow xda member ma
I had trouble but someone here made a token for me. I'm bl unlocked for sure. I'm going to try to magisk root this weekend. The specs are poor on this device (nitro 5p) but is gsi/treble compatible . So I plan on trying that but in the end I'll prob just debloat stock to be as vanilla as I can and also add custom audio.
Click to expand...
Click to collapse
Viper4Android FX with the NEON audio drivers works quite nice on the 5p. A good debloating and some build.prop tweaks to optimize RAM efficiency and responsiveness made a big difference for me. You can also add a line to build.prop to disable the boot animation during boot up, which speeds up boot time considerably. Use Kernel Adiutor-Mod (APK available here on XDA) to enable Touch Boost under CPU settings and change the CPU Governor to Performance. Set I/O scheduler parameters to a 512 KB read-ahead on internal storage, using the noop scheduler preset. Set SELinux to permissive mode as well and use the Low Memory Killer (LMK) preset of Very Aggressive. In the ZRAM options, ensure Swappiness is set to 100.
Keep in mind that when rooting, you will need to install Magisk to run in recovery versus the typical boot.img patching.
Hello,
I have a moto G100 I just purchased. I unlocked the bootloader and I tried to install LineageOS but it was being difficult. I could get it to boot into TWRP. Now I tried to restore everything to stock as it wasn't even booting. After flashing the rom back in via fastboot the unit shows up as a serial device but that's it, no picture on the screen or anything.
I need some help to get this working again. Besides the directions on the LineageOS page sucks, steps are missing and things do not work properly.
Any help would be appreciated.
This is Qualcomm HS-USB QDLoader 9008 mode and won't boot.
Can anyone please help so this won't take weeks or months?
Thanks
Hello,
I fixed the brick with the blankflash file blankflash_nio_RRTS31.Q1-84-24-3-6
I was able to then use the official tool to recover the firmware. I was able to get LineageOS working but I wasn't able to do TWRP at all properly.
So I managed to install twrp but couldn't install lineage or anything out of it...
I managed to get TWRP installed but it was essentially useless as I couldn't access the internal flash unless it was setup by the OS already if you format the internal flash storage with TWRP it's useless especially via MTP.
I was able to install LineageOS and I was able to boot it, but I don't understand why it says I do not have enough space to install gapps. Without gapps LineageOS is essentially useless as an OS unless you do not use anything from google at all whatsoever not eve maps or anything.
How do I fix it so I can install gapps? I can't resize the system partition via TWRP as it doesn't even show it.
Thanks
if you have the bootloader unlocked you can try the "tinyflashscript" way and use that to overwrite all partitions with a stock image found here
RET stands for Retail and than the region code follows, just download the latest one for your region
after that your partitions are reset to the start and you could keep it that way or attempt to install lineage again but clean this time
I ran into the exact same situation as you with the storage issues and this fixed it for me
Hello my G100 was fully hard bricked trying to installed LineageOS (not the modded). I followed the following steps:
1. Installed and booted into LineageOS recovery from electimon.
2. Factory reset
3. Install ROM as adb sideload.
However, installation stuck at 47% and aborted. Phone was hard bricked once turned off. It couldn't even boot into booloader.
Luckily, I was able to enter EDL mode by pressing and holding volume and power down together for some time while it was plugged into PC using usb. Then I used blankflash to restore. This saved me from taking it to repair centre.
Hello,
I had the same brick issue and blankflash fixed it for me. I will try writing stock again then install LOSRecovery again and then try sideloading both LineageOS and gapps but I don't think that will work correctly as I think I did try that but we shall see, last time I did an install though after fixing the brick issue I used fastboot to do the stock recovery which should have fixed the partition sizes...
Thanks
It's strange that device becomes hard bricked because I installed LineageOS before and it booted fine. Only thing now changed is that I'm using February stock ROM instead of December one. Did Motorola change anything in Feb update that would cause hard brick when trying to install custom ROM?
Also, I've never did the "Ensuring all firmware partitions are consistent" thing. It worked before but not sure if we need to do it now.
Hello,
Strange indeed I can get LineageOS installed BUT because this is an A/B phone which is so silly, I can't install Gapps into LineageOS so essentially useless as the installer says the partition is too small and I do not have a way to fix that at the moment.
Thanks, and blankflash was able to get me up and running on stock but I cannot use the phone yet just like the DooGee S95 Pro I bought in hopes to use LineageOS... long story. Stuck with my ZTE Axon 7 from 2016 and a crap phone to make calls since my provider killed service to my ZTE Axon 7 so I carry basically 3 phones now. Until there is a fully working TWRP I am essentially screwed and feel like I wasted $400 on another phone.
marcusah123 said:
Hello,
Strange indeed I can get LineageOS installed BUT because this is an A/B phone which is so silly, I can't install Gapps into LineageOS so essentially useless as the installer says the partition is too small and I do not have a way to fix that at the moment.
Thanks, and blankflash was able to get me up and running on stock but I cannot use the phone yet just like the DooGee S95 Pro I bought in hopes to use LineageOS... long story. Stuck with my ZTE Axon 7 from 2016 and a crap phone to make calls since my provider killed service to my ZTE Axon 7 so I carry basically 3 phones now. Until there is a fully working TWRP I am essentially screwed and feel like I wasted $400 on another phone.
Click to expand...
Click to collapse
Using the method I described above I was able to install Lineageos 19.1 and then gapps (mindthegapps) using lineage recovery. it should be entirely possible
Hello,
With the storage not being large enough I was trying to install openGapps ( stock size ) for Android 11 since I was trying to use Lineage 18.1 and not 19/19.1 since 19/19.1 appear to have bugs and 18.1 does not. Anyhow I tried to sideload openGapps and it said there wasn't enough space on the system partition. I suppose I should try mindthegapps instead.
Thanks
So anyone successfully installed it without causing hardbrick? What exact steps did u follow? r u using g100 or edge s and what is the build number of stock rom prior to install? thanks
Windoors said:
So anyone successfully installed it without causing hardbrick? What exact steps did u follow? r u using g100 or edge s and what is the build number of stock rom prior to install? thanks
Click to expand...
Click to collapse
I used the latest stock after doing a recovery with blankflash and the rescue utility from Motorola. I then installed LOSrecovery because TWRP isn't ready. I then booted into LOSrecovery and sideloaded 19.1 latest from this forum. I can't figure out how to resize /system correctly so I cannot install anything other than MindTheGapps which sucks a lot.
Anyhow if we get a working TWRP soon that will allow resize as TWRP can't show the system partition and A/B switching is being worked out then we will be good to go.
If this isn't helpful or you need exact commands then I can do that too for you.