Related
FIRST VOTE IN POLL BECOME LARGE POLL ALSO HELP FOR XOLO USERS AND LITTLE THANK FOR ME
WORKING HARD ON DEVICES
send me some thank paypal.me/aarushdhama
ROOT
you can root now
But only by pc ADB fastboot
Requirements
1.recovery https://drive.google.com/file/d/0B_cfID200f6QeF8tbU45aGJLcW8/view
2.supersu beta ( download only my SuperSU any other may be bootloop )
3.driver sprd
4.disable pc signature
5.USB cable
Download all files link in download section
**Instructions
FOR BETTER VIDEO TUTORIAL
LINK- https://youtu.be/kQ5PGaQKHfU
1. Disable pc driver signature (search on Google its easy )
2. Connect phone to pc and set media device to CD option
And copy files means driver files
Install driver now x64 for 64 bit and x86 for 32 bit
Make sure ist disable driver signature... otherwise you can't install drivers and without driver no root
3. Enable OEM unlocking and USB debugging
(Go to about tap 8 times on build no. Then you see a option developer option then open and click )
4.copy SuperSU file to phone
5. Recovery (universal) clockworkmod
In pc
6. And you also need a folder which are created in C drive window drive ADB& fastboot
7.copy recovery file name (clockworkmod) to ADB folder and
8. Now connect phone by USB cable
Now go to folder adb and click shift+right click then a option see in list open command prompt here then click it
9. Now you see a cmd option and write
Adb devices. -hit enter
Then you see a popup in phone make sure don't lock your phone your phone display always on
And click on always option in phone and hit allow to option in phone
Now again write "adb devices"
Now you see a device
With some id - device
Now mean your phone connect by adb
10. Now write
Adb reboot bootloader - hit enter
Now your phone go to the fastboot mode
Does not do anything with phone
11. Write now
Fastboot flash recovery clockworkmod.img -hit enter
Now some data you see and ok flashed complete like this
Now disconnect your phone take down battery and and re insult battery and power on by pressing
Volume up (+) power make sure one time
And after some time you see a logo of xolo
And power key left but Don't left volume up key
When you see a recovery option go to update from sd card)internal
Flash SuperSU.zip file
Now reboot and enjoy your rooted xolo era 1X
CUSTOM ROM- cm13 is on the beta version
CM 13 FOR ERA4G/era1x/erax BETA VERSION MAYBE WORK ON ERA X (NOT TESTED) BY MURALIVIJAY AND SUMIT DEV
THIS ROM NOT FULLY WORKING BUGLESS ROM.. UNDER BETA TESTING PROCESSS....... SO IT HAVE BUG AND SORRY FOR MY BAD ENGLISH
WHATS NEW ?
1)FIXED WIFI AND BLUTOOTH
2)FIXED BACKLIGHTING
3)FIXED SENSOR
WHATS NOW WORKING ?
1)WIFI
2)BLUETOOTH
3)GPS
4)CAMERA
5)PRE ROOTED
6)SUPPORT MULTIWINDOW
7)APPS CAN,T LAG RUNNING SMOOTHLY
BUGS :
1)RIL NOT WORKING
2)NO SIM DETECTION (MAIN BUG)
3)AUDIO NOT WORKING
4)SDCARD MOUNTING PROBLEM
5)OPTION NAVIGATION NOT WORKING
HOW TO FLASH ?
(MAKE SURE TAKE BACKUP OF YOUR STOCK ROM USING TWRP)
1)DISBLE DRIVER SIGNATURE VERIFICATION ON YOUR PC
2)RUN "RESEARSCH DOWNLOAD" AS ADMIN
3)LOAD "S204 PAC FIRMWARE"
4)GOTO PARTITION TAP UNSELECT ALL PARTITION EXCEPT FDL1,FDL2
5)NOW LOCATE BOOT AS "BOOT.IMG" FILE SYSTEM AS "SYSTEM.IMG" AND USERDATA DON,T LOCATE ANYTHING THEN CHECK THIS THREE PARTITION
6)REMOVE DEVICE BATTERY PLAY THE FLASH BUTTON THEN FLASH IT
7)PUT BACK BATTERY AGAIN POWER ON NOW CM LOGO WILL APPER WAIT FOR 5MIN TO TAKE FIRST BOOT
(IAM NOT RESPANSABLE IF YOUR GET HARD BRICK AND DAMAGE .. )
(NOTE FOR DEVELOPERS)
i,m hardly tried to fix the bug but unable to fix it... because selunux is (enforce mode) blocking (avc) "rild_sp" socket so .. ril receiver couldn,t find
rild socket .. so we need our device kernel code to fix selinux.. but some after days iam tried new method to bypasss selinux mode by su.d ..it was changed
selinux mode into "permissive mode"..and modem socket connected but bad luck it can,t sim cards .. because iam used samsung device ril to build this rom..
but im take second log again it could,t find "rild2" socket ..i don,t know why its again come ramdisk is ok .. first socket connected .. second socket socket trying to connect ...
so this is very big problem in our device .. any expert sprd developers try to fix it ..
Device tree http://github.com/era4g
any developers can fix those below bugs in future .. in my knowlege iam fixed but some other unable to fix ,, if any developers fixed this bugs please
kindly mail me [email protected] also iam here in hangouts .. Thanks i hope you will this ****s : D
ROM URL DOWNLOAD LINK CM13
https://drive.google.com/file/d/0B7rWS2FCs7IBWURHdDZtdFQwcWc/view
RECOVERY-twrp recovery flash it by flashify after root but this recovery have touch issue but working great for backup/restore /flash anything
for problem fix watch this video
https://www.youtube.com/watch?v=uW6g5Hl03Ks&t=3s
reserved-------:good::fingers-crossed:
Please help anyone port any rom for xolo users twrp available , cm beta version also
Is this rom will work in xolo era 1x ?
please help me bhai how to revert this boot screen something happened and then it is asking me to allow or read only but when i press it it wont register pls help fast bhai
sharvaj said:
please help me bhai how to revert this boot screen something happened and then it is asking me to allow or read only but when i press it it wont register pls help fast bhai
Click to expand...
Click to collapse
have u flash the rom in xolo era 1x ?
bravolol said:
have u flash the rom in xolo era 1x ?
Click to expand...
Click to collapse
Yes i did and now im using that recovery with touch issues and bcoz of that cant do anything pls help, also, i cant boot into system anymore (i got myself into a bootloop?)
Awesome.....!
Took a bit of work around to get this done.
I was confused with your Youtube video. Still Didn't understand why you have booted boot.img and if it was important why wasn't that provided in the download links.
But, You XDA Thread is perfectly descriptive.
Intially, the TWRP didn't boot. But, Once I removed the Battery and reinserted it, everything worked fine.
Thank you for the Thread. Learn't a bit about Android root.
:good::good::good:
---------- Post added at 02:06 AM ---------- Previous post was at 01:42 AM ----------
bunty5555 said:
Please help anyone port any rom for xolo users twrp available , cm beta version also
Click to expand...
Click to collapse
Did you find any custom ROM's???
root successful
rooted my phone using the provided recovery and Supersu.
Try this for rill fixing
Use rill files from ur stock rom dont use from Samsung, but use rill.java of Samsung for building rill, and i saw ur device tree n vendor tree, there was a very main file missing which is required for rill, /bin/cp-diskserver (its very important for rill)
And one more thing you forgot to add this code in build.prop... I saw that u used sc7731c.java rill for telephony.jar so u have to put this in build prop
ro.telephony.ril_class=SC7730CRIL
ro.telephony.prop_class=SC7730CRIL$TelephonyPropertyProvider
Sorry for my bad English i hope u understand
Sent from my [device_name] using XDA-Developers Legacy app
Anyway to fix imei on xolo era 1x .please help me.
Recovery file doesn't exist, please someone share the recovery file to root.
stock rom link for Xolo era 1x pro, or any custom ROM link
Phone bricked
Any help, only cyanogen recovery I can access
amit020 said:
stock rom link for Xolo era 1x pro, or any custom ROM link
Phone bricked
Any help, only cyanogen recovery I can access
Click to expand...
Click to collapse
how did you root it?
Hello everyone. I just want to ask if someone has already made some experiences with rooting the new Bluboo s1? Or has made it with a similar phone and can give some advices to try out. Thank You.
how to root?
ubuntuh said:
Hello everyone. I just want to ask if someone has already made some experiences with rooting the new Bluboo s1? Or has made it with a similar phone and can give some advices to try out. Thank You.
Click to expand...
Click to collapse
I'm in same problem , i already tried with sptool , trying by doogee mix that is the same chipset , but no luck...
https://forum.xda-developers.com/android/general/doogee-mix-development-support-t3632785
it seems that nobody wants root on this phone
btw, when u listnning music by bluetooth is Bluetooth music intermittently cuts out?
tnks
I haven't had this problem in special but still the bluboo s1 is a shame in my opinion. I think i will try to resell it asap. The button for waking the screen is been stuck nearly every time i use it.
bbfsonic said:
I'm in same problem , i already tried with sptool , trying by doogee mix that is the same chipset , but no luck...
https://forum.xda-developers.com/android/general/doogee-mix-development-support-t3632785
it seems that nobody wants root on this phone
btw, when u listnning music by bluetooth is Bluetooth music intermittently cuts out?
tnks
Click to expand...
Click to collapse
Mine works fine with fingerprints sensor (recorded 4 fingerprints in various positions and fingers) and bluetooth using Dacom Gf7. I'm very happy for this 150€ purchase. Maybe there are different hardware versions because someone reports also speaker low levels and mine is strong and clear during calls, too. I also hope to find a way to root this very nice, fast and stable device to enable more options. Keep us informed on your rooting progresses. :laugh:
ROOT DONE!! BLUBOO S1 MTK Nougat7.0 FIRST HOMEMADE ROOT!!
Super easy.
Only need a patched stock boot.img image
And unlock the phone before flash it.
Fastguide:
Requisites...
Fastboot/adb tools and drivers
Firmware V10 (lastest update)
Unlock Bootloader
Start!!
Connect bluboo S1 on fastboot mode.
With adb/fastboot tool.
Write:
fastboot oem unlock.
Take your phone and press vol+ (same as accept unlock process)
Now your bootloader its free and your phone will FORMAT.
(Only keeping the system base)
Now with your bootloader open... Wait for reboot android UI.
Download the lastest Magisk Manager.apk (search on ggle "V5.3.0" works on my own) and install IT.
Download this file on mega. And remove ESPACES from-the-link (MOST IMPORTANT)
mega. nz /#!xQtwnR7S!h1vylwQd3u_lUZ4Cbkw_S8YOsL2VskIDuVfbNTT kEis
(Img Patched with magisk v14/stock boot.img from Bluboo S1 Compilation V10, android 7.)
Now if u have the .img from MEGA.. Rename it "boot.img" and place it on the "adb/fastboot" Folder
Open adb/fastboot tools, write:
adb reboot fastboot
And simple...wait for fastboot and write:
fastboot flash boot boot.img
Blablabla, OKAY!
And reboot it:
Fastboot reboot
And keep sure all has been doned on magisk manager check it.
I can not download from mega.nz link requires key to decrypt, please release key or new link thank
Inviato dal mio Bluboo S1 utilizzando Tapatalk
I could download the link without issues, removing all spaces as the OP wrote. Will give it a shot.
this is the link, all works for me, thanks all, I could restore my apps with TB https://mega.nz/#!xQtwnR7S!h1vylwQd...ockboot.imgfromBlubooS1CompilationV10,android 7.)
Install Koush Universal adb driver and adb.
To unlock boot loader, use the method stated above.
For rooting, install Kingoroot on your pc and enable USB debugging on your phone.
Connect it to the pc by a usb cord and open kingoroot, it will detect your phone and you only have to click the root button and wait for a few minutes.
Ur internet connection should be active during the process.
bbfsonic said:
I'm in same problem , i already tried with sptool , trying by doogee mix that is the same chipset , but no luck...
https://forum.xda-developers.com/android/general/doogee-mix-development-support-t3632785
it seems that nobody wants root on this phone
btw, when u listnning music by bluetooth is Bluetooth music intermittently cuts out?
tnks
Click to expand...
Click to collapse
Yep same problem with bt headphones,tried two sets same result,so it seems yet another problem with this phone ( search other post on this forum you will see there is a growing list!
Hi, I just wanted to share the files and guide how to install updates / systems on LeEco Le S3.
I have an x626 model and everything works great, according to the information I found it should also work on the x622 model.
Files for MediaTek phones (Helio X20 in this case)
Installation:
update.zip
Download files
Put on your phone (root directory)
Power off the phone
Power & Vol+
Follow onscreen instructions
Be Happy
Fastboot
[Windows 10]
Install Drivers & ADB
Unpack files to folder "Flash" on desktop
Rename run.bat to systemflash.bat
Power & Vol- (Wait for fastboot mode)
Connect phone to PC
2-Click on systemflash.bat
Wait for the end of flashing process (10-20min)
Reboot your phone
Be Happy
Orange State remove
[Windows 10]
Power off the phone
Power & Vol-
Go to unpacked "platform-tools" folder
Shift + RMB & Open PowerShell console
Type "fastboot oem lock"
Wait
Type "fastboot reboot"
Be Happy
(Before next flashing u need to unlock flow using "fastboot oem unlock")
Downloads:
ADB & Drivers: https://forum.xda-developers.com/showthread.php?t=2588979
Platform-Tools (orange state): https://developer.android.com/studio/releases/platform-tools.html
[ TESTED, WORKING ] MultiLang Official Rom & ADB Files: https://www.needrom.com/download/leeco-letv-le-s3-x626-multilanguage-eu-fastboot-stock-rom/
Version 5.8.018S should unbrick your phone Google Play included
[ TESTED, WORKING ] EN/CN Official Rom (update.zip, only official recovery): https://www.needrom.com/download/leeco-s3-x626-official-stock-rom/
https://bbs.le.com//zt/eui/le_s3.html (Official link)
[ NOT TESTED ] EN/CN Official Rom & ADB Files: https://www.needrom.com/download/leeco-s3-x626/
[ NOT TESTED ] TWRP: https://www.needrom.com/download/twrp-leeco-3/
Can please give more information about the update ? Did he will fixe the problem ?
tiziano-petrov said:
Can please give more information about the update ? Did he will fixe the problem ?
Click to expand...
Click to collapse
What do u mean? List bugs or something
I'm now using 023S update and i didn't notice any bugs
AniMaya said:
What do u mean? List bugs or something
I'm now using 023S update and i didn't notice any bugs
Click to expand...
Click to collapse
on my behalf, i'm using 018S so i did't get any update ...... and i wounder if update will fix the know issues ?
and thanks for the reply
tiziano-petrov said:
on my behalf, i'm using 018S so i did't get any update ...... and i wounder if update will fix the know issues ?
and thanks for the reply
Click to expand...
Click to collapse
I didn't noticed any bugs on 023S On 018S i could not set the fingerprint lockscreen & there was none of the OTA programs, now there is "System Update" app
Please do explain the FASTBOOT to me clearly?
Can you please help me how to update my x626 to 5.8 018s fastboot? I dont know whay is fastboot and how. Can you please specify it to me clearly or one by one step. This my fb can you please message me there? facebook.com/MissKayeCenteno
Thank you so much.
MissKayeCentenk said:
Can you please help me how to update my x626 to 5.8 018s fastboot? I dont know whay is fastboot and how. Can you please specify it to me clearly or one by one step. This my fb can you please message me there? facebook.com/MissKayeCenteno
Thank you so much.
Click to expand...
Click to collapse
Let's cut off all the long stories and save us some stress. The process of updating is very simple. I just tried it and it worked perfectly. In fact, my x626 is still working very fine with some new features, like system update, introduced. Download the file, copy into your phone directory. Rename to update.zip(if you wish). Then click on the said file from the archives folder on your phone. It will give you two options in the unfolding dialogue; "extract" or "upgrade". Choose "upgrade" and you are pretty good to go...
Hi which file did you use? Im looking for software without the chinease software and Google apps
.
Orcaflugzeug79 said:
Is there a way to update to eui 5.9.xx with TWRP as recovery? Using a le s3 x626 with TWRP recovery. Did it just as you explained another member but nothing changed. Can I just install the downloaded zip file via "install" function in TWRP?
Help is appreciated
Click to expand...
Click to collapse
Yup, u can find ROM in LeEco Le 2 ROMs section Sorry for that, but now i can't add everything here. Later i'll add custom roms and working twrp script installer
Qazstar said:
Hi which file did you use? Im looking for software without the chinease software and Google apps
Click to expand...
Click to collapse
Today i'll add clean and custom roms + TWRP script
sorry... how to upload a cellphone from linux? :'(
someone has a link for the stock recovery sorry if it's already answered, but I didn't find.
Hello! Need official Android 8.1 for X626
hi, I can not install TWRP 3.1.1 on leeco x626
some advice or video idea on the internet
I also want to try TOOL ALL IN ONE, but I'm not sure
I recognize the device and adb but I want to make sure
Thank you
How do I put the files in the root directory if the phone is bricked? I don't know how to do that.
Is it true that LeEco recently launched LeX? Does it mean LeEco is now up and running? Let them help with the latest firmware for x626 or provide the source code needed by developers to do same. The phone OS has been stagnant for too long...
How this post will help me UnBricking x626 ? Help
LeEco x626 Wifi not detecting networks
My LeEco x626 the Wifi does not detect networks. Any idea qhere I can look for the problem and a solution?
Hello everyone.
I am new to this forum so please don't scold me . My brother had problems with his LeEco S3 x626, the phone disconnected from the mobile network and then froze and restarted.
I figured maybe that would be solved by flashing a new rom. While I attempted to unlock the fastboot/bootloader, the phone bricked and is now unusable.
I tried following this thread https://forum.xda-developers.com/le-...power-t3715937 and nothing worked. SPF displays CMD DA FAIL error.
Please help!!!
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.
Update 2021.01.24: I consider the problem mentioned here as solved, since it can be resolved with MTK Bypass explained in the Guides Section. BE CAREFUL however to ONLY choose "Download Only" from the dropdown box in SP Flashtool! DO NOT select anything with "Format" in it, else you will lose S/N, MACs and IMEIs!
--- Original post ---
Hi, I have hard-bricked my new Realme 6 while trying to root it with Magisk. At the moment I am stuck in a bootloop at the power-on logo (realme in white letters). The boot animation (yellow realme letters) does not appear, instead the phone reboots after ~35 seconds. The bootloader says "Orange State".
I can NOT enter fastboot nor recovery mode by any key combination. Holding Power and Vol- makes the string RECOVERY MODE appear for a split second in the lower left part of the screen, however nothing happens afterwards.
I can power down by holding Power and Vol+ an releasing them immediately after the screen goes blank.
Holding Vol- and Vol+ while the phone is off and connecting USB makes a USB serial device appear on a windows machine for about 1-2 seconds before it disappears again.
I am very thankful for any hints on how to unbrick the device.
Here's what I have done in detail to mess up the phone:
1. OTA-Update to the latest OS in my region (EU11.A.48)
2. Unlocked the bootloader with the realme In-depth Test app (everything fine so far)
3. Download stock firmware RMX2001EU_11.A.48 ozip from realmeupdater.com
4. Unzipped with gnu unzip (content was readable, no extra decrytion tool for the ozip needed?) and extracted boot.img
5. Installed Magisk Manager and uploaded boot.img to the phone
6. Patched boot.img with Magisk Manager (and if I remeber correctly DIDN'T UNCHECK Preserve AVB 2.0/dm-verity)
7. Certainly FORGOT to do anything with vbmeta.img
8. Did NOT erase cache and userdata
9. Flashed patched boot.img directly and WITHOUT --disable-verity or --disable-verification
10. Rebooted the phone.
Am I correct that my problem is the AVB/dm-verity part?
Why does the modified boot.img affect the recovery (I thought they were seperate)
Can I try something with SP Flashtool?
I do have a second intact device that I didn't dare to touch yet, if that helps resolving the issue (e.g. for SP Flashtool readbacks).
As said any advice is highly welcome. Please ask I you need any more information to help.
I did that too... Magisk patched boot .img process of rooting is the risky process , I bricked my device, got it into red state.. tried thick and thin to revive using various flash tools, unable to do it, finally went to a shop , got it fixed, go-to a good repair shop, if you go to the service center, they will say replace motherboard for 5 k , I hope it helps, do traditional unlock bootloader TWRP recovery then flashing Magisk zip method for rooting process.
Thank you for sharing! But doesn't red state mean locked BL plus non-stock firmware? I wish I could find any repair shop during this Corona lockdown... May I ask how much they charged you for having the phone reflashed?
cmfan said:
Thank you for sharing! But doesn't red state mean locked BL plus non-stock firmware? I wish I could find any repair shop during this Corona lockdown... May I ask how much they charged you for having the phone reflashed?
Click to expand...
Click to collapse
Yes, you are right , red state means that, I guess bcoz, I may have formatted it and ran again unlocked bootloader but it showed unlocking failed, but I thought that I had previously unlocked it so it should be unlocked but I forgot to do that app thing process of deep test again, and I was on Android 10 latest and patched boot img of previous version using magisk, now I understand what mistake I made, I should have used boot IMG of current version of a 10 , but still I am afraid of doing this magisk method of rooting by patching boot IMG bcoz repair cost me 800/- , and I found out on YT that the latest version of a 10 of my device doesn't readily allows twrp and flashing zip of magisk.... Plus there are half baked info on important things, this is new device for me, I have had rooted Samsung and Lenovo, but rooting this is kind of tricky, bcoz it's still new, I think.... Want to try .... But I m afraid.... Tried fastboot method of TWRP flashing but can't replace stock room, so I guess I can't root .....
Well, there is a tutorial on how to root here on XDA, and seems to be confirmed working. I just didn't know about the vbmeta part from earlier Android versions. Haven't you tried that?
cmfan said:
Well, there is a tutorial on how to root here on XDA, and seems to be confirmed working. I just didn't know about the vbmeta part from earlier Android versions. Haven't you tried that?
Click to expand...
Click to collapse
Thnx man, I have rmx 1825 , but the process would be same for my device, I would have to search for it...
cmfan said:
Thank you for sharing! But doesn't red state mean locked BL plus non-stock firmware? I wish I could find any repair shop during this Corona lockdown... May I ask how much they charged you for having the phone reflashed?
Click to expand...
Click to collapse
Hello, please check my reply to your reply on my thread. BROM mode is as known as "Emergency Mode" and should not be inaccessible. I will once again request you to try different key combinations and also if it's detecting as fastboot, ADB or Fastboot commands should be available. Please try typing adb reboot or fastboot reboot with minimal ADB and fastboot tools and let me know. If you want to personally message me, message my telegram. I will try helping you there.
Why is this thread showing solved !!! It's nothing solved here... Pls check and confirm
daeSundae said:
Hello, please check my reply to your reply on my thread. BROM mode is as known as "Emergency Mode" and should not be inaccessible. I will once again request you to try different key combinations and also if it's detecting as fastboot, ADB or Fastboot commands should be available. Please try typing adb reboot or fastboot reboot with minimal ADB and fastboot tools and let me know. If you want to personally message me, message my telegram. I will try helping you there.
Click to expand...
Click to collapse
I think there is no Emergency Download Mode in Realme devices.. pls guide ...
Ank Sak said:
Why is this thread showing solved !!! It's nothing solved here... Pls check and confirm
Click to expand...
Click to collapse
Hello. Please follow this guide.
Repair DEAD(HARD BRICKED) Realme 3 | 3i Tutorial
In this tutorial we are going to Repair Realme 3 (RMX1821) MT6771 Chipset. from being hard bricked (no charge, no recovery, no fastboot) using SP Flashtool. with the help of Bypass Utility "MTK-bypass" to disable bootrom protection(sla and daa)...
forum.xda-developers.com
daeSundae said:
Hello. Please follow this guide.
Repair DEAD(HARD BRICKED) Realme 3 | 3i Tutorial
In this tutorial we are going to Repair Realme 3 (RMX1821) MT6771 Chipset. from being hard bricked (no charge, no recovery, no fastboot) using SP Flashtool. with the help of Bypass Utility "MTK-bypass" to disable bootrom protection(sla and daa)...
forum.xda-developers.com
Click to expand...
Click to collapse
Thnx that's a life saver, I am afraid to go forward with the device, this is promising, I will try, I found out that the new version c17 os Android 10 I am unable to root by twrp magisk zip flashing method, twrp isn't installing, there's an .ofp extracter, but it gives virus with software, unable to do, even talked on WhatsApp and gave him Gmail id, will try this method , I wanted the SP flash tool method, it's simple and can readily restore the stock rom... Thnx Sundae.. daesundae ... What kind of name is that...?? .. chuckles...
Ank Sak said:
Why is this thread showing solved !!! It's nothing solved here... Pls check and confirm
Click to expand...
Click to collapse
This thread is about a Realme 6 (RMX2001 in my case). I've edited the very first post to immediately show the solution. Please check there or follow daeSundae's guide if you have a different device.
cmfan said:
This thread is about a Realme 6 (RMX2001 in my case). I've edited the very first post to immediately show the solution. Please check there or follow daeSundae's guide if you have a different device.
Click to expand...
Click to collapse
I saw everything that You posted, incidentally the YouTube video on this is on rmx1825 , thnx, whatever you posted it helped..