Database Info

[RECOVERY] ClockworkMod TOUCH 5.5.0.4 v4.3 - (7/9/12)

This is gweedo767's touch recovery ported to the skyrocket/hercules. Because many people have been asking me what the difference between this one and the version that koush put out here is the difference:
This one is open source.
This one has swipe gestures (up,down,left,right)
This one has different UI settings
This one has soft keys on the bottom of the screen
This one has 2 different options of font
Here is a youtube video I made of how it works: ------> VIDEO
4 ways to use recovery:
volume rockers
soft keys on bottom of screen
capacitive buttons
swipe gestures (up/down = scroll && left = back && right = select)
HOW TO INSTALL:​
CWMR5504_INSTALL-4.3.zip (NEW ICS BACKGROUND): ---------> BLUE-FONT
CWMR5504_INSTALL-4.3.zip (NEW ICS BACKGROUND): ---------> ROBOTO-FONT
- Just flash in CWM
Click to expand...
Click to collapse
TERMINAL INSTALL:​
recovery.img: (NEW ICS BACKGROUND) ----------------> BLUE-FONT
recovery.img: (NEW ICS BACKGROUND) ----------------> ROBOTO-FONT
- download to sdcard
- open terminal emulator (or adb) type:
Code:
$ su
# dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22 bs=4096
Click to expand...
Click to collapse
Odin Install​
recovery.tar.md5 (NEW ICS BACKGROUND): ---------> BLUE-FONT
recovery.tar.md5 (NEW ICS BACKGROUND): ---------> ROBOTO-FONT
Click to expand...
Click to collapse
Test Drive:​
CWMRT5504_TEST-4.3.zip(NEW ICS BACKGROUND): -------------------> BLUE-FONT
CWMRT5504_TEST-4.3.zip(NEW ICS BACKGROUND): -------------------> ROBOTO-FONT
(This will not alter ANY files on your phone. It is just a test drive basically. You flash it through ClockworkMod that you have already installed and it runs over it showing you how it would be if you did install it. Once you reboot you will still have the same recovery that you had.)
Click to expand...
Click to collapse
v1:
Code:
- Initial release
v2:
Code:
- fixed "back button disabled/enabled" when scrolling past top to bottom
- 2 different font versions (roboto and normal)
-- roboto font is a little bigger
- complete fix of adb and usb mounting
v2.5:
Code:
- added a cool new ICS background! (thanks CyanmodICS for the idea)
- added green/red font versions
- cleaned up the code a bit
v3:
Code:
- in process of fixing hanging backup issue (need extensive list of apps people have installed when having issue)
- fixed ALOT of bugs
- added many more options for internal/external sdcard
- more....(i cant remember)
- i will add the other color options back in a few days
v3.5
Code:
- fixed recovery.fstab to mount internal sdcard as /sdcard to recognize .hidenandroidprogress file
- ascii art???
v4.0
Code:
- fixed the fix_permissions not working (thanks minotauri)
- fixed sd-ext and .android_secure errors in backup
v4.1
Code:
- re-arranged order of "install from internal/external sdcard" to put internal first
- added "Reboot Recovery" option to the bottom of the advanced menu
- a few code cleanups
v4.2
Code:
- fixed bug where background would reset to blank black after installing a zip/backing up/restoring
- added option to reboot into download mode in advanced>>reboot download mode
v4.3
Code:
- hopefully fixed the hanging backup bug once and for all
- merged all of CWM's latest code changes
Thanks to:
Code:
gweedo767
plastikman
utkanos
romracer

Thanks! I guess i'll be the first tester, to make sure i don't get bricked or anything

Badass!!! Guess I be tester number 2 haha
Sent from my Desire HD using xda premium

Sweet. Flashing now
Sent from my SAMSUNG-SGH-I727 using xda premium

so i created a recovery.tar.md5 to flash through odin. I flashed it and it automatically booted back into android. Once i rebooted into recovery everything worked in there but when i tried to reboot it would only reboot back into recovery. i did a battery pull and waited a few minutes but it only booted into clockworkmod. I had to flash the original clockworkmod 5.5.0.2 i had before to be able to boot back into android. anyone have any ideas on why it gets stuck in a clockworkmod boot loop?
this is only for the recovery.tar.md5...not for the cwmrt5504.zip. just wanted to clarify that. the .zip file is completely safe and will not alter any files on your device when you flash it.

How's the cwm working
Sent from my SAMSUNG-SGH-I727 using xda premium

the zip file seems to work fine. restored a red sonja backup, then flashed another to try it out more. all went well.

so to everyone who has tried it out:
how do you feel about the sensitivity on the swipe gestures? up/down sensitivity? left/right sensitivity? does the sensitivity need to be lowered or raised or stay the same?
thanks

so will this be an actual new recovery or an overlay of type for our current cwm
Sent from my SAMSUNG-SGH-I727 using xda premium

im going to create a recovery.tar.md5 that is flashable via Odin and will be a whole new recovery. but the one i have now gets stuck in a boot loop that only boots into recovery.

Problem with Scrolling...
For me obviously noticed the colours as well noticed that when I pushed Volume increase menu scrolled down and when I pushed Volume Decrease menu scrolled up. Anyone else get that issue... overall what is the difference between this and the other clockworkmod recovery... basically what is the benefit to flashing this over flashing the one that comes with ROM Manager....
Weird when I restarted my phone and went back into recovery it went back to CWM 5.0.2.7 is that what it's supposed to do?

i hadnt checked the volume rocker mappings yet. ill fix that. i just havent used anything but the swipe gestures.
the difference between this and the original one is that you do not need to touch any buttons. you swipe your finger up and down to scroll and swipe left to go back and swipe right to select. and there are the soft buttons on the bottom of the screen. basically there are 4 ways to move around and select and go back.
1.) volume rockers
2.) swipe gestures
3.) soft keys
4.) capacitive buttons
and i explained in the OP that it was a fakeflash. which means that it does not install it on your phone. thats the reason why you booted back into your original clockworkmod. i have an installable version but it is not ready yet. i do not want to release it yet because it could mess up your device.

My Bad... I missed the fake flash... that's why you should read the entire comment I guess LOL... Anyways awesome thanks for the quick reply.

no problem. ive done that before. usually its when i get really excited about a new rom and i download it without reading the whole post and then something doesnt work with it and i get frustrated and realize they have a patch in the OP or something. haha
anyways, once i get the boot loop problem fixed i will make a recovery.tar.md5 that you can just flash in Odin and itll be an entirely new recovery installed

i updated the file on my box.com account with the correct volume rocker key mappings.

So this is the same CWM just a touch screen version... aren't we using a version of CWM that is made for the regular galaxy s2? Isn't that why there are tons of problems with FC's because this CWM does not delete everything it is suppose to and we end up having to install the stock recovery to do a factory reset?

well this is the latest clockworkmod 5.5.0.4. the only other CWM i can find is 5.0.2.7. so its updated. not sure what the changelog is on that though. And this isnt a version that was made for the gs2. it was originally made for the galaxy nexus. Im pretty sure its the same source code as the code from the cm9 repo. Im not 100% sure on that though. ill have to ask gweedo.

and ive been using this recovery for about a week and have backed up/restored/flashed new roms/reset to factory/erase cache/dalvik all a few times and havent had any issues with it not deleting everything.

I have to ask, have you figured out what's up with the colors? They could hurt your eyes if you looked at it too long. xD

Also note, which is something that's also been an issue with the current CWM, Fix Permissions doesn't do a thing. Press it and it instantly tells you it's done. Should at least take a minute to get everything done. Just wanted to mention that this problem still exists. Definitely not at all any kind of dealbreakef, but I just don't get why any ports have worked for our devices.
Sent from my SAMSUNG-SGH-I727 using xda premium

[ROM][MOD] Lenovo A820

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.

ROM SlimStock KK G6-U10: based on B360, pre-rooted, bloatware removed!

ROM SlimStock KK G6-U10
based on: G6-U10V100R001C432B360
last updated: 28-12-2015
features:
- Pre rooted
- bloatware removed
- some useful apps installed (see screenshots)
___________________________________________________________
how to install:
- have a G6-U10 (or any other phone with the same hardware)
- have an unlocked bootloader with custom recovery
- make backup in your recovery, place it on your PC
- download my SlimStock ROM, place it on your SD
- format everything except SD card & recovery
- select "install zip from SD" in your recovery, and flash SlimStock
- wait till it's done, ignore "unable to mount /data", reboot
- wait a while, it might reboot 2 times, and you will boot up!
- (download my GetStarted app package)
Any bugs? please let me know in the comments!
SlimStock_G6U10B360v1 ROM:
MediaFire: https://www.mediafire.com/?wty10969ilv1zjp
MEGA link: https://mega.nz/#!gNdzTSzD
decryption key: !CuSrFuS5YkKObEPbdInqXfIngl-vo8P1h-PTvwREgKI
when your phone goes in bootloop :
press vol+ and hold it, you will goto recovery,
restore your own backup, and describe your problem in the comments and we will try to help you
___________________________________________________________
G6U10_GetStarted.zip:
MEGA link: https://mega.nz/#!ZVsnDQwK!o84Xzvfpn-IbysnwmvEBqHorZtBDoHnKhckKKLDPoY4
Includes:
- ES file explorer Pro
- Greenify Pro
- NovaLauncher
- TeslaUnread (NovaLauncher add-on)
- Moonshine (NovaLauncher themepack)
- blackmarket
- reboot manager
- quickpic
- SD Maid Pro
- TWRPU10
- G6U10_orig_recovery
- kinguser.zip

Screenshots
...

Known bugs/issues
known bugs/issues & changelog
known bugs/issues:
- Nova Launcher quick search box isn't working [fix not found yet]
__________________________________________________
changelog:
v1.0.2
- added custom bootanimation http://gph.is/1Z4Keoz
- added recovery progress bar
- removed reboot line from script (phone won't reboot automatically after flashing SlimStock)
- removed recovery from SlimStock (you will keep the recovery you had)
- added default custom theme
- added custom easter egg in theme
- optimized build.prop
- updated buildnumber
- added EsFileExplorer PRO as system app
- added android 4.3 DNLA app

Thanks for this rom, I've flashed it on the phone of a friend.
I first unlocked the bootloader and then rooted the phone, deleted some bloatware but went a little to far.. nothing worked like it should.
Could not hard reset the phone after that.. SO flashed TWRP and flashed your rom! You saved my life!!!!
Thanks!

useful
thanks

It's saying that the installation was aborted...pls help

Mr.Awesom€ said:
It's saying that the installation was aborted...pls help
Click to expand...
Click to collapse
try a factory reset first.
and make sure you follow the steps. (try a few times),
and give some more info, so I can try to define the problem.

@washichi a big thanks for this ROM, maybe the best for G6-U10.
I have flashed it just now and it seems that everything wroked fine, or quite everything. The only failure is about root permission, that should be included; in fact Kinuser tell me, that "SU upgrade failde. Missing root permission".
What can I do now to obtain root permission? Which guide should I follow?
Thanks
EDIT: Downloading KingRoot directly from browser and using it, seems that now I am a root user.
I hope that everything will continue to go in the right side.
Thanks again for your ROM
EDIT 2: The ROM has a small visual bug in block screen (this is insignificant); more important is that data usage isn't present ?
At the end in the notification scroll bar there are a 'super battery saver" icon and a "do not disturb" icon, but they are useless and do nothing.

I'm not able to install custom recovery, so I'm not able to test this ROM.
When I install CMW (fastboot) I get only black screen, when I try to go to recovery. If I use "Rom Manager", it offers only recovery 3.0.0.5 and when reboot, I'm stuck with stock recovery.
Bootloader is unlocked.
Code:
> fastboot oem get-bootinfo
(bootloader) *******************************************
(bootloader) Bootloader Lock State: UNLOCKED
(bootloader) System State: Bootloader in UNLOCKED state
(bootloader) Bootloader Version: 001.001.000
(bootloader) *******************************************
OKAY [ 0.000s]
finished. total time: 0.000s
EDIT: I managed to flash TWRP 2.7.1.0 and it works. And now I was able to flash this ROM. If I find any bug, will report. Thank you for ROM!
EDIT2: I miss notifications on lock screen. Any idea?

Problems I have:
- people who I speak with, don't hear me well (every "5th" word just cut out)
- when typing (gmail, messenger, sms) everything just crashes and closes
Any idea?

Hey guys,
So I accidentaly flashed this rom on G6 L11 (the 4G version of huawei G6) and now it's bricked. I cannot turn on, boot in recovery, boot in fastboot nor the usb is recognising it. Any ideas?
Thank you.

Call quality
Hey,
Very nice rom, thank you!
Unfortunately I have the same problems with voice quality like veron161 The voice quality during the call is poor and a lot of words are lost. Any ideas?
Thanks!

I am a student
I installed rom huawei g6-u10 b146
now, I am not installing more rom (b360,b330,b120,b135.....).Can you help me.please?

Thanks man! But...
Everything's fine with the rom, worked for me, Venezuela Huawei g6-U251 with TWRP but, mobile network didn't working
Using MOVISTAR, only that problem had any solution?

[ROM] Galaxy Note 5 PC3 Marshmallow Deodexed Stock Rom

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?

[GUIDE/TUTORIAL/HOWTO] Samsung Galaxy S7 Edge Stock to Android 13

[GUIDE/TUTORIAL/HOWTO] Samsung Galaxy S7 Edge Stock to Android 13
[GUIDE/TUTORIAL/HOWTO] Samsung Galaxy S7 Edge (hero2lte Exynos SOC) Stock to Android 13 / LineageOS 20
Supported models
International & Canada:
- SM-G935F
- SM-G935FD
- SM-G935X
- SM-G935W8
Korea:
- SM-G935S
- SM-G935K
- SM-G935L
This detailed step-by-step guide helps you transform your Samsung Galaxy S7 Edge hero2lte to a powerful one with Android 13.
Make sure your phone is hero2lte/Exynos SOC before going further: in Android, go to Settings > About phone > Check Model number is listed above.
If not, quit this tutorial.
### READ THOSE WARNING COMMENTS
CHANGELOG
v5. Back to TWRP 3.6 (3.7 oversize)
v4. Android 13, TWRP 3.7
v3. BitGApps v1, Magisk 25.2
v2. Update TWRP, add adb to change screen definition, update download link
v1. Initial release for Android 12
1) DOWNLOAD
- djibe Galaxy S7 hero2lte pack: https://bit.ly/djibe-galaxys7edge-pack
(contains Samsung tweaked Odin 3.13.1 + Samsung USB drivers + TWRP 3.6.2_9-0 official recovery + Magisk Root + adb.exe). Unzip files.
+ ROM Unofficial LineageOS 20: https://forum.xda-developers.com/t/...ofing-ota-updates-for-s7-edge-exynos.4484511/
Download latest build: https://ivanmeler.github.io/devices/hero2lte.html
+ BiTGApps Package ARM64 13: https://github.com/BiTGApps/BiTGApps-Release/releases
OR NikGApps T Basic: https://sourceforge.net/projects/nikgapps/files/Canary-Releases/NikGapps-T/
OR MindTheGApps 13 ARM64: http://downloads.codefi.re/jdcteam/javelinanddart/gapps
+ Charge phone to 100%
2) BACKUP DATA
Install Samsung USB drivers (you unzipped earlier).
Then plug phone to PC in File transfer mode.
Collect all .jpg or .mp4
Use Google built-in cloud to backup apps like SMS Backup & Restore to backup texts, contacts, etc.
Backup your WhatsApp messages in Google Drive.
Everything else: podcasts, Authenticators, TODOs etc...
Then copy the backup on your PC.
Make sure you have latest official updates for your phone:
Connect to Wifi and go to Settings > About device > Software update > Update now
### BACKUP NOW, you will lose everything.
3) FLASH TWRP 3.7 RECOVERY
Go to Settings > About phone> Software information.
Tap 7 times on Build number item to unlock Developer options.
Go to Settings > Developer options, switch OEM unlock ON and Confirm.
Shutdown phone.
Boot in Download Mode: hold Home + Power + Volume- until you see blue-green Warning screen and release buttons.
Confirm access to Download mode by pressing Volume+.
Phone now displays "Downloading..., Do not turn off target".
Connect phone in USB, wait for drivers installation.
Then launch Odin.exe (included in my archive) and wait for Odin indicator ID:COM to become blue.
In options: Verify re-partition and Auto Reboot are NOT ticked while F. Reset Time is ticked.
In AP > select twrp-3.6.2_9-0-hero2lte.img.tar
### Same recovery for Korean models (G930S/K/L variants)
### Warranty will be Void after next click ###
Click Start.
Wait until flash Success message appears.
Unplug phone.
Restart phone to recovery :
- hold Power + Home + Volume- until phone screen becomes black...
- and immediatly switch from Volume- to Volume+ (still holding Power + Home) and hold until Samsung's logo is displayed to land in TWRP recovery.
### If Android launches, hold 3 buttons until phone restarts and Samsung logo appears.
4) BACKUP IMEI PARTITION AND SYSTEM (Nandroid backup)
(Boot in Recovery Mode: Hold Home + Power + Volume+ until you see Samsung's logo then release and wait a few seconds for TWRP recovery to boot)
Recovery asks for Keep System Read Only ? > Swipe to Allow Modifications.
Go to Wipe > Format Data.
Type: yes and confirm with bottom right check icon.
Encryption is removed. You can now access partitions.
### If you miss this step you won't have access to any partition.
Back to home menu > Backup.
You can now select the partitions you want to save.
Select at least EFS partition to backup your IMEI. If a flash fails and partition is damaged you will still be able to restore this partition and use the phone.
If IMEI is lost during a flash, phone won't be able to reach cellphone networks.
I prefer to backup Boot, System, Baseband and EFS partitions. In case of problem, you will have your phone in its original state.
Swipe to Backup and wait during process.
Go to Home screen and continue with next chapter.
Save backup: still under TWRP recovery, connect phone to PC.
Go to Mount menu and check Data partition is checked and MTB button is on "Disable MTP" state.
From Windows explorer, access phones memory and copy-paste the TWRP folder (located in root folder, beside DCIM and Music folders) somewhere safe on your computer.
5) FORMAT PARTITIONS
### Make sure you copied TWRP backup from internal memory to somewhere safe.
Go to Wipe > Advanced wipe,
select Dalvik, Cache, System, Data, Internal Storage (if you really made a backup at step 2), then Swipe to Wipe.
Back to TWRP home screen, go to Reboot > Recovery and swipe to reboot.
On next launch, check the checkbox to remember choice and swipe to allow modifications.
6) FLASH ROM, (MAGISK ROOT) AND GAPPS
Back to TWRP main menu, go to Mount menu again to connect phone to PC again.
Connect phone to PC and use Windows explorer to copy files on phone's internal memory.
Copy TWRP folder from your phone to somewhere safe on PC.
This backup can restore your phone to its original Samsung state.
Copy files of ROM + BitGApps + Magisk on phone.
Go back to TWRP Home menu. Then tap on Install > choose lineage*.zip,
Optional for root: Add More zips > Magisk*.zip
then Swipe to confirm Flash.
Wait for operation to end.
Go to Reboot > Recovery and swipe to reboot.
After restart, go to Install, select bitgapps*.zip and swipe to flash.
Then tap Wipe cache/dalvik, swipe to confirm,
then Reboot System and on Install TWRP App? menu, tap on button Do Not Install
Wait for the phone to boot during 5 minutes.
7) ROOT ACCESS
Configure Android as you like.
Don't try to set fingerprints at first setup. It will crash.
No need for extra work to be root.
Magisk launches with Android.
Superuser permissions can be managed from Magisk Manager app.
8) TWEAKS
- Calibrate battery: https://www.ifixit.com/Wiki/Battery_Calibration
- Set dark Mode to improve battery by 30%
Settings > Display > Dark theme.
- For better battery, remove Always on display
Settings > Display > Lock screen > Ambient display
- Activate Developer options
Go to Settings > About.
At bottom, tap 7 times on Build number. You activated Developer options.
Go to Settings > System > Advanced > Developer options.
- Change screen definition for low GPU/CPU usage: from 1440x2560 to 1080x1920
You need developer options to enable USB debugging.
Open a terminal where adb.exe from my pack is located.
Plug phone and Authorize USB debugging.
Then type:
Code:
adb shell wm size 1080x1920 && adb shell wm density 400
// Defaults 1440x2560 and 504
- Screen sensitivity is too low ?
Try to recalibrate screen sensitivity with https://play.google.com/store/apps/details?id=touchcalibration.favoritappindia&hl=en&gl=US
Enjoy,
djibe
Thanks: @Ivan_Meler, LineageOS team, TWRP team, TopJohnWu
---------------------------------------
Coming from another ROM
- Backup
- Recovery: Wipe Cache, Dalvik cache, System and Format Data > yes
- Reboot recovery
- Flash rom
- Reboot recovery
- Flash BitGApps
Enjoy
Force Samsung Galaxy S7 restart
Hold Power + Volume down for 10-20 seconds

Thanks for the detailed instructions.
Please fix two minor typos: In the Odin instructions, the files should be hero2lte* not herolte*.
Re Magisk: 24.0, I suppose, should be used / upgraded to. (I've run into issues with 24.2 on another platform.)

steve8x8 said:
Thanks for the detailed instructions.
Please fix two minor typos: In the Odin instructions, the files should be hero2lte* not herolte*.
Re Magisk: 24.0, I suppose, should be used / upgraded to. (I've run into issues with 24.2 on another platform.)
Click to expand...
Click to collapse
Hi, you are correct and I'll fix glitch.
For Magisk, as you report bugs, I'll wait to move to 24.x. You can create an Issue here: https://github.com/topjohnwu/Magisk/issues
Thanks for sharing

I have a problemi instaled twrp format data and and instal rom after configuration rom when i rebooting to twrp data is encrypted. why ?

zulwik said:
I have a problemi instaled twrp format data and and instal rom after configuration rom when i rebooting to twrp data is encrypted. why ?
Click to expand...
Click to collapse
Hi, did you Format Data then Advanced Wipe > Format Cache, System ?
Then
Reboot to Recovery
Flash ROM
Reboot to recovery
Flash BitGapps
Reboot

I solved problem.
I installed older version TWRP with Odin and new version

hey @djibe89 & other XDA folks, thanks for these steps.
I have a SMG935W8 and currently borked on the BiTGApps step. All proceeded smoothly until there and now I'm seeing an error on TWRP and I'm not really sure how to resolve it.
It's complaining that the install config is not found and that it's an unsupported Android SDK version, which doesn't seem quite right.
Any tips would be highly appreciated

Judging from my deep dive, the current LineageOS 19.1 builds are SDK 32, and the BiTGapps builds only support up to 31... Definitely looking for tips, still.
Going to try this post's GApps

Hi, for now, stick to latest LOS 19 build: https://github.com/ivanmeler/ota_provider/releases/tag/herolte_lineage-19.0_1646935359, not 19.1

Or could you try NikGapps and tell us?

Thanks @djibe89 ! I went with NikGapps and that was a win.
It might be good to edit the top post to say 19.0 or have the NikGapps linked in it, for future readers.
Phone's working great. I appreciate it!

Bujiraso said:
Thanks @djibe89 ! I went with NikGapps and that was a win.
It might be good to edit the top post to say 19.0 or have the NikGapps linked in it, for future readers.
Phone's working great. I appreciate it!
Click to expand...
Click to collapse
Hi, I'll update it.
I hoped a newer BitGapps update would be released by now.
Enjoy, this phone is awesome

Hey again!
Been daily driving this for a bit and here's a laundry list of the issues I see, in no order at all.
I'm not sure if they're Lineage issues or artifacts of being an "unsupported" Lineage build.
1. The screen just stays on despite the power save settings (I've tried 15s, 30s, you name it) if I'm on the home screen. Trebuchet, is it?
It's like it has some keep alive function a la YouTube. It's not 100% but it seems far more than 50% of the time that I have to manually lock the device. Anyone know if I've just configured something wrong or if this is how the launcher is supposed to work?
2. Phone services will not stop demanding my location, no matter what I configure. It's every few minutes and it's creeping me out a ton. Why is it so nosey?
3. The call audio quality is still barely usable. While I *can* have intelligible business conversations when required, they suffer the quality noticeably and are terribly robotic and tinny. For personal calls, I tried to play it off once but immediately was laughed out of the call: they asked before even a "how are you" could pass if we could switch to VoIP since it was so comically bad. After some kind tips from Ivan I tried mucking with the mixer levels to no avail. They did seem a bit "low" compared to the 18.1/19.0 values, so I pumped them in a couple places (NB volume from 22 to 32, call default volume on 917 from 98 to 164 -- I have no clue what any of these mean). It might be louder now? It's not worth an A/B test to confirm what should be the expectation, but my point is that it didn't fix the robotic, tinny quality.
4. Banking app complains of the device being rooted, but it isn't. "Great." I hear the latest Zygisk might fix? I haven't tried yet.
Now, I'm still excited to be on 12L! I'm trying to buff my ability to dev on this ROM and fix up some of these issues, as I really don't think this phone needs to be replaced yet, but being stuck on stock Oreo isn't working either, so I say let's hack this thing till it's stable as stock!

Hi @Bujiraso , thanks for sharing.
Didn't use it on a daily basis
Have you tried another launcher ?
I think bank apps detect custom ROM, nothing can be done. Hope I'm wrong. Some genius of signature spoofing can pass this I believe. But I'm not.

djibe89 said:
- To tweak overclocking and more, use SmartPack-Kernel Manager
SmartPack-Kernel Manager - Apps on Google Play
The ultimate tool to manage your kernel
play.google.com
Enjoy,
djibe
Click to expand...
Click to collapse
We're sorry, the requested URL was not found on this server. New Link please.

SERGE4NT said:
We're sorry, the requested URL was not found on this server. New Link please.
Click to expand...
Click to collapse
Hi, you can try https://play.google.com/store/apps/details?id=com.performancetweaker.app or https://f-droid.org/repo/com.smartpack.kernelmanager_174.apk

hi, is it possible for the model number SM-G9350

Klein44 said:
hi, is it possible for the model number SM-G9350
Click to expand...
Click to collapse
Hi, sadly no.
9350 and 9300 have Snapdragon SOCs, not Exynos.
Only Android 8 ROMs: https://forum.xda-developers.com/f/samsung-galaxy-s7-edge-snapdragon-roms-kernels.5975/

Oh, ok. And is there any good custom rom for the SM-G9350 model?

Klein44 said:
Oh, ok. And is there any good custom rom for the SM-G9350 model?
Click to expand...
Click to collapse
Like you see here: https://forum.xda-developers.com/f/samsung-galaxy-s7-edge-snapdragon-roms-kernels.5975/
No.
This happens with Qualcomm proprietary SOCs