Hello partners!!!
Here we share the functional rom last for our MaX2!
At the request of many colleagues, I created this CM13 based on 29 September.
And adding the entire S19 firmware to have it fully updated and upgraded.
Fully functional quick and steady myself I was surprised with the performance tests ... 143,000 AnTuTu with hot enough to test mobile Cold believe can draw record numbers ...
To say that I still have problems with slow motion ....
I'm starting to not know where mistakes can be ....
Libs I managed to trace the entire structure of the official EUI and still does not work ....
Permits revised from top to bottom ...
Libs mother and CM13 ... zilch ...
Perhaps there may be something in the kernel (boot) but there are limited ...
As I change anything to do directly test the ROM does not start or comes into infinite loops ....
So ... I leave the rom completely finished but with 2 bugs.
And each user knows what he wants or what you need.
But the ROM is fully functional for day to day and is really fast and stable.
BUGS:
1 Slowmotion nonfunctional. The rest of the camera is fully functional with 21mpxl.
2nd nonfunctional IRDA. (With this ... if not roms stocks moment ... little we can do ...)
The first!!!! IMPORTANT
We do not force anyone has use or install the rom.
We do not make yourself responsible for possible errors or brik the terminal.
We simply share our work for all so that we can have the terminal in our language.
RoM CM13
CM13 based official of the day 29/09/2016
s19 official firmware with all its libs + kernel.
Rom eliminated completely stock only apks that created conflict with our terminal.
Doze functional.
Sound perfect.
wiffi
BT
Integrated Pico gapps
Some improvements in the build.prop
Installation Method
We have created a zip FULL.
ROM contains firmware s19 + recovery + 5.8 everything necessary for you to come firmware do not have problems to come and stay all properly installed and running smoothly or silly scares.
* Download rom.
* Enter the zip rom on your terminal.
* Restart recovery.
* Since the recovery to the wipes.
* Once the wipes, select the zip and install.
* Once installation is complete, restart System.
* Wait for the rom you first start, it takes a few minutes not alarmed.
downloads TeaMSpaiN
CM13 ROM S19: https://mega.nz/#!SwIHSB7C!rFQJsQxx-J-RI121GWsaC6DAhDkLHzJdDPvdVabZRRY
Your comments on this rom.
And if you find any bug report to try to fix them.
Greetings comrades!
DONATE PAYPAL: https://www.paypal.me/ParasiteYgaseOso
thanks for sharing this
Sent from my Le X821 using XDA-Developers mobile app
Thank you! I will try this rom.
Changing action of the left hardware button doesnt work, it just keeps working as "menu" button.
ArctiX said:
Changing action of the left hardware button doesnt work, it just keeps working as "menu" button.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=68885350&postcount=235
meangreenie said:
http://forum.xda-developers.com/showpost.php?p=68885350&postcount=235
Click to expand...
Click to collapse
Thanks, that worked
Thanks for your work! Does Camera API 2 work this time?
I flashed this rom today. Everything works well for me!
wiped system and dirty flashed from previous cm13 and it seems to be running very well
Nice, smooth, we will see battery performance compared to Mokee.
- Camera2 api doesnt work
- Slowmotion doesnt work
- IR doesnt work
- For me, missing Aegis app from Mokee is a big step back
Sent from my Le X820 using Tapatalk
@ParasiTe_RemiX Did you build this from source or port from another device?
Beautiful ROM, but for me in Japan for some reason LTE is not working, I can get only HSPA. This is strange because in the stock eui I can use LTE no problem.
Also the hardware buttons light up when you touch the screen, on Eui they only lit up when you touched the buttons, not the screen.
Oh, and after checking now, the AudioFX doesn't work system wide, only in the cm music app, in e.g. YouTube or Tidal, it doesn't make any change in sound.
Notification light is blinking when charging, is there any way to make it always on and not blinking?
ArctiX said:
Also the hardware buttons light up when you touch the screen, on Eui they only lit up when you touched the buttons, not the screen.
Oh, and after checking now, the AudioFX doesn't work system wide, only in the cm music app, in e.g. YouTube or Tidal, it doesn't make any change in sound.
Notification light is blinking when charging, is there any way to make it always on and not blinking?
Click to expand...
Click to collapse
For the hardware buttons backlight, you can turn them off in settings/buttons or you can turn the brightness of them right down, via editing the max_brightness file.(can't remember the path name atm, but can easily google)
For the charging light, you can turn the charging light off in settings/display. The options for them don't seem to work unfortunately.
When I plugged my phone to the computer I noticed a blank file with no name and hard disk icon on my sd card, when I tried to delete it, it wiped my whole sd card! don't delete that file if you see it.
Hello, This ROM is also compatible with the version Le Max 2 Pro?
pickmod said:
Hello, This ROM is also compatible with the version Le Max 2 Pro?
Click to expand...
Click to collapse
No, you can't flash it for X620!
bahuy2003 said:
No, you can't flash it for X620!
Click to expand...
Click to collapse
I have Le Max 2 Pro X820... it is compatible?
Thank you, looks really production quality
This is extremely close to what I wanted from this device: Straighforward CM13 (ok, I'll want CM14 next), no bloat, functional and fast.
Also rooted, which means I control my device, not some vendor who wanted my money but fails to cede the control over what he sold.
And most importantly: No longer any of these Chinese apps, which refused to get uninstalled while they claimed about any privilege Android can provide.
I sure hope security patches will be coming for years as the device looks powerful enough to last a long time.
Only bug I've found so far is apps like Hangouts and Duo can't access the Camera for video calls. Apart from that, flawless so far.
Liquid Remix is an android 8.1 project from the old lead of Liquid smooth and XDA dev Dabug123! Liquid Remix is a new age mix of all the best ROMs out today with an added flavor from the old smooth days. All features are open source and will always stay that way as the community is the most important thing to our project! We aren't here for donations or thanks just want to bring a nice smooth ROM to our One Plus 5! Hope you guys enjoy.
Downloads
http://pizzaking.aosiprom.com/liquid5t/
Features
Liquid Lounge
VOLTE
Buttons
Volume rocker
Volume key answer
Volume up in do not disturb
Swap volume rocker orientation
Playback control
Volume keys control media volume
Volume key cursor control
Volume rocker wake
Enable hardware keys
Hardware keys rebinding
Long press button actions
Gestures
Double tap to sleep
Pocket detection
Three finger detection
Screen off power button torch
Lock screen
Lock screen shortcuts
Lock screen weather
Media cover art
Lock screen charging info
Fingerprint authentication vibration
Miscellaneous
Alarm blocker
Wakelock blocker
App ops
MTP instead charging
Wake up on charging
Show CPU info
Navigation bar
DUI
Navbar buttons
Enable soft keys
Notifications
Heads up
Battery lights
Notifications light
Toast app icon
In call vibration options
Power menu
Power menu when locked
Power
Restart
Advanced restart
Screenshot
Screen record
Flashlight
Airplane
Settings
Lock down
Users
Sound panel
Quick settings
Brightness slider
Brightness icon
No quick settings when secured
Quick pull down
Smart pull down
Dark system UI style
Custom header image
Recents panels
Clear all button
Clear all location
Immersive recents
Hidden apps
Status bar
Status bar items
Brightness control
Selector notification
Warning color
ADB notification
Network traffic
Liquid logo
Notification ticker
Settings
One plus buttons
Swap recents with back button
Notification slider
One plus gestures
Camera
Music
Flashlight
Extras -> Haptic feedback
Security
Screen pinning
Apps with usage access
Sound
Media,alarm,ring volume
Volume steps
Do not disturb preferences
Ringtone sounds
Other sounds and vibrations
Display
Tap to wake
Device theme
Quick settings options
Columns
Columns landscape
Rows
Quick bar scroll
Show labels
Brightness slider in footer
Quick settings tiles
ADB network
Caffeine
Heads up
LTE
NFC
PiP
Screen record
Screenshot
Reboot
Sound
Weather
Flashing Instructions
Encrpyted now works!!!!
If you are on oos : wipe everything, format data, flash rom, gapps, super su or magisk (+no verity zip).
If you are on custom N/O rom (decrypted) : wipe everything ( no need for storage), flash rom, gapps , super su or magisk (+no verity zip).
For update: wipe cache/dalvik, flash rom,gapps, super su or magisk (+no verity zip), what you flashed first time.
For twrp use blu twrp or any other.
For gapps : open gapps or beans.
Community
https://plus.google.com/u/0/communities/115990749843435030575
Telegram
https://t.me/joinchat/CjMSiBC3tuKoC8ETEZBH5Q
Thanks
DirtyUnicorns
GZOSP
Abc roms
Nitrogen
Lineage
Omni(Without max headers would never come alive!)
Jayrod for graphics
Aicp
FrankenFlashRemix Dabug123 and special thanks Nathan for great base
Anyone else i forgot let me Know
XDA:DevDB Information
Liquid Remix, ROM for the OnePlus 5T
Contributors
dabug123, liquid0624
Source Code: https://github.com/LiquidRemix
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
Based On: lineage and aosp
Version Information
Status: Stable
Current Stable Version: 9.0.6
Stable Release Date: 2017-12-23
Created 2017-12-24
Last Updated 2018-02-17
download links and other links in pages being edited
for those who want fiingerprint gestures working!
go to my post here;
https://forum.xda-developers.com/showpost.php?p=74947961&postcount=58
press thanks if I helped
Great to see it release this ROM is rock solid and so fast.
Abaddon said:
It's here! Thanks man! So test2 is the latest right? Or another to come?
Click to expand...
Click to collapse
liquid_remix-8..5-20171224-OFFICIAL-dumpling.zip is the latest.
offical build but test2 is nice too....Ill clear out the folder shortly so wont be confusing
Thanks for getting this to official status.
Beware that flashing this if you're not completely decrypted will wipe your internal storage upon first boot (because this runs as decrypted).
Just a heads up for most part rom runs amazing 99% everything is good ,minor things to work on at this point..Thanks to all the testers and public telegram chat that have flashed all our crazy builds to get to where we are today.IF HAVE AN ISSUE PLEASE PROVIDE LOGS!!!
Had a process.core error upon first boot and would't detect my SIM, rebooted and it works fine.
Camera seems to crash whenever you're in the front camera mode, and select the filter icon (not sure what its called), and slide up and back down.
Instagram crashed also on a story, but might be instagram fault.
Is there any way to enable Face Unlock? if not, it should be noted on the main post I'm guessing?
Thanks for the effort!, Will be running this tomorrow and report back.
Great to see this @dabug123. OnePlus apps......this includes the stock camera along with other stock apps?? Does the camera use same protocols as in stock ron like EIS, portrait mode, etc? Decrypted.,...other process needed prior to flashing the rom? If so where would I get this? Sorry for all the q's man. Never had a device that could root so easily and run stock apps with aosp based ROMs. Thanks again!!
Akutsito said:
Had a process.core error upon first boot and would't detect my SIM, rebooted and it works fine.
Camera seems to crash whenever you're in the front camera mode, and select the filter icon (not sure what its called), and slide up and back down.
Instagram crashed also on a story, but might be instagram fault.
Is there any way to enable Face Unlock? if not, it should be noted on the main post I'm guessing?
Thanks for the effort!, Will be running this tomorrow and report back.
Click to expand...
Click to collapse
If u had acore crash then u weren't decrypted which it says in OP.
where to we get the no verity.zip?
fracman said:
where to we get the no verity.zip?
Click to expand...
Click to collapse
https://drive.google.com/file/d/0B0pr-ZA5b-1pWHp5aDkzaC1ydUk/view
this!
5t ok!
All set up. Live the blue. Was on Omni. But this ROM flies in comparison. And smooth. Thank u dev.
Thanks again for your great work dabug123.
I loved your rom and kernel for the oneplus 3 also and great to see you here working on the 5t.
Stupid question, is it not possible to make the rom running also on encrypted devices? I already lose twice my internal storage with backups lol. It's Just a question
Keep up the great work.
Best regards,
ysco..
Navigation bar→off
expended desktop→on
At this time, some applications will have space below. Is there a way to eliminate this space?
What happens if I don't flash the no_verify.zip, I read here that it will wipe the storage, does that mean the whole 128 GB or just the data partation, also should I flash the no verify zip evey time I switch to a new ROM, Kernel etc.
Trying to flash this one: liquid_remix-8..5-20171224-OFFICIAL-dumpling
But unable to boot device, had wipe everything, using the TWRP 3.2.1 (or lates) Tried with GAPPS and just the ROM, anybody else?
Br. Otto
otto_di2 said:
Trying to flash this one: liquid_remix-8..5-20171224-OFFICIAL-dumpling
But unable to boot device, had wipe everything, using the TWRP 3.2.1 (or lates) Tried with GAPPS and just the ROM, anybody else?
Br. Otto
Click to expand...
Click to collapse
Rom works fine u must be unencrypted
So I flashed an12/18 build that was listed on lineageosroms the other day and ran into a couple issues at first but worked around them.
I tried subsequently flashing the 12/22 build and it failed to boot, so I went back to the 12/18 build. 12/18 worked while encrypted with no issues.
You have to start with a clean wipe coming from OOS.
Remember this is AOSP 8.0, so don't flash any of the OOS kernels.
ROM won't detect SIM card on first boot most likely, but should after reboot.
Casting and Google cloud print didn't work for me.
Great, its official now.
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community
Requirements:
- oreo bootloader
- twrp 3.2.0+
- backup everything before install
- wipe data before upgrading from LineageOS 14.1 or stock rom
Install:
- Flash zip in TWRP
- Don't forget about gapps (arm64 8.1)
- Root not included. Flash magisk before first start.
Google apps should be installed via recovery immediately after installing ROM.
If you reboot into ROM before installing Google apps, you must factory reset and then install them, otherwise expect crashes.
Not working:
gps
bt audio
stuff, I haven't checked
I broke my tablet. There are no more updates here further.
Download:
T820: https://drive.google.com/open?id=1ql4VIjTsSHNwzsoJm3Yb8wt0RW9OJerE
Device initial config sources:
https://github.com/bonuzzz
I was about to sell tablet...and get pixil c. Tablet is extremely laggy on stock Oreo. Switched back to your lineage 14.1 build which runs well but realized it was no longer supported. Very happy with your work! Thanks!
I'll give it a go when I get home. Thanks for supporting our device!
I did switch off WiFi upon initial setup, didn't seem to be liking 5g. After setup I switched to 5g WiFi but it kept showing no internet. My other devices don't have this problem. Not a big deal, just giving a heads up. I switched to 2g WiFi and all is well. Wayyyy smoother than stock Oreo. Didn't test gps, I know you said it wasn't working. I don't use GPS on my tablet so no loss there. Thanks again!
For gapps it shows "arm 8.1" it should be "arm64 8.1"
Edit: 5g seems to be working fine after a resetting WiFi, mobile & Bluetooth. Still can't seem to get audio playing through Bluetooth even though it's connected.
Cool! I will be installing this shortly. I was going to switch the the tweaked stock Oreo but will much rather use Lineage since I prefer more of a "vanilla Android" over Samsung's version.
P.S. I recently got myself a pixelbook for chromeos+android+linux and I find myself using that way more than my tab s3. If you need anyone to test something that doesn't really care about stability, let me know!
Edit:
Just wanted to let people know of what I've initially noticed and tested.
* Not laggy like stock is
* Able to format sd card for internal storage
* Official Keyboard case works (didn't use much before)
- show/hide key for virtual keyboard and Lang key don't do anything (at least it appears that way)
- Left 'alt' brings up emoji, right 'alt' brings up symbols on virtual keyboard.
* Auto wake/sleep works with 3rd party case (assume all work since it's just a magnet)
* Auto brightness works but I tested it with a flash light.
I liked the 14.1 version and I seem to like this version as well. It is to early to say more, but why can't you share this with lineage? It would be a dream, if this would be official and we would recieve updates. And maybe they will help you with the missing GPS?
Thanks so much for this. I've been wanting to get an Oreo ROM like this for my S3
EDIT: Is there any chance you could just give a dump of your terminal session of the build? I had started to try & build 15.1 for the S3 WiFi, based on your work for the LTE version, but wasn't having any luck. I'm hoping that if you could provide a terminal dump, it could help me work through my issues to get the build working as well. Would appreciate it =]
Regardless, thanks for taking the time to build this for us WiFi owners! =D
Finally, T820! Have been waiting for this for months now. Gonna give this ROM a try ASAP :laugh:
Thank you so much for this! Testing this weekend.
PuDLeZ said:
Just wanted to let people know of what I've initially noticed and tested.
* Not laggy like stock is
* Able to format sd card for internal storage
* Official Keyboard case works (didn't use much before)
- show/hide key for virtual keyboard and Lang key don't do anything (at least it appears that way)
- Left 'alt' brings up emoji, right 'alt' brings up symbols on virtual keyboard.
* Auto wake/sleep works with 3rd party case (assume all work since it's just a magnet)
* Auto brightness works but I tested it with a flash light.
Click to expand...
Click to collapse
Did you test the spen by any chance?
VVombat said:
Thank you so much for this! Testing this weekend.
Did you test the spen by any chance?
Click to expand...
Click to collapse
I didn't have software installed that I could use it in but I did put it to the home screen and got the circle indicator of where the tip is so it registers. Of course, there was no Samsung menu... Anything specific you want me to try this evening?
PuDLeZ said:
I didn't have software installed that I could use it in but I did put it to the home screen and got the circle indicator of where the tip is so it registers. Of course, there was no Samsung menu... Anything specific you want me to try this evening?
Click to expand...
Click to collapse
Mhm I'm using mainly Squid and Xodo to annotate and notate stuff. If you have them laying around anyways that would be nice, but if not no need to install and waste your time if I'll install tomorrow anyways. Thank you for your answer!
lineage-15.1-20180614-UNOFFICIAL-gts3lwifi doesn't work for me, bootloops, tried almost everything, etc.
RESOLVED: See below how and why.
Good afternoon. Everything works fine, the stylus in all orientations, the AnTuTu test runs fine and there is no understating of indicators on both stock, Wi-Fi is excellent, both 2.4 GHz and 5 GHz.
There are only 2 inconveniences
- Stereo sound from speakers is only in portrait orientation, and landscape channels do not change. Can you make a patch or fix yourself, you can not even change the channels when you turn, but only make a stereo Sound in landscape orientation (videos and movies often look into it);
- No sound goes to the Bluetooth headphones.
In any case, the firmware is super, thank you very much for the work done.
Hello, how to get Bluetooth working? I connect but no sound
Thank you also
Another problem, the sound slows down and stutters in applications (heavy or simple games)
JWnSC said:
For gapps it shows "arm 8.1" it should be "arm64 8.1"
Edit: 5g seems to be working fine after a resetting WiFi, mobile & Bluetooth. Still can't seem to get audio playing through Bluetooth even though it's connected.
Click to expand...
Click to collapse
edited, thanks
yes, bt audio doesn't work. seems I broke it in last moment...
PuDLeZ said:
Just wanted to let people know of what I've initially noticed and tested.
* Not laggy like stock is
* Able to format sd card for internal storage
* Official Keyboard case works (didn't use much before)
- show/hide key for virtual keyboard and Lang key don't do anything (at least it appears that way)
- Left 'alt' brings up emoji, right 'alt' brings up symbols on virtual keyboard.
* Auto wake/sleep works with 3rd party case (assume all work since it's just a magnet)
* Auto brightness works but I tested it with a flash light.
Click to expand...
Click to collapse
I have official keyboard case too. Unfortunately it's almost unusable in aosp if you need more than one keylayout. What about special keys, aosp doesn't have that triggers what stock rom has. I only could advice 3rd party app, but paid https://forum.xda-developers.com/showthread.php?t=1541916
HardWorker79 said:
I liked the 14.1 version and I seem to like this version as well. It is to early to say more, but why can't you share this with lineage? It would be a dream, if this would be official and we would recieve updates. And maybe they will help you with the missing GPS?
Click to expand...
Click to collapse
Nothing will change with official status except It would create more troubles and bureaucracy there.
Nobody will help. Believe me.
Comses said:
Good afternoon. Everything works fine, the stylus in all orientations, the AnTuTu test runs fine and there is no understating of indicators on both stock, Wi-Fi is excellent, both 2.4 GHz and 5 GHz.
There are only 2 inconveniences
- Stereo sound from speakers is only in portrait orientation, and landscape channels do not change. Can you make a patch or fix yourself, you can not even change the channels when you turn, but only make a stereo Sound in landscape orientation (videos and movies often look into it);
- No sound goes to the Bluetooth headphones.
In any case, the firmware is super, thank you very much for the work done.
Click to expand...
Click to collapse
I have an issue somewhere in audio behavior. Will check it deeper.
Comses said:
Another problem, the sound slows down and stutters in applications (heavy or simple games)
Click to expand...
Click to collapse
in games only? I've not noticed anything in videos.
samsuffit said:
Doesn't work for me.
What I did from Lineage 14.1:
- Upgraded TWRP to v3.2.1.1
- Wiped eveything
- Downloaded BRE2 firmware for my country
- Extracted BL....tar.md5 and flashed it with Odin v3.13.1
- Rebooted in recovery mode to be sure of... still don't know what
- Flashed Lineage 15.1
Then I could see the logo animation until the end, just before the system starts, then 3 boot loops and it went to recovery mode
I repeated the exact same sequence and flashed SuperSU v2.82-SR5, same result.
So...:
- Wipe everything
- Flash BL, CSC and CSC_HOME (no need of AP, system partition) with Odin
- Format/Erase Data
- Flash Lineage 15.1
Again a boot loop, this time without going back automaticaly to recovery mode.
Tried with SuperSU, boot loop...
So... This time I flashed eveything, reboot with Samsung Android, test a little bit, then:
- Flash TWRP v3.2.1.1
- Immediatly reboot to recovery mode
- Format/Erase Data
- Wipe everything
- Flash Lineage 15.1
Boot loop...
Tried with SuperSU, boot loop...
I was able to restore a full backup of my previous Lineage 14.1 installation.
What did I do wrong and which kind of logs do you need to help me to understand?
Thank you and thank you to have integrated S-Pen support, I love this thing. I don't realy need GPS.
Edit: in case it was mandatory I tried with Magisk v16.0 and v16.4 instead of SuperSU. Same boot loop.
If it's because I didn't flash the GAPPS, well... nevermind... I'll wait for something else.
Click to expand...
Click to collapse
Magisk is needed for device certification in Play store. That's because it should be flashed with gapps before first boot. So, rom works without gapps and root well.
For what region you downloaded oreo stock rom? I doubt but maybe samsung has different logic in bootloader for relocatable kernel stuff. It's strange how you restored lineage nougat, because that kernel shouldn't work with oreo bootloader.
edit: i'm wrong about bootloader and nougat, because I use now old twrp with nougat kernel.
Flashed old build. Have audio in bt, but don't have speaker rotation. I was sure it worked before...
If someone used or uses lineageos 14.1, is speaker rotation work there or not?
Hello @bonuzzz, thank you for the reply.
I was able to restore my Lineage 14.1 because I flashed the ARA2 boot loader (tried with Odin the first time, then with my TWRP backup, same result)
bonuzzz said:
If someone used or uses lineageos 14.1, is speaker rotation work there or not?
Click to expand...
Click to collapse
Only with VLC. Stuck in portrait mode with stock player. I don't have any games...
The last thing I need to try is installing the GAPPS... Like I said, I don't want to, so if the problem comes from this, I'll pass. But I have to try to be sure...
In this order from TWRP:
- Flash BRE2 boot loader
- Format Data and wipe everything
- Flash Lineage 15.1
- Flash openGAPPS nano arm64 8.1
- Flash Magisk 16.4
And... It's working...
Well...
I want to cry...
So the GAPPS are mandatory.
Thank you for creating a new os for sm-t820.
BT audio is working for me with Sony mdr zx220bt headphones
PixelPie 1.0 -By Team Pixel
Hey Everyone!PixelPie is a custom firmware that ports almost all of the features from a Pixel Device to a Samsung Firmware. This build has been based on the Pixel 3XL. It has been very deeply debloated and optimized for performance, whilst also bringing in many Pixel Features to our devices. It has also undergone a beta test ring, so most if not all of the listed features should be working! Here is a feature list:
Features:
1. AdAway
2. Google Calculator
3. Google Calendar
4. GCam arnova
5. Samsung Stock Camera with Massive HDR parameter changes, while also debloated
6. Google Chrome
6.1. rom works fast
7. Google Clock
8. Google Contacts
9. Google Files GO (File Manager)
10. Samsung Gallery (Stripped Down and lightened to improve performance)
11. GPay (Working Payment Method along with NFC functionality)
12. Google Keep (With Handwriting Libs)
13. Google Lens (Bixby Visions Alternative but works within Google Photos and Pixel Recents)
14. Magisk 19.0 Prebuilt (No Need For Seperate Flash)
15. Google Messages
16. Mtweaks 14.0 (Has GPU Control)
17. Eleven Music (Lineage OS 15.1)
18. Google Phone (Ported Framework for full functionality)
19. Google Photos (Warning: it upload in original quality because it thinks it is a Pixel)
20. Google Play Games
21. Settings debloated, along with framework
22. App Lock (Settings)
23. SystemUI Tuner (Updated)
24. Google Tasks
25. YouTube Vanced
26. Correctly Scaled Pixel Boot Animation (Pixel 2XL)
27. Google Sounds, animations, framework and configs.
28. Pixel Launcher with new gesture navigation and recents menu (Not Pill Navigation)
29. Digital Wellbeing
30. Dolby Atmos (With Gaming Mode) with Correct Tuning and Gain (Main Speaker has most power and Earpiece just adds detail and treble)
31. GBoard and New Pie Emojis (Not Samsung Ones)
32. Incredibly Deep Debloat and DeKnoxed (Same as last time for performance and battery improvements)
33. VoLTE Supported
34. Pixel 3 Live Wallpapers with Normal Wallpapers too.
Bugs: NONE
Notes:
1. RAM management when fresh installed idles around 3.5 Free on 6gb note 9
2. ROM Size has fallen to small size from Stock size
3. Device Maintenance swapped for Files GO and SystemUI Tuner. To view Battery Stats and Storage, pull down the Quick Settings Panel and on the top right click the three bubbles button and then Button Order. Then move the new Battery and Storage icon to the Quick Settings.
5. Make sure you set Google Dialer as your default phone app. Goto Settings/Apps. Click the three dots in the top right corner. Then click default apps. Then Calling App and select Phone.
6. After first boot, reboot your device once.
7. Substratum does still work, just remember to get Samsung Substratum themes. -----IF ROM Support Substratum include-----
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
INSTALL INSTRUCTIONS:
1. Download the zip
2. Wipe System, Data, Dalvik and Cache
3. Flash the zip
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Final Notes, Download Link and Sources:
Feel free to message me on telegram via the group: <Mod Removed>
Download Link 1.0: <Mod Removed>
Mirror Link 1.0 : <Mod Removed>
Kernel Source : http://opensource.samsung.com/reception.do
Credits:
@Skulldron and the entire Pixel Team
Samsung for their amazing device
Augustin for building the ROM
Check out the rom
samsung spen works
samsung health works
samsung gear works
includes gcam and samsung camera
https://imgur.com/a/DLbK8MG
pictures of rom
A new rom yay!!! Right now it's 12:30am here so I'll be downloading overnight and will be flashing the rom after morning ?? Thank you so much, can't wait to try it out!!
Awesome news..... Sound really interesting.. thank you for the new rom here in N9 section. Will flash it soon.
Does anyone has tested this ROM?
cool! Another Rom for our beloved NOTE 9.
Tried installing this, there is something wrong when setting up. Firstly on set up google does not recognise my old pin anymore after flashing. Tried a pincode less back up and that worked. Afterwards when further installing, it keeps asking for a fingerprint but you need to set it uo with a password. Password will get set up the first time and never get recognised again. After trying to set up and tried rebooting the phone screen keeps flickering on the unlock screen.
Hi xXpixelpieXx, please share rom thru Mega pls. Google Drive is too slow in my country.
Amazing news
Sent from my [device_name] using XDA-Developers Legacy app
Downloading Rom, can't wait to try it out!
so i flashed it today (twice) and after a phone restart i get the message "only official released binaries are allowed to be flashed" so i have to restore my phone from odin then restore from twrp. First time it happened i restarted after titanium backup and the second time i restarted after putting my email in the setup wizard.... please fix
wenjie1234 said:
Downloading Rom, can't wait to try it out!
Click to expand...
Click to collapse
good
karapoutsoglou said:
Amazing news
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
yes
eabrillos said:
Hi xXpixelpieXx, please share rom thru Mega pls. Google Drive is too slow in my country.
Click to expand...
Click to collapse
im uploading to mega check mirror link in op in 5 minutes
bartjeh1991 said:
Tried installing this, there is something wrong when setting up. Firstly on set up google does not recognise my old pin anymore after flashing. Tried a pincode less back up and that worked. Afterwards when further installing, it keeps asking for a fingerprint but you need to set it uo with a password. Password will get set up the first time and never get recognised again. After trying to set up and tried rebooting the phone screen keeps flickering on the unlock screen.
Click to expand...
Click to collapse
to skip fingerprint at setup: press the arrow back 1 time thats it?
osk4rin said:
Does anyone has tested this ROM?
cool! Another Rom for our beloved NOTE 9.
Click to expand...
Click to collapse
yes good rom
dsg2003 said:
Awesome news..... Sound really interesting.. thank you for the new rom here in N9 section. Will flash it soon.
Click to expand...
Click to collapse
please try it and give honest review also
Supracer said:
A new rom yay!!! Right now it's 12:30am here so I'll be downloading overnight and will be flashing the rom after morning ? Thank you so much, can't wait to try it out!!
Click to expand...
Click to collapse
good
Supracer said:
so i flashed it today (twice) and after a phone restart i get the message "only official released binaries are allowed to be flashed" so i have to restore my phone from odin then restore from twrp. First time it happened i restarted after titanium backup and the second time i restarted after putting my email in the setup wizard.... please fix
Click to expand...
Click to collapse
flash oreo bootloader and flash the rom again i have this every time i use pie bootloader just flash oreo bootloader it is because the bootloader for pie is not good and it contains problems.
https://androidfilehost.com/?fid=1395089523397887521
flash this in twrp to get oreo bl and then flash this rom and no more problem.
xXPIXELPIEXx said:
good
yes
im uploading to mega check mirror link in op in 5 minutes
to skip fingerprint at setup: press the arrow back 1 time thats it?
yes good rom
please try it and give honest review also
good
Click to expand...
Click to collapse
After setting up a password the phone wont recognise the password anymore. So if you reboot you cant use your phone anymore.... Also the screen starts flickering after the reboot. So you cant even enter anything...
Ok this is the 3rd time and I'm done trying for now... Sorry bro I really wished everything worked perfectly but after finishing up the setup wizard, I restarted my phone and I can't go past the lockscreen.... the screen is on loop (comes up for 1 sec and turns off for 10) and that's without restoring any apps.
xXPIXELPIEXx said:
flash oreo bootloader and flash the rom again i have this every time i use pie bootloader just flash oreo bootloader it is because the bootloader for pie is not good and it contains problems.
https://androidfilehost.com/?fid=1395089523397887521
flash this in twrp to get oreo bl and then flash this rom and no more problem.
Click to expand...
Click to collapse
how to restart phone if i have this error? i cnat reboot to twrp or odin mode. help pls
Used the ROM for quite a while and it's good. The only problem is that I cannot use anything to lock my phone. Fingerprint, face, iris or even the basic ones like pattern, password or pin. Everything just fail. Even you set-up pattern, it doesn't work
Supracer said:
Ok this is the 3rd time and I'm done trying for now... Sorry bro I really wished everything worked perfectly but after finishing up the setup wizard, I restarted my phone and I can't go past the lockscreen.... the screen is on loop (comes up for 1 sec and turns off for 10) and that's without restoring any apps.
Click to expand...
Click to collapse
ok hope u will consider our rom another time
peppect91 said:
how to restart phone if i have this error? i cnat reboot to twrp or odin mode. help pls
Click to expand...
Click to collapse
kindly flash stock rom if you dont know how to solve this :laugh: i post fix right above you :silly:
wenjie1234 said:
Used the ROM for quite a while and it's good. The only problem is that I cannot use anything to lock my phone. Fingerprint, face, iris or even the basic ones like pattern, password or pin. Everything just fail. Even you set-up pattern, it doesn't work
Click to expand...
Click to collapse
works fine for me i will investigate the bug
boys dont use fingerprint sensor or security settings press not now and continue setup press back arrow if you get the fingerprint sensor screen if you want security put pin on your sim card which will lock instantly every time you reboot :good:
https://forum.xda-developers.com/ga...tom-romers-t3923647/post79387468#post79387468
tips so everyone can avoid bugs on roms
peppect91 said:
how to restart phone if i have this error? i cnat reboot to twrp or odin mode. help pls
Click to expand...
Click to collapse
please help us we can't reboot to join in to twrp or odin mode please help
---------- Post added at 04:11 PM ---------- Previous post was at 03:55 PM ----------
after flashed your rom my phone is break please help .
So here they are -
1. First, Is there a way to create a fastboot rom by extracting files from the device? Or you just have to download it?
The reason - As I've always found that stock roms in any phone are the most stable, and it'd be nice if we could create a fastboot rom out of it. Not to forget that we can also save a lot of bandwidth.
2. I recently tried to unlock my device and I was met with an error "wait 72 hours, use your device actively". So what rules I have to follow?
Moreover whenever I try to close my mobile connection whether through notification tab or inside settings, my device restarts.
Are these related? Though if I'm quick enough that I close internet before sim could load and show the H/LTE sign, then it doesn't restarts. But if I turn it later on and decide to shut it off, then it's bound to restart.
Was just tapping on usb tethering and it restarted, don't know if my connection went off as it rebooted very quickly, but it restarted again.
Update : Tried to switch from mobile data to wifi, still restarted. Sometimes if the sim is a little slow to connect to internet and I turn it off, then it doesn't restart either. The data got turned on later and got shut off automatically as in actuality it was off, but the phone didn't restarted then.
3. I'm having some problems with face recognition. First I registered in a dark environment, unlocked it 2/3 times right away. But when I tried later, it didn't worked several times either in dark or well lit environment. Then I installed it in a well lit environment, same thing worked 2/3 times right away, but as soon as I changed the location to dark or back to well lit, it didn't worked again. Just tried it RN, it worked several times except a few times, so what 's going on here? I'm confused.
Update : I think it's a distance issue.
4. This is a general question regarding miui. Where is the data saver (restrict background data) feature in miui? I've tried several times to find it in different mi phones. But was never able to find it. It's been here from kitkat or maybe even older, correct me if I'm wrong. So why not provide it in miui, such a feature rich rom? Is it hidden somewhere?
5. The stock rom my phone has is based on Android 8.1 (8.1.0 OPM1.171019.011) to be exact, for rom version refer to reply. I've tried different versions of gcam, but none of 'em has worked for me. Normal camera app works fine, nothing I've encountered yet.
These are the versions I've tried -
* F1v9.5_6.2.030.apk (Couldn't install as 6.2 is only supported by android pie)
* MGC_6.1.021_XCAMBase_F1_v5a.apk (Installed and worked, details below)
* MGC_6.1.021_Potter_v7.1_san1ty.apk (Installed, didn't open)
* MGC_6.1.021_Potter_v7_san1ty.apk (Installed, didn't open)
On photo, the camera lags like I'm playing a game at 2-3 fps, same for other photo related options. Except for panaroma, photo sphere, lens blur, these I didin't had problem with. Except panaroma pic never showed up in camera app or gallery. In video it doesn't lag, so recording normal video was fine. But when I recorded a slo mo video, it lagged after the recording, inside & out the camera app. Inside gcam the audio was fine but outside it was muffled. By outside I mean gallery app & vlc player.
I may try other versions but each app is so big.
Gurkirat_Singh said:
So here they are -
1. First, Is there a way to create a fastboot rom by extracting files from the device? Or you just have to download it?
The reason - As I've always found that stock roms in any phone are the most stable, and it'd be nice if we could create a fastboot rom out of it. Not to forget that we can also save a lot of bandwidth.
2. I recently tried to unlock my device and I was met with an error "wait 72 hours, use your device actively". So what rules I have to follow?
Moreover whenever I try to close my mobile connection whether through notification tab or inside settings, my device restarts.
Are these related? Though if I'm quick enough that I close internet before sim could load and show the H/LTE sign, then it doesn't restarts. But if I turn it later on and decide to shut it off, then it's bound to restart.
Was just tapping on usb tethering and it restarted, don't know if my connection went off as it rebooted very quickly, but it restarted again.
Update : Tried to switch from mobile data to wifi, still restarted. Sometimes if the sim is a little slow to connect to internet and I turn it off, then it doesn't restart either. The data got turned on later and got shut off automatically as in actuality it was off, but the phone didn't restarted then.
3. I'm having some problems with face recognition. First I registered in a dark environment, unlocked it 2/3 times right away. But when I tried later, it didn't worked several times either in dark or well lit environment. Then I installed it in a well lit environment, same thing worked 2/3 times right away, but as soon as I changed the location to dark or back to well lit, it didn't worked again. Just tried it RN, it worked several times except a few times, so what 's going on here? I'm confused.
Update : I think it's a distance issue.
4. This is a general question regarding miui. Where is the data saver (restrict background data) feature in miui? I've tried several times to find it in different mi phones. But was never able to find it. It's been here from kitkat or maybe even older, correct me if I'm wrong. So why not provide it in miui, such a feature rich rom? Is it hidden somewhere?
Click to expand...
Click to collapse
sir, you never mention which version you are on ? since Boot is locked so definately MIUI but which one? global/beta/Eu/ Stable/chine etc?
anways..
Answer for 1, - No you have to redownload it, the Fastboot Rom consist of few extra files like persist and recovery and if they are update you must use the latest one. however via twrp you can take system/data/ and other partitions backup if you want...
for 2. after 72hours, goto dev option and try enabling oemunlock, it will give you warning but do it, come out of dev option and go in and do it again, repeat until the UNLOCK setting stays on UNLOCK, (don't know why it is, but this is how it is,,,, ) , later verify your miui account and sim, keep signed in. download unlocker and sign- in and try unlocking the device (make sure all qualcom drivers are installed)
for 2 again, This is very strange, ONE OF ITS KIND error I AM hearing , I honestly thought this bug is ONLY custom rom related! , you see Poco f1, Beryllium uses MODIFIED VENDOR IMAGE ( can be found at) https://mirror.akhilnarang.me/MIUI/beryllium/.
now these modified vendor images by MIUI dumps logs on data/data/netstat (specially if you are USB TETHERING on 3g, ... you will start suddent System UI reboots and some com.android.xyz processes crashing errors and if you toggle Airplone mode 3g/4g or usb tethering from quick setting , device either hung or system ui restarts or device reboots.
now this error is always in all custom roms due to vendor image
solution? DELETE all files from data/data/netstat and reboot (rooted device on custom rom)
for locked device (unrooted) you may have to flash updated version of miui to fix this bug!
Once you unlock device take latest vendor image ( i am using 9.6.27.9-0 , it has better battery life) and flash custom rom...
for 2 again,,,, some users are complaing that miui10.3.6 alters fastboot commands! and twrp no longer works! , make sure you don't flash miui10.3.6,
for no3,, i don't use facial unlock feature, i will study more and will get back to u if relevent.
for 4
Open MIUI Security App.
Tap on Data Usage Tool.
Tap on Restrict Data Usage.
Now find out those data hunger apps and restrict them by tapping on the green tick.
@YasuHamed First of all big thanks for such a descriptive answer.
1. Now, I'm on stock miui rom i.e. MIUI global stable 9.6.14.0(OEJMIFD).
So If i haven't updated my rom in any way what so ever. can I create a fastboot rom out of it? If I can then also, will that fastboot rom have all the system settings I have on my phone right now? Or will they be default?
2. While not exactly as you said but something similar happened. I do remember enabling the option of oem unlock, but it was turned off. It didn't gave any warnings, so I enabled it multiple times maybe 4, then on the 4th time it showed me a warning and after that it was enabled permanently, even after several boots and reboots.
IDK which "unlock setting" do you mean, which has to say unlock? Is it something different than I mentioned here or are you talking about Mi unlock status, cause I already tapped the 'add account and device' option in it.
Yes really strange indeed. I'm just worried that my hardware isn't damaged? Cause I just got the phone 2 days ago and if it's only a software thing then it's fine. As I'm sure installing/flashing rom would fix it! But I can't RN as you know the time period. Why am I worried? I took my phone to a mobile shop to put lamination on it asap as to avoid any scratches. As you may know that they use heat gun, to do it properly around the curves, I'm just getting a little worried that it damaged my phone's hardware, please give me hope.
Some other strange things happened as well. After some reboots, when I went into file manager app, it would open showing previews etc. but as soon as I click on storage/folders, it says "disconnected" and later I get a message "couldn't add error 10000" like after 10-15 seconds, as I vaguely remember. But after some reboots it would work just fine so IDK what's going on.
3. I also think it's about the experience. More I used it, I think infrared illuminator doesn't throw rays too far, so you have to keep your face a little close.
4. Thanks I found it. But I don't think it is very effective, feature wise. And I also think it isn't working that well RN as it keeps showing the data usage as 0, maybe cause of the bugs? Also the features like restricting data etc for individual apps is good but if you have to restrict background data for each &very app, you have to do that individually. Though if i restrict data, can an app still use background data? As they are different menus. Also it doesn't show usb tethering or hotspot data or anything like that in the list.
Check my 5. question.
Gurkirat_Singh said:
@YasuHamed First of all big thanks for such a descriptive answer.
1. Now, I'm on stock miui rom i.e. MIUI global stable 9.6.14.0(OEJMIFD).
So If i haven't updated my rom in any way what so ever. can I create a fastboot rom out of it? If I can then also, will that fastboot rom have all the system settings I have on my phone right now? Or will they be default?
2. While not exactly as you said but something similar happened. I do remember enabling the option of oem unlock, but it was turned off. It didn't gave any warnings, so I enabled it multiple times maybe 4, then on the 4th time it showed me a warning and after that it was enabled permanently, even after several boots and reboots.
IDK which "unlock setting" do you mean, which has to say unlock? Is it something different than I mentioned here or are you talking about Mi unlock status, cause I already tapped the 'add account and device' option in it.
Yes really strange indeed. I'm just worried that my hardware isn't damaged? Cause I just got the phone 2 days ago and if it's only a software thing then it's fine. As I'm sure installing/flashing rom would fix it! But I can't RN as you know the time period. Why am I worried? I took my phone to a mobile shop to put lamination on it asap as to avoid any scratches. As you may know that they use heat gun, to do it properly around the curves, I'm just getting a little worried that it damaged my phone's hardware, please give me hope.
Some other strange things happened as well. After some reboots, when I went into file manager app, it would open showing previews etc. but as soon as I click on storage/folders, it says "disconnected" and later I get a message "couldn't add error 10000" like after 10-15 seconds, as I vaguely remember. But after some reboots it would work just fine so IDK what's going on.
3. I also think it's about the experience. More I used it, I think infrared illuminator doesn't throw rays too far, so you have to keep your face a little close.
4. Thanks I found it. But I don't think it is very effective, feature wise. And I also think it isn't working that well RN as it keeps showing the data usage as 0, maybe cause of the bugs? Also the features like restricting data etc for individual apps is good but if you have to restrict background data for each &very app, you have to do that individually. Though if i restrict data, can an app still use background data? As they are different menus. Also it doesn't show usb tethering or hotspot data or anything like that in the list.
Check my 5. question.
Click to expand...
Click to collapse
sir Gurkirat_Singh
1. sir you are on Miui9.6 which is based on oreo.I have personally updated till 10.0.03 and have all the fastboot command working fine.
you may download miui9.6.22 (a bit updated version from what you are currently on) from
http://en.miui.com/thread-3995650-1-1.html ( both Recovery (1.6gb) & Fb rom (2.5gb) as backup.
2. under Developer options , poco f1 has this trick that OEM UNLOCK doesnt stick on UNLOCK and keeps coming to default once after you exit Developer option. on my 5th attempt it finally stick to UNLOCK and i was able to unlock the device from unlocker Tool.
3. I havent removed my poco sticker from back (yet), put 9h class, bought extra skin my self and book cover too so yes I second that. I always protect my devices like part of me , even the retired ones are sleeping in boxes with proper covers and unused accories!,
now, update your rom and try again to toggle 3g/4g usb tethering. 99% chances are its software issue! and i have faced this issue many times and its my 5th month with device so i havent noticed any hardware damage or performance / speed problems yet... so don't worry. YES few kernels affect network connectivity, however I am on Optimus Drunk kernel on Havoc 2.8 and its working like a charm!
-about file manager issue, can you try the same with FX File Explorer? and report back plz
4.if you restrict globally then miui will only allow system apps to use data in background as and when needed. MIUI won't allow facebook/whatsapp and other VOIP callers to work in the background. Once in restricted mode on miui9 on RN5pro, I used to miss call on whatsapp unless i wake the device up and notifications starts appearing that i have many whatsapp miss calls!, this feature went even worse on rn5pro when i was on dual sim, miui use to prefer carier sim over data sim always! so yes miui has strict data usage control.
5. i am unable to find 5th question plz help
few screen shots of my poco f1 on HAVOC2.8 / OD kernel build20190820 / magisk19.3 / gapps nano
@YasuHamed
1. I didn't got the answer to my question, please read my question again.
2. I'm gonna assume you mean 'oem unlock' got enabled and I'd be able to unlock after 72 hours are over.
2. a. I hope so as well, thanks again.
Although sometimes it would run fine and even after turning off mobile data, wifi, usb tethering etc. it won't restart. I thought the oem unlock setting helped but when I tried not an hour ago, it restarted. Same thing with file manager, it's working fine now, I'm sure 3rd party file managers would work fine as well. Only a few times, it showed that 'disconnected' error.
4. I guess I'd just have to hit and trial myself.
5. Check my OP (original post).
Gurkirat_Singh said:
@YasuHamed
1. I didn't got the answer to my question, please read my question again.
2. I'm gonna assume you mean 'oem unlock' got enabled and I'd be able to unlock after 72 hours are over.
2. a. I hope so as well, thanks again.
Although sometimes it would run fine and even after turning off mobile data, wifi, usb tethering etc. it won't restart. I thought the oem unlock setting helped but when I tried not an hour ago, it restarted. Same thing with file manager, it's working fine now, I'm sure 3rd party file managers would work fine as well. Only a few times, it showed that 'disconnected' error.
4. I guess I'd just have to hit and trial myself.
5. Check my OP (original post).
Click to expand...
Click to collapse
sir
1. I never read any such method so far where you can reverse engineer the extracted files in partitions and pack them back as fastboot rom. and to think of it thats almost impossible because stockroms usually comes with digitally signed by vendors ensuring no foul play.
2. once your 72hrs over, just unlock the oem unlock switch from Dev option, verify sim of on your mi account, download the unlock tool, login using same mi account, hit unlock, after success, the device will BOOT on POCO logo and "UNLOCKED" will start appearing (always) and all data partition, internal storage will be wiped! so make sure you take backup!
2a. with me on custom rom it wasn't a sure thing but it used to happend randomly when least expected.
5. on oreo , GCAM version came in sep2016 worked for me and later ones are for pie and kept crashing (please check old version on apkmirror)
@YasuHamed Thanks for all the help.
5. I did found a version that is working fine for now. But the features I was interested in was super res zoom, night mode, slo mo etc. Super rez wasn't that impressive(seemed similar to stock zoom), night mode either, slo mo still doesn't work properly and phone heats up, even when I'm not using too old of a version of gcam. Even the stock cam app took some good shots with zooming.
And if those features will work better with pie version then IDK what to say cause that new version would come with better stock cam having slo mo, night mode and all that shiz if not everything. So I'm kinda thinking is this gcam port really relevant? It drastically changed image quality with my RN3 but I don't see that now.
Edit: Also I wanted to say that my phone was working fine now i.e. no reboots after closing mobile data or wifi or switching. But you know what they say don't celebrate too soon. As soon as I used usb tethering the problem arised again, I wasn't able to it for 2 days as my PC wasn't booting. Same reason why I wasn't able to reply to you earlier.
Not only this, this whole bugged situation has started to irritate me a lot. Just today I was trying to run flash on my android. And even on the supported browser, it just wouldn't show up. I really hope after I unlock this device, all of these bugs would go away after the data gets deleted, or I'm gonna be more disappointed.
@YasuHamed This has really started to piss me off now. It has started again.
While IDK if the camera or flash not working properly are related to this whole bugged system or not. But I guess usb tethering is the trigger to this whole thing. Everything was working fine, it started to record the mobile data usage, didn't turned off when turned off the mobile data and even worked when I used usb tethering, but suddenly it reboots and the whole **** show all over again. I'm really pissed now. Oh btw it started showing 0 data used AGAIN.
Gurkirat_Singh said:
@YasuHamed This has really started to piss me off now. It has started again.
While IDK if the camera or flash not working properly are related to this whole bugged system or not. But I guess usb tethering is the trigger to this whole thing. Everything was working fine, it started to record the mobile data usage, didn't turned off when turned off the mobile data and even worked when I used usb tethering, but suddenly it reboots and the whole **** show all over again. I'm really pissed now. Oh btw it started showing 0 data used AGAIN.
Click to expand...
Click to collapse
please consider upgrading to MIUI10.3.x , download the complete recovery rom and name it as update.zip and put it in download folder and open updater and call the rom from there , and flash it, I suggest CLEAN FLASHING so all the data will be deleted!
plz take backup!
@YasuHamed can you please find me fastboot rom for miui 9.6.14(OEJMIFD), I tried but I couldn't find it. I'd do the full clean flash through edl mode. That would resolve any bugs related software, right?
Come to think of it, why did this all started happening at the first place? As I remember, it all started after a failed attempt to unlock, I mean not fail fail, I just had to wait before I could do so. Do you see any patterns?
Also if you know anything in this regard, did the stock rom (9.6.14) had such problems back in the day?
Gurkirat_Singh said:
@YasuHamed can you please find me fastboot rom for miui 9.6.14(OEJMIFD), I tried but I couldn't find it. I'd do the full clean flash through edl mode. That would resolve any bugs related software, right?
Come to think of it, why did this all started happening at the first place? As I remember, it all started after a failed attempt to unlock, I mean not fail fail, I just had to wait before I could do so. Do you see any patterns?
Also if you know anything in this regard, did the stock rom (9.6.14) had such problems back in the day?
Click to expand...
Click to collapse
frankly i never used my poco on miui either on 9 nor on 10 ,
the day I got, I placed unlock request and after 3-4 days, I unlocked my device and put it on HAVOC and since then my experience is based on custom roms but i did flash miui 10 in between just to have a taste of it! and came back to havoc in a day or two, hence i never deeply tested these feature.
however I do know that modified vendore have created usb tethering problems throughout devices
https://mirom.ezbox.idv.tw/en/phone/beryllium/roms-global-stable/
@YasuHamed I don't think mine contains modified rom. As I went ahead and checked all the possibilities like using cn as in china in the codename of a global rom, updates are also working. I even went ahead to check the authenticity of my device. It checks out with some other things on the box as well. So I'm 100% sure, that this has got nothing related to that.
Some other things which I tried in the meantime. I wanted to test if I can run tegra games on this device. So I installed gltools and build prop. Gltools to make the app believe that my device has the gpu it's looking for. Build prop to make app believe I have the device on which this is supposed to run. But I ended up with the same results. So IDK what I did wrong there? In this regard I wanna ask that, is it possible for root checker to show your device is rooted when in fact its not properly rooted.
Why am I asking this? Cause while going through rooting procedure I skipped a few steps like not flashing 'disable force encryption treble' which I did notice after unlocking, during first boot, the device did do some encryption. I skipped that step cause of something mentioned on this link https://twrp.me/xiaomi/xiaomipocophonef1.html regarding dm verity, but as I just checked the same is mentioned regarding rn3 so IDK what to make of this now, but what I did is not 'swipe to allow modifications' and click on 'read only' in twrp recovery and it did rebooted to recovery properly. As mentioned in the link that some system could force to flash stock recovery. Other than that, not factory resetting, data wiping after root, but does it really matter that much?
I can hear you say that dude you're playing with your device too much, of course it's gonna have these problems. To that, I say I didn't do anything like this, prior to unlocking but the problems were still there if not all of them. So what is the root cause of this then? Do I really need to take it service centre to get it checked out or just flashing the rom through edl mode would fix this?
Not just that after I made those changes in build prop(not including gltools) something very weird/interesting happened. If I would restart my device the boot logo shown is poco but the boot splash is mi logo. And when it rebooted after closing the internet, it would only show the mi logo but then I remember that it must've been soft(hot) reboot as it only shows boot splash.
Not only this, after rebooting the style of the rom changed as well. The icon on the home rearranged themselves a bit. So instead of seeing 5 icons in a row, it was all 4 icons on home as well as on app drawer. As you may know Kika keyboard is defaulty present in this rom but after the build prop modifications, whenever I lock my device and wake it up it started showing ads sometimes, maybe the same ad everytime IDK.
Another thing as you know there is an option of reboot to recovery under about phone updates. When I did that that it showed the 'android' logo. I tried it again but it kept showing the loading sign only.
Also how did you find these files? Thanks again m8. You know just for reference if I'd have to find them myself. Also what are those that say (rolled back).
Gurkirat_Singh said:
@YasuHamed I don't think mine contains modified rom. As I went ahead and checked all the possibilities like using cn as in china in the codename of a global rom, updates are also working. I even went ahead to check the authenticity of my device. It checks out with some other things on the box as well. So I'm 100% sure, that this has got nothing related to that.
Some other things which I tried in the meantime. I wanted to test if I can run tegra games on this device. So I installed gltools and build prop. Gltools to make the app believe that my device has the gpu it's looking for. Build prop to make app believe I have the device on which this is supposed to run. But I ended up with the same results. So IDK what I did wrong there? In this regard I wanna ask that, is it possible for root checker to show your device is rooted when in fact its not properly rooted.
Why am I asking this? Cause while going through rooting procedure I skipped a few steps like not flashing 'disable force encryption treble' which I did notice after unlocking, during first boot, the device did do some encryption. I skipped that step cause of something mentioned on this link https://twrp.me/xiaomi/xiaomipocophonef1.html regarding dm verity, but as I just checked the same is mentioned regarding rn3 so IDK what to make of this now, but what I did is not 'swipe to allow modifications' and click on 'read only' in twrp recovery and it did rebooted to recovery properly. As mentioned in the link that some system could force to flash stock recovery. Other than that, not factory resetting, data wiping after root, but does it really matter that much?
I can hear you say that dude you're playing with your device too much, of course it's gonna have these problems. To that, I say I didn't do anything like this, prior to unlocking but the problems were still there if not all of them. So what is the root cause of this then? Do I really need to take it service centre to get it checked out or just flashing the rom through edl mode would fix this?
Not just that after I made those changes in build prop(not including gltools) something very weird/interesting happened. If I would restart my device the boot logo shown is poco but the boot splash is mi logo. And when it rebooted after closing the internet, it would only show the mi logo but then I remember that it must've been soft(hot) reboot as it only shows boot splash.
Not only this, after rebooting the style of the rom changed as well. The icon on the home rearranged themselves a bit. So instead of seeing 5 icons in a row, it was all 4 icons on home as well as on app drawer. As you may know Kika keyboard is defaulty present in this rom but after the build prop modifications, whenever I lock my device and wake it up it started showing ads sometimes, maybe the same ad everytime IDK.
Another thing as you know there is an option of reboot to recovery under about phone updates. When I did that that it showed the 'android' logo. I tried it again but it kept showing the loading sign only.
Also how did you find these files? Thanks again m8. You know just for reference if I'd have to find them myself. Also what are those that say (rolled back).
Click to expand...
Click to collapse
-sir, most of your observations are pertaining to V9.6.14.0.OEJMIFD, where I am not on MIUI hence I will wait for other members to step in and share their views about them.
- you can always use "Disable-Force-Encryption-Treble" from https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389, when flashing rom (clean flash, FORMAT DATA) to disable encryption on kernel level.
- since Twrp official doesnt support OTA so if you call recovery from updater, it wont work! you may have to use Orange Fox (oct/nov2018) version which had OTA support or better flash full rom after downloading desired version from https://mirom.ezbox.idv.tw/en/phone/beryllium/roms-global-stable/
- what are you looking is from different world of android devices, such as TEMP ROOT, IVORY ROOT (sony xperia on android 5.1) days only! when nothing used to be changed but just to gain access of certain partition temporarily, temp root techniques used to apply to extract DRM KEYS. ITs not the case here hence you will have to root your device properly!
- about gpu, i never tried but you can used app such as FK kernel manage or Kernel Auditor to play with your GPU accordingly
- twrp usually ask keep system readonly whenever flashed new room its standard warning to avoid any bootloops since Twrp doesn't know you will be flashing kernel and/or disabling dm varity soon. so it warns you.
- don't worry POCO is FREE from ARB4 $hit so when page said ROLLED BACK, it means those version were recalled back for some buggs and an update released soon after!
@YasuHamed So IDK whether I was clear or not, cause I couldn't understand most of the answers you gave me, maybe they got mixed up, IDK. Anyways I'll try to keep it simple and answer in best way possible and keep it organised so there's confusion.
1. Thing I forgot to mention, after flashing 'disable force encryption treble' file, my root stopped working, I thought it was part of the whole bugged system. In actuality, when I checked the steps while it was flashing, it installed Magisk 16.7, I think. That's why root stopped working. After flashing latest Magisk, it worked fine. So, After flashing "disable" file, Can I flash Magisk over it to get the latest Magisk version? Will it affect the disabled function in any way? Currently I have 3 files, which one do you suggest -
Disable-Force-Encryption-Treble.zip
DisableForceEncryption_Treble_v18.0.zip
Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip
Third one is form the link you provided.
2. DK if TWRP supports OTA, but I was able to boot to TWRP after tapping on reboot to recovery, just saying. By full rom do you mean the stock roms?
3. Did you meant if it checks out in root checker, then it's properly rooted already!?
4. This FK Kernel Manager or Kernel Auditor, you talk about, does it works the same way as Build Prop or GLTools? Cause I'm not an expert in using these tools. I just followed the steps mentioned in this video https://youtu.be/Y1wPIHhM1Yw similarly for the other games I was trying to run by gathering build prop info related to shield tv/tablet/portable but it didn't worked in my favor.
5. So if you chose the option of 'swipe to allow modifications' options instead of 'read only', and your phone boots without any bootloops or anything, as I've done a lot of time on my RN3 without even thinking about it, does that mean that everything's fine? Even when you haven't disabled dm-verity and still are on stock kernel(the one contained in stock roms i think). Does stock kernel changes to custom when you flash a custom rom? Does TWRP makes any changes to stock one if your system boots without any above mentioned problems having stock rom? Any details regarding differences in these two options?
6. When you say an update released soon after? Do you mean same versions were released with bugs fixed or a new/next version was released? In other words, is it ok to try these versions with such bad bugs that they were called back? Were those system breaking bugs fixed in the same version? Also again, I'd really appreciate if you could tell me how'd you find these roms?
7. I'm almost certain that usb tethering is the trigger to these reboots when turning off internet. Cause if I power off the device and turn it on later, then turn on-ff data, it doesn't reboot but sometimes it does. But as soon as I turn usb tethering on, it would reboot and the whole debacle starts again. And the ads kika shows are different along side something related to ram cleaner everytime. So I think it does uses internet. IK you don't use miui, just putting the info out there, if someone thinks of stepping in later.
please view my replies sir
Gurkirat_Singh said:
@YasuHamed So IDK whether I was clear or not, cause I couldn't understand most of the answers you gave me, maybe they got mixed up, IDK. Anyways I'll try to keep it simple and answer in best way possible and keep it organised so there's confusion.
1. Thing I forgot to mention, after flashing 'disable force encryption treble' file, my root stopped working, I thought it was part of the whole bugged system. In actuality, when I checked the steps while it was flashing, it installed Magisk 16.7, I think. That's why root stopped working. After flashing latest Magisk, it worked fine. So, After flashing "disable" file, Can I flash Magisk over it to get the latest Magisk version? Will it affect the disabled function in any way? Currently I have 3 files, which one do you suggest -
Disable-Force-Encryption-Treble.zip
DisableForceEncryption_Treble_v18.0.zip
Disable_Dm-Verity_ForceEncrypt_08.18.2019.zip
Third one is form the link you provided.
I flashed "DisableForceEncryption_Treble_v18.0.zip" and it worked/works, but I always flash before magisk., the current version is Magisk19.3 hence I recomend you to use the updated version, 16.7 is obsolete long back. However if 19.3 may give you bootloops then the max you can go back is Magisk18.0 (since after 18.1, Magisk started using different Script language unknown to some recoveries. However if BOTH (your recovery and Magisk are latest, it should work just fine
2. DK if TWRP supports OTA, but I was able to boot to TWRP after tapping on reboot to recovery, just saying. By full rom do you mean the stock roms?
once on RN5p I tried updating OTA via twrp, it never booted to update hence I recomend you to download full recovery rom 1.8gb, of the build you want and flash it via twrp
3. Did you meant if it checks out in root checker, then it's properly rooted already!?
plz try any root checker and see
4. This FK Kernel Manager or Kernel Auditor, you talk about, does it works the same way as Build Prop or GLTools? Cause I'm not an expert in using these tools. I just followed the steps mentioned in this video https://youtu.be/Y1wPIHhM1Yw similarly for the other games I was trying to run by gathering build prop info related to shield tv/tablet/portable but it didn't worked in my favor.
fk kernel manager or kernel Auditor does support editing build prop, apart from many tweaks for GPU and Cores. the video shows a simple edit in order to think your device is some other version of Galaxy to trick samsung app ; however The boy didn't explain why he just didn't install the already downloaded apk file from fortnite website ?
5. So if you chose the option of 'swipe to allow modifications' options instead of 'read only', and your phone boots without any bootloops or anything, as I've done a lot of time on my RN3 without even thinking about it, does that mean that everything's fine? Even when you haven't disabled dm-verity and still are on stock kernel(the one contained in stock roms i think). Does stock kernel changes to custom when you flash a custom rom? Does TWRP makes any changes to stock one if your system boots without any above mentioned problems having stock rom? Any details regarding differences in these two options?
if you are flashing MIUI From twrp, and DON"T wana ROOT then yes you should never allow system modification because then device will never boot in to system due to DM-Verity. However if you are rooting yoru device, try reading Magisk Lines, It always patch fstab and disable Dm-verity, once its disabled /system parition permision wont be verified on boot. So when you boot in to twrp and you know you are going to flash Magisk, you can ALLOW SYSTEM MODIFICATION swip
on Custom Roms it doesn't matter, because twrp never ask such question. "allow system modification" is only limited to StockRoms
6. When you say an update released soon after? Do you mean same versions were released with bugs fixed or a new/next version was released? In other words, is it ok to try these versions with such bad bugs that they were called back? Were those system breaking bugs fixed in the same version? Also again, I'd really appreciate if you could tell me how'd you find these roms?
the next version above ROLLED BACK one is the bug fixed. (now i don't know what exactly were they) . Also MIUI forums for devices always announce updates! you can google
7. I'm almost certain that usb tethering is the trigger to these reboots when turning off internet. Cause if I power off the device and turn it on later, then turn on-ff data, it doesn't reboot but sometimes it does. But as soon as I turn usb tethering on, it would reboot and the whole debacle starts again. And the ads kika shows are different along side something related to ram cleaner everytime. So I think it does uses internet. IK you don't use miui, just putting the info out there, if someone thinks of stepping in later.
well probably this is the bug of this version 9.6.14 hence you should upgrade atleast to 9.6.20 in order to compare
Click to expand...
Click to collapse
@YasuHamed Again a little bit confused by some answers, but I'll try to keep it simple.
1. Do you mean you flash "d-f-e-t" file before magisk? That's what I was asking, does magisk interfere with the steps, this file does, in anyway? And why didn't u used the 'third file', the one from the link you mentioned, isn't that the better one in some ways?
2. I never said I tried to install an OTA through TWRP. I just said I was able to boot to TWRP through 'reboot to recovery' option under system updates tab.
3. I checked it with one 'root checker' app, do I need to check with others? Can you name some?
4. He didn't used the same apk, cause he wanted to show & tried to explain, what kind of changes we were doing to the system, rather than just blindly following the instructions, like what normally happens in these scenarios. I thought that was given, anyways, I've tried same things before in past. When I had the apk, data/obb files of an app/game, I'd simply just try to install them on miui and they'd just crash, but doing the same thing on a custom rom and it works, no special steps. Similarly did all this work, and ended with crashes, maybe I'll do the same thing on a custom rom and it'll work. On that note, do you know where I can download stable builds of lineage OS, or do I just have to research which one is a a stable version, Or is it okay to download any latest nightly builds, the only thing they post on their official website?
5. If one taps on 'read only' option the first time, and when it boots to twrp again and doesn't asks for it. Can one find that option somewhere else in twrp? I did that and still I'm booting normally, how's that possible then, if you say system won't boot!? And what does that option 'allow system modifications' do exactly? How unlocking & rooting are different, security wise? Cause vendors like Xiaomi allow unlocking officially, which means it doesn't void your warranty, though I don't know what would happen if you walk in with an unlocked device in their service centre, cause I've never done it, But they still warn you about data stealing during unlock process etc. Although if you root your device then it's out of warranty, but it's a much simpler process than unlocking. So what's the difference, is the threat real? Or is it just marketing to keep you locked in the stock experience?
6. Again you didn't tell me how'd you find those roms!?
7. It's just really random, sometimes it doesn't restart even when internet is turned off, sometimes with usb tethering on or sometimes not even connected to the pc. Kika still shows them ads, also after an app is installed/uninstalled etc. Other than those appearance changes, I wasn't also able to dial down the brightness to the very low. Whenever i did it, it restarted, camera stopped working etc. I revert the changes I did in build.prop to make it poco again, it rebooted and the boot splash was fixed, but as soon as the ui showed up, the poco launcher kept crashing. It was good that I had my apps opened in background and miui remembers them even after reboot, otherwise there would've been no way to access build.prop, so I revert it back to any shield tv/portable/tablet settings and it started working normally. Finally I've decided, I'm gonna edl flash the stock rom and report back if these bugs happen again(I hope it's only software), I downloaded 2 roms over this period of time i.e. 9.6.14 & 10.3.7.0, will try and get back to you.
Sorry for the late reply, got a little busy.
sir ..........................
Gurkirat_Singh said:
@YasuHamed Again a little bit confused by some answers, but I'll try to keep it simple.
1. Do you mean you flash "d-f-e-t" file before magisk? That's what I was asking, does magisk interfere with the steps, this file does, in anyway? And why didn't u used the 'third file', the one from the link you mentioned, isn't that the better one in some ways?
1- Yes I flashed DFET before Magisk19.3 - and why i didn't use the third file, i remember in post one user confirmed this particular one working for him (atleast) so i downloaded that one.
2. I never said I tried to install an OTA through TWRP. I just said I was able to boot to TWRP through 'reboot to recovery' option under system updates tab.
2- ideally this is the case with recoveries which doesn't support OTA, OrangeFox based on OLD version of TWRP does support OTA , I NEVER TRIED but worth reading the post. you should find it in the Poco Development section
3. I checked it with one 'root checker' app, do I need to check with others? Can you name some?
3- I use THIS ONE
4. He didn't used the same apk, cause he wanted to show & tried to explain, what kind of changes we were doing to the system, rather than just blindly following the instructions, like what normally happens in these scenarios. I thought that was given, anyways, I've tried same things before in past. When I had the apk, data/obb files of an app/game, I'd simply just try to install them on miui and they'd just crash, but doing the same thing on a custom rom and it works, no special steps. Similarly did all this work, and ended with crashes, maybe I'll do the same thing on a custom rom and it'll work. On that note, do you know where I can download stable builds of lineage OS, or do I just have to research which one is a a stable version, Or is it okay to download any latest nightly builds, the only thing they post on their official website?
4- To get general IDEA about altering Build.Prop, The video is Good! however you can not assume Samsung Modded Android over MIUI's one! also It seems the boy in the video has Android7 where Miui Poco is atleast on 8.1, there is huge difference!
The only way to find out whether any type of build.prop (EVEN ON CUSTOM ROMS) will WORK or NOT on POCO; is to Try and find out yourself.
5. If one taps on 'read only' option the first time, and when it boots to twrp again and doesn't asks for it. Can one find that option somewhere else in twrp? I did that and still I'm booting normally, how's that possible then, if you say system won't boot!? And what does that option 'allow system modifications' do exactly? How unlocking & rooting are different, security wise? Cause vendors like Xiaomi allow unlocking officially, which means it doesn't void your warranty, though I don't know what would happen if you walk in with an unlocked device in their service centre, cause I've never done it, But they still warn you about data stealing during unlock process etc. Although if you root your device then it's out of warranty, but it's a much simpler process than unlocking. So what's the difference, is the threat real? Or is it just marketing to keep you locked in the stock experience?
5- Once twrp changes the /System as writable, cannot be undone from Twrp itself - since you have magisk16.7 as you mention earlier the dm-varity is turned off and you are booting normally.
-unlocking means, your device can accept fastboot commands to Alter various Partitions developed by Third Party! /recovery /system /vendor /oem etc
-Rooting is Gaining /system access in Android OS to perform Forbiddon and/or Unsafe Commands / Apps etc
- now your question about security , i will simply say! its HIGHLY UNSECURE to unlock your device & Root it!, there is debate about SeLinux Permissions to be Permissive or Enforcing , SELinux in enforcing mode is considered to be little better and secure but Permissive mode means any command can be run even by hacker to gain your /system access ! REFERENCE
- unlocked bootloader is also very unsafe! anyone can just flash any compatable recovery and atleast WIPE your data!
HENCE this is what i say to all my fellow friends and mates in general! if you are CONCERN security privacy , NEVER ROOT your device! or keep two devices, one being as family device! for fotos, emails contacts etc! and play with the other!
- about warranty! every region has different rules! my country's Xiaomi centre doesn't cover any brick devices because here they are alreadly selling many Redmi fones on UNLOCKED mode! directly from china!
6. Again you didn't tell me how'd you find those roms!?
https://c.mi.com/oc/miuidownload/index select poco and see officially available rom
7. It's just really random, sometimes it doesn't restart even when internet is turned off, sometimes with usb tethering on or sometimes not even connected to the pc. Kika still shows them ads, also after an app is installed/uninstalled etc. Other than those appearance changes, I wasn't also able to dial down the brightness to the very low. Whenever i did it, it restarted, camera stopped working etc. I revert the changes I did in build.prop to make it poco again, it rebooted and the boot splash was fixed, but as soon as the ui showed up, the poco launcher kept crashing. It was good that I had my apps opened in background and miui remembers them even after reboot, otherwise there would've been no way to access build.prop, so I revert it back to any shield tv/portable/tablet settings and it started working normally. Finally I've decided, I'm gonna edl flash the stock rom and report back if these bugs happen again(I hope it's only software), I downloaded 2 roms over this period of time i.e. 9.6.14 & 10.3.7.0, will try and get back to you.
EDL ? you mean fastboot rom flashing via miflasher!, thats not edl! to trigger EDL you must have
1. authorized Xiaomi Account
2. back panel of poco to be opened and short test point to put device in EDL
Sorry for the late reply, got a little busy.
Click to expand...
Click to collapse
@YasuHamed
1. I tested the third file. It worked without any problems even after flashing magisk. Cause it doesn't mess or flash any magisk files, it also detects what sort of root the phone have.
3. -> 2. I used the same app to check so.
3. You mention some good points there. That's the same reason, things worked out in custom roms and not miui in my earlier experiences. As miui is heavily loaded compared to any custom rom or samsung experinece. I'll try it on other OSs and report back. On the same note, from what I've read that lineage team doesn't release stable builds or at least not anymore. I'm currently downloading pixel experience. Should I go with this one or lineage os? Is it like any other custom OS or heavily loaded like miui? Also what is the difference between PE normal vs plus vs caf? Also I'm gonna try multi rom, as it would be much better for testing.
4. (new) As you said you use havoc os or havoc kernel I think. Which other custom roms have you tried? Is havoc your favourite one? What sort of uses you make with these custom OSs, just normal daily use or something else? Or anything else you wanna share in this manner about your experience, recommendations or anything else.
5. I think I understand a bit, if I use the option 'swipe to allow system modifications' and do not root my device i.e. not flashing magisk which in turn won't disable dm-verity and then if I try to boot to system, it'll go in booloop?
IF I'm right, then what is "read only & root" vs "allow system modifications & root"? Also I have the latest magisk version. What I was trying to say, "When I flashed the 'first' file out of the three 'dfet' files, it flashed magisk 16.7 as well causing latest magisk manager to not work", which I figured out and fixed immediately.
Also when the first time I flashed twrp, only then I got these options. But later on when I flashed the fresh rom through fastboot and then the recovery I simply got booted to the main menu without getting to choose any of these options. During that, I formatted all the stuff like system, internal storage etc. which i wasn't supposed to format, cause of which I had to flash again, but I forgot to select the 'clean all' option instead of 'clean all and lock' option. So i had to unlock again and flash twrp again. But even after all that twrp remebered all the changes I made to it like time, vibration, brightness settings and again it didn't showed any of those two options. More on this in the last response.........
6. And again you gave me the link to miui's official website. I was asking how'd you find all those older roms at one place.
7. So I finally flashed miui rom today, having high hopes, which were proven to be right first then crushed down later. After I flashed the rom, I tested the heck out of it like turning data on/off, usb tethering on/off, no problem occured, didn't found any bugs except one in data usage, it was showing like 100-600gigs(I don't remember exactly) of usage, then it started showing 1300-1400gigs, but after seeing that my confidence dipped down a little.
But still I moved on and flashed twrp on it to get it rooted. After rooting everything was fine even the data usage bug also went away, then I installed gltools and I had my phone connected to pc in usb tethering, suddenly I hear a sound(it restarted<insert gta sa cj meme>) and it starts all over again. I flashed 9.6.14 ver of rom btw.
As you already know from my response above that I was only able to flash through fastboot mode and I wasn't able to get into edl mode as I read just a few hours ago that it's locked away. So my question is, is there a chance that this all could be solved if the rom is flashed through edl. As that's much more of a clean install rather than fastboot, as I mentioned twrp remembered the settings and all that shiz. Or should I just try another ver of miui I have or the custom rom I've downloaded?
Also to get into edl mode, does both of these requirements needed to be met? Or any 1 should work? :-
Authorised account - So who can get this? Is there any bypass or workaround for it?
Test Point - I don't wanna open my phone, as you know it's new & all, tho it's not a problem if there's no other way. It's just that I have some bad memories regarding test point of my beloved RN3(now dead) so I just wanted to stay away from hardware as long as possible. Is there any bypass or a workaround for it?
................................................................................................................................................................................
Gurkirat_Singh said:
@YasuHamed
1. I tested the third file. It worked without any problems even after flashing magisk. Cause it doesn't mess or flash any magisk files, it also detects what sort of root the phone have.
we i am glad , we have a winner here
3. -> 2. I used the same app to check so.
3. You mention some good points there. That's the same reason, things worked out in custom roms and not miui in my earlier experiences. As miui is heavily loaded compared to any custom rom or samsung experinece. I'll try it on other OSs and report back. On the same note, from what I've read that lineage team doesn't release stable builds or at least not anymore. I'm currently downloading pixel experience. Should I go with this one or lineage os? Is it like any other custom OS or heavily loaded like miui? Also what is the difference between PE normal vs plus vs caf? Also I'm gonna try multi rom, as it would be much better for testing.
Temporarily , LOS is suspended but even unofficial roms till mid August are very stable ! you should try! , hoever Pixel is very popular too, on deeper level what diferences you may find thats only user can discover over time. there is no direct answer to this question! LOS is driven from CynogenMod which was on AOSP wehre Pixel is CAF based, so the difference comes on Kernel Level this means CAF rom may have different Hardware performance / behaviour when compare to AOSP based roms (and vice versa). I am not sure about multirom as a daily driver, yes I would like to try for fun but wont keep it.
4. (new) As you said you use havoc os or havoc kernel I think. Which other custom roms have you tried? Is havoc your favourite one? What sort of uses you make with these custom OSs, just normal daily use or something else? Or anything else you wanna share in this manner about your experience, recommendations or anything else.
on Poco i have tried Nitrogen, Omni, MoKee, BootLeggers, CrDroid, LOS and Havoc..
BootLeggers is pretty stable rom! however CrDroid is outstanding because the developer @gwolfu is more active and releases many updates (sometimes 3-4 in a month). Crdroid has serious level of customization (dirtyUnicorn) and you can change the look of your rom in every possible way you imagine!
so the question is WHY am I on Havoc, well the simple answer is both Crdoid and Havoc Offers serious level of DU customization & variations found on deeper level. some items which crdroid doesn't offer i found in Havoc so I stick to it, moreoever I feel the font and resolution by default in havoc is next to pixel where in Crdoid you manualy have to fix (dpi and font)
now I am on havoc2.8 but I am using Optimus Drunk Kernel (which is also used by CRDROID) - the developer of havoc2.8 offers SHADOW kernel which as I said I feel is not very battery effcient (atleast for me, others can disagree)
5. I think I understand a bit, if I use the option 'swipe to allow system modifications' and do not root my device i.e. not flashing magisk which in turn won't disable dm-verity and then if I try to boot to system, it'll go in booloop?
IF I'm right, then what is "read only & root" vs "allow system modifications & root"? Also I have the latest magisk version. What I was trying to say, "When I flashed the 'first' file out of the three 'dfet' files, it flashed magisk 16.7 as well causing latest magisk manager to not work", which I figured out and fixed immediately.
-keeping system Read only OR swipe to allow /system as writable is on Recovery Level ,
- when you keep system on READY ONLY on recovery Level and later flash magisk, the module magisk modify the /system permission which twrp doesn't know!
-if you "allow system modification on twrp level the /system is now set on writable permission by twrp, and magisk is a module which is always set to alter /system partition permission irespective of Global policy on recovery level
Also when the first time I flashed twrp, only then I got these options. But later on when I flashed the fresh rom through fastboot and then the recovery I simply got booted to the main menu without getting to choose any of these options. During that, I formatted all the stuff like system, internal storage etc. which i wasn't supposed to format, cause of which I had to flash again, but I forgot to select the 'clean all' option instead of 'clean all and lock' option. So i had to unlock again and flash twrp again. But even after all that twrp remebered all the changes I made to it like time, vibration, brightness settings and again it didn't showed any of those two options. More on this in the last response.........
now this let me think a little bit, the only possible explaination (in theory) I found is
- when you flash all or clean flash all, its not necessary that /recovery partition is first erased by miflasher! and recovery.img file has many folders including setting folder! so miflasher and later by you simply there was swaping of recoveries, the Tree was always there! when you reflashed twrp! try to do this way
Code:
fastboot erase recovery
fastboot flash twrp.img
this should erase any previous left over data and settings
try and let me know!
6. And again you gave me the link to miui's official website. I was asking how'd you find all those older roms at one place.
i simply google / web search rom number with device name with code name like Miui9.6.20 fastboot download poco f1 beryllium and google suggest few popular results which usually works for me!
7. So I finally flashed miui rom today, having high hopes, which were proven to be right first then crushed down later. After I flashed the rom, I tested the heck out of it like turning data on/off, usb tethering on/off, no problem occured, didn't found any bugs except one in data usage, it was showing like 100-600gigs(I don't remember exactly) of usage, then it started showing 1300-1400gigs, but after seeing that my confidence dipped down a little.
But still I moved on and flashed twrp on it to get it rooted. After rooting everything was fine even the data usage bug also went away, then I installed gltools and I had my phone connected to pc in usb tethering, suddenly I hear a sound(it restarted<insert gta sa cj meme>) and it starts all over again. I flashed 9.6.14 ver of rom btw.
I would say 9.6.14 had bug so reflashing didnt help! as I said before, consider upgrading atleast to 9.6.20
As you already know from my response above that I was only able to flash through fastboot mode and I wasn't able to get into edl mode as I read just a few hours ago that it's locked away. So my question is, is there a chance that this all could be solved if the rom is flashed through edl. As that's much more of a clean install rather than fastboot, as I mentioned twrp remembered the settings and all that shiz. Or should I just try another ver of miui I have or the custom rom I've downloaded?
Also to get into edl mode, does both of these requirements needed to be met? Or any 1 should work? :-
Authorised account - So who can get this? Is there any bypass or workaround for it?
Test Point - I don't wanna open my phone, as you know it's new & all, tho it's not a problem if there's no other way. It's just that I have some bad memories regarding test point of my beloved RN3(now dead) so I just wanted to stay away from hardware as long as possible. Is there any bypass or a workaround for it?
till MiMax
-holding THREE buttons for 30 seconds used to trigger edl mode
-miflasher simply identify EDL mode and used to flash the beryllium fastboot rom
the question is why they stopped?
well fastboot rom when extracted, hackers can simply alter and repack the img files! YOU CAN EVEN place twrp as "recovery.img" in extracted folder miui will flash twrp thinking its vendor recovery! and the device in EDL mode will accept it..
this was serious security risk! so they capped EDL mode in both ends
- miuiflasher needs AUTHORISED ACCOUNT
- DEVICE won't enter in edl mode unless you remove back cover and under batter wire you short two motherboard points with thin wire or tweaser! (and immediately connect usb calbe to system)
now what can you do?
1. use older version of Miflasher which doesnt verify rom
2. user altered rom of specific build or time to WAKE UP your BRICKED device!
I have never done it so you need to investigate and use your poco as gunie pig to test these methods after REMOVING Back Panel (HIGHLY NOT RECOMENDED
or take device to authorised Mi Dealer and let them EDL for you!
Click to expand...
Click to collapse