Flashing a new ROM - General Questions and Answers

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

Related

[Q] Help with EKEN T01a

I recently purchased an EKEN T01a and i can't get the thing to respond. While i was installing apps i tried to change the dpi settings from 120 to 150 and now the pop up message i receive on the screen says "Unfortunately, the launcher has stopped". I tried looking for firmware on the net to do a wipe but i have found nothing. If anyone can help i would appreciate it thanks.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A
*** UPDATE 09 May 2012 ***
Finally EKEN has added the links for the T01, T02 and T10 firmwares to his website. They're compatible with T01a T02a and T10a too.
EKEN Support Page
***********************
EKEN T01A Stock ICS Firmware 4.0.3 (v0.8.1 - 2012-02-24)
Finally found, after a long ride : I attach the necessary software and instruction found over the net to flash it. In the firmware file there are further instructions and links, but this is the correct procedure from futeko dot com
Firmware details:
File Name: sun4i_crane_t01a_0.8.1_20120224.rar
Type: Firmware
Manufacturer: Eken
Tablet Name: sun4i_crane_t01a_0.8.1_20120224
Model Number: T01A T01
CPU Name & Model: Allwinner A10
Firmware Date: 2012-02-24
OS Name: ICS
OS Version Number: 4.0.3
Firmware Type: Stock
Flashing Instructions:
Q: How to flash firmware (also known as a 'ROM') on the Eken T01 and T10 (and T01A)?
A: This is a fiddly process so some perseverance might be required. It will work in the end. From user reports it seems to work most smoothly on the 32bit version of Windows XP. Instructions:
- Firmware must be flashed using a Windows application called Livesuit. Download it from the link below.
- Once downloaded, and before attaching your tablet to your PC, run the file 'LiveSuitPack_version_1.09_20111101.exe' from within the Livesuit folder. This should install a new device on your system (VID_1f3a_PID_efe8). This device may show with an exclamation mark in Windows Device Manager, this doesn't matter and can be ignored.
- Now download the firmware image you want to install. Firmwares are linked to in the downloads section to the left. After decompressing the archive you will end up with a .img file (e.g. 'sun4i_crane_t01a_0.8.1_20120224.img'). This is the firmware/ROM image that you are going to flash (or copy) to the tablet.
- Without attaching your tablet to your PC run 'LiveSuit.exe' from within the Livesuit folder. You should get an application with 6 icons.
- You will be asked if you want to be guided through the process, select no.
- Click on the leftmost icon (a cube), browse to your downloaded firmware image, and select it.
- Now attach your tablet to your PC by USB cable whilst holding down the volume+ button on the top. Straight after attaching the cable, and whilst still holding down the volume+ button, start pressing the tablet power button repeatedly. This (slightly frenzied) procedure puts the tablet into update mode.
- After a few seconds you will be asked if you want to perform a forced firmware update. Select yes. You will be asked if you're sure. Select yes.
- The update will start. You can release volume+ at this point.
- The update should take approx 3 minutes to complete. You will see a % complete progress bar during the process and will get a dialog saying OK when it's done.
- Turn your tablet on and you will have the new firmware.
Click to expand...
Click to collapse
Live Suit Pack v1.09 Link: Download / Mirror
EKEN T01A Firmware Link: Download
New Firmwares:
EKEN FTP Link: EKEN Public FTP
------------------------------------------------------------------------------------
ROOT Instructions & Script (windows):
PELASE READ CAREFULLY BEFORE PROCEED!!!
DOWNLOAD: Mediafire.com - BalTac-EKEN-RootScript
Instructions and script are fully based on the work of MrTasselhof for Ainol Novo 7 Advanced, from slatedroid forum. My only work was to adapt (I've deleted the uneeded part of the code from the .BAT file) and test the script for EKEN T01a Tablet. Maybe it just work even for other eken devices. Please feedback.
MrTasselhof said:
This is a straightforward script.
It's sole purpose is to get your device rooted and provide the tools to verify it.
------------------------------------------------------------------------------------
**IMPORTANT PRE-CHECK LIST**
Connect your tablet using the OTG port (normal procedure)
- YOU MUST USE THE INCLUDED USB CABLE
Make sure USB Debugging is ENABLED
- Settings --> Applications --> Development --> USB debugging (Green Checkmark)
Make sure to check Device Manager to ensure that there aren't any devices with a yellow exclamation mark.(WARNING: the eken tablet HAVE one of the drivers with an exclamation mark: please, just ignore it )
- Right Click on My Computer --> Manage Device --> Device Manager
Here is a link to a driver package I created... (I didn't need to use them. Drivers suited with LiveSuitPack are enough, but just in case...)
- Download Link: Mediafire.com - Android USB Multiple Driver Pack
-----------------------------------------------------------------------
Instructions:
Extract the folder to ANY location you wish. (it is self contained)
Run !RUN-ME-BalTac-RootScript.bat
You will be given the following prompt:
Make sure to enable USB Debugging on the tablet
- Settings -) Applications -) Development -) USB debugging (green checkmark)
'
1. Check Tablet Connection
2. Verify Tablet is ROOT Capable (with this script)
3. Run ROOT Script
'
4. Quit
'
Choose Option (1 thru 4):
Option 3 Performs the actual ROOT process.
- It also installs the following programs: (don't worry if they are already installed)
* Superuser
* Root Checker
* Root Explorer
* Busybox
Watch the magic happen
Enjoy!
Tasselhof
Click to expand...
Click to collapse
------------------------------------------------------------------------------------
EDIT.:Zero Size Internal Storage Problem and the step taken to fix it.
(source.:http://forum.xda-developers.com/showpost.php?p=29800946&postcount=78 )
Got the same problem. After reset, storage size become Zer0!. Fixed it by doing this:
1. Put a copy of term.apk into my memory card.
2. Run file manager and locate term.afk, run it to install.
3. Open terminal emulator and got nice prompt. Alas don't get the sharp prompt (#)
***ROAD BLOCK*** Need to root the tablet first.
4. Grab Tesselhof script (Tasselhof - Root, Market, Build.Prop, & Tweaks Script - AllWinner A10)
5. Install PdaNetA350.exe just to be sure that the tablet connect....
6. Run Tesselhof. Da*n, did not work 100%. Continue with option 2,3,4,5 in Tesselhof. Reboot the tablet.
7. Rerun Tesselhof. Option 2,3,4,5 again! Success!!
8. Reinstall term.afk and running it...
9. Execute the god command "su" !! Yes.... got the sharp prompt! Hehe (#)
10. Typing this one liner to fix Zero size storage
cp /system/xbin/busybox /system/bin
Pressing enter and rebooting the tablet.
FIXED!!
File location:
Term.apk http://cloud.github.com/downloads/jackpal/Android-Terminal-Emulator/Term.apk
Tesselhof script:Tasselhof - Root, Market, Build.Prop, & Tweaks Script - AllWinner A10.rar (Link Broken: use mine above)
PdaNet: http://pdanet.co/bin/PdaNetA350.exe
Did not work on Eken T10
Hi,
I try this procedure on my Eken T10 and did not worked at all....even worst my tablet now boots to a black screen.... bricked !!!
any suggestions or ideas ???
Tried the procedure several times and no luck
freakma said:
Hi,
I try this procedure on my Eken T10 and did not worked at all....even worst my tablet now boots to a black screen.... bricked !!!
any suggestions or ideas ???
Tried the procedure several times and no luck
Click to expand...
Click to collapse
Maybe you are using the wrong firmware. this one is intended for EKEN MID T01A 7". Yours is the 10" tablet EKEN MID T10. But don't worry: There is a link that you can find in the guide that come with the previous firmware. Is an eken FTP space where are stored the latest firmware for T01A, T02A and T10A (and I suppose they are even compatible for T01, T02 and T10). Let's have a try. If this one won't work I'll try to find the specific T10 firm.
EKEN FTP link: CLICK
user: down
pass: down
Site Changed:
EKEN FTP Link: EKEN Public FTP
EDIT.: To download the files I must have to use Filezilla. With the normal browsing I've no success in downloading.
info on t01a
hi big big thnx, im use to flashing as ive done same to my sgs n sgs2 . been looking for info all day on about this n very little or even not cross referenced. i just bought her indoors a 7" android tab mid-t01a and kept getting a ' android.process.acore error ' it ended up being that the contacts apk wasnt installed . so found this link that help me out
pandawillforum.com/showthread.php?10059-i-need-eken-T01-firmwire
also here's the link for contacts apk
mediafire.com/?vhs5o5bigkadsma
anyways i thought i'd share my little bit of know how to everyone else
just in case ...
cheers again n1kman
Hello, just wondering if the 7" you mentioned firmware for in this post is the same as the MID-T01a available at geeks.com, amazon, ect
Here is one picture. I just searched for MID-T01A and found this post.
{
"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"
}
Trying to figure out if there is any community/manufacturer support for this tablet, and if it is worth purchasing.
Banyon said:
Hello, just wondering if the 7" you mentioned firmware for in this post is the same as the MID-T01a available at geeks.com, amazon
[...]
Trying to figure out if there is any community/manufacturer support for this tablet, and if it is worth purchasing.
Click to expand...
Click to collapse
I think that Is the same device, but for now I haven't find any community that give an exaustive support to the tablet. There is something compatible in communities that develop for Ainol tablets, like slatedroid forum (some app and scripts. but don't use Ainol custom firmwares: they aren't compatible and will brick your device!!!). If you only need to ROOT that tablet you can try this using only the first 3 options (others might cause the tablet stop working or give some error):
Tasselhof ROOT script
If this external link is not allowed, I ask the moderators to warn me and I will report here the entire guide and the necessary files.
Hi,
Would you happen to be able to find T02's firmware? Eken's official FTP is extremely slow and impossible to download from.
T01's firmware doesn't work
mwerkz said:
Hi,
Would you happen to be able to find T02's firmware? Eken's official FTP is extremely slow and impossible to download from.
T01's firmware doesn't work
Click to expand...
Click to collapse
I've found this one (I can't try it so I'm not sure if it's a true T02 Fw): EKEN T02 Firmware 2012/04/07 - DOWNLOAD
But the download manager say to me that is an FTP transaction and the download is extremely slow (ETA: about 2 hours). If you want I can download it and reup in my mediafire account.
baltac said:
I've found this one (I can't try it so I'm not sure if it's a true T02 Fw): EKEN T02 Firmware 2012/04/07 - DOWNLOAD
But the download manager say to me that is an FTP transaction and the download is extremely slow (ETA: about 2 hours). If you want I can download it and reup in my mediafire account.
Click to expand...
Click to collapse
Hi!
Would appreciate if you caould do that, even from the link, the estimated download that's showing is 10days.......
*** UPDATE 09 May 2012 ***
Finally EKEN has added the links for the T01 T02 and T10 firmwares to his website. They're compatible with T01a too.
EKEN Support Page
***********************
mwerkz said:
Hi!
Would appreciate if you caould do that, even from the link, the estimated download that's showing is 10days.......
Click to expand...
Click to collapse
EKEN T02a Original Firmware
Android v4.0
Release Date: 2012/04/07
Mediafire.com - DOWNLOAD
Flasher:
LiveSuitPack v1.09 (USB drivers included)
Mediafire.com - DOWNLOAD
Flashing and ROOTing instructions: HERE
Useful Info:
mwerkz said:
This is the exact firmware I had before the brick. Finally got the device working again after two weeks of searching!
PS: It may be just me but it's good to know that installing the ICS Hide status bar hack (replacing android.policy.jar and Settings.apk) will not let the T02 boot pass the android screen.
Click to expand...
Click to collapse
baltac said:
EKEN T02a Original Firmware
Android v4.0
Release Date: 2012/04/07
DOWNLOAD
Flasher:
LiveSuitPack v1.09 (USB drivers included)
DOWNLOAD
Flashing and ROOTing instructions: HERE
Please, let me know if this is the right fw for you and if the ROOT work even in this tablet.
Click to expand...
Click to collapse
THANK YOU FOR THE LINK!
This is the exact firmware I had before the brick. Finally got the device working again after two weeks of searching!
Really appreciate the time and help you have rendered!
PS: It may be just me but it's good to know that installing the ICS Hide status bar hack (replacing android.policy.jar and Settings.apk) will not let the T02 boot pass the android screen.
has anyone tried this?
Hi, can anyone confirm that this is working?
also has anyone tried the v6 supercharge script on this tablet?
whiz_gadgetz said:
Hi, can anyone confirm that this is working?
Click to expand...
Click to collapse
For T01a I confirm for sure. Tested by myself.
For the T02a read the mwerkz post:
mwerkz said:
THANK YOU FOR THE LINK!
This is the exact firmware I had before the brick. Finally got the device working again after two weeks of searching!
Click to expand...
Click to collapse
whiz_gadgetz said:
also has anyone tried the v6 supercharge script on this tablet?
Click to expand...
Click to collapse
Haven't tried the supercharge script, sorry. If you test it, please report your feedback.
hi baltac..
i got eten t01a tablet. recently i edit the build.prop for the tablet. after reboot my tablet got stuck at android loading page. i push volume + and power button then the tablet loading to android system recovery 3e page. got message reboot system now, apply update from external storage, factory reset, wipe cache partition, apply update from cache. i try to select to factory reset nothing happen. can i use the firmware and steps which you post at first page to recover back my tablet? pls advice. tq
bellow is my previous builb prop before my tablet got stuck at start up screen.
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=IML74K
ro.build.display.id=crane_evb-eng 4.0.3 IML74K 20120224 test-keys
ro.build.version.incremental=20120224
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=2012年 02月 24日 星期五 10:20:44 CST
ro.build.date.utc=1330050044
ro.build.type=eng
ro.build.user=pshu
ro.build.host=Ingen-cross
ro.build.tags=test-keys
ro.product.model=T01A
ro.product.brand=softwinners
ro.product.name=crane_evb
ro.product.device=crane-evb
ro.product.board=crane
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=unknown
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=crane-evb
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=crane_evb-eng 4.0.3 IML74K 20120224 test-keys
ro.build.fingerprint=softwinners/crane_evb/crane-evb:4.0.3/IML74K/20120224: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.heapsize=48m
ro.kernel.android.checkjni=0
persist.sys.timezone=GMT-8
persist.sys.language=en
persist.sys.country=US
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
persist.sys.usb.config=mass_storage,adb
ro.sf.lcd_density=120
ro.product.firmware=0.8.1
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
hi.. ialready download the EKEN T01A Firmware but got message the file was corrupt when i try to open the img file. the file size about 105 mb.. pls help.
Thanks Baltac
will do =)
Thanks
Thanks for the files and instructions. They will be a great help.
Manage to boot up my eken after I download latest firmware from eken website. Latest update include the market enablers as well as flash support.

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.

[GUIDE] Huawei Y5C | Y541-U02 | Honor Bee : Stock ROMs, ROM Dumping, Root & Flashing

[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?

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.

HA3_PX5_10.0_ota(2020/07/06) HA/Dasaita

Android 10.0 version from HA/Dasaita for PX5 Head Units.
Enjoy
Download:
Fast --> Download
build.prop:
Code:
# begin common build properties
# autogenerated by build/make/tools/buildinfo_common.sh
ro.system.build.date=Mon Jul 6 21:04:48 CST 2020
ro.system.build.date.utc=1594040688
ro.system.build.fingerprint=rockchip/rk3368/rk3368:10/QQ2A.200305.004.A1/hct07062104:userdebug/test-keys
ro.system.build.id=QQ2A.200305.004.A1
ro.system.build.tags=test-keys
ro.system.build.type=userdebug
ro.system.build.version.incremental=eng.hct.20200706.211222
ro.system.build.version.release=10
ro.system.build.version.sdk=29
ro.product.system.brand=rockchip
ro.product.system.device=rk3368
ro.product.system.manufacturer=rockchip
ro.product.system.model=PX5
ro.product.system.name=rk3368
# end common build properties
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=QQ2A.200305.004.A1
ro.build.display.id=rk3368-userdebug 10 QQ2A.200305.004.A1 eng.hct.20200706.211222 test-keys
ro.build.version.incremental=eng.hct.20200706.211222
ro.build.version.sdk=29
ro.build.version.preview_sdk=0
ro.build.version.preview_sdk_fingerprint=REL
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=10
ro.build.version.security_patch=2020-05-05
ro.build.version.base_os=
ro.build.version.min_supported_target_sdk=23
ro.build.date=Mon Jul 6 21:04:48 CST 2020
ro.build.date.utc=1594040688
ro.build.type=userdebug
ro.build.user=hct
ro.build.host=r930
ro.build.tags=test-keys
ro.build.flavor=rk3368-userdebug
# 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.wifi.channels=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=rk3368
# Do not try to parse description or thumbprint
ro.build.description=rk3368-userdebug 10 QQ2A.200305.004.A1 eng.hct.20200706.211222 test-keys
# end build properties
#
# from device/rockchip/rk3368/system.prop
#
#
# system.prop
#
ro.ril.ecclist=112,911
rild.libpath=/vendor/lib64/libril-rk29-dataonly.so
rild.libargs=-d /dev/ttyACM0
vendor.rild.libpath=/vendor/lib64/libril-rk29-dataonly.so
vendor.rild.libargs=-d /dev/ttyACM0
# end of device/rockchip/rk3368/system.prop
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.bionic.ld.warning=1
ro.treble.enabled=true
persist.debug.dalvik.vm.core_platform_api_policy=just-warn
dalvik.vm.lockprof.threshold=500
net.bt.name=Android
Root? )
-Monty- said:
Root? )
Click to expand...
Click to collapse
No Root at the moment for Android 10 MTCE Devices
1- What is the difference from HCT4, HLA and HA3?
2- My radio is dasaita but any of these 3 roms are compatible right?
3- all roms include day and night mode?
Regards.
JonatanP said:
1- What is the difference from HCT4, HLA and HA3?
2- My radio is dasaita but any of these 3 roms are compatible right?
3- all roms include day and night mode?
Regards.
Click to expand...
Click to collapse
1. Look at the screenshots. It's almost the UI.
2. Yes!
3. No. Only the MX/Witson ROM.
jamal2367 said:
1. Look at the screenshots. It's almost the UI.
2. Yes!
3. No. Only the MX/Witson ROM.
Click to expand...
Click to collapse
3. The dasaita rom have a night mode, if you have activate ngiht mode in your google acount with android 10 the googles app are all in night mode, also the seettings and others thinks. Don't have a day and night mode like Mx/witson with the launcher, music or bluetooth.
segu45 said:
3. The dasaita rom have a night mode, if you have activate ngiht mode in your google acount with android 10 the googles app are all in night mode, also the seettings and others thinks. Don't have a day and night mode like Mx/witson with the launcher, music or bluetooth.
Click to expand...
Click to collapse
That's what I meant.
jamal2367 said:
That's what I meant.
Click to expand...
Click to collapse
:good:
Screenshots
I installed it, tried it, it works well!
Here are some screenshots.
Doky1988 said:
I installed it, tried it, it works well!
Here are some screenshots.
Click to expand...
Click to collapse
Can you do me a favor? Can you extract the amp,file browser, Bluetooth and radio apks from this rom.
Guys sorry, can I install this on my px5 mtce_lm? Or is it better wait Android 10 from erisin/lm?
Francex10 said:
Guys sorry, can I install this on my px5 mtce_lm? Or is it better wait Android 10 from erisin/lm?
Click to expand...
Click to collapse
I installed HCT4 on my PX5 MTCE_LM.
Was A9. InstallModPro help me for upgrade to A10
Android 10 is very Good as well as GPS.
Can't install this update
Hi guys,
I have an RK3368 octa core PX5 device currently running Android 9. I've tried to install this update, but am getting an error. The process starts, but then the recovery screen appears. The sequence of messages reads :-
Verifying Update Package...
Update package verification took 46.2 s (result 0).
Installing update...
Target: rockchip/rk3368/blah blah blah
assert failed: update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list")
E:Error in /mnt/usb_storage/update.zip (Status 7)
Installation aborted
I then need to reboot.
When I insert the USB card and the system picks up the update file, there is an option to format the device - I'm not selecting that. Do I need to tick the box to format the device ? Or does anyone have any ideas whet the issue might be ?
Thanks.
Archbishop666 said:
Hi guys,
I have an RK3368 octa core PX5 device currently running Android 9. I've tried to install this update, but am getting an error. The process starts, but then the recovery screen appears. The sequence of messages reads :-
Verifying Update Package...
Update package verification took 46.2 s (result 0).
Installing update...
Target: rockchip/rk3368/blah blah blah
assert failed: update_dynamic_partitions(package_extract_file("dynamic_partitions_op_list")
E:Error in /mnt/usb_storage/update.zip (Status 7)
Installation aborted
I then need to reboot.
When I insert the USB card and the system picks up the update file, there is an option to format the device - I'm not selecting that. Do I need to tick the box to format the device ? Or does anyone have any ideas whet the issue might be ?
Thanks.
Click to expand...
Click to collapse
You need the Android 10 recovery to install this.
You can find it here:
http://hal9k.ru/?page_id=207
Jamal,
Thanks - I've purchased the recovery tool, and upgraded successfully. Actually it was a breeze using the recovery tool, made it really easy !
Thanks again.
jamal2367 said:
You need the Android 10 recovery to install this.
You can find it here:
[l]
Click to expand...
Click to collapse
People can also try the upgrade to Android 9 or 10 using manufacturer free tools and the ROM .img file - an OTA ZIP wont work.
This is how the manufacturer does it.
See my thread.
---------- Post added at 07:36 AM ---------- Previous post was at 07:34 AM ----------
Archbishop666 said:
Jamal,
Thanks - I've purchased the recovery tool, and upgraded successfully. Actually it was a breeze using the recovery tool, made it really easy !
Thanks again.
Click to expand...
Click to collapse
Also see thread regarding upgrading to Android 10 using free tools.
marchnz said:
People can also try the upgrade to Android 9 or 10 using manufacturer free tools and the ROM .img file - an OTA ZIP wont work.
This is how the manufacturer does it.
See my thread.
---------- Post added at 07:36 AM ---------- Previous post was at 07:34 AM ----------
Also see thread regarding upgrading to Android 10 using free tools.
Click to expand...
Click to collapse
It doesn't work on any head unit.
jamal2367 said:
It doesn't work on any head unit.
Click to expand...
Click to collapse
I think you mean, not all units have a GPS sdcard slot. Often these are hidden and internal to the unit.
The factory methods do work where the unit has an SDcard, id 0/1 USB or use OTG.
Furthermore, some units have OTG without mods by simply connecting a USB-USB. In fact it will work for any rockchip headunit, but must use the correct manufacturer type .IMG.
E.g. all MTCD/E use HCT type or MTCD/E images from HA, GS,
marchnz said:
I think you mean, not all units have a GPS sdcard slot. Often these are hidden and internal to the unit.
The factory methods do work where the unit has an SDcard, id 0/1 USB or use OTG.
Furthermore, some units have OTG without mods by simply connecting a USB-USB. In fact it will work for any rockchip headunit, but must use the correct manufacturer type .IMG.
E.g. all MTCD/E use HCT type or MTCD/E images from HA, GS,
Click to expand...
Click to collapse
Also with GPS slot it doesn't work with some of them and the method with USB A to A doesn't work either, there is only the OTG variant which not everybody has and you have to remove the radio from the car first.
The Mod Installer Pro from hal9k_ is better suited and less complicated.
jamal2367 said:
Also with GPS slot it doesn't work with some of them and the method with USB A to A doesn't work either, there is only the OTG variant which not everybody has and you have to remove the radio from the car first.
The Mod Installer Pro from hal9k_ is better suited and less complicated.
Click to expand...
Click to collapse
When people have money, they will pay for what they like and feel the best, the easiest. For example, they like Rom Dasaita but do not have the img file, if using the free tool, they must download another img file of another company to install, then be able to install the rom with their favorite ota file. They pay for time wasted and spend that time to experience, to do other things and make more money for them, haha

Categories

Resources