Related
Let it now be hacked by the USA! France, those silly, um, baguette-eaters, via Bloggee, has several videos and some forums (in French) showing (but I don't think explaining) a hacked Archos 70B ereader/tablet. Can we get there??
I'd like to see a guide for hacking this 130 euro Android tablet!
About: I AM A N00B. I AM UNWORTHY! You are all wiser and cooler and better at all of this than me. I cannot write code, except some CSS and HTML, blah blah beginner stuff. I was the guy that jailbroke friends' iPhones when we studied in Italy. I like learning how to do things, but can't get extremely in depth, though I respect the process and the art behind it. Currently, my iPhone died so for a phone I have a quad-band Huawei J2SE POS I couldn't modify much, and a netbook with dual-boot Win7/Linux. Now in Germany, I bought a lovely Archos 70B ereader, and while it does the job of ereader, it's ugly and clunky and I want to hack it into running a cleaner, prettier Android ROM (with marketplace) since this seems to be a new device with a lot of potential.
Questions that haven't been answered by looking through these forums, and that I have encountered trying to customize my tablet:
Trying to get marketplace, I finally found an .apk to download, but trying to install, it said (paraphrase) "Only works with Froyo." SOO, Android's various versions (Eclair, Froyo, Gingerbread, Honeycomb, etc) while all the same OS in a way, prevent apps compatible with one version from being installed onto another version. It's like trying to install Win95 stuff on XP, or Win7 stuff on XP. Correct?
Issue: Finding Eclair-compatible .apk files. Where are they? Or, can Eclair apps be installed on other builds of Android, & vice versa?
Trying to upgrade the hardware to Froyo, well, I can't find anything. If a machine has the minimum hardware specs, why is installing any version an issue? Why can't I just search certain websites for an installer package and then use it, like a Windows or Linux .ISO, etc?
Issue: Upgrading from one Android OS/version to another (Eclair to Froyo, Froyo to Gingerbread, Eclair to Gingerbread)
Trying to upgrade firmware on device, I've found that Archos' website has no downloads for 70B ereader...HMMM. Issue, much? My firmware on the device is 1.0.1. There is no "Update Firmware" option or anything, and the firmware display is grayed out, so you can't touch it for further details or anything.
Issue: How do I update/backup/recover firmware for this device (or any, I guess)
While I have found guides to using Nandroid to backup a system in case of issues, they all seem to require that you have Marketplace so you can get Nandroid...and since this Archos version of Android doesn't have Marketplace...I've tried AppBrain Appmarket but the webpage isn't helpful: it says dl nandroid from marketplace or navigate there on my device's browser, but my device's browser won't download the APK when I visit the site. How does one get nandroid and a solid backup without marketplace? (.apk anywhere??)
Permanent rooting on this device; currently I use Z4Root and do temporary rooting, since 1) that's what guides said worked and 2) I don't know if permanently rooting my device will somehow destroy my data or be unrecoverable without further restore options.
Issue: Permanent root vs. temporary root (and why use one or the other)
Installing a custom ROM. In short, because I just am not clear, can someone clarify for me? Is this like basically wiping the HDD to all 0's, down to the first sector, and installing an entire new OS (called a "ROM") onto the HDD? I know a flash HDD is different than a circular spinning drive with Windows and an MBR, etc, but I'm curious if a custom ROM erases EVERYTHING, including a flash drive equivalent to all recovery/installer partitions. Or is there a tiny partition left and, if the factory reset button is pushed, that reinstalls/recovers everything? If that is not the case, then don't I need stock Archos ROM to reinstall/recover, if I wanted to go back to that?
Issue: Does a custom ROM completely wipe a HDD all to 0's, and if so, how does recovery work if using a device-specific build for Android (like Archos')
Maybe nobody cares about this tablet, and sure it's slow, but having a sub-$200 Android tablet would rock, and figuring out how to root and ROM and customize a device would be great.
Also, I want to say that most important is knowing if/how/why I can return to my stock Archos version of Android if dissatisfied; second most importantly is how to improve this (and any) device with a crappy tweaked Android OS into a pretty and fast (with marketplace) Android OS.
THANKS
Current for Archos 70B
Model Number A7EB
Firmware Version 1.0.1
Kernel Version 2.6.25 [email protected] #14
Build Number v.0.18.ECLAIR.eng.root.20110324.142810
Have successfully rooted (temporarily, until reboot) via Z4root.
Currently trying to use ArcTools...I had the site linked, and lots of other nifty links throughout, but xda handicaps us n00bs until 8 posts. So no links. Sorry.
Currently...
stuck at the same place as these people, pretty much.
http
forum.archosfans.com
viewtopic.php?f=82&t=51066
sorry for breaking it up. insert slashes to go to the link, or just visit the forum and search for Archos 70b.
currently looking into loading the (much nicer-looking) Voltaire firmware onto the 70b, if the parts are the same...hope i don't get a spanish installer program
BQReaders voltaire is exactly same hardware than archos 70b ereader,
BQReaders voltaire use a "standard" google android interface: android market, no application install restriction, google account sync etc.
Rom install procedure:
Download 3 zips from bqreaders.com website:
Usb device driver, MSWindows upgrade software, bqreader voltaire firmware.
1. Uncompress the 3 zips on your windows desktop
2. Turn off the 70b
3. Connect 70b to your PC using the usb link
4. press and lock right arrow button on 70b
5. press and lock power button
6. windows detects a neu device.
7. remove locks on keys and install the new device using uncompressed drivers.
9. Run the upgrade softwarelancer: RKAndroidBatchUpgrade.exe (if driver is correctly installed, youshould see the square "1" in device upgrade area in green color.
10. Check "image", and select the firmware (.img) décompressé.
11. click on Upgrade.
12. The square blink in "orange" color.
13. The device restarts.
14. unconnect usb link
15. the upgrade procedure continue on 70b screen.
16. the device restarts showing "bq" logo
17. screen calibration.
Warning: all internal flash data is lost!
stopdatrue said:
BQReaders voltaire is exactly same hardware than archos 70b ereader,
BQReaders voltaire use a "standard" google android interface: android market, no application install restriction, google account sync etc.
Rom install procedure:
Download 3 zips from bqreaders.com website:
Usb device driver, MSWindows upgrade software, bqreader voltaire firmware.
1. Uncompress the 3 zips on your windows desktop
2. Turn off the 70b
3. Connect 70b to your PC using the usb link
4. press and lock right arrow button on 70b
5. press and lock power button
6. windows detects a neu device.
7. remove locks on keys and install the new device using uncompressed drivers.
9. Run the upgrade softwarelancer: RKAndroidBatchUpgrade.exe (if driver is correctly installed, youshould see the square "1" in device upgrade area in green color.
10. Check "image", and select the firmware (.img) décompressé.
11. click on Upgrade.
12. The square blink in "orange" color.
13. The device restarts.
14. unconnect usb link
15. the upgrade procedure continue on 70b screen.
16. the device restarts showing "bq" logo
17. screen calibration.
Warning: all internal flash data is lost!
Click to expand...
Click to collapse
IMPORTANT QUESTION !!
Can i downgrade when i do this ^^ ?
i have found this:
xxx:xxx.archoslounge.net/forum/showthread.php?t=17642&p=275535&viewfull=1#post275535
^^
firmware_Archos70bereader.zip
xxxx:xxx.multiupload.com/U8MOUTWI5T
Does not work
It crashes at 99%. Luckily I had a recovery image.
I followed all the steps but can't get the image to install properly
We really need a rooted version of the BQ Voltaire software. Mine has now crashed twice since using it. If I could backup it wouldnt be nearly so bad.
The temporary root doesnt seem to work for me.
I have recently brought the Archos 70B ereader. I would like to know how to perform a factory restore. I have already tried to the reset button on the back, but that's just resulting in turning of the device. I also noticed the startup wizard on the setting menu, which after adjusting the startup setting is adding the factory apps back to the device. However, it does not seem to erase the whole internal memory like a real factory restore would do.
Does anyone knows how to perform a real hardreset on the reader?
Thanx.
I have upgraded my 70b succesfully with the BQ firmware.
It runs nicely tho it seems the battery is having a hard time.
So far i haven't managed to get it to last for more then a day.
Currently testing with juice defender to see if it helps.
I noticed some questions about reinstalling the default archos image (factory reset). The procedure to do this is the same as the installation of the BQ firmware. You just need to select the correct image.
So make sure you have both the archos and the bq image before attempting the upgrade. When you brick it, use the installation procedure to get it back to life.
However, when done properly, the BQ firmware should work.
Note: The drivers are not compatible with a 64bit OS. I flashed mine with an old XP-32 running laptop where WIN7-64 would fail.
I have a bq Voltaire running latest firmware (1.0.8) an i was able to temp root with Universal Androot.
will try to perm root and report back
...but is there any rom with software buttons (back, home, menu)?
because the bq does not have them...
cheers
EDIT: was unable to perm root with either Universal Androot or z4root...
I also have the software installed BQ. Works perfectly. I can not say that the batterylif is a problem. BQ software works much better tehn de the Archos Software.
The Archos 70 b eReaders and BQ Voltaire tablet run with the firmware Voltaire_20110699_v2.0.9.-2 _update.img very stable. For some days has been there one for this equipment android 2.2 version. There were some crahs on my device with that and moving the Apps on a SD card also doesn't work.
A rooted version with containedly in the Link2SD (you can move the Apps on SD card) the above-mentioned version in the link. E.g. an optimal mode of operation is possible with a 32 GB SD card class 10.
The Mini tool partition software can with standalone the SD card be formatted into 2 partitions. 1st partition FAT32 (e.g. 28 GB) 2nd partition ext3 (rest) both primary.
The approx. 2 GB suffice for many Apps.
For link see Archosfans forum. (i can't write link here)
Works like a charm with the Voltaire rom!
So THANX guys
how to remove key locks ?
stopdatrue said:
BQReaders voltaire is exactly same hardware than archos 70b ereader,
BQReaders voltaire use a "standard" google android interface: android market, no application install restriction, google account sync etc.
Rom install procedure:
Download 3 zips from bqreaders.com website:
Usb device driver, MSWindows upgrade software, bqreader voltaire firmware.
1. Uncompress the 3 zips on your windows desktop
2. Turn off the 70b
3. Connect 70b to your PC using the usb link
4. press and lock right arrow button on 70b
5. press and lock power button
6. windows detects a neu device.
7. remove locks on keys and install the new device using uncompressed drivers.
9. Run the upgrade softwarelancer: RKAndroidBatchUpgrade.exe (if driver is correctly installed, youshould see the square "1" in device upgrade area in green color.
10. Check "image", and select the firmware (.img) décompressé.
11. click on Upgrade.
12. The square blink in "orange" color.
13. The device restarts.
14. unconnect usb link
15. the upgrade procedure continue on 70b screen.
16. the device restarts showing "bq" logo
17. screen calibration.
Warning: all internal flash data is lost!
Click to expand...
Click to collapse
Hallo all and thank you for this great manual.
I allready prepared all: downloads, installing usb and uncompressing and so on, tryed many times, but my problem is your point 7): remove key-locks. , whichj I didn´read clearly before and thats why I want to install any new system on my/our Archos BQVoltaire: My daughter played with the login until it was locked and I do not have any Google-Password to unlock this. Nor dont know, how to hard reset or anything else. I am just a user, nothing else. Tried everything, but didn´t get it.
Do anybody hav an idea, how I can solve this, I would be really happy. Thx a lot in advance.
Giant THANKS, is easy as instruction say, and works a charm...now i have a tablet instead of a****!
stopdatrue said:
BQReaders voltaire is exactly same hardware than archos 70b ereader,
BQReaders voltaire use a "standard" google android interface: android market, no application install restriction, google account sync etc.
Rom install procedure:
Download 3 zips from bqreaders.com website:
Usb device driver, MSWindows upgrade software, bqreader voltaire firmware.
1. Uncompress the 3 zips on your windows desktop
2. Turn off the 70b
3. Connect 70b to your PC using the usb link
4. press and lock right arrow button on 70b
5. press and lock power button
6. windows detects a neu device.
7. remove locks on keys and install the new device using uncompressed drivers.
9. Run the upgrade softwarelancer: RKAndroidBatchUpgrade.exe (if driver is correctly installed, youshould see the square "1" in device upgrade area in green color.
10. Check "image", and select the firmware (.img) décompressé.
11. click on Upgrade.
12. The square blink in "orange" color.
13. The device restarts.
14. unconnect usb link
15. the upgrade procedure continue on 70b screen.
16. the device restarts showing "bq" logo
17. screen calibration.
Warning: all internal flash data is lost!
Click to expand...
Click to collapse
Point 7) of the instruction ????
Maybe for you woks like a charm. :good: Congratulations, fine for you.
But my problem has not been solved, since july last year!! I understand the entire instruction, already downloaded all indicated files, but as I already mentioned, my problem is point 7 of the instructions: "7. remove locks on keys and install the new device using uncompressed drivers"
.
The thread here is called something like "how to hakk keylocked installation...". Isn´t it?
But in Point 7) says: ".. remove locks on keys..." !!! What a fool is this, it is ridiculous. If I could remove this f... keylock manually, so why should I make a hard-reset.??? This is the REASON for what I´m going to do this !!!
My Archos ereader is not stolen nor part of any fraud. It just were handled foolish form my daughter, which is 10 y old.
Ok, if anybody have another idea, how to remove this keylock, you are welcome, thx
cvesch said:
I have upgraded my 70b succesfully with the BQ firmware.
It runs nicely tho it seems the battery is having a hard time.
So far i haven't managed to get it to last for more then a day.
Currently testing with juice defender to see if it helps.
I noticed some questions about reinstalling the default archos image (factory reset). The procedure to do this is the same as the installation of the BQ firmware. You just need to select the correct image.
So make sure you have both the archos and the bq image before attempting the upgrade. When you brick it, use the installation procedure to get it back to life.
However, when done properly, the BQ firmware should work.
Note: The drivers are not compatible with a 64bit OS. I flashed mine with an old XP-32 running laptop where WIN7-64 would fail.
Click to expand...
Click to collapse
For me it was the same. The drivers are working only on 32-bit win WinToUSB - cool tool, if you don't want to reinstall your win.
---------- Post added at 09:21 AM ---------- Previous post was at 09:07 AM ----------
MICROSOFT.WINDOWS.RT.8.1.WITH.OFFICE.2013.RT.RTM.WOA.ENGLISH.DVD-WZT
MICROSOFT.WINDOWS.RT.8.1.ADK.KIT.WOA.RTM-WZT
Thats all I want to say
windowsrtc said:
MICROSOFT.WINDOWS.RT.8.1.WITH.OFFICE.2013.RT.RTM.WOA.ENGLISH.DVD-WZT
MICROSOFT.WINDOWS.RT.8.1.ADK.KIT.WOA.RTM-WZT
Thats all I want to say
Click to expand...
Click to collapse
Anyone tried it yet? Looks like a risky process.
windowsrtc said:
MICROSOFT.WINDOWS.RT.8.1.WITH.OFFICE.2013.RT.RTM.WOA.ENGLISH.DVD-WZT
MICROSOFT.WINDOWS.RT.8.1.ADK.KIT.WOA.RTM-WZT
Thats all I want to say
Click to expand...
Click to collapse
Thanks. Unfortunately, what I gather from what I'm reading is that that image does not contain drivers. You need to manually add the drivers to the image before you install. If you don't, you'll brick your tablet, according to WZT. People may want wait a little bit until there are clear directions and a few people who can verify that they worked (i.e. that they installed 8.1 without any problems).
Additional note: It sounds like the driver package is only for the Surface RT, so users with other Windows RT tablets (ex. ASUS VivoTab RT) may brick their tablets if they try to use it. They'll have to wait until someone releases a driver package for their model (which WZT says might have to be taken from the Preview build).
Osprey00 said:
Even more unfortunately, while WZT has teased info about the driver package, they haven't actually leaked it yet.
Click to expand...
Click to collapse
This part isn't actually true, for what it's worth- it's included with the main download.
jhoff80 said:
This part isn't actually true, for what it's worth- it's included with the main download.
Click to expand...
Click to collapse
Oh, OK. I didn't catch that. They made it appear as though it was a separate download. Ah, you're right: there they are.
just run setup.exe
all drivers for surface are build in
BTW:I have rollback to 8.0 again
Osprey00 said:
...users with other Windows RT tablets (ex. ASUS VivoTab RT) may brick their tablets if they try to use it.
Click to expand...
Click to collapse
It is very difficult to brick an RT device. You can always recover it if you can boot to USB, and you have a recovery image and familiar with windows command line tools (diskpart, dism and so on).
Unfortunatley I'm on a business trip and can't create an upgrade instruction for VivoTab users. But there is nothing difficult - as we already have all needed drivers on a recovery partition, and all you need - just insert them into WIM using the Wzor's instructions from his original post on ru-board.
Installed this tonight. Note that drivers are NOT included in the iso from Wzor.
Extract boot.wim and install.wim from Wzor's iso, inject Wzor's RTM drivers via dism, commit, put boot.wim and install.wim with drivers back into iso, image to USB drive. I installed from within RT using setup (keeping nothing).
You have to use the default key on installation. You need to find out your actual RT key before you do this otherwise you end up with a non-activated RT 8.1 and no key. Export DigitalProductId and DigitalProductId4 from HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion and obtain your key. Instructions on how to here.
Works great. In the short amount of time I've been testing everything works perfectly OK, including all my accessories. (discussion here).
mamaich said:
It is very difficult to brick an RT device. You can always recover it if you can boot to USB, and you have a recovery image and familiar with windows command line tools (diskpart, dism and so on).
Click to expand...
Click to collapse
I figured as much, but not everyone may have the recovery image or the knowledge, and, for them, a dead device that they're unable to recover is as good as a brick. Regardless, I just wanted to pass along the same language that WZT used so that I'm not guilty of misrepresenting the risks or responsible if someone can't fix what he got himself into.
derausgewanderte said:
Installed this tonight. Note that drivers are NOT included in the iso from Wzor.
Extract boot.wim and install.wim from Wzor's iso, inject Wzor's RTM drivers via dism, commit, put boot.wim and install.wim with drivers back into iso, image to USB drive. I installed from within RT using setup (keeping nothing).
You have to use the default key on installation. You need to find out your actual RT key before you do this otherwise you end up with a non-activated RT 8.1 and no key. Export DigitalProductId and DigitalProductId4 from HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion and obtain your key. Instructions on how to here.
Works great. In the short amount of time I've been testing everything works perfectly OK, including all my accessories. (discussion here).
Click to expand...
Click to collapse
Thanks for your instructions and verifying that it works. The original instructions don't mention writing down your current key first. While I likely would've done that anyways, it's re-assuring to see it in writing, just in case. I might give this a go tomorrow.
FYI, there's now an ISO with the Surface RT drivers baked in, so that users don't have to use DISM to add them manually. The release name is:
DRIVERS FOR SURFACE RT ONLY___MICROSOFT WINDOWS RT 8 1 WITH OFFICE 2013 RT RTM WOA ENGLISH DVD-WZT
Note that it's only for the Surface RT, not other RT tablets.
Also note that you need the installation key, and, also, before installation, you need to export and decrypt your retail 8.0 key. Information on that is available here
Osprey00 said:
Also note that you need the installation key, and, also, before installation, you need to export and decrypt your retail 8.0 key. Information on that is available here
Click to expand...
Click to collapse
and here is the direct link to Osprey00's post with a way of getting the key if you only have your RT.
Good news!
I'll just wait till some skillful surface owner gets the jailbreak and then update!
huslterose said:
Good news!
I'll just wait till some skillful surface owner gets the jailbreak and then update!
Click to expand...
Click to collapse
[EDIT: Never mind. I misunderstood.]
I don't follow. There's nothing to "jailbreak" and it can't get much easier than it is now (outside of simply waiting until Microsoft rolls out 8.1 via Automatic Updates). You just follow instructions to find out your 8.0 key, install the 8.1+drivers ISO (not the one in the OP; the one that I listed a few posts up) with a general installation key, then activate 8.1 with your 8.0 key.
Osprey00 said:
I don't follow. There's nothing to "jailbreak" and it can't get much easier than it is now (outside of simply waiting until Microsoft rolls out 8.1 via Automatic Updates). You just follow instructions to find out your 8.0 key, install the 8.1+drivers ISO (not the one in the OP; the one that I listed a few posts up) with a general installation key, then activate 8.1 with your 8.0 key.
Click to expand...
Click to collapse
I think he is referring to the lack of jailbreak on 8.1 for unsigned desktop apps - a feature which should have been in the OS from the start, instead microsoft wasted time patching the exploit the jailbreak used and destroyed the usefulness of the tablet for some.
He was probably intending to say something along the lines of him not updating to 8.1 until after someone makes a new jailbreak for it.
If you can live without the jailbreak, thats fine. Windows store is a bit too limited in my opinion, but it will grow (still gutted they blocked access to both localhost for network connections and COM ports in windows apps though).
SixSixSevenSeven said:
I think he is referring to the lack of jailbreak on 8.1 for unsigned desktop apps - a feature which should have been in the OS from the start, instead microsoft wasted time patching the exploit the jailbreak used and destroyed the usefulness of the tablet for some.
He was probably intending to say something along the lines of him not updating to 8.1 until after someone makes a new jailbreak for it.
If you can live without the jailbreak, thats fine. Windows store is a bit too limited in my opinion, but it will grow (still gutted they blocked access to both localhost for network connections and COM ports in windows apps though).
Click to expand...
Click to collapse
Ah! Gotcha. It slipped my mind that the jailbreak for unsigned apps not working in 8.1 is a valid reason for not upgrading, so I was thinking that he was waiting for something to make the upgrade, itself, even easier. Thanks for the clarification.
@Osprey00 - is there a direct link perhaps
aooga said:
Could someone please post instructions on how to decrypt the registry values? The link that was posted is down. Thanks.
Click to expand...
Click to collapse
Sure. There are a few different ways to do it. In order of simplest to most complicated...
METHOD 1 - Can be done solely from Windows RT (any version):
1. Follow these instructions to create a batch file.
2. Run the batch file on the tablet to get your key.
3. Either write the key down or right-click anywhere in the window, select Mark, highlight the key, right-click again (which will copy the key to the clipboard), paste the key into a text file and then copy that text file to another computer or backup drive.
4. Optional, but recommended: Check that the key is valid by inputting it into a key checker, such as The Ultimate PID Checker. If it tells you that the key is invalid, then try one of the other two methods.
METHOD 2 - Requires regular, non-RT Windows (XP/Vista/7/8):
1. In RT, open the charms bar, click Search, enter "Regedit" and run Regedit.
2. Export HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion to a .reg file.
3. Copy that .reg file to your non-RT Windows.
4. On your non-RT Windows (all remaining steps will be done there), right-click the .reg file and choose Edit. Change "CurrentVersion" to "CurrentVersionRT". Re-save the file.
5. Double-click on the .reg file and import it.
6. Download and install WinTK.
7. Run WinTK, paste "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersionRT" (without quotes) into the field and press the Decrypt button.
*If, for some reason, WinTK won't run, you can try this: download and unzip Produkey, run Regedit, export your CurrentVersion key to a backup .reg file, change the key name in your RT .reg file from "CurrentVersionRT" back to "CurrentVersion", remove all values in your RT .reg file except for DigitalProductId and DigitalProductId4 (make sure that they're NOT the ones under the DefaultProductKey sub-branch), import that (thus overwriting your Windows key with your Windows RT key), run Produkey, write down the Product Key, then import the backup .reg file to restore your Windows key (important, obviously).
8. Write down the product key.
9. Optional, but recommended: Check that the key is valid by inputting it into a key checker, such as The Ultimate PID Checker. If it tells you that the key is invalid, then try one of the other two methods.
10. Optional: Open Regedit again and delete the CurrentVersionRT key, just to clean up.
METHOD 3 - Can be done solely from Windows RT, but only on 8.0 (won't work on 8.1 Preview or 8.1 RTM) and is more complicated than Method 1:
1. Download and unzip the RT jailbreak tool.
2. Run RunExploit.bat. Choose 'R' from the menu. Let it finish, then press any key when it asks you to.
3. Download and install Win86emu.
4. Download and unzip Produkey.
5. Open the charms bar, click Search, enter "Regedit" and run Regedit.
6. Export HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion to a .reg file.
7. Find the Win86emu tile (icon is "x86") on your Start screen, flick down on it to bring up the options bar and tap Open File Location... or, at the Desktop, you can browse to C:\ProgramData\Microsoft\Windows\StartMenu\Programs\win86emu.
8. Double-tap the "x86 Registry Editor" shortcut.
9. In that registry editor, import the .reg file that you exported in step 4. This will import the settings into the special x86 registry that the emulator created when you installed it and which all x86 programs (including Produkey) will think is the real registry.
10. Double-tap the "Run x86 Program" shortcut.
11. Browse to and select the produkey.exe that you unzipped in step 2.
12. Find the Product Key listed for Windows in the window that appears and write it down. If nothing appears, click on Select Source and verify that it's searching the local computer (top-most radio button).
13. Optional, but recommended: Check that the key is valid by inputting it into a key checker, such as The Ultimate PID Checker. If it tells you that the key is invalid, then try one of the other two methods.
If one method doesn't seem to work for you, try one of the others.
Osprey00 said:
Sure. There are a few different ways to do it. I'll describe two...
...
Hopefully, I didn't forget any steps from either of those methods.
Click to expand...
Click to collapse
Thanks!. Now just waiting to download the iso. Its taking an age.
EDIT: mydigitallife was hacked...thats why the links are down.
aooga said:
Thanks!. Now just waiting to download the iso. Its taking an age.
EDIT: mydigitallife was hacked...thats why the links are down.
Click to expand...
Click to collapse
thanks for the info. was about to search for reasons. hacked by MS?
derausgewanderte said:
thanks for the info. was about to search for reasons. hacked by MS?
Click to expand...
Click to collapse
Yeah I was clueless why it wasn't working, so I just looked at their facebook page.
Would putting a link like this on XDA be considered warez? If not, can someone who has already downloaded the ISO with drivers upload it somewhere? There is no way I'm waiting till Oct. 16
Good morning all.
So I installed the 8.1 preview through the store when it first came out a few months ago with no problems. Last night I went to try to move over to the official 8.1 release by going to the store then opening the browser then clicking on the link to take me back to the store to retrieve the official update through the store. The store update "application" never showed up(even after a few restarts and repeating the process). I thought it was strange so I said "screw it, i have nothing important on here" and decided to do a full/clean restore.
I plugged the charger in, let it go about its business and walked away. I came back 2 hours later and the screen was black(no "restoring windows" progress"). Let it sit for another hour in case it was doing something I just wasnt seeing. Came back and decided to hit the power button. Screen turned on with the "Surface" start up logo and then I got this error message.
http://i.imgur.com/Q37Af1a.jpg
Now I am stuck in a boot loop where if i hit "ok" it just restarts and brings me back here.
Of course I never made a 8.1 recovery USB. I have the touch keyboard and access to a USB keyboard too.
Any ideas/direction/thoughts AT ALL are greatly appreciated.
EDIT: I was considering using my colleagues RT to create a recovery image to attempt to get this guy booting but it seems as though this is a bad idea due to his SN being copied over to my RT and causing issues. Am I correct in assuming so?
The CD key ought to come from flash ROM, but it depends on how the recovery image works, which I don't know >.<
If you can use his recovery image to boot to command prompt, you can mount your SSD's registry hive and dump the product key data, then decode it on a Windows PC. Then after recovering with the image, even if the product key ended up copying your colleague's Surface's key, you could just go to System and click "Change product key" and type your own key. (In this situation, the desktop will likely be black, a sign that Windows was unable to activate. Changing the key to yours will fix that, of course.)
I'm not saying that this is easy or anything, but this ought to work, with my understanding of Windows NT.
Note that you don't need to bother decoding the registry data if you notice after recovering that your product ID in System is different than your colleague's, and it also says that Windows is activated. This would mean that the recovery image grabbed your CD key out of flash ROM.
EDIT: I guess what I meant to say is that when you boot to command prompt, run regedit. In regedit, go to HKEY_LOCAL_MACHINE then File/Load Hive. Find your system hive on your SSD, which may be on a different drive letter than usual, in somewhere like Z:\Windows\System32\config\SYSTEM. Give it some name like "meow". Find the subkey meow\SOFTWARE\Microsoft\Windows NT\CurrentVersion. Go to File/Export and export that to a .reg file on your USB stick. If there is an option to do so non-recursively (I forget, and I'm on my iPad), use it because that key is big. Once you've backed it up, you're safe to recover, because now you have everything needed to find out your old key if required.
If in fact you do need to use that .reg file to determine your old key, let me know so I can help you out. Some tricks will be required to proceed.
Melissa
munsterrr said:
Good morning all.
So I installed the 8.1 preview through the store when it first came out a few months ago with no problems. Last night I went to try to move over to the official 8.1 release by going to the store then opening the browser then clicking on the link to take me back to the store to retrieve the official update through the store. The store update "application" never showed up(even after a few restarts and repeating the process). I thought it was strange so I said "screw it, i have nothing important on here" and decided to do a full/clean restore.
I plugged the charger in, let it go about its business and walked away. I came back 2 hours later and the screen was black(no "restoring windows" progress"). Let it sit for another hour in case it was doing something I just wasnt seeing. Came back and decided to hit the power button. Screen turned on with the "Surface" start up logo and then I got this error message.
http://i.imgur.com/Q37Af1a.jpg
Now I am stuck in a boot loop where if i hit "ok" it just restarts and brings me back here.
Of course I never made a 8.1 recovery USB. I have the touch keyboard and access to a USB keyboard too.
Any ideas/direction/thoughts AT ALL are greatly appreciated.
EDIT: I was considering using my colleagues RT to create a recovery image to attempt to get this guy booting but it seems as though this is a bad idea due to his SN being copied over to my RT and causing issues. Am I correct in assuming so?
Click to expand...
Click to collapse
If you recover using an 8.1 recovery image form somebody else it won't mess with the keys. Worst case is that you may have to activate and you do not have a key. If you look at this post by Osprey you will see how to get the key from a 8.0 installation. That won't help you of course unless you have access to the registry and hive as Melissa suggested.
I actually recommend you use an 8.0 image to recover your RT and then upgrade. The only thing you have to do is get the image and "burn" it to a thumb drive. There are no steps required to obtain your key. Make a bootable thumb drive with an image you can download from here and start from scratch. Your system will automatically activate going this route. I've done this several times to switch between Preview 8.1 and 8.0. Follow the instructions above from Osprey's post to obtain your key just in case you do need it sometime in the future. Then you upgrade to 8.1 (nothing necessary in terms of activating this way).
Here is a post with a link on how to recover with a USB recovery image. One important point when you put the image onto the thumb drive is that it has to be bootable. Use UltraIso or Rufus to put the image onto the thumb drive (FAT32 formatted).
munsterrr said:
Any ideas/direction/thoughts AT ALL are greatly appreciated.
Click to expand...
Click to collapse
Apparently this is a widespread problem, and one of the reasons I haven't upgraded to 8.1. Heres the solution: http://kickthatcomputer.wordpress.com/2013/10/19/windows-rt-8-1-upgrade-fails-with-boot-configuration-error/
Thanks for the replies everyone. My colleague was able to upgrade to 8.1 on his RT with no problems. We were able to copy the image(minus recovery partition) over to a thumb drive and I was able to boot from that and eventually upgrade myself.
ok! where to even start...
I like many got this 2in1 at wal-mart and I live it. unfortunately I like many am not yet familiar with the new UEFI bootloader bios SOC stuff
heres what I do know and please correct me if im wrong. also please tell me if this 2 in 1 is and can be flashed the same as the asus t100
ok the Flexx11 has a bayntrail-t CR quad core processor 1.33-1.83ghz model Z3735F the t100 is3740
11.6" screen ips touchscreen at 1366x768 res
Efun is the corp and yifang vers.NX1106.1.02.008\139
THE BIOS IS YFG0315009112
it is a 32bit EFI bootloader
the reason I mention all of this is I have tried several times to dualboot androoid and each time ruined the computer and had to return it and I simply no longer wish to return it and love it to much to get something else
the first try the time began to lag and was unfixable for some reason the second time i somehow lost the keys booting and formatted wrong or something and the tablet bricked it would remain black with keyboard lit and no button combo could get it back no boot at all.
I am currently using AMIDUOS to run android kitkat and I love it but from what I understand it isnt compatible with win10 and really still isnt the same as the full android being on the tablet although really really close and awesome
but honestly I have been doing this stuff for years and now with this new windows secure boot and system on a chip stuff im lost
ever get anywhere with this?
I'm curious as well.
It has to be possible. I say that because I recently owned a ChuWi dual-boot device with the same Baytrail processor and SOC.
I wonder if it wouldn't be possible to take a system dump from one of the chuwi dualboot devices and flash it to the nextbook.
Sent from my Ascend Mate 2 using XDA Free mobile app
I'm also interested in doing this. It appears that the Nextbook Ares has the same hardware (minus 1GB RAM) but has Android. I contacted Nextbook to see if I could get a copy of the Ares Android firmware but was denied. If someone with the Ares could upload a backup that would be helpful.
I was finally able to get this working using this method...
https://hitricks.com/guide-how-to-dual-boot-remix-os-with-windows-uefi-legacy
So far I was able to get it to boot from a partition on the main drive as a test. In the process of installing to a secondary partition on my sd card. We'll see how it goes.
I wasnt able to get the boot menu that he shows but after going through the steps I then had an Android OS boot option in the bios boot menu. Pretty awesome! Runs great. Tried running Dead Trigger 2 as a test with full graphics. Ran perfectly.
I just bought one of these yesterday, and it shipped with Windows 10 Home 32-bit. I'm trying to install the 64-bit version but it won't boot from USB. Turns out it doesn't support 64-bit OSes. Where can I find recovery images for this? I messed up and now I don't have audio or touchscreen drivers.
64 bit processor?
I just bought one of these yesterday, and it shipped with Windows 10 Home 32-bit. I'm trying to install the 64-bit version but it won't boot from USB. Turns out it doesn't support 64-bit OSes. Where can I find recovery images for this? I messed up and now I don't have audio or touchscreen drivers.
Click to expand...
Click to collapse
Alright, I'm slightly confused now. Looking at system specs for mine it says it has an x64 based processor. Doesn't that mean it should be able to handle 64-bit OS? Even though it comes with 32-bit? If possible I would like to put 64-bit on it as well, but I'd like to be sure that that's not going to break it.
GeneticJulia said:
Alright, I'm slightly confused now. Looking at system specs for mine it says it has an x64 based processor. Doesn't that mean it should be able to handle 64-bit OS? Even though it comes with 32-bit? If possible I would like to put 64-bit on it as well, but I'd like to be sure that that's not going to break it.
Click to expand...
Click to collapse
It just won't boot the USB. At all. Unless it's 32-bit.
rowdyrocket said:
I was finally able to get this working using this method...
https://hitricks.com/guide-how-to-dual-boot-remix-os-with-windows-uefi-legacy
So far I was able to get it to boot from a partition on the main drive as a test. In the process of installing to a secondary partition on my sd card. We'll see how it goes.
I wasnt able to get the boot menu that he shows but after going through the steps I then had an Android OS boot option in the bios boot menu. Pretty awesome! Runs great. Tried running Dead Trigger 2 as a test with full graphics. Ran perfectly.
Click to expand...
Click to collapse
I'm loving Remix OS on here with dual boot. Having some issues though and I really want this to work.
Main and I mean main issue is no sound at all, no rotation is next in line and Bluetooth isn't working. Everything else works great.
This is so awesome its like Android lollipop with windows desktop functionality. Now if I can get the bugs fixed I will be in android hog heaven.
GREAT FIND BRO!!!!! EXACTLY what I was looking for maybe even better than.
for those interested here is the XDA section for all things REMIX OS
http://forum.xda-developers.com/remix
By the way for those who may want to know I installed dual boot onto the hard drive it went with no issues.Here's some tips for flexx 11
1. I used a partition manager such as easy partition manager to partition the C: drive regardless of what the tutorial said. Couldn't use windows disk management. I deleted the recovery for an extra 5 gigs (make a backup if you do) I used about 19 gigs from the C: drive and made an E: NTFS.
2.Also do not use the remix files from that tutorial use the ones here from the main site http://www.jide.com/remixos-for-pc they are newer and the ones from the other post where incomplete. Also the newer ones on the site now include OTA updating which is totally awesome.
3. I'm hoping this will help someone..... After I was all finished I expected it to dual boot as any other dual boot restart and then i would see options for the OS's not the case here I got stuck on this I was using easy BCD and trying all sorts of stuff, once I looked at the tut a little closer I realized you don't need any of that. Once your all done do a restart and it will go back to windows as usual. Now go to settings, then recovery, then advanced startup and choose from devices I think its the second option on the left list. There you will find Android OS click that and it will take you to your dual boot options. Sounds a lot more complicated than it really is. But believe me once you know this your better off.
And that's all I've got please and I mean please post here with any fixes especially for sound and if you have questions I will try to help.
Thanks
PS: I AM GETTING OCASIONAL LOCK UPS, MEANING THE OS FREEZES AND I HAVE TO RESTART BY HOLDING POWER.
Im not sure if this is good news or not...
Using the methos outlined I was not able to get audio bluetooth autorotate and other things to work but after a bit of digging I found out that remix os has an image specifically for nextbook baaytrail (Our PC) here: http://www.jide.com/remixos/devices
click other upper left.....
I cannot find instructions to install this though and using the other install instructions from here fail because the only part of the file to replace is the system image.
I also attempted the other install methods and easy BCD does not work for this PC
So if anyone can help to install this file specifically for our computer as well as verify that it works and what works and how you installed would be great
OK this is really cool I have made headway sort of.
I have installed kit kat android-x86-4.4-r3.img using the Androidx86-Installv24-5800.exe installer and i have rotation, root and it works pretty good for the most part wifi works great so far no bluetooth, it freezes during shut down and the major issue as in most cases is the sound. Im not sure about the camera now that I think about but i will check and report back here.
I really want the sound working on this and I woud be bigtime happy this forum could be solved as far as im concerned
From what I understand there is a bug with baytrail and linux where the spp port is pointed automatically to the usb or something. but for the life of me after weeks of scouring the internet cannot find a laymens guide to a simple fix for this. I'm really not even sure there is one because I'm yet find a rock solid confirmation of a solution
Update: camera doesn't work either
So far the 4.4.3 port is the best. I just can't seem to find any help whatsoever so its looking like so close yet so far away. Its a pure shame that audio and a few other major bugs are the only things in the way of this being a fully working and easy dual boot method.
I have bought a nextbook flexx10 but am unable to install remix OS. I have followed all the steps highlighted before.
1. partitioned the drive with gparted to make a 10G NTFS drive
2. downloaded android x86 5.1.1 iso and remix iso from jide website.
3. used android installer and android 5.1.1 iso to install the image
4. used 7zip to uncompress the remix iso
5. then copied over the 4 necessary files from remix to the drive to the android drive
6. copied over grub.cfg
Now, I do see the entry for androidOS but when I select that, I just get a message at the center of my screen that says "AndroidOS boot failed" and a blue OK button in DOS like font. thats it.. I am interested in knowing if any additional BIOS settings needs to be tweaked.
furthermore, I have tried installing android x86 6.0 by formating the same partition as ext4. All proceeded well and i got to the last screen that said "Run android-x86 now" or reboot. I removed the USB and was able to get into android. (some missing functionality). But when i reboot into windows and try to boot into androis, I get the same message of Andoid boot failed..
Thus I need to know if there's some BIOS settings related to permissions or sorts that i'm missing.
thanks
murlig123 said:
I have bought a nextbook flexx10 but am unable to install remix OS. I have followed all the steps highlighted before.
1. partitioned the drive with gparted to make a 10G NTFS drive
2. downloaded android x86 5.1.1 iso and remix iso from jide website.
3. used android installer and android 5.1.1 iso to install the image
4. used 7zip to uncompress the remix iso
5. then copied over the 4 necessary files from remix to the drive to the android drive
6. copied over grub.cfg
Now, I do see the entry for androidOS but when I select that, I just get a message at the center of my screen that says "AndroidOS boot failed" and a blue OK button in DOS like font. thats it.. I am interested in knowing if any additional BIOS settings needs to be tweaked.
furthermore, I have tried installing android x86 6.0 by formating the same partition as ext4. All proceeded well and i got to the last screen that said "Run android-x86 now" or reboot. I removed the USB and was able to get into android. (some missing functionality). But when i reboot into windows and try to boot into androis, I get the same message of Andoid boot failed..
Thus I need to know if there's some BIOS settings related to permissions or sorts that i'm missing.
thanks
Click to expand...
Click to collapse
Sorry for the late reply, use the installer and create a separate drive using C: like a D: or E: and get android 4.4 the .IMG that should work for you and the installer should do everything for you.
So use the uefi android installer after you partition a drive to load android 4.4 the uefi IMG
Its just going to piss you off though because there's no audio and seemingly no way to fix it, which is a crying shame ��
P.S. typically secure boot is off in the bios on this machine, but if by any chance you turned it on or the newer ones come that way make sure it is off or this will not work.
UEFI Settings
So I can get to a menu with 6 icons (2 rows and 3 columns) by running the "shutdown.exe /r /o" command and then going to Troubleshoot>Advanced Options>UEFI Firmware Settings and clicking restart. The problem is that when I get to this menu the touchscreen and keyboard do not work, and I can only move the highlighter up and down, not left and right. Hopefully one you guys have figured this out. I contacted the Nextbook support desk and they were no help at all.
korycooper said:
So I can get to a menu with 6 icons (2 rows and 3 columns) by running the "shutdown.exe /r /o" command and then going to Troubleshoot>Advanced Options>UEFI Firmware Settings and clicking restart. The problem is that when I get to this menu the touchscreen and keyboard do not work, and I can only move the highlighter up and down, not left and right. Hopefully one you guys have figured this out. I contacted the Nextbook support desk and they were no help at all.
Click to expand...
Click to collapse
Okay. So I was able to test this one of my co workers Nextbook and it seems like its a problem with mine.
This might be beneficial for us Flexx 11 users. It's a full port of Remix 2.0 to the Ares 8 with everything working except the camera rotation issue. Very promising. I've heard the hardware is similar. Working on attempting to install on mine. Anyone else tried it?
http://forum.xda-developers.com/remix/supported-devices/port-remix-os-2-0-nextbook-ares-8-t3498015
Hey guys,
NextBook Flexx 11, 64Gb, NXW116QC264, Windows 10
I'm really interested in trying to install Remix OS in Dual boot. However, in my trials, I goofed up my tablet. I found an image, but it turned out to be a Windows 8.1 image, and it wiped everything from my tablet. I had originally had Windows 10 on it.
Could someone perhaps be able to send me the recovery partition of their Nextbook; as long as they had Win10 installed. Maybe if I dump a Win10 recovery partition, I can do a repair on it and restore Win10 to the system.
I can't find the stock/factory rom for the Win10 version of the Flexx.
Thanks in advance,
Kori
KorishanTalshin said:
Hey guys,
NextBook Flexx 11, 64Gb, NXW116QC264, Windows 10
I'm really interested in trying to install Remix OS in Dual boot. However, in my trials, I goofed up my tablet. I found an image, but it turned out to be a Windows 8.1 image, and it wiped everything from my tablet. I had originally had Windows 10 on it.
Could someone perhaps be able to send me the recovery partition of their Nextbook; as long as they had Win10 installed. Maybe if I dump a Win10 recovery partition, I can do a repair on it and restore Win10 to the system.
I can't find the stock/factory rom for the Win10 version of the Flexx.
Thanks in advance,
Kori
Click to expand...
Click to collapse
Just to be clear...(and this goes for everyone wondering in the future) it was windows 10, from the factory??? Last i checked
they only shipped with windows 8.1 or android, depending on the model...If not and you put windows 10 on there, back when it was free, you just use the media creation tool from Microsoft to update windows 8.1 to Windows 10 (after restoring windows 8.1)... it can do this because most tablets have unchangeable hardware, so no cd key is required...it's like how your md5 hash verifies your downloaded files, Windows provides Microsoft with your hardwares md5 hash signature and if it is in the list, then it activates the pc/tablet... but, it only works if you got it free, not if you bought it... if you bought win10 then you will need your cd-key when you re-install, while the other steps are same as above... just note, that for the free upgrade there was NO cd-key, therefore in that instance, if it asked you for a key, you would leave it blank, which you can do in any case, and add your key in from Windows if needed...
And... as for the others having sound issues in Android, I read something about a reason for that having to do with something called an... 'audio stack', I think it was??? Not 100% sure what it meant, but basically, it is designed so the audio hardware only works in windows, I think... (so they can make more money, by making you buy the android tablet separately...)
hope this helps someone who stumbles upon this thread...
Wiebenor said:
Just to be clear...(and this goes for everyone wondering in the future) it was windows 10, from the factory??? Last i checked
they only shipped with windows 8.1 or android, depending on the model...If not and you put windows 10 on there, back when it was free, you just use the media creation tool from Microsoft to update windows 8.1 to Windows 10 (after restoring windows 8.1)... it can do this because most tablets have unchangeable hardware, so no cd key is required...it's like how your md5 hash verifies your downloaded files, Windows provides Microsoft with your hardwares md5 hash signature and if it is in the list, then it activates the pc/tablet... but, it only works if you got it free, not if you bought it... if you bought win10 then you will need your cd-key when you re-install, while the other steps are same as above... just note, that for the free upgrade there was NO cd-key, therefore in that instance, if it asked you for a key, you would leave it blank, which you can do in any case, and add your key in from Windows if needed...
And... as for the others having sound issues in Android, I read something about a reason for that having to do with something called an... 'audio stack', I think it was??? Not 100% sure what it meant, but basically, it is designed so the audio hardware only works in windows, I think... (so they can make more money, by making you buy the android tablet separately...)
hope this helps someone who stumbles upon this thread...
Click to expand...
Click to collapse
I realize this is a dead thread, but I had to chime in... I bought my NextBook Flexx 11 from Walmart 3 or 4 years ago and it shipped with Windows 10 Home, not Windows 8.1... However, IMHO, Windows 10 is a resource hog on this little device. I'm currently looking in to installing Linux...
Hi guys,
I've finally managed to get Windows 10 back to my Lumia 530.. from "bare metal" (really, it looked death at some try-and-fail steps
It will be done in two steps.
First, we need to push it to the 10586.107
The second update we will deploy the "final" version of v1511 - 10586.1176 (the fixed issues betwenn 107 and 1176 are a list of 8pages paper )
WHAT YOU NEED:
- Windows Device Recovery Tool (can ressurect dead phones, when nothing else can connect to it.... )
- The included thor2.exe cmdline tool (find it in the install path of the Recovery Tool).
- The Stock Windows 8.1 (can be downloaded by the tool or by yourself at lumiafirmware com
- IUTOOL.exe (included in the Windows Driver Kit (WDK) or from here, the big Windows 10 Mobile Offline Thread) as well as the perfect prepared first packages:
- the "win10_mobile_offline_updater_v41.wim" provided on this page. YOU need only the files in THIS SUBFOLDER: "3rd Generation\43X-532"
- If you want to prepare further updates or a different phone, you'll need also (comes with IUTOOL.exe) GetDuLogs.exe (I HIGHLY RECOMMEND to run it with your fresh updated device connected to USB), It will rip the update log wich are nice but it also includes a package list, that were updated on your Phone. THIS IS IMPORTANT because these package names are the packages you will need for every device upgrade rollup..
HOW TO:
1st: I believe i took the GUI Recovery tool the first time i succeeded but at my second try it didn't work.. The whole success depends on a few megabytes of free space. So whatever caused this, MY LAST and sucessful try worked after i flashed the Stock FFU with the command line tool thor2.exe using the whole bunch of options:
thor2 -mode uefiflash -ffufile "your_Phones_Stock_Build_imageFile.ffu" -do_full_nvi_update -do_factory_reset -reboot
After the reboot, and you will only succeed by following: Leave the phone at the first Screen (The Welcome, languange selection), connect to USB, let windows install the driver and once connected (when using Windows 10) Remove the device from Devices And Printers otherwise IUTOOL.exe will put out an error and won't work.
now start the update by launching: iutool -V -p e:\folderName (Where All The CABs Are Inside).. You won't get any message on your phone, but IF it fails, IUTOOL will put out an Error - in all my tries within 5 minutes.. YOU NEED TO WAIT for reboot. The Lumia 530 will take around 30minutes until it reboots itself. It boots in the known maintenance mode, takes some time and will come up with Windows 10.0.586.107. Because we didn't went through the OOBE before, either only the Start Screen will be empty or in addition the App list will not show every app - as expected - Easy Fix: If you have the settings app, go to SYSTEM-INFO and launch a factory reset.. If not take the hardware forced way: Hold Volume down AND the power button until it vibrates, release ONLY the button, hold volume down a bit longer to get the phone recognized what you want. When it shows the "!" launch the factory reset by pushing in this row: Vol Up - Vol Down - Power - Volume down..
the keyboard wont work so if you want your backup to be forced while OOBE, you need to make your Wifi Open without password... There is a fix for this issue on the Main Thread for the Offline Update, but i just removed my (in my case) German Keyboard and the englich keyboard worked fine immediately after removing..
The Swiss keyboard was also good for me - but i didn't care a lot - will be fixed with the final Update...
THE OOBE WAY doesn't work any more, seems like Microsoft wasn't amused by this and closed this nice door i just found as my very last idea with this phone. The genius idea.. i felt so cool after that really worked.... Now the last step: don't forget to call "getdulogs -o e:\outputfile.cab" in the cab are the logs as well as the important package list..
The second update is easier, because there is not much you can do... You can find it with normal Update search but - trust me - in the best case it fails with 50 MB too less space... really hard So the difficult part this time is to identify and get your packages. I've searched my 6 disks and finally i'found my phone updates but unfortunately i must have overwritten my get.cmd for 1176 which was a download batch for the files.. ****.. but it's also hard to identify the correct package at Microsoft, i'm tired but here's the little gift, definetely the correct package, you'll find here (i cannot post links, too new ) catalog-update-microsoft-com and seach for "14003.1176". The 2500 MB folder is yours, look for " Windows Mobile 10 Production Bundle - OS 10.0.14003.1176 update for all mobile phone devices", Click "Download to see all package links and download the ones in the log files package list...
I got 168 files, should be more - even if more are not a problem - we don't have any space for maybe resolution packages for other devices. NO
If you have some scripting or programming knowlegde, there are some hints for it below.. Or Contact me if you need help.
Update is easy:
- Factory Reset AND DON'T CONNECT your phone to the Wifi - at no point
- After OOBE - Uninstall absolutely every thing that is able to, delete temp files - these little two things worked fine for me, key point here is NO CONNECTION TO NOWHERE BEFORE.. again, we are fighting for 50 MB, so if it was connected -> do the factory reset before... but do it also if it never was on, because there are few files from the previous update, that will lock us these 50 MB...
Update itself like before, IUTOOL.exe -V -p u:\cabFolder
WHAT YOU NEED TO KNOW... If you like ****, this time you can watch the update progress - IUTOOL.exe forces the normal windows update so it will show progress..
reboot to maintenance mode - will all work fine BUT THE FIRST REBOOT - keep cool, and enjoy the blue flashing Disco Screen you will get - you can try to reboot, but it didn't help on all my 2 deployments. what it needs (was a surprise for me, and it helped twice) is a simple factory reset.. like i wrote in the previous update. This time you will have to use the hardware way i mentioned.. Thats all.. One little issue, i couldn't fix yet, but i don't care.. MSN News App, And the Weather App are only links to the store and for whatever reason the store thinks it is already installed, Take Foreca Weather... Everything else works fine.. Keyboard as well with native german on my side
Hopefully i mentioned it detailed enough... worked TWO times for me now.. 14393 update needs too much space, don't even think about it
I'm currently slowly reading into Deploying and developing customized windows mobile images, not that i wan't to run it on my 530 but maybe i'll find somehing...
Greetings, Stephan.. Below some hints for the downloads, if you want to script it...
THE SECOND UPDATE is based on the package list i've ripped. With this and the version number (this is tricky, because the internal Build will not stay at 10586, so you will find the update by searching for "Windows Mobile 1176" or sth near.. look for a Folder size of ~2500 and the update rollup .1176 - i'm not really sure - it was some near 14003.1176 (The Build number MUST BE LOWER than 14393. You'll either some creative knowledge like programming or a lot of patience and motivation to find all your 127 packages and download it manually.. i copied the the whole filename's list and the prefix to have a download link and then i wrote a little C# to compare my needed package List with the whole build list from microsoft.. i added also a "wget -c ". It's even more complicated... 2 different "base" links (i just took both links - only the correct one will work. And finally - the last complication is - there are downloads "tagged" with a "cbs" as well as with "cbsu" in the filename FOR MOST PACKAGES, i've not tried to find what it means - but however i decided to take the CBS because their filesize was realisic, cbsu are way too small, may be these are one fixes from last update, and not the whole rollup - what we need....
..the keyboard wont work so if you want your backup to be forced while OOBE, you need to make your Wifi Open without password...
Click to expand...
Click to collapse
Forget that... you cannot apply your backup at this time, even with internet connected... The hard point would be to login with Microsoft
can you post screenshots?
I followed that whole guide but I didn't succeed. It was then that I deleted the .cab files from languages that I'm not going to use and I remade the whole process, being transferred 31 files. I crossed my fingers and received the full storage message but the update followed and to my surprise the phone restarted and updated.
Someone to helpme with efiesp.bin partition?
Hello,
im trying to understand ur method but im not that into microsoft stuffs so, what do u mean with:
" now start the update by launching: iutool -V -p e:\folderName (Where All The CABs Are Inside) ? "
I get it done with more than 1Gb of free storage !
so I start with your steps u provided above and I got lost honestly.
-I have lumia 530 Dual SIM (1019) previous build was 8.1 I don't recall OS version but it was the latest, so yeah I searched for more information and I found this thread https://forum.xda-developers.com/windows-10-mobile/guide-win10-mobile-offline-update-t3527340/ of this glorious man @hikari_calyx
-I tired to intall W10 even the method says that not supported for 4gb devices, and it was really a fail because following his steps ended up with fail to update due to low storage, then I tried to delete anything I could, but again it fails for just 140mb or so... an idea pops up in my head which updating after a hard reset so the OEM apps won't get installed, and
here are the steps
1- go to the link provided for @hikari_calyx and follow the steps (make sure to download the .cab files) until it fails to update.
2- perform a hard reset to your phone (power off, press vol - and power button together after the vibrate release ur finger from power button and keep pressing vol - then in order : vol - vol + power button vol - )
and don't pass the language selection screen just keep it there.
3- Now go and update it like you just did before hard reset, it will take a lot of time just plug it to a power source and keep it cold, maybe more than 1 hour.
4-hurry it boot up you might face a problem in "Almost done.." screen, so the solution is : lock the screen and turn it on again, once u slide the lock screen up and before the app reloads keep pressing the "win" button it will open "one handed mode" then bring down the notification center and press anything (maybe win button I don't recall) until it goes to home screen (not 100% sure what I have done it was so random lol)
Congratulations u have W10 with a lot of storage.
STALKER18 said:
I get it done with more than 1Gb of free storage !
so I start with your steps u provided above and I got lost honestly.
-I have lumia 530 Dual SIM (1019) previous build was 8.1 I don't recall OS version but it was the latest, so yeah I searched for more information and I found this thread https://forum.xda-developers.com/windows-10-mobile/guide-win10-mobile-offline-update-t3527340/ of this glorious man @hikari_calyx
-I tired to intall W10 even the method says that not supported for 4gb devices, and it was really a fail because following his steps ended up with fail to update due to low storage, then I tried to delete anything I could, but again it fails for just 140mb or so... an idea pops up in my head which updating after a hard reset so the OEM apps won't get installed, and
here are the steps
1- go to the link provided for @hikari_calyx and follow the steps (make sure to download the .cab files) until it fails to update.
2- perform a hard reset to your phone (power off, press vol - and power button together after the vibrate release ur finger from power button and keep pressing vol - then in order : vol - vol + power button vol - )
and don't pass the language selection screen just keep it there.
3- Now go and update it like you just did before hard reset, it will take a lot of time just plug it to a power source and keep it cold, maybe more than 1 hour.
4-hurry it boot up you might face a problem in "Almost done.." screen, so the solution is : lock the screen and turn it on again, once u slide the lock screen up and before the app reloads keep pressing the "win" button it will open "one handed mode" then bring down the notification center and press anything (maybe win button I don't recall) until it goes to home screen (not 100% sure what I have done it was so random lol)
Congratulations u have W10 with a lot of storage.
Click to expand...
Click to collapse
@STALKER18 did you manage to get 1703 or 1709 on the Lumia 530?
Someone can help me with efiesp.bin file dumped with WPInternals?