STOCK ROM IMAGES BLU DASH 5.0 D410a V27-GENERIC Android Kitkat 4.4.2 MT6572 Chipset (no UBIFS)
PLEASE READ THE INSTRUCTIONS BEFORE FLASHING YOUR PHONE SO THAT YOU WON'T BRICK IT.
EDIT: 14 January 2015. Updated the TWRP 2.8.2.0 download link. Fixed the problem where ADB and MTP was not functioning in TWRP. Added backup support for a few other partitions including the Baseband.
EDIT: 19 January 2015. Changed method of rooting and added flashable zip with modified kernel to add init.d support (that was tested and is functioning properly.)
STEP 1
BACKUP YOUR MEDIATEK DEVICE
Prerequisites
All of the software is for Windows.
Download and Extract the MTK USB Drivers and the SP Flash Tool found closest to the top of the list at:
http://mtk2000.ucoz.ru/
Press the play button to the right of the file to start the download.
Download MTK Droid Root & Tools
Latest version can be found by following the link of the following post.
http://forum.xda-developers.com/showpost.php?p=38320254&postcount=1
Hint: Click the show content button to see the link to another forum with the download link
Direct Download Link of MTK Droid Root & Tools if you are having problems getting the link.
http://depositfiles.com/files/ne1gnposp
You will need Winrar to extract the files.
That can be downloaded from: http://www.rarlab.com/download.htm
READ HERE ON HOW TO BACKUP: http://forum.xda-developers.com/showpost.php?p=38337401&postcount=5
Thanks to @rua1 for the instructions and software.
NOTE: I WOULD RECOMMEND BACKUPING UP THE USRDATA PARTITION AS WELL TO DO THAT USE HEX "0X96B40000" AS THE LENGTH DURING READ BACK IN SP FLASH TOOL
To flash the DASH 5.0 you need to use the Preloader to do it.
STEP 2
Installing the Preloader Driver (READ this section entirely before trying)
Open Device Manager
Start -> Run
Type:
Code:
devmgmt.msc
Press Enter
Turn off the phone until it is completely shut down with nothing plugged in the USB port. You will see the screen go black and shortly afterwards it will vibrate.
With Device Manager open, connect the USB cable to the phone without turning it on.
You will see the MT65XX Preloader appear (see image)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Quickly double click MT65XX Preloader before it disappears, if it disappered, just unplug and plug back in the cable and try again.
Under the Driver tab, click Update Driver, click Browse my computer for driver software.
Using the Browse button find the MTKUSBAll folder you extracted and click on "New inst. win 7&8x64" and click OK
Click Next
If you get the message "Windows can't verify the publisher of this driver software", just click "Install this driver software anyway"
Click Close
Click Close
After the driver is installed you can unplug the phone.
STEP 3
Uploading the image files to the phone{/B}
WARNING: The BLU-DASH-5.0_141022_BLU-D410a-V27-GENERIC_FOR_SP_FLASH_TOOL.zip file has all of the necessary images but do not flash them unless you trying to recover from a brick.
DO NOT FLASH THE PRELOADER.BIN AS IT MAY BRICK YOUR PHONE.
THE ONLY FILES I HAVE PERSONALLY TESTED ARE boot.img, factory_NONmodified_recovery.img and system.img
Download BLU-DASH-5.0_141022_BLU-D410a-V27-GENERIC_FOR_SP_FLASH_TOOL.zip from here:
http://d-h.st/3L9G
See Step 5
Extract the SP Flash Tool.
Extract the system.img and MT6572_Android_scatter.txt (and/or boot.img and factory_NONmodified_recovery.img, if you wish)
Open the SP Flash Tool
Click the Download tab
Click the Scatter-loading button and select the MT6572_Android_scatter.txt file.
Click the location of ONLY the parition(s) you are going to flash: ANDROID = SYTEM partition (system.img), BOOTIMG = KERNEL (boot.img) and RECOVERY=RECOVERY (factory_NONmodified_recovery.img or custom recovery file)
Select the image file (e.g. system.img or system_rooted.img)
MAKE SURE ALL OTHERS ARE NOT TICKED
Click the Download button.
Plug in the phone or unplug and plug it back in to start flashing the images to the phone.
Note: This can also be done with the battery removed.
Your phone will have root.
STEP 4 - Adding TWRP
First we need to rename the file recovery-from-boot.p found in the /system folder.
Using a File Manager with root permissions rename
Code:
recovery-from-boot.p
to
Code:
recovery-from-boot.bak
OR
From an adb shell, rename the file
Code:
su
cd /system
mv recovery-from-boot.p recovery-from-boot.bak
Now turn off the phone and with SP Flash Tool flash TWRP 2.8.2.0. Download link below.
NOTE: Select only the RECOVERY partition to flash. TWRP themes are supported as well as the Aroma File Manager.
http://d-h.st/aQmt
STEP 5 - Rooting and adding init.d support
Go to http://download.chainfire.eu/supersu
Download the latest SuperSU.
Go to http://d-h.st/AJQ
Download the init.d support zip file.
Boot to TWRP while connected to a PC with adb tools run the command
Code:
adb reboot recovery[/url]
OR
Hold down the power select Reboot and hold down the volume up button until you see the TWRP logo.
Via the install menu, flash the SuperSU zip and inti.d support zip.
ALL DONE!
THANKS:
[user=631273]@Chainfire[/user] for SuperSU
[user=5119815]@rua1[/user] for MTK Droid Root & Tools and instructions on how to use SP Tools
[user=4478781]@yuweng[/user] for creating the tool to make TWRP for MediaTek devices
[user=912474]@Dees_Troy[/user] for TWRP
I will give a brief explanatoin and will elaborate more when I have the time.
For Root:
Thanks to @Chainfire
I basically mounted the system.img in a Linux OS and copied the files from the SuperSU v2.36 zip file and placed them in their relevant directories added the relevant permissions, etc.
For init.d scripts
Thanks to @alireza7991
See his thread: http://forum.xda-developers.com/showthread.php?t=2287540
I modified the kernel to boot and created a flashable zip that adds busybox to /system/xbin and creates the necessary folders then flashes the modified kernel.
For TWRP:
Thanks to @yuweng
I used Easy Magic TWRP Installer for MTK. See http://forum.xda-developers.com/showthread.php?p=53752834#post53752834
It worked but changed my partition information for some reason even though the size fit my paritition size. I wiped my phone and lost my baseband and recovered it. Posted a new thread on how to do that. See http://forum.xda-developers.com/android/software-hacking/restore-baseband-mt65xx-devices-t2967949
That is why I posted the image file so no one has to face that problem too. I tested it and it is functioning without any problems.
You can follow yuweng's thread to make it smaller if your partition size is smaller than 6MB for some phones, at a cost of course.
Anyone looking for baseband files can check http://forum.xda-developers.com/android/software-hacking/restore-baseband-mt65xx-devices-t2967949
For anyone wanting to use Link2SD on this, I have created a flashable zip to use with a custom recoveery that adds init.d support, installs Link2SD as a system app and adds a modified mount script that functions properly.
Requires root and a SD card with the second partition formatted as EXT4.
Download -> http://d-h.st/Dcgh
After flash this rom only get Blu screen, wipe and cache reset and the same, trun to V14 again and power on ok, this v 27 in the 2 variants, stock and rroted not start.
jorgefar said:
After flash this rom only get Blu screen, wipe and cache reset and the same, trun to V14 again and power on ok, this v 27 in the 2 variants, stock and rroted not start.
Click to expand...
Click to collapse
What procedure did you use to flash it?
SP_Flash_Tool_exe_windows_v5.1420.00
Scatter File from V27
selected only:
Recovery: non modified...
Boot: boot.img
Android : System.img or System Rooted
Flashed OK
Only Blu screen and restar...
Im currently on V14 Ok
jorgefar said:
SP_Flash_Tool_exe_windows_v5.1420.00
Scatter File from V27
selected only:
Recovery: non modified...
Boot: boot.img
Android : System.img or System Rooted
Flashed OK
Only Blu screen and restar...
Im currently on V14 Ok
Click to expand...
Click to collapse
Your phone is a BLU Dash 5.0 D410a and NOT the 5.0+ or 5.0 Studio right?
It sounds like your kernel (boot.img) is not booting the /system partition. Try flashing the /system and recovery partitions only for now and see what happens. Do not flash the boot.img
Thanks for you le answer! Thats right, is a Blu Dash 5.0 D410a, I try on Monday the suggested and post results!!!
Hi again, flashed system and recovery only, stuck on Blu screen again, try wipe and reset cache, stuck on screen Blu,any recomendation??
Added a flashable zip to add init.d and install LInk2SD with a modified mount script to run properly on this phone, BLU DASH 5.0 D420a running V27 Android 4.4.2.
See post #3
dechronic said:
Your phone is a BLU Dash 5.0 D410a and NOT the 5.0+ or 5.0 Studio right?
It sounds like your kernel (boot.img) is not booting the /system partition. Try flashing the /system and recovery partitions only for now and see what happens. Do not flash the boot.img
Click to expand...
Click to collapse
I'm having the same problem as Jorgefar. Mine is on v24 instead of v14 though after the factory update to 4.4.2. I rooted it with kingroot, but I would like to have twrp recovery. I've done everything you instructed him, but mine gets stuck in the bootloop as well. I thought i could just flash the recovery, and did the rename on the recovery file, but that didn't work still had factory recovery. After that I did the entire procedure and got the bootloop.
Sexyr said:
I'm having the same problem as Jorgefar. Mine is on v24 instead of v14 though after the factory update to 4.4.2. I rooted it with kingroot, but I would like to have twrp recovery. I've done everything you instructed him, but mine gets stuck in the bootloop as well. I thought i could just flash the recovery, and did the rename on the recovery file, but that didn't work still had factory recovery. After that I did the entire procedure and got the bootloop.
Click to expand...
Click to collapse
After installing TWRP you need boot into TWRP before booting into Android and install the latest SuperSU. The install-recovery.sh will replace TWRP with the stock recovery on the first boot if SuperSU is not installed, which renames it.
After flashing TWRP with the Smart Phone Flash Tool, disconnect the cable, press the power button and then hold the volume up button to enter TWRP.
dechronic said:
After installing TWRP you need boot into TWRP before booting into Android and install the latest SuperSU. The install-recovery.sh will replace TWRP with the stock recovery on the first boot if SuperSU is not installed, which renames it.
After flashing TWRP with the Smart Phone Flash Tool, disconnect the cable, press the power button and then hold the volume up button to enter TWRP.
Click to expand...
Click to collapse
Cool got it and am on v27 now. thanks..... now if ony there were other roms for it ah well, at least i'm rooted again with recovery.
can i flash this on BLU Dash 5.0 D400a
dechronic said:
Anyone looking for baseband files can check http://forum.xda-developers.com/android/software-hacking/restore-baseband-mt65xx-devices-t2967949
For anyone wanting to use Link2SD on this, I have created a flashable zip to use with a custom recoveery that adds init.d support, installs Link2SD as a system app and adds a modified mount script that functions properly.
Requires root and a SD card with the second partition formatted as EXT4.
Download -> http://d-h.st/Dcgh
Click to expand...
Click to collapse
This say file no longer available..could it be downloaded elsewhere?
Does this work on 5.0+?
Stiffymeister said:
Does this work on 5.0+?
Click to expand...
Click to collapse
Don't think so but I think I have a 5.0+ image. Anything in particular you looking for? I should be able to provide it tomorrow
i have tried everything as you said but after using the flash too and b4 installing recovery it says my phone is not rooted so it wont let me rename the recovery file. should i have a rooted system image in the scatter file cause i dont see one in the files i extracted. p.s. i downloaded all the files you linked so if im missing something can someone please point me in the right direction. thanks
blu dash 5.0 d410a v27
dlongnasty said:
i have tried everything as you said but after using the flash too and b4 installing recovery it says my phone is not rooted so it wont let me rename the recovery file. should i have a rooted system image in the scatter file cause i dont see one in the files i extracted. p.s. i downloaded all the files you linked so if im missing something can someone please point me in the right direction. thanks
blu dash 5.0 d410a v27
Click to expand...
Click to collapse
I probably need to redo the steps for a couple of the posts.
Download the TWRP at http://d-h.st/aQmt
Upload it to the phone. Make sure that only recovery is ticked in the Smart Phone Flash Tool (SP Flash Tool) and select the file you downloaded. You should be able to figure out the rest based on my instructions.
Flash SuperSU which can be downloaded from http://download.chainfire.eu/supersu
It will rename the file that would put back the original recovery.
That should be it.
got it working thanks. are their any custom roms for the d410a?
Related
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Welcome
FazHDv3 is the Samsung S4 Based Custom Rom
This ROM is ported from SamHDv3 for Customizations and Smoothness of 701HD
Special Thanks to abhishek for his invaluable contribution.
FAZHD ROM Features
Same as http://forum.xda-developers.com/showthread.php?t=2201122
How To Flash :
( You Can Take CMW Backup for Revert back to your old system )
Flashing procedure is different Don't Skip
1) Download Fazhd rom and bin files
Extract them both.copy allfiles in bin files to rom's system/bin
copy updater-script and replace with updater-script in here .META-INF/com/google/android/here
make a zip of rom
2) Put into External SD Card
3) Go To CMW Recovery
4) Wipe Data/Factory Reset And Wipe Partition
5) From Advance Menu Do Dalvik Catch Clear
6) Go in Mount And Storage select FORMAT SYSTEM
7) Select Intall From SD and Select File And Click YES
8) Select FazHDV3.zip And Select YES
9) Reboot Your System
10) Enjoy
Downloads
Rom http://d-h.st/NVu
bin files http://d-h.st/BBf
updater-script http://www.mediafire.com/?mv7fksxvttm4c41
Hi Buddy, Can you port the Ultimate 2.1 Rom by Back37 of Xolo Q800/GiONEE GN708W to Lava IRIS 504Q??
It's SUPER AWESOME ROM!! GIONEE FIRMWARE ROCKS!
Here's the link.
https://disk.yandex.com/public/?hash=MliKIOx5Mpen0T9iZd1uQmMX6bJee7QjjfPLQtVMXoU=
Thanks lot!
NHS2008 said:
Hi Buddy, Can you port the Ultimate 2.1 Rom by Back37 of Xolo Q800/GiONEE GN708W to Lava IRIS 504Q??
It's SUPER AWESOME ROM!! GIONEE FIRMWARE ROCKS!
Here's the link.
https://disk.yandex.com/public/?hash=MliKIOx5Mpen0T9iZd1uQmMX6bJee7QjjfPLQtVMXoU=
Thanks lot!
Click to expand...
Click to collapse
I ported lewa os to lava iris 504q..
Will upload soon
Sent from my iris504Q using xda premium
Thanks I would be very greatful if you could port that rom. Its too goood
Thanks a Lot.... can you try to port Canva4HD from same dev...
fandroid7 said:
Welcome
FazHDv3 is the Samsung S4 Based Custom Rom
This ROM is ported from SamHDv3 for Customizations and Smoothness of 701HD
Special Thanks to abhishek for his invaluable contribution.
FAZHD ROM Features
Same as http://forum.xda-developers.com/showthread.php?t=2201122
How To Flash :
( You Can Take CMW Backup for Revert back to your old system )
Flashing procedure is different Don't Skip
1) Download Fazhd rom and bin files
Extract them both.copy allfiles in bin files to rom's system/bin
copy updater-script and replace with updater-script in here .META-INF/com/google/android/here
make a zip of rom
2) Put into External SD Card
3) Go To CMW Recovery
4) Wipe Data/Factory Reset And Wipe Partition
5) From Advance Menu Do Dalvik Catch Clear
6) Go in Mount And Storage select FORMAT SYSTEM
7) Select Intall From SD and Select File And Click YES
8) Select FazHDV3.zip And Select YES
9) Reboot Your System
10) Enjoy
Downloads
Rom http://d-h.st/NVu
bin files http://d-h.st/BBf
updater-script http://www.mediafire.com/?mv7fksxvttm4c41
Click to expand...
Click to collapse
Thanks a Lot.... can you try to port Canva4HD from same dev... great abhishek.....
and can it be possible if you put bin files... in the same.. .zip.. and do we need to sign the zip after copy - paste of bin files and updater script...
port MTK6589 roms easy
defy403 said:
Thanks a Lot.... can you try to port Canva4HD from same dev... great abhishek.....
and can it be possible if you put bin files... in the same.. .zip.. and do we need to sign the zip after copy - paste of bin files and updater script...
Click to expand...
Click to collapse
Download MTK firmware adaptor forum.china-iphone.ru/post862552.html
you should install adb and root access to phone and your stock boot.img
1. download Rom you need to port
2. open mtk firware Adaptor
3. select profile as mtk6589
4.get files from your phone.
5. make your system files as system.zip (will get from backup of your rom)
get files from your system.zip
the tool will look like not responding but its copying rom files
6. get files from port rom
7. tick automated boot.img and make modded boot.img from stock boot.img
8. make adapted rom (port rom for your device)
it will automatically sign your rom
you can edit build.prop before creating rom
copy to phone and flash via cwm
updater-script will be automatically created.
test the rom and tell me if you have any problem like
dark camera. audio not wotking
will tell you how to fix it
stuck on boot loop....
fandroid7 said:
Download MTK firmware adaptor forum.china-iphone.ru/post862552.html
you should install adb and root access to phone and your stock boot.img
1. download Rom you need to port
2. open mtk firware Adaptor
3. select profile as mtk6589
4.get files from your phone.
5. make your system files as system.zip (will get from backup of your rom)
get files from your system.zip
the tool will look like not responding but its copying rom files
6. get files from port rom
7. tick automated boot.img and make modded boot.img from stock boot.img
8. make adapted rom (port rom for your device)
it will automatically sign your rom
you can edit build.prop before creating rom
copy to phone and flash via cwm
updater-script will be automatically created.
test the rom and tell me if you have any problem like
dark camera. audio not wotking
will tell you how to fix it
Click to expand...
Click to collapse
stuck on boot loop.... what to do now......!!!
defy403 said:
stuck on boot loop.... what to do now......!!!
Click to expand...
Click to collapse
its becouse of boot.img
just tap modifying boot.img button two or more times after selecting boot.img
its because of bad repacking of boot.img
if you use android kitchen
then make portrom.zip working folder and replace your stock boot.img
unpack boot.img by going to advanced and unpack repack boot.img unpack pressing w
rename boot extracted to stock boot
change boot.img with port roms boot.img
unpack port boot.img
copy zimage or zboot (i forgot real name) zxxxxxxx from stock boot to boot exracted
repack boot.img and make zip using 7zip of new boot.img+meta+system and flash rom it will boot
need help badly....
fandroid7 said:
its becouse of boot.img
just tap modifying boot.img button two or more times after selecting boot.img
its because of bad repacking of boot.img
if you use android kitchen
then make portrom.zip working folder and replace your stock boot.img
unpack boot.img by going to advanced and unpack repack boot.img unpack pressing w
rename boot extracted to stock boot
change boot.img with port roms boot.img
unpack port boot.img
copy zimage or zboot (i forgot real name) zxxxxxxx from stock boot to boot exracted
repack boot.img and make zip using 7zip of new boot.img+meta+system and flash rom it will boot
Click to expand...
Click to collapse
hi sir,
how to boot into recovery... i am getting 8038 in sp flash tool... have cwm backup...... device is not detected on mtk... and getting 8038 error in sp flash tool... what to do... plz plz help...
defy403 said:
hi sir,
how to boot into recovery... i am getting 8038 in sp flash tool... have cwm backup...... device is not detected on mtk... and getting 8038 error in sp flash tool... what to do... plz plz help...
Click to expand...
Click to collapse
are you using cwm
download mobile uncle tools for mediatech and select reboot to recovery
resolved... phone is back to life....
defy403 said:
hi sir,
how to boot into recovery... i am getting 8038 in sp flash tool... have cwm backup...... device is not detected on mtk... and getting 8038 error in sp flash tool... what to do... plz plz help...
Click to expand...
Click to collapse
done... phone back to life... selected... firmware upgrade and did... flash factory rom backup.... and it's again alive...
with CWM & SU along with mobile uncle....
i think from next time... whenever i will try to do experiments.... will... make sure... i have backup ready..
so doing a new backup with CWM and SU... right away... also doing IMEI restore as it went to null.....
---------- Post added at 08:03 AM ---------- Previous post was at 07:54 AM ----------
fandroid7 said:
are you using cwm
download mobile uncle tools for mediatech and select reboot to recovery
Click to expand...
Click to collapse
HI....
i was stuck on boot loop... so not getting into recovery... even mtk was not detecting my phone... so i flashed... factory rom.. backup.. via firmware upgrade in sp flash tool... 3.13.... and did a factory reset and i am back in business,,,, still thanks for help...
you are from India... i am from mumbai.... can i just replace.... boot.img in custom rom with my phone's boot.img.... and do same for LK.bin... i.e. uboot.img... will that work....
---------- Post added at 09:01 AM ---------- Previous post was at 08:03 AM ----------
defy403 said:
done... phone back to life... selected... firmware upgrade and did... flash factory rom backup.... and it's again alive...
with CWM & SU along with mobile uncle....
i think from next time... whenever i will try to do experiments.... will... make sure... i have backup ready..
so doing a new backup with CWM and SU... right away... also doing IMEI restore as it went to null.....
---------- Post added at 08:03 AM ---------- Previous post was at 07:54 AM ----------
HI....
i was stuck on boot loop... so not getting into recovery... even mtk was not detecting my phone... so i flashed... factory rom.. backup.. via firmware upgrade in sp flash tool... 3.13.... and did a factory reset and i am back in business,,,, still thanks for help...
you are from India... i am from mumbai.... can i just replace.... boot.img in custom rom with my phone's boot.img.... and do same for LK.bin... i.e. uboot.img... will that work....
Click to expand...
Click to collapse
hi all...
http://forum.xda-developers.com/show....php?t=2012770
http://forum.xda-developers.com/show....php?t=1574401
check this thread...
this even works with our Zen 701HD... so install and enjoy.... new freedom... and.. no custom rom.. needed....
Replaced boot.img and it worked
fandroid7 said:
Download MTK firmware adaptor forum.china-iphone.ru/post862552.html
you should install adb and root access to phone and your stock boot.img
1. download Rom you need to port
2. open mtk firware Adaptor
3. select profile as mtk6589
4.get files from your phone.
5. make your system files as system.zip (will get from backup of your rom)
get files from your system.zip
the tool will look like not responding but its copying rom files
6. get files from port rom
7. tick automated boot.img and make modded boot.img from stock boot.img
8. make adapted rom (port rom for your device)
it will automatically sign your rom
you can edit build.prop before creating rom
copy to phone and flash via cwm
updater-script will be automatically created.
test the rom and tell me if you have any problem like
dark camera. audio not wotking
will tell you how to fix it
Click to expand...
Click to collapse
Replaced boot.img and it worked... bootup perfectly first time... all things working correctly... but now not booting up again... after i tried to restart...
troubleshooting done.... only needed to replace build.prop... and it works great.... even blow to unlock works...
only camera is dark... as told by you.. please tell me how to fix....
defy403 said:
Replaced boot.img and it worked... bootup perfectly first time... all things working correctly... but now not booting up again... after i tried to restart...
Click to expand...
Click to collapse
Hi can you share the files I need to flash from S.P. Tools to make my Irsi 504q back working?
I only have CWM backup. I've bircked it while trying a ported rom from Q800...THANKS!
please help me with camera
fandroid7 said:
Download MTK firmware adaptor forum.china-iphone.ru/post862552.html
you should install adb and root access to phone and your stock boot.img
1. download Rom you need to port
2. open mtk firware Adaptor
3. select profile as mtk6589
4.get files from your phone.
5. make your system files as system.zip (will get from backup of your rom)
get files from your system.zip
the tool will look like not responding but its copying rom files
6. get files from port rom
7. tick automated boot.img and make modded boot.img from stock boot.img
8. make adapted rom (port rom for your device)
it will automatically sign your rom
you can edit build.prop before creating rom
copy to phone and flash via cwm
updater-script will be automatically created.
test the rom and tell me if you have any problem like
dark camera. audio not wotking
will tell you how to fix it
Click to expand...
Click to collapse
only camera is dark... as told by you.. please tell me how to fix....
defy403 said:
only camera is dark... as told by you.. please tell me how to fix....
Click to expand...
Click to collapse
to fix camera.
I assume you use dsixda's kitchen.
Set up working folder for stock rom
Go to advanced > tools for boot.img
> unpack boot.img
Navigate to the folder called Boot-extracted.
> rename it to something else (for now: stock boot)
Set up working folder for port rom.
Go to advanced > unpack boot.img
Do a google search for 'winmerge' > install program (free).
Open winmerge, for left navigate to the 'stock boot' folder, and select init.rc (about 40kb)
For right, navigate to the port 'boot-extracted', and select init.rc (about 40kb)
In winmerge find lines like this
Chmod camera blablabla (on the left pane you will see where there are differences)
Chown camera blablabla
If there are differences in those lines, copy the stock lines, and overwrite the port ones
Save the files (crtl+s)
Navigate to boot extracted folder, you can close winmerge. Copy stock Zimage (from 'stock boot' folder) to port, and overwrite the Zimage there with stock one.
Go back to kitchen, > advanced > tools for boot.img > build new boot image.
Unable to open your site for downloading ROM, could you reupload please.
Looking for more ROMS.
Hi again fan droid.... It would help if you can fix the issues and upload the completed ROM....
I faced the same camera issue when I ported naturewiz HD..... Will you help fix that too?
Sent from my ultrafone 701HD
bro post the ROM, so that we could test it.
use MTK root tools
NHS2008 said:
Hi can you share the files I need to flash from S.P. Tools to make my Irsi 504q back working?
I only have CWM backup. I've bircked it while trying a ported rom from Q800...THANKS!
Click to expand...
Click to collapse
use MTK Root tools ...
1. recovery..backup tab
2. select prepare blocks for flash tool
3. select .md5 file from your CWM backup
4. it will checksum... and prepare files which can be flashed via... SP Flash Tool...
5. make sure you select... firmware upgrade... while flash...
* please note... you will need sp flash tool v3.13 & also.... all the files.... i.e. from preloader to cache.. and even userdata... nvram...tar...
please hit thanks if i help
post the ROM bro, so that we could test it. waiting for a long time.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I successfully ported TWRP to Panasonic Eluga Note (MTK6753) after a four day effort. Not a dev here. First time doing this.
<TLDR? skip this>
When I started using android in my HTC HD2, every ROM was pre rooted. I took it for granted.
So I get this cheapo MTK and breaking into it is like banging head against a wall!! I was frustrated with the battery drain: Device never sleeps since the last OTA!
So I learnt SP flash tools and downgraded. ( wiped nvram and created another mess in the process- which is a different story. I solved it)
I could spend this effort and time to stop that pesky "Panasonic" bootaudio too. And that's the first thing I deleted after I booted TWRP, even before rooting.
</TLDR? skipped this>
First things first, enable ADB, enable OEM unlock in developer options, and go to bootloader to unlock it <fastboot oem unlock> THIS WILL WIPE DATA!!
Second thing: Backup nvram.img by sp flash readback and learn how to flash it back (search XDA)- Sometimes you can learn from other's mistakes too! I spent a day and half writing back IMEI and WIFI Mac.
Process (if you don't trust me and want to reproduce the steps yourself)
1. Download stock firmware. (google knows)
2. Patch boot.img so that it doesn't overwrite TWRP with stock recovery on each boot (extract by Carliv Image kitchen and hash out the three lines 663, 664 and 665 mentioning "service flash_recovery /system/bin/install-recovery.sh" in init.rc). I created two copies in the same folder (boot.img, and boot-verified.img) and copied scatter into the same folder for flashing. That's what I saw in the firmware folder.
3. Port TWRP using Carliv Image Kitchen method. I downloaded TWRP from here https://forum.xda-developers.com/android/software/twrp-porter-maker-mediatek-mt67xx-32-t3681861 but didn't use their method. It didn't work. The TWRP for this chip was stated as android N, but worked well.
4. Flash ported TWRP after copying scatter file to the Carliv Imagekitchen output folder and selecting that scatter in SP droid tools. I again created recovery.img and recovery-verified.img. Don't know if its needed that way. You could wait and flash boot and recovery together from the same folder.
5. That's it, you can enter custom recovery now. Get that pesky "panasonic" bootaudio off the system/media folder now! You can stay content after this or proceed to root.
<nandroid backup now, including Nvram and NVdata. Just in case>
6. Download Supersu zip flashable and flash it via TWRP. https://download.chainfire.eu/1113/SuperSU/UPDATE-SuperSU-v2.82-20170528234214.zip?retrieve_file=1 worked for me.
7. Reboot, check root!
If you're more daredevil,
8. Download Xposed flashable zip SDK23 and flash it. Download Xposed installer and copy it to SDcard too.
9. Reboot to recovery and flash the zip. Reboot, install xposed installer. Reboot again.
You're done!
I'll upload my boot.img and ported TWRP if anyone shows any interest in this.
Cheers!
(Bonus: this phone has built in IPtables support in the kernel! I used to flash custom kernel for this ability in other Stock ROMs. AFfirewall works "out of the box"- after rooting, of course!)
Edit: uploaded my modded boot.img and ported TWRP. find it here https://drive.google.com/file/d/1sM1BnyBUFN7PfncFcM7vzIet6gKt3G_L/view?usp=sharing
If you want to go the easy route, unzip the folder and flash it with sp flash. You'll be able to boot into recovery and do the other steps for rooting.
Rememer ONLY DOWNLOAD, don't format, or format and download, or anything!
Brilliant Work man. I also was sort of in your situation as well . i have a panasonic Eluga A3 (Qmobile Noir E2) in my country. Stock Qmobile rom was horrendous. so i flashed the panasonic rom but hated the boot audio and the bloatware that came with it. so i decided to make a slimmed down version of it and successfully did it by using superr's kitchen. and also using the kitchen i removed the encryption on the boot.img and then patched it using magisk for easy rooting without recovery. when flashed together with the modded system.img and modded boot.img and twrp, i was totally in control of my device.
If you need any help with anything mtk send me a pm
also are you able to access internal storage in twrp or not ??
andromodgod said:
If you need any help with anything mtk send me a pm
also are you able to access internal storage in twrp or not ??
Click to expand...
Click to collapse
I can access internal storage in twrp. There's a choice to select the internal storage. Havent backed up to it or anything. But its there. I copied a file into it through TWRP now, and it works. I think its all about the fstab. If you don't get access to internal storage, see for any red errors in TWRP output. I can look into my fstab to see what's relevant.
I have a little hiccup though. Now my network drops (both sim at a time), even during a call. But maybe its because I swapped sim 1 and sim 2. I'll let things settle and see if it will persist. In the meanwhile, I swapped sims back to original.
bad.bid said:
I can access internal storage in twrp. There's a choice to select the internal storage. Havent backed up to it or anything. But its there. I copied a file into it through TWRP now, and it works. I think its all about the fstab. If you don't get access to internal storage, see for any red errors in TWRP output. I can look into my fstab to see what's relevant.
I have a little hiccup though. Now my network drops (both sim at a time), even during a call. But maybe its because I swapped sim 1 and sim 2. I'll let things settle and see if it will persist. In the meanwhile, I swapped sims back to original.
Click to expand...
Click to collapse
i wasn't able to access internal storage at first because device was encrypted beforehand. also sim issues might be caused by imei/nvram . check if your device imei matches your imei on the device box.
andromodgod said:
i wasn't able to access internal storage at first because device was encrypted beforehand. also sim issues might be caused by imei/nvram . check if your device imei matches your imei on the device box.
Click to expand...
Click to collapse
Ya, I fixed Imei issues. this one is like a signal drop once every 15 minutes.
bad.bid said:
I successfully ported TWRP to Panasonic Eluga Note (MTK6753) after a four day effort. Not a dev here. First time doing this.
<TLDR? skip this>
When I started using android in my HTC HD2, every ROM was pre rooted. I took it for granted.
So I get this cheapo MTK and breaking into it is like banging head against a wall!! I was frustrated with the battery drain: Device never sleeps since the last OTA!
So I learnt SP flash tools and downgraded. ( wiped nvram and created another mess in the process- which is a different story. I solved it)
I could spend this effort and time to stop that pesky "Panasonic" bootaudio too. And that's the first thing I deleted after I booted TWRP, even before rooting.
</TLDR? skipped this>
First things first, enable ADB, enable OEM unlock in developer options, and go to bootloader to unlock it <fastboot oem unlock> THIS WILL WIPE DATA!!
Second thing: Backup nvram.img by sp flash readback and learn how to flash it back (search XDA)- Sometimes you can learn from other's mistakes too! I spent a day and half writing back IMEI and WIFI Mac.
Process (if you don't trust me and want to reproduce the steps yourself)
1. Download stock firmware. (google knows)
2. Patch boot.img so that it doesn't overwrite TWRP with stock recovery on each boot (extract by Carliv Image kitchen and hash out the three lines 663, 664 and 665 mentioning "service flash_recovery /system/bin/install-recovery.sh" in init.rc). I created two copies in the same folder (boot.img, and boot-verified.img) and copied scatter into the same folder for flashing. That's what I saw in the firmware folder.
3. Port TWRP using Carliv Image Kitchen method. I downloaded TWRP from here https://forum.xda-developers.com/android/software/twrp-porter-maker-mediatek-mt67xx-32-t3681861 but didn't use their method. It didn't work. The TWRP for this chip was stated as android N, but worked well.
4. Flash ported TWRP after copying scatter file to the Carliv Imagekitchen output folder and selecting that scatter in SP droid tools. I again created recovery.img and recovery-verified.img. Don't know if its needed that way. You could wait and flash boot and recovery together from the same folder.
5. That's it, you can enter custom recovery now. Get that pesky "panasonic" bootaudio off the system/media folder now! You can stay content after this or proceed to root.
<nandroid backup now, including Nvram and NVdata. Just in case>
6. Download Supersu zip flashable and flash it via TWRP. https://download.chainfire.eu/1113/SuperSU/UPDATE-SuperSU-v2.82-20170528234214.zip?retrieve_file=1 worked for me.
7. Reboot, check root!
If you're more daredevil,
8. Download Xposed flashable zip SDK23 and flash it. Download Xposed installer and copy it to SDcard too.
9. Reboot to recovery and flash the zip. Reboot, install xposed installer. Reboot again.
You're done!
I'll upload my boot.img and ported TWRP if anyone shows any interest in this.
Cheers!
(Bonus: this phone has built in IPtables support in the kernel! I used to flash custom kernel for this ability in other Stock ROMs. AFfirewall works "out of the box"- after rooting, of course!)
Edit: uploaded my modded boot.img and ported TWRP. find it here https://drive.google.com/file/d/1sM1BnyBUFN7PfncFcM7vzIet6gKt3G_L/view?usp=sharing
If you want to go the easy route, unzip the folder and flash it with sp flash. You'll be able to boot into recovery and do the other steps for rooting.
Rememer ONLY DOWNLOAD, don't format, or format and download, or anything!
Click to expand...
Click to collapse
Can you please mention the steps and software needed for rooting the device plz plz plz
gt612 said:
Can you please mention the steps and software needed for rooting the device plz plz plz
Click to expand...
Click to collapse
No need to quote the whole post!
Download twrp and boot from here. https://drive.google.com/file/d/1sM1BnyBUFN7PfncFcM7vzIet6gKt3G_L/view?usp=sharing
download super su from the link in original post. flash iso files in the twrp boot zip (they are for the updated latest version of android 6.0.1). flash supersu via twrp. search for how to do these things.
Hello. I have an Allveiw V2 Viper S (the romanian version fo the eluga note). I got a stock rom (not from my phone) from where i took and modified both the boot.img and the recovery.img and also used the scatter from here to. I couldn`t make mtk droid tools to see my device. I managed to unlock the bootloader, but when i tried to flash the boot and recovery spft gave me a " Obtain DRAM Faild" error. Can you please help?
Thanks!
madhogg said:
Hello. I have an Allveiw V2 Viper S (the romanian version fo the eluga note). I got a stock rom (not from my phone) from where i took and modified both the boot.img and the recovery.img and also used the scatter from here to. I couldn`t make mtk droid tools to see my device. I managed to unlock the bootloader, but when i tried to flash the boot and recovery spft gave me a " Obtain DRAM Faild" error. Can you please help?
Thanks!
Click to expand...
Click to collapse
This was an impulse project. I learned many things in the way. But I have left that effort behind. So, for now: no idea. Hope google helps!
bad.bid said:
I successfully ported TWRP to Panasonic Eluga Note (MTK6753) after a four day effort. Not a dev here. First time doing this.
<TLDR? skip this>
When I started using android in my HTC HD2, every ROM was pre rooted. I took it for granted.
So I get this cheapo MTK and breaking into it is like banging head against a wall!! I was frustrated with the battery drain: Device never sleeps since the last OTA!
So I learnt SP flash tools and downgraded. ( wiped nvram and created another mess in the process- which is a different story. I solved it)
I could spend this effort and time to stop that pesky "Panasonic" bootaudio too. And that's the first thing I deleted after I booted TWRP, even before rooting.
</TLDR? skipped this>
First things first, enable ADB, enable OEM unlock in developer options, and go to bootloader to unlock it <fastboot oem unlock> THIS WILL WIPE DATA!!
Second thing: Backup nvram.img by sp flash readback and learn how to flash it back (search XDA)- Sometimes you can learn from other's mistakes too! I spent a day and half writing back IMEI and WIFI Mac.
Process (if you don't trust me and want to reproduce the steps yourself)
1. Download stock firmware. (google knows)
2. Patch boot.img so that it doesn't overwrite TWRP with stock recovery on each boot (extract by Carliv Image kitchen and hash out the three lines 663, 664 and 665 mentioning "service flash_recovery /system/bin/install-recovery.sh" in init.rc). I created two copies in the same folder (boot.img, and boot-verified.img) and copied scatter into the same folder for flashing. That's what I saw in the firmware folder.
3. Port TWRP using Carliv Image Kitchen method. I downloaded TWRP from here https://forum.xda-developers.com/android/software/twrp-porter-maker-mediatek-mt67xx-32-t3681861 but didn't use their method. It didn't work. The TWRP for this chip was stated as android N, but worked well.
4. Flash ported TWRP after copying scatter file to the Carliv Imagekitchen output folder and selecting that scatter in SP droid tools. I again created recovery.img and recovery-verified.img. Don't know if its needed that way. You could wait and flash boot and recovery together from the same folder.
5. That's it, you can enter custom recovery now. Get that pesky "panasonic" bootaudio off the system/media folder now! You can stay content after this or proceed to root.
<nandroid backup now, including Nvram and NVdata. Just in case>
6. Download Supersu zip flashable and flash it via TWRP. https://download.chainfire.eu/1113/SuperSU/UPDATE-SuperSU-v2.82-20170528234214.zip?retrieve_file=1 worked for me.
7. Reboot, check root!
If you're more daredevil,
8. Download Xposed flashable zip SDK23 and flash it. Download Xposed installer and copy it to SDcard too.
9. Reboot to recovery and flash the zip. Reboot, install xposed installer. Reboot again.
You're done!
I'll upload my boot.img and ported TWRP if anyone shows any interest in this.
Cheers!
(Bonus: this phone has built in IPtables support in the kernel! I used to flash custom kernel for this ability in other Stock ROMs. AFfirewall works "out of the box"- after rooting, of course!)
Edit: uploaded my modded boot.img and ported TWRP. find it here https://drive.google.com/file/d/1sM1BnyBUFN7PfncFcM7vzIet6gKt3G_L/view?usp=sharing
If you want to go the easy route, unzip the folder and flash it with sp flash. You'll be able to boot into recovery and do the other steps for rooting.
Rememer ONLY DOWNLOAD, don't format, or format and download, or anything!
Click to expand...
Click to collapse
Brother i try this method at Panasonic eluga ray 700 (MT6753_EB_90S55ER7_V1008) flash complete and successful install problem my set dead not On so i install original Panasonic eluga ray 700 (MT6753_EB_90S55ER7_V1008) flash set is dead and not connecting to pc plz help me what i can do ......
andromodgod said:
Brilliant Work man. I also was sort of in your situation as well . i have a panasonic Eluga A3 (Qmobile Noir E2) in my country. Stock Qmobile rom was horrendous. so i flashed the panasonic rom but hated the boot audio and the bloatware that came with it. so i decided to make a slimmed down version of it and successfully did it by using superr's kitchen. and also using the kitchen i removed the encryption on the boot.img and then patched it using magisk for easy rooting without recovery. when flashed together with the modded system.img and modded boot.img and twrp, i was totally in control of my device.
If you need any help with anything mtk send me a pm
also are you able to access internal storage in twrp or not ??
Click to expand...
Click to collapse
Panasonic eluga ray 700 (MT6753_EB_90S55ER7_V1008) after flash set is dead and not connecting to pc plz help us expert......
....
Network drop
Hello dear friend I successfully flash twrp 3.0.2 but I see network signal problem signal drop many time..
Pls tell me how to resolve these issue..
Singnal drop
bad.bid said:
Ya, I fixed Imei issues. this one is like a signal drop once every 15 minutes.
Click to expand...
Click to collapse
Dear sir panasonic eluga note network signal drop many time a day after installing ur ported twrp ..Pls tell me how to resolve signal drop issue..
Really wanna do it but your steps sound way complicated for "non-MTK pro guy". I have that device lying unused. it would be awesome if you could throw a "readme" file in your drive or here with simpler guidance steps like other "TWRP & root installation guide" we have for other phones. Plus You seem like you could port/build a ROM for this device and make substratum friendly. I know it's a big ask & I have a feeling that you like dark UI for that device too . Hoping for the best response.
If you're more daredevil,
8. Download Xposed flashable zip SDK23 and flash it. Download Xposed installer and copy it to SDcard too.
9. Reboot to recovery and flash the zip. Reboot, install xposed installer. Reboot again.
I have a doubt about these two steps
Should i have to flash it twice and have to download two separate file which is one flashable zip and installer. And in the next step 9th which zip file should i flash.
My questions might sound silly but i am asking so because when last time i tried i installed xposed, installed its firmware and then downloaded a module it was cynolockscreen something and applied it. It asked ne to reboot i did but then my phone crashed. Screen was going on and off then i rebooted to recovery and did a factory reset amd since then i haven't done any thing in my phone not even flashed the SuperSU...
Can you please help me with the further steps...
rooting eluga note
can u pls tell me how to root eluga note? i've tried many apps to root it but nothing worked
If you have unlocked bootloader and TWRP, you can flash a newer firmware using HuRUpdater
This steps can be risky for your device if you don't know what you are doing, so try to read some guide about flashing first
before attempt these operations if you are a new to these things.
I don't take any responsability of catastrophic failures and loss of data.
-- I did a titanium backup before the upgrade, but in my case no restore was needed as all data were retained.
In this simple update no factory reset was triggered.
Please read the HUrupdater thread also for more informations.
- Install Unofficial TWRP by Pretoriano80
- Download HuRUpdater 0.3 and put it in a folder in your sdcard
-Search the firmware for your device with Firmware Finder
Make sure you download the correct firmware version for your device (type, region code)
wrong firmware can brick your device
I used updated firmware files APPROVED for my device checked with firmware finder app.
I don't know if flashing NOT APPROVED files will harm your device. You have been warned.
I successfully updated my device from CLT-L29C636B130 to CLT-L29C636B131
***Don't try to rebrand your phone with this method***
- Use FullOTA-MF images of the firmware and download the 3 files needed
in my case:
update.zip
update_data_full_public.zip
update_full_CLT-L29_hw_spcseas.zip
- rename the 3 files to:
update.zip
update_data_public.zip
update_all_hw.zip
and put the files in the same folder with HuRUpdater 0.3
(optional)
- The Update will overwrite your TWRP custom recovery so to retain it automatically rename the TWRP IMAGE
twrp_clt_0.1.img to recovery.img and put in the same folder with others files.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
- Remove all security locks from your phone before rebooting to TWRP.
Go to System- Developer Options
Disable Screen lock (third row)
this will suffice to remove the security locks of the phone (sequences, pin,fingerprints)
-Reboot to TWRP
If you are rooted, remove Magisk first with its uninstaller. I don't know if it's needed but better don't have things like that
messing around during the update. You can reroot later anyway.
-Go to the folder with the files and flash the system using the HuRUpdater_0.3.zip ONLY
That great tool will do all the job needed. After system, it will reflash the TWRP recovery IMG you previoulsly renamed
overwriting again the stock ramdisk_recovery that comes with the firmware.
It will take some minutes, don't panic and let the process end.
You will see some red errors but don't worry,it's fine
- Reboot in your TWRP to check (from inside TWRP , reboot - recovery, be sure not to have a usb cable plugged or it will trigger stock EMUI e-recovery)
- Wipe dalvik and cache
- Reroot new system with Magisk
-Reboot to system and restore the security lock in developer options
- Restore your fingerprints and pins
- Enjoy the update.
Thanks to @zxz0O0 for this great Tool, works good on P20 pro too.
And obviously @Pretoriano80 for his recovery.
Reserved
Working adb sideload?
If an update is already approved by Huawei, can we just download the firmware through HFF and place it in the appropriate folder, go to SYSTEM to check for updates, and then install it?
mangusZen said:
If you have unlocked bootloader and TWRP, you can flash a newer firmware using HuRUpdater
This steps can be risky for your device if you don't know what you are doing, so try to read some guide about flashing first
before attempt these operations if you are a new to these things.
I don't take any responsability of catastrophic failures and loss of data.
-- I did a titanium backup before the upgrade, but in my case no restore was needed as all data were retained.
In this simple update no factory reset was triggered.
Please read the HUrupdater thread also for more informations.
- Install Unofficial TWRP by Pretoriano80
- Download HuRUpdater 0.3 and put it in a folder in your sdcard
-Search the firmware for your device with Firmware Finder
Make sure you download the correct firmware version for your device (type, region code)
wrong firmware can brick your device
I used updated firmware files APPROVED for my device checked with firmware finder app.
I don't know if flashing NOT APPROVED files will harm your device. You have been warned.
I successfully updated my device from CLT-L29C636B130 to CLT-L29C636B131
***Don't try to rebrand your phone with this method***
- Use FullOTA-MF images of the firmware and download the 3 files needed
in my case:
update.zip
update_data_full_public.zip
update_full_CLT-L29_hw_spcseas.zip
- rename the 3 files to:
update.zip
update_data_public.zip
update_all_hw.zip
and put the files in the same folder with HuRUpdater 0.3
(optional)
- The Update will overwrite your TWRP custom recovery so to retain it automatically rename the TWRP IMAGE
twrp_clt_0.1.img to recovery.img and put in the same folder with others files.
- remove all security locks from your phone before rebooting to TWRP.
Go to System- Developer Options
Disable Screen lock (third row)
this will suffice to remove the security locks of the phone (sequences, pin,fingerprints)
-Reboot to TWRP
-If you are rooted, remove Magisk first with its uninstaller. I don't know if it's needed but better don't have things like that
messing around during the update. You can reroot later anyway.
-Go to the folder with the files and flash the system using the HuRUpdater_0.3.zip ONLY
That great tool will do all the job needed. After system, it will reflash the TWRP recovery IMG you previoulsly renamed
overwriting again the stock ramdisk_recovery that comes with the firmware.
- It will take some minutes, don't panic and let the process end.
You will see some red errors but don't worry,it's fine
- Reboot in your TWRP to check (from inside TWRP , reboot - recovery, be sure not to have a usb cable plugged or it will trigger stock EMUI e-recovery)
- Wipe dalvik and cache
- Reroot new system with Magisk 16.4
-Reboot to system and restore the security lock in developer options
- restore your fingerprints and pins
- enjoy the update.
Thanks to @zxz0O0 for this great Tool, works good on P20 pro too.
And obviously @Pretoriano80 for his recovery.
Click to expand...
Click to collapse
ekremxx said:
Working adb sideload?
Click to expand...
Click to collapse
I have not tried that, it depends on the TWRP recovery, let us know if you try
sarichter said:
If an update is already approved by Huawei, can we just download the firmware through HFF and place it in the appropriate folder, go to SYSTEM to check for updates, and then install it?
Click to expand...
Click to collapse
I really don't know, and I don't think it will work.
As far as I know this is the only manual update method for now.
I just updated to unapproved .150 for my c636 and all seems fine
If I reinstall twrp by renaming it as recovery.img, will HuRUupdater install the twrp in recovery_ramdisk, or will it replace eRecovery instead?
If twrp doesn't replace eRecovery, how do I get to eRecovery? As of now, whenever I want to enter recovery, it will get to twrp.
sishafie said:
If I reinstall twrp by renaming it as recovery.img, will HuRUupdater install the twrp in recovery_ramdisk, or will it replace eRecovery instead?
If twrp doesn't replace eRecovery, how do I get to eRecovery? As of now, whenever I want to enter recovery, it will get to twrp.
Click to expand...
Click to collapse
eRecovery is not replaced.
To enter there try other volume button or with a cable plugged
Not working adb sideload... How I can install I not know...not have my phone micro SD card slot...puff
sishafie said:
If I reinstall twrp by renaming it as recovery.img, will HuRUupdater install the twrp in recovery_ramdisk, or will it replace eRecovery instead?
If twrp doesn't replace eRecovery, how do I get to eRecovery? As of now, whenever I want to enter recovery, it will get to twrp.
Click to expand...
Click to collapse
when booting there is a screen prompting to whether you want to go to eRecovery by pressing up or just boot into system and something ike that
---------- Post added at 04:23 PM ---------- Previous post was at 04:23 PM ----------
ekremxx said:
Not working adb sideload... How I can install I not know...not have my phone micro SD card slot...puff
Click to expand...
Click to collapse
why you want to do sideload ? guide clearly explained to install it using TWRP.
if you dont have TWRP, then install it first
I install twrp but how can I install whitour sd card I not have sd card slot my Huawei p20 pro one SIM card join no have sd card slot how I can install i not know.. when I try install abd sideload hrudader say cant find update.zip
update_data_public.zip
update_all_hw.zip
ekremxx said:
I install twrp but how can I install whitour sd card I not have sd card slot my Huawei p20 pro one SIM card join no have sd card slot how I can install i not know.. when I try install abd sideload hrudader say cant find update.zip
update_data_public.zip
update_all_hw.zip
Click to expand...
Click to collapse
The guide never said that you need sdcard
it said, that u need to put all those three files in same folder with the HuruUpdater.zip , and of course you can put it in your internal storage
i wont explain anything here. you better re-read the whole main post, as it already very clear
- put all files in one folder
- reboot to twrp
- flash huruupdater.zip
- boot to system
- reboot to twrp
- flash magisk to reroot
which step exactly that not understandable ? :silly:
I can install that's style orjinal filmware ty so much
Forgive me if this is not the appropriate forum, one question:
I have the Huawei P20, for this phone I only have 2 firmware files, the "Update .zip" and the "update_full_EML_L09_hw_eu.zip ".
Can't find the "update_data_public.zip"
Can I install the new firmware with Hurupdater anyway ? Thanks in advance.
Roberto
moghetto said:
Forgive me if this is not the appropriate forum, one question:
I have the Huawei P20, for this phone I only have 2 firmware files, the "Update .zip" and the "update_full_EML_L09_hw_eu.zip ".
Can't find the "update_data_public.zip"
Can I install the new firmware with Hurupdater anyway ? Thanks in advance.
Roberto
Click to expand...
Click to collapse
You should check and ask at P20 and HURupdater threads.
I don't know about P20.
Hello! Thank you very much for this tutorial .. A question.. I am in Chipset-boston 8.1.0. 001 (01DL) I have the bootloader open, just by installing the recovery that you say in the tutorial and then the other steps, I would not have a problem, right?
can I downgrade firmware safely with this method? im on 150 and want to go back to 130
Ferezesal19 said:
Hello! Thank you very much for this tutorial .. A question.. I am in Chipset-boston 8.1.0. 001 (01DL) I have the bootloader open, just by installing the recovery that you say in the tutorial and then the other steps, I would not have a problem, right?
Click to expand...
Click to collapse
You should not have problem, unless you are trying to rebrand.
Allesa said:
can I downgrade firmware safely with this method? im on 150 and want to go back to 130
Click to expand...
Click to collapse
I don't know about downgrading and I would not raccomend it
mangusZen said:
You should not have problem, unless you are trying to rebrand.
Click to expand...
Click to collapse
Thanks you. Only i want to Update... What firm you recommend That improves the duration of the battery?
TWRP + MAGISK for our Motorola One Action
First of all, let me thank to @ilia3367 for his big effort bringing the joy of mod to our phones (One Vision and Action) and my fellow countryman @sfoot13 for his unvaluable help.
Original guide
Disclaimer
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Backup all your personal information, it'll be wiped.
* This process was performed on the XT2013-1 using PSBS29.-21-20-4 compilation.
Click to expand...
Click to collapse
Instructions
1- Unlock your Motorola One Action using Motorola's Official Guide.
2- Download this file to your PC.
2.1- Get the latest compilation of your firmware, according to your region, here.
2.2- Unzip the file downloaded on step 2 on c:\adb (you should already have installed ADB, Fastboot and Drivers at this point) and unzip the firmware in a place of your convenience.
3- Copy the files KANE_flash_stock.bat and vbmeta.img (remember, both files are from the file you've downloaded on the step 2) of c:\adb to the firmware folder you unzipped on step 2.2.
3.1- Some firmwares have one more system.img_sparsechunk than others, in case the firmware you've download has 10 system.img_sparsechunk add the follow line (after the 9th system.img_sparsechunk) to the .bat file using any text editor (notepad is ok) and save it:
Code:
fastboot flash system_a system.img_sparsechunk.10
4- Copy this files (located at c:\adb) to your External SD (mandatory):
Disable_Dm-Verity_ForceEncrypt.zip
MagiskManager-v7.3.4.apk
Magisk-v19.4.zip
TWRP-3.3.1_Installer_One_Vision.zip
This is where the fun begins.
5- Reboot your phone to bootloader mode.
6- Once detected, execute the KANE_flash_stock.bat you've edited and copied to the firmware folder and wait until the phone reboots to bootloader again (around 2-3 minutes)
7- Open CMD on your computer and type
Code:
cd c:\adb
, then
Code:
fastboot -w
and when it's done
Code:
fastboot boot TWRP-3.3.1_Motorola_One_Vision.img
8- TWRP will boot on your phone, surely in Russian, check the box and swipe to allow modifications on /system. I suggest you to set TWRP on your language (if not Russian of course ), the language setting is on the right column on the third button, and then, the globe icon (the last one), choose your language and set it up using the gray button.
*If you can't get to TWRP the first time, after the Android One Screen, keep pressing volume down and power buttons, when the phone shuts down, release the button power and get into fastboot again and try the command described above (fastboot boot TWRP...). Try until you can get into TWRP recovery, the first time took me around 4-5 times.
8.1- According to your language, go to Install > Select Storage > Micro SD card and flash TWRP-3.3.1_Installer_One_Vision.zip, once it's done, go to the home screen.
8.2- Now tap on Wipe > Format Data > Type Yes and go back to the home screen again.
8.3- Reboot to Recovery.
9- Install > Magisk-v19.4.zip and Disable_Dm-Verity_ForceEncrypt.zip, go to the home screen and tap on Reboot > Bootloader
9.1- On CMD type
Code:
fastboot flash vbmeta_a vbmeta_patch.img
and when it's done, press the power button to start.
10- The phone will show Android One Logo > Unlocked Bootloader warning screen > Android One Logo > It will reboot and will repeat the same process
10.1- After that scary but necessary reboot, it will reach the setup screen and... It will reboot and will repeat the process shown on step 10.
11- Once it reaches the setup screen again it will not reboot again (randoms reboot has been reported, nothing serious, let it reboot and keep it using).
12- Complete setup.
13- Uninstall Magisk Manager and install the APK you've copied to your External SD on step 4.
Now you're rooted.
Thanks for taking the time to read the whole guide and excuse my not-so-well (poor is threshed) english.
The original guide didn't work for me on the part when it says to boot TWRP using fastboot > Wipe Data > boot TWRP via fastboot again, it kept hanging on the Android One screen.
Greetings,
Charly.
Screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I keep getting stuck on boot screen
Has anyone tried it yet? Because I tried to root the device following the guide but can't get it to boot in twrp. Every time I try to, It gets stuck on the boot screen and Then I have to repair it through moto smart assistant
Root Moto One Action - Working on Android Pie (9) and Q (10) 23.01.2020
anongh0st said:
Has anyone tried it yet? Because I tried to root the device following the guide but can't get it to boot in twrp. Every time I try to, It gets stuck on the boot screen and Then I have to repair it through moto smart assistant
Click to expand...
Click to collapse
There's another way to do it.
Download the files and install magisk on your phone.
1. Open magisk and patch your boot.ing
2. Save your patched boot to adb-fastboot folder.
3. Reboot to bootloader.
4. Flash vbmeta.img: fastboot flash vbmeta_a vbmeta.img
5. Flash your patched boot: fastboot flash boot_a PATCHEDBOOT.IMG
6. Flash vbmeta_patched: fastboot flash vbmeta_a vbmeta_patch.img
7. fastboot erase userdata and reboot.
8. Configure your phone and install magisk manager apk.
9. Here, you'll need and app... Franco kernel app, because that app allow you to flash zips without twrp (I don't know a similar app).
10. Open Franco kernel app and install twrp installer zip and reboot.
11. Reboot into FASTBOOT and type fastboot -w after that, select "Reboot Recovery".
12. Now, configure Twrp, change language and format Data (type YES), if you don't format data, you'll end in bootloop.
13. Flash magisk again because the phone was unrooted when twrp installer was flashed and flash Disable_Dm-Verity_ForceEncrypt.zip.
14. Reboot and if everything was successfully, you should be rooted with twrp working.
15. Be grateful
---------- Post added at 02:33 AM ---------- Previous post was at 02:27 AM ----------
@Tuandroidaldia
Thank you so much for the guide
If you want to UPGRADE or DOWNGRADE MAGISK, do this:
Download the Magisk version that you need and reboot into recovery.
1. Flash the downloaded Magisk version.
2. Now flash Disable_Dm-Verity_ForceEncrypt.zip
3. Reboot.
4. Check if everything is ok.
5. Hit or say "thanks".
anongh0st said:
Has anyone tried it yet? Because I tried to root the device following the guide but can't get it to boot in twrp. Every time I try to, It gets stuck on the boot screen and Then I have to repair it through moto smart assistant
Click to expand...
Click to collapse
I rooted my device and then made this guide, so yes, I "followed" it If you're not able to boot into TWRP then you're missing some steps, like "fastboot -w"
Hi, I just have a little query. My device model number is XT2013-2. Since you performed the aforementioned steps on XT2013-1, do you have any idea whether it will work on my device or not? The sole reason I cannot go ahead and try it myself is that the XT2013-2 is currently not supported by Moto Smart Assistant. So I don't want to leave my device in a bricked state with no workaround. Therefore any help in this regard will be highly appreciated.
binary**# said:
Hi, I just have a little query. My device model number is XT2013-2. Since you performed the aforementioned steps on XT2013-1, do you have any idea whether it will work on my device or not? The sole reason I cannot go ahead and try it myself is that the XT2013-2 is currently not supported by Moto Smart Assistant. So I don't want to leave my device in a bricked state with no workaround. Therefore any help in this regard will be highly appreciated.
Click to expand...
Click to collapse
I bricked my device a few times and never used "Moto Smart Assistant", only fastboot and fastboot commands. In order to achieve root on your device, you should get the firmware (step 2.1). In case you have no luck getting root, you can recover your device using fastboot and fastboot commands.
Tuandroidaldia said:
I bricked my device a few times and never used "Moto Smart Assistant", only fastboot and fastboot commands. In order to achieve root on your device, you should get the firmware (step 2.1). In case you have no luck getting root, you can recover your device using fastboot and fastboot commands.
Click to expand...
Click to collapse
Got it. Thanks By the way, is there any batch file to execute these all fastboot commands at one go? Because I only know the fastboot commands for flashing all the sparsechunk, .bin and.img files. But on extracting the stock firmware. there seem to be various other files as well, of which I have no clue whatsoever. Neither do I have any idea regarding their fastboot commands.
binary**# said:
Got it. Thanks By the way, is there any batch file to execute these all fastboot commands at one go? Because I only know the fastboot commands for flashing all the sparsechunk, .bin and.img files. But on extracting the stock firmware. there seem to be various other files as well, of which I have no clue whatsoever. Neither do I have any idea regarding their fastboot commands.
Click to expand...
Click to collapse
Yes, download the file attached in the 2nd step in this post and grab the file "KANE_flash_stock.bat" and if the firmware you downloaded for your XT2013-2 has 10 system.img_sparsechunk add the follow line (after the 9th system.img_sparsechunk) to the .bat file using any text editor (notepad is ok) and save it:
Code:
fastboot flash system_a system.img_sparsechunk.10
Unzip the firmware file and copy "KANE_flash_stock.bat" to the unzipped firmware folder.
Tuandroidaldia said:
Yes, download the file attached in the 2nd step in this post and grab the file "KANE_flash_stock.bat" and if the firmware you downloaded for your XT2013-2 has 10 system.img_sparsechunk add the follow line (after the 9th system.img_sparsechunk) to the .bat file using any text editor (notepad is ok) and save it:
Code:
fastboot flash system_a system.img_sparsechunk.10
Unzip the firmware file and copy "KANE_flash_stock.bat" to the unzipped firmware folder.
Click to expand...
Click to collapse
It seems my wordings confused you. By saying "these fastboot commands", I was referring to the fastboot commands to be used while flashing the files of the stock firmware and not for the rooting process. The latter part you have already explained quite well in the first post itself. Anyways, thanks for the suggestions
So here are my results
After unlocking the bootloader, I was able to execute the process upto the point we have to boot the TWRP recovery. Although the fastboot command showed the success message while booting to twrp recovery, yet the device got stuck in the Android One screen. So then I had to (obviously) skip the flashing of TWRP zip, Magisk zip, and DM Verity file. I went ahead and flashed the vbmeta file and the device got booted to Android OS without any hiccups. So currently the device works normally but without root (and recovery). The only reason I guess for that is you have tried this on XT 2013-1 whereas mine was XT 2013-2. But still, I don't think that should have made such a glaring difference.
As a side note, please change the TWRP boot command from fastboot boot TWRP-3.3.1_One_Vision.img
to fastboot boot TWRP-3.3.1_Motorola_One_Vision.img. The zip file contains the TWRP recovery with the latter name. Although not a big issue for us, still any new user may get confused with the subsequent error message that will pop up.
binary**# said:
It seems my wordings confused you. By saying "these fastboot commands", I was referring to the fastboot commands to be used while flashing the files of the stock firmware and not for the rooting process. The latter part you have already explained quite well in the first post itself. Anyways, thanks for the suggestions
Click to expand...
Click to collapse
I understood you. One of the steps for achieving root is to flash the Stock Firmware (with the patched vbmeta.img), so, If you want to go back to stock, you have to flash the entire firmware using the same commands as described above (with the stock vbmeta.img)
binary**# said:
After unlocking the bootloader, I was able to execute the process upto the point we have to boot the TWRP recovery. Although the fastboot command showed the success message while booting to twrp recovery, yet the device got stuck in the Android One screen. So then I had to (obviously) skip the flashing of TWRP zip, Magisk zip, and DM Verity file. I went ahead and flashed the vbmeta file and the device got booted to Android OS without any hiccups. So currently the device works normally but without root (and recovery). The only reason I guess for that is you have tried this on XT 2013-1 whereas mine was XT 2013-2. But still, I don't think that should have made such a glaring difference.
As a side note, please change the TWRP boot command from fastboot boot TWRP-3.3.1_One_Vision.img
to fastboot boot TWRP-3.3.1_Motorola_One_Vision.img. The zip file contains the TWRP recovery with the latter name. Although not a big issue for us, still any new user may get confused with the subsequent error message that will pop up.
Click to expand...
Click to collapse
Thanks for the note, I'll change the guide ASAP. If you don't get to TWRP at the first try, you have to reboot into bootloader again (keep pressing the power button and volumen down button until it powers off, release the power button and it should reboot to bootloader), enter fastboot boot TWRP-3.3.1_Motorola_One_Vision.img and see if you can boot into TWRP, if not, try again until you can boot to TWRP (it took me around 3 or 4 times to get TWRP booted on my One Action the first time)
Hi Guys!
Got my Action One today (US User here!) and was pulling out my damn hair!!!
For those who can NOT boot into TWRP double check STEP 3!!! My issue was, even though I copied the extra zip file into the firmware folder, it did NOT overwrite the vbmeta.img so it was still loading the non patched version! Once I saw that the version it was flashing was from 9-16-2019 (For my firmware - RETAIL) and not the one from the zip from 9-26-2019! Once did that, on the second try TWRP booted and volia!
SO OP Please add to check the vbmeta.img is the correct version being flashed if they can not boot to TWRP and thanks for the instructions!
Ok so stupid me (This happened to me on my G5s+. I come from Quark so there was only one possible firmware for the phone since it was a verizon branded firmware) flashed the wrong firmware (RETAIL vs RETUS) but this guys doesn't see to work on the XT2013-4 though. The RETAIL firmware will let me have data but no voice on Verizon.
Any suggestions anyone?
My dear ... I did all the correct procedure, following every detail and more than once. And it didn't work! Neither this method nor the replacement of boot.img with the magiskmanager patch. "failed to validate boot image"
Motorola One Action XT2013-1
Sorry for the Google translator.
thalesjans said:
My dear ... I did all the correct procedure, following every detail and more than once. And it didn't work! Neither this method nor the replacement of boot.img with the magiskmanager patch. "failed to validate boot image"
Motorola One Action XT2013-1
Sorry for the Google translator.
Click to expand...
Click to collapse
During the original setup, where did it fail? Did it not boot TWRP?
Nothing works. Neither the original setup nor enter TWRP. This available TWRP doesn't even actually install (Failed). I downloaded from the unofficial TWRP site, and this was OKAY but did not boot ... already did and redo the procedure more than ten times ... give up !!!
thalesjans said:
Nothing works. Neither the original setup nor enter TWRP. This available TWRP doesn't even actually install (Failed). I downloaded from the unofficial TWRP site, and this was OKAY but did not boot ... already did and redo the procedure more than ten times ... give up !!!
Click to expand...
Click to collapse
So you first downloaded and flashed your firmware from the listed and did the sets to add in the extra line of code for it? Did that even complete? Then the fastboot -w? Also you copied over the vbmeta.img in the zip to the firmware folder? Twrp will not boot if that patched file is not there. Also you only boot from twrp not flash it. You don't flash it until later
---------- Post added at 02:46 PM ---------- Previous post was at 02:45 PM ----------
Also what model of the XT2013 are you uaing? There is XT2013-1 thru XR2013-4.
Root success! Xt2013-2
So I finally rooted my Moto One Action (XT2013-2). I read on many forums that the method of flashing the patched boot.img file gave some kind of validation error for their boot files. But anyhow I went ahead with the very method and was able to successfully root my device. Here are the steps to be followed.
STEPS:
View attachment 4870223
NOTE: USERS HAVING XT 2013-2 (INDIAN VARIANT) MAY DIRECTLY TAKE MY PATCHED BOOT.IMG FILE. IT IS BASED ON THE FIRMWARE VERSION PSBS29.39-23-6
1. Extract the boot.img file from the stock firmware.
2. Patch it via Magisk Manager. The magisk_patched.img file will now be created under the Downloads folder. Move it to the platform-tools folder on your desktop.
3. Reboot to fastboot mode and flash the vbmeta file via fastboot flash vbmeta_a vbmeta.img
4. Now use the fastboot flash boot_a magisk_patched.img to flash the patched boot file.
5. Next, flash the vbmeta patched file using fastboot flash vbmeta_a vbmeta_patch.img
6. Then erase user data using fastboot erase userdata
7. Finally fastboot reboot
8 Now set up the device and install the Magisk Manager app.
9. Head over to the Magisk Manager app. It will ask for some additional configurations. Allow it. It will take a minute or two for the Magisk configuration to complete. Once done, your device will automatically reboot once. it's normal.
10. That's it. Your Moto One Action will now be successfully rooted (as already mentioned, the process was carried on the version XT 2013-2.)
WARNING
Do it at your own risk , neither XDA nor me will be responsible for any damage that may occur
Overview
Rooting your device will give you freedom to enjoy plethora of features like removing OEM bloatwares , using system level Firewall , backing up and restoring all data of Apps , underclocking kernel for better battery life etc .
Requirements
Bootloader Unlocked Realme GT Neo 2 (Guide - https://forum.xda-developers.com/t/bootloader-unlocking-on-indian-model-rui-2-0-latest-a07.4391679/ )
A PC (windows or linux) with adb- fastboot installed
USB cable
Magisk Stable Apk
TWRP.img thanks to @ SathamHussainM from his thread on the same topic
Downloads ADB-FASTBOOT setup for windows https://forum.xda-developers.com/at...484757/?hash=78ebfa42e75a5def462676a93fff24c7
TWRP.img file link https://www.androidfilehost.com/?fid=17825722713688258515
Magisk23 apk Click here
Root Checker App link https://apkpure.com/root-and-safetynet-checker/com.atominvention.rootchecker/download?from=details
STEPSCopy this file to your PC C:\adb folder and rename it to twrp.img
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Boot your device into fastboot mode Open Command Line
Go To C:\adb folder , press shift and do a right click , select open Powershell window here
Now type
fastboot devices
, press enter it should show your device now
now type
fastboot boot twrp.img
Process will take 10 second
Your device will reboot and after some time it will show TWRP logo ( it takes time 1 min approx )
wait some time
then In PC file explorer it will show realme gt neo 2 , open it
go to internal storage > Downloads and copy paste the twrp.img file and magisk alpha apk
In twrp backup BOOT , EFS, Modem ,Persist-Image
after backup is done come back to TWRP home and tap on Install button go to the folder where you saved both the files
and select Install image button , now it will show twrp.img file , tap on it then select recovery partition and swipe to confirm flash
After process is complete press Back button and come to TWRP home
Again press install button and select magisk.apk and swipe to confirm flash , this will install Magisk 23 after process is complete press home button go to reboot tab and select system
, Now phone will reboot to system
In phone open file manager and install magisk.apk
Open magisk app it will show magisk installed
just to be sure press the install button and select direct install and press Lets GO
After process is complete press the reboot button and it will boot back to system mode now
Your phone is rooted with magisk 23 and you are eligible to enjoy variety of mods and themes for your device .
Q1) Why are you not flashing recovery directly ?
A) Becuase Its risky (very low chance of flashing failing from fastboot ),So
first we boot this twrp file temporarily and backup all important partitions
When it is clear recovery is working fine , we copy the twrp.img and flash it from twrp to make it permanent .
Q2) Why are you not flashing magisk patched image ?
Ans) Becuase Its risky (the patched boot image you got may not be of your model or software version which will cause bootloop , SO
we trust in magisk to use our device boot.img to create a patched boot.img with magisk support , then we reflash magisk from magisk App to confirm it .
Is there any way to flash stock rom if twrp is installed?
This post says "for all models" but your bootloader unlocker post is for Indian model?
Just asking. It can cause misunderstanding.
Spl1tz said:
This post says "for all models" but your bootloader unlocker post is for Indian model?
Just asking. It can cause misunderstanding.
Click to expand...
Click to collapse
This guide will work for all variants of GT NEO 2 , however the unlocking guide is for Indian Variant only .
So if you somehow managed to unlock Non-Indian Model of RMX3370 you can safely follow this guide (no liabilities of OP ) to install TWRP then root your device
ultimatesprit said:
Is there any way to flash stock rom if twrp is installed?
Click to expand...
Click to collapse
Why do you want to flash stock ROM ?
If it is booting problem you can read this guide
If you just want to reset you have to first remove magisk then from TWRP do factory reset from WIPE section.
However you can try this RollBack ZIP for Indian Variant of Realme GT NEO 2
Email44841 said:
This guide will work for all variants of GT NEO 2 , however the unlocking guide is for Indian Variant only .
So if you somehow managed to unlock Non-Indian Model of RMX3370 you can safely follow this guide (no liabilities of OP ) to install TWRP then root your device
Click to expand...
Click to collapse
Ah gotcha. And now i see bootloader unlock for all variants too. Finally!
Thank you for your hard work
Email44841 said:
Why do you want to flash stock ROM ?
If it is booting problem you can read this guide
If you just want to reset you have to first remove magisk then from TWRP do factory reset from WIPE section.
However you can try this RollBack ZIP for Indian Variant of Realme GT NEO 2
Click to expand...
Click to collapse
This is my first realme device.I would prefer to keep a stock rom to flash incase any boot loop. Not decided to flash twrp permanently. i hope i can boot to stock recovery and flash rollback package to be in stock..Will it work?
Is it possible to use Kernal editor app after root to undervolt/overvolt GPU?
I have moved magisk23aplha.apk to /sdcard/download, but i can't find it in the path after click 'Install Zip', how?
lspgzz said:
I have moved magisk23aplha.apk to /sdcard/download, but i can't find it in the path after click 'Install Zip', how?
Click to expand...
Click to collapse
sry for disturbe, i got it. Just rename the file into '.zip' and install it
Spl1tz said:
ow i see bootloader unlock for all variants too
Click to expand...
Click to collapse
Incorrect. Not all variants
can we update the magisk to latest version (stable or beta) ?
Yes
reversegear said:
can we update the magisk to latest version (stable or beta) ?
Click to expand...
Click to collapse
You can Safely update to latest Magisk releases
My twrp says "internal storage 0 MB", rui3.0 any idea how to fix this?
I booted in twrp when i click any option it makes a hissing noise (in twrp) and when i try to backup says unable to mount storage (unable to mount /data/media/TWRP/.twrps faild to mount '/data' (invalid argument) also i cant see my device on my computer.
theogr91 said:
I booted in twrp when i click any option it makes a hissing noise (in twrp) and when i try to backup says unable to mount storage (unable to mount /data/media/TWRP/.twrps faild to mount '/data' (invalid argument) also i cant see my device on my computer.
Click to expand...
Click to collapse
Are you able to boot into ROM ?
What have you done before this started happening ?
coz that happens when rui gets corrupted and is unable to mount /data and If unable to boot into saystem then the only solution is to do flash stock boot.IMG and wipe all data
RMX3370 said:
Are you able to boot into ROM ?
What have you done before this started happening ?
coz that happens when rui gets corrupted and is unable to mount /data and If unable to boot into saystem then the only solution is to do flash stock boot.IMG and wipe all data
Click to expand...
Click to collapse
After i unlocked bootloader i flashed ui 2 twrp to ui3 and bricked i fixed it with ofp flash sideload from twrp i can use my phone just bs on twrp