Related
Well, here it is, a new rom since Asus last put out a rom update back in 2008.
Thanks to Makuu (especially), Lenny, AstainHellbring, the creators of the tools I used to make this rom, and anyone else that I failed to mention in name who gave me the knowledge to complete this rom.
Asus Mypal A6x6 WM6.1.4 version 1
Windows CE version 5.2.20757 (Build 20757.1.4.0)
This was tested on an Asus Mypal A626 (and works). It should work with the A686/A696, but the other models were not tested.
Updates
Office Mobile with the addition of a zip decompressor
Additions (due to OS update)
Task Manager
domain enrollment
support for Microsoft System Center Mobile Device Manager
Removals
none
I really just took the stock Asus rom from the latest OEM update and upgraded the os.
download: http://sharecash.org/download.php?file=135906
At this time, this will be the only download link. Mirrors will be created in the future (after I give permission).
Instructions
Before you do anything, make sure you have at least a 256mb SD card and a card reader (you can get one at a place like Radio Shack or Office Depot). You also need to install winrar (found at http://www.win-rar.com/index.php?id=943&dl=wrar390.exe). Your SD card must be formatted with the FAT16 file system.
To format your SD Card with the FAT16 file system
Step 1: To do this insert the SD Card into the reader and go to "My Computer".
Step 1a: BACKUP YOUR FILES before you start!!
Step 2: Right-click the drive letter of the SD Card reader (differs for each computer, probably either E:\ or F:\ or G:\) and click "Format".
Step 2a: Don't worry about any of the options except for file system, choose "FAT"
Step 3: Click "Start" and wait until it is done
Step 1: Get (OS) rom image
Step 2: Extract files to any folder on hard drive using Winrar
Step 3: Go to the folder where you extracted the files in the RAR archive
Step 4: Make sure that the filename is "CANNES_A_WM6.img"
Step 4a: if the img file it's not exactly "CANNES_A_WM6.img", rename it to that
Step 5: Format the SD card if you haven't already done so using the instructions above
Step 6: Copy the img file to the SD card, see step 6a
Step 6a: Make sure that the img file is the ONLY file on the SD card after formatting
Step 7: Take SD Card out of SD Card reader and put it in the a6x6
Step 8: Make sure that the a6x6 is plugged in via ac adapter before doing the next few steps
Step 9: activate SD Loader using the following instructions {
Step 9a: Hold down the power button and enter button (that's the button in the center of the d-pad)
Step 9b: Double tap the soft reset button while holding the other 2 buttons
Step 9c: After double tapping the soft reset button, keep the other 2 buttons held until a blue screen comes up that says something like Asus Cannes flashing utility
Step 9d: Wait until the process is finished (it's near the end when it says "writing private")
}
Step 10: At this point, your a6x6 should reboot on its own
Step 11: enjoy your updated rom
If you have any questions, feel free to just post or PM me.
Update: As I release new roms, if you have a support question, please give me the rom version so I know what rom you are working with. You can get the rom version from the filename of the rom pack.
Example: Asus_A626_WM614_1
A626 = device (most often it will be A626, will rarely be different), WM614 = os version, 1 = release #
I do plan on posting a kitchen so you can make your own roms in a few days. Any future releases will include a changelog and will (probably) be posted on different threads.
My work is free for everyone's use, but if you feel compelled to give a donation towards my work (I am a full-time college student working on this in what little spare time I have), my paypal e-mail is "[email protected]"
It doesn't work on A696.
Flashing ok but on reboot it stay on Blue Asus logo.
Have to downgrade with USBLoader.
Try formatting the sd card with http://www.sdcard.org/consumers/formatter/ (you want full erase, not quick erase), then try the formatting and flashing instructions again. It can't hurt to run scandisk on the sd card either (check both fix and repair).
I tryed what you said, no luck.
I succesfully installed 6.1 from Globalbus but it suffer from translation problems.
Back to 6.0.
Ready to test future versions as 6.1 is MUCH faster to launch apps.
Thanks for the update Steven.
I'll be flashing tonight after work. I have to dig around to find a smaller SD card. Can the img be converted to an nb0 file that I can flash over usb? I found a tool called img2nb0 that was used with the Dell Axims but it didn't seem to convert correctly... I get a 0 byte output file. It's a dotnet program so I'm going to try to decompile it tonight and see if I can understand it at all.
I'll post later tonight when I've gotten it flashed and tested.
I tryed, but no luck too . Getting to something you call Asus Cannes flashing utility. It detects FAT16 SD Card and asking for external power. After plugging external power simply rebooting device after detecting SD card with no errors very quickly.
yurius said:
I tryed, but no luck too . Getting to something you call Asus Cannes flashing utility. It detects FAT16 SD Card and asking for external power. After plugging external power simply rebooting device after detecting SD card with no errors very quickly.
Click to expand...
Click to collapse
Use the formatting program I posted a link to before and then try all the steps again.
I did modify the instructions to include the part about plugging it in the wall. I forgot that the asus tech support dude said you had to have it plugged into the wall before it will work.
bmasephol said:
Thanks for the update Steven.
I'll be flashing tonight after work. I have to dig around to find a smaller SD card. Can the img be converted to an nb0 file that I can flash over usb? I found a tool called img2nb0 that was used with the Dell Axims but it didn't seem to convert correctly... I get a 0 byte output file. It's a dotnet program so I'm going to try to decompile it tonight and see if I can understand it at all.
I'll post later tonight when I've gotten it flashed and tested.
Click to expand...
Click to collapse
Don't waste your time. Unlike the dell axim, the a6x6 actually uses the img file as the flashing format (no extracting anything from the img file needed).
darky_mtp said:
I tryed what you said, no luck.
I succesfully installed 6.1 from Globalbus but it suffer from translation problems.
Back to 6.0.
Ready to test future versions as 6.1 is MUCH faster to launch apps.
Click to expand...
Click to collapse
Who makes the sd card you are using and what is its size? SDHC cards will NOT work for this procedure, it must be a NORMAL SD card.
Also, the img file should be the ONLY file on the SD card after formatting.
Tryed to use USBLoader with this img file, get "CANNES_A_WM6.img is not a valid image file!" error. Next step was using SDFormatter with recomended settings (full erase, FAT16) - same thing with rebooting after detecting SD card (1GB Sandisk).
I was able to successfully flash my A626 tonight. Used a sandisk 1gb sd card. Formatted it with windows as FAT, did a full format not quick and copied just the img file. Rebooted the A626 using the instructions and it worked.
Played around a bit with WM, tested bluetooth and wifi. Installed my music program and it worked. Changed some settings around just to ensure that all worked.
Thanks for working on this Steven... let me know if there is anything specific you need tested. I'm going to leave it on the device. I use it everyday for a music player at work.
I might play around with the img2nb0 tool tomorrow after work just to see if I can get it to work.
bmasephol said:
I was able to successfully flash my A626 tonight. Used a sandisk 1gb sd card. Formatted it with windows as FAT, did a full format not quick and copied just the img file. Rebooted the A626 using the instructions and it worked.
Played around a bit with WM, tested bluetooth and wifi. Installed my music program and it worked. Changed some settings around just to ensure that all worked.
Thanks for working on this Steven... let me know if there is anything specific you need tested. I'm going to leave it on the device. I use it everyday for a music player at work.
I might play around with the img2nb0 tool tomorrow after work just to see if I can get it to work.
Click to expand...
Click to collapse
It's good to see that at least 1 person verifies that my instructions and rom work.
You won't get the img2nb0 file to work at all on the asus rom. The img2nb0 tool was designed with the structure of (only) the axim rom in mind. It will not work with a non-axim rom (I tried it when I started my research on a626 rom cooking).
bmasephol
Is it possible for you to create NB0 file from clean (just after reflash or after hard reset)flashed device? This will help to create alternate method of flashing Asus A6x6 with this ROM.
yurius said:
I tryed, but no luck too . Getting to something you call Asus Cannes flashing utility. It detects FAT16 SD Card and asking for external power. After plugging external power simply rebooting device after detecting SD card with no errors very quickly.
Click to expand...
Click to collapse
I had this effect too.
Several tries later it worked !
I used a 256MB card with only one file.
I think that if something was wrong with the card or file, the flash sequence could not say "all ok".
There's something my A696 don't like.
darky_mtp
I have sume suggestions about our problem. I think ,that problem is in AC adapter. I'm using some universal 5V 500mah adapter, that switch device into some data transfer mode (many usb devices charging only when connected to PC). So when I get Motorola AC adapter with MiniUSB I'll try to flash device from SD card.
yurius said:
darky_mtp
I have sume suggestions about our problem. I think ,that problem is in AC adapter. I'm using some universal 5V 500mah adapter, that switch device into some data transfer mode (many usb devices charging only when connected to PC). So when I get Motorola AC adapter with MiniUSB I'll try to flash device from SD card.
Click to expand...
Click to collapse
When I tested the rom, I used the standard ac adapter that came with the device. I would say that the only "supported" ac adapter with my roms is the one that asus gave you in the package.
My A626 enters SD flashing mode but then it reboots before flashing the new rom. I use Kingston 512 MB SD card, I tried doing full format on it both with Windows tool and SDFormatter. Flashing Globalbus 6.1 via USB works OK.
yurius said:
bmasephol
Is it possible for you to create NB0 file from clean (just after reflash or after hard reset)flashed device? This will help to create alternate method of flashing Asus A6x6 with this ROM.
Click to expand...
Click to collapse
I would be willing to do that but I would want Steven to "bless" that because it's his ROM and I don't want to create another distribution source without his approval.
As for the ROM it has been working all morning without issue.
Ok, there is a tool that I used to turn the the img into nb0 files. However, that tool splits it into 3 parts, (apparently bootloader, os, and storage). The bootloader and storage nb0 files should not be touched. As for the os nb0, I have no idea what effect flashing just the os nb0 (generated with the tool) part via usbloader would do. If you do try flashing just the os nb0 file via usbloader, you're on your own as far as support and recovery is concerned. Even if the usbloader thing worked, I have no idea what effect it would have on the bootloader and storage parts (the device could be scarred for life as far as it's concerned).
Hello everyone. I haven't flashed Android to NAND yet but I'd like to try it.
I am sure this question has been asked before but I did try the search and I couldn't find it. Sorry if this has already been asked.
So, for the Kaiser, if I flash Android to NAND (ie: Polymod's most recent) how do you flash back to Windows Mobile?
I'm concerned because USB does not connect properly when Android is running with HaRET ("unrecognized USB device" using XP SP3 couldn't make heads or tails of the drivers in the SDK but then I didn't try installing the whole environment)
So I guess my question is -- even with the device unrecognized, can you still flash it back? If so, how? Is it really simple and easy?
Please let me know and point me in the right direction! Thanks!
aikeru said:
Hello everyone. I haven't flashed Android to NAND yet but I'd like to try it.
I am sure this question has been asked before but I did try the search and I couldn't find it. Sorry if this has already been asked.
So, for the Kaiser, if I flash Android to NAND (ie: Polymod's most recent) how do you flash back to Windows Mobile?
I'm concerned because USB does not connect properly when Android is running with HaRET ("unrecognized USB device" using XP SP3 couldn't make heads or tails of the drivers in the SDK but then I didn't try installing the whole environment)
So I guess my question is -- even with the device unrecognized, can you still flash it back? If so, how? Is it really simple and easy?
Please let me know and point me in the right direction! Thanks!
Click to expand...
Click to collapse
I beleive you can always follow the process here.
Your boot loader should not change when flashing so not being able to use the USB while in Android is not going to prevent your returning back to a stock ROM. I have not tested this but I'm pretty sure that you can always get back to your boot loader screen and re-flash from that point. Can someone confirm that this is the appropriate solution?
deekjx said:
I beleive you can always follow the process here.
Your boot loader should not change when flashing so not being able to use the USB while in Android is not going to prevent your returning back to a stock ROM. I have not tested this but I'm pretty sure that you can always get back to your boot loader screen and re-flash from that point. Can someone confirm that this is the appropriate solution?
Click to expand...
Click to collapse
Did anyone try this solution?
Since the bootloader is still there all you do if not able to flash via async when in android is flash via bootloader
Moved to general as not ROM Dev.
Thanks for the information, guys!! I will have to try it out over this weekend and see how it goes...
I can confirm that flashing via bootloader works fine, also flashing from SD works as well, in fact I keep a 128MB sd with a WM kaisimg.nbh on it handy just in case I need to flash a good WM rom for some reason.
Is there an Android OS with everything working on the Kaiser?
Dukenukemx said:
Is there an Android OS with everything working on the Kaiser?
Click to expand...
Click to collapse
You can see in different post of android rom what works and what doesn't works.
actually, Bluetooth and camera never works for in android 2.x build and some other apps doesn't works
I've been running Android for a few weeks now from this thread:
http://forum.xda-developers.com/showthread.php?t=614382
I've found everything to work with the exception of Bluetooth, video camera (normal camera works fine), and the barcode scanner. Also, my battery life is cut in half, but I have an extended life battery so I get a day or two out of it.
I prefer this method as you can just boot Android at will and can soft reset to go back to WinMo.
Just to let everyone know I did flash WM back just fine since I have HardSPL 3.56 and used the stylus to press the reset + camera button at the same time to get to the tri-color screen.
From there I flashed from USB without any problems.
Thanks again for all the help!
I am having problems reverting back to WM after attempting to install android to NAND. Something happened where the only way I was able to get to the android installer would be if I had the KAISDIAG.nbh file on the SD card so it would get past the tri color hard spl screen . Well as a result, I can't get into boot loader. It shows that screen for a split second, then if I do camera + power and then reset. Then I have to pull the battery. Can someone help me? It seems like it will only go into the Android bootloader, which obviously won't allow it to install a WM rom. SD flashes are my only choice because the usb port is pretty messed up. Any help would be greatly appreciated. Thanks.
The procedure for flashing WM back using SD card is much the same as flashing the Nand bootloader for Android.
First get a WM rom, copy the RUU_Signed.nbh to SD card, rename it to KAISimg.nbh, pull the battery, replace, press power and hold camera button, this should start the flash process.
Note that the SD card must be formatted FAT32, or it will not find the KAISimg.nbh.
If you prefer to flash a stock rom you will usually have to extract the RUU_Signed.nbh from the installer, just open it in winrar.
the reset in android is not working correctly. The correct way to get into bootloader is to pull the battery, wait a few minutes, rpelace the battery, press power and then press and hold camera button, do not use reset.
zenity said:
The procedure for flashing WM back using SD card is much the same as flashing the Nand bootloader for Android.
First get a WM rom, copy the RUU_Signed.nbh to SD card, rename it to KAISimg.nbh, pull the battery, replace, press power and hold camera button, this should start the flash process.
Note that the SD card must be formatted FAT32, or it will not find the KAISimg.nbh.
If you prefer to flash a stock rom you will usually have to extract the RUU_Signed.nbh from the installer, just open it in winrar.
the reset in android is not working correctly. The correct way to get into bootloader is to pull the battery, wait a few minutes, rpelace the battery, press power and then press and hold camera button, do not use reset.
Click to expand...
Click to collapse
Thanks, but unfortunately this still did not work. Have any other suggestions? I think the only way will it even do anything is if I have the KAISDIAG.nbh file on the card. It recognizes that, but then goes straight to linux. IDK what else to do. Could you be a little more clear on the procedure for getting into the bootloader? Thanks.
Ok please follow these steps carefully.
1. Format the SD card, make sure you are formatting it as FAT32, not FAT.
2. Download a Winmo Rom from somewhere handy.
3. Extract the Rom to a handy folder, find the RUU_Signed.nbh file, rename that to KAISimg.nbh
4. Copy the KAISimg.nbh file to the SD card. You should only have one file on the SD card, no folders just the NBH file.
5. pull the battery from the phone, wait at least 5 minutes.
6. Replace the battery. Press Power button, and hold down camera button, until the tri color screen appears.
7. The screen should now change to a white one, and when it's checked the nbh it will ask you to press power key again. do that.
8. Now it should flash the rom, this should take a while, 5-10 minutes, once it's finished you should get a message of success.
9. Now pull the battery again, wait 5 minutes, replace the battery, and power on, you should now boot into Winmo.
Hopefully this should solve your problems, if not then let me know which setp failed and we can work on that stage.
Finally, don't panic, take it slow, it'll all work out
Thanks, but the problem starts at number 6. I am supposed to press the power button, release it, and hold the camera button till it gets to the white screen, right? It's still stuck at the splash screen. I tried holding both and that didn't work either. Anything else I can try? I hope i'm not screwed?
If I put the battery in, boot it up, then push the camera and insert the stylus into the reset hole, it gets to the tricolor screen, then for about 0.5sec it flashes the white screen with a message saying "No image File." I know for sure the .nbh file is there.
I have experienced this before, when I tried to use an SD card that was formatted FAT, when formatting you must make sure it is formatted FAT32, the bootloader cannot read FAT formatted SD cards, even if Winmo and Android can.
I format using a card reader, and in windows it is sometimes easy to overlook the file system type, most SD cards are usually formatted FAT when they are new, and you must change the formatting, or it will just format FAT again.
zenity said:
I have experienced this before, when I tried to use an SD card that was formatted FAT, when formatting you must make sure it is formatted FAT32, the bootloader cannot read FAT formatted SD cards, even if Winmo and Android can.
I format using a card reader, and in windows it is sometimes easy to overlook the file system type, most SD cards are usually formatted FAT when they are new, and you must change the formatting, or it will just format FAT again.
Click to expand...
Click to collapse
Unfortunately, as much as I wish it was, it is not the problem. I'm on a Mac, but booted windows 7 to be make sure it was formatted to FAT 32, which it was. Is there some way I can fix permissions? Every time it runs, I keep getting the error saying that it is in read only mode. I obviously need to get it into writing mode. I don't think the fix permissions option on the installer did anything either.
The eclair build still will not install on my phone. I changed to an earlier .nbh file and now don't need the KAISDIAG.nbh file to get out of the splash screen and into the installer. When I run the install command for NAND, it says it can't mount, "no such file exists", "failed to extract." Keep in mind I haven't even gotten Android installed to NAND, just the installer itself. I can't even go back to WinMo either. It also seems like a permissions error since I believe it said the SD card is read only, but when plugged into my computer I fixed that and now it is read-write, but not on the phone. Please help because I really want to either get this working, or get back to WinMo instead of have this useless phone I currently have. Thanks.
Is there a way to enter the command line from the installer screen?
Tilt Fanatic said:
The eclair build still will not install on my phone. I changed to an earlier .nbh file and now don't need the KAISDIAG.nbh file to get out of the splash screen and into the installer. When I run the install command for NAND, it says it can't mount, "no such file exists", "failed to extract." Keep in mind I haven't even gotten Android installed to NAND, just the installer itself. I can't even go back to WinMo either. It also seems like a permissions error since I believe it said the SD card is read only, but when plugged into my computer I fixed that and now it is read-write, but not on the phone. Please help because I really want to either get this working, or get back to WinMo instead of have this useless phone I currently have. Thanks.
Is there a way to enter the command line from the installer screen?
Click to expand...
Click to collapse
Alright, I'll try and sum up your experiences. Tell us if we're missing anything;
You have the following symptoms
Linux Android-installer works
Tri-color bootloader semi-works
You cannot use the USB
You cannot install polymod's Eclair build
Now, you have mentioned a couple of things you have tried, such as
Replacing the Linux NBH with another version
Fixing permissions on the SD-card
Fixing permissions through the Android-installer
Flashing a WinMO ROM through SD card
You did mention getting other behaviours when you switched to another NBH, such as "KAISDIAG.nbh" not being required.
Now, this is a long shot coming from me, as I have had no troubles with flashing, and the fact that I can use my USB, but since your phone is pretty messed up I guess it can't hurt as a suggestion;
You can flash to other NBH's I take it, as you mentioned you did a downgrade. What I'm a bit curious about is whether you did try to flash to a WinMO rom when you had downgraded to your current NBH.
Also, you said the previous NBH required you to have "KAISDIAG.nbh" on the card to even get working. Did you try and rename a WinMO-ROM's NBH to "KAISDIAG.nbh" and flash that? Might be that the flasher is really constrictive with the file names.
EDIT: Oh, and what about trying to run other Eclair builds? Just to see if you can nail it down to this being a problem of the builds or something more bound to the actual hardware/SPL/NBH's.
Android boot error "micropklt_lcd_ctrl: This function should no longer be used"
I've been battling this error again and again whenever I tried another Android release, and since there are no real answers around, but some others have the same problem, which according to searches mostly goes unanswered in bigger threads, I decided to go ahead and dedicate one thread to it.
Problem: After installing Android and running it, its boot ends up in an eternal loop displaying
Code:
micropklt_lcd_ctrl: This function should no longer be used
.
Setting: German Rhodium. Initially an Energy ROM. Since I thought it might be something from the ROM, the latest one is Energy.RHODIUM.21889.Android(ULTRA_LITE_ROM)_28.Jan.
8 GB SD from Kingston. Since this was named as a possible problem, tried with 1 GB SD (Kingston) as well.
Reformatted SD and restarted from scratch.
Tried Android versions:
Project Android 030810.cab
Project Android 033110.cab
[MJG]Rhod.Eclair.Rebuild033110.3.rar
plus various older ones (with different base name, xAndroid or something like that?) already deleted.
Tried to disable 3D Hardware during boot.
Another suggested workaround to use specific files from older releases; these I could no longer find on the net.
To sum attempts up:
Tried different (?) Android releases (xAndroid, Project Android) - fail
Tried small SD card (1 GB) - fail
Tried SanDisk instead of Kingston SD card - pending
Tried to reformat SD card (with SD card formatter) - fail
Tried to disable 3D Hardware - fail
Tried WinMo ROM labeled as created for Android (Energy.RHODIUM.21889.Android(ULTRA_LITE_ROM)_28.Jan) - fail
Tried to insert SIM card (was missing) - fail
Tried to update HardSSL (Rhodium-HardSPL_V2_00R3.exe) - fail
Information:
(forum prevented me from adding links to external information)
This forum, other members with same problem
Looking for: suggestions what else to try.
ItsReallyMe said:
I've been battling this error again and again whenever I tried another Android release, and since there are no real answers around, but some others have the same problem, which according to searches mostly goes unanswered in bigger threads, I decided to go ahead and dedicate one thread to it.
Problem: After installing Android and running it, its boot ends up in an eternal loop displaying
Code:
micropklt_lcd_ctrl: This function should no longer be used
.
Setting: German Rhodium. Initially an Energy ROM. Since I thought it might be something from the ROM, the latest one is Energy.RHODIUM.21889.Android(ULTRA_LITE_ROM)_28.Jan.
8 GB SD from Kingston. Since this was named as a possible problem, tried with 1 GB SD (Kingston) as well.
.
Click to expand...
Click to collapse
I have an AT&T Tilt2, stock rom, 8GB SanDisk. I see a very similar message when booting xdandroid, but mine continues to boot through, my boot sequence snippet runs like this:
Code:
[ 26.309173] Adding 102392k swap on /dev/block/ramzswap0.
Priority:-1 extents:1 across: 102392k
[ 26.484039]Something used micropklt_lcd_ctrl: This function should no longer be used
USING EXPERIMENTAL TILT2 LAYOUT
op: cannot stat '/init.etc/keymaps/tilt2_navi_pad.kl': No such file or directory
Touchscreen device directory is /sys/class/input/input2
Then continues to the screen calibration. I know I'm not helping directly, but perhaps can help lead others to clues ?
i already started a topic for this exact error....
http://forum.xda-developers.com/showthread.php?t=632128
So far no one has come up with a solution...
Oh, sorry, I searched the forum a few times, but mus have forgotten that thread, otherwise I would've posted there as well...
From what I can read there, maybe I should try a SanDisk instead of Kingston SD? Or is it SD vs. SDHC? Anyway, I just ordered a 2 GB SanDisk from Amazon (smallest one I could get ) and will try this next...
I managed to solve it by reflashing the newest HardSPL. (In my case I had a corrupt microp firmware, casuing all kind of problems in WM as well).
It might not solve the problem for you, but it can't hurt either
My SanDisk SD has not yet arrived, but I tried to insert a SIM card (phone currently has none, since I' using another one while testing) - no changes.
Thanks for the HardSPL hint - tried as well. No Luck, but at least another topic to add to the "things I tried" list
Okay.. So, i tried HardSPL.
Task 29
Reloaded my Rom
Hard Reset
Formatted Memory Stick
Followed ALL instructions!
Nothing happened.
I then went back and tried an old version of android from this thread
I used the 12/20 2.01 version.
AAAANNND..... it loaded right away....
WHY does this old version work, and the new ones wont?
what is different?
Update: my SanDisk SD card arrived, so I loaded [MJG]Rhod.2.1Sense.042310.rar, extracted it to the card, and started it. Same problem. This means it does not seem like a Kingston SD card problem.
So... I tested, and can confirm that the old build you linked solved the problem for me as well!
I have searched this ENTIRE FORUM and read EVERY SINGLE GOD FORSAKEN post about this error. I am at my whits end!
Someone said they got it to work with a more current package and an old rootfs.img
I didnt try the same two builds they did, i tried the sense ui one and the old rootfs. from the build i said works. it did not work.
so i figured i would compare the two rootfs.img to see what the difference is.
however, i cannot open the contents in windows (from what i understand)
so i install UBUNTU on my computer.
I cant for the life of me figure out how to mount the damn image!
PLEASE SOMEONE ELSE! please look this up. i am frustrated beyond words.
if you can give me a way to compare these files in windows, i will be glad to do it.
I just cant stand windows mobile crashing all the mother f-ing time and i REALLY REALLY REALLY want to use android. Im sorry for being so frustrated. i have spent literally HOURS on this...
Anyone, anything?
Mount rootfs.img
eternalcold said:
Anyone, anything?
Click to expand...
Click to collapse
You can mount image in terminal like this:
first create dir with:
mkdir /mnt/rootfs
then mount the image:
mount rootfs.img /mnt/rootfs/ -o loop
then change dir to /mnt/rootfs and you have the android FS.
i will also compare old and new rootfs so maybe we will found something!
BR
I still have this problem.
I tried what you said, but i keep getting errors. I cant seem to get it to work. I will again look through all the threads again, as well as the different websites i found from google. i will link them tomorrow when i get a chance. If anyone else has found anything, please let me know.
The latest kernel has the following commit message
"rewritten micropklt_lcd_ctrl calls to micropklt_set_misc_states calls"
So this might fix it for you guys?
It seems to have some other problems with sleep etc, but if it boots it is something
I see, thanks for looking, however, i still cant figure out how to mount and change things in ubuntu (sorry, i know i am a newb) would you be able to repackage it with the line changed to the old one? and upload it? i will check it out to see if it works.
It's alive!!
Download latest Android build with latest kernel from hxxp://glemsom.anapnea.net/android/htc-msm-android/ and replace zImage and modules and thats it.
i didn't test it full, but it starts!
Thanks to Star-Lite for info!!!
BR
Ah yes it works! Beautiful beautiful!
Don't thank me, thank CaptNoord for fixing this in the kernel
I'm sure he has a donate button somewhere
I will donate as soon as the bills are past this month (a couple more days)
Out of plain curiousity, is there a reason why this error only happened on some devices and not others? Could it be from a hardware difference between maybe different revisions of the device?
use the right starup.txt file
YONSTOPTECH AWINNER A31 KIT KAT TABLET 10.1 / 2GB RAM 8 OR 16 GB STORAGE, ANDROID 44.4.2 HDMI, 1080X600 DISPLAY.2 MICRO USB OTG PORTS, MICRO SD CARD SLOT, PRE ROOOTED OR IF NOT SEE BELOW. MADE FOR OEM ONLY BUT MORE GENERIC MODEL HAVE BEEN SEEM THAN AN ACTUALLY OEM LIKE GOOWEEL, FUSION, ONDA, ETC. UNDER $130 ON EBAY COMES WITH ALL CONNECORS, EXT SD CARD, STYLUS, AND TABLET/
I'VE SEEM VARIOUS QUESTIONS ASKED ABOUT MODEL BS 1078 ,ALL OVER THE WEB, ENOUGHTHAT I WISH TO SHARE SOME BASIC AND USEFULL INFO WITH THE MASSES.
ROOT....
THE Best AND EASIET WAY TO ROOT FOR ME HAS BEEN (I OWN 4) ROOT GENIOUS , FOR DOWNLOAD AND INSTRUCTIONS http://androidxda.com/DOWNLOAD-ROOT-GENIUS
IT'S A COMPONANT OF SHUAME AND IS A ONE CLICK ROOT METHOD STANDALONE IN ENGLISH.
RECOVERY...
BASIC RECOVERY IS INSTALLED ALREADY AS MY TABLET WERE PRE ROOTED., THOUGH SOM,E HAVE HAD DIFFICULTY USING THE MANUFACTURER AS THE VOLUME KEYS DON'T WORK PERFECTLY
A TIP=INSTALLED A MOUSE THROUGH THE OTG CABLE PROVIDED AND JUST MOVE MOUSE AROUND TO HIGHLIGHT SELECTION, THE VOLUME UP BUTTON FOR SELECTION. DO NOT PRESS VOLUME DOWN. LET'S YOU UPDATE FROM BOTH INTERESTING AND EXTERNAL
FIRMWARE/ROM ... THE LATESTKITKAT ROM FOR AUGUST 2014 IS AVAILABLE,NOT SURE OF IT'S CHANGELOG AS I'M HAPPY WITH THE 6 29 VERSION AND DON'T WANT TO CABLE YET .SOME HAVE THIS TABLET WITH 4.2, THIS UPGRADE IS TO4.4.2
http://pan.baidu.com/share/home?uk=1679008622 IS THE LINK TO FIRMWARE
TOOLS....
ALLWINNER INCLUDE THE TOOLS FOR EASY SD CARD FLASHING IN THE ALLWINNER A SERIES SDK FOR KITKAT. YOU'LL NEED A 4GB SD CARD, PHEONIX CARD.MSI AND THE WORD DOC INCLUDE IN FIRMWARE PACKAGE TO PUT ONTO EXTERNAL SD CARD SHOULD YOU WISH TO INSTALLED THAT WAY, WHEN POWER ON IT SHOULD START TO BOOT WITH YOUR EXT SD INSERTED, FROM THE SD CARD. ONCE IT REBOOTS, TAKE OUT EXT SD CARD, AND YOUR GOOD TO GO
HERE IS THE FULL SDK THAT YOU'LL NEED AS IT INCLUDE DRIVERS AND TOOLS FOR TWEAKING THE ROM, CHANGE BOOT ANIMATION , AND VARIOUS OTHER. OEM DIRECTED TWEAKS.
http://pan.baidu.com/wap/link?sharei...r_TOOLS&page=1
IN EACH DOWNLOAD ABOVE INCLUDES A WORD DOC IN EN/CHINESE WITH DIAGRAMS TO SHOW YOU HOW TO FLASH, MOD, EDIT BUILD.PROP ETC.
ANY QUESTIONS, DON'T HESITATE TO ASK
PAUL TARANEH
ALSO REF TO http://forum.xda-developers.com/showthread.php?t=2704721 FOR MORE INFO ABOUT ROOTING TABLET
Paulzt said:
YONSTOPTECH AWINNER A31 KIT KAT TABLET 10.1 / 2GB RAM 8 OR 16 GB STORAGE, ANDROID 44.4.2 HDMI, 1080X600 DISPLAY.2 MICRO USB OTG PORTS, MICRO SD CARD SLOT, PRE ROOOTED OR IF NOT SEE BELOW. MADE FOR OEM ONLY BUT MORE GENERIC MODEL HAVE BEEN SEEM THAN AN ACTUALLY OEM LIKE GOOWEEL, FUSION, ONDA, ETC. UNDER $130 ON EBAY COMES WITH ALL CONNECORS, EXT SD CARD, STYLUS, AND TABLET/
I'VE SEEM VARIOUS QUESTIONS ASKED ABOUT MODEL BS 1078 ,ALL OVER THE WEB, ENOUGHTHAT I WISH TO SHARE SOME BASIC AND USEFULL INFO WITH THE MASSES.
ROOT....
THE Best AND EASIET WAY TO ROOT FOR ME HAS BEEN (I OWN 4) ROOT GENIOUS , FOR DOWNLOAD AND INSTRUCTIONS http://androidxda.com/DOWNLOAD-ROOT-GENIUS
IT'S A COMPONANT OF SHUAME AND IS A ONE CLICK ROOT METHOD STANDALONE IN ENGLISH.
RECOVERY...
BASIC RECOVERY IS INSTALLED ALREADY AS MY TABLET WERE PRE ROOTED., THOUGH SOM,E HAVE HAD DIFFICULTY USING THE MANUFACTURER AS THE VOLUME KEYS DON'T WORK PERFECTLY
A TIP=INSTALLED A MOUSE THROUGH THE OTG CABLE PROVIDED AND JUST MOVE MOUSE AROUND TO HIGHLIGHT SELECTION, THE VOLUME UP BUTTON FOR SELECTION. DO NOT PRESS VOLUME DOWN. LET'S YOU UPDATE FROM BOTH INTERESTING AND EXTERNAL
FIRMWARE/ROM ... THE LATESTKITKAT ROM FOR AUGUST 2014 IS AVAILABLE,NOT SURE OF IT'S CHANGELOG AS I'M HAPPY WITH THE 6 29 VERSION AND DON'T WANT TO CABLE YET .SOME HAVE THIS TABLET WITH 4.2, THIS UPGRADE IS TO4.4.2
http://pan.baidu.com/share/home?uk=1679008622 IS THE LINK TO FIRMWARE
TOOLS....
ALLWINNER INCLUDE THE TOOLS FOR EASY SD CARD FLASHING IN THE ALLWINNER A SERIES SDK FOR KITKAT. YOU'LL NEED A 4GB SD CARD, PHEONIX CARD.MSI AND THE WORD DOC INCLUDE IN FIRMWARE PACKAGE TO PUT ONTO EXTERNAL SD CARD SHOULD YOU WISH TO INSTALLED THAT WAY, WHEN POWER ON IT SHOULD START TO BOOT WITH YOUR EXT SD INSERTED, FROM THE SD CARD. ONCE IT REBOOTS, TAKE OUT EXT SD CARD, AND YOUR GOOD TO GO
HERE IS THE FULL SDK THAT YOU'LL NEED AS IT INCLUDE DRIVERS AND TOOLS FOR TWEAKING THE ROM, CHANGE BOOT ANIMATION , AND VARIOUS OTHER. OEM DIRECTED TWEAKS.
http://pan.baidu.com/wap/link?sharei...r_TOOLS&page=1
IN EACH DOWNLOAD ABOVE INCLUDES A WORD DOC IN EN/CHINESE WITH DIAGRAMS TO SHOW YOU HOW TO FLASH, MOD, EDIT BUILD.PROP ETC.
ANY QUESTIONS, DON'T HESITATE TO ASK
PAUL TARANEH
ALSO REF TO http://forum.xda-developers.com/showthread.php?t=2704721 FOR MORE INFO ABOUT ROOTING TABLET
Click to expand...
Click to collapse
Good thread Paul nice to have a place to discuss this tablet i have just posted in the other thread you refereed to but will also post it here below
I bought a 10.1 Allwinner A31s 16GB from Ebay for £60 the device details show as a YONESTOPTECH BS1078
It is a nice tablet for the price and came pre rooted witch was great.
One of the first things i did was make a backup off the Rom with online nandroid backup as i like messing and wanted a backup just in case i messed up. and here is where things got messy, online nandroid backup would only be able to restore if i had a custom recovery (CWM or TWRP)
So off i went and tried to install TWRP from the guide on this thread http://forum.xda-developers.com/showthread.php?t=2210676
Long story short it didn't work an i thought i had bricked it as it was stuck on the boot logo, i managed to find FW for a Q102 A31S Tablet Stock Firmware 4.4.2 wich is the same tablet under a different name, after several failed attempts to recover through phoenix suite as i couldn't get it into recovery, i downloaded phoenixcard and successfully flashed the FW Phew all was good lol.
So if anyone has successfully installed a custom recovery any info would be grateful as it would be nice to try a custom Rom.
I have also had a little play with dragonface for allwinner devices as this lets you change a few things on the stock ROM ISO and then you can re flash with your custom changes, Two things i would like to tweak are volume and lcd settings as i feel the volume on this device is to quiet and the lcd contrast could do with tweaking. in dragon face you can load the sys.cofig settings, i have found the volume config but haven't got a clue what can be changed to increase the max volume level so if anybody has any knowledge then any input would be appreciated, here is the code for audio settings,
Code:
;pa_single_vol,pa_double_vol: 31 level,1.5db/step.0x1f is the large volume.
;cap_vol:use for system record,0x0--0db,0x1--24db,0x2--27db,0x3--30db,0x4--33db,0x5--36db,0x6--39db,0x7--42db
;headphone_vol,earpiece_vol: must least than 0x3b. 0x1 is a step.
;headset_mic_vol: headset mic(mic2) vol,use for phone headset mic call
;main_mic_vol: main mic(mic1) vol,use for phone main mic call
;--------------------------------------------------------------------------------
[audio_para]
audio_used = 1
audio_hp_ldo = "none"
headphone_vol = 0x3b
earpiece_vol = 0x3b
cap_vol = 0x7
pa_single_vol = 0x1b
pa_double_used = 1
pa_double_vol = 0x1f
headphone_direct_used = 0
headphone_mute_used = 0
audio_pa_ctrl = port:PA18<1><default><default><0>
audio_mute_ctrl = port:PA17<1><default><default><0>
headset_mic_vol = 6
main_mic_vol = 6
Thanks in advance for any input
Click to expand...
Click to collapse
Got straight from manufacturer today
The FW download link:
Updata tools: http://pan.baidu.com/s/1pJkEHAF
FW: http://pan.baidu.com/s/1gdw0sSz
Of anyone can flash and offer any input that's great.
Thanks,,,, Paul Taraneh
Sorro for offtopic, but has anyone found a suitable case for this tablet?
Paulzt said:
Got straight from manufacturer today
The FW download link:
Updata tools: http://pan.baidu.com/s/1pJkEHAF
FW: http://pan.baidu.com/s/1gdw0sSz
Of anyone can flash and offer any input that's great.
Thanks,,,, Paul Taraneh
Click to expand...
Click to collapse
Just flashed that FW and can confirm it is the stock FW pre rooted and working fine.
Thanks
Sent from my rk3288 using XDA Premium 4 mobile app
ezcast application install error
Hi,
I get an error message when I try to install the ezcast app on the tablet, do you have any
idea why this would happen? I would really like to cast from this device to my tv.
Also when I try to install the fulltilt poker app from fulltilt.com, the site doesn't recognize my
device as an android device. I got over it by copying the .apk file from another device but
I just thought to mention it.
Thanks,
Zohar
Hmm. I've been able to install ezcast on mine, and maybe the poker game was initially meant for windows. Your tab most likely came pre rooted so check your root permission. For ez cast contact the apps developer he is very good at replying just give all stats from about phone . good luck
Sent from my XT1034 using XDA Premium 4 mobile app
Now I know the button + problem prior to update rom
Paulzt said:
YONSTOPTECH AWINNER A31 KIT KAT TABLET 10.1 / 2GB RAM 8 OR 16 GB STORAGE, ANDROID 44.4.2 HDMI, 1080X600 DISPLAY.2 MICRO USB OTG PORTS, MICRO SD CARD SLOT, PRE ROOOTED OR IF NOT SEE BELOW. MADE FOR OEM ONLY BUT MORE GENERIC MODEL HAVE BEEN SEEM THAN AN ACTUALLY OEM LIKE GOOWEEL, FUSION, ONDA, ETC. UNDER $130 ON EBAY COMES WITH ALL CONNECORS, EXT SD CARD, STYLUS, AND TABLET/
I'VE SEEM VARIOUS QUESTIONS ASKED ABOUT MODEL BS 1078 ,ALL OVER THE WEB, ENOUGHTHAT I WISH TO SHARE SOME BASIC AND USEFULL INFO WITH THE MASSES.
ROOT....
THE Best AND EASIET WAY TO ROOT FOR ME HAS BEEN (I OWN 4) ROOT GENIOUS , FOR DOWNLOAD AND INSTRUCTIONS http://androidxda.com/DOWNLOAD-ROOT-GENIUS
IT'S A COMPONANT OF SHUAME AND IS A ONE CLICK ROOT METHOD STANDALONE IN ENGLISH.
RECOVERY...
BASIC RECOVERY IS INSTALLED ALREADY AS MY TABLET WERE PRE ROOTED., THOUGH SOM,E HAVE HAD DIFFICULTY USING THE MANUFACTURER AS THE VOLUME KEYS DON'T WORK PERFECTLY
A TIP=INSTALLED A MOUSE THROUGH THE OTG CABLE PROVIDED AND JUST MOVE MOUSE AROUND TO HIGHLIGHT SELECTION, THE VOLUME UP BUTTON FOR SELECTION. DO NOT PRESS VOLUME DOWN. LET'S YOU UPDATE FROM BOTH INTERESTING AND EXTERNAL
FIRMWARE/ROM ... THE LATESTKITKAT ROM FOR AUGUST 2014 IS AVAILABLE,NOT SURE OF IT'S CHANGELOG AS I'M HAPPY WITH THE 6 29 VERSION AND DON'T WANT TO CABLE YET .SOME HAVE THIS TABLET WITH 4.2, THIS UPGRADE IS TO4.4.2
http://pan.baidu.com/share/home?uk=1679008622 IS THE LINK TO FIRMWARE
TOOLS....
ALLWINNER INCLUDE THE TOOLS FOR EASY SD CARD FLASHING IN THE ALLWINNER A SERIES SDK FOR KITKAT. YOU'LL NEED A 4GB SD CARD, PHEONIX CARD.MSI AND THE WORD DOC INCLUDE IN FIRMWARE PACKAGE TO PUT ONTO EXTERNAL SD CARD SHOULD YOU WISH TO INSTALLED THAT WAY, WHEN POWER ON IT SHOULD START TO BOOT WITH YOUR EXT SD INSERTED, FROM THE SD CARD. ONCE IT REBOOTS, TAKE OUT EXT SD CARD, AND YOUR GOOD TO GO
HERE IS THE FULL SDK THAT YOU'LL NEED AS IT INCLUDE DRIVERS AND TOOLS FOR TWEAKING THE ROM, CHANGE BOOT ANIMATION , AND VARIOUS OTHER. OEM DIRECTED TWEAKS.
http://pan.baidu.com/wap/link?sharei...r_TOOLS&page=1
IN EACH DOWNLOAD ABOVE INCLUDES A WORD DOC IN EN/CHINESE WITH DIAGRAMS TO SHOW YOU HOW TO FLASH, MOD, EDIT BUILD.PROP ETC.
ANY QUESTIONS, DON'T HESITATE TO ASK
PAUL TARANEH
ALSO REF TO http://forum.xda-developers.com/showthread.php?t=2704721 FOR MORE INFO ABOUT ROOTING TABLET
Click to expand...
Click to collapse
Let pressed the button + and hit hit hit hit the power button a lot of times after you begin press the power button some times connect to pc and when in the devices manager appear the new device and start to configure it let it the table quiet now go to pc wait a moment to windows configure it and do it with phoenix, if somebody have win 8 8.1 or 7 x64 you must disble signatures of drivers, in windows 8 go to restar but dont press the button restart, press shift and with shift pressed clic in restar a menu appear go to advanced options, advanced options and later the pc restart with a menu there press 7 for disable the driver signature and there install phoenixm if you already installed install it again and you can see the diferrences, now my tablet is with a new rom and i made it in win 8.1 x64, thanks for all the info, steps and rom thank so much
Anyone know if there's a version of 'CyanogenMod' available for this tablet ???
Thnxs in advance for any info.
I just purchased an AllWinner Q102 Tablet. It took me a day or so to realize that it also is pre-rooted. Here is my problem. I continue to get errors that say "unfortunately google play.... has stopped." or "unfortunately Netflix has stopped"
It's driving me crazy! I can't use any of my regular apps.
The model is a Q102
Android Version
4.4.2
Firmware version
v4.5.0919P
Kernel version
3.3.0
[email protected] #20
Wed Sep 10 21:31:21 CST 2014
It seems like a nice little tablet for the price....
I would rather go to stock if it works rather than a root that is flakey
Thanks for any help you can give!
My Google Play reboots, but no "unfortunately" messages
djrnewcastle said:
I just purchased an AllWinner Q102 Tablet. It took me a day or so to realize that it also is pre-rooted. Here is my problem. I continue to get errors that say "unfortunately google play.... has stopped." or "unfortunately Netflix has stopped"
It's driving me crazy! I can't use any of my regular apps.
The model is a Q102
Android Version
4.4.2
Firmware version
v4.5.0919P
Kernel version
3.3.0
[email protected] #20
Wed Sep 10 21:31:21 CST 2014
It seems like a nice little tablet for the price....
I would rather go to stock if it works rather than a root that is flakey
Thanks for any help you can give!
Click to expand...
Click to collapse
I seem to have the identical tablet (specdevice . com / showspec.php ? id=5f13-c36d-ffd4-db280033c587) purchased in October. Mine was also pre-rooted, and it took me a while to figure that out too!
I do not see the messages/crashes that you see; my apps generally run with stability. I do occasionally experience surprise reboots (presumably from crashes) when I connect a USB device or am attempting to upgrade a large app via Google Play. I assume that my Google Play reboots are somehow related to running out of app disk space. Even though my tablet has 32 GB flash internally (split into two 16 GB flash devices) for some reason only 2GB was allocated to the /data partition, where apps are installed. When I found your post, I was actually looking for a solution to increase my tablet's /data partition. I read about different firmware downloads available (earlier in this thread, and in a chinagadgetsreviews blogspot -- sorry, XDA does not let me post links yet) but don't know whether they would help me with my small /data partition problem.
I'd be happy to test any particular apps on my tablet, if that would be of diagnostic use to you. And please let me know if you ever discover a solution to increase the app disk space.
bs1078 tonbux 10.1
Hi mines same bricked it with something now only get heart screen anyone know a fix memory man issues I had root toolbox app and you can change memory cache size etc if not another app carefully as can brick if Ness wrong settings ie screen resolution
stuck on first logo not android man
Hi got same tablet but stuck on very first logo do you know if this is still bootable by your method ? Thanks in advance for any assist
jayden91012 said:
Hi got same tablet but stuck on very first logo do you know if this is still bootable by your method ? Thanks in advance for any assist
Click to expand...
Click to collapse
Jayden just reflash the firmware with phoenix suite.
---------- Post added at 10:05 AM ---------- Previous post was at 10:01 AM ----------
cqfast said:
I seem to have the identical tablet (specdevice . com / showspec.php ? id=5f13-c36d-ffd4-db280033c587) purchased in October. Mine was also pre-rooted, and it took me a while to figure that out too!
I do not see the messages/crashes that you see; my apps generally run with stability. I do occasionally experience surprise reboots (presumably from crashes) when I connect a USB device or am attempting to upgrade a large app via Google Play. I assume that my Google Play reboots are somehow related to running out of app disk space. Even though my tablet has 32 GB flash internally (split into two 16 GB flash devices) for some reason only 2GB was allocated to the /data partition, where apps are installed. When I found your post, I was actually looking for a solution to increase my tablet's /data partition. I read about different firmware downloads available (earlier in this thread, and in a chinagadgetsreviews blogspot -- sorry, XDA does not let me post links yet) but don't know whether they would help me with my small /data partition problem.
I'd be happy to test any particular apps on my tablet, if that would be of diagnostic use to you. And please let me know if you ever discover a solution to increase the app disk space.
Click to expand...
Click to collapse
I reccommend a app called foldermount (Root) you can change storage location to extsd i use it for most games and large apps had this tablet about year now.
Hi ... are the links for firmware etc. in post #1 still good ?,
I don't seem to get anywhere finding the download. ... Jack
jachol said:
Hi ... are the links for firmware etc. in post #1 still good ?,
I don't seem to get anywhere finding the download. ... Jack
Click to expand...
Click to collapse
Here you go jack this is the link to q102 firmware which is same as bs1078 stock.
http://chinagadgetsreviews.blogspot.com/2014/09/download-android-kitkat-442-stock_11.html
If you need anything else just ask i have most stuff on my laptop for this device if needed if links not working.
DJBoxer said:
Here you go jack this is the link to q102 firmware which is same as bs1078 stock.
http://chinagadgetsreviews.blogspot.com/2014/09/download-android-kitkat-442-stock_11.html
If you need anything else just ask i have most stuff on my laptop for this device if needed if links not working.
Click to expand...
Click to collapse
Hi DJB,
Thanks for quick reply ... downloading now, not sure think tried this source before (long story),
will try it with Phoenix USB Pro, chances are I need to come back to you thanks for the offer,
PM will be best I think. ... Jack
Hi,
I have this same tablet and i have a problem. When i connect it to my computer or my girlfriend´s(win 7 and 8.1) The tablet is not recongnized.
anybody know why ? i was trying around to find the drivers but i only found google ones.
I would be really thankfull if u could give me a hand on this.
Lomezno said:
Hi,
I have this same tablet and i have a problem. When i connect it to my computer or my girlfriend´s(win 7 and 8.1) The tablet is not recongnized.
anybody know why ? i was trying around to find the drivers but i only found google ones.
I would be really thankfull if u could give me a hand on this.
Click to expand...
Click to collapse
Hi, sorry for late reply, been tied up with family business for a whle.
re. drivers Pda. net drivers seem to work OK for me, this link should help ... J
http://forum.xda-developers.com/showthread.php?t=1983470
Hello,
Perhaps this issue has been solved multiple times already, but I was unable to find an answer so far. I just don't know where to start.
I own a Xtrons Android 5.1.1 head unit for a 2012 Audi A3.
The device has the MCU version of MTCD_GS_V2.04_1. It was rooted previously and ran Malaysk ROM for a week, then I restored the original ROM and upgraded it to a newer version. It still is rooted. I've been using the head unit for 10 months after that without big issues until last week.
The problem: it doesn't boot anymore. It happened on a parking lot when I switched to the back gear which turned on the rearview camera. At the switch, the screen went black and the head unit didn't respond to any button. I tried to reset it, attempted to load the recovery screen as I successfully did many times before. It didn't work. I disconnected the power and all other cables and let it stay for a few days, then connected and tried again. The issue is the same: when I power on the device, the boot stops on the Android logo screen (Lolipop). It doesn't go any further.
I contacted the tech support and they said they need to see the head unit. But doesn't rooting void the warranty? Is there anything that would help me to reanimate the head unit at home?
I'd appreciate any help.
Thanks.
d_motley said:
Hello,
Perhaps this issue has been solved multiple times already, but I was unable to find an answer so far. I just don't know where to start.
I own a Xtrons Android 5.1.1 head unit for a 2012 Audi A3.
The device has the MCU version of MTCD_GS_V2.04_1. It was rooted previously and ran Malaysk ROM for a week, then I restored the original ROM and upgraded it to a newer version. It still is rooted. I've been using the head unit for 10 months after that without big issues until last week.
The problem: it doesn't boot anymore. It happened on a parking lot when I switched to the back gear which turned on the rearview camera. At the switch, the screen went black and the head unit didn't respond to any button. I tried to reset it, attempted to load the recovery screen as I successfully did many times before. It didn't work. I disconnected the power and all other cables and let it stay for a few days, then connected and tried again. The issue is the same: when I power on the device, the boot stops on the Android logo screen (Lolipop). It doesn't go any further.
I contacted the tech support and they said they need to see the head unit. But doesn't rooting void the warranty? Is there anything that would help me to reanimate the head unit at home?
I'd appreciate any help.
Thanks.
Click to expand...
Click to collapse
Use the SD Firmware Tool to create a bootable SD card with the original firmware. Follow the procedure described here:
https://forum.xda-developers.com/showpost.php?p=67184851&postcount=50
m00n61 said:
Use the SD Firmware Tool to create a bootable SD card with the original firmware. Follow the procedure described here:
https://forum.xda-developers.com/showpost.php?p=67184851&postcount=50
Click to expand...
Click to collapse
Sorry for sent reply and thanks for the tip. I needed time to buy a new SD card for creating the bootable SD card as suggested in a post you linked to. I didn't work for me though. The software that should create the bootable SD card doesn't see the SD card. The computer sees and formats the SD card but when I start the app and try to choose the SD card, there's nothing in the drop down menu to choose from.
d_motley said:
Sorry for sent reply and thanks for the tip. I needed time to buy a new SD card for creating the bootable SD card as suggested in a post you linked to. I didn't work for me though. The software that should create the bootable SD card doesn't see the SD card. The computer sees and formats the SD card but when I start the app and try to choose the SD card, there's nothing in the drop down menu to choose from.
Click to expand...
Click to collapse
Did you give it administrative privilege? It must access the boot area of the SD, it won't work without.
m00n61 said:
Did you give it administrative privilege? It must access the boot area of the SD, it won't work without.
Click to expand...
Click to collapse
Never heard of that.