I bricked my Desire 310 when i tried to replace the stock recovery.
Rooted it successfully, read a lot of threads regarding MTK-based phones and thought i might be able to get more out of it, as i wasn't completely fine with 4.2.2 installed on a brand new phone.
However, i ended up with trying to install a custom recovery as described [here(would be a link if i were allowed to post them)]. The whole process gave no error, everything looked fine, ending with a "success!"-message, followed by a reboot, showing just the HTC splash... and a reboot... and a reboot... and.. well i guess you know what happened next.
Based on a whole lot of different threads, this might not be the end of my phone, as i can still see the [preloader(would be a picture if i were allowed to link it)] in my device manager, which basically means "hi, i'm not completely dead and you might find a way to recover me".
The question is: how?
I tried out SP Flash tool and MTK Flash tool so far. both programs find the phone when i get it ready to download my previously made backup (hey. i might not exactly know what i'm doing there, but at least i saved everything before i wrecked it! ).
The problem is: I just get an[error message(look above)] about some failed download to SRAM sorcery, which sounds cool and important but doesn't give me a clue about what i'm doing wrong or how to fix it. (cable ok tested 3 different cables, including the one the device was shipped with, also tested it on my PC running win 8.1 x64 and another one running win 7 x86)
Does anyone have an idea how i could get at least a working bootloader/recovery back to my device?
Tell me if you need any extra information
I also link an attachment including the log file created by SP Flash Tool.
View attachment 2772794
Well. That's it. Thanks in advance for anything that may be posted in here
Two Pictures related to this:
View attachment 2772803
View attachment 2772804
Need your help
Reebee87 said:
I bricked my Desire 310 when i tried to replace the stock recovery.
Rooted it successfully, read a lot of threads regarding MTK-based phones and thought i might be able to get more out of it, as i wasn't completely fine with 4.2.2 installed on a brand new phone.
However, i ended up with trying to install a custom recovery as described [here(would be a link if i were allowed to post them)]. The whole process gave no error, everything looked fine, ending with a "success!"-message, followed by a reboot, showing just the HTC splash... and a reboot... and a reboot... and.. well i guess you know what happened next.
Based on a whole lot of different threads, this might not be the end of my phone, as i can still see the [preloader(would be a picture if i were allowed to link it)] in my device manager, which basically means "hi, i'm not completely dead and you might find a way to recover me".
The question is: how?
I tried out SP Flash tool and MTK Flash tool so far. both programs find the phone when i get it ready to download my previously made backup (hey. i might not exactly know what i'm doing there, but at least i saved everything before i wrecked it! ).
The problem is: I just get an[error message(look above)] about some failed download to SRAM sorcery, which sounds cool and important but doesn't give me a clue about what i'm doing wrong or how to fix it. (cable ok tested 3 different cables, including the one the device was shipped with, also tested it on my PC running win 8.1 x64 and another one running win 7 x86)
Does anyone have an idea how i could get at least a working bootloader/recovery back to my device?
Tell me if you need any extra information
I also link an attachment including the log file created by SP Flash Tool.
View attachment 2772794
Well. That's it. Thanks in advance for anything that may be posted in here
Two Pictures related to this:
View attachment 2772803
View attachment 2772804
Click to expand...
Click to collapse
Hi ! saw your thread and required your help
1) can u proveide me information about how exactly did you root your device !!
And secondly if u remember your phone's build number can u plzz tel me because I also have aproblem with my desire 310 its single sim and 1gb ram version I eceived a software update and after the installation the phone keeps rebooting after every 2 mins if I use it or plug it in for charging and stays awake if I put it in ecovery or factory mode so I needed your roms backup so that I can fix my phone Unless if your phone was of the same specks as mine
I will be waiting for your soon response thanks
It happend the same for me! U can try recovery mode but it is not gonna work.
I have the same problem (
i have this phone and after update that i have no problem with that. my phone is rooted by vroot app
Reebee87 said:
I bricked my Desire 310 when i tried to replace the stock recovery.
Rooted it successfully, read a lot of threads regarding MTK-based phones and thought i might be able to get more out of it, as i wasn't completely fine with 4.2.2 installed on a brand new phone.
However, i ended up with trying to install a custom recovery as described [here(would be a link if i were allowed to post them)]. The whole process gave no error, everything looked fine, ending with a "success!"-message, followed by a reboot, showing just the HTC splash... and a reboot... and a reboot... and.. well i guess you know what happened next.
Based on a whole lot of different threads, this might not be the end of my phone, as i can still see the [preloader(would be a picture if i were allowed to link it)] in my device manager, which basically means "hi, i'm not completely dead and you might find a way to recover me".
The question is: how?
I tried out SP Flash tool and MTK Flash tool so far. both programs find the phone when i get it ready to download my previously made backup (hey. i might not exactly know what i'm doing there, but at least i saved everything before i wrecked it! ).
The problem is: I just get an[error message(look above)] about some failed download to SRAM sorcery, which sounds cool and important but doesn't give me a clue about what i'm doing wrong or how to fix it. (cable ok tested 3 different cables, including the one the device was shipped with, also tested it on my PC running win 8.1 x64 and another one running win 7 x86)
Does anyone have an idea how i could get at least a working bootloader/recovery back to my device?
Tell me if you need any extra information
I also link an attachment including the log file created by SP Flash Tool.
View attachment 2772794
Well. That's it. Thanks in advance for anything that may be posted in here
Two Pictures related to this:
View attachment 2772803
View attachment 2772804
Click to expand...
Click to collapse
Select DA_SWSEC.bin as Download-Agent...
Related
i just bought a chinese htm xs5292 runnin 4.1.1 i want to root and upgrade to 4.3 any help on how to do this would be greatly appreciated, here are the specs
manufacturer - htm
model - x5292
android version - 4.1.1
kernel - x5292 dual core
software - mt5617-c913-en-vo5
hardware - c913-v1.02
i'm a first timer at this so please speak like you would to a child (even though i'm 35)
many thanks in advance
paul
paul0909 said:
i just bought a chinese htm xs5292 runnin 4.1.1 i want to root and upgrade to 4.3 any help on how to do this would be greatly appreciated, here are the specs
manufacturer - htm
model - x5292
android version - 4.1.1
kernel - x5292 dual core
software - mt5617-c913-en-vo5
hardware - c913-v1.02
i'm a first timer at this so please speak like you would to a child (even though i'm 35)
many thanks in advance
paul
Click to expand...
Click to collapse
I can help you get rooted. First you will need to install drivers on your PC so your device can communicate with the root program. Then try this:
http://forum.xda-developers.com/showpost.php?p=43163569&postcount=7
If that dont work, let me know. You can always use MTK Droid Tools and SP flash tool to pull your stock recovery and port it into a custom recovery that will allow you to flash a simple root.zip
Hope this helps!
usb drivers
thanks Klown80, that looks like it should work, but first i need to install my usb drivers, i have loked at a ton of sites and they all didnt work, i need spreadtrum usb drivers, but can't figure out wich ones, a few said they all worked on any spreadtrum phone, but either im installing them incorrectly, or they simply didnt work,
again, thanks for any help in advance
paul
paul0909 said:
thanks Klown80, that looks like it should work, but first i need to install my usb drivers, i have loked at a ton of sites and they all didnt work, i need spreadtrum usb drivers, but can't figure out wich ones, a few said they all worked on any spreadtrum phone, but either im installing them incorrectly, or they simply didnt work,
again, thanks for any help in advance
paul
Click to expand...
Click to collapse
Try using this, it installs drivers for many different phones, it may not be the actual manufacturers drivers for your specific device but it will help get your phone talking to your PC:
http://www.snappea.com/
Also - Make sure you are going into settings and turning USB debugging on. You can usually find this under Settings > Developer Options.
snapea
Again, thanks Klown, but no joy, i tried serveral times and after 15 - 20 mins of "fobulating" (is that even a real word ) my phone it said "failed to processs phones data" i tried restarting both devices etc and a couple of other thing suggested but no joy.
Any other ideas, as always thanks in advance.
Paul
oh ps, i also tried to connect to snapea via wifi, but got the same message
paul0909 said:
Again, thanks Klown, but no joy, i tried serveral times and after 15 - 20 mins of "fobulating" (is that even a real word ) my phone it said "failed to processs phones data" i tried restarting both devices etc and a couple of other thing suggested but no joy.
Any other ideas, as always thanks in advance.
Paul
oh ps, i also tried to connect to snapea via wifi, but got the same message
Click to expand...
Click to collapse
Try these drivers
https://www.dropbox.com/sh/oaslz8xuxk7ag50/VRzHnZvA-b
finally
\it worked, can't thank you enough, one more bothersome question, now i have my phone rooted how do i safely, and i emphasise safely upgrade from 4.1.1 to 4.3
I have looked into it a bit myself, and am in half a mind to give it a go, but the warnings about bricking my phone always puts me off, so once again, thanks in advance for any help given, and many thanks for the help so far.
Paul
paul0909 said:
\it worked, can't thank you enough, one more bothersome question, now i have my phone rooted how do i safely, and i emphasise safely upgrade from 4.1.1 to 4.3
I have looked into it a bit myself, and am in half a mind to give it a go, but the warnings about bricking my phone always puts me off, so once again, thanks in advance for any help given, and many thanks for the help so far.
Paul
Click to expand...
Click to collapse
Go here and download MTK Droid Tools from first post:
http://forum.xda-developers.com/showthread.php?t=2160490&styleid=18
Run the program and connect your phone to PC, this tool will tell you lots of info about your phone but the main function is to possibly back up your stock firmware (This is good to have if you plan on trying to flash anything to the phone, this way you will have your stock files to fall back on in case something you flash to the phone does not work.) Once you have MTK Droid Tools running and phone connected, what does it say next to Hardware on the phone info tab please?
I am not sure off top of my head about updating to a higher version of Android but this back up step is REALLY important. It is hard if not impossible to find stock firmware floating around on the net for these chinese clone devices. IF you have stock files backed up you can flash almost anything you want knowing you have a way to restore your phone to working order. IF you look around here on XDA you will see tons of posts by people looking for the stock firmware for their clone phone after soft bricking it playing around. Sadly there is not much help for them unless they find someone with the EXACT same phone and are willing to share their back up (if the next person made one theirselves that is!)
hardware
Klown80 said:
Go here and download MTK Droid Tools from first post:
http://forum.xda-developers.com/showthread.php?t=2160490&styleid=18
Run the program and connect your phone to PC, this tool will tell you lots of info about your phone but the main function is to possibly back up your stock firmware (This is good to have if you plan on trying to flash anything to the phone, this way you will have your stock files to fall back on in case something you flash to the phone does not work.) Once you have MTK Droid Tools running and phone connected, what does it say next to Hardware on the phone info tab please?
I am not sure off top of my head about updating to a higher version of Android but this back up step is REALLY important. It is hard if not impossible to find stock firmware floating around on the net for these chinese clone devices. IF you have stock files backed up you can flash almost anything you want knowing you have a way to restore your phone to working order. IF you look around here on XDA you will see tons of posts by people looking for the stock firmware for their clone phone after soft bricking it playing around. Sadly there is not much help for them unless they find someone with the EXACT same phone and are willing to share their back up (if the next person made one theirselves that is!)
Click to expand...
Click to collapse
Thanks again, while i go to the link and follow the next steps i thought i'd put up the hardware version you asked for
hardware - c913-v1.02
Paul
edit
even though my pc now recognises the fact that tere is a spreadtrum phone in my devices list and i managed to root it ok, when i load up mtk droid tools it says "the device isn't revealed, connect or reconnect a cable"
needless to say i tried reconnecting and it didn't change i downloaded the adb drivers from the link under the mtk link but have no idea what to do with them,
appologies for my ignorance in all of this, but like i said in my first post, i have no idea what i'm doing with all this, thanks
paul
pps the hardware version i posted was from the info on my phone
Hi fellow xda'rs,
I recently bought a Android TV Stick from Geek(app) from china.
I thought I had found a bargain as its specs were:-
2GB RAM
Quad Core CPU
16GB Storage
I managed to snap this up for £24 which I thought was a bargain but when I got the device delivered and was using it I thought it was a little on the slow side so I began to think it was a clone as its default OS theme was not the same as the usual CX919's aswell.
So I wanted to flash the device with a new ROM specifically the Finless 1.6b ROM.
So after following the instructions to installing the ROM using the software provided with the ROM download I managed to install the drivers and get the software to recognize the device. I then wiped the NAND and attempted to install the ROM but it failed .
Now the device does not boot at all and is not recognized by the PC. Windows just states the device is not recognized and has malfunctioned
So I cannot flash any other or what I believer I have found to be the original ROM for the clone device.
The board states its a GXT_D16_LP_V1.8 150310
I have seen that there are tutorials on putting the device into Mask Flash mode by shorting pins but as this is for the genuine CX919 my board is totally different and does not have the pins available to short I think.
In short could anyone help me to put this device into Mask Flash mode and tell me what id need to do and what pins to short please?
I have attached a couple of pictures of the device and board.
lowery91 said:
hi fellow xda'rs,
i recently bought a android tv stick from geek(app) from china.
I thought i had found a bargain as its specs were:-
2gb ram
quad core cpu
16gb storage
i managed to snap this up for £24 which i thought was a bargain but when i got the device delivered and was using it i thought it was a little on the slow side so i began to think it was a clone as its default os theme was not the same as the usual cx919's aswell.
So i wanted to flash the device with a new rom specifically the finless 1.6b rom.
So after following the instructions to installing the rom using the software provided with the rom download i managed to install the drivers and get the software to recognize the device. I then wiped the nand and attempted to install the rom but it failed .
Now the device does not boot at all and is not recognized by the pc. Windows just states the device is not recognized and has malfunctioned
so i cannot flash any other or what i believer i have found to be the original rom for the clone device.
The board states its a gxt_d16_lp_v1.8 150310
i have seen that there are tutorials on putting the device into mask flash mode by shorting pins but as this is for the genuine cx919 my board is totally different and does not have the pins available to short i think.
In short could anyone help me to put this device into mask flash mode and tell me what id need to do and what pins to short please?
I have attached a couple of pictures of the device and board.
Click to expand...
Click to collapse
problem solved! :d
i found the mask flash mode pins to short by trial and error and luckily enough after 1 hour i solved it and got the pc to flash it back to its original rom. If anyone has the same device or issues and would like to know how to solve this i will be happy to help
I would be interested. I have a very similar clone (was supposed to be mk809iv). I have the same board although possibly different chipset.
I haven't bricked it (yet) but will probably do so if I can't find a way to root it. I think it may have come pre-rooted as super su was preinstalled but it has never worked (possibly because the app updated but not the binary?). I have since tried to update the binary and killed the root access completely.
Questions:
Is the ROM you used pre-rooted or rootable (if you've tried)?
Which pins need shorting? I have a button on the side that may be doing the same thing.
OT. How do I upload images or can I not as a new member?
Thanks in advance
any guide? i have the same device or where to download rom?
If your still looking, i might be able to help with a rom, root, and guide.
Thank you but managed to get root the same day you posted. I may still give it a go when my new tv box turns up though if you dont mind posting the info?
For anyone else interested in how I gained root:
1. Search for, download and install kingroot 4.6.5 (this is the version I used, only the latest version is available from official site and cannot be sure next steps will work with it)
2. Run kingroot and follow steps to gain root (dongle may reboot)
3. BUY super sume from play store.
4. Run super sume and follow steps to replace kingroot with super su.
what pins did you short
I am having problems flashing my hdmi stick . I can't get it to flash mode. which pins did you shorted?
can you email me a picture of it? [email protected] thanks
Lowery91 said:
problem solved! :d
i found the mask flash mode pins to short by trial and error and luckily enough after 1 hour i solved it and got the pc to flash it back to its original rom. If anyone has the same device or issues and would like to know how to solve this i will be happy to help
Click to expand...
Click to collapse
Hello,
Having some problems with this stick .Messed up trying to flash a non rooted rom and now I only get a blue icon in rkbatch tool ( after short pin 5-6 ) and nothing happens. Download boot fail errors for a year...
Can someone help me please?
Is it the same model? What version of rkflash tool are you using. And what version are you trying to flash. In my case I didn't need to short any pins.
spade2be said:
Is it the same model? What version of rkflash tool are you using. And what version are you trying to flash. In my case I didn't need to short any pins.
Click to expand...
Click to collapse
I've used several batchtools from 1.5 ( doesn't see my device at all ) to 1.8, different roms ( neomod, finless, stock cx919 roms )hoping one would give me something. All different bootloaders 1.24, 2.08, 2.13,...
I'm going to check mine out. It's been a minute since I used it. But I got the rock chip tool and the img file. I'll zip it up and pm you the link asap.
spade2be said:
I'm going to check mine out. It's been a minute since I used it. But I got the rock chip tool and the img file. I'll zip it up and pm you the link asap.
Click to expand...
Click to collapse
Thnx a million for your help. I've gone bonkers over this hahaha
Lowery91 said:
problem solved! :d
i found the mask flash mode pins to short by trial and error and luckily enough after 1 hour i solved it and got the pc to flash it back to its original rom. If anyone has the same device or issues and would like to know how to solve this i will be happy to help
Click to expand...
Click to collapse
what pins did you short
I am having problems flashing my hdmi stick . I can't get it to flash mode. which pins did you shorted?
can you email me a picture of it? [email protected] thanks
So I got a cheap android tablet and I wanted to root it. I was successful so I decided to install TWRP. I searched for my specific model and found an image on a german forum. I downloaded and flashed it and it got stuck in a reboot loop. So I looked at the image and it was for the QV1030. I tried to get it into recovery but couldn't. Many sources told me to hold Vol Up and Lock, and I tried this and more. Nothing would make it enter recovery mode. Then I read about SP Flash Tool and found the stock rom for the tablet and decided I would try to flash that. It kept coming up with an error, and every source online told me to format the flash except for the bootloader and then I could flash it. So I did. Now it doesn't show anything on screen, and SP Flash Tool comes up with error 6045. But it does show up in device manager under com ports as, "MediaTek USB Port" so I think I can still do something about it. I don't have any backups. I don't know what I'm doing. I require assistance please.
So I reflashed the entire backup and it come up with no error. The logo comes up and it plays the chime. The logo does this little shimmer effect and once it gets to this screen, it shimmers indefinitely. If I plug it in, it begins installing a driver and then stops part way through.
drsinclair said:
So I reflashed the entire backup and it come up with no error. The logo comes up and it plays the chime. The logo does this little shimmer effect and once it gets to this screen, it shimmers indefinitely. If I plug it in, it begins installing a driver and then stops part way through.
Click to expand...
Click to collapse
I left it for about 5 minutes and it finished the driver. I thought it froze but I was wrong. It shows up now on device manager under Portable Devices as, "MTP USB Device". I tried to see if it was listed as a device by ADB. It is not. Lets just say I've already learned a thing or two about this stuff. Good thing I did it on an 80 dollar chinese tablet and not my HTC One M9
drsinclair said:
I left it for about 5 minutes and it finished the driver. I thought it froze but I was wrong. It shows up now on device manager under Portable Devices as, "MTP USB Device". I tried to see if it was listed as a device by ADB. It is not. Lets just say I've already learned a thing or two about this stuff. Good thing I did it on an 80 dollar chinese tablet and not my HTC One M9
Click to expand...
Click to collapse
I got it to work again mostly. So I realized that I wasn't flashing the whole backup. Some things didn't have a path and I had to set it manualy. Now it has CFW for some reason, but I reset it and it works now. The only thing is WiFi is not turning on. Any ideas about that?
drsinclair said:
I got it to work again mostly. So I realized that I wasn't flashing the whole backup. Some things didn't have a path and I had to set it manualy. Now it has CFW for some reason, but I reset it and it works now. The only thing is WiFi is not turning on. Any ideas about that?
Click to expand...
Click to collapse
I actually want to upgrade this from Android 4.2.2 to a more recent version. Do you guys have any ideas about that?
So I've come to the conclusion that while the device is no longer bricked, the current installation is written over the old one and things are conflicting. I know this because I looked through the cache and found filenames referring to apps I had installed before breaking it. So would the solution be to wipe the system partition and reflash the system.img so everything is fresh? Or does the problem lie elsewhere.
I formated the system partition, used SP Flasher to flash system.img and then did a factory reset. The issue has still not been solved. And now that I have done that, I don't have root access anymore. Framaroot says it was successful and I restart and check root explorer on ES File Explorer and it doesn't work.
I gained root access using a different method. However the WiFi still doesn't work. I think it may be that the mac address information was from the backup I flashed from the internet, and therefore doesn't match. I found a guide that tells me how to hex edit a file and put in my real mac address, but it's unavailable under wifi. I don't have the sticker on the back that says it either. How else can I find it?
Turns out the mac address can be anything. I used SN Write tool and an AB DB for my chipset and it still didn't solve the problem. I have no idea what to do. Can anyone help me?
I fixed the issue by grabbing a different backup from some russian website and flashing the system.img and secro.img to it. It now works fine 100%. Thanks
help - link
drsinclair said:
I fixed the issue by grabbing a different backup from some russian website and flashing the system.img and secro.img to it. It now works fine 100%. Thanks
Click to expand...
Click to collapse
Hey man! I have the same problems with my QV 830. Can you give me the link for system.img and secro.img, please?
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.
Here you go:
https://1drv.ms/u/s!AshkuG2cY1T0xPZArSsy6iO1e_UnPw
This is a zip file with all the tools and files you need and instructions on how to use them.
What it covers:
Restoring bricked device (as long as download mode still works)
Unlocking bootloader (firmware dependent)
Rooting (any firmware)
Installing a custom recovery (any firmware)
Installing a custom ROM (any firmware)
I made this because all the guides for this phone were seemingly outdated, and some required tools and files were incredibly hard to find. Didn't want anyone else going through the pain I went through to break this phone open.
Thank you so much for uploading this. The charging port on my Nexus died and I have to use my old Note 2 as a backup, but I forget how this old piece of junk works. This should be very helpful.
I rooted and flashed twrp to boot to a triangle saying system software not authorized. Tried 3 firmwares and wont boot correctly. I got error about firmware update failed use kies... Kies won't do anything and kies 3 says unsupported device. On the 3rd firmware (root66 rooted stock ) firmware file I now am back to the original triangle system software not authorized by Verizon ..
How do I fix this?!?
robles4242 said:
I rooted and flashed twrp to boot to a triangle saying system software not authorized. Tried 3 firmwares and wont boot correctly. I got error about firmware update failed use kies... Kies won't do anything and kies 3 says unsupported device. On the 3rd firmware (root66 rooted stock ) firmware file I now am back to the original triangle system software not authorized by Verizon ..
How do I fix this?!?
Click to expand...
Click to collapse
Did you read my guide? You can't flash TWRP unless you successfully unlocked your bootloader with Casual, otherwise you are limited to SafeStrap. Also you can't restore with Kies, you have to use Odin and the files I've included to restore.
yambag said:
Thank you so much for uploading this. The charging port on my Nexus died and I have to use my old Note 2 as a backup, but I forget how this old piece of junk works. This should be very helpful.
Click to expand...
Click to collapse
Nice to see people still looking for something like this, so my guide wasn't for nothing!
I was geeked to see this!! but then i got "This item might not exist or is no longer available"
I take it back.. i let it sit on the "failed" page for like 2 min, and randomly it popped up with a download!
Well the auto bootloader didn't work, so now i'm at the root section. However i'm getting an error where ADB isn't detecting my phone. USB debug is on, and i'm definitely in media mode and not installer. The phone shows up in windows and looks good, but adb doesnt detect. I opened command prompt and ran adb /? and found adb devices -l, and it reports "list of devices" and theres nothing in the list. I can't imagine why it's not seeing it. I tried turning on and off debug mode, switching from camera mode to media, changing usb ports. still nothing comes up, but windows sees it fine. grrrr
*edit, well since we can't delete posts i'll leave this here, because i have to. But what i did was re-open the "no you verizon" and it showed DISCONNECTED also. I changed usb ports like 3 times, turned usb debug on and off, changed from installer mode, to camera, to media mode, restarted the phone and the computer multiple times.. and then it just all of a sudden was detected again. So i went with it and it seems to have worked.
-it took 3 times to actually work, you noted it may take multiples, and it sure did. I ran it through the command prompt so i could read the text, and it took 5 times longer and reported much more stuff when it actually worked.
-final edit: if you can't unlock your bootloader, you're still stuck with ditto or alliance from 2014, and lots of apps won't update on android that old. So if you thought this guide was some holy grail, it is not. But still useful if you need the assist, so thanks to the author.
Hi, total noob here, I just bought Verizon note 2 at a yard sale but there is a pin I don't know. When I went to do a factory reset it booted into TWRP, so I am assuming is rooted. Do I need to be able to get into the phone to use your tools? I know nothing about TWRP. I would like to install a newer Android version and unlock it so I can use TMobile. Thanks
Something wrong...
when i try to load this file from the packages folder i get an error message:
"md5 error! Binary is invalid"
none of the other three works for me. they all come back ailed.
any suggestions?
awesome! thanks for posting this, just found my old note 2 and want to get it up and running again for the kids.
Kudos!
Used this to get my Note 2 up and going again temporarily until the Pixel 4a release...
NOTE: I had strange issues with Odin on my modern X570 board (USB 3.2 Gen 2) where I did not receive any errors, yet the process would randomly seem to time out. Sometimes I'd get stuck at flashing boot.img, sometimes it would hang up at the start, once I got to flashing system.img and it seemed to hang....
Used an older PC circa 2013, no issues! Not the first time I've had issues with this newer motherboard and older USB flashing interfaces; had the same issue on my Note 8 (RIP) as well.
excited to try this.
I'm on some rooted 4.4.2 stock-looking rom. Recovery doesn't look custom.
Hoping to be able to install a working Oreo or Pie ROM
great post, bought a couple of these for almost nothing and am having fun playing with them. sadly they are both 4.4.2 but its great fun anyway.
SilentNightx said:
I made this because all the guides for this phone were seemingly outdated, and some required tools and files were incredibly hard to find. Didn't want anyone else going through the pain I went through to break this phone open.
Click to expand...
Click to collapse
Thank you for sharing. Always difficult to find those tools after a few years!!!