Introduction:
Smartfren Andromax Q is the fourth device with official Cyanogen OS support.
http://www.xda-developers.com/xda-external-link/andromax-q-is-a-new-cyanogen-device-in-indonesia/
https://cyngn.com/blog/cyanogen-comes-to-indonesia-with-smartfren
http://www.smartfren.com/id/andromax-q/
Specification:
http://bestmobs.com/smartfren-andromax-q/
Device Codename:
"rendang": https://en.wikipedia.org/wiki/Rendang
Stock ROM:
Take a look in @Spannaa's thread in OnePlus One section to get a clear idea about signed fastboot zips, signed zips, boot-debuggable images and OTA incremental update zips. Cyanogen does provide stock factory package for this device (from 2015/09/04), but I'm able to scrap the all of the links using my tool.
Build 2015-11-11 (cm-12.1-YOG4PAS42M):
http://builds.cyngn.com/cyanogen-os...PAS42M-rendang-signed-fastboot-ae9f129c55.zip
http://builds.cyngn.com/cyanogen-os...rendang-signed-fastboot-ae9f129c55.zip.md5sum
http://builds.cyngn.com/cyanogen-os...12.1-YOG4PAS42M-rendang-signed-258d4e132b.zip
http://builds.cyngn.com/cyanogen-os...G4PAS42M-rendang-signed-258d4e132b.zip.md5sum
http://builds.cyngn.com/cyanogen-os...PAS42M-rendang-boot-debuggable-407a3c9ad7.img
http://builds.cyngn.com/cyanogen-os...rendang-boot-debuggable-407a3c9ad7.img.md5sum
Click to expand...
Click to collapse
YOG4PAS2H2 to YOG4PAS42M: http://builds.cyngn.com/incremental/rendang/cm-rendang-86917f8d9b-to-c4e9f095bc-signed.zip
Build 2015-09-15 (cm-12.1-YOG4PAS2H2):
http://builds.cyngn.com/cyanogen-os...m-12.1-YOG4PAS2H2-rendang-signed-fastboot.zip
http://builds.cyngn.com/cyanogen-os...YOG4PAS2H2-rendang-signed-fastboot.zip.md5sum
http://builds.cyngn.com/cyanogen-os...17f8d9b/cm-12.1-YOG4PAS2H2-rendang-signed.zip
http://builds.cyngn.com/cyanogen-os.../cm-12.1-YOG4PAS2H2-rendang-signed.zip.md5sum
http://builds.cyngn.com/cyanogen-os...m-12.1-YOG4PAS2H2-rendang-boot-debuggable.img
http://builds.cyngn.com/cyanogen-os...YOG4PAS2H2-rendang-boot-debuggable.img.md5sum
Click to expand...
Click to collapse
YNG1TBS1ZM to YOG4PAS2H2: http://builds.cyngn.com/incremental/rendang/cm-rendang-41daeb34c5-to-86917f8d9b-signed.zip
Build 2015-08-17 (cm-12.1-YOG4PAS1P4):
http://builds.cyngn.com/cyanogen-os...m-12.1-YOG4PAS1P4-rendang-signed-fastboot.zip
http://builds.cyngn.com/cyanogen-os...YOG4PAS1P4-rendang-signed-fastboot.zip.md5sum
http://builds.cyngn.com/cyanogen-os...726a317/cm-12.1-YOG4PAS1P4-rendang-signed.zip
http://builds.cyngn.com/cyanogen-os.../cm-12.1-YOG4PAS1P4-rendang-signed.zip.md5sum
http://builds.cyngn.com/cyanogen-os...m-12.1-YOG4PAS1P4-rendang-boot-debuggable.img
http://builds.cyngn.com/cyanogen-os...YOG4PAS1P4-rendang-boot-debuggable.img.md5sum
Click to expand...
Click to collapse
Build 2015-06-19 (cm-12.0-YNG1TBS2XI):
http://builds.cyngn.com/cyanogen-os...m-12.0-YNG1TBS2XI-rendang-signed-fastboot.zip
http://builds.cyngn.com/cyanogen-os...YNG1TBS2XI-rendang-signed-fastboot.zip.md5sum
http://builds.cyngn.com/cyanogen-os...82ddb7d/cm-12.0-YNG1TBS2XI-rendang-signed.zip
http://builds.cyngn.com/cyanogen-os.../cm-12.0-YNG1TBS2XI-rendang-signed.zip.md5sum
http://builds.cyngn.com/cyanogen-os...m-12.0-YNG1TBS2XI-rendang-boot-debuggable.img
http://builds.cyngn.com/cyanogen-os...YNG1TBS2XI-rendang-boot-debuggable.img.md5sum
Click to expand...
Click to collapse
Build 2015-05-16 (cm-12.0-YNG1TBS1ZM):
http://builds.cyngn.com/cyanogen-os...m-12.0-YNG1TBS1ZM-rendang-signed-fastboot.zip
http://builds.cyngn.com/cyanogen-os...YNG1TBS1ZM-rendang-signed-fastboot.zip.md5sum
http://builds.cyngn.com/cyanogen-os...aeb34c5/cm-12.0-YNG1TBS1ZM-rendang-signed.zip
http://builds.cyngn.com/cyanogen-os.../cm-12.0-YNG1TBS1ZM-rendang-signed.zip.md5sum
http://builds.cyngn.com/cyanogen-os...m-12.0-YNG1TBS1ZM-rendang-boot-debuggable.img
http://builds.cyngn.com/cyanogen-os...YNG1TBS1ZM-rendang-boot-debuggable.img.md5sum
Click to expand...
Click to collapse
Build 2015-04-24 (cm-12.0-YNG1TBS1DM):
http://builds.cyngn.com/cyanogen-os...m-12.0-YNG1TBS1DM-rendang-signed-fastboot.zip
http://builds.cyngn.com/cyanogen-os...YNG1TBS1DM-rendang-signed-fastboot.zip.md5sum
http://builds.cyngn.com/cyanogen-os...80facfc/cm-12.0-YNG1TBS1DM-rendang-signed.zip
http://builds.cyngn.com/cyanogen-os.../cm-12.0-YNG1TBS1DM-rendang-signed.zip.md5sum
http://builds.cyngn.com/cyanogen-os...m-12.0-YNG1TBS1DM-rendang-boot-debuggable.img
http://builds.cyngn.com/cyanogen-os...YNG1TBS1DM-rendang-boot-debuggable.img.md5sum
Click to expand...
Click to collapse
Flash Stock Firmware:
Code:
fastboot -i 0x201E oem unlock #Unlocks the bootloader; skip if already unlocked
fastboot -i 0x201E flash aboot emmc_appsboot.mbn
fastboot -i 0x201E flash modem NON-HLOS.bin
fastboot -i 0x201E flash rpm rpm.mbn
fastboot -i 0x201E flash sbl1 sbl1.mbn
fastboot -i 0x201E flash tz tz.mbn
fastboot -i 0x201E flash hyp hyp.mbn
fastboot -i 0x201E flash boot boot.img
fastboot -i 0x201E flash cache cache.img
fastboot -i 0x201E flash system system.img
fastboot -i 0x201E flash recovery recovery.img
fastboot -i 0x201E flash userdata userdata.img
fastboot -i 0x201E oem lock #Locks the bootloader (optional)
Track OTA:
https://play.google.com/store/apps/details?id=com.arjanvlek.cyngnotainfo
Unbricking the device (flash using Qualcomm QLOADER mode):
http://www.needrom.com/download/smartfren-andromax-g36c1h-cyanogenmod/
Root:
1. Unlock the bootloader (fastboot -i 0x201E oem unlock).
2. Flash (fastboot -i 0x201E flash recovery XXX.img) or tethered-boot (fastboot -i 0x201E boot XXX.img) the latest Cyanogen recovery (replace XXX with the name of the Cyanogen recovery).
3. Flash or adb sideload the latest SuperSU zip.
CyanogenMod:
Being an official Cyanogen supported device, CyanogenMod is already available for it.
Link to latest nightly: https://download.cyanogenmod.org/get/rendang-latest.zip
Link to latest snapshot: https://download.cyanogenmod.org/get/rendang-snapshot.zip
[Reserved for future]
I don't have the device myself, so it would be better if some friends from Indonesia will help me out
1. Please post the device's hardware IDs of adb & fastboot interfaces. We may need them to whitelist the device for detection.
Got the device IDs:
ro.usb.vid=201E
ro.usb.id.charge=F006
ro.usb.id.mtp=2282
ro.usb.id.mtp_adb=2281
ro.usb.id.ptp=2284
ro.usb.id.ptp_adb=2283
ro.usb.id.ums=2286
ro.usb.id.ums_adb=2285
Click to expand...
Click to collapse
2. Post raw backup of 'aboot' partition before & after unlocking bootloader; we need them to add this device in this project.
Kernel Source: https://github.com/CyanogenMod/android_kernel_smartfren_msm8916
Device Tree: https://github.com/CyanogenMod/android_device_smartfren_rendang
I would like to post a screenshot but every time I press the picture button it said "xdamobile has stopped responding" and there are 2 buttons report and OK. The same problem with bbm app. Also happen on FB Lite app, when trying to post a pic in a reply, didn't complained if I tried to post a pic as an actual post. :banghead:
Wondering what's wrong. I already did 5 factory resets and 1 complete os reinstall.
https://www.dropbox.com/sh/1xp5ltlnek0t0je/AACTgldjQsCkKozAoXhGrcmOa?dl=0 pictures/screenshots of antutu benchmark results
http://www.needrom.com/download/smartfren-andromax-g36c1h-cyanogenmod/ link to download full 1.3gb rom
Sent from my Andromax G36C1H using XDA Free mobile app
try to install another gallery source
COS 12.1 is available! Updated first post.
hd.herlambang said:
try to install another gallery source
Click to expand...
Click to collapse
so I have to uninstall the gallery app in the phone and replace it with another gallery app? I don't understand.
question:
I've rooted my device using KingRoot. I was able to download the whole 429.4mb worth of "incremental update" yesterday BUT was not able to install the update. after I pressed the "install update" button, the phone rebooted, went into the picture of the green android robot having a spinning stuff in the stomach while wiggling the antennae (which sent my kids to burst laughing), then it kicked me into recovery mode. unfortunately I picked the highlighted option, which would be the most logical for me after applying an update, which is "reboot system now" instead of "apply update" or "power off". but when I got back in, the build number didn't change. and also I can't find the update again while doing "check system update". after 2 restarts, then phone will notify me that there's an update available. so I thought that I will just redo the update, but alas I can't find it anywhere in the phone/physical sdcard. there's nothing dated 10/2/2015 (october 2nd, 2015). then I started opening every single available viewable folder, and found that the folder /dev and most of its contents were dated 10/2/2015. and well, it seemed like that I have to waste another 500mb to redownload the whole updates again. although I'm not sure what went wrong.
should I unroot first? or should I reflash the whole phone first? can anyone give me any advice? thanks!
@bulukaki
It would be better to get the latest fastboot flashable package & do a clean flash.
@Titokhan
Build 2015-09-15 (cm-12.1-YOG4PAS2H2)
Build 2015-08-17 (cm-12.1-YOG4PAS1P4)
what was the differences between of them ? in addition to the built date.
why there were YNG1TBS1ZM to YOG4PAS2H2: http://builds.cyngn.com/incremental
whereas the latest CM12.0 is cm-12.0-YNG1TBS2XI ?
and there is no YNG1TBS2XI to YOG4PAS2H2.
@hd.herlambang
As Cyanogen doesn't publish any official changelogs, we've to depend of CyanogenMod changelogs: http://www.cmxlog.com/12.1/rendang/
Again, the incremental OTAs are tracked via Cyanogen's own API so it entirely depends on them.
Just bought this phone. Thanks for the thread.
I am trying to build cyanogenmod using the build guide for rendang. (can't include url)
There is some problem but i've past that. Now i meet another problem that i'm stuck.
Error after brunch rendang.
target thumb C++: libinputservice <= frameworks/base/libs/input/PointerController.cpp
target thumb C++: libinputservice <= frameworks/base/libs/input/SpriteController.cpp
target thumb C: libsuspend <= system/core/libsuspend/autosuspend.c
target thumb C: libsuspend <= system/core/libsuspend/autosuspend_autosleep.c
target thumb C: libsuspend <= system/core/libsuspend/autosuspend_earlysuspend.c
target thumb C: libsuspend <= system/core/libsuspend/autosuspend_wakeup_count.c
make: *** No rule to make target `/media/im/ext4/andromaxQ/cyanogen/out/target/product/rendang/obj/lib/libtime_genoff.so', needed by `/media/im/ext4/andromaxQ/cyanogen/out/target/product/rendang/obj/SHARED_LIBRARIES/libandroid_servers_intermediates/LINKED/libandroid_servers.so'. Stop.
make: *** Waiting for unfinished jobs....
make: Leaving directory `/media/im/ext4/andromaxQ/cyanogen'
Click to expand...
Click to collapse
Someone can give any hint about it?
Titokhan said:
[Reserved for future]
I don't have the device myself, so it would be better if some friends from Indonesia will help me out
1. Please post the device's hardware IDs of adb & fastboot interfaces. We may need them to whitelist the device for detection.
Got the device IDs:
2. Post raw backup of 'aboot' partition before & after unlocking bootloader; we need them to add this device in this project.
Click to expand...
Click to collapse
How can I help/participate for this project? I have a non-rooted bootloader-locked Andromax Q with CM12.1 installed
@zlebors
Thanks for your interest. You need to unlock the bootloader, temp-boot CyanogenMod recovery, sideload SuperSU zip to be rooted. Then backup the 'aboot' partition. Now relock the bootloader & again backup the 'aboot' partition - please post those two backups.
:good::highfive:
Updated first post - cm-12.1-YOG4PAS42M-rendang.
Ask
Gan... Andromax Qi bisa di root ga ?
Soalnya pake kingroot gagal terus
need my SF Max Q to be rooted, was failed with kingroot and iroot. anyone could help?
when later i have rooted-phone, i wanna move pre-installed apps like chrome or google other fam apps, is it affecting on next update of cyanogen os installation?
@rahendz
1. To root, please read the first post carefully. You just need to flash SuperSU zip package via CyanogenMod recovery.
2. Yes, removing system applications leads to inability to install subsequent OTA. But you can grab the full signed zip from the first post & flash to bypass this problem.
Titokhan said:
@rahendz
1. To root, please read the first post carefully. You just need to flash SuperSU zip package via CyanogenMod recovery.
2. Yes, removing system applications leads to inability to install subsequent OTA. But you can grab the full signed zip from the first post & flash to bypass this problem.
Click to expand...
Click to collapse
which full signed zip exactly?
YOG4PAS2H2 to YOG4PAS42M: http: //builds.cyngn.com/incremental/...5bc-signed.zip
Click to expand...
Click to collapse
i downloaded it and try to flash, bu i have "signature verification failed" in return. is there something wrong?
Titokhan said:
Root:
1. Unlock the bootloader (fastboot -i 0x201E oem unlock).
2. Flash (fastboot -i 0x201E flash recovery XXX.img) or tethered-boot (fastboot -i 0x201E boot XXX.img) the latest Cyanogen recovery (replace XXX with the name of the Cyanogen recovery).
3. Flash or adb sideload the latest SuperSU zip.
Click to expand...
Click to collapse
Thanks for step guide rooting this device, it works 100%. Even i know this quite late though but it's great to know what works. Sorry for my bad english. May i ask once again tito? just before i know this step, i try many ways to root and makes my HH little uncomfortable to use and i wanna flash with CM12.1 stock, in many post i barely understand the step.
Could you just give me easy step to understand how to flash CM12.1 using adb fastboot? because what i read, i've download the stock with size almost 1.5gb but in next step we only need the boot, recovery and system image. But in another post, those three taken from platform-tool compressed file. that's what makes me confused. thanks before.
Related
Hi All, I am starting this thread with the very reason to educate and help newbies as well serve as a resource guide that could be used by all.
In this guide I will be explaining about the following:
1) Unlocking Bootloader
2) Flashing TWRP and Rooting
3) Restore to Stock
4) Remove unlocked bootloader warning
Please let me know if anyone needs more info/help on anything. I will try my best to help you and add it to this guide so everybody benefits from it.
Unlocking Bootloader
>>> Unlocking Bootloader will overwrite any data stored on your device, backup your files before proceeding <<<
Unlocking Bootloader:
1- Register
Head to Motorola website and register your E-Mail ID.
Open Setting on your device and go to About Phone. Next, tap 7 times on Build Number and get the Developer Options unlocked.
Head back to Main Settings Menu and go to Developer Options and switch the 'Allow OEM Unlock' option.
2- Getting Unique ID for each device
Reboot to Bootloader (power off, then press the power and volume down buttons simultaneously).
On your desktop, open a command prompt or terminal, and go to the directory where you installed the Android SDK tools (or make sure mfastboot is in your $PATH)
At the prompt, type
Code:
$ mfastboot oem get_unlock_data
You will get something like this:
On a Windows Desktop, the returned string format would be
Code:
$ fastboot oem get_unlock_data
(bootloader) 0240540162024205#4C4D3556313230
(bootloader) 30373as313630330df332323239#BD00
(bootloader) 8A672BA4746C2CE0a328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
On a Mac OS Desktop, the returned string format would be
Code:
INFO0A40040192024205#4C4D3556313230
INFO30373731363031303332323239#BD00
INFO8A672BA4746C2CE02328A2AC0C39F95
INFO1A3E5#1F53280002000000000000000
INFO0000000
Paste together the 5 lines of output into one continuous string without (bootloader) or ‘INFO’ or white spaces. Your string needs to look like this:
Code:
0240540162024205#4C4D355631323030373as313630330df332323239#BD008A672BA4746C2CE0a328A2AC0C39F951A3E5#1F532800020000000000000000000000
3- Unlocking the device
Check if your device can be unlocked by pasting this string in the specific field on the Motorola website, and clicking “Can my device be unlocked?”
NOTE: If your device is unlockable, a "REQUEST UNLOCK KEY" button will now appear at the bottom of that page. Click on it and wait for the unique code to be sent to your mail.
After you got the code type the following :
Code:
mfastboot oem unlock <code>
and wait your device to reboot !
Flashing TWRP and Rooting
Flashing TWRP:
>>> Flashing TWRP or Rooting will void your warranty. Please ask anything before doing, if your not fully confident on what to be done. <<<
Get the TWRP image file from http://forum.xda-developers.com/mot...p-twrp-3-0-2-2-recovery-moto-g4-plus-t3386586
Next, get the adb and mfastboot from https://drive.google.com/file/d/0B5jlU9JnLAZGbVU0UzJ3N3p4X2M/view?usp=sharing
Unzip the file and place the image file inside the extracted folder.
Reboot to Bootloader (power off, then press the power and volume down buttons simultaneously).
Open a new command prompt or terminal window and do the following:
Code:
mfastboot flash recovery twrp_*version*_athene.img
Rooting Device:
>>> The old guide is outdated. Will be updated shortly. <<<
Restore Stock Firmware
>>> Please know your model number properly. I am not responsible if you flash the wrong firmware. <<<
NOTE: Flashing the wrong firmware may only leave you with no RIL temporarily but always be careful.
Flashing Stock Firmware:
1) Download the correct firmware for your device from http://www.filefactory.com/folder/c6cdedc45a775d27
2) Download adb and fastboot from https://drive.google.com/file/d/0B5jlU9JnLAZGbVU0UzJ3N3p4X2M/view?usp=sharing
3) Extract the firmware into the folder containing abd and fastboot.
4) Reboot the phone into Bootloader (power off, then press the power and volume down buttons simultaneously).
5) Execute these commands and make sure you receive an 'OKAY' after each command.
Code:
mfastboot oem fb_mode_set
mfastboot flash partition gpt.bin
mfastboot flash bootloader bootloader.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash dsp adspso.bin
mfastboot flash oem oem.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash system system.img_sparsechunk.4
mfastboot flash system system.img_sparsechunk.5
mfastboot flash system system.img_sparsechunk.6
mfastboot flash system system.img_sparsechunk.7
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot erase customize
mfastboot erase clogo
mfastboot oem fb_mode_clear
mfastboot reboot
OR
5) You can use the script I have attached below(Windows only) to flash it for you. Just download the zip and extract it into same folder and run it.
Device will now Reboot into Stock.
>>> Irritated by the Unlocked Bootloader Warning? <<<
Download the attached file.
Download adb and fastboot from here : https://drive.google.com/file/d/0B5j...ew?usp=sharing
Extract the downloaded file into the same folder as adb and fastboot is extracted to
Open a command prompt and type in the following:
Code:
mfastboot flash logo logo.bin
Reboot
Reserved!
Flash this- LazyFlasher - https://goo.gl/dBzV6q After flashing SuperSU! Device should reboot fine!
Or else we can create modified boot image and flash it and then flash SuperSU
TheDj408 said:
Flash this- LazyFlasher - https://goo.gl/dBzV6q After flashing SuperSU! Device should reboot fine!
Or else we can create modified boot image and flash it and then flash SuperSU
Click to expand...
Click to collapse
We need modified boot.img for now but I am busy with work so can't get full time on it. Will try to get root asap!
boot.img need to disable selinux it interferes with root
Please download the TWRP to another site, Android File Host is updated.
TheDj408 said:
Flash this- LazyFlasher - https://goo.gl/dBzV6q After flashing SuperSU! Device should reboot fine!
Or else we can create modified boot image and flash it and then flash SuperSU
Click to expand...
Click to collapse
Did you try with lazy flasher? TWRP and Root worked?
carreddy said:
Did you try with lazy flasher? TWRP and Root worked?
Click to expand...
Click to collapse
you had to download the TWRP before the site went to repair?
Good Collection..
"At last but not least"
You forget to mention... This Process will void your cell phones Warranty
sirtbhopal said:
Good Collection..
"At last but not least"
You forget to mention... This Process will void your cell phones Warranty
Click to expand...
Click to collapse
I will update OP with that. Thanks
wizard-dima said:
you had to download the TWRP before the site went to repair?
Click to expand...
Click to collapse
wizard-dima said:
boot.img need to disable selinux it interferes with root
Please download the TWRP to another site, Android File Host is updated.
Click to expand...
Click to collapse
AFH is up now. I have also uploaded to G Drive. Please check the TWRP thread for links.
no networks or wifi after flashing stock rom
after flashing stock rom there is no mobile network or wifi turning on
also while flashing partition i am getting following error
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.046s
Srbjitkng said:
after flashing stock rom there is no mobile network or wifi turning on
also while flashing partition i am getting following error
writing 'partition'...
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.046s
Click to expand...
Click to collapse
Which file did u download? I believe you have the wrong file. Link it here or pm me or find me on facebook.com/yeshwanthvshenoy for faster help.
EDIT : This is the correct stock rom for Indian devices http://www.filefactory.com/file/64m...24.139-23.1_cid50_subsidy-DEFAULT_CFC.xml.zip
yeshwanthvshenoy said:
Which file did u download? I believe you have the wrong file. Link it here or pm me or find me on facebook.com/yeshwanthvshenoy for faster help.
EDIT : This is the correct stock rom for Indian devices http://www.filefactory.com/file/64m...24.139-23.1_cid50_subsidy-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Yeshwant did u started developing something for our moto g
link which i have downloaded
yeshwanthvshenoy said:
Which file did u download? I believe you have the wrong file. Link it here or pm me or find me on facebook.com/yeshwanthvshenoy for faster help.
hi,i have moto g4 plus xt1643
i downloaded my stock rom named
G4_XT1641-XT1643_ATHENE_6.0.1_MPJ24.139-13.1_cid50_subsidy-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Srbjitkng said:
yeshwanthvshenoy said:
Which file did u download? I believe you have the wrong file. Link it here or pm me or find me on facebook.com/yeshwanthvshenoy for faster help.
hi,i have moto g4 plus xt1643
i downloaded my stock rom named
G4_XT1641-XT1643_ATHENE_6.0.1_MPJ24.139-13.1_cid50_subsidy-DEFAULT_CFC.xml.zip
Click to expand...
Click to collapse
Check my previous post. I have already provided the link for you. I am pretty sure if you flash it, it will solve the issues. I had the same issue few days back. It is confusing their naming convention for the file. We have XT1643 and there are lot of files that refer to XT1643. Technically, it is the same device but with different radio(you might have flashed the uk firmware or the eu firmware, maybe). I know its a bit confusing but for now just download the link I gave you and you will be back to normalcy. Peace
Click to expand...
Click to collapse
Worked!!!
Thanks!!!for the link....Got back to stock....every thing is working
will the phone be under warranty if I restore the "stock firmware"?
If not, is it possible anyhow to regain phone's warranty?
Hi there!
I've been trying to port CM14.1 to my Oppo F1 (code f1f with Snapdragon 616). I got a build with backlight always on and a lot of things already working (touchscreen, 4G, camera).
After a few hours digging into the code and a dozen of kernel builds, I couldn't find a way to make the backlight brightness level work correctly. From my understanding, this Oppo device (among other CM friends sharing the same kernel repo) seems to be the only one using GPIO to initialize the backlight. It seems that the MSM video driver is using this kind of Qualcomm SoC « magic » registers to control the backlight.
Has anyone been working on this? Any repo recommandations from where I could take inspiration to fix this?
A picture to encourage anyone to work on this…
kdd998 said:
Hi there!
I've been trying to port CM14.1 to my Oppo F1 (code f1f with Snapdragon 616). I got a build with backlight always on and a lot of things already working (touchscreen, 4G, camera).
After a few hours digging into the code and a dozen of kernel builds, I couldn't find a way to make the backlight brightness level work correctly. From my understanding, this Oppo device (among other CM friends sharing the same kernel repo) seems to be the only one using GPIO to initialize the backlight. It seems that the MSM video driver is using this kind of Qualcomm SoC � magic � registers to control the backlight.
Has anyone been working on this? Any repo recommandations from where I could take inspiration to fix this?
A picture to encourage anyone to work on this�
Click to expand...
Click to collapse
Backlight works fine on cm13 builds. Are you using kernel source from the cyanogenmod git? Did you have to make any changes to the kernel source? CM kernel source was working fine for me with cm13 up to about a month ago but then started causing bootloops (seems to be something in the dtb). Also, does rotation work, I have been having problems using their sources with accelerometer. I do have a build of cm13 with everything working well, but it is using @uberlaggydarwin kernel source from github and I don't think he wants me to share things built from it (better moving forward to be on official cm sources anyway).
Try this op2 also has backlight issue in custom rom.
Group Butler [beta]:
Type the below commands in terminal to turn off backlight
su (give permission when prompted)
echo 0 > /sys/class/leds/button-backlight/max_brightness
chmod 755 > /sys/class/leds/button-backlight/max_brightness
MiniBlu said:
Backlight works fine on cm13 builds. Are you using kernel source from the cyanogenmod git?
Click to expand...
Click to collapse
Yes, the msm8939 kernel common to Oppo devices.
MiniBlu said:
Did you have to make any changes to the kernel source?
Click to expand...
Click to collapse
Yes, changes are necessary. I didn't have a look at audio yet, but the touchscreen driver needs changes, dtsi files to clear warnings and the lm3630 driver needs a lot of changes to make the probe work.
MiniBlu said:
CM kernel source was working fine for me with cm13 up to about a month ago but then started causing bootloops (seems to be something in the dtb).
Click to expand...
Click to collapse
Yes, but with cm-14.1, there's a big gap in the kernel source. It seems to be nearer the CAF source and all the ugly Oppo ifdefs are out (seriously, Oppo's coding style is awful ).
MiniBlu said:
Also, does rotation work, I have been having problems using their sources with accelerometer.
Click to expand...
Click to collapse
I'll try to see if rotation is OK but I have doubts. I didn't have a look at it yet. Which device is it?
Ucihaflash said:
Type the below commands in terminal to turn off backlight
su (give permission when prompted)
echo 0 > /sys/class/leds/button-backlight/max_brightness
chmod 755 > /sys/class/leds/button-backlight/max_brightness
Click to expand...
Click to collapse
Thanks for the tip, I'll have a look, but I find it strange that this device is in the leds class, I thaught it was in the backlight class. It needs to be tried anyway
So, rotation doesn't work. But button-backlight is there, but I cannot control backlight. I'll continue digging…
Wow u actually been able to put cm14 on oppo f1. C
When you finish this will you make it public? Many people would love this
Of course, if ever I succeed, it's open source. The goal is to have an official device in CM. But on CM14.1, we're far from it. On CM13, I believe it's almost ready, but i'll let the actual devs who did the job take care of it.
Thanks so much. Good luck with cm14. Hope u succeed! ?
verry happy to see that, good luck thank's:good::good::good::good::good::good:
kddoran said:
verry happy to see that, good luck thank's:good::good::good::good::good::good:
Click to expand...
Click to collapse
- 6months latter
........... . .when you guys realize that Oppo has the worst vendor ive ever seen on the planet, bad,slowest(never)get update at all..
MiniBlu said:
Backlight works fine on cm13 builds. Are you using kernel source from the cyanogenmod git? Did you have to make any changes to the kernel source? CM kernel source was working fine for me with cm13 up to about a month ago but then started causing bootloops (seems to be something in the dtb). Also, does rotation work, I have been having problems using their sources with accelerometer. I do have a build of cm13 with everything working well, but it is using @uberlaggydarwin kernel source from github and I don't think he wants me to share things built from it (better moving forward to be on official cm sources anyway).
Click to expand...
Click to collapse
Which sources did you use to build? Last time I tried compiling from the official sources I got some errors building the kernel so I gave up but that was a while ago.
As an Oppo f1 user, good luck to your project since oppo never update its thing
kdd998 said:
Of course, if ever I succeed, it's open source. The goal is to have an official device in CM. But on CM14.1, we're far from it. On CM13, I believe it's almost ready, but i'll let the actual devs who did the job take care of it.
Click to expand...
Click to collapse
Is there a hope for getting officially build on CM
i am currently on project spectrum and want to flash back colour os through fastboot. has anyone done it before. i want to do it but have a habit of bricking my device. Would this be correct.
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery.img
or
flashall
or will fastboot -w and fastboot update colouros.zip work?
which would work?
Jamie_oppo said:
i am currently on project spectrum and want to flash back colour os through fastboot. has anyone done it before. i want to do it but have a habit of bricking my device. Would this be correct.
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery.img
or
flashall
or will fastboot -w and fastboot update colouros.zip work?
which would work?
Click to expand...
Click to collapse
no. none of the above will work. System image is to large to flash by fastboot.
To return to coulouros you would need to pull these files form the colouros.zip and put them in you fastboot folder
boot.img
logo.bin
NON-HLOS.bin
reserve4.img
rpm.mbn
sbl1.mbn
static_nvbk.bin
tz..mbn
then pull emmc_appsboot.mbn from magictricks.zip, and put it in fatboot folder.
then put twrp-3.0.2-0-f1f.img in fastboot folder.
then put modified colouroszip file from here on your external sdcard.
From cmd in fastboot folder run
fastboot flash boot boot.img
fastboot flash LOGO logo.bin
fastboot flash modem NON-HLOS.bin
fastboot flash reserve4 reserve4.img
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash oppostanblk static_nvbk.bin
fastboot flash tz tz.mbn
fastboot flash recovery twrp-3.0.2-0-f1f.img
fastboot boot recovery twrp-3.0.2-0-f1f.img
Unplug usb cable.
This should have flashed all firmware back to stock (except bootloader to magicktricks unlocked bootloader and recovery to twrp) and rebooted you into twrp. You can now WIPE data and cache then flash the colouros.zip. (once in colouros you may need to enable oem unlocking in developer settings and then do a fastboot oem unlock.)
From here if you want to go back to project spectrum you can just flash the colouros recovery I sent you earlier and the flash project spectrum from it.
*NOTE* all the above should work but you attempt this at your own risk. I take no responsibility for possible bad outcome.
Thanks so much. I will try this as soon as I can. If something goes wrong after fastboot boot the twrp image will I still have fastboot just in case??
MiniBlu said:
no. none of the above will work. System image is to large to flash by fastboot.
To return to coulouros you would need to pull these files form the colouros.zip and put them in you fastboot folder
boot.img
logo.bin
NON-HLOS.bin
reserve4.img
rpm.mbn
sbl1.mbn
static_nvbk.bin
tz..mbn
then pull emmc_appsboot.mbn from magictricks.zip, and put it in fatboot folder.
then put twrp-3.0.2-0-f1f.img in fastboot folder.
then put modified colouroszip file from here on your external sdcard.
From cmd in fastboot folder run
fastboot flash boot boot.img
fastboot flash LOGO logo.bin
fastboot flash modem NON-HLOS.bin
fastboot flash reserve4 reserve4.img
fastboot flash rpm rpm.mbn
fastboot flash sbl1 sbl1.mbn
fastboot flash oppostanblk static_nvbk.bin
fastboot flash tz tz.mbn
fastboot flash recovery twrp-3.0.2-0-f1f.img
fastboot boot recovery twrp-3.0.2-0-f1f.img
Unplug usb cable.
This should have flashed all firmware back to stock (except bootloader to magicktricks unlocked bootloader and recovery to twrp) and rebooted you into twrp. You can now WIPE data and cache then flash the colouros.zip. (once in colouros you may need to enable oem unlocking in developer settings and then do a fastboot oem unlock.)
From here if you want to go back to project spectrum you can just flash the colouros recovery I sent you earlier and the flash project spectrum from it.
*NOTE* all the above should work but you attempt this at your own risk. I take no responsibility for possible bad outcome.
Click to expand...
Click to collapse
i extacted all the files and put twrp and the magictricks thing in the fastboot folder
fastboot flash boot boot.img
fastboot flash LOGO logo.bin
fastboot flash modem NON-HLOS.bin These all worked fine
but when i got to reserve4 i got C:\Users\ponyd\Desktop\back to colour os>fastboot flash reserve4 reserve4.img
target reported max download size of 268435456 bytes
sending 'reserve4' (5176 KB)...
OKAY [ 0.200s]
writing 'reserve4'...
FAILED (remote: size too large)
finished. total time: 0.216s
i shat my self when that happened? i then flashed the boot.img logo and modem of project spectrum and went back to spectrum. DId i do something wrong?
Backlight fix
Try coloros setting app. Search and u will get it.
I'm actually under spectrum project hope you could port this cm14.1 for OPPO f1...
Thanks
I know this may be abit reluctance but you may want to open source the project on what you have now and list what is working and what's isn't, and I'm sure people will contribute to the project given that is qcom there should not be much of an issue to get it working.
Stock ROM for Moto G4/G4 Plus NPJS25.93-14-8
Installing this Stock ROM will unroot your device and remove any custom Recovery.
If you device is soft bricked or facing bootloop issue or experience lags, then you should download and Flash this ROM.
This is the latest Stock Firmware of Moto G4 and Moto G4 Plus.
Build - NPJS25.93-14-8
This build will update your Bootloader. If you try to downgrade it for any reason, you may brick your device.
This process can take roughly 20-30 minutes so please be patient.
This Flashable zip can install over any previous version including Soak ROM or MM or Custom ROM.
As you already know, you Don't have to unlock your bootloader.
Prerequisites:
RSDLite 6.2.4
Firmware 7.0_NPJS25.93-14-8 [Thanks to AFH and uploaders]
Procedure 1:
♦ Download the application RSDLite and install it.
♦ Download and unpack the firmware from rar.
♦ Run RSDLite.
♦ Click on the button with three dots and select flashall.xml.
♦ Reboot your phone into fastboot mode [press the volume down + power button]
♦ Connect your phone to a PC. The program should detect the phone.
♦ Press the Start button and wait until the end of the firmware until the phone restarts.
Procedure 2:
You can also use fastboot commands if you prefer it.
♦ Download ADB and fastboot driver for your PC/MAC
♦ Download and install Drivers for your Moto G4/G4 Plus
♦ Download ROM
♦ Now Power Off your phone and boot into Bootloader mode [Press and Hold "Power + Volume Down"]
♦ Use the below commands one by one. [If you are using mfastboot then type 'mfastboot' instead of 'fastboot']
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
fastboot reboot
If you want to lock your Bootloader use the below lines.
Code:
fastboot oem fb_mode_set
fastboot oem lock begin
fastboot oem lock begin
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem lock
fastboot oem fb_mode_clear
fastboot reboot
or use the batch from attachment
You MUST take backup of your important data. I am NOT responsible for data loss or bricked device
Tested on my XT1643.
are you sure it works??
[email protected]$hil said:
are you sure it works??
Click to expand...
Click to collapse
it must have to. btw it worked for me
arunzone said:
it must have to. btw it worked for me
Click to expand...
Click to collapse
the firmware download link does not work.. it says something went wrong
[email protected]$hil said:
the firmware download link does not work.. it says something went wrong
Click to expand...
Click to collapse
check now. the link has been updated.
[email protected]$hil said:
the firmware download link does not work.. it says something went wrong
Click to expand...
Click to collapse
Translate the web page and sign in using google or telegram account.... it worked to download from there.... haven't installed tho...
arunzone said:
check now. the link has been updated.
Click to expand...
Click to collapse
Thnx now downloading
It works perfectly. I was able to flash lastest Nougat update over 1st Soak Test. It's completely not necessary to downgrade to MM and unlock bootloader.
How is this working???
Between 1st soak and final OTA, 2 more soak test builds came i heard. How is this process working for you. please help explain!!!
arunzone said:
Many of us has already installed the first soak test and now have problems while update to latest version. This tutorial is for those who don't want to unlock their bootloader.
This process can take roughly 20-30 minutes so please be patient.
This Flashable zip can install over Soak Test ROM or MM.
You Don't have to unlock your bootloader or downgrade to MM and data will not be deleted.
Prerequisties:
RDSLite
Firmware
Procedure:
Download the program and install.
Download and unpack the firmware.
Run the program.
Click on the button with three dots and select flashall.xml.
Reboot your phone into fastboot mode [press the volume down + power button]
Connect your phone to a PC. The program should detect the phone.
Press the Start button and wait until the end of the firmware until the phone restarts.
As a precaution, enable OEM Unlocking under developer options. If anything goes wrong you can still unlock your bootloader and install custom firmware.
Also take backup of your important data.
I am not responsible if you brick your device.
Tested on my XT1643 with unlocked bootloader with soak 1.
Click to expand...
Click to collapse
Will it work with Windows XP? Also please mention required drivers & if possible link to download drivers.
arunzone said:
Many of us has already installed the first soak test and now have problems while update to latest version. This tutorial is for those who don't want to unlock their bootloader.
This process can take roughly 20-30 minutes so please be patient.
This Flashable zip can install over Soak Test ROM or MM.
You Don't have to unlock your bootloader or downgrade to MM and data will not be deleted.
Prerequisties:
RDSLite
Firmware.
Click to expand...
Click to collapse
Does this Firmware support VoLTE?
Sent from my XT1562 using Tapatalk
Worked perfectly with modified system on first soaktest and twrp Recovery, so no need to delect them before. After flashing the updated firmware, the system is clean and Stock Recovery is back. :good:
kumeipark said:
Does this Firmware support VoLTE?
Click to expand...
Click to collapse
Yes it supports volte feature.
praveenbda said:
Will it work with Windows XP? Also please mention required drivers & if possible link to download drivers.
Click to expand...
Click to collapse
Yes. Please install drivers from Motorola website or from below link.
https://forum.xda-developers.com/showthread.php?t=2588979
rishisharma1986 said:
Between 1st soak and final OTA, 2 more soak test builds came i heard. How is this process working for you. please help explain!!!
Click to expand...
Click to collapse
Since this this is flashable, it doesn't look for what your Mobile already has. It will just install the rom. Even if you are not on official rom.
arunzone said:
Since this this is flashable, it doesn't look for what your Mobile already has. It will just install the rom. Even if you are not on official rom.
Click to expand...
Click to collapse
Will this clear all my data or just installs like ota ?
sam sundar said:
Will this clear all my data or just installs like ota ?
Click to expand...
Click to collapse
It won't delete your data. Just take a backup as a failsafe.
arunzone said:
it must have to. btw it worked for me
Click to expand...
Click to collapse
How to download the firmware frm the file given they r saying some dfrnt language
---------- Post added at 05:16 AM ---------- Previous post was at 05:10 AM ----------
arc4d14n said:
Translate the web page and sign in using google or telegram account.... it worked to download from there.... haven't installed tho...
Click to expand...
Click to collapse
Bro how to translatethe webpage
gokulkishor said:
How to download the firmware frm the file given they r saying some dfrnt language
---------- Post added at 05:16 AM ---------- Previous post was at 05:10 AM ----------
Bro how to translatethe webpage
Click to expand...
Click to collapse
Open the link in chrome and it ask to translate. That page contains only one button in the center of the page. Click it. A dialog box will appear, tick the check box and click on enabled button.
gokulkishor said:
How to download the firmware frm the file given they r saying some dfrnt language
---------- Post added at 05:16 AM ---------- Previous post was at 05:10 AM ----------
Bro how to translatethe webpage
Click to expand...
Click to collapse
I've used Google Chrome automatic translate, anyway it was for older link, it has been updated, but if it's in Russian as the previous one, you can use the same method
Guys, tired of waiting for Nougat update on my Moto X Pure I took a route and never regretted. I converted my Pure edition to Style RETEU.en and went all the way to Nougat, without any hiccup.. Phone is as smooth as was with Marshmallow version. Below I will describe all the steps for successful update to Nougat. Skipping the details that we all know of. REMEMBER: You do at your own risk and I am not responsible for any of your mistake (Complete each step exactly. They are simple)
1. Get your bootloader unlocked as we will require it once, to take a nandroid backup for safety.
2. Install TWRP 3.1.1.0 to make a nandroid backup on phone.
3. Once backup is done copy it from phone to PC to make it safe. It will take some time as mine was 6GB in size.
4. Before rebooting into fastboot select "Do not install TWRP" in recovery.
5. Now using fastboot start flashing components from Official stock ROM of Motorola downloaded from dl.prazaar.de which is XT1572_CLARK_RETEU_6.0.1_MPHS24.107-58-5. This is Android Marshmallow base at 6.0.1. Not to flash components is boot, partition, Modem, fsk and recovery files. Make sure you flash rest of files including all the sparsechunks. Commands can ne found elsewhere on the forum.
6. Reboot into recovery and clear cache and userdata partitions. Reboot normal now.
7. Phone will start the setup like after factory reset. Just skip restoring your personal data by answering No to save time. But let it complete whatever else it do. Now "About phone" will say device is Moto X Style and build is MM 6.0.1 RETEU.en. This is just fine. Phone converted (No GSM signal is no worry at this time).
8. Try System Update. If update is available fine, otherwise we do it manually to take it to MPHS24.107-58-13 (required as Nougat pre-requisite).
9. Download Blur_Version.24.221.5.clark_reteu.reteu.en.EU from dl.prazaar.de. This is MPHS24.107-58-13 update. Copy it to root of Phone memory and reboot to recovery and pick Apply update from SDcard. The update will happen smoothly.
10. Again boot and skip Android setup. About phone will say your current build version.
11. Now download and copy Blur_Version.24.231.13.clark_reteu.reteu.en.EU from dl.prazaar.de into root directory of your phone.
12. Boot into recovery and choose Apply the file from SDCard. WOW this is Nougat update. It will successfully complete the update.
13 Download Last official Clark MM stock ROM from Motorola website and open the zip file to extract NON-HLOS.bin and fsk.mbn and flash it from fastboot in the standard way.
14. Go into recovery and clean cache and userdata partitions
15. Boot normally to be greeted by Nougat firsttime setup.
16. Congratulations. You have Nougat and Moto X Style.
No links to files?
You have not read it completely. I have mentioned download source which is dl.prazaar.de for all the files. Since each file is Stock ROM or blur version and greater than 1GB. What is the purpose to attach them here? The site is well know to carry Style firmware.
What about ota?
Bart_UA said:
What about ota?
Click to expand...
Click to collapse
There are two files I mentioned that starts with the name "Blur_Version". These are always OTAs!!! You apply through Wifi or SDCard, what is the difference?
This is my About Phone screen after the update.
jaffers said:
This is my About Phone screen after the update.
Click to expand...
Click to collapse
You can do backup with twrp and upload it for them.
Boot(before root)+system only.
Root is not required in my steps and TWRP not installed permanently (See my steps).
I know. I have xt1572, don't need.
For others you can do backup and upload it. All what they need: boot+system partitions.
For Backup & restore:
fastboot boot twrp.img
Anyone who want restore should do own backup and copy yours into the same folder.
Into twrp works MTP.
GOOD LUCK FOR ALL.
Out of curiosity... why go through this when its "easier" to just root and flash DU or LineageOS? Is the "stock" nougat running that much more smoothly? Its 7.0 with an old security path right? The latest versions of DU and Lineage are 7.1.2 and have up to date security patches.
Bwangster12 said:
Out of curiosity... why go through this when its "easier" to just root and flash DU or LineageOS? Is the "stock" nougat running that much more smoothly? Its 7.0 with an old security path right? The latest versions of DU and Lineage are 7.1.2 and have up to date security patches.
Click to expand...
Click to collapse
Very simple. people like me don't want to loose Moto Action, Moto Display and Moto Voice. You loose all that in custom roms. I tried Lineage in my wife's Moto X 2014 a month ago. Frequent reboots, crash and reboot during video recording etc. This after several months of constant updates. Stock ROM do not have this type of issues. Atleast in the last decade not once any of my phone ever rebooted on its own. So I don't approve custom roms. If you don't mind, go ahead.
dzidexx said:
I know. I have xt1572, don't need.
For others you can do backup and upload it. All what they need: boot+system partitions.
For Backup & restore:
fastboot boot twrp.img
Anyone who want restore should do own backup and copy yours into the same folder.
Into twrp works MTP.
GOOD LUCK FOR ALL.
Click to expand...
Click to collapse
I debloated Stock Nougat before setting up my phone. If I give them my image then they will loose confidence of my steps cause several apps are not present. It is better to take standard update route.
jaffers said:
I debloated Stock Nougat before setting up my phone. If I give them my image then they will loose confidence of my steps cause several apps are not present. It is better to take standard update route.
Click to expand...
Click to collapse
Yes. Now you shouldn't.
Bwangster12 said:
Out of curiosity... why go through this when its "easier" to just root and flash DU or LineageOS? Is the "stock" nougat running that much more smoothly? Its 7.0 with an old security path right? The latest versions of DU and Lineage are 7.1.2 and have up to date security patches.
Click to expand...
Click to collapse
Stock Nougat is getting August security patch rigth now!
Dual sim
Is it dual sim supportable after updating?
NahuelMS said:
Stock Nougat is getting August security patch rigth now!
Click to expand...
Click to collapse
Blueborne is fixed in September security fix.
jaffers said:
Guys, tired of waiting for Nougat update on my Moto X Pure I took a route and never regretted. I converted my Pure edition to Style RETEU.en and went all the way to Nougat, without any hiccup.. Phone is as smooth as was with Marshmallow version. Below I will describe all the steps for successful update to Nougat. Skipping the details that we all know of. REMEMBER: You do at your own risk and I am not responsible for any of your mistake (Complete each step exactly. They are simple)
9. Download Blur_Version.24.221.5.clark_reteu.reteu.en.EU from dl.prazaar.de. This is MPHS24.107-58-13 update. Copy it to root of Phone memory and reboot to recovery and pick Apply update from SDcard. The update will happen smoothly.
11. Now download and copy Blur_Version.24.221.5.clark_reteu.reteu.en.EU from dl.prazaar.de into root directory of your phone.
Click to expand...
Click to collapse
Hi, downloading the necessary files to upgrade my phone and I see you show the same file to download in steps 9 and 11. Is this file being installed twice?
5. Now using fastboot start flashing components from Official stock ROM of Motorola downloaded from dl.prazaar.de which is XT1572_CLARK_RETEU_6.0.1_MPHS24.107-58-5. This is Android Marshmallow base at 6.0.1. Not to flash components is boot, partition, Modem, fsk and recovery files. Make sure you flash rest of files including all the sparsechunks. Commands can ne found elsewhere on the forum.
Click to expand...
Click to collapse
I completed the steps up to this one. I want to make sure I don't accidentally flash everything.
So noob question, what files do I not fastboot? I know boot and recovery. Appreciate the help.
NON-HLOS.bin
fsg.mbn
BTFM.bin
flashfile.xml
servicefile.xml
slcf_ref_d_default_v.1.0.nvm
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
any possibility to flash custom recorvery/root on android 7? When im flashing recorvery via fastboot it says "permission deined"
nvm im dumb, misswrite a single letter in fastboot
I find this post a bit hard to read.
1). You are not really clear on exactly what to flash. You are close but not precise. If you are going to provide instruction like this you might need to be a bit more granular.
2). You mention the same file twice for both the pre-requisite patch and the nougat update. Are then both one in the same? This doesn't make sense.
I followed these instructions up to step #7. I flashed the following files:
logo.bin
BTFM.bin
fastboot flash bootloader bootloader.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
I left out the following:
boot.img
fsg.mbn
gpt.bin
NON-HLOS.bin
recovery.img
My phone is showing Moto X Style however my build # is MPHS24.107-58-5 and not MM 6.0.1 RETEU.en
System version is reporting 24.221.5.clark_reteu.reteu.en.EU retus
If I try to move forward with the MPHS24.107-58-13 update I get a digital signature error.
jaffers said:
You have not read it completely. I have mentioned download source which is dl.prazaar.de for all the files. Since each file is Stock ROM or blur version and greater than 1GB. What is the purpose to attach them here? The site is well know to carry Style firmware.
Click to expand...
Click to collapse
How to Remove Unlocked Bootloader Warning on Moto X4
Shoutout/Credits to xda member @AvenidaDelGato for the modified logo bin file.
Text Guide.
Make sure adb and fastboot are setup and working.
Donwload and Unzip the modified logo file. Place logo3.bin in platform-tools folders, or whereever you have fastboot and adb.
Navigate to adb/fastboot folder
Windows
Code:
adb devices
Code:
adb reboot bootloader
Code:
fastboot devices
Code:
fastboot flash logo_a logo3.bin
Code:
fastboot flash logo_b logo3.bin
Code:
fastboot reboot
Mac/Linux
Code:
./adb devices
Code:
./adb reboot bootloader
Code:
./fastboot devices
Code:
./fastboot flash logo_a logo3.bin
Code:
./fastboot flash logo_b logo3.bin
Code:
./fastboot reboot
Downloads
Modified Logo.bin zip file - https://forum.xda-developers.com/showpost.php?p=77013516&postcount=4
Mirror of Modified logo.bin zip file - https://mega.nz/#!eYFiVaxT!mpt4RhJDToEcJG4TSpw-CBePLIhd_hm8OjRGTu3egoU
ADB and Fastboot - https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
Motorola Drivers - https://support.motorola.com/us/en/drivers
Thanks, that worked to remove the bootloader unlocked warning screen!
One other thing though is when the phone is first turned on while the Moto M logo is still on the screen (just before the Moto startup animation), a line of yellow console text appears over the Moto M logo that says "Verity mode is set to logging." Is there a way to turn that off? Aside from unlocking the bootloader, flashing the logo3.bin file and installing Magisk Manager from TWRP, my phone/ROM is a completely stock retail XT1900-1 (I didn't even flash TWRP to the recovery partition, I just booted it with fastboot to backup my device and install Magisk).
If anyone can help safely remove that line about verity logging without messing anything up that'd be awesome.
kofruge said:
If anyone can help safely remove that line about verity logging without messing anything up that'd be awesome.
Click to expand...
Click to collapse
I think verity is set to logging is not part of the logo. It's a text message which is coming up for a reason i do not know.
Be careful with this method, when you receive updates via OTA, you will not be able to update them since they will get an error ...
Oh yeah, didn't think of that... Any way to fix OTA installation after flashing this?
kofruge said:
Thanks, that worked to remove the bootloader unlocked warning screen!
One other thing though is when the phone is first turned on while the Moto M logo is still on the screen (just before the Moto startup animation), a line of yellow console text appears over the Moto M logo that says "Verity mode is set to logging." Is there a way to turn that off? Aside from unlocking the bootloader, flashing the logo3.bin file and installing Magisk Manager from TWRP, my phone/ROM is a completely stock retail XT1900-1 (I didn't even flash TWRP to the recovery partition, I just booted it with fastboot to backup my device and install Magisk).
If anyone can help safely remove that line about verity logging without messing anything up that'd be awesome.
Click to expand...
Click to collapse
It worked for me as well on LOS 16, except for the Verity Logging Text, would be nice if we could turn that of too?
Just installed this and it works fine, but is there an Android One version/can one be made? Thanks!
MeowDotEXE said:
Just installed this and it works fine, but is there an Android One version/can one be made? Thanks!
Click to expand...
Click to collapse
https://forum.xda-developers.com/moto-x4/themes/bootlogo-custom-bootlogos-dark-variant-t3832118
is there a way to restore the old logo?
vidra said:
is there a way to restore the old logo?
Click to expand...
Click to collapse
Just fastboot flash the boot logo file part of the factory firmware.
https://forum.xda-developers.com/moto-x4/how-to/guide-how-to-flash-official-factory-t3808348
munchy_cool said:
How to Remove Unlocked Bootloader Warning on Moto X4
Shoutout/Credits to xda member @AvenidaDelGato for the modified logo bin file.
Text Guide.
Make sure adb and fastboot are setup and working.
Donwload and Unzip the modified logo file. Place logo3.bin in platform-tools folders, or whereever you have fastboot and adb.
Navigate to adb/fastboot folder
Windows
Code:
adb devices
Code:
adb reboot bootloader
Code:
fastboot devices
Code:
fastboot flash logo_a logo3.bin
Code:
fastboot flash logo_b logo3.bin
Code:
fastboot reboot
Mac/Linux
Code:
./adb devices
Code:
./adb reboot bootloader
Code:
./fastboot devices
Code:
./fastboot flash logo_a logo3.bin
Code:
./fastboot flash logo_b logo3.bin
Code:
./fastboot reboot
Downloads
Modified Logo.bin zip file - https://forum.xda-developers.com/showpost.php?p=77013516&postcount=4
Mirror of Modified logo.bin zip file - https://mega.nz/#!eYFiVaxT!mpt4RhJDToEcJG4TSpw-CBePLIhd_hm8OjRGTu3egoU
ADB and Fastboot - https://www.xda-developers.com/adb-fastboot-any-directory-windows-linux/
Motorola Drivers - https://support.motorola.com/us/en/drivers
Click to expand...
Click to collapse
I appreciate your work very much! Is it too much to ask for a AndroidOne Boot Logo?
HACK3DANDR0ID said:
I appreciate your work very much! Is it too much to ask for a AndroidOne Boot Logo?
Click to expand...
Click to collapse
No need to quote the OP.
HACK3DANDR0ID said:
I appreciate your work very much! Is it too much to ask for a AndroidOne Boot Logo?
Click to expand...
Click to collapse
i dont make bootlogos
download android one firmware, and flash logo.bin from there
munchy_cool said:
i dont make bootlogos
download android one firmware, and flash logo.bin from there
Click to expand...
Click to collapse
Found what i was looking for thanks
kofruge said:
If anyone can help safely remove that line about verity logging without messing anything up that'd be awesome.
Click to expand...
Click to collapse
wanb1i said:
It worked for me as well on LOS 16, except for the Verity Logging Text, would be nice if we could turn that of too?
Click to expand...
Click to collapse
Flash the attached modified bootloader (unzip first).
Code:
fastboot flash bootloader no-verity-warning-bootloader.img
Found it from a telegram channel. Tested it myself.
Credit @abrfilho
Code:
SHA256SUMs:
b2efd37d2bef4e2de5bcbd7ca3e643a1e1e246d597e6ed4389679d321bebd2f0 no-verity-warning-bootloader.img
fcf3391a13f757d3f998c9b14c5ef40e6084d65b2d0162273d3842e75f972281 no-verity-warning-bootloader.zip
gleenfield97 said:
Flash the attached modified bootloader (unzip first).
Found it from a telegram channel. Tested it myself.
Credit @abrfilho
Click to expand...
Click to collapse
It worked for me, thank you heaps!
gleenfield97 said:
Flash the attached modified bootloader (unzip first).
Found it from a telegram channel. Tested it myself.
Credit @abrfilho
Click to expand...
Click to collapse
I tried this, and bootlooped. I am on stock 9.0 Retail US. Perhaps this is not the right one for my device.
jhedfors said:
I tried this, and bootlooped. I am on stock 9.0 Retail US. Perhaps this is not the right one for my device.
Click to expand...
Click to collapse
Maybe it's not compatible with stock. I'm using Havoc.
The AndroidOne logo.bin if anyone else needs it.
Extracted from stock XT1900-1_PAYTON_FI_9.0_PPW29.69-26_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip.
Md5: e306b8ea948a10ec304ca62ebcd60495
Just a warning: after flash the bootlogo file, it seems this change prevent OTA updates. Some hours ago, i receive the 2019 july security patch update and it fails at 90-95 percent. I make a factory reset and it didn't help. Then I flashed the stock rom and the update install very well.