Related
Hello! I've been trying to flash CWM on my LG Optimus 3D, but, unfortunately, I was unable to. I am currently on a stock ROM (or should I say..stuck ROM)
My device is rooted, USB Debugging is enabled, I tried with ROM Manager and Recovery Flash (both from the Market) as well as two PC application. Here is what I get from the CWM Recovert touch installer:
Code:
#######################################
# #
# With this tool you flash the #
# ClockWorkMod-Recovery-Touch 5.8.1.5 #
# at your LG-P920 Optimus 3D #
# #
# by paki0402 #
#######################################
==== You do this on your own risk!! ====
You want to flash the recovery
and you agree the disclaimer then
choose "Y" to start or "N" to exit!
========================================
Choose Y or N [Y,N]?Y
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
### Start Installation ###
------------------
Start ADB-Server
------------------
* daemon not running. starting it now *
* daemon started successfully *
----------------
Copy Files
----------------
----------------------------
Install CWM-Recovery-Touch
----------------------------
/sdcard/mmcblk0p6.backup: cannot open for write: Read-only file system
/sdcard/recovery.img: cannot open for read: No such file or directory
/sdcard/recovery.img: cannot open for read: No such file or directory
----------------------
Remove Temp-Files
----------------------
rm failed for /sdcard/recovery.img, Permission denied
---------------------
Reboot Device
---------------------
### Installation finished! ###
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Press any key to continue . . .
After so many tries, I went in to ROM Manager (where it tells me there is no available version for my P920 and specified as manually installed 3x+. Now my phone won't start. I press the power button, the LG logo appears for half a second, then it shuts down. Guess I'll have to reflash it with the LG Recovery tool...
Thank you in advance!
Here is a link to a very good tutorial. there are quite a few more on this subject.
http://forum.xda-developers.com/showthread.php?t=2195753
You can substitute your own choice of rom after loading the V28b that updates your phone to 4.0.4 (ICS)
BrreaKer said:
Hello! I've been trying to flash CWM on my LG Optimus 3D, but, unfortunately, I was unable to. I am currently on a stock ROM (or should I say..stuck ROM)
My device is rooted, USB Debugging is enabled, I tried with ROM Manager and Recovery Flash (both from the Market) as well as two PC application. Here is what I get from the CWM Recovert touch installer:
Code:
#######################################
# #
# With this tool you flash the #
# ClockWorkMod-Recovery-Touch 5.8.1.5 #
# at your LG-P920 Optimus 3D #
# #
# by paki0402 #
#######################################
==== You do this on your own risk!! ====
You want to flash the recovery
and you agree the disclaimer then
choose "Y" to start or "N" to exit!
========================================
Choose Y or N [Y,N]?Y
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
### Start Installation ###
------------------
Start ADB-Server
------------------
* daemon not running. starting it now *
* daemon started successfully *
----------------
Copy Files
----------------
----------------------------
Install CWM-Recovery-Touch
----------------------------
/sdcard/mmcblk0p6.backup: cannot open for write: Read-only file system
/sdcard/recovery.img: cannot open for read: No such file or directory
/sdcard/recovery.img: cannot open for read: No such file or directory
----------------------
Remove Temp-Files
----------------------
rm failed for /sdcard/recovery.img, Permission denied
---------------------
Reboot Device
---------------------
### Installation finished! ###
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Press any key to continue . . .
After so many tries, I went in to ROM Manager (where it tells me there is no available version for my P920 and specified as manually installed 3x+. Now my phone won't start. I press the power button, the LG logo appears for half a second, then it shuts down. Guess I'll have to reflash it with the LG Recovery tool...
Thank you in advance!
Click to expand...
Click to collapse
keith210350 said:
Here is a link to a very good tutorial. there are quite a few more on this subject.
http://forum.xda-developers.com/showthread.php?t=2195753
You can substitute your own choice of rom after loading the V28b that updates your phone to 4.0.4 (ICS)
Click to expand...
Click to collapse
Thank you very much, my friend! I shall try to do this. However, I wanted to find a ROM that is below 4.0.4, I already have the stock 4.0.4 installed, and it is really, really slow. I was looking for an older ROM but unfortunately all links are dead..And CyanogenMod seems not to work for me --'
BrreaKer said:
Thank you very much, my friend! I shall try to do this. However, I wanted to find a ROM that is below 4.0.4, I already have the stock 4.0.4 installed, and it is really, really slow. I was looking for an older ROM but unfortunately all links are dead..And CyanogenMod seems not to work for me --'
Click to expand...
Click to collapse
If you do a search on the optimus 3d forum for "downgrade to gingerbread" you will find help to downgrade. A gingerbread (2.3.5) rom can not be used if you do not downgrade from ICS. None of the rom manager type of apps that are available from the play store work with this phone.Only use the methods to install roms using the recommended methods in the optimus 3D forums
If you upgraded to ICS using LG official update tools, many users have had problems after upgrading. Try the method described in my original post and if you are not happy with the results maybe then try a downgrade.
Hi Friends Really XDA it's such amazing world that i learn & solve many many of my problem with it really BIG thanks for those built this arena :good:
----- Today I want to share such amazing thing that will help many of people those who search for Easiest way to root them android phones
and install custom recovery
---- and specially thing for those who want to unlock bootloader on just one click ( Just For Sony Xperia Lovers )
ok let us start :
##First :
One-click Root for many many android phones specially xperia lovers
# E-Root (Require Internet Connection ) : support all sony xperia phones just u want to do enable USB Debugging and plug your phone and hit ROOT
* Download from here ==> http://upfile.mobi/301234
# Root-Genius ( Require Internet Connection ) : if the 1st tool dos't work with other phones try this --- this is really universal toolkit to root any android device
i test it on many many devices such as samsung - lg - sony - htc - lenovo - karbonn - micromax and it's work well :angel:
* Download From here ==> https://www.mediafire.com/?45zrgixrcuqup65
## Easiest To Install Custom Recoveries :
Recovery-Tool: with this APK you can install custom recovery on your smartphone in 5 second
all you want rooted devices and install it and hit the refresh icon on it and then click install recovery you will see online custom recoveries image install it or if your devices dos't have online support find out IMG and flash it via this tool by click on install recovery and search for IMG on your storage that's all
* Download From here ==> https://www.mediafire.com/?73j7q39fwpc349k
## One-click bootloader Unlocker Toolkit ( Just for sony xperia ) :
all you want internet connection -- enable USB Debugging and plug your devices and click unlock and enjoy
* Download From here ==> https://www.mediafire.com/?4d5z4q6ad4xpoen
That's All Hope that i help you
( Sorry For my poor English )
------------------------------------------------------------
Your Thanks enough for me )
Elephone P6000
Phone reviews by @s7yler
Stock ROM (SPFlash):
from elephone servers
from needrom.com
Custom Recovery --- Touch RecoveryCourtesy of @bigrammy, @carliv and @Santhosh MVarious
Latin Paradise(拉丁乐园)(Elephone) on Baidu
P6000 Folder
OTA Updates - direct from elephone
--- both are 404 now ---
12282014 to 31012015
01092015 to 31012015
Other threads and useful sites:
http://forum.xda-developers.com/android/general/elephone-p6000-mtk6732-64-bit-4g-5-2g-t2957425
SP Flash Thread - P6000
4pda thread - translated top post is fairly concise
Check your Mobile Network/Carrier
Please use the other threads/Q&A and the thanks button - to minimise duplicate posts reporting the same issues.
I'd like this thread to be used mainly for bug fixes, tips and tricks. If someone reports a similar problem/fix/bug click the thanks button if you'd like to agree.
Bugs
Android 5.0 'Official' Release
Update Official (V3.3)
Some modifications: #186
Android 5.0 Beta
12-02-15 ROM available on needrom.com
Hardware buttons don't work
Battery doesn't draw charge
Ril related memory leak
No ADB
Android 4.4.4 (V8.4)
Notification light - not breathing when charging
OTG only works with self-powered devices
Battery seems to jump from 100% to ~90% Soon after removing from charger
Screen jumps several pixels (30) on slow scrolling. Android 4.4.4 (V8.3) bugs not present in V8.4Data encryption results in a stalled boot/softbrick
FAQ/Fixes
1. Notification light is not working in V8.4 as it was in V8.3
Try Light Manager from the play store or gravity box (xposed module)
2. Does OTG work?
It seems to work only with a powered USB hub - I've only been able to check a powered external hard-drive which wouldn't connect
3. How do you fix the screen jump issue?
There are several options here:
From @the1024 / zOrgent we have two options 1. Using a chinese tool - and 2. Using a .bat
From elephone we have TpUpgrade.apk (appears to only work with V8.4)
From lidmiloff we have P6000 Bugfixer.apk
4. How do you restore a Stock ROM?
Download a SPFlash ROM from #1; you will need to install MediaTek USB VCOM drivers (if they aren't automatically installed); On the download page select the scatter from the ROM folder; and the page should populate with the various .img's and .bins; if it doesn't then double click on the entry and locate it manually (also useful if you wan to change boot/recovery with SPFlash). Hit download; remove the battery from the phone and connect it to the PC (you can connect the battery again). The connection will be fairly instantaneous (there may be a driver install the first time it's connected); if it doesn't connect then unplug/replug.
More details from @bigrammy found here
5. Battery jump from 100% to 90%.
Haven't really noticed this too much - download an app like Battery Monitor Widget, add widget (Battery monitor widget gauge => Content => Central value => Battery => Battery Current (mA)) which will show you the battery drain/draw and charge until the draw is close to; if not +0mA
6. Is there any touch recovery?
As of now (pre-5.0) there is no touch recovery. The recovery thread on #1 contains various recoveries - most of which boot but none have touch - this seems to be a kernel issue.
Touch recoveries can be found here. These are built for KK.
7. What about Custom ROMs?
Potential Port devices (MT6732/MT6752) and their ROMS
As there are no official sources released; for MT6732 or P6000 then custom ROMs are a no-go for now. Porting ROMs from other devices running on MT6732 (and MT6752); i.e. Ulefone Be Pro for example is theoretically possible but there doesn't appear to be any custom ROMs on these chips that offer anything different than the stock/AOSP(almost) that we have already. As other devices get released possibly running MIUI or ColorOS then Custom ROMs may be possible.
FlymeOS
8. How do you take a screenshot?
Natively pressing Volume down and power together for 1 second will take a screenshot - it may take a while to get used to - if volume mixer appears then they were too slow and need to wait for it to disappear. Over adb/terminal you can make use of screencap and screen record
9. How do you back up EVERYTHING(except preloader)?
In SPFlash Tools => readback from 0x00 to 0x3a3e000000
This is a fairly quick way to make sure you have a copy of all the partitions on the device; it will create a 14GB+ file containing all the partitions. You will need to break this block up (manually for the moment) into it's constituent parts if you want to use it to restore - using a Hex-editor (HxD for example) and a copy of the matching /proc/partinfo file and/or scatter.txt
The essential partitions to backup for a fully running device are - boot, (recovery), system, (cache) and data which can all be backed up using a custom recovery. The one other partition needed is nvram - this can be backed up with SPFlash (look at /proc/partinfo) or with dd commands. The nvram partition will only be needed to be restored if you Format All with SPFlash. If you don't have a backup you can restore/recreate the IMEI files that it contains.
10. How do you backup/restore IMEI?
Several options here:
1. MTKDroid
2. Backup NVFLASH partition via readback in SPFlash Tools (look at the scatter.txt) to restore you need to modify the scatter.txt to give the nvflash a file_name: and change it from is_Download: false to is_Download: true
3. From elephone there's a IMEI coding tool
4. Keep a copy of the /data/nvram folder
5. Create new imei files to add to nvram folder/partition with imei.exe
6. Chamelephon app from the play store
7. MTK Engineering Mode
11. Adb access with 5.0 Beta ROMs
1. Use KingoRoot
2. Add the Mediatek subsystem id (0x0e8d) to adb_usb.ini
12. Any Stock Camera fixes?
For KK-4.4.4 from @z0rgent at 4pda
FAQ/Fixes Continued
Android 5.0 V1; V1.1; V2.2 (V3.2); V3.3 #125 #186These versions seem to have gapps preinstalled and are prerooted - for everything else have a look at the 5.0 Betas section below
5.0 Modifications #186Android 5.0 Beta1 Beta2 Beta3
To gain adb access
Linux/Windows - need to add the Mediatek subsystem id (0x0e8d) to adb_usb.ini
Linux: ~/.android/adb_usb.ini
Windows: C:/Users/${Username}/.android/adb_usb.iniKingoRoot It won't root the device however - I believe this is due to it installing a 32bit su binary rather than a 64bit one.
Root
For root install SuperSU v2.11+
Confirmation
Custom Recovery
Recovery from @carliv - from #1; modded to boot on L (basically just the cmdline changed / initrd.gz from stock L recovery replaced with carliv's built CWM).
Carliv Port by hanuma50 on 4pda (hopefully all his work and not partially stolen to take credit)
This recovery seems to only work when the Lollipop Beta ROM is installed.
Gapps
64-bit gapps made for the Nexus 9.
My phone seems to be running a little hot after installing the gapps - but that might just all the cores kicking in.
Mirrored copy of the version I'm using.
(OP's thread has updated them and removed the previous version)
Busybox
64-bit busybox installation
Removing encrypted data (temporarily)
In recovery while in an adb shell: /sbin/make_ext4fs /dev/block/mmcblk0p19
This will allow you to restore backed up data - but it will get re-encrypted on first boot, I'll take a look at removing encryption when I get the chance - should be either secro partition or something in the boot.img
Android 5.0 Beta Breakdown
Screenshots to come later.
Entering LKVOL UP and POWER (this no longer enters recovery)
From lk menu: entering fastboot mode and normal boot works.
Entering recovery (stock) doesn't work and I can't tell if the other normal boot options do anything differentCharging batteryFlashing a custom recovery should allow you some way to charge the batteryI haven't yet been able to install/boot any recovery. Flashing lk and boot from 4.4.4 (I took them from the 48MB OTA) seems to let you charge when powered off. ConfirmedRIL Memory leakThere seems to be a RIL/Sim related memory leak leading to random reboots - for testing purposes disable the sim card(s) or enter airplane mode
I could be wrong about the RIL and the ROM just needed time to settle; all I can say is I had reboots until I switched to airplane modeIMEIIMEI was lost but that would be due to formatted flash memory (wiped nvflash partition) - it's a good idea to keep a backup regardless.Antutu Scores64-bit Antutu Scores are around 28000
32-bit Scores are around 27000
Data-encrypted 4.4.4 Antutu scores are also around 28000SensorsBacklight, sound ... can't be changed
Brightness can be fixed in MTK Engineering Mode #5ROM is not rooted; does not have gapps installed and data is encrypted.
TL;DR The issues with the 5.0 Beta ROM, are primarily not ROM related but kernel related, they have bumped the kernel version up to 3.10.61+, and the issues that need correcting are the various kernel modules (power,sensors).
Android L kernel config
Annotated /system/build.prop
Stripped top of build.prop (build properties) due to size
# begin mediatek build properties
ro.mediatek.version.release=ALPS.KK2.MP13.V1.27
ro.mediatek.platform=MT6752
ro.mediatek.chip_ver=S01
ro.mediatek.version.branch=KK2.MP13
ro.mediatek.version.sdk=3
# end mediatek build properties
#
# from out/target/product/k01q_e/obj/CUSTGEN/config/system.prop
#
#
# system.prop for generic sdk
#
rild.libpath=/system/lib/mtk-ril.so
rild.libargs=-d /dev/ttyC0
# MTK, Infinity, 20090720 {
wifi.interface=wlan0
# MTK, Infinity, 20090720 }
# MTK, mtk03034, 20101210 {
ro.mediatek.wlan.wsc=1
# MTK, mtk03034 20101210}
# MTK, mtk03034, 20110318 {
ro.mediatek.wlan.p2p=1
# MTK, mtk03034 20110318}
# MTK, mtk03034, 20101213 {
mediatek.wlan.ctia=0
# MTK, mtk03034 20101213}
#
wifi.tethering.interface=ap0
#
ro.opengles.version=196608
wifi.direct.interface=p2p0
# dalvik.vm.heapgrowthlimit=256m
# dalvik.vm.heapsize=512m
# USB MTP WHQL
ro.sys.usb.mtp.whql.enable=0
# Power off opt in IPO
sys.ipo.pwrdncap=2
# Switching Menu of Mass storage and MTP
ro.sys.usb.storage.type=mtp #### adding ,massstorage to this gives an additional USB option but it apears to still mount as a media device (MTP) adding ,mass_storage will let you mount the microsd card
# USB BICR function
ro.sys.usb.bicr=no #### changing to yes will allow you to mount /system/mobile_toolkit/iAmCdRom.iso to PC via USB ####
# USB Charge only function
ro.sys.usb.charging.only=yes
# audio
ro.camera.sound.forced=0
ro.audio.silent=0
ro.zygote.preload.enable=0
#
# ADDITIONAL_BUILD_PROPERTIES
#
persist.gemini.sim_num=2
ro.gemini.smart_sim_switch=false
ro.gemini.smart_3g_switch=0
ro.gemini.sim_switch_policy=1
ril.specific.sm_cause=0
bgw.current3gband=0
ril.external.md=0
ro.btstack=blueangel
ro.sf.hwrotation=0
ril.current.share_modem=2
curlockscreen=1
ro.mediatek.gemini_support=true
persist.radio.fd.counter=15
persist.radio.fd.off.counter=5
persist.radio.fd.r8.counter=15
persist.radio.fd.off.r8.counter=5
persist.radio.fd.on.only.r8.network=0
drm.service.enabled=true
fmradio.driver.enable=1
ril.first.md=1
ril.flightmode.poweroffMD=1
ril.telephony.mode=0
dalvik.vm.mtk-stack-trace-file=/data/anr/mtk_traces.txt
persist.mtk.anr.mechanism=1
mediatek.wlan.chip=CONSYS_MT6752
mediatek.wlan.module.postfix=_consys_mt6752
ril.radiooff.poweroffMD=0
ro.config.notification_sound=Proxima.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.config.ringtone=Backroad.ogg
persist.mtk.wcn.combo.chipid=-1
ter.service.enable=0
mediatek.extmd.usbport=0
ro.lte.dc.support=0
ril.active.md=0
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=4.4.4
ro.com.google.clientidbase=alps-k01q_e-{country}
ro.com.google.clientidbase.ms=alps-k01q_e-{country}
ro.com.google.clientidbase.yt=alps-k01q_e-{country}
ro.com.google.clientidbase.am=alps-k01q_e-{country}
ro.com.google.clientidbase.gmm=alps-k01q_e-{country}
wfd.dummy.enable=1
persist.sys.dalvik.vm.lib=libdvm.so #### Charnging this to libart.so appears to have no effect ####
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
# begin fota properties
ro.fota.platform=MTK6732_KK
ro.fota.type=phone
ro.fota.oem=new-bund6732_KK
ro.fota.device=k01q_e
ro.fota.version=eng.jenkins.1422677980
# end fota properties
ro.sf.lcd_density=190
#### Stock value I believe is 320; changing to >190 switches the device to phablet mode; this spoofs the screen size to be 7.73 inches (CPU-Z) enabling tablet apps in the apps store after clearing play store app data ####
qemu.hw.mainkeys=0
#### This enables softkeys ####
Annotated /custom/customprop/custom.prop
ro.product.model=Elephone P6000
ro.product.name=Elephone P6000
ro.product.brand=elephone
ro.product.manufacturer=elephone
ro.bt.name=P6000
ro.wifi.name=P6000
ro.notification.breath=yes #### This seems to not be working with V8.4 ####
ro.build.display.id=ALPS.KK2.MP13.V1.27
ro.internal.build.version=K01Q-E.ELEPHONE.vR83.E4.150109
ro.custom.build.version=Elephone_P6000_V8.4_20150109
ro.fota.device=Elephone_P6000
ro.fota.version=Elephone_P6000_V8.4_20150109202612
MTK Engineering Mode
*#*#3646633#*#* (*#*#ENGMODE#*#*)
What can be done in engineering mode
General non-specific guide
Backlight
Hardware ===> LCM ===> LCM Cycle ===> add a value between 5 and 55 ===> Hit Set.
(On L at least this value will jump to value in the millions/billions; unsure if this has any implications)
Audio
http://forum.xda-developers.com/showthread.php?t=2746861
http://forum.xda-developers.com/showthread.php?t=2248396
GPS
http://www.cnx-software.com/2013/11...ps-lock-on-mediatek-mt65xx-based-smartphones/
Orientation / GSensor
Hardware Testing ===> Sensor ===> Sensor Calibration ===> GSensor Calibration ===> Do Calibration (20% tolerance)
IMEI Restore
Command should be AT +...
Xposed Installer (or WSM Tools)
I've had no problems with any xposed modules.
You will get a warning regarding AliyunOS -
this issue is reported due to the presence of /system/framework/*.jar.jex files.
You can ignore/move/remove these *.jar.jex files without it causing any (noticable) issue.
I haven't decompiled any apps so I don't know if. jex files are used elsewhere within the ROM (in place of .jar),
so can't comment on whether the stock ROM is indeed an Aliyun OS.
I would advise backing them up so that any future OTA can complete 100%.
Any issues identified with xposed modules will be reported here.
Very Helpful and concise
Nice one bro :good:
Subscribed
Ludmiloff's Screen fix apk version 1.2 final now works with 8.3 also. Just wanted to give you a quick update so you edit your post HypoTurtle
greekfragma said:
Ludmiloff's Screen fix apk version 1.2 final now works with 8.3 also. Just wanted to give you a quick update so you edit your post HypoTurtle
Click to expand...
Click to collapse
Still doesn't work for me on 8.3.
Nice one, i get my phone in a couple of weeks.
Hello
and Thanks for all your work ! :victory:
Can you add how save and restore imei ?
xenonism said:
Still doesn't work for me on 8.3.
Click to expand...
Click to collapse
Sorry to hear that man. Can you give more details? Are the driver version letters shown normal or "?"
greekfragma said:
Sorry to hear that man. Can you give more details? Are the driver version letters shown normal or "?"
Click to expand...
Click to collapse
Well, I tried the first methods which came out and they wouldn't work. Then I upgraded to V8.4, at the same time the Elephone APK came out, so I used it and it set the thresholds to 3 and 4. Then I decided to go back to V8.3 and since then, no method managed to make a persistent change to the values (I tried ludmiloff's works, Elephone's APK modified by me, which worked for others, and the old Russian method). At best, I get the new vaules in the "init config" portion of the configuration, never in the "real config" portion, and they are always gone after a reboot. File permissions of /proc/gt9xx_config are 660, owned by root. The config version letter is currently F and ludmiloff's app reads it correctly.
I guess that's all the info I can share.
xenonism said:
Well, I tried the first methods which came out and they wouldn't work. Then I upgraded to V8.4, at the same time the Elephone APK came out, so I used it and it set the thresholds to 3 and 4. Then I decided to go back to V8.3 and since then, no method managed to make a persistent change to the values (I tried ludmiloff's works, Elephone's APK modified by me, which worked for others, and the old Russian method). At best, I get the new vaules in the "init config" portion of the configuration, never in the "real config" portion, and they are always gone after a reboot. File permissions of /proc/gt9xx_config are 660, owned by root. The config version letter is currently F and ludmiloff's app reads it correctly.
I guess that's all the info I can share.
Click to expand...
Click to collapse
Well, time to get in here, I guess...
@xenonism, the best I could tell you is to start over with clean ROM, preferably the one listed at 4pda.ru thread about elephone P6000 (in the head section) and try again. There must be something messed up in your device. I really believe the config is independent of ROM. The secret is very simple, you must start with new version letter and at offset 184 set correct checksum. How to calculate checksum:
//cal checksum
byte checksum;
for(i=0; i<chip_cfg_len; i++) {
checksum += file_config;
}
file_config[chip_cfg_len] = (~checksum) + 1;
Where chip_cfg_len = 184
Then write the checksum and write 0x01 at offset 185.
I believe you already know where are the theshsold values - at offset 16 and 17.
If you wish, I could send you my hand crafted config, which I was an inspiration for my apk.
Good luck
Err... it looks like I am unable to install a clean ROM, or even to update the existing one. I guess I'll have to sort this issue out before I join back the discusssion.
I have a fully functionalV8.3_20141228 ROM running and carliv's CWM from the 7th of February installed. The phone offers me the OTA update and it downloads a ~23 MB update. When I agree to install it, the phone reboots to CWM and the update fails with the following messages:
E:Invalid command argument
Finding update package...
E:unknown volume for path [/storage/sdcard0/adupsfota/update.zip]
E:Can't mount /storage/sdcard0/adupsfota/update.zip
Installation aborted.
Click to expand...
Click to collapse
If I try to install the same update with ROM Manager, it also fails in CWM with the following message:
-- Installing: [FILENAME SHOWS HERE]
Finding update package...
Opening update package...
Installing update...
Installation aborted.
Click to expand...
Click to collapse
But when I reboot the phone, I get the "Android is upgrading...] Screen, saying it's optimizing 124 apps. I believe no actual update takes place, though.
And here's what I'd consider the relevant portion of the recovery.log file:
Preparing to install ROM...
about to run program [/cache/dowipedalvikcache.sh] with 1 args
mount: mounting /dev/block/platform/mtk-msdc.0/by-name/userdata on /data failed: Device or resource busy
mount: mounting /dev/block/platform/mtk-msdc.0/by-name/cache on /cache failed: Device or resource busy
mount: can't find /sd-ext in /etc/fstab
umount: can't umount /sd-ext: Invalid argument
run_program: child exited with status 1
about to run program [/sbin/chmod] with 3 args
about to run program [/tmp/recovery/11-rommanager.sh] with 2 args
mount: mounting /dev/block/platform/mtk-msdc.0/by-name/system on /system failed: Device or resource busy
about to run program [/sbin/umount] with 2 args
Click to expand...
Click to collapse
If I try to install the full 20150109 ROM with ROM Manager, it also fails in CWM, without displaying any meaningful messages in recovery. I also get the "Android is upgrading screen here".
The errors in recovery.log are the same as above.
I guess I could install the full ROM via SP Flash Tool, right?
Also... I have a couple of questions to ask, can I feel free to do it in this thread? Some might be trivial for most.
ludmiloff said:
Well, time to get in here, I guess...
@xenonism, the best I could tell you is to start over with clean ROM, preferably the one listed at 4pda.ru thread about elephone P6000 (in the head section) and try again.
Click to expand...
Click to collapse
@ludmiloff does your app require busybox to be installed?
Downloading from 4pda.ru is a bit hit and miss for me, any chance someone can post the CWMLollipop.img...
Is there any difference in the 4pda.ru ROMs and the ones on needrom.com?
Also found a fix for the backlight in Android L - in engineering mode - not sure if it will do anything useful in 4.4.4 (lower the minimum brightness?).
MTK Engineering Mode => Hardware => LCM => LCM Cycle => value between 5 and 55.
xenonism said:
Err... it looks like I am unable to install a clean ROM, or even to update the existing one. I guess I'll have to sort this issue out before I join back the discusssion.
Click to expand...
Click to collapse
Feel free to elaborate. Edit your previous post with your current setup / what you've tried - so we can turn it into a troubleshooting post.
HypoTurtle said:
Feel free to elaborate. Edit your previous post with your current setup / what you've tried - so we can turn it into a troubleshooting post.
Click to expand...
Click to collapse
Ok, thanks a lot. I will edit my post right now. The thing is... I haven't used an Android phone in 4 years and I did a lot of my tinkering on my P6000 while working or late at night so.. things got a bit messy.
@HypoTurtle,
My app does not require busybox. It simply run some commands in the shell, though.
In fact It is my first experience with android programming and I just followed some examples found here and there. I also wanted to make a Kotlin based app, but then I decided to continue with plain old java. The app might not a perfect one. Hope it worked for many of elephone owners
---------- Post added at 08:05 AM ---------- Previous post was at 07:41 AM ----------
@xenonism, you should try a clean ROM with sp flash tool. It is a bit tricky, I have tried one from needrom and as the author suggested, I did not check the preloader mark. Then my phone ended totally bricked. The ROM from 4pda worked for me. Today I'm going to reflash it again and investigate why my app does not work on it.
@ludmiloff, I ended up installing 20150109 via SP Flash Tool and then updating via OTA to the latest version. Sure enough, your app worked then. And permissions for gt9xx_config are now 666.
I am not particularly happy with the gravitybox solution for the notification issue, so I'm trying to look into it, but I am not really hopeful to achieve something.
xenonism said:
@ludmiloff, I ended up installing 20150109 via SP Flash Tool and then updating via OTA to the latest version. Sure enough, your app worked then. And permissions for gt9xx_config are now 666.
I am not particularly happy with the gravitybox solution for the notification issue, so I'm trying to look into it, but I am not really hopeful to achieve something.
Click to expand...
Click to collapse
Same I did just few minutes ago. Won't install updates and will try to make my app working on this ROM.
BTW. Russian method write a very different format to file /process/gmnodexxxxxxx where xxxxxxx is build date. I'm pretty sure if I could change the file with correct checksum and version letter it should work too.
Anyway, my intent was to fix the scroll after I applied the elephone apk. For sure the Russian method with correct version letter and checksum would work too and it is still the best flow now for phones with very stock ROM. I already explained how to calculate the checksum.
HypoTurtle said:
@ludmiloff does your app require busybox to be installed?
Downloading from 4pda.ru is a bit hit and miss for me, any chance someone can post the CWMLollipop.img..
Click to expand...
Click to collapse
I cant see any CWMLollipop.img there
They only list two recoverys my P6000CWM3.img with no links or credits of course
and carliv's CWM_Modd_2.img again no links or credits
I will be working on the lollipop soon
I am getting another phone very soon to use for daily life so I can use the P6000 for dev only purposes.
[GUIDE] Huawei Y5C | Y541-U02 | Honor Bee : Stock ROMs, ROM Dumping, Root & Flashing
Disclaimer
Upon following this guide, you may or may not achieve same results with others. I am not held responsible for anything unexpected that may happen to your device. Do your research first regarding the areas you do not quite understand. Follow at your own risk.
Prerequisites
Spreadtrum Flash Tool R4.0.0001 (PAC Flashing) or Flashfire (Zip flashing)
SPRD USB Driver (needed for PAC Flashing)
Male to Micro USB Cable (needed for PAC Flashing)
7-Zip
Root with SuperSU (just below, needed for first time Zip flashing)
Packet (*.pac) or Zip ROM (found below)
Rooting
Install and gain root through KingRoot android application.
Restart your phone. (I've encountered a sudden reboot when doing the steps below without this)
Replace KingRoot with SupeSU through this script.
Once the archive is downloaded, extract it. There will be a folder named root where you extract it.
Download and open Terminal Emulator.
Change directory to the root folder that was extracted:
Code:
cd /path/to/root
Then ask for root permissions:
Code:
su
Now run the first script:
Code:
sh level1.sh
Run the second script:
Code:
sh level2.sh
Leave the terminal running and open KingRoot.
Press the button at the upper right corner, and choose general settings.
Scroll down and press uninstall.
Uncheck backup and press OK.
After KingRoot has finished uninstalling, go ahead and uninstall Purify as well.
Go back to the terminal and run the third, last script:
Code:
sh level3.sh
Again leaving the terminal running, install SuperSU and open it.
Let it update the root binary through Normal method, and restart.
Notes:
Currently SuperSU's prompt for applications asking for root permissions does not work, but, changing the setting to "grant" will. Just return it to "deny" afterwards, for security. That's the workaround for now.
Dumping
Before doing anything to your device, it is advised to create a ROM dump/backup beforehand. Also make sure you have a lot of free space on your internal storage.
Open up terminal and gain root permissions:
Code:
su
Then get the partition details:
Code:
ls -al /dev/block/platform/sprd-sdhci.3/by-name
Dump each partition (X) with its name (Y):
Code:
dd =if/dev/block/mmcblk0pX of=/sdcard/Y.img
Do not forget to dump the two bootloaders:
Code:
dd =if/dev/block/mmcblk0boot0 of=/sdcard/splloader.img
Code:
dd =if/dev/block/mmcblk0boot1 of=/sdcard/uboot.img
Flashing
PAC
Extract all the downloaded archives and install the driver (either 32install for 32/86bit or 64install for 64bit OS).
Open the flash tool by double clicking the executable named "ResearchDownload".
Once the flash tool opens, click the single gear button at the top left.
Find and open the PAC ROM.
Press the play button.
Power down the device, hold the volume down button and plug it into the PC.
The flash tool will then recognize the device and start downloading binaries to it.
Once the progress column shows "PASSED", the binary download is finished and the device can now be safely unplugged.
Remove the battery, reinsert, and power the device.
Zip
Gain root if not already done so.
Open Flashfire. (press agree and the other one is up to the user)
Press the red circular button with a plus sign ( + ) on the bottom right, and choose Flash ZIP or OTA.
Find and open the downloaded Zip ROM.
There will be a pop-up for a few settings, leave it as is and press the check icon at the upper right.
Now when the pop-up closes, swipe down and press the Flash button with a lighting icon.
Press OK, and let it flash.
The device will reboot once flashing is finished.
Unbrick Stock PAC ROM
Y541-U02V100R001C567B116
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=HUAWEIY541-U02
ro.build.version.sdk=19
ro.build.version.codename=REL
ro.build.version.release=4.4.2
ro.build.version.security_patch=2016-03-01
ro.build.version.base_os=
ro.build.date=Mon May 23 22:44:32 CST 2016
ro.build.date.utc=1464014672
ro.build.type=user
ro.build.user=
ro.build.host=a7fcf16085c3
ro.build.tags=ota-rel-keys,release-keys
ro.product.model=HUAWEI Y541-U02
ro.product.brand=HUAWEI
ro.product.name=Y541-U02
ro.product.device=HWY541-U
ro.product.board=Y541-U02
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HUAWEI
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=sc8830
# ro.build.product is obsolete; use ro.product.device
ro.build.product=Y541-U02
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=Y541-U02-user 4.4.2 HUAWEIY541-U02 135 ota-rel-keys,release-keys
ro.build.fingerprint=HUAWEI/Y541-U02/HWY541-U:4.4.2/HUAWEIY541-U02/C567B116:user/ota-rel-keys,release-keys
ro.build.characteristics=default
ro.zygote.disable_gl_preload=false
# end build properties
#
# from device/ontim/Y541-U02/system.prop
#
ro.sf.lcd_density=240
ro.sf.lcd_width=54
ro.sf.lcd_height=96
ro.opengles.version=131072
ro.product.hardware=SP7731GEA_V1.0.0
debug.hwui.render_dirty_regions=false
ro.config.hw_showSimName=true
ro.config.hw_hideSimIcon=false
ro.config.coop_stk1comp=com.android.stk1;com.android.stk1.StkLauncherActivity
# Bluetooth OPP low speed for save power
debug.bt.lowspeed=false
persist.ttydev=ttyVUART0
# delay for ConnectivityChange broadcast (ms)
conn.connectivity_change_delay = 0
ro.product.partitionpath=/dev/block/platform/sprd-sdhci.3/by-name/
# Default ecclist
ro.ril.ecclist=112,911,#911,*911
persist.modem.w.enable=1
persist.modem.w.nvp=w
ro.modem.w.dev=/dev/cpw
ro.modem.w.tty=/dev/stty_w
ro.modem.w.eth=seth_w
ro.modem.w.snd=1
ro.modem.w.diag=/dev/slog_w
ro.modem.w.loop=/dev/spipe_w0
ro.modem.w.nv=/dev/spipe_w1
ro.modem.w.assert=/dev/spipe_w2
ro.modem.w.vbc=/dev/spipe_w6
ro.modem.w.id=0
ro.modem.w.fixnv_size=0x40000
ro.modem.w.runnv_size=0x60000
persist.sys.engpc.disable=0
ro.modem.wcn.enable=0
ro.modem.wcn.dev=/dev/cpwcn
ro.modem.wcn.tty=/deiv/stty_wcn
ro.modem.wcn.diag=/dev/slog_wcn
ro.modem.wcn.assert=/dev/spipe_wcn2
ro.modem.wcn.id=1
ro.modem.wcn.count=1
camera.disable_zsl_mode=1
ro.digital.fm.support=1
ro.config.ksm.support=true
#supprot storage path change
ro.storagepath.change.support=true
#supprot quickcamera
ro.quickcamera.support=true
#zram config
ro.config.zram.support=true
ro.board_ram_size=mid
# SPRD: add low cost low memory @{
ro.config.low_ram=true
# @}
#if our product not support drm,set as false
drm.service.enabled=true
# hotspot development
ro.hotspot.enabled=1
# this product does not support bt and softap coexist
ro.btwifisoftap.coexist=true
# SPRD: add support hwrotation
ro.sf.hwrotation=0
#SPRD: add support follow sim system config
persist.support.fssc=1
#SPRD: add for cphs
persist.support.oplpnn=true
persist.support.cphsfirst=false
#SPRD: add support virtualnet
persist.support.virtualnet=true
#ontim:add support huawei wlan setting
persist.huawei.wifi.setting=true
#SPRD: add support encrypt
ro.encrypt.devices.support=0
#SPRD: add support vt
persist.sys.support.vt=false
#SPRD: delete baseband version
ro.show.basebandversion=false
#SPRD: mccmnc config path
ro.mccmnc.info.path=/globalinfo/
#for app can install on sd and primary is internal
ro.storage.installonsd=true
# Audio Dump Information for HAL
audio.dump.show.switch=0
hw-k3-burst-supported=1
# adapter for HuaWei PIN(keyguard apk) added by liulibo
ro.config.is_sprd=true
#avoid gallery function:chang voice pic to video.
ro.config.hw_trans_voiceimage=false
#avoid gallery map function
ro.config.support_gallery_map=false
#wifi_country
ro.config.custCountryEnable=ir,sd,sy,kr
# SPRD: DC lowpower
sys.dc.lowpower=true
ro.systemui.flashlight.timeout=0
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.build.version.incremental=C567B116
ro.product.sw.internal.version=Y541-U02V100R001C567B116_user_30323_160523.223910
ro.product.sw.external.version=Y541-U02V100R001C567B116
ro.build.cust.id=Y541-U02V100R001C567B116
ro.versioninfo.delivery=MocorDroid4.4_TShark28_2341A_W15.16.5
ro.com.android.dateformat=MM-dd-yyyy
ro.carrier=unknown
persist.sys.sprd.modemreset=1
ro.adb.secure=1
persist.sys.sprd.wcnreset=1
ro.xtsdisableverify=1
ro.storage.flash_type=2
keyguard.no_require_sim=true
ro.com.android.dataroaming=false
ro.msms.phone_count=2
persist.msms.phone_count=2
persist.msms.phone_default=0
ro.modem.w.count=2
persist.sys.support.vt=false
sys.usb.gser.count=4
lmk.autocalc=false
persist.sys.data_reserved=100
ro.config.ringtone=Huawei_Tune.ogg
ro.config.ringtone0=Huawei_Tune.ogg
ro.config.ringtone1=Huawei_Tune_Piano.ogg
ro.config.notification_sound=Bongo.ogg
ro.config.alarm_alert=Creamy.ogg
persist.sys.wakeup.enable=0
ro.config.hw_timeformat=true
ro.config.timeformat=24
persist.sys.modem.diag=,none
persist.sys.slog=0
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=96m
dalvik.vm.heapsize=256m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=8m
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=4.4_r7
ro.build.display.id=Y541-U02V100R001C567B116
ro.config.max_starting_bg=3
ro.com.google.clientidbase=android-huawei
ro.com.google.clientidbase.yt=android-huawei
ro.com.google.clientidbase.am=android-huawei
ro.com.google.clientidbase.gmm=android-huawei
ro.com.google.clientidbase.ms=android-huawei
ro.dual.sim.phone=true
ro.config.hw_coop_no_setting=true
ro.config.remove_subscribe_menu=1
ro.config.hw_coop.ontim=true
ro.config.hw_coop.show_Sun=1
ro.config.app_big_icon_size=90
ro.config.hwcust_drawbgicon=false
ro.config.hw_coop_delay=true
ro.config.hwtheme=1
persist.radio.langu.rule=0
data.icon.onlyconnected=true
persist.sys.certification=103323
ro.config.is_support_my=true
ro.product.hwinternal.version=Y541-U02V100R001C567B116
ro.product.hwinternal.ver.time=160523.223910
persist.sys.dalvik.vm.lib=libdvm.so
net.bt.name=Android
ro.floatkey.show=false
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Notes:
These ROMs are repacked and tested first before being posted, so if one of these does not work, try another. If none worked, just wait, others will share a new partition dump.
These ROMs do not contain a system, custom and cache dump because these are for unbricking for now. Prerooted full repacks are coming soon.
Stock ZIPs
Notes:
As the device refuses any custom or modified stock binaries, Flashfire is the only way to go to install zips.
These are pre-rooted, deodexed, zipaligned, de-bloated, and of course tested.
None at the moment.
Troubleshooting
If the flash tool fails to download, either the downloaded ROM is incompatible with the device, or the cable is loose.
If the device shows a white screen but the booting sound is heard, try another one.
Support
If anyone happens to have the same device model in fully working condition but seems to be different, kindly make a partition dump of it and PM the link, so it can be processed and uploaded here.
Credits & Sources
@najoor for the original KingRoot to SuperSU script.
GSM Flashfile Website
@Kingxteam for KingRoot
@Chainfire for SuperSU & Flashfire
Is there any customs available for this device
anil kalyan said:
Is there any customs available for this device
Click to expand...
Click to collapse
As of now, with the bootloader locked, there is none.
In future can we expect the same..........
The closest we can get is a modified stock. In the future, there might, but let us not get our hopes up.
techyzen101 said:
The closest we can get is a modified stock. In the future, there might, but let us not get our hopes up.
Click to expand...
Click to collapse
When can we expect this
Where we are on this Can we expect Lollipop rom anytime
Please provide the lollipop ROM
after flash check download state, last download maybe not complete.
Does anyone have a full file or link .pac file Y541-U02V100R001C567B116 ~ 1.5Gb
Y541-U02V100R001C567B112
I need This version pac file help plz
snmobilecenter said:
after flash check download state, last download maybe not complete.
Click to expand...
Click to collapse
hello can i ask if what can be done when you encouter this error upon power on?
tried flashing with research download and upgrade downgrade tool from spdflashtools.
got it to flash firmware v105. but after flashing, blank screen won't power on. also cannot go to recovery.
tried to flash it again with different version, did not go thru anymore and cannot go through any firmware versions.
stuck at FDL2 failing.
tried android usb drivers and spd /sci drivers still stuck at fdl2
please help.
how to get twrp?
Hello guys, welcome again to my thread
this thread will be my tutorial too for reminder how to reinstalling my Nubia Red Magic 3
i will tell you how to do step by step guide how to do clean Install :
Requirement :
- ADB installed, check with command
Bash:
adb devices
Download all needed first :
First download ROM here V3.34 : http://romdownload.nubia.com/红魔3/V3.34/NX629J-update.zip
// android 11 is not stable yet, there is a lot of function like gyro and other sensor that not working
After that download TWRP here, https://forum.xda-developers.com/t/...twrp-for-nubia-red-magic-3-3s-stable.3962482/
then download Magisk APK : https://magiskmanager.com/
create a zip file from Magisk.apk -> Magisk.zip, we need both of them
then download NIK GAPPS NikGapps-core-arm64-10-20210424-signed.zip and nikgapps config, https://sourceforge.net/projects/nikgapps/files/
download nik gapps, Releases > 23 April 2021 > NikGapps-full-arm64-10-20210423-signed.zip > https://sourceforge.net/projects/ni...ps-full-arm64-10-20210423-signed.zip/download
download nik gapps config, Relaases > Config > nikgapps.config > https://sourceforge.net/projects/nikgapps/files/Releases/Config/nikgapps-config/
After download, do this carefully step by step :
Bash:
# go to download folder
cd ~/Downloads
# now on android, Settings > About Phone > click Build Number 5 times
# go to developer options with usb debugging enable
# Settings > Advanced Settings > Developers Option > Enable toggle USB Debugging > Enable toggle OEM Unlocking
# push ROM file to adb
adb push NX629J-update.zip /storage/emulated/0/
# after push go to your android,
# go to Settings > System Update > pick "..." 3 dot on top right corner > Local Update
# then install Choose from local and pick NX629J-update.zip
# Install
# now on android, after all ROM installed successful do unlock developer options
# Settings > About Phone > click Build Number 5 times
# go to developer options with usb debugging enable
# Settings > Advanced Settings > Developers Option > Enable toggle USB Debugging > Enable toggle OEM Unlocking
# then reboot to bootloader
adb reboot bootloader
# then do unlock and flash twrp
fastboot devices
fastboot oem nubia_unlock NUBIA_NX629J
fastboot flash recovery twrp-3.3.1-3-NX629J-mauronofrio.img
# and now twrp was installed, reboot with command below
# now we need to clean ROM installing
adb reboot recovery
# now on android, you can see twrp menu
# go to Wipe > Advanced Wipe > check all of thing in there
# check Dalvik/Art Cache
# check Cache
# check System
# check Vendor
# check Data
# check Internal Storage
# and "Swipe to Wipe" dont do reboot here!!! please dont do
# now push ROM zip again in twrp,
adb push NX629J-update.zip /
# if it cannot mount or said read only file system
# this step if error only !!
adb shell
# you will goin to android sh, run command mount
mount -o rw,remount /
exit
# you will goin to your shell again, do push zip again
adb push NX629J-update.zip /
# after your push now you need to enable read access again on /
adb shell
mount -o ro,remount /
exit
# now on twrp, go to Install > go to / directory, just pick "up a level" until its gone,
# and on / folder you will see NX629J-update.zip,
# and do install on NX629J-update.zip > "swipe to install"
# it will fill data on that we are wiping off
# then push Magisk.zip
adb push Magisk.zip /
# now on twrp, go to Install > go to / directory > install Magisk.zip
# then push
adb push NikGapps-core-arm64-10-20210424-signed.zip /
adb push nikgapps.config /
# now on twrp, go to Install > go to / directory > pick NikGapps-core-arm64-10-20210424-signed.zip
# > "swipe to install" > "wipe dalvik cache/cache"
# reboot to system now
adb reboot
# after you see launcher screen, do install Magisk.apk
adb install Magisk.apk
# popup will be shown on screen, and click "OK"
Now you get clean Install CN ROM with all working feature
- Disable cover detection on Screen
Settings > Lockscreen, Launcher and Theme > Toggle disable "pocket mode"
- Disable Recommeded Application
Settings > Lockscreen, Launcher and Theme > Launcher Setting > Toggle disable ["Fancy Icon", "show the first screen negative", "Recommended Applications"]
Done.
If anything mistakes happen let me know ya.
Not Working :
- Google services Push Notif on Lock Screen, bug hunter @Faonee
[Guide][Stable] How to clean Install CN ROM + TWRP + ROOT + GAPPS on our Nubia Red Magic 3
Hello guys, welcome again to my thread this thread will be my tutorial too for reminder how to reinstalling my Nubia Red Magic 3 i will tell you how to do step by step guide how to do clean Install : Requirement : - ADB installed, check with...
forum.xda-developers.com
Credit :
@Secretcow
[Guide] Unlocking Red Magic 3's Bootloader
Requirements: - To Unlock Bootloader On Nubia Red Magic 3 (NX629J), you will need a computer. - Charge the Nubia Red Magic to at least 50%. - You need a USB cable to connect your phone to PC. (Users reported better luck with usb 2.0 port vs usb...
forum.xda-developers.com
[Guide] Flashing TWRP & Granting Root Access (Magisk Systemless) - Red Magic 3
Use this guide to root for now for global rom: https://forum.xda-developers.com/red-magic-3/how-to/red-magic-3-root-guide-t3933148 Requirements: - Unlocked Bootloader On Nubia Red Magic 3 (NX629J)...
forum.xda-developers.com
Well sure I'm goona do this...well I'm waiting for the new update 红魔3/红魔3S Android R V5.14 coming soon.....
NubiaNinja said:
Well sure I'm goona do this...well I'm waiting for the new update 红魔3/红魔3S Android R V5.14 coming soon.....
Click to expand...
Click to collapse
I am not sure v5.14 is already stable yet, cause if we see v3 and v2, there is a lot of changes until it stable.
And there must plenty degraded performance instead of android 10. Cause I got AnTuTu only 450k on Android R on Rom v5.1x
never00miss said:
I am not sure v5.14 is already stable yet, cause if we see v3 and v2, there is a lot of changes until it stable.
And there must plenty degraded performance instead of android 10. Cause I got AnTuTu only 450k on Android R on Rom v5.1x
Click to expand...
Click to collapse
Yes @never00miss you were are saying right I think I'm only one who think observed feel the best update was of CN V3.34 Android 10 OF R3,but mine was something 3.04/3.09/3.11 OF R3S I can't remember ??but sure it was android 10 bruh ur saying right...review I'm playing pubg mobile for almost 12 hrs continuosly on this update V3.34 played till almost next update comes.With 90fps game mode on fan speed normal I remember I don't feel any issue lagging, shuttering or any kind of fps down and sometimes I recording too my gameplays making short clips of engaging on fights..well no problem BUT only problem I face was Render in game heavy for a bit of moment then I decided I have to upgraded to Android 11 I think so game needed but this is the time I upgraded by OTA means phone update push the new one V5.11 which was failed version of Android 11 full of bugs I used for some days then I can't play pubg mobile not running game launcher malfunctioning screen flickers and many bugs nevermind I make my mind to return back to android 10 well I think I have to put the 3.34 zip to internal storage like simple way of reboot to recovery by inbuilt recovery wipe/data/cache boom I started installing zip lol who knows the Android 11 new policy added anti-rollback...system Lol DEVICE BRICKEDDDDDD!This is Nubia fail! At that moment I knew I f_____up!
Wait for 1-2 week dead phone....since whole Chinese community of Nubia Redmagic3/3S Flooded and crying in Chinese forum then the GOD ENTERS THE CHAT "SCARLETT GLASS" POSTED SOMETHING A RECOVERY TOOL Then the issue solved TWRP flashed since then I rooted checking gsi roms and new updates V5.11 Rebrushed and rightnow I'm on V5.13 but truely I'm saying my honestly review I don't like ANDROID 11 I can't play for long periods maximum 3-4hours pubg heating so much lagging and shuttering occurs! Device heat so much exceed sometimes 50 degrees lol I don't want to lost my precious hands I don't have girlfriend yet! Lol..... I'm afraid to play for long time!
GO FOR V3.34 PEOPLES WHO LOOK.....THIS POST WELL people this is the #Antutu Score of my Android 11 CN V5.13 NUBIA REDMAGIC 3S Well this score is due to SD 855+ I think so so...never mind YOU CAN SEE THE DIFFERENCE SCORE OF R3 AND R3S CPU AN D GPU R3 WINS....
R3S Has more scored but R3 have some stability...so V3.34 wins! Even Chinese forum people confirm V3.34 was best!
note: I can't remember which version I was running on android 10 I forgot 3.04/3.09/3.11??
sorry..on my RM3S but android 10
This works on both version of RM3 right?
NubiaNinja said:
Yes @never00miss you were are saying right I think I'm only one who think observed feel the best update was of CN V3.34 Android 10 OF R3,but mine was something 3.04/3.09/3.11 OF R3S I can't remember ??but sure it was android 10 bruh ur saying right...review I'm playing pubg mobile for almost 12 hrs continuosly on this update V3.34 played till almost next update comes.With 90fps game mode on fan speed normal I remember I don't feel any issue lagging, shuttering or any kind of fps down and sometimes I recording too my gameplays making short clips of engaging on fights..well no problem BUT only problem I face was Render in game heavy for a bit of moment then I decided I have to upgraded to Android 11 I think so game needed but this is the time I upgraded by OTA means phone update push the new one V5.11 which was failed version of Android 11 full of bugs I used for some days then I can't play pubg mobile not running game launcher malfunctioning screen flickers and many bugs nevermind I make my mind to return back to android 10 well I think I have to put the 3.34 zip to internal storage like simple way of reboot to recovery by inbuilt recovery wipe/data/cache boom I started installing zip lol who knows the Android 11 new policy added anti-rollback...system Lol DEVICE BRICKEDDDDDD!This is Nubia fail! At that moment I knew I f_____up!
Wait for 1-2 week dead phone....since whole Chinese community of Nubia Redmagic3/3S Flooded and crying in Chinese forum then the GOD ENTERS THE CHAT "SCARLETT GLASS" POSTED SOMETHING A RECOVERY TOOL Then the issue solved TWRP flashed since then I rooted checking gsi roms and new updates V5.11 Rebrushed and rightnow I'm on V5.13 but truely I'm saying my honestly review I don't like ANDROID 11 I can't play for long periods maximum 3-4hours pubg heating so much lagging and shuttering occurs! Device heat so much exceed sometimes 50 degrees lol I don't want to lost my precious hands I don't have girlfriend yet! Lol..... I'm afraid to play for long time!
GO FOR V3.34 PEOPLES WHO LOOK.....THIS POST WELL people this is the #Antutu Score of my Android 11 CN V5.13 NUBIA REDMAGIC 3S Well this score is due to SD 855+ I think so so...never mind YOU CAN SEE THE DIFFERENCE SCORE OF R3 AND R3S CPU AN D GPU R3 WINS....
R3S Has more scored but R3 have some stability...so V3.34 wins! Even Chinese forum people confirm V3.34 was best!
note: I can't remember which version I was running on android 10 I forgot 3.04/3.09/3.11??
sorry..on my RM3S but android 10
Click to expand...
Click to collapse
No, you got it wrong on AnTuTu version, you are run on v9 AnTuTu that on my device it will get score on 588k, on you are on 536k
You can see the results on my thread, in this thread I am using v5.13
[OVERCLOCK] GPU overclocking | Upgrade your Red Magic 3 to Red Magic 3s | Unleash the Beast
Before do all of this tutorial, Please keep in mind, that if you are dont have basic on Unix System dont do this!! i am buy this device just for gaming only, and i am buy secondhand on 20 April 2021. Goals : for overclock and unleash all inside...
forum.xda-developers.com
Faonee said:
This works on both version of RM3 right?
Click to expand...
Click to collapse
Yup, correct, both RM3 and RM3s works very well
never00miss said:
No, you got it wrong on AnTuTu version, you are run on v9 AnTuTu that on my device it will get score on 588k, on you are on 536k
You can see the results on my thread, in this thread I am using v5.13
[OVERCLOCK] GPU overclocking | Upgrade your Red Magic 3 to Red Magic 3s | Unleash the Beast
Before do all of this tutorial, Please keep in mind, that if you are dont have basic on Unix System dont do this!! i am buy this device just for gaming only, and i am buy secondhand on 20 April 2021. Goals : for overclock and unleash all inside...
forum.xda-developers.com
Yup, correct, both RM3 and RM3s works very well
Click to expand...
Click to collapse
never00miss said:
No, you got it wrong on AnTuTu version, you are run on v9 AnTuTu that on my device it will get score on 588k, on you are on 536k
You can see the results on my thread, in this thread I am using v5.13
[OVERCLOCK] GPU overclocking | Upgrade your Red Magic 3 to Red Magic 3s | Unleash the Beast
Before do all of this tutorial, Please keep in mind, that if you are dont have basic on Unix System dont do this!! i am buy this device just for gaming only, and i am buy secondhand on 20 April 2021. Goals : for overclock and unleash all inside...
forum.xda-developers.com
Yup, correct, both RM3 and RM3s works very well
Click to expand...
Click to collapse
Yes, I looked at the thread carefully but you haven't mentioned that we RM3S users can also apply this method...for overclock well I have to try it first...lol I think that thread is only for RM3 users... Sorry. Yeah V9 Antutu was score is damnn soo good.... Lesss goooo.....
NubiaNinja said:
Yes, I looked at the thread carefully but you haven't mentioned that we RM3S users can also apply this method...for overclock well I have to try it first...lol I think that thread is only for RM3 users... Sorry. Yeah V9 Antutu was score is damnn soo good.... Lesss goooo.....
Click to expand...
Click to collapse
Cause konabess process is unpacking binary on boot.img and re-compiling again, and boot.img it's same on all CN ROM that working on both devices RM3 and RM3s
I've installed everything succesfully. Only one thing thats bugging me that app notification doesn't show up on the lockscreen. I've tried disabling and enabling lockscreen notification but still not showing.
Faonee said:
I've installed everything succesfully. Only one thing thats bugging me that app notification doesn't show up on the lockscreen. I've tried disabling and enabling lockscreen notification but still not showing
Click to expand...
Click to collapse
ZTE have their own SDK for showing push notification info on their lock screen, and not all of apps support this lock screen info and integrate ZTE notification SDK.
So this problem depends on developer of apps, or ZTE must develop to allow all notification showing in locks screen and allow Google play services to show notification on lock Screen, * this is impossible yet cause of china vs us regulations for integrating gapps.
You can go on notification, Settings > Notification and status Bar > Notification Management > System, a lot of apps provided by CN ROM is supported by showing notif on lock screen. But in third party apps is not showing advanced feature to show notif on lock screen
*For reminder who's people is installing CN ROM, google services SDK feature like push notification (fcm) Or anything relate will not supported by apps in CN ROM it self. if you wanna working push notification and supported by system apps, you need to install from ZTE appcenter
never00miss said:
ZTE have their own SDK for showing push notification info on their lock screen, and not all of apps support this lock screen info and integrate ZTE notification SDK.
So this problem depends on developer of apps, or ZTE must develop to allow all notification showing in locks screen and allow Google play services to show notification on lock Screen, * this is impossible yet cause of china vs us regulations for integrating gapps.
You can go on notification, Settings > Notification and status Bar > Notification Management > System, a lot of apps provided by CN ROM is supported by showing notif on lock screen. But in third party apps is not showing advanced feature to show notif on lock screen
*For reminder who's people is installing CN ROM, google services SDK feature like push notification (fcm) Or anything relate will not supported by apps in CN ROM it self. if you wanna working push notification and supported by system apps, you need to install from ZTE appcenter
Click to expand...
Click to collapse
Thanks for the reply. Well that sucks. Need to get used to it somehow Haha.
Can you please write a guide to install android 11? I know it got bugs but I want to try it once atleast
souma_rox said:
Can you please write a guide to install android 11? I know it got bugs but I want to try it once atleast
Click to expand...
Click to collapse
Same as this tutorial "maybe", cause a lot of update on ZTE CN ROM flashable via TWRP.
You just need to change from v3.3x zip to v5.1x zip and flash on TWRP.
And what's said by @mauronofrio that TWRP only works again Chinese bootloader, so its "maybe" possible to flash CN ROM via twrp
Adb comand doesn't work for me.
Amuror3z said:
Adb comand doesn't work for me.
Click to expand...
Click to collapse
whut?? you need to make sure your adb installed well bruh.
Can we use the ok google hotword in the CN rom?
souma_rox said:
Can we use the ok google hotword in the CN rom?
Click to expand...
Click to collapse
You need to install full pack of nikgapps to get google assistant
I'm not sure what I'm doing wrong. I got Magisk to work and I have the rom up and running, but google play store doesn't seem to work. Which version exactly do I need to flash?
hidelater said:
I'm not sure what I'm doing wrong. I got Magisk to work and I have the rom up and running, but google play store doesn't seem to work. Which version exactly do I need to flash?
Click to expand...
Click to collapse
NIK GAPPS NikGapps-core-arm64-10-20210424-signed.zip
heya, nice guide.
just wanted to notify you that if you want to install the 3.34 cn rom / global rom from inside twrp, you might get a zip error.
to fix this, simply delete compatibility.zip from inside the NX629J-update.zip
under linux you can do this simply with "zip -d NX629J-update.zip compatibility.zip".
unpacking/repacking the zip is not advised
edit: seems this is only a thing if you try to flash from android 11 (v5.14) to android 10 (v3.34)
oh and the "adb reboot recovery" command (after flashing twrp) wont work since you are in fastboot mode during that step, "fastboot reboot recovery" might work