Hello,
I'm new here so I hope this thread is where it should be and it's okay to post such an experience here.
So, few days ago I bought Sony Ericsson X10i. As I understand, it was from UK's 3 Network. I bought it in Lithuania, it was already unlocked. It had R2BA020, so I rooted it, deleted some of the unnecessary apps, but... I couldn't stay calm when I knew there is newer firmware out there (I am an update maniac - all my software needs to be updated, sometimes to alpha versions). So I haven't found a guide how to update firmware here, on xda (haven't search for more than few minutes), but first result on the Google gave me the guide at xperiax10.net (I can't post the full link here as I am a new user).
I downloaded the Nordic Generic X10i Firmware (R2BA026). Started SEUS, rewritten the current firmware. Next - rename the new files to match the old files and backup the old files. So, FILE_277505303 became FILE_277466517 and FILE_277508959 became FILE_277410324.
First attempt at cheating on SEUS:
deleted the old files, successfully replaced the smaller file, but failed at the bigger file.
Second attempt:
delete the old files, successfully replaced the smaller file, but failed at the bigger file. BUT, this time, I turned on my phone and noticed a small difference - in the locale settings, first option was United States (previously it was United Kingdom). So, third attempt:
removed only the big file, left the smaller with the old filename (FILE_277508959). SEUS started downloading the files and I see the difference in download size. It matches the Nordic Generic X10i Firmware (R2BA026). And the filenames are FILE_277505303 and FILE_277508959. Update completes, I start up the phone and what I see is new firmware! Everything works, so I download Universal Androot and root the phone.
The purpose for this post - For those who cannot debrand the phone successfully, you only need to place the smaller file in the blob_fs and then try to repair the phone twice. It worked for me, so I hope it will work for you too and make your life easier
Sorry if this post is too large
Related
Hi everyone
I really need your help guys, I'm desperate!! I wanted to upadate my x10 mini to froyobread following all the instructions.
1. I rooted the phone with SuperOneClick
2. I flashed it using FlashTool, and here is the problem: I used a different firmware (e15i_2.1.1.a.0.6_Nordic) <--- That's the firmware for Xperia X8. The flashing was succesful, but when it finished, the phone started rebooting over and over with only a blackscreen (no SE logo).
I've tried many ways to restore the phone, such as:
1- FlashTool with a firmware for x10 mini (The problem is I need to check "USB Debugging" inside the O.S., so I couldn't repair it this way.
2- I tried PC Companion and SEUS but when I follow the program steps it says "Your phone is up to date so no needs bla bla bla..."
I don't know what else to do... I'm frustrated and really hope you can help me guys.
Thank'u
SOLVED:
Finally I fixed the problem flashing with x10flash and 1.6 android firmware (it's called "E10i_1.6 1.2.A.1.174 406.7z"). (x10flash isn't the same as Flashtool, so if you wanna recover to life your phone, you must use x10flash)
I put the rar files of the firmware 1.6 inside the "firmware" folder from "X10Flash-2.1" and then I flashed with the X10flash.bat file.
After that, when te x10flash.bat was opened, I select number "2" and then "N". Next, you have to select your operative system. (win xp, vista, 7, etc)
Finally, you can install the rom or baseband whatever you want.
(I can't put the links 'cos I'm a new member, but you can google them)
- E10i_1.6 1.2.A.1.174 406.7z
- x10Flash
I hope this helps.
Do you still have that files? I am unable to download that files . I have googled them but links have expired.
Thanks.
Hello, my first post in these forums. Have been exploring a bit through all the information, and I think I need some help. I am pretty experienced with networks and windows/linux usage and administration, but have been using an android phone for just 2 weeks.
I have a Sony Xperia U with Android 2.3.7 Gingerbread, as it came out of the box. Any updates have yet to arrive, PC Companion says that I am using the last available firmware but I know that this is not the case as several ICS firmwares have already been published. Bootloader is locked, but can be unlocked.
I would like to flash my phone manually to ICS, using the last (or the best as recommended by you) firmware update. I would like to start with a stock rom, try rooting and than try custom roms when I get accustomed to the process of flashing. Mostly, I want to use the phone to the most of it's abilities (battery, speed, graphics etc).
I have found here that last firmware is 6.1.1.B.1.89, but I could not find it here on the forums.
First, I am in a dilemma which .ftf file to use for my phone. I have downloaded:
XperiaU_ICS4.0.4_nu.ftf
ST25i_.54_Nordic_DevStaff.ftf
ST25i_6.1.1.B.1.54 GENERIC - user_Sony.ftf
I have checked two threads in more detail:
http://forum.xda-developers.com/showthread.php?t=2028139
http://forum.xda-developers.com/showthread.php?t=1974430
What does SI Number or ROM Location 1263-1753 / WORLD mean? My number on the back of the phone (behind the battery) is 1261-9036. What happens if I flash 1263-1753 firmware to my phone? Please recommend an ICS firmware that performs well and is applicable to my phone.
Can I use ST25i_6.1.1.B.1.54 GENERIC - user_Sony - since there is no SI Number or ROM Location there? Can I root this firmware through Flashtool OR Root_with_Restore_by_Bin4ry_v26. I would like to root to be able to delete bloatware from Sony.
I have also looked at Freexperia project, but it says there that the version is still in development and has issues with FM Radio - which is something I use every day.
Other than this, I installed flashtool-0.9.10.1 on Windows 7. I installed the drivers in Flashtool\drivers. All drivers said "Ready to use". Rebooted the PC, switched off the phone. When I connected it while holding Volume-up, it said ready to use. When I connected it while holding Volume-down, it says device disconnected. Have tried reinstalling the drivers (Flashboot and Flashmode are selected), Windows Safe Mode, disabled Microsoft Security Essentials. I went to Device Manager (as suggested in the forums) and I uninstalled "Android Device", the drivers would still not work.
This morning I remembered that USB debugging was not checked on the phone - might this be the problem? I will try again when I get home. Please provide any other tips to connect the Xperia to Flashtool.
Thank you for all replies in advance. All best.
[UPDATE]
I went to Sony's website for unlocking the bootloader. Is the Android SDK necessary for Flashtool too? Do I need the android_winusb.inf file provided there?
Thanks for all the information here.
I flashed my phone with ST25i_6.1.1.B.1.54 GENERIC - user_Sony, along with [Kernel][Sony Xperia U][March - 24] Sliding_XU [Stock][CM]
First impression is that it is laggy, much slower than Gingerbread. Any recommendations?
All best.
if u are on stock android u will hate it. Its time for u to start searching and flashing custom stock based roms... These are usually VERYY smooth... NO MATTER WHAT DO NOT STAY AT STOCK ANDROID, trust me, u will want to take a hammer and smash ur phone... Also, consider using kernels that allow u to overclock ur phone... Do not worry, if u overclock from 1ghz to 1.15ghz i dont think u will have any problem... Have been using overclocked phone for 6 months and so far no problem...
Thank you for the reply. I am using CM 9 (FXP213) as of an our ago, and I can feel the amazing difference. As I can see, CM has very basic apps by default. As it says on the CM wiki:
Optional: Download any supplemental 3rd-party applications packages for the device you wish to use. (You have to install a 3rd-party app to get the Google apps, like Gmail, Play Store, and Youtube.)
Where do I download these from? Any other resources on CM that are good for a new user?
All best.
KitKat for the Omate TrueSmart
Congratulations, you made it this far and managed to keep your unit alive long enough to upgrade it to the next level!
4.4.2 Changelog:
================
Fixed glitch in boot animation to make it smoother
BTLE profile and PAN profiles added
Full Settings Menu
Functional Accessibility Menu
Updated Wi-Fi Drivers, now supports ip6, ip4, and low-power mode
Updated GPS Drivers, lock-on after initial lock and AGPS update should be quicker
Kernel updated from 3.4.5 to 3.4.67, supports SELinux
Unlocked bootloader and insecure kernel allows for root access through SU
Google Play Services included
Google Talkback/Voice Search integrated
Fixed glitch where Voice Search would not complete spoken sentences
TWRP updated to 2.8.3.0 with full features and MTP support
Camera now operates at 5MP/720P without force closing
Security holes have been closed
MALI 400 drivers updated
Battery management integrated; after first boot battery readings should be accurate
Sound issues fixed; microphone should no longer sound muffled
Soft reset implemented, holding both buttons for 10-15 seconds should power down or reset unit
ART mode implemented, allowing for faster and more efficient performance
Known Issues:
=============
Sensors are non-functional until updated drivers are available (if they become available)
Settings is not accessible from status bar icon
1900MHz units are unable to access 3G data currently (if a modem becomes available this should change)
Bluetooth connectivity may occasionally drop out depending on data load
APNs are not automatically added
IMEI may be lost or corrupted after installation
Instructions:
=============
REQUIRED PROGRAMS:
1) SP FLASH TOOL
2) MTK DROID TOOL
3) WINDOWS OS XP or HIGHER
The All Tools suite for MTK devices can be found here:
MTK All Tools Suite
****** You must install the preloader drivers for your device using the 32-bit or 64-bit installer (dpinst) for your operating system before you continue. ******
I suggest making a full backup of your device either in TWRP or in MTK DROID TOOLS (1:1) to preserve valuable data or in case of a failed upgrade. You should always back up your IMEI/NVRAM in DROID TOOLS for safe-keeping and this is no different.
Download the full set of factory images here:
Omate 4.4.2 Factory Image RAR
Extract the contents of the ZIP file to a known directory and proceed to the next step.
Next, navigate to the Settings menu on your Omate TrueSmart and, under Accessibility, disable Quick Boot. This is the only way to enter Download mode reliably. With that completed, power down your watch.
Finally, open the scatter file (mt6572_scatter_emmc.txt) found in the directory you extracted the ZIP file to in SP FLASH TOOL and check to make sure each file is present. You may need to manually add the system.img and recovery.img. To do this, double click on the empty box and select the file.
Once you've made sure each file matches, go to the drop-down menu where it says "Download" and select "Firmware Upgrade". Take one last look to make sure every file is selected and press the Download button on the top left of the screen.
With the watch powered off, go ahead and plug it in. THEN WAIT. It will take between 5-10 minutes to fully upgrade your unit. You should see a red bar, then green, then purple, then yellow. If you get any error that says "BROM DLL ERROR" note down the error number and send me a message. If it gives you a green checkbox, you're done with this step.
Now you're ready to boot the watch. Press and hold the power button until it powers on. The first boot will take approximately 5 minutes to complete while it assembles all of the information. Once it finishes, power down the watch. Hold the home (bottom) button and press and hold the power (top) button simultaneously (at the same time). You'll see a recovery menu. Press the power button to boot into TWRP. From there, select "Wipe" followed by "Factory Reset". You will want to reset the watch to factory settings. You can either make a backup or go ahead and reboot the system.
Congratulations! You should now be on Android 4.4.2 for your Omate TrueSmart.
NOTES
=====
If you're missing APN information I suggest you either restore previously saved APNs or add them manually if they disappear. Currently 3G data will not work on 1900MHz units.
This firmware was designed for UMEOX smart watches operating on the x201-series MT6572 chipset. I am not responsible if you damage your watch because you flashed the firmware incorrectly or to the incorrect watch.
If you have any questions as to whether your watch is compatible, please message me.
It is IMPOSSIBLE to brick your watch if you are flashing this firmware. If for some reason you think your watch is bricked or you feel uncomfortable flashing this firmware you are welcome to send your unit to me (if you pay shipping) or I am available to help over Chrome Remote Desktop to flash it for you.
If you are having issues getting the firmware to work, please send the following information to me:
Watch Manufacturer
Date Received
Last Known Firmware
Case Material
And I will answer on a case-by-case basis to help you troubleshoot. I never make guarantees but I promise to help as much as I am able.
Finally, please take the time to thank the brave soul who voided his warranty to get me the prototype firmware for this. I won't reveal his name for security's sake, but he obtained a developer unit from another company who uses the x201 chipset and was kind enough to upload the system dump in September of last year. I would have presented this sooner to you guys, but until the method for flashing the S8 firmware was released I had no idea why I couldn't get it to work.
SPECIAL THANKS
==============
Laurent LePen, for giving me the tools from UNOVA to make this possible
@Dees_Troy, for having the patience to flash the firmware, assemble a system image, and update TWRP
Derek Serianni, for flashing his watch 42 times to test the firmware
Christos Vorkas, for testing SIM functions and the early firmware
@AdamOutler, for advice operating Linux and troubleshooting errors
The Anonymous Firmware donor, who voided his warranty and bravely e-mailed me about 1.5GB worth of files
XDA, for always having that clinch moment where someone has a breakthrough that helps the rest of us
KNOWN COMPATIBLE UNITS:
IconBit:
Callisto 100, 300
SimValley:
Pearl AW414, AW420/1
UMEOX
X201
Omate
TS-1/TrueSmart 512MB/4GB Edition
TS-1/1900MHz 1GB/8GB Extreme Edition
TS-1/2100MHz 1GB/8GB Extreme Edition
For Root, download Chainfire's latest SuperSU package and flash in TWRP:
SuperSU 2.44
Derek Serianni, for flashing his watch 42 times to test the firmware
Click to expand...
Click to collapse
I think that number is a lot higher actually..... but, 42 is quite fitting as this is now the answer to the ultimate question...
It has been an exciting couple of days testing and flashing.
Despite all the trial and errors, not once did the watch become unrecoverable.
If you load Google Now Launcher and the latest Google Search APK (and setting it up properly) you can use the "Ok Google" feature from the lock menu as well as in the OS.
I stopped wearing my LG G and am now wearing the TS daily....
Kudos for all the hard work!
I knew there was light at the end of the tunnel!
D.
Great job!
hi dan,
i have tried to flash this to my EU 1/8G Pre May Omate TS.
Watch Manufacturer - Omate
Date Received - Pre May
Last Known Firmware - EU Ensec Stock 0706
Case Material - Steel
A few questions:
1) the downloaded KK Omate rar file does not include UBOOT.BIN or a BOOT.IMG file. Am I supposed to leave it blank or use the UBOOT / BOOT IMG from my current Omate's backup?
EDIT: I have tried using the UBOOT.bin and BOOT.IMG from another KK thread but still run into the same "CheckSum Failed" error i mentioned below: http://forum.xda-developers.com/showpost.php?p=57433563&postcount=189.
2) under FLash Tool: the ANDROID file is usually blank - i have selected system.img from the rar file for the file to be flashed for this. Is this correct?
3) When flashing via FlashTool, about 27 seconds into the flash (i see a RED Bar, then it changes to a couple of BLUE "Read Back" bars), I keeping getting a error saying "CheckSum Failed". I have tried redownloading the KK Omate rar file and trying again but to no avail.
EDIT: I have tried with different ports, different cables, including cleaning the Omate TS's ports with no luck. Just prior to the flash, i was able to do a full backup so it does seem strange and does not seem specific to the cables/ports/contacts on the TS.
UPDATE: Seems to be working - TRY Flash Tool v3.1332 instead of the latest V5.1352. It is now flashing fine as mentioned by Dan.
FINAL: My TS boots up fine with KK now! If you face the checksum error as i did, try using SP Flash Tool v3.1332 instead! - LINK HERE: http://androidxda.com/smart-phone-flash-tool
Any advice on the above?
NO UBOOT
Trying to flash this on my Omate 2100 unit but the UBOOT is missing for me? Got the system.img and recovery.img added but no uboot.
I am also not sure what to select as "BOOTIMG".
Watch Manufacturer - Omate
Date Received - Pre May
Last Known Firmware -ZGPAX S8
Case Material - Steel
I have made it.
But Attention:
No baseband is included.
Baseband for EU, 2100 is not included in this ROM.
So you can not use the phone to call.
I am back to ZGPAX S8.
Watch Manufacturer - Omate
Date Received - Pre May
Last Known Firmware - RSR 0.8
Case Material - Steel
Same as aeron16 with the KK Omate rar file not including UBOOT.IMG or a BOOT.IMG and using system.img for the ANDROID file.
I've tried via Win7 & Win 8.1, Win7 didn't install the preload drivers but Win8 did..
..could anyone that has sucessfully installed it create a flashable image we could use directly in TWRP?
Caboose1979 said:
Watch Manufacturer - Omate
Date Received - Pre May
Last Known Firmware - RSR 0.8
Case Material - Steel
Same as aeron16 with the KK Omate rar file not including UBOOT.IMG or a BOOT.IMG and using system.img for the ANDROID file.
I've tried via Win7 & Win 8.1, Win7 didn't install the preload drivers but Win8 did..
..could anyone that has sucessfully installed it create a flashable image we could use directly in TWRP?
Click to expand...
Click to collapse
Mike? hehe did you get the same error i had? with the CheckSum failed as well?
Isn't the baseband included under "0 Needed files -> NA/World Baseband"?
I can not check if valid files. My TS is not booting/reacting to Flash tool anymore...
Not sure if I did it correctly but because I could not find the boot.img within the supplied files I took the boot.img from the other kitkat rom here on xda. Have at least a working TS now .
Only problem right now is that the home button is not functioning as the home button. It sets the volume to max.
seppen said:
Watch Manufacturer - Omate
Date Received - Pre May
Last Known Firmware -ZGPAX S8
Case Material - Steel
I have made it.
But Attention:
No baseband is included.
Baseband for EU, 2100 is not included in this ROM.
So you can not use the phone to call.
I am back to ZGPAX S8.
Click to expand...
Click to collapse
I had the same issue as well!
Thanks. Works well like the other early ROMs and is a bit better prepared including Google Play etc. Can we remove the extra apps like QQ etc from the image for a future release? Edit that might have been my fault from not wiping after flashing although I was pretty sure I had already removed them from the ROM whilst creating a flashable zip.
When turning on Wifi I do get an NVRAM error initially in the list of Wifi items. It fairly quickly finds real ones and it connects fine to my AP.
I have the issue with the second button turning up the volume too. There is a fix in the other thread for this.
Also I had to manually select system.img, the recovery, uboot.img and boot.img (the latter two weren't in the archive so I took from the X202 image in the original KK thread).
Glad to see Omate somewhat taking credit on Facebook. It seems I'm banned on Facebook from recently posting after commenting that they probably shouldn't be taking credit for this. The initial announcement a few days back has 14 missing/hidden comments. Oh so childish LLP - I'm sure you're reading.
I'd like the sensors if possible, mainly for a shake/rotate to wake up function..
---------- Post added at 11:43 PM ---------- Previous post was at 11:38 PM ----------
Caboose1979 said:
could anyone that has sucessfully installed it create a flashable image we could use directly in TWRP?
Click to expand...
Click to collapse
I'm going to take a look at doing this when I get a chance in the next couple of days. I had a basic one working with just system and boot images of the KK ROMs. It should be possible but I'm kinda new to this so not sure if there are any limitations when flashing everything like this. I do need to make sure I know all of the device names to flash.
Hi Guys,
Not sure where I am going wrong, can't make head nor tails so far.
Truesmart doesn't look to be detected in SPFlash, is SPflash what is meant about mtktools? i can find an application in that folder..
On from that i am also missing the .img files that the others are.
sorry to be a hassle, i will do my best to work it out, but just need a bit of help getting off in the right direction please,
also i haven't done any other flashing etc with my truesmart, is there anything i should be doing prior for brick protection?
it is a 2100mhz model
Cheers
burlyoaf said:
Truesmart doesn't look to be detected in SPFlash, is SPflash what is meant about mtktools? i can find an application in that folder..
Click to expand...
Click to collapse
MTKDroidTools is different to SP Flash Tool. They are 1 and 2 respectively in the All Tools folder.
Follow the instructions exactly particularly the order. Turn the watch completely off (disable Quick boot), click download and *then* plug the cable in.
Quick Update:
My EU 1/8G Omate TS-1 Pre-May is up and running fine (see my earlier post for some tips / advice based on the issues i had).
1 major issue as below:
However, under Baseband - it shows unknown, and similarly in IMEI - it also shows unknown.
i tried to flash the old 2100 World Baseband.zip in TWRP, but no luck,
tried to use MKT Tools to restore my NVRAM but no luck either (just shows install\data\nvram) and then nada.
minor issue: home button is defaulting to UP Volume instead of HOME function. I will try to flash the FIX_HOME.zip in the other thread and report back.
any advice Dan or anyone else who has theirs working?
If it says uboot, that's the lk.bin.
seppen said:
Watch Manufacturer - Omate
Date Received - Pre May
Last Known Firmware -ZGPAX S8
Case Material - Steel
I have made it.
But Attention:
No baseband is included.
Baseband for EU, 2100 is not included in this ROM.
So you can not use the phone to call.
I am back to ZGPAX S8.
Click to expand...
Click to collapse
Stop with the attentions. The baseband is included. I've had at least 5 people flash it with no issues.
IF you are missing a baseband, sit tight. Try flashing the UNOVA system image, then flash this again.
IF you are having checksum issues, either use an older version of flash tool OR format and flash the stock firmware.
The LK and Kernel must have been a goof on my part. I'll fix that.
Hi,
Before unlocking the bootloader on my Xperia Z5 Compact, I want to backup the drm-keys. This can only be done be rooting the device, without unlocking the bootloader. To do this I need any version prior to 32.0.A.6.200. So far so good.
I've used Xperifirm to download an old firmware version (several, actually) and tried to flash it using Flashtool. Here's the problem. It never gets past the following lines:
Code:
20/038/2016 11:38:49 - INFO - Processing modem.sin
20/038/2016 11:38:49 - INFO - Checking header
20/038/2016 11:38:49 - INFO - Flashing data
Yesterday, I've waited for several hours for it to finish, but it never does.
What I've tried so far:
- different cable
- different USB-port
- different computer running a different OS
- several firmwares from Xperifirm: they all fail in exactly the same way
- Restoring the firmware with the Xperia PC Companion: works like a charm, but I'm stuck again with the newest firmware again
Also: I've created an .ftf file from the stuff the PC Companion downloads and when using that in Flashtool, it doesn't work either. Using the official PC Companion however does work.
My Z5 Compact (E5823) is non-branded and should be without simlock.
Thanks a lot!
My friend and I had the exact same issue with our E5823 (Z5 Compact). Turns out when you download flashtool, there is a patch at the bottom of all the download links that you need to apply. Once you replace the .jar file in C:\Flashtool with the patched version, it should work fine.
Took me way longer than I want to admit to figure out I was missing the patch...
DAVe3283 said:
My friend and I had the exact same issue with our E5823 (Z5 Compact). Turns out when you download flashtool, there is a patch at the bottom of all the download links that you need to apply. Once you replace the .jar file in C:\Flashtool with the patched version, it should work fine.
Took me way longer than I want to admit to figure out I was missing the patch...
Click to expand...
Click to collapse
I think there is an even newer version out now. But I had that same problem of not adding the patch as well.
Thanks a lot, it seems you're right about Flashtool. The problem occurs with version 0.9.22.0 (both x86 and x64). The version currently on the website is 0.9.22.1, so I suppose the patch you're refering to is now included in the main download.
Actually I've ended up using Flashtool 0.9.18.6, which did the trick fine.
So thanks again, my problem is solved
I tried to change the Chinese Firmware to Global firmware to (Meizu Pro 7) and now I have a problem.
I followed this guide on this web:
chinahandys .net (I can't copy the link here since I have a new user
and so I deleted the file "boot.img"
I also couldn't open the Update.zip file with Winrar or another archive program.
then, I tried to do this :
"10. In FlashFire, select the small plus icon at the bottom right and select “Flash ZIP or OTA”. Select the “update.zip” file and confirm the pop-up with the tick at the top right"
but I couldn't find the “update.zip” file there.
finally, I tried to open the update.zip by pressing "Update".
since then my phone won't start.
The only thing i can do is pressing the "plus" button and another button below which will lead to me to a screen of Updating the system. when I try to do it's wrong because "firmware not found".
My phone is stock on the screen "flyme".
please help me!! I just bought this phone
(danhdongufixer) he is on Facebook.... He single handily brought my pro 7 plus back from the dead get ahold of him he's wizard .
I had same problem and this guy fixed my phone get in touch with him because there is nothing else you can do meizu left a lot of us hanging for over 3 months and no help . Good luck
You maybe don't use the good Firmware
maorsah said:
I tried to change the Chinese Firmware to Global firmware to (Meizu Pro 7) and now I have a problem.
I followed this guide on this web:
chinahandys .net (I can't copy the link here since I have a new user
and so I deleted the file "boot.img"
I also couldn't open the Update.zip file with Winrar or another archive program.
then, I tried to do this :
"10. In FlashFire, select the small plus icon at the bottom right and select “Flash ZIP or OTA”. Select the “update.zip” file and confirm the pop-up with the tick at the top right"
but I couldn't find the “update.zip” file there.
finally, I tried to open the update.zip by pressing "Update".
since then my phone won't start.
The only thing i can do is pressing the "plus" button and another button below which will lead to me to a screen of Updating the system. when I try to do it's wrong because "firmware not found".
My phone is stock on the screen "flyme".
please help me!! I just bought this phone
Click to expand...
Click to collapse
Hi,
For 3 month, I hope you have find the solution. If you don't, here is mine :
I had the same problème on my phone.
I couldn't reinstall it, I think the version that I downloaded wasn't compatible with the "Chinese" version of my mobile.
You need to find the good firmware !
Could you try with this chinese firmware : MEIZU PRO7 Standard Version -Flyme6.1.3.2A-7.0
It's worked on my phone.
So,
Press and hold the volume up and power button until the screen goes on recovery mode.
Connect the device to the laptop or PC, you can open the device. You will see an empty partition named recovery.
Now copy the downloaded firmware of your phone and place it in the recovery partition. Just copy update.zip to recovery partition.
Now in the phone select update firmware and clear data and press next.
The phone will reboot and install the firmware.
Wait, wait, wait 15mn be patient.
tell me if it's working on your phone.
excuse me for my poor English !
Math32 said:
Hi,
For 3 month, I hope you have find the solution. If you don't, here is mine :
I had the same problème on my phone.
I couldn't reinstall it, I think the version that I downloaded wasn't compatible with the "Chinese" version of my mobile.
You need to find the good firmware !
Could you try with this chinese firmware : MEIZU PRO7 Standard Version -Flyme6.1.3.2A-7.0
It's worked on my phone.
So,Press and hold the volume up and power button until the screen goes on recovery mode.
Connect the device to the laptop or PC, you can open the device. You will see an empty partition named recovery.
Now copy the downloaded firmware of your phone and place it in the recovery partition. Just copy update.zip to recovery partition. Now in the phone select update firmware and clear data and press next.
The phone will reboot and install the firmware.
Wait, wait, wait 15mn be patient.
tell me if it's working on your phone.
Click to expand...
Click to collapse
Hello!
Was everything, such as google playstore and english language, still working on you phone after you updated the firmware?
I was also wondering if theres need to backup the IMEI somewhere?
Im currently running a modified verision of 6.1.3.2A which doesnt have all the features for the 2nd display and hence looking for an upgrade.
Leone1 said:
Hello!
Was everything, such as google playstore and english language, still working on you phone after you updated the firmware?
I was also wondering if theres need to backup the IMEI somewhere?
Im currently running a modified verision of 6.1.3.2A which doesnt have all the features for the 2nd display and hence looking for an upgrade.
Click to expand...
Click to collapse
I used this chinese version less than 10mn. I would advise you to install the G firmware !
I didn't install the playstore (too thing in chinese in this firmware) that's why after running the version 6.1.3.2A, i used this tutorial :
https://forum.xda-developers.com/showpost.php?p=75297402&postcount=70
"Download the firmware Flyme 6.1.3.2G from here
http://www.flymeos.com/firmwarelist?modelId=88&type=1
after you can do the instructions in video
https://www.youtube.com/watch?v=aDp6oZL4Wx4 "
Be careful when you install superSU to do the same thing as in the video. I don't do the same than on the vidéo that's why i need to reinstall the chinese firmware. After the installation i wait 15mn and my phone stays on Flyme. i restart it and it worked for installing busybox and flashfire.
I wish you bon courage !
Math32 said:
I used this chinese version less than 10mn. I would advise you to install the G firmware !
I didn't install the playstore (too thing in chinese in this firmware) that's why after running the version 6.1.3.2A, i used this tutorial :
https://forum.xda-developers.com/showpost.php?p=75297402&postcount=70
"Download the firmware Flyme 6.1.3.2G from here
http://www.flymeos.com/firmwarelist?modelId=88&type=1
after you can do the instructions in video
https://www.youtube.com/watch?v=aDp6oZL4Wx4 "
Be careful when you install superSU to do the same thing as in the video. I don't do the same than on the vidéo that's why i need to reinstall the chinese firmware. After the installation i wait 15mn and my phone stays on Flyme. i restart it and it worked for installing busybox and flashfire.
I wish you bon courage !
Click to expand...
Click to collapse
Ah ok, so you only used it to be able to flash the global rom on?
Ive read multiple places that its not possible to update from A to G, thats why i was thinking about going to the 7.0.0.0A ROM instead. The shop i bought it from (CECT, who are not very well informed at all) told me it would brick the phone to go to G from A, my phone is apparently not intended for global sale thats why they make their own version and flashes it on...
So now im just looking for someone who can confirm that updating to the A-rom wont remove google play or english.
EDIT: I have the Helio P25 model