Related
HUGE BREAKING NEWS!!! THIS JUST IN:
May 12th, 2008
ENTER "FrankenKaiser"
For the past several weeks, I've been working with Jocky on unbricking devices with nuked SPL's as a result of task 2a MTTY commands. Last week the amazing Jocky found a way to exploit OEMSBL & to Security Unlock a BRICKED device via dload mode. That's right, you heard correctly, Jocky Security Unlocked a bricked device, giving me access to all of the OEMSBL, Radio Boot Loader commands!!!
Subsequently, Jocky has written a tool that will then use this exploit to load a new SPL via Dload mode into ram & do some device initialization. After three chalenging & frustrating weeks, we were able to load a SPL into ram, get the spl to stick & voila.....I now have the first ever Kaiser recovered from being a nuked SPL brick!!!!
I won't give to many details, as this is really Jocky's baby & it's his place to share the information as he sees fit, but I'll tell you that this tool may be the start of something huge! It will allow you to test SPL versions & recover from bad SPL flashes. I believe this tool is also going to be the center of fixing the locked AT&T radio's.
I can take no credit for this tool, I was really nothing more than a brave & willing guinea pig, that occasionally floated theories, & remembered some of the little stuff.
Jocky did let me name the tool, based on the first thing I thought & said when we were talking about the theory behind the tool, which was "Oh my God, It's alive, it's aliiiiive!!!!", so the tool has been named FrankenKaiser!
If you have a Bricked Kaiser, Let me know, post it here in this thread until Jocky start a thread specifically related to this new tool. Please don't overwhelm Jocky with requests & PM's, as the tool must be moddified for each & every different OEMSBL version. If you have a task 2a or other bricked Kaiser, please PM me or post the info here on this thread & depending on the type of brick you have, someone will let you know if this tool can help you.
Okay, it's true I've put my Tilt thru hell & back trying to help out the noobie. I have done partial flashes, radio & rom, to recreate their problems in an effort to guide them thru the solutions.
I've alway been able to recover......Until now!
A WARNING TO ALL USERS FROM OTHER DEVICES NEWLY COMING TO THE KAISER!!!
After countless trips to hell & back for my device, it finally, It is totally dead. After doing a few MTTY task & info calls while assisting a noobie I decided to format my device & the nand storage to start afresh. Now I am stuck in OEMSBL.
Should you try and format or dump bad blocks as previously possible on some older devices using the task 2a command. There are several thing you need to know. Firstly, you'll need to immediately flash a new SPL BEFORE soft resetting. Otherwise, your device will not boot period. You will find that the service LED light stays green like it is fully powered, & the "GREEN" light will come on whenever you hit the power button, but when you plug it into the USB port on your PC, it will only be seen as new hardware & will add the following new devices: a NMEA GPS Device, a Qualcomm Data Device, an Qualcomm Diagnostic Interface, a Baseline Modem, Baseline Storage Device, etc. But A/S will not run & MTTY cannot communicate using standard commands nor can it be used thru the USB port.
The reason this happens is becauser you have just completely formatted the NAND, essentialy killing the Boot Loader or SPL.
As of this time, there is no known recovery for this type of brick. Several people are working towards a fix, but unless your device is security unlocked, there will be no miraculous recovery.
ALWAYS EXCERSIZE EXTREME CAUTION WHEN COMMUNICATING THRU MTTY WITH SPL OR WITH OEMSBL. DO NOT ASSUME THAT THE SPL COMMANDS ARE STATIC> THEY CAN & DO CHANGE BETWEEN DIFFERENT SPL VERSIONS & DEVICES.
As an example, Tilt Devices with the 1.56SPL can execute the boot command, whilee HTC 1.93SPL devices cannot & require a task 8 to reset.
If you do not know what SPL is, or have no idea the available commands & their effects, do not use them.
Aaaarghhhh.... that's horrible
Did you try to take out the battery already?
Maybe disable all Active sync tasks before you plugin to the usb?
Also a suggestion, flash a rom from sd?
I do think your device is still alive because otherwise it wouldn't be recognized ad all!
Laurentius26 said:
Aaaarghhhh.... that's horrible
Did you try to take out the battery already?
Maybe disable all Active sync tasks before you plugin to the usb?
Also a suggestion, flash a rom from sd?
I do think your device is still alive because otherwise it wouldn't be recognized ad all!
Click to expand...
Click to collapse
Laurentius is right; it would surprise me if the Flash from SD-card would not work for you!
Good luck,
Edward
sorry to say that but it is a true brick now, it is recognized by windows because there it falls back to qualcomm diagnostic mode (which will not help you at all) I had exactly the same situation and you won't be able to flash it, send it to htc for repair
No, The screen will not turn on & when plugged in it now acts as accessories or hardware for my PC.
The chipset inside the device is still getting power, & it is a chipset that is powerful & used for many, many things. So, it's no suprise that it sees the modem, the Basecom Interactive, Basecom NMEA device, etc...What it doesn't see is all of it integrated into a package & it actually creates 6 or 7 port connections thru XP Hardware Wizard for each "accessory".
What I believe has happened is that the unit has been completely formatted meaning the actual Windows CE has been destroyed, formatted, removed, kaput...
The only way to revive I think would be to reload CE into the device the way Mfg's & OEM's do.
There should be a way in QPST or MTTY to switch the phone from diagnostic into download mode, from there you could use the QPST Software Download tool to load up the firmware..
Da_G said:
There should be a way in QPST or MTTY to switch the phone from diagnostic into download mode, from there you could use the QPST Software Download tool to load up the firmware..
Click to expand...
Click to collapse
nope, there is now way to do that
Actually Hanza, there is absolutely a way to do it. I mean the OEM does it, so technically it is possible & there are articles about it all ove MSDN.
The problem is that I think it will require platform builder. Or maybe the tools used to load linux onto the device.
If we can load linux onto the devices,Hanza, then there is no reason we couldn't load CE. The only question is...What tools are needed.
I'll play around with loading linux or maybe the Android SDK while waiting for my new device.
GSLEON3 said:
Actually Hanza, there is absolutely a way to do it. I mean the OEM does it, so technically it is possible & there are articles about it all ove MSDN.
The problem is that I think it will require platform builder. Or maybe the tools used to load linux onto the device.
If we can load linux onto the devices,Hanza, then there is no reason we couldn't load CE. The only question is...What tools are needed.
I'll play around with loading linux or maybe the Android SDK while waiting for my new device.
Click to expand...
Click to collapse
sorry, that's a misunderstanding my post was referring to the use of pst software/mtty and usb connection, and I reckon that it's cruel to give the man hope, though you can always buy yourself a piece of software built based on jtag, special serial connector and a book how to to that but given the sources you mentioned I reckon you haven't read much about the problem yet, my kaiser is about two be back from service this week and if there was no breakthrough on the internet about that with last 2 weeks then there is no know way how to talk to qualcomm diagnostic software directly using usb.
In reading this thread and the other, am I to understand that via MTTY commands, you have wiped not only your splash, radio & OS, but also SPL from your phone completely?
BTW, have you tried using itsme's utilities, e.g., pdocwrite to upload nb files directly? I have little or no experience with this tool, but I thought suggesting it wouldn't hurt...
_Alex_ said:
In reading this thread and the other, am I to understand that via MTTY commands, you have wiped not only your splash, radio & OS, but also SPL from your phone completely?
BTW, have you tried using itsme's utilities, e.g., pdocwrite to upload nb files directly? I have little or no experience with this tool, but I thought suggesting it wouldn't hurt...
Click to expand...
Click to collapse
yes Alex, also SPL (which is the real problem here), and you can't use pdocwrite unless you could actually talk to the device which in qualcomm diagnostic mode you can't with this software as it will not accept any commands other than specific to that mode, I have flashed windows mobile device for about 4 years now and that's actually the first time I ended up with a real brick but of course htc can easily fix it (they did it in 1 day, most likely in less than 30 minutes) but they have equipment to do that which I don't and only few users on xda have that kind of equipment, to get more info about it you could look in the search for task 2a there were bricks like this before us
Alex,
Yes CE, Radio, SPL, OS... All see to be completely wiped with the task 2a command. I don't think pdocwrite will work as its still needs a medium to connect to my device. That medium is what I have yet to find. The first step would be to somehow restore boot loader. I am currently trying to see if I csan use qpst to push linux to the device. I haev found some CE restore utilities for reverting from linux, but first I need to be able to at least boot to SPL or another Bootloader.
Whats about Windows CE and KITL Mode?
The device stays in OEMSBL. If you use the MotorolaQ drivers, you will be able to connect to the right COM port and issue radio bootloader commands. You will probably be able to unbrick it depending on what problem it has. First try the easy one:
* Execute "setboot 0" and "cego" commands.
If this does not work, then probably your SPL has been erased in NAND, you can check that by dumping radio memory address 0 right after executing "cego" command. (commands: "cego" and "mb 0 40000").
If it's all 0xFF then your SPL has been erased. Here's how to fix that:
1) Issue command 'setboot 1' (with the default 0, the application ARM is hang because it tries to execute 0xFF), this way it keeps the SPL in memory after reset.
2) Copy a full SPL at address 0 by issuing 256K times 'mb <address> 1 <byte>' (i've written a small app that does this for you...)
3) Patch the 'cego' function in ram, to NOP the function that loads application arm bootloader, in my case (OEMSBL version 1.27.12) the patch was 'mw 901708 1 0000a0e1' you'll have to figure it out yourself if you have a different OEMSBL version.
4) execute 'cego' and see the bootloader 3color screen appear again (keep the bootloader keys pressed if you have not used a patched SPL in step 2)
5) Flash HardSPL.
6) Connect to OEMSBL again and execute "setboot 0".
7) See the device booting OS
Thanks pof!
setboot 0 returns ARM9BootMode:0, so it is communicating. However, I get invalid command errors with the cego & mb commands. You think there is a way to flash an spl.nbh using OEMSBL thru pnewbootloader? I believe you're right on the money & from what I've learned playing around today is that the task 2a command indeed formats the NAND. So bye bye bootloader. I think it's now just a matter of finding a way to flash spl back. That said however, I can figure things out given a lot of time, but I'm definitely nowhere near a bright bulb on the XDA X-mas tree, so to speak. So you'll have to forgive me if the meaning of "Patch the 'cego' function in ram, to NOP the function that loads application arm bootloader" escapes me.
Thanks again!
When I used to work @ symbol we used to interface with our devices directly in IPL mode using hyperterminal (included in windows). I wonder if you could accomplish something like that?
From there we used to use IPL commands (I dont remember them because this was a long time ago)
GSLEON3 said:
Thanks Oli!
However, I get invalid command errors with the cego & mb commands. Also, where can I find the spl patch app you've written? I searched high & low.
Thanks again!
Click to expand...
Click to collapse
I think POF is talking about JumpSPL correct? I am surprised it didn't work after what POF recommended his right on 99% of the time!
I believe s right. I just think the cego command isn't correct for my device. I think maybe this command has changed just as spl commands can change between versions. The mb command also returns an invalid argument.
But it's definitely down the right path.
GSLEON3
I really wish I could help you out man. You have done alot on this forum for alot of people. Unfortunately I'm about as lost in here as a hooker in a pecker patch. Sorry bro, wish I could help.
pof's method only works if your device is security unlocked
Has anyone ever tried to flash a rom or develop a rom that can be flashed by a Mac? I have Missing sync to sync my Tilt and to download .cabs and .exe's.
Works great by the way. I have flashed several roms from Windows XP on the " other side " of my Intel chip, so no problem there. Just wondering can it be done from the Mac side? And has anyone done it?
I have been using Macs and Apples for over 25 years ( started with Apple IIc) and never once had the urge to switch so comments from the "Apple Bashers" will mean nothing to me
Just curious.
no i'm not going bash apple but i haven't come across anything for mac and i believe the kaisercustomruu.exe can only be run only on windows
I have successfully flashed my Tilt using a Parallels install of XP Pro. Of course that requires an Intel Mac to accomplish...
NotATreoFan said:
I have successfully flashed my Tilt using a Parallels install of XP Pro. Of course that requires an Intel Mac to accomplish...
Click to expand...
Click to collapse
I have flashed several roms using both Parallels and Bootcamp on the other side of my Intel/Mac chip and .exe file will not run on OS X but is it possible to create a rom using say a .dmg package instead of an .exe package?
The problem is far beyond the fact that the package is in exe the tools to actually flash the rom are windows only
I'd just flash from the MicroSD card.
Read here:
http://forum.xda-developers.com/showthread.php?t=336158
AstainHellbring said:
The problem is far beyond the fact that the package is in exe the tools to actually flash the rom are windows only
Click to expand...
Click to collapse
Obviously you can't just re-package under a different file extension. What " tools " are you refering to? Kitchen tools? Again just re-packaging. Leopard can run on an intel chip. Word, Excel, etc, can run natively on a Mac. Can you put together a rom or write one from scratch that can be downloaded natively to a Mac and then flashed to a Kaiser? Even theoretically?
You can use whatever OS you want... Just do what Peterfnet suggested... Use the SD card method... It's safer and easier.
Just follow the link provided by Peterfnet!
Rayan said:
You can use whatever OS you want... Just do what Peterfnet suggested... Use the SD card method... It's safer and easier.
Just follow the link provided by Peterfnet!
Click to expand...
Click to collapse
It wasn't a "how do I flash a rom question " , I press a button and my screen twirls from OS X Leopard to Windows XP , I flash a new rom, press another button and my screen twirls back to Leopard and all my Mac apps. ( new Intel Chip for Mac)
The question was " what do the knowledgeable people here think? " Are there limitations of computer science that would prevent this or just limitations of available ground work that I could create?
Edit: I re-read this post and it sound kind of terse, I didn't meanit that way.
Thanks for your input Rayan
I see no reason why it would not be possible to flash a ROM natively inside Mac OS. But in order to do so, the flashing application written by HTC would need to be recoded to run on Mac.
If you extract the .exe file that is inside the rar file posted by the chefs here, you will see 5-10 files, one of which is the OS.nbh file. If you can write a program for Mac OS that can communicate with the Kaiser and call that file, then it would be possible. (DISCLAIMER: I am NOT a programmer, so it is a definite possibility that I could be talking out of my ass.)
Since flashing is not yet available to Linux users, then Mac is probably still a bit off.
peterfnet said:
I'd just flash from the MicroSD card.
Read here:
http://forum.xda-developers.com/showthread.php?t=336158
Click to expand...
Click to collapse
best option all around
Well, ever since I discovered the SD Card method I don't flash it through the PC anymore... No more fears of freezing up, power failures and such!
In fact, I carry several "test" ROMS in my card just to install them on the go whenever I'm bored! LOL...
Here's an answer from someone who is paid to write software....
You're correct there is no technical reason that you can't flash your phone from a Mac OS.
Basically the whole process is a few commands & responses sent across the USB port and then the nbh image streamed via the port to the waiting device.
Here's the bind: Microsoft is well known for not working well with others. Why would they be motivated to provide non-MS OS the ability to flash "Windows Mobile"? It's kind of like iTunes being able to integrate with non-iPod MP3 players as well as it works with iPods (or so I've heard).
Thanks all , it looks like I have my next project. Thanks for all your input. peterfnet and Rayan thanks when HTC comes out with their new rom update and new driver package at the end of the month I'm going the card method for a change.
Hi guys !
I wanted to know whether the new Samsung Galaxy Tab 3 10.1 can run Windows 8./LINUX !!
Theoretically it shouldn't be too hard as it has an Intel Atom x86 processor and it shares a lot of it's specs with the Acer Iconia w510 and other tablets running Windows 8
Can you please tell me some of the issues that we may have to deal with ?
Like we will have to do something with the bootloader to make Windows 8 bootable and things like that :/
And please if you want to say something like -Why do you want to run windows on an Android tablet-
XDA is about modding. A new OS will not hurt anyone AFAIK.
What are your ideas ? I think it can be done but what will we need to do ?
Now we will be concentrating on Linux. it Will be easier.
Please use this thread for discussing Linux on the Samsung Galaxy Tab 3 10.1
Thanks for reading !
Nitro_123 said:
Hi guys !
I wanted to know whether the new Samsung Galaxy Tab 3 10.1 can run Windows 8.
Theoretically it shouldn't be too hard as it has an Intel Atom x86 processor and it shares a lot of it's specs with the Acer Iconia w510 and other tablets running Windows 8
Can you please tell me some of the issues that we may have to deal with ?
Like we will have to do something with the bootloader to make Windows 8 bootable and things like that :/
And please if you want to say something like -Why do you want to run windows on an Android tablet-
XDA is about modding. A new OS will not hurt anyone AFAIK.
What are your ideas ? I think it can be done but what will we need to do ?
Thanks for reading !
Click to expand...
Click to collapse
much like apple windows 8 is closed source. Thats pretty much the end of the thread. Without a way to compile, edit the operating system and know what changes your making its just not a undertaking many will accept.
@trevd Do you have anything to say about this ?
@wranglerray I'm just talking about installing windows to a device. AFAIK no compiling/editing will be needed. There are other tablets out there that do the same thing so why not this one ? The only major hurdle I see is making some kind of a custom bootloader that can boot the windows stuff instead of the android stuff. THAT part will probably need to be made from scratch or it may be ported from a similar device.
There are quite a few devices like this that run windows with similar specs so why not this one ?
Nitro_123 said:
@trevd Do you have anything to say about this ?
@wranglerray I'm just talking about installing windows to a device. AFAIK no compiling/editing will be needed. There are other tablets out there that do the same thing so why not this one ? The only major hurdle I see is making some kind of a custom bootloader that can boot the windows stuff instead of the android stuff. THAT part will probably need to be made from scratch or it may be ported from a similar device.
There are quite a few devices like this that run windows with similar specs so why not this one ?
Click to expand...
Click to collapse
well quite honestly your talking about porting windows to a device. Our device comes with android and you want to port windows to it instead. So on our device there are parititons chuncks of data of varying sizes allocated to hold a small part of the code that runs our phone. from ramdisk to the radio. The issue on its surface, we dont know how that partition table lines up with a different device.(which the partition table can and most likely is, completely different) and because winodws 8 is closed source we dont know how it boots, or how to edit the imstaller to ensure the os gets copied over the correct partitions. if porting were as easying as just flashing what ever you want and then changing some things to tweak it i'm sure you'd see hundreds of ports in a day or two. Unforntatley it really kinda sucks
The partitions are the biggest problem. We could in theory also boot from the SD card and as a result bypass all the android stuff and get it dual-booting but first we need to know how we can boot windows
Nitro_123 said:
@trevd Do you have anything to say about this ?
Click to expand...
Click to collapse
Hi There
I've not got a device in my hands yet to be able to give a proper device focused opinion on this.
but since you ask, I will say It really all depends on the bootloader setup on the device and how accessible that is, it could well be a proprietary Samsung Design in which case I wouldn't want to "mess" with it unless you had a JTag handy for when s**t goes wrong, otherwise you'll be holding a very expensive brick.
Even without bootloader access theoretically you could create a 3rd stage bootloader ( possibly Grub2/uboot ) which sits in place of the kernel in the boot image ( or recovery image ) , this would give the Option to load android or chainload into the windows boot manager, this is how things are done on classic x86.
If you have to go with a 3rd Stage Loader then the first steps is to get your own code running instead of the Standard Kernel Initialization inside an android boot image, There's all sorts of fun to be had after that as basically you'd need to place things in memory where the Kernel or the Boot Manager is expecting to find them amongst many other things.
Standard Windows 7/8 Installations setup a "hidden ( not assigned a drive letter in windows) " 100MB NTFS partition which contains the bootmgr.exe ( TRIVIA : boot manager replaced NT LOADER ( NTLDR ) which was used by Windows XP ). The boot configuration datafile ( BCD ) contains the settings for loading the actual operating system.
I wouldn't be too concerned about the closed source nature of Windows as there's still plenty of folks doing some absolutely bonkers **** with Windows/Windows Booting. Check out http://reboot.pro if you want to see some of that. My favourite is the 10MB WindowsXP that boots cmd.exe and nothing else LOL WAT!?! . I'm not saying you'll find the answers there but I'd consider it the "state of the art" when booting windows in unusual ways.
Without getting too far ahead, if you did get it booting then it appears the Asus Memo Pad FHD 10 which is a windows 8 device has the same SOC so I would expect there to be driver support already present ( or available ).
Additionally I've not even considered UEFI and how that would affect the whole scenario as I've not delved into the UEFI chaos yet.
Personally I've not used Windows in anger for a couple of years and I've only booted Windows 8 in VM's just to have a look, so my "WindowsFu" is getting a little rusty.
In Summary : Technically Possible ( anything is possible ) - All depends on the bootloader and how much you want it! and to paraphrase @wranglerray "If it was easy, everyone would be doing it"
Trevd
@trevd @wranglerray Thanks so much for the input
This shouldn't really be too hard to do for an experienced dev IMO but I don't have mcuh experience with all this stuff
The stuff that has been done to the HD2 was a lot harder I think but Cotulla still managed to make a custom bootloader and boot WP7 things like that
Thanks again for the comments
@wranglerray @trevd
http://forum.xda-developers.com/showthread.php?t=2540480
Please read the above link
basically we can now understand what the partitions are and what they do
Is it really that hard to make some kind of a zip file that can be flashed in recovery to boot the windows 8 bootloader ?
Why can't we just install an image of windows 8 to the SD card and boot off it ?
What do I need to know in order to understand and try to make this work ? Since no one is developing for the tab 3 10.1 I thought I'd give it a try
Nitro_123 said:
@wranglerray @trevd
http://forum.xda-developers.com/showthread.php?t=2540480
Please read the above link
basically we can now understand what the partitions are and what they do
Is it really that hard to make some kind of a zip file that can be flashed in recovery to boot the windows 8 bootloader ?
Why can't we just install an image of windows 8 to the SD card and boot off it ?
What do I need to know in order to understand and try to make this work ? Since no one is developing for the tab 3 10.1 I thought I'd give it a try
Click to expand...
Click to collapse
As a newbee I will guess:
Windows can take a bigger effort.
Runing Linux natively, easier. Android drivers should be already Linux Compatible. Tweeking them under Linux I do not know. My best guess is looking how to make grub to run first for dual booting. Or even better, Create a partition on external SD forl Linux, To be safe on TWRP recovery add a bottom to boot Linux or even esier re-use one temporary to test posibility.
Good Luck.
dale_para_bajo said:
As a newbee I will guess:
Windows can take a bigger effort.
Runing Linux natively, easier. Android drivers should be already Linux Compatible. Tweeking them under Linux I do not know. My best guess is looking how to make grub to run first for dual booting. Or even better, Create a partition on external SD forl Linux, To be safe on TWRP recovery add a bottom to boot Linux or even esier re-use one temporary to test posibility.
Good Luck.
Click to expand...
Click to collapse
@dale_para_bajo EXACTLY my friend. You stole the words right out of my mouth
Objective: Get Linux booting. SD card way is better.
Any updates on this?
SharpnShiny said:
Any updates on this?
Click to expand...
Click to collapse
It will never happen, the firmware isn't compatible.
calden74 said:
It will never happen, the firmware isn't compatible.
Click to expand...
Click to collapse
Yeah I've looked a bit more into it since, I think the best chance was Windows RT, and that isn't downloadable I believe, so that's it. Thanks for the reply though.
SharpnShiny said:
Yeah I've looked a bit more into it since, I think the best chance was Windows RT, and that isn't downloadable I believe, so that's it. Thanks for the reply though.
Click to expand...
Click to collapse
Even if Windows RT aka an ARM optimized ISO, was downloadable, it COULD NOT be used on Tab 3 10.1
Because this Tab doesn't have an ARM CPU, it have a x86 (32Bits) CPU. So better get a x86 ISO. I also got the same idea (like many other Tab 3 10.1 users). But the dream is NOT going anywhere. Also, Android apps are honestly BAD OPTIMIZED for this CPU ! That's why the Tab lags.
I sold mine and have bought a Tab 7.7 w/ SuperAmoled HD Screen but I broke its screen and can't now find any replacement in my region
Our best chance would be:
Ability of instally Windows 8 into a single .IMG file like Windows XP has been installed !
However, QEMU and KVM refuses to install Windows 8 into a VM idk why !
The RAM of the Tab is also a bit low to run Windows 8 inside Android.
If only a Great Dev could port or create "The Multi-boot bootloader" for Tab 3 10.1 as done on Nexus 7, then I won't waste my money buying a Windows 8 Tablet again since I would manage to install Windows 8 natively, whatever happened !
Sent from my roomate's computer
Can this work?
trevd said:
Hi There
I've not got a device in my hands yet to be able to give a proper device focused opinion on this.
but since you ask, I will say It really all depends on the bootloader setup on the device and how accessible that is, it could well be a proprietary Samsung Design in which case I wouldn't want to "mess" with it unless you had a JTag handy for when s**t goes wrong, otherwise you'll be holding a very expensive brick.
Even without bootloader access theoretically you could create a 3rd stage bootloader ( possibly Grub2/uboot ) which sits in place of the kernel in the boot image ( or recovery image ) , this would give the Option to load android or chainload into the windows boot manager, this is how things are done on classic x86.
If you have to go with a 3rd Stage Loader then the first steps is to get your own code running instead of the Standard Kernel Initialization inside an android boot image, There's all sorts of fun to be had after that as basically you'd need to place things in memory where the Kernel or the Boot Manager is expecting to find them amongst many other things.
Standard Windows 7/8 Installations setup a "hidden ( not assigned a drive letter in windows) "* 100MB NTFS partition which contains the bootmgr.exe ( TRIVIA : boot manager replaced NT LOADER (* NTLDR ) which was used by Windows XP ). The boot configuration datafile ( BCD )* contains the settings for loading the actual operating system.
I wouldn't be too concerned about the closed source nature of Windows as there's still plenty of folks doing some absolutely bonkers **** with Windows/Windows Booting. Check out httpdouble slash)reboot(dot)pro if you want to see some of that. My favourite is the 10MB WindowsXP that boots cmd.exe and nothing else LOL WAT!?! . I'm not saying you'll find the answers there but I'd consider it the "state of the art" when booting windows in unusual ways.
Without getting too far ahead, if you did get it booting then it appears the Asus Memo Pad FHD 10 which is a windows 8 device has the same SOC so I would expect there to be driver support already present ( or available ).
Additionally I've not even considered UEFI and how that would affect the whole scenario as I've not delved into the UEFI chaos yet.
Personally I've not used Windows in anger for a couple of years and I've only booted Windows 8 in VM's just to have a look, so my "WindowsFu" is getting a little rusty.
In Summary : Technically Possible ( anything is possible ) - All depends on the bootloader and how much you want it! and to paraphrase** @wranglerray "If it was easy, everyone would be doing it"
Trevd
Click to expand...
Click to collapse
I am new to the forum but not windows and android though not advanced but do you think that getting those files in the 100mb partition and making an ext2 image of them with slight modifications to fit in the architecture and flash the image as a recovery image?
or perhaps we could use rom manager and by creating a virtual rom composing of windows and boot them via the rom manager tool.
or perhaps we could use grub or a similar tool to boot into an image file or sdcard with windows installed on it and flash the grub files onto the recovery partition but some one with advanced info please confirm all these possibilities!
________________________________________________________________________________________
Hit thanks if I helped, its not that tough
Go ahead guys !
This thread is becoming IRRELEVANT !
Tab 3 was made to run Android (and possibly Ubuntu since Android is a mobile version of Linux) but NOT Windows !
So just use Android or Nothing.
Sent from my roomate's computer
yes but
Nonta72 said:
Go ahead guys !
This thread is becoming IRRELEVANT !
Tab 3 was made to run Android (and possibly Ubuntu since Android is a mobile version of Linux) but NOT Windows !
So just use Android or Nothing.
Sent from my roomate's computer
Click to expand...
Click to collapse
Yes, but since both Windows and any x86 Linux are designed for the same architecture, shouldn't we be able to boot Windows?
glorified sd card
Dani515 said:
Yes, but since both Windows and any x86 Linux are designed for the same architecture, shouldn't we be able to boot Windows?
Click to expand...
Click to collapse
i think it's possible
check this out starting at angel_666's post #18
http://forum.xda-developers.com/showthread.php?t=2589370&page=2
finding out where the flag checking starts and finishes would probably make the third stage boot
more realizeable. i directly flashed both grub and then plop to recovery block and got nowhere,
so it's mmcblk0boot0 or mmcblk0boot1, i haven't found anything in param===>/dev/block/mmcblk0p16 yet
and if p5210 has the little kernel burnt onto the chip setup, from my understanding of what i've
read it's a really basic/small/simple setup so even if the flag was there and unchangeable we should
still be able to get past it somewhere else, right?
Really ?
Dani515 said:
Yes, but since both Windows and any x86 Linux are designed for the same architecture, shouldn't we be able to boot Windows?
Click to expand...
Click to collapse
I firstly got this idea and have posted here on XDA about it :good:
Look at this thread http://forum.xda-developers.com/showthread.php?t=2682603
However, mine was about running Windows 8 inside Android
Sent from my roomate's computer
Done already?
Hello,
I have found this thread: http://forum.xda-developers.com/showthread.php?t=2070139
If you read further, you can find almost complete solution for archlinux natively on Note 10.1. WIth multiple fixes/scripts. Any reason why it cannot be done on tab3 10.1? I'm asking because I might try to compile proper kernel and prepare some distribution as tablet provides power that ends up completely wasted by android.
Welcome to my tutorial !
You can find others tutorials related to the Cube i6 :
Update your EFI BIOS
Install Android 4.4.4 (Stock & RemixOS)
Disclamer: This process might contain ROM hacking, this is for advanced users.
Software included may be subject to copyright.
Flash your device at your own risk. Developer is not responsible for what you do on your device.
What you need:
Cube i6 Air (3G or Wifi)
2 Flash Drives (1Gb or more, and 4Gb or more)
OTG cable
USB Hub (3 Ports recommended)
WinPE for Win10 (Downloadable on my drive)
Win10 32 bits ISO (link in tutorial)
THIS IS THE LINK I'M REFFERING TO WHEN SAYING "THE DRIVE"
https://drive.google.com/folderview?id=0B8YPw4HjmqNCZktOZy1OTEN2ZVE&usp=sharing
What to do :
1.) Start by plugging the first usb drive (1Gb or more) into your computer, and format it to FAT32 using any formatting tool,
MAKE SURE YOU CHANGE PARTITION TABLE STYLE TO GPT, EITHER YOU WILL END UP WITH ERROR ON WINPE INSTALL
2.) Now you need to download WinPE from the drive, go to your device folder, then go into the windows folder, and download it.
Once you downloaded it, uncompress. You will find a "WinPE_XX" folder inside, take all of its content, and extract it to your freshly formatted drive.
Heres what looks like the root of your key:
3.) Your USB Install Drive is ready. You can plug it off and save it for later.
You now need to download a 32Bits ISO version of windows, if you already have one, it should work, if you don't, you can download it from Microsoft Website
4.) Now take your downloaded ISO, and mount it with either windows, daemon tools, PowerISO, or any Disk Image Manager.
Once mounted, you need to navigate to the X:\sources\ folder, and extract "Install.wim" anywhere on your PC. Thats the windows system we will install.
5.) Go to the drive, into your device folder, go to windows folder, and download the "Image_Recovery_Extra.zip" you can find there.
It contains recovery + Files mandatory for install (because the Windows PE we're using is hacked from Cube).
6.) Take your second USB Drive (of 4Go minimum, it needs to hold windows), and format it to NTFS Filesystem with any formatting tool.
Now you can extract the "images" folder of the previously "Image_Recovery_Extra.zip" downloaded (KEEP THE IMAGES FOLDER THIS TIME)
And also copy inside that "images" folder your previously extracted Install.wim image file.
7.) You're good to go ! You can unplug the keys from your PC, and start working on the tablet as of now !
You need to boot to BIOS settings, using "ESC" key at startup of tablet. Once there, go to SCU Settings, the bottom right square.
You need to set your primary boot to "Windows" in the boot tab, or the key won't boot. If it is already, you can exit SCU and start step 8.
If it is not, just select it, then press F10. Tablet should reboot. Press ESC again at startup, and start step 8.
8.) Now everything is straightforward: Just select "Boot from EFI File", select your USB key in the list, and go to EFI folder, then go inside BOOT folder, and select "Bootia32.efi"
The tablet should boot to a command prompt (it lags much, but we will install drivers later) and it should install windows automatically then shut down.
If install fails, update your BIOS and try again or post here for some help.
Preparation looks like this:
Working device looks like this:
9.) Now you can get rid of the installation USB keys, you only need mouse and keyboard. Fire up your tablet freshly flashed, it should boot to a chinese logo with a circle under it. it might reboot a few times, it is actually expanding filesystem and populating your win10 install. Wait until you end up in language screen. if it shuts down, put it on again if it does not automatically.
10.) Windows is ready, now follow the instructions, language, set your name, until you end up on the windows desktop. When you are here, you need to download from the drive the Driver Package for windows 10, which is located inside the driver folder, inside the windows folder of your devices folder. It sould be named "Z37XX_CPU_Chipset.zip"
Extract it on the tablet, and run the included "Setup.exe". When finished, reboot your tablet.
you can also find various driver i added for os switch and gyrometer
Congrats! You successfully Installed Windows 10!
I do not guarantee it works on every device, nor with every windows version, but it works in my installation with a regular Win10 x86 Pro.
There might be some upgrades to do, as I personnally hacked the WinPE that is available on Cube's site, with Windows 10 ADK WinPE,
so feel free to report bugs, enhancements to this method. and report cube for not doing this so far !!!
Regards,
Max.
Top! Thank you!
I had exactly the same issue and want to fix it this weekend. My I6 arrived on Thursday. Now I follow your instructions to update to Windows 10.
Hi, glad it is helping! tell me if you are having issues, or if some steps aren't detailed! i'll upload some photos later. if you need something for this tablet feel free to ask
regards
stalker2106 said:
Hi, glad it is helping! tell me if you are having issues, or if some steps aren't detailed! i'll upload some photos later. if you need something for this tablet feel free to ask
regards
Click to expand...
Click to collapse
Hey Max,
now I have the first problem.
On my Windows 10 Image I do not have any install.wim file. There is only a install.esd (about 2GB) file in the \sources\ folder. But this file is not possible to extract with 7zip. The only *.wim file in the directory is the boot.wim. What have I to do?
scharrrfi said:
Hey Max,
now I have the first problem.
On my Windows 10 Image I do not have any install.wim file. There is only a install.esd (about 2GB) file in the \sources\ folder. But this file is not possible to extract with 7zip. The only *.wim file in the directory is the boot.wim. What have I to do?
Click to expand...
Click to collapse
Alright, i don't know what ISO of windows 10 you have, but i found a tutorial on how to convert esd to WIM, so no worries (http://www.intowindows.com/how-to-easily-convert-install-esd-to-install-wim/) furthermore, i would recommend using PowerISO for extracting the file, as i'm not aware of how to extract from ISO with 7zip
Okay, thank you. With this it works
But I have some error when I boot the WinPE on step 8. I get the message: "The boot configuration data for your PC is missing or contains errors" File: \EFI\Microsoft\Boot\BCD Error code: 0xc000000f""
On this point the tablet do not recognize any keyboard command.
scharrrfi said:
Okay, thank you. With this it works
But I have some error when I boot the WinPE on step 8. I get the message: "The boot configuration data for your PC is missing or contains errors" File: \EFI\Microsoft\Boot\BCD Error code: 0xc000000f""
On this point the tablet do not recognize any keyboard command.
Click to expand...
Click to collapse
What is that \EFI\Microsoft\Boot\BCD you are trying to boot from ?
You should select \EFI\Boot\bootia32.efi. If it does not work make sure your BIOS is at version 206 (its my case, so i guess it can be this) and if not, upgrade it with the provided tutorial, maybe you'll have more luck with that ? You can check its version on android by going to device info in settings and check IFW Version.
EDIT: The WinPE media might be trying to access your hard drive EFI folder to use its BCD configuration, check that too, maybe you can format that EFI partition before booting to winpe ?*
EDIT2: Check BCD integrity maybe, 262 144 bits is what it weights on my side
stalker2106 said:
What is that \EFI\Microsoft\Boot\BCD you are trying to boot from ?
You should select \EFI\Boot\bootia32.efi. If it does not work make sure your BIOS is at version 206 (its my case, so i guess it can be this) and if not, upgrade it with the provided tutorial, maybe you'll have more luck with that ? You can check its version on android by going to device info in settings and check IFW Version.
EDIT: The WinPE media might be trying to access your hard drive EFI folder to use its BCD configuration, check that too, maybe you can format that EFI partition before booting to winpe ?*
EDIT2: Check BCD integrity maybe, 262 144 bits is what it weights on my side
Click to expand...
Click to collapse
I do not know, why it says \EFI\Microsoft\Boot\BCD. I selected the correct .efi-file.
But I think my tab is now gone. I have try the bios update from 203 to your 206. It have flash completed to 100% and turns the tablet off. I wait a few minutes and then I try to turn it on again for another try to install Windows 10. But it will not turn on again. It does also not recognize the charger anymore. I think I brick the i6 with the 206 Bios. What a bother!
scharrrfi said:
I do not know, why it says \EFI\Microsoft\Boot\BCD. I selected the correct .efi-file.
But I think my tab is now gone. I have try the bios update from 203 to your 206. It have flash completed to 100% and turns the tablet off. I wait a few minutes and then I try to turn it on again for another try to install Windows 10. But it will not turn on again. It does also not recognize the charger anymore. I think I brick the i6 with the 206 Bios. What a bother!
Click to expand...
Click to collapse
Ok, if the process went 100%, then there is a high probability it is not bricked.
Remember that still, you can boot using DnX mode holding power and volume +.
What do you mean by "it does not recognize the charger" ? when you plug it, the charging led does not light up ?
Thats very odd. because its not controlled by bios but only hardware derivation I guess.
please keep me tuned in on that !!
Edit: FYI I used the exact same BIOS on my model, which is a i632GB15378650186.
stalker2106 said:
Ok, if the process went 100%, then there is a high probability it is not bricked.
Remember that still, you can boot using DnX mode holding power and volume +.
What do you mean by "it does not recognize the charger" ? when you plug it, the charging led does not light up ?
Thats very odd. because its not controlled by bios but only hardware derivation I guess.
please keep me tuned in on that !!
Edit: FYI I used the exact same BIOS on my model, which is a i632GB15378650186.
Click to expand...
Click to collapse
DnX mode does also not work. And yes i mean, that the LED does not light up at all.
My model is i632GB15224920293. I think it is an older one.
scharrrfi said:
DnX mode does also not work. And yes i mean, that the LED does not light up at all.
My model is i632GB15224920290. I think it is an older one.
Click to expand...
Click to collapse
Wow. You mean there are older model with other BIOS System ?
I'm so unhappy to hear your story. I hope i can help to fix it !
Whatsoever, how can any BIOS accept flashing itself if its not corresponding ?
Good thing you point out there, but c'mon, how can your tablet be bricked if the process went OK...
Maybe you can contact cube about it ? Maybe if you hold power long enough it will turn off ?
Once the tablet did this to me, had to hold power 10s to get it back off !
EDIT: good thing I remember is that i had it shipped with 205 BIOS, so i guess you're right and its an older model you have. Still, I have spare BIOS Firmware 204 that I flashed for testing purposes that also worked flawlessly !
EDIT2: found that there might be tons of differents models like raspberry pi, look this one does not match with any of ours : http://winphonetech.com/wp-content/uploads/2015/08/cube.jpg or maybe it is just a serial number generated from the # produced or the current date of prod ?
stalker2106 said:
Wow. You mean there are older model with other BIOS System ?
I'm so unhappy to hear your story. I hope i can help to fix it !
Whatsoever, how can any BIOS accept flashing itself if its not corresponding ?
Good thing you point out there, but c'mon, how can your tablet be bricked if the process went OK...
Maybe you can contact cube about it ? Maybe if you hold power long enough it will turn off ?
Once the tablet did this to me, had to hold power 10s to get it back off !
EDIT: good thing I remember is that i had it shipped with 205 BIOS, so i guess you're right and its an older model you have. Still, I have spare BIOS Firmware 204 that I flashed for testing purposes that also worked flawlessly !
EDIT2: found that there might be tons of differents models like raspberry pi, look this one does not match with any of ours : http://winphonetech.com/wp-content/uploads/2015/08/cube.jpg or maybe it is just a serial number generated from the # produced or the current date of prod ?
Click to expand...
Click to collapse
Yes, I think you are right, that the last numbers are any kind of a serial number. Do you have another Bios file? On the web I found only the 201. I can try to buy an ISP programmer and reflash the tablet.
And I have tried different buttons combinations on hold in hope that the tablet wake up again. But still nothing
scharrrfi said:
Yes, I think you are right, that the last numbers are any kind of a serial number. Do you have another Bios file? On the web I found only the 201. I can try to buy an ISP programmer and reflash the tablet.
And I have tried different buttons combinations on hold in hope that the tablet wake up again. But still nothing
Click to expand...
Click to collapse
Thats some freaking bad news ...
I uploaded 204 BIOS to the drive... cheers, fingers crossed.
It's a great news that the I6 Air is possible to upgrade to Win10 now. But before taking action, I have one question to clarify. After the upgrading, is the Android system still there and can switch over freely as before?
dahuzi said:
It's a great news that the I6 Air is possible to upgrade to Win10 now. But before taking action, I have one question to clarify. After the upgrading, is the Android system still there and can switch over freely as before?
Click to expand...
Click to collapse
Yeah, windows fill the partition space that is already configured, it means even if you resized your android to a 8 Gigs partition, the windows will not erase it !
For the switching process, it is even better because YOU install the switcher, and configure it the way you want (dektop shortcut, taskbar button, ...)
I can bring windows screenshots on purpose if needed
regards,
Stalker2106.
stalker2106 said:
Yeah, windows fill the partition space that is already configured, it means even if you resized your android to a 8 Gigs partition, the windows will not erase it !
For the switching process, it is even better because YOU install the switcher, and configure it the way you want (dektop shortcut, taskbar button, ...)
I can bring windows screenshots on purpose if needed
regards,
Stalker2106.
Click to expand...
Click to collapse
Thanks for clarification, another question, how about the system activation? Will the system become activated automatically?
And moreover, the drive folder you provided has no more WinPE available. Please check.
Thanks again.
dahuzi said:
Thanks for clarification, another question, how about the system activation? Will the system become activated automatically?
And moreover, the drive folder you provided has no more WinPE available. Please check.
Thanks again.
Click to expand...
Click to collapse
Hi, bad manipulation yesterday led me to delete archive from drive, but its uploading again !
I tried again the tutorial because of the problem of " scharrrfi" to check if its not broken in any manner, and it worked flawlessly !
Furthermore, the system is yours, and therefore, is not activated by default, it asks for a serial key !
Files should be on the drive later today
EDIT: The files are up on the cloud !
Now I wait for my ISP programmer. But I know, why I get first the message "The boot configuration data for your PC is missing or contains errors" File: \EFI\Microsoft\Boot\BCD Error code: 0xc000000f"". I found the solution in another forum. There was a problem with the formatting of my USB stick. I have to format it with an partitioning tool to GPT. And then it should work.
If I know this before, I have not to try to flash the bios...
scharrrfi said:
Now I wait for my ISP programmer. But I know, why I get first the message "The boot configuration data for your PC is missing or contains errors" File: \EFI\Microsoft\Boot\BCD Error code: 0xc000000f"". I found the solution in another forum. There was a problem with the formatting of my USB stick. I have to format it with an partitioning tool to GPT. And then it should work.
If I know this before, I have not to try to flash the bios...
Click to expand...
Click to collapse
Yeah, I admit that was kind of my fault telling you that upgrading your bios would change anything in your boot configuration, i'm so sorry
Let's hope this will work, still hope, windows 10 will make its way to your tablet no worries !
After some days of using it i report some glitches though:
Orientation sometimes get rekt, i dont know why but you have to set it manually...
Also the tablet is not as responsive as it is on android, but I guess power consumption is higher on windows, as it heats much more !
Sometimes i touch the part near the lens and it feels really hot !
Btw when on low battery, the power saver settings got me doubling my battery time, which is nice !
And on idle, locked, the battery charge way faster than on android.
Hi I have an other error - if I boot with the bootia file I got short 4 error messages: UEFILINUX ERROR [uefi_get_battery_status:121] Failed to get battery status - und error 160, 121 again and 149, all error with the battery. I haved update the firmware from 201 to 206. The battery is over 90% full in windows. Have you an idea whats wrong?
Hi, i am sorry if this is not the right forum, maybe there are no forums about tablets.
Chuwi HiBook Pro - i want android only, how to remove windows from dual boot and save space.
it seems that all tutorials show how to remove android from tablet, but i would like to remove windows.
Thank you.
METAL66 said:
Hi, i am sorry if this is not the right forum, maybe there are no forums about tablets.
Chuwi HiBook Pro - i want android only, how to remove windows from dual boot and save space.
it seems that all tutorials show how to remove android from tablet, but i would like to remove windows.
Thank you.
Click to expand...
Click to collapse
Windows is probably the main/primary OS. If getting Android to boot is somewhat linked to the existence of Windows, then you might not be able to remove it. That's probably why no one did that yet.
Edit: I found this http://forum.chuwi.com/thread-1848-1-1.html
Maybe you can give it a try. Remember that you do it at your own risks.
Hi and thanks for your replies, no i dont want to take risks, as i am no expert.
the next question is
Can i show more space on android? the 46Gbs taken by windows? do i only get 9Gb of it on android ??
METAL66 said:
Hi and thanks for your replies, no i dont want to take risks, as i am no expert.
the next question is
Can i show more space on android? the 46Gbs taken by windows? do i only get 9Gb of it on android ??
Click to expand...
Click to collapse
What you're trying to do is getting more space under Android.
That won't go without repartitioning. It's another task for the expert. Although you should be able to access (read) windows partition in Android if you use an app that can mount NTFS drivers in Android system.
Bigger issue. I just tried to reset from window to the if Android disappears. The tablet is stuck at some boot situation. Anyway to solve this plz?
METAL66 said:
Bigger issue. I just tried to reset from window to the if Android disappears. The tablet is stuck at some boot situation. Anyway to solve this plz?
Click to expand...
Click to collapse
I'm not familiar with these tablets, so I cant help you sorry.
METAL66 said:
Bigger issue. I just tried to reset from window to the if Android disappears. The tablet is stuck at some boot situation. Anyway to solve this plz?
Click to expand...
Click to collapse
Hi @METAL66 are you still stuck?
I don't have a guaranteed solution (I have original not "Pro") for you but the following helped me get Android working again when it got stuck at the Intel Inside logo.
This tablet is a x86-64 PC, and boots into a UEFI BIOS first.
1. If you don't have the Chuwi keyboard for this tablet, you can use an OTG (on the go) cable to connect a regular PC keyboard to it. I used a USB hub to allow me to connect a USB drive at the same time:
Code:
[Tablet] -- (OTG) -- [USB hub] -- [keyboard]
[USB storage]--------------------/
With the keyboard attached, you can press Del or Esc (a few times) during bootup to enter the BIOS config.
In there you can change things like whether to show a "quiet" boot or not. I turned it off so I see the AMI BIOS info when it first boots.
2. The official Chuwi Web site has self-contained recovery image installers (WinPE based).
This is the tutorial I used to recover Android while preserving Windows 10.
http -- forum.chuwi.com / thread-1283-1-1.html
Among the available recovery images is one that installs Android and causes Windows to be "lost"
http -- forum.chuwi.com / thread-1210-1-1.html
I'm not sure if the WinPE instance they distribute has full control over the partitions (presumably it at least has software on it to allow access to the Android partitions to repair the boot files write the image), but if so, maybe you can use it to delete the Windows Partitions and reclaim the space for use by Android.