Related
Hi folks. I have tried the Odin process three times to try to get CWM functioning on my I/O tab with no luck.
The actual Odin process seems to work fine; however, when I reboot the tab to enter recovery mode; I never get the recovery option. I only have the USB symbol and the downloading option. Also, in the upper left corner, I have:
Fastboot USB download protocol
bootloader version unknown
baseband version %s
serial number:
lock state unlocked
What am i missing? Can the I/O tab use CWM?
Thanks!!
I had the same thing, but when I am trying to root the device it just lock on boot screen. I am not a dummy but something is wrong where several users have diffrent symptoms. I would wait until further development is done. This is still a little shaky.
Odin CWM doesn't work for some reasons ..
Use this post to get rooted
http://forum.xda-developers.com/showpost.php?p=15735928&postcount=2
Follow the instructions carefully !!
Download CWM and do an Install on CWM (it will install 4.0.0.4)
copy the required files to the root directory /sdcard/ (main directory if you don't know)
-Get the roms from HERE
-Get the su_busybox_misc-sam_tab_10.1-051511 HERE
Flash in the ROM 1st .. the apply the SU update (in RECOVERYMOD BEFORE you reboot)
Data / wipe
THEN REBOOT
I missed that 2nd update zip .. and trust me its a pain to get it rooted after that ..
The same procedure will not work again once you're on TW3.1 rom .. you will need an image of the system files and NVflash now..
BTW if you can do NVflash .. then I can send you the image files for 3.1TW rooted ..
fgarcia25 said:
I had the same thing, but when I am trying to root the device it just lock on boot screen. I am not a dummy but something is wrong where several users have diffrent symptoms. I would wait until further development is done. This is still a little shaky.
Click to expand...
Click to collapse
Ha .. I have 3 IO to play with (from friends)..
1st one is rooted out of the box ..
2nd one cannot communicate on FASTBOOT
3rd one does everything nicely (thats the one I had the image extracted with NVFlash)
I'll say it nicely before someone comes to say it rudely, this probably belongs in a general section rather than the development section (that is, until you develop a method to get around the restriction you've found )
Workaround method
http://forum.xda-developers.com/showpost.php?p=16196597&postcount=3
Plus I have the images to go with in case you brick yours
bill.allrobots.org said:
I'll say it nicely before someone comes to say it rudely, this probably belongs in a general section rather than the development section (that is, until you develop a method to get around the restriction you've found )
Click to expand...
Click to collapse
If you have fastboot working, then rooting is as simply as 'fastboot boot [cwm recovery filename].img'
I spent a long time getting fastboot to work, but the only fix was to finally download PDANET software to my PC and install it while it was connected to my tab. After that I got fastboot working.
Fastboot made the rooting process 100% easier. You can root any stock ROM with it and not have to reflash to 3.0.1.
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums and Read THIS
Moving to General
I had the same problem with my I/O. I finally got a recovery option. What I did was flash the Euro version of TW located in the development section (which is buggy as ****).. After that I Installed CWM and flashed pershoot's root tools. Then I flashed the latest TW Rom. Everything is running smoothly, despite the samsung apps fc. Be weary of the disclaimers located on all the sections I have suggested. All of these steps are at your own risk...
Odin worked on my I/O tab after i put TW on it. I had to boot the tab into CWM via fastboot from a mac
Hello every one
After i try the new Android v4.2.1 rom by randomblame i want to get back to v4.1.2 but i did not format data this is what i think that brick my A500
So i recovered my device via EUUs_SBK_Acer_A500_1.016.05_COM_GEN1
but after that i couldn't flash any ics rom or ics bootloader
every time i try to flash ics bootloader with "blackthund3r_A500_APX_Flash_Tool_v0."@ the device stock during the process and stock in apx mod so i have to recover it again and so on
i have try : BabSector to format partition and try Afterota after th euus recovery but without luck
i can't even flash ics on hc bootloader "lightspeed 4.8"
now i'm running hc 3.2.1 rom by civato
what i'm doing wrong ? Help Please
I'm really missing CM10
bad English ....sorry
haytham-88 said:
Hello every one
After i try the new Android v4.2.1 rom by randomblame i want to get back to v4.1.2 but i did not format data this is what i think that brick my A500
So i recovered my device via EUUs_SBK_Acer_A500_1.016.05_COM_GEN1
Click to expand...
Click to collapse
So you can boot into the OS OK??
Did you root it?
You may have to take an OTA or update.zip to 3.1 first and flash the v8 from that as I'm unsure it will work from 3.0.1
but after that i couldn't flash any ics rom or ics bootloader
every time i try to flash ics bootloader with "blackthund3r_A500_APX_Flash_Tool_v0."@ the device stock during the process and stock in apx mod so i have to recover it again and so on
Click to expand...
Click to collapse
is their an "apx device" listed in hardware and printers or in your pc system tray?
do you get "acer apx mode" displayed on your tab?
now i'm running hc 3.2.1 rom by civato
Click to expand...
Click to collapse
go to the root guide in my sig and Make absolutely certain you do the first 4 steps in that guide.
d/l the latest apx Flash manager tool v 1.0.2 and use the bundle market in it to install bundle #17
OR
use civato's nvflash package instead as this requires your tab to be in apx mode (black screen/pwr lite on) to work AND will give you a more specific error if it fails.
Once the flash is complete BOOT STRAIGHT TO CWM and flash your cm10.1 rom
THEN Do a factory/data reset and enable wipe of /data/ media (in mounts/storage menu) wipe cache and dalvik cache too. Reboot to cm 10.1!!!
Please do all the steps in the order they are given -
If "it doesn't work" we will need you to tell us what is or isn't happening and where in the process it fails!!!
Good luck
Thank you for reply
dibb_nz said:
So you can boot into the OS OK??
Did you root it?
You may have to take an OTA or update.zip to 3.1 first and flash the v8 from that as I'm unsure it will work from 3.0.1
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Yes I can
It's rooted because it is a custom ROM with CWM Recovery 1.3.4 by Thor
Is it OK to flash the ICS Bootloader from HC 3.2.1 "Civato-FLEXSTRIKER-HC.3.2.1 R6-BASE"?
is their an "apx device" listed in hardware and printers or in your pc system tray?
do you get "acer apx mode" displayed on your tab?
Click to expand...
Click to collapse
Yes their is an "apx device"
and my tab shows "entering apx mode..." or something like that ! with ACER logo
go to the root guide in my sig and Make absolutely certain you do the first 4 steps in that guide.
d/l the latest apx Flash manager tool v 1.0.2 and use the bundle market in it to install bundle #17
OR
use civato's nvflash package instead as this requires your tab to be in apx mode (black screen/pwr lite on) to work AND will give you a more specific error if it fails.
Once the flash is complete BOOT STRAIGHT TO CWM and flash your cm10.1 rom
THEN Do a factory/data reset and enable wipe of /data/ media (in mounts/storage menu) wipe cache and dalvik cache too. Reboot to cm 10.1!!!
Please do all the steps in the order they are given -
If "it doesn't work" we will need you to tell us what is or isn't happening and where in the process it fails!!!
Good luck
Click to expand...
Click to collapse
"USB drivers from the Android SDK" on step 1 maybe that is what I need
So I'll give it a try and tell you what happens.
And again thank you for your help.
Well..
I followed your root guide and used Civato's nvflash package, lots of things happened.
file no 1 is the first result
then file no 2 , here is where I get stuck in apx mode again !!
errors i get :
error formating partition 4
error formating partition 6
The thing is, not every time I try to recover my tab it works
I succeed only once of every 15 tries to recover my tab.
so maybe some partitions are messed up or something.
One time, I tried to flash Civato's nvflash package again , and after few times the bootloader was flashed correctly, but the recovery wasn't !!
So, I tried to use fastboot to flash the recovery ... and it went O.K
After that, I restarted to recovery, formated data (factory reset) , cache , delvik cash, flashed the rom, rebooted the tab ...... but nothing happened !!
and i'm stuck here
I've done lots of searching around the forums and most of them recommend BabSector or tdv4_rollback_rom or EUUs .
only EUUs are working, and even that would work one time of around 10 to 20 tries.
do i have to flash the primery kernel via fastboot , and if so, how to get the kernel from the rom?
thanks in advance
haytham-88 said:
Well..
I followed your root guide and used Civato's nvflash package, lots of things happened.
file no 1 is the first result
then file no 2 , here is where I get stuck in apx mode again !!
errors i get :
error formating partition 4
error formating partition 6
The thing is, not every time I try to recover my tab it works
I succeed only once of every 15 tries to recover my tab.
so maybe some partitions are messed up or something.
One time, I tried to flash Civato's nvflash package again , and after few times the bootloader was flashed correctly, but the recovery wasn't !!
So, I tried to use fastboot to flash the recovery ... and it went O.K
After that, I restarted to recovery, formated data (factory reset) , cache , delvik cash, flashed the rom, rebooted the tab ...... but nothing happened !!
Click to expand...
Click to collapse
Boot to fastboot mode
Fastboot erase userdata, cache, system and flexrom - use separate command for each partition, note any write errors and post back.
Fire up apxflash tool....you MUST dump, save then use your tabs BCT when u get to that window - this should repair the bct error shown in the 2nd text file.
Also tick "show nvflash commands " this will show any read/write or partition errors..
If you get partition errors run babsector (d/l in the root guide) and follow the steps I posted there.
Boot directly to recovery and try flashing a rom again
I've done lots of searching around the forums and most of them recommend BabSector or tdv4_rollback_rom or EUUs .
only EUUs are working, and even that would work one time of around 10 to 20 tries.
do i have to flash the primery kernel via fastboot , and if so, how to get the kernel from the rom?
thanks in advance
Click to expand...
Click to collapse
No u shouldn't have to flash a kernel its included in the rom.
A full and complete erase is required first
(If there are errors here like can't read/write or bad data....your tab is toast) if not,
The bct error must be repaired next, else your tab won't flash any rom at all, even if the tool says PASS
Then reset your partitions with babsector.far
(Any errors like those listed above....your tab is toast)
With all the errors you're having its pointing to a faulty chip, flashing should not be this problematic.
Be sure to follow the direct order of repair....otherwise you'll be compounding errors
Sent from my A500 using Tapatalk 2
Sorry for my late reply
I didn't run apxflash tool I have try something before that I have flash a HC rom over the ICS bootloder "it is wrong I know" but it went OK and the tab boot to the rom!!!!!!!!!
So now I have ICS bootloader with HC rom. what is going on ??
I have a new long work "13 hour" and I can't spend alot of time with my tab but I want to understand what is wrong with my tab
I'm really thankful for your time.
haytham-88 said:
Sorry for my late reply
I didn't run apxflash tool I have try something before that I have flash a HC rom over the ICS bootloder "it is wrong I know" but it went OK and the tab boot to the rom!!!!!!!!!
So now I have ICS bootloader with HC rom. what is going on ??
I have a new long work "13 hour" and I can't spend alot of time with my tab but I want to understand what is wrong with my tab
I'm really thankful for your time.
Click to expand...
Click to collapse
Well, thats different!!!
Are you running stock HC or is it a custom one?
Which recovery are you using?
Download Acer Recovery Installer from the market, it will tell you your bootloader version. You will need root priveleges to run this
dibb_nz said:
Well, thats different!!!
Are you running stock HC or is it a custom one?
Click to expand...
Click to collapse
A custom rom, Civato-flexstriker-hc.3.2.1 r6
Which recovery are you using?
Click to expand...
Click to collapse
CWM Recovery v5.5.0.x(thor2002ro/digetx rev1.7.3)
Download Acer Recovery Installer from the market, it will tell you your bootloader version. You will need root priveleges to run this
Click to expand...
Click to collapse
Bootloader Version: 0.03.14-MUL
and i can acsses Skrilax_CZ's bootloader V8 bootmenu Mode and all of it's functions
i think that i did not understand the bootloader thing yet!!!
haytham-88 said:
A custom rom, Civato-flexstriker-hc.3.2.1 r6
CWM Recovery v5.5.0.x(thor2002ro/digetx rev1.7.3)
Bootloader Version: 0.03.14-MUL
and i can acsses Skrilax_CZ's bootloader V8 bootmenu Mode and all of it's functions
i think that i did not understand the bootloader thing yet!!!
Click to expand...
Click to collapse
ok lets start with the bootloader and why we need it...
On most android devices your first step to flashing a custom rom is to root so you can flash a custom recovery....
With our Acer Tabs since HC 3.2 the bootloader is locked...meaning even having root access did not give us the ability to 'flash' a custom recovery - its just not possible....the only way to do it is with the "patched" bootloader - I don't know how the magic works, but the devs managed to find a way to 'trick' the system into allowing their version of "patched bootloader" to be installed which would allow the flashing of a custom recovery....and there is a very specific way of getting this patched or unlocked bootloader onto your tab....this is with a program called "nvFlash" which runs via "apx mode" or "acer download mode" using our tabs unique ID, the cpuid.....to make it even easier The devs created a "package" which will nvFlash the patched bootloader AND a custom recovery all in one go!! Once we'd done that all we needed to do was to boot straight to recovery and flash our desired ICS or JB rom!!!
In the beginning, way back in the day....some folks weren't at all comfortable going to these lengths just to have a custom rom, so some of the rom cooks gave us the choice to upgrade to the patched bootloader or to stick with the HC bootloader, by flashing a custom HC kernel after the bootloader flash....this is what you were alluding to earlier??
Most roms now only work with the patched bootloader i.e. skrilax_cz 3.14 MUL -v8
keep in mind these are ICS and JB roms...
I hope that provides a bit more understanding on the bootloader thing and why we need it...
Now back to your original problem, not sure why you cannot flash a JB rom, have you tried it again??? I just cannot think of anything that would prevent you from flashing anything except an HC Rom - You might wanna ask the question in the JB rom thread...there might have been specific steps you needed to take to downgrade from 4.2 (can't think what though) or others may have posted similar problems...sorry couldnt help you out ....
...but let us know how you get on, good luck!!
Finally I have moved from HC to JB and that is how :
- ubdating the bootloader from v8 to v9
- nothing changed trying to flash any rom I already have
- then and I don't know why I download an Android 4.3.1 from TegraOwners forums [WIP]A500/A501 JB-MR2(4.3.1) - V8t6
link http://forum.tegraowners.com/viewtopic.php?f=9&t=1312
flash the rom and everything went OK !!!
Finally Fixed
Finally I have moved from HC to JB and that is how :
- ubdating the bootloader from v8 to v9
- nothing changed trying to flash any rom I already have
- then and I don't know why I download an Android 4.3.1 from TegraOwners forums [WIP]A500/A501 JB-MR2(4.3.1) - V8t6
link http://forum.tegraowners.com/viewtopic.php?f=9&t=1312
flash the rom and everything went OK !!!
I have had many android devices and almost all of them i have turned to this site to either make them better or give them renewed life. The nexus 7 is my first tablet and due to previous experience i came straight here to us and upgrade to the kernals and firmwares off the perfectionists i have come to know! (thank you all for the many years of making my devices as great and if not better than more recent mobile devices!)
Today i got my nexus seven and i downloaded: [Google Nexus 7 TOOLKIT V4.0.0] Drivers, Backup, Unlock, Root, CWM, Flash + MUCH MORE
This i belive allowed me to unlock my boot loadeder and root my device (althoug i have no way to confirm rooting!).
After unlocking bootloader and rooting i attempted to install a custom rom (Smooth rom 4.3) using given instructions to use JRomflasher from there page. Only problem is, jrom does not find zipped or unzipped rom leaving me without an os! Could one of you nice guys help me out! I had a wifi 4.2.1 tab if that could help! kind regards, Alex!
Re: Please help a girl in need!
Download a kernel onto your computer as well as a ROM. Open a command prompt shift +right click. Plug the n7 in to the computer. Type "fastboot reboot recovery" without the quotations and press enter. Your device should boot into Cwm/twrp or whatever recovery in installed. Using windows explorer, Drag the ROM and kernel to your n7. First flash the kernel, then the ROM, then reboot. I know cause this happened to me too.
NEXUS 7:
Unlock/Root
Prime D
M-Kernel
PimpMyROM
Cheers for advice but my device still refuses to acknowledge an updates there! in rar/zip or unzipped format! it just loops me back to start screen and i fail to do it all over again! Through experience i believe its my version of clockwork mod gone wrong as it gives me the option to install zip from sd card but continuoslly fails! what am i doing wrong?
In the future please use a title that is indicative of your actual problem and will be found and possibly help someone with a similar issue who does a search before posting. Also, people in here are helpful to all, regardless of gender. Thanks.
frap129 said:
Download a kernel onto your computer as well as a ROM. Open a command prompt shift +right click. Plug the n7 in to the computer. Type "fastboot reboot recovery" without the quotations and press enter. Your device should boot into Cwm/twrp or whatever recovery in installed. Using windows explorer, Drag the ROM and kernel to your n7. First flash the kernel, then the ROM, then reboot. I know cause this happened to me too.
NEXUS 7:
Unlock/Root
Prime D
M-Kernel
PimpMyROM
Click to expand...
Click to collapse
Flashing a kernel before you flash a ROM would have no effect at all because nearly all ROMs generally overwrite the boot partition. (I dunno, maybe there are Aroura installers that avoid installing boot partitions). I think you meant to say "Flash ROM, then flash kernel".
@OP Use the toolkit to restore the stock rom, and then immediately
- use the recovery to make a backup and
- copy the backup to your PC
after you have done that, only then you should start considering custom ROMs and kernels. You might even want to rehearse a couple of disaster scenarios so that you are familiar with the custom recovery you have installed.
Because of the lack of an external SD card, there are plenty of folks who - due to unfamiliarity with how things work - not only screwed up an installation, but also deleted all their backups on the *emulated* SD card.
good luck
also do what the above poster said, and I find using either goo manager or rom manager probably the easiest way for a noob to flash some roms
so use your tool kit to "return to stock" ( hopefully it has that option) then root it, then install goo manager or rom manager to automate rom installs for you
Miami_Son said:
In the future please use a title that is indicative of your actual problem and will be found and possibly help someone with a similar issue who does a search before posting. Also, people in here are helpful to all, regardless of gender. Thanks.
Click to expand...
Click to collapse
ok sorry! do you have any input though because atm i have a TABLET THAT ONLY SAYS GOOGLE!, SORRY TO SOUND TROLL!
Re: Please help a girl in need!
bftb0 said:
Flashing a kernel before you flash a ROM would have no effect at all because nearly all ROMs generally overwrite the boot partition. (I dunno, maybe there are Aroura installers that avoid installing boot partitions). I think you meant to say "Flash ROM, then flash kernel".
Click to expand...
Click to collapse
No, this happened to me and when i tried to flash a ROM it said "Flash Failed" so i tried to flash a kernel first, then ROM and it worked.
NEXUS 7:
Unlock/Root
Prime D
M-Kernel
PimpMyROM
frap129 said:
No, this happened to me and when i tried to flash a ROM it said "Flash Failed" so i tried to flash a kernel first, then ROM and it worked.
Click to expand...
Click to collapse
A million different things could have caused that.
You don't need to take my word for it though - just open up the installer scripts for each and note the erasing of the boot partition. It is impossible that you can flash a kernel to the boot partition, and then erase that partition, and then flash something else there (the boot image from the ROM), and have the original kernel survive.
I suppose that certain Aroura ROMs (or multi-ROM) installers could behave differently as they may allow mix-n-match ROM/kernel combinations.
But in general, standalone ROMs always overflash the boot partition (that's where the kernel & ramdisk image goes), so installing them 2nd would certainly overflash any prior "kernel flash". (Moreover, many of the kernel flashes drop stuff into /system/etc and elsewhere - so those things would get trashed too).
@OP : If the Google (black and white screen) shows a little open padlock at the bottom, then your bootloader is unlocked.
read this thread to figure out how to get into the bootloader/fastboot mode:
[REF] Nexus 7 Button Combinations
frap129 said:
No, this happened to me and when i tried to flash a ROM it said "Flash Failed" so i tried to flash a kernel first, then ROM and it worked.
NEXUS 7:
Unlock/Root
Prime D
M-Kernel
PimpMyROM
Click to expand...
Click to collapse
You r equate correlation with causation and have doled out bad advice based upon that flawed logic. The simple fact is that the kernel is overwritten when the rom is flashed.
Sent from my Nexus 7 using Tapatalk HD
Hi all,
I got a brand new Wileyfox Storm which I liked to have rooted. When I booted the phone I got several updates which I installed first.
After updating I followed this guide: http://forum.xda-developers.com/wileyfox-storm/general/root-wileyfox-storm-t3250992
And also with a little bit help from the Cyanogen wiki: https://wiki.cyanogenmod.org/w/Install_CM_for_kipper
Reason I chose for this method is because I tried the recommended WinDroid Toolkit before but the server doesn't has the required files anymore so that program is useless for the Wileyfox Storm.
I'm running Cyanogen Os version 13.1.2-ZNH2KAS3NA-kipper btw (offical FOTA).
When I followed Bobslesbricoleurs tutorial to unlock the bootloader I got a message but not one I expected. It said:
<bootloader> Device already : unlocked !
OKAY [ 0.000s]
finished. total time : 0.000s
Does this mean I got my Wileyfox Storm with bootloader already unlocked? That how I read it...
I continued to start rooting it, but not before testing if I could still boot but everything was fine.
I tried to flash the attached custom recovery I got OK and a 'remote: size too large' error. It didn't successful flashed the recovery.
I checked if everything still was ok and it was. I could boot and everything.
So I tried something different. I'm not new to flashing (I've had a Galaxy S2 for 5 years which was running on CM13) so I went to the Cyanogen site and downloaded the latest stable (snapshot) recovery for kipper which was cm-13.0-20160820-SNAPSHOT-ZNH5YAO0J4-kipper-recovery.img.
I tried to flash that recovery and it succeeded. I could still boot recovery and system... except that after booting system the ROM would replace the recovery back to stock.
I did some research on this but I couldn't find any helpful information about it for the Storm device. So I Googled it in general and read somewhere that COS had a developers toggle to disable 'updating recovery'.
This is probably where I made my mistake because I unchecked that update recovery toggle and reflashed the snapshot recovery that worked before.
I'm not very sure, I should have written this down, but if I remember correctly the system could still boot.
I didn't know how to flash the SuperSu-v2.46_signed.zip with fastboot, the tutorial didn't specify this and I'm used to flashing from recovery (fastboot is kinda new to me, although I have worked with adb commands before).
So I booted the rom, installed AirDroid to push the zip to my internal storage and I went back to the recovery.
I flashed the SuperSu-v2.46_signed.zip with the update option in the recovery.
And now the rom is in a boot loop.
I already tried a full factory reset but it's still boot looping.
I know that in the tutorial topic FluffyTwit has had a similar problem, not sure if it's the same but it looks like it.
The given solution is "Flash stock boot.img from stock rom zip, reboot" to which he replied " flashed the whole .zip file because I saw a tutorial on some website...".
But at this stage I'm a bit afraid that I'll do it wrong again, as the instructions are either out-dated or they're just not 100% correct. Could someone help me out and/or confirm the exact steps I should do to get my device back up and running?
I'd rather keep the device stock without root than rooting it with risks of bricking. I have a feeling this device isn't as safe to rooting as I'm used to..
Thank you in advance.
Edit: I've found my solution and had to change something.
You can read it here starting from Edit 2.
http://forum.xda-developers.com/showpost.php?p=68632922&postcount=84
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