hi
i have a deca-core note 4, but when i tried to update some mui or something via the update menu, it just came up with a blue chinese recovery mode after a reboot, so maybe someone can help me out with what to do next?
and if its deca-core(2.1ghz), then it is mediatek, not snapdragon? (i dont see any model numbers on the box)
i also managed to get into the fastboot mode with the white soviet bunny fixing the robot, but which tool should i use next then?
maybe something from here? - https://forum.xda-developers.com/redmi-note-4/how-to/guide-redmi-note-4-unlock-bootloader-t3517806
and which tool could i use to check if it's unlocked or not?
and if im already hacking the stuff around, should i already root it somehow then? currently im not even sure what is twrp and all of the other stuff... :s
(and the recovery mode had somekind of big alien head as a logo with some red text below it)
the stock version was also somekind of android 6.0, but can i somehow upgrade it to 7.0 then? (which i actually wanted to achieve via the update menu, but it only downloaded 104MB of mui update... and then crashed...)
thanks
jimmer1 said:
hi
i have a deca-core note 4, but when i tried to update some mui or something via the update menu, it just came up with a blue chinese recovery mode after a reboot, so maybe someone can help me out with what to do next?
and if its deca-core(2.1ghz), then it is mediatek, not snapdragon? (i dont see any model numbers on the box)
i also managed to get into the fastboot mode with the white soviet bunny fixing the robot, but which tool should i use next then?
maybe something from here? - https://forum.xda-developers.com/redmi-note-4/how-to/guide-redmi-note-4-unlock-bootloader-t3517806
and which tool could i use to check if it's unlocked or not?
and if im already hacking the stuff around, should i already root it somehow then? currently im not even sure what is twrp and all of the other stuff... :s
(and the recovery mode had somekind of big alien head as a logo with some red text below it)
the stock version was also somekind of android 6.0, but can i somehow upgrade it to 7.0 then? (which i actually wanted to achieve via the update menu, but it only downloaded 104MB of mui update... and then crashed...)
thanks
Click to expand...
Click to collapse
Deca core means it's MediaTek which means your phone will never receive Android 7.
Which ROM are you actually trying to install?
it was just doing its own mui update, but then it did not boot anymore after the reboot and now i dont really know what do i need to do next... i did get it to fastboot mode, but i dont know what i need to do next and which files i need etc... (the main recovery mode seems to be in chinese, but i did notice the fastboot button in it... after the big alien head logo with some red text below it...)
how can i check if its unlocked and which recovery version should i go through then?:s
well, seems like it booted back up after i just switched the phone off overnight....
and now it wants to do another mui v9.5.2.0.mbfmifa stable update, 1,4gb.... so how was it even 104mb before...
(update includes global browser v9.5.6 to fix GDPR and FC(04-13), fix security exception(04-13) and fix reboot always after OTA update(04-13)...)
and the current version seems to be android 6.0 MRA58K (2018-02-05) with MUI global 9.5 Stable, 9.5.1.0(mbfmifa)...
but should i even bother with the update then or just use the phone as is?
(i did not see any OEM unlocking menu either, altho i did enable the developer options...)
well, if i would want to root it, then which procedure should i go through? and is there any rooting procedure for Mediatek chip anyway?
jimmer1 said:
well, if i would want to root it, then which procedure should i go through? and is there any rooting procedure for Mediatek chip anyway?
Click to expand...
Click to collapse
https://forum.xda-developers.com/redmi-note-4/development/how-to-install-twrp-recovery-root-t3717952
So lets begin.
Your phone is for sure mediatek since its decacore codenamed
NIKEL remember it for future use.
Doing stuff with a mtk device actually harder than a snapdragon(eg. xiaomi redmi note 4 snapdragon) and in my point of view and experience i have had chances of bricking a mtk are more, that doesnt mean that you will brick your device. So if you are ready to take the risk do it. You will be rewarded by being free from thr Miui, having a lot more battery,performance and upgrading to the latest Android 8.1 as well as some great tweaks!( I hate miui lol)
:Basic Info:
P.S.->(MAKE A BACKUP OF EVERYTHING AS YOUR DATA MIGHT BE ERASED IF YOU UNLOCK YOUR BOOTLOADER.)
P.S.2-> (If my explaination is unclear forgive me as its almost 6 months that i erased miui from my phone)
Now for the procedure, go to settings->System->About Phone->Tap Build number 7 times.This will enable developer options.Go again to settings if i recall dev settings are generated before the System. Open Dev settings and scroll a little but, dont touch anything though. Spot a setting that says about OEM unlock,open it. If it says recovery locked its locked,otherwise unlocked.
Now if you want to unlock recovery you should apply for unlock permission here ( http://en.miui.com/unlock). Log in with your mi account read and follow the steps given. You will eventually apply for unlock permission after writing and accepting some stuff. At most you will wait 7 to 14 days till a message containing a code and further steps to unlocking bootloader will be sent to your phone number. You will need a pc for this and downloading miflashtool which you can find going to the page i gave you before. Follow the steps given and pray to god that everything will be fine.
hase 1:
Here comes the hard part:
Flasher Toolkit – TWRP 3.0.2 and ROOT Universal Tool for Redmi Note 4 MTK
The complete and very easy to use tool to flash TWRP Custom Recovery and easily root your Redmi Note 4 MTK phone with a few simple steps. Below you’ll find a short tutorial on how to use this tool.
Latest version of Flasher Toolkit for NIKEL:
ok thanks, i will probably try this when i have some more time, but the last link seems to be missing.
(and cpu-z also says that its mediatek helio x20, 2.11ghz, mt6797)
Related
PRO 7 PLUS A ROM TO GLOBAL(PRO 7 PLUS M793Q)
"1. Download Flyme 6.7.10.31 beta rom from official chinese Flyme site and put it to your phone's main folder
2. Enter Recovery mode (Volume Up + Power), select "Update firmware" and "Wipe data", then wait until the update is done
3. Download Flyme 6.1.2.0G rom from official site and also put it to your phone just like the chinese rom
4. Enter Recovery mode again and do the same things - select "Update firmware" and "Wipe data", then wait until the update is done
Good luck with this guide and dont forget to wipe twice your device phone."
Hi everyone,I managed to succesfully install it with the given steps above. Thanks a lot. But, I want to switch to "A(Chinese)" from "Global" software again. I tried the methods i already knew but i get the error "too old". What should i do? Is there anyone tried both softwares and can help me out?I want to go back to A(Chinese) version of the software from Global version. How can i do that? Please help.
ModelRO 7 PLUS M793Q
up Is there nobody to help?
its is not possible if u update your chines A with G the phone id change too .. so you stuck on that unless Meizu do something about it
Lazohiwa said:
its is not possible if u update your chines A with G the phone id change too .. so you stuck on that unless Meizu do something about it
Click to expand...
Click to collapse
If the friend who made the share had caught this warning. Because no software is installed on the device.
what is the benefit going from A to G, and vice-versa?
BADA 187 said:
what is the benefit going from A to G, and vice-versa?
Click to expand...
Click to collapse
The chinese version A has no audio resampling built in by default system wide and also gives acces to hidden nfc chip that is restricted to be used exclusively within meizu pay app - payment system in china, which in turn hasnt been launched yet. Not to mention the lack of ubiquitous google eye
It is actively discussed on russian forum 4pda.ru
Hi folks,
Today it's a great day for me : I have successfully patched the kernel to have a 100% working TWRP 3.2.1 for our Maze Alpha 4G.
I have port a Jemmini build for Bluboo S1 and I have patch the kernel to have a working touch panel
I have followed this Thead
For the Maze Alpha 6G version, you can test it and tell me please.
How to flash:
I Fastboot method (must unlock device) :
1- Reboot your phone in bootloader mode : adb reboot bootloader or phone off, press and hold at the same time POWER and Vol+ buttons
2- Connect your phone to your computer with adb/fastboot already installed
3- Unlock your bootloader : fastboot oem unlock (it will erase you data, only data)
4- Flash the recovery : fastboot flash recovery recovery_maze_alpha_4G_twrp-321.img
II SPFlashTool method (no need to unlock device) :
1- Download latest version of SPFlashTools.
2- Execute it and load the provided scatter (the recovery image must be in the same folder as the scatter and must be renamed to recovery.img) then press "Dowbload" button
3a- windows SPFlashTools users : phone off, press VOL+ and connect it to your PC (running SPFlashTool and waiting for phone connetion)
3b- linux SPFlashTools users : phone off and connected to PC , press VOL+ and POWER while your PC is running SPFlashTool (with sudo) and waiting for phone connetion.
Update : you can found here the latest version: TWRP 3.3.0 for MAze Alpha 4Ghttps://github.com/dreambo/android_device_maze_alpha/releases/tag/3.3.0
have a nice day.
Works great on Maze alpha 4G. Thanks.
But I forgot to save original recovery...
super_sonic said:
Works great on Maze alpha 4G. Thanks.
But I forgot to save original recovery...
Click to expand...
Click to collapse
You can get the original recovery from the stock rom designed for SPFlashTool, provided here
dreambo said:
You can get the original recovery from the stock rom designed for SPFlashTool, provided here
Click to expand...
Click to collapse
Thanks. Can you share stock recovery.img, if you have it? I have recovery-verified.img from V05 but I don't know if there is a new update and if size is correct: 11,54MB. Your TWRP recovery has got a size of 14.24MB...
Can you make a small procedure on how to install it? Will help many nOOb's out.
And people need to report back issues and successes !!!! Again I see many questions and people with issues that we seniors try to help out with that end up in no more response which to me is not done and not helping others.
I have a 6GB version that I could test on but at the moment I am using it for other stuff and I can't risk bricking it this week.
Would finally love to start some stuff happening on this phone.
Ok in the process of doing so on my 6GB/64GB version.
edit : congratz I now have a 'phone' that can only go into TWRP . Should have never ever done this!
Says no OS installed ... really nice
Edit 2: after hours wasted was able to get your zipped rom on the Maze but I got no boot with that TWRP, so flashed recovery-verified.img from the 6GB rom from Alpha I had downloaded ... It would then start up but show 4GB out of 6GB. No good but at least all the rest seemed to work. All other effort to get it going back with the proper kernel etc resulted in frustration.
So now to flash the official rom back via their tool... that one got me really frustrated and was completely my fault that I couldn't figure it out. But you know angry, frustrated, must get it back to work, can do this ... After all these years of toying with phones we are so used to pressing 'power and vol+ or vol-' together to make something work. Now in the end I re-read the manual again and saw that you only have to push vol+ and NOT vol+ and power together or it wont go in the mode it should go to make it flash!!
In case this happens : The best advice I can give to people is to download the proper MTK drivers. Search for vcom drivers for MTK and you will find.
Print out the instructions and mark every step you do to the letter. The flashing itself only takes like 3 or 4 minutes
lukesan said:
Ok in the process of doing so on my 6GB/64GB version.
edit : congratz I now have a 'phone' that can only go into TWRP . Should have never ever done this!
Says no OS installed ... really nice
Edit 2: after hours wasted was able to get your zipped rom on the Maze but I got no boot with that TWRP, so flashed recovery-verified.img from the 6GB rom from Alpha I had downloaded ... It would then start up but show 4GB out of 6GB. No good but at least all the rest seemed to work. All other effort to get it going back with the proper kernel etc resulted in frustration.
So now to flash the official rom back via their tool... that one got me really frustrated and was completely my fault that I couldn't figure it out. But you know angry, frustrated, must get it back to work, can do this ... After all these years of toying with phones we are so used to pressing 'power and vol+ or vol-' together to make something work. Now in the end I re-read the manual again and saw that you only have to push vol+ and NOT vol+ and power together or it wont go in the mode it should go to make it flash!!
In case this happens : The best advice I can give to people is to download the proper MTK drivers. Search for vcom drivers for MTK and you will find.
Print out the instructions and mark every step you do to the letter. The flashing itself only takes like 3 or 4 minutes
Click to expand...
Click to collapse
Haha I did the same exact thing..and managed to get it working after flashing it with the spflash tool but the trick is if you have Windows 10 latest version you won't be able to do this..at least I couldn't because of driver incompatibility so in my case:
1 I installed Windows 7 and installed mtk drivers for spflash tool
2.booted into twrp
2.1 if you can't boot into twrp or it doesn't turn on you can still try this
3.Start sp flash tool and download the zip the one(in case of trouble)that the moderator published
4. Load the scatter file and make sure that all of the files and the scatter are in the same folder.
5.click download and leave it like that
6.plug in your phone in fastboot if you can't try one of the following
6.1 just plug it in turned off and monitor spflash tool status
6.2 plug it in holding volume up key (just volume not power)
6.3 in twrp go to boot and boot into bootloader
And the tool should do the rest
If all else fails check the drivers one more time
After all that if you are feeling adventurous flash twrp one more time and do not factory reset through twrp ! Because that was the problem in my case and after you unlock bootloader boot your phone and go through the setup without setting the password because twrp will be locked.
Good luck.
frumac96 said:
Haha I did the same exact thing..and managed to get it working after flashing it with the spflash tool but the trick is if you have Windows 10 latest version you won't be able to do this..at least I couldn't because of driver incompatibility so in my case:
1 I installed Windows 7 and installed mtk drivers for spflash tool
2.booted into twrp
2.1 if you can't boot into twrp or it doesn't turn on you can still try this
3.Start sp flash tool and download the zip the one(in case of trouble)that the moderator published
4. Load the scatter file and make sure that all of the files and the scatter are in the same folder.
5.click download and leave it like that
6.plug in your phone in fastboot if you can't try one of the following
6.1 just plug it in turned off and monitor spflash tool status
6.2 plug it in holding volume up key (just volume not power)
6.3 in twrp go to boot and boot into bootloader
And the tool should do the rest
If all else fails check the drivers one more time
After all that if you are feeling adventurous flash twrp one more time and do not factory reset through twrp ! Because that was the problem in my case and after you unlock bootloader boot your phone and go through the setup without setting the password because twrp will be locked.
Good luck.
Click to expand...
Click to collapse
Wait a sec., missing a couple of things here.
1) Do you have a 6GB ?
2) In case you have a 6GB did you manage to get it working, rooted and all?
Your point 6) well I flashed mine on the latest 64bit win10 ... but.... if the phone is off and you connect the usb cable my phone tried to boot up either in twrp with no com port. Also booting it in bootloader doesn't make the comport visible so you can't flash.
The only way to make mine visible for the flashtool was to press vol+ and then connect the usb cable.
Btw I am glad someone finally responds and spreads information. A very good post! Your first 'thanks' well deserved!
I wonder where the guys are that I was trying to help. Did they throw their phones away or something? Sharing is caring I thought.
I want to root mine to alter the camera settings and the media xml file. I find it strange that our sensor, which is the same as in my wife's Xiaomi's, takes seriously bad pictures.
lukesan said:
Wait a sec., missing a couple of things here.
1) Do you have a 6GB ?
2) In case you have a 6GB did you manage to get it working, rooted and all?
Your point 6) well I flashed mine on the latest 64bit win10 ... but.... if the phone is off and you connect the usb cable my phone tried to boot up either in twrp with no com port. Also booting it in bootloader doesn't make the comport visible so you can't flash.
The only way to make mine visible for the flashtool was to press vol+ and then connect the usb cable.
Btw I am glad someone finally responds and spreads information. A very good post! Your first 'thanks' well deserved!
I wonder where the guys are that I was trying to help. Did they throw their phones away or something? Sharing is caring I thought.
I want to root mine to alter the camera settings and the media xml file. I find it strange that our sensor, which is the same as in my wife's Xiaomi's, takes seriously bad pictures.
Click to expand...
Click to collapse
Sorry forgot to mention I have a 4 GB version but since maze is not providing the roms on their website any further development will be limited..thank God for dreambo he is the only guy doing any work here and like you said nobody is responding to any questions asked..shame really because maze is a great phone with a terrible camera..which drivers did you use on Windows 10? because I tried a hundred of them and non of them recognize my phone..and in adb I can run the command fastboot reboot bootloader but after reboot none of the commands are working .
And yes I did manage to install twrp and root using magisk and I to hope that all those other guys didn't brick their phones
frumac96 said:
Sorry forgot to mention I have a 4 GB version but since maze is not providing the roms on their website any further development will be limited..thank God for dreambo he is the only guy doing any work here and like you said nobody is responding to any questions asked..shame really because maze is a great phone with a terrible camera..which drivers did you use on Windows 10? because I tried a hundred of them and non of them recognize my phone..and in adb I can run the command fastboot reboot bootloader but after reboot none of the commands are working .
And yes I did manage to install twrp and root using magisk and I to hope that all those other guys didn't brick their phones
Click to expand...
Click to collapse
This is the filename I used on Windows 10 VCOM Drivers (All MTK Devices & All Windows OS version).zip I think I downloaded it from XDA somewhere.
Also something you must know https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/
Another thing I experienced is that one USB connector is not the other one on a pc. Always connect it to the ones directly on the main board next to the other device outputs like audio etc. and preferably not go through ones that have been extended via a cable like the ones on top of the casing or so. Also a must have application is usbdeview.
Well should be easy to get it going if you can boot it into 'fastboot' then you can try as much as you want to. But djeeeeezzzz the letters are very small when you boot it with a power+volume up . Also check that volume up will toggle between 'fastboot', 'recovery' and 'normal start' and volume minus will select it, not the power button which would be more logical to me.
I might have another go at trying to get it working on my 6GB but it involves having a lot of time and knowing that I will get frustrated. Installing all apps and settings is also a time consuming thing. Once you have TWRP on it it all becomes easy to backup. So many things to test or try.
Maybe dreambo has an idea on how to get mine up to a 6GB one as it is probably only indicated in the kernel.
Anyway I will continue to write down my progress.
Ok more frustration. Done multiple things to try to get this running. It's good to know that the original rom is easy to install again after practice.
Take 1: Try to install clean 6GB rom and immediately install TWRP.
Results: Dreambo forgot 1 step and that is to allow OEM unlock in the developer options. If you do the adb command to unlock press volume up and it will unlock (very hard to see, very small letters on the display in bootloader mode)
Well TWRP starts but immediately I get a message 'mount decrypt data password' which I tried a couple of things but no go. Also googled... different solutions but always ending in a bootloop to TWRP
A possible solution that I read was to create a startup pin .... no go 'pin not valid'
Take 2: Take all the rom files and change the scatter file with the one dreambo provided.... Thought it was successful but ended up with the same Chinese recovery. Trying to figure out why since the filename was correct like indicated in the scatter file. Came to the conclusion that the original file was/is called recovery-verified.img and not recovery.img. Really really strange this one as in the original scatter file it also points to recovery.img. So this one I will have to investigate. Renaming the TWRP file to recovery-verified.img lead to a error during the initial scan of the flashtool.
So moral of the story is that I am back on square 1 and lost 2 hours today (plus putting all apps and settings back) today.
I get a bit lost, is this TWRP method only working with the 6GB or also with the 4GB version?
CYberdog11 said:
I get a bit lost, is this TWRP method only working with the 6GB or also with the 4GB version?
Click to expand...
Click to collapse
There is no fundamental difference between 6G and 4G version.
It must works in boat versions.
If you have issues with SPFlashTool try this (no need to install any drivers on Windows 10) :
Put the preloader.bin (found in the rom package designed for SPFlashTool) in the same folder as the recovery.img without checking it the list of partitions (only recovery must be checked) and click on Download to flash the recovery, as usual.
Perhaps SPFlashTool cannot read by himself the preloader in the EMMC, and we must provide it.
The linux version of SPFlashTool not works at this moment, I do not know why
With the SPflashtool I always get the error:
ERROR:STATUS_DA_HASH_MISMATCH (0xC0070004)
HINT
CYberdog11 said:
With the SPflashtool I always get the error:
ERROR:STATUS_DA_HASH_MISMATCH (0xC0070004)
HINT
Click to expand...
Click to collapse
From another thread:
mmakdz said:
google translate
Hello
I had the same problem, (error BROM ERROR: STATUS_DA_HASH_MISMATCH)
what I did: I use Windows 7 System
1- clear all drivers for smartphones with "usbdeview-2-17"
2- install Drivers "Drivers_Auto_Installer_v1.1236.00"
3- install "PdaNetA4170"
4- use "SP_Flash_Tool_v5.1708_Win" to flash the rom. first flash the preloader alone and then flash the others.
the problem was the bad installation of the drivers, after that everything went well for me.
try it can work for you too.
the mentioned software is easy to find on google
Click to expand...
Click to collapse
dreambo said:
There is no fundamental difference between 6G and 4G version.
It must works in boat versions.
If you have issues with SPFlashTool try this (no need to install any drivers on Windows 10) :
Put the preloader.bin (found in the rom package designed for SPFlashTool) in the same folder as the recovery.img without checking it the list of partitions (only recovery must be checked) and click on Download to flash the recovery, as usual.
Perhaps SPFlashTool cannot read by himself the preloader in the EMMC, and we must provide it.
The linux version of SPFlashTool not works at this moment, I do not know why
Click to expand...
Click to collapse
If there is no difference between the 4GB and 6GB then why did I literally spend days on trying this and documenting what happened?
lukesan said:
If there is no difference between the 4GB and 6GB then why did I literally spend days on trying this and documenting what happened?
Click to expand...
Click to collapse
Do you have the 2 versions of the phone and do you have notice any difference of the flashing procedure ?
dreambo said:
Do you have the 2 versions of the phone and do you have notice any difference of the flashing procedure ?
Click to expand...
Click to collapse
I only have the 6GB version of the Maze Alpha. But you wrote that the procedure should work for both versions. I think I wrote down what happened with mine if I installed TWRP.
I tried both the 'regular' flashing and then the full rom install with the trick to put the files in the directory and rename but both ended up as I've written in my previous post.
lukesan said:
I only have the 6GB version of the Maze Alpha. But you wrote that the procedure should work for both versions. I think I wrote down what happened with mine if I installed TWRP.
I tried both the 'regular' flashing and then the full rom install with the trick to put the files in the directory and rename but both ended up as I've written in my previous post.
Click to expand...
Click to collapse
From times to times, I notice trouble with flashing using SPFlashTools.
First (when I post my first post relating of the root) I use the linux version : no issues it works perfect, no need of any drivers!
Actually, no way to have it working on linux, why I do not know!
I have tried Windows 10 and I notice that we have to provide the preloader to have it working, as I write in my post.
In theory, and only in theory, the SPFlashTool must works the same manner in any phone with a Mediatek SOC.
But in reality, we have notice that with exactly the same phone the flashing procedure works for some users and not for others!
SPFlashTool is a very capricious software, there is no warranty to have it 100% working in any platform, even with the same OS.
dreambo said:
From times to times, I notice trouble with flashing using SPFlashTools.
First (when I post my first post relating of the root) I use the linux version : no issues it works perfect, no need of any drivers!
Actually, no way to have it working on linux, why I do not know!
I have tried Windows 10 and I notice that we have to provide the preloader to have it working, as I write in my post.
In theory, and only in theory, the SPFlashTool must works the same manner in any phone with a Mediatek SOC.
But in reality, we have notice that with exactly the same phone the flashing procedure works for some users and not for others!
SPFlashTool is a very capricious software, there is no warranty to have it 100% working in any platform, even with the same OS.
Click to expand...
Click to collapse
The thing is that I have no issue with flashing the software as I can perfectly flash the original rom. The problem is that when flashing the TWRP file, in both options by the way, so also via method 1, I get a boot loop.
Hello XDA Forums,
I have been a guest on the website for a while now when looking for android knowledge and I usually grasp a good amount of whatever I am trying to accomplish. However, the issue I am currently having I feel is considered IMPOSSIBLE to fix and I want to confirm that by this community.
Phone: Blu
Model: NEO XL N110U
Android build version: 6.0
Custom build version (It’s a stock a downloaded, ill explain in a sec)” BLU_N110U_V10_GENERIC_MARSHMALLOW 05-08-2016 16:30
What happened is that about a year ago or so I updated the android version from lollipop to marshmallow using the OTA update (which is the wireless update). Worst decision ever as I found out that this update gave me 4 specific viruses that sends my information over to a Chinese server. Here are links on the virus:
https://www.droid-life.com/2016/11/15/blu-security/
https://blog.malwarebytes.com/cybercrime/2016/11/mobile-menace-monday-adups-old-and-new/
https://android.gadgethacks.com/new...be-affected-by-adups-chinese-spyware-0175014/
With this problem, I thought “I can just root my device and delete the files… right”? I never rooted a device before, but I have jail broken iphones, modded psps, and ds so I felt like this would be easy……Turns out its impossible if you already updated to that wireless update with marshellow. I also tried unlocking bootloader and that failed super hard as well! Here is what I tried:
1. Tried Kingroot app – failed
2. Tried kingroot on pC – failed
3. Went into developer options and enabled usb debugging and oem unlocking to TRY and unlock the bootloader. – that part worked……HOWEVER
4. Went into the recovery and choice reboot to bootloader. Then connected my Blu phone to my PC, went into Command prompt and typed, “fastboot oem unlock” (I believe I had to download fastboot and adb tools first). – This was painful for me. It gave me the option to unlock the bootloader using the up and down volume buttons. I need to press “Volume up” on my phone to confirm the OEM unlock……..HOWEVER THAT HAS BEEN COMPLETELY DISABLED. The buttons work, but when I need to confirm the oem unlock, it doesn’t allow me to do this. THIS I BELIEVE HAS BEEN PURPOSELY DONE.
5. I downloaded a stock version of my phone’s rom but at a lower android number (5.1) and tried to flash it to the phone using SP Flash tools. – Failed. It would stay illuminated black and the intro sound would come on but I wouldn’t see anything. I looked into that and I believe that is because there is something called version binding where if I update the version build, I can’t downgrade to use the same exploit.
6. Since the phone was bricked, I wanted to try to bring it back to life by downloading the stock rom for my phone at the same virus build version I’m at now and flash it to the phone. – It worked with viruses and all.
7. I Then thought, “Can’t I use open the rom file and delete the viruses I want, then flash it to the phone?” So I tried that by using mtk extractor which allowed me to open the system.img file for the stock rom which contains the android data. From there I went into the apps folder and deleted the 4 virus apps. Then I packaged the system.img back together into one file and then used that system.img when I used sp flash tool to flash the rom onto the phone. – It was stuck on the logo……I can still access the recovery fine and still doesn’t allow me to oem unlock.
This is where I have given up. At this point, I feel like I would need to learn more about the system.img file and what it looks for in the beginning. I just want to fool it into booting without those apps. I know there is something stopping it from booting because when I go into the recovery part and select the option to do a “root integrity check” it tells me those specific apps are missing. Is there any way to change the root integrity check to not look for those apps?
So I know this a lot of information but I need to write this down for all the steps I toke. I hope that this thread can help anyone with a Blu Neo XL device come to some information. If I can confirm from this forum that there is nothing that can be done. I feel then a law suit with Blu is in order and everyone should throw out there compromised phones. I have seen numerous other posts on this subject and so far NO ONE HAS ANSWERED EVEN ONCE. One pore guy had to keep bumping his thread of months until he gave up; atleast tell me its not possible! Here are the link I saw on this from here:
https://forum.xda-developers.com/android/help/tried-to-root-sort-blu-neo-xl-t3559702
Here are my main questions:
Is it possible to access the root (either via pc with command prompt or linux with terminal or even on the device itself) without rooting or unlocking the bootloader (since both seem to be impossible).
Can you extract a system.img file, modify it, then put it back to get together to flash it to a device without unlocking bootloader?
Infact can you modify any part of the rom or .imgs and flash it to spflash tools? (Or maybe I was doing wrong?)
Is there anyway to figure out how to modify the tamper bit if I have to find a way to get around the virus bug on my device that doesn’t allow me to use the “Volume up” button to confirm that I want to unlock the bootloader? (I’m not even sure if this phone has that, I just saw that for this oneplus and thought maybe it can be on all phones in a different way?) Here is a link on that-
https://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912
The goal is get rid of the virus that sends my data back to Chinese servers. Also, the goal is to get an answer from the community here to put this to rest.
If you need any information on this or want me to upload anything please let me know.
Thank you for your time!
Bump as I need hope.
I understand people may not have this phone but I need some sort of reply to confirm that this isn't possible. I want this thread to be the first post anyone sees if they type in "Blu Neo XL" for rooting purposes.
Even if anyone that has a phone that is similar that is affected, that would be anyone who has:
R1 HD
Energy X Plus 2
Studio Touch
Advance 4.0 L2
Neo XL
Energy Diamond
bump
Waited around for awhile but now its time be obnoxious. I will bump my other thread as well and just start hi-jacking other threads until mods ban me or someone answers me for once.
bump
bump
bump again and again and ****ing again!
another day, another bump
another day, another bump
another day, another bump
another day, another bump
another day, another bump
another day, another bump
another day, another bump
another day, another bump
Also, I got a Moto G5S Plus instead finally. It toke me awhile to save the money because I don't make much but atleast I have phone that isn't sending my data over to china.....or maybe it still is sending my data who knows where. Either way, Bump.
Hey man, I didnt read through your entire post. But can't you just downgrade the version to one that is possible to root?
Or you can also get another phone that does have root as an option. Also, I don't think you should bump your own threads. Just wait it out, or ask in other threads for help.
Edit: Oh Man, I didn't even notice someone responded to this! Awesome.
It says in the rules to ask here. So I decided to ask here espcially since this phone doesn't have its own dedicated forum. I got a new phone about a month ago and its pretty good so far.
This is more of a lost cause but I bring this up just in cause other people get affected. I believe the Blu company had to pay the Justice department for this so they got away with it and thats no big deal now of days. lol
erickkg said:
Hey man, I didnt read through your entire post. But can't you just downgrade the version to one that is possible to root?
.
Click to expand...
Click to collapse
Also for those of you out there suffering, the above statement is not possible because the newer versions of Android OS have "version binding" so downgrading to an OS that is lower that way you upgraded to wont allow the phone to get pass the bios or whatever the android bios recovery start name is. (I don't remember right now) Even if you mod the recovery or bios file.
So here it is almost a year later from you writing this post and I have found myself in the same predicament you were once in and was hoping there was answers somewhere, but from the looks of it I am guessing I'm better off just breaking this phone in half and getting myself a new, virus free, root-able phone. Am I correct?
this phone use mt6739.so i want to flash it the twrp to my phone.i dunno to unlock the bootloader but the twrp file not have for this device.
I just saw this post as I too have a Honor 7S
There is NO TWRP for our device.
The TWRP for the Honor 7A/7C/7X and Honor 7 doesn't work on our device and you got to pay 4 euros to unlock the bootloader before you can even flash TWRP (and there isn't one)
This Device is treble compatible but now I've found out there is zero development and no Devs Interested in it it's a complete and utter waste of time and has gone back into its box, never to be seen again.
hi there, I get this phone recently (because is old) and I created twrp for i,t so here it is, if you want some fun
you can flash it via flashtool on locked bootloader in to boot partition and after that you push twrp.img via adb to internal storage and flash it in to erecovery and recovery slot, and you are good to go
Samuel Ladziansky said:
hi there, I get this phone recently (because is old) and I created twrp for i,t so here it is, if you want some fun
you can flash it via flashtool on locked bootloader in to boot partition and after that you push twrp.img via adb to internal storage and flash it in to erecovery and recovery slot, and you are good to go
Click to expand...
Click to collapse
Hi I have a problem. I'm having brom issues in trying to flash it
Hi
I thinking you dont have "Authentication file" so you using "mtksecurebootdisabler",
so you need patch your drivers with libusb "patch".
Try this one, for me it works.
So open libusb that you install.
connect your honor7s to the pc with disconnected batery and hold volume down.
in patch option select your usb mtk device "idk how is called" and patch it
after patching reconnect phone and it will works.
usab1oy said:
Hi I have a problem. I'm having brom issues in trying to flash it
Click to expand...
Click to collapse
and little hint
dont flash whole rom if the phone can boot becasue after clean flash "format+download"
you lost log and cust partition because the image files are not secureboot signed and your phone get in to bootloop
and also you lost imei codes so no cellular after that
If you do so
you can fix it in that recovery were I enabled option to format log partition
after you format log to ext4, your phone will boot but without huawei/honor bootanimation
you dont need to worry about cust partition, if you didnt format it it still boot but without bootanimation and you lost some of garbage apps that are in that partition (amazon etc...)
(twrp boots in russian language, idk for now how to change it to boot in english or slovak lanuage (because Im from slovakia) and also it have Lenovo Logo becasuse I use sources from Lenovo A5 that have same cpu)
I will make in future separated thread for this....
Thanks alot for this.. I don't know maybe I should try the disconnected battery. But from a yt link I saw
The link : Honor 7s Dua-Al000
I wonder how his worked
I'll have to know how to disconnect the battery thou. I'm a noob at this.
Samuel Ladziansky said:
Hi
I thinking you dont have "Authentication file" so you using "mtksecurebootdisabler",
so you need patch your drivers with libusb "patch".
Try this one, for me it works.
So open libusb that you install.
connect your honor7s to the pc with disconnected batery and hold volume down.
in patch option select your usb mtk device "idk how is called" and patch it
after patching reconnect phone and it will works.
Click to expand...
Click to collapse
Sorry for the noob question but after patching with the battery disconnected. When I want to use spflash tools would I still use disconnect the battery to flash the recovery and co.
usab1oy said:
Sorry for the noob question but after patching with the battery disconnected. When I want to use spflash tools would I still use disconnect the battery to flash the recovery and co.
Click to expand...
Click to collapse
you can patch it or flash it without disconecting the battery
Here is how:
turn it off
Push and hold volume down
While holding volume down connect usb cable
But is recomended to disconect battery because the phone can boot up instead to go in flash mode.
usab1oy said:
Thanks alot for this.. I don't know maybe I should try the disconnected battery. But from a yt link I saw
The link : Honor 7s Dua-Al000
I wonder how his worked
I'll have to know how to disconnect the battery thou. I'm a noob at this.
Click to expand...
Click to collapse
Well he did with the battery and he add more steps that are not necessary for flashing, like scanning for COM port etc...
When I first try flash my 7s I download flashtool and didn't change any settings, I just load the rom and flash it.
So you must try to find your best way how to do and I will help you
And I wonder how he can flash the Log and Cust partition via flashtool, Maybe he have unlocked bootloader or something
Update: he have in the video description link for "lib usb" but didn't show it in video, or I'm just blind or something
Samuel Ladziansky said:
Well he did with the battery and he add more steps that are not necessary for flashing, like scanning for COM port etc...
When I first try flash my 7s I download flashtool and didn't change any settings, I just load the rom and flash it.
So you must try to find your best way how to do and I will help you
And I wonder how he can flash the Log and Cust partition via flashtool, Maybe he have unlocked bootloader or something
Update: he have in the video description link for "lib usb" but didn't show it in video, or I'm just blind or something
Click to expand...
Click to collapse
Yeah. For the flash mode, I wonder why his own he said I need to hold the volume up and down button at the same time. But thanks I'll do it and let you know.
here is version 3 of twrp recovery port
-fixed language form russia to english
-lenovo banner replaced with original TWRP
Samuel Ladziansky said:
here is version 3 of twrp recovery port
-fixed language form russia to english
-lenovo banner replaced with original TWRP
Click to expand...
Click to collapse
At this point. Might just abandon it. Thanks for everything. Ran into laptop issue on my third trial lol.
Yeah I see, drivers issues, it happens to me too, but I install windows 7 and everything works... but I think is not worth it to format your laptop and install win7 only for this mediatek crap, where you can't unlock bootloader or anything because Huawei trying to protect customers and they believe that their android is best for they're phones
Samuel Ladziansky said:
Yeah I see, drivers issues, it happens to me too, but I install windows 7 and everything works... but I think is not worth it to format your laptop and install win7 only for this mediatek crap, where you can't unlock bootloader or anything because Huawei trying to protect customers and they believe that their android is best for they're phones
Click to expand...
Click to collapse
Honestly. I spend a whole night researching videos for the phone. Only to get that link I send. And after all that. It still didn't work. Lol. I have a Poco x3 pro. I wonder if snapdragon android 12 can be rooted. Probably going to try it next month or so.
Snapdragon is eazy for root.
I have Redmi note 11 and it was easy, now I running on Android 13 from stock android 11, if you will need some help with something, I'm here, and I think there is device forum so there is community for that device
I bought RN 4 Mediatek with the cheapest deal, 4/46, Its still usable, n i forgot to do overall check coz its cheap
The issues :
1. i cant log on my Mi Account, coz everytime i do that, the notif 'getting security info' shows, n it never stop
2. I cant update apps in playstore. I can install new apps from apkpure site but it need to reboot
3. Everytime after reboot, a 'wait for debugger to attach' notif slways shows, n its related to Mi Find Device
So i assumed this RN 4 is Bricked n now i need HELP to UNBRICK it n i wish someone know also the test point. Coz like i used to unbrick other Mi phones, flashing via test point can fix all software issue
PLEASE HELP
T.I.A
First of all it's technically not bricked but considering that it's a cheap deal that probably means it's used and I hope you got the MI account that can unlock this phone, been long since I used miui on my note 4 so I dunno what happenes if you don't have it
but anyway here are some tips
1- if the device is unlocked try wiping all user data through the miui recovery (or if it has other recovery like twrp)
2- if the device isn't but you can still access fastboot then you might be able to erase the user data using
[fastboot erase userdata]
That's ocourse that means you need fastboot on your PC Abd also the device USB drivers
3- if that's still not working you might need to actua flash a stock ROM using MiFlash tool, while you're at it look for "deep flash" cause in my case just flashing in fastboot mode had so many troubles, but in download mode it went perfect
PS: I entered the download mode on my note 4 through fastboot code that I really can't remember right now, try this before resorting to short circuiting your device for download mode