[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
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?
Welcome to POCO F1 Ultimate Collection!
(beryllium)
OFFICIAL STOCK MIUI ROM
You can check my Guides for installation.
Recovery ROM V12.0.3.0.QEJMIXM
Fastboot ROM V12.0.3.0.QEJMIXM
POCO F1 Global Stable ROM Library / POCO F1 MIUI Official ROMs Archive
FIRMWARE & VENDOR
POCO F1 Firmware
POCO F1 Vendor
POCO F1 Latest Firmware & Vendor
CUSTOM ROMS
You can check my Guides for installation.
Note: I've created an award system for people which are not familiar with custom ROMs, to help them choose a ROM which is stable for daily use, gets frequently updates with security patches every month and has active development, so they don't mess with ROMs which appearing and then dissapearing (and we have a lot of them).
ROMs under awarded ROMs are not order by rating and just have random order.
If you are knowledge, you can ignore my awards and choose any ROM you like.
My standards for giving award to a ROM are:
Open Source
Stable enough for daily use
SELinux Enforcing
Safetynet pass by default
Encrypted by default
Debloated
Active & Stable Development
Translations
Popularity
OTA
No Pixel Thermals
What is System_EXT? Check out here.
Based on MIUI ROM
MIUI MindEdition
MIUI 13 MindEdition A12 Unofficial
PocoOS
MIUI 14
BeosXPredator
Xiaomi.eu V12.0.3.0.QEJMIXM
Elite ROM
MIUI 12 Global Stable Modiefied
Linux Distribution
Ubuntu Touch
Droidian Unofficial
Android 13
crDroid [Installation Guide] [crDroid Recovery]
AwakenOS [Installation Guide] [TWRP by REIGNZ Recovery]
Official LineageOS / LineageOS microG [Installation Guide] [LineageOS Recovery]
PixelOS [Same as AwakenOS Installation Guide] [TWRP by REIGNZ Recovery]
ArrowOS [Same as AwakenOS Installation Guide] [TWRP by REIGNZ Recovery]
Paranoid Android / Unofficial PA [Same as AwakenOS Installation Guide] [TWRP by REIGNZ Recovery]
ReloadedOS [Same as AwakenOS Installation Guide] [TWRP by REIGNZ Recovery]
BaikalOS
SOSP-OS Project
Pixel Experience Unofficial
StatiXOS
Project Elixir
ArrowOS-MiPA Edition
EvolutionX
Project 404
DerpFest
LessAOSP
DivestOS
PixelExtended
CalyxOS
LibreMobileOS
CorvusOS
Project Blaze
BananaDroid
PixelPlusUI
BlissROM
Nusantara
riceDroid
Xtended
ColtOS
VoidUI
Black Iron
AncientOS
StagOS
SparkOS
AlphaDroid
SuperiorOS
ProtonPlus
CygnusOS
VoltageOS
CherishOS
xdroidOSS
EternityOS
Android 12/12L
Android 12L/12.1
crDroid [Installation Guide] [crDroid Recovery]
AwakenOS [Installation Guide] [TWRP by REIGNZ Recovery]
Official LineageOS / LineageOS microG [Same as crDroid Installation Guide but use LineageOS ROM / Recovery] [LineageOS Recovery]
Pixel Experience [Installation Guide] [PE Recovery]
ProtonAOSP
Paranoid Android
PixelOS
LibreMobileOS
CalyxOS
riceDroid
FluidOS
Project404
ForkLineageOS
Project Elixir
ArrowOS Unofficial
CorvusOS
EvolutionX
/e/OS
DerpFest
SyberiaOS
BiancaProject
VoidUI
LineageOS++ by side
CherishOS
SparkOS
StagOS
CygnusOS
AtomXCLO
FlamingoOS
KomodoOS
CipherOS
Nusantara Project
AncientOS
PixyOS
xDroid
LessAOSP
LeOS
VoltageOS
Kaleidoscope
ElytraOS
KryptonAOSP
Project Zephyrus
Project Arcana
ProjectBlaze
FusionOS
POSP
PixelBlaster
Android 12
MSM Xtended
PixelPlusUI
Project Radiant
BlissROM
CAFEX
SuperiorOS
Fluid
AOSPK
OctaviOS Unofficial
AospExtended Unofficial
Android 11
LineageOS / LineageOS microG
Pixel Experience
crDroid Android
ArrowOS
HavocOS
BaikalOS
EvolutionX
DotOS
AICP
Fork LineageOS
CalyxOS
/e/OS
AospExtended
PixelPlusUI
Paranoid Android
MSM Xtended
WaveOS
RohieOS
Project 404
BlissROM
CAFEX
xdroidCAF
DerpFest
BananaDroid
RevengeOS
AOSiP
ShapeShiftOS
Fluid
AwakenOS
POSP
PixelROM
SpiceOS
Styx Project
Project Sakura
StagOS
ArcaneOS
Syberia
TenX-OS
StatixOS
ColtOS
CherishOS
CesiumOS
Bootleggers
AOSPK
KangOS
ReloadedOS
CygnusOS
CesiumOS
Candy 11
AncientOS
OctaviOS
Nusantara Project
ConquerOS
HornbillOS
HyconOS
Android 10
Pixel Experience
LineageOS
crDroid
ReloadedOS
EvolutionX
Paranoid Android
CorvusOS
HavocOS / HavocOS Fan Build
ArrowOS
KeepQassa
CarbonROM
AOSiP
PixelROM
PixelDust
POSP
Ressurection Remix
MSM Xtended
AICP
OmniROM
CAFEX
DeepFest
NitrogenOS
Komodo OS
PixysOS
BlissROM
ColtOS
SuperiorOS
HornbillOS
ZenX OS
StagOS
NusantaraProject / Unofficial NusantaraProject
Project Sakura
CUSTOM KERNELS
What is System_EXT? Check out here.
Active Development
SilverCore Kernel
No Gravity Kernel [NGK Profiles -> Infos about Profiles]
Kawaii Kernel
Ingenium Kernel
Rockstar Kernel
EOL (Archived)
BAALAM Kernel
Gear Kernel
NexusCAF Kernel
Optimus Drunk Kernel
Franco Kernel
arter97 Kernel
Twisted Kernel
Illusion Kernel
Sphinx Kernel
Stealth Kernel
MiPa Kernel
MiPa Kernel
Canting Kernel
Delta Kernel
Seshstation Kernel
XDKernel
Simple Kernel
Parallax Kernel
Malakas Kernel
CUSTOM RECOVERIES
You can check my Guides for installation.
What is System_EXT? Check out here.
Unofficial TWRP Recovery by REIGNZ (Normal version= system_ext / NSE version=Non system_ext) [Telegram Support] [Current Bugs/Issues]
Official TWRP Recovery
LineageOS Recovery
crDroid Recovery
Pixel Experience Recovery
Dynamic Retrofit Recovery
OrangeFox Recovery
PitchBlack Recovery
Sky Hawk Recovery Project
GAPPS & microG
GApps
Note: be sure you have selected Platform: ARM64 and the proper Android version of the ROM you are going to flash. If the ROM you want to flash include GApps, no need to download and flash any GApps at all.
Most of the GApps have also a config. file which can be used to to configure your installation the way you like. You can skip any Package that you don't want to be part of your installation. For more infos about that, read the instructions of the GApps you chose or search in Google.
Retrial-NikGApps
NikGApps [Create your own NikGApps build -> Video Guide] [Guide for Packages Information/Description]
BiTGApps
MindTheGapps
FlameGApps [FlameGApps Config] [FlameGApps A13 Basic]
Open GApps / Open GApps Unofficial A12L
LiteGapps
microG
If you don't want to use Google Play Services and general move away from Google, microG and its variants is an open source alternative which replace these services.
NanoDroid
MinMicroG
BiTGApps microG
microG Revived
microG
MAGISK ROOT
You can check my Guides for installation.
Magisk (APK)
Magisk.zip (Flashable Zip)
Uninstall.zip (Flashable Zip)
Magisk Canary (APK)
Magisk Delta
FoxMagiskModuleManager (This app replace the official magisk module repository since no longer available)
Momo (You can use this app too check if any modifications related Magisk are detected or not)
Universal SafetyNet Fix by kdrag0n [Video Guide]
Shamiko (Hide Root from apps) [Guide]
Note: If your apps detect root, follow this Guide (or this) to pass SafetyNet and have certified Play Store. [YouTube Video Guide]
DISABE FORCE ENCRYPTION (DFE) & ENCRYPTION
You can check my Guides to find for what is used for.
Disable Force Encryption A13 (DFE A13)
Disable Force Encryption (DFE)
Encrypt Data
GOOGLE CAMERA PORTS & UNIVERSAL STOCK CAMERA UNINSTALLER & ANXCAMERA
Note: You can use 2 or more different GCams by installing GCams with different package names.
For example you can use Sanity's v9.6 ENG and BSG v8.1 MGC or Parrot etc... and vice versa.
That way you will have a stable GCam which everything works (Sanity's), but you can also have a latest version of GCam for features that v9.6 of Sanity's doesn't have, like astro mode etc.
Read the FAQ.
Poco F1 Photography: Telegram Group
san1ty
Parrot043
BSG (Public Version) [Video Stabilization Settings]
BSG (Private Version) [XML Configs] [Video Review]
Parrot043 (7.0.009_FinalBuildGoodbye_V1) / Settings (Apply the settings of this thread)
GoogleCameraMod07062019_xiaomi-sdm845 (Old 9.6 PE Default GCam)
ANXCamera (Magisk Module - No Addon needed)
Universal Stock Camera Uninstaller (Flash it in Recovery)
Note: If you updated GcamGo from the Play Store, you will need to flash this file and manually uninstall GcamGo from the app info.
GOOGLE PLAY SYSTEM UPDATE 🛡
You can manually update Google Play System by downloading and installing Main components.
ULTIMATE COLLECTIONS & GUIDES (APPS)
Check the Privacy & Security section in my Guides.
If for some reason you can't find/install an app on Google Play Store due country restrictions or anything, you can sideload the app from APKMirror.
Android Ultimate Collection & Guides
Windows Ultimate Collection & Guides
ReVanced & ReVanced Extended - Guides & Useful Links
UNIVERSAL ANDROID DEBLOATER
Universal Android Debloater
XIAOMI TOOLS
Mi Unlock
Xiaomi Mi Flash Tool
Xiaomi ADB/Fastboot Tools
Fastboot Drivers
Persist Partition (beryllium)
MINIMAL ADB AND FASTBOOT
Minimal ADB and Fastboot
ADB & Fastboot++
Fastboot Drivers
AMD RYZEN/INTEL FASTBOOT FIX
Check the AMD Ryzen Fastboot Fix Guide for the proper steps.
AMD Ryzen/Intel Fastboot Fix (Batch File .bat)
Fastboot Drivers
POCO F1 COLLECTION MIRROR
POCO F1 Collection AFH Mirror
HALL OF FAME OF DEVELOPERS
This section is to honor and support the developers who contribute to keep alive our device with active development over the years and they continue doing it.
This is also a kind of motivation for new or juniors devs to join the Hall of Fame of Developers.
By supporting the Devs not only is helpful for them but also for the community itself.
bgcngm
REIGNZ3
gwolfu
Pierre2324
Scroll Down to check the Guides
POCO F1 Ultimate Guides!
(beryllium)
!DISCLAIMER!
Most people I know (including myself) who used my Guides and steps, did that with success many times. If you don't follow exactly the steps or you do a mistake during the process, I do not take any responsibility for any unexpected results or damage that may happen. However I am here to help if something goes wrong, just ask in the thread.
AMD RYZEN/INTEL FASTBOOT FIX
Some AMD Ryzen or Intel Systems may have problems to recognize your device in fastboot. Try the following ways:
1. Install Fastboot Drivers (Extract the folder for windows 10) at Device Manager while your device is connected in Fastboot mode.
2. Download this .bat file (unzip it) or manually create a .bat file with these lines below, and run it as an administrator, then reboot:
Code:
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\18D1D00D0100" /v "osvc" /t REG_BINARY /d "0000" /f
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\18D1D00D0100" /v "SkipContainerIdQuery" /t REG_BINARY /d "01000000" /f
reg add "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\usbflags\18D1D00D0100" /v "SkipBOSDescriptorQuery" /t REG_BINARY /d "01000000" /f
3. Enable USB Debugging at device (Settings > Additional settings > Developer options > USB Debugging) and give authorization after connecting it to PC.
4. Use USB Hub.
5. Use USB Type-A 2.0.
6. Install AMD Ryzen Chipset Drivers or Intel Chipset Drivers.
Check the steps an another user did to make it work here.
If this doesn't help, unfortunately you have to use Intel System which is more likely to work.
UNLOCK BOOTLOADER
Note: Some AMD Ryzen Systems may have problems to recognize your device in fastboot. [Read the AMD Fastboot Fix Guide above]
Please keep in mind by Unlocking Bootloader the device will reset and all your data will be lost. Make a backup of your data first to PC or to USB.
1. Create a Mi account on Xiaomi’s website.
2. Add a phone number to your Mi account.
3. Insert a SIM into your phone (If you haven't added already). [Do not insert 2 SIM, only 1 until the Bootloader is unlocked. If you have 2 SIM into your phone, remove 1 and reboot.]
4. Enable developer options in Settings > About Phone by repeatedly tapping (7 times) on MIUI Version.
5. Link the device to your Mi account in Settings > Additional settings > Developer options > Mi Unlock status. Also enable USB Debugging.
6. Download the Mi Unlock app (Windows is required to run the app).
7. Run the Mi Unlock app and follow the instructions provided by the app.
8. Reboot your device into Fastboot mode. For that simply turn off your device, press the Power Button + Volume Down (–) button at the same time. Then connect the device to the Windows PC/laptop via a micro USB cable.
9. After device and Mi account are successfully verified, the Bootloader should be Unlocked and your device will restart by itself.
INSTALL CUSTOM RECOVERY
Fastboot Method (No Custom Recovery currently installed)
Note: Some AMD Ryzen Systems may have problems to recognize your device in fastboot. [Read the AMD Fastboot Fix Guide above]
1. Make sure your Bootloader is Unlocked.
2. Enable developer options in Settings > About Phone by repeatedly tapping (7 times) on MIUI Version.
3. Enable USB Debugging in Settings > Additional settings > Developer options > USB Debugging.
4. Download a custom recovery of your choice and copy the .img to your Internal Storage or to SDCard. [You can find a recovery of your choice in my Collection]
5. Download the portable Minimal ADB and Fastboot and run cmd.exe
6. Reboot to Fastboot mode by pressing Power Button + Volume Down (–) and keep holding both buttons until the word “FASTBOOT” appears on the screen, then release.
7. Once the device is in Fastboot mode, connect your device to PC and verify you can find it by typying in cmd: fastboot devices.
8. Boot into Recovery by typing in cmd: fastboot boot <recovery_filename>.img (The file may not be named identically to what stands in this command, so adjust accordingly and write the full path of it, check the example below).
This command will not flash permantly the recovery, it will just temporary boot into it and afterwards you will flash permantly the twrp.img you copied into your Internal Storage or SDcard in recovery partition.
For example:
Code:
fastboot boot C:\Users\Retrial\Desktop\twrp-beryllium-v3.7.0-A12-V2.img
9. Now into TWRP, press Install > Install Image > Locate & Select the twrp.img you previously downloaded and copied from PC into your Internal Storage or to your SDcard > Choose Recovery and Flash!
10. Go back into Home page of TWRP and press Reboot to Recovery or manually by holding Power Button + Volume Up (+) until you boot to Recovery.
11. Done! You now have a new Custom Recovery installed.
Recovery Method (Custom Recovery already installed or booted)
1. Download a custom recovery of your choice. [You can find a recovery of your choice in my Collection]
2. Reboot to Recovery by holding Power Button + Volume Up (+).
3. Press Install > Install Image.
4. Locate the recovery.img you recently downloaded.
5. Select it and choose the option Recovery and Flash.
6. Go back and Reboot to Recovery.
7. Done! Your new recovery should be installed.
CLEAN INSTALL CUSTOM ROM
Note: If you have issues after flash check possible solutions here:
Check integrity of all downloads (compare checksums), do the downloads again.
Make sure you Wiped everything and Formated Data (format data not just wipe) except external SDCard and USB OTG.
Flash only the ROM (without GApps and Magisk) and check if the problem persists. If yes, flash another ROM.
Try other GApps package.
If nothing helps, go back to stock and start from scratch.
Note: You can also Flash Custom ROM using ADB sideload Method.
What is System_EXT? Check out here.
You can also do the same steps below to install Stock MIUI Recovery ROM.
1. Backup all your data to PC or to external SDCard. [All your data into Internal Storage will be lost on step 7 while Formating Data or Wiping Internal Storage]
2. Unlock Bootloader. [Read the Unlock Bootloader Guide above]
3. Download: [You can find everything in my Collection]
Custom Recovery of your choice. [Recommened to use Unofficial TWRP by REIGNZ3 (A12_System_Ext) for A12L+ ROMs]
Custom ROM of your choice.
GApps (be sure you have selected Platform: ARMx64 and the proper Android version of the ROM you are going to flash) if the ROM you are going to flash does not include. [Optional]
Magisk Root. [Optional]
Disable Force Encryption or Encryption. [Optional] (Read DFE & Encryption Guide above)
4. Move all these files in one folder to your PC or to External SDCard if you have one.
5. Install Custom Recovery. [Read the Install Custom Recovery Guide above]
6. Reboot to Recovery Power Button + Volume Up (+)
7. Installation:
Steps without external SDCard:
Select Wipe > Advanced Wipe
Select Dalvik / ART Cache, System, System_Ext, Data, Internal Storage, Vendor, Cache and then Swipe to Wipe. [All your data into Internal Storage will be lost]
Go back > Press Reboot > Reboot to Recovery again. [That step needed for the next step of formating the data because TWRP by REIGNZ have issue]
Go back and select Wipe > Format Data > type yes [All your data into Internal Storage will be lost]
Connect your device to PC while you are on TWRP and transfer into Internal Storage, the ROM, GApps etc. and the files you want to flash.
Flash ROM > GApps [Optional]
[Optional] Mount Vendor and Flash DFE [Optional - Not Recommended] or Encryption [Optional] (Read DFE & Encryption Guide above)
Reboot Enjoy!
[Optional] If you want to root, reboot once again to TWRP Recovery and flash Magisk then reboot to system and enjoy!
Steps with external SDCard:
go to Advanced > File Manager > External_SD and delete all folders in ur ext sd card (For example you should delete: Android, .android_secure, LOST.DIR, DCIM, etc) except your personal files/folders and the folder with your custom ROM/Gapps/Magisk/DFE or Encryption you want to flash.
Each app on your phone with the WRITE_EXTERNAL_STORAGE permission may create files or folders in ur sdcard. Most of these folders have once been created by one of these apps and many of them may be deleted with a few exceptions (e.g. Android, .data, .android_secure, these contain important system or app data like a game's downloaded content):
.android_secure: apps installed and then moved to sdcard
Android: app data/cache
data: app data
.estrongs: ES file manager
LOST.DIR: sort of trash folder (collects recovered files after phone crashes)
DCIM: phone gallery's photos and previews
OTA-update: Over The Air update service
ppy_cross: an unknown third-party app's data.
So I recommend to delete them so you can put your phone/sdcard in a clean state and is guaranteed to be able to re-create these folders.
Select Advanced Wipe
Select Dalvik / ART Cache, System, System_Ext, Data, Internal Storage, Vendor, Cache and then Swipe to Wipe. [All your data into Internal Storage will be lost]
Go back > Press Reboot > Reboot to Recovery again. [That step needed for the next step of formating the data because TWRP by REIGNZ have issue]
Go back and select Wipe > Format Data > type yes [All your data into Internal Storage will be lost]
Flash ROM > GApps [Optional]
[Optional] Mount Vendor and Flash DFE [Optional - Not Recommended] or Encryption [Optional] (Read DFE & Encryption Guide above)
Reboot Enjoy!
[Optional] If you want to root, reboot once again to TWRP Recovery and flash Magisk then reboot to system and enjoy!
DIRTY INSTALL YOUR CUSTOM ROM
Note: Before you start flashing, keep in mind the ROM you dirty flashing MUST be the same with the one you have already installed.
1. Make a full nandroid backup, just in case something goes wrong. You can use TWRP to do that. (TWRP > Backup > Select everything) [Optional]
2. Remove all Magisk modules. [Optional]
3. Reboot to TWRP and Wipe Dalvik / ART Cache, System, System_Ext, Vendor, Cache.
4. Flash the ROM > GApps [Optional] > Magisk [Optional]
5. [Optional] Mount Vendor and Flash DFE [Optional - Not Recommended] or Encryption [Optional] (Read DFE & Encryption Guide above)
6. Reboot and Enjoy!
I've skipped some explanations, because if you are going to dirty flash, you already know for example how to boot to TWRP.
CLEAN INSTALL OFFICIAL STOCK MIUI ROM & RELOCK BOOTLOADER
Note: Some AMD Ryzen or Intel Systems may have problems to recognize your device in fastboot. [Read the AMD Ryzen/Intel Fastboot Fix Guide above]
1. Backup all your data to PC or to external SDCard, if it's possible. [All your data into Internal Storage will be lost]
2. Download the official Fastboot ROM and unzip it to your PC. [You can find it in my Collection]
3. Download Xiaomi Mi Flash Tool and run XiaomiMiFlash.exe.
4. Turn off you device and then boot in Fastboot mode by pressing Power Button + Volume Down (–) and keep holding both buttons until the word “FASTBOOT” appears on the screen, then release.
5. Connect your device to PC via USB Cable.
6. On the Xiaomi Mi Flash Tool, Click on Select and browse to the folder where you have Unzip the downloaded ROM file then press OK.
7. Click on Refresh button and you will see that your device connected to port com.
8. Select what method you prefer:
Clean All: The process will flash full Fastboot ROM and will wipe everything (include user data) but Bootloader will remain unlocked.
Save User Data: The process will flash Fastboot ROM without wiping user data.
Clean All and Lock: The process will flash full Fastboot ROM and will wipe everything (include user data) but Bootloader will be relocked
9. Now click on the Flash button to begin the flashing progress.
10. Once your ROM is successfully flashed, you’ll see green bar inside XiaomiMiFlashtool.
BACKUP & RESTORE ROM (NANDROID BACKUP)
Check this Youtube Video to see the process in action.
Backup:
1. Remove Lockscreen Method. (You will have to set fingerprints again after Restore)
2. Reboot to Recovery (Power Button + Volume Up (+))
3. Choose Backup and Select Boot > System Image > Vendor Image > Data (excl. storage)
4. Select Storage and choose SDcard if you have one otherwise let it on Internal Storage.
5. Swipe to Backup.
6. Done!
Restore:
1. Reboot to Recovery. (Power Button + Volume Up (+))
2. Select Wipe > Advanced Wipe.
3. Select Dalvik / ART Cache, System, System_Ext, Data, Vendor, Cache and then Swipe to Wipe.
4. Press Home Button to go back and Select Restore.
5. Select the backup file with the ROM and make sure Boot, System Image, Data (excl. storage) and Vendor Image are selected.
6. Select Swipe to Restore and when completed Reboot to System.
7. Done!
Note: After you restore backup you might be unable to use old lock method such as PIN or Pattern to unlock your device (that's why you remove it before you take backup), in order to remove lock method you need to boot recovery and then:
Mount system
Go to file manager
Go to data/system
Delete locksettings.db
This way, you will not have any lock method set, but added fingerprints will remain.
FIX FOR STUCK ON OREO FIRMWARE (SOFTBRICKED)
FIX (Read Carefully)
MAGISK ROOT
The easiest way to root your device is via Magisk, it should work in all ROMs, Stock and Customs.
Install Magisk:
1. Install latest TWRP Recovery. [Read the Install Custom Recovery Guide above]2. Download the Magisk [You can find it in my Collection]3. Reboot to TWRP Recovery by pressing Power Button + Volume Up (+) and flash it.4. Reboot and check whether the Magisk app is installed. If it isn’t installed automatically, manually install the APK. [You can find it in my Collection]Note#1: From Official TWRP Recovery 3.5.1 and onwards (and other recoveries based on that), Magisk.apk can be flashed as apk without the need of rename it to .zip. So you can simply flash the Magisk.apk in TWRP.Manually Creation of Flashable Zip:Download the latest Magisk APK and rename the Magisk.apk → Magisk.zip.Note#2: If your bank apps detect root, follow this Guide.
Uninstall Magisk:
Flash the Uninstall.zip in TWRP Recovery and reboot. [You can find it my Collection]
If Magisk App isn’t uninstalled automatically, manually uninstall the app.
Manually creation of Flashable Uninstall Zip:
Download the latest Magisk APK and rename the Magisk.apk → uninstall.zip
Uninstall Magisk directly through the Magisk app. Simply press the Uninstall button.
Note: If your apps detect root, follow this Guide (or this) to pass SafetyNet and have certified Play Store. [YouTube Video Guide]
DISABLE FORCE ENCRYPTION (DFE) & ENCRYPTION
[You can find it in my Collection]
Disable Force Encryption
Disable Force Encryption (a.k.a DFE) is flashed during installation of a custom ROM to avoid the system encrypting /data partition when the devices boot for the first time.Some ROMs are not encrypted by default and so is not necessary to flash DFE. However if your ROM comes with encryption by default you can always flash DFE after clean installation of ROM and always after every update or flash or you can use any custom recovery like OrangeFox, Pitchblack, Skyhawk Recovery Project which can automatic flash DFE after every flash.I don't recommended to use DFE if you don't switch ROMs frequently and you are casual user. Beside the fact that if you lose your device your data are not protected, many people get in confusion while doing OTA or manually updates, which if the ROM is encrypted by default and flashed DFE and in next update you forget to flash DFE you will lock out from your data and you wil get into bootloop (use custom recoveries mentioned above to avoid that).
Encryption
Encrypted ROMs are recommended if you are stable and casual user of a ROM. Encryption have the benefit to protect your data, in case you lose your device for example. Always use the latest TWRP Recovery so you can be able to decrypt the data by filling the same lock screen password you have set in ROM.Some ROMs are not encrypted by default but devs provide an Encryption.zip (script) which can encrypt the ROM. Same as DFE you need to flash it after clean installation of ROM and always after every update to stay encrypted and not get into bootloop. Unfortunatly there is not any custom recovery automatic doing that like with DFE, so you must be careful, avoid doing OTA updates and flash it every time you manually update a ROM.
REMOVE SECURITY PIN/PATTERN (LOCKSCREEN SETTINGS)
Check HERE and HERE.
SCREEN RETENTION FIX
Screen Retention FIx: If you have an issue with screen retention apply this configuration to your device ROM.
HOW TO TAKE LOGS
How to take logs on Android
BATTERY TIPS
Xiaomi POCOPHONE F1 Battery Model: BM4E
Battery Replacment (Video)
Recommended Battery: NOHON for POCO F1 (AliExpress)
Advanced Guide
Simple Battery & Charging Tips
Improve your SOT
Battery Calibration
Method 1
Steps:
1. Discharge your phone fully until it turns itself off.
2. Turn it on again and let it turn itself off.
3. Plug your phone into a charger and, without turning it on, let it charge until the on-screen or LED indicator says 100 percent.
4. Turn your phone on. It's likely that the battery indicator won't say 100 percent, so plug the charger back in (leave your phone on) and continue charging until it says 100 percent on-screen as well.
5. Unplug your phone and restart it. If it doesn't say 100 percent, plug the charger back in until it says 100 percent on screen.
6. Repeat this cycle until it says 100 percent (or as close as you think it's going to get) when you start it up without it being plugged in.
Method 2
Notes: It won't dramatically extend battery life, but it will give your old battery at least 30 minutes additional run time.
Steps:
1. Get "GSam or Ampere" from the Google Play Store.
2. Launch the app and fully charge your phone. (Important: Only proceed with the calibration when the word "Full" appears in GSam or Ampere.)
3. While your phone is still connected to the cable reboot your phone to recovery mode, open file manager and navigate to "/data/system" and delete "batterystats.bin," "batterystats-checkin.bin," and "batterystats-daily.xml."
4. Reboot your phone (while it is still plugged in) and charge it until it reads "full" on GSam or Ampere.
5. Unplug the cable and use your phone normally until it shuts down (0 percent )
6. Charge your phone to 100% while it is turned off.
7. Boot into os and plug in your phone and charge it until it says "full" on the GSam or Ampere.
8. Unplug and have fun!
Battery Capacity Health
Notes:
1) Before checking the battery health, charge the device to 100%.
2) Check charge counter values and consider first 4 digits from left as your battery capacity in mAh. And check charge counter. (Charge counter/level)*100 is the battery capacity.
To find battery capacity in Windows:
Enable Developer options in your device.
Enable USB Debugging in your device.
Conect your device to PC and give permissions.
Open Minimal ADB (run cmd.exe) or Platform tools.
Type "adb shell dumpsys battery" command in Minimal ADB or Platform tools.
To find battery capacity in Android (Terminal) - Root needed:
Download an android terminal app like Termux,
Open terminal and type: cat/sys/class/power_supply/battery/charge_full
Overheating
Following reasons will lead to device heating issue:
During the initial setup after purchase or when restoring data.
Downloading large files.
Using apps that require more power or using apps for extended periods such as:
Playing high-quality games for long time.
Recording videos for extended periods.
Streaming videos while using the maximum brightness setting.
Using the Screen Mirroring / Smart View feature (connecting mobile to a TV).
While multitasking or when running many apps in the background i.e:
Using Multi window.
Updating or installing apps while recording videos.
Downloading large files during a video call.
Recording videos while using a navigation app.
Large amount of data for syncing with the cloud, email, or other accounts.
Exposing device under sunlight when temperature is high around you.
Extensive usage of mobile hotspot and tethering feature.
Using device in areas with weak signals or no reception or in roaming network.
Charging the battery with a damaged / unapproved USB cable.
Device's multipurpose jack is damaged or exposed to foreign materials, such as liquid, dust, metal powder, and pencil lead.
Solution:
Turn off Wi-fi, GPS , bluetooth and other connectivity options when not in use by dragging the notification panel.
Decrease screen brightness.
Close background running applications.
Too many applications installed in device may result in device heating since their corresponding process will keep on running in background. It is advised to uninstall un-necessary apps if not using them.
Avoid using apps like GPS, data dependent apps or graphic intensive games for longer duration since they require more energy to function, causing device to heat.
It is advised not to use device while charging as it may cause the device to over heat.
General:
DO:
Use manual brightness or dim the screen.
Turn off notifications for apps you don't use. Better still, delete/disable the apps entirely if you don't need them.
Enable battery or power saving mode when you want to extend your battery life.
Use the power adapter that came with your phone. Other chargers can charge slowly/faster but they can also damage your phone or battery.
Turn off bluetooth, location tracking, and Wi-Fi (unless you are actively using it)
Turn off print services from bluetooth connection preferences.
Avoid extremes of heat and cold. If your phone gets very hot or cold it can strain the battery and shorten it's lifespan.
DON'T:
Have Bluetooth or Wi-Fi turned on constantly.
Leave apps running in the background. Instead restrict background usage off apps that you don't need running.
Push email means your device is always listening for new email which drains alot of battery.
Drain your phone battery all the way to 0% or charging it all the way to 100%. Keep it between 20% - 90% for longer battery lifespan.
The more advanced the graphics and animations are (games, videos, photos, animations), the harder the processor and graphics chip in your smartphone have to work. More activity means more battery use.
PRIVACY & SECURITY
Some useful links:
All about Privacy & Security at Privacy Guides.
Electronic Frontier Foundation.
Check if your email address or your phone number is in a data breach at Have I been Pwned & at Firefox Monitor.
PrivacyTests: Open-source tests of web browsers privacy.
Test your browser to see how well you are protected from tracking and fingerprinting at Cover Your Tracks by EFF and at Bromite fingerprint mitigations tests.
WebRTC IP Leak Test. WebRTC is a new communication protocol that relies on JavaScript that can leak your actual IP address from behind your VPN. You can find more infos how to disable it at Privacy Guides in browsers section.
Ad Block Tester is a free service on the Internet to evaluate content blocking solutions. It is not designed to be a benchmark, but it reveals the level of blocking against a set of hosts that are very popular.
Check on AM I FLoCed? by EFF if your your Chrome browser has been turned into a guinea pig for Federated Learning of Cohorts or FLoC, Google’s latest targeted advertising experiment.
How to block ads on Android.
εxodus: εxodus analyzes Android applications in order to list the embedded trackers and ads.
Spyware Watchdog Article Catalog: A catalog which determinate under tests and tracking if an app is spyware and what data it collects.
CryptPad: CryptPad is built to enable collaboration. It synchronizes changes to documents in real time. Because all data is encrypted, the service and its administrators have no way of seeing the content being edited and stored.
PrivateBin: PrivateBin is a minimalist, open-source online pastebin where the server has zero knowledge of pasted data. Data is encrypted/decrypted in the browser using 256-bit AES. It is the improved version of ZeroBin.
ShutUP10++ , Privacy.Sexy: Disable major tracking features of Windows.
General:
Always prefer Open Source or well popular Programs, Apps, ROMs, Kernels & Stuff.
Open Source doesn't mean it's 100% safe but it's unlikely to have something suspicious, since you and other users can check the code in GitHub or in any other code hosting platform the "stuff" is hosted. You can also find and use FOSS apps at F-Droid or at Droid-ify (Recommended).
Prefer ROMs & Kernels with SELinux Enforcing. You can find informations here.
Always download and install Apps, Programs, ROMs & Stuff from official sources and do not use redirection links from different sites. Google is your friend to find the official source of the stuff you want.
Always check the permissions an app requires, before download and install it to your device. If an app ask for permissions which has nothing to do with the app functionality then it's should be reconsider or ask the developer why these permissions needed.
You can also check if the app includes trackers and ads with εxodus.
If you want to avoid Google and Play Store (De-Google), you can choose a ROM without GApps preinstalled like LineageOS and use Droid-ify client which is an installable catalogue of FOSS (Free and Open Source Software) applications for the Android platform. The client makes it easy to browse, install, and keep track of updates on your device. Note that not all apps from Play Store will be available in Droid-ify or F-Droid. Only Open Source projects. You can find alternatives though.
Alternative you can use LineageOS for microG or any ROM which support signature spoofing and can support microG and use Aurora Store.
For Windows use the default Windows Defender & Malwarebytes to scan your files whenever you want (Prefered before open or install them). Also use the addon/extension uBlock Origin in your Browser. These should be enough for normal users. You can also use the tool ShutUP10++ or Privacy.Sexy to disable major tracking features of Windows.
For Android Do not use any antivirus - antimalware since it's useless, just check what apps and from where you installing.
Always verify the source of addons/extensions in your browser. Avoid installing random and unpopular addons/extensions. Keep it minimal and clean, so browser can be fast and safe, no need bunch of extensions.
If you are using VPN, always check the terms and rules of the provider. Avoid random VPN Services.
Recommended VPN Services.
Using a VPN will not keep your browsing habits anonymous, nor will it add additional security to non-secure (HTTP) traffic.
Recommended is to encrypt your data/files always before uploading them to cloud with tools like Cryptomator.
Always use unique and strong passwords for each of your accounts.
Use awarded open source Password Managers like KeePass or KeePassXC for Desktop and KeePassDX for Android to manage your passwords and have them with you safe, encrypted and secure. Must be noted you can use the same database file between these programs.
Always enable 2 Step Authentication wherever is available for your accounts.
You can use apps like Aegis Authenticator.
Do not open or click on links attached in unknown emails or SMS you may get. Always check the address of the email or the number of SMS and verify it's legit from the official source.
Create and use "burned" email for accounts/sites you have concerns but you definitely want to try them. Do not use your personal or business email. You can also create and use email aliases of your email with SimpleLogin which is open source and awesome service.
Changelog
Note: Changes in Collection & Guides happens in real time. The date I post these Changelogs is just a sum up since I can't post all the changes the time that happening to avoid spamming the thread. So you can always consider the Collection & Guides Up-to-Date. However, I may announce some big changes in posts before I include them in the Changelogs.
LATEST
Update: 07/06/2023
Changelog
ARCHIVED
Update: 08/04/2023
Changelog
Update: 18/01/2023
Changelog
Update: 16/12/2022
Changelog
Update: 29/10/2022
Changelog
Update: 24/09/2022
Changelog
Update: 02/08/2022
Changelog
Update: 01/07/2022
Changelog
Update: 30/05/2022
Changelog
Update: 01/05/2022
Changelog
Update: 28/02/2022
Changelog
Update: 28/02/2022
Changelog
Update: 07/02/2022
Changelog
Update: 20/01/2022
Changelog
Update: 23/12/2021
Changelog
Update: 20/11/2021
Changelog
Update: 16/10/2021
Changelog
Update: 31/08/2021
Changelog
Update: 02/08/2021
Changelog
Update: 17/07/2021
Changelog
Update: 22/06/2021
Changelog
Update: 23/05/2021
Changelog
Update: 01/05/2021
Changelog
Update: 19/04/2021
Changelog
Update: 04/04/2021
Changelog
Update: 16/03/2021
Changelog
Update: 27/02/2021
Changelog
Update: 26/02/2021
Changelog
Update: 23/02/2021
Changelog
Update: 21/02/2021
Changelog
Update: 25/01/2021
Changelog
Update: 14/01/2021
Changelog
Update: 13/01/2021
Changelog
Update: 17/12/202
Changelog
Update: 20/11/2020
Initial Release
Awesome job, my friend! :good:
Great job. Everything in one place.
Sent from my POCOPHONE F1 using Tapatalk
Amazing Work. All silly and important questions have been answered at one place.
+Add Mi Assistant (Xiaomi PC Suite China) in Xiaomi Tools. It Helps to fix bootloop in locked bootloader nowadays.
this in one stop for all poco stuff...
amazing work.... [emoji106][emoji106][emoji106][emoji106]
SPLESHER said:
Awesome job, my friend! :good:
Click to expand...
Click to collapse
Kadajo said:
Great job. Everything in one place.
Sent from my POCOPHONE F1 using Tapatalk
Click to expand...
Click to collapse
Krisranger said:
Amazing Work. All silly and important questions have been answered at one place.
+Add Mi Assistant (Xiaomi PC Suite China) in Xiaomi Tools. It Helps to fix bootloop in locked bootloader nowadays.
Click to expand...
Click to collapse
Mr.Sm1th said:
this in one stop for all poco stuff...
amazing work.... [emoji106][emoji106][emoji106][emoji106]
Click to expand...
Click to collapse
Thank you guys! I will try to keep the thread always up-to-date.
If you find a broken link, something wrong or you have a suggestion, please do not hesitate, tell it!
Today I made couple of changes in Guides & Collection so infos can be more clear and I've added some stuff!
Retrial said:
Thank you guys! I will try to keep the thread always up-to-date.
If you find a broken link, something wrong or you have a suggestion, please do not hesitate, tell it!
Today I made couple of changes in Guides & Collection so infos can be more clear and I've added some stuff!
Click to expand...
Click to collapse
Im in now miui global 12.0.2
I facing problem while voice call
Another end of caller hear a noise
Is there fix
Please guide me ...
hari1jack said:
Im in now miui global 12.0.2
I facing problem while voice call
Another end of caller hear a noise
Is there fix
Please guide me ...
Click to expand...
Click to collapse
Try to do factory reset (firstly save all your personal data to PC or to external SDCard). 12.0.2 and general all the latest miui updates are full of bugs and slow down your device. Also the chances to get new android version in miui are very low. I will not talk about security and tracking.
I recommended you to move away from miui and use a custom rom of your choice. :fingers-crossed:
Awesome thread, everything at one place. Thanks man.
You have gathered so much collective information at one place. It will be helpful if we found which Roms are from Pixel Ports and supports Google photos free unlimited high quality storage.
OP, this is a godsend! Thank you so so much. Any idea what settings I should be using for the most "pixel like" photos on parrots gcam?
raydialseeker113 said:
OP, this is a godsend! Thank you so so much. Any idea what settings I should be using for the most "pixel like" photos on parrots gcam?
Click to expand...
Click to collapse
Hey thanks! I mostly use the default settings and I get very nice photos.
Krisranger said:
You have gathered so much collective information at one place. It will be helpful if we found which Roms are from Pixel Ports and supports Google photos free unlimited high quality storage.
Click to expand...
Click to collapse
Unfortunately, It's unknown yet. I will keep an eye on it but I doubt if it will work. Even new pixel phones will not have free unlimited storage. We will see...
Retrial said:
Hey thanks! I mostly use the default settings and I get very nice photos.
Click to expand...
Click to collapse
Any idea why the autofocus on the camera is so broken?
Using PE+ and ngk2.0
raydialseeker113 said:
Any idea why the autofocus on the camera is so broken?
Using PE+ and ngk2.0
Click to expand...
Click to collapse
I don't know but you can try the latest port of Parrot or use Sanitys or BSG ports. Try and find out which is the best for you You can also try to ask on Photography thread.
Retrial said:
Try to do factory reset (firstly save all your personal data to PC or to external SDCard). 12.0.2 and general all the latest miui updates are full of bugs and slow down your device. Also the chances to get new android version in miui are very low. I will not talk about security and tracking
I recommended you to move away from miui and use a custom rom of your choice. :fingers-crossed:
Click to expand...
Click to collapse
Thank you for the reply ...
Can you suggest me bug less rom without mic issue during call
Retrial said:
Unfortunately, It's unknown yet. I will keep an eye on it but I doubt if it will work. Even new pixel phones will not have free unlimited storage. We will see...
Click to expand...
Click to collapse
Yes new pixel phones will not have this advantage. (New pixel phones which ain't even launched yet)
But we have some roms which are ported from existing pixel phones like Pixel 3 and Pixel 4.
I got to know that Awaken OS based on Android 11 is detecting as Pixel 4 in Google photos. I'm not sure, I personally didn't install it yet.
I'm sure about some Roms and Ports like Pixel Rom and Pixel 4 xl ports are obviously detecting as Pixel 4 and they are enjoying new Google Assistant and Google One features as well.
hari1jack said:
Thank you for the reply ...
Can you suggest me bug less rom without mic issue during call
Click to expand...
Click to collapse
I personally use Pixel Experience the Plus Edition. It's stable and ready out of the box.
However there a lot of nice ROMs, you check them in my collection and decide which fit for you.
Krisranger said:
Yes new pixel phones will not have this advantage. (New pixel phones which ain't even launched yet)
But we have some roms which are ported from existing pixel phones like Pixel 3 and Pixel 4.
I got to know that Awaken OS based on Android 11 is detecting as Pixel 4 in Google photos. I'm not sure, I personally didn't install it yet.
I'm sure about some Roms and Ports like Pixel Rom and Pixel 4 xl ports are obviously detecting as Pixel 4 and they are enjoying new Google Assistant and Google One features as well.
Click to expand...
Click to collapse
Well the thing is we don't know yet if POCO F1 detecting as Pixel 4 in Google Security is enough to bypass and trick Google to have unlimited storage. We need to wait till June 1st, 2021 which this change will take place. Until then, the storage remain unlimited.
Welcome to S4 Unified Collection!
STOCK ROM FIRMWARES
[Check my Guides for Installation]
Note: If you can't find the Firmware for your device from the link below, then it's not my fault. Android File Host informed me, they delete files with less population on downloads. I don't have these files anymore.
You can find the latest Stock ROM Firmware for your S4 variant below:
GT-I9295 (jactivelte): I9295XXSDQD6 / Build Date: 2017-04-20 / OS: Lollipop 5.0.1
GT-I9500 (ja3gxx): I9500XXUHQD1 / Build Date: 2017-04-25 / OS: Lollipop 5.0.1
GT-I9505 (jfltexx): I9505XXUHQK1 / Build Date: 2017-11-09 / OS: Lollipop 5.0.1
GT-I9505G (jgedlte): I9505GUEUDPF1 / Build Date: 2016-05-13 / OS: Lollipop 5.1.1
GT-I9506 (ks01lte): I9506XXUDRB1 / Build Date: 2018-02-15 / OS: Lollipop 5.0.1
GT-I9515 (jfvelte): I9515XXS1BQD2 / Build Date: 2017-04-17 / OS: Lollipop 5.0.1
GT-I9515L (jfvelte): I9515LUBU1BQF1 / Build Date: 2017-06-08 / OS: Lollipop 5.0.1
SCH-I545 (jfltevzw): VERIZON USERS: since your bootloader is locked, you must be on the VRUAMDK
SCH-I545L (jfltelra): I545LWWSGQA1 / Build Date: 2017-01-05 / OS: Lollipop 5.0.1
SCH-R970 (jflteusc): R970TYSGPL1 / Build Date: 2016-12-02 / OS: Lollipop 5.0.1
SCH-R970C (jfltecri): R970CVRUFND1 / Build Date: 2014-04-11 / OS: KitKat 4.4.2
SCH-R970X (jfltecsp): R970XWWSGQA1 / Build Date: 2017-01-05 / OS: Lollipop 5.0.1
SGH-I337 (jflteatt): AT&T USERS: since your bootloader is locked, you must be on the UCUAMDB or UCUAMDL
SGH-I337M (jftlecan): I337MVLSGQB1 / Build Date: 2017-02-09 / OS: Lollipop 5.0.1
SGH-M919 (jfltemo): M919UVSFQA1 / Build Date: 2017-01-04 / OS: KitKat 4.4.4
SM-S975L (TracFone-StraightTalk): S975LUDUANB1 / Build Date: 2014-02-04 / OS: Jelly Bean 4.3
SPH-L720 (jfltespr): L720VPSGPL1 / Build Date: 2016-12-20 / OS: Lollipop 5.0.1
MODEMS & BOOTLOADERS
[Check my Guides for Installation]
Note: If you can't find the Modem/Bootloader for your device from the link below, then it's not my fault. Android File Host informed me, they delete files with less population on downloads. I don't have these files anymore.
You can find the latest Bootloader & Modem for your S4 variant below:
GT-I9295 (jactivelte): I9295XXSDQD6 COMBINED BOOTLOADER & MODEM / BOOTLOADER - MODEM
GT-I9500 (ja3gxx): I9500DXUHPB1 MODEM
GT-I9505 (jfltexx): I9505XXUHQK1 COMBINED BOOTLOADER & MODEM / BOOTLOADER - MODEM
GT-I9505G (jgedlte): I9505GUEUDPF1 MODEM
GT-I9506 (ks01lte): I9506XXUDRB1_I9506XXUDRA1 COMBINED BOOTLOADER & MODEM / BOOTLOADER - MODEM
GT-I9515 (jfvelte): I9515XXU1BQD2 COMBINED BOOTLOADER & MODEM / BOOTLOADER - MODEM
GT-I9515L (jfvelte): I9515LUBU1BQF1 COMBINED BOOTLOADER & MODEM / BOOTLOADER - MODEM
SCH-I545 (jfltevzw): VERIZON USERS: since your bootloader is locked, you must be on the VRUAMDK
SCH-I545L (jfltelra): I545LWWSGQA1 COMBINED BOOTLOADER & MODEM / BOOTLOADER - MODEM
SCH-R970 (jflteusc): R970TYSGPL1 COMBINED BOOTLOADER & MODEM / BOOTLAODER - MODEM
SCH-R970C (jfltecri): R970CVRUFND1 COMBINED BOOTLAODER & MODEM / BOOTLOADER - MODEM
SCH-R970X (jfltecsp): R970XWWSGQA1 COMBINED BOOTLOADER & MODEM / BOOTLOADER - MODEM
SGH-I337 (jflteatt): AT&T USERS: since your bootloader is locked, you must be on the UCUAMDB or UCUAMDL
SGH-I337M (jftlecan): I337MVLSGQB1 COMBINED BOOTLOADER & MODEM / BOOTLOADER - MODEM
SGH-M919 (jfltemo): M919UVSFQA1 COMBINED BOOTLOADER & MODEM / BOOTLOADER - MODEM
SM-S975L (TracFone-StraightTalk): S975LUDUANB1 COMBINED BOOTLOADER & MODEM / BOOTLOADER - MODEM
SPH-L720 (jfltespr): L720VPSGPL1 COMBINED BOOTLOADER & MODEM / BOOTLOADER - MODEM
RECOMMENDED ROMS
Recommend ROMs for the variants below, are:
Official LineageOS / LineageOS microG, Official crDroid, Official DivestOS or any of JDCTeam ROMs with tags [LIVE] [STABLE] [DAILY]
GT-I9505 (jfltexx)
GT-I9505G (jgedlte)
GT-I9507 (jtfddxx)
GT-I9508 (jfltezm)
GT-I9515 (jfvelte)
GT-I9515L (jfvelte)
SCH-I545 (jfltevzw) VERIZON USERS: since your bootloader is locked, you must be on the VRUAMDK
SCH-I545L (jfltelra)
SCH-R970 - jflteusc
SCH-R970C (jfltecri)
SCH-R970X (jfltecsp)
SGH-I337 (jflteatt) AT&T USERS: since your bootloader is locked, you must be on the UCUAMDB or UCUAMDL
SGH-I337M (jftlecan)
SGH-M919 (jfltemo)
SM-S975L (TracFone-StraightTalk)
SPH-L720 (jfltespr)
Recommened ROMs for the variants below are:
GT-I9295 (jactivelte): Official LineageOS / LineageOS microG
GT-I9500 (ja3gxx): -
GT-I9506 (ks01lte): Unofficial LineageOS 20.0 or Unofficial crDroid
TWRP RECOVERIES
[Check my Guides for Installation]
The list below contains the variants which can use the latest Official Unified TWRP Recovery or Unofficial TWRP Recovery or OrangeFox Recovery:
GT-I9505 (jfltexx)
GT-I9505G (jgedlte)
GT-I9507 (jtfddxx)
GT-I9508 (jfltezm)
SCH-I545 (jfltevzw)
SCH-I545L (jfltelra)
SCH-R970 - jflteusc
SCH-R970C (jfltecri)DCTeam
SCH-R970X (jfltecsp)
SGH-I337M (jftlecan)
SGH-M919 (jfltemo)
SM-S975L (TracFone-StraightTalk)
SPH-L720 (jfltespr)
The list below contains the variants which need a specific TWRP Recovery version:
GT-I9295 (jactivelte): Official TWRP Recovery
GT-I9500 (ja3gxx): Official TWRP Recovery
GT-I9506 (ks01lte): Official TWRP Recovery / TWRP- 3.6.0_9-0 or OrangeFox Recovery Project
GT-I9515 (jfvelte): Official TWRP Recovery
GT-I9515L (jfvelte): Official TWRP Recovery
SGH-I337 (jflteatt): TWRP Recovery Locki Patched by mattgyver
GAPPS & microG
GApps
Note: You should always use the smallest package of GApps, be sure you have selected Platform: ARM and the proper Android version of the ROM you are going to flash. If the ROM you want to flash include GApps, no need to download and flash any GApps at all.
Most of the GApps have also a config. file which can be used to to configure your installation the way you like. You can skip any Package that you don't want to be part of your installation. For more infos about that, read the instructions of the GApps you chose or search in Google.
MindTheGapps
BiTGApps
NikGApps (Only Core version)
Open GApps / Open GApps Unofficial A12L
LiteGapps
microG
If you don't want to use Google Play Services and general move away from Google, microG and its variants is an open source alternative which replace these services.
NanoDroid
MinMicroG
BiTGApps microG
microG
MAGISK ROOT
You can check my Guides for installation.
Magisk (APK)
Magisk.zip (Flashable Zip)
Uninstall.zip (Flashable Zip)
Magisk Canary (APK)
Magisk Delta
FoxMagiskModuleManager (This app replace the official magisk module repository since no longer available)
Momo (You can use this app too check if any modifications related Magisk are detected or not)
Universal SafetyNet Fix by kdrag0n [Video Guide]
Shamiko (Hide Root from apps) [Guide]
Note: If your apps detect root, follow this Guide (or this) to pass SafetyNet and have certified Play Store. [YouTube Video Guide]. For Microsoft Intune and other microsoft apps, check this guide.
PIT FILES
Note: If you messed the partitions of your device, you can fix it by simply flashing the PIT FILE for your variant via Odin in the PIT TAB.
The list below contains PIT FILES for some variants:
GT-I9500 (ja3gxx) PIT FILE
GT-I9505 (jftlexx) PIT FILE
SAMSUNG USB DRIVER
Note: If you have a problem while you connect the device to your PC and PC can't recognize it, you may miss the Samsung USB DRIVER. To fix follow these steps:
1. Download SAMSUNG USB DRIVER.
2. Unzip it and install it to your PC.
3. Connect your device and done! Now should be ok.
ODIN
You can download ODIN HERE. Recommened version is Odin 3.12.3
ULTIMATE COLLECTIONS & GUIDES (APPS)
Check the Privacy & Security section in my Guides.
If for some reason you can't find/install an app on Google Play Store due country restrictions or anything, you can sideload the app from APKMirror.
Android Ultimate Collection & Guides
Windows Ultimate Collection & Guides
ReVanced & ReVanced Extended - Guides & Useful Links
UNIVERSAL ANDROID DEBLOATER
Universal Android Debloater
S4 UNIFIED COLLECTION MIRROR
S4 Unified Collection AFH Mirror
DISCORD SERVER
Please verify yourself at #welcome channel. Read #FAQ channel.
Discord Server
JDCTEAM UNIVERSE
Here you can find the work of JDCTeam over the years for our S4 device!
Scroll Down to check the Guides
Welcome to S4 Unfied Guides!
!DISCLAIMER!
Most people I know (including myself) who used my Guides and steps, did that with success many times. If you don't follow exactly the steps or you do a mistake during the process, I do not take any responsibility for any unexpected results or damage that may happen. However I am here to help if something goes wrong, just ask in the thread.
INSTALL BOOTLOADER & MODEM
You can flash Bootloader & Modem with two methods:
Combined: [Recommended]
1. Download Odin and the COMBINED BOOTLOADER _MODEM.tar for your variant to your PC. [You can find everything in my Collection]
2. Reboot your device to Download Mode by pressing Power Button + Vol.down + Home Button and run Odin from your PC as administrator.
3. Put the COMBINED BOOTLOADER_MODEM.tar to AP section, untick Auto-Reboot, flash!
4. When It's done, reboot your device by pressing Power Button for couple of seconds.
Seperate:
1. Download Odin, the BOOTLOADER.tar and MODEM .tar for your variant to your PC. [You can find everything in my Collection]
2. Reboot your device to Download Mode by pressing Power Button + Vol.down + Home Button and run Odin from your PC as administrator
3. Put the BOOTLOADER to BL section and MODEM to CP section, untick Auto-Reboot and flash!
4. When It's done, reboot your device by pressing Power Button for couple of seconds.
Notes:
Check what version of Modem and Bootloader you have with apps like Device Info HW.
If Modem & Bootloader didn't changed to the version you wanted, do the same steps again with the method you have selected.
If for some reason Odin failed to flash, make sure your run Odin as adminstrator, try to change USB Port in your PC and don't move the cable during flash. Also if you have Odin and the files on an External hard drive, move Odin and all the files you want to flash, into one folder to your Main Drive for example C: drive.
For Stock Rom to have your WiFi working you need to have the same version of Modem/BL as your Firmware. For example if you have QK1 Stock ROM then you need to have QK1 Modem/Bootloader. On Custom ROMs doesn't matter. You can have any Modem/BL of your variant you want but recommend is always the latest.
INSTALL TWRP RECOVERY
ODIN Method (No TWRP Recovery currently installed)
1. Download Odin and the .tar file of the TWRP to your PC. [You can find everything in my Collection]
2. Reboot to Download Mode by pressing Power Button + Vol.Down + Home Button.
3. Run Odin as adminstrator > connect your device to PC > put the .tar file of TWRP in AP section > untick Auto-Reboot in options and flash.
4. Done! Restart to TWRP Recovery. (power button+vol.up+home button)
Recovery Method (TWRP Recovery already installed)
1. Download .img of TWRP Recovery. [You can find everything in my Collection]
2. Reboot to Recovery by holding Power Button + Volume Up (+).
3. Press Install Image.
4. Locate the recovery.img you recently downloaded.
5. Select it and choose the option Recovery and Flash.
6. Go back and Reboot to Recovery.
7. Done! Your new recovery should be installed.
CLEAN INSTALL CUSTOM ROM
Note: If you have issues after flash check possible solutions here:
Check integrity of all downloads (compare checksums), do the downloads again.
Make sure you Wiped everything and Formated Data (format data not just wipe) except external SDCard and USB OTG.
Flash only the ROM (without GApps and Magisk) and check if the problem persists. If yes, flash another ROM.
Try other GApps package.
If nothing helps, go back to stock and start from scratch.
Note: You can also Flash Custom ROM using ADB sideload Method.
1. Backup all your data to PC or to external SDCard. [All your data into Internal Storage will be lost on step 7 while Formating Data or Wiping Internal Storage]
2. Install the latest Bootloader & Modem for your S4 variant. [Read the Install Bootloader & Modem Guide above]
3. Download: [You can find everything in my Collection]
TWRP Recovery.
Custom ROM of your choice.
GApps (be sure you have selected Platform: ARM and the proper Android version of the ROM you are going to flash) if the ROM you are going to flash does not include. [Optional]
Magisk Root. [Optional]
4. Move all these files in one folder to your PC or to External SDCard if you have one.
5. Install TWRP Recovery. [Read the Install Custom Recovery Guide above]
6. Turn off your device and Reboot to Recovery Power Button + Volume Up (+)
7. Installation:
Steps without external SDCard:
Select Wipe > Advanced Wipe
Select Dalvik / ART Cache, System, Data, Internal Storage, Cache and then Swipe to Wipe. [All your data into Internal Storage will be lost]
Go back and select Wipe > Format Data > type yes [All your data into Internal Storage will be lost]
Connect your device to PC while you are on TWRP and transfer into Internal Storage, the ROM, GApps etc. and the files you want to flash.
Flash ROM > GApps [Optional]
Reboot Enjoy!
[Optional] If you want to root, reboot once again to TWRP Recovery and flash Magisk (you need to download it again if you previously had it in Internal Storage) then reboot to system and enjoy!
Steps with external SDCard:
go to Advanced > File Manager > External_SD and delete all folders in ur ext sd card (For example you should delete: Android, .android_secure, LOST.DIR, DCIM, etc) except your personal files/folders and the folder with your custom ROM/Gapps/Magisk/DFE you want to flash.
Each app on your phone with the WRITE_EXTERNAL_STORAGE permission may create files or folders in ur sdcard. Most of these folders have once been created by one of these apps and many of them may be deleted with a few exceptions (e.g. Android, .data, .android_secure, these contain important system or app data like a game's downloaded content):
.android_secure: apps installed and then moved to sdcard
Android: app data/cache
data: app data
.estrongs: ES file manager
LOST.DIR: sort of trash folder (collects recovered files after phone crashes)
DCIM: phone gallery's photos and previews
OTA-update: Over The Air update service
ppy_cross: an unknown third-party app's data.
So I recommend to delete them so you can put your phone/sdcard in a clean state and is guaranteed to be able to re-create these folders.
Select Advanced Wipe
Select Dalvik / ART Cache, System, Data, Internal Storage, Cache and then Swipe to Wipe. [All your data into Internal Storage will be lost]
Go back and select Wipe > Format Data > type yes [All your data into Internal Storage will be lost]
Flash ROM > GApps [Optional]
Reboot Enjoy!
[Optional] If you want to root, reboot once again to TWRP Recovery and flash Magisk then reboot to system and enjoy!
DIRTY INSTALL YOUR CUSTOM ROM
Note: Before you start flashing, keep in mind the ROM you dirty flashing MUST be the same with the one you have already installed.
1. Make a full nandroid backup, just in case something goes wrong. You can use TWRP to do that. (TWRP > Backup > Select everything) [Optional]
2. Remove all Magisk modules. [Optional]
3. Reboot to TWRP and Wipe Dalvik / ART Cache, System and Cache.
4. Flash the ROM > GApps [Optional] > Magisk [Optional]
5. Reboot and Enjoy!
I've skipped some explanations, because if you are going to dirty flash, you already know for example how to boot to TWRP.
CLEAN INSTALL OFFICIAL STOCK ROM
Note: For Stock Rom to have your WiFi working you need to have the same version of Modem/BL as your Firmware. For example if you have QK1 Stock ROM then you need to have QK1 Modem/Bootloader. On Custom ROMs doesn't matter. You can have any Modem/BL of your variant you want but recommend is always the latest.
1. Download the latest stock ROM (Firmware), Modem & Bootloader for your variant, TWRP Recovery (.tar file) and ODIN to your PC. [You can find everything in my Collection]
2. Install TWRP Recovery [Read the Install Custom Recovery Guide above]
3. Reboot to TWRP Recovery and Select Wipe > Advanced Wipe
4. Select Dalvik / ART Cache, System, Data, Cache, External SDCard (if you have) and then Swipe to Wipe.
5. Go back and select Wipe > Format Data > type yes [All your data into Internal Storage will be lost]
6. Reboot to Download Mode Power by pressing Power Button + Vol.Down + Home Button
7. Run Odin as adminstrator from your PC > connect your device > put the Stock Rom (Firmware) file to AP section and flash it!
8. Let the ROM boot.
9. Install the same version of Bootloader & Modem as your Firmware. [Read the Install Bootloader & Modem Guide above]
10. Enjoy!
BACKUP & RESTORE ROM (NANDROID BACKUP)
Check this Youtube Video to see the process in action.
Backup:
1. Reboot to Recovery (Power Button + Volume Up (+))
2. Choose Backup and Select Boot > System > Data (excl. storage)
3. Select Storage and choose SDcard if you have one otherwise let it on Internal Storage.
4. Swipe to Backup.
5. Done!
Restore:
1. Reboot to Recovery. (Power Button + Volume Up (+))
2. Select Wipe > Advanced Wipe.
3. Select Dalvik / ART Cache, System, Data, Cache and then Swipe to Wipe.
4. Press Home Button to go back and Select Restore.
5. Select the backup file with the ROM and make sure Boot, System and Data (excl. storage) are selected.
6. Select Swipe to Restore and when completed Reboot to System.
7. Done!
MAGISK ROOT
The easiest way to root your device is via Magisk, it should work in all ROMs, Stock and Customs.
Install Magisk:
1. Install latest TWRP Recovery. [Read the Install Custom Recovery Guide above]2. Download the Magisk [You can find it in my Collection]3. Reboot to TWRP Recovery by pressing Power Button + Volume Up (+) and flash it.4. Reboot and check whether the Magisk app is installed. If it isn’t installed automatically, manually install the APK. [You can find it in my Collection]Note#1: From Official TWRP Recovery 3.5.1 and onward (and other recoveries based on that), Magisk.apk can be flashed as apk without the need of rename it to .zip. So you can simply flash the Magisk.apk in TWRP.Manually Creation of Flashable Zip:Download the latest Magisk APK and rename the Magisk.apk → Magisk..zip.Note#2: If your bank apps detect root, follow this Guide.
Uninstall Magisk:
Flash the Uninstall.zip in TWRP Recovery and reboot. [You can find it my Collection]
If Magisk App isn’t uninstalled automatically, manually uninstall the app.
Manually creation of Flashable Uninstall Zip:
Download the latest Magisk APK and rename the Magisk.apk → uninstall.zip
Uninstall Magisk directly through the Magisk app. Simply press the Uninstall button.
Note: If your apps detect root, follow this Guide (or this) to pass SafetyNet and have certified Play Store. [YouTube Video Guide]
MIXER_PATHS (INCREASE VOLUME VALUES)
Check HERE and HERE.
HOW TO TAKE LOGS
How to take logs on Android
SCREEN RETENTION FIX
Screen Retention FIx: If you have an issue with screen retention apply this configuration to your device ROM.
BATTERY TIPS
Samsung Galaxy S4 Battery Model: B600BE
Battery Replacment (Video)
Advanced Guide
Simple Battery & Charging Tips
Improve your SOT
Battery Calibration
Method 1
Steps:
1. Discharge your phone fully until it turns itself off.
2. Turn it on again and let it turn itself off.
3. Plug your phone into a charger and, without turning it on, let it charge until the on-screen or LED indicator says 100 percent.
4. Turn your phone on. It's likely that the battery indicator won't say 100 percent, so plug the charger back in (leave your phone on) and continue charging until it says 100 percent on-screen as well.
5. Unplug your phone and restart it. If it doesn't say 100 percent, plug the charger back in until it says 100 percent on screen.
6. Repeat this cycle until it says 100 percent (or as close as you think it's going to get) when you start it up without it being plugged in.
Method 2
Notes: It won't dramatically extend battery life, but it will give your old battery at least 30 minutes additional run time.
Steps:
1. Get "GSam or Ampere" from the Google Play Store.
2. Launch the app and fully charge your phone. (Important: Only proceed with the calibration when the word "Full" appears in GSam or Ampere.)
3. While your phone is still connected to the cable reboot your phone to recovery mode, open file manager and navigate to "/data/system" and delete "batterystats.bin," "batterystats-checkin.bin," and "batterystats-daily.xml."
4. Reboot your phone (while it is still plugged in) and charge it until it reads "full" on GSam or Ampere.
5. Unplug the cable and use your phone normally until it shuts down (0 percent )
6. Charge your phone to 100% while it is turned off.
7. Boot into os and plug in your phone and charge it until it says "full" on the GSam or Ampere.
8. Unplug and have fun!
Battery Capacity Health
Notes:
1) Before checking the battery health, charge the device to 100%.
2) Check charge counter values and consider first 4 digits from left as your battery capacity in mAh. And check charge counter. (Charge counter/level)*100 is the battery capacity.
To find battery capacity in Windows:
Enable Developer options in your device.
Enable USB Debugging in your device.
Conect your device to PC and give permissions.
Open Minimal ADB (run cmd.exe) or Platform tools.
Type "adb shell dumpsys battery" command in Minimal ADB or Platform tools.
To find battery capacity in Android (Terminal) - Root needed:
Download an android terminal app like Termux,
Open terminal and type: cat/sys/class/power_supply/battery/charge_full
Overheating
Following reasons will lead to device heating issue:
During the initial setup after purchase or when restoring data.
Downloading large files.
Using apps that require more power or using apps for extended periods such as:
Playing high-quality games for long time.
Recording videos for extended periods.
Streaming videos while using the maximum brightness setting.
Using the Screen Mirroring / Smart View feature (connecting mobile to a TV).
While multitasking or when running many apps in the background i.e:
Using Multi window.
Updating or installing apps while recording videos.
Downloading large files during a video call.
Recording videos while using a navigation app.
Large amount of data for syncing with the cloud, email, or other accounts.
Exposing device under sunlight when temperature is high around you.
Extensive usage of mobile hotspot and tethering feature.
Using device in areas with weak signals or no reception or in roaming network.
Charging the battery with a damaged / unapproved USB cable.
Device's multipurpose jack is damaged or exposed to foreign materials, such as liquid, dust, metal powder, and pencil lead.
Solution:
Turn off Wi-fi, GPS , bluetooth and other connectivity options when not in use by dragging the notification panel.
Decrease screen brightness.
Close background running applications.
Too many applications installed in device may result in device heating since their corresponding process will keep on running in background. It is advised to uninstall un-necessary apps if not using them.
Avoid using apps like GPS, data dependent apps or graphic intensive games for longer duration since they require more energy to function, causing device to heat.
It is advised not to use device while charging as it may cause the device to over heat.
General:
DO:
Use manual brightness or dim the screen.
Turn off notifications for apps you don't use. Better still, delete/disable the apps entirely if you don't need them.
Enable battery or power saving mode when you want to extend your battery life.
Use the power adapter that came with your phone. Other chargers can charge slowly/faster but they can also damage your phone or battery.
Turn off bluetooth, location tracking, and Wi-Fi (unless you are actively using it)
Turn off print services from bluetooth connection preferences.
Avoid extremes of heat and cold. If your phone gets very hot or cold it can strain the battery and shorten it's lifespan.
DON'T:
Have Bluetooth or Wi-Fi turned on constantly.
Leave apps running in the background. Instead restrict background usage off apps that you don't need running.
Push email means your device is always listening for new email which drains alot of battery.
Drain your phone battery all the way to 0% or charging it all the way to 100%. Keep it between 20% - 90% for longer battery lifespan.
The more advanced the graphics and animations are (games, videos, photos, animations), the harder the processor and graphics chip in your smartphone have to work. More activity means more battery use.
PRIVACY & SECURITY
Some useful links:
All about Privacy & Security at Privacy Guides.
Electronic Frontier Foundation.
PrivacyTests: Open-source tests of web browsers privacy.
Check if your email address or your phone number is in a data breach at Have I been Pwned & at Firefox Monitor.
Test your browser to see how well you are protected from tracking and fingerprinting at Cover Your Tracks by EFF and at Bromite fingerprint mitigations tests.
WebRTC IP Leak Test. WebRTC is a new communication protocol that relies on JavaScript that can leak your actual IP address from behind your VPN. You can find more infos how to disable it at Privacy Guides in browsers section.
Ad Block Tester is a free service on the Internet to evaluate content blocking solutions. It is not designed to be a benchmark, but it reveals the level of blocking against a set of hosts that are very popular.
Check on AM I FLoCed? by EFF if your your Chrome browser has been turned into a guinea pig for Federated Learning of Cohorts or FLoC, Google’s latest targeted advertising experiment.
How to block ads on Android.
εxodus: εxodus analyzes Android applications in order to list the embedded trackers and ads.
Spyware Watchdog Article Catalog: A catalog which determinate under tests and tracking if an app is spyware and what data it collects.
CryptPad: CryptPad is built to enable collaboration. It synchronizes changes to documents in real time. Because all data is encrypted, the service and its administrators have no way of seeing the content being edited and stored.
PrivateBin: PrivateBin is a minimalist, open-source online pastebin where the server has zero knowledge of pasted data. Data is encrypted/decrypted in the browser using 256-bit AES. It is the improved version of ZeroBin.
ShutUP10++ , Privacy.Sexy: Disable major tracking features of Windows.
General:
Always prefer Open Source or well popular Programs, Apps, ROMs, Kernels & Stuff.
Open Source doesn't mean it's 100% safe but it's unlikely to have something suspicious, since you and other users can check the code in GitHub or in any other code hosting platform the "stuff" is hosted. You can also find and use FOSS apps at Droid-ify.
Prefer ROMs & Kernels with SELinux Enforcing. You can find informations here.
Always download and install Apps, Programs, ROMs & Stuff from official sources and do not use redirection links from different sites. Google is your friend to find the official source of the stuff you want.
Always check the permissions an app requires, before download and install it to your device. If an app ask for permissions which has nothing to do with the app functionality then it's should be reconsider or ask the developer why these permissions needed.
You can also check if the app includes trackers and ads with εxodus.
If you want to avoid Google and Play Store (De-Google), you can choose a ROM without GApps preinstalled like LineageOS and use Droid-ify client which is an installable catalogue of FOSS (Free and Open Source Software) applications for the Android platform. The client makes it easy to browse, install, and keep track of updates on your device. Note that not all apps from Play Store will be available in Droid-ify or F-Droid. Only Open Source projects. You can find alternatives though.
Alternative you can use LineageOS for microG or any ROM which support signature spoofing and can support microG and use Aurora Store.
For Windows use the default Windows Defender & Malwarebytes to scan your files whenever you want (Prefered before open or install them). Also use the addon/extension uBlock Origin in your Browser. These should be enough for normal users. You can also use the tool ShutUp10++ or Privacy.Sexy to disable major tracking features of Windows.
For Android Do not use any antivirus - antimalware since it's useless, just check what apps and from where you installing.
Always verify the source of addons/extensions in your browser. Avoid installing random and unpopular addons/extensions. Keep it minimal and clean, so browser can be fast and safe, no need bunch of extensions.
If you are using VPN, always check the terms and rules of the provider. Avoid random VPN Services.
Recommended VPN Services.
Using a VPN will not keep your browsing habits anonymous, nor will it add additional security to non-secure (HTTP) traffic.
Recommended is to encrypt your data/files always before uploading them to cloud with tools like Cryptomator.
Always use unique and strong passwords for each of your accounts.
Use awarded open source Password Managers like KeePass or KeePassXC for Desktop and KeePassDX for Android to manage your passwords and have them with you safe, encrypted and secure. Must be noted you can use the same database file between these programs.
Always enable 2 Step Authentication wherever is available for your accounts.
You can use apps like Aegis Authenticator.
Do not open or click on links attached in unknown emails or SMS you may get. Always check the address of the email or the number of SMS and verify it's legit from the official source.
Create and use "burned" email for accounts/sites you have concerns but you definitely want to try them. Do not use your personal or business email. You can also create and use email aliases of your email with SimpleLogin which is open source and awesome service.
DISCORD SERVER
Please verify yourself at #welcome channel. Read #FAQ channel.
Discord Server
Changelog
Note: Changes in Collection & Guides happens in real time. The date I post these Changelogs is just a sum up since I can't post all the changes the time that happening to avoid spamming the thread. So you can always consider the Collection & Guides Up-to-Date. However, I may announce some big changes in posts before I include them in the Changelogs.
LATEST
Update: 18/01/2023
Changelog
ARCHIVED
Update: 29/10/2022
Changelog
Update: 01/07/2022
Changelog
Update: 07/05/2022
Changelog
Update: 01/04/2022
Changelog
Update: 28/02/2022
Changelog
Update: 04/02/2022
Changelog
Update: 23/12/2021
Changelog
Update: 01/10/2021
Changelog
Update: 31/08/2021
Changelog
Update: 01/05/2021
Changelog
Update: 19/04/2021
Changelog
Update: 27/02/2021
Changelog
Update: 28/01/2021
Initial Release
Hi guys,
I can't manage to install the Bootloader & Modem via Odin on my phone.
Does the phone need to be already rooted in order to install the B&M?
Attached is also the capture I took when rebooting the phone in Download mode.
I selected "reboot to bootloader" in order to install the B&M, because otherwise Odin won't detect that the phone is connected to the PC. Probably I'm doing something wrong.
Any help will be very much appreciated.
Thanks in advance.
{
"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"
}
R_A_N_D_Y said:
Does the phone need to be already rooted in order to install the B&M?
Click to expand...
Click to collapse
I'n not 100% sure, but I think no
R_A_N_D_Y said:
Attached is also the capture I took when rebooting the phone in Download mode.
Click to expand...
Click to collapse
The picture shows your device in recovery
R_A_N_D_Y said:
I selected "reboot to bootloader"
Click to expand...
Click to collapse
How did you do that? I'm not aware of such a reboot option.
You should boot into download mode (see above for how to). It should look like attached picture 1
In Odin, before you start flashing, you should see a success message "<ID ... Added!! If not, you should check if you have all required driver installed for your device.
pocketrule said:
I'n not 100% sure, but I think no
The picture shows your device in recovery
How did you do that? I'm not aware of such a reboot option.
You should boot into download mode (see above for how to). It should look like attached picture 1
In Odin, before you start flashing, you should see a success message "<ID ... Added!! If not, you should check if you have all required driver installed for your device.
View attachment 5212215View attachment 5212217
Click to expand...
Click to collapse
Thank you very much !
R_A_N_D_Y said:
Hi guys,
I can't manage to install the Bootloader & Modem via Odin on my phone.
Does the phone need to be already rooted in order to install the B&M?
Attached is also the capture I took when rebooting the phone in Download mode.
I selected "reboot to bootloader" in order to install the B&M, because otherwise Odin won't detect that the phone is connected to the PC. Probably I'm doing something wrong.
Any help will be very much appreciated.
Thanks in advance.
Click to expand...
Click to collapse
No need root.
Download and install the Samsung USB Drivers in your PC. (You can find it in my collection)
Download the Combined Bootloader & Modem for your variant from my collection.
Turn off your device.
Reboot your device to Download Mode by pressing Power Button + Vol.down + Home Button and run Odin from your PC as administrator.
Put the COMBINED BOOTLOADER_MODEM.tar to AP section, untick Auto-Reboot in options and flash!
When It's done, reboot your device by pressing Power Button for couple of seconds.
New Update:
Changelog:
Added Changelog Tracking at #3 post
Added Privacy & Security section in Guides.
Added a Note to check Privacy & Security Guide at Useful Apps section in Collection.
Added Flashable Zips for Install & Uninstall Magisk in Collection.
Updated the Magisk Guide and added Flashable Zip method.
Reordered the sections in Guides.
Hi Retrial, first of all this is a really useful post thank you so much!
I just bought a brand new S4 GT-I9505 and I used the latest TWRP in your post wich is twrp-3.5.1_9-0-jflte.img.tar for flashing lineage-17.1-20210116-UNOFFICIAL-jflte.zip and I have some question if you are so kind to aswer me:
I want to update the firmware so I downloaded the last one for Italy from Updato.com which is I9505XXUHPK2 (Genuary 2017) and I would like to know if is a good idea to flash it with Odin and if I have to fresh re-installing Lineage. Then I would like to know if after updating the firmware I can update only XXUHQC1_BOOTLOADER and XXUHQC1_COMBINED which are the international versions and obviously the most recent versions.
Do you think is possible? Thanks in advance. Kind Regards
hermes127 said:
Hi Retrial, first of all this is a really useful post thank you so much!
I just bought a brand new S4 GT-I9505 and I used the latest TWRP in your post wich is twrp-3.5.1_9-0-jflte.img.tar for flashing lineage-17.1-20210116-UNOFFICIAL-jflte.zip and I have some question if you are so kind to aswer me:
I want to update the firmware so I downloaded the last one for Italy from Updato.com which is I9505XXUHPK2 (Genuary 2017) and I would like to know if is a good idea to flash it with Odin and if I have to fresh re-installing Lineage. Then I would like to know if after updating the firmware I can update only XXUHQC1_BOOTLOADER and XXUHQC1_COMBINED which are the international versions and obviously the most recent versions.
Do you think is possible? Thanks in advance. Kind Regards
Click to expand...
Click to collapse
Hello,
If you flash firmware u need to reflash lineageos from start along with twrp. U can only do it via Odin.
Btw use the latest for your variant from my collection. Doesn't matter the country.
Flashing firmware=flashing stock rom. Why u want to do that if u are already in los?
You can flash bootloader and modem seperate yes (but I recommend to use my combined .tar which include both of them), without the need to flash everything again. Just go to Odin and flash the combined .tar I have made to AP. Once again, all the latest versions are included in my collection, doesn't matter the country so just use them.
All the infos and steps you need are in my collection and guides. Let me know if you have more questions.
Retrial said:
Flashing firmware=flashing stock rom. Why u want to do that if u are already in los?
Click to expand...
Click to collapse
Hi thanks for your fast response! I want to flash an updated firmware because my S4 GT-I9505 is new and probably from an old stock so the firmware is for sure the old one (2013-2014) ,right now in lineage os in setting/info I can't see the current version of baseband. I don't care if I have to re-install Lineage and the recovery, I had to do it before installing Lineage, I know I forgot it... but I wanted just to know if is possible to do now without breaking something. Now you say that it doesn't make sense and that is better to just flash your combined Modem and Bottloader package, is it correct? What's your advice: installing your last complete firmware or just the combined Bootloader and Modem package? I red somewhere in this forum that it's better to update the firmware before installing lineage so I wanted to do the installation again in the right way. Sorry if it's an annoying question I'm not an expert and I want just to be sure. Thank you so much for your support.
hermes127 said:
Hi thanks for your fast response! I want to flash an updated firmware because my S4 GT-I9505 is new and probably from an old stock so the firmware is for sure the old one (2013-2014) ,right now in lineage os in setting/info I can't see the current version of baseband. I don't care if I have to re-install Lineage and the recovery, I had to do it before installing Lineage, I know I forgot it... but I wanted just to know if is possible to do now without breaking something. Now you say that it doesn't make sense and that is better to just flash your combined Modem and Bottloader package, is it correct? What's your advice: installing your last complete firmware or just the combined Bootloader and Modem package? I red somewhere in this forum that it's better to update the firmware before installing lineage so I wanted to do the installation again in the right way. Sorry if it's an annoying question I'm not an expert and I want just to be sure. Thank you so much for your support.
Click to expand...
Click to collapse
Just follow what Retrial said; flashing his combo-file will accomplish what you want. Starting from scratch like you wanna do isn't any better.
I flashed bootloaders and modems so often, I can't even remember. Flashing stock firmware? Maybe once!
hermes127 said:
Hi thanks for your fast response! I want to flash an updated firmware because my S4 GT-I9505 is new and probably from an old stock so the firmware is for sure the old one (2013-2014) ,right now in lineage os in setting/info I can't see the current version of baseband. I don't care if I have to re-install Lineage and the recovery, I had to do it before installing Lineage, I know I forgot it... but I wanted just to know if is possible to do now without breaking something. Now you say that it doesn't make sense and that is better to just flash your combined Modem and Bottloader package, is it correct? What's your advice: installing your last complete firmware or just the combined Bootloader and Modem package? I red somewhere in this forum that it's better to update the firmware before installing lineage so I wanted to do the installation again in the right way. Sorry if it's an annoying question I'm not an expert and I want just to be sure. Thank you so much for your support.
Click to expand...
Click to collapse
Firmware=Stock Samsung ROM. Firmware does not include Modem & Bootloader. So even if u flash Firmware u have to also flash Bootloader & Modem.
Now you say that u are on lineageos, I don't know what version you are but you can flash via Odin the combined .tar file which include Bootloader & Modem and then clean install via TWRP the latest LineageOS along with latest GApps if you use.
If you want to start from scratch-fresh then follow my Guides: "Clean Install Official Stock ROM" and then the guide "Clean Install Custom ROM".
With few words: go to TWRP wipe everything, the connect ur device to PC and flash via Odin the latest Firmware (stock ROM). Let it boot and then flash via Odin the latest Bootloader & Modem. Then flash TWRP and clean install the latest LineageOS with GApps (optional).
Everything you need is on my collection and all steps in my guides. Since u have i9505 variant you need the latest Firmware/Modem & Bootloader which is I9505XXUHQK1.
Let me know how it goes or if you have any other questions.
Retrial said:
Flashing firmware=flashing stock rom. Why u want to do that if u are already in los?
Click to expand...
Click to collapse
Retrial said:
Firmware=Stock Samsung ROM. Firmware does not include Modem & Bootloader. So even if u flash Firmware u have to also flash Bootloader & Modem.
Now you say that u are on lineageos, I don't know what version you are but you can flash via Odin the combined .tar file which include Bootloader & Modem and then clean install via TWRP the latest LineageOS along with latest GApps if you use.
If you want to start from scratch-fresh then follow my Guides: "Clean Install Official Stock ROM" and then the guide "Clean Install Custom ROM".
With few words: go to TWRP wipe everything, the connect ur device to PC and flash via Odin the latest Firmware (stock ROM). Let it boot and then flash via Odin the latest Bootloader & Modem. Then flash TWRP and clean install the latest LineageOS with GApps (optional).
Everything you need is on my collection and all steps in my guides. Since u have i9505 variant you need the latest Firmware/Modem & Bootloader which is I9505XXUHQK1.
Let me know how it goes or if you have any other questions.
Click to expand...
Click to collapse
Wow your instructions are absolutely detailed and useful, thank you so much Retrial for your support.! I'll opt for the "start from scratch-fresh" install by following your guides. If I can take advantage of your competence I would like to ask you just one last advice: I switched to Lineage OS for privacy reasons (I don't like google so I don't need GApps) and I also use it for sharing internet to my MacBook Pro with USB tethering (not wifi tethering which is not safe for privacy) so do you think that the Optimized Lineage OS (Android 10) version from JDCTeam is the right version for me? May I use the Android 11 version? Probably I'm asking you to much things and I can understand if you can't answer me, you have been really kind and I really appreciated your help. Anyway I'll post here my experience with "start from scratch-fresh instal" .
Anything for the AT&T S4 Active (+) variant?
hermes127 said:
Wow your instructions are absolutely detailed and useful, thank you so much Retrial for your support.! I'll opt for the "start from scratch-fresh" install by following your guides. If I can take advantage of your competence I would like to ask you just one last advice: I switched to Lineage OS for privacy reasons (I don't like google so I don't need GApps) and I also use it for sharing internet to my MacBook Pro with USB tethering (not wifi tethering which is not safe for privacy) so do you think that the Optimized Lineage OS (Android 10) version from JDCTeam is the right version for me? May I use the Android 11 version? Probably I'm asking you to much things and I can understand if you can't answer me, you have been really kind and I really appreciated your help. Anyway I'll post here my experience with "start from scratch-fresh instal" .
Click to expand...
Click to collapse
Don't worry mate, ask whatever you want. I will help if I can.
Optimized LineageOS 10 is great but it's EOL (end of life). Optimized LineageOS 11 is also great and it's currently under development.
But since you are looking for privacy & security it's better to use Official LOS with guarantee monthly security patches cause lately optimized los stays a bit behind on updates. (Dev is busy) Soon official 11 will also be released.
blackhawk said:
Anything for the AT&T S4 Active (+) variant?
Click to expand...
Click to collapse
I think ur variant has locked bootloader so I don't know if anything exist.
Retrial said:
I think ur variant has locked bootloader so I don't know if anything exist.
Click to expand...
Click to collapse
Thank you. If you become aware of any work arounds please let me know.
It's a phone that is expendable now
blackhawk said:
Thank you. If you become aware of any work arounds please let me know.
It's a phone that is expendable now
Click to expand...
Click to collapse
I know there is a workound for S4 AT&T on specific firmware with locki patched TWRP but I don't think it's exist anything for ur S4 active at&t. I will let u know if I find anything.
Retrial said:
Don't worry mate, ask whatever you want. I will help if I can.
Optimized LineageOS 10 is great but it's EOL (end of life). Optimized LineageOS 11 is also great and it's currently under development.
But since you are looking for privacy & security it's better to use Official LOS with guarantee monthly security patches cause lately optimized los stays a bit behind on updates. (Dev is busy) Soon official 11 will also be released.
Click to expand...
Click to collapse
Ok thank you, I'll follow your advice.