Develop Bugs

Jiayu G2S - "unofficial forum"

JIAYU G2S
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The Jiayu G2S was released on January 1, 2013. It was a significant upgrade to the G2 with a lot of hardware changes. For the price, it had an impressive list of specifications:
MTK MT6577T ARMv7 Cortex-A9 Dual-core 1.2GHz processor
GPU: PowerVR SGX531
4 inch QHD IPS screen, 960x540 pixel display, OGS (One Glass Screen)
Dual SIM cards supporting GSM 850/900/1800/1900mhz & WCDMA 3G 2100mhz network (only one 3G slot)
1GB RAM / 4GB ROM
Supports up to 32gb class 12 microSD card (TF card)
8MP rear camera, 2MP front camera
Supports WiFi a/b/g & WiFi hotspot, Bluetooth with EDR & A2DP, GPS & AGPS
Android 4.1 OS (Jelly Bean), multi-language
FM Radio
Gravity Sensor, Proximity Sensor, Light Sensor, Magnetic Sensor, Gyroscopic Sensor
2200mah battery
Size: 125 x 61x 9.9mm
Weight: 145g with battery
Overall, I really like the look and feel of the phone. Except for the ear speaker hole, the front is one solid piece of glass, wrapped around with a very solid metal frame. The metal frame is not just a thin piece of sheet metal, but is cast metal, provides for complete rigidity for the whole phone, and should do a good job of protecting that large piece of screen glass. This also means that the phone has a bit of weight, but that feels good in my hand. Additionally, I like the more rectangular design of the phone and the more square edge down the sides that the flat metal frame provides. It is very easy to hold onto.
Call quality is very good for me. Reception seems on par with other phones I've used. The wifi might be a bit weaker than my Huawei G300, but it is fine. The screen is very nice to look at and very sensitive, but you should read below about the "jump screen" problem. You should also read below about potential problems with GPS connection issues. I've now owned two of these phones. The first had the jump screen problem, and was replaced under warranty. The replacement has terrible GPS pickup, but no jump screen problem.
The large battery means that I have no problem getting through a day of use, and I probably could use it for two days without a charge most of the time. (But I do not use the phone for gaming.) The phone runs most of the time at 1001mhz or 250mhz when on, and will only jump to 1200mhz in extreme conditions. "Deep sleep" mode is for when the screen is off, but the phone will run at 1001mhz when charging no matter if it is on and being used or not. That is an issue for phones based on this MTK chipset and not exclusive to the JY G2S.
Jiayu includes a few apps targeting the Chinese market for this phone, but other than that, the OS is mostly "vanilla" Android Jelly Bean (AOSP). The phone comes already rooted, so freezing or deleting unwanted apps is a simple solution for what you don't want. There are a number of modified roms available already, including the Lewa rom (http://www.needrom.com/phone-roms/jiayu/g2s/). But you should note that later hardware versions of this phone have different components. You should make a note of what the rom version is that came installed on your phone so that you know what hardware version you are using.
"Jump Screen" Problem Solved?:
Many of the first batch of phones were plagued with screen problems. Commonly referred to as the "jump screen" problem, the result is that when scrolling through screens of data, the screen just "jumps" to a different location without any apparent reason. The screen also "quivers" when touching it, even if you aren't moving your finger. Jiayu promptly acknowledged the problem and tried to correct it with a quick ROM update released on January 9, 2013. (The build number of the ROM is: G2S 20130108-104044.) This ROM update did seem to work for some, but for others the problem persisted.
At this point, I personally don't know if the problem has been completely solved in the manufacturing of subsequent batches of the phone. My phone had the problem, and flashing the new ROM did not solve it. I returned the phone for replacement under warranty and did receive a replacement phone that does not have the problem. So whether or not there still is a manufacturing problem, Jiayu can replace the phone with one that works. However, see below for the GPS connection problem that I now have.
GPS Connection Problems:
There are also a number of users here who are reporting difficulty with weak GPS fix. My GPS fix on my first phone was excellent, but my replacement phone is not good at all. It has been suggested to install "Faster GPS" from the Play Store, which will let you set your location. Also, you can look at this post from later in this thread for more information: http://forum.xda-developers.com/showpost.php?p=39975417&postcount=209. (Please post any solutions you discover in this thread.)
ROM Flashing:
One of my initial struggles was getting the official rom flashing tool to work. I finally got things going, and I hope I can help others who "just don't get it". So if you want some detailed instructions in English for how to flashing a new official ROM onto the Jiayu G2S, have a look at the second post. (If you are flashing a third-party rom, follow the rom builder's instructions.)
ClockworkMod Recovery:
"Thingbreaker" has provided us with a working CWM Recovery. Here's his post link: http://forum.xda-developers.com/showpost.php?p=37521066&postcount=28
There are two ways to flash the CWM Recovery image: using the ROM flashing tool (harder) or using Mobileuncle Tools (easier).
To use Mobileuncle Tools, install it from the Play Store (free). Copy the CWM Recovery image file to the root of your SD card, making sure there are no spaces in the filename. Run Mobileuncle Tools and choose Recovery Update. Choose the recovery image file that Thingbreaker provided.
To use the ROM flashing tool, you first you need to understand how to flash a complete rom as explained in the second post of this thread directly below. After you know how to do that, then look at this post to learn what is different about only flashing the recovery image: http://forum.xda-developers.com/showpost.php?p=37499848&postcount=23
Conclusion:
I do not recommend purchasing this phone. Period. Until Jiayu can do a better job of quality control, I don't recommend their products. There are other companies out there who's phones are only slightly more expensive, but who have a much better reputation for quality control.
Jiayu, if you are reading this, you need to do better! And you really need to improve your repair department as well. Sending me a replacement phone with a GPS problem causes me to wonder if you are using the "shuffle" method of passing around bad phones instead of repairing them. I'm NOT a satisfied customer.

“Unofficial” Guide to Flashing the Official Jiayu G2S ROM
Disclaimer: I’m just one guy who got this to work after a lot of trial and error. I’m only telling you how I did it. I don’t claim it will work for you. I don’t guarantee you won’t brick your phone by following these instructions. And you should understand that if you don’t bother to read carefully and do exactly what I say, you really can brick your phone. Also, it seems there has been an upgrade to some of the components in later versions of the phone released in March 2013, and you will want to verify which version of the phone you have before installing any roms. You should be able to check the rom build information for the date on your particular phone. This guide only describes how to flash the official rom from Jiayu for the G2S. If you intend to install some other third-party rom, please follow that rom builder's instructions.​
Pre-requisites:
You need a PC running Microsoft Windows 2000 or higher.
If you haven’t previously installed msxml 6.0 and .net Framework 4.0 or higher on you Windows PC, do so first. Get them directly from Microsoft. (I assume you know how to search.)
Download the following:
Latest Jiayu G2S ROM update; the rom I installed was the G2s_20130109-104044 stock rom: http://pan.baidu.com/share/link?shareid=157669&uk=839171988 (Note: the build number of the ROM after installation is: G2S 20130108-104044; don't be confused by the name of the file.) Use Google Translate if you need to see which button to push to start the download. Also note that there is a newer official rom for newer versions of the phone. The rom date is 20130306. I don't know what happens if you install the newer version on an older phone.
This zip file contains the Android USB driver, VCom drivers, SP Flash Tool, and a document of these instructions (ReadMe.doc): http://www.mediafire.com/?tc4q3wy5eabowhf
Unzip the files you downloaded and move/copy folders and files where they need to go:
Within the rom zip that you downloaded from the Baidu website, you can find the \G2s_20130109-104044 sub-folder. This folder contains the actual rom files (14 files). Move this entire folder onto your desktop. The reason for doing this is that there are folders within the zip file whose names contain characters that your version of Windows might not be able to read, even if you can see them in Windows Explorer (the filemanager). This will cause you trouble when you try to flash the rom.
After unzipping the driver and flash tool zip file, you will find the \USB-VCOM-Drivers folder with \INF and \SYS sub-folders. In the \INF folder there are three other sub-folders: \ 2K_XP_COM, \Vista, and \Win7.
Copy the \INF\cdc-acm.inf file into your C:\Windows\inf folder. (You may have to give permission to do this.)
Based on your version of Windows (2K-XP, Vista, Win7, 32-bit or 64-bit), locate the one correct usb2ser_????.inf file and copy it to your C:\Windows\inf folder. (You may have to give permission to do this.)
Copy both the \SYS\androidusb.sys and \SYS\usbser.sys into your C:\Windows\System32\driver folder. (You may have to give permission to do this.)
Install the drivers:
Plug your phone into your computer with a USB cable. If you had not previously installed the drivers, the system will start trying to install them.
If the system asks you to choose to install the drivers, click on “install the software automatically” and proceed.
If system is unsuccessful in locating and installing the drivers, you can try to go back and locate the drivers yourself by pointing to the individual files, but this should not happen if you properly copied the drivers over to your C:\Windows system folders.
BACKUP YOUR DATA NOW!
Proceeding beyond this point is going to mean that EVERYTHING on you phone is going to be deleted and a new system will replace it.
You have been warned!
Warning!
Attempting to install a rom that does not use the correct “scatter” file (see description below) will brick your phone. Don’t do it. If you aren’t sure a rom is made for your phone, don’t attempt to install it.
Install the updated ROM:
1. Turn off your phone, open the back, and remove the battery.
2. Plug your USB cable into your PC and phone. If your PC attempts to install drivers, let it finish.
3. Unplug your phone from the cable.
4. Start the SP Flash Tool program by clicking on the Flash_tool.exe file. If you get a security warning, allow it to run.
5. Click on the “Scatter-loading” button on the right side.
6. Browse to your \Desktop\G2s_20130109-104044 folder and choose the MT6577_Android_scatter_emmc.txt file. All other files will be chosen automatically.
7. Click on the “Firmware -> Upgrade” button.
8. Plug your USB cable firmly into the phone. The Flash Tool will automatically start flashing your new rom. Wait for it to finish and show you the green circle.
9. Unplug your phone from the cable.
Rebooting the phone:
1. Install your battery.
2. Very carefully, without touching the screen, push the power button.
3. Do not touch the phone as it boots!
4. After it has completed booting, you may again use your phone normally.

Following the advice that it might help if the phone is very cold when updating to the new rom, I tried putting it in the refrigerator. Unfortunately, that did not seem to help in my case. The phone still has the "jump screen" problem.
Of course, any other ideas would be appreciated as well.
Has anyone yet been successful in creating a Recovery mod (i.e. ClockworkMod Recovery)?

Tell Me Some Unofficial Way Of Hacking Based On Geograohical Location
Any Jealousy people Tell Me Some Unofficial Way Of Hacking Based On Geographical Location.

twrock: Make sure you do not have screen protector applied and you do not touch the screen during the first boot after flashing.

Thanks for the advice. But I'm not using a screen protector, and I am being very careful about not touching the phone. Nothing seems to help.
Sent from my G2S using xda app-developers app

Have you identified production date of your phone? Is there a sticker anywhere? We might come to a conclusion later on, of which date onward the factory has solved the problem... It might be a hardware problem after all.
Still waiting for mine to arrive...

hi there, for those who already have in their hands the g2s is it possible to give more reviews about its gps and the camera especially at night? thanks

Hi.
I have just created a ClockWorkMod recovery image for the Jiayu G2S.
I don't have the phone yet, it is still on its way, so I can't guarantee that it will work.
Download: http://db.tt/vFO4S6Mc
When flashing this recovery, use the same scatter file as for the stock rom.
If you don't have the scatter file here it is: http://db.tt/Z4TWPowQ
Please try it at your own risk, and give me feedback.

I received mine today. I am stunned. This thing is amazing. After all the HTC's I have this is a dream.
Mine doesn't seem to have the screen problem, but has the 20130108 firmware. I will wait a couple of days and see how it's running and the flash it.
CWM for this would be amazing and unabridged CyanogenMod would be even greater. Wonderful times!!!

fcsabika said:
Hi.
I have just created a ClockWorkMod recovery image for the Jiayu G2S.
I don't have the phone yet, it is still on its way, so I can't guarantee that it will work.
Download: http://db.tt/vFO4S6Mc
When flashing this recovery, use the same scatter file as for the stock rom.
If you don't have the scatter file here it is: http://db.tt/Z4TWPowQ
Please try it at your own risk, and give me feedback.
Click to expand...
Click to collapse
I'll give it a try.
What method did you use to create it? Did you use Koush's "builder"?
I also tried to make a CWM Recovery using the builder. The builder said it was successful, but the resulting CW recovery would not boot.
I'll let you know when I have the time to try it. Thanks.

Anyone know how to get rid of the Google search bar at the top of the standard Launcher? I'd guess that Google doesn't want us to be able to get rid of it.

sdssss said:
hi there, for those who already have in their hands the g2s is it possible to give more reviews about its gps and the camera especially at night? thanks
Click to expand...
Click to collapse
I don't know if my experience is much help. I live in Taiwan, so I suspect my GPS satellite locks were about the same as they would be in China. So for what it's worth....
My first GPS use locked in less than two minutes. I was outside in a parking lot on a clear day when I started. I got into the car after about 30 seconds and put the phone on the dashboard. It was locked in before the screen shut off (which is set at 2 minutes). I did not have Wifi connected, so no help from that. Subsequent to that first use, locking in took less than 15 seconds.
I haven't taken any pictures at night, so I can't help you there.
I'll mention here that if I decided to order this phone today, I'd find a way to get it straight from Jiayu. I ordered mine from Etotalk.com (and wasted money on their "Etotalk mod rom"), and they aren't being very helpful with aftersales follow up. I finally gave up on them and am now talking straight to Jiayu support. But I have to wait until after Chinese New Year to send it back. They said that they would not be able to replace the phone until after Chinese New Year anyway, so sending it back now would only mean I would be without the phone longer.

hello, i'm G2S first batch too, what do you mean about shaking problem? is it shake hard ? i got the problem while charging the phone, but if it's unplug, it's seems to be normal.
i'll try the new firmware from this thread, thanks for the link :laugh:
by the way, i've ported the CWM recovery for G2S, i'll upload it if you need it

For those who already have the phone, is the signal strong even if you are inside buildings?
I'm asking this because many users report that jiayu g3's signal is very week when you get indoor, and i'd like to know if it was corrected in this version.

sempracurtir said:
For those who already have the phone, is the signal strong even if you are inside buildings?
I'm asking this because many users report that jiayu g3's signal is very week when you get indoor, and i'd like to know if it was corrected in this version.
Click to expand...
Click to collapse
my phone is work normally even inside the buildings it depends on the network carrier, except you're in the basement
by the way, i've flashed the newest firmware from the page1, and the "jumpscreen" error while charging is now fixed. More stable touchscreen, thanks man :laugh:

Gps
fix ok, but not accurate.
The worst gps that I have had.
Solutions?
Hello
verbal

twrock said:
I'll give it a try.
What method did you use to create it? Did you use Koush's "builder"?
I also tried to make a CWM Recovery using the builder. The builder said it was successful, but the resulting CW recovery would not boot.
I'll let you know when I have the time to try it. Thanks.
Click to expand...
Click to collapse
Yes I have used the builder.
So did anyone try my CWM recovery?

fcsabika said:
Yes I have used the builder.
So did anyone try my CWM recovery?
Click to expand...
Click to collapse
Sorry, how can I install it?
I read your post yesterday but I didn't understand.
Can you explain me better?
Thanks.

lelepanz said:
Sorry, how can I install it?
I read your post yesterday but I didn't understand.
Can you explain me better?
Thanks.
Click to expand...
Click to collapse
You can install it the same way as the official rom.
See the second post by twrock.

Managed to Root Xtouch X817 Tablet (Rooting method should work on all xtouch)

Hello
After a week of searching and trying to root my xtouch x817 i failed to get the drivers to work.
However 5 minutes ago i managed to root it
So here is what i did
I downloaded moborobo program and got the drivers from it however it was not working
so i went to c:\windows\users\{your user}\.android\ and i made a file named adb_usb.ini
and in that folder i added 0x2207
and finnaly usind ADB DEVICES command i detected my device with a weird serial number
which is
0123456789ABCDEF
and finally i downloaded bin4ry root tool
and i selected the first option and I DID NOT RESTORE
and it worked
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
image won,t work?
download https://www.dropbox.com/s/ug4s5momn72wpkg/20130526_001159.jpg

Well Done!
ananjaser1211 said:
Hello
After a week of searching and trying to root my xtouch x817 i failed to get the drivers to work.
However 5 minutes ago i managed to root it
So here is what i did
I downloaded moborobo program and got the drivers from it however it was not working
so i went to c:\windows\users\{your user}\.android\ and i made a file named adb_usb.ini
and in that folder i added 0x2207
and finnaly usind ADB DEVICES command i detected my device with a weird serial number
which is
0123456789ABCDEF
and finally i downloaded bin4ry root tool
and i selected the first option and I DID NOT RESTORE
and it worked
image won,t work?
download https://www.dropbox.com/s/ug4s5momn72wpkg/20130526_001159.jpg
Click to expand...
Click to collapse
That's great brother, I got this tablet sometime ago, sadly my son has broken it's WiFi, most probably hardware issue. I need to root it to be able to use reverse tethering on the device through USB. I have a little bit of experience rooting, I have two other rooted androids in the house, but could you please help me with Bin4ry Root Tool as I have never used it?
Specially with X817.

irisgenx said:
That's great brother, I got this tablet sometime ago, sadly my son has broken it's WiFi, most probably hardware issue. I need to root it to be able to use reverse tethering on the device through USB. I have a little bit of experience rooting, I have two other rooted androids in the house, but could you please help me with Bin4ry Root Tool as I have never used it?
Specially with X817.
Click to expand...
Click to collapse
Hey
I did not use Bin4ry tool for long time but i guess it is shown in the window how to do the root
it is super easy to use don,t worry
and for the wifi issue i had it in my tab
you will see a cable connected to a sort of sticker it is golden colored
the wifi is poor because the gold cable is probably cutted

ananjaser1211 said:
Hey
I did not use Bin4ry tool for long time but i guess it is shown in the window how to do the root
it is super easy to use don,t worry
and for the wifi issue i had it in my tab
you will see a cable connected to a sort of sticker it is golden colored
the wifi is poor because the gold cable is probably cutted
Click to expand...
Click to collapse
Okay Thanks brother. I don't have access to the tablet as of now. When I get it back , I will try this and bug you again if there's any issue.
Thanks for the WiFi tip too. I'll see if that connection is maybe damaged.

ananjaser1211 said:
Hello
After a week of searching and trying to root my xtouch x817 i failed to get the drivers to work.
However 5 minutes ago i managed to root it
So here is what i did
I downloaded moborobo program and got the drivers from it however it was not working
so i went to c:\windows\users\{your user}\.android\ and i made a file named adb_usb.ini
and in that folder i added 0x2207
and finnaly usind ADB DEVICES command i detected my device with a weird serial number
which is
0123456789ABCDEF
and finally i downloaded bin4ry root tool
and i selected the first option and I DID NOT RESTORE
and it worked
image won,t work?
download https://www.dropbox.com/s/ug4s5momn72wpkg/20130526_001159.jpg
Click to expand...
Click to collapse
Dear Adnan,
I search whole web and found that you are the only one who claim to root Xtouch x817 tablet. If this is correct, would you like to describe it further (how you do that). Actually i have 2 piece of this tablet and both looks bricked to me. i want to know how i can restore them on factory settings.
Regards,
Xinixi

xinixi said:
Dear Adnan,
I search whole web and found that you are the only one who claim to root Xtouch x817 tablet. If this is correct, would you like to describe it further (how you do that). Actually i have 2 piece of this tablet and both looks bricked to me. i want to know how i can restore them on factory settings.
Regards,
Xinixi
Click to expand...
Click to collapse
Hey, well it was pretty straight forward. the table uses no security methods or whatsoever like locked bootloaders etc. so we can root it using any generic tool. for example. Bin4ry root tool .which is the one i used .
I did alot of searches and saw people use generic android drivers . the trick was. download generic drivers using any android managing tool such as moborobo or Wondershare MobileGo for android. then let it install the drivers . and then you need to navigate to
c:\windows\users\{your user}\.android\
inside it you will find this file "adb_usb.ini"
If not then make one.
type this in it 0x2207 and save the file
then enabled USB Debugging
and opened bin4ry and rooted it using that tool
the hard part is to get the drivers working. thats it
about your bricked device, check their site
to download the firmware and the tool. they got a really good manual to restore the tablet

ananjaser1211 said:
Hey, well it was pretty straight forward. the table uses no security methods or whatsoever like locked bootloaders etc. so we can root it using any generic tool. for example. Bin4ry root tool .which is the one i used .
I did alot of searches and saw people use generic android drivers . the trick was. download generic drivers using any android managing tool such as moborobo or Wondershare MobileGo for android. then let it install the drivers . and then you need to navigate to
c:\windows\users\{your user}\.android\
inside it you will find this file "adb_usb.ini"
If not then make one.
type this in it 0x2207 and save the file
then enabled USB Debugging
and opened bin4ry and rooted it using that tool
the hard part is to get the drivers working. thats it
about your bricked device, check their site
to download the firmware and the tool. they got a really good manual to restore the tablet
Click to expand...
Click to collapse
Thanks for the advice, I checked the product website and am still with stand empty hands. The XTouch (UAE) website remove this model & its support. The Nigerian website has this model but they don't provide any support, infect their support page does not exist (beyond the link). I want to know that can i get its firmware and toolkit from any other source.
BTW i managed to restore one piece, however the other set is still dead for me :crying:

xinixi said:
Thanks for the advice, I checked the product website and am still with stand empty hands. The XTouch (UAE) website remove this model & its support. The Nigerian website has this model but they don't provide any support, infect their support page does not exist (beyond the link). I want to know that can i get its firmware and toolkit from any other source.
BTW i managed to restore one piece, however the other set is still dead for me :crying:
Click to expand...
Click to collapse
I just checked the UAE site. and yeah apperantly they removed the device . pretty bad, but i think if you contacted the support they may give you the link to the download site ( it is in Chinese so i don,t really think you will find it in ease)
I had the files before but the HDD the contains them died.

HTC M9 Qfil flash help needed (Qualcomm MSM8994) {Images Attached}

In my position I'm having bricked HTC M9 which need to recover user data (Photos of new born kid which don't have backups)
Symptoms :-
NO power LED (Even charger connected)
NO HTC Logo
NO boot menu
NO vibrations
Power On button do nothing
Power + Volume down nothing
But when it connected to PC it shows Qualcomm service port "Qualcomm HS-USB QDLoader 9008 (COM8)"
After spending long time on reading I figure out If I'm able to fix the partition table & connect Qualcomm HS-USB QDLoader 9006 interface,
Then the eMMC can be mounted to local PC via USB. then I can recover my data,
So I'm planing to use Qfil to flash required data to mobile
So I downloaded Qfil from here
Downloaded stock firmware from here or here
My problem is it required following 3 files
prog_emmc_firehose_8994_lite.mbn
[*]rawprogram0.xml
[*]patch0.xml
prog_emmc_firehose_8994_lite.mbn file found & attaching
I'm still unable to find above three files any where from internet,
Please can some one help me to find this files (or extract the from some where)
I'm attaching some Images of device manage view, Qfile & stock ROM I have respectively
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Have you read this thread https://forum.xda-developers.com/windows-10-mobile/create-rawprogram0-xml-ffu-file-extract-t3385201 ?.
Beamed in by telepathy.

shivadow said:
Have you read this thread https://forum.xda-developers.com/windows-10-mobile/create-rawprogram0-xml-ffu-file-extract-t3385201 ?.
Beamed in by telepathy.
Click to expand...
Click to collapse
Hi My Friend, thanx for take your time,
Yep I read it, but the problem is
1. to use this tool we need "prog_emmc_firehose_8994_lite.mbn" file
2. we can only get "rawprogram0.xml" file from this, still need "patch0.xml"
Any one could help me with this will be a great help.
Thanx Mate

Good news , I have found the programmer for MSM8994 "prog_emmc_firehose_8994_lite.mbn"
I'm attaching it above for any one who is in the same boat as me.
Please some one help me to find "rawprogram0.xml and patch0.xml" files for HTC M9
https://drive.google.com/file/d/0BzypAwIfVp1gV1Vjc2FSQlhlaHM/view?usp=sharing

Hello Sir,
You contacted me via PM. I usually do not give any private support, so I'll answer here. Public is always better, because it might help other people.
From what I've learned in the past, the only phone I was ever able to recover by connecting directly to the SoC via that low level serial connection you're planning to use was the HTC One S in 2012. Ever since, I haven't seen anyone accomplish that, except maybe team sunshine (@Beaups and @jcase), who also won't be supporting cases like yours anymore due to time constraints.
With the HTC ONE S, the problem was that that qhusb serial connection couldn't be made stable on Windows. Lack of proper drivers was what I suspected back then. It only worked in Linux, Ubuntu.
So, I am guessing you're in deep sh!t and chances to recover your phone that way are pretty damn near zero.
Also, I faced the same problem like you now: the required files are very hard to come by and for the M9, I definitely don't have them. I didn't even keep the old OneS stuff.
So, unfortunately, your only chance will be to find someone near you with a riff jtag box and have him jtag flash your phone.
I know @Tecardo can do that, because we built up a jtag service in 2012 for XDA users, but he is located in Germany and I don't know where you are. But you can sure contact him.
Also, there usually are people in eBay all over the world selling this service.
Please try that. It's a lot less pain.

Sneakyghost said:
Hello Sir,
You contacted me via PM. I usually do not give any private support, so I'll answer here. Public is always better, because it might help other people.
From what I've learned in the past, the only phone I was ever able to recover by connecting directly to the SoC via that low level serial connection you're planning to use was the HTC One S in 2012. Ever since, I haven't seen anyone accomplish that, except maybe team sunshine (@Beaups and @jcase), who also won't be supporting cases like yours anymore due to time constraints.
With the HTC ONE S, the problem was that that qhusb serial connection couldn't be made stable on Windows. Lack of proper drivers was what I suspected back then. It only worked in Linux, Ubuntu.
So, I am guessing you're in deep sh!t and chances to recover your phone that way are pretty damn near zero.
Also, I faced the same problem like you now: the required files are very hard to come by and for the M9, I definitely don't have them. I didn't even keep the old OneS stuff.
So, unfortunately, your only chance will be to find someone near you with a riff jtag box and have him jtag flash your phone.
I know @Tecardo can do that, because we built up a jtag service in 2012 for XDA users, but he is located in Germany and I don't know where you are. But you can sure contact him.
Also, there usually are people in eBay all over the world selling this service.
Please try that. It's a lot less pain.
Click to expand...
Click to collapse
hello Sir,
Thanx for your time taken,
Actually I don't need recover the phone, I just need to restore partition table & put the phone in to "Qualcomm HS-USB QDLoader 9006 " mode. ( now it is on Qualcomm HS-USB QDLoader 9008 mode)
then I can mount the eMMC to Windows OS & recover what I need from the memeory.
So please any one can direct me to that way ??
thanx again
BR

war357 said:
hello Sir,
Thanx for your time taken,
Actually I don't need recover the phone, I just need to restore partition table & put the phone in to "Qualcomm HS-USB QDLoader 9006 " mode. ( now it is on Qualcomm HS-USB QDLoader 9008 mode)
then I can mount the eMMC to Windows OS & recover what I need from the memeory.
So please any one can direct me to that way ??
thanx again
BR
Click to expand...
Click to collapse
As far as my experience went five years ago, mounting the storage chip was not possible. A reflash was, although pretty complicated, just so possible.
I wish you good luck with your adventure.

Sneakyghost said:
As far as my experience went five years ago, mounting the storage chip was not possible. A reflash was, although pretty complicated, just so possible.
I wish you good luck with your adventure.
Click to expand...
Click to collapse
Ok Mate, Thanx
one other thing,
Do you know a way to just flash only boot partition (from USB cable)
Forgot to answer, I live far from German, Sri Lanka (Southeast Asia) so unable to access most of the resources.
thanx
br

Sneakyghost said:
Hello Sir,
You contacted me via PM. I usually do not give any private support, so I'll answer here. Public is always better, because it might help other people.
From what I've learned in the past, the only phone I was ever able to recover by connecting directly to the SoC via that low level serial connection you're planning to use was the HTC One S in 2012. Ever since, I haven't seen anyone accomplish that, except maybe team sunshine (@Beaups and @jcase), who also won't be supporting cases like yours anymore due to time constraints.
With the HTC ONE S, the problem was that that qhusb serial connection couldn't be made stable on Windows. Lack of proper drivers was what I suspected back then. It only worked in Linux, Ubuntu.
So, I am guessing you're in deep sh!t and chances to recover your phone that way are pretty damn near zero.
Also, I faced the same problem like you now: the required files are very hard to come by and for the M9, I definitely don't have them. I didn't even keep the old OneS stuff.
So, unfortunately, your only chance will be to find someone near you with a riff jtag box and have him jtag flash your phone.
I know @Tecardo can do that, because we built up a jtag service in 2012 for XDA users, but he is located in Germany and I don't know where you are. But you can sure contact him.
Also, there usually are people in eBay all over the world selling this service.
Please try that. It's a lot less pain.
Click to expand...
Click to collapse
Actually these phones are pain to me ? taking them apart and reassembling them isn't easy at all. Sadly. And the new HTC U isn't much better
---------- Post added at 01:06 PM ---------- Previous post was at 01:04 PM ----------
war357 said:
Ok Mate, Thanx
one other thing,
Do you know a way to just flash only boot partition (from USB cable)
Forgot to answer, I live far from German, Sri Lanka (Southeast Asia) so unable to access most of the resources.
thanx
br
Click to expand...
Click to collapse
It's m possible Right now. Or I don't know any way. We don't have the resources for that. I could be wrong, but it gets harder getting these Files

Rawprogram0.xml is supposed to be creatable from the dragonboard tools.
Isn't it "fastboot flash boot.img"?
Beamed in by telepathy.

war357 said:
My problem is it required following 3 files
prog_emmc_firehose_8994_lite.mbn
[*]rawprogram0.xml
[*]patch0.xml
Click to expand...
Click to collapse
rawprogram0.xml for M9 here.
This from my gpt.bin
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/gpt.bin bs=8 count=2176
and converted to rawprogram0.xml

shivadow said:
Rawprogram0.xml is supposed to be creatable from the dragonboard tools.
Isn't it "fastboot flash boot.img"?
Beamed in by telepathy.
Click to expand...
Click to collapse
hi Sir,
Fastboot is not working,
only software download mode working, whole partition table has messed up,
so no other option than finding above files & flash via QFil.
Thanx
BR

For info: https://forum.xda-developers.com/showpost.php?p=68390222&postcount=11

Bro, that was a great help,
That was a huge favor.

That was a huge favor.....
Thanx bro, thanx a lot
One more file & I'm goor to go
See you mate!

Golv said:
rawprogram0.xml for M9 here.
This from my gpt.bin
and converted to rawprogram0.xml
Click to expand...
Click to collapse
war357 said:
hi Sir,
Fastboot is not working,
only software download mode working, whole partition table has messed up,
so no other option than finding above files & flash via QFil.
Thanx
BR
Click to expand...
Click to collapse
Thanx a lot bro, taking your time for me is much appreciated,
If possible please help me to get patch0.xml also
Thanx again

Golv said:
rawprogram0.xml for M9 here.
This from my gpt.bin
Code:
dd if=/dev/block/mmcblk0 of=/sdcard/gpt.bin bs=8 count=2176
and converted to rawprogram0.xml
Click to expand...
Click to collapse
Hello,
Thanx for your great help,
but I have one more favor , can you extract patch0.xml from your M9 please,
I can't find anyone who has M9 around me to extract the patch0.
it would be a great help.
Thanx
BR

war357 said:
Hello,
Thanx for your great help,
but I have one more favor , can you extract patch0.xml from your M9 please,
I can't find anyone who has M9 around me to extract the patch0.
it would be a great help.
Thanx
BR
Click to expand...
Click to collapse
Try to use the zeroed file (empty content)

Golv said:
Try to use the zeroed file (empty content)
Click to expand...
Click to collapse
did you get this working?
i have a working m9 and qfil set up if you know how to read from the working m9?
G

gda_scooby said:
did you get this working?
i have a working m9 and qfil set up if you know how to read from the working m9?
G
Click to expand...
Click to collapse
Hi,
No Bro, Still no luck,
I don't know exact way to extract patch0.xml,
Normally it should come with firmware file,
But no sign of that on internet,
Seems really bad luck,
Any way Bro, thanx for your support,:good:

Bootloader deleted, hard brick, need some help?

Hello guys,
I have cedric, bootloader unlocked, rooted, etc.. I used some SDcard format app and selected wrong storage to format emmcblk0, so i formated entire phone, now in device manager its detected as "Quectel QDLoader 9008
" cannot power it on as well i think bootloader is bricked, i tryed to flash but cant find anything related to this phone, also cant find blankflash.
Do you guys have any info on how to unbrick this hard-brick, or its just paper weight? I don't get how did moto/lenovo allow bootloader erase option from system, even with root...
Regards

Perhaps search for some driver that enables the transfer of the bootloader for "Quectel QDLoader 9008"?
I've found some results relating to unbricking this, and according to some of them it refers to a chipset, use this search perhaps https://www.google.co.uk/search?q=Q...rome..69i57.2111j0j7&sourceid=chrome&ie=UTF-8
---------- Post added at 11:30 PM ---------- Previous post was at 11:28 PM ----------
found this, it may help http://www.androidbrick.com/lenovo-zuk-phones-qfil-roms-unbrick-guide/

Tryed, not applicable for this mode, i need blankflash or some other method, i still have yet to try sdcard flash, but i am loosing hope here, might just accept that its totally bricked and thats it, oh well moving on i guess.

Guys i am trying to make unbrick method for Cedric, does anyone have 5 minutes of time to make loader.img, all you have to do is to be on firmware .93, bl unlocked and rooted.
Type in terminal emulator dd if=/dev/block/mmcblk0 of=/sdcard/Loader.img bs=1024 count=168960
And upload me that file, it will be around 160mb, i will try to test it and if it works upload the tutorial. The command above just reads your mmmcblk0 so there is no chance of bricking your device.

No one willing to give away five minutes to help? I will make it worthwhile since my phone is dead i am sure there is a change to fix it with this, and will make tutorial for community

magix01 said:
No one willing to give away five minutes to help? I will make it worthwhile since my phone is dead i am sure there is a change to fix it with this, and will make tutorial for community
Click to expand...
Click to collapse
Hey Mate i would help you if i could, but i'm on -72, if this would help you tell me, and i will upload the file asap.

@Cubico
We can try, but i don't think it will work tho. Please upload and we will see i guess

Ok guys new update, @Cubico provided me with Loader.img -73 firmware, so far tried nothing changed, device still showing no sign of life except Qualcomm 9008... not booting or anything, if someone have 93 bootloader Loader.img dump i can try that too, if not i will take it to shop to someone with JTAG and update you on status.

I have got a similar issue with an X4 that's hard bricked.
I know wrong forum, but I can't find anyone to help.
Trying to use QFIL I get "Download Fail: Switch To EDL Fail: Failed to Switch to Emergency Download mode"
ANY ideas? Thank you anyone that may be able to help!

Try installing this driver, then transfer/flash the bootloader, I can't help you with the actual img though.
http://www.androidbrick.com/download/qualcomm-qdloader-hs-9008-edl-usb-driver/#

magix01 said:
Ok guys new update, @Cubico provided me with Loader.img -73 firmware, so far tried nothing changed, device still showing no sign of life except Qualcomm 9008... not booting or anything, if someone have 93 bootloader Loader.img dump i can try that too, if not i will take it to shop to someone with JTAG and update you on status.
Click to expand...
Click to collapse
Hi, just saw this - I'm on NP25.137-93
Do you still need this dump?
Let me know and I'll get on it
Edit - aww crap!
Really sorry to get your hopes up! Just remembered, my phone's not unlocked or rooted! This is the first phone I've had in years that I've kept unrooted, so I didn't initially realise.
?

Np, i took the phone to service center for JTAG, hopefully they will manage to fix it somehow

Exanneon said:
Try installing this driver, then transfer/flash the bootloader, I can't help you with the actual img though.
http://www.androidbrick.com/download/qualcomm-qdloader-hs-9008-edl-usb-driver/#
Click to expand...
Click to collapse
This is not related to driver, bot Qualcomm and Quectel 9008 drivers work and allow communication with the phone, patch level is too high so blankflash files dont pass and dont allow bootloader to be flashed. Only solution is JTAG or motherboard replacement if patch level is higher than one in april 2017 i think.

Rip another cedric.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This has happened to me and I'm lucky had the assistance replaced the motherboard of the device. Your bootloader was not deleted, it was moved to a temporary partition that the boot script cannot find after pressing to start.
The problem with the manufacture is of the appliance was to have the bootloader on the same chip as the other partitions, causing the device to be easily hardbroken.
Solution? None so far.
I saw a guy who unbricked a potter (G5 Plus), but I've seen nothing from the G5.

Heh, another G5 killer here. A bad attempt at downgrading due to IMEI 0 left it as QLoader 9008. I guess I'll have to go back to my old Nexus 4.

Motorola sucks bad, Google and Xiaomi for instance have tools to recover dead bootloader eg. "Mi Flash", motorola gave developers easy bootloader unlock but no way to recover it, whats the point then, either make it recoverable or make it non erasable easily.

magix01 said:
Guys i am trying to make unbrick method for Cedric, does anyone have 5 minutes of time to make loader.img, all you have to do is to be on firmware .93, bl unlocked and rooted.
Type in terminal emulator dd if=/dev/block/mmcblk0 of=/sdcard/Loader.img bs=1024 count=168960
And upload me that file, it will be around 160mb, i will try to test it and if it works upload the tutorial. The command above just reads your mmmcblk0 so there is no chance of bricking your device.
Click to expand...
Click to collapse
https://drive.google.com/file/d/1H2Qkc1XKbr7Is46n5xdCFlgiuIH1m-vE/view?usp=sharing

abhimanyuk said:
https://drive.google.com/file/d/1H2Qkc1XKbr7Is46n5xdCFlgiuIH1m-vE/view?usp=sharing
Click to expand...
Click to collapse
It doesn't seem to work for me. It might be because I had the latest January update when I killed my Cedric.

These .img files should boot bootloader directly from SDCard but it seems thar Cedric does not support this feature, so only way is JTAG and non updated blank-flash file.

magix01 said:
These .img files should boot bootloader directly from SDCard but it seems thar Cedric does not support this feature, so only way is JTAG and non updated blank-flash file.
Click to expand...
Click to collapse
Yeah, I tried with two different SD*cards, but the device would only blink the notification light while being recognised as Qualcomm Loader.

Zenwatch (WI500Q) firmware needed...

Hey all.
It seems like this section of the forum hasn't seen any visitors for some time, not surprising given the age of the original Zenwatch. However, I am posting this on the slim chance that someone with one of these watches might see it and help a brother out.
My Zenwatch was bricked years ago following a corrupted OTA update, and hasn't seen the light of day since. Recently though I found the watch, charged it up, and gave it another go. The stock firmware was still crashing constantly leaving the watch unusable, but I managed to install the Asteroid OS on the watch and now it works, albeit in a very limited fashion compared to the official software.
Now that I know that the watch itself is OK, and it just needs the stock firmware to be installed, I turn to you. Asus were unable to help me, as they no longer have access to the original firmware (or more likely, they're unwilling to share them with an end user), I am hoping that someone on this forum still possesses one of these watches and can create and share a backup of the OS, as it now appears that this is pretty much my last chance of getting my watch working properly again.
So, any retro watch owners left in this corner of the t'interweb?

Hi! I have this watch with stock firmware. Tell how to do the backup or send manual and I'll do it.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

helloworld1337 you might be about to make a lot of people very happy!
I'm not sure how to extract the firmware from the watch, I'll have to do a little research in to that, but I don't think it's a particularly complicated procedure. Give me a little time and I'll get back to you as soon as I can.
Thanks again!

OK, I think I understand how to do this now, but as with any image copying / rooting process, only proceed if you are happy to do so, there is always the slim chance that rooting a watch can have undesired effects, but mine rooted without any issues. So, here we go...
Files that you will need...
KingRoot - https://kingroot-pc.en.uptodown.com/windows/download
ADB & Fastboot - https://developer.android.com/studio/releases/platform-tools
ADB Explorer - Can be found in the Microsoft Store. It only gets a 1* rating but we only need it to look for files and delete created images once we're done with them.
Next, connect your watch to your PC via the charging dock and a suitable USB cable. Now comes the technical stuff which I hope I have understood correctly...
1) Enable developer mode on your Zen watch. You do this by going to settings/about and tapping on the version number 7 times. This should enable the developer options, one of which should be to enable USB debugging (I can't tell exactly where this option is as my watch is running Asteroid OS, but it should be in there somewhere).
2) Extract the ADB tools to a known folder. Open a command prompt in that folder. Type the command "Fastboot oem unlock". This should unlock the bootloader on your watch.
3) Install and run KingRoot, this will root your watch granting you access to all the files on it. Again, this step is done at your own risk, I did it with mine and it worked perfectly, but it would be remiss of me to not give a warning at least. It takes a little while to complete so be patient.
4) Open ADB Explorer and hopefully your watch will be listed in the left-hand panel in the devices list. If it is, click on it and then click the browse button, this should display all of the accessible directories. In my case I see "Internal storage" and "Root", open "Root".
5) At this point we are looking for a folder that contains all of the partitions listed by name. On my watch it is in /dev/disk/by-partlabel, but again, I'm running Asteroid OS. Another possibility is /dev/block/platform/dw_mmc/by-name, but have a browse around the dev folder and subfolders, somewhere in there should be folder with lots of files, some named "boot" "recovery" and "system". Make a note of the path to these files.
6) In the command prompt type "ADB shell", the cursor should change to a # symbol (the first time you do this, type "mkdir images", this will create an images folder on your watch that'll just make things a little easier to navigate in the next steps, you only have to run this command once).
7) Type "dd if=/dev/disk/by-partlabel/boot of=/images/boot.img" but change the "/dev/disk/by-partlabel/boot" to match the path that you found on your watch earlier. If successful this will create a "boot.img" file in the /images/ directory. This can take a while depending on the size of the partition, just give it some time and it will eventually go back to the # prompt (boot and recovery are about 16mb, system is about 500mb so takes longer).
8) Type "Exit" which should return you to a normal command prompt. Now type "ADB pull /images/boot.img", this will copy the boot.img file to your PC (into the same folder as the ADB command file).
9) Use the ADB Explorer program to go to the /images/ folder on your watch and delete the boot.img file, it'll just free up space for more images.
10) Repeat steps 6-9 for the "recovery" and "system" partitions, naming the created image files recovery.img and system.img respectively. Don't forget to delete them off your watch after you have copied them to your PC as the system one takes up quite a bit of space.
11) Take the three image files (boot.img, recovery.img and system.img) and upload them to a sharing site of your choice, then let me know the links to them.
I have tested the above steps with my Zenwatch and have successfully extracted and then re-flashed the images. With luck, and the images you produce, this will allow me to re-flash my watch back to factory standard, then I'll see if there's somewhere where I can host them permanently for anyone else that may need them, as I suspect that I am not the only one looking for them.
Fingers crossed!

Hi!
I got problems with ROOTing.
Tried Kingroot, kingoroot - failed at exploiting. Also looked for TWRP, but all links dead.
ED: Failed means that process went to the end without results.

Yeah I've not been able to find TWRP anywhere either. It's gone midnight now and I'm turning in but I'll see what I can find tomorrow. Bear with me, we're almost there.

Just to check, have you done these steps?
On your watch, head to Menu->Settings->About and tap on Build number for 7-8 times until it says you are a developer. When it does, the developer menu should be unlocked on your watch.
Head to Menu->Settings->Developer options and enable ADB debugging. Without this, your computer will not be able to communicate with your watch.

Yeah sure. I also went to the fastboot mode by swiping from right top corner to left bottom at boot, or sth like that and enabled bootloader by oem unlock. Kingroot has problem with rooting because device is unsupported. It tries many root strategies but all of them are unsuccessfull. It's Marshmallow 6.0.1 - m1d65s build.

We could try Kingo Root, an ironically close name to the other app, but beggars can't be choosers at the moment.
Kingo Root, the king root android app for free.
Kingo Root is #1 one click root solution so easy to use. Take your android phone by your control! You will love this feeling - the freedom.
www.kingoapp.com
I tried it on my watch and phone but they're already rooted so the process didn't succeed (obviously), but it could be worth a try.

As I mentioned before I tried both with no success.

Listen, I don't really care about this watch, its laying on my shelf and getting dust.
PM me address and I'll try to ship it to You somehow.
Obvously it's weared and has burnt pixels but stilll working and may be the donor - maybe somehow You'll manage to download the software and share with others.

As I mentioned before I tried both with no success.
Click to expand...
Click to collapse
Ah, that's my bad, I misread your reply, I didn't realise that you had already tried that one.
Listen, I don't really care about this watch, its laying on my shelf and getting dust.
PM me address and I'll try to ship it to You somehow.
Obvously it's weared and has burnt pixels but stilll working and may be the donor - maybe somehow You'll manage to download the software and share with others.
Click to expand...
Click to collapse
Damn man, that is exceedingly generous of you! If you're sure that you're happy to do that then I am more than willing to cover the cost of postage. I'll PM you my details and we can get something arranged, you are an absolute legend sir.

Package sent. Shipping cost was like few screws so donate for any charity when you got it and we're good.

helloworld1337 said:
Package sent. Shipping cost was like few screws so donate for any charity when you got it and we're good.
Click to expand...
Click to collapse
I absolutely will do that, and thank you again, in these days of doom and gloom you have absolutely rekindled my faith in humanity .

For anyone following this thread, the stock firmware files are now available HERE.

Howdy! Nice to see you done the work
BR

helloworld1337 said:
Howdy! Nice to see you done the work
BR
Click to expand...
Click to collapse
Hi BR.
Yup, I eventually managed to work out a somewhat unconventional way to access the storage on the watch, something which I would not have been able to do without your generous donation. I also apologise for not letting you know that it arrived safely, that was an oversight on my part I think caused in part by the dejection that set in from repeatedly failing to root the damn thing .
However, between us we have succeeded in creating the firmware files, and are now able to offer them up to anyone that needs them. I'd call that a job well done .