Related
Q&A for [MOD][SEP 14] MultiROM v28 (Redesigned GUI!)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
I'm trying to get ubuntu touch RTM running with MultiRom on my Nexus 4, and it's erroring out on boot. When I try to view the log it seems like it gets overwritten by the log for the successful android boot every time I try and get the phone to a place where I can actually access it.
I couldn't find a way to view it through recovery, and copying it to the sd card doesn't give an option to re-name, so it gets overwritten. How can I actually view the log?
rooting secondary rom
Tassadar, i have your lollipop factory image installed as secondary rom. I have a question about rooting it. I have read in other threads one cannot just flash supersu zip for root to work, that people are using CF Autoroot instead. Would this method overwrite multirom recovery ? Could you say best method for rooting. Thanks
does this contain the new radio, bootloader etc?
Solved by flashing permissive boot image zip from skypompos thread and super su 2.19 zip.
Grabbed lrx21t_mako.zip from OP's basketbuild site, fresh installed as secondary ROM, stuck at boot animation forever.
Primary ROM is stock 4.4.4, with latest 4.4.4 kernel+1105recovery+v29 all installed by multirom.
5.0.1
Hey man,
I know its just out,
but a 5.0.1 LRX22C_mako.zip would be awesome!
Thanks
question
Hi, can i use multirom on my nexus 4 with lollipop? And can i use as secondary rom a rom based on kitkat?
Does MultiRom work on lg optimus g (e975) mako unlocked and by modifying build prop to nexus 4?
[Q]
Hey , i just downloaded 5.0.1 and flashed my nexus 4 with stock 5.0.1 , rooted and flashed custom recovery too, used your kernel for 5.0.1,and flashed your custom TWRP
installed multirom and now, TWRP->Advance..->Multirom->Add new rom -> android-> zip-> and here, renamed my " occam-jdq39-factory-345dc199.tgz (4.2.2)" to " occam-jdq39-factory-345dc199.ZIP" to be able to flash ZIP
when i select " occam-jdq39-factory-345dc199.zip " to flash as secondry ROM ,after 1sec TWRP restart, i mean it close itself and reopen at TWRP main page, and then i can see "occam-jdq39-factory-345dc199" in rom list
but cant boot it and getting error
(log file attached)
whats wrong?
How do I restore a backup of any secondary ROM?
Hey, I have just made a back up of the data partition of my secondary ROM but, when I tried to restore it I realised that it's only possible to restore a back up for the primary ROM. There's any way to do that? Thanks.
[A]
Eraicos said:
Hey, I have just made a back up of the data partition of my secondary ROM but, when I tried to restore it I realised that it's only possible to restore a back up for the primary ROM. There's any way to do that? Thanks.
Click to expand...
Click to collapse
Hello,
You can Swap your roms, swap primary with secondary, restore your data partition backup, then swap back,
Stuck at google logo.
Hi everyone, first post here, two days after buying this phone and I'm already in trouble.
I followed the instructions to use MultiROM to add Ubuntu Touch; and everything was fine, until I decided I wanted RW access. Then, I had the idea to sudo apt-get upgrade within Ubuntu... it failed to complete the installation of the packages (though it had space... I think), then I tried to reboot the phone.
Now it gets stuck at the google logo; and if you press the power button to shut it down, it starts again after a second or two.
I can access recovery mode pressing the three buttons, and within, I get to MultiROM TWRP by choosing "Recovery Mode"; but there's a lot of options here and I could not find anything that allows me to boot on either Android ("Internal" seems to be gone) or Ubuntu.
I'm an experienced linux user but -as can be seen- this is my first foray with Android, smartphones, and the like.
Let me know what other information should I provide; and thanks in advance for your help.
Gorsh said:
Hi everyone, first post here, two days after buying this phone and I'm already in trouble.
I followed the instructions to use MultiROM to add Ubuntu Touch; and everything was fine, until I decided I wanted RW access. Then, I had the idea to sudo apt-get upgrade within Ubuntu... it failed to complete the installation of the packages (though it had space... I think), then I tried to reboot the phone.
Now it gets stuck at the google logo; and if you press the power button to shut it down, it starts again after a second or two.
I can access recovery mode pressing the three buttons, and within, I get to MultiROM TWRP by choosing "Recovery Mode"; but there's a lot of options here and I could not find anything that allows me to boot on either Android ("Internal" seems to be gone) or Ubuntu.
I'm an experienced linux user but -as can be seen- this is my first foray with Android, smartphones, and the like.
Let me know what other information should I provide; and thanks in advance for your help.
Click to expand...
Click to collapse
Nevermind. I flashed everything from scratch and now the phone is back on its feet.
I am not sure what is the problem, but adding specific radio images for secondary ROMs is not working. I tried with Sailfish OS and MIUI to include older radio images for them to work, but nothing changed.
Update primary rom
Hello.
I want to do a clean install of euphoria as the main rom. If I do I might lose the second rom?
Thank you for your attention.
Noelito3 said:
Hello.
I want to do a clean install of euphoria as the main rom. If I do I might lose the second rom?
Thank you for your attention.
Click to expand...
Click to collapse
according to the main thread in the section update /modify not
---------- Post added at 04:29 PM ---------- Previous post was at 04:16 PM ----------
silly question maybe but if I want to make my secondary rom the interal one and wipe the current internal, a copy secondary to internal would just do that right?
I wanted to do a swap first to be on the safe side, but I don't have enough free space for that
other remark : the app doesn't see that Ubuntu touch us already installed?
Multirom Ubuntu touch start error
İ have an issue about Ubuntu touch. İ installed multirom and installed what it recomemmends. İ installed Ubuntu stable with multirom. İt installed and opened first time. i choose my lang. etc . İt says phone is ready but there is an ubuntu icon rolling. Nothing else... İ cannot skip this icon. i Waited 1 hour or more 3 times. i have a nexus 4 with stock 5.1
I have some wondering what bothers me:
1. Internal rom is mounted read-only ?
2. Matter where I install the rom that I use more often,daily use ?
3. In system I do not realize if it moves slower but in recovery does(and load slower at startup),it can influence the performances and battery life in system?
Hi everyone!
This is my first post, hope there is a solution.
I have Samsung Galaxy A3 [A300FU].
I wanted to get rid of branded firmware, so I've found stock ROM here: mrcrab.net/stockrom/sm-a300fu.html and flash it with Odin and it was ok.
Then I wanted root, so I've followed this guide: trueandroid.com/root-samsung-galaxy-a3-sm-a300f-easy-guide and now, whenever I restart the phone, it boots to the screen with yellow text: set warranty bit : recovery (file_1.jpg). Then it goes to the screen with opened green robot (file_2.jpg) and after I choose: reboot system now, it loads to OS normally.
How to fix it?
Ok guys, I don't know what happened, but I've managed to save the day
What I did was connecting my phone to KIES and select Firmware Update and Initialization from the Tools menu. It wipes all the data so be prepare for that. This helped to get rid of the yellow text on the screen while booting, but the phone still kept booting to the recovery mode.
Then I've installed TriangleAway from this thread: forum.xda-developers.com/galaxy-s2/orig-development/2014-01-15-triangleaway-v3-26-t1494114 but it didn't seems to work (and, by the way, it doesn't support my phone). I've also installed SuperSU from Play Store, and also didn't work, so I've uninstalled both and reboot the phone. And guess what - it booted normally, straight to the OS.
Magic.
Sooo, the solution I've provided above wasn't what I needed, because I insist to have my device rooted. That's why I started once again.
I've installed stock ROM, rooted it and the result was the same (yellow text and booting through recovery mode).
I've customized the build with 360 Security (there's many apps out there which allow uninstalling system software and bloatware). Then I've installed Team Win Recovery Project through Odin meant for Samsung Alpha (teamw.in/project/twrp2) and that was it. No more yellow text or booting to the recovery mode. Shiny clean rooted A3.
locovibe said:
Sooo, the solution I've provided above wasn't what I needed, because I insist to have my device rooted. That's why I started once again.
I've installed stock ROM, rooted it and the result was the same (yellow text and booting through recovery mode).
I've customized the build with 360 Security (there's many apps out there which allow uninstalling system software and bloatware). Then I've installed Team Win Recovery Project through Odin meant for Samsung Alpha (teamw.in/project/twrp2) and that was it. No more yellow text or booting to the recovery mode. Shiny clean rooted A3.
Click to expand...
Click to collapse
Hello, I recently bought a A3 as well and im quite dissapointed to see there are no custom roms or forums dedicated to the A Series (A3, A5, A7). Ive been itching to root and install a custom rom seeing the stovk is starting to slow down a A LOT! Could you help me out by guiding me through the bloatware removal as i dont want to uninstall something i shouldn't
Sent from my SM-A300FU using XDA Free mobile app
locovibe said:
Sooo, the solution I've provided above wasn't what I needed, because I insist to have my device rooted. That's why I started once again.
I've installed stock ROM, rooted it and the result was the same (yellow text and booting through recovery mode).
I've customized the build with 360 Security (there's many apps out there which allow uninstalling system software and bloatware). Then I've installed Team Win Recovery Project through Odin meant for Samsung Alpha (teamw.in/project/twrp2) and that was it. No more yellow text or booting to the recovery mode. Shiny clean rooted A3.
Click to expand...
Click to collapse
You flashed a custom recovery meant for Galaxy Alpha on Galaxy A3? Doesn't doing that bricks the device? I'm having the same problem too.
Sent from my SM-A300F using XDA Free mobile app
Ok, here are the steps:
Download the newest formware from sammobile and install it through Odin.
Turn off the phone and boot into recovery, wipe cache and run factory reset. I don't know if it's meaningful, but I did it and that's it.
Set up the device and turn on USB Debugging in Developer options. To make those options appear you have to open Settings, then About Phone and keep tapping on Build Number.
Download root files for your model from here: autoroot.chainfire.eu, run Odin, install it and turn on the phone.
I assume you'll get those messages like I did "Set warranty bit : recovery" and the phone will keep booting into recovery mode and from there you can boot into OS. But it's unconvenient, so I've download the TWRP files to get rid of it. At first I used files for Alpha but last time I've install recovery meant for S4 Qualcomm and it worked as well (here: twrp.me/devices/samsunggalaxys4internationalqualcomm.html).
It didn't brick my phone. It keeps going. I don't know much about devices so I didn't hesitate I just wanted root for Macrodroid
Oh and I have SD Maid to freeze unwanted apps, like preinstalled ones and those I don't use, like android e-mail app (I prefer Gmail), stock calendar S Planner (I have Sunrise, it syncs with iCal), KNOX, live wallpapers, some widgets, Fliboard, S Voice, Google Movies Music Games Newsstand Books Hangouts, Google+, Hancom Office.
* Download Odin 3.09 from here: odindownload.com (second link)
Is TWRP 2.80 Working?
locovibe said:
Ok, here are the steps:
Download the newest formware from sammobile and install it through Odin.
Turn off the phone and boot into recovery, wipe cache and run factory reset. I don't know if it's meaningful, but I did it and that's it.
Set up the device and turn on USB Debugging in Developer options. To make those options appear you have to open Settings, then About Phone and keep tapping on Build Number.
Download root files for your model from here: autoroot.chainfire.eu, run Odin, install it and turn on the phone.
I assume you'll get those messages like I did "Set warranty bit : recovery" and the phone will keep booting into recovery mode and from there you can boot into OS. But it's unconvenient, so I've download the TWRP files to get rid of it. At first I used files for Alpha but last time I've install recovery meant for S4 Qualcomm and it worked as well (here: twrp.me/devices/samsunggalaxys4internationalqualcomm.html).
It didn't brick my phone. It keeps going. I don't know much about devices so I didn't hesitate I just wanted root for Macrodroid
Oh and I have SD Maid to freeze unwanted apps, like preinstalled ones and those I don't use, like android e-mail app (I prefer Gmail), stock calendar S Planner (I have Sunrise, it syncs with iCal), KNOX, live wallpapers, some widgets, Fliboard, S Voice, Google Movies Music Games Newsstand Books Hangouts, Google+, Hancom Office.
* Download Odin 3.09 from here: odindownload.com (second link)
Click to expand...
Click to collapse
I like what you did!. Is the TWRP 2.80 or twrp2 for Samsung Alpha working in Samsung A3? I mean to say that if you go to recovery by pressing Vol Up _Power _ Home Butttons, does TWRP Recovery appears? Or the stock recovery appears and you solve only the recovery and yellow problem?
If the TWRP Recovery Appears then you can install custom roms, backup your system and data. This will be a great job done by you and many owners of Samsung A3 will be thankful to you. Please Reply because I want to test it on my mobile
Etnad07 said:
I like what you did!. Is the TWRP 2.80 or twrp2 for Samsung Alpha working in Samsung A3? I mean to say that if you go to recovery by pressing Vol Up _Power _ Home Butttons, does TWRP Recovery appears? Or the stock recovery appears and you solve only the recovery and yellow problem?
If the TWRP Recovery Appears then you can install custom roms, backup your system and data. This will be a great job done by you and many owners of Samsung A3 will be thankful to you. Please Reply because I want to test it on my mobile
Click to expand...
Click to collapse
Well, it seems it only solved yellow text and can't boot into recovery at all. It can't be that way! So!
I've installed unbranded software once again and was waiting to update to Lollipop via Kies. But it took so long that I couldn't resist to root, but I did it differently this time. I've found KingRoot app which works like a charm. Just download the apk [mmgr.myapp.com/myapp/Kingroot/webapp_kingroot/image/KingRoot-4.1.0.249-release-nolog-201505211812_105001.apk] from [kingroot.net/down#root], run it and voila! No hassle, no Odin. After rooting there will come up two apps: Kinguser and some app in Asian. I've uninstalled the second one - it cleans memory and stuff. Stock recovery stays untouched and booting is normal.
Hi Everyone!
I Hope There Is a Solution....
I have galaxy a500g running with stock lollipop and I need to install a custom rom so I flashed TWRP_2.8_SM-A500-LL.img and booted into recovery once it booted into recovery it struck at set warranty bit:recovery and struck at recovery loop....is there a way to install a working custom recovery for galaxy a500g
Thanks in advance
***PLEASE DO NOT SKIP THE INSTRUCTION THAT SAYS MAKE A BACKUP*****
Lots of people are requesting help after not making a backup. And while people are able to help, the files are very large and takes up considerable bandwidth. Much better to EASILY create your own backup.
-------------------------------------------------------------------------
First of all a BIG thanks to @ionioni, this is all his work i am just re-uploading files and some sort of instructions. Much of the instructions are also lifted from ionioni, so thanks from me too!
That's right sources here: https://twrp.me
There Is currently no xposed support for intel 64 bit android
Neither I or the developer take any responsibility for damage to yourself or your tablet, by carrying out anything written here you accept full liability for your actions. I am quite sure xda forums feel the same.
****BIG WARNING , This is ONLY for the Yoga Tab 3 Pro models YT3-X90(F|X|L) Intel Atom powered CherryTrail SoC devices flashing any of these files to another device will more than likely result in BRICK!!****
ANOTHER BIG NOTE.....lollipop can only be rooted using supersu version 2.46 whilst marshmallow version ,as of writing, can ONLY get root using magisk!
You should backup all important data before attempting any of this as you will be losing all data during the process. Titanium backup is good for backing up and restoring apps, other personal files can be moved to external sd or copied to computer.
First off you will need to have fastboot installed on your PC if you havn't already. Find it here......
For windows. https://dl.google.com/android/repository/platform-tools-latest-windows.zip
For Mac. https://dl.google.com/android/repository/platform-tools-latest-darwin.zip
For Linux. https://dl.google.com/android/repository/platform-tools-latest-linux.zip
To gain ROOT access.....
1. download and extract the twrp.img file from the zip attached (YOU MUST EXTRACT FROM THE ZIP!!!) and copy supersu.zip or magisk.zip to tablets external memory card. https://download.chainfire.eu/696/SuperSU/ (LOLLIPOP only supersu v2.46 is supported, other versions cause bootloop) or https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 for MARSHMALLOW.
2. unlock your tab if is not unlocked (this is mandatory in order to boot custom images like TWRP recovery):
a) Enable developer options ( Go settings, at bottom select "About tablet" then press "Build number" 7 times. congrats you are now a developer.)
b) Go back to settings and now at the bottom there is a new option "developer options" in developer options enable "OEM unlocking"
3.Restart in fastboot mode (hold volume + while powering on tablet)
4. In the same foler you have extracted your TWRP.img (in windows) hold shift key while right clicking in the explorer window, select open command window here.
5. At the command prompt (black window that opens) type "fastboot oem unlock" for LOLLIPOP or "fastboot flashing unlock" for MARSHMALLOW. at this point you will be prompted that you want to delete all data, this is obviously a security measure that cannot be avoided.
6. go to step 7.
7. In command window (the little black window you opened earlier) type "fastboot boot twrp-2.8.7.0(6)-x90.img" your tablet should now boot to TWRP. ( This is a live session TWRP has not been flashed to your tablet)
******MAKE A TWRP BACKUP!!!!!!!!!!********* DO NOT SKIP THIS STEP.
Modifying system files will mean that you are unable to take Lenovo OTA Updates, the only way to install new updates is to later restore your TWRP stock backup, then reROOT. thats just the way it is i am afraid.
8. in TWRP install SuperSU.zip (lollipop) or magisk.zip (marshmallow) located at your external memory card.
9. Thats it enjoy Your rooted tablet.
10. If you experience time changing upon reboot use your favourite method to edit build prop, I used buildprop editor found in the playstore. Find "persist.sys.timezone" and change it to your location, I had to set mine to Europe/London.
PS...your tablet will hang on every boot at bootloader error 3 to warn about the unlocked bootloader, PLEASE DO NOT lock your bootloader, this is a small annoyance and makes brick recovery much easier. (just restore your lovely TWRP stock backup.
In order to install new Lenovo OTA update you must restore your TWRP stock backup, then take the OTA, then go through the root process again making a new TWRP stock backup after applying the new OTA.
Just one more BIG WARNING, this twrp comes with an option to reboot to bios. Be warned if you don't know what you are doing and you mess something up in there, FULL BRICK! no one will be able to help you recover.
PPS...there seems to be some issues with using magisk modules on our tab. To install them one must download them and then manually install them from twrp.
https://download.chainfire.eu/696/SuperSU/
Now for the real magic.
this can be achieved with or without root! just make sure, as per the ROOT instructions, the first thing you do in TWRP is make a full backup.
As a yoga tab 3 pro owner you know that your tablet lags, crashes and is generally buggy, mine would frequently crash during periods of long sleep.
there is a solution to this problem that is rather simple but seems to yield huge results. if we just run our tablet with the data partition unencrypted it runs like any other nice android device.
once again myself or the developer take no resposibility for your actions if you would like to try this.
instructions by ionioni.
""encryption of the 'data' partition (the one that holds your installed apps, personal stuff etc) is forced on these devices (even with no password set) the 'data' partition is automatically encrypted at boot time if it 'sees' an un-encrypted 'data' partition. in order to disable the enforced 'data' encryption i made a script that will disable the forced encryption flag in the existing boot (partition) image (encryption can still be triggered by the user in the Settings->Security panel). this will not decrypt an encrypted 'data' partition! will just allow you to boot having an un-encrypted 'data' partition."".........ionioni
1. make sure that when you make your TWRP backup that you include the boot partition (it will be patched by the script to disable forced encryption).
2. copy attached x90-disable_encr.zip to your tab and install from TWRP (once finished it will create also a backup of your original boot partition in the folder where the zip is located, however this is only a safety backup as you should have already backed up your Boot partition when making your TWRP backup)
3. **DO NOT SKIP THIS STEP** to finish, reboot in fastboot mode and input "fastboot format data" in order to have a clean(un-encrypted) 'data' partition on the next boot (and it will no longer be automatically encrypted as long as you have the modified boot)
alternatively you can format 'data' from within TWRP if you use the attached 'data' enabled TWRP.
i can confirm that since i have been running my tablet unencrypted using ionionis zip that i hav had no lagging, no crashing. runs just like any other android device. The kernel memory hog still remains but it works silky smooth.
Should anything go wrong stock rom for MARSHMALLOW can be found here...
https://forum.xda-developers.com/thinkpad-tablet/general/yoga-tab-3-pro-debrick-method-t3776951
Thank you for continuing the work !
Do you have compared the difference between encrypted/decryptet - is it worth to do all the stuff (root, etc.) ?
If you have to say a number in percent, how faster will it be ? You've tested multi-user (2nd user) ? If i setup a second user the tablet is nearly unusable - it's better with disabled encryption?
Sorry that i have a lot of questions, but it sounds not that easy and i think about it if its worth to do it
edit:
if i make a full backup - where is the backup of TWRP stored? Do i need a sdcard? Will it be overwritten by OTA/Update/Rooting/Decryption?
thx for your answers already.
I havnt tried with a second user. I could try for you.
before unencryption performance was sluggish. after unencrypted its just fine.
I know it seems like a lot of detail but it is actually easier than it sounds.
You don't have to have root to run the unencrypted stuff but you still need to oem unlock and make a full backup. Backup must be on external media, either ext sd or usb otg.
Your data would not be mountable in twrp unless unencrypted already. And then if you ever accidentily encrypted you ay be forced to format losing your backups.
External media is the way to go.
Sent from my SAMSUNG-SGH-I317 using Tapatalk
If i try "decryption" than root is not far away (so i also get rid of some "lets say useless" system apps)
If ýou can try to check for multiuser you should have running facebook on both accounts (cause fb need a lot of ram and cpu)
maybe i will try it on weekend. i'll think about it....
What about the other peoples who own this tab?
gtx, juergen
Well I would always go ROOT, as it offers more choice, but of course the choice is ultimately yours.
I can try multi users but unfortunately I am one of those weirdos that does not use facebook. I guess I could try a couple of instances of chrome/Firefox.
Sent from my SAMSUNG-SGH-I317 using Tapatalk
Ok just set up a new user switched between them ran chrome on both with several tabs open. didn't seem too bad.
Indeed more feedback from other users who have benifitted from unencrypted data partition would be useful.
Sent from my SAMSUNG-SGH-I317 using Tapatalk
Thanks for your effort.
Hello,
BIG THANKS for your Root solution !
All working !!! thanks !!
All thanks to ionioni, this is all his work, i was just the guinea pig. Glad you have root, did you run the unencryption zip?
Sent from my Lenovo YT3-X90F using Tapatalk
Thanks ionioni and joesnose!
I rooted my device and ran the unencryption zip, it definitely makes everything a little smoother.
Also, I successfully mounted my exFAT sdcard with the help of lurker0's post here: http://forum.xda-developers.com/showthread.php?t=3126394.
Nice. Thanks for the exfat find.
Sent from my SAMSUNG-SGH-I317 using Tapatalk
joesnose said:
Indeed more feedback from other users who have benifitted from unencrypted data partition would be useful.
Click to expand...
Click to collapse
Since the old thread is locked, I'll repeat myself here:
I rooted my YT3-X90F and decrypted it as well. Result is better overall performance (some1 asked rating in percentage, I would say +40% speed & +60% response).
But, sadly, it still needs restart every ~24hours, because all the freezes and lags come back with time.
Advise:
For those who want to root this device only to make it work with Sixaxis controller - don't even start. Yoga T3 doesn't support required bluetooth drivers (huge shame on Lenovo).
doesn't seem to connect to the ds4 either. Just sticks at pairing.
Sent from my GT-N7105 using Tapatalk
Hi Joesnose and thanks for putting the instructions up (and of course, thanks to ionioni).
I have a couple of questions.
EDIT; oh pants, I have some more (possibly stupid) questions - just to be sure I know what I'm doing !
In the very first instructions about rooting:
1. I download the twrp.img.zip to my PC and unzip it to PC right ?
2. And the SuperSu goes in my ext SD card, not on the PC ?
3. I assume I must connect the YT3 Pro to the PC at some point ? When would that be ??
4. I don't understand instruction 7. It says type "fastboot boot twrp-2.8.7.0(6)-x90.img". Do I need to have that file downloaded or something ? What is twrp-2.8.7.0(6)-x90.img file ?
And what does it mean, "This is a live session TWRP has not been flashed to your tablet" ?
I can see that in the section about unencrypting the data partition that there is a file with a similar name to " twrp-2.8.7.0(6)-x90.img' but it has the words "data-enabled" in the fine name. I'm not sure what to do with this ??
5. At what point do I take a back-up of the original YT3 Pro stock image ? It's listed between 7 and 8 ? Do I do it right after 7 ? How do you make the back-up please ? And I guess I better store another copy somewhere safe, off the SD card too ?
6. If I just root this, can I then get OTA updates normally ? (without having to restore to stock).
7. And, if I do root and/or data unencryption, can the YT3 Pro be put back exactly how it was before changing anything ? Including it getting OTA updates normally ?
8. How do I make back-ups of apps while the YT3 Pro IF I wanted to restore those apps later on on an UNrooted YT3 Pro ? I don't know why I'd want an UNrooted YT3 Pro in the future, but for instance, if I used Titanium Backup, that needs root right ?? For instance, if I want to restore data from a Titanium Backup on an UNrooted YT3 Pro, will it work ? Or can I use something else ?
Sorry about all the questions - I can't believe I've rooted and installed custom ROMs for 4 devices - for some reason this seems different to the others and it was a while ago !
Thanks in advance
Frenchdroid said:
Hi Joesnose and thanks for putting the instructions up (and of course, thanks to ionioni).
I have a couple of questions.
EDIT; oh pants, I have some more (possibly stupid) questions - just to be sure I know what I'm doing !
In the very first instructions about rooting:
1. I download the twrp.img.zip to my PC and unzip it to PC right ?
2. And the SuperSu goes in my ext SD card, not on the PC ?
3. I assume I must connect the YT3 Pro to the PC at some point ? When would that be ??
4. I don't understand instruction 7. It says type "fastboot boot twrp-2.8.7.0(6)-x90.img". Do I need to have that file downloaded or something ? What is twrp-2.8.7.0(6)-x90.img file ?
And what does it mean, "This is a live session TWRP has not been flashed to your tablet" ?
I can see that in the section about unencrypting the data partition that there is a file with a similar name to " twrp-2.8.7.0(6)-x90.img' but it has the words "data-enabled" in the fine name. I'm not sure what to do with this ??
5. At what point do I take a back-up of the original YT3 Pro stock image ? It's listed between 7 and 8 ? Do I do it right after 7 ? How do you make the back-up please ? And I guess I better store another copy somewhere safe, off the SD card too ?
6. If I just root this, can I then get OTA updates normally ? (without having to restore to stock).
7. And, if I do root and/or data unencryption, can the YT3 Pro be put back exactly how it was before changing anything ? Including it getting OTA updates normally ?
8. How do I make back-ups of apps while the YT3 Pro IF I wanted to restore those apps later on on an UNrooted YT3 Pro ? I don't know why I'd want an UNrooted YT3 Pro in the future, but for instance, if I used Titanium Backup, that needs root right ?? For instance, if I want to restore data from a Titanium Backup on an UNrooted YT3 Pro, will it work ? Or can I use something else ?
Sorry about all the questions - I can't believe I've rooted and installed custom ROMs for 4 devices - for some reason this seems different to the others and it was a while ago !
Thanks in advance
Click to expand...
Click to collapse
Ok let me see if I can help.
1. Yes
2. Yes
3.you must have the yt3 connected to your pc as the commands will be sent from your pc. Tablet must be in fastboot mode.
4. Yes sorry, when you extract the twrp.zip the file is called "twrp-2.8.7.6(0)-x90.img"
the twrp recovery is not flashed to your tablet it is just loaded temporarily, in a live session. Once rebooted it is gone. Normal recovery is not overwritten.
To run the unencrytption script one must be in twrp.
5. As soon as you get twrp loaded make a backup to either external sd or usb and yes not a bad idea to have a backup of your backup.
6. No
7. Yes, simply restore your backup before taking an ota update.
8. not sure about this one.
Indeed it appears like a lot of instructions but once you get into it its just like any other device.
Hope that helps.
Sent from my GT-N7105 using Tapatalk
Big thanks for the answers - makes more sense now, especially the bit about a recovery session as I'm used to installing clockwork and using it on the device.
You can install twrp to your device but only do this after you have made a backup from a live session, making sure of course that your backup contains the original recovery.
Sent from my GT-N7105 using Tapatalk
joesnose said:
You can install twrp to your device but only do this after you have made a backup from a live session, making sure of course that your backup contains the original recovery.
Sent from my GT-N7105 using Tapatalk
Click to expand...
Click to collapse
Oh, ? At what point does twrp get installed and how do you do that?
And is it obvious how to include the original recovery in the backup?
I thought I had it nailed!
Be cautious with the latest N910TUVS2EPG2.
You might not be able to downgrade the bootloader once its updated.
If you look back at the history of builds for the N910T you will see the following:
N910TUV U2 EPE3 = 6.0.1
N910TUV U2 DOK2 = 5.1.1
N910TUV U1 COG2 = 5.0.2
Pay attention to the U1 & U2 numbers.
Notice that you can upgrade and downgrade between 6.0.1 and 5.1.1 but cannot downgrade to 5.0.1
Both 6.0.1 and 5.1.1 have U2 in their build. In the past (at least on some devices) once these numbers change is when you cannot downgrade to a different number.
So whats my point? Look at the latest build. N910TUV S2 EPG2.
"S2" This very well could mean you can not downgrade to 5.1.1 and or PE3 6.0.1.
It also could mean that there have been some other bootloader changes.
There have been some reports that some on the latest N910TUVS2EPG2 have had trouble flashing TWRP.
Disclaimer: This info is not to be taken as golden fact. I'm just providing it so people can look out and be aware this has been the case in the past.
Since a lot of this information has not been confirmed and will not be confirmed by Samsung we can only go by past situations.
This has been indeed the case on both the Note 4 and the Galaxy Tab S2
To everyone that has indeed updated to this new Firmware version (N910TUVS2EPG2) please post any experiences from it.
Any problems? Any confirmed known changes. Anything.
Thanks!
I updated, and I was able to install twrp, root, and xposed. However, I have heard reports that twrp doesn't work for some people.
I updated yesterday. Took a couple of tries, but I got it to install twrp & supersu. Currently rooted on epg2
Can anyone point me in the direction of installing xposed on 6.0.1?
N910T here. Updated to EPG2 and I was able flash twrp, supersu v2.76 and custom ROM. I haven't tried rolling back to 5.1.1 bootloader yet.
Sent from my SM-N910T3 using Tapatalk
ayeitschris said:
N910T here. Updated to EPG2 and I was able flash twrp, supersu v2.76 and custom ROM. I haven't tried rolling back to 5.1.1 bootloader yet.
Sent from my SM-N910T3 using Tapatalk
Click to expand...
Click to collapse
Chocu1a said:
I updated yesterday. Took a couple of tries, but I got it to install twrp & supersu. Currently rooted on epg2
Can anyone point me in the direction of installing xposed on 6.0.1?
Click to expand...
Click to collapse
Any chance one of you could try rolling back to 5.1.1 or even PE3?
Regarding Xposed it should be the same one as PE3.
http://forum.xda-developers.com/note-4-tmobile/general/pe3-xposed-n910t-t3-marshmallow-t3406950
Also, How is PG2 running for you both? Anything worth mentioning?
DeeXii said:
Any chance one of you could try rolling back to 5.1.1 or even PE3?
Regarding Xposed it should be the same one as PE3.
http://forum.xda-developers.com/note-4-tmobile/general/pe3-xposed-n910t-t3-marshmallow-t3406950
Also, How is PG2 running for you both? Anything worth mentioning?
Click to expand...
Click to collapse
I upgraded to the new MM and everything its ok, twrp, (your root systemless) is ok and all is ok! let me rolling back to LP now, gime a 20 or 30 min...:good:
wilsonmd said:
I upgraded to the new MM and everything its ok, twrp, (your root systemless) is ok and all is ok! let me rolling back to LP now, gime a 20 or 30 min...:good:
Click to expand...
Click to collapse
Any update to this?
DeeXii said:
Any update to this?
Click to expand...
Click to collapse
Odined stock EPG2 tar, SuperSu systemmode, Xposed alt 86 wanam, TWRP 3.0.2-0, no issues. Great battery, runs smoother, no hiccups. :good:
DeeXii said:
Any update to this?
Click to expand...
Click to collapse
via Odin and i could not let me try flashing the LP bootloader and flash any room ......
How Downgrade your T-Mobile Note 4 (N910t) from MM (any version) to DOK2 Lollipop!
DeeXii said:
Any update to this?
Click to expand...
Click to collapse
IM NOT RESPONSABLE IF A HEART ATTACK OCCUR OR YOUR PHONE BLOW UP WITH ALL THE ROOF :silly:
IF YOU HAVE YOUR PHONE IN MM PG2 STOCK rooted with super SU systemless and last TWRP instaled (like me) YOU CAN DOWNGRADE TO D0K2 LOLLIPOP :
******REMEMBER Disable Reactivation lock (see picture below) and activate USB debuggin, Before DO this procedure!!*******
1-Download the DOK2 BOOTLOADER HERE https://www.androidfilehost.com/?fid=24269982087008410 and the D0K2 modem here: https://www.androidfilehost.com/?fid=24269982087008409 ( i did use 3.0.9 Odin) >>>>>>>>>thanks to @xoxo_xdagirl91 for post the links!
2- Download The 5.1.1 rom here: http://forum.xda-developers.com/note-4-tmobile/development/rom-maximum-ovrdrive-v15-1-1-t3196653 its an awsome rom by @OvrDriVE and so Thanks for that!
3-Put the ovrDrive 5.1.1 rom into the external sd card together with the upgrade. (because need erase all in the internal memory, remember, make a back up of your data in the phone or in the internal memory if you want).
4-now GO to your TWRP and wipe cache-dalvik-system-data-INTERNALmemory x3 ..........DONT TOUCH YOUR EXTERNAL SD, REMEMBER THE OVRDRIVE 5.1.1 ROM IS THERE!
******REMEMBER WHEN YOU ERASE YOUR INTERNAL MEMORY JUST REBOOT AGAIN IN RECOVERY, each time you erase yor internal memory, when reboot in TWRP you see the warning and said that you need to click in "never show this screen during boot again" just click there and swipe to allow Modifications or the stock recovery will rewrite again. TURN OF YOUR PHONE!
5-GO TO DOWNLOAD MODE TO USE Odin and flash the 5.1.1 bootloader FIRST, WHEN FINISH, Flash the modem ..... REMEMBER: put the bootloader in the BL section FIRST AND FLASH & FOLLOWING THE modem in the CP section of odin
6- When finish the step 5, go to your recovery TWRP>install>go to ext sd>flash the ROM first, when finish, wipe dalvik, cache and reboot again in TWRP
7- Just flash the othe part of the rom........the upgrade zip file, when finish just reboot the system aaaaaaaand
WALAAAAAHHHHHH!!!!!!
I DID IT EXACTLY AS DIRECTED AND I HAVE A CLEAN OVRdrive
rooted rom in 5.1.1. Now you can flash via ODIN the original firmware on 5.1.1:good::good:
Just wanted to share my experience for posterity. Here's what I did (and promptly undid). I don't know much about anything, so feel free to laugh and/or point out where I went wrong:
1. Installed the stock N910TUVS2EPG2 from Odin on my 910T.
2. Flashed SuperSU System Mode (which is wrong, I think...should have done systemless, right?)
3. Got the scary yellow "set warranty bit kernel" message and nothing else on the screen.
4. After a couple of attempted reboots, I got the message saying something to the effect of unauthorized software being installed and I'd have to send it in to get it repaired.
5. After a couple of reboots (pulled the battery and tried turning it on again a couple of time), it went through a full boot. After the boot was complete, I got another message within the OS about unauthorized software.
6. Opened SuperSU, unrooted and restored stock recovery.
Everything seems fine now, like nothing ever happened. Calls, data, wifi, and all that are working. I'll wait for the experts to chime in before I attempt this again. I'm just happy it works...at least as far as I can tell.
mykos said:
Just wanted to share my experience for posterity. Here's what I did (and promptly undid). I don't know much about anything, so feel free to laugh and/or point out where I went wrong:
1. Installed the stock N910TUVS2EPG2 from Odin on my 910T.
2. Flashed SuperSU System Mode (which is wrong, I think...should have done systemless, right?)
3. Got the scary yellow "set warranty bit kernel" message and nothing else on the screen.
4. After a couple of attempted reboots, I got the message saying something to the effect of unauthorized software being installed and I'd have to send it in to get it repaired.
5. After a couple of reboots (pulled the battery and tried turning it on again a couple of time), it went through a full boot. After the boot was complete, I got another message within the OS about unauthorized software.
6. Opened SuperSU, unrooted and restored stock recovery.
Everything seems fine now, like nothing ever happened. Calls, data, wifi, and all that are working. I'll wait for the experts to chime in before I attempt this again. I'm just happy it works...at least as far as I can tell.
Click to expand...
Click to collapse
Those scary red and yellow warnings are standard. Just lets you know the phone has been modified, nothing to worry about. To keep it simple, you can use either systemmode or systemless. And of course you will get a message saying the phone is using an unauthorized software, because you just flashed a custom ROM. Haha. That only pops up when you check for system updates.
xdapowerapps said:
Those scary red and yellow warnings are standard. Just lets you know the phone has been modified, nothing to worry about. To keep it simple, you can use either systemmode or systemless. And of course you will get a message saying the phone is using an unauthorized software, because you just flashed a custom ROM. Haha. That only pops up when you check for system updates.
Click to expand...
Click to collapse
Thanks for the response! I gave it another shot this morning.
Used CF Auto Root, installed TWRP, no issues. I was having random restarts on non-stock roms, but none on this one even with rigorous testing.
xdapowerapps said:
Those scary red and yellow warnings are standard. Just lets you know the phone has been modified, nothing to worry about. To keep it simple, you can use either systemmode or systemless. And of course you will get a message saying the phone is using an unauthorized software, because you just flashed a custom ROM. Haha. That only pops up when you check for system updates.
Click to expand...
Click to collapse
They say that this compilation can not Downgrade "N910TUVS2EPG2" to 5.1.1 o another 6.0.1 compilation
IS TRUE..!!
mykos said:
Thanks for the response! I gave it another shot this morning.
Used CF Auto Root, installed TWRP, no issues. I was having random restarts on non-stock roms, but none on this one even with rigorous testing.
Click to expand...
Click to collapse
Glad that everything is running smooth for you! I normally like to run stock, install TWRP, root, and then tweak whatever I don't like. Right now I'm running an S7E Port located HERE. Process requires a little work; 1st) flash the ROM, 2) flash kernel, 3) flash data fix, 4) ??? , 5) profit. :laugh:
---------- Post added at 05:29 PM ---------- Previous post was at 05:25 PM ----------
kiikez said:
They say that this compilation can not Downgrade "N910TUVS2EPG2" to 5.1.1 o another 6.0.1 compilation
IS TRUE..!!
Click to expand...
Click to collapse
That is correct; presently you cannot downgrade from EPG2 to a lower version due to security policy changes. Maybe there will be a workaround soon; however, I have 0 issues on EPG2. :good:
xdapowerapps said:
Glad that everything is running smooth for you! I normally like to run stock, install TWRP, root, and then tweak whatever I don't like. Right now I'm running an S7E Port located HERE. Process requires a little work; 1st) flash the ROM, 2) flash kernel, 3) flash data fix, 4) ??? , 5) profit. :laugh:
---------- Post added at 05:29 PM ---------- Previous post was at 05:25 PM ----------
That is correct; presently you cannot downgrade from EPG2 to a lower version due to security policy changes. Maybe there will be a workaround soon; however, I have 0 issues on EPG2. :good:
Click to expand...
Click to collapse
Conflicting reports on here. I haven't tried this myself yet but THIS post states a successful downgrade. YMMV.
mykos said:
Just wanted to share my experience for posterity. Here's what I did (and promptly undid). I don't know much about anything, so feel free to laugh and/or point out where I went wrong:
1. Installed the stock N910TUVS2EPG2 from Odin on my 910T.
2. Flashed SuperSU System Mode (which is wrong, I think...should have done systemless, right?)
3. Got the scary yellow "set warranty bit kernel" message and nothing else on the screen.
4. After a couple of attempted reboots, I got the message saying something to the effect of unauthorized software being installed and I'd have to send it in to get it repaired.
5. After a couple of reboots (pulled the battery and tried turning it on again a couple of time), it went through a full boot. After the boot was complete, I got another message within the OS about unauthorized software.
6. Opened SuperSU, unrooted and restored stock recovery.
Everything seems fine now, like nothing ever happened. Calls, data, wifi, and all that are working. I'll wait for the experts to chime in before I attempt this again. I'm just happy it works...at least as far as I can tell.
Click to expand...
Click to collapse
how did you flashed the super su systemless?
Cannot root or odin twrp after latest (pg2) update. Odin to pe2 and everything is back to normal.
xdapowerapps said:
Glad that everything is running smooth for you! I normally like to run stock, install TWRP, root, and then tweak whatever I don't like. Right now I'm running an S7E Port located HERE. Process requires a little work; 1st) flash the ROM, 2) flash kernel, 3) flash data fix, 4) ??? , 5) profit. :laugh:
---------- Post added at 05:29 PM ---------- Previous post was at 05:25 PM ----------
That is correct; presently you cannot downgrade from EPG2 to a lower version due to security policy changes. Maybe there will be a workaround soon; however, I have 0 issues on EPG2. :good:
Click to expand...
Click to collapse
Could you list the exact steps. I would like to try that ROM as well, considering we don't have any MM ports for our T-Mo Note 4. How is it working so far?
Thanks
krishelnino said:
Could you list the exact steps. I would like to try that ROM as well, considering we don't have any MM ports for our T-Mo Note 4. How is it working so far?
Thanks
Click to expand...
Click to collapse
Sure bud.
1) Download the M6 ROM from Dev-Host or from MediaFire.
Put this file in your external SD card.
2) Download the BeastMode kernel.
Put this file in your external SD card.
3) Download the Data Fix - MM_DataFixs7rebootmenu.zip.
Put this file in your external SD card.
4) Boot into recovery. Make a backup of your current ROM just in case. :fingers-crossed:
5) Go into Advanced Wipe (if you're using TWRP) and wipe dalvik, system, data, cache, internal storage (or whichever options are available in the recovery you are using).
6) Flash M6 Rom from Step 1. Do not restart.
7) Flash kernel from Step 2. Do not restart.
8) Flash data fix from Step 3.
9) Now wipe cache and dalvik cahe. Restart.
Once you restart, it will look like your phone crashed or is stuck in a bootloop, it's not. Let it sit there for about 10-15 minutes and it will boot into the setup screen. Good luck. :good:
We have the first port and root for this highly unpopular BLU phone.
BLU DASH M 2 - Carliv Touch Recovery 6.6.1 aka CTRI have managed to replace the stock recovery and still keep the stock system since there are no customs roms at the moment. The recovery doesn't require you to be rooted but rooting is possible after flashing or booting this rom. Don't fall for the fake Dash files on youtube, I have downloaded them all and they are copies of similar phones and don't work.. This one is ported over from the D070Q by Carliv.
It will not flash a full custom rom but will flash ZIPs so you can root, recover, flash partitions and hopefully pave the way for a TWRP . I do have a TWRP ported over to the BLU Dash M 2 but the touch doesn't work so you can't pass the first swipe screen.
DOWNLOAD from uploadfiles.io @ https://ufile.io/8oc6k
Instructions
- Make sure to backup any important files, this will wipe your data pics, vids, etc..
- Enable OEM unlock under developer options and power down phone
- Boot to stock recovery by holding PWR + VOL UP
- In recovery choose "Reboot to Bootloader" ( aka fastboot )
- You should now be at a blank screen with Fastboot mode: at the bottom
Open your terminal and type the following code, obviously replacing your paths with the correct ones.
fasboot devices < --- will return a serial number or something to indicate connection is OK
fastboot oem unlock <--- will prompt your phone screen to accept unlock request, chose VOL Up to accept and make sure it says "Unlock pass" at the bottom
For testing only
fastboot -c "lge.kcal=0|0|0|x" boot CTR_6.6.1_BLU_DASH_M2_D090U.img
For permanent flash
fastboot flash recovery CTR_6.6.1_BLU_DASH_M2_D090U.img
Don't power down, instead boot in the same recovery
fastboot -c "lge.kcal=0|0|0|x" boot CTR_6.6.1_BLU_DASH_M2_D090U.img
Inside CTR select Wipe cache, Dalvik cache, Userdata / Data.
Select Reboot Phone from CTR menu and when asked to patch , Select " NO "
On first reboot it will reboot twice, then boot the stock system as if it was a factory reset.
This now paves the way for root with Magisk. See my post after this for rooting Blu Dash M2.
Enjoy !
RESERVED
Hey Thank you, got it working. Had to alter it a bit though. Had to select "Yes" for the fix as mine was restoring the old recovery.
Also when I followed your method, the system was not mounting the internal storage.
So I didn't wipe the data and used "Yes" when rebooting and the recovery is good.
I'll be looking out for the root constructions.
Great tutorial though.
73Hn said:
Hey Thank you, got it working. Had to alter it a bit though. Had to select "Yes" for the fix as mine was restoring the old recovery.
Also when I followed your method, the system was not mounting the internal storage.
So I didn't wipe the data and used "Yes" when rebooting and the recovery is good.
I'll be looking out for the root constructions.
Great tutorial though.
Click to expand...
Click to collapse
That will not work for root because Magisk needs the original boot rom. I'm sure it worked for you and that's a good start but wiping the partitions in order does work as well, I probably just left something out or got the order wrong. It's important we don't use CTR to patch because then Magisk complains about boot img being aleady patched and doesn't work.
Anyway you get the idea, it took me a few tries as well but in the end I managed to keep all 3 features intact, the stock rom + CTR + root. If you need to start again you don't need the full rom or sp flash, just flashing system.img to sytem partition works to restore everything.
I'm hoping to find the source code to the kernel and make a TWRP with touch working but the CTR is the only thing we have so far. It does flash zips just not full operating systems. It also flashes boot and recovery partitions.
Thanks, I can restore and try again. Do you have the tutorial for the magisk to root?
73Hn said:
Thanks, I can restore and try again. Do you have the tutorial for the magisk to root?
Click to expand...
Click to collapse
I think most can figure out Magisk from here, the real hurdle was the lack of a recovery because the stock rom doesn't allow Magisk to be flashed.
Thanks, I already started checking in on it... I'll update here once I get through.
How to Root Blu Dash M 2 with Magisk
I have managed to root the stock system using Magisk. The stock recovery will not let you do this, as usual ignore the garbage on youtube and personal blogs, they're giving false info and fake files. This method works and I'm the first user who ported CTR 6.6 to allow for this.
DOWNLOAD Magisk from developer https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
FOLLOW THE ABOVE POST to replace stock recovery with CTR 6.6
Instructions
- Follow first post to install CTR 6.6 recovery and reboot a couple of times to make sure it stuck.
- Enable OEM unlock under developer options and power down phone
- Boot to new CT 6.6 recovery by pressing PWR + VOL UP
- In recovery choose "Install Zip" and choose the "Magisk.zip" from your /SDCARD
Magisk installer will launch and if you did everything right, complete without errors.
- Select Reboot Phone from CTR menu and when asked to patch , Select " NO "
Phone should now reboot twice and have Magisk installed. I have verified root by deleting protected files like default.prop and gave Root Explorer permanent root access. If something doesn't work just find the right sequence. I believe it was flash system, flash recovery. wipe partitions. flash magisk
Enjoy !
The only thing left do now is find the Blu kernel source code for the M2 so a working TWRP can be compiled from scratch, then any MT6580 rom should be flashable.
Perfectly... Got it working using your same method after reinstalling the firmware... only difference was.
After installing recovery and booting into it, I then installed Magisk via adb sideload.
Confirmed root works.
Thank you very much for your patience and assistance
graciaaas
romish said:
How to Root Blu Dash M 2 with Magisk
I have managed to root the stock system using Magisk. The stock recovery will not let you do this, as usual ignore the garbage on youtube and personal blogs, they're giving false info and fake files. This method works and I'm the first user who ported CTR 6.6 to allow for this.
DOWNLOAD Magisk from developer https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
FOLLOW THE ABOVE POST to replace stock recovery with CTR 6.6
Instructions
- Follow first post to install CTR 6.6 recovery and reboot a couple of times to make sure it stuck.
- Enable OEM unlock under developer options and power down phone
- Boot to new CT 6.6 recovery by pressing PWR + VOL UP
- In recovery choose "Install Zip" and choose the "Magisk.zip" from your /SDCARD
Magisk installer will launch and if you did everything right, complete without errors.
- Select Reboot Phone from CTR menu and when asked to patch , Select " NO "
Phone should now reboot twice and have Magisk installed. I have verified root by deleting protected files like default.prop and gave Root Explorer permanent root access. If something doesn't work just find the right sequence. I believe it was flash system, flash recovery. wipe partitions. flash magisk
Enjoy !
Click to expand...
Click to collapse
Thank you very much! You do not know how much I needed to be root! I thought that this device was impossible to root. I really am very grateful. Friend was asking me if you could adapt the custom Slimrom rom for this device? because all the storage of this one takes the system, it would be of great help for all the users of this phone, I do not know if you can or are interested, but I thank you in advance
romish said:
We have the first port and root for this highly unpopular BLU phone.
DOWNLOAD from uploadfiles.io @ https://ufile.io/bj9kk
Enjoy !
Click to expand...
Click to collapse
Hi, can you provide a download link that doesn't require you to get a premium account to access the file. It's against XDA rules.
kirito9 said:
Hi, can you provide a download link that doesn't require you to get a premium account to access the file. It's against XDA rules.
Click to expand...
Click to collapse
It is not premium, the file just expired so the site will keep it on line for a fee. I'll upload it again.
romish said:
It is not premium, the file just expired so the site will keep it on line for a fee. I'll upload it again.
Click to expand...
Click to collapse
Try this one.. if the host tries to replace it with the original let us know and one of the others who have the file will re upload it to another host. I don't feel like signing up anywhere so that is why I use this host.
https://ufile.io/8oc6k
https://ufile.io/8oc6k
https://ufile.io/8oc6k
kevoncrush said:
Thank you very much! You do not know how much I needed to be root! I thought that this device was impossible to root. I really am very grateful. Friend was asking me if you could adapt the custom Slimrom rom for this device? because all the storage of this one takes the system, it would be of great help for all the users of this phone, I do not know if you can or are interested, but I thank you in advance
Click to expand...
Click to collapse
All 'ya 'all are welcome . Unfortunately I can't go any further because there is no source for the kernel so TWRP won't work because there is no touch to get past the first screen. Otherwise if it. did slim rom would flash without any problems, its just these older recoveries don't support a few things that TWRP has to make flashing full roms successful. If someone has source files for the BLU Dash M2 let me know.
I'll just let you guys know, I managed to make a pretty good custom rom with root only by deleteing everything but the core OS. I don't recommend this for everyone but I did get rid of just about everything and made this 6.0 more like 4.4 .. I got it to the point where even the phone and SMS didn't work and the google framework was deleted, then slowly began adding my approved versions of apps. Now its totally de googled but again I realize this isn't for everyone. I just wanted a small rom with camera ad GPS and those are working fine for me.
Custom recovery link taken down again
Could someone please upload the custom recovery again?
[Port] [Recovery] BLU DASH M 2
I tried to fast boot as peryour instructions but I get the error: cannot load ' ctr_6.6.1 etc. :crying:
Please try this link, if you have a better locarion to store it please do so and reshare as this link is only valid for 2 days.
ctr_6.6.1_blu_dash_m2_d090u.img
---------- Post added at 05:08 AM ---------- Previous post was at 05:01 AM ----------
If that recovery does not work, try this one. I have two of different sizes and can't remember which one i used.
recovery.img
Download link
Please repost the download link