My X1 (7d-501u) is running 4.4.2, emui 3.0, 400dpi (b005). I tried several times to flash firmware b001 (4.4.2, emui 2.3, 320dpi) without success, it always displayed "update failed" on Recovery screen (EMUI Recovery version 1.0).
I used to flash new roms a few times in the past on this X1 without problem.
It also generated log file on the scard; but I can't read it. I wish to know what it reported in the log file so that I can know reasons of update failure.
Any app to display content of the log file (text edit displayed unreadable text)?
I attach one of the log file here for reference.
bthoven said:
My X1 (7d-501u) is running 4.4.2, emui 3.0, 400dpi (b005). I tried several times to flash firmware b001 (4.4.2, emui 2.3, 320dpi) without success, it always displayed "update failed" on Recovery screen (EMUI Recovery version 1.0).
I used to flash new roms a few times in the past on this X1 without problem.
It also generated log file on the scard; but I can't read it. I wish to know what it reported in the log file so that I can know reasons of update failure.
Any app to display content of the log file (text edit displayed unreadable text)?
I attach one of the log file here for reference.
Click to expand...
Click to collapse
Dear bthoven, sdcard log is a text file and can be read by any text editor. However, I have checked your attachment, each character is a null value (ascii zero). Something is wrong in your phone. Try resetting the phone to factory settings and then try flashing the b001 (4.4.2, emui 2.3, 320dpi) rom.
I was on 4.4.2, emui 3.0, 400dpi (b002) and I had no problem flashing b001.
Thanks. I managed to update to b001 successfully. Still have no idea how I made it.
I found b002/005 are so much smoother than b001 that I thought b001 is still 4.2. I might go back to b005 later. Let me play it for a while.
Related
Hello, I just registered because I have a problem with my IUNI U2 and it's driving me crazy.
I love the phone but I don't like the IUNI OS, it's giving me all sorts of problems, so I wanted to switch to MIUI 7 or 6 since I've always liked it. Few days ago I have noticed that MIUI 7 is now available for a number of other devices, including my IUNI U2.
The problem is this. I downloaded the zip file from the MIUI 7 IUNI U2 page, but when I open it, winrar gives me some sort of error, and the content is only a folder called META-INF, and inside this folder there is a file called MANIFEST.MF. That's it, no other files, and this seems kind of suspicios to me, like the file got corrupted during download and some files are missing? So I asked my girlfriend to download the same package on her PC to see if there were any differences; she downloaded it twice, same error and same contents of the file. I even tried the one on a chinese website, romzj, same thing. I don't know what's going on.
Also, how do I actually change from my IUNI OS to MIUI 6 or 7? I don't know what to do, I'm a total newbie, and this phone (IUNI U2) doesn't have much following, so there aren't any guides on what to do. Does the update wipe my data? Should I backup? How do I use the zip file?
Also, my Android version is 4.3 (the chinese website says that both MIUI 7 and 6 are for 4.4, will this cause any problems?) and build number is U2-32G-BetaV1.3-20140818.
I know my post was written in a confusing way and that I'm asking for a lot of help, but if someone could lend me a hand I would be eternally grateful to them. As I said, I'm kinda unexperienced when it comes to ROMs, so you'd be giving me a huge helping hand. Thanks in advance for your help!
Bump
What recovery did you use? I use the so called "CWM-based Recovery v6.0.5.1 Only for U810". If you replicate that steps you made I can very likely help you...
Hello,
I have a DOOGEE DG-700 that I am trying to resuscitate. All has gone well, except for one problem: the toush area of the screen is shifter tpo the left by about 40 pixels, and nothing in the left area (like the letter 'p', or some 'close' buttons) can be accessed, and I believe this is also why the "swipe to execute" in the TWRP recovery does not work, which makes the recovery tool even more useless that the stock chinese language one :/
I have tried every calibration app I could find, tried changing screen resolutions, which had no effect. I even tried to edit the script.bin file (which I could not find) to change to x/y coords and the /data/data/touchscreen.calibration/files files (which did not exist). There is a utility called "Edit Script EasyTools v2.exe" that claims to edit script.bin, but I not been able to find a copy that is not corrupted.
So... how do I go about moving the active area of the touchscreen to the right about 40 pixels?
I have seen the suggestion of installing a new rom, but I have yet to find another rom for the DG700 that works, including the rom from DOOGEE !
Thanks
Details
Model: Titans2_DG700
Android Version: 5.0
Baseband Version: DOOGEE-Titans2_DG700.2015/05/12
Kernel Version: [email protected]2015/05/12
Build Number: DOOGEE-Titans2_DG700-Android5.0R21-2015_07_02
ROM: custom R21, rooted, made by the XDA dev "Yalita35254"
Recovery: recovery_TWRP_2860_DG700_LP.img
Hi ,
I was trying to install certain application, but I couldn't because of my android version, so then I rooted my device and I edited configuration file (system/build.prop) with system variables such as API version, android version, name of device etc. First I changed only my android version from 4.3 to 5.1 and I rebooted my tablet and my system was fine, but my application still doesn't open. Then I thought that API version could cause the program to start, so I changed it from 18 to 24, I rebooted tablet and every Google Service was crashing with message "Unfortunately, Google XXX services has stopped"
I was trying to open configuration file again, but it's impossible, because of error messages.
I did force restore android system, but it doesn't restore system configuration files
And I installed app with gives access for editing system files again (i got apk file by usb), but I can't open it.
My tablet: Huawei Mediapad t1 8.0
Thank you for help
Dear all,
Though I'm kind of a beginner, I have made much progress backing up and decrypting Whatsapp messages from my old Android phone. However, there seems to have been an even older installment of Whatsapp running from an SD-card on the same device. There are Whatsapp-database files there, but I cannot find the decryption key.
I have tried many ways of going about it:
1. Exploring the root of the SD Card does not lead anywhere.
2. When I use Whatsapp-Key-DB-extractor by Tripcode, it only extracts from the phone's main drive.
3. When I transfer the older databases from the SD-card into their corresponding folder on the phone (either alongside, or replacing them), and then run the Extractor, again no success.
4. In the Apps menu of my phone Configurations, when I go to Whatsapp, the button "Move to SD-card" is unavailable. I figured this may be because only older versions of Whatsapp were able to move to an SD-card and run from there.
5. I downloaded and tried to install older versions of Whatsapp through APK-mirror (with the objective to consequently see if I can move it to the SD-card), but all of them ended in "unable to install"... And anyway, the oldest version available on apkmirror is not as old as the databases we're talking about (which are from June-July 2014).
6. Finally, I noticed that part of the Whatsapp-extractor's procedure is to revert to an older version (2.11.431) and back, so I tried interrupting the process before it sets the new version back. To no avail.
Can anyone come up with a workaround? Those messages are quite precious diaries of those days. My phone is an Experia Z (Model D5503, Android 5.1.1), but it has been stuck in a BootLoop since a very long time. I finally found the time and energy to sit down and see if I can learn how to get the most valuable information out of it after all, and after many, many hours and lots of patience and steady-handedness (the rebooting seems to occur with movement), I decrypted the database from the phone itself. Now I really cannot accept defeat in front of an even older treasure
Oh and post-edit: The databases from 2014 are crypt7. The ones that I DID extract succesfully are crypt12.
Best,
Publo
Change your region via full OTA.
You do everything at your own risk, I am not responsible for any damages. The Chinese version cannot be changed in this way, please use this guide.
This guide allows you to change region within one Android version or upgrade without unlocking the bootloader. Android 13 prepackaged OTA files for India and EU regions will be listed here. If you want to switch to another region, you can ask the author of the post or edit the OTA file yourself according to this guide.According to this guide, user data will not be deleted.
Spoiler: Editing the payload-properties.txt file in full OTA
Download the full OTA from this link Move it to your device's internal memory To edit you will need an advanced device manager that you can download from the Play Store
Through the file manager, we find the OTA file that we are going to edit. Click on the file and open it in the manager, 3 files will open. Click on payload-properties.txt and change the line oplus_update_engine_verify_disable=0 to 1
We save in the upper right and you leave. The edited file will update in about 3 minutes. There may be an update error and there will be two zip archives in the folder, nothing wrong with that! We will keep both files but select the file without tmp to update.
Instructions : 1. Download the full OTA of the desired region and put it in the root directory of the internal memory.
RMX3301_11_C.20_IN
RMX3301_11_C.19_EUEX
RMX3301_11_C.19_RU
2. Installation of the OPLocal_ Update application. Go to your smartphone's settings, then Apps > Management. applications, 3 dots and check Show System ! Look for SOFTWARE UPDATE and clear this app's cache and data! Then install the OPLocal_ Update app for Android 12 or 13 (choose the version that is current on the device)
OPLocalUpdate_For_Android12.apk
OPLocalUpdate_For_Android13.apk
3. Installing an update through a third-party application! Next, open the app we installed and update it through it (gear top right and select the .zip file in the root directory of the internal memory), an installation window should appear! If everything is fine, the process will start and you will be prompted to restart your smartphone after installing the update. Installation takes 20-30 minutes.
After restarting your smartphone, you are in a new region.
It is recommended to flash the firmware file twice to flash both slots!
Many thanks to 4pda forum members KRD_RUS and [email protected] who created the tutorials.
Spoiler: Video instructions
Excellent tutorial. This was the only way possible, I was able to change the Rom from Global (previously Chinese) to INDIA region.
Thanks pal for all your help!
What is the point of changing to India region? Does the india rom have built in call Recorder?
I chose these regions because of the GDPR version and export.
Call recording has RU version.
Stano36 said:
I chose these regions because of the GDPR version and export.
Call recording has RU version.
Click to expand...
Click to collapse
Only RU has call Recorder?
How does this affect ota security updates?
The RU version has recording for sure.
OTA will run smoothly.
With this procedure I won't need to unlock the bootloader? So does that mean that NFC and banking apps don't work perfectly?
Yes, they will work without problems.
Hello
You only linked India and EU roms, is the RU rom available somewhere ?
Link added
from IN C12 my can't transfer through EUEX C12 this way? Thanks
You can
Does Russia have C 12 or only C 08 because Realme wont update due those stupid sanctions?
The Realme server only offers C.08, but C.12 should arrive by air.
Hi! I'm on GDPR version (GT2 RMX3311) and I wold like to unlock the bootloader by switching region to India, unlock via deep testing apk, and flash back the GDPR firmware, will this work? Will the bootloader remain unlock if I flash gdpr fw back?
Tried it, it doesn't work for GT 2.
@daniml3 tried it
So, I flashed the Indian ROM and all was fine, except that RIL didn't work, so l didn't have a working SIM and neither an IMEI, so I couldn't unlock the bootloader as it needs a working IMEI for that.
Click to expand...
Click to collapse
Has anyone tried to use the (RMX3311) "modem.img" in the (RMX3312) "payload.bin" and then to flash the RMX3312 FW on the RMX3311 GT2 ?
RMX3311 said:
Has anyone tried to use the (RMX3311) "modem.img" in the (RMX3312) "payload.bin" and then to flash the RMX3312 FW on the RMX3311 GT2 ?
Click to expand...
Click to collapse
I don't know about it
Thank you so much !
According this method, the Taiwan Ver. was successfully converted to the India Ver. Install google play coloros Phone APP. can automatically record calls
I have downloaded the firmware file and placed it in the root folder, but the updater still says "Move installation package into root directory".
Help would be appreciated. Thanks.