Related
I am a long time user of this website, and recently switched from my Touch Pro 2 to my Samsung Captivate. I did put on the Froyo 2.2 leak and it's been alright for the past month. Well tonight I wanted to take a look at Cogintion hoping for a bit more speed without the AT&T bloatware.
I have to say at this point getting Froyo 2.2 on was a pain. It did not work one click. but that's in the past.
So I downloaded the Odin3 from:
http://forum.xda-developers.com/showthread.php?t=731989
I let it stay on file analysis for over an hour. When I figured it was stuck, I pulled the power and rebooted to get to the "phone+!+computer" screen. After some more research I was able to get into download mode, and Odin does see the phone but never moves past File Analysis. I tried the Master Clear and it just says Master Clear started.
I found another thread that mentioned that the phones with a build date prior to 1010 did not always play nice with odin, so I tried the procedure in this thread: http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36
Of course my phone is 1011 and I have not been able to find any info related to my build. At this point nothing is working to recover my phone. Can anyone help?
UPDATE: Good news.. I pulled out an old laptop with windows XP and tried the ODIN3 update again. This time it was sucessfull. I tried this on four different windows 7 machines and could not perform this update. I had full administrative rights, and no antivirus enabled.. So FYI for anyone having issues.
Good to know, Thanks.
Windows 7
Works for me Windows 7 Pro x64
Have Windows 7 Pro x64 on this laptop and two other desktops. No Problems
I agree, I have done my friends older phone from various windows 7 phones with no problem. This one was just stubborn. I can tell you I tried at least 20 times to get ODIN to download the files... It would just never move past the first step. I have since this post tried again from Win7 and no go. Works perfect from the any of the three winxp machines I have tried. May have something to do with my build date? Just guessing.
Sent from my HTC Wildfire using XDA App-put out a post about half hour ago but I never stated my problems...got sim free,unlocked sgs I bricked it I could only d/load via jig,so I flashed it using odin but I must've done it wrong as I got no network connection, incoming + outgoing wasn't viable,I tried flashing it again (infinity),then it bricked again,as of now my galaxy is "dead",if any 1 can help me it would b appreciated,I do not have much knowledge apart from basics so please don't be smart as I am only asking for help here,oh I have to use a jig as I can't get 3 button mode,also I formatted my internal + external memory (8gb + 16gb)....that was the last advice I got + think this Is where my problem started from?thank you....
pmb6177 said:
Sent from my HTC Wildfire using XDA App-put out a post about half hour ago but I never stated my problems...got sim free,unlocked sgs I bricked it I could only d/load via jig,so I flashed it using odin but I must've done it wrong as I got no network connection, incoming + outgoing wasn't viable,I tried flashing it again (infinity),then it bricked again,as of now my galaxy is "dead",if any 1 can help me it would b appreciated,I do not have much knowledge apart from basics so please don't be smart as I am only asking for help here,oh I have to use a jig as I can't get 3 button mode,also I formatted my internal + external memory (8gb + 16gb)....that was the last advice I got + think this Is where my problem started from?thank you....
Click to expand...
Click to collapse
OK so if you can get into download? If you can then its a matter of getting Odin to see the phone - which really means getting windows to recognize the phone. This would mean that odin does not light up in one of the com ports.
If this assumption is right, make you have the latest drivers (see other posts - I had a link in another post so if you look for my posts you'll find it), reinstall kies (but do not have it open), clean the usb port/cable on the phone and computer with alcohol just to be sure (that was my old issue and it takes forever to troubleshoot), then put into download with jig (I assume you start with a battery pull?). If you've done the kies/drivers thing (good chance if your asking on this forum - just try the cleaning).
You can also try various different usb ports - the theory is the one at the back of a desktop work best but my laptop ones seem fine (now - see cleaning above).
I know this is not that step by step it sounds like your trouble is the connection not the steps as you have already attepted the flash.
If still not working , try to vary the connect order (odin first, then connect or reverse etc).
From there follow a good odin guide and flash a full stock firmware to start (presumably your official one).
I believe you are only truly dead when you cannot get to download mode.
Good luck!
Thank you for taking the time to send that post ; one last thing ... any thoughts on getting my sgs to "day 1" , like before all the trouble I was stock eclair 2.1,Vodafone,blah,blah ; how do I get back after formatting both my internal + external , I'm presuming I've erased my stock FW?
Sent from my HTC Wildfire using XDA App
I think you also got similar advice to mine on another post. Don't worry about going to day 1 with eclair. If you flash a stock froyo firmware with odin you'll have a phone like it came out yesterday. Now, it will also likely be unrooted and maybe locked (I'm not unlocked so I'm not sure about that part).
So once you get to the stock firmware you'll need to root again and maybe unlock (stock is stock after all). You may want to just try Darky's resurection rom (for Odin use)
, link here, which should make your phone faster and keep you rooted and unlocked.
If you don't care about root etc, then I think stock is fine as long as it doesn't lock the phone to another provider (use the search function in the forums). One warning is once you know how to change things (and recover) you might spend hours trying to play with the custom roms just because you can .
Good luck in the AM
hi ive searched for a few hours and tried so many different sequences her eon the forums and for some reason i cant get odin3 1.78 to recognize my captivate... otherwise i would have an awesome Cyanogenmod 7 on it.
i rooted it and installed clockwork from the thread "how to install roms" under the dev threads (the big sticky) then attempted to install a custom rom through clockwork and it failed. now my original rom is messed up. i can load into it but android.phone continuously closes...i cant get odin to see my phone thus i cant reflash the original firmware....
yes i have drivers installed.
yes i have the AIO toolbox.
now for some reason i cannot get Odin to recognize my phone AT ALL (download/recovery/loaded). ive literally tried everything i can think of and to be honest i hope someone here can make me look stupid and help me fix it . ive flashed roms before back in the day with my tilt and cliq. but ive been out of the game for a very long time and lemme tell you im completely lost feeling.
im on windows 7 ultimate x86 fully updated.
ill be glad to donate a little bit for some success on just getting odin to recognize because i have everything. its just that stopping me..
in the meantime my phone is just useless
It might be problems with usb port. Try different ports and/or a totally different computer. Make sure you have drivers according to your computer (32-bit /64). I don't really know why it isn't working.
im sure if he got cwm copied to the phone the USB works...
i have never heard of odin3 1.78
only 1.0 1.3 1.5 1.7 1.81 and 1.82
and some odins only work with some phones..
did this odin ever work for you? or never?
try this one...
no i used my laptop MicroSD then transfered into my root folder of my phone.
ive tried it on 4 computers in my house so far all windows 7 32 bit.
installed the drivers from the AIO and even KIE after seeing no results. ive tried different ports as well and thats the exact odin im using ;(
i also attempted XP compatability mode seeing on another thread windows XP worked for another user in a somewhat situation so im debating whether or not to dual boot XP just to fix my phone lol
so your computer doesnt even see it when you mount usb to copy files? not just odin? did it ever work?
i run windows 7 64 bit no probs.
EDIT... i just re-read your first post....
ODIN ONLY sees the phone in download mode. ONLY
no it doesnt see it at all i think im goin to uninstall drivers and reboot.
now it makes the sound that windows found it but i cant access it or visually see it as a mass storage device even when i specify the settings (disabling debug/enabling mass storage) and under download mode it just doesnt see it at all.
i think im going to get organized and correclty reinstall anything i might think may be an issue
also installing xp on a virtual box on my linux machine to my right
virtual machines and odin dont mix well
with linux use heimdall instead of odin. but the machine still needs to see the device.
and try the drivers from samsung.
USE THE ORIGINAL SAMSUNG CABLE!!!!!!!
some cheap cables, like the one for my bluetooth headset are power only usb cables. the other 2 data pins dont connect end to end!!!!!!!!
ahh maybe thats the problem, i happened to pick up my captivate from someone on criraglist just yesterday and it was just phone and charger. how can i tell if i have an original or not? and yea i tried the drivers from samsung for the galaxy S as well. i was so irritated earlier lol i took a break and came back to it
if windows doesnt beep when pluggin in, then the cable is probably no good...
or try the cable with another phone/ usb hard drive / some data device that takes that input....? or go to radio hack and pick up a new cable. if that doesnt work return it to the hack for your$$ back.. if it does work its worth the 15-20$...
or maybe the phone has a dead usb port... that has happened to some people
okay i found a cord that gives me "usb device not recognized" when im loaded into my phone fully and select mass storage. this is after i installed the samsung driver exe 32 bit for my 32 bit windows 7.
looks like windows 7 attempts to install drivers for "mass storage device" and it fails.
my windows will fail on phone boot a few times because the phone cycles thru different modes.. adb and download mode work on different drivers...
remember to mount to see sd card on pc...
but at least you are getting something now... maybe now is the time to try other pcs..
just throwing out some ideas its getting late.... lol
lol yea thanks man ill reinstall android sdk and java se and see if i can get the adb to be seen and try different drivers for now. thanks for helping me ill donate to you in the end even if we cant get it but man my phone is wacked, all the services are force cosing on it. its so useless right now
ConnectionStatus: FailedEnumeration
Current Config Value: 0x00 -> Device Bus Speed: Low
Device Address: 0x00
Open Pipes: 0
*!*ERROR: No open pipes!
===>Device Descriptor<===
*!*ERROR: bLength of 0 incorrect, should be 18
bLength: 0x00
bDescriptorType: 0x00
bcdUSB: 0x0000
bDeviceClass: 0x00
*!*ERROR: Device enumeration failure
thats what im getting in every port on my laptop.
okay man i got it.. i rebooted my pc after uninstalling EVERYTHING (java sdk,eclipse, android sdk, AIO Captivate toolbox, all drivers known to man that dealt with the phone) then logged back in, i downloaded and loaded up UVCView.x86 and tried my phone on every single usb port on my laptop while disconnecting ANY other device thats including my mouse and for some reason my captivate only worked on 1 usb port that was on the side of my laptop (left side) and would only make a (ding dong) sound if my external was detached from my laptop (weird) but wouldnt install drivers still. reinstalled the set of drivers needed and installed AIO captivate toolbox, nothing happened. so i put my phone in download mode and i went into the Compatibility options for the AIO toolbox and set to run as windows xp SP3 + checkboxed run in 256 color, Disable visual themes, Disable desktop composition, Disable scaling on high DPI settings and run as Administrator Then doubled clicked/loaded it up. sure looked like utter crap but my phone was seen by windows and sure enough it had 2 drivers it installed. i went into flash to stock and COM 3 came right up i cried with happiness and i flashed faster than my eyes blink while on a cup of sugar. then i went ahead and tested the com 3 detectability under Odin (i set odin with the EXACT same compatibility mode settings as the AIO - i used odin by itself just for testing) and COM 3 was instantly seen. after flashing to stock and making sure eveyrthing was okay, i went ahead and installed the speedmod kernel and yet again windows 7 x86 recgonized the device and it installed about 7 different drivers! i should be okay from here im not totally noobed feeling now.
Thanks for stickin by my side for the information and support TRusselo ill donate to you for that.
PS : i think im going to research for a week or two on getting what i ned for my linux box in the near future lol
congrats!!!!
yep yep, got cyanogenmod 7 running great, sure is a battery killer though, seriously im afraid of leaving the house with this lmao. my next paycheck be sure to see a donate from dahrat
Hey XDA, it's been a while. I tried to flash stock JF6 on my cappy last night and things went to hell.
The phone now only starts up for a forced download mode (inserting battery while holding volume buttons). When attached to Odin3-One-Click, it can begin the reset but crashes to a solid grey/pink/red screen when installing factoryfs.rfs, and then refuses to start up again for a couple of minutes. The previous ROM was cognition 4, I believe, alongside the CogKernel. I'm working with Windows 7 x64, which I understand can cause problems, but I don't really have a choice here.
I've uninstalled and reinstalled the Samsung drivers from the official Odin3 thread, restarting between each step. I've tried changing USB ports. I've also tried to flash with Heimdall, but it only sees the device as "Gadget Serial" and can't work with it.
What do I try next? When the phone comes back to life I'll be trying Odin with compatibility mode, but I don't know what else to do. Please save me!
Are you flashing with or without bootloaders? If without, try flashing a stock rom with them.
Also, look in my signature for the "Captivate Connection Issues" thread. That has some additional things you might be able to try.
jmtheiss said:
Are you flashing with or without bootloaders? If without, try flashing a stock rom with them.
Also, look in my signature for the "Captivate Connection Issues" thread. That has some additional things you might be able to try.
Click to expand...
Click to collapse
I'm using the Odin3 from DG's page: http://forum.xda-developers.com/showthread.php?t=731989
I do not get to choose what installs, however, I have Odin3v1.85 Multi Downloader that allows me to select files. Could you link me to a ROM that I should use?
Try GB 2.3.5 i897ucKK4
Sent from my SAMSUNG-SGH-I897 using xda premium
4-2ndtwin said:
Try GB 2.3.5 i897ucKK4
Sent from my SAMSUNG-SGH-I897 using xda premium
Click to expand...
Click to collapse
Ok, my question then would be - Bootloaders or no bootloaders? (I'm assuming I should go with bootloaders unless told otherwise)
EDIT: Bigger problem - the phone is taking longer and longer to recover from crashes. Last time I only waited a matter of minutes before it could get back to download mode, this time I've waited 20 and it still hasn't fixed itself.
U may have some hardware issues then.
But if it gets going u will need the GB Bootloaders in order to run GB.
Sent from my SAMSUNG-SGH-I897 using xda premium
Damn, it's really unresponsive now. 50 minutes wasn't enough this time. I'm getting worried, I can't remember how many tries it took last night, and I really need my phone back. A failed flash during the transfer of factoryfs.rfs shouldn't hardbrick anything, should it?
Nope. That should not at all. Just a failure during the boot.bin and/or sbl.bin would cause a hard brick...or mismatched bootloaders between froyo and gb.
Which specific Odin3 one click did u use ?? Gotta link to it or the thread ??
BTW I haven't even tried GB yet. I'm still waiting for it to "cool down" from the last crash. I don't know why it's doing this now, since I had it in download mode an hour and a half ago and didn't crash it or anything.
4-2ndtwin said:
Which specific Odin3 one click did u use ?? Gotta link to it or the thread ??
Click to expand...
Click to collapse
The one specified in my second post: http://forum.xda-developers.com/showthread.php?t=731989
^
Ok thx. Just wanted to make sure it wasn't the Stock jf6 with the "3 button fix".
Well i hope it gets going for ya. Not sure what could be the problem.....do u have another battery to try out in the phone ?? -- Just tryin to think of what may have gone awry.
Sent from my SAMSUNG-SGH-I897 using xda premium
I don't think it's the battery, though just before I flashed I had a 0% battery level erroneously detected.
UPDATE: The device is starting again, but now it only shows up in windows as "unknown device" and windows reports that it's malfunctioning. I'm restarting now.
Sorry for the double post, I think this is relevant though.
Now that the phone powers on to the download screen, I can plug it in to the computer but now receive an "Unknown Device!" error. Honestly this is just ridiculous, especially since I had no trouble transferring some of the Odin files. I'm downloading Puppy Linux now to see if Heimdall will pull me out of this.
UPDATE: The first time I started Heimdall on Linux it was able to detect the phone, but failed after the LOKE handshake part. Now it no longer sees the phone. I'm beginning to think there's something wrong with the USB port, even though it worked fine for file transfers just 2 days ago.
UPDATE 2: Good news everyone! The same linux install on a different laptop was able to see the device, and Heimdall could get all the way to "rebooting device" using the cyanogenmod kernel. However, the CM package doesn't seem to include bootloaders, so I can't actually start up the phone after downloading. I just realized that 4-2 also linked to Heimdall compatible bootloaders, so I'll be trying those now.
Jergling said:
Sorry for the double post, I think this is relevant though.
Now that the phone powers on to the download screen, I can plug it in to the computer but now receive an "Unknown Device!" error. Honestly this is just ridiculous, especially since I had no trouble transferring some of the Odin files. I'm downloading Puppy Linux now to see if Heimdall will pull me out of this.
UPDATE: The first time I started Heimdall on Linux it was able to detect the phone, but failed after the LOKE handshake part. Now it no longer sees the phone. I'm beginning to think there's something wrong with the USB port, even though it worked fine for file transfers just 2 days ago.
UPDATE 2: Good news everyone! The same linux install on a different laptop was able to see the device, and Heimdall could get all the way to "rebooting device" using the cyanogenmod kernel. However, the CM package doesn't seem to include bootloaders, so I can't actually start up the phone after downloading. I just realized that 4-2 also linked to Heimdall compatible bootloaders, so I'll be trying those now.
Click to expand...
Click to collapse
UPDATE 3: It turned out the problem was with the first laptop's USB setup. Every port is attached to an internal replicator, which I believe was the problem. I hooked it up to an old Toshiba and the Heimdall version of UCKK4 installed flawlessly. Now I'm running CM9 and it's amazing. Thanks 4-2ndtwin!
Hey everybody,
I do own a X98 Air III (M5C5) and after long hours of reading on xda I am wondering if there is a single documented case of succesful installation of a dualbooting system on the M5C5 model. Most seem to fail at flashing Mireks ROM in the first place. The lack of clear, concise instructions looks to me as if there is no safe way of flashing this particular model right now. Does this sound right to you or is there something I overlooked?
Thanks a lot!
cubeikon said:
Hey everybody,
I do own a X98 Air III (M5C5) and after long hours of reading on xda I am wondering if there is a single documented case of succesful installation of a dualbooting system on the M5C5 model. Most seem to fail at flashing Mireks ROM in the first place. The lack of clear, concise instructions looks to me as if there is no safe way of flashing this particular model right now. Does this sound right to you or is there something I overlooked?
Thanks a lot!
Click to expand...
Click to collapse
I have successfully installed the dual boot v1.00 after a softbrick trying to install the 2.02 bios. I think the issue is that your tablet is not rooted, that is why you cant flash android. Look @ the ionioni tool to unbrick soft-bricked tabs on how to flash that dualboot bios. Keep reading you will get there
cubal1br3 said:
I have successfully installed the dual boot v1.00 after a softbrick trying to install the 2.02 bios. I think the issue is that your tablet is not rooted, that is why you cant flash android. Look @ the ionioni tool to unbrick soft-bricked tabs on how to flash that dualboot bios. Keep reading you will get there
Click to expand...
Click to collapse
Well, you flashed the BIOS and - as I was stating - first of all softbricked your device, due to lack of proper instructions. There is absolutely no comprehensible information on how to correctly flash or modify this model of the X98 Air III on these forums right now.
Also: did you simply install the 1.00 dualbooting BIOS or did you succesfully install both Andriod AND Windows at the same time? I guess flashing the BIOS can be achieved but again: theres no information on how to properly install Windows & Android on the M5C5. Anf if there's people like you out there who've done it, I don't understand why nobody bothered to document their process and share it with everyone..
Thanks!
cubeikon said:
Well, you flashed the BIOS and - as I was stating - first of all softbricked your device, due to lack of proper instructions. There is absolutely no comprehensible information on how to correctly flash or modify this model of the X98 Air III on these forums right now.
Also: did you simply install the 1.00 dualbooting BIOS or did you succesfully install both Andriod AND Windows at the same time? I guess flashing the BIOS can be achieved but again: theres no information on how to properly install Windows & Android on the M5C5. Anf if there's people like you out there who've done it, I don't understand why nobody bothered to document their process and share it with everyone..
Thanks!
Click to expand...
Click to collapse
Installing Windows and Android is the easy part, once you get the dual bios working. Look at this page (http://forum.xda-developers.com/x98-air/help/unbrick-bios-softbrick-withouth-eeprom-t3285054) to find the files and how to flash them. The only duil bios avaliable is that v1.00. When you successfully flashed that you can install android in dnx mode with partiotion tables with less than full partition size (I personally used the 3gb partiotion, you can find it in mirek190 roms) and than you just attach a otg hub with a bootable flash drive with windows 10 32 bit(never go for 64bit - you will brick), boot in bios by holding Esc on your keyboard (that you also have connected to the hub, as well as a mouse btw), than select the boot drive (you can find a tutorial @ Techtablets youtube page).
I have swapped between the v1.00 dual boot bios and the 2.05 android only bios a few times, and it works fine. Read all the posts in the page above to better understand how dual boot works.
Good luck!
cubal1br3 said:
Installing Windows and Android is the easy part, once you get the dual bios working. Look at this page (http://forum.xda-developers.com/x98-air/help/unbrick-bios-softbrick-withouth-eeprom-t3285054) to find the files and how to flash them. The only duil bios avaliable is that v1.00. When you successfully flashed that you can install android in dnx mode with partiotion tables with less than full partition size (I personally used the 3gb partiotion, you can find it in mirek190 roms) and than you just attach a otg hub with a bootable flash drive with windows 10 32 bit(never go for 64bit - you will brick), boot in bios by holding Esc on your keyboard (that you also have connected to the hub, as well as a mouse btw), than select the boot drive (you can find a tutorial @ Techtablets youtube page).
I have swapped between the v1.00 dual boot bios and the 2.05 android only bios a few times, and it works fine. Read all the posts in the page above to better understand how dual boot works.
Good luck!
Click to expand...
Click to collapse
Hi, thanks for detailing things a bit. :good: Is there any major disadvantage to using the dualbooting 1.00 BIOS as opposed to 2.5? Missing features? Other relates quirks with the 1.00 BIOS? I was wondering since you swapped back and forth with both versions.
Thanks!
cubeikon said:
Hi, thanks for detailing things a bit. :good: Is there any major disadvantage to using the dualbooting 1.00 BIOS as opposed to 2.5? Missing features? Other relates quirks with the 1.00 BIOS? I was wondering since you swapped back and forth with both versions.
Thanks!
Click to expand...
Click to collapse
Hi, there a few problems with the 1.00 dual boot bios and I think its because it wasn't meant to be used with the M5C5, our version of Air III is supposed to be Android only and we are basically hijacking the bios from c6j8, that works but its not perfect (at least for me). The main issues I have encountered is not really with any of the device capabilities - the cameras, wifi, hdmi and everything else works as good as it was intended but sometimes I run in to troubles when switching on the device. When I let the battery run out I will not be able to turn the devise on until it is charged up to 40% (that takes around 45 min) that can lead up to a few minor heart attacks the first couple of times you encounter that. The way I deal with that issue is by never letting the battery run lower than 20% so its not a problem for me but if you use your tablets in such a way that they run out of juice constantly I would suggest you just stick with the android only bios - the one you currently have or the 2.05 version (you might already have that on your device).
Now the advantages of dual boot are many - I believe Windows is a superior OS, in the way that it gives me a lot more productivity and multitasking capabilities that I personalty enjoy. For some reason the volume goes a lot louder on Windows than on any Android rom I have tried. I do believe we should get the most out of our devices and that's why I stick with dual boot for now. It is far form a perfect solution but everyone that reads this should evaluate the pros and cons - if you don't mind the stress of not being able to turn on your devise for 45 min or so you might enjoy the dual boot (or might be able to find a better dual boot bios).
As a conclusion experiences with Chinese tablets always vary from one to the other and it might be just my unit that is faulty (the boot up issue) so all you do is at your own risk, but if you keep on reading and trying out solutions you can get a lot of stuff working (just remember to breath)
cubal1br3 said:
Hi, there a few problems with the 1.00 dual boot bios and I think its because it wasn't meant to be used with the M5C5, our version of Air III is supposed to be Android only and we are basically hijacking the bios from c6j8, that works but its not perfect (at least for me). The main issues I have encountered is not really with any of the device capabilities - the cameras, wifi, hdmi and everything else works as good as it was intended but sometimes I run in to troubles when switching on the device. When I let the battery run out I will not be able to turn the devise on until it is charged up to 40% (that takes around 45 min) that can lead up to a few minor heart attacks the first couple of times you encounter that. The way I deal with that issue is by never letting the battery run lower than 20% so its not a problem for me but if you use your tablets in such a way that they run out of juice constantly I would suggest you just stick with the android only bios - the one you currently have or the 2.05 version (you might already have that on your device).
Now the advantages of dual boot are many - I believe Windows is a superior OS, in the way that it gives me a lot more productivity and multitasking capabilities that I personalty enjoy. For some reason the volume goes a lot louder on Windows than on any Android rom I have tried. I do believe we should get the most out of our devices and that's why I stick with dual boot for now. It is far form a perfect solution but everyone that reads this should evaluate the pros and cons - if you don't mind the stress of not being able to turn on your devise for 45 min or so you might enjoy the dual boot (or might be able to find a better dual boot bios).
As a conclusion experiences with Chinese tablets always vary from one to the other and it might be just my unit that is faulty (the boot up issue) so all you do is at your own risk, but if you keep on reading and trying out solutions you can get a lot of stuff working (just remember to breath)
Click to expand...
Click to collapse
Well that was very helpful. I might consider simply replacing stock android with mirek190 v7.0 at this point. It seems having Windows 10 available is not worth the hassle for me, when it comes to the bootup issues you described. Thanks for clearing things up significantly for me! :laugh:
Is there any proper dualboot bios other than v 1.00 for M5C5?
Hi folks,
I ordered a Air III a week ago and I haven't got my hands on it yet. But from what I found researching the forums is that there's a version of 2.05 bios that's been reported working with the Air III. Refering to the following 2 posts:
http://forum.xda-developers.com/x98...m-bios-x98-air-iii-32gb-t3310436#post65204355
Then I downloaded X98_Air_2_android_5.0_mirek190_v7.0-ultra-light, replaced /data/BIOS/2-05.bin with the one from the above mentioned link (https://mega.nz/#!dYxVTQrL!J9h-bk-hW...8TF6XXr-JwpgdU). Then I launched FLASH_tool_Teclast_x98_air_devices-v3.0, hit 4, then hit 2 and select 2.05. It updated the M5C5 to the most recent BIOS. You can tell because the tablet doesnt start up displaying chinese letters anymore but instead showing the latin letters TECLAST
If you want to keep your Windows installation I believe you have to change partition.tbl but not sure how this would work . I'm Android only now.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=65166671&postcount=87
DONE!
It's true the first boot logo is about BIOS. I made backup and flash it by mirek tool
Here you can find it: https://mega.nz/#!dYxVTQrL!J9h-bk-hW...8TF6XXr-JwpgdU
Just replace this file in \X98_Air_2_android_5.0_mirek190_v7.0\data\BIOS and run flash version 2.05
Click to expand...
Click to collapse
The only I'm not sure is if I have to (or can) flash Mirek rom using MFT BEFORE flashing the bios so it's pre-rooted.
Can anybody confirm this (@mrchrister ?) and also if you need the tablet to be rooted?
Thanks