I am using CE OS 5.2.20753 Build 20753.1.4.0 PV SB on O2 Atom Exec. I am trying to flash my ROM with any of the provided ROMS in this forums rite from WM5 till Jamies latest ROM.
As a background, I have already configured my mobile in VISTA laptop using the MANUALS & RAR files, provided around a year back.
The problem is as follows:
1. I run the package, which internally unzips all the files in C:\Windows\Temp
2. DSUU starts executes and provides a screen to select OS, OS+Extended ROM, OS+Eboot only, etc....
3. I tried using both ALL, OS only, OS+Extended ROM but i get the error as mentioned below.
4. I get a screen which speaks about all the my current RADIO, ROM version and the TO BE new versions.
5. I select OK / Continue.
6. Program reboots my Atom exec and stucks in "USB CONNECTED" black screen. This continues untill i try to manually terminate the DSUU process.
7. To recover from this, I remove the battery manually and insert and start the phone.
8. Phone starts working from the stage where I started flashing with new ROM.
I am totally confused as i tried a lot of ROMS rite rom Wm5, WM6 & WM6.1 which also includes all the ROMS, which i have already used in the past on the same phone.
Gurus, please suggest the possible wayout, as i am stuck on this ROM for a long time and unable to test all these new wonderful ROMS.
ASH
use win xp not vista in flashing roms...
Use the search function, there is an answer to Your question in some of the forums at xda-developers and it is posible to flash roms from VISTA, but after doing some reinstalation on USB drivers and some tweaking....try to find VISTA ROM UPGRADE
My experience is:
I followed the instructions and they worked 2 times and I have flashed the ROM twice, I dont know what happened to my computer because after that never again make it to work in vista.
I whish You Could!
Thanks
Thanks for the suggestions. I have flashed this mobile around more than 20 times out of which atleast 10 times in Vista.
My problem is, after flashing the current ROM, i am unable to flash on this device. i tried flashing other device from the same laptop and it works
When i start the flashing procedure, mobile enters into Boot mode and then nothing happens. i remove battery and mobile boots up with the same old ROM.
Please helppppppp
ASh
I have a tmous HD 2 that orinally had windows os on it. I have since tried to flash a new rom. When I originally started this process I was dual booting. The phone would start out in windows mobile 6.5 with no update and I had to phisically launch the Android rom. After this I started playing around in order to get phone to boot in android only. The SPL I have is 2.08 HSPL I was getting stuck at the t-mobile stick together screen and then I tried bootloader mode and I was able to launch boot loader mode but wont let me do anything. Originally the rom was in an unziped format and thats how i was dual booting. Then i tried the ziped format and this is where my phone has went bonkers and won't do anything, by that i mean it wont turn on in either mode regualr or boot load. tried to connect to computer and computer dosent regonize it. has anyone ran across this? and if so can you please help me out? i am a little tech savvay but not great at it. any help would be greatly apricceated. Also when i had android running on phone it was supprisingly fast and worked flawlessly!
From a previous thread here on xda.
Q; How to install cooked Rom (using Task 29)
My Install Strategy;
· Run Microsoft My Phone Sync
· Turn off antivirus software in Desktop PC (Stop Avast Anti-Virus)
· Remove SIM and microSDHC Storage Card
· RUN XDA Developers “HD2 Task 29” as an Administrator
Task 29 is not mandatory that's true, but it's a safe way to ensure that you don't have any old files remaining after flashing a new rom.
There is no harm in doing it and the easy way is to use the tool I provided in this post:
Connect your device and flash as you do with an ordinary rom, when completed (100%) press volume down and keep I pressed until the device has restarted showing the coloured boot screen, then you flash the Rom.
· Install your cooked Rom as an Administrator
NOTE 6: Please, Hard-Reset after flash process has completed.
· Add SIM and microSDHC Storage Card
· Set Time and DATE
NOTE 7: Please, Restart the phone, after first manila screen.
· Run Desktop pc FULL ActiveSync, select setup device.
I have done this but phone wont boot up in order to do a hard reset like mentioned!
Q; I downloaded and extracted the zip file from a cooked Rom, and noticed there was no ruu file attached. What to do?
You can download the SSPL_RUU, here. place the SSPL_RUU file into the map where you unzipped your cooked Rom and lounge to start.
I have done this.
What more do I need to do in order to get my phone back up and running?
Thank you in advance for help and support
I've succesfully installed Ubuntu on the AC100 on internal Storage.
Because Ubuntu was a bit slow I "played" around with removing packages, changing X-Desktop etc.
Long Story Short: Linux hangs up on booting
Now I wan't to switch back to Android, but there are a few Problems:
1. I have no Backup (yes, you may call me a morron)
2. I tried to flash Images from Folio3xx v0.4(Honeycomb for Folio 100) via Fastboot Method, but I can't get into fastboot mode (3xPower, 1xVolUp)
3. what I can do is boot into RecoveryMode (ctrl+esc, power on) but I don't know what and if I can do anything in RecoveryMode
On my PC I can use Win7 and Linux (Ubuntu)
I hope anyone can help........
This is Folio 100 thread, not AC100. This roms probably won't work on your device. Go here and ask if someone can solve your problem.
Jon2555 said:
This is Folio 100 thread, not AC100. This roms probably won't work on your device.
Click to expand...
Click to collapse
Sorry, I thought AC100 uses almost the same Hardware.....
Jon2555 said:
Go here and ask if someone can solve your problem.
Click to expand...
Click to collapse
Altough I prefer XDA I'll try my luck there, THX for link
@Mod - you may close / delete
Hello to all community,
strange things happened here... I use a Star H920+ phone. I had some problems with Bluetooth and Wifi, so i decided to flash rom again. I downloaded the rom from needrom dot com. (As new user, i cannot post the full url yet)
I used Smart Flash Tools to do the job. Firstly i had some difficulties getting some errors. After some search, i used MtkDroidTools and i got the right sizes for memory and write them at scatter file. The procedure went well and i got a green circle at Flash Tool.
And that's it...
After that, i get the absolute Black. But... the strange thing is that the Windows detects the phone. I tried every combination to get into recovery mode, but nothing. Only black screen.
I tried Flash Tools again to flash it with the same or an older rom, but after the some seconds, the application is not responding and Windows says that the Smart Flash Tools application has stopped responding and must be closed.
MtkDroidTools doesn't recognized the phone now.
But, as i have it connected with the pc, the sound of plug and unplug a device is heared all the time. ( Maybe it is rebooting continuously )
I hope that the hoping thing is that Windows detects the phone, but i cannot do anything more...
Do you have any idea to propose me ?
Thank you very much,
Periklis
Perarg said:
Hello to all community,
strange things happened here... I use a Star H920+ phone. I had some problems with Bluetooth and Wifi, so i decided to flash rom again. I downloaded the rom from needrom dot com. (As new user, i cannot post the full url yet)
I used Smart Flash Tools to do the job. Firstly i had some difficulties getting some errors. After some search, i used MtkDroidTools and i got the right sizes for memory and write them at scatter file. The procedure went well and i got a green circle at Flash Tool.
And that's it...
After that, i get the absolute Black. But... the strange thing is that the Windows detects the phone. I tried every combination to get into recovery mode, but nothing. Only black screen.
I tried Flash Tools again to flash it with the same or an older rom, but after the some seconds, the application is not responding and Windows says that the Smart Flash Tools application has stopped responding and must be closed.
MtkDroidTools doesn't recognized the phone now.
But, as i have it connected with the pc, the sound of plug and unplug a device is heared all the time. ( Maybe it is rebooting continuously )
I hope that the hoping thing is that Windows detects the phone, but i cannot do anything more...
Do you have any idea to propose me ?
Thank you very much,
Periklis
Click to expand...
Click to collapse
I have the same problem patrida !!! Have you found out a sollution yet ?
Use SP_Flash_Tool_v3.1344.0.212
And select Firmware -> upgrade
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.