Related
[Patch] Adlxmod.F4D.2.03-patch
This patch includes previous Adlxmod.F4D.2.02 patch, plus:
- Semi-transparent pulldown bar
- Updated: Google Maps 5.2
- Updated: Market 2.3.4
- Latest Cyanogen APN list (February 06, 2011)
- Fixed notification texts not always white in the DarkBar version (only applies to Adlxmod.F4D.2.03-DarkBarOnly patch)
- Note 1: This patch will restore the white notification bar. Download the new DarkBar patch to switch again to a Black bar.
- Note 2: This patch will automatically wipe the Dalvik cache, so the first reboot will take some more time (can take >5 min depending if you have many apps installed) - Don't freak out.
New Notification bar patches:
- Dark Bar : Adlxmod.F4D.2.03-DarkBarOnly-signed.zip
- White Bar: Adlxmod.F4D.2.03-WhiteBarOnly-signed.zip
[Patch] Adlxmod.F4D.2.02-patch
This patch includes previous Adlxmod.F4D.2.01 patch, plus:
- BlurHome selectable: You can switch to BlurHome if you like it
- Added: Adobe Flash 10.1.106.16
- Updated: Market 2.3.2
- Updated TitaniumBackup 3.7.1
- Added: Copy to Clipboard
- Added: Shrinkpipe
- Removed BlurUpdater.apk
Base rom Adlxmod "Froyo for Defy" v2.0:
- Based off UK 3.4.2-117 Froyo leak
- Fully Deodexed by me -> Theme ready
- Optionally a dark notification bar patch can be installed, see below. White patch also provide to get back at it.
- Rooted, Recovery installed
- Phone can be used with no SIM
- Includes Motoblur, but it can be skipped
- Many language supported: Spanish, English, French, Portuguese,...
- Camera flash IS working and synced
Added:
- LG Optimus 2X ringtones (some literal in chinese)
- Adlxmod splash (installed on 1rst boot, will appear on 2nd boot)
- HTC_IME Keyboard para Froyo!
- Gingerbread Keyboard
- Android Terminal Emulator
- Wireless (Wifi & Bluetooth) Tethering
- Busybox fully installed
- AOSP Email App
- Titanium 3.6.7.1
- LauncherPro 0.8.3
- Tenfar Recovery
- 3D Gallery (my mod)
- Overclock support (phone won't be OCed by default)
- SetCPU (free from XDA, please donate on the Market)
- Milestone Overclock
- Added in /system/xbin: rwsystem/rosystem, wpa_cli, zipalign, strace, ssh, sqlite3, dexopt-wrapper, tcpdump, fix_permissions, iptables,...
- Extensive APNs list (Cyanogenmod)
- Ad-Blocking
- AOSP Eclair icons & lock screen sliders
Updated:
- Market 2.2.11 + Market Fix (Paypal shows up for example)
- Google Maps 5.1.0
- Adobe FlashPlayer 10.1
Download these files:
Chinese sbf : Defy_2_2_CN.zip
Rom's Nandroid: Adlxmod.F4D.2.00.zip
Boot+Devtree : Tmo_2.2.1-3.4.2-107-boot-devtree-ONLY.sbf
SuperOneClick : SuperOneClickFor2.1.zip
(this link included Tenfar Recovery with an installer) -> use this one.
Latest Adlxmod Froyo for Defy patch: Adlxmod.F4D.2.03-patch-signed.zip
Optional files you may need:
- Dark Bar : Adlxmod.F4D.2.03-DarkBarOnly-signed.zip
- White Bar: Adlxmod.F4D.2.03-WhiteBarOnly-signed.zip
- Patches for fixing signal/baseband, 2g/3g
- Alternative languages (like PortugueseBR,...) for Swype: see here
Instructions: Please READ-RELAX-READ-FOLLOW
First of all, check CAREFULLY in which case you are:
Case 1:
If you come from a US T-Mobile Defy with the 3.6.90 update
If you have already flashed a non-downgrabable sbf (2.51 or 3.4.2).
Case 2: If you are not in case 1.
Due to Motorola Defy having a locked bootloader at the time of doing this rom, the flashing process is quite complex, so READ AND FOLLOW it VERY CAREFULLY, or you will end with a non booting phone. If it is the case, you should restart again the whole procedure from the beginning.
I recommend you print the whole procedure, and check every step as you do them.
PLEASE READ EVERY SINGLE STEP BEFORE STARTING IT AND FOLLOW THE ORDER CAREFULLY.
If you don't respect the steps and order, the result can be unpredictable.
Only run the steps that apply for your case!
This Rom is a Nandroid backup of system to be restored over the phone:
Unzip the rom file, and place the 2011-02-03.11.17_Adlxmod.F4D.2.00-WhiteBar folder into the SD:/goapkrev/backup/ folder. If SD:/goapkrev/backup/ doesn't exist you have to create it. It should look as follow:
SD:/goapkrev/backup/2011-02-03.11.17_Adlxmod.F4D.2.00-WhiteBar/system.img
SD:/goapkrev/backup/2011-02-03.11.17_Adlxmod.F4D.2.00-WhiteBar/nandroid.md5
Start with FULL battery! (cases 1 & 2)
Be sure your phone's battery is charged 100% before starting.
Wipe all (case 2 ONLY)
Boot your Defy into Stock Recovery (Power + Volume Down button)
Tap in the bottom right corner of the screen to get into the menu
Select Wipe Data, then press OK
Reboot phone into USB Bootloader Init mode (Power + Volume Up button)
Flash Chinese sbf, root, install recovery (case 2 ONLY)
!! WARNING !! Be sure you are in case 2 before you follow! If you are in case 1, read instructions again!
Connect the phone via USB to your computer
Flash Chinese Froyo sbf using latest RSD Lite (4.9) & latest Motorola drivers (4.8)
After flashing the phone will reboot. As we have wiped, it should boot correctly into the Chinese rom.
At the Chinese Motoblur login screen:
Select English language
Press Menu -> Skip Motoblur setup
Root, Install recovery (case 2. also case 1 if you have never rooted & installed recovery)
Go to Settings, Applications, Development -> Enable USB Debugging Mode
Root the phone using the provided SuperOneClick
Don't reboot yet. Run the "Install Recovery.bat" in the same SuperOneClick folder.
This will copy Tenfar Custom bootstrap recovery to the phone and reboot it.
Power up the phone again & wait until it boots.
Go to Settings, Applications, Development -> DISABLE USB Debugging Mode
Open "System Recovery" App in the App Drawer
Press "Install Recovery System", when Asked for Superuser permissions, give them and wait until it says "Install Success!"
Reboot into Custom Recovery & Flash Rom (case 1 & 2)
Go to Settings, Applications, Development -> DISABLE USB Debugging Mode
Open "System Recovery" App in the App Drawer
Press "Recovery Boot"
In Recovery, Select Backup & Restore -> Restore > Select the rom Adlxmod F4D v2.00 folder
Here you can also flash the patches you want to install (Apply zip from sdcard)
Get back to the recovery main menu, and WIPE ALL
(case 1 ONLY) Reboot. End.
Flash boot&devtree (fixes cam flash) (case 1 & 2)
Reboot. /!\ While the phone powers off and on again, maintain the "Volume UP" button pressed!!
Phone should now boot into USB Bootloader Init mode again.
If your phone doesn't boot into USB Bootloader Init mode, and you start to see the (M) Moto logo, pull the battery, unplug the USB cable. wait 10 sec. Plug the battery again, maintain the "Volume UP" button pressed and press Power. maintain the "Volume UP" button pressed until it you get to USB Bootloader Init mode.
Connect the phone via USB to your computer (if it was unplugged)
Flash the boot+devtree sbf provided by me using latest RSD Lite (4.9) & latest Motorola drivers (4.8)
End. Enjoy your Adlxmod Froyo for Defy!
Once you have correctly done the process, you may want to flash some option patches. Just go into Recovery mode and flash the zip you need from the optional patches.
Phew what a detailed protocol. Thank you so much will try it tomorroow
Sent from my MB525 using XDA App
Thanks for this! So your ROM is downgradable if we follow these instructions? I don't want to lose downgradability.
Update0: You really need to add that if you don't remove the battery FAST enough and your phone DOES go into Tenfar recovery, it will brick your phone. Because that is where I'm at right now.
I'm trying to start over, but I can't get anywhere except Stock recovery (which doesn't respond to any commands on the OK Button - wierd) and the USB Bootloader, which doesn't help because if I go through the whole process without doing the factory reset, I can't get to Tenfar's recovery boot after flashing the devtree only sbf - I just get a blank screen.
So I'm pretty much effed.
Update1: no wait, the Stock recovery is working, it's just going ... really ... really .. slow. Hope my battery doesn't run out before I get the factory reset done.
Update2: Ok yeah, still not working. Tried three times now. Can't get to Tenfar Custom Recovery after flashing the devtree sbf no matter what I do. If I leave it plugged in after flashing devtree and allow RSD lite to reboot the phone, I get "please manually power up this phone" and a blank screen. If I reboot manually, I just get the motorola logo forever.
Update3: I am going to try a different ROM entirely and maybe I can get a working phone before work tomorrow...
Update4: Yeah, your instructions were backwards. I should have noticed that right away, but didn't notice until I tried Higgsy's 2.2.1 Froyo build. You need to flash the boot+devtree sbf AFTER you restore the Adlxmod F4D v2.00 folder image - i.e. follow these steps: http://forum.xda-developers.com/showthread.php?t=937319
If you do it in the right order, this ROM works fine and is actually pretty cool (first boot takes a long time of course so be patient.)
THX Adlxmud for you custom rom! your description is great...
But 1 question, the optional patch (Dark-Bar) is work on other ROMS for example Rom 3.4.2 UK?
Tomorrow maybe try it
Thank you!
will try it rite now, coming from chinese sbf, never flashed 2.51. will post feedback tomorrow.
Darkcaptain said:
THX Adlxmud for you custom rom! your description is great...
But 1 question, the optional patch (Dark-Bar) is work on other ROMS for example Rom 3.4.2 UK?
Tomorrow maybe try it
Thank you!
Click to expand...
Click to collapse
hmm good question dude dark bar would look awesome going to try it as im board let you know if it works
edit tried it, it works but imo doesn't suite stock rom
rob-t said:
Thanks for this! So your ROM is downgradable if we follow these instructions? I don't want to lose downgradability.
Click to expand...
Click to collapse
If you haven't flashed any UNdowngrabable rom, you should be able to flash this one. After flashing this rom using my procedure, you will NOT loose downgradability. In other words, yes, my rom is downgradable.
rob-t said:
You really need to add that if you don't remove the battery FAST enough and your phone DOES go into Tenfar recovery, it will brick your phone. Because that is where I'm at right now.
Click to expand...
Click to collapse
If you land in Tenfar recovery you haven't followed my instructions that say:
- Press "Recovery Boot". /!\ Phone should now reboot. While the phone powers off and on again, maintain the "Volume UP" button pressed!!
- Phone should now boot into USB Bootloader Init mode again.
If your phone doesn't boot into USB Bootloader Init mode, and you start to see the (M) Moto logo, pull the battery, unplug the USB cable. wait 10 sec. Plug the battery again, maintain the "Volume UP" button pressed and press Power. maintain the "Volume UP" button pressed until it you get to USB Bootloader Init mode.
Click to expand...
Click to collapse
That means that, anyway you land in Tenfar recovery, just reboot your phone into USB Bootloader Init mode again to flash the boot-devtree.sbf.
If you get a non-booting device at some step, try to just reboot your phone into USB Bootloader Init mode again to flash the boot-devtree.sbf at this step.
rob-t said:
Update1: no wait, the Stock recovery is working, it's just going ... really ... really .. slow. Hope my battery doesn't run out before I get the factory reset done.
Click to expand...
Click to collapse
Well, Stock Recovery is a bit tricky to use... In my particular case I use the vol up/down to select menu entry, and I tap on [ok] (I usually have to tap several time to have the [ok] actually do something. Once it starts, yes, the Wipe is very slow! Like 1-2 minutes.
rob-t said:
Update2: Ok yeah, still not working. Tried three times now. Can't get to Tenfar Custom Recovery after flashing the devtree sbf no matter what I do. If I leave it plugged in after flashing devtree and allow RSD lite to reboot the phone, I get "please manually power up this phone" and a blank screen. If I reboot manually, I just get the motorola logo forever.
Click to expand...
Click to collapse
That is weird... Anyway I'll double check later, but it's what I have written on my notes, and I've followed my notes a lot of times, so I guess this order worked for me at least.
rob-t said:
Update4: Yeah, your instructions are backwards. I should have noticed that right away, but didn't notice until I tried Higgsy's 2.2.1 Froyo build. You need to flash the boot+devtree sbf AFTER you restore the Adlxmod F4D v2.00 folder image - i.e. follow these steps: http://forum.xda-developers.com/showthread.php?t=937319
If you do it in the right order, this ROM works fine and is actually pretty cool (first boot takes a long time of course so be patient.) PM me when you fix your instructions and I'll remove this.
Click to expand...
Click to collapse
I guess there is nothing wrong in flashing the boot-devtree sbf at the end, it should work the same, so I have updated the instruccions here. Maybe it reduce the problems. Anyone here with the same issue? If so, from what rom do you come from?
Also, one more thing: if you come from another UK or US based froyo rom, you should be able to skip the whole procedure and just restore the nandroid backup.
adlxdum said:
Also, one more thing: if you come from another UK or US based froyo rom, you should be able to skip the whole procedure and just restore the nandroid backup.
Click to expand...
Click to collapse
ill give that ago running uk 2.2
Nice rom, will feedback you...
can confirm that if you already running 2.2 all you need to do is run the nadroid back up and all should be good btw dude nice rom
First of all thanks for this rom! I am expecting my Defy over the mail by monday or tuesday and up till now this rom is the most appealing.
I have one question. How do you prevent motoblur installation? Is that simply a matter of skipping at first boot? Do you have plans to make a deblurred version of your rom?
coming from a 2.2 Chinese rom, it stuck on motoblur animation and didnt boot, i followed each letter from the instructions , no luck on this yet.
that happened to me pulling the battery sorted it and it booted fine after that
i think native boot+devtree would be better, so here it is.
racca said:
i think native boot+devtree would be better, so here it is.
Click to expand...
Click to collapse
I also had this one, but as the US one was working correctly I sticked with it. I have posted what I have tested.
Boot loop in Motoblur Animation?
fabianowerner said:
coming from a 2.2 Chinese rom, it stuck on motoblur animation and didnt boot, i followed each letter from the instructions , no luck on this yet.
Click to expand...
Click to collapse
If you have Boot loop in Motoblur Animation, please try this:
- Boot your Defy into Stock Recovery (Power + Volume Down button)
- Tap in the bottom right corner of the screen to get into the menu
- Select Wipe Data, then press OK
- Reboot phone into USB Bootloader Init mode (Power + Volume Up button)
- Flash the boot+devtree sbf provided by me using latest RSD Lite (4.9) & latest Motorola drivers (4.8)
Then reboot. How does it go?
adlxdum said:
I guess there is nothing wrong in flashing the boot-devtree sbf at the end, it should work the same, so I have updated the instruccions here. Maybe it reduce the problems. Anyone here with the same issue? If so, from what rom do you come from?
Click to expand...
Click to collapse
Thanks, yeah I was coming from Eclair 2.34, so I should be downgradable. Can confirm that the camera works fine on this ROM.
Sadly, I have the dreaded "Unable to open connection to server" problem with Android 2.2 so no more exchange email.
Update: Ran a quadrant benchmark on my phone with this ROM, got 1299, so pretty good! I haven't removed any apps, and also added SetVsel and DroidWall. Overclocking in SetVsel was set to: 1000mhz/52 600mhz/36 300mhz/26. About the same speed as I had going in Eclair.
Missing WIpe!
There was a missing step (to Wipe all) in my instructions, sorry. It's fixed on the first post.
- In Recovery, Select Backup & Restore -> Restore > Select the rom Adlxmod F4D v2.00 folder
- Get back to the Recovery Menu, and WIPE ALL once more.
Click to expand...
Click to collapse
Hmmm, I'm not sure having both email apps installed is a good idea. Once you get past setup in either app (took about 20 tries but finally it connected to the server and completed setup), either app will both force-close as soon as they are launched. Were you actually set up an exchange account during testing of this rom?
Will give this a try, Is market working?
also can i flash the data.img from my backup to restore my apps and data?
Dear Owners,
Discontinued
In this post you can find a multilingual (mainly European) modified rom for the smartphone Lenovo A820.
IMPORTANT NOTE!
The newer phones do not work well with S138 or older kernel (no info about S147).
The sympthom is that the touch screen works on inappropriate way: after the first screenlock it does not work again.
For this reason it is highly recommended that update your kernel if you have got this issue.
The kernel changer to S150 zip can be run from modified recovery (CWM, TWRP, COT, Carliv, etc...).
Note that all the things in this thread you do with your phone can be dangerous. I cannot take responsibility for your phone damage.
So, do it at your own risk.
Before you do anything, I recommend you to save your current ROM (I would say it is mandatory!)
There are many ways to save and I highlight some (links will be added later):
1, for non-rooted phones:
- SP_Flashtool, readback option.
- CWM (or TWRP) backup, if it is available on your phone
2, for rooted phones:
- MTKDroidTools backup
- command line dd-backup
In order to install this ROM, you need to have CWM recovery on your phone.
If you have not got this recovery or you do not know which recovery you have got, you have to read post#3 before you do anything.
If you get error during the installation of the ROM, see post#4.
The restore option of the CWM rcovery is not as good as it could have been expected, so please read post#4 carefuly for CWM restoration issues, tricks.
Update: CWM 6.0.4.0 with S150 stock kernel.
Just to clarify the power-on modes:
Normal phone mode: press the power button
Meta mode: VOLUME DOWN + POWER
Factory mode: VOLUME UP + POWER
Recovery mode: VOLUME DOWN + VOLUME UP + POWER
Consider the warranty issues, you need to backup you rom.
In addition, I always suggest to do a backup before install any new ROM to your phone.
You can do it with CWM recovery in backup menu.
About installation in general.
Pre-requisites: CWM recovery menu installed on your phone. (This ROM can be installed from CWM recovery.)
The ROM file must be saved on your physical SD card.
Enter into CWM recovery.
In CWM recovery you can go up/down with the volume up/down keys. The “enter” is the power button.
Choose the “install zip from SD card” menu item.
Choose the “choose zip from SD card” menu item.
Select the rom you want to install.
Choose “OK” in the menu item.
If you need a detailed explanation of its use, see the tutorial : http://bm-smartphone-reviews.blogspot.com/2012/02/complete-guide-to-clockworkmod-recovery.html
Right after the ROM installation has been finished, you can install gapps as well, before restart.
Windorws driver installation:
Please do not ask me about it. I use mainly Linux, which is more friendly.
What I did in XP under Virtualbox was:
Downloaded the Lenovo drivers from here: <link>
Manually added the com ports in control panel.
MOD CP4.0
V1
The modified rom has got the stock kernel - Lenovo A820_ydss_S135_130403
This completely changes your phone appearance, your Lenovo UI will be disappeared.
Also Lenovo applications are not integrated to this rom.
It will look like the stock Jelly Bean.
Main features:
-The firmware is rooted.
-Boot logo, boot/shutdown animations and sounds are changed to Lenovo.
-Minimalist appearance and content, for this reason you have to install google applications manually, from CWM recovery <link>. After gapps installation everything works well (many people wants to have mainly Google Play. It do work.)
-Slide unlock.
-Multilingual. For supported languages, see the screenshots.
-The default language/region is Hungarian, but you can easily choose your one.
Known bugs:
- I found was that the charging logo with turned off phone is not proper.
-the camera does not work adequately in video-camera mode.
-the default setting in some of the application is V987.
V2
The modified rom has got the stock kernel - Lenovo A820_S135_130403
The camera was changed to a non-multilingual one. It looked that the black screen in camcorder mode solved.
But after googleapps something went wrong... black screen again.
V3
The modified rom has got the stock kernel - Lenovo A820_S135_130403
In V3 there is not any significant changes (camera app was changed back to the multilingual one), but I modified the gapps, which caused the camcorder issue.
So, for this modified rom you need to use this gapps.
V3 download link: CP4.0-by-cappa72-v3 - dropbox
or
CP4.0-by-cappa72-v3 - 4shared
Bug: Still, the camera has got green lines in the case of playback.
CP4.1
V1
The kernel has changed to A820_YDSS_S130_130324.
The camera application does not generate green bands in playback.
The default language was set to English, default time zone was set to London.
CP4.1-by-cappa72-v1
You can use the googleapps mentioned for CP4.0-v3
CP4.2
V1
The kernel has changed to A820_S138_130419
CP4.2-by-cappa72-v1
Bug list
#3 - CP4.2-v1 - Wen try to choose themes, the laucher is Force Closed (FC) - Settings was modified to resolve this issue.
#4 - CP4.2-v1 - Serial number is 0123456789ABCDEF instead of the original S/N - not a real bug
#5 - CP4.2-v1 - Under the battery level of 15% the SystemUI is Force Closed (FC) - was a user error, when people deleted the necessary ui files.
CP4.3
This release will be the continuation of the 4.2, but with the newest available kernel (S150) and will (plan) contain all the things that are included in the 5.3.
This will not be with Aromainstaller and will contain the gapps.
Hopefully comng within two weeks.
MOD CP5.3
Available now (25.11.2013.)
CP5.3
V1
Change log; what’s new compared to CP4.2
Aromainstaller is used for optional installation possibilities.
- still Jelly Bean 4.1
- kernel is the stock S150
- Modified systemUI by [email protected] (1% battery signal; automatic hide function for non-used sim signal)
- Modified Settings by apeelme (sloving bug #3)
- Baseband is from the stock ROM S150.
- gps.conf is set to EU by default
- apns.xml is modified for Telenor-HU from “net” to “online”
- gps-tracker solver added to build.prop (dalvik.vm.execution-mode=int:fast)
- libvcodecdrv.so replaced to solve green bars in case of video playback.
- updated MobileUncleTools (2.9.5) in case of 3rd party SW.
There is no default ringtone set! Right after the installation you have to set the ringtone, message alert and so on... otherwise your phone will not play sound...
Important feature!
If you have already repartitioned with the script, you can simply install this ROM, it will recognise that the repartition had been done; and you do not have to run "disable internal SD card" script from CWM.
But please note that this function is onyl available with the repartition script; with Meteos rom editor repartitioning this function is not available.
Right after the installatio, there is not any sound set. Nor the ringtone, nor the message an alert. So, you have to set it first.
Available on mediafire : Link
md5sum: 86e241fcac6faf4fa6baf0f9cc4a18a0
Additional possibility:Change of FM radio
The FM radio can be changed back to Lenovo’s one with this script. It was requested by some people due to the fact that Lenovo’s FM radio can work without connecting the earphone.
The link is here. http://data.hu/get/6494163/FM-radio-change.zip
You can install it from CWM recovery, with the same method that you used during the installation of the ROM. This script does not affect any other part of the ROM, but the FM radio.
Repartition
Please DO NOT USE IT for Lenovo-based ROMs. Sometimes it can cause bootloop or other inconvenience.
The repartition of internal memory of the Lenovo A820 phone has been solved already.
With this action youd intednal SD card will be disappeared and will be added to the /data partition.
Before you do anything, make a CWM backup, and save all your data from internal SD card!
The easiest way is to use this CWM script, if you want to have the maximum available size (2,7GB) for the /data partition.
You have to install it from CWM recovery.
After the installation you need to do a factory reset.
After the factory reset, you have to disable your internal SD card, with CWM script.
And then, you can reboot your phone to check if yo have got the new size of /data partition:
settings --> storage
"internal data storage; full capacity 2,7GB"
"internal SD card; full capacity <your physical SD card capacity"
If the above data appear, you have successfully repartitioned you phone's internal memory!
If you want to have your data back, go into CWM recovery, and choose
backup and restore --> advanced restore --> <choose your save> --> Restore data
And then, your data are available again, after the reboot.
Please do not use it, if you do not want to have the 2,7GB of /data partition!
For Lenovo-based ROMs you need to use Meteos-apk for repartition of A820.
Internal/external SD card exchanger
If you want to use your physical SD card as the default one, and still want to use your emmc-SD card (aka internal SD card by default), you can change it by this CWM script.
Important link in summary:
The driver what works is here.
The original stock recovery is here
The autoroot package can be found here.
The preferred CWM is here.
The root script is here, you can install is from CMW, and your phone will be rooted.
The usable Flashtool is here.
The scattel file for Flashtool is here.
Credits:
bgcngm for the base of the ROM (BM1.0 for ZTE V987), and his amazing tutorials
iBotPeaches and brut.all for apktool
dsixda for his ROM kitchen which is really helpfull for easy-deodexing
Koush for his wonderfull CWM recovery
amarullz for his amazing AROMA installer
...and finally to all the devs whose apps, tweaks and scripts I have used on my custom ROMs
Very nice Thanks for your hard work and good luck
CWM recovery
Installing CWM on your phone
You need to install proper drivers to your computer.
Available (ported) CWM recoveries:
With newest kernel:
CWM recovery 6.0.1.2 - S150 - ported from [email protected] ZTE V970 recovery.
CWM recovery 6.0.4.0 - S150 - ported from [email protected] ZTE V967S recovery.
CWM recovery 6.0.1.2 - S138 - ported from [email protected] ZTE V970 recovery.
CWM recovery 6.0.1.2 - S135 - ported from [email protected] ZTE V970 recovery.
Option 1, with SP Flashtool
Download the SP_Flashtool software to your computer. Extract it to a directory, where you want to run it from.
Download the scatter file, which you will need if you want to use SP_Flashtool.
Download the CWM
(5.5.0.4, 6.0.1.2, 6.0.2.8; it is your decision)
Run the SP_Flashtool.
Browse your scatter file.
Choose only the recovery.
Tick the “DA DL all with checksum” (you can find it close to the download button). It is a really important point!
If your phone is connected, let’s disconnect it from the computer.
Turn off your phone. Take the battery out from your phone for 5 sec. Insert the battery to you phone. Keep it still turned off.
In the flashtool press the Download button.
Choose OK to the warning message.
Connect your phone to the computer.
The flashtool will flash the recovery into your phone.
When the green circle appears, wait for 5-10 secs, and the unplug your phone.
If everything went well, you can enter into the recovery menu (see 1st post, power-on modes)
Option 2, on rooted phone, with MobileUncleTools.
Install MobileUncletools 2.8.x or higher from the Play Store.
Save one of the CWM I linked to the root directory of your physical SD card.
- select menuitem Recovery Update. The program will list the available recovery images.
- choose the one, what you want to install
- It asks back: "Are you sure flash recovery!" - Use recovery file: <name of the recovery what you choose previously>. Tap to OK.
- After the flashing process it offers you to reboot into recovery. If you tap OK, it will automatically reboot your phone to recovery. If you tap cancel, you can use your phone as a phone.
- Before you tap to "reboot to recovery", I suggest you to wait approx. 5-10sec.
Use of the CWM.
If you enter into the CWM (6.x.x.x) recovery, the following buttons can be used:
- Power button : “enter”
- Volume down : step down in the menu
- Volume up : step up in the menu
- Soft key “option”: step down in the menu
- Soft key “back” : step back in the menu
In 5.x.x.x you cannot use soft keys, but the physical buttons works on the same way as in the case of 6.x.x.x
CWM restoration
I experienced failures in restoration of the CWM backup.
This was a real surprise for me because I have not faced this issue with other MTK phones.
So, the issue is that the CWM restoration does not work immediately.
In details:
-I saved the stock rom by CWM 6.0.1.2 (CWM was complied by Bruno, and I modified it for A820)
-For checking the restore function, I did a factory reset: the phone stopped working.
-I did the CWM restoration, but still the phone stopped at the boot animation. And stayed it for 15min. I removed the battery then.
In order to solve the issue, the following method was done:
-In the advanced restore I choose the restore /system (only!)
-After restoring the /system I turned off the phone took the battery out, waited 5 secs, inserted the battery back.
-Turning on the phone it worked again with the restored data, BUT the internal SD card was injured! I formatted the internal SD card – with this action I lost all my data that were saved on the internal SD card.
So, please be careful using it! Save your internal SD card data before the CWM restoration!
This was experience in case of all the available CWM (5.5.0.4, 6.0.1.2, 6.0.2.8).
Installation issues
Post#4 troubleshooting
If you cannot install the ROM by an error:
Code:
assert failed: getprop("ro.product.model") == "Lenovo A820"
E:Error in /sdcard/Lenovo-a820-update-CP4.0-v1.zip (status 7)
This is a safety feature, not a bug.
This error message is a warning that you have not got the proper CWM. (Most of the available CWMs are based on ZTE, STAR phones and contain improper model description.
My CWMs contain the proper one, I modified them, so you need to install a CWM I mod for Lenovo A820.
In this case you have to update your CWM to a ported one that I did.
Great!
I would love an multi lingual rom, but for now I just want to root it. (ones it gets delivered that is)
Are there tools specific for this device to root is with out flashing?
Checking out your rom in the meantime. :fingers-crossed:
ebsbow said:
Great!
I would love an multi lingual rom, but for now I just want to root it. (ones it gets delivered that is)
Are there tools specific for this device to root is with out flashing?
Checking out your rom in the meantime. :fingers-crossed:
Click to expand...
Click to collapse
If you have got CWM recovery on your phone (or a chinese one that has got "xx SD yyy ZIP" menuitem), then you can use root-zip, installing it from CWM recovery.
Thanks
Thanks
Where are the screenshots?
please add some screenshots.
deathhand said:
please add some screenshots.
Click to expand...
Click to collapse
I tried to upload some, but the server was down that time.
I will try it again tomorrow.
Thanks for this rom, I flashed it succesfull on the Lenovo A820, it also takes away that terrible skin from Lenovo.
Gapps link
Thnak you for your ROM. I tried it for a couple of hours and there some minor problems that I don´t know if there are rom related.
1. There is no link to the gapps, so I downloaded a random one and I have errors with google search.
2. The videocam record with a green band on one side.
3. The gps is slow, doesn´t pick satellites easily.
4. If you choose automatic time the it always consider that you´re in china. If you choose manually your timezone then it is ok.
Overall it is a very well-done rom and I would keep it for daily use.
Thanks
1. Are you sure you downloaded the Gapps for Android 4.1.x? You should have this gapps version: gapps-jb-20121011-signed, this the right version you should flash. I first flashed the rom and after that the gapps.
I have reproduced your issue and you need to update the Google search app in the playstore, after that the errors are gone.
2. I have reproduced what you reported, I want to try if I can grab the original camera app from Lenovo and see if it still has the issue, but I don't think its a big problem, I bought the phone for someone else, but this issue is not to big, I don't suppose people often record with an smartphone and this rom at least got Dutch in, the original phone firmware was bloated with China Unicom bloatware, Lenovo skin and had no Dutch support.
3. Try GPSfix, ussualy this kinda works, but the MT6577 chip was know for having GPS problems, perhaps its the same with MT6589? But there are many apps out there that can help you fix it.
I think this in a great rom, Lenovo is a big brand in China, so many will choose Lenovo and with this rom you get rid off the terrible lephone skin, I mentioned this rom in my review about this phone
Oh here you got some screenshots.
Feel free to use them in the OP.
Don't know about you but I do use my device a lot for video recording.
I think it is imperative that all basic functions work flawlessly.
The custom rom's with android 4.2 also have an video bug at this time, which is a bit unacceptable.
I'm sure it will be sorted out :victory:
Well yes, but having fully Dutch support is better, you can always flash new update off the custom rom when it get fixed. I only recorded a few time video with my own smartphone.
Lebrija said:
Thnak you for your ROM. I tried it for a couple of hours and there some minor problems that I don´t know if there are rom related.
1. There is no link to the gapps, so I downloaded a random one and I have errors with google search.
2. The videocam record with a green band on one side.
3. The gps is slow, doesn´t pick satellites easily.
4. If you choose automatic time the it always consider that you´re in china. If you choose manually your timezone then it is ok.
Overall it is a very well-done rom and I would keep it for daily use.
Thanks
Click to expand...
Click to collapse
1, I have added the link.
2, Thanks for the feedback, it is really useful to know. The playback contains the green band, the file itself does not.
I changed the kernel to the '130'-one, and now it works with the camera application, and the playback is also correct.
3, You shall try the EPO / A-GPS support for getting it better. Or thy DexterMorganNL's suggestion.
4, I have never faced this issue, but in the new version I set the default time zone to London.
The new one is available, you can see it in the first post.
cappa72 said:
1, I have added the link.
2, Thanks for the feedback, it is really useful to know. The playback contains the green band, the file itself does not.
I changed the kernel to the '130'-one, and now it works with the camera application, and the playback is also correct.
3, You shall try the EPO / A-GPS support for getting it better. Or thy DexterMorganNL's suggestion.
4, I have never faced this issue, but in the new version I set the default time zone to London.
The new one is available, you can see it in the first post.
Click to expand...
Click to collapse
Thank you for your time. I will try the new version. But, why have you used an older kernel?
By the way, with version 3 I also had some problems with the gyroscope when playing Real Racing 3.
Great work
Its great you released the update so fast, you brought us really good work. I think new owner off this phone is going be thankful, they requested me to buy a phone for them while I'm in China, and when I got it it was not fully Dutch supported, had the terrible skin.
So its great have this phone, because this way I can deliver it without the Chinese bloatware and with full Dutch language and ofcourse Google apps.
EDIT
The newest release gives me a black screen after I boot it up after having it flashed, so I have reverted back to your previous release.
OK. I'm ready to weep.
I've previously had a ROM from NeedRom on my A820.
I'd like to give Cappa's ROM a try, but when I try to install from CWM Recovery I hit the Error outlined in Post 4.
I then follow the advice of Post 3... But there are no links to A820-compatible CWM Recovery installations. I found one on a hungarian site linked to Cappa, but all I get is a .img file and no idea how to get that on to my phone.
Can anyone post detailed instructions, or send me to a page (in English) where I can find instructions on how to get the ball rolling so I can use Cappa's ROM?
Thanks.
Google is my friend. Yes. But Google Translate isn't.
TheTen said:
OK. I'm ready to weep.
I've previously had a ROM from NeedRom on my A820.
I'd like to give Cappa's ROM a try, but when I try to install from CWM Recovery I hit the Error outlined in Post 4.
I then follow the advice of Post 3... But there are no links to A820-compatible CWM Recovery installations. I found one on a hungarian site linked to Cappa, but all I get is a .img file and no idea how to get that on to my phone.
Can anyone post detailed instructions, or send me to a page (in English) where I can find instructions on how to get the ball rolling so I can use Cappa's ROM?
Thanks.
Google is my friend. Yes. But Google Translate isn't.
Click to expand...
Click to collapse
Update, I think I sorted it...
Bit of imagination (and could have totally done the wrong thing, but it seems to be making progress...)
I decided to take a known ROM install that I've tested and that works, which has a recovery.img included, and I renamed the recovery.img to recovery_bak. I then renamed my 'new' CWMRecovery image to recovery.img and dumped it in the directory with the ROM data that I got off NeedRom. I loaded up SPFlashTool and loaded the scatter file from that ROM, then deselected every component except 'recovery' and flashed it.
End result is that I have a phone which recovery-boots to the version 6 cappa-modded CWMR which I found on the Hungarian site, and in turn that CWMR has just installed both the required ZIP updates outlined in Post 1, and Cappa's ROM is now sat on my second A820 awaiting setting up...
I hope I did the right thing, and this won't come back to bite me in the ass later... The newer recovery.img was slightly larger than the old one, but I'm assuming that the scatter file isn't about storing specific pieces of the ROM in specific places based on exact size of file, and thus perhaps all things will continue to work swimmingly.
Galaxy Note 5 PC3 Marshmallow Stock Deodexed Rom
This build is based on the stock PC3 6.0.1 Marshmallow build.
This is a first release. Even though it has been tested, please report any issues.
You MUST be running a Marshmallow bootloader to run this rom!
The FULL odin firmware must be flashed at least once to prep the phone. It is available here -- > Marshmallow 6.0 Odin files N920PVPU2BPC3
Features:
- Rooted
- Busybox
- Hotspot enabled
- Knox Removed
- ItsOn Removed
- 5 way reboot
- Signature verification removed
- Netflix & screen mirroring fixes
- All apps updated to current versions
Download Link ---> N920P_PC3.6.0.1.De-Odexed.Ver1.1.zip
MD5 Checksum: 324eb4f81999acb0d39ad68f3ed4abb2
Rom Installation
Preparing the stock rom
• In the stock rom, turn on developer mode, enable USB debugging and OEM Unlock
- Settings>>>about device>>> scroll to bottom and tap build number 8 times
now press back button once and tap developer options...
- Toggle on both USB debugging and OEM Unlock.
• Copy the downloaded rom.zip file to internal storage
Install Custom Recovery with Odin
• Download Odin & custom recovery tar
Odin3_v3.10.6.zip
twrp-3.0.2-0-M-nobleltespr.tar.tar
• Extract Odin zip-file
• Power down the phone
• Open Odin on pc
• Boot phone in Download Mode (press and hold Home + Power + Volume Down buttons)
• Connect phone and wait until you get a blue sign in Odin
• Add the recovery file to AP / PDA (depending on version of Odin)
• Make sure re-partition & Auto Reboot are NOT ticked
• Click the start button and let the Odin flash complete
• Unplug & Reboot phone directly into Recovery Mode
(press and hold Power + Volume Down buttons and as soon as the phone reboots hold Home + Power + Volume Up buttons )
• BACKUP YOUR CURRENT SETUP WITH TWRP
• Do a FULL wipe but do not reboot yet
A full wipe includes:
Dalvik Cache
System
Data
Cache
• Flash rom and reboot.
Code:
[B]Changelog:[/B]
[B]Version 1.1[/B]
- permission fixes tnx to [user=3699616]@mwilky[/user]
- SuperSU Beta updated to v2.71
- OTG storage fixed
- Gear VR fixed
- Fixed something else, I just don't remember what it was ;)
[B]Version 1.0[/B]
- initial release
Android M Debloat tool
Attached at the bottom of this post.
HIGHLY recommended to remove all the unnecessary bloat.
Flash right after rom install (before rebooting) for best results.
Credits:
@mwilky for permission fixes to get things running the way its supposed to
@SuperR. for the rom kitchen and his ongoing support
Note 5 Recoveries
Note 5 Kernels
Sprint Galaxy Note 5 Modems
** Modems are flashed in Odin. The tar file gets placed in the CP slot.
================================================
Mini-Bootloaders
These will allow you to flash between 5.1.1 and 6.0x with ease.
Important note:
- You MUST flash the full marshmallow tarball at least once to prepare the phone.
- You MUST match the Bootloader version to your backup, they are not interchangeable. The OK3 firmware will run older versions of 5.1.1 too.
Mini Bootloaders Link
OK3 = 5.1.1
PA2 & PC3 = 6.0.1
Use of Mini Bootloaders:
- These do not include the OS and REQUIRE that you have a matching OS backup already saved to restore
- Flash the bootloader with Odin (same instructions apply as rom flash in Post #1). Make sure you uncheck the auto reboot choice first.
Once the flash is complete unplug the phone, press and hold pwr + volume/down to reboot and as soon as the phone resets, immediately press pwr + home + volume/up to enter custom recovery and restore your backup.
** If you missed the key sequence try again, it takes good timing but I'm sure you'll be a pro at it in no time.
Just for Fun
ZTE 'DiscoBall' Lockscreen
- two finger hold on disco ball brings up extended shortcut menu
- works ONLY on swype type lockscreen
- does not have onscreen notifications, its just a cool little app
- little bug, pressing home button takes you right to the desktop so be aware if you carry this in your pocket, it may unlock on its own
SElinux permissive or enforced?
primaleph said:
SElinux permissive or enforced?
Click to expand...
Click to collapse
Stock kernel.
So we have to be on mm to flash this? This might be a dumb question, is there anyway of being on 5.1.1 to flash this?
Tdunham always got our hack thanks bro
Sent from my SM-N920P using XDA Premium HD app
Debloat tool updated v1.1 to deal with some of those nasty Sprint apps that get installed to the data partition if you forget to flash it before the first boot.
Known issue - some of the Sprint bloat will popup with some errors that they cannot install. Not really interested in getting all the downloaded bloat working at the moment, just thought I would point it out to prevent some questions.
tdunham said:
Debloat tool updated v1.1 to deal with some of those nasty Sprint apps that get installed to the data partition if you forget to flash it before the first boot.
Known issue - some of the Sprint bloat will popup with some errors that they cannot install. Not really interested in getting all the downloaded bloat working at the moment, just thought I would point it out to prevent some questions.
Click to expand...
Click to collapse
To fix this, remove Sprint ID. Freezing it or hiding it with Debloater may not be enough.
Is there a kernel for this rom?
tdunham said:
Galaxy Note 5 PC3 Marshmallow Stock Deodexed Rom
This build is based on the stock PC3 6.0.1 Marshmallow build.
This is a first release. Even though it has been tested, please report any issues.
You MUST be running a Marshmallow bootloader to run this rom!
Features:
- Rooted
- Busybox
- Hotspot enabled
- Knox Removed
- ItsOn Removed
- 5 way reboot
- Signature verification removed
- Netflix & screen mirroring fixes
- All apps updated to current versions
Download Link ---> N920P_PC3.6.0.1.De-Odexed.Ver1.0.zip
Rom Installation
Preparing the stock rom
• In the stock rom, turn on developer mode, enable USB debugging and OEM Unlock
- Settings>>>about device>>> scroll to bottom and tap build number 8 times
now press back button once and tap developer options...
- Toggle on both USB debugging and OEM Unlock.
• Copy the downloaded rom.zip file to internal storage
Install Custom Recovery with Odin
• Download Odin & custom recovery tar
Odin3_v3.10.6.zip
twrp-3.0.0-3-M-nobleltespr.tar.tar
• Extract Odin zip-file
• Power down the phone
• Open Odin on pc
• Boot phone in Download Mode (press and hold Home + Power + Volume Down buttons)
• Connect phone and wait until you get a blue sign in Odin
• Add the recovery file to AP / PDA (depending on version of Odin)
• Make sure re-partition & Auto Reboot are NOT ticked
• Click the start button and let the Odin flash complete
• Unplug & Reboot phone directly into Recovery Mode (press and hold Home + Power + Volume Up buttons)
• BACKUP YOUR CURRENT SETUP WITH TWRP
• Do a FULL wipe but do not reboot yet
A full wipe includes:
Dalvik Cache
System
Data
Cache
• Flash rom and reboot.
Android M Debloat tool
Attached at the bottom of this post.
HIGHLY recommended to remove all the unnecessary bloat.
Flash right after rom install (before rebooting) for best results.
Click to expand...
Click to collapse
Freaking cool dude..
It says my USB storage is corrupt. But I put in my S6 and it works fine. I even formatted it and it still says corrupt. If you could upload a patch to fix that'd be sweet. That's the only issue I've come across. Thanks for the ROM.
---------- Post added at 06:54 AM ---------- Previous post was at 06:46 AM ----------
I even went into TWRP and it let me mount USB storage and select from it. So gotta be something in ROM that keeps saying it's corrupt. Thanks again.
The hotspot hack you have on this rom, do you use The HiddenMenu.apk from the OK3 Rom?
Androidwarrior said:
The hotspot hack you have on this rom, do you use The HiddenMenu.apk from the OK3 Rom?
Click to expand...
Click to collapse
No, patched in services.
Bobthahog said:
It says my USB storage is corrupt. But I put in my S6 and it works fine. I even formatted it and it still says corrupt. If you could upload a patch to fix that'd be sweet. That's the only issue I've come across. Thanks for the ROM.
---------- Post added at 06:54 AM ---------- Previous post was at 06:46 AM ----------
I even went into TWRP and it let me mount USB storage and select from it. So gotta be something in ROM that keeps saying it's corrupt. Thanks again.
Click to expand...
Click to collapse
I'm hearing about this on other versions of MM as well. Someone suggested that they formatted the SD on the phone and its working fine again.
As far as I know, its not doing it on stock but this version is so new that I cant verify if it has something to do with marshmallow being deodexed or what the issue is with that. We'll have to keep an eye on it. I have a few smaller SD cards, maybe I'll start swapping them around to see if I can duplicate it. We need more information and input from other people. :good:
tdunham said:
No, patched in services.
Click to expand...
Click to collapse
If the prl or profile gets updated will it break the hotspot hack?
Androidwarrior said:
If the prl or profile gets updated will it break the hotspot hack?
Click to expand...
Click to collapse
Dude, you've run a bunch of my stuff, has that EVER broken hotspot?
For everyone else, the real answer is no.
Quick question. Does the MM debloat tool effect GearVR?
For those with internal storage issues, open up a terminal & try
su
restorecon -FR /data/media/0
Not sure if will work but it would on my Nexus 5 when I encountered that issue.
Can this be used as a daily
I just stumbled onto this thread. Is the ROM buggy? I can't tell from the comments
Flashed this morning and running great. Good work Dunham. Question, what was the ad block app you used on MOAR rom?
Hi,
Hope somebody got some more tips or a fix for the following problem i have with my huawei mate 9 C432 (europe version) (bought 2nd hand with this problem)
* Phone came with not working touch at android lock screen ONLY (brown wallpaper, water dock, clock works, icons show like normal)
* When i go to recovery everything works fine, NO touchscreen problem at all.
* Couldnt get my product id number inside settings to generate unlock bootloader code so i used DC PHOENIX, DC UNLOCKER, HCU. FLashed the following with DC phoenix, this unlocked my bootloader.
- Flashed MHA-AL00A_HLMHAAL00AM00A063_Factory_firmware_China_Nonspecific_Android_7.0_EMUI_5.0.dgtks
- MHA-L29B_C432B185_Firmware_Switzerland_Nonspecific_Android7.0_EMUI5.0.APP
- L29B_C432B185_update_MHA-L29_hw_eu.APP
(In this order)
After Flashing these 3 files my phone boots like normal and STILL i get the same touchscreen problem at the lockscreen (brown wallpaper). Recovery works fine, fastboot also.
Then i decided to flash only the FACTORY FIRMWARE CHINA NONSPECIFIC 7.0 DGTKS file >>>>>> Now at this lockscreen the touchscreen magically works and i can do whatever i want in the settings (android 4.2 i believe). No problems at all. Problem is i cant stay at this HUAWEI ASCEND (bootlogo) firmware. I want Android 7 / 8 for Huawei mate 9.
After this i also flashed TWRP recovery and did a format CACHE, DALVIK, SYSTEM, DATA and then installed custom firmware RomAur-v2.2 from this forum.
After flash i get the freaking brown bridge lockscreen AGAIN with no working touchscreen. The phone doesnt give me any SETUP (language, wifi etc) option at all before lockscreen, with Samsung phone roms i usually have to setup the custom rom first. None of that here.
Highlighted some "maybe" important info??
===========================================================
Twrp Custom Rom RomAur-v2.2 flash log:
RomAur B197 v2.2 by auras76
>>> Mounting partitions
>>> Writing system
>>> Creating toolbox symlinks
>>> Setting permissions
>>> Flashing Boot
>>> Installing Busybox
>>> Installing Magisk...
**************************
* Magisk v14.0(1400) Installer
**************************
- Mounting /system, /vendor, /cache, /data
- Device Platform: arm64
- Constructin Enviremonment
- Adding addon.d survival script
- Found Boot Image: /dev/block/sdd32
- Unpacking Boot image
- Checking ramdisk status
- Stock boot image detected!
- Backing up stock boot image
- Patching ramdisk
- Repacking boot image
- Flashing new boot image
- Unmounting partitions
- Done
>>> Enable init.d...
***********************************
System/Less Module Template
***********************************
A simple init.d emulator (@korom42)
***********************************
- Magisk/Systemless Install
- Mounting /system(ro), /vendor(ro), /data, /cache ! Magisk is not installed!
>>> Unmounting partitions
>>> Installation Complete!
script succeeded: result was [>>> Installation Complete!]
Update partition details
....done
So hope it a bit clear for you guys, maybe you can help me??
What could this be? I was think about some corrupt touchscreen related files that are present on the internal space of the phone that are stuck in there and need to delete them?? Maybe some boot image that doesnt get flash.
THANKS
No help so i fixed it after spending too much money on tools and testing for days. Nevermind its fixed now.
Dramacydril said:
No help so i fixed it after spending too much money on tools and testing for days. Nevermind its fixed now.
Click to expand...
Click to collapse
hi
i have this problem too
if you fixed it please tell me how?
thanks
{
"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"
}
V 3.0 - EMUI 8.0DONOT COPY MY WORK, Ask for Permissions
Code:
- I am not responsible for the damage of your cell phone if you do not correctly perform the steps
- loser warranty
- if you are not sure better not to touch and leave this page
COMPATIBLE WITH
with all versions, P20 lite, remember to know your original compilation if at any time you want to return to stock for example ANE-LX3C25 with this data you can return to stock.
This version is based on the official modification of EMUI, activating functions that are in the high-end versions, adding some modifications for their better performance.
REQUIREMENTS:
- EMUI 8.0.0
- Activate the OEM unlocking, which is in adjustment / developer options and leave it so forever to avoid conflict.
- unlock the bootloader.
- install the recovery that I will leave, automated from windows-linux
Guard the rom in an external memory.
Turn off the cell phone press the plus and power buttons until you have the TWRP window
Press WIPE
Press FORMAT DATA
Write the word "yes" without quotes and accept, just do the work
Press BACK to go back several times to the main window.
Press WIPE, then ADVANCE WIPE
Verify that the partition DATA this in the f2fs extension
Mark: Dalvik, cache, data, internal storage, system
IMPORTANT !: do not mark "micro sdcard".
Once you have marked, slide the "swipe to wipe" arrow to clear it.
Go back to the main sale, press INSTALL
Press SELECT STORAGE
Switch to Micro SDCard to find the rom.
Look for the MORFUZ rom and flash
At the end of the installation press "wipe davilk-cache", wait for it to finish.
Reboot system.
Congratulations now will start the rom MORFUZ
It seems that Huawei modified the modem partition in the September-October patch and the MORFUZ kernel does not work incoming and outgoing calls.
-IMPORTANTonly install this module from the root Magisk options if incoming and outgoing calls do not work.
https://mega.nz/#!F7oXzSRZ!8uuSCIx4UTbuWkTEYoFmTXTCwvIr6Reuc1vyq6OIhw0
Rom Siriuz
https://mega.nz/#!tYBjTQhC!yPbPXkazpQUy7bzLdm33rEapihBB8iVmSGlGxy1RweI
TWRP Mod by catuva21 - VERSION 2
unzip, the file is automatic
https://mega.nz/#!uD4FlCqL!ERBzP4ZWa2sR8f_wnn15F_cOFCdYVKgfYETjiehQkkQ
TELEGRAM GROUP
https://t.me/joinchat/ERAhfQ8kyF6_iH5nMun5dg
Contributors:
CATUVA21
Credits:
- Openkirin Recovery TWRP
- Alexxx1
- Chisetdel31260
ROM OS Version: ANE-L
ROM Kernel: Stock
ROM Firmware Required: EMUI 8.0.0
Version Information:
Status: Stable
Created on: 2018-06-30
Last Updated on: 2018-09-10
DESCRIPTION ROM SIRIUZDETAILS OF THE ROM
SIRIUZ 3.0
- Base firmware P20 lite (security patch for September).
- Custom kernel MorfuZ now works wifi and bluetooth.
- Huawei ID integrated and running.
- New bootanimation.
- New bootlogo.
- Percentage activated from start, for other models.
- Activated the font change in themes.
- New topics.
- 7 themes to change the font customization.
- Yorreciones de camara.
- Youtube advance updated.
- Adaway ad blocker.
- VolTe Activated.
- Magisk 17.1
SIRIUZ 2.6
- P20 lite base firmware (August security patch).
- MorfuzKernel 2.1 selinux Permissive.
- Turbo GPU.
- Added support init.d.
- Added busybox.
- Huawei ID back.
- Boot profile for the Darknnes-Blu_Active kernel within init.d improves performance.
- Change of the MTweaks auditor kernel application.
- Added Lent AR fun camera function.
- Magisk 16.7.
- Increase bitrate of photos and video, improve quality.
- Application of return mail.
- Youtube Mod Updated.
- New Gboard keyboard.
SIRIUZ 2.4
-Base firmware P20 lite(security patch jun).
-Activated Dual Speaker.
-Added DolbyAtmos in Music.
-New Boot logo.
-Added custom watermark for the P20 lite.
-Now without patches.
-Installation mode AROMA-INSTALLER.
-Music: stock or crack.
-Camera: stock, Mate10Pro or P20Pro.
-Root: Magisk or Supersu.
-Navbar, Use the fingerprint sensor as a navigation bar.
-Solid explorer, Kernel Auditor, Quick Reboot.
-MxPlayer.
-Sony Music.
-Eliminated the data space.
-Deodexed (improves optimization).
-Improvements in the quality of photos, video and sound..
-It eliminated unnecessary google applications.
-Added Call Recorder.
-Added Youtube Mod (function in the background).
-Activated multi-user X5.
-Keyboard change, google.
-Reduction of size of icons.
-Activated glove mode.
-Mtu 1500.
-Explored files improved.
-Added main screen design 5x5,5x6,6x5.
-Added more applications of social networks of Twin cloning.
. * facebook, faceboot lite
. * messenger, messenger lite
. * whatsapp, whatsapp mod
. * instagram
. * snapchat
. * telegram
. * twitter
. * mega
. * creativefrends
. * microsoft office
r2
when i go to security options settings app crashes
cant setup fingerprint id
oh now it works after playing with the instalation settings
I got an error during installation and start bootlooping, latter with more time I'll try again.
Thanks to share your work with us.
Error finishing the installation:
set_perm: some changes failed
Other problems:
-Does not detect micro sd
-You can not configure a screen lock method (settings close when you try to enter that section)
-Developer options can not be activated (the settings are closed when you press compile)
Those problems are what happened to me, I followed the installation instructions exactly as it says in the post
same problem with me
brandox0 said:
Error finishing the installation:
set_perm: some changes failed
Other problems:
-Does not detect micro sd
-You can not configure a screen lock method (settings close when you try to enter that section)
-Developer options can not be activated (the settings are closed when you press compile)
Those problems are what happened to me, I followed the installation instructions exactly as it says in the post
Click to expand...
Click to collapse
The rom is working or not?
thanks for the rom!
followed the install instructions except i didn't install the TWRP321_OREO_P20LITE.rar because i previously installed it following these instructions.
chose to install the custom kernel and SuperSU. not sure right now what else. i will write it down when i try the next build.
i encountered the following issues:
-error finishing the installation: set_perm: some changes failed during flashing (could this be because i didn't install your modded TWRP?)
-unable to set the lockscreen options
-unable to set up fingerprintid
-settings crashes when attempting to enable dev options
-sd card isn't detected within the fw
once i saw the sdcard isn't detected, i tried to recover from my latest backup but TWRP wasn't able because /system was only mounted as read-only (could this be as well because i didn't install your modded TWRP?).
ended up having to reflash stock from erecovery, rerooting and reinstalling TWRP in order to restore from my last backup (maybe i did something wrong?).
after reading the features list, i personally would use it as my main rom. i'd love to see it with viper4android included and with an all dark theme though but that's just me.
thanks for your work! looking forward to more!
luigi997 said:
The rom is working or not?
Click to expand...
Click to collapse
Well, if you eliminate the fact that the fingerprint reader or any other screen lock method does not work, you can not use the micro sd and the developer options are not available. So yes, the rom works.
You can try to urge it, maybe you're lucky and do not have mistakes.
brandox0 said:
Well, if you eliminate the fact that the fingerprint reader or any other screen lock method does not work, you can not use the micro sd and the developer options are not available. So yes, the rom works.
You can try to urge it, maybe you're lucky and do not have mistakes.
Click to expand...
Click to collapse
If i try to uninstall an app, the system reboot.
I've installed the modded kernel
Anyone with no issues? Can be used as a daily driver?
Please report back testers ^_^
[email protected] said:
Anyone with no issues? Can be used as a daily driver?
Please report back testers ^_^
Click to expand...
Click to collapse
Nope, so far I haven't seen anyone reporting positively. No fingerprintid and no security features makes the rom pretty much unusable as far as I've tested and seen on the thread. I'm awaiting to see how this develops..
Success
This rom is working prefectly.. i have keep on trying to re install the rom.I always follow the exact instruction, and i have found out. You will have a set_perm: some changes failed. IF you mark check the navbar, and status bar while in aroma installer.. I have able to use everything. Ill try to make a screenshot of it.
riorabel12 said:
This rom is working prefectly.. i have keep on trying to re install the rom.I always follow the exact instruction, and i have found out. You will have a set_perm: some changes failed. IF you mark check the navbar, and status bar while in aroma installer.. I have able to use everything. Ill try to make a screenshot of it.
Click to expand...
Click to collapse
Awesome! I'll try again!
Did you flash the recovery included in the post?
What do you mean with "If you mark check the navbar, and status bar while in aroma installer"?
Thanks for the feedback!
madalone said:
Awesome! I'll try again!
Did you flash the recovery included in the post?
What do you mean with "If you mark check the navbar, and status bar while in aroma installer"?
Thanks for the feedback!
Click to expand...
Click to collapse
YES. I HAVE FLASH THE RECOVERY. AND WHEN YOU FIRST DO THAT... AND YOU SHOULD PUT THE ROM INTO YOUR SD CARD..
YES, IF YOU MARK CHECK THE NAVBAR ANF STATSBAR. WHILE CHOOSING YOUR DESIRED APPS. YOU WILL SEE THAT IN THE VERY LAST PAGE OF THE AROMA INSTALLER. WHERE YOU HAVE THE OPTIONS. NAVBAR STATSBAR, SOLID EXPLORER, KERNEL AUDIATOR, AND the QUICK REBOOT. SO JUST MARK CHECK THE SOLID EXPLORER,KERNELAUDITOR,AND QUICK REBOOT..
SO TRY IT NOW. AND GIVE ME SOME FEEDBACK IF IT WORKS IN YOU. ALSO KINDLY TRY TO DO A SCREENSHOT. I DONT HAVE OTHER PHONE TO TAKE A SHOT ON IT. KUDOS THANKS
ok so i flashed the provided recovery and the rom following the instructions with the following options in aroma installer:
Kernel: Morfu2kernel
Root: SuperSU
Camera: P20 Pro
Music: Stock
Kernel Auditor
Quick Reboot
the installation went through except bootimage patcher failed at decompressing ramdisk (failure, aborting).
edit1: after a cache wipe, i rebooted the phone. the phone boots but no root.
tried to flash SuperSU through TWRP but failed.
wiped data/cache/dalvik/system & reflashed rom with Stock kernel & Magisk no bootimage patcher errors. after a cache wipe, rebooted & phone has root :victory:
brandox0 said:
I also want to try again, but I'm still not sure.
So far, how is the rom working? Is there a fault signal mentioned above?
Click to expand...
Click to collapse
so far i'm still getting all my apps installed. i'll letcha know how i get on with it.
edit2: as i am stubborn, i reflashed the rom with the custom kernel and Magisk. root is on and the phone seems to run smoothly.
madalone said:
ok so i flashed the provided recovery and the rom following the instructions with the following options in aroma installer:
Kernel: Morfu2kernel
Root: SuperSU
Camera: P20 Pro
Music: Stock
Kernel Auditor
Quick Reboot
the installation went through except bootimage patcher failed at decompressing ramdisk (failure, aborting). is that the kernel failing to install?
after a cache wipe, i rebooted the phone. the phone boots as expected.
Click to expand...
Click to collapse
I also want to try again, but I'm still not sure.
So far, how is the rom working? Is there a fault signal mentioned above?
madalone said:
ok so i flashed the provided recovery and the rom following the instructions with the following options in aroma installer:
Kernel: Morfu2kernel
Root: SuperSU
Camera: P20 Pro
Music: Stock
Kernel Auditor
Quick Reboot
the installation went through except bootimage patcher failed at decompressing ramdisk (failure, aborting).
edit1: after a cache wipe, i rebooted the phone. the phone boots but no root.
tried to flash SuperSU through TWRP but failed.
wiped data/cache/dalvik/system & reflashed rom with Stock kernel & Magisk no bootimage patcher errors. after a cache wipe, rebooted & phone has root :victory:
so far i'm still getting all my apps installed. i'll letcha know how i get on with it.
Click to expand...
Click to collapse
I worked perfectly, the only problem is that mobile became very slow.
rapza4 said:
I worked perfectly, the only problem is that mobile became very slow.
Click to expand...
Click to collapse
i had that plus overheating but after what i did in edit2 it was gone and the phone runs smoothly.
on another note: is it possible to make this rom have init.d support somehow? it'd be cool for stuff like Liveboot..