Related
Hi, I was trying to use Flash tool and Don't know what happend but My Phone is completely DEAD right now even power button is also not working no screen is there (just blank phone).
I am having UMI X2 2GB rom, 32 gb internal memory, 1.5 GHZ (MT6589T) Model.
I tried to use SP Flash tool to recover my phone. Firstly I tried to format the phone, After that I tried to run the correct scatter file for MT6589 (from one of the ROM Posted under UMI-X2).
Drivers for the SP Flash tool is loaded correctly (into my Windows 8 Pc). I was previosly getting error as follow : SP FLASH TOOL ERROR: (8200)
[Platform Error] The load and target are inconsistent!
Now, after searching a lot I found that its something wrong with SP Flash tool version.
So I downloaded SP Flash Tool V3.1304.O.sn119 version. After that I am trying to "Download" the rom (with the correct scatter file for my ROM). but its only showing me RED Bar (with 100%) and after that it does nothing. Its neither showing me any error nor its continuing the process.
I am in serious problem here. Please help me out.
Thanks in advance!
- Umang
umang_nine said:
Now, after searching a lot I found that its something wrong with SP Flash tool version.
So I downloaded SP Flash Tool V3.1304.O.sn119 version. After that I am trying to "Download" the rom (with the correct scatter file for my ROM). but its only showing me RED Bar (with 100%) and after that it does nothing. Its neither showing me any error nor its continuing the process.
I am in serious problem here. Please help me out.
Click to expand...
Click to collapse
Try this version of :
SP Flash Tool
October Official Rom
USB Drivers (if needed)
Works for me.
Necro thread...
I have the same issue.
A couple of days ago the phone just started turning off / locking up when off, and having great difficulty tuning on... i.e. pulling out the battery for a minute or a few times.
Now the phone won't turn on at all. They only sign of life is the charging animation when you plug it in.
Prior to all this, there appeared a window in Chinese with some options. my GF (who's phone it is) just pressed something, no idea what. But she said something about 'drawing on the screen'??? sound like something locked up and the previous frame wasn't deleted from the frame buffer before redrawing the new one... I have no idea.
Anyway, I tried going into recovery to see if there was anything I could do there, unfortunately everything was in Chinese, so not much help. for some reason now, the recovery isn't even working.
Now I can connect to the phone via SPflash, but I get the above response: '[Platform Error] The load and target are inconsistent!'
Some other ROMs I tried give me this response:
'The load to be downloaded is for MT6589;
The target platform is MT6582_S00'
Which is quite suspicious.
Any ideas?
Thanks
hisense HS-U980 bricked....
hi,i have the smartphone hisense hs-u980 with mt6589 or mt6589t, i dont understand.... so, i briched with sp.flash tool and now is ompletly dead,,, can i have ur help-sipport please?
thank u very much
Hs-u980 complete dead/bricked
carretto76 said:
hi,i have the smartphone hisense hs-u980 with mt6589 or mt6589t, i dont understand.... so, i briched with sp.flash tool and now is ompletly dead,,, can i have ur help-sipport please?
thank u very much
Click to expand...
Click to collapse
i have ur same phone and i have ur same problem,my pkone is dead later flash any wrong miui rom from cwm recovery and now is dead,i dont have any idea where is original firmware for sp.flash tool or other how piranha box,please,anyone can please me??? THANK U for read!!!!
I have the same Problem. So frustrating men. If anyone finds a solucion please email me [email protected] ...
SP FLASH TOOL ERROR: (8200)
As i connect my phone it disconnects after 2 seconds..
Please give me a site to download scatter file for my micromax a 310
Hi guys, i really hope you can help me, i m so deseperate...
After OTA Update my CATERPILLAR S30 bricked into bootloop, i can access to the stock recovery (wipe data/factory not fix it) and bootloader show me ; "DC CHECK"
I read that it could be my bootloader (emmc) wich it's corrupted...
The chipset is a Qualcomm Snapdragon MSM8909, of course USB debugging is disabled and i can't find any stock rom, backup for this phone....
Please HELP ME...i work hight in the mountain and if i cant communicate it will become....quite dangerous for me...
If someone has a backup (EU AREA), a stock rom or any solution for me ill be gratefull
Bye
Nobody can upload me OTA file (wich i ll .zip), boot.img, backup or any kind of solution please...?
AnY-One said:
Nobody can upload me OTA file (wich i ll .zip), boot.img, backup or any kind of solution please...?
Click to expand...
Click to collapse
What software version are you on?
Chuggers said:
What software version are you on?
Click to expand...
Click to collapse
Hello there and thanks helping me...
I'm AnY-One but i can't log in with; i dont know why...
I dont know what is my software version i only can say to you that the last update i tried to install came about 10-12/01 (EU France) and i bought this phone the 24/12 and i already did a first update.
So my phone stuck in bootloop (Qualcomm HS-USB QDLoader 9008 recognized) when i tried to install the 2nd update 10-12/01 so...
I have all qualcomm developpers tools with qualcomm flash utility and i can access to stock recovery...perhaps just a boot.img should work...
Pleassse help guys...
"and...as you can read; SORRY FOR MY ENGLISH"
---------- Post added at 05:32 PM ---------- Previous post was at 04:52 PM ----------
an update.zip that i can flash from recovery should be welcome
---------- Post added at 06:19 PM ---------- Previous post was at 05:32 PM ----------
Got it, i think software version (viewing in recovery mode) is LTE_D0201121.0_S30_0.017.01
Zi0nlive said:
-snip-
Click to expand...
Click to collapse
Is warranty not an option?
nagalun said:
Is warranty not an option?
Click to expand...
Click to collapse
it is but it takes time...and i like to fix my mistakes by my self...
Have you a solution for me? can you upload the OTA files or a backup rom .zip?
Zi0nlive said:
it is but it takes time...and i like to fix my mistakes by my self...
Have you a solution for me? can you upload the OTA files or a backup rom .zip?
Click to expand...
Click to collapse
You can access recovery?
Usually when you see "Qualcomm HS-USB QDLoader 9008" it is because the phone can't load the bootloader (bios), so I am a bit confused about the state of your phone.
You likely need more files than the OTA has.
nagalun said:
You can access recovery?
Usually when you see "Qualcomm HS-USB QDLoader 9008" it is because the phone can't load the bootloader (bios), so I am a bit confused about the state of your phone.
You likely need more files than the OTA has.
Click to expand...
Click to collapse
That's a good question ; yes i can access to QDloader HS-USB 9008 with qualcomm drivers ; I CAN ONLY acces to
recovery holding VOL+ then plugin in USB. Phone off then : POWER + VOL+ doesnt boot recovery.
Wipe Data/factory seems to work, adb sideload; device is regognized in adb shell but most of commands answer are: "FAILED (remote: unknown command)" when i choose reboot in bootloader it's the boot screen with 'DC CHECK MODE' left corner..
Is there someone reading me who has the same phone?
Is there someone able to upload me .img (system, boot ...) that i can flash with QPST Tools? Stock Firmware? Nandroid Backup?
Is there someone who can guide me to repair that phone stuck in bootscreen? I think the problem come from my stupidity fogetting to unroot (Kingoroot apk replaced by SuperSU) before OTA update.
How extract my proper firmware
Hello
How extract the om from the device
Help Me
Same problem...
I have the same problem too... Please help
sharing my experience in a similar quest
Hello ! You probably must have resolved the issue by now. Like you, I too had a similar issue ( Reliance Jio Lyf Wind4 - Haier L51)
In my nooby quest for a solution have made some progress. The learning is:
One needs : Mprg8909.hex, 8909_msimage.mbn, rawprogram0.xml, patch0,xml to recover.
If you can get hold of a phone similar to yours, you can dump all the partitions. That can then be used to get the required information to make your unique rawprogram0.xml. The process of dumping becomes very easy if the phone is root and you are running an insecure boot. Using basing Linux commands like fdisk,gparted,proc you can get and idea of your partition details. The dd command will help you dump the partitions.
Yes the tools to use is from the QPST suite or look for the stand alone emmcdl.exe
As your phone is showing the QUSB 9008 mode you need to be able to switch the phone to Emergency Download Mode after which you can use MIflash or similar tool to flash the ROm from the dumped images. Thats where the rawprogram0.xml comes in. It details partition information required to revive the phone.
Havent succeeded yet, but am feeling encouraged. Probably need to resolve syntax errors creating the rawprogram0.xml and figure out if just this much is enough to switch the phone to EDL.
After lurking here for months, this is my first post, therefore I request indulgence in case I have inadvertently erred
TooSour
AnY-One said:
Hi guys, i really hope you can help me, i m so deseperate...
After OTA Update my CATERPILLAR S30 bricked into bootloop, i can access to the stock recovery (wipe data/factory not fix it)
and bootloader show me ; "DC CHECK"
I read that it could be my bootloader (emmc) wich it's corrupted...
The chipset is a Qualcomm Snapdragon MSM8909, of course USB debugging is disabled and i can't find any stock rom, backup for this phone....
Please HELP ME...i work hight in the mountain and if i cant communicate it will become....quite dangerous for me...
If someone has a backup (EU AREA), a stock rom or any solution for me ill be gratefull
Bye
Click to expand...
Click to collapse
You will need:
Hi
I have a similar issue with a different phone (Reliance LYF LS 5014 - a.k.a. Haier HL-L51) Service centres will claim that the motherboard needs to be changed (and charge you an arm and a leg ;p) Even if you get the firmware image it wont help. Thats becuase if you are bricked and in the QLoader 9008 , you first have to get the phone in EDL (emergency download mode) only then can you use MI Flash et al to flash your ROM.
The route I am taking is as follows: got hold of a similar phone and dumped all the partitions using the dd command. Then getting hold of all partition information using gdisk/parted/df et al This is so that I can create a partition.xml. From this I could run a Python script ( PartitionTool.py) to get rawprogram0.xml, patch0.xml. Using emmcldl and partiton.xml I can create the 8909_msimage.mbn . Hopefully, armed with these and QPST /Miflash I should be able to revive my phone. I have read that one needs the mprg8909.hex to kick the phone into EDL but am not convinced that without it I will remain stuck. That file seems to be guarded like a state secret by phone manufacturers.
ALl this I have learnt the hard way over almost a fortnight. I confess that I do fall into the "noob" category and cant program/develop to save my life. Therefore it should be easy for anyone with the right amount of enthu
Cheers
Zi0nlive said:
Is there someone reading me who has the same phone?
Is there someone able to upload me .img (system, boot ...) that i can flash with QPST Tools? Stock Firmware? Nandroid Backup?
Is there someone who can guide me to repair that phone stuck in bootscreen? I think the problem come from my stupidity fogetting to unroot (Kingoroot apk replaced by SuperSU) before OTA update.
Click to expand...
Click to collapse
on continuing my quest for a solution
Havent given up yet.
Discovered two really useful utilities: emmcdl and fh_loader both work from the DOS command prompt and are useful to download images and partitions to the phone.
Managed to create a rawpartition0.xml which I think is for my phone ( LYF Wind 4 a.k.a Haier HL L51 and LS5014) For this I used a similar phone and after rooting it managed to extract start sector and size in kilobytes info for each of the partitions.
Also used EFS Professional to get a backup of emcc firmware.
Have successfully downloaded all the partitions but am failing at the bootloader (emmc firmware) part. Continuing my quest for a solution and will share whatever I figure.
Cheers
Vonageext4ts said:
Havent given up yet.
Discovered two really useful utilities: emmcdl and fh_loader both work from the DOS command prompt and are useful to download images and partitions to the phone.
Managed to create a rawpartition0.xml which I think is for my phone ( LYF Wind 4 a.k.a Haier HL L51 and LS5014) For this I used a similar phone and after rooting it managed to extract start sector and size in kilobytes info for each of the partitions.
Also used EFS Professional to get a backup of emcc firmware.
Have successfully downloaded all the partitions but am failing at the bootloader (emmc firmware) part. Continuing my quest for a solution and will share whatever I figure.
Cheers
Click to expand...
Click to collapse
1. Why can't you go to the Rjio service center and get it flashed? Just tell them it got screwed after an update.
2. How did you manage to root the phone? Mine is Flame1 which has same MSM8909 chipset.
I am very not happy with the stock ROM but I don't think anyone has come up with a custom ROM for this cheap chipset.
I have bricked my CAT S30 too. Is there someone who have a solution? Or can somehow make a ROM copy so I can somehow flash it to the phone? I made a lot of searching and can not figure out how to make the phone work again.
hello I need firmware for S30 because I lightened too much after the root and I deleted something I should not, is now locked in the home screen CAT, but I can get into fastboot and bootloader.
thank you guys
file for CAT S30
Hello
I purchased another CAT S30 which has just lit downloaded a system update and I extracted from the cache, now the load so you can work on it.
if you need other things tell me how can I copy them from working phone.
my I crashed after I canceled the DownloadProviderUi.apk files and perhaps I put not compatible. now I can only access the fastboot or DC CHECK mode.
I tried to flash the .zip program but by mistake, I tried to flash the update and installs it by error although it says it has been installed, and still does not start, remains in the white screen CAT
https://www.dropbox.com/s/trqfxvnp90qt8vn/__FUMO.zip?dl=0
Vonageext4ts said:
Havent given up yet.
Discovered two really useful utilities: emmcdl and fh_loader both work from the DOS command prompt and are useful to download images and partitions to the phone.
Managed to create a rawpartition0.xml which I think is for my phone ( LYF Wind 4 a.k.a Haier HL L51 and LS5014) For this I used a similar phone and after rooting it managed to extract start sector and size in kilobytes info for each of the partitions.
Also used EFS Professional to get a backup of emcc firmware.
Have successfully downloaded all the partitions but am failing at the bootloader (emmc firmware) part. Continuing my quest for a solution and will share whatever I figure.
Cheers
Click to expand...
Click to collapse
Hi.. i have a CAT S30 stuck in logo, how i can use your file? thanks
Hi got this same phone only two weeks ago, and broke it trying to root it, got stuck on Bootscreen, however I found an unofficial rom for the device, loaded into an SD card and applied via recovery and boom, its a working phone again.
If you still need help, let me know so I send you a link to the ROM.
Code:
**** DISCLAIMER ****
This post is an EXPERT-LEVEL Post.
I am NOT RESPONSIBLE for what you do to your device.
Please not that I am still working on a solution to this brick.
Hello XDA-Developers,
I recently got my hands on a Meizu M3 note and, of course, wanted the newest - nougat - firmware on it. It seems I accidently flashed a incompatible (or currupted) Update (flashed an A Firmware on a G version phone). Sadly it broke down and showed only vertical stripes on it's display.
Image here: https://ibb.co/cpGunm
After some hours research I found some information on how to reflash the M3 note via SP Flash Tool here and here. Since the first tutorial is for the M3 and M3s and the second tutorial is for the M model of the device (I've got the L model) there are some changes needed for it to somehow magically work.
I exchanged files provided (such as preloader.bin, lk.bin etc) with the matching ones from the latest Official Global Firmware from Meizu. Just extracted them out of the update.zip. (Don't forget to select the Authentication File!)
Image here: https://ibb.co/k3zYDR
Short flashing tutorial: make sure your device is turned off and disconneced then click "Download" and connect your device via USB. Don't worry if it now shows an error like "Download DA Failed", just dismiss the error and click "Download" again. It should flash the device now.
Sadly it is not possible to flash the boot.img provided in the latest official update.zip from Meizu (you'll get an security mismatch error). BUT the boot-verified.img provided by the chinese archive is flashable and is accepted by the device. The device is now in a bootloop, fastboot is accessible via holding Vol - and Power, but no recovery access via Vol+ and Power
The files seem to be repaired now but the display still shows these stripes - I think the firmware actually fried something on the display chipset. I bought a replacement screen and then will update this thread as soon as possible. If you have any Ideas of how to unbrick the device feel free to discuss.
Update 18.11.2017
Thanks to @ncristian !
I did as he suggested, downloaded and flashed the files from the russian forum here (if you do not speak russian and want to get straight to the point: Direct Download Link)
I still have the stripes on my screen but the device booted up successfully and got recognized again by my computer! While booting up I could see the stripes changing their color slightly as the bootanimation of flyme was playing. I guess I will have to replace the screen to make the display error go away... I will update this post as soon as I did so
Update 10.11.2018
Sadly I never actually exchanged the screen, I'm running a Pro 7 Plus as a daily driver now and I'm loving it
Update 19.05.2019
I have attached the boot-verified.img as someone requested it
I had the same problem and I solved thanks to this: https://4pda.ru/forum/index.php?showtopic=739028&st=24480#entry65580668 and Google Translate; I downloaded the .zip, installed drivers, launched the flash tool and flashed files contained in the folder L691H (Remember to install drivers and disable antivirus or it will not work). Then I downloaded FlyMe 6.1.0.0G, went into recovery with vol up + power, copied the update.zip into the device "Recovery" and flashed it; the only problem I had is that the phone charged but he didn't recognize the battery level; by reflashing the files contained in the 4pda .zip, the battery level went up (obviously, after leaving the phone charging for about an hour).
Someone please help my meizu m3 note bricked after flashing flyme 7.8 beta.
Rajdas26 said:
Someone please help my meizu m3 note bricked after flashing flyme 7.8 beta.
Click to expand...
Click to collapse
Try reflashing via the original recovery, that might be your easiest solution. If that doesn't work you might try your luck with something like SP flash tool
Hey. Uhmm i know it's an olld post but i'm hopeless now. I need the boot-verified img you have. i can't find it anywhere. can you send it to my gmail ?? [email protected]
shawn_mendes said:
Hey. Uhmm i know it's an olld post but i'm hopeless now. I need the boot-verified img you have. i can't find it anywhere. can you send it to my gmail ?? [email protected]
Click to expand...
Click to collapse
I have attached the file to the first post. Good thing I never delete anything :angel:
m3shat said:
I have attached the file to the first post. Good thing I never delete anything :angel:
Click to expand...
Click to collapse
First of all, thank you mate I successfully downloaded the boot verified. But still it didn't turned on. Just no power but recognized by the sp tool. I'm starting to think that downloaded again the wrong firmware. I also found out that their are two main board(or whatever is that). So this global firmware can be flashed in the both L and M series. I'm wondering what firmware you used to flash. Again, thank you in advance ^_^
l got same problem .. (because I'm not read careful )l tired to flash using many firmware or using boot verified .. i tired that for 2 Days.. So l give up.. take my device to profesional service . and solved. solved with Emmc repair ..
my device is L681H.
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 guys! I have a problem with one phone that i am trying to fix for someone and I feel sooo, sooo completely lost in all of this as I know almost nothing about this. The cell phone model that is in question is Alcatel One Touch Pop C3-4033x.
It seems to be using a Mediatek chipset and I was reading some of your advices here & there and tried using the program called SP FlashTools but it always resulted in error, in the end. It seems that something is wrong with this phones emmc flash memory. So, I tried transfering some files as a zip files to the SD-card and tried to apply update from it, but it said always: Installation aborted. And then, I have tried looking for a way to flash stock firmware of that specific Alcatel model on SD-card, but I just don't have any clue how to do it, if it is possible, even. Maybe I should just give up trying?
Oh, I almost forgot to write that the phone doesn't have the access to Android OS and USB debugging isn't turned on, because computer doesn't seem to list it and I don't know if there any button combinations that Alcatel uses for this model to get into that fastboot or adb mode, even though have installed mediatek drivers. It can only get into Android System Recovery 3e. That seems to be everything, I think, at least.
Oh guys, I am so, so, so sorry if I am bothering you with this. I just didn't know what or where else to ask this. Thank you sooo much!
Hi download those files:
Firmware:
https://www.mediafire.com/file/bpm4ibsbmr4q6nc/OT-4033X-Without_Mobilis_logo__BY_GSMSERVE.rar/file
SP Flash tool:
https://androidfilehost.com/?fid=11410963190603870440
Driver:
https://mega.nz/#!8VYkQCxD!fkhTrZwFFILDAglO1cR_8pIM4Cel52brZ7RB6QZoc6o
Once you downloaded all right driver open SP flash tool and add Scatter file
MT6572_Android_scatter.txt
Click on Download , connect your phone without battery and see if the process is going on if not try again with battery inside.
If you end up with error do the same thing but now first do Format then after is Finish do Download. Good luck ...
It still displays error :/
Teddy Lo said:
I have tried to do everything like you have said, but it still displays error when i press the Download button, and it displays that error after some seconds pass and also the same happens hen i try to use the Format function. This is the error it displays when i tried with the download button: BROM ERROR: S_DA_SDMMC_WRITE_FAILED (3149)
And this is the same error it displayed when i tried using the Format function: S_DA_SDMMC_WRITE_FAILED (3149)
i am so, so sorry for bothering with this.
Click to expand...
Click to collapse
Try with another version of SP Flash tool little bit newest .