Related
I am brand new to the forums, to give you a little backround on my self. I am pretty much noob when it comes to tinkering with android phones,yet did root a galaxy s2 years back running voodoo custom rom, but sadly since then was not interested. I have good exp when it comes to's computers and have done some minor programming. So now to what I have been trying to do is root my old moto g 2013 gen 1 boost mobile lolli 5.1 installed. (Bootloader is unlocked) I have followed guides via google for 5.0 lolli but have not seen one for 5.1. I have been unsuccessfull on rootting this phone,any help would be awesome
andrewchamp1653 said:
I am brand new to the forums, to give you a little backround on my self. I am pretty much noob when it comes to tinkering with android phones,yet did root a galaxy s2 years back running voodoo custom rom, but sadly since then was not interested. I have good exp when it comes to's computers and have done some minor programming. So now to what I have been trying to do is root my old moto g 2013 gen 1 boost mobile lolli 5.1 installed. (Bootloader is unlocked) I have followed guides via google for 5.0 lolli but have not seen one for 5.1. I have been unsuccessfull on rootting this phone,any help would be awesome
Click to expand...
Click to collapse
Should be the same regardless of version.
You need the motorola drivers for your computer, adb and fastboot (search for Minimal ADB and Fastboot), custom recovery (search for TWRP) and SuperSU - https://download.chainfire.eu/696/supersu/
Connect your phone to your computer using a USB cable, copy SuperSU to the internal storage of your phone.
Reboot your phone into fastboot mode and flash recovery using:
fastboot flash recovery recovery.img <-- name of image that you downloaded and placed into the Minimal ADB and Fastboot directory.
Reboot your phone into recovery and then select Install from TWRP and install SuperSU.
There are lots of guides with more detail, check the Moto G General forum.
Do I have to install android sdk tool in order to do this?
andrewchamp1653 said:
Do I have to install android sdk tool in order to do this?
Click to expand...
Click to collapse
BUMP
andrewchamp1653 said:
BUMP
Click to expand...
Click to collapse
I searched TWRP and they dont have my model listed 2013 xt1031 only have xt 1032 listed.
andrewchamp1653 said:
I searched TWRP and they dont have my model listed 2013 xt1031 only have xt 1032 listed.
Click to expand...
Click to collapse
theres an answer in this other forum thread http://forum.xda-developers.com/showthread.php?t=2561757
good luck
Those links are dead.
andrewchamp1653 said:
Do I have to install android sdk tool in order to do this?
Click to expand...
Click to collapse
Yes, you need Minimal ADB and Fastboot.
Here's the latest TWRP Recovery - http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Deleted
Hi everyone,
after I bought my H60-L04 about a 1,5 years ago, I unlocked/rooted my device and installed a Custom ROM (Liquidsmooth v3.2). Since that day, I didnt change anything regarding OS/ROM.
Now I want to change things up, either testing the new official update or installing a ROM thats based on a newer Android version. Using the search I saw different approaches, some people saying I need to install an old version of EMUI (2.3?) first. I don't want to brick my phone and I dont have much experience with ROMs in general. Can someone please give me a short guideline on what to do?
Thanks in advance!
- Melas
derMelas said:
Hi everyone,
after I bought my H60-L04 about a 1,5 years ago, I unlocked/rooted my device and installed a Custom ROM (Liquidsmooth v3.2). Since that day, I didnt change anything regarding OS/ROM.
Now I want to change things up, either testing the new official update or installing a ROM thats based on a newer Android version. Using the search I saw different approaches, some people saying I need to install an old version of EMUI (2.3?) first. I don't want to brick my phone and I dont have much experience with ROMs in general. Can someone please give me a short guideline on what to do?
Thanks in advance!
- Melas
Click to expand...
Click to collapse
Download the firmware you want to try (LP or MM), use huawei update extractor to extract recovery, boot, Cust and system images from UPDATE.APP (you will get it from firmware). Meanwhile make a dload folder in your SD card and copy update into it.
Flash the images to your phone using fastboot.
Fastboot Flash boot boot.img
Fastboot flash recovery recovery.img
Fastboot flash Cust Cust.img
Fastboot flash system system.img
Press and hold power, vol up, vol down until the phone reboots. Let go of power but keep pressing the other two for 5,6 sec more. A forced update will start.
YOU WILL LOSE ALL YOUR DATA SO MAKE A BACKUP BEFORE DOING THIS.
derMelas said:
Hi everyone,
after I bought my H60-L04 about a 1,5 years ago, I unlocked/rooted my device and installed a Custom ROM (Liquidsmooth v3.2). Since that day, I didnt change anything regarding OS/ROM.
Now I want to change things up, either testing the new official update or installing a ROM thats based on a newer Android version. Using the search I saw different approaches, some people saying I need to install an old version of EMUI (2.3?) first. I don't want to brick my phone and I dont have much experience with ROMs in general. Can someone please give me a short guideline on what to do?
Thanks in advance!
- Melas
Click to expand...
Click to collapse
Just make sure you full unroot your device and flash stock recovery before updating. Or you will end up with a bootloop.
You may use Multitool app.
Thanks for you help, guys. My problem was that I used an old version of MultiTool and my adb-drivers didn't work.
Using your instructions I managed to install stock recovery and EMUI 4.0
derMelas said:
Thanks for you help, guys. My problem was that I used an old version of MultiTool and my adb-drivers didn't work.
Using your instructions I managed to install stock recovery and EMUI 4.0
Click to expand...
Click to collapse
No problem. It is always a good idea to factory reset after a new ROM. And wipe clean SDcard.
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!
hello, I recently installed pixel experience android 10, but for some reason I want to install the android 9 version of it. I already have the files needed but after wiping flashing following steps It just boot into fast boot . any idea why?
nests said:
hello, I recently installed pixel experience android 10, but for some reason I want to install the android 9 version of it. I already have the files needed but after wiping flashing following steps It just boot into fast boot . any idea why?
Click to expand...
Click to collapse
Because your rom file isnt orginial i geuss try another one