Database Info

Help recovering Asus P527 BAD FLASH!! (GSMFFS.NB0)

Hi,
Help needed to restore GSMFSS.NB0 cause flash stops with message,
"GSMFSS at 0x13000000
GSM Doesn't exist
Spin Forever
Use (format All) instead."
Is there a way to format all rom?
Thanx

If you have an original RUU (from either manufacturer or vendor), you could try that and see if you can flash an official rom. First thing would be if you can get into bootloader. If you can't, then I am afraid that you got yourself a pretty expensive paperweight.
However, if you can get into bootloader, there is still hope...
I am sorry but I cannot guide you through the bootloader process for your phone, but I do not own that device. However, this seems to be a way to possibly recover most phones I have seen so far.

Well if press "volume down+Left OK+Reset" i go into this main menu option, with Xand, Nand Format, diagostic,etc but when i press the respective key it does nothing... the GSMFFS error appears when i try to flash from the original RUU. So the device is comunicating, and i can access IPL- insert usb cable...
Can i access the device with rom with P525 Kitchen Tool?
Thnx

santosru said:
Well if press "volume down+Left OK+Reset" i go into this main menu option, with Xand, Nand Format, diagostic,etc but when i press the respective key it does nothing... the GSMFFS error appears when i try to flash from the original RUU. So the device is comunicating, and i can access IPL- insert usb cable...
Can i access the device with rom with P525 Kitchen Tool?
Thnx
Click to expand...
Click to collapse
Well, that is fairly good news... you can apparently access bootloader, so not all hope is lost. As far as the P525 kitchen, you always have to be extremely careful when using a program that was designed to work with a different device from yours.
Have you tried using the RUU after getting the device in bootloader mode? In other words, get it to this status, connect the USB cable to the computer (establish a connection), and then try to use the RUU. It could be that the GSMFFS error could be from the RUU not being able to put the device into bootloader.... It might just work... Good luck!

I got this out of an Asus Russian forum
"Proshivatsya in expert mode, though, and so like to ask
But if you do not return startanet through the expert mode
Hold down, press and hold OK (side button), tyknut stylus reset.
Wait for the appearance of the caption "IPL: Insert USB CABLE"
On the PC run P527FUU.exe, in the back left corner click on the program icon, choose the Expert Mode
Connect the cable and click Update
Do not guarantee the accuracy of keystrokes, but in the manual for the R527 is written that way. "
Here is the link for the site (already google translated)
http://translate.google.com/transla...earch?q=GSMFFS&hl=en&rlz=1C1GGLS_enUS310US310
Browse through some of the posts and see if you can come up with something. From what I have read the "Format All" is accomplished only via "Expert Mode" described above. If you can access that, then you might have a chance to restore the device.

egzthunder1 said:
Have you tried using the RUU after getting the device in bootloader mode? In other words, get it to this status, connect the USB cable to the computer (establish a connection), and then try to use the RUU.
Click to expand...
Click to collapse
Yup, the error appears just 5sec after pressing update button...
I guess the problem resides on the fact that gsmffs.nb0 file is missing from the rom, cause RUU log shows:
ClientDriver.dll Attach
g_Driver=0 g_RTimeout=0 g_WTimeout=0 g_DebugON=0 g_PurgeTx=0 g_PurgeRx=0 g_WaitRx=0 g_splitReadAck=0 g_splitReadAckSize=0
Client_QueueJob(): FeatureID=3, FileName=temp3, HeaderLen=0
Client_QueueJob(): Assumed flashing a Asset Data File because there is no header
Client_QueueJob(): FeatureID=3, FileName=temp2, HeaderLen=0
Client_QueueJob(): Assumed flashing a Asset Data File because there is no header
Client_QueueJob(): FeatureID=17, FileName=temp4, HeaderLen=0
Client_QueueJob(): Assumed flashing a Asset Data File because there is no header
Client_Initialize(): Model=(null), Language=0
Client_Initialize(): Skipping the model verification check
Client_Initialize(): Skipping the language check
Client_Initialize(): rebooting device...
Client_FormatDiskEx(): Type=3 Backup=c:\gsmffs.nb0
OpenComPort(): Wceusbsh
GetWceusbshDevicePreset
OpenComPort(): Wceusbsh \\?\usb#vid_045e&pid_00ce#5&1e9a0cb1&0&1#{25dbce51-6c8f-4a72-8a6d-b54c2b4fc835}
Windows Closing end
OpenComPort(): PC is XP plus
OpenComPort(): PC is XP plus
OpenComPort(): cto.RIT=0 cto.RTM=0 cto.RTC=0
OpenComPort(): cto.WTM=0 cto.WTC=0
OpenComPort(): sucessful
SendFormatDisk() cmd=3
GetEachROMSize(): GSM size=5242880
GetEachROMSize(): OS size=70254592
GetEachROMSize(): EXTROM size=1048576
SendFormatDisk():USBWritePacket
SendFormatDisk(): USBReadPacket
...
And then it hangs on the last command, it should return
SendFormatDisk(): receive format ok
ReadBackup(): Get a packet Remain=65536
...
I assume C:\ is on the pda not my computer right? I guess this file is missing. Very frustating since there's no tools available for my P527...

Look for a Rom dump from this device and see if you can find the missing file.
I think that the C:\ is actually in the computer. Even if the PDA is recognized as external storage, it would probably take a different letter (unless your HDD has a different letter assigned to it). But in bootloader mode, it is not recognized as storage.
Also, look for another RUU (for this device) and see if it works. Good luck

same problem
santosru said:
Well if press "volume down+Left OK+Reset" i go into this main menu option, with Xand, Nand Format, diagostic,etc but when i press the respective key it does nothing... the GSMFFS error appears when i try to flash from the original RUU. So the device is comunicating, and i can access IPL- insert usb cable...
Can i access the device with rom with P525 Kitchen Tool?
Thnx
Click to expand...
Click to collapse
hi santosru,
i am also having same problem were you able to solve it? where you able to select the options?

Ok, this may not work for everyone but it worked for me. I CAN NOT take credit for any of the work. I can how ever offer a very sincere thank you to developers who have brought 6.5 to the P527.
Download SCHIST 21864 from http://forum.xda-developers.com/showthread.php?t=506417
use the P527FUU that is included and check both OS and GSM.
set the OS path to ????/SCHIST_21864_clean\flash.dio.nb0
set the GSM path to ????/SCHIST_21864\EXT GSM(IND)\GSM.dio.nb0
now you need your phone screen to show the IPL: USB Cable message.
turn key lock on, press in on the scroll wheel (left side of phone), press and release the soft reset button with stylus, release the scroll wheel and press the left OK button. it may take a times to get it right but you should get the IPL: screen up. (I actually have to release the scroll wheel then move it down, release and then press the OK button)
insert the usb cable, click the ???? button in P527FUU this should "fix" you.
after it's complete even if phone hangs at the blue Asus screen you can download the correct Asus flash and use the installed included from Asus in advanced mode to restore your phone to WM 6.1 for your area.
if this helps anyone let me know.
IMPORTANT: I just learned that the computer you flash with has something to do with the bad flash. I needed to reflash the original 6.1 back to my phone and it locked up again on my computer, I tried my girl friends and it worked fine using the above steps.

[Q] I think I bricked it??

I think I bricked my Viewsonic G Tablet. I was running VEGAN perfectly then I decided to jack around with Ubuntu the Karmic link found here on XDA under "Ubuntu on G tablet" Did everything the best I could, failed, failed.. booted into clockwork, went to factory reset, no back up found anywhere, formatted EVERYTHING (data, cache, rom) If I plug the USB cable into my laptop it reads as H drive but when I click on H drive it says "please insert a disk in H:" if I put anything on the sd external, I can't get my tablet to even read the external. Every time I click on "mount SD ext" it just says failed. Without clockwork, I just get big red letters "Magic value mismatch" Please tell me I didn't brick it good...
I can get the roms or the zip files etc on the external SD but without being able to boot to or from it, I'm lost.
Thanks

http://forum.xda-developers.com/showthread.php?t=861950
Start there. If you need more help search for "nvflash" and you'll find lots of helpful posts.

Thank you for your quick reply! I am afraid to say that I am SOOOO ignorant on this stuff. I followed the link and it had a lot of information on running the nvflash (I think when you didn't have clockwork installed??) It said stuff about lots of stuff I don't understand, I am SO SORRY to be so basic. I do run Linux Ubuntu 10.10 and Windows 7 on a dual boot with my machine so we can work in either environment. I donwloaded the prereqs from the drop box so I have the files along with two different ROMs, but I can't get the Viewsonic tab to even recognize (via my laptop) the internal SD card. Then the External SD card either so I do not know of a way to get any of these files to the tablet?
Please continue to help me in the MOST basic way you can, if you will. I would be so VERY grateful and give kudos, thanks, or whatever needed. I just want to make it work.

If you are able to boot into recovery then go to advance, then select the option to partition your sd card then select 2048 then 0. See if that helps to get your internal sd card recognized. That has helped me before.
Just an idea. No guarantees it will work.

Start by relaxing and taking a few deep breathes. The instructions there are about as basic as you can get. Main thing istonot get ahead of yourself or read more into it than it says.
I find it easiest to use Linux.
Create a directory to hold the nvflash package.
Extract the nvflash_linux_2010110500.tar.gz archive into the directory.
Extract the nvflash_gtablet_2010110500.zip into the directory.
Put the gtablet into APX mode. From off turn it on while holding the volume down button. You should see the splash screen then it will go black. Plug it into your computer with the USB cable.
Open a terminal window and confirm that your computer can "see" the gtablet by typing "lsusb" command (without the quotes). It should respond with "0955:7820 NVidia Corp.". 7820 means the device is in APX mode.
If all is well at this point change into your nvflash directory and type the following command.
./nvflash_gtablet.sh
Now let the magic happen. In a few minutes you'll be back to factory specs ready to go.

THANK YOU THANK YOU A MILLION times thank you! I can donate to you or XDA via paypal, please let me know how to repay you all! You are wonderful!

No problem. Here to help when I can. If you really feel the need then donate to roebeet (the author of the original instructions).
Have a great day.

K J Rad said:
Start by relaxing and taking a few deep breathes. The instructions there are about as basic as you can get. Main thing istonot get ahead of yourself or read more into it than it says.
I find it easiest to use Linux.
Create a directory to hold the nvflash package.
Extract the nvflash_linux_2010110500.tar.gz archive into the directory.
Extract the nvflash_gtablet_2010110500.zip into the directory.
Put the gtablet into APX mode. From off turn it on while holding the volume down button. You should see the splash screen then it will go black. Plug it into your computer with the USB cable.
Open a terminal window and confirm that your computer can "see" the gtablet by typing "lsusb" command (without the quotes). It should respond with "0955:7820 NVidia Corp.". 7820 means the device is in APX mode.
If all is well at this point change into your nvflash directory and type the following command.
./nvflash_gtablet.sh
Now let the magic happen. In a few minutes you'll be back to factory specs ready to go.
Click to expand...
Click to collapse
THANK YOU!!!!! Man, I thought I had a $400 brick on my hands! I couldn't even boot into recovery! I'll donate to whoever I need to at this point!

These machines are incredibly hard to brick. I've tried ;-)
If you'd like to donate pick one of worthy developers from the GTablet Android Development section and support their work. I use Roebeet's TnT Lite and those instructions above were first written and posted by him as well, so...
Glad you got it working. Have a great day!

Bricked phone build.prop missing

Hi to all here. i just want to ask anyone what to do with my phone. well first of all, my phone is a sky pantech vega racer im-a760s, not really a match for samsungs popularity but budget wise this is the model for me. it has a dual core. now my problem starts when i started editing the build.prop in its system (tweaked for some texting problem of limited character sending). of course i know what im doing on that part, but the only thing i didn't think that would happen was, i copied it in my computer, i edited it there, then i saved it as "all" in file type so it wont become a ".txt" format. but when i placed it in my phone. the file instantly disappeared, i think it was only hidden and the phone just cant identify it nor read it like something. now i restarted the phone, it booted up to its logo then it just went blank and it just stops there. i tried pushing recovery with adb in my pc cmd. but it cannot detect my device(no problem with my adb installation to eliminate this from the question), i also tried putting an sd card with a recovery file but there was no option for sd card path. but the phone can still function well, i know because it can still be loaded under flashboot, download screen and S / W upgrade menu and it can still perform wipes for all partition and caches and can reset for factory settings etc. but whenever i will reboot, its not going to complete. anyone please help me how to make my phone be detected by my pc. The usb drivers are just fine, updated it many times, read all procedure for making the driver connect perfectly. i reformatted the sd so it wont be a problem when i put it in. but in the recovery menu i just cant see my sd card, theres just the option for "update from external storage" but it doesn't have anything inside. what a mess. i cant make my phone reflashed cause its not responding with the connection with my pc. but when i am opening an odin (just used for connection monitoring) there are two yellow boxes with com port like these: 0:[com7] and 0:[com9], so i know it is still somehow communicating with my pc. please help any advice, i dont want to resort to jtag for im not sure if it will support my phone and it's already avialable for the model but definitely not going to send my phone for repair cause it will be costly. thanks to all who will respond. Please help thank you. additionally: OS was ics version 4.0.4 and rooted. already gone through rooting several times with no problem. just the editing part.

to edit Android files on Windows use only Notepad++ anyway do not use Windows notepad this is for Windows files formatting only
well, you have to get build.prop from your phone edit on PC then copy back
so enter recovery connect phone to PC create a folder say C:\tmp
to get build.prop from phone
Code:
adb devices
adb shell
mount system
exit
that's to mount system partition then
Code:
adb pull /system/build.prop C:\tmp\build.prop
edit it and copy back to phone
Code:
adb push C:\tmp\build.prop /system/build.prop
maybe is not your case ? but I wanted to give you an idea

@ruscan.calin
Thanks, great. i will try this one once i get my phone recognized by my pc, adb seems not able to find my devcie have this message like this one:
"
c:\>adb devices
adb server is out of date. killing...
*daemon started successfully *
list of devices attached "
and that's it nothing happens.
thanks for the advice i will definitely use this once i get my phone connected with my system. thanks a lot

cruelink said:
@ruscan.calin
Thanks, great. i will try this one once i get my phone recognized by my pc, adb seems not able to find my devcie have this message like this one:
"
c:\>adb devices
adb server is out of date. killing...
*daemon started successfully *
list of devices attached "
and that's it nothing happens.
thanks for the advice i will definitely use this once i get my phone connected with my system. thanks a lot
Click to expand...
Click to collapse
start phone in recovery mode do not connect to PC at this time
open Device Manager now connect phone to PC
if you see ADB Interface connecting in Dev Manager it's ok if not you have a problem with phone drivers so install it again

ruscan.calin said:
start phone in recovery mode do not connect to PC at this time
open Device Manager now connect phone to PC
if you see ADB Interface connecting in Dev Manager it's ok if not you have a problem with phone drivers so install it again
Click to expand...
Click to collapse
Hi, cant still afford to make the adb component in my device manager to appear, but it's good to inform you that it helped me a bit because i was able to see the storage of my phone and i was also able to put some files in there without any hassle that alone was satisfying me that my phone is not really dead. sad to say i did everything i could to have my pc detect my phone via recovery menu, but still no devices found. it's really weird that some links are saying that i should make my phone's "usb debugging" enabled, wherein fact i cant even go beyond my original problem(bricked phone), i can't even see the inside of my phones directory, only the storage one that was activated just recently. i even did a reinstallation of my usb, uninstalled every other phone related usb installation to avoid conflicts reinstalled my phones proper usb installer then restart. no progress still to be called. it makes me feel that the phone was just trap in the state of booting and not knowing what to do because it cant see any command inside its system. i cant go into the systems directory as well. and that's the only way i think i could revive my phone in replacing a new build.prop, as you advised to be edited in a notepad++ which i recently acquired and installed. by the way how do i save the build.prop to its original file format, and what is the extension. thanks alot for helping out. im getting a little brighter each step of the way, im not loosing it to come to smashing my phone to pieces instead of keeping a very expensive paper weight.

usb debugging enabled is not useful in this case (you can't set it )
build.prop is a file with .prop extension save file with notepad++ name it build.prop then check location of file it should be build.prop notepad from Windows saves it as build.prop.txt that's not good also notepad adds some formatting characters inside file that's wrong so use only Notepad++ when working on Android files (or VIM for Windows editor etc anyway do not use Windows editors they are good for Windows files only)
-try these things on another computer (to install drivers etc)
-I advised somebody to send a mail to manufacturer and he got a reply with a link to stock rom... that's great !
-if you link me your build.prop file I can tell you if it's ok
-pc link - that's to be solved firstly check manufacturer site for sync software/ drivers even send mail

isa. rgiespea
ruscan.calin said:
usb debugging enabled is not useful in this case (you can't set it )
build.prop is a file with .prop extension save file with notepad++ name it build.prop then check location of file it should be build.prop notepad from Windows saves it as build.prop.txt that's not good also notepad adds some formatting characters inside file that's wrong so use only Notepad++ when working on Android files (or VIM for Windows editor etc anyway do not use Windows editors they are good for Windows files only)
-try these things on another computer (to install drivers etc)
-I advised somebody to send a mail to manufacturer and he got a reply with a link to stock rom... that's great !
-if you link me your build.prop file I can tell you if it's ok
-pc link - that's to be solved firstly check manufacturer site for sync software/ drivers even send mail
Click to expand...
Click to collapse
that's great news, you actually come to emailing the phones manufacturer? wow, im flattered. well you're a very nice guy to help me out on this. and i have good news too. i found out that i have a little conflicting usb drivers, as i have installed samsung for my previous phone(samsung galaxy 1) i had it liquidated for this new one. but a little hard on the support. you gave me a new idea about the usb. so i uninstalled all the related usb drivers and have it reinstalled. now i am able to communicate with OTA firmware server, and i got a reading that was not happening before(stucked in just detecting the phone) now i have a percentage reading of downloading or so. but i still have to wait if it will complete and have it repaired. so by now you can give me a little more help cause im still not at it in pushing through the use of adb programming. and the link you mentioned, i'll wait for the progress about it and see what really was it. and thanks a lot. really appreciate it.

fixed bricked phone via OTA by fixing link to pc.
Hi, i thank you for your help. i managed to fix the phone myself. i just missed the simple step that you advised me. fix the link first to pc. i have installed another model of the phone for the same manufacturer with different type so that was causing the mixed up for updating and recovering via the OTA site of the phone. so yey. you helped a lot. i thank you. i am now running at ics version 4.0.4 and now rooted. i will not commit the same mistake of saving the build.prop with another format. that was bad. so then i'll be very careful in editing the build.prop and first of all, i will keep a backup inside where i can access it even if it will be hard bricked. never forget that one from now on. so this is it. i thank you. of all the place ive been circling around for answer. here is where i found it. and just one person. hooray. thank you very much.

cruelink said:
Hi, i thank you for your help. i managed to fix the phone myself. i just missed the simple step that you advised me. fix the link first to pc. i have installed another model of the phone for the same manufacturer with different type so that was causing the mixed up for updating and recovering via the OTA site of the phone. so yey. you helped a lot. i thank you. i am now running at ics version 4.0.4 and now rooted. i will not commit the same mistake of saving the build.prop with another format. that was bad. so then i'll be very careful in editing the build.prop and first of all, i will keep a backup inside where i can access it even if it will be hard bricked. never forget that one from now on. so this is it. i thank you. of all the place ive been circling around for answer. here is where i found it. and just one person. hooray. thank you very much.
Click to expand...
Click to collapse
that's good news ! and thanks for feedback
feedback is an invaluable resource ! (some just forget about that from my experience :laugh: NOT your case ! )

[GUIDE][Cube i6 Air (3G or Wifi)] How to install Windows 10 !

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?

Urgent Help - Keep booting into recovery

Hello
Please help, My oppo r7+ keep booting in to recovery. it shows wiping loading screen for 2 seconds and screen goes black. Please help.

Here is what I have done
Hello, I know how frustrating this is, I been playing with the files some of the good bodies from here share with me, my oppo R7plusm is totally death I don't even get to see the logo, I have manage to make the computer recognize the phone, however I'm still stucked and phone still death, and I do not have the time do play with this any more, I did not need a new phone, I'm (was) just fan of oppo phones (THANK YOU OPPO FOR MAKING A GREAT PIECE OF HARDWARE AND PIECE OF SH** SOFTWARE) you got one more unhappy client thanks to your st**ip way of making software without updates, poor follow up to international roms, bla bla..
Here is what I have done until now
Downloaded this kit that was shared from one of the users on this discussion: (note I cant post link directly since I'm new on this great forum) so you will have to put together this link: https : //docs . google . com/uc?id=0B8R7-aow-mrqT2pZYkIxMHdMcVE&export=download
1. you must uncompress the directories, I used 7zip is very good and not intrusive as other programs
2. you will find 2 directories (1. with usb qualcom drivers) and (2. oppo r7plus rom with a tool inside called Msm8x39Download Tool V1.6.7)
3. Install the qualcom usb drivers (please note: I don't know if is true or not, but is recommended to use a USB Port v2 not v3
4. Go to the room directory we unziped, and look for the tool called Msm8x39Download and right click on it, and run as administrator or uncheck the box that says protect)
5. once the application is running connect your death phone to the computer using a good usb cable
6. press the power button + volume up ad the same time, wait about 12 to 15 seconds until you see your phone is listed on the program list
7. there is a button that says Verify (you can click on this and see if all the files are correct) note: the checking takes about 1 minutes so wait until it finish you will see a popup windows with the results (to be honest with you I don't know why most of the say OK, except system.img and userdata.img says fails (I'm assuming this is the reason I have not been able to revive my phone)
8. However to reinstall the corrupted files on your phone you must click on the button that says Start (note: you must keep checked the After-sales upgrade moc) once you click start you will see the program runs and show a green bar loading something (when it finish if you are lucky enough you will get your phone back to live)
AS I SAID in the begining I have not been able to recover my, after the green bar finish loading the program says waiting for usb to be connected?? if somebody in the world is kind enough or happen to know how to fix this problem please help, there are thing that you do just for the love of it.
I will keep trying when I get a chance to do it, if I manage to recover it I will make a video with instructions to do it, however if someone else discover a better or easy way please share
