STAR / ALPS U9501 Both MTK6589 and MTK6582
WARNING: Please make sure your phone is the exact same model & specification before flashing anything to your phone. Just because it looks the same does not mean it is the same phone. There are many many phones of this type with different hardware such as camera's, screen's & different RAM sizes and ROM sizes of which many are faked!! If in doubt do not flash anything.
YOU HAVE BEEN WARNED
{
"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"
}
First things first Read this entire post before you do anything!!
Backup Backup!
I cannot stress enough the importance of getting a full backup of your phone's stock ROM before you begin flashing tweaking or anything else Generally there is no, zero, none, manufacturer support for these devices so unless the seller made a full backup of your device you are screwed if something goes wrong :crying: SO getting a backup should be your very first step.
As said earlier there are many many variations of this phone I am sure with all kind's of different hardware configurations such as CPU, RAM, ROM, CAMERA and SCREENS so it's important to get your phones factory ROM Backed Up the most important things are the uboot.img boot.img it's also a good idea to have a stock recovery.img :good: The uboot and boot.img are what contains your phones specific hardware configuration such as the list above so providing you maintain your stock uboot and boot.img you will always be able to get these things working correctly. :highfive:
Caution: Not all is as it may seem I purchased two phones from different sellers on ebay both phones claimed to be the exact same specification MTK6589 1GB RAM 8GB ROM 720 x1280 screen res.
When the phones arrived they looked identical and I was very impressed with the general quality and the quick, smooth & responsive ROM.
So I set about getting them both rooted.
MTK Droid tools reported one phone as MTK6582 so after backing up and rooting I looked through the rom and found a script called "agold_cheat_evaluating_software.xml" This script fools all benchmark testing softwares into reporting any MTK6582 and even an MTK6572 device to be reported as an MTK6589 with a CPU frequency of 1.2ghz the rom also affects mobileuncle. This just demonstrates that you must proceed with caution
I was in middle of writing a tut to show Noob's how to best achieve a full backup when I came across this most excellent Tutorial by @rnovino on pinoyscreencast.net. :highfive: http://pinoyscreencast.net/get-stock-rom-romdump-mediatek-mt6582-via-mtk-droid-root-tools/
Please follow his instructions according to your true CPU type the MTK6589 is in the video and some extra steps are required for the MTK6582 version which he explains in post :victory: I thank him for saving me so much time and effort :laugh:
He has also linked and listed the tools and drivers required
MTK Droid tools will show the true CPU you have in your phone so a massive thanks to @Rula1 for his awesome work on this tool Please hit his thanks button. Here
Posting on this thread:
Please do not QUOTE large posts in full :crying: only QUOTE the relevant part and delete the rest. Use The Hide button when posting large amounts Code or text if someone has requested it. As one guy said on xda after someone quoted a large TUT “Dude you owe me a new mouse wheel” LOL
Thanks:
Use the Thanks button if someone has helped you. :highfive:
Manners:
Being British most of us are polite and I expect you to be too. My Mother always said “son remember manners cost nothing but they will get you a long way in life”. :angel:
Helping yourselves:
Please try to help yourself as much as you can. Google Search is your Best Friend so please use it in the first instance. :highfive: I will do my best to help where I can but I am no top developer so try not to get too techy on me. I will try to explain things in plain English for the less experienced and experienced to understand.
TWRP V2.5.0 Recovery for MTK6589
Well I finally managed to manually port TWRP to our phone :victory:
The main problem was a standard port of TWRP would always exceed the recovery partition size no matter how I tried. The kernel of our phone is rather large at 4.2mb and this combined with the TWRP files would always come out too large. :crying:
I was about to give up on ever having TWRP again when I spotted this recompiled version of TWRP on the lenovo ru forum. Here So thanks and credit to the guy who recompiled TWRP to give me those few extra mb's to allow me to squeeze TWRP on to our phone. :highfive: I still had to edit a few images but it now works. :victory: :victory: :victory:
IMPORTANT:
Before you flash this double check the file size against your stock recovery.img or recovery partition size. Highlight recovery/right click/properties/details and check the actual size's
If the twrp recovery is larger than the "stock" recovery.img or recovery partition it will kill your sim slots They will not be displayed or detected!! If it's smaller then your good to go
There is also included in the download MY factory recovery CWM recovery build.prop file and two boot.img's one factory one patched for root
You are responsible for flashing so you do so at your own risk and I will not be responsible for any damage or bricks.
Download HERE
TWRP V2.5.0 Recovery for MTK6582
Well I finally managed to manually port TWRP to our phone :victory:
The main problem was a standard port of TWRP would always exceed the recovery partition size no matter how I tried. The kernel of our phone is rather large at 4.2mb and this combined with the TWRP files would always come out too large. :crying:
I was about to give up on ever having TWRP again when I spotted this recompiled version of TWRP on the lenovo ru forum. Here So thanks and credit to the guy who recompiled TWRP to give me those few extra mb's to allow me to squeeze TWRP on to our phone. :highfive: I still had to edit a few images but it now works. :victory: :victory: :victory:
IMPORTANT:
Before you flash this double check the file size against your stock recovery.img or recovery partition size. Highlight recovery/right click/properties/details and check the actual size's
If the twrp recovery is larger than the "stock" recovery.img or recovery partition it will kill your sim slots They will not be displayed or detected!! If it's smaller then your good to go
There is also included in the download MY factory recovery CWM recovery build.prop file and two boot.img's one factory one patched for root
You are responsible for flashing so you do so at your own risk and I will not be responsible for any damage or bricks.
Download: HERE
Stock Firmware (Roms)
MTK6582 Version
Restore files only SpFlashtool required.
Download Here
MTK6589 Version
MTK6589: SP Flash tool Required Phone.info Here
Code:
Hardware : MT6589
Model : 06v20_v89_gq3009hd
Build number : 06v20_v89_gq3009hd_20131024
Build date UTC : 20131023-220102
Android v : 4.2.2
Baseband v: MOLY.WR8.W1248.MD.WG.MP.V6.P9, 2013/07/09 20:18
Kernel v : 3.4.5 ([email protected]) (gcc version 4.6.x-google 20120106 (prerelease) (GCC) ) #1 SMP Thu Oct 24 05:57:20 CST 2013
Uboot build v : ----- should be root shell
LCD Driver IC : 1-LT050ANKP029A
installed .apk (APP) List
Code:
C:\Users\Dell\Desktop\MtkDroidTools>adb shell pm list packages
package:Agold.com
package:agold.weatherwidget
package:android
package:com.agold.AgoldFactoryTest
package:com.agold.launcher.wallpaper
package:com.agold.launcher.wallpaperlock
package:com.androguide.ryuinferno.universal.init.d.support
package:com.android.SuspendWindow
package:com.android.backupconfirm
package:com.android.browser
package:com.android.calculator2
package:com.android.calendar
package:com.android.cellbroadcastreceiver
package:com.android.certinstaller
package:com.android.contacts
package:com.android.defcontainer
package:com.android.deskclock
package:com.android.dreams.basic
package:com.android.dreams.phototable
package:com.android.email
package:com.android.exchange
package:com.android.facelock
package:com.android.flashlightnotification
package:com.android.galaxy4
package:com.android.gallery3d
package:com.android.htmlviewer
package:com.android.inputmethod.latin
package:com.android.keychain
package:com.android.launcher
package:com.android.location.fused
package:com.android.magicsmoke
package:com.android.mms
package:com.android.music
package:com.android.musicfx
package:com.android.musicvis
package:com.android.noisefield
package:com.android.packageinstaller
package:com.android.phasebeam
package:com.android.phone
package:com.android.protips
package:com.android.providers.applications
package:com.android.providers.calendar
package:com.android.providers.contacts
package:com.android.providers.downloads
package:com.android.providers.downloads.ui
package:com.android.providers.drm
package:com.android.providers.media
package:com.android.providers.settings
package:com.android.providers.telephony
package:com.android.providers.userdictionary
package:com.android.provision
package:com.android.settings
package:com.android.sharedstoragebackup
package:com.android.simmelock
package:com.android.soundrecorder
package:com.android.stk
package:com.android.systemui
package:com.android.vending
package:com.android.videoeditor
package:com.android.vpndialogs
package:com.android.wallpaper
package:com.android.wallpaper.holospiral
package:com.android.wallpaper.livepicker
package:com.buak.Link2SD
package:com.dataviz.docstogo
package:com.devices114
package:com.devices118
package:com.estrongs.android.pop
package:com.example.amaboyapp
package:com.gameloft.android.ANMP.GloftDMHM
package:com.google.android.apps.maps
package:com.google.android.apps.uploader
package:com.google.android.backup
package:com.google.android.ears
package:com.google.android.feedback
package:com.google.android.gm
package:com.google.android.gms
package:com.google.android.googlequicksearchbox
package:com.google.android.gsf
package:com.google.android.gsf.login
package:com.google.android.inputmethod.latin
package:com.google.android.inputmethod.latin.dictionarypack
package:com.google.android.location
package:com.google.android.marvin.talkback
package:com.google.android.onetimeinitializer
package:com.google.android.partnersetup
package:com.google.android.syncadapters.bookmarks
package:com.google.android.syncadapters.calendar
package:com.google.android.syncadapters.contacts
package:com.google.android.talk
package:com.google.android.tts
package:com.google.android.voicesearch
package:com.mediatek
package:com.mediatek.CellConnService
package:com.mediatek.DataUsageLockScreenClient
package:com.mediatek.FMRadio
package:com.mediatek.StkSelection
package:com.mediatek.appguide.plugin
package:com.mediatek.appwidget.weather
package:com.mediatek.appwidget.worldclock
package:com.mediatek.apst.target
package:com.mediatek.atci.service
package:com.mediatek.batterywarning
package:com.mediatek.bluetooth
package:com.mediatek.calendarimporter
package:com.mediatek.connectivity
package:com.mediatek.datatransfer
package:com.mediatek.engineermode
package:com.mediatek.filemanager
package:com.mediatek.lbs.em
package:com.mediatek.mtklogger
package:com.mediatek.notebook
package:com.mediatek.omacp
package:com.mediatek.oobe
package:com.mediatek.schpwronoff
package:com.mediatek.smsreg
package:com.mediatek.systemupdate
package:com.mediatek.systemupdate.sysoper
package:com.mediatek.theme.mint
package:com.mediatek.theme.mocha
package:com.mediatek.theme.raspberry
package:com.mediatek.thermalmanager
package:com.mediatek.todos
package:com.mediatek.videofavorites
package:com.mediatek.videoplayer
package:com.mediatek.vlw
package:com.mediatek.voicecommand
package:com.mediatek.voiceunlock
package:com.mediatek.weather
package:com.mediatek.weather3dwidget
package:com.mediatek.ygps
package:com.mobileuncle.toolbox
package:com.projectmkmassags
package:com.svox.pico
package:com.uucun4470.android.cms
package:com.zte.mobile.MushroomDay
package:eu.chainfire.supersu
C:\Users\Dell\Desktop\MtkDroidTools>adb devices
Agold .apk makes lots of system mods so until this is fully investigated proceed with caution!!
The ROM is smooth and stable with everything working on my device as it should. :good:
Power consumption is very good too under normal use :good:
Below is a file called projectConfig.mk which I believe is run at startup but I have not had chance to fully investigate this. Notice all the cheats that can be activated although they seem not be activated in this rom I think "Agold_Empty" THIS IS A LONG LIST so I have had to upload as an attachment PS: The Rom has superuser but will require the patched boot and a patched recovery of your choice to stay rooted which are included in the download.
com.mobileuncle.toolbox should be removed and replaced with the uptodate version on playstore which now supports our phone more fully
ConfigProject.mk.txt Download
Download: HERE
Hints and Tips
Get Artistic and Make Your Own one of a kind Wallpapers easy noob friendly Here
Hi! I am glad to see this thread!
Just so you know, I found 4 ROMs for that phones on a Rusian forum, and as far as I can see there seems to be two version of that phone...
3 of the ROMs where OEM original ROMs but different releases. The guy who posted those said that only 2 of the three are functionnal on his phone. I tried all ROMs, and in my case, the only one that works is the one that didn't work for him.
My phone is identified as a MTK Model No.: ES-4 (on the back behind the battery). That that mean that it is not a real U9501?
jy_P said:
Just so you know, I found 4 ROMs for that phones on a Rusian forum, and as far as I can see there seems to be two version of that phone...
3 of the ROMs where OEM original ROMs but different releases. The guy who posted those said that only 2 of the three are functionnal on his phone. I tried all ROMs, and in my case, the only one that works is the one that didn't work for him.
My phone is identified as a MTK Model No.: ES-4 (on the back behind the battery). That that mean that it is not a real U9501?
Click to expand...
Click to collapse
Yes I think there could be many many differnt types.
Can you pull the build.prop file from /system of the original stock rom and paste the text as CODE Then HIDE?
This will give us a better idea as to the true model identification :fingers-crossed:
I am going to work now so will take a little time to reply.
This is my build.prop to compare.
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JOP40D
ro.build.display.id=06v20_v89_gq3009hd_20131024
ro.build.version.incremental=eng.root.1382565471
ro.custom.build.version=1382565471
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.2.2
ro.build.date=2013年 10月 24日 星期四 06:01:02 CST
ro.build.date.utc=1382565662
ro.build.type=user
ro.build.user=root
ro.build.host=bahe3-desktop
ro.build.tags=test-keys
ro.product.model=06v20_v89_gq3009hd
ro.product.brand=alps
ro.product.name=06v20_v89_gq3009hd
ro.product.device=06v20_v89_gq3009hd
ro.product.board=06v20_v89_gq3009hd
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=alps
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=06v20_v89_gq3009hd
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=e2006v20_v89_gq3009hd-user 4.2.1 JOP40D eng.root.1382565471 test-keys
ro.build.fingerprint=alps/06v20_v89_gq3009hd/06v20_v89_gq3009hd:4.2.1/JOP40D/1382565471:user/test-keys
ro.build.flavor=
persist.sys.timezone=
ro.build.characteristics=default
ro.build.bluetooth.name=
ro.build.wifi.ssid=
# end build properties
# begin mediatek build properties
ro.mediatek.version.release=ALPS.JB2.MP.V1.2
ro.mediatek.platform=MT6589
ro.mediatek.chip_ver=S01
ro.mediatek.version.branch=ALPS.JB2.MP
ro.mediatek.version.sdk=1
# end mediatek build properties
#
# 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=131072
wifi.direct.interface=p2p0
dalvik.vm.heapgrowthlimit=128m
dalvik.vm.heapsize=256m
# USB MTP WHQL
ro.sys.usb.mtp.whql.enable=0
# Power off opt in IPO
sys.ipo.pwrdncap=2
ro.sys.usb.storage.type=mtp,mass_storage
# USB BICR function
ro.sys.usb.bicr=yes
# 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
#
ril.specific.sm_cause=0
gps.solution.combo.chip=1
ril.external.md=0
fmradio.driver.chip=3
ro.sf.hwrotation=0
ril.current.share_modem=2
launcherplus.allappsgrid=2d
launcher2.allappsgrid=3d_20
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.mtk.wcn.combo.chipid=-1
drm.service.enabled=true
fmradio.driver.enable=1
ril.first.md=1
ril.flightmode.poweroffMD=1
ril.telephony.mode=1
ril.radiooff.poweroffMD=0
dalvik.vm.mtk-stack-trace-file=/data/anr/mtk_traces.txt
mediatek.wlan.chip=MT6628
mediatek.wlan.module.postfix=_mt6628
ro.local.all.language=en_US,fr_FR,it_IT,es_ES,de_DE,nl_NL,cs_CZ,pl_PL,ja_JP,zh_TW,zh_CN,ru_RU,ko_KR,nb_NO,es_US,da_DK,el_GR,tr_TR,pt_PT,pt_BR,rm_CH,sv_SE,bg_BG,ca_ES,en_GB,fi_FI,hi_IN,hr_HR,hu_HU,in_ID,iw_IL,lt_LT,lv_LV,ro_RO,sk_SK,sl_SI,sr_RS,uk_UA,vi_VN,tl_PH,ar_EG,fa_IR,th_TH,sw_TZ,ms_MY,af_ZA,zu_ZA,am_ET,km_KH,my_MM,ur_PK,bn_IN
ro.config.notification_sound=Whistle.ogg
ro.config.alarm_alert=Walk_in_the_forest.ogg
ro.config.ringtone=S_Over_the_horizon.ogg
ro.hnd.analog.audio.max=172
ro.hed.analog.audio.max=148
ro.calll.nor.mic=148
ro.calll.hed.mic=152
ro.idle.nor.mic=192
ro.idle.hed.mic=192
ro.calll.hnd.mic=192
ro.idle.hnd.mic=192
ro.def.bt.in.vol=0x500
ro.def.bt.out.vol=0x2000
ro.def.volume.music=10
ro.def.volume.ring=6
ro.def.volume.voice.calll=6
ro.def.volume.system=6
ro.def.volume.alarm=6
ro.def.volume.notification=6
ro.def.volume.fm=11
ro.def.volume.matv=6
ro.def.volume.dtmf=6
ro.def.volume.system.enforced=6
ro.def.volume.bluetooth.sco=6
ro.def.volume.volume.tts=6
ro.nor.sph.vol=69,81,93,105,114,122,130
ro.hed.sph.vol=76,88,100,112,124,136,148
ro.hnd.sph.vol=79,91,103,115,127,139,155
ro.hed.media.vol=112,136,160,184,208,232,255
ro.hnd.media.vol=104,128,152,176,200,224,248
ro.hnd.tv.vol=112,136,160,184,208,232,255
ro.hed.tv.vol=0,32,64,62,128,160,192
ro.hnd.fm.vol=112,136,160,184,208,232,255
ro.hed.fm.vol=16,80,112,144,176,208,240
ro.nor.key.vol=108,132,156,180,204,228,252
ro.hed.key.vol=108,132,156,180,204,228,252
ro.hnd.key.vol=108,132,156,180,204,228,252
ro.hnd.ring.vol=136,160,184,204,220,236,255
ro.hed.ring.vol=136,160,184,204,220,236,255
ro.def.android.keyboard=en_US
ro.def.android.keyboard1=EMPTY
ro.all.keyboard=en_US,en_GB,ar,bn,cs,de,de_qwerty,es,fr,fr_CA,fr_CH,hi,hu,it,nb,nl,pt,ru,tr,th,el,ur,vi,fa,ms,pt_PT,in_ID,ro,en_PH,iw,pt_BR,zz_qwerty,km_KH,my_MM,fr_qwertz
ro.current.keyboard=en_US,en_GB,ar,cs,de,el,es,fa,fr,fr_CA,hi,hu,it,iw,nl,pt_BR,ro,ru,th,tr,vi,zz_qwerty,bn,en_PH,in_ID,ms,ur,km_KH,my_MM,de_qwerty,fr_qwertz
ro.local.def.language0=EMPTY
ro.local.def.language1=EMPTY
ro.local.def.language2=EMPTY
ro.local.def.language3=EMPTY
ro.def.camera.flash=off
ro.def.camera.zsd=off
ro.def.camera.face=off
ro.def.camera.pic.size.main=4864x2736
ro.def.camera.pic.size.sub=3840x2160
ro.def.camera.exposure.main=0
ro.def.camera.exposure.sub=0
ro.def.camera.antiband.main=auto
ro.def.camera.antiband.sub=50hz
ro.def.camera.bright.main=middle
ro.def.camera.bright.sub=middle
ro.gprs.switch=no
ro.keyboard.vibrate.value=0
ro.build.shutdown.animation=no
ro.build.time.format=12
ro.build.date.format=yyyy-MMM-d-EE
ro.auto.time.update=no
ro.auto.timezone.update=no
ro.build.default.scrbrightness=160
ro.build.max.scrbrightness=255
ro.default.inputmethod=AGOLD_EMPTY
ro.default.gps.switch=null
ro.install.nonmarket.switch=no
ro.gravity.rotation=yes
ro.build.livewp=AGOLD_EMPTY
ro.screenoff.timout=60000
ro.closescreen.timeout=6000
ro.overleap.lockscr=no
ro.build.ipo.setting=yes
ro.alarm.snooze.time=5
ro.alarm.silence.time=5
ro.wifi.notification=no
ro.wifi.sleepmode=0
ro.powerkey.function=0
ro.install.location=2
ro.build.staticwp=com.agold.launcher.wallpaper/wallpaper_default
ro.build.keyboard.touchaudio=yes
ro.build.touch.sound=no
ro.lockscreen.sound=yes
ro.touch.vibrator.feed=yes
ro.build.fontsize=AGOLD_EMPTY
ro.default.fontsize=100
ro.audioprofile.more=no
or.build.vibratorvol=0
or.build.vibratortime=0
or.button.ledvalue=4
ro.browser.homepage=AGOLD_EMPTY
ro.nosignal.hideicons=yes
ro.show.navigationbar=no
or.build.serialname=0123456789ABCDEFG
ro.phone.min.num.match=7
ro.build.autobrightness=no
ro.roaming.reminder=-1
ro.wifimac.tonvram=2
ro.acc.alps.calibration=acc,alps
ro.transition.animation=1
ro.firstboot.date=2013,3,1
ro.enable.internet.call=no
ro.sip.receiver.call=no
ro.default.battery.switch=no
ro.build.audivregain.spk=1285
ro.hallwindow.visible=yes
AP
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Click to expand...
Click to collapse
Hi!
Here is my build.prop
But just so you know, this is not the original one. I flashed my phone already with a few ROMs that I got from that Rusian site. So this ROM is one of the ROM that are supposed to be the stock ROM, but I can tell that the content of the build.prop isn't the same as the original ROM since I don't see the same details in the "About" menu.
I should have made a backup of the original ROM, unfortunately, I didn't. Too late now.
If you want the ROMs let me know, I can send all of them to you.
They are the "stock" version from May, July and September. I also have another ROM that is supposed to be a port of the N9500 which seems to be pretty much the same thing but with different background color in the menus and missing background pictures. So the following build.prop is from that July ROM.
My front camera isn't working, but it never did even with the stock ROM.
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JOP40D
ro.build.display.id=06v20_v89_gq3009hd_20130702
ro.build.version.incremental=eng.root.1372750620
ro.custom.build.version=1372750620
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.2.1
ro.build.date=2013年 07月 02日 星期二 15:39:53 CST
ro.build.date.utc=1372750793
ro.build.type=user
ro.build.user=root
ro.build.host=bahe3-desktop
ro.build.tags=test-keys
ro.product.model=06v20_v89_gq3009hd
ro.product.brand=alps
ro.product.name=06v20_v89_gq3009hd
ro.product.device=06v20_v89_gq3009hd
ro.product.board=06v20_v89_gq3009hd
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=alps
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=06v20_v89_gq3009hd
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=e2006v20_v89_gq3009hd-user 4.2.1 JOP40D eng.root.1372750620 test-keys
ro.build.fingerprint=alps/06v20_v89_gq3009hd/06v20_v89_gq3009hd:4.2.1/JOP40D/1372750620:user/test-keys
ro.build.flavor=
persist.sys.timezone=
ro.build.characteristics=default
ro.build.bluetooth.name=
ro.build.wifi.ssid=
# end build properties
# begin mediatek build properties
ro.mediatek.version.release=ALPS.JB2.MP.V1.2
ro.mediatek.platform=MT6589
ro.mediatek.chip_ver=S01
ro.mediatek.version.branch=ALPS.JB2.MP
ro.mediatek.version.sdk=1
# end mediatek build properties
#
# 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=131072
wifi.direct.interface=p2p0
dalvik.vm.heapgrowthlimit=128m
dalvik.vm.heapsize=256m
# USB MTP WHQL
ro.sys.usb.mtp.whql.enable=0
# Power off opt in IPO
sys.ipo.pwrdncap=2
ro.sys.usb.storage.type=mtp,mass_storage
# USB BICR function
ro.sys.usb.bicr=yes
# 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
#
ril.specific.sm_cause=0
gps.solution.combo.chip=1
ril.external.md=0
fmradio.driver.chip=3
ro.sf.hwrotation=0
ril.current.share_modem=2
launcherplus.allappsgrid=2d
launcher2.allappsgrid=3d_20
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.mtk.wcn.combo.chipid=-1
drm.service.enabled=true
fmradio.driver.enable=1
ril.first.md=1
ril.flightmode.poweroffMD=1
ril.telephony.mode=1
ril.radiooff.poweroffMD=0
dalvik.vm.mtk-stack-trace-file=/data/anr/mtk_traces.txt
mediatek.wlan.chip=MT6628
mediatek.wlan.module.postfix=_mt6628
ro.local.all.language=en_US,fr_FR,it_IT,es_ES,de_DE,nl_NL,cs_CZ,pl_PL,ja_JP,zh_TW,zh_CN,ru_RU,ko_KR,nb_NO,es_US,da_DK,el_GR,tr_TR,pt_PT,pt_BR,rm_CH,sv_SE,bg_BG,ca_ES,en_GB,fi_FI,hi_IN,hr_HR,hu_HU,in_ID,iw_IL,lt_LT,lv_LV,ro_RO,sk_SK,sl_SI,sr_RS,uk_UA,vi_VN,tl_PH,ar_EG,fa_IR,th_TH,sw_TZ,ms_MY,af_ZA,zu_ZA,am_ET,km_KH,my_MM,ur_PK,bn_IN
ro.config.notification_sound=Whistle.ogg
ro.config.alarm_alert=Walk_in_the_forest.ogg
ro.config.ringtone=S_Over_the_horizon.ogg
ro.hnd.analog.audio.max=172
ro.hed.analog.audio.max=148
ro.calll.nor.mic=148
ro.calll.hed.mic=152
ro.idle.nor.mic=192
ro.idle.hed.mic=192
ro.calll.hnd.mic=192
ro.idle.hnd.mic=192
ro.def.bt.in.vol=0x500
ro.def.bt.out.vol=0x2000
ro.def.volume.music=10
ro.def.volume.ring=6
ro.def.volume.voice.calll=6
ro.def.volume.system=6
ro.def.volume.alarm=6
ro.def.volume.notification=6
ro.def.volume.fm=11
ro.def.volume.matv=6
ro.def.volume.dtmf=6
ro.def.volume.system.enforced=6
ro.def.volume.bluetooth.sco=6
ro.def.volume.volume.tts=6
ro.nor.sph.vol=69,81,93,105,117,129,140
ro.hed.sph.vol=76,88,100,112,124,136,148
ro.hnd.sph.vol=79,91,103,115,127,139,155
ro.hed.media.vol=112,136,160,184,208,232,255
ro.hnd.media.vol=104,128,152,176,200,224,248
ro.hnd.tv.vol=112,136,160,184,208,232,255
ro.hed.tv.vol=0,32,64,62,128,160,192
ro.hnd.fm.vol=112,136,160,184,208,232,255
ro.hed.fm.vol=16,80,112,144,176,208,240
ro.nor.key.vol=108,132,156,180,204,228,252
ro.hed.key.vol=108,132,156,180,204,228,252
ro.hnd.key.vol=108,132,156,180,204,228,252
ro.hnd.ring.vol=136,160,184,204,220,236,255
ro.hed.ring.vol=136,160,184,204,220,236,255
ro.def.android.keyboard=en_US
ro.def.android.keyboard1=EMPTY
ro.all.keyboard=en_US,en_GB,ar,bn,cs,de,de_qwerty,es,fr,fr_CA,fr_CH,hi,hu,it,nb,nl,pt,ru,tr,th,el,ur,vi,fa,ms,pt_PT,in_ID,ro,en_PH,iw,pt_BR,zz_qwerty,km_KH,my_MM,fr_qwertz
ro.current.keyboard=en_US,en_GB,ar,cs,de,el,es,fa,fr,fr_CA,hi,hu,it,iw,nl,pt_BR,ro,ru,th,tr,vi,zz_qwerty,bn,en_PH,in_ID,ms,ur,km_KH,my_MM,de_qwerty,fr_qwertz
ro.local.def.language0=EMPTY
ro.local.def.language1=EMPTY
ro.local.def.language2=EMPTY
ro.local.def.language3=EMPTY
ro.def.camera.flash=off
ro.def.camera.zsd=off
ro.def.camera.face=off
ro.def.camera.pic.size.main=3264x2448
ro.def.camera.pic.size.sub=2048x1536
ro.def.camera.exposure.main=0
ro.def.camera.exposure.sub=0
ro.def.camera.antiband.main=auto
ro.def.camera.antiband.sub=50hz
ro.def.camera.bright.main=middle
ro.def.camera.bright.sub=middle
ro.gprs.switch=no
ro.keyboard.vibrate.value=0
ro.build.shutdown.animation=no
ro.build.time.format=12
ro.build.date.format=yyyy-MMM-d-EE
ro.auto.time.update=no
ro.auto.timezone.update=no
ro.build.default.scrbrightness=160
ro.build.max.scrbrightness=255
ro.default.inputmethod=AGOLD_EMPTY
ro.default.gps.switch=null
ro.install.nonmarket.switch=no
ro.gravity.rotation=yes
ro.build.livewp=AGOLD_EMPTY
ro.screenoff.timout=60000
ro.closescreen.timeout=6000
ro.overleap.lockscr=no
ro.build.ipo.setting=yes
ro.alarm.snooze.time=5
ro.alarm.silence.time=5
ro.wifi.notification=no
ro.wifi.sleepmode=0
ro.powerkey.function=0
ro.install.location=2
ro.build.staticwp=com.agold.launcher.wallpaper/wallpaper_default
ro.build.keyboard.touchaudio=yes
ro.build.touch.sound=no
ro.lockscreen.sound=yes
ro.touch.vibrator.feed=yes
ro.build.fontsize=AGOLD_EMPTY
ro.default.fontsize=100
ro.audioprofile.more=no
or.build.vibratorvol=0
or.build.vibratortime=0
or.button.ledvalue=4
ro.browser.homepage=AGOLD_EMPTY
ro.nosignal.hideicons=yes
ro.show.navigationbar=no
or.build.serialname=0123456789ABCDEFG
ro.phone.min.num.match=7
ro.build.autobrightness=no
ro.roaming.reminder=-1
ro.wifimac.tonvram=2
ro.acc.alps.calibration=acc,alps
ro.transition.animation=1
ro.firstboot.date=2013,3,1
ro.enable.internet.call=no
ro.sip.receiver.call=no
ro.default.battery.switch=no
ro.build.audivregain.spk=1285
ro.hallwindow.visible=no
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
---------- Post added at 01:17 PM ---------- Previous post was at 01:14 PM ----------
And many thanks in advance for working on this! I have been looking for a ROM for a long time!
jy_P said:
Hi!
Here is my build.prop
But just so you know, this is not the original one. I flashed my phone already with a few ROMs that I got from that Rusian site. So this ROM is one of the ROM that are supposed to be the stock ROM, but I can tell that the content of the build.prop isn't the same as the original ROM since I don't see the same details in the "About" menu.
I should have made a backup of the original ROM, unfortunately, I didn't. Too late now.
[/COLOR]And many thanks in advance for working on this! I have been looking for a ROM for a long time!
Click to expand...
Click to collapse
Hi bro,
Well from the build.prop I would say our phones are the same It's a real shame and brave you didn't get a backup first before you flashed a new rom. ( Not recommended to others :laugh: )
Did you flash the boot.img too or just system ? If you have the stock boot.img there is a build.prop in there too which will show the true id of your phone. :fingers-crossed:
Get @michfood awesome boot & recovery repack utility for windows V2. Here Unpack to desktop. Then copy your boot.img to the folder then drag and drop it on to the MTK unpack.bat It will make a "boot" folder and in there you can find the contents of your boot.img look in rmdisk folder for your build.prop
As you can see from my build.prop my phones build date is October so slightly newer than the one's you have but please feel free to upload them some place to share. Recomend https://mega.co.nz it's FREE :good: plus you get 50gb storage and you dont get loads of popups and false download links also no need for spliting larger files as some of these JB backups can hit 1gb without trying
I will be uploading and posting my stuff tomorrow and some tut's etc etc for the newcomers. So please stay tuned
Thanks for the Thanks btw. Just hit the thanks button if I helped
Regards bigrammy.
I am uploading the ROMs that I have... Do you want the link(s) as PM? It will take about 24h... My upload is slow.
I am not sure if I still have my original boot image. I might have it, but when I tried the MTK_Unpack, it generated a folder with a bunch of files and folder, but there is no build.prop.
I don't have a Linux OS on hand... Do you want my boot.img that might still be the original one?
jy_P said:
I am uploading the ROMs that I have... Do you want the link(s) as PM? It will take about 24h... My upload is slow.
I am not sure if I still have my original boot image. I might have it, but when I tried the MTK_Unpack, it generated a folder with a bunch of files and folder, but there is no build.prop.
I don't have a Linux OS on hand... Do you want my boot.img that might still be the original one?
Click to expand...
Click to collapse
Hi, Sure you can post the ROM links here if you like :good:
Just try include as much info as you can about each of them maybe you could just pull the build.prop for each so people can check it to see if it matches up with there phones.
Also put a disclaimer saying people flash them at there own risk.
As for boot.img well sorry bro my mistake build.prop is in the factory recovery.img which you probably flashed over. I have been porting recoverys to these phones so I was getting confused as I have unpacked and repacked so many latley Same method applies If you still have the recovery.img. Most I have looked at have a build.prop of some descriptiton some are short version and some are full lengthen.
I use windows too so nothing I do will be in linux.
:cool
USE AT YOUR OWN RISK!
There are risks when flashing devices. If any one of those ROMs isn’t working, just try flashing another one… I am not responsible if you take the risk and break your phone. But note that I flashed them all and my phone is still working
You will find 4 ROMs there https://mega.co.nz/#F!opQn2ARB!YRwITQGXB-EmlVX4KBDqfA
I found all these ROMs as is on the web.
The next 3 comes from a Russian Forums and they are identified as stock ROMs (different releases May, July and September).
The guy that posted those said only the July didn’t work for him. In my case, only the July works. Flash with SP Flash Tool.
06v20_v89_gq3009hd_130529
06v20_v89_gq3009hd_130702
06v20_v89_gq3009hd_130907
This one was identified as a port from the N9500. I tried it, it worked on my phone but other than menu back ground color, it seems to see the same ROM at the user stand point. I have some minor issues with all the ROMs I tried and they are the same on every ROMs (occasional problem connecting Skype, google play that won’t update after some time). This one is a CWR backup. So you need to restore it from CWR and do a Factory reset.
StarU9501FromN9500Original
THOSE ROMs ARE ALL HAVING CHINESSE BLOATWARE, clean it after flashing using MTKDroidTools V2.51
Final note, I don’t see why anyone would need any of these ROMs. The two that I tried aren’t perfect. But if you really need a ROM, this is better than nothing I guess. Make a backup of your phone first with MTKDroidTools (I should have too). We rather need a better ROM. I hope we’ll get one.
If you need to ROOT your original ROM or any of these ones, I did it using UnLockRoot (but I had to run it a few times and skip the reboot step at some point… No more details, good luck). You can install CWR on the original ROM or any of these ones using MTKDroidTools.
Again, I am not responsible if something goes wrong. You do it at your own risks.
If you have question regarding MTKDroidTools, SP Flash Tool or UnLockRoot, ask Google. I found it all, you should be able too!
bigrammy: You will also find there a boot image that could be either the same as the N9500 port or the original one that I had on my phone… I don’t know anymore but it seems to be the one from the N9500 ported ROM.
Click on thanks if that helps!
jy_P said:
Click on thanks if that helps!
Click to expand...
Click to collapse
Thanks for the time and effort in making this post bro :highfive:
Can you post your ROM too since it is more recent than mine?
Thanks!
jy_P said:
Can you post your ROM too since it is more recent than mine?
Thanks!
Click to expand...
Click to collapse
Added to post #3 Here as requested.
Any bloat were? Rooted? Known bugs? Any plans for alternative or custom Rom?
Envoyé de mon 06v20_v89_gq3009hd en utilisant Tapatalk
---------- Post added at 11:23 PM ---------- Previous post was at 11:07 PM ----------
... And thank you too!
Envoyé de mon 06v20_v89_gq3009hd en utilisant Tapatalk
jy_P said:
Any bloat were? Rooted? Known bugs? Any plans for alternative or custom Rom?
Envoyé de mon 06v20_v89_gq3009hd en utilisant Tapatalk
---------- Post added at 11:23 PM ---------- Previous post was at 11:07 PM ----------
... And thank you too!
Envoyé de mon 06v20_v89_gq3009hd en utilisant Tapatalk
Click to expand...
Click to collapse
Post updated with as much info as I have :silly: Rom has superuser but will require patched boot and patched recovery of your choice to stay rooted all included.
com.mobileuncle.toolbox should be removed and replaced with the uptodate version on playstore
bigrammy said:
Post updated with as much info as I have :silly: Rom has superuser but will require patched boot and patched recovery of your choice to stay rooted all included.
com.mobileuncle.toolbox should be removed and replaced with the uptodate version on playstore
Click to expand...
Click to collapse
Thanks
So we can flash it directly with the patched boot and recovery right?
What is the Phone.info? Who does SP Flash tool needs it?
...I couldn't wait so I tried it. It doesn't work. As for May, and September ROMs, I only get a black screens with some strange faded vertical lines. So I restored my previous backup (July ROM).
jy_P said:
...I couldn't wait so I tried it. It doesn't work. As for May, and September ROMs, I only get a black screens with some strange faded vertical lines. So I restored my previous backup (July ROM).
Click to expand...
Click to collapse
Hi,
What doesn't work the rom or the flash via flash tool
phone.info is just for information you need Notepad++ to read it.
Try Flash the rom with the patched boot.img and the system.img only. :fingers-crossed:
After the flash boot to recovery first volume + power and do a full wipe data cache dalvik cache then boot to system
bigrammy said:
Hi,
What doesn't work the rom or the flash via flash tool
phone.info is just for information you need Notepad++ to read it.
Try Flash the rom with the patched boot.img and the system.img only. :fingers-crossed:
After the flash boot to recovery first volume + power and do a full wipe data cache dalvik cache then boot to system
Click to expand...
Click to collapse
The flashing worked. The phone display doesn't work after reboot. I can't even go into recovery.
I tried flashing only the SYSTEM and the BOOT as you asked me, and ...it WORKED!!! :good:
I beleive that all the ROMs I had weir 4.2.1. I am finally having a 4.2.2!
THANKS!
My front camera is still not working though, but that might be an hardware problem with my phone.
jy_P said:
The flashing worked. The phone display doesn't work after reboot. I can't even go into recovery.
I tried flashing only the SYSTEM and the BOOT as you asked me, and ...it WORKED!!! :good:
THANKS!
My front camera is still not working though, but that might be an hardware problem with my phone.
Click to expand...
Click to collapse
:highfive:
[GUIDE] Huawei Y5C | Y541-U02 | Honor Bee : Stock ROMs, ROM Dumping, Root & Flashing
Disclaimer
Upon following this guide, you may or may not achieve same results with others. I am not held responsible for anything unexpected that may happen to your device. Do your research first regarding the areas you do not quite understand. Follow at your own risk.
Prerequisites
Spreadtrum Flash Tool R4.0.0001 (PAC Flashing) or Flashfire (Zip flashing)
SPRD USB Driver (needed for PAC Flashing)
Male to Micro USB Cable (needed for PAC Flashing)
7-Zip
Root with SuperSU (just below, needed for first time Zip flashing)
Packet (*.pac) or Zip ROM (found below)
Rooting
Install and gain root through KingRoot android application.
Restart your phone. (I've encountered a sudden reboot when doing the steps below without this)
Replace KingRoot with SupeSU through this script.
Once the archive is downloaded, extract it. There will be a folder named root where you extract it.
Download and open Terminal Emulator.
Change directory to the root folder that was extracted:
Code:
cd /path/to/root
Then ask for root permissions:
Code:
su
Now run the first script:
Code:
sh level1.sh
Run the second script:
Code:
sh level2.sh
Leave the terminal running and open KingRoot.
Press the button at the upper right corner, and choose general settings.
Scroll down and press uninstall.
Uncheck backup and press OK.
After KingRoot has finished uninstalling, go ahead and uninstall Purify as well.
Go back to the terminal and run the third, last script:
Code:
sh level3.sh
Again leaving the terminal running, install SuperSU and open it.
Let it update the root binary through Normal method, and restart.
Notes:
Currently SuperSU's prompt for applications asking for root permissions does not work, but, changing the setting to "grant" will. Just return it to "deny" afterwards, for security. That's the workaround for now.
Dumping
Before doing anything to your device, it is advised to create a ROM dump/backup beforehand. Also make sure you have a lot of free space on your internal storage.
Open up terminal and gain root permissions:
Code:
su
Then get the partition details:
Code:
ls -al /dev/block/platform/sprd-sdhci.3/by-name
Dump each partition (X) with its name (Y):
Code:
dd =if/dev/block/mmcblk0pX of=/sdcard/Y.img
Do not forget to dump the two bootloaders:
Code:
dd =if/dev/block/mmcblk0boot0 of=/sdcard/splloader.img
Code:
dd =if/dev/block/mmcblk0boot1 of=/sdcard/uboot.img
Flashing
PAC
Extract all the downloaded archives and install the driver (either 32install for 32/86bit or 64install for 64bit OS).
Open the flash tool by double clicking the executable named "ResearchDownload".
Once the flash tool opens, click the single gear button at the top left.
Find and open the PAC ROM.
Press the play button.
Power down the device, hold the volume down button and plug it into the PC.
The flash tool will then recognize the device and start downloading binaries to it.
Once the progress column shows "PASSED", the binary download is finished and the device can now be safely unplugged.
Remove the battery, reinsert, and power the device.
Zip
Gain root if not already done so.
Open Flashfire. (press agree and the other one is up to the user)
Press the red circular button with a plus sign ( + ) on the bottom right, and choose Flash ZIP or OTA.
Find and open the downloaded Zip ROM.
There will be a pop-up for a few settings, leave it as is and press the check icon at the upper right.
Now when the pop-up closes, swipe down and press the Flash button with a lighting icon.
Press OK, and let it flash.
The device will reboot once flashing is finished.
Unbrick Stock PAC ROM
Y541-U02V100R001C567B116
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=HUAWEIY541-U02
ro.build.version.sdk=19
ro.build.version.codename=REL
ro.build.version.release=4.4.2
ro.build.version.security_patch=2016-03-01
ro.build.version.base_os=
ro.build.date=Mon May 23 22:44:32 CST 2016
ro.build.date.utc=1464014672
ro.build.type=user
ro.build.user=
ro.build.host=a7fcf16085c3
ro.build.tags=ota-rel-keys,release-keys
ro.product.model=HUAWEI Y541-U02
ro.product.brand=HUAWEI
ro.product.name=Y541-U02
ro.product.device=HWY541-U
ro.product.board=Y541-U02
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HUAWEI
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=sc8830
# ro.build.product is obsolete; use ro.product.device
ro.build.product=Y541-U02
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=Y541-U02-user 4.4.2 HUAWEIY541-U02 135 ota-rel-keys,release-keys
ro.build.fingerprint=HUAWEI/Y541-U02/HWY541-U:4.4.2/HUAWEIY541-U02/C567B116:user/ota-rel-keys,release-keys
ro.build.characteristics=default
ro.zygote.disable_gl_preload=false
# end build properties
#
# from device/ontim/Y541-U02/system.prop
#
ro.sf.lcd_density=240
ro.sf.lcd_width=54
ro.sf.lcd_height=96
ro.opengles.version=131072
ro.product.hardware=SP7731GEA_V1.0.0
debug.hwui.render_dirty_regions=false
ro.config.hw_showSimName=true
ro.config.hw_hideSimIcon=false
ro.config.coop_stk1comp=com.android.stk1;com.android.stk1.StkLauncherActivity
# Bluetooth OPP low speed for save power
debug.bt.lowspeed=false
persist.ttydev=ttyVUART0
# delay for ConnectivityChange broadcast (ms)
conn.connectivity_change_delay = 0
ro.product.partitionpath=/dev/block/platform/sprd-sdhci.3/by-name/
# Default ecclist
ro.ril.ecclist=112,911,#911,*911
persist.modem.w.enable=1
persist.modem.w.nvp=w
ro.modem.w.dev=/dev/cpw
ro.modem.w.tty=/dev/stty_w
ro.modem.w.eth=seth_w
ro.modem.w.snd=1
ro.modem.w.diag=/dev/slog_w
ro.modem.w.loop=/dev/spipe_w0
ro.modem.w.nv=/dev/spipe_w1
ro.modem.w.assert=/dev/spipe_w2
ro.modem.w.vbc=/dev/spipe_w6
ro.modem.w.id=0
ro.modem.w.fixnv_size=0x40000
ro.modem.w.runnv_size=0x60000
persist.sys.engpc.disable=0
ro.modem.wcn.enable=0
ro.modem.wcn.dev=/dev/cpwcn
ro.modem.wcn.tty=/deiv/stty_wcn
ro.modem.wcn.diag=/dev/slog_wcn
ro.modem.wcn.assert=/dev/spipe_wcn2
ro.modem.wcn.id=1
ro.modem.wcn.count=1
camera.disable_zsl_mode=1
ro.digital.fm.support=1
ro.config.ksm.support=true
#supprot storage path change
ro.storagepath.change.support=true
#supprot quickcamera
ro.quickcamera.support=true
#zram config
ro.config.zram.support=true
ro.board_ram_size=mid
# SPRD: add low cost low memory @{
ro.config.low_ram=true
# @}
#if our product not support drm,set as false
drm.service.enabled=true
# hotspot development
ro.hotspot.enabled=1
# this product does not support bt and softap coexist
ro.btwifisoftap.coexist=true
# SPRD: add support hwrotation
ro.sf.hwrotation=0
#SPRD: add support follow sim system config
persist.support.fssc=1
#SPRD: add for cphs
persist.support.oplpnn=true
persist.support.cphsfirst=false
#SPRD: add support virtualnet
persist.support.virtualnet=true
#ontim:add support huawei wlan setting
persist.huawei.wifi.setting=true
#SPRD: add support encrypt
ro.encrypt.devices.support=0
#SPRD: add support vt
persist.sys.support.vt=false
#SPRD: delete baseband version
ro.show.basebandversion=false
#SPRD: mccmnc config path
ro.mccmnc.info.path=/globalinfo/
#for app can install on sd and primary is internal
ro.storage.installonsd=true
# Audio Dump Information for HAL
audio.dump.show.switch=0
hw-k3-burst-supported=1
# adapter for HuaWei PIN(keyguard apk) added by liulibo
ro.config.is_sprd=true
#avoid gallery function:chang voice pic to video.
ro.config.hw_trans_voiceimage=false
#avoid gallery map function
ro.config.support_gallery_map=false
#wifi_country
ro.config.custCountryEnable=ir,sd,sy,kr
# SPRD: DC lowpower
sys.dc.lowpower=true
ro.systemui.flashlight.timeout=0
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.build.version.incremental=C567B116
ro.product.sw.internal.version=Y541-U02V100R001C567B116_user_30323_160523.223910
ro.product.sw.external.version=Y541-U02V100R001C567B116
ro.build.cust.id=Y541-U02V100R001C567B116
ro.versioninfo.delivery=MocorDroid4.4_TShark28_2341A_W15.16.5
ro.com.android.dateformat=MM-dd-yyyy
ro.carrier=unknown
persist.sys.sprd.modemreset=1
ro.adb.secure=1
persist.sys.sprd.wcnreset=1
ro.xtsdisableverify=1
ro.storage.flash_type=2
keyguard.no_require_sim=true
ro.com.android.dataroaming=false
ro.msms.phone_count=2
persist.msms.phone_count=2
persist.msms.phone_default=0
ro.modem.w.count=2
persist.sys.support.vt=false
sys.usb.gser.count=4
lmk.autocalc=false
persist.sys.data_reserved=100
ro.config.ringtone=Huawei_Tune.ogg
ro.config.ringtone0=Huawei_Tune.ogg
ro.config.ringtone1=Huawei_Tune_Piano.ogg
ro.config.notification_sound=Bongo.ogg
ro.config.alarm_alert=Creamy.ogg
persist.sys.wakeup.enable=0
ro.config.hw_timeformat=true
ro.config.timeformat=24
persist.sys.modem.diag=,none
persist.sys.slog=0
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=96m
dalvik.vm.heapsize=256m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=8m
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=4.4_r7
ro.build.display.id=Y541-U02V100R001C567B116
ro.config.max_starting_bg=3
ro.com.google.clientidbase=android-huawei
ro.com.google.clientidbase.yt=android-huawei
ro.com.google.clientidbase.am=android-huawei
ro.com.google.clientidbase.gmm=android-huawei
ro.com.google.clientidbase.ms=android-huawei
ro.dual.sim.phone=true
ro.config.hw_coop_no_setting=true
ro.config.remove_subscribe_menu=1
ro.config.hw_coop.ontim=true
ro.config.hw_coop.show_Sun=1
ro.config.app_big_icon_size=90
ro.config.hwcust_drawbgicon=false
ro.config.hw_coop_delay=true
ro.config.hwtheme=1
persist.radio.langu.rule=0
data.icon.onlyconnected=true
persist.sys.certification=103323
ro.config.is_support_my=true
ro.product.hwinternal.version=Y541-U02V100R001C567B116
ro.product.hwinternal.ver.time=160523.223910
persist.sys.dalvik.vm.lib=libdvm.so
net.bt.name=Android
ro.floatkey.show=false
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Notes:
These ROMs are repacked and tested first before being posted, so if one of these does not work, try another. If none worked, just wait, others will share a new partition dump.
These ROMs do not contain a system, custom and cache dump because these are for unbricking for now. Prerooted full repacks are coming soon.
Stock ZIPs
Notes:
As the device refuses any custom or modified stock binaries, Flashfire is the only way to go to install zips.
These are pre-rooted, deodexed, zipaligned, de-bloated, and of course tested.
None at the moment.
Troubleshooting
If the flash tool fails to download, either the downloaded ROM is incompatible with the device, or the cable is loose.
If the device shows a white screen but the booting sound is heard, try another one.
Support
If anyone happens to have the same device model in fully working condition but seems to be different, kindly make a partition dump of it and PM the link, so it can be processed and uploaded here.
Credits & Sources
@najoor for the original KingRoot to SuperSU script.
GSM Flashfile Website
@Kingxteam for KingRoot
@Chainfire for SuperSU & Flashfire
Is there any customs available for this device
anil kalyan said:
Is there any customs available for this device
Click to expand...
Click to collapse
As of now, with the bootloader locked, there is none.
In future can we expect the same..........
The closest we can get is a modified stock. In the future, there might, but let us not get our hopes up.
techyzen101 said:
The closest we can get is a modified stock. In the future, there might, but let us not get our hopes up.
Click to expand...
Click to collapse
When can we expect this
Where we are on this Can we expect Lollipop rom anytime
Please provide the lollipop ROM
after flash check download state, last download maybe not complete.
Does anyone have a full file or link .pac file Y541-U02V100R001C567B116 ~ 1.5Gb
Y541-U02V100R001C567B112
I need This version pac file help plz
snmobilecenter said:
after flash check download state, last download maybe not complete.
Click to expand...
Click to collapse
hello can i ask if what can be done when you encouter this error upon power on?
tried flashing with research download and upgrade downgrade tool from spdflashtools.
got it to flash firmware v105. but after flashing, blank screen won't power on. also cannot go to recovery.
tried to flash it again with different version, did not go thru anymore and cannot go through any firmware versions.
stuck at FDL2 failing.
tried android usb drivers and spd /sci drivers still stuck at fdl2
please help.
how to get twrp?
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.