Develop Bugs

[REF] If odin gives error - unbricking

Guide
Yesterday I first successfully flashed G5 firmware + root. Later I unsuccessfully tried to make the lag fix for memory card. After that I recovered back up using Back UP Pro and restarted. Got a bunch of FC, so decided to reflash.
During the flash on first step odin crashed (just a nondescript message with attention sign and path to Odin) + second error right after first one, only with some strange symbals-hieroglyphs after the path to odin).
Edit - pics:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and
After that nothing is happening in odin and everything is grayed out. Error can be different (that was just my error), but the point is that phone is bricked (does not turn on). Causes can vary from you disconecting device during flash, computer crashing, ODIN crashing (my case), alien abductions and other very possible reasons =)
After that I always got the same problem - either stuck on reading file (or what is the first step analyses, etc) or crashes (mostly now).
Phone is bricked - I can either go to download screen, or some screen with phone and computer icons connected by dotted line with attention icon - screenshot, thanks to m3keni.
I looked at "Disable Driver Signature Enforcement" (thanks goes to blackerwater) advice and several recovery advices (up + menu + power; down + power; laptop does not recognize apd device).
Win 7 x64.
Solution

try odin on a different computer phone should be ok once you flash.. i flash multiple times on one then suddenly wouldnt flash anymore.. just hung.. re-did it on a laptop and it worked fine.

dupel said:
Yesterday I first successfully flashed G5 firmware + root. Later I unsuccessfully tried to make the lag fix for memory card. After that I recovered back up using Back UP Pro and restarted.
Got a bunch of FC, so decided to reflash.
During the flash on first step odin crashed (just a nondescript message with attention sign and path to Odin) + second error right after first one, only with some strange symbals-hieroglyphs after the path to odin).
After that I always got the same problem - either stuck on reading file (or what is the first step analyses, etc) or crashes (mostly now).
Phone is bricked - I can either go to download screen, or some screen with phone and computer icons connected by dotted line with attention icon.
I looked at "Disable Driver Signature Enforcement" advice and several recovery advices (up, menu, power; down, power; laptop does not recognize apd device), however, haven't found anything good. Including restarting (device, laptop), using different usb slots (eventually run out of), etc.
What are the other options for recovery? And any possible advice on such an error? Like how to do a complete wipe, hardreset, recovery, better flashing advice?
My first time bricking Android (god knows how much times I did it to my symbian )
Win 7 x64. Will add screenshots (if forums will allow me) tomorrow afternoon, now I need some sleep and have to wake up early.
Click to expand...
Click to collapse
something like this???
If so, try to remove the battery.. leave it out for about 30 - 60 seconds.. patience is the key..
Try to restart your computer and then upon restart.. load odin.. load pit.. code.. modem.. csc..
Now on your phone.. press the volume down + home key then power ON the phone.
Connect your device to your computer.. ding ding..
As per the odin application choose, enabale re-partition..
Then press START.
**cross your fingers and hope for the best.
**i encountered that screen when my lappy suddenly died.. unplugged the wrong power cord (my lappy's battery is MIA at the moment).
Wish you all the best and hope this works.

m3keni said:
something like this???
Click to expand...
Click to collapse
Yup, thats the screen. Today quickly in the morning managed to start up odin, but it got stuck on "set pit file, do not turn off" step. Stuck there for some 5 min already.

dupel said:
Yup, thats the screen. Today quickly in the morning managed to start up odin, but it got stuck on "set pit file, not dot retn off" step. Stuck there for some 5 min already.
Click to expand...
Click to collapse
..since it's been 5 minutes already.. disconnect your phone and then remove the battery for about a minute or 2.
..prepare the following..
s1_odin_20100512.pit *from http://forum.xda-developers.com/attachment.php?attachmentid=359929&d=1279109916
PDA: CODE_I9000XWJG5.tar *from JG5 firmware
PHONE: MODEM_I9000XXJG1.tar *from JG5 firmware
CSC: CSC_I9000OXXJG4.tar *from JG5 firmware
..Access the download mode of your phone.. vol down + home ++ ON..
..Open ODIN3 and then set the directories for the files listed above..
..Connect your phone to the PC and wait for about a minute or 2..
..On ODIN3.. ID:Com should show something.. yellow bar with com port ranging from 1 to 10..
..tick Re-Partition and when you are ready click START.
[that is the exact steps I followed]

m3keni said:
..since it's been 5 minutes already.. disconnect your phone and then remove the battery for about a minute or 2.
..prepare the following..
s1_odin_20100512.pit *from http://forum.xda-developers.com/attachment.php?attachmentid=359929&d=1279109916
PDA: CODE_I9000XWJG5.tar *from JG5 firmware
PHONE: MODEM_I9000XXJG1.tar *from JG5 firmware
CSC: CSC_I9000OXXJG4.tar *from JG5 firmware
..Access the download mode of your phone.. vol down + home ++ ON..
..Open ODIN3 and then set the directories for the files listed above..
..Connect your phone to the PC and wait for about a minute or 2..
..On ODIN3.. ID:Com should show something.. yellow bar with com port ranging from 1 to 10..
..tick Re-Partition and when you are ready click START.
[that is the exact steps I followed]
Click to expand...
Click to collapse
Thats exactly what I have been doing (and tried flashing pit 513 + JG1, as it was my previous firmware), but once again am stuck at crashes in odin.
Will try, if everything fails today, to flash it from friends computer in the evening.

Have you tried downloading a fresh copy of odin? Odin should not need any compatibility modes so you should start looking for what you changed on your PC between the last working and the non-working flash. But rest (relatively) easy: The state your phone is in, is quite easily recovered (given you have a working PC)

Just reflashed my phone successfully. In case anyone has the same error in future what I did is:
1) Run ODIN with admin rights and in comparability mode.
2) Restart. I did about gazilion restarts, both windows and phone.
3) Every flash - restart of phone (remove battery), without SD card or SIM card, restart of Windows (7 x64) - during the boot process press F8 and Select "Disable Driver Signature Enforcement". (thanks to http://forum.xda-developers.com/showthread.php?t=723041 ).
Every restart - new USB port, not sure if it did affect anything.
4) While I have seen recommendations to close Kies and any other software that could use COM ports (I have OVI Suite and Nokia PC Suite installed for my old Nokia 5800) on last sucesful flash-reboot I left everything running.
5) Try re-downloading ODIN again, in case it is corrupted. Or re-downloading the firmware.
6) Very possible solution for my original problem (screenshots) - starting ODIN as soon as windows starts and to flash as soon as you can after windows start. Seems to fix my original issue.
7) Interesting solution by eizyark
The most sucessful combination proved to be:
a) Restart the PC using the Disable Driver Signature Enforcement.
b1) Optionally (if you already have bricked device) try leaving Kies on (tray icon).
b2) Run ODIN and select files you wish to flash (I used pit 512 and JG5 files - all 3, code-pda, modem-phone and csc).
b3) Usually it is recommended to select "Re-Partition" (in some cases might actually help you unbrick - experiment) - I did not.
c) Switch on the phone (insert the battery) and boot into download mode (Volume down + Menu + power)
d) Connect the cables (cable was disconnected from both the device and laptop). At this stage Odin should see your device, as described by flash tutorials (yellow + COM).
e) Flash.

Darkstriker said:
Have you tried downloading a fresh copy of odin?
Click to expand...
Click to collapse
Actually I did. Don't think it was actually a problem with ODIN as its just an executable file. Old-new file sizes were the same and it made no difference trying to flash.
All I can say - Im guite a geek, have been playing around with computers for more than decade and I still dont understand them. I really have no idea what was so different this time, but I actually did flash my phone again.
What is even funnier - just tried to flash the modified kernel for ext4 partition on sd card - same error (phone though reboots without any problems).

I think I found another way as well on how to save your phone. I had a similar problem. what I did was, when odin has detected the phone, press start without adding anything. after a few seconds the phone will boot up normally. well it worked for me, maybe this might help others as well.
Sent from my GT-I9000 using XDA App

Maybe we should pin this or any other topic for people to post if they have bricked their device?

I'm sorry to say this and I in no way mean to offend you:
This "Solution" is a seemingly random collection of steps, any of which may have originally been the real solution. However, many of the steps are likely superfluous and before this can become a guide/reference, you would definitely need to narrow this down to steps that need to be taken in specific situations.

m3keni said:
something like this???
If so, try to remove the battery.. leave it out for about 30 - 60 seconds.. patience is the key..
Try to restart your computer and then upon restart.. load odin.. load pit.. code.. modem.. csc..
Now on your phone.. press the volume down + home key then power ON the phone.
Connect your device to your computer.. ding ding..
As per the odin application choose, enabale re-partition..
Then press START.
**cross your fingers and hope for the best.
**i encountered that screen when my lappy suddenly died.. unplugged the wrong power cord (my lappy's battery is MIA at the moment).
Wish you all the best and hope this works.
Click to expand...
Click to collapse
If you have this screen then just disconnect the USB lead, press and hold, power, vol. down and home until the 'Downloading' screen appears, start ODIN and then reconnect the USB and reflash.

Darkstriker said:
I'm sorry to say this and I in no way mean to offend you:
This "Solution" is a seemingly random collection of steps, any of which may have originally been the real solution. However, many of the steps are likely superfluous and before this can become a guide/reference, you would definitely need to narrow this down to steps that need to be taken in specific situations.
Click to expand...
Click to collapse
I know =) It was just a solution for my original problem. Thats why I said that this, or any other topic. Its just now we had close to 10 topics, not to mention posts in faq or original topics about each firmware asking pretty much the same questions and describing the almost the same problem.
Introduce a bit of order to anarchy, so to say

dupel said:
I know =) It was just a solution for my original problem. Thats why I said that this, or any other topic. Its just now we had close to 10 topics, not to mention posts in faq or original topics about each firmware asking pretty much the same questions and describing the almost the same problem.
Introduce a bit of order to anarchy, so to say
Click to expand...
Click to collapse
The problem is that (unlike your issue) 95% of those could be resolved simply by reading the FAQ properly.

ODIN
1st post
My phone was stuck in this infinite loop where try as I might I couldn't get it to re-flash I tried different computers and all and the only thing that worked was getting odin to flash without a rom.
it got my phone out of the loop
Helped heaps

m3keni said:
If so, try to remove the battery.. leave it out for about 30 - 60 seconds.. patience is the key..
Try to restart your computer and then upon restart.. load odin.. load pit.. code.. modem.. csc..
Now on your phone.. press the volume down + home key then power ON the phone.
Connect your device to your computer.. ding ding..
As per the odin application choose, enabale re-partition..
Then press START.
**cross your fingers and hope for the best.
**i encountered that screen when my lappy suddenly died.. unplugged the wrong power cord (my lappy's battery is MIA at the moment).
Wish you all the best and hope this works.
Click to expand...
Click to collapse
When I press the Volume Down + Home Key and then Power I get the Phone!PC screen instead of the download screen.

was bored at work and just kept pressing the Download mode combo over and over and it went to download mode from the dreaded cell!pc screen. got the stock rom to flash finally and all appears to be well.

Hi,
Sorry to interrupt but I've managed to brick mine completely...I was trying to update to Froyo without getting any far (not applied any firmware as yet) but I thought I could try the three button fix first so I downloaded the .zip file and stored in root directory of phone.
Before I could apply the fix...i was messing around and the three button worked without applying the fix. However, in recovery mode, first i deleted the data and did a factory reset followed by .zip update (three button fix file...what was i thinking!) which screwed up the phone useless.
It does not power up at all even after removing battery etc...the pc will not recognise it either!
Anything i can do without sending back to samsung/vodafone (the phone was rooted!)
Thanks in advance..ash

Trhow it in the water if you have insurance and hope they give you a new one
Sent from my GT-I9000 using XDA App

Alpine Blackbird 2 - Unlocking The Undone

Hello!
I've been out of the phone game for a while (plan on coming back soon though), but I've been tinkering around with random things.
A few months back I picked up a new car that had a double din alpine head unit, and behind the head unit this PMD - 200 Blackbird 2 was being stowed.
Interested in what it was, I quickly learned it was a Windows CE 4.2 based device that alpine had applied a skin to.
As I started messing with it, I realized that whenever I turned it on, it would just go to a black screen. After looking around online and talking to some Representative at Alpine, there was no longer any support for it and they pretty much told me to go screw myself with my obsolete device.
That's fine, I said...I'll figure out a way to get it working. Obviously the device is home to a Win CE infrastructure and I'd be happy with having that alone...and from there I could do many things.
So I started messing with it. Pushing different button combinations seeing if it would boot into a boot-loader or anything. To my avail, about 15 minutes in I had it booting into Windows CE. I Simply held the reset button and the power button for 15 seconds, let off the rest button, it powered on, started playing with the center button...and poof...Windows CE appeared.
So I start messing around. Checking out the pre-installed data and such. Im about to wife all of Alpine's crappy software and have it boot strictly into windows, and by accident I clicked an icon that booted me back into Alpine's overlay.
No matter! I'll just boot back into windows! So I hold the reset button and turn off the device. Then I go through the process of booting windows again....and nothing...it boots straight into "Map Update Mode". I keep trying the same thing, but the more I try, the more frustrated I get that it won't do what I had it doing before.
That's okay. Map update mode is essentially saying the device is looking for update. Oh..I'll give it an "update" alright I said...But it's plainly recognized as a mass storage device.
MY problem is, this has become about alot more than what Im going to do once I get back into windows. It has been bugging the hell out of me, and I REALLY need to get back in, but Im just running dry. There is absolutely NO information out there about this(well, for the blackbird 2 I should say)
I'll list everything I've found so far, if anyone at all has some words of wisdom, a suggestion, or even knows how to do it...please help me out before my head explodes..
Device/Controls:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
--Top//
--Bottom//
Screens and Functions Achieved Thus Far:
--Normal Boot (Hold Power) //
--Basic Boot (Hold Sound Toggle In the Down Position While Holding Power)//
--No Screen Boot #1 (Hold Power Button While Holding Down Arrow On Keypad)
Center Ring is Lit!
--No Screen Boot #2 (Hold Reset + Power + Down Arrow on Keypad)//
Both Center and Outer Ring Lit!
--Windows CE Boot (Unknown)
Instructions on how to Achieve Windows Mode on Alpine BlackBird 1 (PMD-100):
Here procedure for enterin in WinCE 4.2
1. Plug device in charger.
2. Reset the device in the hole taster,
3. Power on while press and hold arrow up,
4. Relise power and hold arrow up,
5. When screen for update map is show don't touch anything on the screen
6. Press and hold Right taster
7. After few seconds you will see WinCE desktop with 9 icons.
Click to expand...
Click to collapse
USB Connectivity only appears to be viable when the device is in "Basic Boot". At that point it appears a s a mass storage device.
ANY HELP would be GREATLY appreciated. You can tell how much this is bugging me based on how in-depth I made this thread.
As stated before there is NO information on how to do this, so this is practically a developing thread. ANY comments to further this are appreciated!
Thank you!

bump? :/

heroskyy said:
bump? :/
Click to expand...
Click to collapse
yes please! bump!
i too got to play with windows ce and all the fun apps that alpine stacked on my unit. all of which worked until a faithful reboot and now i can get any screen action unless i use the vol dwn pwr button method. i'm stuck. i use this in my truck quite often (mostly for the mp3 player and bluetooth functions) but i'm pissed i potentially bricked this piece. if only i had made a BACKUP! anyway. let's see if we can crack this case and get on with the fun stuff! (like miopocket 4.0)
edit: also when trying to apply the patch for the pmd b200p (which worked the first time) it now hangs at 26%... no idea...

Nothing like reviving an old thread, right? I just bought one of these on ebay and it's on the way right now. I think I found instructions on another site to get to the Windows CE environment for this device but can't confirm it without the device itself. I have an IVA-W505 and want to either force updated navteq maps to the device or better yet, replace the GPS application entirely. I hear the one alpine puts on there is rather buggy so I've been trying to find alternative options for GPS but want to make sure I can get some up-to-date maps. Also wanted to look into some cool applications and interfaces and see if maybe I can figure out how exactly it starts working when docked inside the alpine head unit. Too much to learn and sadly, not much experience trying to figure out how exactly a device works.
I've been collecting links for reference once I get the device, if anyone wants them let me know and I'll try to find them all and post them. I work from 8:00 AM - 4:30 PM EDT/GMT -4 so I can probably respond pretty quickly within that time frame but may respond a little slower outside that time frame.
If anyone has any suggestions for things I can do or requests for information I should try to collect please let me know, I am hoping to have the device by the end of next week
---------- Post added at 10:56 AM ---------- Previous post was at 10:51 AM ----------
I found the instructions to access Windows CE (unconfirmed till I get my device to test) and put them below with the link I found them at:
to unlock the PMD-B200P (the "second" version with Alpine's own version of IGO), you need to reset it, hold the up arrow when powering on. then when the update screen appears, reset it again and this time you need to hold the music button when powering up.normaly this works. if it doesn't (sometimes it doesn't, I don't know why), restart the whole procedure).
then you get a screen where you can choose to launch the satnav, WinCE, update, ... at the right bottom, there is a button "enable/disable menu" . if you set it to enable menu, everytime the unit is powered on you will come to this screen.
I am running this unit now with IGO8 and it works great.
- just empty the "flashdrive". if it's not visible, go to "control panel", "storage manager", select "IDE hard disk", on the right panel, select "properties" and then select "mount". and close all windows.
- copy the IGO map to the flashdrive and rename it "Alpine"
- in the Alpine folder, rename the IGO.exe to AlpineNavi.exe and you are ready to go :dance:
Click to expand...
Click to collapse
http://gpsunderground.com/forum/alpine/3219-pmd-b200-nve-p1-unlock.html
If someone is able to test this, let me know if it works?

So after many attempts and further research I don't seem to be having much luck with accessing the Windows CE desktop on this device. I'm going to keep trying of course. Any suggestions for getting further toward getting any kind of unlock would be greatly appreciated

i used the update for the uk model to give me a boot option to load to windows ce instead of the nav software. i'm currently running navon (igo 8.3.5) for gps and it's working great! i'm currently trying to get bluetooth to work as it used to. sorry for such a vague post but if any of you are still tinkering with the blackbird please contact me! would love to share notes!

Alpine PMD-200B attached to Alpine IVA-D106R
Hi to the list
Hope posting in the right section.
I ownn an Alpine PMD-B200P iattached to an Alpine IVA-D106R and i would like
to update it either software and maps.
I have tried changing the IGO8o software with an early release but since i use the PMD
without the autoradio source ( as portable ), everything works great but as i attach it
to the source, the Navigator keeps working OK but i get no audio from the car
speakers, not even the Tick on the display.
Anybody can help me to solve the problem or it is possible to unlock it but does
still work also attached to the Autoradio?
Any help will be really appreciated.
Thanks in advance
Enzo.

unlock
Works 4 me i made the 2.0 upgrade it said upgarde not complete ERROR bla bla bla , i reset and voila i have my boot menu from where i can acces win ce and from there i instaled IGO primo, and i am using it since then, at start it gives the boot menu i select win ce and im good not so bad ooh my unit is Blackbird pmd-b200 (American old version! not the second one ! )

MarkoDaniel said:
Works 4 me i made the 2.0 upgrade it said upgarde not complete ERROR bla bla bla , i reset and voila i have my boot menu from where i can acces win ce and from there i instaled IGO primo, and i am using it since then, at start it gives the boot menu i select win ce and im good not so bad ooh my unit is Blackbird pmd-b200 (American old version! not the second one ! )
Click to expand...
Click to collapse
Please can you tell me how to do to have the boot menu from where you can acces win ce?
Thanks
Enzo

verry simple
ik8ozv said:
Please can you tell me how to do to have the boot menu from where you can acces win ce?
Hello Follow this steps ! download pmd-b200 last update , unzip to pc first !, copy to sd, insert sd, reset unit, hold sound down and power on simultan, let it do the upgrade ! it wil say at end error but dont bother reset and you done you get the boot menu from where you can acces wince ENJOY !
Click to expand...
Click to collapse

MarkoDaniel said:
ik8ozv said:
Please can you tell me how to do to have the boot menu from where you can acces win ce?
Hello Follow this steps ! download pmd-b200 last update , unzip to pc first !, copy to sd, insert sd, reset unit, hold sound down and power on simultan, let it do the upgrade ! it wil say at end error but dont bother reset and you done you get the boot menu from where you can acces wince ENJOY !
Click to expand...
Click to collapse
I already have pmd-b200 last update.
Click to expand...
Click to collapse

MarkoDaniel said:
ik8ozv said:
Please can you tell me how to do to have the boot menu from where you can acces win ce?
Hello Follow this steps ! download pmd-b200 last update , unzip to pc first !, copy to sd, insert sd, reset unit, hold sound down and power on simultan, let it do the upgrade ! it wil say at end error but dont bother reset and you done you get the boot menu from where you can acces wince ENJOY !
Click to expand...
Click to collapse
Hello,
i cannot get it go.
What i have done is:
Downloaded from the Alpine site the file called FU_PMD-B200P_20_20091008.zip.
Unzipped it and got a folder called FU_PMD-B200P_20_20091008.
Opened the folder and got 3 folders and 3 files.
Copied them in the root of a 512MB SDCARD.
Inserted the SD CARD in the PMD.
Pressed the Reset Button.
While pressing the Music button ( the one on the right side ) i've pressed the power on button and keeped pressed both.,
but i do not get into the WINCE.
I have noticed that keeping pressed both the buttons, i can see on the display the word
Loading...
and after about 25 seconds i get the Alpine Logo and then the navigation program loading till the end.
Nothing happens.
Please am i missing any step?
Any help?
Thanks
Enzo.
Click to expand...
Click to collapse

MarkoDaniel said:
ik8ozv said:
Please can you tell me how to do to have the boot menu from where you can acces win ce?
Hello Follow this steps ! download pmd-b200 last update , unzip to pc first !, copy to sd, insert sd, reset unit, hold sound down and power on simultan, let it do the upgrade ! it wil say at end error but dont bother reset and you done you get the boot menu from where you can acces wince ENJOY !
Click to expand...
Click to collapse
Please does anybody use the PMD-B200P attached to a Source.
I am using it with an autoradio Alpine IVA D-106R but after have tried or to update the Igo8 or to update
a map as i attach it to the sorce i get the voice disappearing.
If anyboody ha success can please help me to do so?
Any help will be really appreciated.
Enzo
Click to expand...
Click to collapse

1moretime
you have to : RESET !
Push POWER and Volume down !
IT goes in update mode !
if you have the update memory card it must be in the UNIT !
then when it finish the update 100% you reset !
when unit restartes it shuld try to update the bluetoth and the navi software but it shuld say CheckSum file error !
Reset !
and it goes in BOOT MENU ! from vhere you choose WinCE
---------- Post added at 09:24 AM ---------- Previous post was at 09:16 AM ----------
i use my PMD-B200 with a IVA-B200 , it works great and i can acces IGO , WinCE, Bluetoth, So i can use my IVA-W205 screen with the WinCE like a TABLET BUTT ! my problem the PMD-B200 Memory its 1 root 32 MB and the other root 64MB how can i acces the 4 GB memory ? if i run BLUETOTH and IGO at once it says not enough memory !!!
HOW CAN I ACCES THE 4GB memory ? PLEASE HEALP !

MarkoDaniel said:
you have to : RESET !
Push POWER and Volume down !
IT goes in update mode !
if you have the update memory card it must be in the UNIT !
then when it finish the update 100% you reset !
when unit restartes it shuld try to update the bluetoth and the navi software but it shuld say CheckSum file error !
Reset !
and it goes in BOOT MENU ! from vhere you choose WinCE
---------- Post added at 09:24 AM ---------- Previous post was at 09:16 AM ----------
i use my PMD-B200 with a IVA-B200 , it works great and i can acces IGO , WinCE, Bluetoth, So i can use my IVA-W205 screen with the WinCE like a TABLET BUTT ! my problem the PMD-B200 Memory its 1 root 32 MB and the other root 64MB how can i acces the 4 GB memory ? if i run BLUETOTH and IGO at once it says not enough memory !!!
HOW CAN I ACCES THE 4GB memory ? PLEASE HEALP !
Click to expand...
Click to collapse
Please how did you had success to let it workattached to a Source.
I am using it with an autoradio Alpine IVA D-106R but after have tried, or to update the Igo8 or to update
a map as i attach it to the sorce i get the voice disappearing.
Please can you help me to do so?
Any help will be really appreciated.
thanks in advace
Enzo

do what i adviced u
i gave u all vhat i did and worked for me try it ! 1 more time i can not acces the 4 gb memory SOMEONE ? noone tryes to get to the bottom of this **** ?
---------- Post added at 04:44 PM ---------- Previous post was at 04:30 PM ----------
Did u managed to find a way to get the machine runing ? im sttuck in the same situation eny healp is welcomed thank you

MarkoDaniel said:
i gave u all vhat i did and worked for me try it ! 1 more time i can not acces the 4 gb memory SOMEONE ? noone tryes to get to the bottom of this **** ?
Does it work also when you attach it to the source?
Iget it muted when i attach it to the source.
Are you trying whit an updated Igo8 or just the original?
Finally if you are using an update Igo8 can you pass me the files?
Thanks
Enzo
Click to expand...
Click to collapse

ik8ozv said:
MarkoDaniel said:
i gave u all vhat i did and worked for me try it ! 1 more time i can not acces the 4 gb memory SOMEONE ? noone tryes to get to the bottom of this **** ?
Does it work also when you attach it to the source?
Iget it muted when i attach it to the source.
Are you trying whit an updated Igo8 or just the original?
Finally if you are using an update Igo8 can you pass me the files?
Thanks
Enzo
Click to expand...
Click to collapse
Enzo, I have a 1 version of this thing, had it for several years and it still works attached to my radio in the car.
I am also willing to give away the audio for a better navigation, but today is the first time I ever find out anything about this device.
Where did you get Igo8, did you use the procedure described in the first 3d?
I have actually 2 blackbirds 1, 1 works in the car, the other one is stuck on update because I had a cd with no code, and was thinking on cracking the one that is "blocked" and keep 2 units in the car.
This is really interesting!!!
Click to expand...
Click to collapse

freddy2081 said:
ik8ozv said:
Enzo, I have a 1 version of this thing, had it for several years and it still works attached to my radio in the car.
I am also willing to give away the audio for a better navigation, but today is the first time I ever find out anything about this device.
Where did you get Igo8, did you use the procedure described in the first 3d?
I have actually 2 blackbirds 1, 1 works in the car, the other one is stuck on update because I had a cd with no code, and was thinking on cracking the one that is "blocked" and keep 2 units in the car.
This is really interesting!!!
Click to expand...
Click to collapse
I use the PMD-B200 v.2.0 that i do not know if it is the same as the ones you used.
I got the Igo8 from the web and followed the procedure in the first 3rd.
I repeat whichever Igo8 i put in thePMD it works perfectly but since i attach it to the,
the audio goes off.
Plese can you send me maybe in PM the igo that you use?
Thanks
Enzo
Click to expand...
Click to collapse

ik8ozv said:
freddy2081 said:
I use the PMD-B200 v.2.0 that i do not know if it is the same as the ones you used.
I got the Igo8 from the web and followed the procedure in the first 3rd.
I repeat whichever Igo8 i put in thePMD it works perfectly but since i attach it to the,
the audio goes off.
Plese can you send me maybe in PM the igo that you use?
Thanks
Enzo
Click to expand...
Click to collapse
I didn't do anything to mine, it's a PMD-B100, not even a 200, and as of now is still "stock"
I have to try to play around with the one that is stuck on the update screen and see if I can make anything work on it.
Click to expand...
Click to collapse

Guide how to unlock bricked MCU units

I am not responsible for anything that may happen to your unit by flashing the recovery image.
You do it at your own risk and take the responsibility upon yourself.
Edit 20.05.2018
Updated mtcdmcutool to preapre FULL recovery image (Now after flash recovery image is possible to future update to newer/other version using the standard dmcu.img upload procedure :victory
Before you start you must know what is MCU and what is bricked MCU (this is not the same what bricked SOM: "my Android do not want boot", "my unit stucked at bootlogo" ...)
What you need:
STM32 ST-LINK utility => http://www.st.com/en/development-tools/stsw-link004.html
ST-LINK/V2 programmer, for example => https://i.ebayimg.com/images/g/TE0AAOSwAYtWGQqG/s-l500.jpg
tool to prepare recovery image => https://www.sendspace.com/file/u0vl8w
Steps:
install ST-LINK utility on your PC
find pins on your board: SYS_SWCLK,SYS_SWDIO,+3.3V,GND. Some boards has special pinpads for that:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
connect appropriate wires to ST-LINK/V2 programmer and board
prepare recovery.bin using tool:
Code:
mtcdmcutool.exe -r dmcu.img recovery.bin
in ST-LINK utility connect to MCU. Should be identified as: STM32F091xB-xC
erase MCU (Target->erase chip)
program/flash file recovery.bin [Start address = 0x08000000]
There is another method to flash MCU.
Instead of ST-LINK/V2 programmer, it is possible to use TTL USBtoUART converter. But it requires a little bit more hardware modification. Maybe @Kayhan 17# will write some guide how to prepare and flash MCU. He did it already here
RemmeberThis is not FULL MCU firmware image. So you will not be able to change the MCU firmware to newer/other version using the standard dmcu.img upload procedure. If you want a newer version you must repeat flash MCU according to steps above

Hello!
This will work for a PX5? My head unit won't turn on, just turn on the leds in the unit 3 times and nothing else. The seller is Witson (MX) and I never got into the recovery in this unit. I tried all the procedure that I read but none of them worked to get into recovery (except the one that requiere some hardware modifications).
Thank you!

paniqueado said:
Hello!
This will work for a PX5? My head unit won't turn on, just turn on the leds in the unit 3 times and nothing else. The seller is Witson (MX) and I never got into the recovery in this unit. I tried all the procedure that I read but none of them worked to get into recovery (except the one that requiere some hardware modifications).
Thank you!
Click to expand...
Click to collapse
No, sounds like your SOM or mainboard is faulty. I'd be happy to look at your unit, with return freight.

marchnz said:
No, sounds like your SOM or mainboard is faulty. I'd be happy to look at your unit, with return freight.
Click to expand...
Click to collapse
That explains everything, hahaha. The unit came with a PX3, I installed Malaysk and it was working for a week, after I rebooted it one day it never turn on again. The seller sent me another PX3 board as warranty and it worked for 3 months, then it stop working suddenly one day when I turned on the car.
So then I bought a PX5 board, it worked for 6 months. One day I was driving using only Play Music app and the stereo froze, I turned off the car but the unit did not work again, so I removed it I re installed the original unit. Then after 4 months later I tried to fix it using a PSU but in the moment that I turned it on, the headunit boot and worked normally, I was happy and reinstalled it into my car, but it just worked for a few days. It stopped working when I turned on the car and it was on reverse gear, when I change to first gear the screen flashed and that's it (switch between camera and the main screen).
Sorry for the long story.
Where are you? To see how much is to send it. I can send it from the US.
Thank you!

paniqueado said:
That explains everything, hahaha. The unit came with a PX3, I installed Malaysk and it was working for a week, after I rebooted it one day it never turn on again. The seller sent me another PX3 board as warranty and it worked for 3 months, then it stop working suddenly one day when I turned on the car.
So then I bought a PX5 board, it worked for 6 months. One day I was driving using only Play Music app and the stereo froze, I turned off the car but the unit did not work again, so I removed it I re installed the original unit. Then after 4 months later I tried to fix it using a PSU but in the moment that I turned it on, the headunit boot and worked normally, I was happy and reinstalled it into my car, but it just worked for a few days. It stopped working when I turned on the car and it was on reverse gear, when I change to first gear the screen flashed and that's it (switch between camera and the main screen).
Sorry for the long story.
Where are you? To see how much is to send it. I can send it from the US.
Thank you!
Click to expand...
Click to collapse
New Zealand. It sounds like it has a bad connection, or dry solder joint.

paniqueado said:
Hello!
This will work for a PX5? My head unit won't turn on, just turn on the leds in the unit 3 times and nothing else. The seller is Witson (MX) and I never got into the recovery in this unit. I tried all the procedure that I read but none of them worked to get into recovery (except the one that requiere some hardware modifications).
Click to expand...
Click to collapse
It seems that MCU is working beacuse MCU is responsible for the blinking of leds. Just like @marchnz wrote, problem may be with wire connections. At the beginning check what the state of ACC, then ACC-DET is.

@Wadzio. I was amazed to find this thread, hopefully can fix my PX5, the order of pins in my image is correct?

sibeng said:
@Wadzio. I was amazed to find this thread, hopefully can fix my PX5, the order of pins in my image is correct?
Click to expand...
Click to collapse
Yes, those that pads but you wrong mark signlas. Look at the schematic:
For me should be:
But the surest solution is to check the connection between the pads and CPU pins (according to the scheme of course)

Wadzio said:
Yes, those that pins but you wrong mark signlas. Look at the schematic:
Click to expand...
Click to collapse
yes, wrong mark
Thank you, i'll try later
---------- Post added at 09:36 PM ---------- Previous post was at 09:11 PM ----------
One more question, when the process will be run, the main power supply HU must be connected or not.
or just the + 3.3V power source from the ST-Link USB pin

sibeng said:
yes, wrong mark
Thank you, i'll try later
---------- Post added at 09:36 PM ---------- Previous post was at 09:11 PM ----------
One more question, when the process will be run, the main power supply HU must be connected or not.
or just the + 3.3V power source from the ST-Link USB pin
Click to expand...
Click to collapse
To be sure to turn it off.
+3.3V from ST-LINK for flashing is enough

Wadzio said:
To be sure to turn it off.
+3.3V from ST-LINK for flashing is enough
Click to expand...
Click to collapse
Ok, i noted

First attempt, can't read memory? any suggestion

in some documents mention, The only way to disable the Read Protection is with the Load Flash Demonstrator Software from ST. After to disable the read Protection the FLASH memory is erased (mass erased).
So @kayhan 17 solution with USB Uart maybe working, or somehow
https://forum.xda-developers.com/an...ide-to-recover-dead-mtcd-device-uart-t3750224

sibeng said:
First attempt, can't read memory? any suggestion
Click to expand...
Click to collapse
The memory can not be read because all MCUs have "Read protection" enabled by the manufacturer
First try erase MCU (menu Target->erase chip)

can't perform erase chip, there is an error message when entering the erase chip menu
in another article said: unlock the flash by setting the read out protection to 0 using the ST-Link utility

ok after I update the ST-Link firmware, change the frequency to 1.8Mhz (do not know, useful or not), can successfully erase chip, but so will upload the .bin file, error again "no target connected", stuck at 0x080000B0.
On Log file: "System reset has not raised up after 2 seconds. Sys reset req"
I will not despair to try again

sibeng said:
ok after I update the ST-Link firmware, change the frequency to 1.8Mhz (do not know, useful or not), can successfully erase chip, but so will upload the .bin file, error again "no target connected", stuck at 0x080000B0.
On Log file: "System reset has not raised up after 2 seconds. Sys reset req"
I will not despair to try again
Click to expand...
Click to collapse
Strange. Which tool do you use? ST-LINK v2 similar to that: link ?
---------- Post edited at 15:41 PM ----------
Maybe this link/conversation will help you: link

Wadzio said:
Strange. Which tool do you use? ST-LINK v2 similar to that: link ?
Click to expand...
Click to collapse
yes, maybe i get the defective type, i will try with another st-link

@Wadzio, You are amazing, really great. Your help is successful.
ST Link clue is, connect the main power suply when connecting with PC, can not use power supply from USB.
and managed to write MCU.
restart and upadate the firmware image.
Thank you very much, without you I will be confused.
greetings from Indonesia :good::good::good::good::good:

Could anyone tell me How can I use mtcdtool.exe???
And how do I prepare recovery.bin????
Thanks in advance

Help recovering a "bricked" MTCE, PX6 (Xtrons) unit

Hi all,
first post in this section, so be nice I have a very recent build Xtrons TQ700L unit that i have managed to soft(?) brick after rooting and removing a factory app ("Easy Connect"). On boot I get the initial logo, then after a long time a black screen that goes nowhere. I'm looking for advice on the best strategy to recover/rebuild it.
Hardware details...
build number:
rk3399-userdebug 10 QQ2A.200305.004.A1 eng.hct2.20200521.120545 test-keys
MCU version:
MTCE_GS_V3.53_3
As i understand it i have an "MTCE, GS" MCU and can ONLY flash MCU updates from the GS manufacturer. The MCU is probably not the problem here though.
I have a PX6, Android 10 build date of 20200521. Am I correct in saying i can flash any android 10 ROM designed for the PX6 that is newer than this date? Are the only differences between manufacturers cosmetic, like the nice launcher Xtrons supplies?
When i look on Yandex (https://yadi.sk/d/umCvHqCDzHccr), there is no PX6/Android 10 firmware at all from "GS", but there is from "HCT". Should i be looking at flashing the HCT/PX6/Android 10 firmware date 20200612 from the recovery menu? I can get to recovery easily enough by holding, then double clicking the reset button - i just dont know whether i should be flashing part of or the whole of the above package to fix my brick.
thanks.

So in case this helps anyone else, it was an easy fix. Baby steps below.
- grab the latest "Android 10", "PX6/RK3399" factory ROM either from threads here, or from Yandex. I found HA3_RK3399_10.0_ota(20200706).zip here on XDA.
- unzip the outer layer ZIP file and copy the inner "update.zip" to a micro SD card. The stock recovery systems dont allow any selection of ROM file names, so it must be update.zip.
- put the SD card in the "GPS" SD slot.
- with the unit on, reboot to recovery. My way was using a nail to hold the reset button in until the touch button lights began the flash, then quickly release and double click the reset again.
- in recovery, menu items can be scrolled through by either clicking the reset button, or (in my case) touching anywhere on the screen (easier).
- push and hold the rest button (or screen) to select the item.
- do a "wipe data/factory reset" (i guess) to be sure of cleaning out the old mess.
- then do "Apply update from SD card". it should automatically find the update.zip and apply it to all partitions.
- select reboot. Done.
The ROM i used was a "HA" branded generic ROM, so it didnt have the same launcher as my original "GS" (Xtrons) branded ROM. Xtrons wouldn't supply me with their stock ROM when i asked. The generic one was a little better anyway, since it has a stack of boot animations to choose from, whereas the Xtrons one only had the Xtrons logo. It also doesnt have the Easy Connect app, which is what I was trying to remove in the first place!
Additionally, i was able to obtain root easily by using the wifi ADB method here.

I did the same thing. Stupid app kept opening.
I don't have a micro sd card slot, hope it works with usb stick. Don't have one at the moment to try.
Same as yours.
Also, entering recovery mode you..
Hold reset button for 10 sec, release and immediately press it once.
I have a dicola px6 mtce
I'll update if i get it working.

Android tablet, how to disable kiosk mode or install new firmware

I am new to the android programming world. I own an iQR70 device from MLS that is using -if I read well- the kiosk mode for its own application called MAIC (something like Amazon's Alexa virtual assistant).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The real pain with this device is that the application is buggy does not get any updates and overall does not work properly.
So, my questions are, a) is there any way to disable the kiosk mode and work with it as a normal tablet? or desperately b) Can I install a compatible firmware? I don't care for the data inside.

You can check for update. Look for android version of tablet. You can check their site for any upgrade of software.
You can flash other firmware. Find compatible firmware as per your model.
You can disable apps same as you do on android mobile.

My tablet currently Is dead boot and I am trying to find the test points. Anyway, I have no access to the android os to disable apps. The virtual assistant is the only app I can use, all others are forbidden.

Hi sdancer,
I got the same device and it's stuck in bootloop as well, after I experimented a bit too much. Stock recovery ist not working (when I select it in the boot menu it just reboots again), I can only get into Fastboot mode, but the PC won't recognize the device at all, because I guess I don't have the necessary drivers, USB connection never worked.
Did you manage to get it back on? And does your PC recognize your device?

zeetotheuno said:
Hi sdancer,
I got the same device and it's stuck in bootloop as well, after I experimented a bit too much. Stock recovery ist not working (when I select it in the boot menu it just reboots again), I can only get into Fastboot mode, but the PC won't recognize the device at all, because I guess I don't have the necessary drivers, USB connection never worked.
Did you manage to get it back on? And does your PC recognize your device?
Click to expand...
Click to collapse
Can you send commands under fastboot from your pc; if the drivers are the problem then try to fix them. In my case I deleted the Preload partition so I can not even power up the device. The only solution in my case, is the hardware reset using kolo connection pin shorted with ground and immediately flash from a stock Rom or a previously saved backup. I didn't find time to try it yet.

sdancer said:
Can you send commands under fastboot from your pc; if the drivers are the problem then try to fix them. In my case I deleted the Preload partition so I can not even power up the device. The only solution in my case, is the hardware reset using kolo connection pin shorted with ground and immediately flash from a stock Rom or a previously saved backup. I didn't find time to try it yet.
Click to expand...
Click to collapse
No, I can't send any commands, unfortunately. I can't finx the drivers either, because I never had them. The MTK drivers I installed did never work. I could never connect it to the PC before, because it was never recognized. Did your PC recognize device at all? Or does it recognize the other one you have, which is working?
I opened MAIC and tried to find the test spot, but there is really NOTHING written on the spots (No GND, no Kcolo, just nothing at all). I tried connecting some of the spots, but it didn't work.
If you try it and find out, would you be so kind to share?
By the way, I was able to get into the developer options by chance. When you press the small sun (swipe down on the main screen, and tap on the small sun on the right side, where you set the display brightness, several times)
Usually a prompt will pop up and ask for a password (which I couldn't find anywhere, not even their support would tell me)
But I was lucky once and got into these settings when there was some kind of bug in one of the previous versions. But I couldn't flash anything onto it, because as I said, my computer wouldn't recognize the device.

zeetotheuno said:
No, I can't send any commands, unfortunately. I can't finx the drivers either, because I never had them. The MTK drivers I installed did never work. I could never connect it to the PC before, because it was never recognized. Did your PC recognize device at all? Or does it recognize the other one you have, which is working?
I opened MAIC and tried to find the test spot, but there is really NOTHING written on the spots (No GND, no Kcolo, just nothing at all). I tried connecting some of the spots, but it didn't work.
If you try it and find out, would you be so kind to share?
By the way, I was able to get into the developer options by chance. When you press the small sun (swipe down on the main screen, and tap on the small sun on the right side, where you set the display brightness, several times)
Usually a prompt will pop up and ask for a password (which I couldn't find anywhere, not even their support would tell me)
But I was lucky once and got into these settings when there was some kind of bug in one of the previous versions. But I couldn't flash anything onto it, because as I said, my computer wouldn't recognize the device.
Click to expand...
Click to collapse
Hi, the developer mode is very essential to use the adb (Android debug bridge) and finally disable the kiosk mode. Can you explain how to enable it, because I am not sure if understand well.
My device is dead boot, does not power up currently, but I have another one that works. Before that, yes it connected with my windows, that's how I flashed it and finally bricked it. I have the drivers and they works just fine. In you case you don't have dead boot device, cos you can power it on and use fast boot.
So you don't need hardware reset. Just fix the drivers, if you need them, I can send them to you.
PCB does not have any indication of kolo pin joint. I didn't find anything either, but I am gonna use the mediatek pinout diagram I found, and proceed with test & trial method.

sdancer said:
Hi, the developer mode is very essential to use the adb (Android debug bridge) and finally disable the kiosk mode. Can you explain how to enable it, because I am not sure if understand well.
Click to expand...
Click to collapse
Well, basically just try this, (for the one that still works):
- You just let it boot normally until you see the MAIC woman on the main screen.
- Swipe down from the top of the screen, so you can get to this menu, you know, where you can access "Home", "Music", "Video Call" etc.
- You will see the brightness adjustment bar with a big sun and a small sun. Tap the sun on the right side of the bar about 9 times
- Now you'll see a message pop up, which asks you for a password
And this is where I got stuck for a long time. And usually you can't get past this point I guess.
But one day, when they updated the software to V 4.01 I just could access the developer options and enable ADB and stuff. I have no idea how that worked, it must have been a bug within the version. After another update of the MAIC software (V 4.02), I couldn't access it anymore either.
Maybe you're lucky and you'll be able to get into it too, if you didn't install the latest update yet.
What I did was, I installed a launcher (I was able to use the devices browser and access the apk) and then I could switch between Kiosk mode and the "normal" android display. If you could manage to install any launcher (I used Evie Launcher and it worked great) you can use it like a tablet (it's slow as hell, though).
sdancer said:
My device is dead boot, does not power up currently, but I have another one that works. Before that, yes it connected with my windows, that's how I flashed it and finally bricked it. I have the drivers and they works just fine. In you case you don't have dead boot device, cos you can power it on and use fast boot.
So you don't need hardware reset. Just fix the drivers, if you need them, I can send them to you.
Click to expand...
Click to collapse
That would be soooo great, if you could share the drivers! It would help me a lot. Because like you, I would try flashing a stock ROM, too, and maybe we'll find a way to enable ADB with a modified ROM.
sdancer said:
PCB does not have any indication of kolo pin joint. I didn't find anything either, but I am gonna use the mediatek pinout diagram I found, and proceed with test & trial method.
Click to expand...
Click to collapse
Well, let me know, if you find something! I gave up already, because I really didn't find the right spots. On the small PCB on the left, if you unscrew it and turn it around, there are several more gold points, btw. Maybe you'll find something there. And on the small board (where the Buttons for Power, Volume + and Volume - are located) there are some golden points too.

zeetotheuno said:
Well, basically just try this, (for the one that still works):
- You just let it boot normally until you see the MAIC woman on the main screen.
- Swipe down from the top of the screen, so you can get to this menu, you know, where you can access "Home", "Music", "Video Call" etc.
- You will see the brightness adjustment bar with a big sun and a small sun. Tap the sun on the right side of the bar about 9 times
- Now you'll see a message pop up, which asks you for a password
And this is where I got stuck for a long time. And usually you can't get past this point I guess.
But one day, when they updated the software to V 4.01 I just could access the developer options and enable ADB and stuff. I have no idea how that worked, it must have been a bug within the version. After another update of the MAIC software (V 4.02), I couldn't access it anymore either.
Maybe you're lucky and you'll be able to get into it too, if you didn't install the latest update yet.
What I did was, I installed a launcher (I was able to use the devices browser and access the apk) and then I could switch between Kiosk mode and the "normal" android display. If you could manage to install any launcher (I used Evie Launcher and it worked great) you can use it like a tablet (it's slow as hell, though).
That would be soooo great, if you could share the drivers! It would help me a lot. Because like you, I would try flashing a stock ROM, too, and maybe we'll find a way to enable ADB with a modified ROM.
Well, let me know, if you find something! I gave up already, because I really didn't find the right spots. On the small PCB on the left, if you unscrew it and turn it around, there are several more gold points, btw. Maybe you'll find something there. And on the small board (where the Buttons for Power, Volume + and Volume - are located) there are some golden points too.
Click to expand...
Click to collapse
No problem at all, I will attach them (drivers) on Monday when I return back to my office. I will attach you also screenshots from my device manager to know how windows recognize them.
This is all you need in your case, don't bother with the hardware reset.

sdancer said:
No problem at all, I will attach them (drivers) on Monday when I return back to my office. I will attach you also screenshots from my device manager to know how windows recognize them.
This is all you need in your case, don't bother with the hardware reset.
Click to expand...
Click to collapse
That's awesome! Thank you in advance.
Yeah, I guess the hardware reset really takes some time and a lot of trial and error.
But if you manage to do it, let me know, I'm just curious in general, if that's possible with this device.

To Flash your device,
1) Install the drivers
2) Press Download from SP Flash Tool
2) Connect USB
3) Connect the power outlet from your device (in this case) or connect the battery
****WARNING: DONT FORMAT THE PRELOAD or you will get a DEAD BOOT device, use ONLY DOWNLOAD and not download+format
AutoInstall
=================
MediaTek_Preloader_USB_VCOM_drivers.exe
File on MEGA
mega.nz
Manual Install
=================
MediaTek_Preloader_USB_VCOM_Drivers_Setup_Signed.zip
File on MEGA
mega.nz
MediaTek_Preloader_USB_VCOM_Drivers.zip
File on MEGA
mega.nz

Hey @sdancer, thank you for the drivers. But I must do something wrong, because it's still not detected. It's not showing in my device manager and nothing happens in SP Flashtool.
I tried the automatic install and the manual install, but still nothing :/
Could you maybe explain how exactly you installed them? Maybe I'm making a mistake there.

1) Check the USB cable and make sure it works fine for data transfers (some cables are only for charging and does not contain the data wires inside)
2) Download the drivers https://mega.nz/file/ePITwCbA#DvF-SAOA8_nI0vFReV_fR1JuDJa_1us_SDnQKUstoZ4
3) Follow the instructions I recorded for you at

sdancer said:
1) Check the USB cable and make sure it works fine for data transfers (some cables are only for charging and does not contain the data wires inside)
2) Download the drivers https://mega.nz/file/ePITwCbA#DvF-SAOA8_nI0vFReV_fR1JuDJa_1us_SDnQKUstoZ4
3) Follow the instructions I recorded for you at
Click to expand...
Click to collapse
Hi again, sorry it took a while to reply. So, I tried, and it does find the device now, but only as "Unknown device" and not as "Android Device". I tried several drivers but it won't connect, when I try SP Flashtool.
Really tough thing, this MAIC, haha.

zeetotheuno said:
Hi again, sorry it took a while to reply. So, I tried, and it does find the device now, but only as "Unknown device" and not as "Android Device". I tried several drivers but it won't connect, when I try SP Flashtool.
Really tough thing, this MAIC, haha.
Click to expand...
Click to collapse
Hi
I suppose that this is a driver's problem, you should try to fix it someway.

Hello good people! I did a factory reset because this device was not working good and it was really buggy, I did this before when i had problem with the device, but now I'm stuck at location selection and can't pass it! Please take a look at my pictures, to clear the situation.
I'm seeking for help for months now, so, if anyone can help me, I will be really grateful
Thank you, Marko

Marko121212 said:
Hello good people! I did a factory reset because this device was not working good and it was really buggy, I did this before when i had problem with the device, but now I'm stuck at location selection and can't pass it! Please take a look at my pictures, to clear the situation.
I'm seeking for help for months now, so, if anyone can help me, I will be really grateful
Thank you, Marko
Click to expand...
Click to collapse
Any idea, Any fix?

paulos2951 said:
Any idea, Any fix?
Click to expand...
Click to collapse
I have no idea bro :/ Hoping that someone will help me

Marko121212 said:
Hello good people! I did a factory reset because this device was not working good and it was really buggy, I did this before when i had problem with the device, but now I'm stuck at location selection and can't pass it! Please take a look at my pictures, to clear the situation.
I'm seeking for help for months now, so, if anyone can help me, I will be really grateful
Thank you, Marko
Click to expand...
Click to collapse
I have the same problem with you
If you find a solution please send me a message !

Jim-Kyritsis said:
I have the same problem with you
If you find a solution please send me a message !
Click to expand...
Click to collapse
Hi friend! Are you Greek? Is there a way to contact MLS in Greece?