I NEED Redmi Note 8 Pro firmware v11.0.7.0 PGGMIXM Can Anyone Help? - Redmi Note 8 Pro Questions & Answers

My Phone is UK version 6gb 128GB
MIUI version: MIUI Global | Stable 11.0.7.0 (PGGMIXM)
Android Version: 9 PPR1.180610.011
Security Patch: 2020-04-01
Did anyone get a backup of the above Android 9 firmware version before the upgrade to 10 came out.
The above version supports the new front camera shipped on newer devices.
If anyone was smart enough to make a backup please upload it some place. :fingers-crossed:
I was dumb on this occasion & never got a backup.

bigrammy said:
...MIUI Global | Stable 11.0.7.0 (PGGMIXM)
Android Version: 9 PPR1.180610.011
Security Patch: 2020-04-01
Did anyone get a backup ...
Click to expand...
Click to collapse
I have begonia_global_images_V11.0.6.0.PGGMIXM_20200108.0000.00_9.0_global.tgz (fastboot image), if you want it. Reply and I'll upload it somewhere.

Thanks for the offer but it has to be the v11.0.7.0. Sadly.
I have the v11.0.6.0 but as explained the front camera is not supported on newer built hardware using this firmware version. Basically mi changed the front camera and maybe other hardware on these devices. They unified the kernels in the latest 10 update but 9 is still fragmented.

bigrammy said:
Thanks for the offer but it has to be the v11.0.7.0. Sadly.
I have the v11.0.6.0 but as explained the front camera is not supported on newer built hardware using this firmware version. Basically mi changed the front camera and maybe other hardware on these devices. They unified the kernels in the latest 10 update but 9 is still fragmented.
Click to expand...
Click to collapse
The v11.0.7.0. is an OTA recovery update, did you try to get it through updates?

No OTA's for me except the latest Android 10 update. This 11.0.7 firmware is not available any place and I have searched every official source. Since mi didn't do an official release of this firmware for the begonia I think it's the on device shipped firmware so someone would of needed to make a backup. I never gave it a second thought thinking everything would be Equal but it seems not. :crying:

OK then maybe @bigrammy could try the next update to see what happens, no need to update but only to download the package and share it here.
I also searched and nothing.
Maybe you could try with this guide https://forum.xda-developers.com/mi-mix-2/how-to/guide-reverse-engineering-xiaomi-ota-t3691612 I used to use similar method to catch some early updates on Samsung devices although is pretty probable that Xiaomi dropped this release for some reason.

SubwayChamp said:
OK then maybe @bigrammy could try the next update to see what happens, no need to update but only to download the package and share it here.
I also searched and nothing.
Maybe you could try with this guide https://forum.xda-developers.com/mi-mix-2/how-to/guide-reverse-engineering-xiaomi-ota-t3691612 I used to use similar method to catch some early updates on Samsung devices although is pretty probable that Xiaomi dropped this release for some reason.
Click to expand...
Click to collapse
Thanks but the only OTA I ever get is Android 10 even if I flash the the 11.0.6 firmware. I am well used to all this stuff rolling back and forth and capturing updates etc etc on many devices like Sonys, Nokia, etc but sadly nothing arrived for this v11.0.7.
I guess I will need to wait till someone does a backup of the shipped Android 9 firmware of these newer devices. :fingers-crossed:

@bigrammy
So...you need someone with new camera hardware and correct Android 9 version. Will TWRP backup be enough to get cam drivers?

wojownikhaha said:
@bigrammy
So...you need someone with new camera hardware and correct Android 9 version. Will TWRP backup be enough to get cam drivers?
Click to expand...
Click to collapse
That would be the dream my friend so if you have a TWRP backup of that firmware that would be totally awesome
I still kick myself now for NOT backing up my stock Android 9 first a total epic fail on my part.

bigrammy said:
I still kick myself now for NOT backing up my stock Android 9 first a total epic fail on my part.
Click to expand...
Click to collapse
Indeed. I didn't expect that Xiaomi changed front camera sensor. MIUI has terrible RAM management, so custom ROM is the only reasonable option.
To be honest I don't have TWRP backup, but I thought of buying a second N8 Pro, unlock it, take a TWRP backup and then return it to shop (with relocked bootloader of course).
If it helps the devs - why not?

wojownikhaha said:
Indeed. I didn't expect that Xiaomi changed front camera sensor. MIUI has terrible RAM management, so custom ROM is the only reasonable option.
To be honest I don't have TWRP backup, but I thought of buying a second N8 Pro, unlock it, take a TWRP backup and then return it to shop (with relocked bootloader of course).
If it helps the devs - why not?
Click to expand...
Click to collapse
OK I see. Well I wouldn't worry about it too much because without the camera driver kernel source there is not much can be done really.
The main reason for wanting the Android 9 stock ROM is I had hoped to try some experimentation using the Stock "kernel" which is fully compatible with the Engineering lk and preloader (Can Use SPFlashTool) .
I would not risk buying another one of these phones again until the official source code is updated with the New front camera driver until then we're kind of stuck.
I keep a close eye on any updates for this device and or any other Xiaomi MTK devices that could use this camera in the future.
GitHub - MiCode/Xiaomi_Kernel_OpenSource: Xiaomi Mobile Phone Kernel OpenSource
Xiaomi Mobile Phone Kernel OpenSource. Contribute to MiCode/Xiaomi_Kernel_OpenSource development by creating an account on GitHub.
github.com

bigrammy said:
Xiaomi_Kernel_OpenSource/imgsensor_sensor_list.c at cezanne-q-oss · MiCode/Xiaomi_Kernel_OpenSource
Xiaomi Mobile Phone Kernel OpenSource. Contribute to MiCode/Xiaomi_Kernel_OpenSource development by creating an account on GitHub.
github.com
use camera driver #if defined(S5K3T2SUNNY_MIPI_RAW) #if defined(S5K3T2OFILM_MIPI_RAW) from above thanks.
Click to expand...
Click to collapse
Looks good. Are that a new drivers for our devices?

wojownikhaha said:
Looks good. Are that a new drivers for our devices?
Click to expand...
Click to collapse
They are used in Redmi K30 Ultra which is MTK SoC also so merging the selfie camera drivers into the (begonia) RN8P should be doable.
I am not 100% sure if they would be compatible or if they still rely on (need) the base S5K3T2_MIPI_RAW driver.
Comms with the main dev's is pretty poor and it seems like a bit of a closed club so I can't really ask any meaningful questions. I can only suggest and point and hope they pick it up and use it if it's workable.
I raised an issue on github some time ago but never got any reply just a bunch of commits that seemed unrelated to the camera. https://github.com/AgentFabulous/begonia/issues/1
We could do with a commited XDA kernel dev who is happy to use this forum platform rather than "social media like telegram, twitter, facebook sort of nonsense" which is not my idea of sharing and Learning.
Following anything on those platforms is near impossible for me as everything is a bunch of fragmented one liners
Maybe it's a age thing IDK (It means I Dont Know seemingly )

@bigrammy
I recieved new Note 8 Pro and - guess what - production date is July 2020.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am going to see what version of firmware is installed but.... I don't expect much.
----
EDIT. Version 11.0.5.0(PGGEUXM) Kill me.

wojownikhaha said:
@bigrammy
I recieved new Note 8 Pro and - guess what - production date is July 2020.
I am going to see what version of firmware is installed but.... I don't expect much.
----
EDIT. Version 11.0.5.0(PGGEUXM) Kill me.
Click to expand...
Click to collapse
Yes that's the EU firmware for the Newer Camera like mine. If you could make a backup that would cool

I have it. how to backup the rom?

@kinder_surprise
First - you have to unlock bootloader and then install non CFW TWRP Recovery

kinder_surprise said:
I have it. how to backup the rom?
Click to expand...
Click to collapse
As @wojownikhaha as said the first step is to unlock the bootloader following the official way which is a long drawn out process sadly.
Once you have unlocked the bootloader you need to flash the engineering preloader and LK from here https://forum.xda-developers.com/t/guide-info-psa-redmi-note-8-pro-megathread-cfw.4056527/
Personally I would then just use SPFlashTool to do a "Read Back" of the device as I am not 100% sure if TWRP would boot without a modified boot.img installed which would require overwriting OUR stock boot.img with a boot.img from the other devices without these newer cameras if that makes sense
Put simply we need a copy of our device boot.img.
If TWRP is allowed to boot without any mods to the boot.img then fine simply make a TWRP backup.
Otherwise SPFlashTool is needed to do a backup of our stock partitions.
Let me know what level your at with all this stuff so we can better guide you if required.
Thanks bigrammy

bigrammy said:
I am not 100% sure if TWRP would boot without a modified boot.img
Click to expand...
Click to collapse
I confirm - this is possible. I was able to boot to recovery just after installation (on first Note with 11.0.7.0)
Anyway, I will provide full TWRP backup of stock 11.0.5.0 on next Thursday.

wojownikhaha said:
I confirm - this is possible. I was able to boot to recovery just after installation (on first Note with 11.0.7.0)
Anyway, I will provide full TWRP backup of stock 11.0.5.0 on next Thursday.
Click to expand...
Click to collapse
Hi Thanks for the confirmation that it is possible to boot TWRP without the need to flash a modified boot.img first.
Looking forward to the EU 11.0.5.0 firmware
@kinder_surprise
This info will make things much easier

Related

Samsung S4 Mini LTE i9195 - Stock ROM with Stagefright Security Fix

Just upgraded to the latest Stock ROM for Europe I9195XXUCOH2:
samsung-firmware.org/model/GT-I9195/
samsung-updates.com/device/?id=GT-I9195
sammobile.com/firmwares/database/GT-I9195
When running Stagefright Detector it only shows the following red vulnerability:
CVE 2015 6602 - Requires clicking a web-link, that opens video in the web-browser.
P.S. Had to flash twice as the baseband didn't upgrade the first time, and caused WIFI not to work (Would not turn on).
P.P.S. Used the O2-UK ROM and it changes the bootup-screen and also replaces the Google App Store with its own. Had to manually install Google App Store.
Gives me hope that there will be a fix later for stage fright v2. Though this release was 1 and half months after it was compiled so.... Also the fact O2 has released this but Samsung has yet to release the updated unbranded software is a bit of bull. Phone manufacturers and Google need to get their ass in gear..
Just updated to I9195XXUCOI5 (Spanish), and now Stagefright Detector shows all tests as green.
Also the bootup-screen is back to normal, along with the Google App Store.
Did you (have to) factory reset after flashing?
nick_white said:
Did you (have to) factory reset after flashing?
Click to expand...
Click to collapse
I flashed on top of my existing 4.4.2. Stock ROM, and just had to re-root.
But I guess it would be a good idea to make a backup of text-messages and other stuff.
Hi. My phone was rooted and when i checked it through stagefright except two all were red. And after i saw your comment., i flashed my phone but with original stock rom. and did reset and everything. Still same options are red.
syednawaz said:
Hi. My phone was rooted and when i checked it through stagefright except two all were red. And after i saw your comment., i flashed my phone but with original stock rom. and did reset and everything. Still same options are red.
Click to expand...
Click to collapse
Guess I have a special phone, or maybe something went wrong when flashing. Just re-verified that I have the latest version of stagefright detector from Google App Store, and all tests are green.
snakefoot said:
Just updated to I9195XXUCOI5 (Spanish), and now Stagefright Detector shows all tests as green.
Also the bootup-screen is back to normal, along with the Google App Store.
Click to expand...
Click to collapse
Going to try this tonight when I get home. Currently running the UK O2 firmware, but all but one of the patches shows green. Fingers crossed this new Spanish ROM will be green across the board.
This has really p!&&ed me off! Android phone manufacturers are sooo slow to update their devices. I can understand that some updates like new looks are over looked for older devices, but when it comes to security THEY have a duty to keep their products secure! There needs to be a new system for security updates. This stage fright bug is HUGE in my opinion. Phone manufacturers really don't give a sh!t about their customers, its all about the money. I never had these worries on my Nokia 3310...
I'm so concerned that I'm seriously thinking about getting an iPhone, much better software ecosystem. I just hate IOS compared. It's that or be forced to buy an expensive galaxy S6 or maybe a Moto G 2015 which I've heard has software updates comparable to the Google Nexus phones, which I personally think are a bag of crap...
Samsung being such a BIG concern in the smart phone world are just crap for software support.
I know there are custom ROMs that offer regular updates and the latest patches, but for me NONE of these are stable on my 5 month old device to the point where they can't be run as daily drivers... That and you lose any warranty you had, which is 2 years for Samsung....
Now I'm stuck with laggy stock OS, and I'm regretting getting this phone on contract.
If people were more aware of how insecure there phones really are I think they might not so easily choose android or at least the hundred odd older devices still available for purchase.
I'm so angry its funny... I'm one click away from dumping Samsung for the foreseeable future...
snakefoot said:
I flashed on top of my existing 4.4.2. Stock ROM, and just had to re-root.
But I guess it would be a good idea to make a backup of text-messages and other stuff.
Click to expand...
Click to collapse
I also have 4.4.2 stock.
I am concerned of the difference between CSCs, that there might be strange behavior. So you flashed, didn't reset and everything's fine, no force closes & stuff?
nick_white said:
I also have 4.4.2 stock.
I am concerned of the difference between CSCs, that there might be strange behavior. So you flashed, didn't reset and everything's fine, no force closes & stuff?
Click to expand...
Click to collapse
I did format the cache-partition and also cleared the dalvik-cache.
Thanks for this info, did not see that before.
From the information at Samsung Firmwares Database, the last Spanish ROM is not for LTE? or ist it also fine for LTR?
Franktdf said:
Thanks for this info, did not see that before.
From the information at Samsung Firmwares Database, the last Spanish ROM is not for LTE? or ist it also fine for LTR?
Click to expand...
Click to collapse
I have a S4 Mini LTE and the spanish ROM works fine with mine, and gives me 4G connectivity.
I am hoping for further firmware updates. Everything is red for me except two, as mentioned by someone else. I updated to the latest firmware from May on Three. I thought it was confirmed we were going to get version 5 of Android on the S4 mini... still waiting. I had 4.4.2 before from my last update and then this new update is ALSO 4.4.2...... What got updated? Just patches on things or something? No upgrade of the OS?
Morthawt said:
I am hoping for further firmware updates. Everything is red for me except two, as mentioned by someone else. I updated to the latest firmware from May on Three. I thought it was confirmed we were going to get version 5 of Android on the S4 mini... still waiting. I had 4.4.2 before from my last update and then this new update is ALSO 4.4.2...... What got updated? Just patches on things or something? No upgrade of the OS?
Click to expand...
Click to collapse
Very certain that S4 Mini will not get Android ver. 5.
This is my device status:
- Android Version: 4.4.2
- Kernel Version: 3.4.0-5878679 (23 Sep 2015)
- Build Number: KOT49H.I9195XXUCOI5
Think it is only security fixes, and system-app updates.
Morthawt said:
I am hoping for further firmware updates. Everything is red for me except two, as mentioned by someone else. I updated to the latest firmware from May on Three. I thought it was confirmed we were going to get version 5 of Android on the S4 mini... still waiting. I had 4.4.2 before from my last update and then this new update is ALSO 4.4.2...... What got updated? Just patches on things or something? No upgrade of the OS?
Click to expand...
Click to collapse
The Lollipop update for the S4 Mini got canceled a long time ago
http://www.youmobile.org/blogs/entr...ini-after-all-didn-t-pass-the-Testing-Process
No Stagefright with the Spanish Stock ROM anymore
WIth the Spanish ROM no Stagefright Security problem as of today anymore. :good::good::good:
(My only problem is now, that the phone is getting quite slow, maybe some app . . . )
Have now updated to the latest I9195XXUCOJ1 (TIM), and it feels a lot faster.
Sadly enough the preloaded TIM-applications fills up the entires System-partition, so if wanting to install other apps, then one have to cleanup a little first.
For some unknown reason the Xposed Framework Installer will not install, and gives the following warning:
Xposed is not (yet) compatible with Android SDK version 19 or your processor architecture (armeabi-v7a)
WARNING: Linker: /data/datade.robv.androi.xposed.installer/cache/app_process has text relocations.
CANNOT LINK EXECUTABLE cannot locate symbol "_ZN7android14AndroidRuntime5startEPKcS2_" referenced by /data/datade.robv.androi.xposed.installer/cache/app_process
Seems to be caused by a new security fix: https://android.googlesource.com/pl...+/d4d3181d013f8d9b96de8e396b029f8a418894a7^!/
More Details: http://forum.xda-developers.com/xposed/xposed-android-4-4-4-t3249895
Found solution: http://forum.xda-developers.com/showpost.php?p=64063168&postcount=62
snakefoot said:
Have now updated to the latest I9195XXUCOJ1 (TIM), and it feels a lot faster.
Sadly enough the preloaded TIM-applications fills up the entires System-partition, so if wanting to install other apps, then one have to cleanup a little first.
For some unknown reason the Xposed Framework Installer will not install, and gives the following warning:
Xposed is not (yet) compatible with Android SDK version 19 or your processor architecture (armeabi-v7a)
WARNING: Linker: /data/datade.robv.androi.xposed.installer/cache/app_process has text relocations.
CANNOT LINK EXECUTABLE cannot locate symbol "_ZN7android14AndroidRuntime5startEPKcS2_" referenced by /data/datade.robv.androi.xposed.installer/cache/app_process
Seems to be caused by a new security fix: https://android.googlesource.com/pl...+/d4d3181d013f8d9b96de8e396b029f8a418894a7^!/
More Details: http://forum.xda-developers.com/xposed/xposed-android-4-4-4-t3249895
Click to expand...
Click to collapse
EDIT 2: Using files extracted from an older build of stock kit kat I managed to get Xposed working on the latest stage fright fixed Italian stock firmware. Picture shows which files located in system bin and system lib.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
EDIT: OK I tired this stock rom with xposed and like yourself it doesn't want to install the framework.. The patch from Lombartz thread doesn't work with stock roms. It's got to do with sine new security patch. I'm thinking maybe an older version of the 2 files affected might work. Going to try later. That or ask Lombartz what he did to get it working.
Maybe try the fix for xposed from Lombartz in his cm11 rom and kernel thread. http://forum.xda-developers.com/sh...ht v2)(ECOACTIVE & ECOPLUG)(OC/UV)(20151116) Might work on stock rom too.
I have installed the latest Stock-ROM I9195XXUCPA1, and it works good.
I have tested with AndroidVTS v.13 and it shows that CVE-2015-6616 remains red (All other tests are green).
snakefoot said:
I have installed the latest Stock-ROM I9195XXUCPA1, and it works good.
I have tested with AndroidVTS v.13 and it shows that CVE-2015-6616 remains red (All other tests are green).
Click to expand...
Click to collapse
can you PLEASE help me with my phone (i9192) Stagefright bug ?
all custom ROMS (touchwiz kitkat ) for this models have 7 critical Stagfright bugs , please help me at least remove some of them because i cant find nothing on the net

[Q] Modding on HTC 10

Hi,
any leak, prevision about modding for this device?
I mean, will CM, AOSPA, AOKP etc support it officially? How is the situation with the other HTC's flagships?
Can it be unlocked as M7 with HTC dev site?
Thank you guys
davide136 said:
Hi,
any leak, prevision about modding for this device?
I mean, will CM, AOSPA, AOKP etc support it officially? How is the situation with the other HTC's flagships?
Can it be unlocked as M7 with HTC dev site?
Thank you guys
Click to expand...
Click to collapse
Bit early considering we aren't even positive what the final product's hardware will entirely be Can't wait though
can't wait too that's why i have written xD i don't know what to buy, my s6 is the worst phone for modding and updates, 1 year and i still have not rooted anything! I was getting used to root the first day when i was buying new phones don't want my next phone to be like s6
davide136 said:
can't wait too that's why i have written xD i don't know what to buy, my s6 is the worst phone for modding and updates, 1 year and i still have not rooted anything! I was getting used to root the first day when i was buying new phones don't want my next phone to be like s6
Click to expand...
Click to collapse
Exactly that's what I'm afraid of, too. If I decide to buy a new phone, I'd like to compile ROMs for it by myself, too, but therefore the vendor, device and kernel tree need to be published by HTC. I've just been looking around how custom development for the HTC One M9 looks like. Although I couldn't find many ROMs, there are official Cyanogenmod versions and open device and kernel trees. Thus I could compile many ROMs for the One M9. This gives me hope regarding the HTC 10. The Galaxy S6 instead didn't have no huge moding posibilities. There's only an unofficial, unstable device and kernel tree alongside a bugy CM-version. Just like the S6 the S7 probably won't get huge development support as well. This is what gives me hope regarding the HTC 10.
The only question I'm currently asking myself is if I should buy the HTC 10 or wait for the Oneplus 3 which will be published later in Q2 2016. Compared to the OP2 and OP1 it'll be a bit more expensive but it'll also be better equiped. Furthermore the price will probably be much lower than the price of the HTC 10. What are your expectations and what have you been able to definitely find out so far?
I'm still tryng to figure out what to do...lg has dropped support for rooted or bootloader unlocked device in italy, and the g5 seems to be a bit strange te me, i mean, it's not as premium as g4..regarding oneplus devices, for the 1 and 2 i read about bad screens and something else wich i don't remember, never saw one...i'd prefer staying on a strong brand...samsung obviously is exhiliated from any decision...sony maybe but no xD never liked the screens in the past...
My old nexus 5 make me wish about a decent nexus around 5" screen, I'd really love it, especially powered from a snapdragon 820 cpu..
Mi5 is lovable, but, you know...it's xiaomi...china brand, china support, 30 days for travelling a device if something happens, and that is for 2 times...its frightening xD
Htc 10 seems to be the best choice, ut will surely be premium, even if it does not have a good camera i don't care, just bought an eos 700d xD i just hope there will be a lot of modding, that is why i asked here
Htcdev.com is still working good for all the other htc, it must have decent modding, i think I'll go for it. At least, that's what I'm thinking now...but who knows
Inviato dal mio SM-G920F utilizzando Tapatalk
Yeah, Xiaomi is a brand I've been looking at over the last two years. I recommended Xiaomi phones to friends who wanted to have good and cheap devices. They are lucky all together but the only phone by Xiaomi I'd buy is the Mi Note Pro as a phone should have 5,7 inch in my opinion. I'd also like to have an AMOLED-Display in my next device so I hope HTC will release a bigger version of the 10 as well. The LG G5 is not really what I am looking for since it's a bit strange to have several components you can choose from. I think I'll buy a OP3 when it's published as it'll probably be more developer friendly but maybe the 10 by HTC will convince me, too. I'm really excited about the upcoming devices especially because my Nexus 4 from 2012 becomes slower and slower. Very anoying. Maybe a new Nexus will be released at the Google IO this year. This would be awesome. Anyway, I hope the potent upcoming phones will come sooner than later as I don't know how long my N4 will survive.
Very informed you guys are. I like this thread cause' I think a lot like you.
Sent from my Nexus 5 using XDA-Developers mobile app
Also looking for an answer on this: I was tempted by the Galaxy S7, but the huge issues I've had running anything but TouchWiz based ROMs on my S4 (and so issues running anything Marshmallow based) have put me right off.
How easily moddable have HTC phones been in recent years?
Rohaq said:
Also looking for an answer on this: I was tempted by the Galaxy S7, but the huge issues I've had running anything but TouchWiz based ROMs on my S4 (and so issues running anything Marshmallow based) have put me right off.
How easily moddable have HTC phones been in recent years?
Click to expand...
Click to collapse
The M7, M8, M9, and A9 are all very easy to do basic modding on. Getting s-off and deep modding is a different story. On the M8, at least, you can flash custom ROMs and kernels without s-off, so basically everything most people needs
Anonaru said:
The M7, M8, M9, and A9 are all very easy to do basic modding on. Getting s-off and deep modding is a different story. On the M8, at least, you can flash custom ROMs and kernels without s-off, so basically everything most people needs
Click to expand...
Click to collapse
Well, looks like it paid to wait then, come on, release day!
Anonaru said:
The M7, M8, M9, and A9 are all very easy to do basic modding on. Getting s-off and deep modding is a different story. On the M8, at least, you can flash custom ROMs and kernels without s-off, so basically everything most people needs
Click to expand...
Click to collapse
does it mean that with m9 if you do not s-off you can't touch system, boot or recovery partition? ( i'm still leaving in the time when you did fastboot oem unlock and everything was ok )
davide136 said:
does it mean that with m9 if you do not s-off you can't touch system, boot or recovery partition? ( i'm still leaving in the time when you did fastboot oem unlock and everything was ok )
Click to expand...
Click to collapse
No, the things you can't do without S-Off are:
*flash unsigned firmware packages
*flash firmware packages that don't match CID/MID
*flash RUUs that don't match CID/MID
*change CID/MID
*restore "locked" status (without you can only get "relocked" status)
*restore "software status: official" flag in bootloader (flag sets to "software status: modified" if you flash anything)
What you can do without S-Off:
*unlock bootloader (via HTCdev)
*flash recovery
*root (via superSU package or your favorite custom ROM)
*flash ROMs
0verdaflow said:
When is this gonna be released ??
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Click to expand...
Click to collapse
we will know tomorrow on the announcement but the leaks lead so far for beginning of May release
JEANRIVERA said:
we will know tomorrow on the announcement but the leaks lead so far for beginning of May release
Click to expand...
Click to collapse
Maybe there's another HTC phone to come in early may, hopefully a phablet but let's see...
Anyone know how we will get root on the unlocked version?
km8j said:
Anyone know how we will get root on the unlocked version?
Click to expand...
Click to collapse
By flashing TWRP Recovery then flashing the current SuperSU package ( or use the built-in TWRP option to flash SuperSU if available)
Behold_this said:
By flashing TWRP Recovery then flashing the current SuperSU package ( or use the built-in TWRP option to flash SuperSU if available)
Click to expand...
Click to collapse
Is this a big process? Is everything already available? Does any part of the rooting process wipe the device? If so, may make more sense to just do it right out of the box to avoid losing info
TWRP can already be found and downloaded; at least if one will look for it at the right place . I already downloaded it. SuperSU can as well be downloaded for MM devices. By this I'd guess the root procedure can be done as it always has been.
Sent from my HTC One M9 using XDA Labs
HTCNerdYoda said:
TWRP can already be found and downloaded; at least if one will look for it at the right place . I already downloaded it. SuperSU can as well be downloaded for MM devices. By this I'd guess the root procedure can be done as it always has been.
Click to expand...
Click to collapse
But does the bootloader unlock wrote y the phone?
km8j said:
But does the bootloader unlock wrote y the phone?
Click to expand...
Click to collapse
If you meant wipe the phone, then yes, it does.

Cannot flash Global ROM to Mi Max 32GB/3GB

This is my first Xiaomi phone and it seemed to arrive with a Chinese ROM on it (V7.3.14.0.MBCCNDC) so I have been trying to change it to a proper official Global ROM with zero success so far.
I have downloaded the ROM from here: http://en.miui.com/download-302.html
Filename: miui_MIMAXGlobal_V7.5.3.0.MBCMIDE_267a7c4439_6.0.zip
If I follow either of these guides (I do not need TWRP, just the official ROM) then I always end up failing at the same part.
http://forum.xda-developers.com/mi-max/how-to/installing-twrp-locked-bootloader-t3406501
http://en.miui.com/thread-307139-1-1.html
I reboot the phone into EDL mode by holding down both volume buttons and then connecting a USB cable after the phone has vibrated and stayed on a black screen. The PC then detects the phone as a Qualcomm device and assigns a port number to it.
MiFlash then finds the port number and I point the file browser to the extracted zip folder named: miui_MIMAXGlobal_V7.5.3.0.MBCMIDE_267a7c4439_6.0
After selecting the clean all radio button at the bottom and then pressing the flash button the status and time elapsed meters start moving and then after a few seconds the status changes to 'can not read from port COMxx' (I have used a few different port numbers so it can be COM10, COM20, COM3 etc).
So far I have tried this on three different PC's, 2 running Windows 10 and 1 running Windows 7, and the result is the same every time.
If I download the update file on the phone, rename it to update.zip and then place the update.zip file in the root of the internal storage drive and choose update from file on the phone then the phone reboots to a spinning circle for a while before restarting normally.
I also tried rebooting the phone into recovery mode from the built-in update app and connected it to Mi PC Suite but that just updated it to V7.5.6.0 MBCCNDE which is another China ROM so its still of no use to me really.
Can anybody help with this? This process really shouldn't be so difficult and I am starting to consider sending this phone back. I have made an application with Xiaomi to have the bootloader unlocked but that can take over a week and tbh I don't really want an unlocked bootloader anyway because I have no interest in custom ROM's, root access or special recovery options.
I have seen many people with that problem and haven't seen any working solution yet...
I understand you don't want TWRP or unlocked bootloader but that's the only way you can get the job done and forget all these buggy Xiaomi tools.
Something else you can try... Google QFILwhich is the Qualcomm flash tool and does the same thing what MiFlash does. Search and read the guides how to unbrick Qualcomm devices with QFIL. All additional files needed like flasher, partitions.xml etc are in MIUI fastboot ROM already. Actually MiFlash is based on that tool I think...
Good luck.
nijel8 said:
I have seen many people with that problem and haven't seen any working solution yet...
I understand you don't want TWRP or unlocked bootloader but that's the only way you can get the job done and forget all these buggy Xiaomi tools.
Something else you can try... Google QFILwhich is the Qualcomm flash tool and does the same thing what MiFlash does. Search and read the guides how to unbrick Qualcomm devices with QFIL.
Good luck.
Click to expand...
Click to collapse
Thanks but I'm a bit cautious about being the first person to try to use that QFIL flashing utility with this phone, especially since this phone stupidly doesn't include an integrated recovery system. I've found a generic tutorial for it but it looks pretty scary tbh.
http://www.androidbrick.com/ultimat...agons-are-unbrickable-qhsusb_dload_qpst_qfil/
Incidentally when I updated the phone using Mi PC Suite it killed the Google Play Services and I couldn't fix them so I did a normal factory restore and it has restored to a standard China ROM (MIUI 7.5 | Stable 7.5.6.0 (MBCCNDE) so clearly the vendor flashed some weird custom version to this before they sent it to me.
Honestly, this thing is starting to drive me insane.
You have to use these drivers for your Qualcomm port: https://drive.google.com/file/d/0B9oNcsjcOpNHZjI1OWtFSDFfS3c/view?usp=sharing
Delete the original Windows driver and install it again through device manager.
TEKME said:
You have to use these drivers for your Qualcomm port: https://drive.google.com/file/d/0B9oNcsjcOpNHZjI1OWtFSDFfS3c/view?usp=sharing
Delete the original Windows driver and install it again through device manager.
Click to expand...
Click to collapse
Thanks, I'll give it a try with that driver tomorrow. I did try another driver that I found on Google as well as the auto installed driver because it looked like a communication problem to me.
There's a driver pack on that Xiaomi tips website but I haven't been able to install it because the hosting used by that website is terrible and it just times out.
OK so I think I updated the driver using the one from your link but unfortunately the error is the same.
I uninstalled the device through DM and it self-installed this driver.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then I used the Update driver > Browse > Let me pick > Have Disk option to force the driver from your link to install so the driver was updated to this:
The error in MiFlash is still exactly the same though: can not read from port COMxx.
OK the problem here seems to be that MiFlash cannot support standard recovery ROM's. It has to use those larger ones with the scripts etc included.
I was able to flash this with no problems whatsoever: http://en.miui.com/thread-324576-1-1.html
However I'm worried that might not be the official software and I want to keep this simple and official and get all updates OTA in future.
Unfortunately the only global full ROM available for this phone on the MIUI website is the Developer build.
http://en.miui.com/a-234.html
The version I have just flashed also doesn't include locales for the UK or Japan and I spend most of my time in those countries. I've set it to Singapore for now but I feel like I'm right back to square one with this thing.
From what I read official MIUI Global is missing many locales and that's why people are using xiaomi.eu ROM. I even suggested in there forum to stop calling it global b/c its not and call Asia or something...
nijel8 said:
From what I read official MIUI Global is missing many locales and that's why people are using xiaomi.eu ROM. I even suggested in there forum to stop calling it global b/c its not and call Asia or something...
Click to expand...
Click to collapse
The included country list on it is quite frankly bizarre. It includes some European countries but not others and has options for the Falkland Islands and St. Kitts but no option for Britain or the United States.
Yup no United States
When is the 64/128 global ROM coming out
Sent from my MI MAX using Tapatalk
badrsj said:
Yup no United States
When is the 64/128 global ROM coming out
Sent from my MI MAX using Tapatalk
Click to expand...
Click to collapse
8/16 if they get it right...
The problem is with no UK locale I don't know if I can get the IR Blaster working.
It's a small problem in the grand scheme of things but still one I would like to fix if I can.
@ Blood Rose - I am assuming so far you've kept the boot loader locked and flashed the global stable 7.5 version - on your 32 GB device? did you lose data - did you get any OTAs (security patches). I am looking to go to miui 8 - possibly chinese - the global development may not be as timely. Also I have the 64 gb version and there's not much going on the global ROM versions for that one.
badrsj said:
@ Blood Rose - I am assuming so far you've kept the boot loader locked and flashed the global stable 7.5 version - on your 32 GB device? did you lose data - did you get any OTAs (security patches). I am looking to go to miui 8 - possibly chinese - the global development may not be as timely. Also I have the 64 gb version and there's not much going on the global ROM versions for that one.
Click to expand...
Click to collapse
I did flash a global stable version of 7.5. It's the latest official rom I believe. I did a full wipe to make sure all traces of the Chinese stuff were gone. Because its the latest official version ut hasn't received any OTA updates yet but it at least seems to connect to the official servers to check whereas the ROM the phone came with couldn't.
My bootloader is now unlocked because the MIUI forum staff offered to do immediately for me so I figured I might as well but I will not be using root or any custom builds.
Thanks
Sent from my MI MAX using Tapatalk
am i totally ****ed up? searching how to change my shop rom to another rom for my 3gb/32gb and that what i found. So it is impossible to change rom in this smartphone???
presuntinho said:
am i totally ****ed up? searching how to change my shop rom to another rom for my 3gb/32gb and that what i found. So it is impossible to change rom in this smartphone???
Click to expand...
Click to collapse
That depends on what you want to change it to. If it is a newer/alternative official ROM then that is easy. If it is to a custom ROM then you need an unlocked bootloader.
BloodRose said:
That depends on what you want to change it to. If it is a newer/alternative official ROM then that is easy. If it is to a custom ROM then you need an unlocked bootloader.
Click to expand...
Click to collapse
For custom ROM you do not need unlocked bootloader.
nejcov said:
For custom ROM you do not need unlocked bootloader.
Click to expand...
Click to collapse
I neither know nor care about custom ROMs. I'm quite sure there is probably a way to circumvent Xiaomi's bootloader lock but I was just providing the standard textbook advice tbh.
BloodRose said:
I neither know nor care about custom ROMs. I'm quite sure there is probably a way to circumvent Xiaomi's bootloader lock but I was just providing the standard textbook advice tbh.
Click to expand...
Click to collapse
Hi BloodRose,
Does the Xiaomi ROM support large file sizes, like an HD movie?
I am doing research on the Mi Max before buying.
I am based in the US, and it will not be my primary phone.
Thanks,

[UNOFFICIAL][ROM] LineageOS 15.1 for Galaxy Tab E [SM-T560NU]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello my fellow SM-T560NU (gtelwifiue) owning friends, I thought I'd share with you my build of LineageOS 15.1.
This build contains the July 5 2019 security patch level. Please leave a thumbs up if this is useful to you.
If you need root, flash Magisk from recovery and install Magisk Manager.
I you wish to install the Google apps, flash opengapps from recovery after first boot (you need to get the ARM version for Android 8.1 nano package is recommended).
Code:
All information and files — both in source and compiled form — are provided on an as is basis.
No guarantees or warranties are given or implied. The user assumes all risks of any damages
that may occur, including but not limited to loss of data, damages to hardware, or loss of
business profits. Please use at your own risk. Note that unless explicitly allowed by the warranty
covering your device, it should be assumed that any warranty accompanying your device will
be voided if you tamper with either the system software or the hardware.
Download link: lineage-15.1-20190707-UNOFFICIAL-gtelwifiue.zip
Source: Galaxy-MSM8916 on Github
I have one of these tablets and would love to use it but the custom rom seems to slow it down. It's Android 7. I have TWRP in it but I cannot seem to find a lighter rom to help speed things up. Any thoughts, suggestions?
upyisfar said:
Hello my fellow SM-T560NU (gtelwifiue) owning friends, I thought I'd share with you my build of LineageOS 15.1.
This build contains the April 5 2019 security patch level, and I have not encountered any issues with it so far. Please leave a thumbs up if this is useful to you. I am planning to produce more builds of this ROM in the coming months.
Download link: lineage-15.1-20190409-UNOFFICIAL-gtelwifiue.zip
Source: Galaxy-MSM8916 on Github
Click to expand...
Click to collapse
Appreciate it. I hope you continue to support this tablet of mine ! I've been a fan of LineageOS for awhile !
Build 20190516
Here is a new build of that includes the May 5th 2019 Android security patch level.
lineage-15.1-20190516-UNOFFICIAL-gtelwifiue.zip
Can I install this ROM on a SM-T560 (Wi-Fi) tablet?
davideakc said:
Can I install this ROM on a SM-T560 (Wi-Fi) tablet?
Click to expand...
Click to collapse
Hello, I don't know if you can. This ROM is for devices codenamed gtelwifiue. You should search the forum and find out if the SM-T560 falls under that category.
Zbanded said:
I have one of these tablets and would love to use it but the custom rom seems to slow it down. It's Android 7. I have TWRP in it but I cannot seem to find a lighter rom to help speed things up. Any thoughts, suggestions?
Click to expand...
Click to collapse
Anything older than Nougat will probably suffer from multiple security vulnerabilities. Lineage 15.1 is the only ROM I found that works bug free on my tablet (14.1 has camera issues and 16.0 doesn't wake up when pushing the home button).
upyisfar said:
Anything older than Nougat will probably suffer from multiple security vulnerabilities. Lineage 15.1 is the only ROM I found that works bug free on my tablet (14.1 has camera issues and 16.0 doesn't wake up when pushing the home button).
Click to expand...
Click to collapse
same boat i am in sir
terribly slow with lineage 16
Here is a new build of that includes the June 5th 2019 Android security patch level.
lineage-15.1-20190612-UNOFFICIAL-gtelwifiue.zip
upyisfar said:
Here is a new build of that includes the June 5th 2019 Android security patch level.
Click to expand...
Click to collapse
What is the process after I download the file?
Just open it?
I am new to these kind of updates. Thank you for the post. Trying to get some good lock options on my 560.
tc3500 said:
What is the process after I download the file?
Just open it?
I am new to these kind of updates. Thank you for the post. Trying to get some good lock options on my 560.
Click to expand...
Click to collapse
Hi @tc3500. If you have a previous build of lineage os 15.1 installed you can just flash the new zip in twrp and then reboot. If your tablet is stock, then you need to first root it and then install twrp recovery for the gtelwifiue first. The procedure for doing this is explained in another post on the forum. Please ensure that your model is SM T560NU or else this ROM might not work.
upyisfar said:
Hi @tc3500Please ensure that your model is SM T560NU or else this ROM might not work.
Click to expand...
Click to collapse
I don't have Lineage and have not used TWRP.
But in will search for the thread with the information.
It has been awhile since I rooted a device. But I should be able to.
Thanks very much for your reply. I appreciate it.
.....And my model is exactly that number.
Says it's SM-T560NU. running 7.1.1, last patch 10/1/17.
---------- Post added at 11:54 AM ---------- Previous post was at 11:41 AM ----------
tc3500 said:
.....and my model is exactly that number.
Says it's sm-t560nu. Running 7.1.1, last patch 10/1/17.
Click to expand...
Click to collapse
sm-t560nuueu1cqk2.
tc3500 said:
I don't have Lineage and have not used TWRP.
But in will search for the thread with the information.
It has been awhile since I rooted a device. But I should be able to.
Thanks very much for your reply. I appreciate it.
.....And my model is exactly that number.
Says it's SM-T560NU. running 7.1.1, last patch 10/1/17.
Click to expand...
Click to collapse
From memory, I rooted my tablet by flashing CF-Auto-Root-gtelwifiue-gtelwifiue-smt560nu.zip using Odin (PDA button)on Windows. Can't remember if that gave me twrp or if I had to install it seperately. Hope this helps a bit.
Note: Enable Developer Options: go to Settings -> About device. Tap 7 times on Build number to enable Developer options. Enable OEM unlock and USB debugging options ( Settings -> Developer options )
Note: you will need to have the Samsung USB drivers installed, you can get those by installing the Samsung Kyes software.
Note: Make sure your device is in ODIN download mode (usually you can get there by holding VolDown+Home+Power when the device is turned off)
Backup of my twrp recovery in case you need it.
upyisfar said:
Note: you will need to have the Samsung USB drivers installed, you can get those by installing the Samsung Kyes software.
Click to expand...
Click to collapse
I will download TWRP and the drivers to my laptop.
The other functions are done. Really awesome of you to take your time and reply.
tc3500 said:
I will download TWRP and the drivers to my laptop.
The other functions are done. Really awesome of you to take your time and reply.
Click to expand...
Click to collapse
You're welcome. I hope you succeed at installing LineageOS 15.1 on your tablet. If anything goes wrong, you can download the original firmware for your device from the sammobile.com website and flash using 0din.
upyisfar said:
You're welcome. I hope you succeed at installing LineageOS 15.1 on your tablet. If anything goes wrong, you can download the original firmware for your device from the sammobile.com website and flash using 0din.
Click to expand...
Click to collapse
I have all of the files downloaded to my laptop.
And that took some time. I got a Note 9 last year and I rarely even turn my PC on anymore. So there were many updates and and misc things to attend. Also it is frustratingly slow compared to my phone, haha.
I do need to get CF Root.
But my concern is that my Tab E is a Wifi model. And I am not sure how to verify if it will accept this modification.
It is definitely an SM-T560NU. Specifically an
SM-T560NUUEU1CQK2. I think it's an A3L, not a
gtlewifiue. So I am trying to figure that out. I backed up the device and don't mind trying to move forward if there is more of a chance that I can at least recover it to oem rather than brick it. Any advice on verification of model or recovery if install fails?
Only a guess or opinion, I know that there are no guarantees, lol. But it is very slow and I do need to make my best attempt to improve it.
Thanks.
tc3500 said:
I have all of the files downloaded to my laptop.
And that took some time. I got a Note 9 last year and I rarely even turn my PC on anymore. So there were many updates and and misc things to attend. Also it is frustratingly slow compared to my phone, haha.
I do need to get CF Root.
But my concern is that my Tab E is a Wifi model. And I am not sure how to verify if it will accept this modification.
It is definitely an SM-T560NU. Specifically an
SM-T560NUUEU1CQK2. I think it's an A3L, not a
gtlewifiue. So I am trying to figure that out. I backed up the device and don't mind trying to move forward if there is more of a chance that I can at least recover it to oem rather than brick it. Any advice on verification of model or recovery if install fails?
Only a guess or opinion, I know that there are no guarantees, lol. But it is very slow and I do need to make my best attempt to improve it.
Thanks.
Click to expand...
Click to collapse
From what I gather the letters and digits that follow SM-T560NU describe the carrier or the country of origin but I could be wrong.
I can't advise you to try or not to try flashing this ROM but there is near certainty that you can restore your original firmware from this site using the Odin method if anything goes wrong as I've mentioned in my previous post. If what you're after is speed you could even flash an older firmware (lollipop or marshmallow) and disable auto-update but you'd be left exposed to multiple android security vulnerabilities that aren't present in this updated ROM.
upyisfar said:
From what I gather the letters and digits that follow SM-T560NU describe the carrier or the country of origin but I could be wrong.
I can't advise you to try or not to try flashing this ROM but there is near certainty that you can restore your original firmware from this site using the Odin method if anything goes wrong as I've mentioned in my previous post. If what you're after is speed you could even flash an older firmware (lollipop or marshmallow) and disable auto-update but you'd be left exposed to multiple android security vulnerabilities that aren't present in this updated ROM.
Click to expand...
Click to collapse
I keep the tablet pretty clean. It's an 'extra' device.
Don't really store anything on it. Use if for the web and take it on the boat or guests can use it. I will gl with 15.1 and see what happens. Thanks so much.
I did get the Firmware downloaded, that site is SLOW if you're cheap like me, haha. Hope your day is a good one.
upyisfar said:
From what I gather the letters and digits that follow SM-T560NU describe the carrier or the country of origin but I could be wrong.
I can't advise you to try or not to try flashing this ROM but there is near certainty that you can restore your original firmware from this site using the Odin method if anything goes wrong as I've mentioned in my previous post. If what you're after is speed you could even flash an older firmware (lollipop or marshmallow) and disable auto-update but you'd be left exposed to multiple android security vulnerabilities that aren't present in this updated ROM.
Click to expand...
Click to collapse
Does this look correct?
Is it the 0:[com5] that let's it know to flash the tablet and not my laptop? Lol......
---------- Post added at 10:38 PM ---------- Previous post was at 10:12 PM ----------
@upyisfar....
Did I need to install Lineage or TWRP to the tablet before rooting?
I used the cf-auto root file from the XDA Thread on rooting the sm-t569nu.
......here.... https://consumingtech.com/how-to-root-the-samsung-galaxy-tab-a-9-7/
tc3500 said:
Does this look correct?
Is it the 0:[com5] that let's it know to flash the tablet and not my laptop? Lol......
---------- Post added at 10:38 PM ---------- Previous post was at 10:12 PM ----------
@upyisfar....
Did I need to install Lineage or TWRP to the tablet before rooting?
I used the cf-auto root file from the XDA Thread on rooting the sm-t569nu.
......here.... https://consumingtech.com/how-to-root-the-samsung-galaxy-tab-a-9-7/
Click to expand...
Click to collapse
When I did mine almost a year ago, I rooted first, then I flashed the TWRP img from an app such as rashr or flashify (might have to install the SuperSU app first to get the permission dialogs). Then rebooted into recovery and flashed lineage from there. But now I'm wondering if you might be able to flash TWRP directly from Odin without needing to root first. I wish someone with a fresh experience could chime in here.
Anyhow here's a video I came across that might be helpful to you:
Samsung Galaxy Tab E 9.6 Root & Install TWRP Recovery 100% Working
And yes the SamMobile site is painfully slow but it is a lifesaver if you brick your device. Once you have obtained the firmware, it is really easy to recover your device with Odin.

Question Lack of development?

There has been 0 talk about any ROMs or development for the OP9 and it's been over a month since release. Does anyone know if any developers are working on one??
The OP9 and OP9 Pro don't even have unofficial or official TWRP support yet, so a custom ROM is kinda out of the question until TWRP is on the devices. OP9 Pro literally just got it's first custom kernel 2 days ago. I don't know what the time frame is for custom ROM development but a lot of it hinges on getting TWRP support for the phones.
Side note: You said OP9 in the OP9 Pro forums so I'm gonna assume you were referring to the OP9 Pro. Regardless my statement about needing TWRP support first applies to both phones.
GreaterLesser said:
The OP9 and OP9 Pro don't even have unofficial or official TWRP support yet, so a custom ROM is kinda out of the question until TWRP is on the devices. OP9 Pro literally just got it's first custom kernel 2 days ago. I don't know what the time frame is for custom ROM development but a lot of it hinges on getting TWRP support for the phones.
Side note: You said OP9 in the OP9 Pro forums so I'm gonna assume you were referring to the OP9 Pro. Regardless my statement about needing TWRP support first applies to both phones.
Click to expand...
Click to collapse
TWRP is absolutely not necessary and will most likely never come out for later OP devices, including the 9, unless they figure out the decryption problem. See the 8's etc, plenty of dev and none of the TWRP.
Regarding dev, it's happening, but no need for discussion here until something is at least in a semi-stable beta build.
craznazn said:
TWRP is absolutely not necessary and will most likely never come out for later OP devices, including the 9, unless they figure out the decryption problem. See the 8's etc, plenty of dev and none of the TWRP.
Regarding dev, it's happening, but no need for discussion here until something is at least in a semi-stable beta build.
Click to expand...
Click to collapse
I apologize for my lack of knowledge of what happened in the OnePlus 8 scene as I didn't have that phone. I came from the 6T. But looking through the 8, 8 Pro, and 8T forums, it seems a custom recovery is still needed for custom ROMs. Only difference was the custom recovery was provided by the ROM Dev and not TWRP.
It's early in the game.... will be happening!
ddizzy81 said:
There has been 0 talk about any ROMs or development for the OP9 and it's been over a month since release. Does anyone know if any developers are working on one??
Click to expand...
Click to collapse
We don't have a TWRP build yet, I've been looking to build one but there's a problem with Android Image Kitchen which should hopefully be fixed soon, I'm guessing that's why no-one else has built a recovery. You can read more about it here.
Custom roms are kinda a non-starter without TWRP (or another custom recovery)
OnePlus has been messing up with their source for a while now too, not to mention that we're still getting regular updates to the original release which might mess with kernels too.
We might be another month before you'll start seeing enough stability to start getting custom roms.
EDIT : Looks like AIK might be working properly now, gonna have a look and see if I can get a TWRP build working, although there's no other phones with the same resolution so that might be a problem to get some resources. LG G3 has a similar resolution but not exactly the same, it's very important for the touchscreen setup for TWRP or else the buttons on screen won't be where you're actually tapping.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
For anyone else who fancies trying their hand at it, there's a porting guide here.
To add to what @craznazn said, a custom recovery isn't 100% necessary for custom ROMs. The 7T didn't require it to flash any, as a fastboot method is doable. Developing them is another story, though. Some custom ROMs were based on OOS, while AOSP ones still had some bases from OOS (YAAP, for example, was a Pixel-themed ROM but required you to have OOS11, in some shape or form, installed prior to flashing it because it needed vendor files and so on.
djsubterrain said:
We don't have a TWRP build yet, I've been looking to build one but there's a problem with Android Image Kitchen which should hopefully be fixed soon, I'm guessing that's why no-one else has built a recovery. You can read more about it here.
Custom roms are kinda a non-starter without TWRP (or another custom recovery)
OnePlus has been messing up with their source for a while now too, not to mention that we're still getting regular updates to the original release which might mess with kernels too.
We might be another month before you'll start seeing enough stability to start getting custom roms.
EDIT : Looks like AIK might be working properly now, gonna have a look and see if I can get a TWRP build working, although there's no other phones with the same resolution so that might be a problem to get some resources. LG G3 has a similar resolution but not exactly the same, it's very important for the touchscreen setup for TWRP or else the buttons on screen won't be where you're actually tapping.
View attachment 5298703
For anyone else who fancies trying their hand at it, there's a porting guide here.
Click to expand...
Click to collapse
The Samsung Galaxy S20, and S20 Plus have a very close resolution to the OP9P
OP9P: 1440x3216
SGS20/SGS20+: 1440x3200
And they already have an unofficial twrp build too.
SGS20/SGS20+ TWRP:
[RECOVERY][UNOFFICIAL] TWRP for Galaxy S20 Series (Snapdragon)
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and...
forum.xda-developers.com
Hope this helps.
GreaterLesser said:
The Samsung Galaxy S20, and S20 Plus have a very close resolution to the OP9P
OP9P: 1440x3216
SGS20/SGS20+: 1440x3200
And they already have an unofficial twrp build too.
SGS20/SGS20+ TWRP:
[RECOVERY][UNOFFICIAL] TWRP for Galaxy S20 Series (Snapdragon)
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and...
forum.xda-developers.com
Hope this helps.
Click to expand...
Click to collapse
Sorry to say. But portions are what we are talking about. Resolution has no bearing on getting TWRP working. Ex op7tpro
toolhas4degrees said:
Sorry to say. But portions are what we are talking about. Resolution has no bearing on getting TWRP working. Ex op7tpro
Click to expand...
Click to collapse
Portions...? As in dimensions? It is true the screens are different sizes, as well.
In regards to OP's post that there's been 0 development talk, well, not exactly zero, as unlocking and rooting, as well as conversion from T-Mobile to global, enabling dual-SIM, and the MSM and QPST tools needed for such, have been ongoing for some time. There's no custom ROMs, sure, and I get that a custom kernel was just released, but a massive part of development is simply discussion, throwing around ideas, research, testing, etc. It also helps if more devs happen to purchase our particular device (and thankfully this is something we won't have to worry about for long). It's worse when a device gets little to no development because it simply isn't popular enough to warrant much development. I do get the sentiment that it's been a while, but I guess we'll just have to be patient.
GuyInDogSuit said:
Portions...? As in dimensions? It is true the screens are different sizes, as well.
In regards to OP's post that there's been 0 development talk, well, not exactly zero, as unlocking and rooting, as well as conversion from T-Mobile to global, enabling dual-SIM, and the MSM and QPST tools needed for such, have been ongoing for some time. There's no custom ROMs, sure, and I get that a custom kernel was just released, but a massive part of development is simply discussion, throwing around ideas, research, testing, etc. It also helps if more devs happen to purchase our particular device (and thankfully this is something we won't have to worry about for long). It's worse when a device gets little to no development because it simply isn't popular enough to warrant much development. I do get the sentiment that it's been a while, but I guess we'll just have to be patient.
Click to expand...
Click to collapse
Partitions sorry typo. Also they just released kernel sources not very long ago. In order to build you need these. The dev here had this up and running on his device for a while, but just like ROM devs the first two or three bases they make are not for public and take a long time to work out bugs. Secondly twrp is not required to flash a custom ROM did it via fastboot on my op7tpro. Development is up to owners. You have an unlocked bootloader and kernel sources. If everyone is *****in about development start developing. Download a Linux distro or wubi and and build one for the community. Everyone *****es and doesn't contribute.
toolhas4degrees said:
Partitions sorry typo
Click to expand...
Click to collapse
Ahhh. That makes more sense now.
GreaterLesser said:
The OP9 and OP9 Pro don't even have unofficial or official TWRP support yet, so a custom ROM is kinda out of the question until TWRP is on the devices. OP9 Pro literally just got it's first custom kernel 2 days ago. I don't know what the time frame is for custom ROM development but a lot of it hinges on getting TWRP support for the phones.
Side note: You said OP9 in the OP9 Pro forums so I'm gonna assume you were referring to the OP9 Pro. Regardless my statement about needing TWRP support first applies to both phones.
Click to expand...
Click to collapse
Op8 doesn't even have a working twrp for A11 yet. So that's not it at all. Twrp does nothing for our devices as far as roms or kernels. You flash a kernel through a kernel manager and All the roms flash through fastboot & fastbootd. That's def not it. But it will however take time. We need msm tools prior to messing with things anyway. Or we will all be in a brick like state. And a main dev for aospa which is Paranoid Android has a 9 . That will be soon I'm guessing.
mattie_49 said:
Op8 doesn't even have a working twrp for A11 yet. So that's not it at all. Twrp does nothing for our devices as far as roms or kernels. You flash a kernel through a kernel manager and All the roms flash through fastboot & fastbootd. That's def not it. But it will however take time. We need msm tools prior to messing with things anyway. Or we will all be in a brick like state. And a main dev for aospa which is Paranoid Android has a 9 . That will be soon I'm guessing.
Click to expand...
Click to collapse
Thanks - Someone already explained this earlier.

Categories

Resources