There are some chinese distributors that accidentally clears your NVRAM when flashing their ROM, thus the phone loses IMEI, MAC and other serials.
There are some methods that fixes this by copying files to data/nvram etc, but that's just a temporary fix, and resets after a wipe.
Here is a proper solution. Windows 10 tested.
Do NOT connect your phone yet. Have it turned off completely.
First you need to install the drivers.
Run
Code:
All MTK USB Driverv.9.2.PDanet.Adb 2015\SmartPhoneDriver\Driver_Auto_Installer_SP_MTK\Driver_Auto_Installer\SmartPhoneDriver\x64 or x86\spinstall.exe [B]WITH Administrator privileges[/B]
Maybe there are some other drivers needed, I don't remember all that I've installed. You will find a lot of drivers in my Google Drive (link at the bottom).
Install SP META, and run it. You need to select AP NVRAM Editor and press Connect.
Now connect the phone, it should detect it, and pop up a window.
{
"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"
}
Press Read From NVRAM. Browse APDB_MT6795_S01_L0.MP6_W15.32 and press OK on the warning.
WIFI MAC:
SELECT RDEB LID/AP_CFG_RDEB_FILE_WIFI_LID/1 and press Read From NVRAM
aucMacAddress will be your WIFI MAC address. You need to write every 2 character like 0xD0, 0xB3, etc.
Google drive link with everything you need: HERE
does this method work for all mt6795 device? I need to change the imei of my letv x600. Thank you
lala206 said:
does this method work for all mt6795 device? I need to change the imei of my letv x600. Thank you
Click to expand...
Click to collapse
Yes, it should work. You might need a different APDB file, but that should be in the ROM package for your phone.
Xmister said:
Yes, it should work. You might need a different APDB file, but that should be in the ROM package for your phone.
Click to expand...
Click to collapse
thank you for your reply but in the rom package of letv x600, I couldnt find any APDB file. Could you take a look at the rom package in the attachment for me. Thank you!
First try it with my APDB, only if it not works find another.
And it should be in ROM packages that can be flashed with sp flash or fastboot.
lala206 said:
thank you for your reply but in the rom package of letv x600, I couldnt find any APDB file. Could you take a look at the rom package in the attachment for me. Thank you!
Click to expand...
Click to collapse
here is the rom package that can be flashed with sp flash tool. Would you mind taking a look at it again. I wonder if using your file might brick my phone or not. Thanks!
lala206 said:
here is the rom package that can be flashed with sp flash tool. Would you mind taking a look at it again. I wonder if using your file might brick my phone or not. Thanks!
Click to expand...
Click to collapse
I can't see it, you may have to get it from somewhere else then.
It can't brick your phone. This only touches your NVRAM, so make a backup of it, and you are good to go.
i tried this, i lost my imei and all the time i do a factory for install new rom i've to place the mpb file inside nvram folder, but don't work. I can modify the array in IMEI[0] and IMEI[1], i can write it to nvram (and it remains inside) but if i reboot the phone, i have no IMEI :/
EDIT: i tried to flash an nvram backup of a friend with the same smartphone too, i have initially his imei that i can canghe with the mpb metod, but if i try this guide with his backup flashed his imei is not saved into the array IMEI[0] or IMEI[1]...
ILGreat said:
i tried this, i lost my imei and all the time i do a factory for install new rom i've to place the mpb file inside nvram folder, but don't work. I can modify the array in IMEI[0] and IMEI[1], i can write it to nvram (and it remains inside) but if i reboot the phone, i have no IMEI :/
EDIT: i tried to flash an nvram backup of a friend with the same smartphone too, i have initially his imei that i can canghe with the mpb metod, but if i try this guide with his backup flashed his imei is not saved into the array IMEI[0] or IMEI[1]...
Click to expand...
Click to collapse
If the written values remains inside nvram, then it's most probably some modem inconsistency. First of all, don't change the nvram folder on data, it can overrule the changes you made in the real nvram.
And try to flash a stable rom with MI Flash after you have changed the values in your nvram.
Note: I hope you wrote the 2 digits backwards, as I said so.
Xmister said:
If the written values remains inside nvram, then it's most probably some modem inconsistency. First of all, don't change the nvram folder on data, it can overrule the changes you made in the real nvram
And try to flash a stable rom with MI Flash after you have changed the values in your nvram.
Note: I hope you wrote the 2 digits backwards, as I said so.
Click to expand...
Click to collapse
I write the 2 digit backwards, i think i will try to change again the nvram with my value and after that i use Mi Flash, but i've just change the nvram folder, 2 second before i read you're replay :crying: .
ILGreat said:
I write the 2 digit backwards, i think i will try to change again the nvram with my value and after that i use Mi Flash, but i've just change the nvram folder, 2 second before i read you're replay :crying: .
Click to expand...
Click to collapse
Do a factory reset, that resets the nvram folder. Or you can just delete the nvram folder from your data.
Xmister said:
Do a factory reset, that resets the nvram folder. Or you can just delete the nvram folder from your data.
Click to expand...
Click to collapse
Man I LOVE YOU!!! I want you here for a kiss, all permanent restored.
First i delete the folder nvram, then factory reset from twrp.
I wasn't sure than all was deleted, so i flash the fastboot ROM with MiFlash, i change the IMEI with your guide and last i re-flash with MiFlash.
After reboot IMEI were OK, but for another check i pick twrp, reboot, factory reset again and flash last developer Miui EU (.29) and all work like a charm, so really really thank you ^^
Inviato dal mio Redmi Note 2 utilizzando Tapatalk
ILGreat said:
Man I LOVE YOU!!! I want you here for a kiss, all permanent restored.
First i delete the folder nvram, then factory reset from twrp.
I wasn't sure than all was deleted, so i flash the fastboot ROM with MiFlash, i change the IMEI with your guide and last i re-flash with MiFlash.
After reboot IMEI were OK, but for another check i pick twrp, reboot, factory reset again and flash last developer Miui EU (.29) and all work like a charm, so really really thank you ^^
Inviato dal mio Redmi Note 2 utilizzando Tapatalk
Click to expand...
Click to collapse
I'm glad that I cold help.
You can donate something if you wish,but it's up to you
s 5830i gingerbread to s5 mode
After watching your video I updated my galaxy ace 5830i from gingerbread to s5 mode. But I can't make call or receive call or SMS. It shows that invalid imi like that. Please help me I am in trouble . [email protected] is my email adress please reply me with solution. Please I don't want to lose my phone please tell me what should I do now
We can't help you here. Find the forum for your device.
Is it possible to set a custom IMEI this way?
ILGreat said:
Man I LOVE YOU!!! I want you here for a kiss, all permanent restored.
First i delete the folder nvram, then factory reset from twrp.
I wasn't sure than all was deleted, so i flash the fastboot ROM with MiFlash, i change the IMEI with your guide and last i re-flash with MiFlash.
After reboot IMEI were OK, but for another check i pick twrp, reboot, factory reset again and flash last developer Miui EU (.29) and all work like a charm, so really really thank you ^^
Inviato dal mio Redmi Note 2 utilizzando Tapatalk
Click to expand...
Click to collapse
Hi,
I have the same problem with the IMEI.
I tried to use the fastboot, but couldn't find a proper guide how to do it (can't connect the PC to the phone when it is in fastboot mode). can you help me here? is there a step-by-step guide for newbies? can I use the phone ROM update utility instead of the MiFlash? (what is the difference between the two?)?
in addition, I did not fully understand the steps you've done to recover the IMEI. when you write "First i delete the folder nvram, then factory reset from twrp", how did you deleted the folder (using a file explorer like ES file explorer?), what is twrp?
Thanks in advance.
OKup.
he bro iam new this but i really need your help
I need your help bro to sett your programs on my pc is there a way I can contact you privately please?
okup said:
Hi,
I have the same problem with the IMEI.
I tried to use the fastboot, but couldn't find a proper guide how to do it (can't connect the PC to the phone when it is in fastboot mode). can you help me here? is there a step-by-step guide for newbies? can I use the phone ROM update utility instead of the MiFlash? (what is the difference between the two?)?
in addition, I did not fully understand the steps you've done to recover the IMEI. when you write "First i delete the folder nvram, then factory reset from twrp", how did you deleted the folder (using a file explorer like ES file explorer?), what is twrp?
Thanks in advance.
OKup.
Click to expand...
Click to collapse
It should be use TWRP to Root your RN2 then delete NVRAM folder using ES File Explorer.
Dear sir, my Xiaomi redmi note 2 won't start wifi or bluetoot since the OTA update, I have try down grade it, put chinese ROM and back again to global ROM, flash it, etc but none of it working, I have read your post about reinstall driver for wifi and bluetooth on NVRAM, but your step not work on my computer, can u help me please?
Here is report from spinstall.exe
C:\Users\Double Click\Desktop\All MTK USB Driverv.9.2.PDanet.Adb 2015\SmartPhoneDriver\Driver_Auto_Installer_SP_MTK\Driver_Auto_Installer\SmartPhoneDriver\x86\Infs\usbvcom.inf--->
there are no matching devices in the device tree
C:\Users\Double Click\Desktop\All MTK USB Driverv.9.2.PDanet.Adb 2015\SmartPhoneDriver\Driver_Auto_Installer_SP_MTK\Driver_Auto_Installer\SmartPhoneDriver\x86\Infs\usbvcom_brom.inf--->
there are no matching devices in the device tree
=====Operation Succeeded=====
File Closed.
and here the error warning from SP meta tool
Search Kernel USB COM port time out!
please help me
Related
I called one day the Touchscreen USSD #removed for n00bs and I don't know that this destroy you touchscreen #
but i pressed the UPDATE button DONT TRY and.... touchscreen doesnt work ... after... Update completed!!! Touchscreen works!!!
Is this UPDATE button harmful as update Camera firmware, or is will update a bit of touchscreen files for Android?
It works for me but Don't Try it!! I does't will have a touchscreen series brick on XDA-developers
If this Update butten too harmfull, please remove this therad
Please help...
i'm the victim
I think doing that is harmful!! coz it had killed my touchscreen after update fail!!
still lookin for soln!
but by the way! thanx for ur warning!
SOLUTION!!!!!!!
Rutayuga91 said:
I think doing that is harmful!! coz it had killed my touchscreen after update fail!!
still lookin for soln!
but by the way! thanx for ur warning!
Click to expand...
Click to collapse
-Solution-
Before we start, make sure you have Java, if not download from here: http://java.com/en/download
I did the touch screen firmware update on my old S5570, i deliberately took battery out during update as i couldnt care less about the phone and wanted a challenge; and sure enough it was dead... But wait... I managed to successfully fix it.... how?
Well
1. Put a custom recovery on your phone (Preferably CWM) - On my samsung you put it into download mode and flash through odin
2. Download ANY custom ROM for your device (.zip format)
3. Open the downloaded zip on your computer, navigate using WinRAR to /system and find the file build.prop, open that file with WordPad, not Notepad but WORDPAD. Find where it says "persist", and there will be a few that start with that, go to the last line and insert:
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
This enables USB Debugging by default, I'll explain why you need this later,
Ok save the build.prop and stick it back in the ZIP archive, now download this: https://www.mediafire.com/?omdol91672ieenr
Extract contents to Java directory C:/Program Files (x86)/Java/<Java>/bin (or C:/Program Files/Java/<Java>/bin for 32-bit)
Run cmd and type cd C:/Program Files (x86)/Java/<Java>/bin
(eg "cd C:\Program Files (x86)\Java\jre7\bin")
Place your modified .zip in the /bin folder and name as "rom.zip"
Run sign_file.bat
There should be a rom_signed.zip file in the /bin directory
Now put your phone in recovery and Mount USB storage, drag your "rom-signed.zip" in the root directory, I imagine you'd know how to flash it, but remember to wipe data and cache before hand
Now here's the fun bit
Reboot phone after ROM is installed, 1st boot may take a while
Plug USB in to your computer and download ADB: http://androidarea51.com/downloads/adb.zip
Extract to C drive, now open CMD and type cd.. and cd.. again, then type adb devices, hopefully your phone's serial should appear, if not you have either not got drivers installed or you have done something wrong
So you see your serial number beside adb devices? Great
Now download this: http://androidscreencast.googlecode.com/svn/trunk/AndroidScreencast/dist/androidscreencast.jnlp
^^ This requires USB Debugging ^^
And run it, press a button on your phone and it should appear on your pc screen, using your mouse run through the setup proccess, once done open dialer and press "*#2663#" and press Update, then after reboot your phone and...
Touchscreen fixed successfully xD
This worked for me anyway, sorry if some of the instructions are hard to follow, it's my first tutorial so sorry, but please reply if you need any help
Hi, I was trying to follow your tutorial but when I try to install the rom "signed" CWM says that there's an error, I already tried with different recoveries and in some cases it says that the MD5 doesn't exist or the file is not signed or that the rom-signed.zip file can't be opened. I'm using CWM 6.0.4.5 and twrp 2.7.1.0. but I can't install the rom.
Try to recopy
lalo69 said:
Hi, I was trying to follow your tutorial but when I try to install the rom "signed" CWM says that there's an error, I already tried with different recoveries and in some cases it says that the MD5 doesn't exist or the file is not signed or that the rom-signed.zip file can't be opened. I'm using CWM 6.0.4.5 and twrp 2.7.1.0. but I can't install the rom.
Click to expand...
Click to collapse
Hi. Have you tried to recopy the ROM zip file to your sdcard? This usually happens to me also. Maybe the zip was corrupted while copying it from the PC to your sd card. Try to recopy the ROM.
failed to update.
pcwiztech said:
-Solution-
Before we start, make sure you have Java, if not download from here: http://java.com/en/download
I did the touch screen firmware update on my old S5570, i deliberately took battery out during update as i couldnt care less about the phone and wanted a challenge; and sure enough it was dead... But wait... I managed to successfully fix it.... how?
Well
1. Put a custom recovery on your phone (Preferably CWM) - On my samsung you put it into download mode and flash through odin
2. Download ANY custom ROM for your device (.zip format)
3. Open the downloaded zip on your computer, navigate using WinRAR to /system and find the file build.prop, open that file with WordPad, not Notepad but WORDPAD. Find where it says "persist", and there will be a few that start with that, go to the last line and insert:
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
This enables USB Debugging by default, I'll explain why you need this later,
Ok save the build.prop and stick it back in the ZIP archive, now download this: https://www.mediafire.com/?omdol91672ieenr
Extract contents to Java directory C:/Program Files (x86)/Java/<Java>/bin (or C:/Program Files/Java/<Java>/bin for 32-bit)
Run cmd and type cd C:/Program Files (x86)/Java/<Java>/bin
(eg "cd C:\Program Files (x86)\Java\jre7\bin")
Place your modified .zip in the /bin folder and name as "rom.zip"
Run sign_file.bat
There should be a rom_signed.zip file in the /bin directory
Now put your phone in recovery and Mount USB storage, drag your "rom-signed.zip" in the root directory, I imagine you'd know how to flash it, but remember to wipe data and cache before hand
Now here's the fun bit
Reboot phone after ROM is installed, 1st boot may take a while
Plug USB in to your computer and download ADB: http://androidarea51.com/downloads/adb.zip
Extract to C drive, now open CMD and type cd.. and cd.. again, then type adb devices, hopefully your phone's serial should appear, if not you have either not got drivers installed or you have done something wrong
So you see your serial number beside adb devices? Great
Now download this: http://androidscreencast.googlecode.com/svn/trunk/AndroidScreencast/dist/androidscreencast.jnlp
^^ This requires USB Debugging ^^
And run it, press a button on your phone and it should appear on your pc screen, using your mouse run through the setup proccess, once done open dialer and press "*#2663#" and press Update, then after reboot your phone and...
Touchscreen fixed successfully xD
This worked for me anyway, sorry if some of the instructions are hard to follow, it's my first tutorial so sorry, but please reply if you need any help
Click to expand...
Click to collapse
sir it always fails to update. any solution? im using galaxy pocket.
sumtingswong said:
sir it always fails to update. any solution? im using galaxy pocket.
Click to expand...
Click to collapse
What fails to update?
The ROM installation or Touchscreen?
Finally
Finally someone noticed me.
I've been struggling with this problem for quite sometime now sir. i've followed the procedure sir yet when i press "*#2663#" and press Update, it always fails no matter how many times i do it, please help me sir.
---------- Post added at 08:33 AM ---------- Previous post was at 08:22 AM ----------
pcwiztech said:
What fails to update?
The ROM installation or Touchscreen?
Click to expand...
Click to collapse
Finally someone noticed me.
I've been struggling with this problem for quite sometime now sir. i've followed the procedure sir yet when i press "*#2663#" and press Update, it always fails no matter how many times i do it, please help me sir.
sumtingswong said:
Finally someone noticed me.
I've been struggling with this problem for quite sometime now sir. i've followed the procedure sir yet when i press "*#2663#" and press Update, it always fails no matter how many times i do it, please help me sir.
Click to expand...
Click to collapse
Why do you want to do this - there is no benefit and a strong possibility your touchscreen will no longer work if it goes wrong
marcussmith2626 said:
Why do you want to do this - there is no benefit and a strong possibility your touchscreen will no longer work if it goes wrong
Click to expand...
Click to collapse
No sir. That's the problem, i accidentally accessed the menu in *#2663# and pressed the update button not knowing that i would make my touchscreen unusable. I'm just trying to restore everything back to normal sir, for i cannot afford to buy another phone sir.
Sorry for my bad english, i'm not a native speaker.
sumtingswong said:
No sir. That's the problem, i accidentally accessed the menu in *#2663# and pressed the update button not knowing that i would make my touchscreen unusable. I'm just trying to restore everything back to normal sir, for i cannot afford to buy another phone sir.
Sorry for my bad english, i'm not a native speaker.
Click to expand...
Click to collapse
you can try
http://forum.xda-developers.com/showthread.php?t=1505412
the guide is for the galaxy mini but you should be able to adapt it
sumtingswong said:
No sir. That's the problem, i accidentally accessed the menu in *#2663# and pressed the update button not knowing that i would make my touchscreen unusable. I'm just trying to restore everything back to normal sir, for i cannot afford to buy another phone sir.
Sorry for my bad english, i'm not a native speaker.
Click to expand...
Click to collapse
Try this ROM, this should contain the touchscreen binary in the kernel fixing the update fail message: http://www.mediafire.com/download/l570r7dm7545m34/explode+rom+build+5.zip
pcwiztech said:
Try this ROM, this should contain the touchscreen binary in the kernel fixing the update fail message: http://www.mediafire.com/download/l570r7dm7545m34/explode+rom+build+5.zip
Click to expand...
Click to collapse
still no luck sir, still says update fail.
sumtingswong said:
still no luck sir, still says update fail.
Click to expand...
Click to collapse
Please make sure when you dial *#2663# you press Binary Update and NOT Internal Storage
pcwiztech said:
Please make sure when you dial *#2663# you press Binary Update and NOT Internal Storage
Click to expand...
Click to collapse
it only have one option sir, just update.
{
"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"
}
please help me sir.
pcwiztech said:
Please make sure when you dial *#2663# you press Binary Update and NOT Internal Storage
Click to expand...
Click to collapse
sumtingswong said:
it only have one option sir, just update.
please help me sir.
Click to expand...
Click to collapse
Ah yes. It seems as the kernel is also "00" - try a different ROM or even a rooted stock rom that has a different kernel. My S5570 had the same issue, tried a different rom and voila
pcwiztech said:
Ah yes. It seems as the kernel is also "00" - try a different ROM or even a rooted stock rom that has a different kernel. My S5570 had the same issue, tried a different rom and voila
Click to expand...
Click to collapse
Okay sir, i'll just try all the custom roms.
pcwiztech said:
Ah yes. It seems as the kernel is also "00" - try a different ROM or even a rooted stock rom that has a different kernel. My S5570 had the same issue, tried a different rom and voila
Click to expand...
Click to collapse
after 10 attempts still no luck sir. please advice.
sumtingswong said:
after 10 attempts still no luck sir. please advice.
Click to expand...
Click to collapse
Hi, sorry for delayed reply, It's morning here.
Unfortunately i think the only option will be to replace your phones digitizer, this will cost around £15-£25 from eBay
Unless you can find a boot.img (kernel) that has the touchscreen firmware then that's your only choice.
pcwiztech said:
Hi, sorry for delayed reply, It's morning here.
Unfortunately i think the only option will be to replace your phones digitizer, this will cost around £15-£25 from eBay
Unless you can find a boot.img (kernel) that has the touchscreen firmware then that's your only choice.
Click to expand...
Click to collapse
thanks for your help sir, i really appreciated it. £15 is the price of a 2nd hand galaxy pocket here sir, so i guess i should really saved for it. i guess i should give up now, it's been quite sometime since ive been stressing myself because of this. godbless you sir.
READ THIS FIRST:After downloading "oxygenos_1.0.0.zip" you will notice that it contains a folder with two files:
oxygenos_1.0.0_flashable.md5
oxygenos_1.0.0_flashable.zip
Extract oxygenos_1.0.0_flashable.zip first, then copy it to the SD card, wipe, flash, etc.
MultiROM works!
Check here and click thanks for MMWolverine.
New touchscreen driver to fix ghost touches:
Click here.
__________________________________________
Just a weeeee bit late.
https://oneplus.net/de/oxygenos
__________________________________________
Download it here:
Official:
https://forums.oneplus.net/threads/oxygen-1-0-2-release-with-stagefright-security-patches.340711/
There is a pre-rooted and de-bloated version by @CraZY_BoY^ right here:
[ROM][MOD] OxygenOS - Rooted | Cleaned | Some apps from CM
Features
Screen-off gestures like double-tap to wake, music controls, and shortcuts for the camera and flashlight
Hardware and software navigation keys
Quick settings feature, tiles can be added, removed, and re-organized
Their own file manager, though it's pretty buggy ATM (see below).
Missing features:
Privacy guard
Double tap to sleep
Display color settings
Theming support
Custom camera app (uses Google camera app)
MaxxAudio and Swiftkey (coming in a future update)
{
"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"
}
Installation steps:
Please make sure all your data and files are backed up before commencing. Flashing OxygenOS onto CM does require a system wipe, so you will lose all of your data. We are actively working on an easier, more automated solution soon to be available, but for now the build must be flashed manually.
Please proceed only if you are confident in your abilities to flash a custom ROM. This guide exists to help you flash OxygenOS, but things can still go wrong if not followed correctly. While rooting and flashing will not void your OnePlus warranty, any damage caused by improper flashing is not covered under warranty.
The following instructions assume you have Fastboot and ADB installed.
Step 1
You first need to flash a recovery onto your device. We recommend using TWRP. Please download the recovery image to your computer. You can follow their instructions to flash recovery, or you can reference these steps:
Boot into fastboot mode. You can do this on your OnePlus One by holding down the power button and the volume up button. When you see the fastboot logo, connect your device to your computer.
In your terminal window, find the folder where you put the recovery image and run the following commands:
fastboot oem unlock (You can skip this step if your phone’s bootloader is already unlocked).
fastboot flash recovery <recovery.img>. Image file should be the TWRP recovery image.
fastboot reboot
You should now have the recovery installed.
Step 2
Copy oxygenos_1.0.0.flashable.zip to your phone. On a Mac, you can use Android File Transfer.
Step 3
Boot into recovery. You can do this on your OnePlus One by holding down both the volume down key and the power button.
Step 4
Once you are in the recovery interface, the first thing you want to do is a factory reset. Again, you will lose all your data so please make sure you have backed up everything before doing this.
Step 5
After the wipe, go to install and find oxygenos_1.0.0.flashable.zip. Confirm flash. This will flash OxygenOS onto your device.
Step 6
After the flash succeeds, you can reboot the device, which will take you to the new OxygenOS. Enjoy!
If you find yourself wanting to rollback to CM, Make sure you have TWRP or CM recovery on the device. Another factory reset will be needed before flashing unfortunately so make sure you backup all of you data.
Click to expand...
Click to collapse
Source
To revert back to CM11/CM11s:
Flash the latest CM11/CM11s modem from here.
Restore CM11/CM11s from a backup or flash new.
There is no need to reboot between steps 1 & 2.
Rooting Instructions:
Just like CM11s, download SuperSU-v2.xx.zip to your SD card and flash from recovery.
Known issues:
Reported by OnePlus:
When printing images, printer service may stop
Cannot hang up a call using headphone controls (intermittent)
OTG can only recognize FAT32 file system
During system update, display of wifi/data notification may be incorrect
During system update, display of version number may be incorrect
Files sometimes crash when uploading files to the cloud
Files may crash when renaming image files
Files does not support multi-select deletes
Reported here & elsewhere:
4k video is non-functional with Google camera.
Google Play Services wakelocks. Check here for a fix.
Other Stuff
Wallpapers
Boot animation
Modem
Please click thanks for the guys that posted these for you.
CafeKampuchia said:
Just a weeeee bit late.
https://oneplus.net/de/oxygenos
Click to expand...
Click to collapse
Downloadning now! Lets see
very slow..hope for a mirror soon!
CoreGaming said:
very slow..hope for a mirror soon!
Click to expand...
Click to collapse
Its 700 MB
Nice to know, but I'll wait CM12s and then I choose what to do
I'm getting an average 100-150kbs using Firefox and DownloadThemAll. 1 hr 22 minutes left :/
Edit
Mine's shot up to >300kbs - 20 minutes left
Nothing like flashing a new ROM at 1:30AM!
Downloading now - Cant wait to get this thing running!
I am downloading on both my pc and my opo. on my the opo, it's taking 1 hour or so to download. on my pc it took 10 minutes. both on wireless on the same network.
Uploading to mega now, nearly half way, will post a link when finished.
gsmyth said:
Uploading to mega now, nearly half way, will post a link when finished.
Click to expand...
Click to collapse
Send me the link and I'll update the OP ASAP.
3rd feature according to this video is FILE MANAGER ARE YOU KIDDING ME
MEANWHILE STOCK BUG LIST:
When printing images, printer service may stop
Cannot hang up a call using headphone controls (intermittent)
OTG can only recognize FAT32 file system
During system update, display of wifi/data notification may be incorrect
During system update, display of version number may be incorrect
Files sometimes crash when uploading files to the cloud
Files may crash when renaming image files
Files does not support multi-select deletes
HOPING TO ROOT IT AGAIN VIA RECOVERY AND provide my feedback with xposed, viper sound mod etc
I'm really happy with cm12 nightlies, I'll wait for the reviews whats the battery like?
aravindhramachandran said:
3rd feature according to this video is FILE MANAGER ARE YOU KIDDING ME
MEANWHILE STOCK BUG LIST:
When printing images, printer service may stop
Cannot hang up a call using headphone controls (intermittent)
OTG can only recognize FAT32 file system
During system update, display of wifi/data notification may be incorrect
During system update, display of version number may be incorrect
Files sometimes crash when uploading files to the cloud
Files may crash when renaming image files
Files does not support multi-select deletes
HOPING TO ROOT IT AGAIN VIA RECOVERY AND provide my feedback with xposed, viper sound mod etc
Click to expand...
Click to collapse
Bug list in OP already, friend. Good point on the file manager. I'll add that to the OP as well. :good:
vacenzo said:
I'm really happy with cm12 nightlies, I'll wait for the reviews whats the battery like?
Click to expand...
Click to collapse
Dude, nobody even has it installed yet. And even if they do, it's been <1 hr. We'll know something tomorrow. :highfive:
mirror please. cant flash beacuse my download was corrupted and now the download is super slow. :crying::crying:
saar120 said:
mirror please. cant flash beacuse my download was corrupted and now the download is super slow. :crying::crying:
Click to expand...
Click to collapse
Read the comments.
Transmitted via Bacon
Guys, it keeps giving me error when trying to flash. Im on cm nightlies the latest one but for some reason it wont flash... i can flash other roms just fine
this is what happend to me as well. in the middle of the download i switched from wifi to 3g . i thought it was beacuse of that.
zee24 said:
Guys, it keeps giving me error when trying to flash. Im on cm nightlies the latest one but for some reason it wont flash... i can flash other roms just fine
Click to expand...
Click to collapse
Did you extract the zip? There is a flashable zip in the zip you downloaded.
There is a zip inside downloaded zip! Flash that.
Update Mar-12/2016: as long as on the market appeared a long line of new types of mtk6260 mtk6261 mtk2502C mtk2502A (etc) watches equipped with strange new PCB or flash_ID parameters, the new release <Readback Extractor mtk 2.0> now has the capacity to identify, to read, check, rebuild firmware and collect and insert in the .cfg files the flash_ID's coded inside the ROM dump for almost all types of mtk watchphones or smartwatches based on RTOS Nucleus
NOTE: being tested already for mtk6260 mtk6261 mtk2502C and mtk2502A
In short - if you intend to install in your smartwatch new firmwares, mods etc, before to initiate any flashing with the Flash Tool app (pushing that goddamn < Download > button) think twice, 'bove all better DO a backup for the original firmware, why so? because it's containing all original drivers hence you'll be able to recover 100% your watch in case of bricking.
How to:
First you have need of a full dump of your ROM. Assuming that you already got a Flash Tool 5.15.16 and drivers, and you were at the point of flashing something (already chose the download agent and scatter file)
preparations:
a. Set options/backup and restore on no action
b. load the download agent (you find this file inside the flash tool folder)
c. load a scatter firmware - for initialization flash tool needs a scatter file (.cfg) - for dz09 you get this one - for any other than mtk6260A get here and get a firmware compatible with your PCB
d. in case you have W10 - go to the start menu and click on power and hold down the shift key while clicking on restart. A screen then comes up and you need to choose troubleshooting and then startup options. It will then reboot and give you a menu. press 7 which is ignore signed drivers and then when windows comes up, you will be able to install the drivers.
for instance let's say you have a DZ09 smartwatch:
1 - press < Readback > in upper menu and so < Add > in the middle menu
2 - click twice on the item appears in the main window, set name as ROM_DZ choose in browser the path and save
3 - set as Physical start address 0x00000000 and as Length 0x01000000 or 0x00800000 or 00400000 (try them in this order) then ok
4 - turn off the watch, press < Readback > in the middle menu wait 2 seconds and connect through USB your watch
5 - wait until the upload is complete (big green ring)
Now second stage:
1 - download the app I've built attached here (Readback Extractor mtk) and unzip it
2 - create a folder where you intend to keep in safe the original firmware and name it for instance DZ09-Orig
3 - do a copy of Readback Extractor mtk 2.0.exe and place it inside the DZ09-Orig folder then click twice on it
4 - press <Load Readback file> and browse after the ROM_DZ file created before with the Flash Tool then open
5 - Wait about a minute while the app will check bit by bit the integrity of your file
6 - If everything went ok and your file is healthy then app will show " health 100% " so you can proceed to the next step
7 - Press <Rebuild Firmware> and wait about one minute (it shows a progress counter)
8 - When appears the message " - ALL DONE!!!" close app and go back in the DZ09-Orig folder, now you'll find there a set of new files which are the original firmware kit ready to be flashed back in your phone anytime you want
9 - Enjoy flashing anything you like without any fear that something bad can happen
Some tricks for writing IMEI in your watch NVRAM:
you connect to usb your watch (turned on this time) and set the com port on the watch screen, go in device manager and check the port number your watch is connected, then you open Tera Term hyperterminal (google for this app), connect it as serial com on watch com port and then give the command:
AT + EGMR = 1, 7, " imei number "
if on screen appears OK then ready, you've changed your imei
AFTERWARDS READ ME story - Anywhere you search, there is no one to tell you explicitly how to extract from your mtk smartwatch the firmware kit
All says a halfmouth: Do a full < Readback > in Flash Tool, you'll do it being confident that from now on you say goodbye to any risk because you have A BACKUP hence you start flashing new firmwares. And the Big Brick is coming , you smile and get back to your < Readback > backup discovering that, sadly, you have a binary bulk at first sight good for nothing. It cannot be so useless, isn't it? after all it contains full dump of your ROM! I was in exactly the same situation, so 'cause I didn't find any answer I've started reverse engineering . . . and it worked, first I did it manually for guys being in the same situation, 've noticed that is a common issue so I had to choose how to help, simpler but dangerous (for you) way, to create a tutorial <how to> or the hard way (hard for me), to develop an app which will do all "cooking" automatically and I choose the second because in manually way there is a quite big "chance" to mess up with your primary bootloader which could get to a real tragedy - no modem - brickest brick you saw in your entire life
Readback extractor mtk 2.1 beta
Flash Tool and drivers
Lil to late for me XD.... *just ordered a new one btw*
franc33s said:
Lil to late for me XD.... *just ordered a new one btw*
Click to expand...
Click to collapse
Sorry man, couldn't earlier because I have mine either of two weeks or so. . . still a beginner
Look at the bright side, best lessons we learn from our own mistakes, best part is that if you buy the new one from the same seller, you'll have the firmware hence two working watches!
Are there apps in the works to change watch faces without flashing?
kyitech said:
Are there apps in the works to change watch faces without flashing?
Click to expand...
Click to collapse
Unfortunately, yet, there is no way to get in contact with the watch else than through proprietary mediatek drivers so that the only ways to communicate for now are Flash Tool app and bluetooth modem proprietary commands (the most important of them being secret as well)
To do such a reverse engineering is way way way over my pay grade
Still I'm working for an app which could replace any media in the watch (backgrounds, icons) but through flashing method of course
Thanks for the info...I just think this watch have great potential
Golem_ said:
Unfortunately, yet, there is no way to get in contact with the watch else than through proprietary mediatek drivers so that the only ways to communicate for now are Flash Tool app and bluetooth modem proprietary commands (the most important of them being secret as well)
To do such a reverse engineering is way way way over my pay grade
Still I'm working for an app which could replace any media in the watch (backgrounds, icons) but through flashing method of course
Click to expand...
Click to collapse
Sorry for not knowing, but what about bluetooth app transfer in the Google play store. How can they be used on dz09-?
kyitech said:
Sorry for not knowing, but what about bluetooth app transfer in the Google play store. How can they be used on dz09-?
Click to expand...
Click to collapse
. . . bluetooth modem AT commands, just I told this before, generally speaking, in this way all bluetooth app are working, in our case they are proprietary and most of them SECRET. For more information please check this link, it is an older tutorial posted by me on that site
franc33s said:
Lil to late for me XD.... *just ordered a new one btw*
Click to expand...
Click to collapse
I'm almost sure you found these before me, still, here link you have more than 10 versions of dz09 firmwares (others than we checked before)
It looks like they made a firmware for each phone ) very prolific guys when about dz09
Hope this time you catch the right one!
Golem_ said:
I'm almost sure you found these before me, still, here link you have more than 10 versions of dz09 firmwares (others than we checked before)
It looks like they made a firmware for each phone ) very prolific guys when about dz09
Hope this time you catch the right one!
Click to expand...
Click to collapse
yup already did try them all, they boot fine, just no luck getting the Padgene (padgeME) one yet (so my touchscreen driver would work), the guy is still uploading more firmwares tough *fingers crossed*
Golem_ is a hero!
Thanks for all the time you spend with the gt08
flashtool
Hy ,
I am trying to search for the wright flashtool to make my backup.
And where can i find a tutorial?
I have a gv08s.
Wich drivers do i need, and wich version of flashtool?
Thanks in advance
xeph20 said:
Golem_ is a hero!
Thanks for all the time you spend with the gt08
Click to expand...
Click to collapse
thank you for kind words!
Golem_ said:
thank you for kind words!
Click to expand...
Click to collapse
{
"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"
}
carlospaco said:
Hy ,
I am trying to search for the wright flashtool to make my backup.
And where can i find a tutorial?
I have a gv08s.
Wich drivers do i need, and wich version of flashtool?
Thanks in advance
Click to expand...
Click to collapse
here link you find a good tutorial but instead <download> you have to use <readback>
Golem_ said:
here link you find a good tutorial but instead <download> you have to use <readback>
Click to expand...
Click to collapse
Yes , i have done everything like its said, for couple off days, but i keep getting this error always.
lashtool error: S_BROM_DOWNLOAD_EPP_FAIL (2036)
[EPP] FlashTool environment preparation failed
It May be caused from DRAM initialization failed
Pleace check the EMI information of the MAUI load is correct and fit the target.
Hope that someone can help me with this, i am desperated.
Thanks
carlospaco said:
Yes , i have done everything like its said, for couple off days, but i keep getting this error always.
lashtool error: S_BROM_DOWNLOAD_EPP_FAIL (2036)
[EPP] FlashTool environment preparation failed
It May be caused from DRAM initialization failed
Pleace check the EMI information of the MAUI load is correct and fit the target.
Hope that someone can help me with this, i am desperated.
Thanks
Click to expand...
Click to collapse
give me in PM a skype ID
Golem_ said:
give me in PM a skype ID
Click to expand...
Click to collapse
Oh, i am sorry, but i don't have a skype id.
carlospaco said:
Oh, i am sorry, but i don't have a skype id.
Click to expand...
Click to collapse
Alternatives for live screen sharing like, for instance TeamViewer?
Golem_ said:
Alternatives for live screen sharing like, for instance TeamViewer?
Click to expand...
Click to collapse
i have send you id teamviewer
Please help
Can anyone give me qcn file for ze550kl Z00L
My imei is lost
It's just a small file
Pleaze help pleaze
https://drive.google.com/file/d/0B_D6S6CoxAwEaW9tUVNuSEJycTg/view?usp=drivesdk
Link to QCN file.
Search for 1111111111111111 - SIM 1 IMEI & 1111111111111112 - SIM 2 IMEI
and replace with yours in correct format.
Just for info my device is ZOOL 3GB/16GB Snapdragon 615 variant.
Sent from my ASUS_Z00LD using Tapatalk
aadi50 said:
https://drive.google.com/file/d/0B_D6S6CoxAwEaW9tUVNuSEJycTg/view?usp=drivesdk
Link to QCN file.
Search for 1111111111111111 - SIM 1 IMEI & 1111111111111112 - SIM 2 IMEI
and replace with yours in correct format.
Just for info my device is ZOOL 3GB/16GB Snapdragon 615 variant.
Click to expand...
Click to collapse
thanks a lot bro
For file
But unfortunately it doesn't worked for me
aadi50 said:
https://drive.google.com/file/d/0B_D6S6CoxAwEaW9tUVNuSEJycTg/view?usp=drivesdk
Link to QCN file.
Search for 1111111111111111 - SIM 1 IMEI & 1111111111111112 - SIM 2 IMEI
and replace with yours in correct format.
Just for info my device is ZOOL 3GB/16GB Snapdragon 615 variant.
Click to expand...
Click to collapse
also
When i try to find ur imei
i.e
111111111111111
In hex format
It says no string found
I am using
Ultra edit
And imei converter
addy692 said:
also
When i try to find ur imei
i.e
111111111111111
In hex format
It says no string found
I am using
Ultra edit
And imei converter
Click to expand...
Click to collapse
I rechecked and its fine. I can search it.
Are you trying to convert "1111..." before searching.
If yes then dont. Directly search for "1111..." in editor.
Its a random nmbr i put just as a placeholder only...
Just convert your imei only before replacing in file.
aadi50 said:
I rechecked and its fine. I can search it.
Are you trying to convert "1111..." before searching.
If yes then dont. Directly search for "1111..." in editor.
Its a random nmbr i put just as a placeholder only...
Just convert your imei only before replacing in file.
Click to expand...
Click to collapse
oh ok
I will try
I was converting 1111
:good:
thnku
HELP!!
Please someone have a QCN for Ze550kl(Z00L 2GB RAM) ??
I've hard bricked my phone with 9008, and 9006.. I managed to make it come back to life, but I'm with the 2 IMEI null, and I can not find on the net any QCN for the model of my cell phone, The QCN above its MSM8939 and I need MSM8916 please somebody help me. :crying::crying:
kensk8 said:
Please someone have a QCN for Ze550kl(Z00L 2GB RAM) ??
I've hard bricked my phone with 9008, and 9006.. I managed to make it come back to life, but I'm with the 2 IMEI null, and I can not find on the net any QCN for the model of my cell phone, The QCN above its MSM8939 and I need MSM8916 please somebody help me. :crying::crying:
Click to expand...
Click to collapse
bro did you manage to get the qcn file?
Leelka said:
bro did you manage to get the qcn file?
Click to expand...
Click to collapse
No, unfortunatelly. I'm with my phone until today with IMEI Null, I've tried hardly to find on net but with no success at all. :/
kensk8 said:
Please someone have a QCN for Ze550kl(Z00L 2GB RAM) ??
I've hard bricked my phone with 9008, and 9006.. I managed to make it come back to life, but I'm with the 2 IMEI null, and I can not find on the net any QCN for the model of my cell phone, The QCN above its MSM8939 and I need MSM8916 please somebody help me. :crying::crying:
Click to expand...
Click to collapse
I fixed the imei of my MSM8916 with the qcn above.
igorfs10 said:
I fixed the imei of my MSM8916 with the qcn above.
Click to expand...
Click to collapse
But which are your Zenfone? same than mine?
Z00L 2GB Ram, 4 core, 16GB emmc ?
if yes, how you do?
is possible tell me all the steps do you follow, cuz I'm with many problems with this device, I cannot install any custom roms in it.. I've tried and always get stuck on boot waiting more than 40 mins to boot up and nothing happens, I'm with the IMEI and S/N lost (IMEI "null") and S/N with a ramdom number like 29880ed3 something like this.. I've tried to install custom roms but nothing happeans, tried 6 CR and all get on stuck bootloop, I get unlocked bootloader as ask in steps, cleaned all "wipe, dalvik, data and system" clean install with lastest twrp and stucks on boot.. anyway if its possible to help me I appreciate.
Thanks for now;
kensk8 said:
No, unfortunatelly. I'm with my phone until today with IMEI Null, I've tried hardly to find on net but with no success at all. :/
Click to expand...
Click to collapse
Surprise, i can help you.
https://drive.google.com/file/d/1-9fo7TBwygrDHipjB3271qVpP_EBszjv/view?usp=sharing
Enjoy . :good:
Leelka said:
Surprise, i can help you.
https://drive.google.com/file/d/1-9fo7TBwygrDHipjB3271qVpP_EBszjv/view?usp=sharing
Enjoy . :good:
Click to expand...
Click to collapse
Man I appreciate a lot for ur help, but unfortunatelly this QCN if I put, it will brick my phone again on bootloop cuz this qcn model is for MSM8939, as well my phone is MSM8916
But I really thank you.
kensk8 said:
But which are your Zenfone? same than mine?
Z00L 2GB Ram, 4 core, 16GB emmc ?
if yes, how you do?
is possible tell me all the steps do you follow, cuz I'm with many problems with this device, I cannot install any custom roms in it.. I've tried and always get stuck on boot waiting more than 40 mins to boot up and nothing happens, I'm with the IMEI and S/N lost (IMEI "null") and S/N with a ramdom number like 29880ed3 something like this.. I've tried to install custom roms but nothing happeans, tried 6 CR and all get on stuck bootloop, I get unlocked bootloader as ask in steps, cleaned all "wipe, dalvik, data and system" clean install with lastest twrp and stucks on boot.. anyway if its possible to help me I appreciate.
Thanks for now;
Click to expand...
Click to collapse
Same model ze550kl, 2gb ram, 1.2 ghz quad core.
You need to use an hex editor and imei converter. Use your imei in imei converter and search in hex editor for bytes 1111111111 and overwrite it with your imei converted. Do the same thing with second imei, but this time you have to search for 1111112. There is a software that can change sn but i cant remember. When i have more time i ll make a better tutorial explaining how to use this qcn if needed.
kensk8 said:
Man I appreciate a lot for ur help, but unfortunatelly this QCN if I put, it will brick my phone again on bootloop cuz this qcn model is for MSM8939, as well my phone is MSM8916
But I really thank you.
Click to expand...
Click to collapse
Well you are saying cuz at the time of inserting the file in qpst to restore, it will show like this is not for this model.? Ignore it. Cuz i got it too and ignored it and restored. Voila it worked.
igorfs10 said:
Same model ze550kl, 2gb ram, 1.2 ghz quad core.
You need to use an hex editor and imei converter. Use your imei in imei converter and search in hex editor for bytes 1111111111 and overwrite it with your imei converted. Do the same thing with second imei, but this time you have to search for 2222222222. There is a software that can change sn but i cant remember. When i have more time i ll make a better tutorial explaining how to use this qcn if needed.
Click to expand...
Click to collapse
Ok then. Thanks
Leelka said:
Well you are saying cuz at the time of inserting the file in qpst to restore, it will show like this is not for this model. Ignore it. Cuz i got it too and ignored it and restored. Voila it worked.
Click to expand...
Click to collapse
Ok man I'll try it then, thank you
kensk8 said:
Ok then. Thanks
Ok man I'll try it then, thank you
Click to expand...
Click to collapse
Download 00000000.qcn from aadi50 post
Download HxD https://mh-nexus.de/en/downloads.php?product=HxD
Download IMEI Converter
1 - Open IMEI Converter
2 - Put your IMEI and click on "Convert IMEI"
3 - Copy the number after "08"
{
"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"
}
4 - Open HxD and open 00000000.qcn in HxD.
5 - Go to "Search > Find"
6 - In the "Search for" box put "1111111111111111"
7 - Change "Datatype" to "Hex-value" and change "Search direction" to "All" and press the "Ok" Button
8 - HxD will select the 1111111111111111
9 - Now click with right mouse button right before the first number 1 and select "Paste write" to paste the converted IMEI without "08"
10 - Do the same thing for IMEI 2 But Search for "1111111111111112" in HXD and use your second IMEI
11 - Now save the qcn file in HXD and flash it with qpst
Now you have the right IMEI in your cellphone.
Dont forget to do a factory reset.
I hope it works for you.
igorfs10 said:
Download 00000000.qcn from aadi50 post
Download HxD https://mh-nexus.de/en/downloads.php?product=HxD
Download IMEI Converter
1 - Open IMEI Converter
2 - Put your IMEI and click on "Convert IMEI"
3 - Copy the number after "08"
4 - Open HxD and open 00000000.qcn in HxD.
5 - Go to "Search > Find"
6 - In the "Search for" box put "1111111111111111"
7 - Change "Datatype" to "Hex-value" and change "Search direction" to "All" and press the "Ok" Button
8 - HxD will select the 1111111111111111
9 - Now click with right mouse button right before the first number 1 and select "Paste write" to paste the converted IMEI without "08"
10 - Do the same thing for IMEI 2 But Search for "1111111111111112" in HXD and use your second IMEI
11 - Now save the qcn file in HXD and flash it with qpst
Now you have the right IMEI in your cellphone.
Dont forget to do a factory reset.
I hope it works for you.
Click to expand...
Click to collapse
dude really good work u've done, thanks for tutorial and for ur time for made it, I'll try follow this steps I think that now its possible to recover my IMEI
Have u something to recover others things, I mean Serial Numbers in that case, to recover my phone SN, it was with unknow number, like 28779dc2 and lost it SN for Bluetooth and Wifi too, and now I've got a error too in TWRP "Error /factory mount" and same to try it on flash any Custom Rom, I don't know if cuz this missing SN or error on /factory, cuz I do all steps requested on Customs, Unlocked Bootloader, lastest update asus Ze550kl v.2196 stock rom, I've tried clean everything too for a clean install, tried delete 3 folders after flashed a custom rom in /system/etc/firmware "modem folders" as sugest on another post here in forum, nothing work for me :/
tried all variable customs possible like, based on all versions, 8.0, 7.0, 6,0 as dotOS, Rescurrection Remix, LineAge OS, and with old Cyanogen based 13.1, 14.1, and 15.1 Nothing work on my phone.. I'm very sad :crying:
Anyway I really appreciate ur help guys!
PS: Sorry if have some errors in my English (Brazilian).
There is a software called IMEI & SN writer
https://forum.xda-developers.com/cr...repair-corrupted-invalid-imei-signal-t2927078
You can use it to change sn, imei, bt and wifi mac address to fix this.
For the factory i had the same problem after downgrading to an older lp version. To fix it i had to flash an old asus test version using emmc raw flash tool, after i had to flash the qcn again, flash the asus stock rom and unlocked bootloader again to flash custom rom. Its an extreme dangerous process that can kill your phone. I cant remember now all the steps i had used in this, and i dont want to kill my phone to try. I can boot every custom rom but sometimes i have some issues with bt and wifi on most of oreo roms that are not based no luks lineage.
Ps: Br here too.
Hello people of XDA,
as I promised here, here's a tutorial for getting Android Oreo 8.1 up and running to your device.
NOTE: I DID NOT MAKE THIS TUTORIAL! This is a translated guide from 4PDA by nik-kst. I've also rehosted some of the files on Google Drive so you won't have to register on 4PDA(hopefully).
Code:
[B]Your warranty is now void. [/B]
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this ROM before flashing it! YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
Now that the disclaimer is dealt with, let's get on with this tutorial shall we?
First things first, we need to grab a bunch of things:
SP Flash Tool;
MediaTek VCOM Drivers;
The Stock Kernel(it will make sense to you soon!);
Scatter file for repartitioning, drop it inside the stock kernel folder(credit to fca.sjc);
ADB and Fastboot of your choice;
New recovery;
Oreo's Backup, drop it inside a MicroSD card or drop it once you have re-partitioned the device successfully;
Once you have everything setup and extracted, you're ready to go!
First, we gotta go ahead and install VCOM drivers - we won't be able to do anything to our phone without them.
If you're running Windows 8/10, make sure to disable Driver Signature Verification.
Go to Device Manager, click Action at the top and click Add legacy hardware. A new wizard window will appear.
Choose Install the hardware that I manually select from a list(Advanced);
In the next window, choose Show all devices and click Next, then click Have disk...
Then you will be prompted to direct to the driver install info, so click Browse...
Now go to the folder of drivers and select the Setup Information file that's fitting for your computer, x86 for 32-bit and x64 for 64-bit.
You should now find 5 new devices in the list, add them one by one by repeating steps 2 to 6 until you have all of them installed.
Windows might complain about unsigned drivers, just allow their installation and proceed.
If your ports list looks similar to the picture below, then you're set for the next step!
{
"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"
}
Next, we'll want to back up the NVRAM partition, because AFAIK, it keeps important unique data about your device such as WiFi, IMEI etc. data.
Note: You may want to take out your MicroSD card and SIM cards prior to this just in case. Also, might be the possible fix if readback for NVRAM fails(needs confirmation).
First, open up Flashtool.exe as admin and go to Readback tab;
Click on Add, a new item in the list will appear. You want to double-click on it, so that a Save File window would appear.
Save that file anywhere you want, name it whatever you like, for convenience I've named mine ROM_NVRAM.
Now, you'll want to find the address in the memory for NVRAM partition. To do this, open up the stock firmware(credit to fca.sjc) scatter file in a text editor(like Notepad++), and find line partition_name: nvram
In that paragraph, find two values: linear_start_addr and partition_size they should be 0x380000 and 0x500000 respectively.
Punch in those values into the Readback block start address window, so it should look something like this:
Now, click Read Back, it should gray out along with Add and Remove.
Now, turn off your device, pull out the battery for about 30 seconds, reinsert it and DO NOT TURN IT ON YET! With the Volume Down "-" button pressed, plug in your device into the USB port.
The NVRAM partition should've been read and you'll get a giant green tick sign when it's done.
Now that that's done, we can start repartitioning our device.
Make sure your SP FlashTool is running as admin, otherwise restart it as admin.
Open up the Download tab and in the line Scatter-loading File click Choose and navigate to the 8.1 scatter file, it should be named MT6580_Android_scatter_8.1.txt.
From the dropdown list, select Format All + Download.
Again, take out the battery for 30 seconds and put it back in WITHOUT turning it back on.
Now click Download, and with the Volume down "-" button held down, plug the device into your PC. There should be a bunch of colored progress bars at the bottom of the window.
Once it's done, you should get the giant tick pop-up, after which you can disconnect the device, and start it normally.
NOTE: it takes a while for the first launch, so give it some time!
Once it starts up into the first launch wizard, we can now restore the NVRAM.
In order to activate the memory writing function of SP FlashTool, re-start it with admin and press Ctrl + Alt + V, the window header should have (Advanced mode) now.
From the Window drop-down, select Write Memory, it should redirect you to a new tab named accordingly.
In the File Path field, browse to the ROM_NVRAM backup that you made earlier.
In the Begin Address (HEX) field, copy the linear_start_addr value off the scatter file.
The region should be left at EMMC_USER.
Now, click the Write memory button, turn off the device, re-insert the battery just like before, and connect the device with the Volume Down "-" button pressed.
It should begin the writing of the NVRAM and once it's done a giant tick pop-up will appear.
Now after that is done, boot into the OS, check that everything works, including IMEI and WiFi.
Also, during the setup wizard or later in the settings setup a screen lock with a pattern or a PIN or a password(credit to fca.sjc), because the partitions may remain encrypted and show 0mb(needs confirmation)
Now you'll want to unlock the bootloader and flash the TWRP recovery.
Now this is a standard recovery flash, but for a quick summary:
Enable Developer options;
Enable OEM unlocking;
Reboot into bootloader mode(I like to use ADB for adb reboot-bootloader);
Make sure your device is detected via fastboot devices, if not, google some drivers for ADB;
Unlock the bootloader via fastboot oem unlock, and press the Volume up button to confirm the bootloader unlocking.
Now, reboot the phone, it will take a while to reboot, DO NOT PANIC AND WAIT.
Now that we have bootloader unlocked, we can flash the TWRP:
Go into bootloader mode;
Confirm you are being detected again by fastboot devices;
Flash the recovery with fastboot flash recovery [twrp recovery name].img;
now, WITHOUT booting into system we boot into recovery and confirm it works.
Now that you've done all this, you propably want to run Oreo now, eh? Well, here's what we do now:
Note: make sure you have the Oreo's backup zip extracted at it's own folder inside your MicroSD card or inside the phone's internal storage by now(thanks @ZappaDong for letting me know)
From recovery, select Wipe > Advanced Wipe and select system and vendor, and wipe them. Logs may complain about not seeing vendor, ignore that message.
Then, we restore everything from the Oreo backup;
Finally, do a factory reset(aka wipe Data, Dalvik and cache);
And reboot!
Now, fingers crossed, you should be booting into a fully functional 8.1 Oreo! if you did, congratulations!
Please let me know if I've made any mistakes and/or this has worked for you.
All credits go to the awesome people at 4PDA, especially nik-kst(if you're reading this, you the real MVP!), below I've linked the sources I've written this guide from.
Nik-kst's guide to repartitioning the device for Oreo;
Nik-kst's post about the Stable Oreo ROM.
Reserved for possible FAQ in the future
@aurismat, Hey man it worked as expected ! However, I was a bit confused on the repartitioning part when selecting ''Format all+download'' option then clicking ''start'' will only give an error stating that the IMG file of ''vendor'' is missing. (I am using SP FLASH v5.1744)
But nevertheless, I tried the ''Download only'' option and lucky it worked as well. I just wanted to clarify should it be Format all +download or Download only? Or is there a missing corresponding IMG file for vendor ?
Hey @JustAnormalGuy,
It should've been Format All + Download.
Also I'm glad that my post has helped at least one person.
Thanks for pointing out this omitted detail though, I'll edit the post ASAP.
Thanks for the translation!
--- solved ---
I have tried it three times but never managed to back up the NVRAM partition.
Error: s_dl-get_fram_setting_fail (5054) see attached screenshot
-----------
I have used Win 10 on my Mac and it worked.
Now I am stuck at step "5. Unlock the bootloader via fastboot oem unlock, and press the Volume up button to confirm the bootloader unlocking."
this looks O.K. to me
----------------------------------
>fastboot oem unlock
...
(bootloader) Start unlock flow
OKAY [ 16.047s]
finished. total time: 16.047s
-----------------------------------
But now nothing happens after
-----------------------------------
> fastboot reboot
rebooting...
finished. total time: 0.000s
-----------------------------------
It's stuck in
[Fastboot Mode] <<==
=> FASTBOOT Moe ...
and nothing happens.
UPDATE
O.K. I have used the Power Button to switch it off and on again, there was a small Android for a few seconds and the phone rebooted the second time. Now I am waiting for it to finish booting.
UPDATE 2
TWRP is working now
And what TWRP.img should I use for
"3. Flash the recovery with fastboot flash recovery [twrp recovery name].img;"
in the next paragraph? Is this the "New recovery;" from the download section at the top?
Thank you!
Missing tips:
- Put both scatter files inside the stock kernel folder before starting.
-I used the stock scatter file for the NVRAM backup then the 8.1 scatter only for the Formal all+Download step.
- When you first run the stock ROM, set up a pin or a password, otherwise you will have failed to mount data in twrp and data will show as 0mb due to its encryption.
@aurismat does that WW file includes the new vendor release?
In the vendor, a bug was detected, the camera with the auto flash turned on, did not turn on (rather, it turned on and off immediately), the flash when shooting video.
Now everything works as it should: yes2:
Fixed vendor: 07/07/2018
https://yadi.sk/d/DUGRYLnc3YtADV
I did everything according with this tutorial. Sadly my mobile network is not connecting idk why. I get an error saying Simprocessor and it doesnt connect on mobile network. It detects the networks but wont connect. Im going back to stock until someone can help me fix it.
@ZappaDong:
Yes, you should use the one I provided the link at the list of downloads.
Also, a bit late and I may be wrong, but your DRAM reads may be hindered by a MicroSD card(confirmation needed). Try ejecting it before you read off the NVRAM.
@fca.sjc:
First of all, thanks for pointing out my missing tips.
I'm not really sure if it includes the fixed vendor. I didn't really have any issues with the camera's flash, so they already included it(?)(again, needs confirmation).
For failed connections, make sure you flashed the NVRAM correctly(hence why you should test the telephony after you've repartitioned to stock 5.0 with the NVRAM backup flashed).If you failed to do that, I was told you should be able to recover the NVRAM data with Maui(?) software(confirmation needed, once again).
Thanks to both of you for pointing out these tips, I'll update the guide and credit you when I'll have more time. Cheers!
[*]For failed connections, make sure you flashed the NVRAM correctly(hence why you should test the telephony after you've repartitioned to stock 5.0 with the NVRAM backup flashed).If you failed to do that, I was told you should be able to recover the NVRAM data with Maui(?) software(confirmation needed, once again).
[/LIST]
Click to expand...
Click to collapse
After repartition, wifi, 3g and mobile signal works fine. I just cant flash twrp after unlocking bootloader otherwise i get a bootloop (unable to mount data and storage). So after i installed twrp and wiped/restore vendor and system, i reflashed stock recovery to acess android and then, restarted again to recovery. At this point, i did the write memory step again, using old vendor and the new vendor. None seem to work. I even backed up NVRAM using TWRP at first to make sure i did it right and tried to restore from there and it doesnt seem to be an IMEI issue. Maybe it has something to do with the frequency. Im on Brazil right now and idk
It does recognize my Sim card, my number, it downloads the data operators and etc but it doesnt connect to the mobile signal idk why. The bug starts at the restore step so it has something to do with this part.
I just test stuff but im pretty experienced at flashing and reflashing, etc. I guess only a dev can help and i actually went back to 7.1 UHANS rom, wich i got from 4pda.ru. Before using this rom, I was having a bluetooth audio stream bug and Ive tested like 4-5 roms, one for each kernel that was there. Lets see if someone can help me with this, cause i want oreo for better bluetooth audio stream.
Thanks for your help so far. I really apreciate it. This device is very good and we dont see many mods here on xda for it.
aurismat said:
@ZappaDong:
Yes, you should use the one I provided the link at the list of downloads.
Also, a bit late and I may be wrong, but your DRAM reads may be hindered by a MicroSD card(confirmation needed). Try ejecting it before you read off the NVRAM.
Click to expand...
Click to collapse
Thanks again!
I am using Windows 10 (bootcamp on the iMac) now and I have read the description in the 'old' [ROOT/TWRP] thread but used the files you have provided.
TWRP is working now, but I got an error that the ZIP file on the SD card was corrupted. Maybe I have damaged it when copying it to the SD card under OS X.
I am just redownloading it with Windows 10 and give it another try. (Yandex is very slow now, about 60 KB/s)
------------------------------------------------------------------
UPDATE
I have downloaded "WW_Phone-user_810_O11019_1528478718_release.zip" again, put in on the SD card, booted into Recovery, wiped system and vendor and chose "Install" , selected the "WW_Phone-user_810_O11019_1528478718_release.zip" file.
But I still get an error message.
Installing zip file '/external_SD/WW ... release.zip'
Checking for digest file
Skipping Digest Check: no Digest file found
[IN RED]Invailid zip file format!
Error installing zip file '/ 'external_SD/WW ... release.zip' [/IN RED]
Updating partion details...
...done
I have just copied the zip file from the download folder to the SD card - have I missed anything?
ZappaDong said:
And what TWRP.img should I use for
"3. Flash the recovery with fastboot flash recovery [twrp recovery name].img;"
in the next paragraph? Is this the "New recovery;" from the download section at the top?
Thank you!
Click to expand...
Click to collapse
Yup that one
@ZappaDong, yeah I kind of forgot to mention again - you should've extracted the .zip in which the backup came in. It's a backup, not an installation zip.
It needs to be extracted into its own folder inside the MicroSD card, so that then it could be used by TWRP to recover the partitions.
Thanks for pointing this out to me though, gonna edit it ASAP.
@fca.sjc bro AFAIK that problem of yours could be because of one or more of the following:
1. Your IMEI is missing or null. I would suggest SN Write tool (since I already tried it). Is quite effective, it is comparable to Maui Meta although I haven't tried it yet. (Tutorial here ==> https://forum.hovatek.com/thread-12306.html )
It is better to use PC restore tools since it writes directly to the nvram unlike apks like Chamelephon which (according to what I know) writes only to nvdata.
2. You need to switch the sims. What i mean is just if you have 2 sims on your phone, switch sim 1 in with sim 2. I forgot the explanation on it but it helps.
3. You need to switch off data connection on the other sim. On the several roms I tried on 4pda including this 8.1 pixel based rom, upon first bootup, the data connection on both sims are already on, therefore 3G cannot work. So first turn both sim's connection off then check if network mode is set to 3G. If not do the Solution #2.
JustAnormalGuy said:
@fca.sjc bro AFAIK that problem of yours could be because of one or more of the following:
1. Your IMEI is missing or null. I would suggest SN Write tool (since I already tried it). Is quite effective, it is comparable to Maui Meta although I haven't tried it yet. (Tutorial here ==> https://forum.hovatek.com/thread-12306.html )
It is the best IMEI restore tool since it writes directly to the nvram. (Meaning it retains even after wipes to data, system etc. via twrp)
2. You need to switch the sims. What i mean is just if you have 2 sims on your phone, switch sim 1 with sim 2. I forgot the logic on how that helps but I've seen it as a solution as the phone rereads the sims.
3. You need to switch off data connection on the other sim. On the several roms I tried on 4pda including this 8.1 pixel based rom, upon first bootup, the data connection on both sims are already on, therefore 3G cannot work. So first turn both sim's connection off then check if network mode is set to 3G. If not do the Solution #2.
Click to expand...
Click to collapse
Thanks for your help bro. I did check the IMEI while i was on this oreo rom. It seem to be ok. Number was there but i did not check if it was the right number. I might check it when i try to flash again. Probably later today when i'm home.
The problem wasnt just data connection, it was the connection itself. I couldnt call or receive SMS to activate whatsapp, for example. Like i said previously, those features were ok after repartitioning (on stock repartitioned). After the restore step, i did check all network options, including data, network mode, network connections available,etc. I'll follow your tutorial to restore the IMEI if the numbers are different then. I'll remember to take some screenshots next time so you guys can help me figure out what the problem is. Thanks again
aurismat said:
@ZappaDongIt's a backup, not an installation zip.
Click to expand...
Click to collapse
Yes, that did the trick. The installation went through and everything seems to work now.
Thank you again for your patience.
I saw there in the forum 4pda that are doing roms project treble pro zenfone go, only that I can not understand the mode of installation, you know how?
Ricardo Flowers said:
I saw there in the forum 4pda that are doing roms project treble pro zenfone go, only that I can not understand the mode of installation, you know how?
Click to expand...
Click to collapse
Yeah, it is possible -
FIrstly you'd need a vendor image that has fixed RIL(telephony) - vendor off this thread's 8.1 has RIL broken in Treble ROMs.
Luckily you can get it off any 8.1 custom ROM off ska-vova in 4pda. Just download any of his .zips(i.e. his ResurrectionRemix ROM(which imo is just official ResRemix with their Russian preference for a browser, but fine)), flash them and then backup the /vendor off it(and /boot for good measure)
Buuuuut then you need a TWRP that supports system image flashing - not sure if the one I provided here has it, if it hasn't - I'll post it here.
Then all you need to do is flash the Treble image, restore the /vendor(and /boot if you need to) and hope for the best!
Sadly the Havoc OS 2.0, the only ARM A-Only Pie-based ROM available here didn't work for me - just straight bootloops.
Your mileage may vary - if you get the Havoc OS 2.0 instaled, I'd love to read about it.
aurismat said:
Yeah, it is possible -
FIrstly you'd need a vendor image that has fixed RIL(telephony) - vendor off this thread's 8.1 has RIL broken in Treble ROMs.
Luckily you can get it off any 8.1 custom ROM off ska-vova in 4pda. Just download any of his .zips(i.e. his ResurrectionRemix ROM(which imo is just official ResRemix with their Russian preference for a browser, but fine)), flash them and then backup the /vendor off it(and /boot for good measure)
Buuuuut then you need a TWRP that supports system image flashing - not sure if the one I provided here has it, if it hasn't - I'll post it here.
Then all you need to do is flash the Treble image, restore the /vendor(and /boot if you need to) and hope for the best!
Sadly the Havoc OS 2.0, the only ARM A-Only Pie-based ROM available here didn't work for me - just straight bootloops.
Your mileage may vary - if you get the Havoc OS 2.0 instaled, I'd love to read about it.
Click to expand...
Click to collapse
Can you do a tutorial? I did not quite understand how it installs. Sorry, google translate does not help.
Deleted