Related
Hi all!
I'm sure many of you are confident on doing this, but some are not. This quick how-to is for the scenario when you have Froyo installed with Recovery3e which is the default recovery and you're trying to make a backup of your firmware in Rom Manager without flashing another kernel via Odin.
You click on "backup", the phone reboots to ClockWorkMod Recovery. Or not. You will see Recovery3e popping up with an error message telling you that the package is not signed. Fear not, here's the solution:
Pre-requisites:
Phone must be rooted
Rom Manager installed
ClockWorkMod Recovery installed from within Rom Manager
After getting the error message, just take the battery out and simply apply volume UP + Home button + Power button to get to recovery and CWM will come up, doing what you've asked it for!
Just installing CF-Root with Odin is the simplest solution for me which roots your device and installs ClockworkMod
http://forum.xda-developers.com/showthread.php?t=788108
Is there any useful advantage to loading the latest version of CWM using the market app?
I originally flashed mine with CF-Root, but since have flashed the speedmod kernel and that seems to have changed it again.
alexhull24 said:
Is there any useful advantage to loading the latest version of CWM using the market app?
I originally flashed mine with CF-Root, but since have flashed the speedmod kernel and that seems to have changed it again.
Click to expand...
Click to collapse
I have just updated my rom manager and the change is a new layout with icons and it looks much nicer
The guide is for those, who don't want to change the factory kernel in the rom. Flashing CF-Root/SpeedMod/Voodoo or whatever you sympathize with is the best solution I agree, as it comes with several benefits aside rooting, but not everyone wants to do it that way.
I would add, just to be sure, after backup copy the backup file to external SD card..
myrddral said:
Hi all!
I'm sure many of you are confident on doing this, but some are not. This quick how-to is for the scenario when you have Froyo installed with Recovery3e which is the default recovery and you're trying to make a backup of your firmware in Rom Manager without flashing another kernel via Odin.
You click on "backup", the phone reboots to ClockWorkMod Recovery. Or not. You will see Recovery3e popping up with an error message telling you that the package is not signed. Fear not, here's the solution:
Pre-requisites:
Phone must be rooted
Rom Manager installed
ClockWorkMod Recovery installed from within Rom Manager
After getting the error message, just take the battery out and simply apply volume UP + Home button + Power button to get to recovery and CWM will come up, doing what you've asked it for!
Click to expand...
Click to collapse
hi, i did the same and got the update.zip in my phone but when i try to apply it during 3e recovery, i always get the <E:failed to verify whole-file signature xxxxx Installation abort>
can anyone help me with this issue?
many thanks in advance.
p/s: the phone is already rooted and rom manager installed with the latest CWM recovery 2.5.1.2
current firmware 2.2, kernel version 2.6.32.9, build number froyo.DXJPE
same issue as last post, I have successfully rooted the phone with oneclick, I have installed rom manager, I have flashed CWR (v2.5.1.2) phone is GT-I9000, Firmware is 2.2.1, kernel 2.6.32.9, build FROYO.BOJS5 and baseband is I9000XXJPY
I checked, root is working and rom manager got the proper root access
if I access "backup your current ROM" it takes me to the recovery v3 mode, where there is no backup options. if I try to apply the update.zip, I got the error signature not verify. I remove the battery, I reinsert it and the phone reboot to the recovery3, I apply the update.zip again and get the same messages, again and again.
I could probably install CF-ROOT but I would like to do a nandroid backup first and this is never presented in the options
reup
dereut said:
same issue as last post, I have successfully rooted the phone with oneclick, I have installed rom manager, I have flashed CWR (v2.5.1.2) phone is GT-I9000, Firmware is 2.2.1, kernel 2.6.32.9, build FROYO.BOJS5 and baseband is I9000XXJPY
I checked, root is working and rom manager got the proper root access
if I access "backup your current ROM" it takes me to the recovery v3 mode, where there is no backup options. if I try to apply the update.zip, I got the error signature not verify. I remove the battery, I reinsert it and the phone reboot to the recovery3, I apply the update.zip again and get the same messages, again and again.
I could probably install CF-ROOT but I would like to do a nandroid backup first and this is never presented in the options
reup
Click to expand...
Click to collapse
Same here!
On same ROM...
There is an excellent guide on this forum, and on another one that specify that galaxy s with froyo 2.2.1 and recovery3 needs to install CF-ROOT :
http://www.addictivetips.com/mobile/how-to-install-clockworkmod-recovery-on-samsung-galaxy-s-i9000
and
http://forum.xda-developers.com/showthread.php?t=1035995
what this thread here is about is how NOT to need CF-ROOT
this is a bit like biting your own tail. I think the most important part for me is: if you flash another kernel, can you revert to your previous one as it is not possible to do a nandroid backup before flashing the kernel
for warranty sake, it would be important to be able to revert to a nandroid backed-up ROM, then revert to recovery3 than unroot the phone before bringing it back in case of need of repair
I found an app, sgs kernel flasher, it might be possible to backup the original kernel this way
so it would go like this :
root the phone (onclick root worked well with my phone)
install rom manager
install sgs kernel flasher
backup the kernel
flash CF-ROOT as describe in http://www.addictivetips.com/mobile/how-to-install-clockworkmod-recovery-on-samsung-galaxy-s-i9000 (the clearest guide I found so far)
flash CWR (or is it not necessary with CF-ROOT)
do a nandroid backup
save preciously the backup and the previously backed up kernel
play with the new toys .....
when warranty is needed:
restore the nandroid backed-up ROM
revert to original kernel with sgs kernel flasher
unroot with oneclick
can someone with experience revue this list and tells us if it sound correct ?
thanks
reup
I went a bit further, following my own post just above :
my phone is already rooted and has ROM MANAGER installed
I used the first option of ROM manager and flash the last CWR. that has created a update.zip on my sdcard, but I cannot use it as I am still on recoveryv3
I backed up my kernel using "sgs kernel flash" (found on market)
I flashed a new kernel : CF-Root-XW_XEN_JS5-v1.3-BusyBox-1.17.1.zip. this is because my phone build is build FROYO.BOJS5 (noticed the 2 JS5)
rebooted the phone, I open ROM Manager and went to "reboot into recovery"
there I was on recoveryv2, with very little options but I "apply update.zip" twice (first one failed)
I rebooted and suddenly I had access to the new flashed recovery, CWR with backup options
I did a nandroid backup
one trick, the OK button became the right most button, and not the center one anymore
one think left to do, revert to stock samsung with recovery v3. to test the complete process
another trick, the CF-ROOT kernel came package into a zip files and when trying to flash it with sgs kernel flash it fails. you need to unzip the file first, it will gives you a .tar file, this one can be flash successfully
so all together, we can flash a new kernel all from the phone, without ODIN and without a PC (windows, Linux or other)
reup
dereut said:
I went a bit further, following my own post just above :
my phone is already rooted and has ROM MANAGER installed
I used the first option of ROM manager and flash the last CWR. that has created a update.zip on my sdcard, but I cannot use it as I am still on recoveryv3
I backed up my kernel using "sgs kernel flash" (found on market)
I flashed a new kernel : CF-Root-XW_XEN_JS5-v1.3-BusyBox-1.17.1.zip. this is because my phone build is build FROYO.BOJS5 (noticed the 2 JS5)
rebooted the phone, I open ROM Manager and went to "reboot into recovery"
there I was on recoveryv2, with very little options but I "apply update.zip" twice (first one failed)
I rebooted and suddenly I had access to the new flashed recovery, CWR with backup options
I did a nandroid backup
one trick, the OK button became the right most button, and not the center one anymore
one think left to do, revert to stock samsung with recovery v3. to test the complete process
another trick, the CF-ROOT kernel came package into a zip files and when trying to flash it with sgs kernel flash it fails. you need to unzip the file first, it will gives you a .tar file, this one can be flash successfully
so all together, we can flash a new kernel all from the phone, without ODIN and without a PC (windows, Linux or other)
reup
Click to expand...
Click to collapse
You and me are in exactly the same situation. To do nandroid backup for warranty reason we have to brake that same warranty.
Only I didnt use cf-root, I went for hardcore speedmod...
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
Please
I tried several times to ask on this forum if someone can help me, but no luck so far i am verry desperad now
I have install Skrilax CZ bootloader V8 on my tab, but thats all i dont now what i need to do now to install a custom rom, i have put the update file in to the sd kart but it wont install.
I have this option only
option
Reboot
Fastboot Mode
Boot Primary Kernel Image
Boot Secondary Kernel Image
Boot Recovery
Set Boot Secondary kernel Image
Set Debug mode on
Wipe Cache.
So cany anyone tel me what i must do to root and install CWM recovery
so i can install then after custom roms?
Is ther no tutorial from heren to folow!!
Please don't double post it gets confusing -
remember, this is the holiday season and alot of us are having a break and spending time with our long neglected family members, we can't be around here as much as we would like....
Yes there are guides on using fastboot, skrilax's bootloader thread for one...
PLEASE don't flash an update.zip it doesnt work that way, you'll end up stuck again
you should read the first 2 guides linked in my sig..
I too need help exactly on this point
I have not the slightest clue what to do and i do not think this is a duplicated post.
I spent days to come at this point and i don't want to **** things up.
I red your posts dibb_nz and it just gets more confusing
You write in this post :
PLEASE don't flash an update.zip it doesnt work that way, you'll end up stuck again
and then you write here: http://forum.xda-developers.com/showthread.php?t=2049778
Have your Custom Rom downloaded and copied to your External SD Card ready to install immediatelyafter flashing skrilax's patched bootloader
So is it too hard for someone to tell what to do here to install a custom rom ?!
P.S. I also got [ ERROR: Invalid primary (LNX) kernel image ] on my screen.
http://s15.postimg.org/e02avn6aj/IMG_0020.jpg
something to worry about ?
Thread closed, duplicate of this one:
http://forum.xda-developers.com/showthread.php?t=2076510
Was able to port twrp recovery of blitz smartwatch after unpacking and replacing the kernel file with the lemfo lem5's stock kernel file extracted from unpacking stock recovery of lemfo lem5 and then repacking and flashing it to lemfo lem5. The recovery got successfully installed and all features are working except the recovery screen is flipped / inverted but not the touch response. The touch inputs are the same as non inverted screen and using the touch is pain in the a**s. If the touch input field is at 45 degrees then to access it, need to tap at 225 degrees and on the same radius distance. Can anyone let me know how to flip the recovery screen without affecting the touch fields or is there a similar custom recovery for mtk6580 lollipop smartwatch with flipped screen.
I have not found solution
Same problem with kw88h
And all twrp apk from playstore does not recognize as twrp
Recovery
Flashify can make the job
Only commands from adb... for wipe.
There is not enough space to backup or restore and i think only root and flasify is all you need.
geowolf1000 said:
I have not found solution
Same problem with kw88h
And all twrp apk from playstore does not recognize as twrp
Recovery
Flashify can make the job
Only commands from adb... For wipe
There is not enough space to backup or restore and i think only root is all you need
Click to expand...
Click to collapse
I have got everything working in twrp recovery. The flip recovery is no more a problem now as with some practice now I am comfortably able to use this inverted twrp touch with ease. It works like a charm and just like the official twrp recovery. No problems at all. Now everything is set : bootloader unlocked, rooted with latest binary supersu, custom twrp recovery installed. I also have the stock recovery img backup file, hence can switch back and forth between stock and custom recovery whenever required. No space issue on lemfo lem5 as it has 8gb rom. lastly only xposed installer is to be installed which is not much of a problem as they are available for lollipop with supported sdk and for which as of now I don't see the use of xposed installer right now, hence will install when required. If I am able to somehow flip the recovery screen then that's it! ?
Gautam_Gundap said:
I have got everything working in twrp recovery. The flip recovery is no more a problem now as with some practice now I am comfortably able to use this inverted twrp touch with ease. It works like a charm and just like the official twrp recovery. No problems at all. Now everything is set : bootloader unlocked, rooted with latest binary supersu, custom twrp recovery installed. I also have the stock recovery img backup file, hence can switch back and forth between stock and custom recovery whenever required. No space issue on lemfo lem5 as it has 8gb rom. lastly only xposed installer is to be installed which is not much of a problem as they are available for lollipop with supported sdk and for which as of now I don't see the use of xposed installer right now, hence will install when required. If I am able to somehow flip the recovery screen then that's it! ?
Click to expand...
Click to collapse
If your rom size is not sufficient enough for backup then you can create full rom backup on pc and can restore the same from pc when the need arises. There are software packages available for the same
geowolf1000 said:
I have not found solution
Same problem with kw88h
And all twrp apk from playstore does not recognize as twrp
Recovery
Flashify can make the job
Only commands from adb... for wipe.
There is not enough space to backup or restore and i think only root and flasify is all you need.
Click to expand...
Click to collapse
Gautam_Gundap said:
If your rom size is not sufficient enough for backup then you can create full rom backup on pc and can restore the same from pc when the need arises. There are software packages available for the same
Click to expand...
Click to collapse
I have with chainfire but never had any problem to recover
Thanks
Gautam_Gundap, fantastic work - You've beaten me to the punch as I had been messing with this device since yesterday (already fixed two bootloops I had induced myself -_- ) and I've been looking for a method for porting a TWRP img that wouldn't brick the LEM5.
Would you mind sharing the port? ..Despite the mirrored display/input issues you have so far, having any recovery method right now is very appealing to me considering the hell I had luckily sidestepped, and want to dig further into their stock images: if only to rebuild them with better icons for starters....
If not, can you just run me through your steps for full-backup, and your modification of TWRP for use with LEM5? I don't mind doing the legwork but would rather not walk this firepath alone!
(After 4 years, finally signed up and posted. Feels good to be here, guys! )
cassettesgoboom said:
Gautam_Gundap, fantastic work - You've beaten me to the punch as I had been messing with this device since yesterday (already fixed two bootloops I had induced myself -_- ) and I've been looking for a method for porting a TWRP img that wouldn't brick the LEM5.
Would you mind sharing the port? ..Despite the mirrored display/input issues you have so far, having any recovery method right now is very appealing to me considering the hell I had luckily sidestepped, and want to dig further into their stock images: if only to rebuild them with better icons for starters....
If not, can you just run me through your steps for full-backup, and your modification of TWRP for use with LEM5? I don't mind doing the legwork but would rather not walk this firepath alone!
(After 4 years, finally signed up and posted. Feels good to be here, guys! )
Click to expand...
Click to collapse
There are many advantages of twrp custom recovery, one of them being very fast full rom backup and even faster full rom restore and that too with compression, the pc whereas takes at least 10 times the time to do the same. full rom restore for me does it within 4mins and backup size of full compressed rom is only 1.64GB whereas the pc takes 7GB for the same backup. Needless to say about advantages of other features like customized wipe, flash image and zip files etc. Now for the procedure for porting twrp custom recovery is as follows
Download latest version of mtk extractor for PC. I tried all other methods, but only this one worked for me.
Download custom twrp recovery of blitz or i2 smartwatch which you will find in this forum.
You will require your stock recovery image file for this method. Your watch needs to be rooted to extract the same. Flashify app from playstore will do the job.
Connect watch to pc. Hope you know how to do this. rename stock recovery img to boot. Open mtk extractor and unpack this renamed file. You will find the unpacked files in mtk folder.
Cut these files and paste in a new folder stock recovery.
now rename the custom twrp recovery img you are going to port to boot.
Unpack it, the files will be placed in mtk folder.
Now copy kernel file from the stock recovery folder and paste it in the new unpacked files of ported twrp. PC Prompts replace - yes.
Now repack and you will get boot.img. Rename to recovery.img.
Flash this via fastboot or Flashify. Done. You have now successfully installed twrp recovery.
Note: In the mtk extractor software use the boot feature for all above steps.
If you encounter any problems post here and I will fix it.
To use pc for full rom backup and restore and many other features use cracked version of miracle box v2. 27A. Mtk Droid tools and SP flash tools do not support this watch, so don't waste time trying with it.
Xposed framework installed successfully!
Anyone need full power button menu for lemfo lem5 install advance power menu app from playstore. It works well. Once you long press the power button you get options for power off, reboot, download, recovery, UI restart , screen shot, soft reboot and safe mode reboot. Select floating mode from settings. looks and works nice on smart watch display
Gautam_Gundap said:
There are many advantages of twrp custom recovery, one of them being very fast full rom backup and even faster full rom restore and that too with compression, the pc whereas takes at least 10 times the time to do the same. full rom restore for me does it within 4mins and backup size of full compressed rom is only 1.64GB whereas the pc takes 7GB for the same backup. Needless to say about advantages of other features like customized wipe, flash image and zip files etc. Now for the procedure for porting twrp custom recovery is as follows
Download latest version of mtk extractor for PC. I tried all other methods, but only this one worked for me.
Download custom twrp recovery of blitz or i2 smartwatch which you will find in this forum.
You will require your stock recovery image file for this method. Your watch needs to be rooted to extract the same. Flashify app from playstore will do the job.
Connect watch to pc. Hope you know how to do this. rename stock recovery img to boot. Open mtk extractor and unpack this renamed file. You will find the unpacked files in mtk folder.
Cut these files and paste in a new folder stock recovery.
now rename the custom twrp recovery img you are going to port to boot.
Unpack it, the files will be placed in mtk folder.
Now copy kernel file from the stock recovery folder and paste it in the new unpacked files of ported twrp. PC Prompts replace - yes.
Now repack and you will get boot.img. Rename to recovery.img.
Flash this via fastboot or Flashify. Done. You have now successfully installed twrp recovery.
Note: In the mtk extractor software use the boot feature for all above steps.
If you encounter any problems post here and I will fix it.
Click to expand...
Click to collapse
Very cool - seems straightforward enough. I'll see if I can find something to fix up or workaround to get the rotation back while I'm at it. First thing's first is to give this a shot though. Need to get a windows machine so I'll get it going at work tomorrow!
Will update again soon. Thanks so much for the steps!
Hi guys.. root + twrp ok.. but there are Custom ROM with full smartwatch function (not only standalone)? Or the only one solution (partial solution) is M2D?
Well done! :laugh: I've configured Lem5 TWRP how u can see here:
https://forum.xda-developers.com/smartwatch/other-smartwatches/twrp-lemfo-lem-5-twrp-t3544569
I think/hope i've solved recovery flipped screen issue, because X5 TWRP haven't this problem.
X5 TWRP + Lem5 kernel = solution? I hope so!
If someone want try, please post the result. Thanx at all...!
Sent from my S7 Edge using XDA Labs
I'm trying to flash the recovery through fastboot and I'm getting:
C:\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending 'recovery' (9676 KB)...
OKAY [ 0.366s]
writing 'recovery'...
FAILED (remote: download for partition 'recovery' is not allowed
)
finished. total time: 0.383s
I tried rooting with Kingroot and it really bloated up my device. Factory reset still keeps Kingroot, so I kinda want to start over fresh with TWRP and a clean image. How do you flash TWRP on this watch?
---------- Post added at 02:53 PM ---------- Previous post was at 02:39 PM ----------
Update: I made sure OEM unlock was checked in developer settings and eventually was able to flash TWRP via Fastboot.
My watch is now bootlooping over and over again in TWRP, says:
"Done processing script file, renamed stock recovery file in /system to prevent the stock ROM from replacing TWRP."
dimex said:
I'm trying to flash the recovery through fastboot and I'm getting:
C:\platform-tools>fastboot flash recovery recovery.img
target reported max download size of 134217728 bytes
sending 'recovery' (9676 KB)...
OKAY [ 0.366s]
writing 'recovery'...
FAILED (remote: download for partition 'recovery' is not allowed
)
finished. total time: 0.383s
I tried rooting with Kingroot and it really bloated up my device. Factory reset still keeps Kingroot, so I kinda want to start over fresh with TWRP and a clean image. How do you flash TWRP on this watch?
---------- Post added at 02:53 PM ---------- Previous post was at 02:39 PM ----------
Update: I made sure OEM unlock was checked in developer settings and eventually was able to flash TWRP via Fastboot.
My watch is now bootlooping over and over again in TWRP, says:
"Done processing script file, renamed stock recovery file in /system to prevent the stock ROM from replacing TWRP."
Click to expand...
Click to collapse
if your bootloader is locked, it will not allow you to flash twrp recovery via fastboot . Use SP FLASH TOOLS for this purpose. Once you flash recovery do not reboot to system. Reboot to recovery for the first time and then it should be ok. Else root your watch first and flash recovery using Flashify. This method will also do the job.
Gautam_Gundap said:
if your bootloader is locked, it will not allow you to flash twrp recovery. Use SP FLASH TOOLS for this purpose. Once you flash recovery do not reboot to system. Reboot to recovery for the first time and then it should be ok. Else root your watch first and flash recovery using Flashify. This method will also do the job.
Click to expand...
Click to collapse
Did you read my update? It's bootlooping TWRP.
dimex said:
Did you read my update? It's bootlooping TWRP.
Click to expand...
Click to collapse
If you are unable to reboot to system, then you need to re flash complete stock rom. You can do this using cracked miracle software. I have already uploaded full stock rom for flashing via cracked miracle box software except data/userdata partition . you can find it in one of the lemfo lem5 threads here. After re flash you can use the steps explained earlier to flash twrp recovery
I just released a fully working TWRP 3.0.2 recovery for X5+ and LEM5 here:
http://roundandroidwatches.proboards.com/thread/1016/twrp-recovery-port-x5-lem5
Don't forget to read all the instructions.
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