Related
The Acer Iconia Toolkit is supporting following devices at the moment:
B1-A71
B1-710
B1-A710
B1-711
B1-720
A1-810
A1-811
A3-A10
Liquid S1
Only use these methods if you are sure the device cannot be rooted using a custom recovery from the following thread:
http://forum.xda-developers.com/andr...ax-b1-t2875894
Intel based devices will not be supported ever by this toolkit! Only Mediatek chips are supported!
At the moment the following features are available:
Root from scratch (Unix only / recommended)
Root with prerooted Image (see Download links at the bottom)
Unroot
Swap External <-> Internal SD
Odex ROM
Pull system.img.gz off your device
Download Acer Iconia Toolkit Latest Version
Older Versions:
v0.9.0
v0.8.5
v0.8.4
v0.8.3
v0.8.2
Thank you goes to:
FireDiamond, bullbrand, pawitp, alba81, sodaFR, MatrixDJ96, ak6, min-dfreak, Gilly10, agentdeep, nick_1964, sampod
and the testers
Acer Iconia B1-A71:
Unlock Bootloader
CWM update, that removes bloat
thx to FireDiamond
Apply the "Invalid Partition Error" fix before rooting!!!
To avoid unfixable bootloop, first apply this patch from Acer.
Install the APK, start it, click on FixG1PMT (no feedback) and uninstall afterwards. Good luck!
If you're rooting with prerooted system.img.gz here are the Downloads. Pick the one, fitting to the firmware installed on your tablet, otherwise you will get into bootloop!
RV03RC05:
Acer Firmware Update [mirror] [mirror + md5]
RV04RC04:
[system.img.gz] [mirror]
RV05RC05:
Acer Firmware Update [mirror1] [mirror2] [mirror3] [mirror4 + md5] [mirror5 + md5]
[system.img.gz]
RV02RC12:
system.img.gz
Acer Iconia B1-710 / B1-A710:
Unlock Bootloader (thx to FireDiamond and abstrkt1337)
RV04RC01:
system.img.gz [mirror1] [mirror2]
Stock system Images for B1-710 RV04RC01
Hamza91: stock, rooted
RV04RC01_PA_CA:
Stock and Rooted system image
Acer Iconia B1-711:
RV01RC04_WW_GEN1:
system.img.gz
Acer Iconia B1-720:
RV03RC01_WW_GEN1:
system.img.gz (thx to Hayastan)
RV07RC01_WW_GEN1:
system.img.gz (thx to Hayastan)
Acer Iconia A1-810:
Acer Firmwares
Modified XPosed Installer
RV03RC08:
system.img.gz
RV18RC07_WW_GEN1:
update.zip (about 4MB)
system.img.gz with /system RW workaround (MD5 = 214db984aee42ef0c05d1cfa43d193c1) (needs extra config and SuperSU instead of Superuser) [torrent] (see this post also)
RV21RC02_WW_GEN1:
update.zip
system.img.gz with /system RW workaround (needs extra config and SuperSU instead of Superuser) (see this post also)
RV21RC03_TWN:
system.img.gz with /system RW workaround (needs extra config and SuperSU instead of Superuser) (see this post also)
RV27RC02_PA_CA:
stock system.img.gz (rename to system.img.gz first!)
system.img.gz (rename to system.img.gz first!)
RV27RC03_WW_GEN1:
system.img.gz
stock system.img.gz
update.zip
RV18RC10_PA_CA:
system.img.gz with /system RW workaround (needs extra config and SuperSU instead of Superuser) (see this post also)
RV26RC06_PA_CUS1:
system.img.gz
Stock Images: (Workaround to unroot: Put the system.img.gz of your version into system_image and choose root option in toolkit)
RV03RC08:
system.img.gz
RV18RC07:
system.img.gz ( MD5=550ECDB192F5668264B11B1070F4B932 )
How to root from scratch
Acer Iconia A1-811:
RV01RC11_WW_GEN1:
Acer Firmware Update
RV02RC20:
system.img.gz rooted and stock (including xposed) (thx to konsolen!!)
RV02RC22_TWN_GEN1:
system.img.gz with /system RW workaround (needs extra config and SuperSU instead of Superuser) (see this post also)
Unbrick:
Stock Firmware RV01RC11 (copy on SD and flash from recovery)
Acer Iconia A3-A10:
A3-A10_RV05RC01_PA_CA:
stock system image
Your device not listed above?
Help us getting your device to work with the toolkit.
See this post how you can help.
Common
B1-A71 / B1-710 / B1-A710: Install this after rooting: Superuser App on Google Play Store
A1-810 / A1-811 / B1-711: Install this after rooting: SuperSU App on Google Play Store
Verify your root: Root Checker on Play Store
FAQ
Q: I'm stuck inside a bootloop after rooting!!!11
A1: The system.img.gz you applied, wasn't suiting to the firmware version installed on your tablet. Download latest Acer firmware update ( !!! if available !!!), copy it on a micro sd card, plug it into your Iconia, go to recovery by holding Volume up and Power button while device is turned off. Then choose apply update from sd card.
A2: If you cannot apply any Acer firmware, because you always get a partition error while installing, you should do a reboot after you get the error. A user reported that this made her/his device boot into Android again, showing the new version in settings -> info. Good luck
A3: If your device is really bricked you could try bring it back to life. Here you find help: link1, link2, link3, link4 (many thanks to Gilly10, drmad and Hamza91)
A4 (B1-A71, B1-710, B1-711 only): Unbrick
A5: If the A1 - A4 didn't help. Send back the device to Acer. Tell them you tried to apply an update from sd card and ended up in this bootloop. Sending device back to Acer over UPS is free. Good luck!
Q: Successfully rooted, but still no root after rebooting!
A: Have you installed Superuser App from Google Play Store?
(B1-A71 only)Q: Cannot update, always getting ERROR: - Invalid partition setting; 17: fat 238e8000:888e8000; Instalation aborted.
A: Download "Invalid Partition Error" Patch.
(B1-A71 only)Q: I applied update from RV05RC05 to RV05RC06 but still it shows RV05RC05.
A: There is no RV05RC06. It is the RV05RC05. It got on Acers Download section with a RV05RC06 named zip file. But the content is 100% equal to RV05RC05.
Q: Toolkit fails or crashes for any reason and I don't know what to do.
A: Run it again with parameter -d, e.g.: toolkit.exe -d and post the entire output here.
Q: Root from scratch on Linux doesn't work because of Error message: 'No such file or directory bin/posix/64/adb'
A: sudo apt-get install ia32-libs libstdc++6 libgcc1 zlib1g libncurses5 libsdl1.2debian
Q: Can i flash a custom recovery?
A: No, because bootloader is locked. You would brick your tablet.
Q: Are there Custom ROMs?
A: No, see answer above.
Q: Is my data wiped during root?
A: No.
Q: Do i lose root after factory reset or wipe date?
A: No.
Q: I get an error in Engineer mode entering telnet command.
A: If Swiftkey is installed / enabled try settings Google AOSP Keyboard as default.
Q: How can I start telnet server manually?
A: Try this.
What you can do with root:
Apply Supercharger V6 by zeppelinrox and significally speed up your tablet! [My small How-To]
Install Adaway, an ad-blocker for webbrowsers and apps containing ads.
Install ROM Toolbox and customize boot screen and other funny things.
Install Titanium Backup to Backup, Freeze, Uninstall any App and more.
Install Datasync to sync app data like save states between rooted devices.
What you can NOT do with root on these devices:
Change DPI
Flash Custom Recoveries
Flash Custom ROMs
Sources and Changelos @ github (thanks to nikagl)
Changelog:
v0.9.4
======
- Updated SuperSU to 2.46
- Removed Xposed APK
- Added Liquid S1 support!
v0.9.3
======
- Fix Xposed removal
- Wait longer for MTKLogger to press settings
- Add 811 and KK 810 and 811 to root from system.img
v0.9.2
======
- Removed Xposed till it works
- Add global for allatonce
v0.9.1
======
Added option to enable write access to external sdcard
Added comment for Xposed not working
Removed su delete command in invalid section
v0.9.0
======
- A1-811: Kitkat Support
- A1-xxx: Added proper su-binary
- Added timestamps
- Added descision for Superuser/Supersu
- Added selection for Xposed **not working yet**
- Added option to enable write access to external sdcard
- Added selection to continue automatically (also import the system instead of waiting for enter)
- Removed invalid quote and double exit command
- Added forward delete of characters to make sure Run command is empty
- Added some additional messages during the root process
v0.8.5
======
- A1-810: Fixed target directory for system image (no permissions for /cache directory since Kitkat)
- A1-810: Fixed root from scratch for Kitkat versions (thanks to Just_Another_N00b)
v0.8.4
======
- A1-810: Fixed root for Android Kitkat >= 4.4.2
- A1-810: Fixed abd devices id, changed sind Kitkat update
v0.8.3
======
- Fixed pulling system.img.gz from Windows
v0.8.2
======
- New: Supporting B1-720
v0.8.1
======
- A1-81x: Fixed missing read/write permissions for /system partition (thanks
to twu2!)
- All other devices: fixed missing path to su binary (thanks to arzakon.nn)
v0.8.0
======
- New: Pull system.img.gz from your tablet
- New: Supporting A3-A10
v0.7.8
======
- fixed Swap Internal to External for A1 and B1-710
v0.7.7
======
- Supporting Swap Internal to External for A1 and B1-710
- fixed bug in root from scratch: checking for /bin/su although it's not there
Full Changelog inside the Download.
Error "Permision denied"
entonjackson said:
Changelog:
v0.2.1
======
- Windows: Providing an .exe, so Python is no more needed for Windows users. But you could still use the Python script.
- Unix: Python3 compatibility fixes
v0.2.0
======
- supporting windows 64 and 32 bit (only for rooting with prerooted system.img.gz)
- Linux: added option to choose between 'Root from scratch' and 'Root from prerooted image'
- supporting all versions between python 2.7.4 and 3.3
v0.1.1
======
- supporting linux 64 AND 32bit
- instructions at the beginning
- make compatible to python 3.3
v0.1.0
======
- initial release, only supporting linux 64bit
Click to expand...
Click to collapse
Hi Thanks for your effor and sharing with us.
I got error "failed to copy system._image\system.image.gz to cache/system.image.gz , permission denied
can you give me solution.
thanks very much
cakadut said:
Hi Thanks for your effor and sharing with us.
I got error "failed to copy system._image\system.image.gz to cache/system.image.gz , permission denied
can you give me solution.
thanks very much
Click to expand...
Click to collapse
Windows or Linux?
edit: Ok i found the issue, I just fixed it and going to upload a new version this evening.
New version v0.2.2 is up.
entonjackson said:
New version v0.2.2 is up.
Click to expand...
Click to collapse
I thanks for your work.
I have one problem
failed to copy 'system_image\system.img.gz' to '/cache/system.img.gz': Permissio
n denied
Traceback (most recent call last):
File "easy_root_iconia_b1.py", line 724, in <module>
else:
File "easy_root_iconia_b1.py", line 26, in main
win_main(python3)
File "easy_root_iconia_b1.py", line 642, in win_main
out = p.stdout.readline()
File "subprocess.pyc", line 575, in check_output
subprocess.CalledProcessError: Command ' bin\windows\32\adb.exe push system_imag
e\system.img.gz /cache' returned non-zero exit status 1
Thanks for your futur help
sorry for my english
V0.2.2 still Error
entonjackson said:
New version v0.2.2 is up.
Click to expand...
Click to collapse
Dear Eaton,
after dowbload and run v0.2.2 , still found same problem.
No Progress bar during copy image.
and system shown
failed to copy 'system_image\system.img.gz' to '/cache/system.img.gz': Permissio
n denied
Traceback (most recent call last):
File "easy_root_iconia_b1.py", line 724, in <module>
else:
File "easy_root_iconia_b1.py", line 26, in main
win_main(python3)
File "easy_root_iconia_b1.py", line 642, in win_main
out = p.stdout.readline()
File "subprocess.pyc", line 575, in check_output
subprocess.CalledProcessError: Command ' bin\windows\32\adb.exe push system_imag
e\system.img.gz /cache' returned non-zero exit status 1
Note I am using windows 7.- 64 Bit
Regards,
I uploaded a new version where I added some commands that hopefully resolve the permissions issues.
The problem is, that I can't reproduce it.
Are you rooting the Iconia the first time? or did you already have root before?
Regarding the progress bar. It only appears when writing the system.img.gz
I have Windows 7 64 bit, btw.
entonjackson said:
I uploaded a new version where I added some commands that hopefully resolve the permissions issues.
The problem is, that I can't reproduce it.
Are you rooting the Iconia the first time? or did you already have root before?
Regarding the progress bar. It only appears when writing the system.img.gz
I have Windows 7 64 bit, btw.
Click to expand...
Click to collapse
Dear Enton,
Yes this is the first time B1 will rooting,
I will try again, and report to you,
Regards
cakadut said:
Dear Enton,
Yes this is the first time B1 will rooting,
I will try again, and report to you,
Regards
Click to expand...
Click to collapse
Dear Enton,
The Messages still same, I Attached the Error Pic.
Note :
Iconia B1-A71
ROM 16 GB
RAM 512 MB
Android Version : 4.1.2
Kernel Version : 3.4.0
Image Version : Acer_AV051_B1-A71_RV05RC05_WW_GEN1
Build Number : Acer_AV051_B1-A71_1.258.00_WW_GEN1
Regards,
cakadut said:
Dear Enton,
The Messages still same, I Attached the Error Pic.
Note :
Iconia B1-A71
ROM 16 GB
RAM 512 MB
Android Version : 4.1.2
Kernel Version : 3.4.0
Image Version : Acer_AV051_B1-A71_RV05RC05_WW_GEN1
Build Number : Acer_AV051_B1-A71_1.258.00_WW_GEN1
Regards,
Click to expand...
Click to collapse
I will try to fix it asap. The problem is, that I cannot reproduce it.
I assume that the chmod 777 /cache command that I do, before the adb push command fails with "Operation not permitted."
But this I still don't know how to fix. If someone knows, tell me!
error in v.0.2.3
Dear entonjackson,
thanks for your work and for the time you spend on it.
Unfortunately, I too have problems with the tool for Windows since version 0.2.0 and also with the latest version (0.2.3).
The error messages that I receive are identical (with the same line numbers) to those receiving cakadut in his last post.
I am trying to root Iconia for the first time.
I tried with Windows 7-32bit and Windows 7 64-bit.
My configuration:
Iconia B1-A71 8GB ROM, 512Mb ram
Android 4.1.2
kernel 3.4.0
Image version: Acer_AV051_B1-A71_RV04RC04_WW_GEN1
Build Number: Acer_AV051_B1-A71_1.174.00_WW_GE
I hope you can find the solution.
Thank you for sharing your work with us.
Just uploaded a new version. Could you please try again?
It's hard to fix for me, because I don't have the problem, so all I can do is try. Thanks for the patience!
****, I think i found the bug. Don't try 0.2.4 it won't work also.
foxterrier said:
Dear entonjackson,
thanks for your work and for the time you spend on it.
Unfortunately, I too have problems with the tool for Windows since version 0.2.0 and also with the latest version (0.2.3).
The error messages that I receive are identical (with the same line numbers) to those receiving cakadut in his last post.
I am trying to root Iconia for the first time.
I tried with Windows 7-32bit and Windows 7 64-bit.
My configuration:
Iconia B1-A71 8GB ROM, 512Mb ram
Android 4.1.2
kernel 3.4.0
Image version: Acer_AV051_B1-A71_RV04RC04_WW_GEN1
Build Number: Acer_AV051_B1-A71_1.174.00_WW_GE
I hope you can find the solution.
Thank you for sharing your work with us.
Click to expand...
Click to collapse
Ok, people. With pawitp's help I hopefully fixed the permissions bug.
The problem was, that i was trying to chmod the /cache directory directly from adb shell, which isn't possible. I forgot, that this needs to be done from telnet. So in 0.2.6 I'm setting permission with telnet. This should fix it!
Please report!
Good luck :fingers-crossed:
Dear ethon
hi ethon can u do tutorial video cause i can't found the directory for the "step 6 : go to go to connectivity -> CDS Inforamtion ->Network Utility " and Thnk You :good:
diskenz said:
hi ethon can u do tutorial video cause i can't found the directory for the "step 6 : go to go to connectivity -> CDS Inforamtion ->Network Utility " and Thnk You :good:
Click to expand...
Click to collapse
I will try to do a video tutorial, but it's very easy to do.
Download and install Ex Dialer & Contacts.
Launch the app.
Dial *#*#ENGMODE#*#*.
Swipe from right to left (to Connectivity). Then choose CDS Information and Network Utility.
There you paste this command: /data/local/tmp/busybox telnetd -l /system/bin/sh -p 1234
stell no thing happen maybe i must upgrade to pro version ???
diskenz said:
stell no thing happen maybe i must upgrade to pro version ???
Click to expand...
Click to collapse
No.
Try to dial *#*#3646633#*#*
Else I don't know... this should work in any case...
entonjackson said:
Ok, people. With pawitp's help I hopefully fixed the permissions bug.
The problem was, that i was trying to chmod the /cache directory directly from adb shell, which isn't possible. I forgot, that this needs to be done from telnet. So in 0.2.6 I'm setting permission with telnet. This should fix it!
Please report!
Good luck :fingers-crossed:
Click to expand...
Click to collapse
Thanks entonjackson,
unfortunately with version 0.2.6 I can not get the ADB connection with the tablet. The message it gives me is:
"Trying to Establish ADB Connection (If this hangs, ADB Connection failed. CMD Shell Close and open a new one) ..."
and remains so without making the connection.
If I run the command 'adb devices' in another command line session, the device is seen correctly (0123456789ABCDEF device),
but when I run the new version (0.2.6) of the tool, the message is what I wrote above.
Thank you for your patience.
Elephone P6000
Phone reviews by @s7yler
Stock ROM (SPFlash):
from elephone servers
from needrom.com
Custom Recovery --- Touch RecoveryCourtesy of @bigrammy, @carliv and @Santhosh MVarious
Latin Paradise(拉丁乐园)(Elephone) on Baidu
P6000 Folder
OTA Updates - direct from elephone
--- both are 404 now ---
12282014 to 31012015
01092015 to 31012015
Other threads and useful sites:
http://forum.xda-developers.com/android/general/elephone-p6000-mtk6732-64-bit-4g-5-2g-t2957425
SP Flash Thread - P6000
4pda thread - translated top post is fairly concise
Check your Mobile Network/Carrier
Please use the other threads/Q&A and the thanks button - to minimise duplicate posts reporting the same issues.
I'd like this thread to be used mainly for bug fixes, tips and tricks. If someone reports a similar problem/fix/bug click the thanks button if you'd like to agree.
Bugs
Android 5.0 'Official' Release
Update Official (V3.3)
Some modifications: #186
Android 5.0 Beta
12-02-15 ROM available on needrom.com
Hardware buttons don't work
Battery doesn't draw charge
Ril related memory leak
No ADB
Android 4.4.4 (V8.4)
Notification light - not breathing when charging
OTG only works with self-powered devices
Battery seems to jump from 100% to ~90% Soon after removing from charger
Screen jumps several pixels (30) on slow scrolling. Android 4.4.4 (V8.3) bugs not present in V8.4Data encryption results in a stalled boot/softbrick
FAQ/Fixes
1. Notification light is not working in V8.4 as it was in V8.3
Try Light Manager from the play store or gravity box (xposed module)
2. Does OTG work?
It seems to work only with a powered USB hub - I've only been able to check a powered external hard-drive which wouldn't connect
3. How do you fix the screen jump issue?
There are several options here:
From @the1024 / zOrgent we have two options 1. Using a chinese tool - and 2. Using a .bat
From elephone we have TpUpgrade.apk (appears to only work with V8.4)
From lidmiloff we have P6000 Bugfixer.apk
4. How do you restore a Stock ROM?
Download a SPFlash ROM from #1; you will need to install MediaTek USB VCOM drivers (if they aren't automatically installed); On the download page select the scatter from the ROM folder; and the page should populate with the various .img's and .bins; if it doesn't then double click on the entry and locate it manually (also useful if you wan to change boot/recovery with SPFlash). Hit download; remove the battery from the phone and connect it to the PC (you can connect the battery again). The connection will be fairly instantaneous (there may be a driver install the first time it's connected); if it doesn't connect then unplug/replug.
More details from @bigrammy found here
5. Battery jump from 100% to 90%.
Haven't really noticed this too much - download an app like Battery Monitor Widget, add widget (Battery monitor widget gauge => Content => Central value => Battery => Battery Current (mA)) which will show you the battery drain/draw and charge until the draw is close to; if not +0mA
6. Is there any touch recovery?
As of now (pre-5.0) there is no touch recovery. The recovery thread on #1 contains various recoveries - most of which boot but none have touch - this seems to be a kernel issue.
Touch recoveries can be found here. These are built for KK.
7. What about Custom ROMs?
Potential Port devices (MT6732/MT6752) and their ROMS
As there are no official sources released; for MT6732 or P6000 then custom ROMs are a no-go for now. Porting ROMs from other devices running on MT6732 (and MT6752); i.e. Ulefone Be Pro for example is theoretically possible but there doesn't appear to be any custom ROMs on these chips that offer anything different than the stock/AOSP(almost) that we have already. As other devices get released possibly running MIUI or ColorOS then Custom ROMs may be possible.
FlymeOS
8. How do you take a screenshot?
Natively pressing Volume down and power together for 1 second will take a screenshot - it may take a while to get used to - if volume mixer appears then they were too slow and need to wait for it to disappear. Over adb/terminal you can make use of screencap and screen record
9. How do you back up EVERYTHING(except preloader)?
In SPFlash Tools => readback from 0x00 to 0x3a3e000000
This is a fairly quick way to make sure you have a copy of all the partitions on the device; it will create a 14GB+ file containing all the partitions. You will need to break this block up (manually for the moment) into it's constituent parts if you want to use it to restore - using a Hex-editor (HxD for example) and a copy of the matching /proc/partinfo file and/or scatter.txt
The essential partitions to backup for a fully running device are - boot, (recovery), system, (cache) and data which can all be backed up using a custom recovery. The one other partition needed is nvram - this can be backed up with SPFlash (look at /proc/partinfo) or with dd commands. The nvram partition will only be needed to be restored if you Format All with SPFlash. If you don't have a backup you can restore/recreate the IMEI files that it contains.
10. How do you backup/restore IMEI?
Several options here:
1. MTKDroid
2. Backup NVFLASH partition via readback in SPFlash Tools (look at the scatter.txt) to restore you need to modify the scatter.txt to give the nvflash a file_name: and change it from is_Download: false to is_Download: true
3. From elephone there's a IMEI coding tool
4. Keep a copy of the /data/nvram folder
5. Create new imei files to add to nvram folder/partition with imei.exe
6. Chamelephon app from the play store
7. MTK Engineering Mode
11. Adb access with 5.0 Beta ROMs
1. Use KingoRoot
2. Add the Mediatek subsystem id (0x0e8d) to adb_usb.ini
12. Any Stock Camera fixes?
For KK-4.4.4 from @z0rgent at 4pda
FAQ/Fixes Continued
Android 5.0 V1; V1.1; V2.2 (V3.2); V3.3 #125 #186These versions seem to have gapps preinstalled and are prerooted - for everything else have a look at the 5.0 Betas section below
5.0 Modifications #186Android 5.0 Beta1 Beta2 Beta3
To gain adb access
Linux/Windows - need to add the Mediatek subsystem id (0x0e8d) to adb_usb.ini
Linux: ~/.android/adb_usb.ini
Windows: C:/Users/${Username}/.android/adb_usb.iniKingoRoot It won't root the device however - I believe this is due to it installing a 32bit su binary rather than a 64bit one.
Root
For root install SuperSU v2.11+
Confirmation
Custom Recovery
Recovery from @carliv - from #1; modded to boot on L (basically just the cmdline changed / initrd.gz from stock L recovery replaced with carliv's built CWM).
Carliv Port by hanuma50 on 4pda (hopefully all his work and not partially stolen to take credit)
This recovery seems to only work when the Lollipop Beta ROM is installed.
Gapps
64-bit gapps made for the Nexus 9.
My phone seems to be running a little hot after installing the gapps - but that might just all the cores kicking in.
Mirrored copy of the version I'm using.
(OP's thread has updated them and removed the previous version)
Busybox
64-bit busybox installation
Removing encrypted data (temporarily)
In recovery while in an adb shell: /sbin/make_ext4fs /dev/block/mmcblk0p19
This will allow you to restore backed up data - but it will get re-encrypted on first boot, I'll take a look at removing encryption when I get the chance - should be either secro partition or something in the boot.img
Android 5.0 Beta Breakdown
Screenshots to come later.
Entering LKVOL UP and POWER (this no longer enters recovery)
From lk menu: entering fastboot mode and normal boot works.
Entering recovery (stock) doesn't work and I can't tell if the other normal boot options do anything differentCharging batteryFlashing a custom recovery should allow you some way to charge the batteryI haven't yet been able to install/boot any recovery. Flashing lk and boot from 4.4.4 (I took them from the 48MB OTA) seems to let you charge when powered off. ConfirmedRIL Memory leakThere seems to be a RIL/Sim related memory leak leading to random reboots - for testing purposes disable the sim card(s) or enter airplane mode
I could be wrong about the RIL and the ROM just needed time to settle; all I can say is I had reboots until I switched to airplane modeIMEIIMEI was lost but that would be due to formatted flash memory (wiped nvflash partition) - it's a good idea to keep a backup regardless.Antutu Scores64-bit Antutu Scores are around 28000
32-bit Scores are around 27000
Data-encrypted 4.4.4 Antutu scores are also around 28000SensorsBacklight, sound ... can't be changed
Brightness can be fixed in MTK Engineering Mode #5ROM is not rooted; does not have gapps installed and data is encrypted.
TL;DR The issues with the 5.0 Beta ROM, are primarily not ROM related but kernel related, they have bumped the kernel version up to 3.10.61+, and the issues that need correcting are the various kernel modules (power,sensors).
Android L kernel config
Annotated /system/build.prop
Stripped top of build.prop (build properties) due to size
# begin mediatek build properties
ro.mediatek.version.release=ALPS.KK2.MP13.V1.27
ro.mediatek.platform=MT6752
ro.mediatek.chip_ver=S01
ro.mediatek.version.branch=KK2.MP13
ro.mediatek.version.sdk=3
# end mediatek build properties
#
# from out/target/product/k01q_e/obj/CUSTGEN/config/system.prop
#
#
# system.prop for generic sdk
#
rild.libpath=/system/lib/mtk-ril.so
rild.libargs=-d /dev/ttyC0
# MTK, Infinity, 20090720 {
wifi.interface=wlan0
# MTK, Infinity, 20090720 }
# MTK, mtk03034, 20101210 {
ro.mediatek.wlan.wsc=1
# MTK, mtk03034 20101210}
# MTK, mtk03034, 20110318 {
ro.mediatek.wlan.p2p=1
# MTK, mtk03034 20110318}
# MTK, mtk03034, 20101213 {
mediatek.wlan.ctia=0
# MTK, mtk03034 20101213}
#
wifi.tethering.interface=ap0
#
ro.opengles.version=196608
wifi.direct.interface=p2p0
# dalvik.vm.heapgrowthlimit=256m
# dalvik.vm.heapsize=512m
# USB MTP WHQL
ro.sys.usb.mtp.whql.enable=0
# Power off opt in IPO
sys.ipo.pwrdncap=2
# Switching Menu of Mass storage and MTP
ro.sys.usb.storage.type=mtp #### adding ,massstorage to this gives an additional USB option but it apears to still mount as a media device (MTP) adding ,mass_storage will let you mount the microsd card
# USB BICR function
ro.sys.usb.bicr=no #### changing to yes will allow you to mount /system/mobile_toolkit/iAmCdRom.iso to PC via USB ####
# USB Charge only function
ro.sys.usb.charging.only=yes
# audio
ro.camera.sound.forced=0
ro.audio.silent=0
ro.zygote.preload.enable=0
#
# ADDITIONAL_BUILD_PROPERTIES
#
persist.gemini.sim_num=2
ro.gemini.smart_sim_switch=false
ro.gemini.smart_3g_switch=0
ro.gemini.sim_switch_policy=1
ril.specific.sm_cause=0
bgw.current3gband=0
ril.external.md=0
ro.btstack=blueangel
ro.sf.hwrotation=0
ril.current.share_modem=2
curlockscreen=1
ro.mediatek.gemini_support=true
persist.radio.fd.counter=15
persist.radio.fd.off.counter=5
persist.radio.fd.r8.counter=15
persist.radio.fd.off.r8.counter=5
persist.radio.fd.on.only.r8.network=0
drm.service.enabled=true
fmradio.driver.enable=1
ril.first.md=1
ril.flightmode.poweroffMD=1
ril.telephony.mode=0
dalvik.vm.mtk-stack-trace-file=/data/anr/mtk_traces.txt
persist.mtk.anr.mechanism=1
mediatek.wlan.chip=CONSYS_MT6752
mediatek.wlan.module.postfix=_consys_mt6752
ril.radiooff.poweroffMD=0
ro.config.notification_sound=Proxima.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.config.ringtone=Backroad.ogg
persist.mtk.wcn.combo.chipid=-1
ter.service.enable=0
mediatek.extmd.usbport=0
ro.lte.dc.support=0
ril.active.md=0
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=4.4.4
ro.com.google.clientidbase=alps-k01q_e-{country}
ro.com.google.clientidbase.ms=alps-k01q_e-{country}
ro.com.google.clientidbase.yt=alps-k01q_e-{country}
ro.com.google.clientidbase.am=alps-k01q_e-{country}
ro.com.google.clientidbase.gmm=alps-k01q_e-{country}
wfd.dummy.enable=1
persist.sys.dalvik.vm.lib=libdvm.so #### Charnging this to libart.so appears to have no effect ####
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
# begin fota properties
ro.fota.platform=MTK6732_KK
ro.fota.type=phone
ro.fota.oem=new-bund6732_KK
ro.fota.device=k01q_e
ro.fota.version=eng.jenkins.1422677980
# end fota properties
ro.sf.lcd_density=190
#### Stock value I believe is 320; changing to >190 switches the device to phablet mode; this spoofs the screen size to be 7.73 inches (CPU-Z) enabling tablet apps in the apps store after clearing play store app data ####
qemu.hw.mainkeys=0
#### This enables softkeys ####
Annotated /custom/customprop/custom.prop
ro.product.model=Elephone P6000
ro.product.name=Elephone P6000
ro.product.brand=elephone
ro.product.manufacturer=elephone
ro.bt.name=P6000
ro.wifi.name=P6000
ro.notification.breath=yes #### This seems to not be working with V8.4 ####
ro.build.display.id=ALPS.KK2.MP13.V1.27
ro.internal.build.version=K01Q-E.ELEPHONE.vR83.E4.150109
ro.custom.build.version=Elephone_P6000_V8.4_20150109
ro.fota.device=Elephone_P6000
ro.fota.version=Elephone_P6000_V8.4_20150109202612
MTK Engineering Mode
*#*#3646633#*#* (*#*#ENGMODE#*#*)
What can be done in engineering mode
General non-specific guide
Backlight
Hardware ===> LCM ===> LCM Cycle ===> add a value between 5 and 55 ===> Hit Set.
(On L at least this value will jump to value in the millions/billions; unsure if this has any implications)
Audio
http://forum.xda-developers.com/showthread.php?t=2746861
http://forum.xda-developers.com/showthread.php?t=2248396
GPS
http://www.cnx-software.com/2013/11...ps-lock-on-mediatek-mt65xx-based-smartphones/
Orientation / GSensor
Hardware Testing ===> Sensor ===> Sensor Calibration ===> GSensor Calibration ===> Do Calibration (20% tolerance)
IMEI Restore
Command should be AT +...
Xposed Installer (or WSM Tools)
I've had no problems with any xposed modules.
You will get a warning regarding AliyunOS -
this issue is reported due to the presence of /system/framework/*.jar.jex files.
You can ignore/move/remove these *.jar.jex files without it causing any (noticable) issue.
I haven't decompiled any apps so I don't know if. jex files are used elsewhere within the ROM (in place of .jar),
so can't comment on whether the stock ROM is indeed an Aliyun OS.
I would advise backing them up so that any future OTA can complete 100%.
Any issues identified with xposed modules will be reported here.
Very Helpful and concise
Nice one bro :good:
Subscribed
Ludmiloff's Screen fix apk version 1.2 final now works with 8.3 also. Just wanted to give you a quick update so you edit your post HypoTurtle
greekfragma said:
Ludmiloff's Screen fix apk version 1.2 final now works with 8.3 also. Just wanted to give you a quick update so you edit your post HypoTurtle
Click to expand...
Click to collapse
Still doesn't work for me on 8.3.
Nice one, i get my phone in a couple of weeks.
Hello
and Thanks for all your work ! :victory:
Can you add how save and restore imei ?
xenonism said:
Still doesn't work for me on 8.3.
Click to expand...
Click to collapse
Sorry to hear that man. Can you give more details? Are the driver version letters shown normal or "?"
greekfragma said:
Sorry to hear that man. Can you give more details? Are the driver version letters shown normal or "?"
Click to expand...
Click to collapse
Well, I tried the first methods which came out and they wouldn't work. Then I upgraded to V8.4, at the same time the Elephone APK came out, so I used it and it set the thresholds to 3 and 4. Then I decided to go back to V8.3 and since then, no method managed to make a persistent change to the values (I tried ludmiloff's works, Elephone's APK modified by me, which worked for others, and the old Russian method). At best, I get the new vaules in the "init config" portion of the configuration, never in the "real config" portion, and they are always gone after a reboot. File permissions of /proc/gt9xx_config are 660, owned by root. The config version letter is currently F and ludmiloff's app reads it correctly.
I guess that's all the info I can share.
xenonism said:
Well, I tried the first methods which came out and they wouldn't work. Then I upgraded to V8.4, at the same time the Elephone APK came out, so I used it and it set the thresholds to 3 and 4. Then I decided to go back to V8.3 and since then, no method managed to make a persistent change to the values (I tried ludmiloff's works, Elephone's APK modified by me, which worked for others, and the old Russian method). At best, I get the new vaules in the "init config" portion of the configuration, never in the "real config" portion, and they are always gone after a reboot. File permissions of /proc/gt9xx_config are 660, owned by root. The config version letter is currently F and ludmiloff's app reads it correctly.
I guess that's all the info I can share.
Click to expand...
Click to collapse
Well, time to get in here, I guess...
@xenonism, the best I could tell you is to start over with clean ROM, preferably the one listed at 4pda.ru thread about elephone P6000 (in the head section) and try again. There must be something messed up in your device. I really believe the config is independent of ROM. The secret is very simple, you must start with new version letter and at offset 184 set correct checksum. How to calculate checksum:
//cal checksum
byte checksum;
for(i=0; i<chip_cfg_len; i++) {
checksum += file_config;
}
file_config[chip_cfg_len] = (~checksum) + 1;
Where chip_cfg_len = 184
Then write the checksum and write 0x01 at offset 185.
I believe you already know where are the theshsold values - at offset 16 and 17.
If you wish, I could send you my hand crafted config, which I was an inspiration for my apk.
Good luck
Err... it looks like I am unable to install a clean ROM, or even to update the existing one. I guess I'll have to sort this issue out before I join back the discusssion.
I have a fully functionalV8.3_20141228 ROM running and carliv's CWM from the 7th of February installed. The phone offers me the OTA update and it downloads a ~23 MB update. When I agree to install it, the phone reboots to CWM and the update fails with the following messages:
E:Invalid command argument
Finding update package...
E:unknown volume for path [/storage/sdcard0/adupsfota/update.zip]
E:Can't mount /storage/sdcard0/adupsfota/update.zip
Installation aborted.
Click to expand...
Click to collapse
If I try to install the same update with ROM Manager, it also fails in CWM with the following message:
-- Installing: [FILENAME SHOWS HERE]
Finding update package...
Opening update package...
Installing update...
Installation aborted.
Click to expand...
Click to collapse
But when I reboot the phone, I get the "Android is upgrading...] Screen, saying it's optimizing 124 apps. I believe no actual update takes place, though.
And here's what I'd consider the relevant portion of the recovery.log file:
Preparing to install ROM...
about to run program [/cache/dowipedalvikcache.sh] with 1 args
mount: mounting /dev/block/platform/mtk-msdc.0/by-name/userdata on /data failed: Device or resource busy
mount: mounting /dev/block/platform/mtk-msdc.0/by-name/cache on /cache failed: Device or resource busy
mount: can't find /sd-ext in /etc/fstab
umount: can't umount /sd-ext: Invalid argument
run_program: child exited with status 1
about to run program [/sbin/chmod] with 3 args
about to run program [/tmp/recovery/11-rommanager.sh] with 2 args
mount: mounting /dev/block/platform/mtk-msdc.0/by-name/system on /system failed: Device or resource busy
about to run program [/sbin/umount] with 2 args
Click to expand...
Click to collapse
If I try to install the full 20150109 ROM with ROM Manager, it also fails in CWM, without displaying any meaningful messages in recovery. I also get the "Android is upgrading screen here".
The errors in recovery.log are the same as above.
I guess I could install the full ROM via SP Flash Tool, right?
Also... I have a couple of questions to ask, can I feel free to do it in this thread? Some might be trivial for most.
ludmiloff said:
Well, time to get in here, I guess...
@xenonism, the best I could tell you is to start over with clean ROM, preferably the one listed at 4pda.ru thread about elephone P6000 (in the head section) and try again.
Click to expand...
Click to collapse
@ludmiloff does your app require busybox to be installed?
Downloading from 4pda.ru is a bit hit and miss for me, any chance someone can post the CWMLollipop.img...
Is there any difference in the 4pda.ru ROMs and the ones on needrom.com?
Also found a fix for the backlight in Android L - in engineering mode - not sure if it will do anything useful in 4.4.4 (lower the minimum brightness?).
MTK Engineering Mode => Hardware => LCM => LCM Cycle => value between 5 and 55.
xenonism said:
Err... it looks like I am unable to install a clean ROM, or even to update the existing one. I guess I'll have to sort this issue out before I join back the discusssion.
Click to expand...
Click to collapse
Feel free to elaborate. Edit your previous post with your current setup / what you've tried - so we can turn it into a troubleshooting post.
HypoTurtle said:
Feel free to elaborate. Edit your previous post with your current setup / what you've tried - so we can turn it into a troubleshooting post.
Click to expand...
Click to collapse
Ok, thanks a lot. I will edit my post right now. The thing is... I haven't used an Android phone in 4 years and I did a lot of my tinkering on my P6000 while working or late at night so.. things got a bit messy.
@HypoTurtle,
My app does not require busybox. It simply run some commands in the shell, though.
In fact It is my first experience with android programming and I just followed some examples found here and there. I also wanted to make a Kotlin based app, but then I decided to continue with plain old java. The app might not a perfect one. Hope it worked for many of elephone owners
---------- Post added at 08:05 AM ---------- Previous post was at 07:41 AM ----------
@xenonism, you should try a clean ROM with sp flash tool. It is a bit tricky, I have tried one from needrom and as the author suggested, I did not check the preloader mark. Then my phone ended totally bricked. The ROM from 4pda worked for me. Today I'm going to reflash it again and investigate why my app does not work on it.
@ludmiloff, I ended up installing 20150109 via SP Flash Tool and then updating via OTA to the latest version. Sure enough, your app worked then. And permissions for gt9xx_config are now 666.
I am not particularly happy with the gravitybox solution for the notification issue, so I'm trying to look into it, but I am not really hopeful to achieve something.
xenonism said:
@ludmiloff, I ended up installing 20150109 via SP Flash Tool and then updating via OTA to the latest version. Sure enough, your app worked then. And permissions for gt9xx_config are now 666.
I am not particularly happy with the gravitybox solution for the notification issue, so I'm trying to look into it, but I am not really hopeful to achieve something.
Click to expand...
Click to collapse
Same I did just few minutes ago. Won't install updates and will try to make my app working on this ROM.
BTW. Russian method write a very different format to file /process/gmnodexxxxxxx where xxxxxxx is build date. I'm pretty sure if I could change the file with correct checksum and version letter it should work too.
Anyway, my intent was to fix the scroll after I applied the elephone apk. For sure the Russian method with correct version letter and checksum would work too and it is still the best flow now for phones with very stock ROM. I already explained how to calculate the checksum.
HypoTurtle said:
@ludmiloff does your app require busybox to be installed?
Downloading from 4pda.ru is a bit hit and miss for me, any chance someone can post the CWMLollipop.img..
Click to expand...
Click to collapse
I cant see any CWMLollipop.img there
They only list two recoverys my P6000CWM3.img with no links or credits of course
and carliv's CWM_Modd_2.img again no links or credits
I will be working on the lollipop soon
I am getting another phone very soon to use for daily life so I can use the P6000 for dev only purposes.
[GUIDE] Huawei Y5C | Y541-U02 | Honor Bee : Stock ROMs, ROM Dumping, Root & Flashing
Disclaimer
Upon following this guide, you may or may not achieve same results with others. I am not held responsible for anything unexpected that may happen to your device. Do your research first regarding the areas you do not quite understand. Follow at your own risk.
Prerequisites
Spreadtrum Flash Tool R4.0.0001 (PAC Flashing) or Flashfire (Zip flashing)
SPRD USB Driver (needed for PAC Flashing)
Male to Micro USB Cable (needed for PAC Flashing)
7-Zip
Root with SuperSU (just below, needed for first time Zip flashing)
Packet (*.pac) or Zip ROM (found below)
Rooting
Install and gain root through KingRoot android application.
Restart your phone. (I've encountered a sudden reboot when doing the steps below without this)
Replace KingRoot with SupeSU through this script.
Once the archive is downloaded, extract it. There will be a folder named root where you extract it.
Download and open Terminal Emulator.
Change directory to the root folder that was extracted:
Code:
cd /path/to/root
Then ask for root permissions:
Code:
su
Now run the first script:
Code:
sh level1.sh
Run the second script:
Code:
sh level2.sh
Leave the terminal running and open KingRoot.
Press the button at the upper right corner, and choose general settings.
Scroll down and press uninstall.
Uncheck backup and press OK.
After KingRoot has finished uninstalling, go ahead and uninstall Purify as well.
Go back to the terminal and run the third, last script:
Code:
sh level3.sh
Again leaving the terminal running, install SuperSU and open it.
Let it update the root binary through Normal method, and restart.
Notes:
Currently SuperSU's prompt for applications asking for root permissions does not work, but, changing the setting to "grant" will. Just return it to "deny" afterwards, for security. That's the workaround for now.
Dumping
Before doing anything to your device, it is advised to create a ROM dump/backup beforehand. Also make sure you have a lot of free space on your internal storage.
Open up terminal and gain root permissions:
Code:
su
Then get the partition details:
Code:
ls -al /dev/block/platform/sprd-sdhci.3/by-name
Dump each partition (X) with its name (Y):
Code:
dd =if/dev/block/mmcblk0pX of=/sdcard/Y.img
Do not forget to dump the two bootloaders:
Code:
dd =if/dev/block/mmcblk0boot0 of=/sdcard/splloader.img
Code:
dd =if/dev/block/mmcblk0boot1 of=/sdcard/uboot.img
Flashing
PAC
Extract all the downloaded archives and install the driver (either 32install for 32/86bit or 64install for 64bit OS).
Open the flash tool by double clicking the executable named "ResearchDownload".
Once the flash tool opens, click the single gear button at the top left.
Find and open the PAC ROM.
Press the play button.
Power down the device, hold the volume down button and plug it into the PC.
The flash tool will then recognize the device and start downloading binaries to it.
Once the progress column shows "PASSED", the binary download is finished and the device can now be safely unplugged.
Remove the battery, reinsert, and power the device.
Zip
Gain root if not already done so.
Open Flashfire. (press agree and the other one is up to the user)
Press the red circular button with a plus sign ( + ) on the bottom right, and choose Flash ZIP or OTA.
Find and open the downloaded Zip ROM.
There will be a pop-up for a few settings, leave it as is and press the check icon at the upper right.
Now when the pop-up closes, swipe down and press the Flash button with a lighting icon.
Press OK, and let it flash.
The device will reboot once flashing is finished.
Unbrick Stock PAC ROM
Y541-U02V100R001C567B116
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=HUAWEIY541-U02
ro.build.version.sdk=19
ro.build.version.codename=REL
ro.build.version.release=4.4.2
ro.build.version.security_patch=2016-03-01
ro.build.version.base_os=
ro.build.date=Mon May 23 22:44:32 CST 2016
ro.build.date.utc=1464014672
ro.build.type=user
ro.build.user=
ro.build.host=a7fcf16085c3
ro.build.tags=ota-rel-keys,release-keys
ro.product.model=HUAWEI Y541-U02
ro.product.brand=HUAWEI
ro.product.name=Y541-U02
ro.product.device=HWY541-U
ro.product.board=Y541-U02
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HUAWEI
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=sc8830
# ro.build.product is obsolete; use ro.product.device
ro.build.product=Y541-U02
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=Y541-U02-user 4.4.2 HUAWEIY541-U02 135 ota-rel-keys,release-keys
ro.build.fingerprint=HUAWEI/Y541-U02/HWY541-U:4.4.2/HUAWEIY541-U02/C567B116:user/ota-rel-keys,release-keys
ro.build.characteristics=default
ro.zygote.disable_gl_preload=false
# end build properties
#
# from device/ontim/Y541-U02/system.prop
#
ro.sf.lcd_density=240
ro.sf.lcd_width=54
ro.sf.lcd_height=96
ro.opengles.version=131072
ro.product.hardware=SP7731GEA_V1.0.0
debug.hwui.render_dirty_regions=false
ro.config.hw_showSimName=true
ro.config.hw_hideSimIcon=false
ro.config.coop_stk1comp=com.android.stk1;com.android.stk1.StkLauncherActivity
# Bluetooth OPP low speed for save power
debug.bt.lowspeed=false
persist.ttydev=ttyVUART0
# delay for ConnectivityChange broadcast (ms)
conn.connectivity_change_delay = 0
ro.product.partitionpath=/dev/block/platform/sprd-sdhci.3/by-name/
# Default ecclist
ro.ril.ecclist=112,911,#911,*911
persist.modem.w.enable=1
persist.modem.w.nvp=w
ro.modem.w.dev=/dev/cpw
ro.modem.w.tty=/dev/stty_w
ro.modem.w.eth=seth_w
ro.modem.w.snd=1
ro.modem.w.diag=/dev/slog_w
ro.modem.w.loop=/dev/spipe_w0
ro.modem.w.nv=/dev/spipe_w1
ro.modem.w.assert=/dev/spipe_w2
ro.modem.w.vbc=/dev/spipe_w6
ro.modem.w.id=0
ro.modem.w.fixnv_size=0x40000
ro.modem.w.runnv_size=0x60000
persist.sys.engpc.disable=0
ro.modem.wcn.enable=0
ro.modem.wcn.dev=/dev/cpwcn
ro.modem.wcn.tty=/deiv/stty_wcn
ro.modem.wcn.diag=/dev/slog_wcn
ro.modem.wcn.assert=/dev/spipe_wcn2
ro.modem.wcn.id=1
ro.modem.wcn.count=1
camera.disable_zsl_mode=1
ro.digital.fm.support=1
ro.config.ksm.support=true
#supprot storage path change
ro.storagepath.change.support=true
#supprot quickcamera
ro.quickcamera.support=true
#zram config
ro.config.zram.support=true
ro.board_ram_size=mid
# SPRD: add low cost low memory @{
ro.config.low_ram=true
# @}
#if our product not support drm,set as false
drm.service.enabled=true
# hotspot development
ro.hotspot.enabled=1
# this product does not support bt and softap coexist
ro.btwifisoftap.coexist=true
# SPRD: add support hwrotation
ro.sf.hwrotation=0
#SPRD: add support follow sim system config
persist.support.fssc=1
#SPRD: add for cphs
persist.support.oplpnn=true
persist.support.cphsfirst=false
#SPRD: add support virtualnet
persist.support.virtualnet=true
#ontim:add support huawei wlan setting
persist.huawei.wifi.setting=true
#SPRD: add support encrypt
ro.encrypt.devices.support=0
#SPRD: add support vt
persist.sys.support.vt=false
#SPRD: delete baseband version
ro.show.basebandversion=false
#SPRD: mccmnc config path
ro.mccmnc.info.path=/globalinfo/
#for app can install on sd and primary is internal
ro.storage.installonsd=true
# Audio Dump Information for HAL
audio.dump.show.switch=0
hw-k3-burst-supported=1
# adapter for HuaWei PIN(keyguard apk) added by liulibo
ro.config.is_sprd=true
#avoid gallery function:chang voice pic to video.
ro.config.hw_trans_voiceimage=false
#avoid gallery map function
ro.config.support_gallery_map=false
#wifi_country
ro.config.custCountryEnable=ir,sd,sy,kr
# SPRD: DC lowpower
sys.dc.lowpower=true
ro.systemui.flashlight.timeout=0
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.build.version.incremental=C567B116
ro.product.sw.internal.version=Y541-U02V100R001C567B116_user_30323_160523.223910
ro.product.sw.external.version=Y541-U02V100R001C567B116
ro.build.cust.id=Y541-U02V100R001C567B116
ro.versioninfo.delivery=MocorDroid4.4_TShark28_2341A_W15.16.5
ro.com.android.dateformat=MM-dd-yyyy
ro.carrier=unknown
persist.sys.sprd.modemreset=1
ro.adb.secure=1
persist.sys.sprd.wcnreset=1
ro.xtsdisableverify=1
ro.storage.flash_type=2
keyguard.no_require_sim=true
ro.com.android.dataroaming=false
ro.msms.phone_count=2
persist.msms.phone_count=2
persist.msms.phone_default=0
ro.modem.w.count=2
persist.sys.support.vt=false
sys.usb.gser.count=4
lmk.autocalc=false
persist.sys.data_reserved=100
ro.config.ringtone=Huawei_Tune.ogg
ro.config.ringtone0=Huawei_Tune.ogg
ro.config.ringtone1=Huawei_Tune_Piano.ogg
ro.config.notification_sound=Bongo.ogg
ro.config.alarm_alert=Creamy.ogg
persist.sys.wakeup.enable=0
ro.config.hw_timeformat=true
ro.config.timeformat=24
persist.sys.modem.diag=,none
persist.sys.slog=0
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=96m
dalvik.vm.heapsize=256m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=8m
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=4.4_r7
ro.build.display.id=Y541-U02V100R001C567B116
ro.config.max_starting_bg=3
ro.com.google.clientidbase=android-huawei
ro.com.google.clientidbase.yt=android-huawei
ro.com.google.clientidbase.am=android-huawei
ro.com.google.clientidbase.gmm=android-huawei
ro.com.google.clientidbase.ms=android-huawei
ro.dual.sim.phone=true
ro.config.hw_coop_no_setting=true
ro.config.remove_subscribe_menu=1
ro.config.hw_coop.ontim=true
ro.config.hw_coop.show_Sun=1
ro.config.app_big_icon_size=90
ro.config.hwcust_drawbgicon=false
ro.config.hw_coop_delay=true
ro.config.hwtheme=1
persist.radio.langu.rule=0
data.icon.onlyconnected=true
persist.sys.certification=103323
ro.config.is_support_my=true
ro.product.hwinternal.version=Y541-U02V100R001C567B116
ro.product.hwinternal.ver.time=160523.223910
persist.sys.dalvik.vm.lib=libdvm.so
net.bt.name=Android
ro.floatkey.show=false
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Notes:
These ROMs are repacked and tested first before being posted, so if one of these does not work, try another. If none worked, just wait, others will share a new partition dump.
These ROMs do not contain a system, custom and cache dump because these are for unbricking for now. Prerooted full repacks are coming soon.
Stock ZIPs
Notes:
As the device refuses any custom or modified stock binaries, Flashfire is the only way to go to install zips.
These are pre-rooted, deodexed, zipaligned, de-bloated, and of course tested.
None at the moment.
Troubleshooting
If the flash tool fails to download, either the downloaded ROM is incompatible with the device, or the cable is loose.
If the device shows a white screen but the booting sound is heard, try another one.
Support
If anyone happens to have the same device model in fully working condition but seems to be different, kindly make a partition dump of it and PM the link, so it can be processed and uploaded here.
Credits & Sources
@najoor for the original KingRoot to SuperSU script.
GSM Flashfile Website
@Kingxteam for KingRoot
@Chainfire for SuperSU & Flashfire
Is there any customs available for this device
anil kalyan said:
Is there any customs available for this device
Click to expand...
Click to collapse
As of now, with the bootloader locked, there is none.
In future can we expect the same..........
The closest we can get is a modified stock. In the future, there might, but let us not get our hopes up.
techyzen101 said:
The closest we can get is a modified stock. In the future, there might, but let us not get our hopes up.
Click to expand...
Click to collapse
When can we expect this
Where we are on this Can we expect Lollipop rom anytime
Please provide the lollipop ROM
after flash check download state, last download maybe not complete.
Does anyone have a full file or link .pac file Y541-U02V100R001C567B116 ~ 1.5Gb
Y541-U02V100R001C567B112
I need This version pac file help plz
snmobilecenter said:
after flash check download state, last download maybe not complete.
Click to expand...
Click to collapse
hello can i ask if what can be done when you encouter this error upon power on?
tried flashing with research download and upgrade downgrade tool from spdflashtools.
got it to flash firmware v105. but after flashing, blank screen won't power on. also cannot go to recovery.
tried to flash it again with different version, did not go thru anymore and cannot go through any firmware versions.
stuck at FDL2 failing.
tried android usb drivers and spd /sci drivers still stuck at fdl2
please help.
how to get twrp?
Here wo go for another level...
First Soho Fireos 4 based customized rom
Instruction:
you need to unlock your bootloader first
install TWRP (i dont recommend twrp 3.x)
download:
twrp backup (new version):
2017-06-06--09-43-38_KTU84M_test-keys.part1.rar
This file has been shared with you on pixeldrain
pixeldrain.com
2017-06-06--09-43-38_KTU84M_test-keys.part2.rar
This file has been shared with you on pixeldrain
pixeldrain.com
now have fun
i hope you know how to install a twrp backup
extract the rar on your /sdcard goto twrp and restore backup for system
XDA:DevDB Information
pX-Fire Rom 4.5.5.2, ROM for the Amazon 7" Kindle Fire HD
Contributors
pxrave, spudowiar, ggow, hashcode
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: 4.5.5.x
Based On: FireOS
Version Information
Status: No Longer Updated
Current Stable Version: 4.5.5.x
Stable Release Date: 2017-06-10
Created 2016-12-25
Last Updated 2017-06-10
reserved
reserved too
thanks for the rom, i ve already flashed it onto my soho.
is there a list with all the features of the rom? what did you remove and could you remove the amazon-ads too?
rom seems bugless so far and i ve installed xposed from solarwarez without a problem.
Many thanks for putting this ROM together - it breathes new life into my soho Kindle.
I've just finished installing/booting, ROM is working great. Any tweaking for power/speed would be awesome.
Cheers !
kindle hd 7 3rd generation
will this work with the above kindle. I've already rooted and rom'd my hdx 8.9, so am familiar with the language..its running 4.5.5.2 as well.
I also purchased a fastboot cable.
thanks
How do I root my soho..ive looked through so much today that my mind is spinning... I have a fastboot cable.. ive looked at various threads, but still not sure where to start. I would really appreciate some help, ive read through a document that goes through stages, but i seem to falter at the first hurdle. Anyway, I am not going to give up, just some bullet points as to what to do in what order would be great ...... thank you in anticipation...
wheres the link to the rom?
Smokeybear1987 said:
wheres the link to the rom?
Click to expand...
Click to collapse
I too would like to try this ROM. Does anyone have a link to it?
It is listed but not hyperlinked - First Soho Fireos 4 based customized rom
Thanks!
So I wiped the system partition prior to flashing, and now missing basic system elements for boot. Apparently this is a mod and not a ROM. So what's custom? I don't see anything different. What's "unlocked" exactly that wasn't already?
hey guys i have a twrp system backup for you for the latest update but i recommend the new Android 7.1.X based rom for our device
one last update: for amazon fire os will be uploaded this week
this project is discontinued
check the new rom here
How to root a Kindle Fire 7 (2013) soho
Hello everybody! I am new to xda so I hope I'm in the right place. I have tried to start a new thread about this but I coudl not so I am posting this here hoping to find an answer. Rooting a KF (2013) has proved to be quite challenging for me, also because I am dumb . Anyway I have tried to install the 'Permanent Root with Superuser' via Kindle Fire Utility 0.9.8 but I am not able to. I know that I am missing something but I am too dumb to understand what. I need the help of experts. So, I have run Kindle Fire Utility 0.9.8 and I got this:
HTML:
*****************************************************************
* Kindle Fire Utility 0.9.8 *
*****************************************************************
* This is now being maintained by awidawad *
*****************************************************************
* Credit goes to Vashypooh for original work *
*****************************************************************
1 Bootmode Menu
2 Install Permanent Root with Superuser
3 Install Latest TWRP Recovery
4 Install Latest FireFireFire
5 Extras (Requires Root)
0 Recheck Device Status
ADB Status: Online
Boot Status: Unknown
Please make a selection or hit ENTER to exit:
I have connected my KF Soho to the laptop through the factory cable and I have selected 1, and I got this:
HTML:
*****************************************************************
* Kindle Fire Utility 0.9.8 *
*****************************************************************
* This is now being maintained by awidawad *
*****************************************************************
* Credit goes to Vashypooh for original work *
*****************************************************************
1 Normal (4000)
2 Fastboot (4002)
3 Recovery (5001)
0 Recheck ADB/Fastboot Mode
ADB Status: Online
Boot Status: Unknown
Please make a selection or hit ENTER to return:
Then I have selected 1 and I got this:
HTML:
***********************************************
* Activating Normal (4000) *
***********************************************
The system cannot find the drive specified.
failed to copy 'files\nbmode' to '/data/local/nbmode': Permission denied
Unable to open /data/local/nbmode: No such file or directory
/system/bin/sh: /data/local/nbmode: not found
The kindle has been told to reboot in Normal Mode.
Press any key to continue . . .
If I select fastboot instead, I get this:
HTML:
***********************************************
* Activating Fastboot (4002) *
***********************************************
failed to copy 'files\fbmode' to '/data/local/fbmode': Permission denied
Unable to open /data/local/fbmode: No such file or directory
/system/bin/sh: /data/local/fbmode: not found
The kindle has been told to reboot in Fastboot Mode.
Press any key to continue . . .
In both cases my tablet reboots but checking with 'Root Analyzer' I can see that it is not rooted.
I have also tried rooting with Root_with_Restore_by_Bin4ry_v30 choosing the 1st option but I get this:
HTML:
======================================================================
= This script will root your Android phone with adb restore function =
= Script by Bin4ry (thanks to Goroh_kun and tkymgr for the idea) =
= Idea for Tablet S from Fi01_IS01 =
= (01.05.2013) v30 =
======================================================================
Device type:
1) Normal
2) Special (for example: Sony Tablet S, Medion Lifetab)
3) New Xperia Root by Goroh_kun (Xperia Z, Xperia V [JellyBean] ...)
G) Google Glass Mode (thx Saurik for the ab file)
x) Unroot
Make a choice: 1
Checking if i should run in Normal Mode or special Sony Mode
Please connect your device with USB-Debugging enabled now
Waiting for device to shop up, if nothing happens please check if Windows ADB-drivers are installed correctly!
adb server is out of date. killing...
* daemon started successfully *
remote object '/system/app/Backup-Restore.apk' does not exist
remote object '/system/bin/ric' does not exist
.
.
Above file not found warning ARE NOT ERRORS, it is intended to be this way!
Normal Mode enabled!
.
Pushing busybox....
5282 KB/s (1165484 bytes in 0.215s)
Pushing su binary ....
6985 KB/s (380532 bytes in 0.053s)
Pushing Superuser app
5148 KB/s (1500495 bytes in 0.284s)
Making busybox runable ...
.
Now unlock your device and confirm the restore operation.
Please look at your device and click RESTORE!
If all is successful i will tell you, if not this shell will run forever.
Running ...
At this point, my kindle fire displays a screen where I have to choose between 'Do not restore' and 'Restore my data' and I chose 'Restore my data' but my tablet does not reboot at all and the runme.bat file keeps running forever. I have also tried not to press anything at all on the 'Do not restore/Restore my data' screen and I get this:
HTML:
Successful, going to reboot your device in 10 seconds!
Waiting for device to show up again....
Going to copy files to it's place
mount: permission denied (are you root?)
You can close all open command-prompts now!
After reboot all is done! Have fun!
Bin4ry
Press any key to continue . . .
My tablet actually reboots but checking with Root Analyzer I still see the message 'No, your device is not rooted'. What should I do? :'( Ask me all the questions you need and I'll do my best to answer them. Also, please keep in mind that I am not technical therefore explain me things as you would explain them to a quite smart baby Thanks for your help!
Also, I'll write here more details about my device if it is of any help for you guys:
Device model: Kindle Fire HD (3rd generation)
Year: 2013
Bootloader: Uknown
Board: soho
Device: soho
Model: KFSOWI
OS: Fire OS 4.5.5.3
Try kingroot app
Already tried but it could not root
ssurell said:
Try kingroot app
Click to expand...
Click to collapse
Thanks for your answer. I have tried Kingroot and iRoot but they could not root my tablet. I have tried downloading root_script.zip from the following link: https://forum.xda-developers.com/showpost.php?p=47881661&postcount=1
and I get this
HTML:
======================================================================
======================================================================
Welcome to Kindle Root Utility
Special Thanks to:
Moronig
jcase
fi01
======================================================================
======================================================================
WARNING THIS WORKS ONLY WITH KINDLE HD 7" 2013!
======================================================================
======================================================================
Please connect Device with enabled USB-Debugging to your Computer!
Device connected. Pushing files...
5105 KB/s (104564 bytes in 0.020s)
46 KB/s (188 bytes in 0.003s)
4394 KB/s (89968 bytes in 0.019s)
Changing permissions...
Executing Exploit (could take some minutes, be patient!)
Hit ENTER to continue
Press any key to continue . . .
Device detected: ()
Try to find address in memory...
Attempt msm_cameraconfig exploit...
Detected kernel physical address at 0x80008000 form iomem
Attempt fb_mem exploit...
Detected kernel physical address at 0x80008000 form iomem
Failed to open /dev/graphics/fb0 due to Permission denied
You need to manage to get remap_pfn_range addresses.
Failed to get prepare_kernel_cred addresses.
Failed to get commit_creds addresses.
Failed to get ptmx_fops addresses.
() is not supported.
Failed to setup variables.
Press any key to continue . . .
When I press any key to continue the runme.bat closes down but my does not reboot rooted. I am going to throw it out of the window hahaha
hello guys i updated the links. have fun or create mirrors. thanks
Notice:: own risk
I do not want to talk more and nonsense here about the advantages of this custom..
you can try it and feel the advantages.
before I apologize if this custom is not good
hope you happy..
Update: https://forum.xda-developers.com/hu...te-p9-lite-custom-mate10-lite-nova2i-t3796255
##############################
#request bootloader password: https://emui.huawei.com/en/plugin/unlock/index
#Device, required running Android 7.0
# enable oem unlock developer options
#Special tool unlock n install twrp batch file: https://mega.nz/#!sH5RWYKZ!Yi_pVbRcWrLYIxmiURF3yeEWlRaLJWXBQCevZUYwQPU
# custom nova 2I links : https://mega.nz/#!seBUwIrI!Eki8Ap9Ck_3jVopWGOUJG-RXrmw6EvT4WwGXITT_WGU
# root supersu :
https://mega.nz/#!kW4DFBCA!-HcsLGY9jO92X1qiThRWX8032Jvrzj9IQf3hNjq2zsk
#guide installation custom#
Extract update.zip with name..
Ok..if not understand, watch utube:
...goto twrp..wipe .advanced check all partition wipe..
...install..select microsd find update folder
...Just install ( update_firmware.zip ) only
...wait seconds..auto reboot ..
...n then, after installation success, go twrp again..install supersu.zip ..
# last.. home layout .. hold screen/setting/change 5x5
# if issue..app not show in menu..change theme or restart device..
# back to official emui..please wait..
Add new discussion..
## Extra if u user L31C432/L21C432 direct link
https://forum.xda-developers.com/huawei-p9lite/development/firmware-emui-5-1-huawei-p9-lite-t3768973 by @KingOfMezi
About:
Create: 2018
Rom : stable
Kernel: @HassanMirza01