Database Info

Flashing a new ROM

Hi All,
Please help I am looking to flash a new rom to my old sgs i9000 I use a i9001 and have no probs but I justt tried to flash Blueberry and I am now stuck in a bootloop?
I have been hunting through i9000 development forum for a rom to flash through Odin but I am struggling, all Roms now come as .zip and I cant seem to find an ODIN MD5 type download to flash?
I am just after something rooted deodexed with a supercharger if poss, a good stable custom rom, any advice would be appreciated.
Save my marriage I haven't told the missus her phone is not working right now, she found the last rom too buggy and asked me to fix her phone, now she has nothing I used FEAMOD to do a wipe on all levels and now I am stuck in a bootloop!!!
Thanks in advance,
Adrian.

adriannharris said:
Hi All,
Please help I am looking to flash a new rom to my old sgs i9000 I use a i9001 and have no probs but I justt tried to flash Blueberry and I am now stuck in a bootloop?
I have been hunting through i9000 development forum for a rom to flash through Odin but I am struggling, all Roms now come as .zip and I cant seem to find an ODIN MD5 type download to flash?
I am just after something rooted deodexed with a supercharger if poss, a good stable custom rom, any advice would be appreciated.
Save my marriage I haven't told the missus her phone is not working right now, she found the last rom too buggy and asked me to fix her phone, now she has nothing I used FEAMOD to do a wipe on all levels and now I am stuck in a bootloop!!!
Thanks in advance,
Adrian.
Click to expand...
Click to collapse
Hi Adrian,
Odin and Heimdall (Linux equivalent, which I prefer because it's open-source) are used to talk Samsung's propietary protocol for phone maintenance. With them, you can flash the device partitions. One of these is /boot which includes the bootloader. For flashing custom ROMs, you need to change a part of the bootloader which is called recovery, and install a custom recovery. The zip files you've seen are flashed from within those custom recoveries. One of the most popular is CWM (ClockWorkMod recovery), but there are many others like AmonRa, TWRP, etc.
If you flashed something in the past, you probably already have a custom recovery installed. With full battery charged and preferably cable connected, power off and power on pressing Volume Up and Home button at the same time of the power button. You'll enter the custom recovery that way.
Now choose a ROM (I like TAJB, which today released v7.1, search for it), and download the zip. You can copy it to the device from within the recovery, via "mount's and storage" -> mount usb. Once copied, go to "Flash Zip from sdcard" to flash. Wipes are usually necessary before flashing (Full wipe, wipe cache, wipe dalvik cache). Note that this ROM, as many others, is not a Samsung stock ROM but a Cyanogemod based one, so this means your device won't talk with Heimdall/Odin anymore. Wich is not bad at all, just a clarification.
And that's it basically. I use TitaniumBackup for recovering my apps to the exact status they were before flashing.
Hope this helped.
Javier

Guide To Flashing
dozz01's Avatar
Junior Member - OP
Thanks Meter 50
Posts: 28
Join Date: Feb 2012
Default (03) How to: Flash a Firmware
I. Preparation
1. Choose and download an IMG (Firmware):
a) StockROM: Cube U9GT 2, Window N90, Visture V2, Easypad 970.
b) CustomROM: XDA (wackym), SlateDroid (s1eepy), SlateDroid (db260179), Moage (磨叽哥), FlashMyAndroid (prox32).
2. If necessary download "RKBatchTool".
3. Extra Driver shouldn't be needed, Win7 will recognize the device -> therefore don't install manually ADB-, or USB-Driver.
4. Charge Tablet to >70%
II. Flash
1. Turn tablet (off) and disconnect every cable and charger.
2. Start on PC "RKBatchTool.exe" and choose under the item "FW Path" an IMG (see I. Preparation).
3. Now press Volume (-) on tablet -> keep pressing and connect at the same time the tablet (upper microUSB port, not OTG) with PC -> as soon as you hear the PC is successfully connected or you see in RKBatchTool under "Connected Devices" a green light, then you can stop pressing Volume (-) and the tablet should be recognized from "RKBatchTool".
4. Click in RKBatchTool "Restore" (not Upgrade) and the flash process should begin; the first-time boot will last longer than normally - you can close RKBatchTool and disconnect the USB cable as soon as the tablet is booted.
good luck
Attached Files
File Type: zip RKBatchTool.zip - [Click for QR Code] (945.6 KB, 928 views)
REPLY Multi-Quote This Message
The Following 5 Users Say Thank You to dozz01 For This Useful Post: [ Click to Expand ]
dozz01 Old
15th March 2012, 09:51 PM
(Last edited by dozz01; 30th March 2012 at 08:25 AM.)
#5
dozz01's Avatar
Junior Member - OP
Thanks Meter 50
Posts: 28
Join Date: Feb 2012
Default (04) How to: Use Moage's ROMs
I. Preparation:
1. Download Moage's ROM and unzip: Link
2. Charge Tablet to >70%
3. Switch tablet (off) and disconnect every cable and charger
II. Flash Moage's ROM:
1. Moage's FlashTools:
a) Moage 4.3.5: Open "MoageRomFlash.exe" and choose how much space for applications you would like to have, don't get confused from chinese you will nevertheless see numbers those are important -> click the number you like most, after this the "MoageRKtool.exe" will start automatically
b) Moage x.x.x: when there is no "MoageRomFlash.exe" then start "MoageRKtool.exe" and go on with step 2.
2. Now press Volume (-) on tablet -> keep pressing and connect at the same time the tablet (upper microUSB port, not OTG) with PC -> as soon as you hear the PC is successfully connected or you see in MoageRKtool "Found RKAndroid...", then you can stop pressing Volume (-) and the tablet should be recognized from "RKBatchTool".
3. In "MoageRKtool" select all items except "Backup" and manually link to those files
=> then click at first "EraseIDB" (red circle), after that: click "Run"(blue circle) -> even when it is in chinese the buttons order will be the same.
4. Wait until the device is booted, then remove USB cable and close FlashTools.
Done.
Extra-Feature:
=> If your tablet wont boot anymore, and you don't want to lose your data and settings, then do this to fix the boot problem:
1. Start "MoageRKtool.exe" and select: "Loader", "Parameter", "Boot" and "System"
2. Click "Run" (don't click EraseIDB). Now it will replace just some important system files and the rest will remain.
REPLY Multi-Quote This Message
The Following 5 Users Say Thank You to dozz01 For This Useful Post: [ Click to Expand ]
dozz01 Old
15th March 2012, 10:17 PM
(Last edited by dozz01; 7th May 2012 at 02:48 PM.)
#6
dozz01's Avatar
Junior Member - OP
Thanks Meter 50
Posts: 28
Join Date: Feb 2012
Default (05) How to: Make Gameloft Games visible/installable
Two ways:
1. Modify manually "build.prop" /System (source):
=> you need to change 3 things:
ro.product.model=GT-P1000
ro.product.device=GT-P1000
ro.product.manufacturer=samsung
2. Exchange the build.prop:
=> download an already modified "build.prop", e.g. source; then rename in "build.prop" and exchange the original "build.prop" in "/System" at tablet -> before that it would be wise to backup the original file
Hint: after changing or switching build.prop clear data from "Google Service Framework" and "Google Play Storage" then reboot
The result will be:
Extra Information: Optimizing build.prop
Please HELP!!!
I recently got a u9gt2 and tried everything in the above guide by Dozz01 on my Windows 7 x64 to be able to load apps as it is recognised as chinese! but am not succeeding beyond rooting....please someone tell me what I am missing...I tried with all the mentioned ROMS...
Thanks and please save me!!!

Help Cube U9GT2
Guys find in my build prop. of Cube U9GT2, please help, i am not able to play gameloft games like asphalt 5,6 & GT
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=IML74K
ro.build.display.id=mw07-eng 4.0.3 IML74K 20120522 test-keys
ro.build.version.incremental=20120522
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=2012年 05月 22日 星期二 16:29:51 CST
ro.build.date.utc=1337675391
ro.build.type=eng
ro.build.user=feng
ro.build.host=ubuntu
ro.build.tags=test-keys
ro.product.model=GT-P1000
ro.product.brand=SAMSUNG
ro.product.name=mw07
ro.product.device=GT-P1000
ro.product.board=crane
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=exDroid
# ro.build.product is obsolete; use ro.product.device
ro.build.product=mw07
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=mw07-eng 4.0.3 IML74K 20120522 test-keys
ro.build.fingerprint=yftech/mw07/mw07:4.0.3/IML74K/20120522:eng/test-keys
ro.build.characteristics=tablet
# end build properties
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.com.android.dateformat=MM-dd-yyyy
ro.config.ringtone=Ring_Synth_04.ogg
ro.config.notification_sound=pixiedust.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
ro.kernel.android.checkjni=0
persist.sys.timezone=Asia/Shanghai
persist.sys.language=zh
persist.sys.country=CN
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
debug.egl.hw=1
ro.display.switch=1
ro.opengles.version=131072
persist.sys.strictmode.visual=0
persist.sys.strictmode.disable=1
hwui.render_dirty_regions=false
ro.yftech.default.fontScale=1300
persist.sys.usb.config=mass_storage,adb
further my win 7 pc does not detect the tab if connected in usb debugging mode... pls help......

Odin odin odin...
Sent from my HTC One X using xda premium

CM9 or CM10 for the Cube U9GT2 ?
Currently I have the Evolution 2.3 on my Cube U9GT2. Is there a functional CM9 or CM10 available for this tablet. I'm trying to get a smoother interace and more reliable internet connection.
Thanks,
bman

[Q]Help & Assistance needed [Laime L2+]

Hi, I have a Laime L2+ MTK6589T Quad core 4.0.3, can't boot in to fastboot, can only reach recovery mode, as it keeps bootlooping, it loads to the boot screen say "Laime" and that's it, which leads me to think a corrupt boot, went ahead and wiped the cached etc. , is there an "update.zip" I can get from somewhere or I'm willing to make it myself as tbh i've had enough of my phones turning in to expensive paperweights
Also when I got the phone it didn't include any form of OTA firmware upgrading & there was no play store, if there's any way to include this that would be helpful.
Sorry for being a pain in the arse and asking so much for a first post :silly:

Anyone???

TheOMFG said:
Anyone???
Click to expand...
Click to collapse
www.needrom.com/download/laime-l2-sc8825-2/
1. download rom
2. download upgrade file
3. go into upgrade application
4. select pac file
Start!
@TheOMFG

techrefresh said:
wwwneedromcom/download/laime-l2-sc8825-2/
1. download rom
2. download upgrade file
3. go into upgrade application
4. select pac file
Start!
@TheOMFG
Click to expand...
Click to collapse
The phone does not boot in to fastboot mode, only recovery is there any way I can apply the rom as an update in recovery mode?, if so do need to compile a zip from what the "Upgrade application" downloaded???
I put the .pac file in and my phone never restarted and by the looks of it, no files were flashed to my device so I pulled all the files from the temp folder that it downloads to, here's what I've got:
boot.img
cache.img
DSP_DM_G2.bin
fdl1.bin
fdl2.bin
laime.bmp
nvitem.bin
recovery.img
SC8800G_sc8825_modem_vlx_6825.bin
SC8825.xml
system_2.img
u-boot.bin
u-boot-spl-16k.bin
userdata.img
vmjaluna_6825.image
WVGA_logo_256_t6_guangxin_180.bmp(1)
Where do I go from here?

????

http://specdevice.com/showspec.php?id=a7cb-ae42-ce49-2af60033c587
KERNEL: Linux version 3.0.8 ([email protected]) (gcc version 4.4.3 (GCC) ) #1 SMP PREEMPT Wed Aug 13 11:51:42 CST 2014
CODENAME: REL
Mainboard: sp8825c2
BRAND: L200
CPU_ABI: armeabi-v7a
CPU_ABI2: armeabi
DEVICE: s9_1602
DISPLAY: T6GUANGXIN1602_4.3L035_CN_140813
FINGERPRINT: T6_6825C_SC2330B_GUANGXIN_4.3_L035_CN_16+2_RC_140813
HARDWARE: sc8825
ID: IML74K
TAGS: test-keys
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=IML74K
ro.build.version.incremental=140
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.date=Wed Aug 13 11:49:03 CST 2014
ro.build.date.utc=1407901743
ro.build.type=user
ro.build.user=jenkins
ro.build.host=relserver1
ro.build.tags=test-keys
ro.build.version.release=4.0.3
ro.product.model=L200
ro.product.brand=L200
ro.product.name=s9_1602
ro.product.device=s9_1602
ro.product.board=sp8825c2
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=L200
ro.wifi.channels=
ro.board.platform=sc8825
# ro.build.product is obsolete; use ro.product.device
ro.build.product=s9_1602
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=s9_1602-user 4.0.3 IML74K 140 test-keys
ro.build.characteristics=default
#-----below add or modified by revo begin------------
ro.product.locale.language=zh
ro.product.locale.region=CN
persist.sys.language=zh
persist.sys.country=CN
ro.macro.pro=t6_1602-guangxin
ro.macro.subpro=t6_1602-guangxin-4.3_l035
ro.device.support.gps=1
ro.device.support.gsensor=true
ro.device.support.psensor=false
ro.device.support.lsensor=false
ro.device.support.msensor=false
ro.device.support.bt=true
ro.device.support.wifi=true
ro.device.support.uplmn=false
ro.device.flashlight=true
ro.device.single_camera=false
ro.sf.hwrotation=0
ro.build.display.id=T6GUANGXIN1602_4.3L035_CN_140813
ro.build.fingerprint=T6_6825C_SC2330B_GUANGXIN_4.3_L035_CN_16+2_RC_140813
ro.sf.lcd_density=240
ro.sf.lcd_width=54
ro.sf.lcd_height=96
ro.config.ringtone0=Backroad.ogg
ro.config.ringtone1=Backroad.ogg
ro.config.notification_sound=pixiedust.ogg
ro.config.alarm_alert=
ro.macro.music_light_style=true
ro.macro.single_signal=yes
universe_ui_support_revo=true
ro.lockscreen.android42=false
ro.lockscreen.four.point=true
ro.macro.androidlogo.jellybean=yes
ro.macro.incall_touch_lock=yes
ro.macro.InCallScreenOffTime=
ro.macro.focus=true
ro.macro.auto_time_zone=no
ro.macro.connectdata=no
ro.macro.default_inputmethod=baidu
ro.macro.is24hour=yes
ro.macro.ip_dail=yes
ro.macro.screen_brightness=b_80
ro.macro.volume_music=d_12
ro.macro.volume_ring_notifi=d_7
ro.macro.volume_alarm=d_5
ro.macro.volume_fm=d_15
ro.macro.screen_timeout=lvl_1
ro.macro.install_no_market=true
ro.macro.font_size=Normal
ro.macro.boot_ani_choose=no
ro.email.default.signature=
ro.macro.status_bar_bg=transparent
ro.macro.status_bar_bg2=part_transparent
ro.macro.status_bar_bg3=
ro.macro.baseband_mtk_type=MTK6589T
ro.macro.baseband_mtk_number=quad_core
ro.macro.showcpuwithbb=
ro.macro.android_version=4.2.1JOP40D
ro.macro.kernel_version=3.4.35-g1f428cc
ro.macro.lockscrn_no_statusbar=yes
persist.sys.timezone=Asia/Shanghai
ro.macro.fake_romsize=
ro.macro.increase_ram=
ro.macro.vibrate_on=yes
ro.macro.accele_rotation=false
dailpad_search_list_custram=
ro.macro.camera_fullscreen=
ro.macro.dtmf_volume=40
ro.macro.custom_logo=
ro.macro.cycle_slip=
ro.macro.simcardnumber=
ro.macro.shutdownanim=
ro.macro.wifi_tether_ssid=
ro.macro.audio_profile=
ro.macro.hide_qsb_bar=yes
ro.macro.haptic_feedback=
ro.macro.native_launcher=
ro.macro.dtmf_tone=
ro.revo.testcase_alert=true
ro.revo.testalert_code=true
ro.revo.dcaf_orientation=false
device.support.dccaf=0
device.support.dvcaf=0
ro.macro.not_show_focustip=
ro.revo.gs_replace_ps=true
ro.revo.gs_replace_ps_value=
ro.revo.call_connection_notify=
ro.revo.exchange.notification=
ro.revo.fakedisplaysize=
ro.revo.useoneincomingsrc=
scroll_quick_switch=
ro.contacts.showstarredonly=
ro.revo.ori_incallscreen=true
ro.macro.statusbar_add_font=
ro.macro.wifi_policy=0
ro.revo.android_calc_style=
ro.revo.homepage=
###---3rd party func property
ro.macro.lqplay_lock=
ro.macro.yl_lock=
ro.sky.browser.support=true
ro.macro.cooee_lock=no
ro.macro.ouxin_switch=
ro.macro.all_apps_button_pos=
ro.macro.ibingo_lock=
ro.macro.yllg_lock=
ro.macro.ringcool=
ro.revo.mcetools=
#-----add or modified by revo end-----------
ro.macro.fake_new_function=
ro.macro.fake_score=
ro.macro.fake_resolution=
ro.macro.fake_camera=
ro.macro.fake_cpu=
ro.macro.fake_cpu_hz=
ro.macro.fake_gpu=
ro.macro.fake_rom=
ro.macro.fake_ram=
ro.macro.fake_pixel=
ro.mocro.single_simcard=
ro.macro.pro_sub=
ro.macro.fake_cpu_model=MTK6589
ro.macro.fake_android_version=
ro.macro.fake_dpi=
ro.macro.fake_freq=
ro.macro.google_ui=
ro.macro.vibrate_last=
ro.macro.vibrate_sleep=
ro.revo.sound_save_path=
ro.revo.sales=
ro.revo.sales_number=
ro.revo.add.reboot.menu=
ro.macro.display_battery=
ro.com.android.dateformat=MM-dd-yyyy
ro.macro.own_wallpaper_lock=
ro.revo.power_save=false
ro.macro.close.dc.sound=no
ro.device.support.vt=0
ro.revo.uui_incallscreen=
ro.macro.sync_wallpaper=
persist.sys.salescount=
persist.sys.sales_num=
persist.sys.sales_time=
ro.macro.yingmai_googleui=
ro.macro.yingmai_zen=
ro.macro.mms_signature=
ro.macro.tracker=
persist.sys.trackerstatus=
persist.sys.trackernum=
persist.sys.trackerpass=
persist.sys.trackerimsi=
ro.macro.statusbardata_mkt=
ro.browser.fontsize=
ro.macro.simcardnozero=
# end build properties
ro.sf.lcd_density=240
ro.sf.lcd_width=54
ro.sf.lcd_height=96
ro.gpu=mali
ro.opengles.version=131072
ro.device.support.mmc=1
hwui.render_dirty_regions=false
ro.hwui.text_cache_width=2048
persist.ttydev=ttyVUART0
#if our product support cmcc feature, then set the value true, else do nothing
ro.wifi.support.cmcc=true
#our sp6825c1 product supports Trout chip
ro.wifi.chip.vender=trout
# Can not install packages if the data space has used more than the following ratio value
ro.datastorage.threshold=85
#if out product surport trout chip, we set this
ro.fm.chip.vendor=trout
#if out product surport trout chip, we set this to support hci rset to power off
ro.bt.trout=true
ro.device.support.vt=0
#if our product support single link version
ro.system.property.singleconn=true
ro.product.hardware=sp8825C2_V1.0.0
#true default, false if bt/wifi should not coexist.
ro.btwifi.coexist=true
#if out product support fastboot feature, set as true
persist.sys.support.fastboot=false
# modify for AMS kill background process
ro.support.amskill=true
#if our product not support bt wifisoftap coexist
ro.btwifisoftap.coexist=false
#
# ADDITIONAL_BUILD_PROPERTIES
#
keyguard.no_require_sim=true
ro.com.android.dataroaming=false
lmk.autocalc=false
ksm.support=false
zram.support=true
zram_for_android.enable=true
persist.sys.service.delay=false
persist.sys.lowmem=16
ro.build.product.lowmem=1
persist.blcr.enable=0
ro.callfirewall.disabled=true
persist.msms.phone_count=2
persist.msms.phone_default=0
persist.sys.lowcost=true
persist.sys.sprd.modemreset=1
persist.sys.kdump.enable=0
dalvik.vm.heapstartsize=3m
dalvik.vm.heapsize=64m
dalvik.vm.heapgrowthlimit=48m
ro.config.ringtone=BeatPlucker.ogg
ro.config.notification_sound=pixiedust.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.logappslow=0
ro.floatkey.show=false
persist.sys.kb.auto=1
device.support.face.smile=0
device.support.pano=0

have you already tried factory reset in cwm and clear cashe/data/dalvik cache? try deleting and reseting everything posible. This might remake partitions and reflash some files that maybe have somehow gone wrong and causing bootloop. Also sometimes apps or combinations of apps can make the phone bootloop. Then wiping dalvik cache can help or factory reset can delete the non-system apps that caused it. Either way, it's worth trying it.
If this didn't fix the problem, try to find somthing with a working laime l2+ and ask him to make an backup in cwm and sent his files to you. You should have a file named "clockworkmod" on your sd-card, check if there's a file named "backup" (if there isn't, just make it), and place the backup file inside this folder. The backup file should be name somthing like "2015-04-24.18.03.57" so just a date, and contain some files like boot.img, .android_secure.vfat, cache.ext4.tar, data.ext4.tar and so on. Then go into recovery and restore this backup.
That's the best I can do for you as I don't know a lot about pushing rom's with pc, don't have a laime l2+ myself and don't know anyone who have one.
Pleas hit thanks, as I took the time to try to help you

P6000 General Thread - Bug fixes, FAQ, general info.

Elephone P6000
Phone reviews by @s7yler
Stock ROM (SPFlash):
from elephone servers
from needrom.com
Custom Recovery --- Touch RecoveryCourtesy of @bigrammy, @carliv and @Santhosh M​Various
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 #186​Android 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.ini​KingoRoot 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 different​Charging batteryFlashing a custom recovery should allow you some way to charge the battery​I 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. Confirmed​RIL 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 mode​IMEIIMEI 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 28000​SensorsBacklight, sound ... can't be changed
Brightness can be fixed in MTK Engineering Mode #5​ROM 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.

Nextbook Ares 8 Stock 5.1.1 Problems

This thread is for Nextbook Ares 8 5.1.1
I don't have this device yet, @Conan1201 has offered to send me one, once I get it, I can begin the process of dumping the tablet, pulling the firmware, root, then TWRP.
What I would like is everyone that has this tablet, to post their build.prop and boot.img for each version they have, I am trying to see what the pattern is that is causing some versions to lose sound yet others don't.
Anyway all posts related to Nextbook Ares 8 5.1.1, should be posted in this thread, helps to keep all related posts in one thread, right now 3 or 4 threads have people posting about Nextbook Ares 8 5.1.1, most of those threads have nothing to due with this tablet.
A lot of people are contacting me, after failed attempt of using @greatbal instructions or backup, I have nothing to due with @greatbal, I did read his thread yesterday downloaded the backup he provided, unpacked it, and see that is for an entirely different device, His backup manufacturer Logitech.
It should be, manufacturer Yifang.
Yifang version is nxm890bap
Logitech version is ebm890bap
They indeed two different tablets, one might be able to port one version to the other, but just trying to use one version over the other would cause problems.
Anyway @greatbal did let people know what version he had, and I believe if you had the same version @greatbal had, you would have been fine, the differences in the hardware/software isn't @greatbal fault.
Update 3-22-2017
I have received the tablet from @Conan1201.
Below is a part of the build.prop, an important part is the last line ro.build.flavor, that was the fix for sound on my tablet.
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.hwversion.id=V3.0.1
ro.ota.version.id=V1.0.2
ro.git.version.id=520cd962040ded28926dfaf6e07385aac0420aca
ro.build.id=LMY47V
ro.build.display.id=V1.0.2.LMY47V.eng.midpublic.20160529.132930
ro.build.version.incremental=eng.midpublic.20160529.132930
ro.build.version.sdk=22
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=5.1.1
ro.build.version.security_patch=2015-11-01
ro.build.version.base_os=
ro.build.date=Sun May 29 13:30:49 EDT 2016
ro.build.date.utc=1464543049
ro.build.type=user
ro.build.user=midpublic
ro.build.host=mid
ro.build.tags=release-keys
ro.product.model=NXA8QC116
ro.product.brand=NextBook
ro.product.name=NXA8QC116
ro.product.device=NXA8QC116
ro.product.manufacturer=Yifang
ro.build.flavor=nxm890bap_e_jj_64-user
Ok, some back ground, I got the tablet today, I work out of town stay in a hotel, my wife brought me the tablet and a small Linux laptop.
Setup tablet, enable usb debugging, reboot to bootloader
adb reboot bootloader
Now unlock bootloader
fastboot oem unlock
the tablet is supposed to reboot into recovery and format itself, it didn't I gave it 3 or 4 minutes.
I manually reboot tablet.
Got boot screen up android down recovery
choosing down, I get boot image error, which means recovery partition is locked, due to oem unlock.
boot into bootloader
fastboot oem lock
now reboot recovery no problem.
so recovery partition is out.
This tablet can have a permanent TWRP recovery, only temp TWRP recovery for now, I pulled system, recovery.img, boot.img, fastboot.img,ESP.img.
I backed doored the device and in doing so lost sound, I was able to recovery sound by examining different boot.img and build.prop there is always a pattern just finding it sometimes is the *****.
The pattern ro.build.flavor
Update 3-23-2017
Ok, I put together a Linux / Windows package to let people backup their tablet, you should do this before you root device or anything else some people lost sound, restoring your backup made by this recovery will fix that.
Code:
This is for LInux
You need to already have your tablet setup with usb debugging enabled.
adb reboot bootloader
sudo ./fastboot oem unlock
sudo ./fastboot format userdata (note this is optional, you will lose everything on internal sdcard.)
sudo ./fastboot format cache
sudo ./fastboot.sh
on tablet volume down until you see RESTART BOOTLOADER
power
sudo ./trigger 4
wait for recovery to load will take several minutes.
do a backup to micro sdcard, don't backup data or cache as nothing is there, back up system recovery boot to micro sdcard
Code:
I am don't use windows much from memory the below should be correct, look over it if something needs to be changed let me know.
Note [user=4821597]@social-design-concepts[/user] has a complete windows version of tethering twrp, you still need my files to switch bootloader, once that is done you can then use [user=4821597]@social-design-concepts[/user] tool, or continue using below instructions.
This is for Windows
You need to already have your tablet setup with usb debugging enabled.
adb reboot bootloader
fastboot oem unlock
fastboot format userdata (note this is optional, you will lose everything on internal sdcard.)
fastboot format cache
fastboot flash ESP esp.img
fastboot flash fastboot droidboot.img
on tablet volume down until you see RESTART BOOTLOADER
power
Note if you are going to use [user=4821597]@social-design-concepts[/user] windows tool use it now, else continue with my instructions.
fastboot flash /tmp/recovery.zip recovery.zip
fastboot flash /tmp/recovery.launcher recovery.launcher
fastboot oem start_partitioning
fastboot flash /system/bin/logcat recovery.trigger.new
fastboot oem stop_partitioning
wait for recovery to load will take several minutes.
do a backup to micro sdcard, don't backup data or cache as nothing is there, back up system recovery boot to micro sdcard
Note [user=4821597]@social-design-concepts[/user] tool listed below, any question on his tool ask in below thread, I have no personal experience, but I know it has helped many windows users.
https://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
Download tethered recovery package
You need to extract to use, set permission on files if needed.
https://www.androidfilehost.com/?fid=457095661767147708
Now that the bootloader has been replaced flashing permanent recovery is possible, I already have permanent recovery on mine.
You all need a few more steps, the first is above backing your tablet up.
Next you need to get familiar with Carliv Image Kitchen for Android - unpack/repack boot-recovery
https://forum.xda-developers.com/android/development/tool-cika-carliv-image-kitchen-android-t3013658
Those backed up boot.img need to be modified, we will get into that later.
credits
@greatbal
5.1 rom backup
@Conan1201
Giving me this tablet
@cellneuron
boot.img, build.prop
@social-design-concepts
recovery.launcher, recovery.trigger.new, recovery.trigger.original
@teamwin
recovery source
 @vampirefo
putting this together

If you had done above and changed bootloaders, you can now install permanent recovery.
fastboot flash recovery TWRP_ARES_8_5.1_recovery.img
use bootloader to boot into recovery
in twrp
Wipe > Format Data
https://www.androidfilehost.com/?fid=529152257862713741
If you have same version as I have here is a flashable rom for it, should be used will above recover.
ro.build.flavor=nxm890bap_e_jj_64-user
to install boot into twrp
Wipe > Format Data
install Ares8_5.1_nxm890bap_e_jj_64.zip
https://www.androidfilehost.com/?fid=745425885120718639

This is 3.1 TWRP for those that want it.
https://www.androidfilehost.com/?fid=817550096634761287

This is one of my build.prop.
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.hwversion.id=V7.0.4
ro.ota.version.id=V3.0.3
ro.git.version.id=bd615d50e1043c67a980a006a6d2d9a9bd8ff687
ro.build.id=LMY47V
ro.build.display.id=V3.0.3.LMY47V.eng.midpublic.20160815.090809
ro.build.version.incremental=eng.midpublic.20160815.090809
ro.build.version.sdk=22
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=5.1.1
ro.build.version.security_patch=2015-11-01
ro.build.version.base_os=
ro.build.date=Mon Aug 15 09:09:05 HKT 2016
ro.build.date.utc=1471223345
ro.build.type=user
ro.build.user=midpublic
ro.build.host=mid
ro.build.tags=release-keys
ro.product.model=NXA8QC116
ro.product.brand=NextBook
ro.product.name=NXA8QC116
ro.product.device=NXA8QC116
ro.product.manufacturer=Yifang
ro.build.flavor=nxm890bap_e_hd_64-user
ro.product.board=baytrail
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=x86
ro.product.cpu.abilist=x86,armeabi-v7a,armeabi
ro.product.cpu.abilist32=x86,armeabi-v7a,armeabi
ro.product.cpu.abilist64=
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=baytrail
# ro.build.product is obsolete; use ro.product.device
ro.build.product=nxm890bap_e_hd
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=nxm890bap_e_hd_64-user 5.1.1 LMY47V eng.midpublic.20160815.090809 release-keys
ro.build.fingerprint=NextBook/NXA8QC116/NXA8QC116:5.1.1/LMY47V/V3.0.0:user/release-keys
ro.build.characteristics=nosdcard,tablet
# end build properties
#
# from device/intel/baytrail/nxm890bap_e_hd/system.prop
#
#
# system.prop
#
ro.intel.screenoff_time=-1
ro.intel.def_brightness=145
ro.intel.homepage_base=http://search1.ereadingsource.com/home?client=KBM-0001&source=browser-home
persist.sys.timezone=America/New_York
ro.intel.need_wizard=1
ro.bool.adddemomode=true
ro.intel.demo_mode=0
ro.mtp.manufacturer=Yifang
ro.mtp.model=NXA8QC116
ro.ota.product.name=nxm890bap_e
ro.product.ota.host=wota.yifangdigital.com:9881
ro.com.google.clientidbase=android-efun
ro.com.google.clientidbase.ms=android-efun
ro.com.google.clientidbase.yt=android-efun
ro.com.google.clientidbase.am=android-efun
ro.com.google.clientidbase.gmm=android-efun
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.streaming.video.drs=true
ro.disablelonglongpress=true
ro.dalvik.vm.isa.arm=x86
ro.enable.native.bridge.exec=1
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=100m
dalvik.vm.heapsize=174m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=8m
ro.com.android.dateformat=MM-dd-yyyy
ro.config.ringtone=Ring_Synth_04.ogg
ro.config.notification_sound=pixiedust.ogg
ro.carrier=wifi-only
ro.config.alarm_alert=Alarm_Classic.ogg
systemui.lfb.enabled=1
drm.service.enabled=true
persist.tel.hot_swap.support=true
ro.opengles.version=196609
ro.sf.lcd_density=160
ro.blankphone_id=1
ro.com.google.clientidbase=android-intel
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=5.1_r3
persist.sys.dalvik.vm.lib.2=libart.so
ro.ril.status.polling.enable=0
dalvik.vm.isa.x86.features=sse4_2,aes_in,popcnt,movbe
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.intel.corp.email=1
---------- Post added at 04:48 PM ---------- Previous post was at 04:23 PM ----------
My second Ares 8 v5.1.1. I still have another one which has flashed Batville without sound. These two also have no sound after flashing Greatbal's recovery.
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.hwversion.id=V5.0.6
ro.ota.version.id=V1.0.6
ro.git.version.id=bd615d50e1043c67a980a006a6d2d9a9bd8ff687
ro.build.id=LMY47V
ro.build.display.id=V1.0.6.LMY47V.eng.midpublic.20160913.102503
ro.build.version.incremental=eng.midpublic.20160913.102503
ro.build.version.sdk=22
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=5.1.1
ro.build.version.security_patch=2015-11-01
ro.build.version.base_os=
ro.build.date=Tue Sep 13 10:26:01 HKT 2016
ro.build.date.utc=1473733561
ro.build.type=user
ro.build.user=midpublic
ro.build.host=mid
ro.build.tags=release-keys
ro.product.model=NXA8QC116
ro.product.brand=NextBook
ro.product.name=NXA8QC116
ro.product.device=NXA8QC116
ro.product.manufacturer=Yifang
ro.build.flavor=nxm890bap_e_jd_64-user
ro.product.board=baytrail
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=x86
ro.product.cpu.abilist=x86,armeabi-v7a,armeabi
ro.product.cpu.abilist32=x86,armeabi-v7a,armeabi
ro.product.cpu.abilist64=
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=baytrail
# ro.build.product is obsolete; use ro.product.device
ro.build.product=nxm890bap_e_jd
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=nxm890bap_e_jd_64-user 5.1.1 LMY47V eng.midpublic.20160913.102503 release-keys
ro.build.fingerprint=NextBook/NXA8QC116/NXA8QC116:5.1.1/LMY47V/V3.0.0:user/release-keys
ro.build.characteristics=nosdcard,tablet
# end build properties
#
# from device/intel/baytrail/nxm890bap_e_jd/system.prop
#
#
# system.prop
#
ro.intel.screenoff_time=-1
ro.intel.def_brightness=145
ro.intel.homepage_base=http://search1.ereadingsource.com/home?client=KBM-0001&source=browser-home
persist.sys.timezone=America/New_York
ro.intel.need_wizard=1
ro.bool.adddemomode=true
ro.intel.demo_mode=0
ro.mtp.manufacturer=Yifang
ro.mtp.model=NXA8QC116
ro.ota.product.name=nxm890bap_e
ro.product.ota.host=wota.yifangdigital.com:9881
ro.com.google.clientidbase=android-efun
ro.com.google.clientidbase.ms=android-efun
ro.com.google.clientidbase.yt=android-efun
ro.com.google.clientidbase.am=android-efun
ro.com.google.clientidbase.gmm=android-efun
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.streaming.video.drs=true
ro.disablelonglongpress=true
ro.dalvik.vm.isa.arm=x86
ro.enable.native.bridge.exec=1
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=100m
dalvik.vm.heapsize=174m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=8m
ro.com.android.dateformat=MM-dd-yyyy
ro.config.ringtone=Ring_Synth_04.ogg
ro.config.notification_sound=pixiedust.ogg
ro.carrier=wifi-only
ro.config.alarm_alert=Alarm_Classic.ogg
systemui.lfb.enabled=1
drm.service.enabled=true
persist.tel.hot_swap.support=true
ro.opengles.version=196609
ro.sf.lcd_density=160
ro.blankphone_id=1
ro.com.google.clientidbase=android-intel
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=5.1_r3
persist.sys.dalvik.vm.lib.2=libart.so
ro.ril.status.polling.enable=0
dalvik.vm.isa.x86.features=sse4_2,aes_in,popcnt,movbe
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.intel.corp.email=1

cellneuron said:
This is one of my build.prop.
Click to expand...
Click to collapse
Thanks I need boot.img for each as well.

vampirefo said:
Thanks I need boot.img for each as well.
Click to expand...
Click to collapse
I only backed up one of them in twrp, which is not img format. How to get it for you? The tablet itself has been flashed Greatbal's boot.img.

cellneuron said:
I only backed up one of them in twrp, which is not img format. How to get it for you? The tablet itself has been flashed Greatbal's boot.img.
Click to expand...
Click to collapse
I already downloaded @greatbal boot.img, I don't need it, so all your tablets have been flashed via @greatbal backup?
the one you backed up with twrp should have backup up your boot.img, it will be called boot.emmc.win.

vampirefo said:
I already downloaded @greatbal boot.img, I don't need it, so all your tablets have been flashed via @greatbal backup?
the one you backed up with twrp should have backup up your boot.img, it will be called boot.emmc.win.
Click to expand...
Click to collapse
This boot is for v1.0.6.

cellneuron said:
This boot is for v1.0.6.
Click to expand...
Click to collapse
Ok, thanks I built a recovery based on this boot.img and 1.0.6 build.prop.
Once I receive the tablet I will pull the build.prop from that tablet to compare with yours, if it's correct or close enough I will then dump the tablet's firmware.

vampirefo said:
Ok, thanks I built a recovery based on this boot.img and 1.0.6 build.prop.
Once I receive the tablet I will pull the build.prop from that tablet to compare with yours, if it's correct or close enough I will then dump the tablet's firmware.
Click to expand...
Click to collapse
That's great. Can't wait. Just keep in mind my boot was pulled by wrong recovery.

cellneuron said:
That's great. Can't wait. Just keep in mind my boot was pulled by wrong recovery.
Click to expand...
Click to collapse
Everything the recovery backed up would be correct and usable, a recovery just backs up.
The recovery doesn't modify the backup in anyway, what ever a recovery backed up is what was on the device.
Sent from my NS-P08A7100 using Tapatalk

Does anyone use Linux? I want to know what happened when using trigger 4?
Has anyone backed up ESP?
Would anyone be willing to back up ESP and upload it?
Sent from my NS-P08A7100 using Tapatalk

I have received the tablet from @Conan1201 , I work out of town, be a couple day before I am able to release anything.
I do have some info, I am posting to OP.

vampirefo said:
I have received the tablet from @Conan1201 , I work out of town, be a couple day before I am able to release anything.
I do have some info, I am posting to OP.
Click to expand...
Click to collapse
Great.

cellneuron said:
Great.
Click to expand...
Click to collapse
The temp recovery is up, if people use it and share their back ups, everyone's tablet will get fixed.
We need a backup of each flavor, restoring the correct flavor, to the correct tablet fixes sound.
The recovery will back up recovery, boot, and system, restoring these on the correct tablet returns tablet to out of box, eg working sound.
We can't trick the tablet, it knows what flavor it originally came with, only restoring the exact flavor fixes the problem.

vampirefo said:
The temp recovery is up, if people use it and share their back ups, everyone's tablet will get fixed.
We need a backup of each flavor, restoring the correct flavor, to the correct tablet fixes sound.
The recovery will back up recovery, boot, and system, restoring these on the correct tablet returns tablet to out of box, eg working sound.
We can't trick the tablet, it knows what flavor it originally came with, only restoring the exact flavor fixes the problem.
Click to expand...
Click to collapse
More people should join. I don't have any virgin nextbook ares 8 now.

Just found the topic. Thanks a lot for working on this.
I got two Ares8 without sound due to the root process. I was able to find another unrooted table and followed the exact steps to backup the boot/recovery/system as in the first post.
However, after shutdown, my unrooted one will no longer boot. It got stuck at the next book logo screen for a few minutes, then reboot to this screen again. I could still get into the boatloader and the stock recovery, but what do I do now?
I also used the backup to restore one of my rooted Ares 8, before realizing this. It also wont even boot.

minmao said:
Just found the topic. Thanks a lot for working on this.
I got two Ares8 without sound due to the root process. I was able to find another unrooted table and followed the exact steps to backup the boot/recovery/system as in the first post.
However, after shutdown, my unrooted one will no longer boot. It got stuck at the next book logo screen for a few minutes, then reboot to this screen again. I could still get into the boatloader and the stock recovery, but what do I do now?
I also used the backup to restore one of my rooted Ares 8, before realizing this. It also wont even boot.
Click to expand...
Click to collapse
Reboot to what screen, I am not following you.
Upload your recovery and boot that you backed up.
They will be called
boot.emmc.win
recovery.emmc.win
Also a flashable rom has been upload for my version see post two, I still need your
boot.emmc.win
recovery.emmc.win
and exact details of what you did.
the boot.img needs to be modified, else it takes a while to boot cause by default the boot.img is force encrypted, in stock recovery do factory rest and in time the tablet will boot, cause it has to encrypt.
Sent from my Life_Max-FL using Tapatalk

Here are the files I backuped following the first post.
Once powered on, it will stay on the nextbook logo screen (also a line of text saying "Powered by android"). After a while, the screen will flash once ( that is hwy I thought it rebooted) then it goes into the stock recovery (the lying down android with the chest open) and I could go into the recovery by pressing power+ volume up.
The other tablet, restored using the backup, is the same situation.

minmao said:
Here are the files I backuped following the first post.
Once powered on, it will stay on the nextbook logo screen (also a line of text saying "Powered by android"). After a while, the screen will flash once ( that is hwy I thought it rebooted) then it goes into the stock recovery (the lying down android with the chest open) and I could go into the recovery by pressing power+ volume up.
The other tablet, restored using the backup, is the same situation.
Click to expand...
Click to collapse
That's not the recovery you gave me recovery.emmc.win.md5 I need recovery.emmc.win
anyway in stock recovery factory reset and you should be fine.

[STOCK][M][ARB01] RS988 11C ROM + Flashable ZIPs + IMGs + KDZ

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Carrier-Free USA LG-RS988 11c​
Thread best viewed in desktop/mobile browser (not XDA app!).
This thread provides multiple methods for installing 11c on the USA RS988. Methods include using LG Bridge, manually flashing a KDZ with LGUP/UPPERCUT or using TWRP to flash a "ROM" zip. Please read the Install Directions and FAQ sections below as well as using the thread search feature before flashing the COMPLETE zip or posting questions in this thread.​
11c Information:
Anti-Rollback Version: 01
Android Version: 6.0.1
Android security patch level: July 1, 2016
Baseband version: MPSS.TH.2.0.c1.4-00010-M8996FAAAANAZM-1.43591.5
Kernel version: 3.18.20
Build date: July 18, 2016
Build number: MMB29M
Stock 11c build.prop: Click button below to view..
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=MMB29M
ro.build.display.id=MMB29M
ro.build.version.incremental=162001557d2e4
ro.build.version.sdk=23
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=6.0.1
ro.build.version.security_patch=2016-07-01
ro.build.version.base_os=
ro.build.date=Mon Jul 18 16:05:30 KST 2016
ro.build.date.utc=1468825530
ro.build.type=user
ro.build.user=jenkins
ro.build.host=LGEACI8R2
ro.build.tags=release-keys
ro.build.flavor=h1_lra_us-user
ro.product.model=RS988
ro.product.brand=lge
ro.product.name=h1_lra_us
ro.product.device=h1
ro.product.board=msm8996
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=arm64-v8a
ro.product.cpu.abilist=arm64-v8a,armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=arm64-v8a
ro.product.manufacturer=LGE
ro.product.locale=en-US
ro.wifi.channels=
ro.board.platform=msm8996
# ro.build.product is obsolete; use ro.product.device
ro.build.product=h1
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=h1_lra_us-user 6.0.1 MMB29M 162001557d2e4 release-keys
ro.build.fingerprint=lge/h1_lra_us/h1:6.0.1/MMB29M/162001557d2e4:user/release-keys
ro.build.characteristics=default
ro.lge.lguiversion=5.0
# end build properties
#
# from device/qcom/msm8996/system.prop
#
#
# system.prop for msm8996
#
#rild.libpath=/system/lib/libreference-ril.so
rild.libpath=/vendor/lib64/libril-qc-qmi-1.so
#rild.libargs=-d /dev/smd0
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
ril.subscription.types=NV,RUIM
DEVICE_PROVISIONED=1
# Start in cdma mode
# TODO: Please DO NOT enable the next line when you merge CAF
#ro.telephony.default_network=10
debug.sf.hw=1
debug.egl.hw=1
debug.gralloc.enable_fb_ubwc=1
dalvik.vm.heapsize=36m
dev.pm.dyn_samplingrate=1
persist.demo.hdmirotationlock=false
#ro.hdmi.enable=true
persist.speaker.prot.enable=true
qcom.hw.aac.encoder=true
#
# system props for the cne module
#
persist.cne.feature=1
#For enable Android XLAT, LGE does not use this property
#system prop for enabling/disabling Android XLAT
#persist.net.doxlat=true
#For enable Android XLAT, LGE does not use this property
#system props for the MM modules
media.stagefright.enable-player=true
media.stagefright.enable-http=true
media.stagefright.enable-aac=true
media.stagefright.enable-qcp=true
media.stagefright.enable-fma2dp=true
media.stagefright.enable-scan=true
mmp.enable.3g2=true
media.aac_51_output_enabled=true
# Enable adaptive playback for secure decoder
mm.enable.sec.smoothstreaming=true
av.debug.disable.pers.cache=true
#185971 is decimal sum of supported parsers in AAL
#37491 is decimal sum of supported codecs in AAL
#codecsPARSER_)AAC AC3 AMR_NB AMR_WB ASF AVI DTS FLV 3GP 3G2 MKV MP2PS MP2TS MP3 OGG QCP WAV FLAC AIFF APE
mm.enable.qcom_parser=1048575
persist.mm.enable.prefetch=true
# Additional i/p buffer in case of encoder DCVS
vidc.enc.dcvs.extra-buff-count=2
# Set default power mode to low power for encoder
vidc.debug.perf.mode=2
#
# system props for the data modules
#
ro.use_data_netmgrd=true
persist.data.netmgrd.qos.enable=true
persist.data.mode=concurrent
#system props for time-services
persist.timed.enable=true
#
# system prop for opengles version
#
# 196608 is decimal for 0x30000 to report version 3.0
# 196609 is decimal for 0x30001 to report version 3.1
ro.opengles.version=196609
# system property for maximum number of HFP client connections
bt.max.hfpclient.connections=1
# System property for cabl
#disable cabl for h1
#ro.qualcomm.cabl=2
ro.qualcomm.cabl=0
#
# System props for telephony
# System prop to turn on CdmaLTEPhone always
# TODO: Please DO NOT enable the next line when you merge CAF
#telephony.lteOnCdmaDevice=1
#Simulate sdcard on /data/media
#
persist.fuse_sdcard=true
#system prop for Bluetooth SOC type
qcom.bluetooth.soc=rome
#system prop for wipower support
ro.bluetooth.wipower=true
#Set this true as ROME which is programmed
#as embedded wipower mode by deafult
ro.bluetooth.emb_wp_mode=true
#
#snapdragon value add features
#
ro.qc.sdk.audio.ssr=false
persist.audio.ssr.3mic=false
##fluencetype can be "fluence" or "fluencepro" or "none"
#ro.qc.sdk.audio.fluencetype move to model/audio_config.mk
#ro.qc.sdk.audio.fluencetype=none
persist.audio.fluence.voicecall=true
persist.audio.fluence.voicerec=false
persist.audio.fluence.speaker=true
#system prop for RmNet Data
persist.rmnet.data.enable=true
persist.data.wda.enable=true
persist.data.df.dl_mode=5
persist.data.df.ul_mode=5
persist.data.df.agg.dl_pkt=10
persist.data.df.agg.dl_size=4096
persist.data.df.mux_count=8
persist.data.df.iwlan_mux=9
persist.data.df.dev_name=rmnet_usb0
#property to enable user to access Google WFD settings
persist.debug.wfd.enable=1
##property to choose between virtual/external wfd display
persist.sys.wfd.virtual=0
#property to enable sde downscale feature for external display
#sdm.debug.downscale_external=1
#property to specify the number of frames to skip before setting hint
sdm.perf_hint_window=50
#disable tunnel encoding
tunnel.audio.encode=false
#Buffer size in kbytes for compress offload playback
audio.offload.buffer.size.kb=32
#Enable offload audio video playback by default
#audio.offload.video=true
#Enable 16 bit PCM offload by default
#audio.offload.pcm.16bit.enable=true
#Enable 24 bit PCM offload by default
audio.offload.pcm.24bit.enable=true
#Enable audio track offload by default
audio.offload.track.enable=true
#Enable music through deep buffer
audio.deep_buffer.media=true
#enable voice path for PCM VoIP by default
#use.voice.path.for.pcm.voip move to model/audio_config.mk
#use.voice.path.for.pcm.voip=true
#Enable multi channel aac through offload
audio.offload.multiaac.enable=true
# system prop for NFC DT
ro.nfc.port=I2C
#enable dsp gapless mode by default
#move to model property setting
#audio.offload.gapless.enabled=true
#enable pbe effects
audio.safx.pbe.enabled=true
#parser input buffer size(256kb) in byte stream mode
audio.parser.ip.buffer.size=262144
#property to enable WFD WL solution
ro.vendor.wl_library=libqti-wl.so
#property for vendor specific library
ro.vendor.gt_library=libqti-gt.so
ro.vendor.at_library=libqti-at.so
sys.games.gt.prof=1
#hwui properties
ro.hwui.texture_cache_size=72
ro.hwui.layer_cache_size=48
ro.hwui.r_buffer_cache_size=8
ro.hwui.path_cache_size=32
ro.hwui.gradient_cache_size=1
ro.hwui.drop_shadow_cache_size=6
ro.hwui.texture_cache_flushrate=0.4
ro.hwui.text_small_cache_width=1024
ro.hwui.text_small_cache_height=1024
ro.hwui.text_large_cache_width=2048
ro.hwui.text_large_cache_height=1024
#Disable property for Dolby ds2
audio.dolby.ds2.enabled=false
#Disable property for hard bypass
audio.dolby.ds2.hardbypass=false
audio.offload.passthrough=false
#move to model property setting
#Enable multi offload by defaul
#audio.offload.multiple.enabled=false
# enable navigation bar
qemu.hw.mainkeys=0
#property to enable VDS WFD solution
persist.hwc.enable_vds=1
#Enable stm events
ro.dbg.coresight.config=stm_events
#property to enable fingerprint
persist.qfp=false
#default pd_enable value
persist.sys.pd_enable=0
#Disable rotator split feature
sdm.debug.disable_rotator_split=1
#Increase cached app limit
#ro.sys.fw.bg_apps_limit=60
# property for oom values
ro.sys.fw.bg_cached_ratio=0.33
ro.sys.fw.mOomAdj1=0
ro.sys.fw.mOomAdj2=1
ro.sys.fw.mOomAdj3=2
ro.sys.fw.mOomAdj4=3
ro.sys.fw.mOomAdj5=9
ro.sys.fw.mOomAdj6=15
ro.sys.fw.mOomMinFree1=73728
ro.sys.fw.mOomMinFree2=92160
ro.sys.fw.mOomMinFree3=110592
ro.sys.fw.mOomMinFree4=129024
ro.sys.fw.mOomMinFree5=225000
ro.sys.fw.mOomMinFree6=325000
# reserved wifi related property
dhcp.ap.macaddress=
dhcp.wlan0.dns1=
dhcp.wlan0.dns2=
dhcp.wlan0.domain=
dhcp.wlan0.gateway=
dhcp.wlan0.ipaddress=
dhcp.wlan0.leasetime=
dhcp.wlan0.mask=
dhcp.wlan0.pid=
dhcp.wlan0.reason=
dhcp.wlan0.result=
dhcp.wlan0.server=
dhcp.wlan0.vendorInfo=
dhcp.p2p.dns1=
dhcp.p2p.gateway=
dhcp.p2p.ipaddress=
dhcp.p2p.leasetime=
dhcp.p2p.mask=
dhcp.p2p.pid=
dhcp.p2p.reason=
dhcp.p2p.result=
dhcp.p2p.server=
dhcp.p2p.vendorInfo=
init.svc.dhcpcd_wlan0=
init.svc.dhcpcd_p2p=
init.svc.p2p_supplicant=
init.svc.wififtmd=
init.svc.iprenew_wlan0=
net.change=
net.dns1=
net.dns2=
wlan.driver.status=
#
# ADDITIONAL_BUILD_PROPERTIES
#
log.tag.GpsLocationProvider=DEBUG
log.tag.LocationManagerService=DEBUG
log.tag.NlpProxy=DEBUG
log.tag.LocSvc_java=DEBUG
log.tag.LgeGpsIndicator=DEBUG
log.tag.GeofenceHardwareImpl=DEBUG
log.tag.GeofenceManager=DEBUG
log.tag.FlpServiceProvider=DEBUG
log.tag.GeofenceProxy=DEBUG
ro.com.lge.mada=gms_3.1
ro.build.target_operator=LRA
ro.build.target_country=US
ro.build.target_operator_ext=USA_OPEN
ro.carrier_code=00
ro.telephony.default_network=10
telephony.lteOnCdmaDevice=1
ro.lge.lcd_default_brightness=156
ro.lge.lcd_auto_brightness_mode=true
persist.sys.store_demo_enabled=0
ro.cdma.home.operator.alpha=
ro.cdma.home.operator.numeric=310000
ro.cdma.otaspnumschema=SELC;3;00;07;80;87;88;99
persist.gsm.sms.disablelog=64
persist.radio.volte.dan_support=true
persist.dpm.feature=0
ro.sys.fw.bg_apps_limit=32
ro.config.max_starting_bg=16
wlan.chip.version=bcm43455
wifi.lge.offloading=true
wifi.lge.aggregation=true
wlan.lge.softap5g=true
wlan.lge.dcf.enable=true
wlan.lge.passpoint_setting=true
persist.data.tethering_oc=1
wifi.lge.sleeppolicy=2
wifi.lge.eapaka.aggregation=true
ro.horizontalVVM=true
android.telephony.apn-restore=1800000
persist.lg.data.isSupportPco=true
persist.lg.data.ims_pco=-1
persist.lg.data.internet_pco=-1
ro.dev.fmode=0
ro.dev.fmode_exif=0
persist.http.gba.auth=false
ro.config.ringtone=00_Life_Is_Good.ogg
ro.config.notification_sound=Crystal.ogg
ro.config.alarm_alert=Life_Is_Good_Alarm.ogg
ro.config.timer_alert=Timer.ogg
ro.config.vc_call_vol_steps=8
ro.config.vc_call_vol_default=6
ro.lge.noise.suppression=1
ro.lge.ns.default=1
persist.audio.nsenabled=ON
lge.normalizer.param=version2.0/false/13/true/8000/1/3000/0.5
ro.sdcrypto.syscall=398
ro.com.google.gmsversion=6.0_r4
ro.setupwizard.mode=DISABLED
ro.com.google.apphider=off
lge.nfc.vendor=nxp
ro.com.google.clientidbase=android-om-lge
ro.com.google.clientidbase.ms=android-om-lge
ro.com.google.clientidbase.yt=android-om-lge
ro.com.google.clientidbase.am=android-om-lge
ro.com.google.clientidbase.gmm=android-om-lge
ro.sf.lcd_density=640
persist.sys.strictmode.disable=true
ro.config.vibrate_type=1
persist.service.crash.enable=0
persist.sys.ssr.restart_level=ALL_ENABLE
ro.lge.adoptable_storage=false
ro.frp.pst=/dev/block/bootdevice/by-name/persistent
ro.lge.hl_mode=1
ro.camera.notify_nfc=1
ro.camera.fake_camera_id=2
persist.debug.sensors.hal=i
debug.qualcomm.sns.daemon=i
debug.qualcomm.sns.libsensor1=e
persist.sensors.mag_filter_size=8
persist.sensors.knock_delay=1000
persist.sensors.wul_multilevel=3
persist.sensors.wul_thresh0=2
persist.sensors.wul_thresh1=10
persist.sensors.wul_thresh2=15
persist.sensors.wul_delay=3000
persist.sensors.onhand.en=0
persist.fp.show_percent=false
persist.radio.apm_sim_not_pwdn=1
persist.audio.voice.clarity=off
persist.audio.handset_rx_type=DEFAULT
ro.qc.sdk.audio.fluencetype=nxp
audio.offload.24bit.enable=1
audio.offload.pcm.enable=true
persist.spkr.cal.duration=0
persist.audio.dual_audio=ON
persist.audio.twin_headset=DISABLE
persist.audio.twin_headset_on=0
ro.config.media_vol_extend=ON
ro.lge.vib_magnitude_index=0,1044,1276,1508,1740,1856,1972,2088
use.voice.path.for.pcm.voip=false
audio.offload.gapless.enabled=true
audio.offload.multiple.enabled=true
audio.offload.video=false
audio.offload.pcm.16bit.enable=false
ro.lge.voice.clarity=1
ro.airplane.phoneapp=1
media.input.fd.disable=true
ro.lge.build.basetag=LAMPMMR1R160127
ro.lge.build.branch=msm8996_m_mr1_h1_lra_us_open_mp_160310
sys.knockon.knockoff.distance=10
ro.lge.audio_soundexception=true
sys.lge.bnrd=0
com.lge.splink_screen_off=0
ro.lge.capp_ZDi_O=true
lge.zdi.actionsend=false
lge.zdi.onactivityresult=true
lge.zdi.dragdropintent=false
drm.service.enabled=true
ro.lge.capp_emotional_led=true
wlan.lge.wifidisplay=both
lge.signed_image=true
persist.service.main.enable=0
persist.service.system.enable=0
persist.service.radio.enable=0
persist.service.events.enable=0
persist.service.kernel.enable=0
persist.service.packet.enable=0
persist.service.storage.low=0
persist.service.power.enable=0
persist.service.memory.enable=0
persist.service.ccaudit.enable=0
persist.service.xfrm.enable=0
ro.afwdata.LGfeatureset=VZWBASE
persist.lg.data.fd=0
persist.lg.data.hvolte_vzw=true
persist.telephony.oosisdc=false
persist.qcril.disable_retry=true
persist.lg.data.llkklk.exact=true
persist.lg.data.fds_prop=0
ro.lge.swversion_arb=
ro.lge.swversion=RS98811c
ro.lge.swversion_short=V11c
ro.lge.swversion_rev=00
ro.lge.factoryversion=LGRS988AT-00-V11c-LRA-US-JUL-18-2016+00
dalvik.vm.heapgrowthlimit=256m
ro.vendor.extension_library=libqti-perfd-client.so
persist.radio.sib16_support=1
persist.radio.custom_ecc=1
af.fast_track_multiplier=1
audio_hal.period_size=192
camera.disable_zsl_mode=1
ro.carrier=unknown
dalvik.vm.heapstartsize=8m
dalvik.vm.heapsize=512m
dalvik.vm.heaptargetutilization=0.25
dalvik.vm.heapminfree=4m
dalvik.vm.heapmaxfree=16m
persist.service.odm_log.noti=true
persist.service.odm_log.svc=true
ro.boot.svelte=1
ro.qcom.ad=1
ro.qcom.ad.sensortype=1
ro.qcom.ad.calib.data=/system/media/display/calib.cfg
persist.sys.highlux.menu_on=0
persist.sys.enable_hardreset=0
ro.lge.has_left_sidekey=true
ro.lge.support_vr=true
vr.perfd.controller.start=0
ro.lge.gons.enable=true
wlan.lge.gons.scan.completed=false
wlan.lge.gons.scan.scanonly=false
persist.service.logger.low=0
wlan.chip.vendor=brcm
wifi.lge.patch=true
wlan.lge.concurrency=MCC
wlan.lge.supportsimaka=yes
wlan.lge.softapwps=true
wifi.lge.common_hotspot=true
wifi.lge.supportp2p5g=full
wlan.lge.traffic.trigger=100
wlan.lge.fastroaming=true
persist.sys.dalvik.vm.lib.2=libart
dalvik.vm.isa.arm64.variant=kryo
dalvik.vm.isa.arm64.features=default
dalvik.vm.isa.arm.variant=cortex-a53
dalvik.vm.isa.arm.features=default
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
persist.gps.qc_nlp_in_use=1
persist.loc.nlp_name=com.qualcomm.location
ro.gps.agps_provider=1
ro.expect.recovery_id=0x991300ac242bea961eb43bb887020e1b9b2fabfb000000000000000000000000
Downloads:
Click button below to view downloads for 11c, RS988 and all G5 variants.
Please do not mirror files!
LG-RS98811c-Flashable.COMPLETE-ARB01.zip
LG-RS98811c-Flashable.Bootloader-ARB01.zip
LG-RS98811c-Flashable.Modem-ARB01.zip
RS98811c_00_ARB01.kdz
Codefire Directories:
G5 IMGs, drivers, KDZs, ZIPs and more can be found in the following directories...
LG-RS98811c | LG-RS988 | LG G5
MD5 Sums:
Click button below to view MD5 for each file...
7be5939eea6a82e6c22752b4c39fba0a ./LG-RS98811c-Flashable.Modem-ARB01.zip
15bc82584049ec3a7c62d921c2897267 ./rct.img
8c22ac9a3bff0cdeaeebd71ba7b888f1 ./apdp.img
436e7fffb4740349b2b5f541aadfdec1 ./hyp.img
4017d136c0008421fe7ce17e7477bfc5 ./pmic.img
9af6d5cc7905db1226a5d3dfe552134c ./LG-RS98811c-Flashable.COMPLETE-ARB01.zip
a4345b4a3cd2efdd860ffb1e997f4136 ./boot.img
9cce6a862d149bb5a1e716832dbdb8c3 ./LG-RS98811c-Flashable.Bootloader-ARB01.zip
75bb01c70746b3e9996e5ac88e9e894a ./tz.img
ce0d9aed64a642870db8622e59f50987 ./recovery.img
0bd81d2534ee21e26536d47cf9bdfded ./modem.img
5c2c3e6332d226adb64ab3fbe2935c2b ./persist.img
55eb4f62ebcf5d0248c2be774b27a428 ./cmnlib.img
a74709295e01e5c2c1f9978cfc87ecd1 ./keymaster.img
a937d853e44401cfc1065761ce8a6058 ./RS98811c_00_ARB01.kdz
15bc82584049ec3a7c62d921c2897267 ./factory.img
592c13d33869f08fa51aadffec2578e9 ./raw_resources.img
ed9ea2a17f9152fc1fdfc96b91cbe4b2 ./xbl.img
ed9ea2a17f9152fc1fdfc96b91cbe4b2 ./xbl2.img
8f65b71ee275bd573f092f3216518044 ./laf.img
e4f8c99d6e29eec7f0104dbf41f7e054 ./rpm.img
2e50861904836762aa0e0f264611a5b3 ./msadp.img
dbc93317b178cf1e8e29839703bad5fe ./aboot.img
ca5113cb6a95aefbf12ad823a728fbfa ./devcfg.img
628756d1475c7e6ffa2f974c63261bf6 ./sec.img
b61bb73d635a8c4458542ffa270551d3 ./cmnlib64.img
Install Directions:
You can install RS988 11c using the following methods...
Using LG Bridge on pc/mac. LG Bridge app downloads the latest available KDZ for your phone then installs it.
Using LGUP + UPPERCUT. You can download the 11c KDZ and manually flash it with LGUP.
Using TWRP to flash my 11c COMPLETE zip. You must flash either SuperSU or Magisk zip after flashing COMPLETE zip for root.
All methods listed above are described in full step by step detail below. Click button below to view...
For no root/100% stock just flash the KDZ. Flash KDZ with either LG Bridge or LGUP.
LG Bridge downloads and flashes the KDZ automatically but can be weird/buggy.
LGUP requires downloading 11c KDZ file yourself but it's pretty simple after that.
If you have TWRP and want to keep it or want root then you'll want the zip files.
LG Bridge Directions:
Click button below to view steps
1. Download/install LG Bridge for Windows or Mac.
2. Launch LG Bridge and connect G5 while it is still booted in Android.
3. LG Bridge will detect and connect to your device then scan for updates. Update if available.
LGUP Directions:
Click button below to view steps
1. Download the following three(3) files on Windows PC (Windows only. Mac/Linux? Use a Windows Virtual Machine):
LGUP
UPPERCUT
Latest LG Windows PC drivers
2. Download KDZ. Install LGUP 1.14 and LG USB drivers if not already installed.
3. Turn OFF device then place in Download Mode: Hold Volume Up while plugging in USB cable.
4. Double-click the UPPERCUT.exe to load LGUP...
How-to use LGUP and flash software:
Select device
Check BIN File box under File Type then select KDZ file
Check "Upgrade" box. Refurbish will not work. To wipe data, boot into stock recovery and do a factory reset.
Click START button to flash file to G5 (you may have to close and reopen LGUP before being able to hit Start)
Install via TWRP Directions:
Click button below to view steps
Below are options for flashing zips in TWRP.
IF YOU FLASH THE COMPLETE ZIP YOU WILL LOSE TWRP UNLESS YOU FLASH A ZIP THAT REPACKS THE BOOT.IMG OR YOU DELETE THE "recovery-from-boot.p" FILE IN /SYSTEM.
ZIPS THAT REPACK THE BOOT.IMG INCLUDE SUPERSU OR MAGISK.
To flash the 11c ZIPs you need TWRP installed.
A. Stock ROOTED.
Click the button below to view steps
1. Download the following two files and place on G5 internal or external SD card.
Have encrypted data and no external sdcard? ADB Sideload in TWRP.
LG-RS98811c-Flashable.COMPLETE-ARB01.zip
Latest SuperSU [BETA] Thanks to Chainfire!
2. (re)Boot into TWRP
3. Install the COMPLETE ZIP and SuperSU ZIP:
LG-RS98811c-Flashable.COMPLETE-ARB01.zip (Install > select zip > swipe to confirm/flash)
SuperSU zip (Install > select zip > swipe to confirm/flash)
OPTIONAL:
You can use Magisk instead of SuperSU.
To be extra safe in making sure TWRP sticks (in case zips don't repack the boot.img or user error) delete the "recovery-from-boot.p" file in the root of /system and TWRP will 100% stick... boot repack or not). You can use the TWRP Mounts button mount system as RW. And use the Advanced button in TWRP to use the file manager to delete the "recovery-from-boot.p" in /system.
After zips finish flashing you can reboot! If TWRP asks if you want to install SU, hit no. If TWRP says No OS installed, ignore it.
B. Stock UNROOTED + Keeping TWRP.
You need the COMPLETE zip + either the no-verity-opt-encrypt.zip OR boot repack zip.
Data unncrypted users: Use no-verity-opt-encrypt.zip. Those keeping data encryption: boot repack zip.
If you don't want TWRP/root and don't want to use a KDZ.. flash the COMPLETE zip by itself.
Click the button below to view steps
1. Download files and place on G5 internal or external SD card.
Have encrypted data and no external sdcard? Use ADB Sideload in TWRP.
LG-RS98811c-Flashable.COMPLETE-ARB01.zip
no-verity-opt-encrypt-4.1.zip.Thanks to @jcadduono!
android-boot-repack.zip. Thanks to @jcadduono!
2. (re)Boot into TWRP
3. Install the COMPLETE ZIP + noverity/bootrepack ZIP:
LG-RS98811c-Flashable.COMPLETE-ARB01.zip (Install > select zip > swipe to confirm/flash)
no-verity-opt-encrypt.zip OR android-boot-repack.zip (Install > select zip > swipe to confirm/flash)
After zips finish flashing you can reboot! If TWRP asks if you want to install SU, hit no. If TWRP says No OS installed, ignore it.
FAQ:
Click button below to view FAQ
Q: Why isn't this ROM pre-rooted? Are there any mods?
A: I leave all modifications up to the user, therefore it is up to the user to decide which root method/zip to use or which mods to flash etc. Simply flash the COMPLETE zip then flash the SuperSU zip right after and you'll have a stock-rooted ROM using SuperSU. Want a debloated stock rom? Users/devs should put together a flashable zip that simply deletes apks and other files from the stock roms.. no need to create a whole new 2GB+ rom zip just because you want a few apks removed. The same is true with many mods... flashable mod zips could be used to make changes to this stock base rom.. a whole new rom isn't needed just because a few APKs were modified.
Q: Why did I lose TWRP after flashing this ROM?
A: Android attempts to remove any installed custom recovery(TWRP) each time you boot into Android. To avoid this you can either modify the boot.img or remove the "recovery-from-boot.p" file which is found in the root of your /system partition. Android is able to build the new stock recovery.img when you boot into Android by using the "recovery-from-boot.p" file inside system. But when the boot.img is modified (using SuperSU for example) Android will no longer try to rebuild a stock recovery.img based off the boot.img. Or you can simply remove the "recovery-from-boot.p" file and Android no longer knows how to rebuild stock recovery.
Q: Anti-Rollback 01? What does this mean?
A: It means if you flash 11c or higher you can't flash anything lower than anti-rollback (ARB) v01. 10A was v00. If you manage to flash 10x bootstack (bootloader/modem) after already being on 11c+ you will brick. Just don't flash any 10x files and you're fine (as of May 2017.. can't predict future builds...)
Q: I don't care about root or TWRP.. do I have to worry about this fuse stuff?
A: Nope, if you don't want root or TWRP just use LG Bridge or LGUP to upgrade to stock 11c and keep it movin'.
Q: Why does the boot.img need to be repacked?
A: boot.img is repacked for systemless root. You also need to repack the boot.img to stop TWRP from getting replaced with stock recovery the first time you boot into android after installing a new system/boot. A patch file in the system.img uses the boot.img when it's 100% stock and builds/flashes a stock recovery image... and this would replace TWRP. So to keep TWRP and keep a stock system.img you just repack the boot.img with either the SuperSU/Magisk, verity/encryption zip or the boot repacker zip. If you don't care about keeping TWRP none of this matters.
Q: How do I know if /data and /sdcard are encrypted?
A: If you never used TWRP and wiped/formatted data then you have encrypted data. Have TWRP and aren't sure? Boot into TWRP and try to browse /data or /sdcard... if both are empty then you are encrypted. Can you see stuff in /data and /sdcard? Then your data is not safe and not encrypted(but at least you can see files in TWRP, right?...).
NOTES:
This is for the carrier-free USA RS988 that can be officially bootloader unlocked through the LG Developer program. It should technically work with the Brightpoint variants but was made for the carrier-free variant. I was asked to put together an 11c zip so it was easier to downgrade from Android 7 Nougat to Android 6 Marshmallow by flashing the bootloader or COMPLETE zips in TWRP. LGUP does not allow downgrading from N to M so flashing with TWRP is currently the easiest downgrade method.
For the users stuck on Brightpoint's 10h, just unlock the bootloader, install TWRP and then flash the 11c COMPLETE zip in TWRP... reboot into Android and you'll be ready to accept the 11D and 21A OTA updates.
After someone flashes the 11C COMPLETE zip I need a user to boot into Android and then issue the adb reboot bootloader command to see if you boot into fastboot or if the phone just reboots.
It would be helpful if a user goes back to 11c stock then updates to 11D.. then installs TWRP.. and uses TWRP to backup all the stock 11D partitions (system, boot, modem and all the partitions that make up the bootstack/bootloader).
It would also be helpful if a user did the same when updating to 21A.
The exact process would be to flash back to 11C... take the OTA update to 11D/21A. Boot into fastboot and install twrp. unplug the usb cable and power off the phone. Boot into TWRP. Back up stock partitions in TWRP to tmp directory or external sdcard (internal sdcard will be encrypted and you wont be able to use that unless you format it). Then the partitions will need to be compressed (zip, rar, 7z etc..) and uploaded somewhere so I can download it and then make new flashable zips.
The partitions must be 100% stock.. so back them up before trying to root in TWRP or attempting any mods. OTA update > install twrp > boot into twrp and backup stock partitions.
Click to expand...
Click to collapse
y u quote OP?
For more G5 info see my All-in-One Thread HERE
Follow me on twitter for future updates on LG-related things - twitter.com/@utoprime
Find this thread helpful? Hit the Thanks button!
Feeling extra generous? Click my name at the top of any post and hit donate or click here.
#TEAMCODEFIRE

Thanks @autoprime I will do it right now

Just to confirm @autoprime fastboot access is unavailable on 11c it just reboots when issuing adb reboot bootloader command it does not become accessible until you upgrade to 11d
---------- Post added at 04:43 AM ---------- Previous post was at 04:41 AM ----------
If your phone reboots at all or boot loops when you are trying to setup after downgrading back to 11c just pull battery and go into stock recovery and do a factory reset and all will be good.
AriesTruong said:
Thanks @autoprime I will do it right now
Click to expand...
Click to collapse

I flashed and it boot loop at Enter Pass of phone. I also into recovery and select to factory reset but it still hit boot loop.
What should I do for next step. I will try run lgup when I have pc
---------- Post added at 07:42 AM ---------- Previous post was at 07:02 AM ----------
AriesTruong said:
I flashed and it boot loop at Enter Pass of phone. I also into recovery and select to factory reset but it still hit boot loop.
What should I do for next step. I will try run lgup when I have pc
Click to expand...
Click to collapse
Yes I reflashed with ROM RS98811c via LGUP and it works well. I will check update for Android 7.
Thanks @autoprime and users of RS988

Yes sorry i did not mention flashing the 11c kdz with lgup because i wasn't sure if it had to be done i only did it as a precaution to guarantee i was on factory stock before checking for updates. Just to report that 4g lte is working perfectly now that i am on the 21a nougat
AriesTruong said:
I flashed and it boot loop at Enter Pass of phone. I also into recovery and select to factory reset but it still hit boot loop.
What should I do for next step. I will try run lgup when I have pc
---------- Post added at 07:42 AM ---------- Previous post was at 07:02 AM ----------
Yes I reflashed with ROM RS98811c via LGUP and it works well. I will check update for Android 7.
Thanks @autoprime and users of RS988
Click to expand...
Click to collapse

firenemesis7 said:
Yes sorry i did not mention flashing the 11c kdz with lgup because i wasn't sure if it had to be done i only did it as a precaution to guarantee i was on factory stock before checking for updates. Just to report that 4g lte is working perfectly now that i am on the 21a nougat
Click to expand...
Click to collapse
Did you backup partition and shared with @autoprime? I still download N.21a

No i do not have twrp installed currently wanted to get back to 21a so i could test LTE for everyone that was asking it has been working great all night and today without one disconnection.
AriesTruong said:
Did you backup partition and shared with @autoprime? I still download N.21a
Click to expand...
Click to collapse

@autoprime all i see that i can backup in twrp are system, system image and boot will that be enough to be useful or is there any other way to backup up other partitions? i know recovery, data, and efs would most likely not be needed and that are the only other options.

firenemesis7 said:
@autoprime all i see that i can backup in twrp are system, system image and boot will that be enough to be useful or is there any other way to backup up other partitions? i know recovery, data, and efs would most likely not be needed and that are the only other options.
Click to expand...
Click to collapse
you would need to use adb shell in TWRP to manually backup the partitions. you could use twrps backup feature to backup system image (not system) and boot... but adb would be needed for all the others.
if you have an external sdcard you could backup system image and boot image to your ext-sd using twrps backup feature.
then for the rest you could use adb dd commands to save each partition to the /tmp directory... then after theyre all backed up to /tmp you could then use adb pull to pull each image from /tmp onto your pc.
the adb command's example would be:
adb shell
dd if=/dev/block/bootdevice/by-name/aboot of=/tmp/aboot.img
and those 2 commands above would then backup your aboot partition and save it as an img file in the /tmp directory.
and you would use that same "template" of a dd command for all the other partitions listed in the RS988 11C codefire directory.
dd if=/dev/block/bootdevice/by-name/PartitionNameHere of=/tmp/FileNameHere
so another example would be:
dd if=/dev/block/bootdevice/by-name/modem of=/tmp/modem.img
and you'd do the same for all the other partitions... list of partitions is here. Every file that ends with .img
if you didnt want to save each image file to the /tmp directory and instead directly onto your external sdcard.. you'd have to figure out what the external sdcard directory is..
for example: dd if=/dev/block/bootdevice/by-name/modem of=/sdcard/ext-sd/modem.img
or something along those lines... I don't have the directory for ext off the top of my head.
so with those steps.. you or another user would be making a proper backup of everything and would allow me to make a proper COMPLETE zip and bootloader zip for that software version. Then RS988 users wouldn't need to mess with 11C anymore (unless they wanted to).
a screenshot or copy/paste of the command prompt/terminal with all the adb commands used could be helpful so I could review and make sure there were no typos or mistakes. Forgetting to change the "partition name" in the command put changing the "image name" would result in some pretty dangerous mixups...
for example:
dd if=/dev/block/bootdevice/by-name/modem of=/tmp/modem.img
dd if=/dev/block/bootdevice/by-name/modem of=/tmp/aboot.img
those commands would give you 2 different image names... but looking more closely at the command.. both commands backed up the modem partition... despite the file being named "aboot.img". and if someone then flashed that "aboot.img" to their aboot partition, they would brick. and no kdz or rom zip will ever fix that. perm brick.

Everything worked out good zip file is uploading now and i will post link when it is ready. I included a text file with all my dd commands i used to generate the .img files.

@autoprime https://drive.google.com/open?id=0B9RvufywiW6VZ2d3ck90WFhJaEE this should be everything you need

I spent some time tonight on this.
Got the bootloader unlocked.
Flashed the twrp-3.0.2-1-rs988.img file.
Booted into TWRP and flashed the LG-RS98811c-Flashable.COMPLETE-ARB01.zip
Now the phone boots, asks for a security password, says there is 20/30, and then reboots within 2 seconds.
I'm not sure what to do.
I've done the bottom power button+power key, factory reset twice, says Android Starting, then when it gets to the Welcome Screen, Set Internet Connection and REBOOTS.
Edit:
I went into Download Mode and flashed the 11c KDZ in LG UP. Phone rebooted at end, then started asking again for a password. Went back to the Volume Down+Power and Factory Reset.
I was then able to get the phone to fully boot Android and currently downloading the 11d update.
My question is why it kept asking for a security password on boot, and how can I make sure that doesn't happen again?
Edit #2:
The 11d update downloaded and flashed, and upon reboot, it again is asking for a password to unlock?!?
Edit #3:
Once again did Volume Down+Power to factory reset. Now downloading the 21a.
But I have a feeling once it installs and reboots, it will once again ask for a password.
Edit 4:
Got 21a flashed. LTE with ATT GoPhone working.
The Password on boot is now gone (but still not sure why it kept coming up).
Now just the warning about the Unlocked Bootloader.

firenemesis7 said:
@autoprime this should be everything you need
Click to expand...
Click to collapse
thank you! I went through all the dd commands in the text and looked over the partitions.. everything looks perfect. :good:
I just need to confirm one more thing which I should have mentioned originally but it slipped my mind...
when you first booted into TWRP before the backups TWRP first asks you to enter a decryption password and then asks about keeping system "read-only". Which buttons/options did you select when going through these menus before you got into the main TWRP screen?
I'll assume you hit "cancel" on the decryption screen but for the system read-only menu.. did you select "keep read only" or "swipe to allow modifications" ?
if keep read only was selected.. great.. and I will work on putting the flashable zips together this weekend.
if you swiped to allow modifications, system was remounted and is no longer 100% stock and it wouldnt be the best option for putting together a stock rom... and I would need someone else to make a system backup (I could still use all your other partitions though!)

@autoprime yes i kept everything read only glad everything looks good.
---------- Post added at 03:52 PM ---------- Previous post was at 03:49 PM ----------
Not positive why the password popup kept coming up same thing happened for me i assume maybe because of the unlocked bootloader.
FAUguy said:
I spent some time tonight on this.
Got the bootloader unlocked.
Flashed the twrp-3.0.2-1-rs988.img file.
Booted into TWRP and flashed the LG-RS98811c-Flashable.COMPLETE-ARB01.zip
Now the phone boots, asks for a security password, says there is 20/30, and then reboots within 2 seconds.
I'm not sure what to do.
I've done the bottom power button+power key, factory reset twice, says Android Starting, then when it gets to the Welcome Screen, Set Internet Connection and REBOOTS.
Edit:
I went into Download Mode and flashed the 11c KDZ in LG UP. Phone rebooted at end, then started asking again for a password. Went back to the Volume Down+Power and Factory Reset.
I was then able to get the phone to fully boot Android and currently downloading the 11d update.
My question is why it kept asking for a security password on boot, and how can I make sure that doesn't happen again?
Edit #2:
The 11d update downloaded and flashed, and upon reboot, it again is asking for a password to unlock?!?
Edit #3:
Once again did Volume Down+Power to factory reset. Now downloading the 21a.
But I have a feeling once it installs and reboots, it will once again ask for a password.
Edit 4:
Got 21a flashed. LTE with ATT GoPhone working.
The Password on boot is now gone (but still not sure why it kept coming up).
Now just the warning about the Unlocked Bootloader.
Click to expand...
Click to collapse

autoprime said:
thank you! I went through all the dd commands in the text and looked over the partitions.. everything looks perfect. :good:
I just need to confirm one more thing which I should have mentioned originally but it slipped my mind...
when you first booted into TWRP before the backups TWRP first asks you to enter a decryption password and then asks about keeping system "read-only". Which buttons/options did you select when going through these menus before you got into the main TWRP screen?
I'll assume you hit "cancel" on the decryption screen but for the system read-only menu.. did you select "keep read only" or "swipe to allow modifications" ?
if keep read only was selected.. great.. and I will work on putting the flashable zips together this weekend.
if you swiped to allow modifications, system was remounted and is no longer 100% stock and it wouldnt be the best option for putting together a stock rom... and I would need someone else to make a system backup (I could still use all your other partitions though!)
Click to expand...
Click to collapse
When I did TWRP first boot, I didn't do the swipe right, so it kept it Read. From there I did the 11c Complete flash. Didn't do SuperSU.
Now that I've been on 21a for about 12 hours, I was wondering if there is a way to reverse the unlocked bootloader so that other apps like Android Pay will work?

confirm OEM Unlock is enabled in developer settings. "adb reboot bootloader" then "fastboot oem lock" once you are booted into fastboot. you should not have anything do worry about considering you did not enable modifications in twrp
FAUguy said:
When I did TWRP first boot, I didn't do the swipe right, so it kept it Read. From there I did the 11c Complete flash. Didn't do SuperSU.
Now that I've been on 21a for about 12 hours, I was wondering if there is a way to reverse the unlocked bootloader so that other apps like Android Pay will work?
Click to expand...
Click to collapse

firenemesis7 said:
confirm OEM Unlock is enabled in developer settings. "adb reboot bootloader" then "fastboot oem lock" once you are booted into fastboot. you should not have anything do worry about considering you did not enable modifications in twrp
Click to expand...
Click to collapse
OEM Unlock is grayed out for some reason, probably because it is unlocked? After doing the "Fastboot oem lock" command, I guess this research the phone, meaning apps and setting are cleared?

Yes it will be greyed out but the button is toggled to on. I don't think it will factory reset when you relock.

So I've noticed a major issue today. Not sure if it is with 21a, or with GoPhone (ATT network), but didn't have this issue with 11c/11d...
About half of incoming calls (placed from an land line or other cell) is not going through to the G5. It stays on LTE instead of changing to HSPA when the call comes in, and thus the G5 doesn't ring and goes to voice mail. Then it doesn't get the VM notification. I can place calls fine (changes from LTE to HSPA and back), so it looks to be only on incoming calls.
I've done the "Reset Network", verified the APN, and went to Global to GSM/LTE network mode. But still happens.

Mine is switching just fine on metropcs it actually seems like it switches quicker on 21a when receiving and ending calls than it did on 11c/d